Remediation Lifecycle
Nothing changes silently. Every step documented.
Remediation in Nuxari is a structured, approval-gated process. From finding to evidence package, every stage is logged and every action requires authorization.
The eight stages
Every remediation in Nuxari follows the same lifecycle. No stage can be skipped.
1
Finding
A drift finding documents the deviation: user, resource, observed value, approved baseline, severity, control reference, and a SHA-256 hashed snapshot.
2
Remediation Plan Created
An operator or the AI assistant creates a structured plan documenting the intended action, the affected resource and user, and the recommended change.
3
Approval Required
The plan is submitted to a designated approver. Approvers see the full context, finding, plan, and proposed action, before deciding.
4
Approval Decision
If approved, execution begins. If rejected, the plan is closed and the finding remains open. Both decisions are logged with full context.
5
Pre-Execution Snapshot
Before any change executes, Nuxari captures the current state from the connector. This snapshot is SHA-256 hashed and stored immutably.
6
Execution
The connector executes the approved action with start/end timestamps. Transient failures are retried safely. Permanent failures halt execution and create a failure finding.
7
Validation
After execution, Nuxari re-collects access state to confirm the change took effect and observed access now matches the approved baseline.
8
Evidence Package Created
A complete, signed, Merkle-chained evidence package is created covering finding, approval, snapshot, execution, and validation records.
What this means for your organization
Remediation without Nuxari often looks like: someone spots a problem, sends a Slack message, someone else makes a change, and maybe someone takes a screenshot for the audit file. With Nuxari, the finding is documented, the plan is approved, the state is snapshotted, the change is executed via the connector, and the evidence package is automatically created. The audit file is a byproduct, not a separate task.
What cannot happen
- Execution cannot begin without an approved approval record
- Snapshots cannot be modified after creation
- Evidence packages cannot be deleted within the retention window
- Approval records cannot be back-dated
- Findings cannot be silently closed without an audit trail
Plan statuses
| Status | Description |
|---|---|
| draft | Plan created, not yet submitted for approval |
| pending_approval | Submitted, waiting for approver action |
| approved | Approved, ready for execution |
| rejected | Rejected by approver, plan closed |
| executing | Action in progress |
| executed | Action completed, validation pending |
| validated | Validation confirmed, evidence package created |
| failed | Execution or validation failed |
| cancelled | Cancelled before execution |
Get startedBuild the operating layer
Build the operating layer
for governance work.
See how Nuxari Ops reduces manual IT work, eliminates access drift, and generates audit evidence automatically, across your entire enterprise.