The oscal serializer MUST also write a system-security-plan (each control the checks speak of, implemented where every result shows it and partial where one does not, by the checks that show it; and what the caller says of the system, by the option system: its description, sensitivity level, boundary, import profile, information types, components, users and whose each control is, provider, inherited or customer, none of which is made up where it is not said) and a plan-of-action-and-milestones (the findings that are open and the risks that are not closed, each with its milestones and the exception or accepted risk that holds it until a date) from the same assessment, and all three documents MUST be valid against the schema NIST publishes for OSCAL; a serializer MAY be given a mapping through a crosswalk (0002 FR-002) so that a control of one framework is written under another's identifier.
Enforced (check): .github: cd commons/grc && bun run verify — suite/documents.test.ts
Proved by: grc/suite/documents.test.ts
Written in: grc/src/serializers/oscal/mod.ts
Tests: passed: suite/documents.test.ts oscal writes a system security plan of what is implemented and a plan of action of what is; passed: suite/documents.test.ts the system security plan says what the caller says of the system and invents nothing else:; skipped: suite/documents.test.ts the three OSCAL documents are valid against NIST's published schema, where the schema (OSC
Cited by: GRC, serializers/oscal/mod