JSON syntax
Strict JSON without comments or trailing commas.
Paste OSCAL JSON into this free browser tool, validate it with validators derived from the official NIST OSCAL 1.2.2 JSON Schemas, and jump directly to each reported issue.
Your OSCAL document never leaves your browser. Secani does not upload, store, or use its contents.
Validate manually with the button or press Cmd/Ctrl + Enter.
Paste or type OSCAL 1.2.2 JSON, then run validation.
This free validator checks whether JSON is syntactically correct, recognizes the OSCAL model and declared version, and validates the complete document with the corresponding Secani validator derived from the official NIST OSCAL 1.2.2 JSON Schema.
The profile validator adds a documented compatibility patch for combine.method, which the OSCAL profile model defines but the published NIST 1.2.2 release schema omits.
When the schema reports a problem, the tool shows its JSON Pointer and maps it back to the closest source value. Select an issue to move the editor directly to that location. To keep results responsive, each validation run displays at most the first 20 schema issues.
A valid result has a precise meaning: the document passes that Secani validator. For profiles, this can differ from the unmodified published NIST schema because of the combine.method compatibility patch. It is not a claim of complete semantic or Metaschema conformance.
Strict JSON without comments or trailing commas.
Detection of all eight OSCAL root models.
A clear result for supported OSCAL 1.2.2 documents.
Rules derived from official NIST schemas, plus the documented profile patch.
Paste or type OSCAL 1.2.2 JSON into the editor.
Select Validate OSCAL or press Cmd/Ctrl + Enter.
Select a result to jump to its location, edit the JSON, and validate again.
Required metadata, UUIDs, titles, or model-specific collections are absent.
A string, array, object, number, or boolean appears where the OSCAL schema expects another type.
UUIDs, timestamps, tokens, and other formatted values do not match the OSCAL schema.
The document contains a property that is not allowed at that location in OSCAL 1.2.2.
XML and YAML input, complete Metaschema constraints, UUID uniqueness, semantic reference integrity, profile resolution, and automatic document repair are not validated here.
The editor, JSON parser, and OSCAL schemas execute in browser JavaScript. Validate, Format, Load example, and Clear do not upload OSCAL content or call a Secani validation API.
Secani may measure an ordinary page view, but editor contents, validation results, JSON paths, and tool actions are not included.
The document is not written to local storage or placed in the page URL. Refreshing or closing the page clears it.
Yes. You can paste and validate OSCAL 1.2.2 JSON without an account or payment.
No. Parsing, formatting, and schema validation run locally in your browser. The editor contents and validation results are not sent to Secani.
This tool supports OSCAL 1.2.2 JSON using validators derived from the official NIST release schemas. The profile validator includes a documented compatibility patch for combine.method, which the OSCAL profile model defines but the published 1.2.2 release schema omits.
Not yet. This browser tool currently accepts JSON only.
No. A valid result means the document passes Secani’s OSCAL 1.2.2 JSON Schema validator, derived from the official NIST schemas with the documented profile combine.method compatibility patch. Full Metaschema constraints, semantic references, UUID uniqueness, and profile resolution are outside this first version.