Remediation
Atomic transaction-safe remediation for security teams that cannot accept uncontrolled change execution.
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.
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)
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.
| Feature | This toolkit | OpenVAS | Nessus | Qualys |
|---|---|---|---|---|
| Atomic rollback | Yes | No | No | No |
| Auto-backup before change | Yes | No | No | Limited |
| Transaction timeout | Yes | No | No | No |
| Self-hosted deployment | Yes | Yes | No | No |
| Air-gap capable | Yes | Limited | No | No |
| Script-level audit trail | Yes | No | No | No |