Remediation

Controlled remediation. Automatic rollback. Full audit trail.

Atomic transaction-safe remediation for security teams that cannot accept uncontrolled change execution.

The problem with most remediation tools

Most audit platforms identify what is wrong and stop there. When they do offer remediation, it is script execution without safety nets, no backup, no rollback, and no confirmation that the change worked. A failed fix applied to a production server at 2am is a worse outcome than the original finding.

How atomic remediation works

1. START TRANSACTION
   Create rollback point with configurable timeout (default: 5 min)

2. BACKUP
   Original files backed up with SHA256 checksums in manifest.json

3. APPLY
   Configuration changes applied. Services restarted if required.

4. VALIDATE
   Success -> COMMIT (backups retained for manual rollback)
   Failure -> AUTO-ROLLBACK (original files restored automatically)
    

Dead man's switch

Every remediation transaction has a timeout. If post-execution confirmation is not received within the configured window, the transaction automatically rolls back. Weekend emergencies from bad patches are prevented by design, not by process.

Access controls

Operator workflow

  1. Verify host connectivity (SSH or WinRM test built into platform)
  2. Unlock remediation with secondary auth token
  3. Select fix from eligible fix catalogue
  4. Run dry-run preview and review expected changes
  5. Execute against selected host or canary group
  6. Review execution history
  7. Apply rollback if outcome is not compliant

API surface

What this toolkit has that most alternatives do not

FeatureThis toolkitOpenVASNessusQualys
Atomic rollbackYesNoNoNo
Auto-backup before changeYesNoNoLimited
Transaction timeoutYesNoNoNo
Self-hosted deploymentYesYesNoNo
Air-gap capableYesLimitedNoNo
Script-level audit trailYesNoNoNo