Loading
Loading
Trust center
Security buyers should be able to see what is real today, what is available by contract, and what is not certified yet. This page collects Hanasand security, procurement, data-handling, SLA, and onboarding facts in one place.
Diligence packet
How Hanasand handles watchlists, alert records, webhooks, API access, audit events, and operational logs.
Data processing terms, confidentiality language, order-form notes, and security questionnaire responses for procurement.
Infrastructure, database, mail/notification, payment, and customer-selected integration categories are listed below.
No badge is claimed today. The controls below are the current operating model and the gap is visible by design.
Public packet
Stable URLs a reviewer can inspect before opening a vendor portal.
Enterprise controls
These rows are intentionally plain. If a procurement team needs a control that is not available now, it should be visible before a pilot starts.
Buyer evaluation path
Established dark-web platforms may offer more certifications, references, and coverage claims. Hanasand is a fit when the buyer wants a direct watchlist-to-alert workflow and can verify the live product quickly.
Security model
The core monitoring path is designed around watchlists and alert metadata, not raw leak ingestion into customer dashboards.
Organization names, watched companies, domains, vendors, executives, API keys, webhook endpoints, user roles, and support context.
Matched term, source name, actor/company fields, timestamps, claim summary, status, confidence label, delivery result, and analyst review state.
Request IDs, route health, delivery attempts, error states, service checks, audit events, and rate-limit events needed to secure and operate the service.
Hanasand does not require customers to upload raw leak dumps, malware, production secrets, or unnecessary personal data to receive company exposure alerts.
Incident response
Security concerns, suspected unauthorized access, webhook exposure, and responsible disclosure reports should be routed through support with enough detail to reproduce and scope the issue.
Subprocessors and integrations
Security review path
Hanasand can package the current security overview, DPA request, subprocessor details, SLA notes, onboarding timeline, and questionnaire responses for a pilot or enterprise review.