Why use Compliance
Compliance runs standards-based hardening benchmarks against your Arc sensors on a repeatable basis, replacing one-off manual audits with continuous, auditable evidence of their security posture.
Confirming that an asset meets a security-hardening standard is traditionally a manual exercise. Someone works through a checklist against a benchmark by hand, on however many assets they can reach. The result is a snapshot that starts going stale the moment it is taken. Repeating that consistently, on a schedule, with a defensible record of every exception, is difficult to do by hand at any real scale.
What Compliance gives you
- Standards-based scanning, not ad hoc checklists. A benchmark is a file that follows the Security Content Automation Protocol (SCAP) standard and is written in Extensible Configuration Checklist Description Format (XCCDF) format, the same machine-readable format used by issuing bodies such as DISA for Security Technical Implementation Guide (STIG) benchmarks, so a scan checks the same rules the same way every time.
- Policies that repeat themselves. A policy groups benchmarks into a versioned, reusable unit, so scanning the same target again means running the same policy rather than rebuilding a checklist from scratch.
- An audit trail for exceptions, not silence. When a rule genuinely cannot be met, an override records a reason code and a mandatory justification, keeping a history of who changed the result and why, rather than letting the failure quietly disappear.
In Vantage
Vantage includes a centralized way to configure policies, schedule them, execute them, and track results over time.