onboard-control

To convert a security policy PDF into structured compliance controls, you provide the document path to onboard-control. It parses the PDF and automatically generates a ready-to-use ComplianceAsCode control file structure for auditing.

You can map existing security rules to new policy requirements automatically using onboard-control. It parses your policy document and aligns existing rules across products to the generated control structure.

Supported file formats for parsing security policy documents include PDF, Markdown, HTML, and plain text. onboard-control validates these inputs and infers or confirms the target product before generating control files.

To generate a ComplianceAsCode control file structure from a markdown policy, provide the markdown file path to onboard-control. The tool parses the text, validates the input, and outputs a ready-to-map control file set.

onboard-control does work with policy sources that are not MCP-enabled. It includes fallback behavior to parse local documents and still generate the required control file structure for compliance mapping.

The best way to onboard security policies across different products is to use onboard-control for product scoping and versioning. It parses the policy source and supports mapping existing rules to requirements across your specified products.