Security

Security at Phase

Access to your secrets is controlled by encryption keys that only you hold. Phase is built on a rigorous cryptographic foundation: open source, end-to-end encrypted by default, and engineered for enterprise-grade security.

Trust & compliance

SOC 2 Type 2

Independently audited by Oneleet. Our controls are examined continuously. Audit reports are available in our trust center.

SOC 2 TYPE 2 · CONTINUOUSLY MONITORED

Penetration tested

Penetration tested by Oneleet, an independent security firm, across the platform, APIs and services, with remediation tracked to completion. Executive summaries are available through the trust center.

ONELEET · WITHIN THE LAST 12 MONTHS

OpenAI Daybreak

Phase is an OpenAI Daybreak partner.

Daybreak is OpenAI's cyber defense program. It gives verified defenders governed access to GPT Cyber models, with scope controls, monitoring and human review.

Phase Cloud

Security controls.

The controls in place across the platform and the organization, audited and continuously monitored. The live list is published in the trust center.

AWS eu-central-1 · Frankfurt · 3 AZs
Cloudflare
WAF · DDoS protection
Private VPC
Load balancer
ALB · Multi-AZ
ECS on EC2
Graviton · Nitro · Multi-AZ ASG
RDS PostgreSQL
  • Multi-AZ · PITR
  • KMS CMK at rest
ElastiCache Valkey
  • KMS CMK at rest
  • TLS in transit
AWS KMS
GuardDuty
AWS ACM
CloudWatch

Access Control and Authorization

  • Access granting process used
  • Access management policy established
  • Account inventory maintained
  • Dormant accounts disabled
  • Employee access regularly reviewed
  • MFA required for critical services
  • Password management policy enforced
  • Password management policy established

Infrastructure Security

  • Active discovery tools used
  • Administrator access restricted
  • Automated security scanning performed on infrastructure
  • Buckets not exposed publicly
  • Configuration management system established
  • Firewall restricts public access to infrastructure
  • Infrastructure changes logged
  • Infrastructure changes require review
  • Infrastructure deployed using an infrastructure-as-code tool
  • Production deployment access restricted
  • Unauthorized assets addressed and removed
  • Unique production database authentication enforced
  • VPN used
  • Web Application Firewall (WAF) used

Monitoring and Incident Response

  • Audit log management process maintained
  • Audit logs collected
  • Incident response policy established
  • Incident review process implemented
  • Infrastructure performance monitored
  • Log management used
  • Network infrastructure monitored

Disaster Recovery

  • Automated backups enabled
  • Business continuity and disaster recovery policy established
  • Data recovery process established
  • Disaster recovery plans tested
  • Recovery data isolated

Endpoint Security

  • Anti-malware deployed on end-user devices
  • Data encrypted on end-user devices
  • Firewall maintained on end-user devices
  • Mobile device management (MDM) used

Email Security

  • DMARC policy and verification used
  • Email account access restricted
  • Email settings block malicious content

Vulnerability Management

  • Automated software patch management performed
  • Penetration testing findings remediated
  • Penetration testing performed within the last 12 months
  • Vulnerabilities scanned
  • Vulnerability management policy established

Data Management and Protection

  • Data encrypted at rest
  • Data encrypted in-transit
  • Data inventory maintained
  • Data management and retention policy established

Organizational Security

  • Acceptable use policy established
  • Asset inventory maintained
  • Asset management policy established
  • Change management policy established
  • Changelog established and maintained
  • Code of conduct established
  • Company security commitments externally communicated
  • Data-flow diagrams maintained
  • External support resources available (i.e., documentation)
  • Offboarding process established
  • Onboarding process established
  • Password manager used
  • Performance evaluations conducted
  • Physical access restricted
  • Policies signed by relevant personnel
  • Reference checks performed for employees
  • Roles and responsibilities specified
  • Security awareness training conducted
  • Service description communicated
  • Software development lifecycle established
  • System changes externally communicated
  • System changes internally communicated

Risk Management

  • Risk assessments performed
  • Risk management policy established
  • Vendor inventory maintained
  • Vendor management program established
Cryptography

Crypto.

One standardized set of primitives across the platform: elliptic-curve cryptography on Curve25519, authenticated encryption, and memory-hard key derivation. All implemented using the open source libsodium library.

XCHACHA20-POLY1305 — 192-BIT NONCES · RFC 8439 /  CURVE25519 — PASSES ALL SAFECURVES CRITERIA /  ARGON2ID — PASSWORD HASHING COMPETITION WINNER /  AS USED IN TLS 1.3, SIGNAL, WIREGUARD, TOR
Architecture
E2EE by default

End-to-end encryption

Encrypted by default: keys, values and comments, with an independent key for every environment. In the default E2EE mode Phase servers store only ciphertext and cannot decrypt your secrets.

Your device — plaintext keys only herePhase server — ciphertext onlyArgon2idBlake2b KDFunwraps seed + saltXChaCha20 · X25519 session keyE2EE BOUNDARY — ONLY CIPHERTEXT CROSSESRECOVERY PHRASEBIP39 · 24 WORDS · 32-BYTE ENTROPYrobust secret anchor harvest canyon orbitsilver meadow copper timber drift lensfabric lumber breeze ridge harbor gardentoken trust shield crystal spice randomACCOUNT SEEDUSER KEYPAIRED25519 → X25519ENVIRONMENT KEYSSEED + SALT · RANDOM 32 BYTESX25519 KEYPAIR PER ENVIRONMENTSECRETSKEY · VALUE · COMMENT — EACH ENCRYPTEDWRAPPED ENV KEYSENCRYPTED TO YOUR PUBLIC KEYENCRYPTED SECRETSXCHACHA20-POLY1305 CIPHERTEXTBLAKE2B KEY DIGESTS, KEYED WITH ENV SALTENCRYPTED KEYRINGACCOUNT KEYS — ENCRYPTED WITH DEVICE KEYDEFAULT E2EE — SERVER CANNOT DECRYPT SECRETSOPT-IN SSE FOR THE REST API AND NATIVE SYNCS
Key derivation — on deviceEnvironment keys & secrets — on deviceServer storage — ciphertext onlyDataflow
Keys only you hold

Your account keys derive from a 24-word mnemonic phrase only you hold. Granting access wraps an environment’s keys to your account’s public key. The server stores wrapped keys and ciphertext it cannot open.

24-WORD MNEMONIC · ARGON2ID 1 GB · X25519 WRAPPING
Server-side mode, explicit

End-to-end encryption is the default. Server-side encryption is a per-app opt-in for when you need third-party syncs or the REST API. The environment key is then stored encrypted on the server.

E2EE BY DEFAULT · SSE OPT-IN PER APP
Zero-trust Lockbox

Share a secret with anyone via a single link: the Box Seed travels in the URL fragment, parsed only by the browser and never sent to the server. View limits and expiry built in.

BOX SEED IN THE URL FRAGMENT · KEY DISCARDED AFTER ENCRYPTION
FAQ

Frequently asked questions.

Contact

Questions or disclosures

For security questions, vendor reviews or vulnerability reports, contact our security team.

RFC 9116
Deployment
Get started

Keep your secrets

Self-host or start on fully managed Cloud in under a minute.

Self-hosted

Run Phase on your own infrastructure. Free and open source.

AI agent deployment skill
$ npx skills add phasehq/ai
Cloud

Fully managed. From signup to your first secret in 60 seconds.

Sign up with