Skip to content
Capabilities

Three-mode remediation

Choose the execution path that fits your change process. Mode A gives you manual guidance. Mode B gives you a script to inspect and run. Mode C executes a supported action with your temporary delegated authorization.

The three modes

Start with the finding, its target and its evidence. Then choose from the modes that the finding supports. The three modes describe how a change is delivered; they do not promise three interchangeable executors for every recommendation.

Mode A

Manual playbook

Follow the generated walkthrough in your own tools. The guidance identifies the target and the proposed change. You execute the steps through your normal administrative session and change-control process.

Mode B

Downloadable script

Inspect the generated PowerShell or Azure CLI commands before downloading. Run the script in your own session, using your own credentials. Store the artifact with your change record and use its recorded SHA-256 hash to check integrity.

Mode C

Delegated in-product action

Confirm the selected action and authorize a Microsoft OAuth session. Permafrost uses the delegated token to execute that action in your connected tenant. Your Microsoft permissions determine whether the write is authorized.

A script can include manual preparation or verification steps. An in-product action performs the specific operation described by its consent flow. Read that scope before choosing an execution mode. A SHA-256 hash checks an artifact’s contents; it is not a digital signature or a publisher identity certificate.

Zero standing write access

Collection and analysis use read-only access. Modes A and B leave execution in your environment. Mode C uses a separate delegated session that you authorize for a supported action.

The Mode C token travels through your browser in a sealed session that only the server can open. The credential is not persisted by Permafrost. Permafrost accepts the sealed session once within ten minutes, or until the Microsoft token expires if sooner. The Microsoft token inside keeps its own lifetime at Microsoft, typically 60 to 90 minutes, but Permafrost will not accept it again. The session is recorded as consumed before the executor uses it. The database stores only a replay receipt, never the token or sealed session.

Expired sessions are rejected. Expired replay receipts are pruned on later session consumption. A new action requires a new consent session.

The executor checks your customer, tenant and authorization. Support impersonation sessions cannot execute remediation. An analyst’s delegated token does not grant rights beyond that analyst’s Microsoft permissions.

Read authentication is separate. Workload identity federation stores no customer credential. If you choose a customer app registration with a client secret, that secret is stored in Vault. The default multi-tenant connection uses Permafrost’s application credential.

Guarded auto-remediation

The guarded-remediation settings save preferences for selected finding-and-action pairs. They do not execute actions automatically. Remediation remains analyst-initiated, with the same delegated authorization and target checks as other Mode C actions.

You can enable or disable each eligible pair for your customer. When a supported execution matches a saved preference, the match is recorded in the audit metadata. Saving a preference does not create a session, grant consent or schedule a background write.

The preference catalog covers these combinations:

  • Over-privileged identity: removal of a directory role assignment.
  • Dormant identity with access: removal of a directory role assignment.
  • Application role granted to a guest: removal of the app-role grant.
  • Service-principal credential review: removal of a selected credential.

The preference catalog is separate from the finding-button map. An eligible preference does not add a Mode C button to a finding. Identity disablement, Conditional Access changes and PIM revocation are outside this preference catalog.

Why three modes and not one

Different change processes need different artifacts and execution controls. Choose the path that matches your approval process and the operation you need to perform.

  • Formal change management. Attach the Mode A walkthrough to a change ticket. Your administrator performs the steps in the portal or your own tooling, with the approval and validation steps your organization requires.
  • Scripted operations. Use Mode B when you need a command-by-command preview and a versioned artifact. Your team controls script execution and the credentials used. Keep the downloaded artifact and its hash with the change record.
  • Interactive response. Use Mode C for a supported action you want to execute from the product. Confirm the target, authorize the delegated session and inspect the execution result. The execution record identifies the action and outcome.

All three paths start from the same investigation. Check the assignment, collected evidence and operational purpose. For an access reduction, include the workload owner’s required operations in the change plan, including work outside the observation window.

Mode availability by tier

Your account access, the finding type and the action determine the available controls. The 30-day trial provides access to the Professional product. Paid or agreed account access continues according to your subscription or access grant.

A plan does not turn an unsupported operation into an in-product action. Mode B needs a script generator for that finding. Mode C needs an enabled and configured delegated flow, a resolvable target and a user authorized to act on it.

Open the finding to see its available artifacts and action controls. Use the pricing reference for account access terms and the coverage reference below for the supported operation families.

Per-action mode coverage

Manual guidance and script generation cover finding-specific workflows. The delegated executors support the operations below. Some belong to PIM, group membership or access-request workflows rather than to a finding button.

  • Remove an Entra directory role assignment. Removes the selected standing directory assignment. The finding must resolve to a matching assignment in your tenant.
  • Remove an Azure RBAC role assignment. Removes the selected assignment at its Azure resource scope. It does not create a replacement custom role.
  • Revoke an Entra PIM assignment. Ends the selected directory role schedule using your delegated authorization.
  • Revoke an Azure PIM assignment. Ends the selected Azure resource role schedule. Directory and Azure schedules use separate execution paths.
  • Disable a user. Sets the selected Entra user account to disabled. The account and its assignments remain available for investigation.
  • Disable a service principal. Sets the selected service principal to disabled. This also supports Entra agent identities represented by service principals.
  • Remove an application permission. Removes a selected app-role assignment from a service principal. It does not remove the application itself.
  • Revoke a delegated permission grant. Removes the selected OAuth2 permission grant from the connected directory.
  • Remove a service-principal credential. Removes a selected secret or certificate by its key identifier. It does not issue a replacement credential.
  • Require MFA through Conditional Access. Creates an admin MFA policy in report-only mode or updates a selected policy to require MFA. The consent flow treats this as an elevated action.
  • Convert a permanent Tier-0 role to PIM-eligible. Creates eligibility before removing the standing assignment. The dedicated wizard checks the target and applies last-administrator and break-glass safeguards.
  • Activate an eligible PIM role. Activates your eligible directory role for a bounded duration through the PIM workflow.
  • Tighten a PIM activation policy. Requires MFA and justification and caps activation duration through the PIM policy workflow.
  • Add or remove a group member. Changes the selected group membership. Adding a member to a role-assignable group uses an elevated authorization path because it grants directory privilege.
  • Grant an approved directory role. Uses the access-request workflow to create a time-bound directory role schedule under delegated authorization.
  • Grant an approved application role. Uses the access-request workflow to assign the approved application role to the requester’s principal.

Finding buttons currently map six finding types to Mode C: dormant and orphaned agent identities to service-principal disablement; enabled guest accounts to user disablement; dormant identities with access to directory-role removal; agents holding Azure Owner to Azure-role removal; and permanent Tier-0 roles to the PIM-eligibility wizard. Each requires an open finding and a resolvable identity and tenant. Disablement also requires an enabled target.

For right-sizing, inspect the proposed custom role and export its definition for your deployment process. Removing an assignment is a different operation from creating a narrower role or moving an assignment to a narrower scope.

Limits

The finding-button map is narrower than the delegated action catalog. A supported executor does not imply a button on every related finding. Microsoft 365 workload findings and ambiguous assignment targets use their available manual or scripted workflow.

Managed identities do not have a general disable action here. Credential removal does not rotate a secret or certificate. Generated guidance and scripts do not establish future workload requirements or automatically validate unobserved dependencies.

AWS and GCP are Coming soon. These remediation workflows apply to Microsoft connections. Saved guarded-remediation preferences do not provide automatic quarantine or an inline permissions firewall.