Design Partner Program
TRUST CENTER

We test your defenses. Here's how we protect you while we do.

Hayrok runs offensive validation in customer environments, so we hold ourselves to a higher bar. This page covers our compliance, security practices, data handling and how every test is governed.

AT A GLANCE
Tests run only inside approved scope Every run
Every action approved and recorded Every run
Sensitive fields redacted before storage By default
Private Runner for internal scopes Available
SOC 2 Type I attested Current
COMPLIANCE

Frameworks and Attestations

SOC 2 Type I Design of security, availability and confidentiality controls. Attested
ISO/IEC 27001 Information security management system. Certified
GDPR EU data protection requirements. Compliant
CCPA California consumer privacy requirements. Compliant
CSA STAR Cloud security assurance registry. Listed
HIPAA Safeguards for health information. Compliant

Reports and certificates available on request under NDA

SECURITY PRACTICES

How We Secure Hayrok

Separation of duties Reasoning, approval, execution, validation and evidence run as separate components.
Secure development Code review on every change, dependency scanning and secrets detection in CI.
Validating ourselves Hayrok runs its own validation against Hayrok, and findings are tracked like any customer's.
Penetration testing Independent third-party testing of the platform.
GOVERNED TESTING

Safeguards for Testing in Your Environment

What makes Hayrok different from other vendors is also its biggest trust question. These controls apply to every run, on every plan.

Approved scope only Targets outside the scope lock are denied, not warned.
Named approvals Every run has an approver from the target's owning team.
Safety levels Destructive techniques are blocked from production by policy.
Rate limits and circuit breakers Runs pause automatically if a target degrades.
Test identities only Agents act as labelled test accounts, never real users.
Kill switch One action stops every agent in your tenant.
How safe production testing works →
DATA HANDLING

What We Collect, and What We Don't

WE KEEP+Scope definitions, approvals and run history+Validated results and risk scores+Redacted evidence needed to prove a finding+Account and billing details
WE DON'T×Use customer data to train shared models×Store unredacted sensitive fields by default×Keep evidence longer than the finding needs×Sell or share customer data

Need raw captures to stay in your network? See the Private Runner →

SUBPROCESSORS

Third Parties That Process Customer Data

SUBPROCESSOR PURPOSE LOCATION
[Cloud hosting provider] Platform hosting and storage [Region]
[Email provider] Transactional email [Region]
[Support tool] Customer support tickets [Region]
[Monitoring provider] Application monitoring and logs [Region]

Customers are notified before a new subprocessor is added.

DOCUMENTS

Request Security Documents

Public documents open directly (links to be added). Select restricted ones and request access; some require an NDA.

↗Security overviewArchitecture, governance and controls summary Open ↗PUBLIC
↗Safety modelSafety levels, limits and stop conditions Open ↗PUBLIC
↗Subprocessor listCurrent list and notification process Open ↗PUBLIC
Audit reportIndependent attestation report NDA
Penetration test summaryLatest third-party test summary NDA
Completed security questionnaireStandard industry questionnaire NDA
Data processing agreementTemplate DPA NDA
SELECT DOCUMENTS Use your company email. Requests are reviewed by our security team.
RESPONSIBLE DISCLOSURE

Found a vulnerability in Hayrok?

Tell us privately and we'll work with you to fix it. We won't pursue good-faith research that follows our disclosure policy.

security@hayrok.com Disclosure policy and PGP key on request