Security overview

Permafrost EPM: security at a glance

A one-page summary of how Permafrost handles your data and proves it: for a procurement reviewer who needs the essentials before a full security review. Every statement reflects our real posture.

Sub-processor register 2026.06.1 · Updated 27 June 2026

Architecture

Read-only authentication

Connect to Microsoft with read-only consent. Workload identity federation uses no stored customer credentials. An optional client-secret connection stores its secret in Vault. AWS and GCP are Coming soon.

Read-only by default

Microsoft collection and analysis use read-only access. Optional remediation requires a separate, explicitly authorized delegated session.

Session-only writes (Mode C)

You authorize a temporary delegated OAuth session for supported remediation actions. The sign-in token travels through your browser in a sealed session only the server can open. Permafrost accepts it once within ten minutes and stores no credential, only a replay receipt. Support sessions cannot execute remediation.

Tenant isolation as a hard wall

Your authenticated session determines the customer scope used to retrieve your data. Support access uses a separate, operator-authenticated session that is read-only, time-limited and recorded.

Data handling

What we read
Identity, role-assignment, and entitlement metadata from the clouds you connect: the inputs to a permission-posture score. We do not read your users' mail, files, or message content.
Encryption
TLS in transit everywhere. Database storage is encrypted at rest by our managed-database sub-processor; OAuth tokens are additionally encrypted at the application layer.
Retention & deletion
Data is retained only while your account is active. Cancellation opens a 30-day deletion window, with immediate removal on request. The per-category schedule is published in the Trust Center.
Error monitoring
First-party: application errors are captured in our own infrastructure with secrets and customer PII redacted at the point of capture. No third-party error-tracking provider receives error data.

Sub-processors

The third parties that process data on our behalf, each bound by a data-processing agreement. The canonical, versioned register lives at /trust/sub-processors.

Active sub-processors with purpose, processing region, and transfer basis
Sub-processorPurposeRegionTransfer basis
VercelApplication hosting and edge/serverless computeVercel functions in iad1 (Washington, D.C., United States); static assets and routing use Vercel's global edge networkSCCs + EU-US / UK-US Data Privacy Framework where certified
NeonManaged PostgreSQL database (data at rest)Neon-managed PostgreSQL, AWS us-east-1 (N. Virginia, United States)SCCs + DPF where certified
StripeBilling and payment processingUnited StatesSCCs + DPF where certified
ResendTransactional email delivery (welcome, alerts, billing)United StatesSCCs + DPF where certified
MicrosoftAuthentication (Entra ID sign-in) and the read-only Graph / ARM APIs you authorizePer your Microsoft tenant's configured regionYou control the tenant; Microsoft is your provider. Reads are authorized by your admin's read-only consent — by default under Permafrost's own multi-tenant app (no per-tenant secret held); Pro and above can opt into a dedicated app registration whose secret is held encrypted in our secrets vault
GoogleGoogle Analytics — traffic measurement on the public marketing site onlyUnited StatesSCCs + DPF where certified; consent-gated

Certification posture

Dates instead of silence. We state what we hold, what is underway, and what is inherited from the infrastructure provider: never a certification we do not hold as held.

Permafrost's own certifications

  • SOC 2 Type 2Permafrost's own audit of its security controls over an observation window. In progress.
    In progressExpected H2 2026
  • ISO 27001Information-security management certification for Permafrost. On the roadmap after SOC 2 Type 2.
    PlannedPlanned
  • ISO 42001AI-management-system certification covering Permafrost's analysis and AI governance. On the roadmap.
    PlannedPlanned

Inherited from the infrastructure provider

  • SOC 2Attested at the hosting layer by Permafrost's infrastructure provider. Covers the substrate, not Permafrost's own controls.
    InheritedCurrent
  • ISO 27001Inherited from the infrastructure provider's certified hosting platform.
    InheritedCurrent
  • ISO 27018Cloud-PII protection, inherited from the infrastructure provider's certified platform.
    InheritedCurrent

Need more detail?

For a pre-answered CAIQ-style questionnaire pack, see the Trust FAQ & questionnaire. The full Trust Center: sub-processors, data residency, retention, breach notification, and DPA: is at /trust.

For completed evidence under NDA, reach us through your account team or the contact form.