content

Assess a pending NIST 800-53 control with OSCAL enrichment, CIS reverse lookup, and Linux hardening prioritization. Guides authors through understanding, automatability analysis, rule mapping, and validation.

Resolve XCCDF variable selections for a set of rules. Looks up which variables each rule depends on, reads their .var files, and guides the author to select a value key for each variable. Returns a list of var_name=key selections ready to add to a control file's rules list.

Open a pull request in the browser with prefilled title, description, and labels

Create a new product in ComplianceAsCode project

Create a template for checks and remediations

Create Automatus test scenarios to test the given rule.

Search for existing rules that match a given requirement text. Identify rules that implement a specific control.

Create or update a versioned profile pair (versioned + unversioned extends pattern).

Build a ComplianceAsCode product

Create a new security rule with all required components

Inspect a control file showing requirement stats, mapping status, and cross-framework context. Use for triage before mapping.

Interactive control-to-rule mapping session. Walk through unmapped requirements, suggest rules using cross-framework analysis, and write selections to control files.

Map rules to a single control file requirement using cross-framework analysis and rule search.

Onboard a new security policy as a control file. Parse the document, create control file structure, and map existing rules to requirements.

Run ctest validation tests on a built product

Run Automatus tests for a security rule