Skip to content
oscal

Datasets

  • CNCF AI Ecosystem OSCAL Benchmarks nobody has checked this yet
    31 OSCAL component definitions from oscal-compass-lab/ai-benchmarks, one for each of 31 CNCF AI ecosystem projects (PyTorch, TensorFlow, LangChain, Kubernetes and others), in tests/data/cncf-ai-benchmarks/ under Apache-2.0, with fault-injected copies in tests/data/invalid/cncf-ai-benchmarks/ whose last-modified offset is +0000; tests/test_data.py and just test validate both as ComponentDefinitionDocument after rewriting their keys with underscores.

  • Generated artefacts nobody has checked this yet, still a draft
    Files generated from the OSCAL schema and never edited by hand: project/ (what just gen-project writes, such as JSON Schema, JSON-LD, OWL, SHACL, ShEx, SQL, GraphQL, protobuf, Excel and TypeScript, and the further formats of just gen-project-extended), the dataclass and Pydantic models in src/oscal/datamodel/, docs/schema/oscal.yaml, the gen-doc pages in docs/elements/ and the domain schema copy .lokf/oscal.yaml.

  • NIST 800-53 Rev 5 to AWS Service Mapping (Luigi Carpio) nobody has checked this yet
    A third-party OSCAL 1.1.2 component definition by Luigi Carpio, tests/data/luigi_carpio/component-definition.json under MIT, mapping 31 NIST 800-53 Rev 5 controls to AWS services, each with a fedramp-high property, and marking with cjis-delta where CJIS v6.0 exceeds FedRAMP High (AC-2, IA-2, AU-6, SC-28, IR-6); the test-luigi-carpio recipe, which just test runs, checks it.

  • OSCAL Assessment Plan Schema nobody has checked this yet
    The assessment plan module of the OSCAL schema, src/oscal/schema/oscal_assessment_plan.yaml (id https://w3id.org/lmodel/oscal/oscal_assessment_plan, OSCAL 1.2.3): the AssessmentPlan model of what an assessment covers, and the assessment-common and implementation-common classes (subjects, tasks, observations, findings, risks, system components) that the component, SSP, assessment results and POA&M modules import.

  • OSCAL Assessment Results Schema nobody has checked this yet
    The assessment results module of the OSCAL schema, src/oscal/schema/oscal_assessment_results.yaml (id https://w3id.org/lmodel/oscal/oscal_assessment_results, OSCAL 1.2.3): the AssessmentResults model of what an assessment observed and found, with its results, attestations and assessment log, and AssessmentResultsDocument as its document root; it imports the catalog and assessment plan modules.

  • OSCAL Catalog Schema nobody has checked this yet
    The catalog module of the OSCAL schema, src/oscal/schema/oscal_catalog.yaml (id https://w3id.org/lmodel/oscal/oscal_catalog, OSCAL 1.2.3): the Catalog model of controls, groups, parameters and parts, the metadata, back matter, shared types and mixins every other module imports, and OscalDocument, the schema’s tree root.

  • OSCAL Component Definition Schema nobody has checked this yet
    The component definition module of the OSCAL schema, src/oscal/schema/oscal_component.yaml (id https://w3id.org/lmodel/oscal/oscal_component, OSCAL 1.2.3): the ComponentDefinition model of components, their capabilities and the controls each implements, with ComponentDefinitionDocument as its document root, against which the CNCF and Luigi Carpio fixtures are validated; it imports the catalog and assessment plan modules.

  • OSCAL Mapping Collection Schema nobody has checked this yet
    The mapping collection module of the OSCAL schema, src/oscal/schema/oscal_mapping.yaml (id https://w3id.org/lmodel/oscal/oscal_mapping, OSCAL 1.2.3): the MappingCollection model of how the controls of one catalog or profile relate to another’s, with its provenance, maps, qualifiers, gap summaries, confidence scores and coverage, and MappingCollectionDocument as its document root; it imports the catalog module.

  • OSCAL metaschema copy nobody has checked this yet, still a draft
    OSCAL’s metaschema sources from the v1.2.3 release (usnistgov/OSCAL src/metaschema at commit e061961), copied byte for byte with NIST’s LICENSE.md into src/oscal/schema/metaschema/: never edited here, the source of the allowed values every enum renders, which tests/test_schema_rules.py checks, and compared weekly with upstream by scripts/check_upstream_release.py.

  • OSCAL POA&M Schema nobody has checked this yet
    The plan of action and milestones module of the OSCAL schema, src/oscal/schema/oscal_poam.yaml (id https://w3id.org/lmodel/oscal/oscal_poam, OSCAL 1.2.3): the PlanOfActionAndMilestones model of the risks a system still carries and how they are tracked, through its POA&M items, with PoamDocument as its document root; it imports the catalog and assessment plan modules.

  • OSCAL Profile Schema nobody has checked this yet
    The profile module of the OSCAL schema, src/oscal/schema/oscal_profile.yaml (id https://w3id.org/lmodel/oscal/oscal_profile, OSCAL 1.2.3): the Profile model, a selection of controls from catalogs or profiles and how it merges and modifies them, with ProfileDocument as its document root; it imports the catalog module.

  • OSCAL Schema (top-level) nobody has checked this yet
    The umbrella LinkML schema of OSCAL 1.2.3, src/oscal/schema/oscal.yaml (schema id https://w3id.org/lmodel/oscal, prefix oscal:): it imports the eight model modules, pins OSCAL’s tag v1.2.3 and commit e061961 in its annotations, and its lokf adapt copy .lokf/oscal.yaml, rooted on the eight models, is this bundle’s domain schema.

  • OSCAL System Security Plan Schema nobody has checked this yet
    The system security plan module of the OSCAL schema, src/oscal/schema/oscal_ssp.yaml (id https://w3id.org/lmodel/oscal/oscal_ssp, OSCAL 1.2.3): the SystemSecurityPlan model of a system’s characteristics, its implementation and how it implements a profile’s controls, with SspDocument as its document root; it imports the catalog and assessment plan modules.

  • Test data and schema tests nobody has checked this yet, still a draft
    Example instances of the OSCAL schema in tests/data/: 36 valid files and 26 counter-examples, each named after the class it instantiates (Catalog-001.yaml, Profile-missing-imports.yaml), with an example and a counter-example for every model, the problem/ fixtures and two third-party OSCAL sets; tests/test_data.py and just test hold them to the dataclasses, the generated JSON Schema and linkml-validate, and tests/test_schema_rules.py holds the schema to the metaschema copy and the adapt copy’s names apart from LOKF’s, slsa’s and github-actions’.