OSCAL Profile Schema
datasets/oscal-profile-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-profile-schema- Licence
- https://www.apache.org/licenses/LICENSE-2.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
OSCAL Profile Schema
Section titled “OSCAL Profile Schema”src/oscal/schema/oscal_profile.yaml is the module titled “OSCAL Profile Model”, with the id https://w3id.org/lmodel/oscal/oscal_profile.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-profile-schema.json. It imports linkml:types and the catalog module. Its see_also names NIST’s page on the profile, https://pages.nist.gov/OSCAL/learn/concepts/layer/control/profile/.
The README describes the profile model as a selection of controls from catalogs, and how it alters them.2 Profile is “An OSCAL Profile that designates a set of controls from one or more catalogs or profiles, optionally restructures and modifies them, to describe a basis for a security standard or body of practice”. It requires uuid, metadata and imports, and also holds merge, modify and back-matter. ProfileDocument wraps one profile as the root of a profile document.
The module’s one subset, profile, holds the root document and its profile-specific containers: ProfileImport, the merge classes ProfileMerge, CombinationRule, MergeFlat and MergeCustom, and the modification classes ProfileModify, ParameterSetting, Alteration, Removal and Addition, among others.