Dawnstar Labs Vardhold Docs

Hardening checklist

The settings that put Vardhold into a secure, auditable configuration, written in the style of a DISA STIG so an ISSO or assessor can use them as evidence.

2 min readUpdated October 2026Vardhold 0.1 (pre-release)

On this page
  1. Categories
  2. CAT I
  3. CAT II
  4. CAT III
  5. Quick self-check

This is Vardhold's own guide. It is not a DISA-published STIG and does not replace the Windows STIGs; apply those first. Pilot customers receive the full guide, with check and fix text for every item.

Categories#

CategoryMeaning
CAT IFailing it lets an AI agent act unchecked, or lets the record of what it did be lost or altered.
CAT IIFailing it weakens protection or the evidence trail.
CAT IIIFailing it reduces assurance or makes problems harder to notice.

CAT I#

IDRequirement
AG-001The policy runs in enforce or strict mode
AG-002Hooks and the MCP proxy fail closed
AG-003The Claude Code hook is registered machine-wide
AG-004Every MCP server is routed through the Vardhold proxy
AG-005AI agents run under standard user accounts, or UAC is set to Always notify
AG-006The audit log verifies with the audit key
AG-007The service runs as LocalSystem, starts automatically and restarts on failure

CAT II#

IDRequirement
AG-010Events are exported to the SIEM
AG-011Exports use TLS with certificate validation
AG-012The local log is checked against the SIEM's chain head
AG-013Local retention meets the organisation's requirement
AG-014The data folder is limited to SYSTEM and Administrators
AG-015Endpoint enforcement capabilities are available
AG-016Ask rules deny on timeout
AG-017The installer is verified as validly signed before deployment
AG-018Vardhold warnings and errors are forwarded from the Windows event log
AG-019The system drive is encrypted

CAT III#

IDRequirement
AG-020Every discovered agent has been reviewed
AG-021Automatic suspension on detected blocks is set deliberately
AG-022Redaction covers the organisation's secret formats
AG-023The SBOM of the deployed version is retained
AG-024A kill switch procedure is documented

Quick self-check#

From an elevated PowerShell prompt, the most important items take a minute:

PowerShell
$cli = "C:\Program Files\Vardhold\vardhold.exe"
& $cli status                                   # mode: enforce or strict (AG-001)
& $cli verify                                   # exit code 0 (AG-006)
Get-Service Vardhold | Select-Object Status, StartType   # Running, Automatic (AG-007)
(Get-Acl "$env:ProgramData\Vardhold").Access | Select-Object IdentityReference, FileSystemRights   # SYSTEM and Administrators only (AG-014)