OSCAL System Security Plan Schema
datasets/oscal-ssp-schemaNobody has checked this yet
Written 2026-10-29 by ktl-librarian (automation).
The full record
- Checks
- none recorded
- Sources
- Is part of
- References
- Depends on
- Derived from
- Pointed to by
- OSCAL Schema (top-level) (has part)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/lmodel/oscal/knowledge/datasets/oscal-ssp-schema- Licence
- https://www.apache.org/licenses/LICENSE-2.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
OSCAL System Security Plan Schema
Section titled “OSCAL System Security Plan Schema”src/oscal/schema/oscal_ssp.yaml is the module titled “OSCAL System Security Plan (SSP) Model”, with the id https://w3id.org/lmodel/oscal/oscal_ssp.1 Its version is 1.2.3, its license Apache-2.0, and its source is NIST’s JSON schema of the model, http://csrc.nist.gov/ns/oscal/1.2.3/oscal-ssp-schema.json. It imports linkml:types, the catalog module and the assessment plan module. Its see_also names NIST’s page on the system security plan, https://pages.nist.gov/OSCAL/learn/concepts/layer/implementation/ssp/.
The README describes the model as a system’s characteristics, its implementation and how it implements a profile’s controls.2 SystemSecurityPlan is “A system security plan, such as those described in NIST SP 800-18”. It requires uuid, metadata, import-profile, system-characteristics, system-implementation and control-implementation, and also holds back-matter. SspDocument wraps one plan as the root of a system security plan document.
SystemCharacteristics requires system-ids, system-name, description, system-information, system-status and authorization-boundary. CHANGELOG.md says that it now takes props and links, as OSCAL defines them.3 The module’s one subset, ssp, holds the root document and its SSP-specific containers, such as SystemInformation, SystemImplementation, LeveragedAuthorization, SspControlImplementation and ByComponent.