Skip to content
CIEM · Cloud Infrastructure Entitlement Management

Run Permafrost in your own environment.

Identity attack surface management for Microsoft, AWS and GCP clouds. Your identity data, findings, reports and cloud credentials stay in your environment. Microsoft collection is available first. AWS and GCP collection is coming.

Built for security engineers and cloud architects running Microsoft 365, Entra ID and Azure.

Microsoft Entra ID, Azure and Microsoft 365 · Live today · AWS and GCP: Coming soon

Docker Compose or Kubernetes · Your environment

How scoring works

Read-only OAuth · No stored credentials with workload identity federation · Zero standing write access

Choose how to run it

The same identity analysis, with different responsibilities for data and access.

Self-hosted

  • Run in your environment with Docker Compose or one Helm chart.
  • Identity data, findings, reports and cloud credentials stay with you.
  • Your own app registration. No third-party app with standing directory access.
  • At activation and every six hours on schedule, the install sends its licence key, install ID and app version. Scheduled checks also send human and non-human identity counts. The licensing service sees the source IP and stores a salted hash for abuse control when IP hashing is configured.
  • You own backups, upgrades and the database.
Run it yourself

Hosted

  • Permafrost runs the application and database.
  • Your identity data, findings and reports are stored in our hosting region.
  • Our systems can read your directory whenever your grant is active.
  • Three sign-in methods have different credential risks.
  • You rely on our hosting and database providers.
Review hosted access and risk
The business case: Before and after

Less standing access. Smaller blast radius.

Find the assignments behind your exposure. Compare granted access with observed activity, inspect the configuration and choose the next change from the finding.

Before: Fragmented access data

  • Permissions granted at project start and never revisited.
  • Access reviews require reconciling assignments and activity.
  • Human and non-human access sits in separate inventories.
  • An auditor's request to prove least privilege lands as a fire drill.

After: Access and evidence together

  • Principal scores combine posture, activity signals and open findings.
  • Assignments and observed activity are available together.
  • Non-human identities ranked alongside users, classified by origin.
  • Findings and remediation records are ready to export.
New class: Agent identities

Put agent identities in your access inventory.

See your collected Entra agent identities alongside users, service principals and managed identities. Inspect their origin, assigned access and risk score. Open an agent blueprint to see the resources and actions within reach.

Where we fit: Your existing stack

Built to sit alongside your Microsoft security stack.

Add principal risk scores and permission-gap analysis to your Microsoft security stack. Connect findings to the governance and privileged access controls you already use.

Trust: Verifiable, not asserted

Find the authentication model, data-processing agreement and sub-processor list in the Trust Center.

Under the hood: How it works

From inventory to action.

Explore the inventory, inspect a principal’s score and open the findings behind it. Choose a remediation path for the access you want to change.

See it: In the product

The gap, on one screen.

Coverage by identity class, the per-principal risk waterfall, and standing access for an agent identity. The same surfaces a connected tenant lands on.

Watch the product tour

Explore the product workflow.

The product tour is coming soon. Try the live demo to explore principal scores, finding evidence and remediation options.

Product demo

A short product walkthrough is in production.

Until it lands, take the same surfaces for a spin in the live demo — read-only, synthetic data, no sign-in.

Try the live demo
CORE 01: The gap

One score. The factors behind it.

Unified Principal Risk (UPR) is a composite score from 0 to 100. It combines collected posture and activity signals with open findings so you can prioritize the identities that need action.

  • Window90-day Azure control-plane analysis window.
  • EvidenceCollected activity logs and configuration, attached to findings.
  • ScopeUPR combines privilege, permission creep, scope, dormancy, sensitive permissions, PIM, Conditional Access, account state, risk signals, and open findings.
  • TenantTenant UPR weights principal scores by blast radius, excludes groups and adds a capped contribution from open tenant findings.
38.2Tenant UPR · lower is better

Sample data

CORE 03: Evidence

Severity you can defend.

Activity-based findings cite collected Azure activity-log evidence; configuration findings cite the collected configuration.

  • DrillOpen a finding to inspect the principal, assignment and evidence.
  • ProofAssignment scope, principal context and the supporting evidence.
CORE 04: Remediate

Your change. Your execution path.

Choose from the modes supported by your finding: follow a playbook, run a script or authorize an in-product action. You control the change and the credentials used to make it.

Mode 01: Manual

Guided steps

A precise, scoped runbook for the change: the exact role assignment, the exact scope, the portal path. You stay on the keyboard the whole time.

You execute the reviewed steps

Mode 02: Script with preview

Download, review, run

Inspect every command before download. Compare the generated script with your change plan, then run it from your own shell under your own account.

SHA-256 artifact hash · you execute

Mode 03: Session-only OAuth

Apply in one session

Authorize a supported action with a delegated OAuth session. Your sign-in travels in a sealed session only the server can open. Permafrost accepts it once within ten minutes and stores no credential.

Sealed session · single use · ten-minute window

Isolation

Per-customer isolation. Your inventory, findings and exports stay within your customer boundary.

Scope

CIEM for Microsoft Cloud. Compare entitlements with observed activity and inspect the configuration behind each finding.

Cadence

Scheduled syncs refresh your connected tenant’s inventory, activity and findings.

Run Permafrost in your environment

Take a core sample.

Keep identity data and cloud credentials in your environment.

Demo is read-only · synthetic data · no sign-in

A DuneCodeForge product.