Security & Operations

Admin & Operator Runbooks & SOPs

Standard Operating Procedures (SOPs), incident response runbooks, Tier 3 approval queue protocols, and emergency rollback procedures for VaultHost security staff.

SOP-101

Reviewing & Authorizing Tier 3 Destructive Actions

CRITICAL SEVERITY
Trigger Condition:

An ActionIntent with Risk Tier 3 is submitted by an AI Agent or Developer.

Execution Steps:
  1. Navigate to /admin/approval-queue.
  2. Review the AI Reasoning Trace: verify why the model recommended this destructive action.
  3. Inspect the Before and After State Diff: ensure no unintended tables, buckets, or DNS records are affected.
  4. Verify tenant boundary: ensure resourceUri matches the requesting tenant.
  5. Perform second-factor dual authorization by entering your staff security passcode.
  6. Click "Approve & Execute" or "Reject with Feedback" if alternative mitigation is advised.
SOP-102

Live Action Intent Emergency Rollback & Policy Overrides

HIGH SEVERITY
Trigger Condition:

An erroneous deployment or service reconfiguration occurred.

Execution Steps:
  1. Open /admin/actions to view the real-time execution ledger.
  2. Locate the relevant auditLogId or intentId.
  3. To roll back a worker or configuration, submit a reverse ActionIntent with verb "rollback".
  4. If an AI Agent is behaving aberrantly, enable "Strict AI Quarantine Mode" in /admin/actions to block all autonomous mutations.
SOP-103

Cryptographic Audit Trail Chain Verification

HIGH SEVERITY
Trigger Condition:

Periodic compliance audit (SOC 2, ISO 27001) or suspected log tampering.

Execution Steps:
  1. Run the cryptographic ledger integrity check CLI: vaulthost audit verify-chain --start-log=0.
  2. The tool recalculates HMAC-SHA256 and PQC signatures recursively through the hash chain.
  3. Any mismatch indicates unauthorized log manipulation and triggers an immediate P1 security incident.
SOP-104

PQC Key Rotation & Hardware Node Attestation

MEDIUM SEVERITY
Trigger Condition:

Quarterly cryptographic key rotation or new edge node commissioning.

Execution Steps:
  1. Generate new hybrid keypairs (X25519/ML-KEM-768 and Ed25519/ML-DSA-65).
  2. Verify hardware enclave measurement via AMD SEV-SNP / Intel SGX attestation quote.
  3. Issue updated NodeAttestationReceipt signed by master root key.
  4. Broadcast public keys across global anycast edge nodes.
1