Platform · IxAct

SSF & CAEP-based containment and governance

IxAct

SSF & CAEP-based containment and governance.

Containment becomes an action instead of a ticket: the grant ends in every connected system in seconds, with a record of each.

ixact in the ConteXengine console (softened)
What it does

Three things, every day.

Seventeen built-in actions, among them disable, revoke sessions, remove access, rotate credentials and convert to just-in-time, on every connected system that supports them.

Response actions run with the approvals you set, and every run is recorded.

Shared signals carry the outcome to your identity providers and applications, so containment doesn’t wait for a token to expire.

How it works

From signal to decision.

STEP 1
A finding, or a change in risk, triggers a response.
STEP 2
Actions run through real identity and cloud calls, step by step, each logged.
STEP 3
The outcome is transmitted as a shared signal; recovery is a governed human step.
Containment in seconds, across connected appsPlaybooks with approvals and runsScopes from one identity to the whole estate
Use cases it serves

See it decide.

Containment in secondsUse case 6
Every service account gets an ownerUse case 2
No agent exceeds its humanUse case 4
FAQ

Questions we get asked.

What are SSF and ?

Open standards for sharing security events between identity providers and applications. IxAct transmits the decision outcome through them.

Can actions run automatically?

Yes, where you pre-approve them; otherwise they wait for one or two approvers. Every run is recorded.

What systems can it act on?

Any connected system where an administrator has enabled write-back: identity providers, directories, vaults, ticketing and cloud.

How is recovery handled?

As a governed human step. Once a step-up is approved, the identity resumes, often with reduced scope.

Start read-only

Find out where IxAct applies in your estate.