Skip to content

OSCAL Export

The OSCAL export produces machine-readable files from your own system security documentation.

OSCAL, Open Security Controls Assessment Language, is a NIST file format (XML, JSON, or YAML) for security paperwork. The information inside an OSCAL file is the same information that has always lived in security documents: what your system is, which controls apply, how each is implemented, and what gaps remain. The difference is structure: instead of free-form pages a human has to read, an OSCAL file lays the facts out so a computer can read, validate, and compare them automatically.

Why it matters: assessors and agencies increasingly consume security documentation this way. The platform exports a System Security Plan (SSP) and a Plan of Action and Milestones (POA&M) in OSCAL JSON from the system details you maintain here. It does not generate other OSCAL document types. That saves retyping the same facts into another tool’s format, but it does not change who signs anything.

During the pilot the compliance tools are switched off for customer accounts. See how pass-through works.

  1. Maintain your system details and control implementations in the platform.
  2. Export the SSP or POA&M. The platform checks the document against the NIST OSCAL 1.1.2 schema first. A document that does not conform is refused, nothing is saved, and the response lists the fields to fix.
  3. Run the file through NIST’s own validation tools, then submit it yourself.

An OSCAL file is a record of your own documentation. Exporting it does not assess, approve, or authorize anything. See Shared Responsibility and the Glossary.

Try this in the platform