diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/BUILD-LOG.md b/docs/analysis/2026-08-automating-technical-hardening-guidance/BUILD-LOG.md
index 6d3bd91..33ab04d 100644
--- a/docs/analysis/2026-08-automating-technical-hardening-guidance/BUILD-LOG.md
+++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/BUILD-LOG.md
@@ -8443,3 +8443,119 @@ report Metaschema constraint findings the JSON schema does not express:
step, and prop names outside the allowed set. These are the publisher's
modelling choices, they do not affect the verifier's checks, and they are left
as they are.
+
+## Session: the IBM pairs arrive as single files
+
+### Two combined component definitions added
+
+**Date:** 2026-10-09
+**Scope:** examples/component-first, the example index and lock, the OSCAL
+inventory, one pinned test
+**Result:** `--all --offline` 2701/2701; unit tests 68/68.
+
+**What was added.** Vikas Agarwal supplied two files on issue 16, each holding a
+service component and the validation component that checks it:
+`idservice-oscap-validation-cd.json` (IDSERVICE with OSCAP) and
+`cos-ansible-validation-cd.json` (COS with Ansible). Every component in them is
+identical to its counterpart in the four separate files. The separate files stay,
+because snippets and verifier checks resolve against them; the pairs are an
+easier way into the same content, not a replacement.
+
+**What was changed in them.** Only the document `uuid` and `last-modified`. All
+four separate files share the document UUID `bbdf7ee6-…`, and the combined files
+arrived with it too, so each combined file now has its own:
+`5387e03f-f015-4c6c-a2b8-384f2319c087` for IDSERVICE with OSCAP and
+`51f93843-4b96-4794-a590-1cbc6bad9b73` for COS with Ansible. Nothing inside the
+components was touched. The UUID shared by the four separate files, and the
+control-implementation and implemented-requirement UUIDs shared by the COS and
+IDSERVICE components, are left as published.
+
+**Raised, not changed.** The three OSCAP checks give
+`target-component-uuid` `0c410eb1-…-c80126a984f9`, which names no component. The
+IDSERVICE component is `…984e9`, and the IBM assessment plan uses `…984e9`. The
+same value is in the separate `oscap-validation-component-definition.json`. It
+was put back to the author on issue 16 rather than corrected here.
+
+**What moved with them.** The IBM set is 8 files, so `tools/source-lock.json` and
+the pin in `test_source_inputs.py` say 8, and the index was rebaselined.
+`oscal-artifacts.json` lists 6 component definitions for component-first, up
+from 4, since it counts files. `ibm_cdef_files` in the corpus figures stays at 4:
+its glob is `*component-definition.json`, which the combined `-cd.json` names do
+not match, so the same components are not counted twice.
+
+## Session: issue 16, the review closed out
+
+### What the issue asked for that had not reached the site
+
+**Date:** 2026-10-09
+**Scope:** data/questions.json, data/stakeholders.json, data/six-questions.json,
+component-first.html, two stakeholder checks and the stable question ids
+**Result:** `--all --offline` 2708/2708; unit tests 68/68; approach pages within
+budget at a 9.5 per cent spread.
+
+The review on issue 16 was read end to end against the published pages. Most of
+the accepted edits were already in. What follows is what was not.
+
+**Two accepted moves had become deletions.** The reply on the issue accepted
+moving the observation-to-asset question and the desired-state question to the
+shared section. Both were deleted instead. Both are back, in the shared section,
+under their old ids (`proposal-4`, `paper-comp-2`), and the ids are now held by
+the stable-id check. The observation question is reframed as the issue asked:
+it concerns the current assessment-results model, an observation can name its
+producer through origin actors but not the check it ran, and the component-first
+examples propose the asset UUID and check identifier on each observation.
+
+**The component-first party table now reads as the approach describes itself.**
+The opening post rewrote five rows. Fitted to the table's two-sentence notes and
+to the page budget:
+
+- The mapping provider publishes framework-to-framework mappings, a mapping
+ collection of its own, and does not tie controls to product rules.
+- The technology provider's rules carry the framework tie and the evidence type
+ that proves each rule.
+- The policy engine provider's checks carry no framework tie.
+- The system owner also selects the validation components the plan uses.
+- The auditor's run makes observations and findings; observations roll up to
+ control-level findings through check, rule and control.
+
+This retires the "software or validation" marker on the mapping provider's row,
+which had stood for the open question of which component definition carries the
+tie. The approach's answer is the rule component. Two stakeholder checks move
+with it: a mapping collection may now be the mapping provider's on two
+approaches, and on both it is its own document. The marker's own rule is kept,
+unused, for any approach that leaves the question open again.
+
+**`which-cdef-maps` keeps its id and asks what is still open.** With the tie
+settled on the rule component, the question is how a framework the technology
+provider did not map reaches the same rules: an SSP override, or a mapping
+collection between frameworks, and which keeps rule-level precision.
+
+**The copy-and-tailor convention is cited, and the questions stay open.** The
+answers on the issue to `paper-comp-1`, `-3`, `-4` and `-5` describe one
+convention: with no way to import a component definition, the SSP author copies
+it, merges overlapping components, keeps the rules that serve the profile and
+sets parameter values, with no link back to the source; rules reach the plan and
+results through the SSP. Each question now states that convention and what it
+leaves open.
+
+**Question 4 is answered for component-first.** In the SSP every subject is a
+component, the whole environment defaulting to This System, so the by-component
+response names what the rule runs against. The cell moves from partial to
+filled; its model and assemblies are unchanged.
+
+**The runner convention is stated.** Question 5's cell and the shared
+`proposal-3` question now say that each plan activity names its runner through
+the proposed `assessment-asset-uuid` and its checks through `check-ids`, which
+the committed assessment plan and results already show.
+
+**The editorial standard is printed.** The questions page intro says a question
+sits under the approach where it is most acute, not exclusively, and a question
+every approach shares sits in the shared section.
+
+**Not done, and why.** Questions 6a and 6b stay where they are: the issue says
+findings were added to the assessment results example and an SSP example was
+written, but neither file was attached, and the matrix is verified against the
+committed examples. The "late, external" binding on question 2 stays unavailable
+for component-first: it describes a separate mapping artifact reaching a rule,
+which the schema does not allow, and an SSP override is the implementor's
+response rather than that.
diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/bundle.js b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/bundle.js
index b8390f3..230779d 100644
--- a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/bundle.js
+++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/bundle.js
@@ -10,6 +10,6 @@
* mirror is a build failure rather than a page that quietly shows old content.
*
* Regenerate: python tools/bundle.py
- * Files: 71. Generated from data/ at 2026-09-10T14:55:11+00:00.
+ * Files: 71. Generated from data/ at 2026-10-09T19:22:57+00:00.
*/
-window.TFGBundle = {"analysis.json":{"approaches":[{"id":"a","name":"Catalog-first","path":"catalog-first.html"},{"id":"b","name":"Component-first","path":"component-first.html"},{"id":"c","name":"Assessment-first","path":"assessment-first.html"}],"concluded":null,"corpora":{"note":"Repository-defined inputs: 6 committed IBM and 18 committed Easy Dynamics JSON files, checked against data/examples.json fingerprints, plus 231 public AWS JSON files from the pinned archive and verified cache declared in the lock. Prepare explicitly with python tools/source_inputs.py --fetch; python tools/source_inputs.py --check verifies inputs offline. Missing or corrupt inputs fail rather than being skipped or counted as empty.","source_lock":"tools/source-lock.json"},"forum":"OSCAL Foundation Technical Focus Group on Automated Assessments","id":"2026-08-automating-technical-hardening-guidance","makesRecommendation":false,"makesRecommendationNote":"By design, not because the effort is unfinished. The site states three approaches in the terms their proponents use, prices what each one costs, and stops. A reader looking for a verdict should not infer that one is pending.","openItems":["Proponent review has not happened. No request for corrections has been sent to the publishers of the three bodies of content, so none has been received and nobody has declined."],"opened":"2026-08-12","question":"Where does technical hardening guidance live in OSCAL, and how does an automated check attach to it?","recommendation":null,"status":"active","summary":"Three organizations have published working OSCAL content that answers the same question three different ways. This site puts the three side by side against the same six questions, writes the same two rules out in all three shapes so that the only thing differing between the columns is the modelling, and names the join key that makes each one work.","supersededBy":null,"supersedes":null,"title":"Automating Technical Hardening Guidance with OSCAL","verification":{"command":"python tools/verify.py --all","note":"Every figure and extract on the site is recomputed from a published file. A skipped check is reported separately and never counted as a pass.","workflow":".github/workflows/verify-2026-08-hardening-guidance.yml"}},"assets/diagrams/710-scenario-assessment.svg":"\n","assets/diagrams/710-scenario-catalog.svg":"\n","assets/diagrams/710-scenario-component.svg":"\n","assets/diagrams/73-join-assessment.svg":"\n","assets/diagrams/73-join-catalog.svg":"\n","assets/diagrams/73-join-component.svg":"\n","assets/diagrams/75-stakeholders.svg":"\n","assets/diagrams/76-satisfaction-6a-6b.svg":"\n","data/corpus-stats.json":{"generated_from":"repository-defined inputs in tools/source-lock.json","note":"Every figure the site cites, with the derivation that tools/verify.py --stats recomputes from the source corpora. A mismatch is a hard failure.","stats":[{"derivation":"len(catalog.groups) in AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","key":"aws_groups","label":"groups in the AWS Security Hub catalog","value":77},{"derivation":"sum(len(g.controls) for g in catalog.groups) in aws_security-hub.oscal.json","key":"aws_controls","label":"controls in the AWS Security Hub catalog","value":452},{"derivation":"count of AWS/oscal-content-for-aws-services-main/component-definitions/*.oscal.json","key":"aws_cdef_files","label":"AWS component definition files","value":230},{"derivation":"count of components with type == 'software' across all AWS component-definitions","key":"aws_software_components","label":"AWS Config rules modelled as software components","value":429},{"derivation":"count of software-component implemented-requirements where catalog control's assessment-method part title == component title","key":"aws_title_matches","label":"software component titles matching the catalog TechnicalControlId, out of 429","value":429},{"derivation":"452 minus the count of distinct control-ids cited by software components","key":"aws_controls_without_check","label":"catalog controls with no software check component","value":29},{"derivation":"452 minus the count of distinct control-ids cited by any component","key":"aws_controls_unreferenced","label":"catalog controls referenced by no component at all","value":14},{"derivation":"sum(len(component.rules)) across cos- and idservice-component-definition.json","key":"ibm_rules","label":"rules in the IBM component definitions","value":5},{"derivation":"sum(len(component.checks)) across ansible- and oscap-validation-component-definition.json","key":"ibm_checks","label":"checks in the IBM validation component definitions","value":5},{"derivation":"count of distinct implemented-requirements.control-id across cos and idservice","key":"ibm_control_ids","label":"distinct control-ids covered by the IBM component definitions","value":9},{"derivation":"sum(len(assessment-plan.local-definitions.activities)) across the 15 Easy Dynamics assessment plans","key":"ez_activities","label":"assessment plan activities across the Easy Dynamics corpus","value":2425},{"derivation":"sum(len(activity.steps)) across the 15 Easy Dynamics assessment plans","key":"ez_steps","label":"assessment plan steps across the Easy Dynamics corpus","value":5694},{"derivation":"count of activity props where name == 'method' and value == 'TEST' across the 9 STIG files; no other method value occurs","key":"stig_method_test","label":"STIG activities carrying method TEST, out of 2271","value":2271},{"derivation":"count of step props where name == 'assessment-status' and value == 'automated' in CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","key":"cis_ubuntu_automated","label":"CIS Ubuntu 24.04 steps marked automated","value":576},{"derivation":"same file, value == 'manual'","key":"cis_ubuntu_manual","label":"CIS Ubuntu 24.04 steps marked manual","value":40},{"derivation":"count of step props where name == 'assessment-status' and value == 'automated' in CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","key":"cis_postgres_automated","label":"CIS PostgreSQL 18 steps marked automated","value":0},{"derivation":"same file, value == 'manual'","key":"cis_postgres_manual","label":"CIS PostgreSQL 18 steps marked manual","value":144},{"derivation":"count of Easy Dynamics/STIG_XCCDF to OSCAL Assessment Plans/*.json","key":"stig_files","label":"STIG assessment plan files","value":9},{"derivation":"count of STIG files where assessment-plan.import-ssp.href == 'PLACEHOLDER'","key":"stig_placeholder","label":"STIG files whose import-ssp.href is the literal string PLACEHOLDER","value":9},{"derivation":"count of AWS/oscal-content-for-aws-services-main/catalogs/*.oscal.json","key":"aws_catalog_files","label":"AWS catalog files","value":1},{"derivation":"count of files under Easy Dynamics/** whose root element is assessment-plan. The corpus also holds one assessment-results file and two non-OSCAL benchmark files, which this does not count","key":"ez_files","label":"Easy Dynamics assessment plan files","value":15},{"derivation":"count of IBM/*component-definition.json","key":"ibm_cdef_files","label":"IBM component definition files","value":4},{"derivation":"count of IBM/assessment-plan.json","key":"ibm_ap_files","label":"IBM assessment plan files","value":1},{"derivation":"count of IBM/assessment-result.json","key":"ibm_ar_files","label":"IBM assessment result files","value":1},{"derivation":"recursive count of every props array across Easy Dynamics/**/*.json","key":"ez_props","label":"props across the Easy Dynamics assessment plans","value":55458},{"derivation":"recursive count of every props array across AWS/oscal-content-for-aws-services-main/**/*.json","key":"aws_props","label":"props across the AWS catalog and component definitions","value":6094},{"derivation":"recursive count of every props array across IBM/*component-definition.json","key":"ibm_cdef_props","label":"props across the four IBM component definitions","value":0},{"derivation":"sum(1 for g in catalog.groups if g.groups) in aws_security-hub.oscal.json","key":"aws_nested_groups","label":"AWS catalog groups that themselves contain groups","value":0},{"derivation":"sum(len(c.params) for g in catalog.groups for c in g.controls)","key":"aws_control_params","label":"params declared on AWS catalog controls","value":0},{"derivation":"count of AWS/**/*.json whose root key is profile","key":"aws_profile_files","label":"profile files in the AWS corpus","value":0},{"derivation":"count of Easy Dynamics/CISA BOD 25-01/*.json","key":"cisa_files","label":"CISA BOD 25-01 files: four assessment plans, one assessment result and the sample SSP they import","value":6},{"derivation":"count of step props named criticality with value SHALL in Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","key":"cisa_criticality_shall","label":"steps carrying criticality SHALL in ap-cisa-scuba-agnostic.json","value":73},{"derivation":"count of step props named criticality with value SHOULD in the same file","key":"cisa_criticality_should","label":"steps carrying criticality SHOULD in ap-cisa-scuba-agnostic.json","value":55},{"derivation":"count of objects carrying a string type together with include-all or include-subjects, where type is component","key":"ez_subjects_component","label":"assessment-subject blocks typed component across the Easy Dynamics corpus","value":2407},{"derivation":"same walk, where type is inventory-item","key":"ez_subjects_inventory_item","label":"assessment-subject blocks typed inventory-item across the Easy Dynamics corpus, including the one on each CISA associated activity","value":26},{"derivation":"len(assessment-results.results[0].findings) in IBM/assessment-result.json. The file also carries a findings array at the document root, outside results, where the model does not define one","key":"ibm_ar_findings","label":"findings inside the result object of the IBM assessment result","value":0},{"derivation":"len(assessment-results.results[0].observations) in IBM/assessment-result.json","key":"ibm_ar_observations","label":"observations in the IBM assessment result","value":1},{"derivation":"sum(1 for a in every assessment-plan.local-definitions.activities if a.related-controls) across Easy Dynamics/**/*.json","key":"ez_activities_with_related_controls","label":"assessment plan activities carrying related-controls, out of 2425","value":2279},{"derivation":"sum(1 for ir in every control-implementation.implemented-requirements if not ir.implementing-rules) across IBM/*component-definition.json","key":"ibm_ir_without_rules","label":"IBM implemented-requirements listing no implementing rule, out of 9","value":1},{"derivation":"count of assessment plans under Easy Dynamics/Center for Internet Security/","key":"cis_ap_files","label":"CIS assessment plan files","value":2},{"derivation":"size of the set of control-id values under reviewed-controls.control-selections[].include-controls[] in the two CIS plans","key":"cis_control_ids","label":"distinct control ids referenced across the CIS assessment plans","value":82},{"derivation":"distinct control ids under a control-selection whose props carry resolution-status = synthetic-ids","key":"cis_synthetic_ids","label":"control ids the content itself flags as synthetic","value":53},{"derivation":"count, not set size, of include-control entries under a control-selection flagged resolution-status = synthetic-ids","key":"cis_synthetic_refs","label":"references to those 53 synthetic control ids","value":84},{"derivation":"count of props name=step-type value=remediate across the 15 Easy Dynamics assessment plans","key":"ez_step_type_remediate","label":"steps carrying step-type remediate, all in the STIG plans","value":2271},{"derivation":"count of props name=step-type value=remediation across the 15 Easy Dynamics assessment plans","key":"ez_step_type_remediation","label":"steps carrying step-type remediation, all in the CIS plans","value":380},{"derivation":"count of props name=step-type value=check across the 15 Easy Dynamics assessment plans","key":"ez_step_type_check","label":"steps carrying step-type check, all in the STIG plans","value":2271},{"derivation":"count of props name=step-type value=audit across the 15 Easy Dynamics assessment plans","key":"ez_step_type_audit","label":"steps carrying step-type audit, all in the CIS plans","value":380},{"derivation":"size of the set of sorted step-type value sets, grouped by the directory each plan sits in","key":"ez_step_type_vocabularies","label":"distinct step-type vocabularies in use across the two benchmark families","value":2},{"derivation":"count of files under Easy Dynamics/** whose root element is assessment-results","key":"ez_ar_files","label":"assessment results in the corpus","value":1},{"derivation":"count of files in Easy Dynamics/** whose root element is system-security-plan","key":"ez_ssp_files","label":"system security plans in the corpus: the sample SSP the CISA plans import","value":1},{"derivation":"count of role-id keys valued 'owner' at any depth in AWS/**/component-definitions/*.oscal.json","key":"aws_owner_refs","label":"references to role-id owner across the AWS component definitions","value":429},{"derivation":"count of AWS component definition files containing at least one role-id valued 'owner'","key":"aws_files_referencing_owner","label":"component definition files referencing role-id owner","value":67},{"derivation":"count of metadata.roles entries with id 'author', by file","key":"aws_files_declaring_author","label":"component definition files declaring the role author","value":230},{"derivation":"size of the set of metadata.roles[].id across all 230 AWS component definition files","key":"aws_roles_declared","label":"distinct roles declared anywhere in the AWS component definitions","value":1},{"derivation":"count of control parts with name='guidance' in aws_security-hub.oscal.json","key":"aws_guidance_parts","label":"guidance parts across the catalog controls, one per control","value":452},{"derivation":"size of the set of prose values among control parts named 'guidance'","key":"aws_guidance_distinct","label":"distinct guidance prose strings among the guidance parts","value":1},{"derivation":"count of catalog.groups entries whose id is exactly 'TestControl'","key":"aws_test_groups","label":"catalog groups with the id TestControl","value":1},{"derivation":"sum(len(g.controls)) over catalog groups with id 'TestControl'","key":"aws_test_controls","label":"controls inside the TestControl group","value":1},{"derivation":"count of TestControl controls with a rel='remediation' link whose href does not contain the control's own service prefix","key":"aws_test_controls_mislinked","label":"TestControl controls whose remediation link names a different control","value":1},{"derivation":"count of files in AWS/** whose root element is system-security-plan","key":"aws_ssp_files","label":"system security plans in the corpus","value":0},{"derivation":"count of files in AWS/** whose root element is assessment-plan","key":"aws_ap_files","label":"assessment plans in the corpus","value":0},{"derivation":"count of files in AWS/** whose root element is assessment-results","key":"aws_ar_files","label":"assessment results in the corpus","value":0},{"derivation":"size of the set of component-definition.uuid across IBM/*component-definition.json","key":"ibm_document_uuids","label":"distinct document uuids across the 4 IBM component definition files","value":1},{"derivation":"sum(len(c.checks)) over components in IBM/oscap-validation-component-definition.json","key":"ibm_oscap_checks","label":"checks in the OSCAP validation component","value":3},{"derivation":"count of OSCAP checks whose target-component-uuid is not a component uuid declared in any of the 4 IBM component definitions","key":"ibm_oscap_checks_dangling","label":"OSCAP checks whose target-component-uuid resolves to no component","value":3},{"derivation":"sum(len(c.checks)) over components in IBM/ansible-validation-component-definition.json","key":"ibm_ansible_checks","label":"checks in the ANSIBLE validation component","value":2},{"derivation":"count of ANSIBLE checks whose target-component-uuid is not a component uuid declared in any of the 4 IBM component definitions","key":"ibm_ansible_checks_dangling","label":"ANSIBLE checks whose target-component-uuid resolves to no component","value":0},{"derivation":"1 if the IBM assessment plan carries a 'local-defintions' key and no 'local-definitions' key, else 0","key":"ibm_ap_local_definitions_misspelled","label":"assessment plans spelling local-definitions without its second i","value":1},{"derivation":"count of files in IBM/*.json whose root element is system-security-plan","key":"ibm_ssp_files","label":"system security plans in the corpus","value":0},{"derivation":"count of Easy Dynamics assessment plan files whose text contains the key \"step-type\"","key":"ez_files_with_step_type","label":"assessment plans using step-type at all","value":11}]},"data/criteria.json":{"criteria":[{"name":"Triad fidelity","number":1,"question":"Does the option keep regulator, implementer and assessor roles separable?","slots":["1","3","6a","6b"]},{"name":"Normativity","number":2,"question":"Can the artifact express must versus may? Can an auditor treat it as binding?","slots":["1"]},{"name":"Requirement level","number":3,"question":"Can shall, should and may be represented at all?","slots":["1"]},{"name":"Hierarchy support","number":4,"question":"Does the model natively carry deep benchmark hierarchies?","slots":["1"]},{"name":"Tailoring","number":5,"question":"Can an organization select, exclude and parameterize at scale?","slots":["1"]},{"name":"Authoring burden","number":6,"question":"How many OSCAL artifacts must a benchmark author produce per benchmark, multiplied across roughly 100 CIS guides?","slots":["1","2","3","4","5","6a","6b"]},{"name":"SSP impact","number":7,"question":"How many additional items enter the SSP? Does the SSP end up mixing desired and actual state?","slots":["6a"]},{"name":"Response fidelity","number":8,"question":"Can a system owner answer per host or inventory item, or only per component?","slots":["4"]},{"name":"Traceability","number":9,"question":"Can a consumer traverse control to rule to check to activity to task to observation using core schema only?","slots":["1","2","3","5","6b"]},{"name":"Schema change cost","number":10,"question":"How many models change, and what is the realistic ratification timeline?","slots":["1","2","3","4","5","6a","6b"]},{"name":"Update decoupling","number":11,"question":"When a benchmark revises independently of the regulation, what has to change downstream?","slots":["1"]},{"name":"Cross-framework use","number":12,"question":"Does this help someone operating under SOC 2, ISO and FedRAMP at the same time?","slots":["2"]},{"name":"Inspectability","number":13,"question":"Can an operator see what a check does before running it on their systems?","slots":["3"]},{"name":"Prop dependence","number":14,"question":"How much meaning lives in namespaced props rather than core schema?","slots":["1","2","3","4","5","6a","6b"]},{"name":"Existing content","number":15,"question":"Is there working end-to-end content today, including an SSP and an AR?","slots":["1","2","3","4","5","6a","6b"]}],"note":"Fifteen evaluation criteria maintained in this repository for comparing the three approaches. The questions and slot mappings define the analysis scope."},"data/examples.json":{"cis_derived":["assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json"],"files":[{"approach":"assessment-first","bytes":308830,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","sha256":"521acdef03590676c0a041bf920e36a7575c63683f04e787909d3c4dcc10ea66"},{"approach":"assessment-first","bytes":325728,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-maester.json","sha256":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653"},{"approach":"assessment-first","bytes":293862,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","sha256":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e"},{"approach":"assessment-first","bytes":298328,"path":"assessment-first/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","sha256":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d"},{"approach":"assessment-first","bytes":19829,"path":"assessment-first/CISA BOD 25-01/assessment-plan.json","sha256":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee"},{"approach":"assessment-first","bytes":39652,"path":"assessment-first/CISA BOD 25-01/sample-ssp.json","sha256":"2309e2f7ad9e8a468ac38fa7584094cab3e1bc20fc1d8ae108836f4e65ecf66d"},{"approach":"assessment-first","bytes":1032133,"path":"assessment-first/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1.0.0.json","sha256":"b72eda73c5bef60e2971c93261bc226594cfb8d8aa1be92deb6b2e121bf05379"},{"approach":"assessment-first","bytes":423087,"path":"assessment-first/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","sha256":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8"},{"approach":"assessment-first","bytes":6823924,"path":"assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","sha256":"1a90fccb4442decd119382233ff8986caaaeede83dcf3c5ab22a87c747ab0c81"},{"approach":"assessment-first","bytes":1768114,"path":"assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","sha256":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c"},{"approach":"assessment-first","bytes":821083,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","sha256":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6"},{"approach":"assessment-first","bytes":823183,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","sha256":"e1eed16a4a0f6d6b6025ce05c16832458bbcd4ba16d597340d0c764333197841"},{"approach":"assessment-first","bytes":2454926,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel8.json","sha256":"54cd0e15efb7c96347cfd16012d6fc81b93861079ce8a2ccf4e61eac57b538f7"},{"approach":"assessment-first","bytes":3051725,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel9.json","sha256":"9fbd810f7c658809a3be29bdb9bc14dfdafabbe289482454208f86b3646c7783"},{"approach":"assessment-first","bytes":1310065,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu22.json","sha256":"46738bf619cdfbef00913d761586633bec301e4aae5050a30c823f27509c7e7d"},{"approach":"assessment-first","bytes":1341083,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","sha256":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e"},{"approach":"assessment-first","bytes":1940344,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","sha256":"24dead32391e392f3d25501b0581fef5a719add51667c98920ad01f2d9273207"},{"approach":"assessment-first","bytes":1858865,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","sha256":"bfe441c22311614bc30cd080a57b5242129137912400a73a3e731a9f7a9abd7a"},{"approach":"assessment-first","bytes":1867817,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2025.json","sha256":"b8e54f5a9f6e554cd58bfe0c6b5be46085af5b760786ff6c933b1be7f8150bf8"},{"approach":"component-first","bytes":1106,"path":"component-first/ansible-validation-component-definition.json","sha256":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd"},{"approach":"component-first","bytes":5105,"path":"component-first/assessment-plan.json","sha256":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6"},{"approach":"component-first","bytes":4275,"path":"component-first/assessment-result.json","sha256":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806"},{"approach":"component-first","bytes":2525,"path":"component-first/cos-component-definition.json","sha256":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a"},{"approach":"component-first","bytes":5230,"path":"component-first/idservice-component-definition.json","sha256":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf"},{"approach":"component-first","bytes":1297,"path":"component-first/oscap-validation-component-definition.json","sha256":"9efe6492ede4a21a743db6afe6bf05efda79c206d00dc6ee40e89f16145323f3"}],"link_only":{"catalog-first":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/"},"note":"The curated OSCAL examples committed in this repository, indexed by tools/copy_examples.py with the path, byte count and SHA-256 of each. Every build re-verifies the files against this index, so an edit is only accepted through an explicit --rebaseline run recorded in BUILD-LOG.md. Catalog-first is not here: it is published in a public repository and linked at the locked revision instead.","shared":[{"bytes":10442037,"path":"NIST_SP-800-53_rev5_catalog.json","sha256":"01f37cf90ea99d92242c936cbfbdebcc338eef1f71454e2acac36cc56e9bc062"}]},"data/generated-pages.json":{"note":"The hash of each approach page as this tool last wrote it. tools/approach_pages.py compares the page on disk against this before overwriting, so a hand edit to a generated page stops the build instead of disappearing into it.","sha256":{"assessment-first":"78f38c7ef742a486d4860d618df1a78e4487fef226e77317a5621f5501bab18b","catalog-first":"3319bcf155cdc7881b1dd1bfd42bdf9e679b2ed2ec5ec3b16576b04c15ed4ee8","component-first":"e169a9ca2c71028b41e0b0641dbba2a5086f6d453df2cf2eceefaf23df1d7827"},"written_by":"tools/approach_pages.py"},"data/glossary.json":{"note":"Definitions used by this analysis, with links from first uses. Alternative meanings and unresolved distinctions are identified without selecting an approach.","terms":[{"other_usages":[{"usage":"A normative requirement, a shall, equivalent to a control","who":"Catalog-first, Option A"},{"usage":"A statement of how a component may be configured, descriptive rather than binding","who":"Component-first, Option B"},{"usage":"Colloquially, the check code itself","who":"Ambiguous usage; this analysis distinguishes rule from check"},{"usage":"An AWS Config rule: a deployable resource with parameters","who":"AWS Config, the product"}],"see_also":["check","control","desired state","requirement level"],"site_usage":"One technical requirement or recommendation, finer-grained than a control, without any claim about whether it is binding. A working definition for comparing approaches, not selecting an interpretation.","status":"contested","term":"rule"},{"other_usages":[],"see_also":["rule","validation component","assessment platform"],"site_usage":"An executable or procedural test that determines whether a rule is satisfied. One rule may have many checks, one per tool.","status":"settled","term":"check"},{"other_usages":[{"usage":"Possible state: a technology provider describes available configurations rather than required configurations","who":"Alternative interpretation of component configuration"}],"see_also":["actual state","rule","implementation claim"],"site_usage":"The configuration prescribed by a rule, distinct from the system's observed configuration, or actual state.","status":"contested","term":"desired state"},{"other_usages":[],"see_also":["desired state","assessment result"],"site_usage":"The system's observed configuration, distinct from the configuration prescribed by a rule, or desired state.","status":"settled","term":"actual state"},{"other_usages":[],"see_also":["rule","link to a control","catalog"],"site_usage":"A requirement from a regulatory framework, such as NIST SP 800-53. Coarser than a rule. One control is typically served by many rules.","status":"settled","term":"control"},{"other_usages":[],"see_also":["control","mapping collection","finding","observation"],"site_usage":"An optional relationship from a rule to regulatory controls. A rule may serve several controls, one, or none. A rule without a control link can have observations but no control-targeted finding.","status":"settled","term":"link to a control"},{"other_usages":[{"usage":"Hardening guidance, used interchangeably","who":"This analysis"}],"see_also":["rule","hardening guidance"],"site_usage":"A published set of technology-specific hardening guidance, including CIS Benchmarks, DISA STIGs, CISA SCuBA baselines and technology provider guides.","status":"settled","term":"benchmark"},{"other_usages":[],"see_also":["benchmark","rule"],"site_usage":"Technology-specific guidance for configuring hardware, software or services securely. Used as a synonym for benchmark in this analysis.","status":"settled","term":"hardening guidance"},{"other_usages":[],"see_also":["rule","normativity"],"site_usage":"Whether a statement is a shall, should or may. OSCAL has no dedicated core requirement-level field across these approaches. Properties can carry such labels, but consumers need shared conventions to interpret them; model placement alone does not establish requirement level.","status":"not-established","term":"requirement level"},{"other_usages":[],"see_also":["requirement level","rule"],"site_usage":"Whether an artifact expresses binding requirements against which an auditor can assess a system. Normativity is part of the debate over model placement.","status":"contested","term":"normativity"},{"other_usages":[],"see_also":[],"set_aside":true,"site_usage":"A Component Definition construct grouping components and control-implementations to express joint satisfaction. Whether capabilities should be added to the SSP or removed from Component Definition remains an open design question in this analysis. No position is selected.","status":"contested","term":"capability"},{"other_usages":[{"usage":"A component whose purpose is to run checks rather than to be checked. Type validation, carrying a checks array.","who":"Component-first examples using proposed assemblies"},{"usage":"A component enumerating the compliance frameworks a service has been validated against.","who":"Alternative interpretation, not demonstrated by the OSCAL examples"}],"see_also":["check","component"],"site_usage":"Two distinct meanings are used: a component running checks, or a component describing validation against frameworks. This analysis identifies the intended meaning.","status":"contested","term":"validation component"},{"not_established_note":"The open question is when a component alone identifies a runner and when an assessment platform adds necessary execution context.","other_usages":[],"see_also":["assessment asset","component","actor"],"site_usage":"An OSCAL assessment-assets element that may reference components through uses-components. The examples do not establish a consistent convention for distinguishing assessment platforms, assessment assets and components in runner descriptions.","status":"not-established","term":"assessment platform"},{"not_established_note":"A consumer still needs to associate each task or observation with the asset used.","other_usages":[],"see_also":["assessment platform","component","actor"],"site_usage":"The OSCAL assessment-assets container holds components and assessment-platforms. The examples do not establish a consistent convention for identifying runners across these structures.","status":"not-established","term":"assessment asset"},{"not_established_note":"The examples leave open whether components should represent individual rules, products or policy engines and how consumers reconcile those levels.","other_usages":[],"see_also":["assessment platform","assessment asset","validation component"],"site_usage":"A part of a system, with related meanings across Component Definition, SSP, Assessment Plan and Assessment Results models. The distinction from assessment platforms and assets remains unresolved, as does granularity: a component may represent a configuration rule or a policy engine.","status":"not-established","term":"component"},{"not_established_note":"The examples use different runner-identification conventions. No single convention is established here for associating a task or observation with its producer.","other_usages":[{"usage":"An assessment platform, optionally reaching components through uses-components","who":"OSCAL assessment-assets"},{"usage":"A component of type validation, carrying the checks it runs","who":"Component-first, Option B, proposed schema"},{"usage":"An origin actor on an assessment result","who":"OSCAL assessment-results"},{"usage":"A tool named in a prop at task level","who":"The assessment plans in two of the three corpora"}],"see_also":["assessment platform","assessment asset","component","check"],"site_usage":"The tool or person performing a check, addressed by question 5. Actor is a neutral label in this analysis because no single OSCAL construct covers all uses.","status":"not-established","term":"actor"},{"other_usages":[],"see_also":["assessment result","system security plan"],"site_usage":"The system owner's narrative assertion of control implementation and design intent per component. The SSP represents claims through implemented-requirement, statement and by-component. Addressed by question 6a.","status":"settled","term":"implementation claim"},{"other_usages":[],"see_also":["implementation claim","observation","finding"],"site_usage":"The assessor's evidence-based record of whether a control was satisfied for a subject at a point in time. The AR uses observation, finding and status for binary or graded outcomes. Addressed by question 6b.","status":"settled","term":"assessment result"},{"other_usages":[],"see_also":["finding","assessment result","link to a control"],"site_usage":"An AR element recording observed evidence. Requires uuid, description, methods and collected, with no control reference. Observations are available for rules with or without control links.","status":"settled","term":"observation"},{"other_usages":[],"see_also":["observation","link to a control","assessment result"],"site_usage":"An AR element recording whether an objective is satisfied. The required target type is restricted to statement-id or objective-id, both control-derived. A rule without a control link cannot have a finding.","status":"settled","term":"finding"},{"other_usages":[],"see_also":["link to a control","catalog"],"site_usage":"An OSCAL model, GA since 1.2, relating collections of controls. Third parties can publish mappings after the source catalogs. The mapping-item type permits control and statement targets, not component rules or activities.","status":"settled","term":"mapping collection"},{"other_usages":[],"see_also":["profile","control"],"site_usage":"OSCAL model, Control layer. A structured set of controls and control enhancements.","status":"settled","term":"catalog"},{"other_usages":[],"see_also":["catalog"],"site_usage":"OSCAL model, Control layer. A baseline or overlay that selects and customizes controls from catalogs.","status":"settled","term":"profile"},{"other_usages":[],"see_also":["system security plan","component"],"site_usage":"OSCAL model, Implementation layer. Describes how components implement controls.","status":"settled","term":"component definition"},{"other_usages":[],"see_also":["component definition","implementation claim"],"site_usage":"OSCAL model, Implementation layer. Documents how a particular system implements required controls. Abbreviated SSP.","status":"settled","term":"system security plan"},{"other_usages":[],"see_also":["assessment result","activity","step"],"site_usage":"OSCAL model, Assessment layer. Defines how controls will be assessed, through activities, steps and tasks. Abbreviated AP or SAP.","status":"settled","term":"assessment plan"},{"other_usages":[],"see_also":["step","assessment plan"],"site_usage":"An assessment plan local-definitions element containing steps. How to divide a benchmark procedure between activities and steps remains an analysis question.","status":"not-established","term":"activity"},{"other_usages":[],"see_also":["activity","assessment plan"],"site_usage":"A child of an assessment plan activity. The examples do not establish one consistent boundary between the work represented by an activity and its steps.","status":"not-established","term":"step"},{"other_usages":[],"see_also":["assessment plan","observation","finding"],"site_usage":"OSCAL model, Assessment layer. Documents the results of control assessments, as observations and findings. Abbreviated AR or SAR.","status":"settled","term":"assessment results"},{"other_usages":[],"see_also":["assessment results"],"site_usage":"OSCAL model, Assessment layer. Documents remediation plans for identified issues. Abbreviated POA&M.","status":"settled","term":"plan of action and milestones"},{"other_usages":[],"see_also":["implementer","assessor"],"site_usage":"One of three stakeholder roles. Publishes requirements or recommendations for organisations to version, tailor and cite without depending on a specific system.","status":"settled","term":"publisher"},{"other_usages":[],"see_also":["publisher","assessor","desired state"],"site_usage":"One of three stakeholder roles. Uses requirements as desired-state configuration that a configuration engine can apply.","status":"settled","term":"implementer"},{"other_usages":[],"see_also":["publisher","implementer","check"],"site_usage":"One of three stakeholder roles. Runs checks or reviews sufficient evidence to determine whether requirements are satisfied.","status":"settled","term":"assessor"}]},"data/joins.json":{"approaches":{"assessment-first":{"hops":[{"from":"rule","how":"containment","note":"The activity contains the check as the first step. A property on the step identifies an executable check resolved outside OSCAL.","pairs":[{"foreign":{"field":"no field","model":"assessment-plan","slot":"1"},"how":"containment","primary":{"field":"activities[].steps[].uuid","model":"assessment-plan","slot":"3","value":"333ddd0f-22da-4c18-8bc3-98e808746bca"}},{"foreign":{"field":"steps[].props[name=check].value","model":"assessment-plan","slot":"3","value":"SV-270747r1066730_rule"},"how":"name-match","primary":{"field":"no field","model":"nothing","slot":"5"}}],"to":"check"},{"from":"rule","how":"reference","note":"The activity references the framework control through related-controls, without a separate mapping document or an additional mapping identifier to maintain.","pairs":[{"foreign":{"field":"activities[].related-controls.control-selections[].include-controls[].control-id","model":"assessment-plan","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"reference","note":"The example plan identifies platforms for the assessment as a whole. The platform reference does not identify the engine used for each check.","pairs":[{"foreign":{"field":"assessment-platforms[].uses-components[].component-uuid","model":"assessment-plan","slot":"5","value":"56270516-2673-4d4c-8d4f-52e4107f968d"},"how":"reference","primary":{"field":"assessment-assets.components[].uuid","model":"assessment-plan","slot":"5"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The plan references one system security plan through a back-matter resource. Where no plan of record exists, the resource can describe the system in prose.","pairs":[{"foreign":{"field":"import-ssp.href","model":"assessment-plan","slot":"6a","value":"#d381c885-4851-4931-828c-29bbb24fbaa3"},"how":"reference","primary":{"field":"back-matter.resources[].uuid","model":"assessment-plan","slot":"6a","value":"d381c885-4851-4931-828c-29bbb24fbaa3"}}],"to":"claim"},{"from":"runtime","how":"reference","note":"The example observation references the planned activity as the subject. The reference identifies the activity, not an inventory item assessed by the check.","pairs":[{"foreign":{"field":"observations[].subjects[].subject-uuid","model":"assessment-results","slot":"6b","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"},"how":"reference","primary":{"field":"activities[].uuid","model":"assessment-plan","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}}],"to":"result"},{"from":"result","how":"reference","note":"The finding targets a framework control objective. The target links the result to the framework without depending on an implementation statement in a plan of record.","pairs":[{"foreign":{"field":"findings[].target.target-id","model":"assessment-results","slot":"6b","value":"sc-28_obj"},"how":"reference","primary":{"field":"controls[].parts[objective].id","model":"catalog","slot":"2"}}],"to":"control"}],"introduced":{"field":"activities[].uuid","model":"assessment-plan","note":"The assessment plan defines the rule as an activity in the assessment layer, outside the implementation claim. The chain starts from the activity uuid.","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}},"catalog-first":{"hops":[{"from":"rule","how":"name-match","note":"The control references the check by title, a match not enforced by the schema. The check references the control by a resolvable id.","pairs":[{"foreign":{"field":"parts[assessment-method].props.TechnicalControlId","model":"catalog","slot":"1","value":"SV-270747r1066730_rule"},"how":"name-match","primary":{"field":"components[].title","model":"component-definition","slot":"3","value":"SV-270747r1066730_rule"}},{"foreign":{"field":"implemented-requirements[].control-id","model":"component-definition","slot":"3","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}}],"to":"check"},{"from":"rule","how":"reference","note":"A separate mapping collection links the catalogs. A third party can publish the mapping after both catalogs are published without owning either source.","pairs":[{"foreign":{"field":"maps[].sources[].id-ref","model":"mapping-collection","slot":"2","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}},{"foreign":{"field":"maps[].targets[].id-ref","model":"mapping-collection","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"none","note":"ConfigRuleId identifies the executable rule, but the content does not identify the engine that executes the check.","pairs":[{"foreign":{"field":"components[].props.ConfigRuleId","model":"component-definition","slot":"3","value":"SV_270747R1066730_RULE"},"how":"none","primary":{"field":"no field","model":"nothing","slot":"5"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The claim references a component, not a host. The by-component assembly has no assessment subject field for an individual instance.","pairs":[{"foreign":{"field":"implemented-requirements[].control-id","model":"system-security-plan","slot":"6a","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}},{"foreign":{"field":"by-components[].component-uuid","model":"system-security-plan","slot":"6a","value":"534b356b-0de1-48d4-8536-5d41ed717456"},"how":"reference","primary":{"field":"system-implementation.components[].uuid","model":"system-security-plan","slot":"6a"}}],"to":"claim"},{"from":"claim","how":"reference","note":"The finding targets the implementation statement in the system security plan and references supporting observations, connecting the assessment outcome to the claim.","pairs":[{"foreign":{"field":"findings[].target.target-id","model":"assessment-results","slot":"6b","value":"UBTU-24-600090_smt"},"how":"reference","primary":{"field":"statements[].statement-id","model":"system-security-plan","slot":"6a","value":"UBTU-24-600090_smt"}},{"foreign":{"field":"related-observations[].observation-uuid","model":"assessment-results","slot":"6b","value":"28e28d31-4428-4ff5-8c9e-ea1198dfb552"},"how":"reference","primary":{"field":"observations[].uuid","model":"assessment-results","slot":"6b"}}],"to":"result"}],"introduced":{"field":"controls[].id","model":"catalog","note":"The product catalog defines the rule as a control, using the same OSCAL structure as a regulatory control. The chain starts from the control id.","slot":"1","value":"UBTU-24-600090"}},"component-first":{"hops":[{"from":"rule","how":"composite","note":"The check references both a rule id and a target component uuid. A rule id is unique only within the declaring component.","pairs":[{"foreign":{"field":"checks[].rule-id","model":"component-definition","slot":"3","value":"ubtu24_data_at_rest_encrypted"},"how":"composite","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"checks[].target-component-uuid","model":"component-definition","slot":"3","value":"5ca997b3-bb3e-4c7a-8969-69ed44577d47"},"how":"composite","primary":{"field":"components[].uuid","model":"component-definition","slot":"1","value":"5ca997b3-bb3e-4c7a-8969-69ed44577d47"}}],"to":"check"},{"from":"rule","how":"reference","note":"The component definition contains both references. Control implementations already link components to controls; the proposed implementing-rules assembly adds references to individual rules.","pairs":[{"foreign":{"field":"implemented-requirements[].implementing-rules[].rule-id","model":"component-definition","slot":"2","value":"ubtu24_data_at_rest_encrypted"},"how":"reference","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"implemented-requirements[].control-id","model":"component-definition","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"containment","note":"The validation component contains the checks executed by the engine. Each additional engine is represented by a separate validation component.","pairs":[{"foreign":{"field":"no field","model":"component-definition","slot":"3"},"how":"containment","primary":{"field":"components[].uuid","model":"component-definition","slot":"5","value":"b3c8813d-d479-450a-8178-fbbf846faccf","where":"the validation component"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The proposed implementing-rules assembly references the rule supporting the claim, allowing a consumer to trace the claim to the check through OSCAL references.","pairs":[{"foreign":{"field":"by-components[].implementing-rules[].rule-id","model":"system-security-plan","slot":"6a","value":"ubtu24_data_at_rest_encrypted"},"how":"reference","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"by-components[].component-uuid","model":"system-security-plan","slot":"6a","value":"534b356b-0de1-48d4-8536-5d41ed717456"},"how":"reference","primary":{"field":"system-implementation.components[].uuid","model":"system-security-plan","slot":"6a"}}],"to":"claim"},{"from":"runtime","how":"reference","note":"The observation identifies the check and host, allowing different outcomes for two machines within the same system boundary to be recorded separately.","pairs":[{"foreign":{"field":"observations[].assessment-check-id","model":"assessment-results","slot":"6b","value":"SV-270747r1066730_rule"},"how":"reference","primary":{"field":"checks[].id","model":"component-definition","slot":"3","value":"SV-270747r1066730_rule"}},{"foreign":{"field":"observations[].subjects[].subject-uuid","model":"assessment-results","slot":"6b","value":"06297a03-cae0-414b-8332-2fc882f81aa1"},"how":"reference","primary":{"field":"system-implementation.inventory-items[].uuid","model":"system-security-plan","slot":"4"}}],"to":"result"},{"from":"result","how":"none","note":"The example result contains observations but no findings. No finding target identifies the control, and no finding status records whether the objective was satisfied.","pairs":[{"foreign":{"field":"no field","model":"assessment-results","slot":"6b"},"how":"none","primary":{"field":"no field","model":"catalog","slot":"2"}}],"to":"control"}],"introduced":{"field":"components[].rules[].id","model":"component-definition","note":"The proposed rules assembly defines the rule on the product component. The chain starts from the rule id within that component definition.","slot":"1","value":"ubtu24_data_at_rest_encrypted"}}},"how":[{"key":"containment","label":"Containment","meaning":"A parent contains the child directly; no key matching or dereferencing is needed."},{"key":"reference","label":"Reference","meaning":"A schema-defined identifier reference resolves to a target identifier."},{"key":"name-match","label":"Name match","meaning":"Two strings match by convention. The schema does not enforce the relationship, so a mismatch may go undetected."},{"key":"composite","label":"Composite key","meaning":"Two fields jointly identify a target. Either field alone may identify the wrong target or no target."},{"key":"none","label":"No join","meaning":"No field directly connects the entries. A consumer must follow other relationships, or the connection is absent."}],"intro":"The chain connects a rule to checks, implementation claims and assessment results. Each step identifies the relationships a consumer must resolve and the fields used to resolve those relationships.","note":"The join chain connects rule definitions, checks, implementation claims and assessment results. Each relationship identifies a foreign key and the corresponding primary key. Values match the two example rules on the six questions page; tools/verify.py checks each value against those encodings.","stages":[{"key":"rule","label":"Rule","meaning":"where the rule is introduced","slot":"1"},{"key":"control","label":"Control","meaning":"the framework control served by the rule","slot":"2"},{"key":"check","label":"Check","meaning":"the test of the rule","slot":"3"},{"key":"runtime","label":"Runtime","meaning":"what executes the check","slot":"5"},{"key":"claim","label":"Claim","meaning":"the system owner's statement of implementation","slot":"6a"},{"key":"result","label":"Result","meaning":"what an assessment recorded","slot":"6b"}],"step_order":[["rule","check"],["rule","control"],["check","runtime"],["runtime","claim"],["runtime","result"],["claim","result"],["result","control"]],"title":"How the answers connect"},"data/model-icons.json":{"icons":{"assessment-plan":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"height":"30","rx":"3","soft":false,"stroke-width":"2.27","tag":"rect","width":"24","x":"20","y":"18"},{"d":"M26 15H38V19H26V15Z","soft":false,"stroke-linejoin":"round","stroke-width":"2.27","tag":"path"},{"d":"M26 26L38 26","soft":true,"stroke-linecap":"round","stroke-width":"2.27","tag":"path"},{"d":"M26 32L34 32","soft":true,"stroke-linecap":"round","stroke-width":"2.27","tag":"path"},{"cx":"36","cy":"38","r":"5","soft":false,"stroke-width":"2.27","tag":"circle"},{"d":"M36 36V38H38","soft":false,"stroke-linecap":"round","stroke-width":"1.70","tag":"path"}],"source":"assessment_plan_model.svg","view_box":"11.1907 10.6907 41.6186 41.6186"},"assessment-results":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"height":"32","rx":"3","soft":false,"stroke-width":"2.21","tag":"rect","width":"28","x":"18","y":"16"},{"d":"M24 24L27 27L33 21","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M24 34L27 37L33 31","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M37 24L40 24","soft":true,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M37 34L40 34","soft":true,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"}],"source":"assessment_results_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"catalog":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"d":"M18 18H30L34 22V48L27 45H18V18Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.08","tag":"path"},{"d":"M46 18H34L30 22V48L37 45H46V18Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.08","tag":"path"},{"d":"M22 26L28 26","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M22 32L28 32","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M36 26L42 26","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M36 32L42 32","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"}],"source":"catalog_model.svg","view_box":"13.0728 14.0728 37.8544 37.8544"},"component-definition":{"authored_box":"0 0 64 64","layer":"implementation","shapes":[{"d":"M32 16L46 24V40L32 48L18 40V24L32 16Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M32 16V32M32 32L46 24M32 32L18 24","soft":true,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 32L32 40L46 32","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"}],"source":"component_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"mapping-collection":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"cx":"22","cy":"22","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"cx":"42","cy":"22","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"cx":"32","cy":"42","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"d":"M26 24L38 24","soft":true,"stroke-dasharray":"2 2","stroke-width":"2.08","tag":"path"},{"d":"M25 26L29 38","soft":true,"stroke-width":"2.08","tag":"path"},{"d":"M39 26L35 38","soft":true,"stroke-width":"2.08","tag":"path"}],"source":"control_mapping_model.svg","view_box":"13.0728 13.0728 37.8544 37.8544"},"plan-of-action-and-milestones":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"cx":"32","cy":"32","r":"16","soft":false,"stroke-width":"3.25","tag":"circle"},{"cx":"32","cy":"32","r":"10","soft":true,"stroke-width":"3.25","tag":"circle"},{"cx":"32","cy":"32","fill":"ink","r":"3","soft":false,"tag":"circle"},{"d":"M32 12V8M32 56V52M12 32H8M56 32H52","soft":false,"stroke-linecap":"round","stroke-width":"3.25","tag":"path"}],"source":"plan_of_action_and_milestones_model.svg","view_box":"1.7625 1.7625 60.475 60.475"},"profile":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"d":"M18 20H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 32H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 44H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"cx":"26","cy":"20","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"},{"cx":"38","cy":"32","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"},{"cx":"30","cy":"44","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"}],"source":"profile_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"system-security-plan":{"authored_box":"0 0 64 64","layer":"implementation","shapes":[{"d":"M20 16H36L44 24V48H20V16Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M36 16V24H44","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M32 30V40M32 30L28 31L26 33L26 36L28 39L32 42L36 39L38 36L38 33L36 31L32 30Z","soft":true,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"}],"source":"system_security_plan_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"}},"layers":{"assessment":{"label":"Assessment layer","models":["assessment-plan","assessment-results","plan-of-action-and-milestones"]},"control":{"label":"Control layer","models":["catalog","profile","mapping-collection"]},"implementation":{"label":"Implementation layer","models":["component-definition","system-security-plan"]}},"note":"One icon per OSCAL model, generated by tools/model_icons.py from the authored files in assets/images. Geometry only: the colour is a layer token applied by the stylesheet, and the chip behind the glyph is a CSS box. Do not edit this file; edit the SVG and regenerate."},"data/oscal-artifacts.json":{"note":"tools/oscal_artifacts.py: author data/oscal-artifacts.json.","publishers":[{"files":[{"bytes":924964,"counts":{"controls":452,"groups":77},"file":"catalogs/aws_security-hub.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/catalogs/aws_security-hub.oscal.json","href_external":true,"model":"catalog","model_label":"Catalog","title":"AWS Security Hub Controls"},{"bytes":16118,"counts":{"components":3,"implemented requirements":4,"service":1,"software":2},"file":"component-definitions/acm.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/acm.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Certificate Manager"},{"bytes":27913,"counts":{"components":8,"implemented requirements":12,"service":2,"software":6},"file":"component-definitions/cloudtrail.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/cloudtrail.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS CloudTrail"},{"bytes":12332,"counts":{"components":1,"service":1},"file":"component-definitions/config.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/config.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Config"},{"bytes":43914,"counts":{"components":18,"implemented requirements":43,"service":1,"software":17},"file":"component-definitions/iam.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/iam.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Identity and Access Management"}],"full_name":"Option A","key":"catalog-first","name":"Catalog-first","option":"Option A","repo":"https://github.com/awslabs/oscal-content-for-aws-services","rollup":{"components":861,"count":230,"model_label":"Component definition","note":"One per service. Four are listed above as examples; the rest follow the same shape.","software":429},"root":"AWS/oscal-content-for-aws-services-main","totals":{"Catalog":1,"Component definition":230}},{"files":[{"bytes":1106,"counts":{"components":1,"validation":1},"file":"ansible-validation-component-definition.json","href":"examples/component-first/ansible-validation-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo validation component definition"},{"bytes":5105,"counts":{"activities":0,"tasks":1},"file":"assessment-plan.json","href":"examples/component-first/assessment-plan.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"Assessment Plan"},{"bytes":4275,"counts":{"findings":0,"observations":1,"results":1},"file":"assessment-result.json","href":"examples/component-first/assessment-result.json","href_external":false,"model":"assessment-results","model_label":"Assessment results","title":"Assessment Result"},{"bytes":2525,"counts":{"components":1,"implemented requirements":2,"rules":2,"service":1},"file":"cos-component-definition.json","href":"examples/component-first/cos-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":5230,"counts":{"components":1,"implemented requirements":7,"rules":3,"service":1},"file":"idservice-component-definition.json","href":"examples/component-first/idservice-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":1297,"counts":{"components":1,"validation":1},"file":"oscap-validation-component-definition.json","href":"examples/component-first/oscap-validation-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo validation component definition"}],"full_name":"Option B","key":"component-first","name":"Component-first","option":"Option B","repo":null,"rollup":null,"root":"IBM","totals":{"Assessment plan":1,"Assessment results":1,"Component definition":4}},{"files":[{"bytes":308830,"counts":{"activities":7,"steps":128,"tasks":0},"file":"CISA BOD 25-01/ap-cisa-scuba-agnostic.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-agnostic.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":325728,"counts":{"activities":7,"steps":128,"tasks":1},"file":"CISA BOD 25-01/ap-cisa-scuba-maester.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-maester.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":293862,"counts":{"activities":7,"steps":128,"tasks":1},"file":"CISA BOD 25-01/ap-cisa-scuba-scubagear.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-scubagear.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":298328,"counts":{"findings":128,"observations":128,"results":1},"file":"CISA BOD 25-01/ar-cisa-scuba-scubagear.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ar-cisa-scuba-scubagear.json","href_external":false,"model":"assessment-results","model_label":"Assessment results","title":"CISA SCuBA Assessment Results - M365 Tenant"},{"bytes":19829,"counts":{"activities":8,"steps":8,"tasks":1},"file":"CISA BOD 25-01/assessment-plan.json","href":"examples/assessment-first/CISA%20BOD%2025-01/assessment-plan.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"Entra ID cATO Assessment Plan"},{"bytes":39652,"counts":{},"file":"CISA BOD 25-01/sample-ssp.json","href":"examples/assessment-first/CISA%20BOD%2025-01/sample-ssp.json","href_external":false,"model":"system-security-plan","model_label":"System security plan","title":"Sample ScubaGear System Security Plan"},{"bytes":423087,"counts":{"activities":72,"steps":144,"tasks":8},"file":"Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","href":"examples/assessment-first/Center%20for%20Internet%20Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CIS PostgreSQL 18 Benchmark"},{"bytes":1768114,"counts":{"activities":53,"steps":616,"tasks":7},"file":"Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","href":"examples/assessment-first/Center%20for%20Internet%20Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CIS Ubuntu Linux 24.04 LTS Benchmark"},{"bytes":821083,"counts":{"activities":118,"steps":236,"tasks":2},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/epas.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Postgres Advanced Server"},{"bytes":823183,"counts":{"activities":111,"steps":222,"tasks":2},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/postgres16.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Postgres 16"},{"bytes":2454926,"counts":{"activities":366,"steps":732,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel8.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/rhel8.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Red Hat Enterprise Linux 8"},{"bytes":3051725,"counts":{"activities":446,"steps":892,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel9.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/rhel9.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Red Hat Enterprise Linux 9"},{"bytes":1310065,"counts":{"activities":188,"steps":376,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu22.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/ubuntu22.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Ubuntu 22.04 LTS"},{"bytes":1341083,"counts":{"activities":194,"steps":388,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/ubuntu24.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Ubuntu 24.04 LTS"},{"bytes":1940344,"counts":{"activities":282,"steps":564,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2019.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2019"},{"bytes":1858865,"counts":{"activities":282,"steps":564,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2022.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2022"},{"bytes":1867817,"counts":{"activities":284,"steps":568,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2025.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2025.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2025"}],"full_name":"Option C","key":"assessment-first","name":"Assessment-first","option":"Option C","repo":null,"rollup":null,"root":"Easy Dynamics","totals":{"Assessment plan":15,"Assessment results":1,"System security plan":1}}]},"data/pattern-examples.json":{"benchmark_id":"CAN_Ubuntu_24-04_STIG","examples":{"1":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"steps\": [\n {\n \"uuid\": \"333ddd0f-22da-4c18-8bc3-98e808746bca\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"props","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"An activity. The requirement is the activity title, the work is in its steps, and the identifiers stay in the publisher's own namespace."},{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"steps\": [\n {\n \"uuid\": \"fd6c19bf-7c7f-4376-8dc0-674fd0421f64\",\n \"title\": \"Check: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270732r1066685_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"props","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"An activity. The requirement is the activity title, the work is in its steps, and the identifiers stay in the publisher's own namespace."}],"catalog-first":[{"content":"{\n \"catalog\": {\n \"groups\": [\n {\n \"id\": \"ubuntu-24-04\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"controls\": [\n {\n \"id\": \"UBTU-24-600090\",\n \"title\": \"Data at rest\",\n \"parts\": [\n {\n \"name\": \"statement\",\n \"prose\": \"Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"SV-270747r1066730_rule\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV-270747r1066730_rule\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[19,26]],"focus_key":"props","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A control. The requirement is the control's statement, the check is named in an assessment-method part, and a value, where there is one, is a control parameter."},{"content":"{\n \"catalog\": {\n \"groups\": [\n {\n \"id\": \"ubuntu-24-04\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"controls\": [\n {\n \"id\": \"UBTU-24-400320\",\n \"title\": \"Minimum password length\",\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"The required length is a parameter of the control, so tailoring it is a profile edit rather than a change to the requirement.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"SV-270732r1066685_rule\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV-270732r1066685_rule\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ],\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[23,30]],"focus_key":"props","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A control. The requirement is the control's statement, the check is named in an assessment-method part, and a value, where there is one, is a control parameter."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"5ca997b3-bb3e-4c7a-8969-69ed44577d47\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"description\": \"Ubuntu 24.04 LTS as a component of the system.\",\n \"rules\": [\n {\n \"id\": \"ubtu24_data_at_rest_encrypted\",\n \"description\": \"Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\"\n }\n ]\n }\n ]\n }\n}","focus":[[9,14]],"focus_key":"rules","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A rules entry on the component the rule applies to. The rule is first-class rather than a prop, and a value is a rule param set by the control implementation."},{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"da810545-1635-4323-8e22-a74ddbe2c31d\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"description\": \"Ubuntu 24.04 LTS as a component of the system.\",\n \"rules\": [\n {\n \"id\": \"ubtu24_password_min_length\",\n \"description\": \"Passwords must be at least {param: password_min_length} characters.\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[9,20]],"focus_key":"rules","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A rules entry on the component the rule applies to. The rule is first-class rather than a prop, and a value is a rule param set by the control implementation."}]},"2":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"reviewed-controls\": {\n \"control-selections\": [\n {\n \"description\": \"The controls this assessment may touch.\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n },\n {\n \"control-id\": \"ia-5.1\"\n }\n ]\n }\n ]\n },\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule, derived from its CCI references.\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n }\n ]\n }\n ]\n }\n },\n {\n \"uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule, derived from its CCI references.\",\n \"include-controls\": [\n {\n \"control-id\": \"ia-5.1\"\n }\n ]\n }\n ]\n }\n }\n ]\n }\n }\n}","focus":[[23,34],[39,50]],"focus_key":"related-controls","label":"Both rules and their control ties","rule":"both","shows":"Named on the activity itself. No second document and no second identifier, so nothing can fall out of step, and nothing else can reuse the tie."}],"catalog-first":[{"content":"{\n \"mapping-collection\": {\n \"uuid\": \"d958a01a-6d1a-46fc-8289-ab967af8b955\",\n \"metadata\": {\n \"title\": \"Ubuntu 24.04 LTS product catalog mapped to NIST SP 800-53 Revision 5\",\n \"last-modified\": \"2026-08-20T12:00:00Z\",\n \"version\": \"1.0.0\",\n \"oscal-version\": \"1.2.2\"\n },\n \"provenance\": {\n \"method\": \"human\",\n \"matching-rationale\": \"semantic\",\n \"status\": \"draft\",\n \"mapping-description\": \"Each hardening control is narrower than the framework control it supports, so every map below is a subset relationship.\"\n },\n \"mappings\": [\n {\n \"uuid\": \"f60ce697-4c9d-48e2-8136-f7d3bcb895d7\",\n \"source-resource\": {\n \"type\": \"catalog\",\n \"href\": \"#ubuntu-24-04-product-catalog\"\n },\n \"target-resource\": {\n \"type\": \"catalog\",\n \"href\": \"#nist-800-53-rev5\"\n },\n \"maps\": [\n {\n \"uuid\": \"74734a70-2c15-4634-8fe1-eb70dacc4b33\",\n \"relationship\": \"subset-of\",\n \"matching-rationale\": \"semantic\",\n \"sources\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"UBTU-24-600090\"\n }\n ],\n \"targets\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"sc-28\"\n }\n ]\n },\n {\n \"uuid\": \"da49a963-4911-47d7-837b-da3c516a4708\",\n \"relationship\": \"subset-of\",\n \"matching-rationale\": \"semantic\",\n \"sources\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"UBTU-24-400320\"\n }\n ],\n \"targets\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"ia-5.1\"\n }\n ]\n }\n ]\n }\n ],\n \"back-matter\": {\n \"resources\": [\n {\n \"uuid\": \"13c89eb4-c309-466f-8e39-83e272663a37\",\n \"title\": \"Ubuntu 24.04 LTS product catalog\",\n \"rlinks\": [\n {\n \"href\": \"./ubuntu-24-04-catalog.json\"\n }\n ]\n },\n {\n \"uuid\": \"6d874b7d-f632-43ee-8043-8f0d5bd5fbe2\",\n \"title\": \"NIST SP 800-53 Revision 5\",\n \"rlinks\": [\n {\n \"href\": \"./NIST_SP-800-53_rev5_catalog.json\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[27,62]],"focus_key":"maps","label":"Both rules and their control ties","rule":"both","shows":"A whole document of its own. Metadata and a four-field provenance block come before the first map, and both ends of a map must be a control or a statement."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"control-implementations\": [\n {\n \"uuid\": \"1cc70653-88aa-408e-80ce-fdf004c2e3e1\",\n \"source\": \"trestle://profiles/nist_800_53_rev5/profile.json\",\n \"description\": \"NIST SP 800-53 Revision 5\",\n \"set-parameters\": [\n {\n \"param-id\": \"password_min_length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"implemented-requirements\": [\n {\n \"uuid\": \"891fbbe5-51fa-4d63-8c75-36beb7b9c70b\",\n \"control-id\": \"sc-28\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n },\n {\n \"uuid\": \"53dc0fa3-7de4-4969-86d9-0dba5044e0b3\",\n \"control-id\": \"ia-5.1\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_password_min_length\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[21,40]],"focus_key":"implemented-requirements","label":"Both rules and their control ties","rule":"both","shows":"No second document, and two ties in one place. The implemented requirement ties the component to the control, which OSCAL already does; implementing-rules ties the rule to it, which it does not."}]},"3":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"333ddd0f-22da-4c18-8bc3-98e808746bca\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"Verify the block device carrying user data is encrypted. If it is not, this is a finding.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[14,27]],"focus_key":"steps","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"The steps are the check, and a check prop names it. Put that prop on the step and the plan can ask for one item; put it on the activity and one invocation covers every step beneath. The runner decides which."},{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"fd6c19bf-7c7f-4376-8dc0-674fd0421f64\",\n \"title\": \"Check: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"description\": \"Verify the configured minimum password length is 15 or greater. If it is not, this is a finding.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270732r1066685_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[14,27]],"focus_key":"steps","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"The steps are the check, and a check prop names it. Put that prop on the step and the plan can ask for one item; put it on the activity and one invocation covers every step beneath. The runner decides which."},{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"201588f5-0638-4c98-89d7-e4c215e62171\",\n \"title\": \"Assess Ubuntu 24.04 LTS\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"check\",\n \"value\": \"CAN_Ubuntu_24-04_STIG\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"410c472a-0935-48ee-8543-e39e02365bfd\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\"\n },\n {\n \"uuid\": \"cbcc6a87-99c5-4002-8990-cb54ee8a7377\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[13,17]],"focus_key":"name=check","label":"Multiple tests, with the check at the activity level","rule":"placement","shows":"The same two checks named on the activity instead, for a runner that executes in bulk. One invocation, every step beneath it."}],"catalog-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"272c65cb-9a6d-4344-8938-2e6203673884\",\n \"type\": \"software\",\n \"title\": \"SV-270747r1066730_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-600090.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270747R1066730_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"9133615a-9ffc-4656-8ca7-2b249482ee22\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"b971b7c8-6b4f-4188-8ceb-968a4aacb040\",\n \"control-id\": \"UBTU-24-600090\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[9,15]],"focus_key":"props","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"The check is a software component whose title is the identifier the control's assessment-method part named."},{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"65157847-efa3-4d97-8e62-f6148c556255\",\n \"type\": \"software\",\n \"title\": \"SV-270732r1066685_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-400320.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270732R1066685_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"2293c543-d5f7-45e3-8ef3-3917f9e5ccc1\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"3f57d132-ea15-4517-8398-778950a14382\",\n \"control-id\": \"UBTU-24-400320\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[9,15]],"focus_key":"props","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"The check is a software component whose title is the identifier the control's assessment-method part named."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted on the target host.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"5ca997b3-bb3e-4c7a-8969-69ed44577d47\"\n }\n ]\n }\n ]\n }\n}","focus":[[15,22]],"focus_key":"checks","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"Two components, not one. The rule sits on the product; the check sits on a second component of type validation, one per engine, and reaches back by rule id and the uuid of the component the rule belongs to."},{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"checks\": [\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length on the target host.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"da810545-1635-4323-8e22-a74ddbe2c31d\"\n }\n ]\n }\n ]\n }\n}","focus":[[15,22]],"focus_key":"checks","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"Two components, not one. The rule sits on the product; the check sits on a second component of type validation, one per engine, and reaches back by rule id and the uuid of the component the rule belongs to."}]},"4":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"assessment-subjects\": [\n {\n \"type\": \"inventory-item\",\n \"description\": \"The instances this assessment may touch.\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ],\n \"tasks\": [\n {\n \"uuid\": \"068cacee-b6b7-49c7-844e-e80c42f25fb7\",\n \"type\": \"action\",\n \"title\": \"Assess Ubuntu 24.04 LTS\",\n \"associated-activities\": [\n {\n \"activity-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[3,14]],"focus_key":"assessment-subjects","label":"What the checks run against","rule":"both","shows":"One host, named explicitly as an inventory item."}],"catalog-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"83fd01c4-5007-4281-84bc-2fa040f75e14\",\n \"control-id\": \"UBTU-24-600090\",\n \"by-components\": [\n {\n \"uuid\": \"013a942e-ff7e-466d-821e-c84498c1b9be\",\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"description\": \"The rule was implemented.\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[8,14]],"focus_key":"by-components","label":"What the checks run against","rule":"both","shows":"Every component the catalog applies to, taken together."}],"component-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"c1ea1b60-eab2-46d3-8134-89ac8affdc8a\",\n \"control-id\": \"UBTU-24-600090\",\n \"by-components\": [\n {\n \"uuid\": \"f473f847-a826-48e5-8d9f-53ae40333b88\",\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"description\": \"The rule was implemented.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[8,19]],"focus_key":"by-components","label":"What the checks run against","rule":"both","shows":"The components carrying the rules, named by uuid."},{"content":"{\n \"assessment-plan\": {\n \"assessment-assets\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Copied from the component definition the system owner used.\",\n \"status\": {\n \"state\": \"operational\"\n },\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n },\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[13,26]],"focus_key":"checks","label":"The same component, copied into the assessor's plan","rule":"assessor","shows":"The component definition carried into an assessment plan as an asset. The checks travel with the component that runs them, and each names the component it tests."}]},"5":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"steps\": [\n {\n \"uuid\": \"333ddd0f-22da-4c18-8bc3-98e808746bca\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n },\n \"assessment-assets\": {\n \"components\": [\n {\n \"uuid\": \"56270516-2673-4d4c-8d4f-52e4107f968d\",\n \"type\": \"validation\",\n \"title\": \"The check runner plugin\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"status\": {\n \"state\": \"operational\"\n },\n \"props\": [\n {\n \"name\": \"context\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"{\\\"plugin-path\\\": \\\"runner.plugin\\\", \\\"opa-path\\\": \\\"/usr/local/bin\\\"}\"\n }\n ]\n }\n ],\n \"assessment-platforms\": [\n {\n \"uuid\": \"97f00129-f4ab-424f-8cd0-5ad1fc54f667\",\n \"title\": \"The scanning platform\",\n \"uses-components\": [\n {\n \"component-uuid\": \"56270516-2673-4d4c-8d4f-52e4107f968d\"\n }\n ]\n }\n ]\n },\n \"tasks\": [\n {\n \"uuid\": \"fa3faf4f-3ac3-432c-8d2f-4401173822ea\",\n \"type\": \"action\",\n \"title\": \"Execute the checks\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"97f00129-f4ab-424f-8cd0-5ad1fc54f667\"\n }\n ],\n \"associated-activities\": [\n {\n \"activity-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-all\": {}\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[13,17]],"focus_key":"name=check","label":"What the run reads: the checks and the platform","rule":"assessor-in","shows":"The checks and what runs them, in one plan the assessor owns."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for UBTU-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\"\n }\n ]\n },\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for UBTU-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"title\": \"Observation: SV-270747r1066730_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n },\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"title\": \"Observation: SV-270732r1066685_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[11,11],[27,27],[52,52],[69,69]],"focus_key":"target-id, subject-uuid","label":"What the run produces: the observation","rule":"assessor-out","shows":"The observation names the activity that ran. No plan of record has to exist for it to resolve."}],"catalog-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"272c65cb-9a6d-4344-8938-2e6203673884\",\n \"type\": \"software\",\n \"title\": \"SV-270747r1066730_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-600090.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270747R1066730_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"9133615a-9ffc-4656-8ca7-2b249482ee22\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"b971b7c8-6b4f-4188-8ceb-968a4aacb040\",\n \"control-id\": \"UBTU-24-600090\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n },\n {\n \"uuid\": \"65157847-efa3-4d97-8e62-f6148c556255\",\n \"type\": \"software\",\n \"title\": \"SV-270732r1066685_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-400320.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270732R1066685_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"2293c543-d5f7-45e3-8ef3-3917f9e5ccc1\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"3f57d132-ea15-4517-8398-778950a14382\",\n \"control-id\": \"UBTU-24-400320\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[10,14],[37,41]],"focus_key":"name=ConfigRuleId","label":"What the run reads: the check components","rule":"implementor-in","shows":"The check components the run is handed. What runs them is never named."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"UBTU-24-600090\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-600090_smt\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\"\n }\n ]\n }\n ]\n },\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"UBTU-24-400320\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-400320_smt\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18],[29,35]],"focus_key":"by-components","label":"What the run produces: the response in the plan of record","rule":"implementor-out","shows":"A by-component saying the control is met. Nothing on it names the check that produced it."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted on the target host.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"5ca997b3-bb3e-4c7a-8969-69ed44577d47\"\n },\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length on the target host.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"da810545-1635-4323-8e22-a74ddbe2c31d\"\n }\n ]\n }\n ]\n }\n}","focus":[[15,28]],"focus_key":"checks","label":"What the run reads: the checks it is handed","rule":"implementor-in","shows":"The checks the run is handed, each naming its rule and its subject."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"sc-28\",\n \"statements\": [\n {\n \"statement-id\": \"sc-28_smt.a\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n }\n ]\n }\n ]\n },\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"ia-5.1\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_password_min_length\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[17,21],[39,43]],"focus_key":"implementing-rules","label":"What the run produces: the assertion in the plan of record","rule":"implementor-out","shows":"The response the run writes, carrying implementing-rules so the assertion and its check travel together."},{"content":"{\n \"assessment-plan\": {\n \"assessment-assets\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Copied from the component definition the system owner used.\",\n \"status\": {\n \"state\": \"operational\"\n },\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n },\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[13,26]],"focus_key":"checks","label":"What the run reads: the same checks, in the assessor's plan","rule":"assessor-in","shows":"The same definition, taken into a plan the assessor owns. The checks travel with it."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"description\": \"SV-270747r1066730_rule\",\n \"assessment-check-id\": \"SV-270747r1066730_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n },\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"description\": \"SV-270732r1066685_rule\",\n \"assessment-check-id\": \"SV-270732r1066685_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[9,9],[10,10],[25,25],[26,26]],"focus_key":"assessment-check-id, result","label":"What the run produces: the observation","rule":"assessor-out","shows":"The check identifier joins back to what ran, and the subject is a host rather than a component."}]},"6a":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"import-ssp\": {\n \"href\": \"#d381c885-4851-4931-828c-29bbb24fbaa3\"\n },\n \"back-matter\": {\n \"resources\": [\n {\n \"uuid\": \"d381c885-4851-4931-828c-29bbb24fbaa3\",\n \"title\": \"Ubuntu 24.04 LTS system security plan\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"oscal-ssp\"\n }\n ],\n \"rlinks\": [\n {\n \"href\": \"system-security-plan.json\",\n \"media-type\": \"application/oscal.ssp+json\"\n }\n ],\n \"remarks\": \"Use this to point to an OSCAL-based SSP.\"\n },\n {\n \"uuid\": \"8bb824b6-255b-434c-8f68-e639deb75f89\",\n \"title\": \"System's full name\",\n \"description\": \"Use this resource when no OSCAL-based SSP exists. Briefly describe the system. This appears in the assessment result.\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"no-oscal-ssp\"\n }\n ],\n \"remarks\": \"Only include this resource if no OSCAL-based SSP is available.\"\n }\n ]\n }\n }\n}","focus":[[3,5]],"focus_key":"import-ssp","label":"One pointer, covering both rules","rule":"both","shows":"Not the claim, but where it lives. import-ssp resolves to a back-matter resource naming the system security plan, and a second resource covers the case where no OSCAL one exists."}],"catalog-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"UBTU-24-600090\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-600090_smt\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"by-components","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A by-component response in the SSP, against the product control."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"UBTU-24-400320\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-400320_smt\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"by-components","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A by-component response in the SSP, against the product control."}],"component-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"sc-28\",\n \"statements\": [\n {\n \"statement-id\": \"sc-28_smt.a\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[17,21]],"focus_key":"implementing-rules","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"The same shape, against the framework control, and carrying implementing-rules so the claim names the rule it rests on."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"ia-5.1\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_password_min_length\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[17,21]],"focus_key":"implementing-rules","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"The same shape, against the framework control, and carrying implementing-rules so the claim names the rule it rests on."}]},"6b":{"assessment-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for UBTU-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"title\": \"Observation: SV-270747r1066730_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A finding, targeting the framework control's statement."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for UBTU-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"title\": \"Observation: SV-270732r1066685_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A finding, targeting the framework control's statement."}],"catalog-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for UBTU-24-600090\",\n \"target\": {\n \"type\": \"statement-id\",\n \"target-id\": \"UBTU-24-600090_smt\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"title\": \"Observation for UBTU-24-600090\",\n \"description\": \"The configuration rule was evaluated on the component.\",\n \"methods\": [\n \"TEST\"\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A finding, targeting the product control's statement."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for UBTU-24-400320\",\n \"target\": {\n \"type\": \"statement-id\",\n \"target-id\": \"UBTU-24-400320_smt\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"title\": \"Observation for UBTU-24-400320\",\n \"description\": \"The configuration rule was evaluated on the component.\",\n \"methods\": [\n \"TEST\"\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A finding, targeting the product control's statement."}],"component-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"description\": \"SV-270747r1066730_rule\",\n \"assessment-check-id\": \"SV-270747r1066730_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[10,10]],"focus_key":"result","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"An observation carrying the check id and its result."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"observations\": [\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"description\": \"SV-270732r1066685_rule\",\n \"assessment-check-id\": \"SV-270732r1066685_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[10,10]],"focus_key":"result","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"An observation carrying the check id and its result."}]}},"note":"Our own encodings. Two rules, written in all three shapes, so the only thing that changes between the columns is the modelling.","rules":[{"check_id":"SV-270747r1066730_rule","control":"sc-28","key":"data-at-rest","label":"Rule 1, data at rest","statement":"Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.","stig":{"category":"CAT II","group":"V-270747","id":"UBTU-24-600090","rule":"SV-270747r1066730_rule","severity":"medium"},"why_chosen":"A binary condition with no value to set. It is the simple case, and it is the one all three approaches already have an analogue for."},{"check_id":"SV-270732r1066685_rule","control":"ia-5.1","key":"password-min-length","label":"Rule 2, minimum password length","statement":"Ubuntu 24.04 LTS must enforce a minimum 15-character password length.","stig":{"category":"CAT II","group":"V-270732","id":"UBTU-24-400320","rule":"SV-270732r1066685_rule","severity":"medium"},"why_chosen":"The same shape as the first rule but carrying a value, so it is the rule that shows where each approach puts a parameter. Publishers disagree on the number, which is why the number has to live somewhere addressable."}],"target":{"title":"Ubuntu 24.04 LTS","why":"One target, so the only thing that changes between the three columns is the modelling. Ubuntu because both rules are published for it, by DISA, and a reader can check them."}},"data/provenance.json":{"generated_at":"2026-09-10T14:51:40+00:00","snippet_count":32,"snippets":[{"approach":"assessment-first","bytes":4370,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-activity-v259312","language":"json","pointer":"/assessment-plan/local-definitions/activities/100","sha256_of_content":"f2968c0009fd012a241dc8e3e86173ac47bb4475624d3ccd01d77efd53964e31","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG activity V-259312"},{"approach":"assessment-first","bytes":6648,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-sc28-v270747","language":"json","pointer":"/assessment-plan/local-definitions/activities/101","sha256_of_content":"f6505f9312ba86546b17001b14b7ad797cd83fb68699749488086edb5ac0e8f2","sha256_of_source_file":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","title":"STIG activity V-270747, SC-28"},{"approach":"assessment-first","bytes":1976,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-step-props","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0","sha256_of_content":"e369bbc630cc85afc2a07e99fca48e213cabd815f4bc02ef1ec15034d2b7c33a","sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS audit step props"},{"approach":"assessment-first","bytes":999,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-remediation-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/1","sha256_of_content":"953c73006718d3632307bf47755dc4924e6164f3c03a53e96a3f3d058a4883bd","sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS remediation step"},{"approach":"assessment-first","bytes":270,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","sha256_of_content":"c3298e80edbf681c6da3e2965d161f81804db9d940539e41f77a19cf21e544e0","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA activity context prop"},{"approach":"assessment-first","bytes":928,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","sha256_of_content":"60c8183fb14d09b5f27513b84f394bf8a48670eadaf2f73fd834bc7300011240","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-assets"},{"approach":"assessment-first","bytes":1828,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","sha256_of_content":"ec5873d16ce6100d9be8cce518945b3aee95c50d2ae1ace4e298b860f8433b8f","sha256_of_source_file":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653","slot":"3","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-maester.json","title":"CISA step context prop"},{"approach":"assessment-first","bytes":243,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-related-controls","language":"json","pointer":"/assessment-plan/local-definitions/activities/100/related-controls","sha256_of_content":"2f52e4b5053678f3323139865183d634ff1206753079feff31bcaff76f53c93e","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"2","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG related-controls, the control tie"},{"approach":"assessment-first","bytes":197,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-step-reviewed","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0/reviewed-controls","sha256_of_content":"52c2919dc4f34fd2fbc5907450582b436e7e929a031c2bdb5a9c83d4ae18b30d","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"2","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA step reviewed-controls"},{"approach":"assessment-first","bytes":127,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-subjects-includeall","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"60d2f0f2a596673779c7804e0c6ea2bcc0609b41d54dc4d3c698be49bf268a82","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"4","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG assessment-subjects, include-all"},{"approach":"assessment-first","bytes":277,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"01c9afa2b4ee716f8534f4a2f12777d7202d741c06a7d5182619ca8f3afbc3fe","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"4","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-subjects, one inventory item"},{"approach":"assessment-first","bytes":2946,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"e5939a58c062351efa21b423729e40beeb72d3e13dd32757af065e4709dfbd60","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA task, with timing"},{"approach":"assessment-first","bytes":27,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","sha256_of_content":"84d4c12b8a05a19b8f99d8305498e5760d8bb8dfe987a2ecf4c38abd43d7557b","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"meta","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG import-ssp, an unresolved placeholder"},{"approach":"assessment-first","bytes":94,"extracted_at":"2026-08-22T18:44:16+00:00","id":"ez-cisa-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","sha256_of_content":"b26671d77e040a71e3470a5a13e0f043d7b130bf7b7688629f6405f136b1b7d2","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"import-ssp, resolving to a resource in the same document"},{"approach":"assessment-first","bytes":357,"extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/1","sha256_of_content":"401a0f63ea6221c571902ef0ba27bd50cce9fe2baa09b0cf520e48fa20539f1d","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The resource a resolved import-ssp lands on"},{"approach":"assessment-first","bytes":686,"extracted_at":"2026-08-22T18:46:12+00:00","id":"ez-cisa-no-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/0","sha256_of_content":"e0431570c0eb7d51ecec3ca35a340ae8c920c4c6afc08bb6a36760af82ef1e18","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The alternative resource, where no OSCAL system security plan exists"},{"approach":"assessment-first","bytes":466,"extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ar-finding","language":"json","pointer":"/assessment-results/results/0/findings/0","sha256_of_content":"4e3cfedd3c68517765d05d2cd46cdc0124a29c593c889cba16035c8ab84c1fe0","sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"A finding, targeting an objective"},{"approach":"assessment-first","bytes":762,"extracted_at":"2026-08-22T18:43:41+00:00","id":"ez-cisa-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","sha256_of_content":"631850409afd117649f1abec4da6e649bab0d2d4226d2a28f77d9918ec506b3a","sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"The observation it rests on, and what was examined"},{"approach":"assessment-first","bytes":469,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-resolution-status","language":"json","pointer":"/assessment-plan/reviewed-controls/control-selections/0","sha256_of_content":"4befe7d29d300effc4bdd88c120c2c1f1c00497fc28990444f62c198bc111d04","sha256_of_source_file":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8","slot":"meta","source":"Easy Dynamics/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","title":"CIS resolution status"},{"approach":"catalog-first","bytes":1402,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm2-control","language":"json","pointer":"/catalog/groups/0/controls/1","sha256_of_content":"a7f2e132f5d8e27309dbec9c9b114ed87105ee326046773c5cfe05f5da5b1ab4","sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"ACM.2, the control"},{"approach":"catalog-first","bytes":1177,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-rsa-check-component","language":"json","pointer":"/component-definition/components/2","sha256_of_content":"c4df1c40cb50ca7dd6e7d18862853fef78189e789623abf1c177ea49c9d0b3a1","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"3","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"acm-certificate-rsa-check, the check component"},{"approach":"catalog-first","bytes":538,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-backmatter-source","language":"json","pointer":"/component-definition/back-matter","sha256_of_content":"5e916dfa3cdf4d22fbbf601a1f6b18bc69b0a65d9367e906c26ba11901ab03cd","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"Back-matter, source to the catalog"},{"approach":"catalog-first","bytes":1444,"extracted_at":"2026-08-21T03:10:41+00:00","id":"aws-control-cloudtrail2","language":"json","pointer":"/catalog/groups/15/controls/2","sha256_of_content":"ae48dd920cb756ba4afaec14989d62d63c1954361757346114e807768609940b","sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"CloudTrail.2, the control"},{"approach":"catalog-first","bytes":1439,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-input-parameter","language":"json","pointer":"/component-definition/components/2/props","sha256_of_content":"b8d9cec13e53ca016cfe380b637fec8adfe353e9098e37d90bd28cacf98dcee1","sha256_of_source_file":"940cab9d3328d5ff55e6c69fbfae6fd4e846873d07f70ef7c096651bc8f750ab","slot":"1","source":"AWS/oscal-content-for-aws-services-main/component-definitions/iam.oscal.json","title":"InputParameter props, the parameter mechanism"},{"approach":"catalog-first","bytes":493,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-service-rollup","language":"json","pointer":"/component-definition/components/0/control-implementations/0","sha256_of_content":"dd53d5bd8e01cbaa2b198cf7504ece6374b931ec86c373ae5c9003e34d75dd44","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"AWS Certificate Manager, the service roll-up"},{"approach":"catalog-first","bytes":1367,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-config-service-bare","language":"json","pointer":"/component-definition/components/0","sha256_of_content":"3b3b0c533e8fe9ebc892b5cdf0003bb265591ae3486e5d6317aa847480d88541","sha256_of_source_file":"d5049e46d7a1251932be3e74c1f9bace606ac9b5f5542249ccb884171394a6e7","slot":"5","source":"AWS/oscal-content-for-aws-services-main/component-definitions/config.oscal.json","title":"AWS Config, the engine that runs the checks"},{"approach":"component-first","bytes":1909,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-cos-component","language":"json","pointer":"/component-definition/components/0","sha256_of_content":"63bda68a0ec328946a2ba363442053d4976a7ea78ccc27da761f4dbfc9feae4b","sha256_of_source_file":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a","slot":"1","source":"IBM/cos-component-definition.json","title":"COS component, carrying rules"},{"approach":"component-first","bytes":686,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-statement-rules","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/0","sha256_of_content":"d835c9264269a53f2fbbb988dfe83509b7610a445742300ace8703259dbb3edd","sha256_of_source_file":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf","slot":"2","source":"IBM/idservice-component-definition.json","title":"implementing-rules on ia-5.1"},{"approach":"component-first","bytes":1106,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-validation-ansible","language":"json","pointer":"$","sha256_of_content":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","sha256_of_source_file":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","slot":"3","source":"IBM/ansible-validation-component-definition.json","title":"Ansible validation component, and its checks"},{"approach":"component-first","bytes":624,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-activity","language":"json","pointer":"/assessment-plan/local-defintions","sha256_of_content":"b0157c12fb61e61809b3970895e3d1e9bba4b8c8bfe31c7f20e01ac292c1b252","sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"5","source":"IBM/assessment-plan.json","title":"AP activity, binding check-ids"},{"approach":"component-first","bytes":907,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-task-subjects","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"9852eeea94dab48f8ee5f7351c3ecc86a42be3e2dfd594626cae759ba163e9cd","sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"4","source":"IBM/assessment-plan.json","title":"AP task, subjects and platform"},{"approach":"component-first","bytes":1125,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","sha256_of_content":"eb0d665abc0dc6c1d6528291f5888816e6db04a427d7aaa6bd52bc395d1f9595","sha256_of_source_file":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806","slot":"6b","source":"IBM/assessment-result.json","title":"AR observation, carrying a result"}],"source_inputs":{"sources":[{"approach":"component-first","directory":"examples/component-first","expected_files":6,"key":"ibm","prefix":"IBM"},{"approach":"assessment-first","directory":"examples/assessment-first","expected_files":19,"key":"easy-dynamics","prefix":"Easy Dynamics"},{"approach":"catalog-first","archive_bytes":379596,"archive_sha256":"f309b59344560b88a699c5908fbc70c51c7a0e8e0339d901b1285b9c8d804a18","directory":".cache/oscal-sources/aws/4a1779ffb556c4ab8fb3dad94a19d4d198116803","file_base":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/","json_files":231,"key":"aws","prefix":"AWS/oscal-content-for-aws-services-main","repository":"awslabs/oscal-content-for-aws-services","revision":"4a1779ffb556c4ab8fb3dad94a19d4d198116803","url":"https://codeload.github.com/awslabs/oscal-content-for-aws-services/tar.gz/4a1779ffb556c4ab8fb3dad94a19d4d198116803"}],"version":1},"source_lock":"tools/source-lock.json"},"data/questions.json":{"intro":"These questions identify unresolved design choices, not recommended changes. The analysis distinguishes what the OSCAL examples demonstrate from what remains open across models and approaches.","note":"Editorial analysis questions maintained in this repository, grouped by issues shared across OSCAL and issues specific to each approach. Each question includes its reasoning; the OSCAL examples provide evidence without settling the design choices.","sections":[{"intro":"Gaps in the models themselves. None is answered by choosing an approach, and each changes what all three can express.","key":"all","label":"Across all three approaches","questions":[{"id":"xccdf","q":"Should OSCAL carry this content at all, when XCCDF already does?","why":"XCCDF already represents benchmark checklists. OSCAL could carry equivalent content or connect checklist references to implementation and assessment records. These choices produce different artifacts, translation work and maintenance obligations. The OSCAL examples do not establish which boundary best supports interoperable hardening workflows."},{"id":"rule-metadata","q":"Where does the metadata that describes a rule go?","why":"Rule metadata includes severity, weight, rationale and whether a check is automated or manual. The AWS and DISA OSCAL examples use namespaced properties for severity rather than a dedicated field. Consumers need shared conventions to interpret this content. Which metadata belongs on a rule, and whether shared namespaces or schema fields should carry it, remains open."},{"id":"remediation","q":"Where does remediation land?","why":"The AWS catalog uses remediation links, while the STIG and CIS assessment plans carry remediation steps. The component-first examples do not carry remediation. These conventions do not provide a dedicated rule-remediation field. OSCAL's plan of action and milestones addresses a particular finding, not a reusable fix for every instance of a condition. Which structure should carry reusable remediation instructions remains open."}]},{"intro":"The rule is a control in a catalog. What is unsettled is how many documents that produces and where the outcome lands.","key":"catalog-first","label":"Catalog-first","questions":[{"id":"one-ssp","q":"Do many catalogs converge into one profile and one plan of record, or does each catalog need its own?","why":"A single plan of record could answer a profile merging the catalogs that apply to a system. Separate plans could instead answer each catalog. These structures produce different file counts and response locations, and change whether benchmark outcomes sit beside regulatory outcomes. The worked scenario assumes convergence and counts 18 files; the question is whether that structure meets implementation and assessment needs."},{"id":"requirement-level","q":"If OSCAL gained a field for requirement level, how much of this disagreement would be left?","why":"OSCAL has no dedicated core field distinguishing shall, should and may. The examples can carry such labels in properties, but consumers need conventions to interpret them. Catalog-first puts benchmark and regulatory controls into the same profile. It remains unclear how much model-placement disagreement concerns binding force rather than document structure, and whether a shared requirement-level field would reduce it."},{"id":"control-type","q":"Should a control declare its type, so a regulatory control and a technical hardening control can be told apart?","why":"The catalog/profile model can combine regulatory controls with technical hardening controls, but it has no dedicated core field distinguishing those kinds. Tools would need a shared property convention or schema support to report regulatory coverage separately from hardening coverage. This question concerns the kind of requirement, distinct from whether its requirement level is shall, should or may."},{"id":"paper-cat-1","q":"How should benchmark profiles compose with regulatory profiles as the number of controls grows?","why":"Combining benchmark and regulatory controls increases the work of resolving imports, selections, exclusions and parameter values. The question is how tools should compose and maintain those profiles at scale without obscuring which source supplied a requirement or how a tailoring decision changes downstream content."},{"id":"paper-cat-2","q":"Where should benchmark outcomes be recorded, in SSP implementation claims or assessment results, and how should tools distinguish them?","why":"An SSP by-component response describes an implementation claim, while assessment results record evidence and outcomes. A benchmark workflow may need both, but they answer different questions. Tools need to distinguish intended configuration from observed satisfaction and preserve the relationship between the two records."}]},{"intro":"The rule sits on the component it configures. Open questions concern runner identification, importing component definitions and tailoring benchmark content.","key":"component-first","label":"Component-first","questions":[{"id":"which-cdef-maps","q":"Which component definition carries the tie to the framework, the one holding the rules or the one holding the checks?","why":"The control link is inline rather than held in a mapping collection. The software component definition holds rules, while the validation component definition holds checks; those artifacts may have different maintainers. A mapping provider could update either or both. The OSCAL examples do not establish which document should own that relationship or how duplicated mappings would stay consistent."},{"id":"proposal-1","q":"Should assessment platform usage be optional in an assessment plan?","why":"An assessment plan may describe a runner as a component, a platform using components, or a tool identified through properties. These alternatives leave open when an explicit assessment platform adds necessary information and when a component reference is sufficient for a consumer to execute or interpret a check."},{"id":"proposal-2","q":"When is an assessment component sufficient, and when is an assessment platform also needed?","why":"The OSCAL examples use different combinations of assessment-assets, assessment-platforms and components. They do not establish a shared rule for deciding whether a component alone identifies the runner or a platform must also describe its execution context. A consistent distinction would help consumers interpret equivalent workflows."},{"id":"proposal-3","q":"How should an assessment asset be associated with tasks or activities?","why":"A task identifies work to perform, while an assessment asset describes resources available to perform it. The component-first examples do not establish a complete, interoperable association between these structures. The question is which references should identify the runner for a particular task or activity."},{"id":"proposal-4","q":"How should an observation identify the assessment asset that produced it when several assets are declared?","why":"An assessment result may declare several assets, so naming an observation's producer requires an unambiguous relationship. The component-first result example does not establish a complete path from observation to producing asset. The open question is how consumers should recover that association without relying on tool-specific assumptions."},{"id":"paper-comp-1","q":"How should an SSP combine benchmark and vendor component definitions that describe the same system component?","why":"A system may use vendor component definitions alongside benchmark component definitions for the same software. Importing both can produce overlapping descriptions, rules and control implementations. It remains open whether an SSP should retain multiple OSCAL components, merge them, or use another convention to represent the single system component consistently."},{"id":"paper-comp-2","q":"Should desired-state values from benchmark component definitions be replaced with actual-state values in the SSP?","why":"Rules describe prescribed configuration, while an SSP records the system owner's implementation claims. Replacing prescribed values with actual values could lose the benchmark baseline; retaining only prescribed values could misrepresent implementation. The question is how to keep the two meanings distinct while preserving the relationship between benchmark requirements and the system."},{"id":"paper-comp-3","q":"Which benchmark context should enter an SSP, and how should tools filter component-definition content during import?","why":"Benchmark content can include rules, parameters, rationale and procedural detail, not all of which serves the same purpose in an SSP. Import tooling needs a policy for retaining or omitting that context. The open issue is how to reduce duplication without losing information needed to interpret an implementation claim."},{"id":"paper-comp-4","q":"How should component definitions support benchmark selection, exclusions and parameter tailoring?","why":"The component-first examples place parameters on proposed rules and set-parameters on control implementations. Those structures address parameter values but do not provide a profile's selection and exclusion workflow. How component definitions should support benchmark tailoring, including the scope and persistence of tailoring decisions, remains open."},{"id":"paper-comp-5","q":"Should assessment plans or assessment results support importing component definitions with benchmark context?","why":"The component-first examples carry check content into an assessment plan through assessment assets. That demonstrates one encoding, not a dedicated import mechanism for all benchmark context. The question is whether plans or results should support such imports directly and which rules, parameters and provenance would need to survive."}]},{"intro":"The rule is an activity in an assessment plan. The open question concerns tailoring requirements without losing their assessment context.","key":"assessment-first","label":"Assessment-first","questions":[{"id":"paper-ap-1","q":"How should assessment-plan benchmarks support tailoring available through catalogs and profiles?","why":"Activities and steps have no parameter assembly, so the assessment-first examples place required values in text. Tailoring can therefore require editing procedural content rather than selecting controls or setting parameter values through a profile. The question is how to support reusable, auditable tailoring without losing the assessment workflow."}]}]},"data/scenario-evidence/nist-high-baseline.json":{"counts":{"base":188,"controls":370,"enhancements":182,"families":18},"fetched_at":"2026-08-23","note":"The control identifiers selected by the NIST SP 800-53 Revision 5 HIGH baseline profile. Stored so the scenario's control count can be recomputed here rather than quoted from memory.","oscal_version":"1.2.2","pointer":"/profile/imports/0/include-controls/0/with-ids","profile_last_modified":"2026-05-11","profile_version":"5.2.0","source":"https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_HIGH-baseline_profile.json","title":"Electronic (OSCAL) Version of NIST Special Publication 800-53 Revision 5.1.1 HIGH IMPACT BASELINE","with_ids":["ac-1","ac-2","ac-2.1","ac-2.2","ac-2.3","ac-2.4","ac-2.5","ac-2.11","ac-2.12","ac-2.13","ac-3","ac-4","ac-4.4","ac-5","ac-6","ac-6.1","ac-6.2","ac-6.3","ac-6.5","ac-6.7","ac-6.9","ac-6.10","ac-7","ac-8","ac-10","ac-11","ac-11.1","ac-12","ac-14","ac-17","ac-17.1","ac-17.2","ac-17.3","ac-17.4","ac-18","ac-18.1","ac-18.3","ac-18.4","ac-18.5","ac-19","ac-19.5","ac-20","ac-20.1","ac-20.2","ac-21","ac-22","at-1","at-2","at-2.2","at-2.3","at-3","at-4","au-1","au-2","au-3","au-3.1","au-4","au-5","au-5.1","au-5.2","au-6","au-6.1","au-6.3","au-6.5","au-6.6","au-7","au-7.1","au-8","au-9","au-9.2","au-9.3","au-9.4","au-10","au-11","au-12","au-12.1","au-12.3","ca-1","ca-2","ca-2.1","ca-2.2","ca-3","ca-3.6","ca-5","ca-6","ca-7","ca-7.1","ca-7.4","ca-8","ca-8.1","ca-9","cm-1","cm-2","cm-2.2","cm-2.3","cm-2.7","cm-3","cm-3.1","cm-3.2","cm-3.4","cm-3.6","cm-4","cm-4.1","cm-4.2","cm-5","cm-5.1","cm-6","cm-6.1","cm-6.2","cm-7","cm-7.1","cm-7.2","cm-7.5","cm-8","cm-8.1","cm-8.2","cm-8.3","cm-8.4","cm-9","cm-10","cm-11","cm-12","cm-12.1","cp-1","cp-2","cp-2.1","cp-2.2","cp-2.3","cp-2.5","cp-2.8","cp-3","cp-3.1","cp-4","cp-4.1","cp-4.2","cp-6","cp-6.1","cp-6.2","cp-6.3","cp-7","cp-7.1","cp-7.2","cp-7.3","cp-7.4","cp-8","cp-8.1","cp-8.2","cp-8.3","cp-8.4","cp-9","cp-9.1","cp-9.2","cp-9.3","cp-9.5","cp-9.8","cp-10","cp-10.2","cp-10.4","ia-1","ia-2","ia-2.1","ia-2.2","ia-2.5","ia-2.8","ia-2.12","ia-3","ia-4","ia-4.4","ia-5","ia-5.1","ia-5.2","ia-5.6","ia-6","ia-7","ia-8","ia-8.1","ia-8.2","ia-8.4","ia-11","ia-12","ia-12.2","ia-12.3","ia-12.4","ia-12.5","ir-1","ir-2","ir-2.1","ir-2.2","ir-3","ir-3.2","ir-4","ir-4.1","ir-4.4","ir-4.11","ir-5","ir-5.1","ir-6","ir-6.1","ir-6.3","ir-7","ir-7.1","ir-8","ma-1","ma-2","ma-2.2","ma-3","ma-3.1","ma-3.2","ma-3.3","ma-4","ma-4.3","ma-5","ma-5.1","ma-6","mp-1","mp-2","mp-3","mp-4","mp-5","mp-6","mp-6.1","mp-6.2","mp-6.3","mp-7","pe-1","pe-2","pe-3","pe-3.1","pe-4","pe-5","pe-6","pe-6.1","pe-6.4","pe-8","pe-8.1","pe-9","pe-10","pe-11","pe-11.1","pe-12","pe-13","pe-13.1","pe-13.2","pe-14","pe-15","pe-15.1","pe-16","pe-17","pe-18","pl-1","pl-2","pl-4","pl-4.1","pl-8","pl-10","pl-11","ps-1","ps-2","ps-3","ps-4","ps-4.2","ps-5","ps-6","ps-7","ps-8","ps-9","ra-1","ra-2","ra-3","ra-3.1","ra-5","ra-5.2","ra-5.4","ra-5.5","ra-5.11","ra-7","ra-9","sa-1","sa-2","sa-3","sa-4","sa-4.1","sa-4.2","sa-4.5","sa-4.9","sa-4.10","sa-5","sa-8","sa-9","sa-9.2","sa-10","sa-11","sa-15","sa-15.3","sa-16","sa-17","sa-21","sa-22","sc-1","sc-2","sc-3","sc-4","sc-5","sc-7","sc-7.3","sc-7.4","sc-7.5","sc-7.7","sc-7.8","sc-7.18","sc-7.21","sc-8","sc-8.1","sc-10","sc-12","sc-12.1","sc-13","sc-15","sc-17","sc-18","sc-20","sc-21","sc-22","sc-23","sc-24","sc-28","sc-28.1","sc-39","si-1","si-2","si-2.2","si-3","si-4","si-4.2","si-4.4","si-4.5","si-4.10","si-4.12","si-4.14","si-4.20","si-4.22","si-5","si-5.1","si-6","si-7","si-7.1","si-7.2","si-7.5","si-7.7","si-7.15","si-8","si-8.2","si-10","si-11","si-12","si-16","sr-1","sr-2","sr-2.1","sr-3","sr-5","sr-6","sr-8","sr-9","sr-9.1","sr-10","sr-11","sr-11.1","sr-11.2","sr-12"]},"data/scenario.json":{"approaches":{"assessment-first":{"files":[{"count":1,"detail":"800-53 Revision 5","items":[{"name":"NIST 800-53"}],"model":"catalog","what":"the framework only"},{"count":1,"detail":"","items":[{"name":"800-53 High"}],"model":"profile","what":"the High baseline"},{"count":0,"detail":"activities identify related controls; reviewed-controls defines the assessment plan's control scope","model":"mapping-collection","what":"none, framework mappings are on activities"},{"count":0,"detail":"assessment-assets contains the components running checks; separate component definition documents are not needed","model":"component-definition","what":"none, engines are identified in each plan"},{"count":1,"detail":"assessment plans reference the system security plan without adding guidance to the implementation claims","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 370 controls"},{"count":4,"detail":"the three guides contain 547 requirements as activities and steps; each assessment plan references one system security plan through import-ssp","items":[{"name":"800-53 AP"},{"name":"CIS Ubuntu AP"},{"name":"DISA PgSQL AP"},{"name":"CISA SCuBA AP"}],"model":"assessment-plan","what":"one for the framework assessment, one per guide"},{"count":4,"detail":"four results documents, not four sections in one document; import-ap is a single required object referencing exactly one assessment plan","items":[{"name":"800-53 AR"},{"name":"CIS Ubuntu AR"},{"name":"DISA PgSQL AR"},{"name":"CISA SCuBA AR"}],"model":"assessment-results","what":"one per plan; each result references exactly one plan"}],"plan_of_record":"The system security plan addresses 370 controls; all three guides remain in assessment plans","rule":"Each guide becomes an assessment plan with a separate assessment results document. The framework catalog and baseline profile remain unchanged."},"catalog-first":{"files":[{"count":4,"detail":"800-53 Revision 5, CIS Ubuntu, DISA PostgreSQL, CISA SCuBA","items":[{"name":"NIST 800-53"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"}],"model":"catalog","what":"one for the framework, one for each guide"},{"count":5,"detail":"the High baseline, three guide selections and an organisational profile merging all four selections; import-profile is a single required object in the system security plan","items":[{"name":"800-53 High"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"},{"name":"Org merged"}],"model":"profile","what":"one selection per catalog and one merged selection"},{"count":3,"detail":"without mappings, guidance controls and framework controls remain two unrelated sets in the system security plan","items":[{"name":"CIS to 800-53"},{"name":"STIG to 800-53"},{"name":"SCuBA to 800-53"}],"model":"mapping-collection","what":"one per guide, linking guidance controls to framework controls"},{"count":3,"detail":"the control references a check identifier; a software component with a matching name describes the check's execution","items":[{"kind":"software","name":"Ubuntu checks"},{"kind":"software","name":"PgSQL checks"},{"kind":"software","name":"M365 checks"}],"model":"component-definition","what":"one per technology, containing check components"},{"count":1,"detail":"370 framework controls and 547 guidance controls, each requiring a by-component response; one import-profile references the merged profile because the field is a single required object","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 917 controls"},{"count":1,"detail":"","items":[{"name":"System AP"}],"model":"assessment-plan","what":"one"},{"count":1,"detail":"","items":[{"name":"System AR"}],"model":"assessment-results","what":"one"}],"plan_of_record":"The system security plan addresses 917 controls: 370 from the framework and 547 from the guides","rule":"Each guide becomes a catalog with a selection profile and a mapping collection linking guidance to the framework. The system security plan addresses every control in the merged set."},"component-first":{"files":[{"count":1,"detail":"800-53 Revision 5","items":[{"name":"NIST 800-53"}],"model":"catalog","what":"the framework only"},{"count":1,"detail":"","items":[{"name":"800-53 High"}],"model":"profile","what":"the High baseline"},{"count":0,"detail":"control implementations identify the controls served by the rules; no separate document carries the mapping","model":"mapping-collection","what":"none, framework mappings are inside component definitions"},{"count":6,"detail":"Ubuntu, PostgreSQL and Microsoft 365, with one validation component definition per checking engine","items":[{"kind":"software","name":"Ubuntu"},{"kind":"software","name":"PostgreSQL"},{"kind":"software","name":"Microsoft 365"},{"kind":"validation","name":"Ubuntu checks"},{"kind":"validation","name":"PgSQL checks"},{"kind":"validation","name":"M365 checks"}],"model":"component-definition","what":"three products with 547 rules, three engines with checks"},{"count":1,"detail":"the control count remains unchanged; rules are included in system-implementation","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 370 controls and containing 547 rules"},{"count":1,"detail":"","items":[{"name":"System AP"}],"model":"assessment-plan","what":"one"},{"count":1,"detail":"","items":[{"name":"System AR"}],"model":"assessment-results","what":"one"}],"plan_of_record":"The system security plan addresses 370 controls and contains 547 desired-state rules in components","rule":"Each guide becomes rules on the component being configured. Each checking engine becomes a separate validation component. The framework catalog and baseline profile remain unchanged."}},"excluded_model":{"model":"plan-of-action-and-milestones","reason":"The plan of action and milestones records unmet requirements and remediation. The document serves the same purpose in all three approaches and is excluded from the comparison."},"framework":{"base":188,"controls":370,"derivation":"count of /profile/imports/0/include-controls/0/with-ids in the published HIGH baseline profile, version 5.2.0","enhancements":182,"families":18,"label":"NIST SP 800-53 Revision 5, High baseline","source":"data/scenario-evidence/nist-high-baseline.json"},"hardening":[{"count_rule":"audit-steps","derivation":"count of steps titled 'Audit for ...' in Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json. The file carries 616 steps, one audit and one remediation for each recommendation, in 53 activities.","grouping":53,"grouping_label":"sections","key":"cis-ubuntu","label":"CIS Ubuntu 24.04 LTS Benchmark","requirements":308,"source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","technology":"Ubuntu"},{"count_rule":"step-type-check","derivation":"count of props step-type=check in Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json. The file carries 111 activities and 222 steps, one check and one remediate for each.","grouping":111,"grouping_label":"activities, one per requirement","key":"disa-postgres","label":"DISA STIG PostgreSQL 16","requirements":111,"source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","technology":"PostgreSQL"},{"count_rule":"steps","derivation":"count of steps in Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json, which carries 128 steps across 7 activities, one activity per Microsoft 365 service.","grouping":7,"grouping_label":"services","key":"cisa-bod-25-01","label":"CISA BOD 25-01 SCuBA","requirements":128,"source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","technology":"Microsoft 365"}],"items_note":"Each entry represents one file, with a name shortened for the diagram tile. Component-first distinguishes the product component, of type software, from the checking component, of type validation. File counts alone do not show component types.","models":["catalog","profile","mapping-collection","component-definition","system-security-plan","assessment-plan","assessment-results"],"note":"One system, one baseline and three hardening guides, modelled with each approach. The scenario compares document counts and system security plan content, not overall capability. Counts derive from the corpus, the NIST profile in data/scenario-evidence/, or OSCAL schema constraints. Each file row records the applicable constraint.","summary":"A system follows the NIST SP 800-53 Revision 5 High baseline and hardening guides for Ubuntu, PostgreSQL and Microsoft 365. The three approaches model the same requirements, using every OSCAL model except the plan of action and milestones.","title":"One system, three hardening guides"},"data/schema-evidence/assessment-subject.json":{"constraints":["anyOf requires include-all or include-subjects","each selection branch has optional type with anyOf enum [\"component\",\"inventory-item\",\"location\",\"party\",\"user\"]"],"definition":"oscal-ap-oscal-assessment-common:assessment-subject","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ap-oscal-assessment-common:assessment-subject","anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description"},"exclude-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ap-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["component","inventory-item","location","party","user"]}],"description":"Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.","title":"Subject Type"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description"},"exclude-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"include-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["component","inventory-item","location","party","user"]}],"description":"Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.","title":"Subject Type"}},"required":["include-subjects"]}],"description":"Identifies system elements being assessed, such as components, inventory items, and locations. In the assessment plan, this identifies a planned assessment subject. In the assessment results this is an actual assessment subject, and reflects any changes from the plan. exactly what will be the focus of this assessment. Any subjects not identified in this way are out-of-scope.","title":"Subject of Assessment","type":"object"},"model":"assessment-plan","note":"OSCAL 1.2.1 assessment subjects select all subjects or an explicit set. The optional type vocabulary includes component, inventory-item, location, party and user, supporting assessment of individual hosts.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_assessment-plan_schema.json at definitions/oscal-ap-oscal-assessment-common:assessment-subject.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ap-schema.json"},"data/schema-evidence/by-component.json":{"constraints":["required == [\"component-uuid\",\"uuid\",\"description\"]","has property \"component-uuid\"","has no property \"subject\", \"subject-uuid\", \"inventory-item-uuid\" or \"type\""],"definition":"oscal-ssp-oscal-ssp:by-component","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ssp-oscal-ssp:by-component","additionalProperties":false,"description":"Defines how the referenced component implements a set of controls.","properties":{"component-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to the component that is implementing a given control.","title":"Component Universally Unique Identifier Reference"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes how a control or a control statement is implemented within the referenced system component.","title":"Control Implementation Description"},"export":{"additionalProperties":false,"description":"Identifies content intended for external consumption, such as with leveraged organizations.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that can be available to another system leveraging this system.","title":"Control Implementation Export Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided":{"items":{"additionalProperties":false,"description":"Describes a capability which may be inherited by a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that can be provided to another system leveraging this system.","title":"Provided Control Implementation Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Provided Universally Unique Identifier"}},"required":["uuid","description"],"title":"Provided Control Implementation","type":"object"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsibilities":{"items":{"additionalProperties":false,"description":"Describes a control implementation responsibility imposed on a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that a leveraging system must implement to satisfy the control provided by a leveraged system.","title":"Control Implementation Responsibility Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.","title":"Provided UUID"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Responsibility Universally Unique Identifier"}},"required":["uuid","description"],"title":"Control Implementation Responsibility","type":"object"},"minItems":1,"type":"array"}},"title":"Export","type":"object"},"implementation-status":{"$ref":"#/definitions/oscal-ssp-oscal-implementation-common:implementation-status"},"inherited":{"items":{"additionalProperties":false,"description":"Describes a control implementation inherited by a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is inheriting from a leveraged system.","title":"Inherited Control Implementation Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.","title":"Provided UUID"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Inherited Universally Unique Identifier"}},"required":["uuid","description"],"title":"Inherited Control Implementation","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"satisfied":{"items":{"additionalProperties":false,"description":"Describes how this system satisfies a responsibility imposed by a leveraged system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is implementing based on a requirement from a leveraged system.","title":"Satisfied Control Implementation Responsibility Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsibility-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system.","title":"Responsibility UUID"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Satisfied Universally Unique Identifier"}},"required":["uuid","description"],"title":"Satisfied Control Implementation Responsibility","type":"object"},"minItems":1,"type":"array"},"set-parameters":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-implementation-common:set-parameter"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"By-Component Universally Unique Identifier"}},"required":["component-uuid","uuid","description"],"title":"Component Control Implementation","type":"object"},"model":"system-security-plan","note":"The oscal-ssp-oscal-ssp:by-component definition, which is the only way a system security plan responds to a control. It is keyed by component-uuid and has no subject of any kind: no inventory-item, no location, no party, no user. A plan can describe inventory items elsewhere, in system-implementation, but a control response cannot be made against one, so two hosts of the same component share a single response.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_ssp_schema.json at definitions/oscal-ssp-oscal-ssp:by-component.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ssp-schema.json"},"data/schema-evidence/finding-target.json":{"constraints":["required == [\"type\",\"target-id\",\"status\"]","type is constrained by allOf to enum [\"statement-id\",\"objective-id\"]","status.required includes \"state\"","status.state enum == [\"satisfied\",\"not-satisfied\"]"],"definition":"oscal-ar-oscal-assessment-common:finding-target","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:finding-target","additionalProperties":false,"description":"Captures an assessor's conclusions regarding the degree to which an objective is satisfied.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the assessor's conclusions regarding the degree to which an objective is satisfied.","title":"Objective Status Description"},"implementation-status":{"$ref":"#/definitions/oscal-ar-oscal-implementation-common:implementation-status"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"status":{"additionalProperties":false,"description":"A determination of if the objective is satisfied or not within a given system.","properties":{"reason":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["pass","fail","other"]}],"description":"The reason the objective was given it's status.","title":"Objective Status Reason"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"state":{"allOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["satisfied","not-satisfied"]}],"description":"An indication as to whether the objective is satisfied or not.","title":"Objective Status State"}},"required":["state"],"title":"Objective Status","type":"object"},"target-id":{"$ref":"#/definitions/TokenDatatype","description":"A machine-oriented identifier reference for a specific target qualified by the type.","title":"Finding Target Identifier Reference"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this objective status.","title":"Objective Status Title"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["statement-id","objective-id"]}],"description":"Identifies the type of the target.","title":"Finding Target Type"}},"required":["type","target-id","status"],"title":"Objective Status","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:finding-target definition from the OSCAL 1.2.1 assessment-results model, demonstrating that a finding target requires type, target-id, and status, restricts type by allOf to the closed enumeration statement-id or objective-id, and requires a status.state drawn from the closed enumeration satisfied or not-satisfied.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/finding.json":{"constraints":["required includes \"target\""],"definition":"oscal-ar-oscal-assessment-common:finding","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:finding","additionalProperties":false,"description":"Describes an individual finding.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this finding.","title":"Finding Description"},"implementation-statement-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related.","title":"Implementation Statement UUID"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"origins":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:origin"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"related-observations":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:related-observation"},"minItems":1,"type":"array"},"related-risks":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:associated-risk"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"target":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:finding-target"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this finding.","title":"Finding Title"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Finding Universally Unique Identifier"}},"required":["uuid","title","description","target"],"title":"Finding","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:finding definition from the OSCAL 1.2.1 assessment-results model, demonstrating that every finding must carry a target.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/mapping-item.json":{"constraints":["required == [\"type\",\"id-ref\"]","type is constrained by allOf to enum [\"control\",\"statement\"]","no property named 'uuid'","no property named 'href'"],"definition":"oscal-mapping-oscal-mapping-common:mapping-item","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-mapping-oscal-mapping-common:mapping-item","additionalProperties":false,"description":"A specific edge within a source or target that is the subject of a mapping.","properties":{"id-ref":{"$ref":"#/definitions/StringDatatype","description":"A reference to an identified subject that is of the specified type .","title":"Subject Identifier Reference"},"links":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:remarks"},"type":{"allOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["control","statement"]}],"description":"The semantic type of the subject.","title":"Subject Type"}},"required":["type","id-ref"],"title":"Mapping Entry Item (source or target)","type":"object"},"model":"mapping-collection","note":"The oscal-mapping-oscal-mapping-common:mapping-item definition from the OSCAL 1.2.1 mapping-collection model, demonstrating that a mapping item requires only type and id-ref, restricts type by allOf to the closed enumeration control or statement, and defines no uuid or href property.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-mapping-schema.json"},"data/schema-evidence/mapping-resource-reference.json":{"constraints":["required == [\"type\",\"href\"]","type uses anyOf (open vocabulary) with enum [\"catalog\",\"profile\"]"],"definition":"oscal-mapping-oscal-mapping-common:mapping-resource-reference","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-mapping-oscal-mapping-common:mapping-resource-reference","additionalProperties":false,"description":"A reference to a resource that is either the source or the target of a mapping.","properties":{"href":{"$ref":"#/definitions/URIReferenceDatatype","description":"A resolvable URL reference to the base catalog or profile that this profile is tailoring.","title":"Catalog or Profile Reference"},"links":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:link"},"minItems":1,"type":"array"},"ns":{"$ref":"#/definitions/URIDatatype","description":"An optional namespace qualifying the resource's type.","title":"Resource Type Namespace"},"props":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["catalog","profile"]}],"description":"The semantic type of the resource.","title":"Resource Type"}},"required":["type","href"],"title":"Mapped Resource Reference","type":"object"},"model":"mapping-collection","note":"The oscal-mapping-oscal-mapping-common:mapping-resource-reference definition from the OSCAL 1.2.1 mapping-collection model, demonstrating that a mapped resource reference requires type and href and constrains type with an open anyOf vocabulary whose enumeration lists catalog and profile.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-mapping-schema.json"},"data/schema-evidence/metadata.json":{"constraints":["required == [\"title\",\"last-modified\",\"version\",\"oscal-version\"]"],"definition":"oscal-ap-oscal-metadata:metadata","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ap-oscal-metadata:metadata","additionalProperties":false,"description":"Provides information about the containing document, and defines concepts that are shared across the document.","properties":{"actions":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:action"},"minItems":1,"type":"array"},"document-ids":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:document-id"},"minItems":1,"type":"array"},"last-modified":{"$ref":"#/definitions/oscal-ap-oscal-metadata:last-modified"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"locations":{"items":{"additionalProperties":false,"description":"A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.","properties":{"address":{"$ref":"#/definitions/oscal-ap-oscal-metadata:address"},"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the location, which may be used by a tool for display and navigation.","title":"Location Title"},"urls":{"items":{"$ref":"#/definitions/URIDatatype","description":"The uniform resource locator (URL) for a web site or other resource associated with the location.","title":"Location URL"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique ID for the location, for reference.","title":"Location Universally Unique Identifier"}},"required":["uuid"],"title":"Location","type":"object"},"minItems":1,"type":"array"},"oscal-version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:oscal-version"},"parties":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:address"},"minItems":1,"type":"array"},"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"external-ids":{"items":{"additionalProperties":false,"description":"An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).","properties":{"id":{"$ref":"#/definitions/StringDatatype"},"scheme":{"anyOf":[{"$ref":"#/definitions/URIDatatype"},{"enum":["http://orcid.org/"]}],"description":"Indicates the type of external identifier.","title":"External Identifier Schema"}},"required":["id","scheme"],"title":"Party External Identifier","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"member-of-organizations":{"items":{"$ref":"#/definitions/UUIDDatatype","description":"A reference to another party by UUID, typically an organization, that this subject is associated with.","title":"Organizational Affiliation"},"minItems":1,"type":"array"},"name":{"$ref":"#/definitions/StringDatatype","description":"The full name of the party. This is typically the legal name associated with the party.","title":"Party Name"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the party.","title":"Party Short Name"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["person","organization"]}],"description":"A category describing the kind of party the object describes.","title":"Party Type"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique identifier for the party.","title":"Party Universally Unique Identifier"}}},{"additionalProperties":false,"properties":{"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"external-ids":{"items":{"additionalProperties":false,"description":"An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).","properties":{"id":{"$ref":"#/definitions/StringDatatype"},"scheme":{"anyOf":[{"$ref":"#/definitions/URIDatatype"},{"enum":["http://orcid.org/"]}],"description":"Indicates the type of external identifier.","title":"External Identifier Schema"}},"required":["id","scheme"],"title":"Party External Identifier","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"location-uuids":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:location-uuid"},"minItems":1,"type":"array"},"member-of-organizations":{"items":{"$ref":"#/definitions/UUIDDatatype","description":"A reference to another party by UUID, typically an organization, that this subject is associated with.","title":"Organizational Affiliation"},"minItems":1,"type":"array"},"name":{"$ref":"#/definitions/StringDatatype","description":"The full name of the party. This is typically the legal name associated with the party.","title":"Party Name"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the party.","title":"Party Short Name"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["person","organization"]}],"description":"A category describing the kind of party the object describes.","title":"Party Type"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique identifier for the party.","title":"Party Universally Unique Identifier"}}}],"description":"An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.","title":"Party","type":"object"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"published":{"$ref":"#/definitions/oscal-ap-oscal-metadata:published"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"responsible-parties":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:responsible-party"},"minItems":1,"type":"array"},"revisions":{"items":{"additionalProperties":false,"description":"An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).","properties":{"last-modified":{"$ref":"#/definitions/oscal-ap-oscal-metadata:last-modified"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"oscal-version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:oscal-version"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"published":{"$ref":"#/definitions/oscal-ap-oscal-metadata:published"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the document revision, which may be used by a tool for display and navigation.","title":"Document Title"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["version"],"title":"Revision History Entry","type":"object"},"minItems":1,"type":"array"},"roles":{"items":{"additionalProperties":false,"description":"Defines a function, which might be assigned to a party in a specific situation.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A summary of the role's purpose and associated responsibilities.","title":"Role Description"},"id":{"$ref":"#/definitions/TokenDatatype","description":"A unique identifier for the role.","title":"Role Identifier"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the role.","title":"Role Short Name"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the role, which may be used by a tool for display and navigation.","title":"Role Title"}},"required":["id","title"],"title":"Role","type":"object"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the document, which may be used by a tool for display and navigation.","title":"Document Title"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["title","last-modified","version","oscal-version"],"title":"Document Metadata","type":"object"},"model":"assessment-plan","note":"The shared oscal-metadata:metadata assembly. Every OSCAL document, a catalog among them, is required to carry a title, a last-modified timestamp, a version and the OSCAL version it conforms to. That is what makes a published guide citable as a document rather than as a copy.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_assessment-plan_schema.json at definitions/oscal-ap-oscal-metadata:metadata.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ap-schema.json"},"data/schema-evidence/observation.json":{"constraints":["required == [\"uuid\",\"description\",\"methods\",\"collected\"]","no property named 'target'","no property named 'control-id'","no property named 'objective-id'"],"definition":"oscal-ar-oscal-assessment-common:observation","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:observation","additionalProperties":false,"description":"Describes an individual observation.","properties":{"collected":{"$ref":"#/definitions/DateTimeWithTimezoneDatatype","description":"Date/time stamp identifying when the finding information was collected.","title":"Collected Field"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this assessment observation.","title":"Observation Description"},"expires":{"$ref":"#/definitions/DateTimeWithTimezoneDatatype","description":"Date/time identifying when the finding information is out-of-date and no longer valid. Typically used with continuous assessment scenarios.","title":"Expires Field"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"methods":{"items":{"anyOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["EXAMINE","INTERVIEW","TEST","UNKNOWN"]}],"description":"Identifies how the observation was made.","title":"Observation Method"},"minItems":1,"type":"array"},"origins":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:origin"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"relevant-evidence":{"items":{"additionalProperties":false,"description":"Links this observation to relevant evidence.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this evidence.","title":"Relevant Evidence Description"},"href":{"$ref":"#/definitions/URIReferenceDatatype","description":"A resolvable URL reference to relevant evidence.","title":"Relevant Evidence Reference"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["description"],"title":"Relevant Evidence","type":"object"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"subjects":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:subject-reference"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this observation.","title":"Observation Title"},"types":{"items":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["ssp-statement-issue","control-objective","mitigation","finding","discovery","historic"]}],"description":"Identifies the nature of the observation. More than one may be used to further qualify and enable filtering.","title":"Observation Type"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Observation Universally Unique Identifier"}},"required":["uuid","description","methods","collected"],"title":"Observation","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:observation definition from the OSCAL 1.2.1 assessment-results model, demonstrating that an observation requires uuid, description, methods, and collected, and defines no target, control-id, or objective-id property.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/poam-outcomes.json":{"constraints":["properties includes \"observations\"","properties includes \"findings\"","observations items ref the shared assessment-common observation","findings items ref the shared assessment-common finding"],"definition":"oscal-poam-oscal-poam:plan-of-action-and-milestones","fetched_at":"2026-08-18","fragment":{"properties":{"findings":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:finding"},"minItems":1,"type":"array"},"observations":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:observation"},"minItems":1,"type":"array"},"risks":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:risk"},"minItems":1,"type":"array"}},"required":["uuid","metadata","poam-items"]},"fragment_note":"Only required and the observations, findings and risks properties are carried.","model":"plan-of-action-and-milestones","note":"The root assembly of the OSCAL 1.2.1 plan-of-action-and-milestones model. It carries observations and findings as sibling arrays, so assessment results is not the only model in which an outcome can be recorded. Both models sit in the Assessment layer; no control-layer or implementation-layer model carries either.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-poam-schema.json"},"data/schema-evidence/result.json":{"constraints":["required includes \"reviewed-controls\""],"definition":"oscal-ar-oscal-ar:result","fetched_at":"2026-08-18","fragment":{"properties":{"reviewed-controls":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls"}},"required":["uuid","title","description","start","reviewed-controls"]},"fragment_note":"Only required and the reviewed-controls property are carried. The other properties of result are not relevant to this claim and are omitted.","model":"assessment-results","note":"The result assembly of the OSCAL 1.2.1 assessment-results model. Every result is required to declare the controls it reviewed, so the control frame is unavoidable at the result level. The referenced reviewed-controls assembly requires control-selections, and a selection may use include-all rather than naming individual controls, so the requirement can be met without listing any one control.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/reviewed-controls.json":{"constraints":["required == [\"control-selections\"]","control-selections items use anyOf with required [\"include-all\"] or [\"include-controls\"]"],"definition":"oscal-ar-oscal-assessment-common:reviewed-controls","fetched_at":"2026-08-18","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls","additionalProperties":false,"description":"Identifies the controls being assessed and their control objectives.","properties":{"control-objective-selections":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this collection of control objectives.","title":"Control Objectives Description"},"exclude-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ar-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this collection of control objectives.","title":"Control Objectives Description"},"exclude-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"include-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-objectives"]}],"description":"Identifies the control objectives of the assessment. In the assessment plan, these are the planned objectives. In the assessment results, these are the assessed objectives, and reflects any changes from the plan.","title":"Referenced Control Objectives","type":"object"},"minItems":1,"type":"array"},"control-selections":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of in-scope controls specified for assessment.","title":"Assessed Controls Description"},"exclude-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ar-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of in-scope controls specified for assessment.","title":"Assessed Controls Description"},"exclude-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"include-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-controls"]}],"description":"Identifies the controls being assessed. In the assessment plan, these are the planned controls. In the assessment results, these are the actual controls, and reflects any changes from the plan.","title":"Assessed Controls","type":"object"},"minItems":1,"type":"array"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of control objectives.","title":"Control Objective Description"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["control-selections"],"title":"Reviewed Controls and Control Objectives","type":"object"},"model":"assessment-results","note":"The reviewed-controls assembly of the OSCAL 1.2.1 assessment-results model. It requires control-selections, and each selection must carry either include-all or include-controls. So the requirement that a result declare the controls it reviewed can be satisfied with include-all, without naming any one control. The single assessment result in the three bodies of content does exactly that.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/six-questions.json":{"answer_states":[{"key":"filled","label":"Answered","meaning":"The published content answers this question."},{"key":"partial","label":"Partly answered","meaning":"The published content answers part of this question."},{"key":"empty-absent","label":"Not answered","meaning":"The published content does not answer the question or state a reason for the omission."}],"approaches":[{"key":"catalog-first","label":"Catalog-first","layer":"Control","one_line":"The rule is a catalog control; the check is a software component in a component definition.","option_letter":"A","primary_model":"catalog","repo":"https://github.com/awslabs/oscal-content-for-aws-services","serves_stakeholder_first":"publisher","status_annotation":"experimental, per publisher"},{"key":"component-first","label":"Component-first","layer":"Implementation","one_line":"The rule uses a proposed assembly on the product component; the check uses a proposed assembly on a validation component.","option_letter":"B","primary_model":"component-definition","repo":null,"serves_stakeholder_first":"implementer","status_annotation":"proposed schema"},{"key":"assessment-first","label":"Assessment-first","layer":"Assessment","one_line":"The rule is an assessment plan activity or step; a property identifies the check.","option_letter":"C","primary_model":"assessment-plan","repo":null,"serves_stakeholder_first":"assessor","status_annotation":"placeholder and synthetic identifiers"}],"carrier_note":"Each answer identifies the OSCAL model and assemblies representing the capability. Rules use catalog controls, component rules or assessment activities; the choice affects references to checks, claims and results.","empty_states":[{"key":"empty-absent","label":"Unanswered, no stated position","meaning":"The published content does not answer the question or state a reason for the omission.","rendering":"hollow with a light dotted fill"}],"finding":"Questions 1 and 2 are answered by all three approaches. No approach fully answers both 6a and 6b, and no approach answers every question.","legend":{"answers_title":"Is the question answered?","label":"How to read an answer","mechanism_title":"How the capability is enabled","why_one_block":"Each cell combines an answer state with mechanism badges. A shared legend explains both dimensions together.","why_uneven":"Answer states describe evidence coverage. Mechanism descriptions also explain schema and tool-support requirements, so the descriptions need additional detail."},"matrix":[{"approach":"catalog-first","assemblies":["control"],"mechanisms":["assembly","prop"],"model":"catalog","note":"One control per rule. Existing assemblies capture context around the rule's intent.","props":[{"name":"TechnicalControlId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"1","snippet_ids":["aws-acm2-control","aws-input-parameter"],"state":"filled"},{"approach":"component-first","assemblies":["component","rules"],"mechanisms":["proposed"],"model":"component-definition","note":"The proposed rules assembly sits on the component alongside control-implementations.","slot":"1","snippet_ids":["ibm-cos-component"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The activity defines the rule and the step describes the check. Without a parameter field, required values are recorded in text.","props":[{"name":"check","ns":"http://comply0.com/ns/oscal"}],"slot":"1","snippet_ids":["ez-stig-activity-v259312","ez-stig-sc28-v270747"],"state":"filled"},{"approach":"catalog-first","assemblies":["mapping","map"],"mechanisms":["assembly"],"model":"mapping-collection","note":"A separate mapping collection links rules to framework controls. The published corpus contains no such mapping document.","slot":"2","snippet_ids":["aws-acm-backmatter-source","aws-acm-service-rollup"],"state":"filled"},{"approach":"component-first","assemblies":["component","implemented-requirement","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"component-definition","note":"Existing assemblies link the component to the control. Linking an individual rule requires the proposed assembly.","slot":"2","snippet_ids":["ibm-statement-rules","ibm-cos-component"],"state":"filled"},{"approach":"assessment-first","assemblies":["reviewed-controls","activity","related-controls"],"mechanisms":["assembly"],"model":"assessment-plan","note":"Two levels: reviewed-controls defines the required plan scope; related-controls optionally links an activity to controls.","slot":"2","snippet_ids":["ez-stig-related-controls","ez-cisa-step-reviewed"],"state":"filled"},{"approach":"catalog-first","assemblies":["component","implemented-requirement"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"The check identifier resolves within the runtime to an executable machine check.","props":[{"name":"ConfigRuleId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"3","snippet_ids":["aws-acm2-control","aws-acm-rsa-check-component"],"state":"filled"},{"approach":"component-first","assemblies":["component","checks"],"mechanisms":["proposed"],"model":"component-definition","note":"The proposed schema places both composite-key fields on the check. The rule has no reference back to the check.","slot":"3","snippet_ids":["ibm-validation-ansible"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"Three conventions: CISA references an executable through a JSON string in a prop; STIG and CIS describe checks in prose.","props":[{"name":"check","ns":"http://comply0.com/ns/oscal"}],"slot":"3","snippet_ids":["ez-cis-step-props","ez-cis-remediation-step","ez-cisa-context-step"],"state":"partial"},{"approach":"catalog-first","assemblies":["implemented-requirement","by-component"],"mechanisms":["assembly"],"model":"system-security-plan","note":"The by-component response identifies a component, not an instance. An assessment plan cannot import a catalog directly.","slot":"4","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["implemented-requirement","by-component","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"system-security-plan","note":"The proposed rule reference extends by-component. An assessor can include the component definition and associated checks in an assessment plan.","slot":"4","snippet_ids":["ibm-validation-ansible"],"state":"partial"},{"approach":"assessment-first","assemblies":["assessment-subjects","task","subjects"],"mechanisms":["assembly"],"model":"assessment-plan","note":"The plan defines subject scope; activity-associated tasks select targets. Both can identify inventory items, representing instances rather than classes.","slot":"4","snippet_ids":["ez-subjects-includeall","ez-subjects-explicit"],"state":"filled"},{"approach":"catalog-first","assemblies":["component"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"The content records inputs and outputs but not the engine. ConfigRuleId resolves within the engine. No assessor workflow is shown; an assessment plan cannot import a catalog directly.","paths":[{"assemblies":["component","by-component"],"in":{"slot":"3"},"key":"implementor","label":"Implementor's path","out":{"slot":"6a"}}],"props":[{"name":"ConfigRuleId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"5","snippet_ids":["aws-config-service-bare"],"state":"partial"},{"approach":"component-first","assemblies":["component"],"mechanisms":["assembly","proposed"],"model":"component-definition","note":"The examples leave runner associations unresolved, including how an assessment asset links to a task or an observation.","paths":[{"assemblies":["component","checks","by-component","implementing-rules"],"in":{"slot":"3"},"key":"implementor","label":"Implementor's path","out":{"slot":"6a"}},{"assemblies":["component","checks","assessment-assets","observation","assessment-check-id","result"],"copy":{"slot":"3"},"in":{"model":"assessment-plan"},"key":"assessor","label":"Assessor's path","out":{"slot":"6b"}}],"slot":"5","snippet_ids":["ibm-ap-activity","ibm-ap-task-subjects","ibm-ar-observation"],"state":"filled"},{"approach":"assessment-first","assemblies":["assessment-platforms","component","task"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The platform executes the check, a referenced component represents the plugin, and a task property identifies the platform.","paths":[{"assemblies":["activity","step","assessment-platforms","component","task","observation"],"in":{"model":"assessment-plan"},"key":"assessor","label":"Assessor's path","out":{"slot":"6b"}}],"props":[{"name":"assessment-platform","ns":"http://comply0.com/ns/oscal"}],"slot":"5","snippet_ids":["ez-cisa-context-activity","ez-cisa-assessment-assets","ez-cisa-task-timing"],"state":"partial"},{"approach":"catalog-first","assemblies":["implemented-requirement","by-component"],"mechanisms":["assembly"],"model":"system-security-plan","note":"The component definition describes how a component could satisfy a control, not a system's implementation. The corpus contains no system security plan.","slot":"6a","snippet_ids":["aws-acm-rsa-check-component","aws-acm-service-rollup"],"state":"partial"},{"approach":"component-first","assemblies":["implemented-requirement","by-component","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"system-security-plan","note":"The claim uses a by-component response. Identifying the supporting rule requires the proposed implementing-rules assembly.","slot":"6a","snippet_ids":[],"state":"empty-absent"},{"approach":"assessment-first","assemblies":["import-ssp","back-matter","resource"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The assessment plan references the document containing the implementation claim. A back-matter resource supports cases without a plan of record.","slot":"6a","snippet_ids":["ez-cisa-import-ssp","ez-cisa-ssp-resource","ez-cisa-no-ssp-resource","ez-stig-import-ssp"],"state":"partial"},{"approach":"catalog-first","assemblies":["finding"],"mechanisms":["assembly"],"model":"assessment-results","note":"No assessment results are published in the catalog-first OSCAL corpus.","slot":"6b","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["observation"],"mechanisms":["assembly","proposed"],"model":"assessment-results","note":"The result contains observations but no findings or objective status. The control reference must be recovered through the assessment plan.","slot":"6b","snippet_ids":["ibm-ar-observation"],"state":"partial"},{"approach":"assessment-first","assemblies":["finding","observation"],"mechanisms":["assembly"],"model":"assessment-results","note":"A separate results document imports the plan. Findings have targets and status; observations identify the executed activity as the subject.","slot":"6b","snippet_ids":["ez-cisa-ar-finding","ez-cisa-ar-observation"],"state":"filled"}],"mechanism_note":"Answer states describe coverage in the published corpus. Mechanism badges identify the OSCAL structures needed to represent an answer. Evidence coverage does not establish schema adoption or tool interoperability.","mechanism_states":[{"key":"assembly","label":"Released OSCAL assembly","meaning":"A released OSCAL assembly provides the capability without a schema change.","rendering":"a solid badge","short":"OSCAL assembly"},{"key":"proposed","label":"Proposed assembly","meaning":"The capability requires a proposed assembly. Interoperable use requires schema adoption and tool support for the new structure.","rendering":"a dashed badge","short":"Proposed"},{"key":"prop","label":"Namespaced property","meaning":"A property in the publisher's namespace provides the capability. Tools need a shared convention to interpret the property; the OSCAL schema does not define the meaning.","rendering":"a dotted badge","short":"Prop"}],"note":"The six questions and answer matrix compare OSCAL JSON examples, including content using proposed assemblies. tools/verify.py --matrix checks each cell against the example files. Notes describe supported capabilities and unresolved questions.","paths_note":"Each runner path shows one input document and one output document. The documents depend on whether the system owner or assessor runs the check.","proposed_assemblies":["assessment-check-id","associated-checks","checks","implementing-rules","result","rule-groups","rules"],"slots":[{"key":"rule","name":"What the rule requires","number":"1","optional":false,"question":"What condition must hold, and where is the requirement defined?","short":"Rule","why_separate":"A technology-specific requirement defines one testable condition. Parameter options and defaults belong with that definition where the selected model supports them."},{"binding_times":[{"authored_by":"Rule author","key":"inline","label":"Author-time, inline","mechanism":"The rule declares its control directly"},{"authored_by":"Rule author","key":"pointer","label":"Author-time, by pointer","mechanism":"A prop carries an external framework identifier that a consumer must resolve"},{"authored_by":"Rule author or third party","available_to":{"assessment-first":false,"catalog-first":true,"component-first":false},"key":"late","label":"Late, external","mechanism":"A separate artifact links a rule to a control after publication","why":"mapping-item.type is restricted by allOf to control and statement, and mapping-item has neither uuid nor href. External mappings therefore reach rules modelled as controls or control statements, not component rules or activities. This OSCAL schema constraint does not establish a preferred approach."}],"cost_of_leaving_empty":{"evidence":["observation.json","finding.json","finding-target.json"],"finding":"Not available. finding requires target; finding-target requires type, restricted by allOf to statement-id or objective-id, both control-derived.","observation":"Available. AR observation requires only uuid, description, methods and collected, with no control reference.","summary":"Without a control link, an assessor can record an observation but not a finding against a control statement or objective."},"key":"control-tie","name":"How the rule links to a control","number":"2","optional":true,"question":"Does this rule help satisfy a regulatory control, and which one?","short":"Control","why_separate":"A rule is finer-grained than a control and may serve several controls, one, or none. A control-linking mechanism is required, but using the mechanism is optional."},{"key":"check","name":"How the rule is tested","number":"3","optional":false,"question":"Which executable or procedure tests the rule?","short":"Check","why_separate":"A rule may have several checks, one per tool. The examples separate rule definitions from checks and reference external executables rather than embedding code in OSCAL."},{"key":"subject","name":"What the check runs against","not_established":true,"not_established_note":"The examples use assessment platforms, assets and components differently. A consistent distinction between the subject being assessed and the resources performing the assessment is not established here.","number":"4","optional":false,"question":"Is the subject a host, component, account or another resource?","short":"Subject","why_separate":"The subject identifies the assessed host, inventory item, component or account. Criterion 8 addresses response fidelity."},{"key":"actor","name":"What performs the check","not_established":true,"not_established_note":"The same distinction remains open in question 4. The approaches use different combinations of assessment-assets, assessment-platforms, uses-components, validation components, origin actors, task-level props and the method prop.","number":"5","optional":false,"question":"Which tool or person performs the check, and how is the runner identified?","short":"Runner","why_separate":"The runner may be a validation component, assessment platform, tool or person. The method prop identifies examine, interview or test."},{"group_name":"Implementation claims and assessment outcomes","key":"implementation-claim","name":"How the system claims it meets the rule","number":"6a","optional":false,"question":"How does the system owner describe implementation of the rule?","short":"Claim","why_separate":"The system owner provides a narrative claim of implementation and design intent per component. The SSP represents claims through implemented-requirement, statement and by-component."},{"group_name":"Implementation claims and assessment outcomes","key":"assessment-result","name":"How an assessment records the outcome","number":"6b","optional":false,"question":"Was the rule satisfied, when, and for which subject?","short":"Result","why_separate":"The assessor records evidence and a binary or graded outcome per subject at a point in time. The AR uses observation, finding and status. A desired-state rule has a binary satisfaction condition; the SSP implementation claim is narrative."}]},"data/snippets/aws-acm-backmatter-source.json":{"approach":"catalog-first","content":"{\n \"resources\": [\n {\n \"uuid\": \"ab8a6a36-2706-49e5-b87e-498c52ba6a61\",\n \"title\": \"AWS Regions Component Definition\",\n \"rlinks\": [\n {\n \"href\": \"../aws_regions.oscal.json\",\n \"media-type\": \"application/json\"\n }\n ]\n },\n {\n \"uuid\": \"f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"title\": \"AWS Security Hub Controls\",\n \"rlinks\": [\n {\n \"href\": \"../catalogs/aws_security-hub.oscal.json\",\n \"media-type\": \"application/json\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-backmatter-source","language":"json","pointer":"/component-definition/back-matter","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"Back-matter, source to the catalog"},"data/snippets/aws-acm-rsa-check-component.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"b5e8b205-cc1f-4bd0-9e51-4ebaab18f69a\",\n \"type\": \"software\",\n \"title\": \"acm-certificate-rsa-check\",\n \"description\": \"Checks if RSA certificates managed by AWS Certificate Manager (ACM) have a key length of at least '2048' bits. The rule is NON_COMPLIANT if the minimum key length is less than 2048 bits.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"ACM_CERTIFICATE_RSA_CHECK\"\n },\n {\n \"name\": \"asset-type\",\n \"value\": \"automated-inspection\"\n },\n {\n \"name\": \"ResourceType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"AWS::ACM::Certificate\"\n }\n ],\n \"responsible-roles\": [\n {\n \"role-id\": \"owner\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"4f227b9d-b47b-4c06-bb55-8f3a17e29b74\",\n \"source\": \"#f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"description\": \"Security Hub control implementation\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"4de99497-e4fe-4dfd-80a7-ebbd59f06364\",\n \"control-id\": \"ACM.2\",\n \"description\": \"Implemented via AWS Config Rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-rsa-check-component","language":"json","pointer":"/component-definition/components/2","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"3","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"acm-certificate-rsa-check, the check component"},"data/snippets/aws-acm-service-rollup.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"ae50c910-9057-4345-89d9-c2ae4c1f0b08\",\n \"source\": \"#f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"description\": \"AWS Security Hub control implementation\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"c3e6d492-b3b6-46d9-9e2a-7d6d9922f3fa\",\n \"control-id\": \"ACM.1\",\n \"description\": \"Security Hub control ACM.1\"\n },\n {\n \"uuid\": \"551c5fc8-569a-4ea5-a0d8-0b524e9f4205\",\n \"control-id\": \"ACM.2\",\n \"description\": \"Security Hub control ACM.2\"\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-service-rollup","language":"json","pointer":"/component-definition/components/0/control-implementations/0","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"AWS Certificate Manager, the service roll-up"},"data/snippets/aws-acm2-control.json":{"approach":"catalog-first","content":"{\n \"id\": \"ACM.2\",\n \"title\": \"ACM.2\",\n \"props\": [\n {\n \"name\": \"SeverityLabel\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"HIGH\"\n },\n {\n \"name\": \"TriggerType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Change Triggered\"\n },\n {\n \"name\": \"EvaluatedServices\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"ACM\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://docs.aws.amazon.com/console/securityhub/ACM.2/remediation\",\n \"rel\": \"remediation\"\n }\n ],\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"This control checks whether RSA certificates managed by AWS Certificate Manager use a key length of at least 2,048 bits. The control fails if the key length is smaller than 2,048 bits.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"RSA certificates managed by ACM should use a key length of at least 2,048 bits\"\n },\n {\n \"name\": \"guidance\",\n \"prose\": \"For information on how to correct this issue, consult the AWS Security Hub controls documentation.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"acm-certificate-rsa-check\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"acm-certificate-rsa-check\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm2-control","language":"json","pointer":"/catalog/groups/0/controls/1","section":null,"sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"ACM.2, the control"},"data/snippets/aws-config-service-bare.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"9a02ef98-02b2-49c4-a3ea-3c546e830a15\",\n \"type\": \"service\",\n \"title\": \"AWS Config\",\n \"description\": \"AWS Config is a service that continuously monitors and records your AWS resource configurations and allows you to automate the evaluation of recorded configurations against desired settings.\",\n \"props\": [\n {\n \"name\": \"service-id\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Config Service\"\n },\n {\n \"name\": \"version\",\n \"value\": \"2014-11-12\"\n },\n {\n \"name\": \"availability\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"REGIONAL\"\n },\n {\n \"name\": \"label\",\n \"value\": \"AWS Config\",\n \"class\": \"marketingName\",\n \"group\": \"marketing\"\n },\n {\n \"name\": \"apiEndpointPrefix\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"arnNamespace\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"cloudTrailEventSource\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"lifecycle-stage\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"generally-available\"\n },\n {\n \"name\": \"iamServicePrefix\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n }\n ],\n \"links\": \"...\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-config-service-bare","language":"json","pointer":"/component-definition/components/0","section":null,"sha256_of_source_file":"d5049e46d7a1251932be3e74c1f9bace606ac9b5f5542249ccb884171394a6e7","slot":"5","source":"AWS/oscal-content-for-aws-services-main/component-definitions/config.oscal.json","title":"AWS Config, the engine that runs the checks"},"data/snippets/aws-control-cloudtrail2.json":{"approach":"catalog-first","content":"{\n \"id\": \"CloudTrail.2\",\n \"title\": \"CloudTrail.2\",\n \"props\": [\n {\n \"name\": \"SeverityLabel\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"MEDIUM\"\n },\n {\n \"name\": \"TriggerType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Periodic\"\n },\n {\n \"name\": \"EvaluatedServices\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"CloudTrail\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://docs.aws.amazon.com/console/securityhub/CloudTrail.2/remediation\",\n \"rel\": \"remediation\"\n }\n ],\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"This AWS control checks whether AWS CloudTrail is configured to use the server side encryption (SSE) AWS Key Management Service (AWS KMS) customer master key (CMK) encryption. The check will pass if the KmsKeyId is defined.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"CloudTrail should have encryption at-rest enabled\"\n },\n {\n \"name\": \"guidance\",\n \"prose\": \"For information on how to correct this issue, consult the AWS Security Hub controls documentation.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"cloud-trail-encryption-enabled\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"cloud-trail-encryption-enabled\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-21T03:10:41+00:00","id":"aws-control-cloudtrail2","language":"json","pointer":"/catalog/groups/15/controls/2","section":null,"sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"CloudTrail.2, the control"},"data/snippets/aws-input-parameter.json":{"approach":"catalog-first","content":"[\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"IAM_PASSWORD_POLICY\"\n },\n {\n \"name\": \"asset-type\",\n \"value\": \"automated-inspection\"\n },\n {\n \"name\": \"MaxPasswordAge\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"90\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"PasswordReusePrevention\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"24\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"MinimumPasswordLength\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"14\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireNumbers\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireSymbols\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireLowercaseCharacters\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireUppercaseCharacters\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"MinimumPasswordLength\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"7\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"PasswordReusePrevention\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"4\",\n \"class\": \"InputParameter\"\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-input-parameter","language":"json","pointer":"/component-definition/components/2/props","section":null,"sha256_of_source_file":"940cab9d3328d5ff55e6c69fbfae6fd4e846873d07f70ef7c096651bc8f750ab","slot":"1","source":"AWS/oscal-content-for-aws-services-main/component-definitions/iam.oscal.json","title":"InputParameter props, the parameter mechanism"},"data/snippets/ez-cis-remediation-step.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"7be22348-467b-563a-9c21-d438e47df7df\",\n \"title\": \"Remediation for Ensure cramfs kernel module is not available\",\n \"description\": \"Run the following script to unload and disable the `cramfs` module:\\n\\n**- IF -** the `cramfs` kernel module is available in ANY installed kernel:\\n\\n- Create a file ending in `.conf` with `install cramfs /bin/false` in the `/etc/modprobe.d/` directory\\n- Create a file ending in `.conf` with `blacklist cramfs` in the `/etc/modprobe.d/` directory\\n- Run `modprobe -r cramfs 2>/dev/null; rmmod cramfs 2>/de [truncated]\",\n \"props\": [\n {\n \"name\": \"assessment-status\",\n \"value\": \"automated\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-rule-id\",\n \"value\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"step-type\",\n \"value\": \"remediation\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-remediation-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/1","section":null,"sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS remediation step"},"data/snippets/ez-cis-resolution-status.json":{"approach":"assessment-first","content":"{\n \"description\": \"CIS Controls v8.0 derived from benchmark cc8:controlURI paths. Provide a CIS Controls v8 OSCAL catalog via --cis-catalog-v8 for authoritative control-id resolution.\",\n \"props\": [\n {\n \"name\": \"framework\",\n \"value\": \"CIS Controls v8.0\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"resolution-status\",\n \"value\": \"synthetic-ids\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ],\n \"include-controls\": \"...\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-resolution-status","language":"json","pointer":"/assessment-plan/reviewed-controls/control-selections/0","section":null,"sha256_of_source_file":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8","slot":"meta","source":"Easy Dynamics/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","title":"CIS resolution status"},"data/snippets/ez-cis-step-props.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"5c4c3bec-7bbe-521d-9a90-c04102edce9b\",\n \"title\": \"Audit for Ensure cramfs kernel module is not available\",\n \"description\": \"## Description\\n\\nThe `cramfs` filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems. A `cramfs` image can be used without having to first decompress the image.\\n\\n## Audit\\n\\nRun the following script to verify:\\n\\n**- IF -** the `cramfs` kernel module is available in ANY installed kernel, verify:\\n\\n- An entry including `/bin/true` or `/bin/false` exists in a file w [truncated]\",\n \"props\": [\n {\n \"name\": \"assessment-status\",\n \"value\": \"automated\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-rule-id\",\n \"value\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"step-type\",\n \"value\": \"audit\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-control-uri\",\n \"value\": \"http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-control-uri\",\n \"value\": \"http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"CM-7\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"stig-finding-id\",\n \"value\": \"V-230498\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-safeguard-urn\",\n \"value\": \"urn:cisecurity.org:controls:8.0:4:8\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-safeguard-urn\",\n \"value\": \"urn:cisecurity.org:controls:7.0:9:2\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ],\n \"remarks\": \"Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-step-props","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0","section":null,"sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS audit step props"},"data/snippets/ez-cisa-ar-finding.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"b5d014ae-23b1-51b8-845a-972f40def692\",\n \"title\": \"MS.AAD.1.1v1: Legacy Authentication Blocking\",\n \"target\": {\n \"type\": \"objective-id\",\n \"status\": {\n \"state\": \"satisfied\"\n },\n \"target-id\": \"ms.aad.1.1v1\"\n },\n \"description\": \"Conditional Access policy confirmed blocking all legacy authentication protocols for all users.\",\n \"related-observations\": [\n {\n \"observation-uuid\": \"941e3133-152b-5301-8762-abd228b5ee80\"\n }\n ]\n}","extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ar-finding","language":"json","pointer":"/assessment-results/results/0/findings/0","section":null,"sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"A finding, targeting an objective"},"data/snippets/ez-cisa-ar-observation.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"941e3133-152b-5301-8762-abd228b5ee80\",\n \"title\": \"Observation: MS.AAD.1.1v1 - Legacy Authentication Blocking\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"remarks\": \"Legacy authentication is blocked tenant-wide via a Conditional Access policy in the enabled state. Control CM-7 is satisfied.\",\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"422ccfe4-7b60-4fe8-81ff-3d4464cc6e05\"\n }\n ],\n \"collected\": \"2026-03-05T15:30:00-05:00\",\n \"description\": \"Examiner queried the Conditional Access policy configuration via Microsoft Graph API. A policy targeting all users with a condition for legacy authentication protocols and a grant control of 'Block' was identified and confirmed enabled.\"\n}","extracted_at":"2026-08-22T18:43:41+00:00","id":"ez-cisa-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","section":null,"sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"The observation it rests on, and what was examined"},"data/snippets/ez-cisa-assessment-assets.json":{"approach":"assessment-first","content":"{\n \"components\": [\n {\n \"uuid\": \"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\",\n \"type\": \"software\",\n \"title\": \"ScubaGear Plugin\",\n \"description\": \"CLI plugin on Comply0 platform for verifying M365 configuration settings using CISA ScubaGear.\",\n \"props\": [\n {\n \"name\": \"context\",\n \"value\": \"{\\\"plugin-path\\\":\\\"Comply0.Kansa.Extensions.ScubaGear.dll\\\",\\\"script-path\\\":\\\"Resources\\\\\\\\Invoke-ScubaGear.ps1\\\",\\\"app-id\\\":\\\"c4d39d69-aea7-4acc-af2c-45c502d3a308\\\",\\\"opa-path\\\":\\\"/usr/local/bin\\\"}\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"status\": {\n \"state\": \"operational\"\n }\n }\n ],\n \"assessment-platforms\": [\n {\n \"uuid\": \"15000cf8-2f2a-4417-8b93-60a1f209ee95\",\n \"title\": \"Comply0 cATO Agent\",\n \"uses-components\": [\n {\n \"component-uuid\": \"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-assets"},"data/snippets/ez-cisa-context-activity.json":{"approach":"assessment-first","content":"[\n {\n \"name\": \"context\",\n \"value\": \"{\\\"ProductNames\\\":\\\"aad\\\",\\\"component-uuid\\\":\\\"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\\\"}\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n },\n {\n \"name\": \"check\",\n \"value\": \"MS.AAD\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n]","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA activity context prop"},"data/snippets/ez-cisa-context-step.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"4b7f6f09-84da-4c03-ba7b-d02ff52d5b69\",\n \"title\": \"MS.AAD.3.7v1\",\n \"description\": \"Managed devices SHOULD be required for authentication.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"EXAMINE\"\n },\n {\n \"name\": \"criticality\",\n \"ns\": \"http://cisa.gov/ns/oscal\",\n \"value\": \"SHOULD\"\n },\n {\n \"name\": \"context\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"{\\\"SkipHybridJoinCheck\\\":false}\"\n },\n {\n \"name\": \"check\",\n \"value\": \"MS.AAD.3.7\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://github.com/cisagov/ScubaGear/tree/main/PowerShell/ScubaGear/baselines/aad.md#msaad37v1\",\n \"rel\": \"canonical\"\n },\n {\n \"href\": \"https://attack.mitre.org/techniques/T1078/\",\n \"text\": \"T1078: Valid Accounts\",\n \"rel\": \"mitre\"\n },\n {\n \"href\": \"https://attack.mitre.org/techniques/T1078/004/\",\n \"text\": \"T1078.004: Cloud Accounts\",\n \"rel\": \"mitre\"\n }\n ],\n \"reviewed-controls\": {\n \"control-selections\": [\n {\n \"include-controls\": [\n {\n \"control-id\": \"ac-20\",\n \"statement-ids\": [\n \"ac-20_smt.b\"\n ]\n },\n {\n \"control-id\": \"ia-3\",\n \"statement-ids\": [\n \"ia-3_smt\"\n ]\n }\n ]\n }\n ]\n },\n \"remarks\": \"The security risk of an adversary authenticating to the tenant from their own device is reduced by requiring a managed device to authenticate. Managed devices are under the provisioning and control of the agency. [OMB-22-09](https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf) states, \\\"When authorizing users to access resources, agencies must consider at least one device-level signal [truncated]\"\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","section":null,"sha256_of_source_file":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653","slot":"3","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-maester.json","title":"CISA step context prop"},"data/snippets/ez-cisa-import-ssp.json":{"approach":"assessment-first","content":"{\n \"href\": \"#75e00698-e43b-4d6f-be7f-d1227a3a3e39\",\n \"remarks\": \"Link the SAP to the SSP.\"\n}","extracted_at":"2026-08-22T18:44:16+00:00","id":"ez-cisa-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"import-ssp, resolving to a resource in the same document"},"data/snippets/ez-cisa-no-ssp-resource.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"f56da5c6-da67-4c40-acc8-6814bf7aa374\",\n \"title\": \"System's Full Name\",\n \"description\": \"# USE THIS RESOURCE WHEN NO OSCAL-BASED SSP EXISTS\\n\\nBriefly describe the system. This will appear in the SAR.\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"no-oscal-ssp\"\n },\n {\n \"name\": \"import-profile\",\n \"ns\": \"https://fedramp.gov/ns/oscal\",\n \"value\": \"#890170c3-d4fa-4d25-ab96-8e4bf7cc237c\"\n },\n {\n \"name\": \"purpose\",\n \"ns\": \"https://fedramp.gov/ns/oscal\",\n \"value\": \"Briefly state the system's purpose. This will appear in the SAR.\"\n }\n ],\n \"remarks\": \"Only include this resource if no OSCAL-based SSP is available.\"\n}","extracted_at":"2026-08-22T18:46:12+00:00","id":"ez-cisa-no-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/0","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The alternative resource, where no OSCAL system security plan exists"},"data/snippets/ez-cisa-ssp-resource.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"75e00698-e43b-4d6f-be7f-d1227a3a3e39\",\n \"title\": \"Kalvico Enterprise ICAM SSP\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"oscal-ssp\"\n }\n ],\n \"rlinks\": [\n {\n \"href\": \"system-security-plan.json\",\n \"media-type\": \"application/oscal.catalog+json\"\n }\n ],\n \"remarks\": \"Use this to point to an OSCAL-based SSP.\"\n}","extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/1","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The resource a resolved import-ssp lands on"},"data/snippets/ez-cisa-step-reviewed.json":{"approach":"assessment-first","content":"{\n \"control-selections\": [\n {\n \"include-controls\": [\n {\n \"control-id\": \"cm-7\",\n \"statement-ids\": [\n \"cm-7_smt\"\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-step-reviewed","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0/reviewed-controls","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"2","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA step reviewed-controls"},"data/snippets/ez-cisa-task-timing.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"c2f71c67-3d4c-43ba-ad9d-949d0396413f\",\n \"type\": \"action\",\n \"title\": \"Automate assessment of ScubaGear tests using Comply0 Platform Assessment Agent\",\n \"description\": \"Execute CISA SCuBA assessment tests using the Comply0 cATO Agent with ScubaGear plugin.\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"value\": \"15000cf8-2f2a-4417-8b93-60a1f209ee95\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"timing\": {\n \"at-frequency\": {\n \"period\": 24,\n \"unit\": \"hours\"\n }\n },\n \"associated-activities\": [\n {\n \"activity-uuid\": \"760fe3fc-45af-4c62-b095-265a56a1dedf\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"4e391cf6-5549-46f3-b3d7-aad12cd5a226\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"2c69fb5c-056f-4788-be36-723b939a4766\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"04319877-e72d-4967-b968-4852e6738113\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"53852402-8cd6-4e1c-a559-f31bb004a66e\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"c98b996e-8dae-40ef-8b40-100ffbe9e5e3\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"5f62a033-3847-43ec-bafd-3dc1a7621029\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA task, with timing"},"data/snippets/ez-stig-activity-v259312.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"e69fb43b-9565-58f6-badc-e31834e575f6\",\n \"title\": \"V-259312: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"stig-group-id\",\n \"value\": \"V-259312\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-rule-id\",\n \"value\": \"SV-259312r961818_rule\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"category\",\n \"value\": \"CAT II\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"srg\",\n \"value\": \"SRG-APP-000501-DB-000336\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"sequence\",\n \"value\": \"101\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-000172\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"au-12\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"documentable\",\n \"value\": \"false\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"93fcfc80-5643-5c15-835d-aaa4d000daeb\",\n \"title\": \"Check: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"## Check\\n\\nExecute the following SQL the \\\"enterprisedb\\\" operating system user:\\n\\n```bash\\n> psql edb -c \\\"SHOW edb_audit_statement\\\"\\n```\\n\\nIf the result is not \\\"all\\\" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"check\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"assessment-method\",\n \"value\": \"TEST\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-000172\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"au-12\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n },\n {\n \"uuid\": \"e58bf90b-06dc-537f-81a9-68e61e87b7a7\",\n \"title\": \"Remediate: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"## Remediate\\n\\nExecute the following SQL as the \\\"enterprisedb\\\" operating system user:\\n\\n```bash\\n> psql edb -c \\\"ALTER SYSTEM SET edb_audit_statement = 'all'\\\"\\n> psql edb -c \\\"SELECT pg_reload_conf()\\\"\\n```\\n\\nor\\n\\nUpdate the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"remediate\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n }\n ],\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"au-12\"\n }\n ]\n }\n ]\n },\n \"remarks\": \"Source SRG: SRG-APP-000501-DB-000336\\nDPMS Target identifier: 5575\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-activity-v259312","language":"json","pointer":"/assessment-plan/local-definitions/activities/100","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG activity V-259312"},"data/snippets/ez-stig-import-ssp.json":{"approach":"assessment-first","content":"{\n \"href\": \"PLACEHOLDER\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"meta","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG import-ssp, an unresolved placeholder"},"data/snippets/ez-stig-related-controls.json":{"approach":"assessment-first","content":"{\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"au-12\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-related-controls","language":"json","pointer":"/assessment-plan/local-definitions/activities/100/related-controls","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"2","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG related-controls, the control tie"},"data/snippets/ez-stig-sc28-v270747.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"c8eaf2b1-c63f-5693-a1a5-e4e66a760c41\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system.\\n\\nThis requirement addresses protection of user-generated data, as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.\\n\\nSatisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS [truncated]\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"stig-group-id\",\n \"value\": \"V-270747\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-rule-id\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"category\",\n \"value\": \"CAT II\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"srg\",\n \"value\": \"SRG-OS-000185-GPOS-00079\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"sequence\",\n \"value\": \"102\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-001199\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002475\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002476\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-004910\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.1\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.3\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"documentable\",\n \"value\": \"false\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"0423503f-e675-545e-8a9b-740c1b5f51ce\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"## Check\\n\\nNote: If there is a documented and approved mission requirement for data-at-rest to not be encrypted, this requirement is not applicable.\\n\\nVerify Ubuntu 24.04 LTS prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption.\\n\\nDetermine the partition layout for the system with the following command:\\n\\n```bash\\n$ sudo fdisk -l\\n(..)\\nDisk /dev/vda: 15 GiB, 16106127360 bytes, 31457280 sectors\\nUnits: sectors of 1 * 512 = 512 bytes\\nSector size (logical/physical): 512 bytes / 512 bytes\\nI/O size (minimum/optimal): 512 bytes / 512 byte [truncated]\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"check\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"assessment-method\",\n \"value\": \"TEST\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-001199\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002475\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002476\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-004910\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.1\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.3\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n },\n {\n \"uuid\": \"0820d37b-cdcb-5e32-a660-e1111ad328dc\",\n \"title\": \"Remediate: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"## Remediate\\n\\nTo encrypt an entire partition, dedicate a partition for encryption in the partition layout.\\n\\nNote: Encrypting a partition in an already-installed system is more difficult because it will need to be resized and existing partitions changed.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"remediate\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n }\n ],\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n },\n {\n \"control-id\": \"sc-28.1\"\n },\n {\n \"control-id\": \"sc-28.3\"\n }\n ]\n }\n ]\n },\n \"remarks\": \"Source SRG: SRG-OS-000185-GPOS-00079\\nDPMS Target identifier: 5673\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-sc28-v270747","language":"json","pointer":"/assessment-plan/local-definitions/activities/101","section":null,"sha256_of_source_file":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","title":"STIG activity V-270747, SC-28"},"data/snippets/ez-subjects-explicit.json":{"approach":"assessment-first","content":"[\n {\n \"type\": \"inventory-item\",\n \"description\": \"The M365 tenant instance being assessed. Assume it's defined in SSP.\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n]","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"4","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-subjects, one inventory item"},"data/snippets/ez-subjects-includeall.json":{"approach":"assessment-first","content":"[\n {\n \"type\": \"component\",\n \"description\": \"Target system being assessed against the STIG.\",\n \"include-all\": {}\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-subjects-includeall","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"4","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG assessment-subjects, include-all"},"data/snippets/ibm-ap-activity.json":{"approach":"component-first","content":"[\n {\n \"activities\": [\n {\n \"uuid\": \"a1b2c3d4-1111-4aaa-8888-111111111111\",\n \"description\": \"Execute Ansible checks to validate the controls.\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"check-ids\": [\n \"check-1\",\n \"check-2\"\n ]\n },\n {\n \"uuid\": \"b2c3d4e5-2222-4bbb-9999-222222222222\",\n \"description\": \"Execute OSCAP checks to validate the controls.\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984e8\",\n \"check-ids\": [\n \"check-1\",\n \"check-3\"\n ]\n }\n ]\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-activity","language":"json","pointer":"/assessment-plan/local-defintions","section":null,"sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"5","source":"IBM/assessment-plan.json","title":"AP activity, binding check-ids"},"data/snippets/ibm-ap-task-subjects.json":{"approach":"component-first","content":"{\n \"uuid\": \"b3504d22-0e75-4dd7-9247-618661beba4e\",\n \"type\": \"action\",\n \"title\": \"Execute Ansible Checks\",\n \"description\": \"The assessor will execute the Ansible checks defined in the validation component using the Ansible assessment platform to collect evidence for the assessment.\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"value\": \"d8c9a1e5-1c3b-4f0b-9c8e-2a1b2c3d4e5f\"\n }\n ],\n \"timing\": {\n \"at-frequency\": {\n \"period\": 1,\n \"unit\": \"days\"\n }\n },\n \"associated-activities\": [\n {\n \"activity-uuid\": \"a1b2c3d4-1111-4aaa-8888-111111111111\",\n \"subjects\": [\n {\n \"subject-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984fe\"\n }\n ]\n },\n {\n \"activity-uuid\": \"b2c3d4e5-2222-4bbb-9999-222222222222\",\n \"subjects\": [\n {\n \"subject-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984ff\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-task-subjects","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"4","source":"IBM/assessment-plan.json","title":"AP task, subjects and platform"},"data/snippets/ibm-ar-observation.json":{"approach":"component-first","content":"{\n \"uuid\": \"6c0a18ff-36b4-45b2-9e8b-6e3011bee6b1\",\n \"description\": \"check-result\",\n \"assessment-check-id\": \"check-1\",\n \"assessment-asset/component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984e8\",\n \"result\": \"pass\",\n \"props\": [\n {\n \"name\": \"idref\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"xccdf_org.ssgproject.content_rule_package_prelink_removed\"\n },\n {\n \"name\": \"result\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"pass\"\n },\n {\n \"name\": \"time\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"2025-02-26T03:47:26-05:00\"\n },\n {\n \"name\": \"severity\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"medium\"\n }\n ],\n \"methods\": [\n \"TEST-AUTOMATED\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"c8ca2d73-c917-4901-9098-71b2c601f471\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2025-02-26T12:45:58+00:00\"\n}","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","section":null,"sha256_of_source_file":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806","slot":"6b","source":"IBM/assessment-result.json","title":"AR observation, carrying a result"},"data/snippets/ibm-cos-component.json":{"approach":"component-first","content":"{\n \"uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\",\n \"type\": \"service\",\n \"title\": \"COS\",\n \"description\": \"COS\",\n \"rules\": [\n {\n \"id\": \"cos_access_endpoint_type\",\n \"description\": \"Ensure Cloud Object Storage is accessible only by using {param: endpoint_access} endpoints\",\n \"params\": [\n {\n \"id\": \"endpoint_access\",\n \"label\": \"Endpoint Access type\",\n \"select\": {\n \"how-many\": \"one\",\n \"choice\": [\n \"public\",\n \"private\",\n \"direct\"\n ]\n }\n }\n ]\n },\n {\n \"id\": \"cos_encryption_hyperprotect_key_configured\",\n \"description\": \"Ensure Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"08159454-994c-49ed-8f78-f2293b1274a2\",\n \"source\": \"trestle://profiles/ACME_official/profile.json\",\n \"description\": \"ACME Official Profile\",\n \"set-parameters\": [\n {\n \"param-id\": \"endpoint_access\",\n \"values\": [\n \"private\"\n ]\n }\n ],\n \"implemented-requirements\": [\n {\n \"uuid\": \"c6ccfcbc-4553-40e6-b4e8-eadbff8d4756\",\n \"control-id\": \"ac-4\",\n \"description\": \"This control is implmeneted by ensuring the COS is only available on private endpoints.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"cos_access_endpoint_type\"\n }\n ]\n },\n {\n \"uuid\": \"455563ca-c454-41d5-aa3b-f57843d95aab\",\n \"control-id\": \"sc-28\",\n \"description\": \"Ensure that data is encrypted and the key is managed by the customer.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"cos_encryption_hyperprotect_key_configured\"\n }\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-cos-component","language":"json","pointer":"/component-definition/components/0","section":null,"sha256_of_source_file":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a","slot":"1","source":"IBM/cos-component-definition.json","title":"COS component, carrying rules"},"data/snippets/ibm-statement-rules.json":{"approach":"component-first","content":"{\n \"uuid\": \"c6ccfcbc-4553-40e6-b4e8-eadbff8d4756\",\n \"control-id\": \"ia-5.1\",\n \"description\": \"\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"08cc185d-27d8-4412-9cb4-25ebf1397a39\",\n \"description\": \"\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"idservice_password_min_length\"\n },\n {\n \"rule-id\": \"idservice_strong_pass_enabled\"\n }\n ]\n },\n {\n \"statement-id\": \"ia-5.1_smt.e\",\n \"uuid\": \"89f1f3be-d915-4134-94ab-577cba3f3c9a\",\n \"description\": \"\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"idservice_password_not_reuse_min_count\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-statement-rules","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/0","section":null,"sha256_of_source_file":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf","slot":"2","source":"IBM/idservice-component-definition.json","title":"implementing-rules on ia-5.1"},"data/snippets/ibm-validation-ansible.json":{"approach":"component-first","content":"{\n \"component-definition\": {\n \"uuid\": \"bbdf7ee6-3e0a-4065-8ecf-50f4129de473\",\n \"metadata\": {\n \"title\": \"Demo validation component definition\",\n \"last-modified\": \"2026-05-15T14:29:37+00:00\",\n \"version\": \"1.0\",\n \"oscal-version\": \"1.2.1\"\n },\n \"components\": [\n {\n \"uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"type\": \"validation\",\n \"title\": \"ANSIBLE\",\n \"description\": \"ANSIBLE\",\n \"checks\": [\n {\n \"id\": \"check-1\",\n \"description\": \"Check Cloud Object Storage is accessible only by using private endpoints\",\n \"rule-id\": \"cos_access_endpoint_type\",\n \"target-component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\"\n },\n {\n \"id\": \"check-2\",\n \"description\": \"Check Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)\",\n \"rule-id\": \"cos_encryption_hyperprotect_key_configured\",\n \"target-component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\"\n }\n ]\n }\n ]\n }\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-validation-ansible","language":"json","pointer":"$","section":null,"sha256_of_source_file":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","slot":"3","source":"IBM/ansible-validation-component-definition.json","title":"Ansible validation component, and its checks"},"data/source-files.json":{"excluded":[{"path":"disa/U_Readme_SRG_and_STIG.pdf","why":"About the STIG and SRG packages as a set rather than about any one guide, so it has no row in a table of one row per guide."},{"path":"oscal","why":"The OSCAL representations of this guidance are published separately. This table lists the documents read as input, not what was written from them."}],"files":[{"bytes":1032133,"guidance":"cis-postgresql-18","href":"sources/cis/CIS_PostgreSQL_18_Benchmark_v1.0.0.json","kind":"source","media":"json","media_label":"JSON document","mime":"application/json","name":"CIS_PostgreSQL_18_Benchmark_v1.0.0.json","publisher":"cis","sha256":"b72eda73c5bef60e2971c93261bc226594cfb8d8aa1be92deb6b2e121bf05379","size":"1.0 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":1506309,"guidance":"cis-postgresql-18","href":"sources/cis/CIS_PostgreSQL_18_Benchmark_v1.0.0.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"CIS_PostgreSQL_18_Benchmark_v1.0.0.pdf","publisher":"cis","sha256":"eae098af712ef333be2ebb146e72d8cdcba9f740f3a99e15de8363055f49f1b9","size":"1.5 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":6823924,"guidance":"cis-ubuntu-24-04","href":"sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","kind":"source","media":"json","media_label":"JSON document","mime":"application/json","name":"CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","publisher":"cis","sha256":"1a90fccb4442decd119382233ff8986caaaeede83dcf3c5ab22a87c747ab0c81","size":"6.8 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":10372494,"guidance":"cis-ubuntu-24-04","href":"sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.pdf","publisher":"cis","sha256":"8ebe23d21c23e383c81620ad04655e3b1d8fdf0b6eb9ddfdb7a97d0a5b5e7ef1","size":"10.4 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":640043,"guidance":"disa-ubuntu-22-04","href":"sources/disa/U_CAN_Ubuntu_22-04_LTS_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CAN_Ubuntu_22-04_LTS_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"73c26b6592dfc02f7f0eb456e0f89143ea1e2d8af7ebc61bd8bfae01f5a4c9d8","size":"640 kB","terms":"Public domain. A work of the United States Government."},{"bytes":658230,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml","publisher":"disa","sha256":"4c527cf0ed912947bb0c51be15f1a6bbc5a4bf05469ae083d94a01471edea77c","size":"658 kB","terms":"Public domain. A work of the United States Government."},{"bytes":934796,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1_Release_Memo.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_STIG_V1_Release_Memo.pdf","publisher":"disa","sha256":"9c3292baa367f97d0dc8c8a235a77dd49acfe53598d667902ab3e1e7d3d3d9a0","size":"935 kB","terms":"Public domain. A work of the United States Government."},{"bytes":425770,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_V1R5_Overview.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_V1R5_Overview.pdf","publisher":"disa","sha256":"7b4e8bc528e6e23c9bac33b760793d86e6d4954ff724f9db1e108ef071a22c8e","size":"426 kB","terms":"Public domain. A work of the United States Government."},{"bytes":301891,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_V1R5_Revision_History.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_V1R5_Revision_History.pdf","publisher":"disa","sha256":"3f00fb641e059376fb8b8d4404e3e2abf0a6a95950568740172086c441457a56","size":"302 kB","terms":"Public domain. A work of the United States Government."},{"bytes":456124,"guidance":"disa-postgres-16","href":"sources/disa/U_CD_Postgres_16_STIG_V1R2_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CD_Postgres_16_STIG_V1R2_Manual-xccdf.xml","publisher":"disa","sha256":"d468632da49f29b1616347dc7d79f429ff72ded2685a2ffb55b416d76192ce32","size":"456 kB","terms":"Public domain. A work of the United States Government."},{"bytes":432719,"guidance":"disa-epas","href":"sources/disa/U_EPAS_STIG_V2R1_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_EPAS_STIG_V2R1_Manual-xccdf.xml","publisher":"disa","sha256":"c9a9fb2f652495433a3639f740ef08d856c722be5d8bfdb729c87f843f3767ec","size":"433 kB","terms":"Public domain. A work of the United States Government."},{"bytes":936441,"guidance":"disa-windows-2019","href":"sources/disa/U_MS_Windows_Server_2019_STIG_V3R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2019_STIG_V3R8_Manual-xccdf.xml","publisher":"disa","sha256":"f483e86fdaf1caf0ad904b99ae117667fb61e48e0f62fbbcbd4ac30facef0e36","size":"936 kB","terms":"Public domain. A work of the United States Government."},{"bytes":906114,"guidance":"disa-windows-2022","href":"sources/disa/U_MS_Windows_Server_2022_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2022_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"991ad360c2ca40c5ab743b22b045ac9a98134a2c7360983ae32a1dac62de65de","size":"906 kB","terms":"Public domain. A work of the United States Government."},{"bytes":913750,"guidance":"disa-windows-2025","href":"sources/disa/U_MS_Windows_Server_2025_STIG_V1R1_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2025_STIG_V1R1_Manual-xccdf.xml","publisher":"disa","sha256":"5ae22836beba53091fa6269eaa974e54c226f3e2113cc9a3ec0183a8e16f51ee","size":"914 kB","terms":"Public domain. A work of the United States Government."},{"bytes":1267893,"guidance":"disa-rhel-8","href":"sources/disa/U_RHEL_8_STIG_V2R7_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_RHEL_8_STIG_V2R7_Manual-xccdf.xml","publisher":"disa","sha256":"9c5c57f34c78e3c70d5bc9755169b99f9e6965509b8e06f277c82982bccc8411","size":"1.3 MB","terms":"Public domain. A work of the United States Government."},{"bytes":1397262,"guidance":"disa-rhel-9","href":"sources/disa/U_RHEL_9_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_RHEL_9_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"bcb1c86161034ced8accca81f15efe40d4e4cfdce003b6b2b456cb49fcd094e3","size":"1.4 MB","terms":"Public domain. A work of the United States Government."}],"media_types":{"json":{"label":"JSON document","mime":"application/json"},"pdf":{"label":"PDF document","mime":"application/pdf"},"xml":{"label":"XML document","mime":"application/xml"}},"not_copied":[{"publisher":"cisa","what":"The SCuBA secure configuration baselines themselves","where":null,"where_label":null,"why":"The baselines are published by CISA and no copy of them is held here. What was read for this analysis was the baseline content as converted, and those conversions are published separately."},{"publisher":"aws","what":"The Security Hub controls, as published","where":"https://github.com/awslabs/oscal-content-for-aws-services","where_label":"oscal-content-for-aws-services","why":"This publisher ships its guidance as OSCAL already, so there is no separate source document to hold. The published content is linked rather than copied, so there is one copy to keep current."}],"not_shipped":[{"path":"cis","why":"Held locally, not redistributed. Download the Benchmarks from cisecurity.org into sources/cis/ under the filenames recorded here to rebuild anything that reads them."}],"note":"Every file under sources/, with its media type and size read from disk, and the benchmark row it belongs to. Built by tools/sources_files.py; verified by tools/verify.py --sources, which fails if a link points at a missing file, a file sits in the folder unlinked, or a file names a row that does not exist.","totals":{"bytes":29005893,"files":16,"size":"29.0 MB"}},"data/sources.json":{"columns":["Publisher","Guidance","Source form held"],"note":"The hardening guidance read as input to this analysis, one row per benchmark or guide rather than one per publisher, because the unit a reader recognises is the benchmark. Each row carries the documents read for it: a file icon downloads one file, a globe opens the publisher's page. What was written from this guidance, in OSCAL, is published separately and is not a column here; it is kept under 'publishers' so tools/verify.py --sources can still recompute it against the corpora.","publishers":{"aws":{"derivation":"AWS/oscal-content-for-aws-services-main: catalogs/*.oscal.json and component-definitions/*.oscal.json","full_name":"Amazon Web Services","name":"AWS","oscal_counts":{"catalogs":1,"component_definitions":230,"controls":452,"groups":77},"oscal_form":"one catalog of 452 controls across 77 groups, and 230 component definitions","source_counts":{}},"cis":{"derivation":"assessment-plan documents under Easy Dynamics/Center for Internet Security; source files under Hardening Guides/Center for Internet Security","full_name":"Center for Internet Security","name":"CIS","oscal_counts":{"assessment_plans":2},"oscal_form":"two assessment plans","source_counts":{"pdf":2,"xccdf_json":2}},"cisa":{"derivation":"assessment-plan documents under Easy Dynamics/CISA BOD 25-01; no publisher source material is present","full_name":"Cybersecurity and Infrastructure Security Agency","name":"CISA","oscal_counts":{"assessment_plans":4,"assessment_results":1},"oscal_form":"four assessment plans and one assessment result","source_counts":{}},"disa":{"derivation":"assessment-plan documents under Easy Dynamics/DISA; *-xccdf.xml under Hardening Guides/DISA","full_name":"Defense Information Systems Agency","name":"DISA","oscal_counts":{"assessment_plans":9},"oscal_form":"nine assessment plans","source_counts":{"xccdf_xml":9}}},"rows":[{"guidance":"Ubuntu Linux 24.04 LTS Benchmark","key":"cis-ubuntu-24-04","publisher":"cis","source_form":"XCCDF-derived JSON, and PDF","version":"v1.0.0"},{"guidance":"PostgreSQL 18 Benchmark","key":"cis-postgresql-18","publisher":"cis","source_form":"XCCDF-derived JSON, and PDF","version":"v1.0.0"},{"guidance":"Ubuntu 22.04 LTS STIG","key":"disa-ubuntu-22-04","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Ubuntu 24.04 LTS STIG","key":"disa-ubuntu-24-04","publisher":"disa","source_form":"XCCDF XML, and three release notes","version":"V1R5"},{"guidance":"Red Hat Enterprise Linux 8 STIG","key":"disa-rhel-8","publisher":"disa","source_form":"XCCDF XML","version":"V2R7"},{"guidance":"Red Hat Enterprise Linux 9 STIG","key":"disa-rhel-9","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Windows Server 2019 STIG","key":"disa-windows-2019","publisher":"disa","source_form":"XCCDF XML","version":"V3R8"},{"guidance":"Windows Server 2022 STIG","key":"disa-windows-2022","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Windows Server 2025 STIG","key":"disa-windows-2025","publisher":"disa","source_form":"XCCDF XML","version":"V1R1"},{"guidance":"PostgreSQL 16 STIG","key":"disa-postgres-16","publisher":"disa","source_form":"XCCDF XML","version":"V1R2"},{"guidance":"EDB Postgres Advanced Server STIG","key":"disa-epas","publisher":"disa","source_form":"XCCDF XML","version":"V2R1"},{"guidance":"BOD 25-01, the SCuBA baselines","key":"cisa-bod-25-01","links":[{"href":"https://www.cisa.gov/resources-tools/services/bod-25-01-implementing-secure-practices-cloud-services-required-configurations","kind":"web","label":"BOD 25-01, on the publisher's site"}],"publisher":"cisa","source_form":"None held here","version":null},{"guidance":"Security Hub security best-practice controls","key":"aws-security-hub","links":[{"href":"https://aws.github.io/aws-security-services-best-practices/guides/security-hub/","kind":"web","label":"Security Hub best practices, on the publisher's site"},{"href":"https://github.com/awslabs/oscal-content-for-aws-services","kind":"web","label":"The same controls as OSCAL, in the publisher's repository"}],"publisher":"aws","source_form":"Published as OSCAL, and linked","version":null}],"summary":"Hardening guidance used as input","summary_sub":"Two CIS Benchmarks, nine DISA STIGs, CISA BOD 25-01 and the AWS Security Hub controls, with the documents read for each."},"data/stakeholders.json":{"approaches":{"assessment-first":{"auditor":{"flows":[{"from":[{"model":"assessment-plan"}],"makes":"the observations","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor's run produces assessment results, not implementation claims. The workflow does not update the system security plan."},"benchmark":{"note":"The guidance provider writes activities and steps. The policy engine provider supplies executable checks.","writes":[{"model":"assessment-plan"}]},"engine":{"note":"The policy engine provider adds checks to the assessment plan. The plan identifies the engine in assessment-assets.","writes":[{"model":"assessment-plan"}]},"mapper":{"note":"The mapping provider edits the assessment plan, naming the framework controls covered by the activity.","writes":[{"model":"assessment-plan"}]},"owner":{"note":"The system owner supplies the profile and system security plan. The assessor's workflow does not depend on the owner's automation.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"note":"The technology provider writes activities and steps. The policy engine provider supplies executable checks.","writes":[{"model":"assessment-plan"}]}},"catalog-first":{"auditor":{"flows":[{"from":[{"kind":"software","model":"component-definition"}],"makes":"the findings","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor runs the checks independently. The resulting finding targets the system owner's implementation statement."},"benchmark":{"writes":[{"model":"catalog"}]},"engine":{"note":"The provider publishes checks as components of type software, referencing the guidance authors' catalog. System owners and auditors run the checks.","writes":[{"kind":"software","model":"component-definition"}]},"mapper":{"note":"The mapping provider writes a separate framework mapping. The published corpus contains no mapping collection for hardening guidance.","writes":[{"model":"mapping-collection"}]},"owner":{"flows":[{"from":[{"kind":"software","model":"component-definition"}],"makes":"the control-implementation responses","runtime":true,"to":[{"model":"system-security-plan"}]}],"note":"The system owner selects requirements and merges catalogs through a profile imported by the system security plan.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"writes":[{"model":"catalog"}]}},"component-first":{"auditor":{"flows":[{"from":[{"model":"assessment-plan"}],"makes":"the observations","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor runs checks through an assessment plan, allowing the result to identify a host rather than a component."},"benchmark":{"writes":[{"kind":"software","model":"component-definition"}]},"engine":{"note":"The provider publishes checks in a component of type validation. System owners and auditors run the checks.","writes":[{"kind":"validation","model":"component-definition"}]},"mapper":{"note":"The mapping provider edits a component definition. Whether the rules or the checks carry the framework mapping remains open.","writes":[{"kind":"software or validation","model":"component-definition"}]},"owner":{"flows":[{"from":[{"kind":"validation","model":"component-definition"}],"makes":"the control-implementation responses","runtime":true,"to":[{"model":"system-security-plan"}]}],"writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"writes":[{"kind":"software","model":"component-definition"}]}}},"groups":[{"key":"guidance","label":"Hardening guidance authors","note":"Benchmark publishers and technology providers author guidance in the same OSCAL model for each approach."},{"key":"automation","label":"Automation providers and operators","note":"Providers build policy engines. System owners and auditors run checks to produce implementation responses or assessment results."}],"intro":"Seven parties publish, implement or assess hardening guidance. The table maps each party to OSCAL models and groups guidance authors separately from automation providers and operators.","note":"The mapping identifies the OSCAL models used by seven parties from guidance publication through audit. Component types distinguish guidance from checks where both use component definitions. Two groups identify guidance authors and automation providers and operators. Policy engine providers build tools; system owners and auditors execute the flows shown. Mapping providers are separate because guidance authors do not always publish framework mappings: STIGs carry CCIs, DISA's CCI list names the 800-53 controls, and third parties publish mappings through NIST's OLIR programme.","parties":[{"key":"regulatory","name":"Regulatory control providers","who":"NIST and other bodies publishing regulatory controls, such as SP 800-53"},{"key":"mapper","name":"Mapping providers","who":"Organisations linking guidance to frameworks through DISA's CCI list, NIST's OLIR programme or the Secure Controls Framework"},{"group":"guidance","key":"benchmark","name":"Technical hardening guidance providers","who":"CIS, DISA and other benchmark publishers"},{"group":"guidance","key":"software","name":"Technology providers","who":"Vendors publishing configuration guidance for hardware, software and services, independently or with benchmark publishers such as CIS"},{"group":"automation","key":"engine","name":"Policy engine providers","who":"Providers of assessment and checking tools such as OPA, Kyverno, ScubaGear and OpenSCAP"},{"group":"automation","key":"owner","name":"System owners","who":"Organisations implementing and documenting controls on a system"},{"group":"automation","key":"auditor","name":"Independent auditors","who":"Assessors running checks and reviewing results independently of system owners"}],"runtime":"A policy engine reads OSCAL, executes checks and writes OSCAL. Providers publish the checks; each flow identifies the party executing the checks."},"data/tradeoffs.json":{"approaches":{"assessment-first":{"cons":[{"body":"The activity title contains the required value, so changing the value requires editing the plan rather than resolving a profile.","title":"Required values lack resolvable parameters"},{"body":"The model provides activities and steps, so guidance nested four levels deep must be represented within those two structural tiers.","title":"Guide hierarchy is limited to two tiers"},{"body":"The published result references a plan absent from the corpus and assigns an observation a subject type not defined by the model.","title":"Published references and types need correction"}],"intro":"Publishing technical hardening guidance as an assessment plan has these strengths and risks.","pros":[{"body":"The assessment plan references implementation claims without adding claims, so adding or retiring a guide does not change the system security plan.","title":"Guidance stays outside the plan of record"},{"body":"A separate assessment results document imports a plan; the corpus includes findings that target objectives and reference supporting observations.","title":"Assessment results reference an assessment plan"},{"body":"An assessment subject can be an inventory item, allowing separate findings for two hosts running one operating system with different configurations.","title":"Subjects can identify individual hosts"},{"body":"Tasks carry schedules and identify execution platforms, placing the timing and runtime context for checks in the assessment plan.","title":"The plan records execution context"}]},"catalog-first":{"cons":[{"body":"The system security plan must address benchmark requirements alongside regulatory controls; whether each additional catalog requires a separate plan remains unsettled.","title":"Benchmark catalogs add maintenance work"},{"body":"Multiple frameworks and benchmarks require catalogs, profiles and mappings to be maintained together, increasing tool integration work and profile resolution complexity.","title":"Combined baselines complicate profile resolution"},{"body":"A by-component response identifies a component, not an instance, so one exception among a hundred hosts sharing that component cannot be distinguished.","title":"Responses do not identify individual instances"}],"intro":"Publishing technical hardening guidance as a catalog has these strengths and risks.","pros":[{"body":"Technical requirements use catalog controls and follow the same references through the remaining OSCAL models as regulatory controls.","title":"Technical and regulatory requirements use one model"},{"body":"A profile selects the hardening requirements an organisation adopts and sets organisationally defined parameters without changing the source catalog.","title":"Rules can be tailored"},{"body":"Controls, parts and nested groups represent checks, remediation and explanatory prose, including the structure of a thousand-page guide.","title":"Catalog structures represent guide content"},{"body":"A separate mapping-collection links guidance to a framework, allowing a third party to publish the mapping without owning either catalog.","title":"Third parties can publish framework mappings"}]},"component-first":{"cons":[{"body":"The proposal changes component definitions, system security plans, assessment plans and assessment results; existing schema support does not cover the proposed assemblies.","title":"Four models require schema changes"},{"body":"Rules describing the required component configuration enter the system security plan, which documents the system's implemented controls and current configuration.","title":"Desired state enters the plan of record"},{"body":"Rationale, audit procedure and remediation provide guidance context, but the published rules omit these fields and support remains proposed.","title":"Published rules omit guide context"},{"body":"A by-component response can reference a rule but not an individual instance, so exceptions remain associated with the component.","title":"Responses do not identify individual instances"},{"body":"Inventory items would also need implementing-rules support for a claim to identify a host rather than a component class.","title":"Host-level claims may require inventory support"}],"intro":"Publishing technical hardening rules in a component definition has these strengths and risks.","pros":[{"body":"A component definition describes how a product can meet controls; the proposed rules provide configuration requirements for automation in the same document.","title":"One artifact describes capability and supports automation"},{"body":"The product component holds the rule and a validation component holds the check; a second engine uses a second validation component.","title":"Rules and checks remain separate"},{"body":"The proposed implementing-rules assembly links a control implementation claim to the rule used to satisfy the control.","title":"Implementation claims can reference rules"},{"body":"Existing guidance directs technology providers to describe product capabilities in component definitions, where the proposal would also place hardening rules.","title":"Technology providers can extend component descriptions"}]}},"note":"Strengths and risks for each approach. Entry counts may differ; tools/approach_pages.py enforces prose budgets within and across approaches. Scenario figures remain on the scenario page. BUILD-LOG.md records the basis for each entry. Where present, schema_evidence identifies checked schema fragments and is not rendered."},"data/views.json":{"automation_argument":{"claim":"The automation argument treats applying and verifying hardening guidance as operational work, not just a finer-grained form of regulatory control. Automation coverage varies across the published guides.","claim_not_made":"Hardening guidance is never performed manually. The corpus includes manual procedures and does not support that claim.","evidence":[{"automated":"2271 activities carry method TEST","corpus":"STIG, all 9 files","manual":"none","stat_keys":["stig_method_test"]},{"automated":"576 steps","corpus":"CIS Ubuntu 24.04","manual":"40 steps","stat_keys":["cis_ubuntu_automated","cis_ubuntu_manual"]},{"automated":"0 steps","corpus":"CIS PostgreSQL 18","manual":"144 steps, covering every step; every activity carries method EXAMINE","note":"This guide provides a counterexample to the claim that all hardening procedures are automated.","stat_keys":["cis_postgres_automated","cis_postgres_manual"]}]},"crux":{"note":"Model placement alone does not establish whether guidance is binding. Every approach needs a way to distinguish requirements from optional configurations or assessment procedures."},"note":"Three editorial interpretations of a hardening rule, ordered by OSCAL layer rather than rank. The analysis uses a working definition without selecting an interpretation. Each view links to a stakeholder glossary term.","views":[{"aligned_approach":"catalog-first","definition":"A binding requirement, expressed as a shall. A rule differs from a regulatory control in specificity.","implies_layer":"Control","implies_model":"catalog","key":"requirement","label":"A requirement","stakeholder":"publisher"},{"aligned_approach":"component-first","definition":"A description of possible component configurations. The technology provider describes capabilities; the adopting organisation sets requirements.","implies_layer":"Implementation","implies_model":"component-definition","key":"capability","label":"A capability statement","stakeholder":"implementer"},{"aligned_approach":"assessment-first","definition":"A procedure for applying or verifying hardening guidance. Assessment activities and steps describe the work, with executable checks referenced for automation.","implies_layer":"Assessment","implies_model":"assessment-plan","key":"procedure","label":"An assessor's procedure","stakeholder":"assessor"}],"why_this_matters":"OSCAL has no dedicated core requirement-level field distinguishing shall, should and may. The gap affects every approach; model placement alone cannot establish whether guidance expresses requirements, capabilities or assessment procedures.","working_definition":{"status":"A working definition for comparing the three approaches without selecting an interpretation.","term":"rule","text":"One technical requirement or recommendation, finer-grained than a control, without any claim about whether it is binding."}}};
+window.TFGBundle = {"analysis.json":{"approaches":[{"id":"a","name":"Catalog-first","path":"catalog-first.html"},{"id":"b","name":"Component-first","path":"component-first.html"},{"id":"c","name":"Assessment-first","path":"assessment-first.html"}],"concluded":null,"corpora":{"note":"Repository-defined inputs: 6 committed IBM and 18 committed Easy Dynamics JSON files, checked against data/examples.json fingerprints, plus 231 public AWS JSON files from the pinned archive and verified cache declared in the lock. Prepare explicitly with python tools/source_inputs.py --fetch; python tools/source_inputs.py --check verifies inputs offline. Missing or corrupt inputs fail rather than being skipped or counted as empty.","source_lock":"tools/source-lock.json"},"forum":"OSCAL Foundation Technical Focus Group on Automated Assessments","id":"2026-08-automating-technical-hardening-guidance","makesRecommendation":false,"makesRecommendationNote":"By design, not because the effort is unfinished. The site states three approaches in the terms their proponents use, prices what each one costs, and stops. A reader looking for a verdict should not infer that one is pending.","openItems":["Proponent review has not happened. No request for corrections has been sent to the publishers of the three bodies of content, so none has been received and nobody has declined."],"opened":"2026-08-12","question":"Where does technical hardening guidance live in OSCAL, and how does an automated check attach to it?","recommendation":null,"status":"active","summary":"Three organizations have published working OSCAL content that answers the same question three different ways. This site puts the three side by side against the same six questions, writes the same two rules out in all three shapes so that the only thing differing between the columns is the modelling, and names the join key that makes each one work.","supersededBy":null,"supersedes":null,"title":"Automating Technical Hardening Guidance with OSCAL","verification":{"command":"python tools/verify.py --all","note":"Every figure and extract on the site is recomputed from a published file. A skipped check is reported separately and never counted as a pass.","workflow":".github/workflows/verify-2026-08-hardening-guidance.yml"}},"assets/diagrams/710-scenario-assessment.svg":"\n","assets/diagrams/710-scenario-catalog.svg":"\n","assets/diagrams/710-scenario-component.svg":"\n","assets/diagrams/73-join-assessment.svg":"\n","assets/diagrams/73-join-catalog.svg":"\n","assets/diagrams/73-join-component.svg":"\n","assets/diagrams/75-stakeholders.svg":"\n","assets/diagrams/76-satisfaction-6a-6b.svg":"\n","data/corpus-stats.json":{"generated_from":"repository-defined inputs in tools/source-lock.json","note":"Every figure the site cites, with the derivation that tools/verify.py --stats recomputes from the source corpora. A mismatch is a hard failure.","stats":[{"derivation":"len(catalog.groups) in AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","key":"aws_groups","label":"groups in the AWS Security Hub catalog","value":77},{"derivation":"sum(len(g.controls) for g in catalog.groups) in aws_security-hub.oscal.json","key":"aws_controls","label":"controls in the AWS Security Hub catalog","value":452},{"derivation":"count of AWS/oscal-content-for-aws-services-main/component-definitions/*.oscal.json","key":"aws_cdef_files","label":"AWS component definition files","value":230},{"derivation":"count of components with type == 'software' across all AWS component-definitions","key":"aws_software_components","label":"AWS Config rules modelled as software components","value":429},{"derivation":"count of software-component implemented-requirements where catalog control's assessment-method part title == component title","key":"aws_title_matches","label":"software component titles matching the catalog TechnicalControlId, out of 429","value":429},{"derivation":"452 minus the count of distinct control-ids cited by software components","key":"aws_controls_without_check","label":"catalog controls with no software check component","value":29},{"derivation":"452 minus the count of distinct control-ids cited by any component","key":"aws_controls_unreferenced","label":"catalog controls referenced by no component at all","value":14},{"derivation":"sum(len(component.rules)) across cos- and idservice-component-definition.json","key":"ibm_rules","label":"rules in the IBM component definitions","value":5},{"derivation":"sum(len(component.checks)) across ansible- and oscap-validation-component-definition.json","key":"ibm_checks","label":"checks in the IBM validation component definitions","value":5},{"derivation":"count of distinct implemented-requirements.control-id across cos and idservice","key":"ibm_control_ids","label":"distinct control-ids covered by the IBM component definitions","value":9},{"derivation":"sum(len(assessment-plan.local-definitions.activities)) across the 15 Easy Dynamics assessment plans","key":"ez_activities","label":"assessment plan activities across the Easy Dynamics corpus","value":2425},{"derivation":"sum(len(activity.steps)) across the 15 Easy Dynamics assessment plans","key":"ez_steps","label":"assessment plan steps across the Easy Dynamics corpus","value":5694},{"derivation":"count of activity props where name == 'method' and value == 'TEST' across the 9 STIG files; no other method value occurs","key":"stig_method_test","label":"STIG activities carrying method TEST, out of 2271","value":2271},{"derivation":"count of step props where name == 'assessment-status' and value == 'automated' in CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","key":"cis_ubuntu_automated","label":"CIS Ubuntu 24.04 steps marked automated","value":576},{"derivation":"same file, value == 'manual'","key":"cis_ubuntu_manual","label":"CIS Ubuntu 24.04 steps marked manual","value":40},{"derivation":"count of step props where name == 'assessment-status' and value == 'automated' in CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","key":"cis_postgres_automated","label":"CIS PostgreSQL 18 steps marked automated","value":0},{"derivation":"same file, value == 'manual'","key":"cis_postgres_manual","label":"CIS PostgreSQL 18 steps marked manual","value":144},{"derivation":"count of Easy Dynamics/STIG_XCCDF to OSCAL Assessment Plans/*.json","key":"stig_files","label":"STIG assessment plan files","value":9},{"derivation":"count of STIG files where assessment-plan.import-ssp.href == 'PLACEHOLDER'","key":"stig_placeholder","label":"STIG files whose import-ssp.href is the literal string PLACEHOLDER","value":9},{"derivation":"count of AWS/oscal-content-for-aws-services-main/catalogs/*.oscal.json","key":"aws_catalog_files","label":"AWS catalog files","value":1},{"derivation":"count of files under Easy Dynamics/** whose root element is assessment-plan. The corpus also holds one assessment-results file and two non-OSCAL benchmark files, which this does not count","key":"ez_files","label":"Easy Dynamics assessment plan files","value":15},{"derivation":"count of IBM/*component-definition.json","key":"ibm_cdef_files","label":"IBM component definition files","value":4},{"derivation":"count of IBM/assessment-plan.json","key":"ibm_ap_files","label":"IBM assessment plan files","value":1},{"derivation":"count of IBM/assessment-result.json","key":"ibm_ar_files","label":"IBM assessment result files","value":1},{"derivation":"recursive count of every props array across Easy Dynamics/**/*.json","key":"ez_props","label":"props across the Easy Dynamics assessment plans","value":55458},{"derivation":"recursive count of every props array across AWS/oscal-content-for-aws-services-main/**/*.json","key":"aws_props","label":"props across the AWS catalog and component definitions","value":6094},{"derivation":"recursive count of every props array across IBM/*component-definition.json","key":"ibm_cdef_props","label":"props across the four IBM component definitions","value":0},{"derivation":"sum(1 for g in catalog.groups if g.groups) in aws_security-hub.oscal.json","key":"aws_nested_groups","label":"AWS catalog groups that themselves contain groups","value":0},{"derivation":"sum(len(c.params) for g in catalog.groups for c in g.controls)","key":"aws_control_params","label":"params declared on AWS catalog controls","value":0},{"derivation":"count of AWS/**/*.json whose root key is profile","key":"aws_profile_files","label":"profile files in the AWS corpus","value":0},{"derivation":"count of Easy Dynamics/CISA BOD 25-01/*.json","key":"cisa_files","label":"CISA BOD 25-01 files: four assessment plans, one assessment result and the sample SSP they import","value":6},{"derivation":"count of step props named criticality with value SHALL in Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","key":"cisa_criticality_shall","label":"steps carrying criticality SHALL in ap-cisa-scuba-agnostic.json","value":73},{"derivation":"count of step props named criticality with value SHOULD in the same file","key":"cisa_criticality_should","label":"steps carrying criticality SHOULD in ap-cisa-scuba-agnostic.json","value":55},{"derivation":"count of objects carrying a string type together with include-all or include-subjects, where type is component","key":"ez_subjects_component","label":"assessment-subject blocks typed component across the Easy Dynamics corpus","value":2407},{"derivation":"same walk, where type is inventory-item","key":"ez_subjects_inventory_item","label":"assessment-subject blocks typed inventory-item across the Easy Dynamics corpus, including the one on each CISA associated activity","value":26},{"derivation":"len(assessment-results.results[0].findings) in IBM/assessment-result.json. The file also carries a findings array at the document root, outside results, where the model does not define one","key":"ibm_ar_findings","label":"findings inside the result object of the IBM assessment result","value":0},{"derivation":"len(assessment-results.results[0].observations) in IBM/assessment-result.json","key":"ibm_ar_observations","label":"observations in the IBM assessment result","value":1},{"derivation":"sum(1 for a in every assessment-plan.local-definitions.activities if a.related-controls) across Easy Dynamics/**/*.json","key":"ez_activities_with_related_controls","label":"assessment plan activities carrying related-controls, out of 2425","value":2279},{"derivation":"sum(1 for ir in every control-implementation.implemented-requirements if not ir.implementing-rules) across IBM/*component-definition.json","key":"ibm_ir_without_rules","label":"IBM implemented-requirements listing no implementing rule, out of 9","value":1},{"derivation":"count of assessment plans under Easy Dynamics/Center for Internet Security/","key":"cis_ap_files","label":"CIS assessment plan files","value":2},{"derivation":"size of the set of control-id values under reviewed-controls.control-selections[].include-controls[] in the two CIS plans","key":"cis_control_ids","label":"distinct control ids referenced across the CIS assessment plans","value":82},{"derivation":"distinct control ids under a control-selection whose props carry resolution-status = synthetic-ids","key":"cis_synthetic_ids","label":"control ids the content itself flags as synthetic","value":53},{"derivation":"count, not set size, of include-control entries under a control-selection flagged resolution-status = synthetic-ids","key":"cis_synthetic_refs","label":"references to those 53 synthetic control ids","value":84},{"derivation":"count of props name=step-type value=remediate across the 15 Easy Dynamics assessment plans","key":"ez_step_type_remediate","label":"steps carrying step-type remediate, all in the STIG plans","value":2271},{"derivation":"count of props name=step-type value=remediation across the 15 Easy Dynamics assessment plans","key":"ez_step_type_remediation","label":"steps carrying step-type remediation, all in the CIS plans","value":380},{"derivation":"count of props name=step-type value=check across the 15 Easy Dynamics assessment plans","key":"ez_step_type_check","label":"steps carrying step-type check, all in the STIG plans","value":2271},{"derivation":"count of props name=step-type value=audit across the 15 Easy Dynamics assessment plans","key":"ez_step_type_audit","label":"steps carrying step-type audit, all in the CIS plans","value":380},{"derivation":"size of the set of sorted step-type value sets, grouped by the directory each plan sits in","key":"ez_step_type_vocabularies","label":"distinct step-type vocabularies in use across the two benchmark families","value":2},{"derivation":"count of files under Easy Dynamics/** whose root element is assessment-results","key":"ez_ar_files","label":"assessment results in the corpus","value":1},{"derivation":"count of files in Easy Dynamics/** whose root element is system-security-plan","key":"ez_ssp_files","label":"system security plans in the corpus: the sample SSP the CISA plans import","value":1},{"derivation":"count of role-id keys valued 'owner' at any depth in AWS/**/component-definitions/*.oscal.json","key":"aws_owner_refs","label":"references to role-id owner across the AWS component definitions","value":429},{"derivation":"count of AWS component definition files containing at least one role-id valued 'owner'","key":"aws_files_referencing_owner","label":"component definition files referencing role-id owner","value":67},{"derivation":"count of metadata.roles entries with id 'author', by file","key":"aws_files_declaring_author","label":"component definition files declaring the role author","value":230},{"derivation":"size of the set of metadata.roles[].id across all 230 AWS component definition files","key":"aws_roles_declared","label":"distinct roles declared anywhere in the AWS component definitions","value":1},{"derivation":"count of control parts with name='guidance' in aws_security-hub.oscal.json","key":"aws_guidance_parts","label":"guidance parts across the catalog controls, one per control","value":452},{"derivation":"size of the set of prose values among control parts named 'guidance'","key":"aws_guidance_distinct","label":"distinct guidance prose strings among the guidance parts","value":1},{"derivation":"count of catalog.groups entries whose id is exactly 'TestControl'","key":"aws_test_groups","label":"catalog groups with the id TestControl","value":1},{"derivation":"sum(len(g.controls)) over catalog groups with id 'TestControl'","key":"aws_test_controls","label":"controls inside the TestControl group","value":1},{"derivation":"count of TestControl controls with a rel='remediation' link whose href does not contain the control's own service prefix","key":"aws_test_controls_mislinked","label":"TestControl controls whose remediation link names a different control","value":1},{"derivation":"count of files in AWS/** whose root element is system-security-plan","key":"aws_ssp_files","label":"system security plans in the corpus","value":0},{"derivation":"count of files in AWS/** whose root element is assessment-plan","key":"aws_ap_files","label":"assessment plans in the corpus","value":0},{"derivation":"count of files in AWS/** whose root element is assessment-results","key":"aws_ar_files","label":"assessment results in the corpus","value":0},{"derivation":"size of the set of component-definition.uuid across IBM/*component-definition.json","key":"ibm_document_uuids","label":"distinct document uuids across the 4 IBM component definition files","value":1},{"derivation":"sum(len(c.checks)) over components in IBM/oscap-validation-component-definition.json","key":"ibm_oscap_checks","label":"checks in the OSCAP validation component","value":3},{"derivation":"count of OSCAP checks whose target-component-uuid is not a component uuid declared in any of the 4 IBM component definitions","key":"ibm_oscap_checks_dangling","label":"OSCAP checks whose target-component-uuid resolves to no component","value":3},{"derivation":"sum(len(c.checks)) over components in IBM/ansible-validation-component-definition.json","key":"ibm_ansible_checks","label":"checks in the ANSIBLE validation component","value":2},{"derivation":"count of ANSIBLE checks whose target-component-uuid is not a component uuid declared in any of the 4 IBM component definitions","key":"ibm_ansible_checks_dangling","label":"ANSIBLE checks whose target-component-uuid resolves to no component","value":0},{"derivation":"1 if the IBM assessment plan carries a 'local-defintions' key and no 'local-definitions' key, else 0","key":"ibm_ap_local_definitions_misspelled","label":"assessment plans spelling local-definitions without its second i","value":1},{"derivation":"count of files in IBM/*.json whose root element is system-security-plan","key":"ibm_ssp_files","label":"system security plans in the corpus","value":0},{"derivation":"count of Easy Dynamics assessment plan files whose text contains the key \"step-type\"","key":"ez_files_with_step_type","label":"assessment plans using step-type at all","value":11}]},"data/criteria.json":{"criteria":[{"name":"Triad fidelity","number":1,"question":"Does the option keep regulator, implementer and assessor roles separable?","slots":["1","3","6a","6b"]},{"name":"Normativity","number":2,"question":"Can the artifact express must versus may? Can an auditor treat it as binding?","slots":["1"]},{"name":"Requirement level","number":3,"question":"Can shall, should and may be represented at all?","slots":["1"]},{"name":"Hierarchy support","number":4,"question":"Does the model natively carry deep benchmark hierarchies?","slots":["1"]},{"name":"Tailoring","number":5,"question":"Can an organization select, exclude and parameterize at scale?","slots":["1"]},{"name":"Authoring burden","number":6,"question":"How many OSCAL artifacts must a benchmark author produce per benchmark, multiplied across roughly 100 CIS guides?","slots":["1","2","3","4","5","6a","6b"]},{"name":"SSP impact","number":7,"question":"How many additional items enter the SSP? Does the SSP end up mixing desired and actual state?","slots":["6a"]},{"name":"Response fidelity","number":8,"question":"Can a system owner answer per host or inventory item, or only per component?","slots":["4"]},{"name":"Traceability","number":9,"question":"Can a consumer traverse control to rule to check to activity to task to observation using core schema only?","slots":["1","2","3","5","6b"]},{"name":"Schema change cost","number":10,"question":"How many models change, and what is the realistic ratification timeline?","slots":["1","2","3","4","5","6a","6b"]},{"name":"Update decoupling","number":11,"question":"When a benchmark revises independently of the regulation, what has to change downstream?","slots":["1"]},{"name":"Cross-framework use","number":12,"question":"Does this help someone operating under SOC 2, ISO and FedRAMP at the same time?","slots":["2"]},{"name":"Inspectability","number":13,"question":"Can an operator see what a check does before running it on their systems?","slots":["3"]},{"name":"Prop dependence","number":14,"question":"How much meaning lives in namespaced props rather than core schema?","slots":["1","2","3","4","5","6a","6b"]},{"name":"Existing content","number":15,"question":"Is there working end-to-end content today, including an SSP and an AR?","slots":["1","2","3","4","5","6a","6b"]}],"note":"Fifteen evaluation criteria maintained in this repository for comparing the three approaches. The questions and slot mappings define the analysis scope."},"data/examples.json":{"cis_derived":["assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json"],"files":[{"approach":"assessment-first","bytes":308830,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","sha256":"521acdef03590676c0a041bf920e36a7575c63683f04e787909d3c4dcc10ea66"},{"approach":"assessment-first","bytes":325728,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-maester.json","sha256":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653"},{"approach":"assessment-first","bytes":293862,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","sha256":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e"},{"approach":"assessment-first","bytes":298328,"path":"assessment-first/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","sha256":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d"},{"approach":"assessment-first","bytes":19829,"path":"assessment-first/CISA BOD 25-01/assessment-plan.json","sha256":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee"},{"approach":"assessment-first","bytes":39652,"path":"assessment-first/CISA BOD 25-01/sample-ssp.json","sha256":"2309e2f7ad9e8a468ac38fa7584094cab3e1bc20fc1d8ae108836f4e65ecf66d"},{"approach":"assessment-first","bytes":1032133,"path":"assessment-first/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1.0.0.json","sha256":"b72eda73c5bef60e2971c93261bc226594cfb8d8aa1be92deb6b2e121bf05379"},{"approach":"assessment-first","bytes":423087,"path":"assessment-first/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","sha256":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8"},{"approach":"assessment-first","bytes":6823924,"path":"assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","sha256":"1a90fccb4442decd119382233ff8986caaaeede83dcf3c5ab22a87c747ab0c81"},{"approach":"assessment-first","bytes":1768114,"path":"assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","sha256":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c"},{"approach":"assessment-first","bytes":821083,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","sha256":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6"},{"approach":"assessment-first","bytes":823183,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","sha256":"e1eed16a4a0f6d6b6025ce05c16832458bbcd4ba16d597340d0c764333197841"},{"approach":"assessment-first","bytes":2454926,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel8.json","sha256":"54cd0e15efb7c96347cfd16012d6fc81b93861079ce8a2ccf4e61eac57b538f7"},{"approach":"assessment-first","bytes":3051725,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel9.json","sha256":"9fbd810f7c658809a3be29bdb9bc14dfdafabbe289482454208f86b3646c7783"},{"approach":"assessment-first","bytes":1310065,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu22.json","sha256":"46738bf619cdfbef00913d761586633bec301e4aae5050a30c823f27509c7e7d"},{"approach":"assessment-first","bytes":1341083,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","sha256":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e"},{"approach":"assessment-first","bytes":1940344,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","sha256":"24dead32391e392f3d25501b0581fef5a719add51667c98920ad01f2d9273207"},{"approach":"assessment-first","bytes":1858865,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","sha256":"bfe441c22311614bc30cd080a57b5242129137912400a73a3e731a9f7a9abd7a"},{"approach":"assessment-first","bytes":1867817,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2025.json","sha256":"b8e54f5a9f6e554cd58bfe0c6b5be46085af5b760786ff6c933b1be7f8150bf8"},{"approach":"component-first","bytes":1106,"path":"component-first/ansible-validation-component-definition.json","sha256":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd"},{"approach":"component-first","bytes":5105,"path":"component-first/assessment-plan.json","sha256":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6"},{"approach":"component-first","bytes":4275,"path":"component-first/assessment-result.json","sha256":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806"},{"approach":"component-first","bytes":3332,"path":"component-first/cos-ansible-validation-cd.json","sha256":"25fb1b83230e0c5df473013775b7b9769fb1b981d90b9d7539f57694ce3c89ec"},{"approach":"component-first","bytes":2525,"path":"component-first/cos-component-definition.json","sha256":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a"},{"approach":"component-first","bytes":5230,"path":"component-first/idservice-component-definition.json","sha256":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf"},{"approach":"component-first","bytes":6228,"path":"component-first/idservice-oscap-validation-cd.json","sha256":"b3f4d83f10133e7ee058b24eb1598f2f081704beaa68473a499c7d7b481a5d06"},{"approach":"component-first","bytes":1297,"path":"component-first/oscap-validation-component-definition.json","sha256":"9efe6492ede4a21a743db6afe6bf05efda79c206d00dc6ee40e89f16145323f3"}],"link_only":{"catalog-first":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/"},"note":"The curated OSCAL examples committed in this repository, indexed by tools/copy_examples.py with the path, byte count and SHA-256 of each. Every build re-verifies the files against this index, so an edit is only accepted through an explicit --rebaseline run recorded in BUILD-LOG.md. Catalog-first is not here: it is published in a public repository and linked at the locked revision instead.","shared":[{"bytes":10442037,"path":"NIST_SP-800-53_rev5_catalog.json","sha256":"01f37cf90ea99d92242c936cbfbdebcc338eef1f71454e2acac36cc56e9bc062"}]},"data/generated-pages.json":{"note":"The hash of each approach page as this tool last wrote it. tools/approach_pages.py compares the page on disk against this before overwriting, so a hand edit to a generated page stops the build instead of disappearing into it.","sha256":{"assessment-first":"78f38c7ef742a486d4860d618df1a78e4487fef226e77317a5621f5501bab18b","catalog-first":"3319bcf155cdc7881b1dd1bfd42bdf9e679b2ed2ec5ec3b16576b04c15ed4ee8","component-first":"1049b6ef117611e6a1bd4db635f57d67895b7e3b6801a8d925a9c05c5901dc8e"},"written_by":"tools/approach_pages.py"},"data/glossary.json":{"note":"Definitions used by this analysis, with links from first uses. Alternative meanings and unresolved distinctions are identified without selecting an approach.","terms":[{"other_usages":[{"usage":"A normative requirement, a shall, equivalent to a control","who":"Catalog-first, Option A"},{"usage":"A statement of how a component may be configured, descriptive rather than binding","who":"Component-first, Option B"},{"usage":"Colloquially, the check code itself","who":"Ambiguous usage; this analysis distinguishes rule from check"},{"usage":"An AWS Config rule: a deployable resource with parameters","who":"AWS Config, the product"}],"see_also":["check","control","desired state","requirement level"],"site_usage":"One technical requirement or recommendation, finer-grained than a control, without any claim about whether it is binding. A working definition for comparing approaches, not selecting an interpretation.","status":"contested","term":"rule"},{"other_usages":[],"see_also":["rule","validation component","assessment platform"],"site_usage":"An executable or procedural test that determines whether a rule is satisfied. One rule may have many checks, one per tool.","status":"settled","term":"check"},{"other_usages":[{"usage":"Possible state: a technology provider describes available configurations rather than required configurations","who":"Alternative interpretation of component configuration"}],"see_also":["actual state","rule","implementation claim"],"site_usage":"The configuration prescribed by a rule, distinct from the system's observed configuration, or actual state.","status":"contested","term":"desired state"},{"other_usages":[],"see_also":["desired state","assessment result"],"site_usage":"The system's observed configuration, distinct from the configuration prescribed by a rule, or desired state.","status":"settled","term":"actual state"},{"other_usages":[],"see_also":["rule","link to a control","catalog"],"site_usage":"A requirement from a regulatory framework, such as NIST SP 800-53. Coarser than a rule. One control is typically served by many rules.","status":"settled","term":"control"},{"other_usages":[],"see_also":["control","mapping collection","finding","observation"],"site_usage":"An optional relationship from a rule to regulatory controls. A rule may serve several controls, one, or none. A rule without a control link can have observations but no control-targeted finding.","status":"settled","term":"link to a control"},{"other_usages":[{"usage":"Hardening guidance, used interchangeably","who":"This analysis"}],"see_also":["rule","hardening guidance"],"site_usage":"A published set of technology-specific hardening guidance, including CIS Benchmarks, DISA STIGs, CISA SCuBA baselines and technology provider guides.","status":"settled","term":"benchmark"},{"other_usages":[],"see_also":["benchmark","rule"],"site_usage":"Technology-specific guidance for configuring hardware, software or services securely. Used as a synonym for benchmark in this analysis.","status":"settled","term":"hardening guidance"},{"other_usages":[],"see_also":["rule","normativity"],"site_usage":"Whether a statement is a shall, should or may. OSCAL has no dedicated core requirement-level field across these approaches. Properties can carry such labels, but consumers need shared conventions to interpret them; model placement alone does not establish requirement level.","status":"not-established","term":"requirement level"},{"other_usages":[],"see_also":["requirement level","rule"],"site_usage":"Whether an artifact expresses binding requirements against which an auditor can assess a system. Normativity is part of the debate over model placement.","status":"contested","term":"normativity"},{"other_usages":[],"see_also":[],"set_aside":true,"site_usage":"A Component Definition construct grouping components and control-implementations to express joint satisfaction. Whether capabilities should be added to the SSP or removed from Component Definition remains an open design question in this analysis. No position is selected.","status":"contested","term":"capability"},{"other_usages":[{"usage":"A component whose purpose is to run checks rather than to be checked. Type validation, carrying a checks array.","who":"Component-first examples using proposed assemblies"},{"usage":"A component enumerating the compliance frameworks a service has been validated against.","who":"Alternative interpretation, not demonstrated by the OSCAL examples"}],"see_also":["check","component"],"site_usage":"Two distinct meanings are used: a component running checks, or a component describing validation against frameworks. This analysis identifies the intended meaning.","status":"contested","term":"validation component"},{"not_established_note":"The open question is when a component alone identifies a runner and when an assessment platform adds necessary execution context.","other_usages":[],"see_also":["assessment asset","component","actor"],"site_usage":"An OSCAL assessment-assets element that may reference components through uses-components. The examples do not establish a consistent convention for distinguishing assessment platforms, assessment assets and components in runner descriptions.","status":"not-established","term":"assessment platform"},{"not_established_note":"A consumer still needs to associate each task or observation with the asset used.","other_usages":[],"see_also":["assessment platform","component","actor"],"site_usage":"The OSCAL assessment-assets container holds components and assessment-platforms. The examples do not establish a consistent convention for identifying runners across these structures.","status":"not-established","term":"assessment asset"},{"not_established_note":"The examples leave open whether components should represent individual rules, products or policy engines and how consumers reconcile those levels.","other_usages":[],"see_also":["assessment platform","assessment asset","validation component"],"site_usage":"A part of a system, with related meanings across Component Definition, SSP, Assessment Plan and Assessment Results models. The distinction from assessment platforms and assets remains unresolved, as does granularity: a component may represent a configuration rule or a policy engine.","status":"not-established","term":"component"},{"not_established_note":"The examples use different runner-identification conventions. No single convention is established here for associating a task or observation with its producer.","other_usages":[{"usage":"An assessment platform, optionally reaching components through uses-components","who":"OSCAL assessment-assets"},{"usage":"A component of type validation, carrying the checks it runs","who":"Component-first, Option B, proposed schema"},{"usage":"An origin actor on an assessment result","who":"OSCAL assessment-results"},{"usage":"A tool named in a prop at task level","who":"The assessment plans in two of the three corpora"}],"see_also":["assessment platform","assessment asset","component","check"],"site_usage":"The tool or person performing a check, addressed by question 5. Actor is a neutral label in this analysis because no single OSCAL construct covers all uses.","status":"not-established","term":"actor"},{"other_usages":[],"see_also":["assessment result","system security plan"],"site_usage":"The system owner's narrative assertion of control implementation and design intent per component. The SSP represents claims through implemented-requirement, statement and by-component. Addressed by question 6a.","status":"settled","term":"implementation claim"},{"other_usages":[],"see_also":["implementation claim","observation","finding"],"site_usage":"The assessor's evidence-based record of whether a control was satisfied for a subject at a point in time. The AR uses observation, finding and status for binary or graded outcomes. Addressed by question 6b.","status":"settled","term":"assessment result"},{"other_usages":[],"see_also":["finding","assessment result","link to a control"],"site_usage":"An AR element recording observed evidence. Requires uuid, description, methods and collected, with no control reference. Observations are available for rules with or without control links.","status":"settled","term":"observation"},{"other_usages":[],"see_also":["observation","link to a control","assessment result"],"site_usage":"An AR element recording whether an objective is satisfied. The required target type is restricted to statement-id or objective-id, both control-derived. A rule without a control link cannot have a finding.","status":"settled","term":"finding"},{"other_usages":[],"see_also":["link to a control","catalog"],"site_usage":"An OSCAL model, GA since 1.2, relating collections of controls. Third parties can publish mappings after the source catalogs. The mapping-item type permits control and statement targets, not component rules or activities.","status":"settled","term":"mapping collection"},{"other_usages":[],"see_also":["profile","control"],"site_usage":"OSCAL model, Control layer. A structured set of controls and control enhancements.","status":"settled","term":"catalog"},{"other_usages":[],"see_also":["catalog"],"site_usage":"OSCAL model, Control layer. A baseline or overlay that selects and customizes controls from catalogs.","status":"settled","term":"profile"},{"other_usages":[],"see_also":["system security plan","component"],"site_usage":"OSCAL model, Implementation layer. Describes how components implement controls.","status":"settled","term":"component definition"},{"other_usages":[],"see_also":["component definition","implementation claim"],"site_usage":"OSCAL model, Implementation layer. Documents how a particular system implements required controls. Abbreviated SSP.","status":"settled","term":"system security plan"},{"other_usages":[],"see_also":["assessment result","activity","step"],"site_usage":"OSCAL model, Assessment layer. Defines how controls will be assessed, through activities, steps and tasks. Abbreviated AP or SAP.","status":"settled","term":"assessment plan"},{"other_usages":[],"see_also":["step","assessment plan"],"site_usage":"An assessment plan local-definitions element containing steps. How to divide a benchmark procedure between activities and steps remains an analysis question.","status":"not-established","term":"activity"},{"other_usages":[],"see_also":["activity","assessment plan"],"site_usage":"A child of an assessment plan activity. The examples do not establish one consistent boundary between the work represented by an activity and its steps.","status":"not-established","term":"step"},{"other_usages":[],"see_also":["assessment plan","observation","finding"],"site_usage":"OSCAL model, Assessment layer. Documents the results of control assessments, as observations and findings. Abbreviated AR or SAR.","status":"settled","term":"assessment results"},{"other_usages":[],"see_also":["assessment results"],"site_usage":"OSCAL model, Assessment layer. Documents remediation plans for identified issues. Abbreviated POA&M.","status":"settled","term":"plan of action and milestones"},{"other_usages":[],"see_also":["implementer","assessor"],"site_usage":"One of three stakeholder roles. Publishes requirements or recommendations for organisations to version, tailor and cite without depending on a specific system.","status":"settled","term":"publisher"},{"other_usages":[],"see_also":["publisher","assessor","desired state"],"site_usage":"One of three stakeholder roles. Uses requirements as desired-state configuration that a configuration engine can apply.","status":"settled","term":"implementer"},{"other_usages":[],"see_also":["publisher","implementer","check"],"site_usage":"One of three stakeholder roles. Runs checks or reviews sufficient evidence to determine whether requirements are satisfied.","status":"settled","term":"assessor"}]},"data/joins.json":{"approaches":{"assessment-first":{"hops":[{"from":"rule","how":"containment","note":"The activity contains the check as the first step. A property on the step identifies an executable check resolved outside OSCAL.","pairs":[{"foreign":{"field":"no field","model":"assessment-plan","slot":"1"},"how":"containment","primary":{"field":"activities[].steps[].uuid","model":"assessment-plan","slot":"3","value":"333ddd0f-22da-4c18-8bc3-98e808746bca"}},{"foreign":{"field":"steps[].props[name=check].value","model":"assessment-plan","slot":"3","value":"SV-270747r1066730_rule"},"how":"name-match","primary":{"field":"no field","model":"nothing","slot":"5"}}],"to":"check"},{"from":"rule","how":"reference","note":"The activity references the framework control through related-controls, without a separate mapping document or an additional mapping identifier to maintain.","pairs":[{"foreign":{"field":"activities[].related-controls.control-selections[].include-controls[].control-id","model":"assessment-plan","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"reference","note":"The example plan identifies platforms for the assessment as a whole. The platform reference does not identify the engine used for each check.","pairs":[{"foreign":{"field":"assessment-platforms[].uses-components[].component-uuid","model":"assessment-plan","slot":"5","value":"56270516-2673-4d4c-8d4f-52e4107f968d"},"how":"reference","primary":{"field":"assessment-assets.components[].uuid","model":"assessment-plan","slot":"5"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The plan references one system security plan through a back-matter resource. Where no plan of record exists, the resource can describe the system in prose.","pairs":[{"foreign":{"field":"import-ssp.href","model":"assessment-plan","slot":"6a","value":"#d381c885-4851-4931-828c-29bbb24fbaa3"},"how":"reference","primary":{"field":"back-matter.resources[].uuid","model":"assessment-plan","slot":"6a","value":"d381c885-4851-4931-828c-29bbb24fbaa3"}}],"to":"claim"},{"from":"runtime","how":"reference","note":"The example observation references the planned activity as the subject. The reference identifies the activity, not an inventory item assessed by the check.","pairs":[{"foreign":{"field":"observations[].subjects[].subject-uuid","model":"assessment-results","slot":"6b","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"},"how":"reference","primary":{"field":"activities[].uuid","model":"assessment-plan","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}}],"to":"result"},{"from":"result","how":"reference","note":"The finding targets a framework control objective. The target links the result to the framework without depending on an implementation statement in a plan of record.","pairs":[{"foreign":{"field":"findings[].target.target-id","model":"assessment-results","slot":"6b","value":"sc-28_obj"},"how":"reference","primary":{"field":"controls[].parts[objective].id","model":"catalog","slot":"2"}}],"to":"control"}],"introduced":{"field":"activities[].uuid","model":"assessment-plan","note":"The assessment plan defines the rule as an activity in the assessment layer, outside the implementation claim. The chain starts from the activity uuid.","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}},"catalog-first":{"hops":[{"from":"rule","how":"name-match","note":"The control references the check by title, a match not enforced by the schema. The check references the control by a resolvable id.","pairs":[{"foreign":{"field":"parts[assessment-method].props.TechnicalControlId","model":"catalog","slot":"1","value":"SV-270747r1066730_rule"},"how":"name-match","primary":{"field":"components[].title","model":"component-definition","slot":"3","value":"SV-270747r1066730_rule"}},{"foreign":{"field":"implemented-requirements[].control-id","model":"component-definition","slot":"3","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}}],"to":"check"},{"from":"rule","how":"reference","note":"A separate mapping collection links the catalogs. A third party can publish the mapping after both catalogs are published without owning either source.","pairs":[{"foreign":{"field":"maps[].sources[].id-ref","model":"mapping-collection","slot":"2","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}},{"foreign":{"field":"maps[].targets[].id-ref","model":"mapping-collection","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"none","note":"ConfigRuleId identifies the executable rule, but the content does not identify the engine that executes the check.","pairs":[{"foreign":{"field":"components[].props.ConfigRuleId","model":"component-definition","slot":"3","value":"SV_270747R1066730_RULE"},"how":"none","primary":{"field":"no field","model":"nothing","slot":"5"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The claim references a component, not a host. The by-component assembly has no assessment subject field for an individual instance.","pairs":[{"foreign":{"field":"implemented-requirements[].control-id","model":"system-security-plan","slot":"6a","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}},{"foreign":{"field":"by-components[].component-uuid","model":"system-security-plan","slot":"6a","value":"534b356b-0de1-48d4-8536-5d41ed717456"},"how":"reference","primary":{"field":"system-implementation.components[].uuid","model":"system-security-plan","slot":"6a"}}],"to":"claim"},{"from":"claim","how":"reference","note":"The finding targets the implementation statement in the system security plan and references supporting observations, connecting the assessment outcome to the claim.","pairs":[{"foreign":{"field":"findings[].target.target-id","model":"assessment-results","slot":"6b","value":"UBTU-24-600090_smt"},"how":"reference","primary":{"field":"statements[].statement-id","model":"system-security-plan","slot":"6a","value":"UBTU-24-600090_smt"}},{"foreign":{"field":"related-observations[].observation-uuid","model":"assessment-results","slot":"6b","value":"28e28d31-4428-4ff5-8c9e-ea1198dfb552"},"how":"reference","primary":{"field":"observations[].uuid","model":"assessment-results","slot":"6b"}}],"to":"result"}],"introduced":{"field":"controls[].id","model":"catalog","note":"The product catalog defines the rule as a control, using the same OSCAL structure as a regulatory control. The chain starts from the control id.","slot":"1","value":"UBTU-24-600090"}},"component-first":{"hops":[{"from":"rule","how":"composite","note":"The check references both a rule id and a target component uuid. A rule id is unique only within the declaring component.","pairs":[{"foreign":{"field":"checks[].rule-id","model":"component-definition","slot":"3","value":"ubtu24_data_at_rest_encrypted"},"how":"composite","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"checks[].target-component-uuid","model":"component-definition","slot":"3","value":"5ca997b3-bb3e-4c7a-8969-69ed44577d47"},"how":"composite","primary":{"field":"components[].uuid","model":"component-definition","slot":"1","value":"5ca997b3-bb3e-4c7a-8969-69ed44577d47"}}],"to":"check"},{"from":"rule","how":"reference","note":"The component definition contains both references. Control implementations already link components to controls; the proposed implementing-rules assembly adds references to individual rules.","pairs":[{"foreign":{"field":"implemented-requirements[].implementing-rules[].rule-id","model":"component-definition","slot":"2","value":"ubtu24_data_at_rest_encrypted"},"how":"reference","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"implemented-requirements[].control-id","model":"component-definition","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"containment","note":"The validation component contains the checks executed by the engine. Each additional engine is represented by a separate validation component.","pairs":[{"foreign":{"field":"no field","model":"component-definition","slot":"3"},"how":"containment","primary":{"field":"components[].uuid","model":"component-definition","slot":"5","value":"b3c8813d-d479-450a-8178-fbbf846faccf","where":"the validation component"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The proposed implementing-rules assembly references the rule supporting the claim, allowing a consumer to trace the claim to the check through OSCAL references.","pairs":[{"foreign":{"field":"by-components[].implementing-rules[].rule-id","model":"system-security-plan","slot":"6a","value":"ubtu24_data_at_rest_encrypted"},"how":"reference","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"by-components[].component-uuid","model":"system-security-plan","slot":"6a","value":"534b356b-0de1-48d4-8536-5d41ed717456"},"how":"reference","primary":{"field":"system-implementation.components[].uuid","model":"system-security-plan","slot":"6a"}}],"to":"claim"},{"from":"runtime","how":"reference","note":"The observation identifies the check and host, allowing different outcomes for two machines within the same system boundary to be recorded separately.","pairs":[{"foreign":{"field":"observations[].assessment-check-id","model":"assessment-results","slot":"6b","value":"SV-270747r1066730_rule"},"how":"reference","primary":{"field":"checks[].id","model":"component-definition","slot":"3","value":"SV-270747r1066730_rule"}},{"foreign":{"field":"observations[].subjects[].subject-uuid","model":"assessment-results","slot":"6b","value":"06297a03-cae0-414b-8332-2fc882f81aa1"},"how":"reference","primary":{"field":"system-implementation.inventory-items[].uuid","model":"system-security-plan","slot":"4"}}],"to":"result"},{"from":"result","how":"none","note":"The example result contains observations but no findings. No finding target identifies the control, and no finding status records whether the objective was satisfied.","pairs":[{"foreign":{"field":"no field","model":"assessment-results","slot":"6b"},"how":"none","primary":{"field":"no field","model":"catalog","slot":"2"}}],"to":"control"}],"introduced":{"field":"components[].rules[].id","model":"component-definition","note":"The proposed rules assembly defines the rule on the product component. The chain starts from the rule id within that component definition.","slot":"1","value":"ubtu24_data_at_rest_encrypted"}}},"how":[{"key":"containment","label":"Containment","meaning":"A parent contains the child directly; no key matching or dereferencing is needed."},{"key":"reference","label":"Reference","meaning":"A schema-defined identifier reference resolves to a target identifier."},{"key":"name-match","label":"Name match","meaning":"Two strings match by convention. The schema does not enforce the relationship, so a mismatch may go undetected."},{"key":"composite","label":"Composite key","meaning":"Two fields jointly identify a target. Either field alone may identify the wrong target or no target."},{"key":"none","label":"No join","meaning":"No field directly connects the entries. A consumer must follow other relationships, or the connection is absent."}],"intro":"The chain connects a rule to checks, implementation claims and assessment results. Each step identifies the relationships a consumer must resolve and the fields used to resolve those relationships.","note":"The join chain connects rule definitions, checks, implementation claims and assessment results. Each relationship identifies a foreign key and the corresponding primary key. Values match the two example rules on the six questions page; tools/verify.py checks each value against those encodings.","stages":[{"key":"rule","label":"Rule","meaning":"where the rule is introduced","slot":"1"},{"key":"control","label":"Control","meaning":"the framework control served by the rule","slot":"2"},{"key":"check","label":"Check","meaning":"the test of the rule","slot":"3"},{"key":"runtime","label":"Runtime","meaning":"what executes the check","slot":"5"},{"key":"claim","label":"Claim","meaning":"the system owner's statement of implementation","slot":"6a"},{"key":"result","label":"Result","meaning":"what an assessment recorded","slot":"6b"}],"step_order":[["rule","check"],["rule","control"],["check","runtime"],["runtime","claim"],["runtime","result"],["claim","result"],["result","control"]],"title":"How the answers connect"},"data/model-icons.json":{"icons":{"assessment-plan":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"height":"30","rx":"3","soft":false,"stroke-width":"2.27","tag":"rect","width":"24","x":"20","y":"18"},{"d":"M26 15H38V19H26V15Z","soft":false,"stroke-linejoin":"round","stroke-width":"2.27","tag":"path"},{"d":"M26 26L38 26","soft":true,"stroke-linecap":"round","stroke-width":"2.27","tag":"path"},{"d":"M26 32L34 32","soft":true,"stroke-linecap":"round","stroke-width":"2.27","tag":"path"},{"cx":"36","cy":"38","r":"5","soft":false,"stroke-width":"2.27","tag":"circle"},{"d":"M36 36V38H38","soft":false,"stroke-linecap":"round","stroke-width":"1.70","tag":"path"}],"source":"assessment_plan_model.svg","view_box":"11.1907 10.6907 41.6186 41.6186"},"assessment-results":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"height":"32","rx":"3","soft":false,"stroke-width":"2.21","tag":"rect","width":"28","x":"18","y":"16"},{"d":"M24 24L27 27L33 21","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M24 34L27 37L33 31","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M37 24L40 24","soft":true,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M37 34L40 34","soft":true,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"}],"source":"assessment_results_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"catalog":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"d":"M18 18H30L34 22V48L27 45H18V18Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.08","tag":"path"},{"d":"M46 18H34L30 22V48L37 45H46V18Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.08","tag":"path"},{"d":"M22 26L28 26","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M22 32L28 32","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M36 26L42 26","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M36 32L42 32","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"}],"source":"catalog_model.svg","view_box":"13.0728 14.0728 37.8544 37.8544"},"component-definition":{"authored_box":"0 0 64 64","layer":"implementation","shapes":[{"d":"M32 16L46 24V40L32 48L18 40V24L32 16Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M32 16V32M32 32L46 24M32 32L18 24","soft":true,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 32L32 40L46 32","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"}],"source":"component_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"mapping-collection":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"cx":"22","cy":"22","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"cx":"42","cy":"22","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"cx":"32","cy":"42","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"d":"M26 24L38 24","soft":true,"stroke-dasharray":"2 2","stroke-width":"2.08","tag":"path"},{"d":"M25 26L29 38","soft":true,"stroke-width":"2.08","tag":"path"},{"d":"M39 26L35 38","soft":true,"stroke-width":"2.08","tag":"path"}],"source":"control_mapping_model.svg","view_box":"13.0728 13.0728 37.8544 37.8544"},"plan-of-action-and-milestones":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"cx":"32","cy":"32","r":"16","soft":false,"stroke-width":"3.25","tag":"circle"},{"cx":"32","cy":"32","r":"10","soft":true,"stroke-width":"3.25","tag":"circle"},{"cx":"32","cy":"32","fill":"ink","r":"3","soft":false,"tag":"circle"},{"d":"M32 12V8M32 56V52M12 32H8M56 32H52","soft":false,"stroke-linecap":"round","stroke-width":"3.25","tag":"path"}],"source":"plan_of_action_and_milestones_model.svg","view_box":"1.7625 1.7625 60.475 60.475"},"profile":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"d":"M18 20H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 32H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 44H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"cx":"26","cy":"20","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"},{"cx":"38","cy":"32","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"},{"cx":"30","cy":"44","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"}],"source":"profile_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"system-security-plan":{"authored_box":"0 0 64 64","layer":"implementation","shapes":[{"d":"M20 16H36L44 24V48H20V16Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M36 16V24H44","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M32 30V40M32 30L28 31L26 33L26 36L28 39L32 42L36 39L38 36L38 33L36 31L32 30Z","soft":true,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"}],"source":"system_security_plan_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"}},"layers":{"assessment":{"label":"Assessment layer","models":["assessment-plan","assessment-results","plan-of-action-and-milestones"]},"control":{"label":"Control layer","models":["catalog","profile","mapping-collection"]},"implementation":{"label":"Implementation layer","models":["component-definition","system-security-plan"]}},"note":"One icon per OSCAL model, generated by tools/model_icons.py from the authored files in assets/images. Geometry only: the colour is a layer token applied by the stylesheet, and the chip behind the glyph is a CSS box. Do not edit this file; edit the SVG and regenerate."},"data/oscal-artifacts.json":{"note":"tools/oscal_artifacts.py: author data/oscal-artifacts.json.","publishers":[{"files":[{"bytes":924964,"counts":{"controls":452,"groups":77},"file":"catalogs/aws_security-hub.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/catalogs/aws_security-hub.oscal.json","href_external":true,"model":"catalog","model_label":"Catalog","title":"AWS Security Hub Controls"},{"bytes":16118,"counts":{"components":3,"implemented requirements":4,"service":1,"software":2},"file":"component-definitions/acm.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/acm.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Certificate Manager"},{"bytes":27913,"counts":{"components":8,"implemented requirements":12,"service":2,"software":6},"file":"component-definitions/cloudtrail.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/cloudtrail.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS CloudTrail"},{"bytes":12332,"counts":{"components":1,"service":1},"file":"component-definitions/config.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/config.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Config"},{"bytes":43914,"counts":{"components":18,"implemented requirements":43,"service":1,"software":17},"file":"component-definitions/iam.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/iam.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Identity and Access Management"}],"full_name":"Option A","key":"catalog-first","name":"Catalog-first","option":"Option A","repo":"https://github.com/awslabs/oscal-content-for-aws-services","rollup":{"components":861,"count":230,"model_label":"Component definition","note":"One per service. Four are listed above as examples; the rest follow the same shape.","software":429},"root":"AWS/oscal-content-for-aws-services-main","totals":{"Catalog":1,"Component definition":230}},{"files":[{"bytes":1106,"counts":{"components":1,"validation":1},"file":"ansible-validation-component-definition.json","href":"examples/component-first/ansible-validation-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo validation component definition"},{"bytes":5105,"counts":{"activities":0,"tasks":1},"file":"assessment-plan.json","href":"examples/component-first/assessment-plan.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"Assessment Plan"},{"bytes":4275,"counts":{"findings":0,"observations":1,"results":1},"file":"assessment-result.json","href":"examples/component-first/assessment-result.json","href_external":false,"model":"assessment-results","model_label":"Assessment results","title":"Assessment Result"},{"bytes":3332,"counts":{"components":2,"implemented requirements":2,"rules":2,"service":1,"validation":1},"file":"cos-ansible-validation-cd.json","href":"examples/component-first/cos-ansible-validation-cd.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":2525,"counts":{"components":1,"implemented requirements":2,"rules":2,"service":1},"file":"cos-component-definition.json","href":"examples/component-first/cos-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":5230,"counts":{"components":1,"implemented requirements":7,"rules":3,"service":1},"file":"idservice-component-definition.json","href":"examples/component-first/idservice-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":6228,"counts":{"components":2,"implemented requirements":7,"rules":3,"service":1,"validation":1},"file":"idservice-oscap-validation-cd.json","href":"examples/component-first/idservice-oscap-validation-cd.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":1297,"counts":{"components":1,"validation":1},"file":"oscap-validation-component-definition.json","href":"examples/component-first/oscap-validation-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo validation component definition"}],"full_name":"Option B","key":"component-first","name":"Component-first","option":"Option B","repo":null,"rollup":null,"root":"IBM","totals":{"Assessment plan":1,"Assessment results":1,"Component definition":6}},{"files":[{"bytes":308830,"counts":{"activities":7,"steps":128,"tasks":0},"file":"CISA BOD 25-01/ap-cisa-scuba-agnostic.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-agnostic.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":325728,"counts":{"activities":7,"steps":128,"tasks":1},"file":"CISA BOD 25-01/ap-cisa-scuba-maester.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-maester.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":293862,"counts":{"activities":7,"steps":128,"tasks":1},"file":"CISA BOD 25-01/ap-cisa-scuba-scubagear.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-scubagear.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":298328,"counts":{"findings":128,"observations":128,"results":1},"file":"CISA BOD 25-01/ar-cisa-scuba-scubagear.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ar-cisa-scuba-scubagear.json","href_external":false,"model":"assessment-results","model_label":"Assessment results","title":"CISA SCuBA Assessment Results - M365 Tenant"},{"bytes":19829,"counts":{"activities":8,"steps":8,"tasks":1},"file":"CISA BOD 25-01/assessment-plan.json","href":"examples/assessment-first/CISA%20BOD%2025-01/assessment-plan.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"Entra ID cATO Assessment Plan"},{"bytes":39652,"counts":{},"file":"CISA BOD 25-01/sample-ssp.json","href":"examples/assessment-first/CISA%20BOD%2025-01/sample-ssp.json","href_external":false,"model":"system-security-plan","model_label":"System security plan","title":"Sample ScubaGear System Security Plan"},{"bytes":423087,"counts":{"activities":72,"steps":144,"tasks":8},"file":"Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","href":"examples/assessment-first/Center%20for%20Internet%20Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CIS PostgreSQL 18 Benchmark"},{"bytes":1768114,"counts":{"activities":53,"steps":616,"tasks":7},"file":"Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","href":"examples/assessment-first/Center%20for%20Internet%20Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CIS Ubuntu Linux 24.04 LTS Benchmark"},{"bytes":821083,"counts":{"activities":118,"steps":236,"tasks":2},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/epas.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Postgres Advanced Server"},{"bytes":823183,"counts":{"activities":111,"steps":222,"tasks":2},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/postgres16.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Postgres 16"},{"bytes":2454926,"counts":{"activities":366,"steps":732,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel8.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/rhel8.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Red Hat Enterprise Linux 8"},{"bytes":3051725,"counts":{"activities":446,"steps":892,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel9.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/rhel9.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Red Hat Enterprise Linux 9"},{"bytes":1310065,"counts":{"activities":188,"steps":376,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu22.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/ubuntu22.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Ubuntu 22.04 LTS"},{"bytes":1341083,"counts":{"activities":194,"steps":388,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/ubuntu24.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Ubuntu 24.04 LTS"},{"bytes":1940344,"counts":{"activities":282,"steps":564,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2019.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2019"},{"bytes":1858865,"counts":{"activities":282,"steps":564,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2022.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2022"},{"bytes":1867817,"counts":{"activities":284,"steps":568,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2025.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2025.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2025"}],"full_name":"Option C","key":"assessment-first","name":"Assessment-first","option":"Option C","repo":null,"rollup":null,"root":"Easy Dynamics","totals":{"Assessment plan":15,"Assessment results":1,"System security plan":1}}]},"data/pattern-examples.json":{"benchmark_id":"CAN_Ubuntu_24-04_STIG","examples":{"1":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"steps\": [\n {\n \"uuid\": \"333ddd0f-22da-4c18-8bc3-98e808746bca\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"props","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"An activity. The requirement is the activity title, the work is in its steps, and the identifiers stay in the publisher's own namespace."},{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"steps\": [\n {\n \"uuid\": \"fd6c19bf-7c7f-4376-8dc0-674fd0421f64\",\n \"title\": \"Check: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270732r1066685_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"props","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"An activity. The requirement is the activity title, the work is in its steps, and the identifiers stay in the publisher's own namespace."}],"catalog-first":[{"content":"{\n \"catalog\": {\n \"groups\": [\n {\n \"id\": \"ubuntu-24-04\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"controls\": [\n {\n \"id\": \"UBTU-24-600090\",\n \"title\": \"Data at rest\",\n \"parts\": [\n {\n \"name\": \"statement\",\n \"prose\": \"Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"SV-270747r1066730_rule\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV-270747r1066730_rule\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[19,26]],"focus_key":"props","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A control. The requirement is the control's statement, the check is named in an assessment-method part, and a value, where there is one, is a control parameter."},{"content":"{\n \"catalog\": {\n \"groups\": [\n {\n \"id\": \"ubuntu-24-04\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"controls\": [\n {\n \"id\": \"UBTU-24-400320\",\n \"title\": \"Minimum password length\",\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"The required length is a parameter of the control, so tailoring it is a profile edit rather than a change to the requirement.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"SV-270732r1066685_rule\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV-270732r1066685_rule\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ],\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[23,30]],"focus_key":"props","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A control. The requirement is the control's statement, the check is named in an assessment-method part, and a value, where there is one, is a control parameter."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"5ca997b3-bb3e-4c7a-8969-69ed44577d47\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"description\": \"Ubuntu 24.04 LTS as a component of the system.\",\n \"rules\": [\n {\n \"id\": \"ubtu24_data_at_rest_encrypted\",\n \"description\": \"Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\"\n }\n ]\n }\n ]\n }\n}","focus":[[9,14]],"focus_key":"rules","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A rules entry on the component the rule applies to. The rule is first-class rather than a prop, and a value is a rule param set by the control implementation."},{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"da810545-1635-4323-8e22-a74ddbe2c31d\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"description\": \"Ubuntu 24.04 LTS as a component of the system.\",\n \"rules\": [\n {\n \"id\": \"ubtu24_password_min_length\",\n \"description\": \"Passwords must be at least {param: password_min_length} characters.\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[9,20]],"focus_key":"rules","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A rules entry on the component the rule applies to. The rule is first-class rather than a prop, and a value is a rule param set by the control implementation."}]},"2":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"reviewed-controls\": {\n \"control-selections\": [\n {\n \"description\": \"The controls this assessment may touch.\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n },\n {\n \"control-id\": \"ia-5.1\"\n }\n ]\n }\n ]\n },\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule, derived from its CCI references.\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n }\n ]\n }\n ]\n }\n },\n {\n \"uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule, derived from its CCI references.\",\n \"include-controls\": [\n {\n \"control-id\": \"ia-5.1\"\n }\n ]\n }\n ]\n }\n }\n ]\n }\n }\n}","focus":[[23,34],[39,50]],"focus_key":"related-controls","label":"Both rules and their control ties","rule":"both","shows":"Named on the activity itself. No second document and no second identifier, so nothing can fall out of step, and nothing else can reuse the tie."}],"catalog-first":[{"content":"{\n \"mapping-collection\": {\n \"uuid\": \"d958a01a-6d1a-46fc-8289-ab967af8b955\",\n \"metadata\": {\n \"title\": \"Ubuntu 24.04 LTS product catalog mapped to NIST SP 800-53 Revision 5\",\n \"last-modified\": \"2026-08-20T12:00:00Z\",\n \"version\": \"1.0.0\",\n \"oscal-version\": \"1.2.2\"\n },\n \"provenance\": {\n \"method\": \"human\",\n \"matching-rationale\": \"semantic\",\n \"status\": \"draft\",\n \"mapping-description\": \"Each hardening control is narrower than the framework control it supports, so every map below is a subset relationship.\"\n },\n \"mappings\": [\n {\n \"uuid\": \"f60ce697-4c9d-48e2-8136-f7d3bcb895d7\",\n \"source-resource\": {\n \"type\": \"catalog\",\n \"href\": \"#ubuntu-24-04-product-catalog\"\n },\n \"target-resource\": {\n \"type\": \"catalog\",\n \"href\": \"#nist-800-53-rev5\"\n },\n \"maps\": [\n {\n \"uuid\": \"74734a70-2c15-4634-8fe1-eb70dacc4b33\",\n \"relationship\": \"subset-of\",\n \"matching-rationale\": \"semantic\",\n \"sources\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"UBTU-24-600090\"\n }\n ],\n \"targets\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"sc-28\"\n }\n ]\n },\n {\n \"uuid\": \"da49a963-4911-47d7-837b-da3c516a4708\",\n \"relationship\": \"subset-of\",\n \"matching-rationale\": \"semantic\",\n \"sources\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"UBTU-24-400320\"\n }\n ],\n \"targets\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"ia-5.1\"\n }\n ]\n }\n ]\n }\n ],\n \"back-matter\": {\n \"resources\": [\n {\n \"uuid\": \"13c89eb4-c309-466f-8e39-83e272663a37\",\n \"title\": \"Ubuntu 24.04 LTS product catalog\",\n \"rlinks\": [\n {\n \"href\": \"./ubuntu-24-04-catalog.json\"\n }\n ]\n },\n {\n \"uuid\": \"6d874b7d-f632-43ee-8043-8f0d5bd5fbe2\",\n \"title\": \"NIST SP 800-53 Revision 5\",\n \"rlinks\": [\n {\n \"href\": \"./NIST_SP-800-53_rev5_catalog.json\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[27,62]],"focus_key":"maps","label":"Both rules and their control ties","rule":"both","shows":"A whole document of its own. Metadata and a four-field provenance block come before the first map, and both ends of a map must be a control or a statement."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"control-implementations\": [\n {\n \"uuid\": \"1cc70653-88aa-408e-80ce-fdf004c2e3e1\",\n \"source\": \"trestle://profiles/nist_800_53_rev5/profile.json\",\n \"description\": \"NIST SP 800-53 Revision 5\",\n \"set-parameters\": [\n {\n \"param-id\": \"password_min_length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"implemented-requirements\": [\n {\n \"uuid\": \"891fbbe5-51fa-4d63-8c75-36beb7b9c70b\",\n \"control-id\": \"sc-28\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n },\n {\n \"uuid\": \"53dc0fa3-7de4-4969-86d9-0dba5044e0b3\",\n \"control-id\": \"ia-5.1\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_password_min_length\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[21,40]],"focus_key":"implemented-requirements","label":"Both rules and their control ties","rule":"both","shows":"No second document, and two ties in one place. The implemented requirement ties the component to the control, which OSCAL already does; implementing-rules ties the rule to it, which it does not."}]},"3":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"333ddd0f-22da-4c18-8bc3-98e808746bca\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"Verify the block device carrying user data is encrypted. If it is not, this is a finding.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[14,27]],"focus_key":"steps","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"The steps are the check, and a check prop names it. Put that prop on the step and the plan can ask for one item; put it on the activity and one invocation covers every step beneath. The runner decides which."},{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"fd6c19bf-7c7f-4376-8dc0-674fd0421f64\",\n \"title\": \"Check: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"description\": \"Verify the configured minimum password length is 15 or greater. If it is not, this is a finding.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270732r1066685_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[14,27]],"focus_key":"steps","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"The steps are the check, and a check prop names it. Put that prop on the step and the plan can ask for one item; put it on the activity and one invocation covers every step beneath. The runner decides which."},{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"201588f5-0638-4c98-89d7-e4c215e62171\",\n \"title\": \"Assess Ubuntu 24.04 LTS\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"check\",\n \"value\": \"CAN_Ubuntu_24-04_STIG\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"410c472a-0935-48ee-8543-e39e02365bfd\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\"\n },\n {\n \"uuid\": \"cbcc6a87-99c5-4002-8990-cb54ee8a7377\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[13,17]],"focus_key":"name=check","label":"Multiple tests, with the check at the activity level","rule":"placement","shows":"The same two checks named on the activity instead, for a runner that executes in bulk. One invocation, every step beneath it."}],"catalog-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"272c65cb-9a6d-4344-8938-2e6203673884\",\n \"type\": \"software\",\n \"title\": \"SV-270747r1066730_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-600090.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270747R1066730_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"9133615a-9ffc-4656-8ca7-2b249482ee22\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"b971b7c8-6b4f-4188-8ceb-968a4aacb040\",\n \"control-id\": \"UBTU-24-600090\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[9,15]],"focus_key":"props","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"The check is a software component whose title is the identifier the control's assessment-method part named."},{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"65157847-efa3-4d97-8e62-f6148c556255\",\n \"type\": \"software\",\n \"title\": \"SV-270732r1066685_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-400320.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270732R1066685_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"2293c543-d5f7-45e3-8ef3-3917f9e5ccc1\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"3f57d132-ea15-4517-8398-778950a14382\",\n \"control-id\": \"UBTU-24-400320\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[9,15]],"focus_key":"props","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"The check is a software component whose title is the identifier the control's assessment-method part named."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted on the target host.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"5ca997b3-bb3e-4c7a-8969-69ed44577d47\"\n }\n ]\n }\n ]\n }\n}","focus":[[15,22]],"focus_key":"checks","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"Two components, not one. The rule sits on the product; the check sits on a second component of type validation, one per engine, and reaches back by rule id and the uuid of the component the rule belongs to."},{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"checks\": [\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length on the target host.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"da810545-1635-4323-8e22-a74ddbe2c31d\"\n }\n ]\n }\n ]\n }\n}","focus":[[15,22]],"focus_key":"checks","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"Two components, not one. The rule sits on the product; the check sits on a second component of type validation, one per engine, and reaches back by rule id and the uuid of the component the rule belongs to."}]},"4":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"assessment-subjects\": [\n {\n \"type\": \"inventory-item\",\n \"description\": \"The instances this assessment may touch.\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ],\n \"tasks\": [\n {\n \"uuid\": \"068cacee-b6b7-49c7-844e-e80c42f25fb7\",\n \"type\": \"action\",\n \"title\": \"Assess Ubuntu 24.04 LTS\",\n \"associated-activities\": [\n {\n \"activity-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[3,14]],"focus_key":"assessment-subjects","label":"What the checks run against","rule":"both","shows":"One host, named explicitly as an inventory item."}],"catalog-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"83fd01c4-5007-4281-84bc-2fa040f75e14\",\n \"control-id\": \"UBTU-24-600090\",\n \"by-components\": [\n {\n \"uuid\": \"013a942e-ff7e-466d-821e-c84498c1b9be\",\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"description\": \"The rule was implemented.\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[8,14]],"focus_key":"by-components","label":"What the checks run against","rule":"both","shows":"Every component the catalog applies to, taken together."}],"component-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"c1ea1b60-eab2-46d3-8134-89ac8affdc8a\",\n \"control-id\": \"UBTU-24-600090\",\n \"by-components\": [\n {\n \"uuid\": \"f473f847-a826-48e5-8d9f-53ae40333b88\",\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"description\": \"The rule was implemented.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[8,19]],"focus_key":"by-components","label":"What the checks run against","rule":"both","shows":"The components carrying the rules, named by uuid."},{"content":"{\n \"assessment-plan\": {\n \"assessment-assets\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Copied from the component definition the system owner used.\",\n \"status\": {\n \"state\": \"operational\"\n },\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n },\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[13,26]],"focus_key":"checks","label":"The same component, copied into the assessor's plan","rule":"assessor","shows":"The component definition carried into an assessment plan as an asset. The checks travel with the component that runs them, and each names the component it tests."}]},"5":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"steps\": [\n {\n \"uuid\": \"333ddd0f-22da-4c18-8bc3-98e808746bca\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n },\n \"assessment-assets\": {\n \"components\": [\n {\n \"uuid\": \"56270516-2673-4d4c-8d4f-52e4107f968d\",\n \"type\": \"validation\",\n \"title\": \"The check runner plugin\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"status\": {\n \"state\": \"operational\"\n },\n \"props\": [\n {\n \"name\": \"context\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"{\\\"plugin-path\\\": \\\"runner.plugin\\\", \\\"opa-path\\\": \\\"/usr/local/bin\\\"}\"\n }\n ]\n }\n ],\n \"assessment-platforms\": [\n {\n \"uuid\": \"97f00129-f4ab-424f-8cd0-5ad1fc54f667\",\n \"title\": \"The scanning platform\",\n \"uses-components\": [\n {\n \"component-uuid\": \"56270516-2673-4d4c-8d4f-52e4107f968d\"\n }\n ]\n }\n ]\n },\n \"tasks\": [\n {\n \"uuid\": \"fa3faf4f-3ac3-432c-8d2f-4401173822ea\",\n \"type\": \"action\",\n \"title\": \"Execute the checks\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"97f00129-f4ab-424f-8cd0-5ad1fc54f667\"\n }\n ],\n \"associated-activities\": [\n {\n \"activity-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-all\": {}\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[13,17]],"focus_key":"name=check","label":"What the run reads: the checks and the platform","rule":"assessor-in","shows":"The checks and what runs them, in one plan the assessor owns."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for UBTU-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\"\n }\n ]\n },\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for UBTU-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"title\": \"Observation: SV-270747r1066730_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n },\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"title\": \"Observation: SV-270732r1066685_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[11,11],[27,27],[52,52],[69,69]],"focus_key":"target-id, subject-uuid","label":"What the run produces: the observation","rule":"assessor-out","shows":"The observation names the activity that ran. No plan of record has to exist for it to resolve."}],"catalog-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"272c65cb-9a6d-4344-8938-2e6203673884\",\n \"type\": \"software\",\n \"title\": \"SV-270747r1066730_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-600090.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270747R1066730_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"9133615a-9ffc-4656-8ca7-2b249482ee22\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"b971b7c8-6b4f-4188-8ceb-968a4aacb040\",\n \"control-id\": \"UBTU-24-600090\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n },\n {\n \"uuid\": \"65157847-efa3-4d97-8e62-f6148c556255\",\n \"type\": \"software\",\n \"title\": \"SV-270732r1066685_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-400320.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270732R1066685_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"2293c543-d5f7-45e3-8ef3-3917f9e5ccc1\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"3f57d132-ea15-4517-8398-778950a14382\",\n \"control-id\": \"UBTU-24-400320\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[10,14],[37,41]],"focus_key":"name=ConfigRuleId","label":"What the run reads: the check components","rule":"implementor-in","shows":"The check components the run is handed. What runs them is never named."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"UBTU-24-600090\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-600090_smt\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\"\n }\n ]\n }\n ]\n },\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"UBTU-24-400320\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-400320_smt\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18],[29,35]],"focus_key":"by-components","label":"What the run produces: the response in the plan of record","rule":"implementor-out","shows":"A by-component saying the control is met. Nothing on it names the check that produced it."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted on the target host.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"5ca997b3-bb3e-4c7a-8969-69ed44577d47\"\n },\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length on the target host.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"da810545-1635-4323-8e22-a74ddbe2c31d\"\n }\n ]\n }\n ]\n }\n}","focus":[[15,28]],"focus_key":"checks","label":"What the run reads: the checks it is handed","rule":"implementor-in","shows":"The checks the run is handed, each naming its rule and its subject."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"sc-28\",\n \"statements\": [\n {\n \"statement-id\": \"sc-28_smt.a\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n }\n ]\n }\n ]\n },\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"ia-5.1\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_password_min_length\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[17,21],[39,43]],"focus_key":"implementing-rules","label":"What the run produces: the assertion in the plan of record","rule":"implementor-out","shows":"The response the run writes, carrying implementing-rules so the assertion and its check travel together."},{"content":"{\n \"assessment-plan\": {\n \"assessment-assets\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Copied from the component definition the system owner used.\",\n \"status\": {\n \"state\": \"operational\"\n },\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n },\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[13,26]],"focus_key":"checks","label":"What the run reads: the same checks, in the assessor's plan","rule":"assessor-in","shows":"The same definition, taken into a plan the assessor owns. The checks travel with it."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"description\": \"SV-270747r1066730_rule\",\n \"assessment-check-id\": \"SV-270747r1066730_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n },\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"description\": \"SV-270732r1066685_rule\",\n \"assessment-check-id\": \"SV-270732r1066685_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[9,9],[10,10],[25,25],[26,26]],"focus_key":"assessment-check-id, result","label":"What the run produces: the observation","rule":"assessor-out","shows":"The check identifier joins back to what ran, and the subject is a host rather than a component."}]},"6a":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"import-ssp\": {\n \"href\": \"#d381c885-4851-4931-828c-29bbb24fbaa3\"\n },\n \"back-matter\": {\n \"resources\": [\n {\n \"uuid\": \"d381c885-4851-4931-828c-29bbb24fbaa3\",\n \"title\": \"Ubuntu 24.04 LTS system security plan\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"oscal-ssp\"\n }\n ],\n \"rlinks\": [\n {\n \"href\": \"system-security-plan.json\",\n \"media-type\": \"application/oscal.ssp+json\"\n }\n ],\n \"remarks\": \"Use this to point to an OSCAL-based SSP.\"\n },\n {\n \"uuid\": \"8bb824b6-255b-434c-8f68-e639deb75f89\",\n \"title\": \"System's full name\",\n \"description\": \"Use this resource when no OSCAL-based SSP exists. Briefly describe the system. This appears in the assessment result.\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"no-oscal-ssp\"\n }\n ],\n \"remarks\": \"Only include this resource if no OSCAL-based SSP is available.\"\n }\n ]\n }\n }\n}","focus":[[3,5]],"focus_key":"import-ssp","label":"One pointer, covering both rules","rule":"both","shows":"Not the claim, but where it lives. import-ssp resolves to a back-matter resource naming the system security plan, and a second resource covers the case where no OSCAL one exists."}],"catalog-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"UBTU-24-600090\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-600090_smt\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"by-components","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A by-component response in the SSP, against the product control."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"UBTU-24-400320\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-400320_smt\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"by-components","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A by-component response in the SSP, against the product control."}],"component-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"sc-28\",\n \"statements\": [\n {\n \"statement-id\": \"sc-28_smt.a\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[17,21]],"focus_key":"implementing-rules","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"The same shape, against the framework control, and carrying implementing-rules so the claim names the rule it rests on."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"ia-5.1\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_password_min_length\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[17,21]],"focus_key":"implementing-rules","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"The same shape, against the framework control, and carrying implementing-rules so the claim names the rule it rests on."}]},"6b":{"assessment-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for UBTU-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"title\": \"Observation: SV-270747r1066730_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A finding, targeting the framework control's statement."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for UBTU-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"title\": \"Observation: SV-270732r1066685_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A finding, targeting the framework control's statement."}],"catalog-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for UBTU-24-600090\",\n \"target\": {\n \"type\": \"statement-id\",\n \"target-id\": \"UBTU-24-600090_smt\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"title\": \"Observation for UBTU-24-600090\",\n \"description\": \"The configuration rule was evaluated on the component.\",\n \"methods\": [\n \"TEST\"\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A finding, targeting the product control's statement."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for UBTU-24-400320\",\n \"target\": {\n \"type\": \"statement-id\",\n \"target-id\": \"UBTU-24-400320_smt\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"title\": \"Observation for UBTU-24-400320\",\n \"description\": \"The configuration rule was evaluated on the component.\",\n \"methods\": [\n \"TEST\"\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A finding, targeting the product control's statement."}],"component-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"description\": \"SV-270747r1066730_rule\",\n \"assessment-check-id\": \"SV-270747r1066730_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[10,10]],"focus_key":"result","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"An observation carrying the check id and its result."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"observations\": [\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"description\": \"SV-270732r1066685_rule\",\n \"assessment-check-id\": \"SV-270732r1066685_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[10,10]],"focus_key":"result","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"An observation carrying the check id and its result."}]}},"note":"Our own encodings. Two rules, written in all three shapes, so the only thing that changes between the columns is the modelling.","rules":[{"check_id":"SV-270747r1066730_rule","control":"sc-28","key":"data-at-rest","label":"Rule 1, data at rest","statement":"Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.","stig":{"category":"CAT II","group":"V-270747","id":"UBTU-24-600090","rule":"SV-270747r1066730_rule","severity":"medium"},"why_chosen":"A binary condition with no value to set. It is the simple case, and it is the one all three approaches already have an analogue for."},{"check_id":"SV-270732r1066685_rule","control":"ia-5.1","key":"password-min-length","label":"Rule 2, minimum password length","statement":"Ubuntu 24.04 LTS must enforce a minimum 15-character password length.","stig":{"category":"CAT II","group":"V-270732","id":"UBTU-24-400320","rule":"SV-270732r1066685_rule","severity":"medium"},"why_chosen":"The same shape as the first rule but carrying a value, so it is the rule that shows where each approach puts a parameter. Publishers disagree on the number, which is why the number has to live somewhere addressable."}],"target":{"title":"Ubuntu 24.04 LTS","why":"One target, so the only thing that changes between the three columns is the modelling. Ubuntu because both rules are published for it, by DISA, and a reader can check them."}},"data/provenance.json":{"generated_at":"2026-10-09T18:46:33+00:00","snippet_count":32,"snippets":[{"approach":"assessment-first","bytes":4370,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-activity-v259312","language":"json","pointer":"/assessment-plan/local-definitions/activities/100","sha256_of_content":"f2968c0009fd012a241dc8e3e86173ac47bb4475624d3ccd01d77efd53964e31","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG activity V-259312"},{"approach":"assessment-first","bytes":6648,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-sc28-v270747","language":"json","pointer":"/assessment-plan/local-definitions/activities/101","sha256_of_content":"f6505f9312ba86546b17001b14b7ad797cd83fb68699749488086edb5ac0e8f2","sha256_of_source_file":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","title":"STIG activity V-270747, SC-28"},{"approach":"assessment-first","bytes":1976,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-step-props","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0","sha256_of_content":"e369bbc630cc85afc2a07e99fca48e213cabd815f4bc02ef1ec15034d2b7c33a","sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS audit step props"},{"approach":"assessment-first","bytes":999,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-remediation-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/1","sha256_of_content":"953c73006718d3632307bf47755dc4924e6164f3c03a53e96a3f3d058a4883bd","sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS remediation step"},{"approach":"assessment-first","bytes":270,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","sha256_of_content":"c3298e80edbf681c6da3e2965d161f81804db9d940539e41f77a19cf21e544e0","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA activity context prop"},{"approach":"assessment-first","bytes":928,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","sha256_of_content":"60c8183fb14d09b5f27513b84f394bf8a48670eadaf2f73fd834bc7300011240","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-assets"},{"approach":"assessment-first","bytes":1828,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","sha256_of_content":"ec5873d16ce6100d9be8cce518945b3aee95c50d2ae1ace4e298b860f8433b8f","sha256_of_source_file":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653","slot":"3","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-maester.json","title":"CISA step context prop"},{"approach":"assessment-first","bytes":243,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-related-controls","language":"json","pointer":"/assessment-plan/local-definitions/activities/100/related-controls","sha256_of_content":"2f52e4b5053678f3323139865183d634ff1206753079feff31bcaff76f53c93e","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"2","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG related-controls, the control tie"},{"approach":"assessment-first","bytes":197,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-step-reviewed","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0/reviewed-controls","sha256_of_content":"52c2919dc4f34fd2fbc5907450582b436e7e929a031c2bdb5a9c83d4ae18b30d","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"2","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA step reviewed-controls"},{"approach":"assessment-first","bytes":127,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-subjects-includeall","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"60d2f0f2a596673779c7804e0c6ea2bcc0609b41d54dc4d3c698be49bf268a82","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"4","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG assessment-subjects, include-all"},{"approach":"assessment-first","bytes":277,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"01c9afa2b4ee716f8534f4a2f12777d7202d741c06a7d5182619ca8f3afbc3fe","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"4","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-subjects, one inventory item"},{"approach":"assessment-first","bytes":2946,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"e5939a58c062351efa21b423729e40beeb72d3e13dd32757af065e4709dfbd60","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA task, with timing"},{"approach":"assessment-first","bytes":27,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","sha256_of_content":"84d4c12b8a05a19b8f99d8305498e5760d8bb8dfe987a2ecf4c38abd43d7557b","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"meta","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG import-ssp, an unresolved placeholder"},{"approach":"assessment-first","bytes":94,"extracted_at":"2026-08-22T18:44:16+00:00","id":"ez-cisa-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","sha256_of_content":"b26671d77e040a71e3470a5a13e0f043d7b130bf7b7688629f6405f136b1b7d2","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"import-ssp, resolving to a resource in the same document"},{"approach":"assessment-first","bytes":357,"extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/1","sha256_of_content":"401a0f63ea6221c571902ef0ba27bd50cce9fe2baa09b0cf520e48fa20539f1d","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The resource a resolved import-ssp lands on"},{"approach":"assessment-first","bytes":686,"extracted_at":"2026-08-22T18:46:12+00:00","id":"ez-cisa-no-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/0","sha256_of_content":"e0431570c0eb7d51ecec3ca35a340ae8c920c4c6afc08bb6a36760af82ef1e18","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The alternative resource, where no OSCAL system security plan exists"},{"approach":"assessment-first","bytes":466,"extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ar-finding","language":"json","pointer":"/assessment-results/results/0/findings/0","sha256_of_content":"4e3cfedd3c68517765d05d2cd46cdc0124a29c593c889cba16035c8ab84c1fe0","sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"A finding, targeting an objective"},{"approach":"assessment-first","bytes":762,"extracted_at":"2026-08-22T18:43:41+00:00","id":"ez-cisa-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","sha256_of_content":"631850409afd117649f1abec4da6e649bab0d2d4226d2a28f77d9918ec506b3a","sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"The observation it rests on, and what was examined"},{"approach":"assessment-first","bytes":469,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-resolution-status","language":"json","pointer":"/assessment-plan/reviewed-controls/control-selections/0","sha256_of_content":"4befe7d29d300effc4bdd88c120c2c1f1c00497fc28990444f62c198bc111d04","sha256_of_source_file":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8","slot":"meta","source":"Easy Dynamics/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","title":"CIS resolution status"},{"approach":"catalog-first","bytes":1402,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm2-control","language":"json","pointer":"/catalog/groups/0/controls/1","sha256_of_content":"a7f2e132f5d8e27309dbec9c9b114ed87105ee326046773c5cfe05f5da5b1ab4","sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"ACM.2, the control"},{"approach":"catalog-first","bytes":1177,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-rsa-check-component","language":"json","pointer":"/component-definition/components/2","sha256_of_content":"c4df1c40cb50ca7dd6e7d18862853fef78189e789623abf1c177ea49c9d0b3a1","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"3","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"acm-certificate-rsa-check, the check component"},{"approach":"catalog-first","bytes":538,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-backmatter-source","language":"json","pointer":"/component-definition/back-matter","sha256_of_content":"5e916dfa3cdf4d22fbbf601a1f6b18bc69b0a65d9367e906c26ba11901ab03cd","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"Back-matter, source to the catalog"},{"approach":"catalog-first","bytes":1444,"extracted_at":"2026-08-21T03:10:41+00:00","id":"aws-control-cloudtrail2","language":"json","pointer":"/catalog/groups/15/controls/2","sha256_of_content":"ae48dd920cb756ba4afaec14989d62d63c1954361757346114e807768609940b","sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"CloudTrail.2, the control"},{"approach":"catalog-first","bytes":1439,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-input-parameter","language":"json","pointer":"/component-definition/components/2/props","sha256_of_content":"b8d9cec13e53ca016cfe380b637fec8adfe353e9098e37d90bd28cacf98dcee1","sha256_of_source_file":"940cab9d3328d5ff55e6c69fbfae6fd4e846873d07f70ef7c096651bc8f750ab","slot":"1","source":"AWS/oscal-content-for-aws-services-main/component-definitions/iam.oscal.json","title":"InputParameter props, the parameter mechanism"},{"approach":"catalog-first","bytes":493,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-service-rollup","language":"json","pointer":"/component-definition/components/0/control-implementations/0","sha256_of_content":"dd53d5bd8e01cbaa2b198cf7504ece6374b931ec86c373ae5c9003e34d75dd44","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"AWS Certificate Manager, the service roll-up"},{"approach":"catalog-first","bytes":1367,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-config-service-bare","language":"json","pointer":"/component-definition/components/0","sha256_of_content":"3b3b0c533e8fe9ebc892b5cdf0003bb265591ae3486e5d6317aa847480d88541","sha256_of_source_file":"d5049e46d7a1251932be3e74c1f9bace606ac9b5f5542249ccb884171394a6e7","slot":"5","source":"AWS/oscal-content-for-aws-services-main/component-definitions/config.oscal.json","title":"AWS Config, the engine that runs the checks"},{"approach":"component-first","bytes":1909,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-cos-component","language":"json","pointer":"/component-definition/components/0","sha256_of_content":"63bda68a0ec328946a2ba363442053d4976a7ea78ccc27da761f4dbfc9feae4b","sha256_of_source_file":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a","slot":"1","source":"IBM/cos-component-definition.json","title":"COS component, carrying rules"},{"approach":"component-first","bytes":686,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-statement-rules","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/0","sha256_of_content":"d835c9264269a53f2fbbb988dfe83509b7610a445742300ace8703259dbb3edd","sha256_of_source_file":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf","slot":"2","source":"IBM/idservice-component-definition.json","title":"implementing-rules on ia-5.1"},{"approach":"component-first","bytes":1106,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-validation-ansible","language":"json","pointer":"$","sha256_of_content":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","sha256_of_source_file":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","slot":"3","source":"IBM/ansible-validation-component-definition.json","title":"Ansible validation component, and its checks"},{"approach":"component-first","bytes":624,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-activity","language":"json","pointer":"/assessment-plan/local-defintions","sha256_of_content":"b0157c12fb61e61809b3970895e3d1e9bba4b8c8bfe31c7f20e01ac292c1b252","sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"5","source":"IBM/assessment-plan.json","title":"AP activity, binding check-ids"},{"approach":"component-first","bytes":907,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-task-subjects","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"9852eeea94dab48f8ee5f7351c3ecc86a42be3e2dfd594626cae759ba163e9cd","sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"4","source":"IBM/assessment-plan.json","title":"AP task, subjects and platform"},{"approach":"component-first","bytes":1125,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","sha256_of_content":"eb0d665abc0dc6c1d6528291f5888816e6db04a427d7aaa6bd52bc395d1f9595","sha256_of_source_file":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806","slot":"6b","source":"IBM/assessment-result.json","title":"AR observation, carrying a result"}],"source_inputs":{"sources":[{"approach":"component-first","directory":"examples/component-first","expected_files":8,"key":"ibm","prefix":"IBM"},{"approach":"assessment-first","directory":"examples/assessment-first","expected_files":19,"key":"easy-dynamics","prefix":"Easy Dynamics"},{"approach":"catalog-first","archive_bytes":379596,"archive_sha256":"f309b59344560b88a699c5908fbc70c51c7a0e8e0339d901b1285b9c8d804a18","directory":".cache/oscal-sources/aws/4a1779ffb556c4ab8fb3dad94a19d4d198116803","file_base":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/","json_files":231,"key":"aws","prefix":"AWS/oscal-content-for-aws-services-main","repository":"awslabs/oscal-content-for-aws-services","revision":"4a1779ffb556c4ab8fb3dad94a19d4d198116803","url":"https://codeload.github.com/awslabs/oscal-content-for-aws-services/tar.gz/4a1779ffb556c4ab8fb3dad94a19d4d198116803"}],"version":1},"source_lock":"tools/source-lock.json"},"data/questions.json":{"intro":"These questions identify unresolved design choices, not recommended changes. Each question sits under the approach where it is most acute, not exclusively; a question that applies to every approach sits in the shared section. The analysis distinguishes what the OSCAL examples demonstrate from what remains open across models and approaches.","note":"Editorial analysis questions maintained in this repository, grouped by issues shared across all approaches and issues specific to each approach. Each question includes its reasoning; the OSCAL examples provide evidence without settling the design choices.","sections":[{"intro":"Questions shared by all three approaches. None is answered by choosing an approach, and each affects how the resulting artifacts are interpreted.","key":"all","label":"Across all three approaches","questions":[{"id":"xccdf","q":"Should OSCAL carry this content at all, when XCCDF already does?","why":"XCCDF already represents benchmark checklists. OSCAL could carry equivalent content or connect checklist references to implementation and assessment records. These choices produce different artifacts, translation work and maintenance obligations. The OSCAL examples do not establish which boundary best supports interoperable hardening workflows."},{"id":"rule-metadata","metadata":["Severity","Weight","Version","Title","References","Identifiers","Vulnerability discussion","Check content","Fix text"],"q":"Where should rule metadata, including remediation, go?","why":"The DISA XCCDF benchmark carries the fields below, with distinct check and fix content. The AWS and DISA OSCAL examples use namespaced properties for severity rather than a dedicated field. The STIG and CIS assessment-plan examples include remediation as steps, but an AP step does not inherently distinguish a check from a fix; they rely on titles or step-type properties. Which metadata belongs in each OSCAL model, and how should consumers distinguish remediation from checks?"},{"id":"proposal-1","q":"What does an assessment-platform add when an assessment component already describes the runner?","why":"An OSCAL assessment plan can declare a runner as a component in assessment-assets, or describe an assessment-platform that includes a component. The examples do not establish what information the platform contributes beyond that component, such as execution context, or when that additional structure is needed. This choice applies regardless of where the hardening rule is modeled."},{"id":"proposal-3","q":"How should an assessment plan associate an assessment asset with its tasks or activities?","why":"Assessment results can associate a task and the assessment-platform that produced its results, using result origins and actors. An assessment plan has no corresponding way to say which component or assessment-platform should execute each task or activity before results exist. The component-first examples propose an assessment-asset-uuid and check-ids on each activity, naming the validation component that runs it and the checks it runs. The plan-side linkage is needed in all three approaches."},{"id":"proposal-4","q":"How should an observation identify the assessment asset and check that produced it when several assets are declared?","why":"An assessment result may hold observations from several assessment assets. In the current model, an observation can name the tool or assessment-platform that produced it through origin actors, but has no field naming the check it ran. The component-first examples propose an asset UUID and a check identifier on each observation, so a consumer can follow observation, asset, check, rule and control. The question applies to every approach that reports automated results."},{"id":"paper-comp-2","q":"Should desired-state values from benchmark guidance be replaced with actual-state values in the SSP?","why":"Benchmark guidance prescribes configuration values, while an SSP records the system owner's implementation claims, so every approach that produces SSP content faces this choice. In the component-first examples the SSP author copies a rule's parameters and may set a value equal to, stricter than or looser than the default. Replacing prescribed values could lose the benchmark baseline; keeping only prescribed values could misrepresent the implementation. How should tools keep the two meanings distinct?"}]},{"intro":"The rule is a control in a catalog. Open questions concern how catalogs combine, how many documents that produces and where outcomes land.","key":"catalog-first","label":"Catalog-first","questions":[{"id":"one-ssp","q":"Do many catalogs converge into one profile and one plan of record, or does each catalog need its own?","why":"A single plan of record could answer a profile merging the catalogs that apply to a system. Separate plans could instead answer each catalog. These structures produce different file counts and response locations, and change whether benchmark outcomes sit beside regulatory outcomes. The worked scenario assumes convergence and counts 18 files; the question is whether that structure meets implementation and assessment needs."},{"id":"requirement-level","q":"If OSCAL catalog controls gained a field for requirement level, how much of this disagreement would be left?","why":"OSCAL catalog controls have no dedicated core field distinguishing shall, should and may. The examples can carry such labels in properties, but consumers need conventions to interpret them. Catalog-first puts benchmark and regulatory controls into the same profile. It remains unclear how much model-placement disagreement concerns binding force rather than document structure, and whether a shared requirement-level field would reduce it."},{"id":"control-type","q":"Should an OSCAL catalog control declare its type, so a regulatory control and a technical hardening control can be told apart?","why":"The catalog/profile model can combine regulatory controls with technical hardening controls, but it has no dedicated core field distinguishing those kinds. Tools would need a shared property convention or schema support to report regulatory coverage separately from hardening coverage. This question concerns the kind of requirement, distinct from whether its requirement level is shall, should or may."},{"id":"paper-cat-1","q":"How should benchmark profiles compose with regulatory profiles as the number of controls grows?","why":"Combining benchmark and regulatory controls increases the work of resolving imports, selections, exclusions and parameter values. The question is how tools should compose and maintain those profiles at scale without obscuring which source supplied a requirement or how a tailoring decision changes downstream content."},{"id":"paper-cat-2","q":"Where should benchmark outcomes be recorded, in SSP implementation claims or assessment results, and how should tools distinguish them?","why":"An SSP by-component response describes an implementation claim, while assessment results record evidence and outcomes. A benchmark workflow may need both, but they answer different questions. Tools need to distinguish intended configuration from observed satisfaction and preserve the relationship between the two records."},{"id":"ssp-claim-evidence","q":"How should evidence be linked to an SSP implementation claim when a benchmark result is recorded there?","why":"An assessment-results observation can use relevant-evidence to point to supporting material. An SSP by-component implementation claim has no equivalent field for attaching evidence directly to the claim. If a benchmark outcome is recorded in the SSP, how should tools connect that claim to its supporting evidence without conflating it with an assessed result in an AR?"},{"id":"benchmark-vendor-catalogs","q":"How should an SSP combine benchmark and vendor catalogs that describe the same system recommendations?","why":"A benchmark and a vendor catalog may describe overlapping recommendations for the same system. An SSP responding to both needs to preserve which source supplied each recommendation while avoiding duplicate or conflicting implementation claims. It remains open whether one profile should reconcile those controls before the SSP imports it, or whether another convention should relate equivalent recommendations."}]},{"intro":"The rule sits on the component it configures, and that component carries the tie to the framework. Open questions concern reaching other frameworks, copying component definitions into an SSP and tailoring benchmark content.","key":"component-first","label":"Component-first","questions":[{"id":"which-cdef-maps","q":"When the rule component carries the framework tie, how should another framework reach the same rules?","why":"In this approach the component definition holding the rules carries the tie to the framework through implemented-requirements; a check reaches a control only through check, rule and control, and a validation component carries no framework tie. A system held to another framework can override the tie in its SSP, or transpose results through a mapping collection between the two frameworks. Which route preserves rule-level precision, and who maintains it, remains open."},{"id":"paper-comp-1","q":"How should an SSP combine benchmark and vendor component definitions that describe the same system component?","why":"A system may use vendor and benchmark component definitions for the same software, which can overlap in descriptions, rules and control implementations. OSCAL has no mechanism for importing a component definition, so the convention in this approach is to copy both into the SSP and merge them into one component, keeping only the rules that serve the profile's controls. What remains open is how a merged component records which source supplied each rule."},{"id":"paper-comp-3","q":"Which benchmark context should enter an SSP, and how should tools filter component-definition content during import?","why":"Benchmark content can include rules, parameters, rationale and procedural detail. The convention in this approach copies the rule identifier, description, parameter identifier and value, and the implementing-rules tie to controls; audit and remediation procedures are optional, at the SSP author's discretion. Copying duplicates content across every SSP that uses the component. Whether an import mechanism should replace copying, and what filtering it would need, remains open."},{"id":"paper-comp-4","q":"How should component definitions support benchmark selection, exclusions and parameter tailoring?","why":"The component-first examples place parameters on proposed rules and set-parameters on control implementations. The convention in this approach is to tailor while copying: the SSP author drops rules that serve no selected control and sets parameter values, with no link back to the source component definition. That serves one system, but leaves open how tailoring decisions persist and stay auditable when the source component definition changes."},{"id":"paper-comp-5","q":"Should assessment plans or assessment results support importing component definitions with benchmark context?","why":"The component-first examples carry checks into an assessment plan as assessment assets, while rules stay in the SSP and reach the plan and results through their imports, so SSP tailoring carries forward. That demonstrates one encoding, not a dedicated import mechanism. The question is whether plans or results should import component definitions directly, and which rules, parameters and provenance would need to survive."}]},{"intro":"The rule is an activity in an assessment plan. The open question concerns tailoring requirements without losing their assessment context.","key":"assessment-first","label":"Assessment-first","questions":[{"id":"paper-ap-1","q":"How should assessment-plan benchmarks support tailoring available through catalogs and profiles?","why":"OSCAL assessment-plan activities and steps have no parameter assembly, so the assessment-first examples place required values in text. Tailoring can therefore require editing procedural content rather than selecting controls or setting parameter values through a profile. The question is how to support reusable, auditable tailoring without losing the assessment workflow."}]}]},"data/scenario-evidence/nist-high-baseline.json":{"counts":{"base":188,"controls":370,"enhancements":182,"families":18},"fetched_at":"2026-08-23","note":"The control identifiers selected by the NIST SP 800-53 Revision 5 HIGH baseline profile. Stored so the scenario's control count can be recomputed here rather than quoted from memory.","oscal_version":"1.2.2","pointer":"/profile/imports/0/include-controls/0/with-ids","profile_last_modified":"2026-05-11","profile_version":"5.2.0","source":"https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_HIGH-baseline_profile.json","title":"Electronic (OSCAL) Version of NIST Special Publication 800-53 Revision 5.1.1 HIGH IMPACT BASELINE","with_ids":["ac-1","ac-2","ac-2.1","ac-2.2","ac-2.3","ac-2.4","ac-2.5","ac-2.11","ac-2.12","ac-2.13","ac-3","ac-4","ac-4.4","ac-5","ac-6","ac-6.1","ac-6.2","ac-6.3","ac-6.5","ac-6.7","ac-6.9","ac-6.10","ac-7","ac-8","ac-10","ac-11","ac-11.1","ac-12","ac-14","ac-17","ac-17.1","ac-17.2","ac-17.3","ac-17.4","ac-18","ac-18.1","ac-18.3","ac-18.4","ac-18.5","ac-19","ac-19.5","ac-20","ac-20.1","ac-20.2","ac-21","ac-22","at-1","at-2","at-2.2","at-2.3","at-3","at-4","au-1","au-2","au-3","au-3.1","au-4","au-5","au-5.1","au-5.2","au-6","au-6.1","au-6.3","au-6.5","au-6.6","au-7","au-7.1","au-8","au-9","au-9.2","au-9.3","au-9.4","au-10","au-11","au-12","au-12.1","au-12.3","ca-1","ca-2","ca-2.1","ca-2.2","ca-3","ca-3.6","ca-5","ca-6","ca-7","ca-7.1","ca-7.4","ca-8","ca-8.1","ca-9","cm-1","cm-2","cm-2.2","cm-2.3","cm-2.7","cm-3","cm-3.1","cm-3.2","cm-3.4","cm-3.6","cm-4","cm-4.1","cm-4.2","cm-5","cm-5.1","cm-6","cm-6.1","cm-6.2","cm-7","cm-7.1","cm-7.2","cm-7.5","cm-8","cm-8.1","cm-8.2","cm-8.3","cm-8.4","cm-9","cm-10","cm-11","cm-12","cm-12.1","cp-1","cp-2","cp-2.1","cp-2.2","cp-2.3","cp-2.5","cp-2.8","cp-3","cp-3.1","cp-4","cp-4.1","cp-4.2","cp-6","cp-6.1","cp-6.2","cp-6.3","cp-7","cp-7.1","cp-7.2","cp-7.3","cp-7.4","cp-8","cp-8.1","cp-8.2","cp-8.3","cp-8.4","cp-9","cp-9.1","cp-9.2","cp-9.3","cp-9.5","cp-9.8","cp-10","cp-10.2","cp-10.4","ia-1","ia-2","ia-2.1","ia-2.2","ia-2.5","ia-2.8","ia-2.12","ia-3","ia-4","ia-4.4","ia-5","ia-5.1","ia-5.2","ia-5.6","ia-6","ia-7","ia-8","ia-8.1","ia-8.2","ia-8.4","ia-11","ia-12","ia-12.2","ia-12.3","ia-12.4","ia-12.5","ir-1","ir-2","ir-2.1","ir-2.2","ir-3","ir-3.2","ir-4","ir-4.1","ir-4.4","ir-4.11","ir-5","ir-5.1","ir-6","ir-6.1","ir-6.3","ir-7","ir-7.1","ir-8","ma-1","ma-2","ma-2.2","ma-3","ma-3.1","ma-3.2","ma-3.3","ma-4","ma-4.3","ma-5","ma-5.1","ma-6","mp-1","mp-2","mp-3","mp-4","mp-5","mp-6","mp-6.1","mp-6.2","mp-6.3","mp-7","pe-1","pe-2","pe-3","pe-3.1","pe-4","pe-5","pe-6","pe-6.1","pe-6.4","pe-8","pe-8.1","pe-9","pe-10","pe-11","pe-11.1","pe-12","pe-13","pe-13.1","pe-13.2","pe-14","pe-15","pe-15.1","pe-16","pe-17","pe-18","pl-1","pl-2","pl-4","pl-4.1","pl-8","pl-10","pl-11","ps-1","ps-2","ps-3","ps-4","ps-4.2","ps-5","ps-6","ps-7","ps-8","ps-9","ra-1","ra-2","ra-3","ra-3.1","ra-5","ra-5.2","ra-5.4","ra-5.5","ra-5.11","ra-7","ra-9","sa-1","sa-2","sa-3","sa-4","sa-4.1","sa-4.2","sa-4.5","sa-4.9","sa-4.10","sa-5","sa-8","sa-9","sa-9.2","sa-10","sa-11","sa-15","sa-15.3","sa-16","sa-17","sa-21","sa-22","sc-1","sc-2","sc-3","sc-4","sc-5","sc-7","sc-7.3","sc-7.4","sc-7.5","sc-7.7","sc-7.8","sc-7.18","sc-7.21","sc-8","sc-8.1","sc-10","sc-12","sc-12.1","sc-13","sc-15","sc-17","sc-18","sc-20","sc-21","sc-22","sc-23","sc-24","sc-28","sc-28.1","sc-39","si-1","si-2","si-2.2","si-3","si-4","si-4.2","si-4.4","si-4.5","si-4.10","si-4.12","si-4.14","si-4.20","si-4.22","si-5","si-5.1","si-6","si-7","si-7.1","si-7.2","si-7.5","si-7.7","si-7.15","si-8","si-8.2","si-10","si-11","si-12","si-16","sr-1","sr-2","sr-2.1","sr-3","sr-5","sr-6","sr-8","sr-9","sr-9.1","sr-10","sr-11","sr-11.1","sr-11.2","sr-12"]},"data/scenario.json":{"approaches":{"assessment-first":{"files":[{"count":1,"detail":"800-53 Revision 5","items":[{"name":"NIST 800-53"}],"model":"catalog","what":"the framework only"},{"count":1,"detail":"","items":[{"name":"800-53 High"}],"model":"profile","what":"the High baseline"},{"count":0,"detail":"activities identify related controls; reviewed-controls defines the assessment plan's control scope","model":"mapping-collection","what":"none, framework mappings are on activities"},{"count":0,"detail":"assessment-assets contains the components running checks; separate component definition documents are not needed","model":"component-definition","what":"none, engines are identified in each plan"},{"count":1,"detail":"assessment plans reference the system security plan without adding guidance to the implementation claims","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 370 controls"},{"count":4,"detail":"the three guides contain 547 requirements as activities and steps; each assessment plan references one system security plan through import-ssp","items":[{"name":"800-53 AP"},{"name":"CIS Ubuntu AP"},{"name":"DISA PgSQL AP"},{"name":"CISA SCuBA AP"}],"model":"assessment-plan","what":"one for the framework assessment, one per guide"},{"count":4,"detail":"four results documents, not four sections in one document; import-ap is a single required object referencing exactly one assessment plan","items":[{"name":"800-53 AR"},{"name":"CIS Ubuntu AR"},{"name":"DISA PgSQL AR"},{"name":"CISA SCuBA AR"}],"model":"assessment-results","what":"one per plan; each result references exactly one plan"}],"plan_of_record":"The system security plan addresses 370 controls; all three guides remain in assessment plans","rule":"Each guide becomes an assessment plan with a separate assessment results document. The framework catalog and baseline profile remain unchanged."},"catalog-first":{"files":[{"count":4,"detail":"800-53 Revision 5, CIS Ubuntu, DISA PostgreSQL, CISA SCuBA","items":[{"name":"NIST 800-53"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"}],"model":"catalog","what":"one for the framework, one for each guide"},{"count":5,"detail":"the High baseline, three guide selections and an organisational profile merging all four selections; import-profile is a single required object in the system security plan","items":[{"name":"800-53 High"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"},{"name":"Org merged"}],"model":"profile","what":"one selection per catalog and one merged selection"},{"count":3,"detail":"without mappings, guidance controls and framework controls remain two unrelated sets in the system security plan","items":[{"name":"CIS to 800-53"},{"name":"STIG to 800-53"},{"name":"SCuBA to 800-53"}],"model":"mapping-collection","what":"one per guide, linking guidance controls to framework controls"},{"count":3,"detail":"the control references a check identifier; a software component with a matching name describes the check's execution","items":[{"kind":"software","name":"Ubuntu checks"},{"kind":"software","name":"PgSQL checks"},{"kind":"software","name":"M365 checks"}],"model":"component-definition","what":"one per technology, containing check components"},{"count":1,"detail":"370 framework controls and 547 guidance controls, each requiring a by-component response; one import-profile references the merged profile because the field is a single required object","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 917 controls"},{"count":1,"detail":"","items":[{"name":"System AP"}],"model":"assessment-plan","what":"one"},{"count":1,"detail":"","items":[{"name":"System AR"}],"model":"assessment-results","what":"one"}],"plan_of_record":"The system security plan addresses 917 controls: 370 from the framework and 547 from the guides","rule":"Each guide becomes a catalog with a selection profile and a mapping collection linking guidance to the framework. The system security plan addresses every control in the merged set."},"component-first":{"files":[{"count":1,"detail":"800-53 Revision 5","items":[{"name":"NIST 800-53"}],"model":"catalog","what":"the framework only"},{"count":1,"detail":"","items":[{"name":"800-53 High"}],"model":"profile","what":"the High baseline"},{"count":0,"detail":"control implementations identify the controls served by the rules; no separate document carries the mapping","model":"mapping-collection","what":"none, framework mappings are inside component definitions"},{"count":6,"detail":"Ubuntu, PostgreSQL and Microsoft 365, with one validation component definition per checking engine","items":[{"kind":"software","name":"Ubuntu"},{"kind":"software","name":"PostgreSQL"},{"kind":"software","name":"Microsoft 365"},{"kind":"validation","name":"Ubuntu checks"},{"kind":"validation","name":"PgSQL checks"},{"kind":"validation","name":"M365 checks"}],"model":"component-definition","what":"three products with 547 rules, three engines with checks"},{"count":1,"detail":"the control count remains unchanged; rules are included in system-implementation","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 370 controls and containing 547 rules"},{"count":1,"detail":"","items":[{"name":"System AP"}],"model":"assessment-plan","what":"one"},{"count":1,"detail":"","items":[{"name":"System AR"}],"model":"assessment-results","what":"one"}],"plan_of_record":"The system security plan addresses 370 controls and contains 547 desired-state rules in components","rule":"Each guide becomes rules on the component being configured. Each checking engine becomes a separate validation component. The framework catalog and baseline profile remain unchanged."}},"excluded_model":{"model":"plan-of-action-and-milestones","reason":"The plan of action and milestones records unmet requirements and remediation. The document serves the same purpose in all three approaches and is excluded from the comparison."},"framework":{"base":188,"controls":370,"derivation":"count of /profile/imports/0/include-controls/0/with-ids in the published HIGH baseline profile, version 5.2.0","enhancements":182,"families":18,"label":"NIST SP 800-53 Revision 5, High baseline","source":"data/scenario-evidence/nist-high-baseline.json"},"hardening":[{"count_rule":"audit-steps","derivation":"count of steps titled 'Audit for ...' in Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json. The file carries 616 steps, one audit and one remediation for each recommendation, in 53 activities.","grouping":53,"grouping_label":"sections","key":"cis-ubuntu","label":"CIS Ubuntu 24.04 LTS Benchmark","requirements":308,"source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","technology":"Ubuntu"},{"count_rule":"step-type-check","derivation":"count of props step-type=check in Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json. The file carries 111 activities and 222 steps, one check and one remediate for each.","grouping":111,"grouping_label":"activities, one per requirement","key":"disa-postgres","label":"DISA STIG PostgreSQL 16","requirements":111,"source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","technology":"PostgreSQL"},{"count_rule":"steps","derivation":"count of steps in Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json, which carries 128 steps across 7 activities, one activity per Microsoft 365 service.","grouping":7,"grouping_label":"services","key":"cisa-bod-25-01","label":"CISA BOD 25-01 SCuBA","requirements":128,"source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","technology":"Microsoft 365"}],"items_note":"Each entry represents one file, with a name shortened for the diagram tile. Component-first distinguishes the product component, of type software, from the checking component, of type validation. File counts alone do not show component types.","models":["catalog","profile","mapping-collection","component-definition","system-security-plan","assessment-plan","assessment-results"],"note":"One system, one baseline and three hardening guides, modelled with each approach. The scenario compares document counts and system security plan content, not overall capability. Counts derive from the corpus, the NIST profile in data/scenario-evidence/, or OSCAL schema constraints. Each file row records the applicable constraint.","summary":"A system follows the NIST SP 800-53 Revision 5 High baseline and hardening guides for Ubuntu, PostgreSQL and Microsoft 365. The three approaches model the same requirements, using every OSCAL model except the plan of action and milestones.","title":"One system, three hardening guides"},"data/schema-evidence/assessment-subject.json":{"constraints":["anyOf requires include-all or include-subjects","each selection branch has optional type with anyOf enum [\"component\",\"inventory-item\",\"location\",\"party\",\"user\"]"],"definition":"oscal-ap-oscal-assessment-common:assessment-subject","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ap-oscal-assessment-common:assessment-subject","anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description"},"exclude-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ap-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["component","inventory-item","location","party","user"]}],"description":"Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.","title":"Subject Type"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description"},"exclude-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"include-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["component","inventory-item","location","party","user"]}],"description":"Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.","title":"Subject Type"}},"required":["include-subjects"]}],"description":"Identifies system elements being assessed, such as components, inventory items, and locations. In the assessment plan, this identifies a planned assessment subject. In the assessment results this is an actual assessment subject, and reflects any changes from the plan. exactly what will be the focus of this assessment. Any subjects not identified in this way are out-of-scope.","title":"Subject of Assessment","type":"object"},"model":"assessment-plan","note":"OSCAL 1.2.1 assessment subjects select all subjects or an explicit set. The optional type vocabulary includes component, inventory-item, location, party and user, supporting assessment of individual hosts.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_assessment-plan_schema.json at definitions/oscal-ap-oscal-assessment-common:assessment-subject.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ap-schema.json"},"data/schema-evidence/by-component.json":{"constraints":["required == [\"component-uuid\",\"uuid\",\"description\"]","has property \"component-uuid\"","has no property \"subject\", \"subject-uuid\", \"inventory-item-uuid\" or \"type\""],"definition":"oscal-ssp-oscal-ssp:by-component","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ssp-oscal-ssp:by-component","additionalProperties":false,"description":"Defines how the referenced component implements a set of controls.","properties":{"component-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to the component that is implementing a given control.","title":"Component Universally Unique Identifier Reference"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes how a control or a control statement is implemented within the referenced system component.","title":"Control Implementation Description"},"export":{"additionalProperties":false,"description":"Identifies content intended for external consumption, such as with leveraged organizations.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that can be available to another system leveraging this system.","title":"Control Implementation Export Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided":{"items":{"additionalProperties":false,"description":"Describes a capability which may be inherited by a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that can be provided to another system leveraging this system.","title":"Provided Control Implementation Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Provided Universally Unique Identifier"}},"required":["uuid","description"],"title":"Provided Control Implementation","type":"object"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsibilities":{"items":{"additionalProperties":false,"description":"Describes a control implementation responsibility imposed on a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that a leveraging system must implement to satisfy the control provided by a leveraged system.","title":"Control Implementation Responsibility Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.","title":"Provided UUID"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Responsibility Universally Unique Identifier"}},"required":["uuid","description"],"title":"Control Implementation Responsibility","type":"object"},"minItems":1,"type":"array"}},"title":"Export","type":"object"},"implementation-status":{"$ref":"#/definitions/oscal-ssp-oscal-implementation-common:implementation-status"},"inherited":{"items":{"additionalProperties":false,"description":"Describes a control implementation inherited by a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is inheriting from a leveraged system.","title":"Inherited Control Implementation Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.","title":"Provided UUID"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Inherited Universally Unique Identifier"}},"required":["uuid","description"],"title":"Inherited Control Implementation","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"satisfied":{"items":{"additionalProperties":false,"description":"Describes how this system satisfies a responsibility imposed by a leveraged system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is implementing based on a requirement from a leveraged system.","title":"Satisfied Control Implementation Responsibility Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsibility-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system.","title":"Responsibility UUID"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Satisfied Universally Unique Identifier"}},"required":["uuid","description"],"title":"Satisfied Control Implementation Responsibility","type":"object"},"minItems":1,"type":"array"},"set-parameters":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-implementation-common:set-parameter"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"By-Component Universally Unique Identifier"}},"required":["component-uuid","uuid","description"],"title":"Component Control Implementation","type":"object"},"model":"system-security-plan","note":"The oscal-ssp-oscal-ssp:by-component definition, which is the only way a system security plan responds to a control. It is keyed by component-uuid and has no subject of any kind: no inventory-item, no location, no party, no user. A plan can describe inventory items elsewhere, in system-implementation, but a control response cannot be made against one, so two hosts of the same component share a single response.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_ssp_schema.json at definitions/oscal-ssp-oscal-ssp:by-component.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ssp-schema.json"},"data/schema-evidence/finding-target.json":{"constraints":["required == [\"type\",\"target-id\",\"status\"]","type is constrained by allOf to enum [\"statement-id\",\"objective-id\"]","status.required includes \"state\"","status.state enum == [\"satisfied\",\"not-satisfied\"]"],"definition":"oscal-ar-oscal-assessment-common:finding-target","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:finding-target","additionalProperties":false,"description":"Captures an assessor's conclusions regarding the degree to which an objective is satisfied.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the assessor's conclusions regarding the degree to which an objective is satisfied.","title":"Objective Status Description"},"implementation-status":{"$ref":"#/definitions/oscal-ar-oscal-implementation-common:implementation-status"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"status":{"additionalProperties":false,"description":"A determination of if the objective is satisfied or not within a given system.","properties":{"reason":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["pass","fail","other"]}],"description":"The reason the objective was given it's status.","title":"Objective Status Reason"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"state":{"allOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["satisfied","not-satisfied"]}],"description":"An indication as to whether the objective is satisfied or not.","title":"Objective Status State"}},"required":["state"],"title":"Objective Status","type":"object"},"target-id":{"$ref":"#/definitions/TokenDatatype","description":"A machine-oriented identifier reference for a specific target qualified by the type.","title":"Finding Target Identifier Reference"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this objective status.","title":"Objective Status Title"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["statement-id","objective-id"]}],"description":"Identifies the type of the target.","title":"Finding Target Type"}},"required":["type","target-id","status"],"title":"Objective Status","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:finding-target definition from the OSCAL 1.2.1 assessment-results model, demonstrating that a finding target requires type, target-id, and status, restricts type by allOf to the closed enumeration statement-id or objective-id, and requires a status.state drawn from the closed enumeration satisfied or not-satisfied.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/finding.json":{"constraints":["required includes \"target\""],"definition":"oscal-ar-oscal-assessment-common:finding","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:finding","additionalProperties":false,"description":"Describes an individual finding.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this finding.","title":"Finding Description"},"implementation-statement-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related.","title":"Implementation Statement UUID"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"origins":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:origin"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"related-observations":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:related-observation"},"minItems":1,"type":"array"},"related-risks":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:associated-risk"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"target":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:finding-target"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this finding.","title":"Finding Title"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Finding Universally Unique Identifier"}},"required":["uuid","title","description","target"],"title":"Finding","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:finding definition from the OSCAL 1.2.1 assessment-results model, demonstrating that every finding must carry a target.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/mapping-item.json":{"constraints":["required == [\"type\",\"id-ref\"]","type is constrained by allOf to enum [\"control\",\"statement\"]","no property named 'uuid'","no property named 'href'"],"definition":"oscal-mapping-oscal-mapping-common:mapping-item","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-mapping-oscal-mapping-common:mapping-item","additionalProperties":false,"description":"A specific edge within a source or target that is the subject of a mapping.","properties":{"id-ref":{"$ref":"#/definitions/StringDatatype","description":"A reference to an identified subject that is of the specified type .","title":"Subject Identifier Reference"},"links":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:remarks"},"type":{"allOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["control","statement"]}],"description":"The semantic type of the subject.","title":"Subject Type"}},"required":["type","id-ref"],"title":"Mapping Entry Item (source or target)","type":"object"},"model":"mapping-collection","note":"The oscal-mapping-oscal-mapping-common:mapping-item definition from the OSCAL 1.2.1 mapping-collection model, demonstrating that a mapping item requires only type and id-ref, restricts type by allOf to the closed enumeration control or statement, and defines no uuid or href property.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-mapping-schema.json"},"data/schema-evidence/mapping-resource-reference.json":{"constraints":["required == [\"type\",\"href\"]","type uses anyOf (open vocabulary) with enum [\"catalog\",\"profile\"]"],"definition":"oscal-mapping-oscal-mapping-common:mapping-resource-reference","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-mapping-oscal-mapping-common:mapping-resource-reference","additionalProperties":false,"description":"A reference to a resource that is either the source or the target of a mapping.","properties":{"href":{"$ref":"#/definitions/URIReferenceDatatype","description":"A resolvable URL reference to the base catalog or profile that this profile is tailoring.","title":"Catalog or Profile Reference"},"links":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:link"},"minItems":1,"type":"array"},"ns":{"$ref":"#/definitions/URIDatatype","description":"An optional namespace qualifying the resource's type.","title":"Resource Type Namespace"},"props":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["catalog","profile"]}],"description":"The semantic type of the resource.","title":"Resource Type"}},"required":["type","href"],"title":"Mapped Resource Reference","type":"object"},"model":"mapping-collection","note":"The oscal-mapping-oscal-mapping-common:mapping-resource-reference definition from the OSCAL 1.2.1 mapping-collection model, demonstrating that a mapped resource reference requires type and href and constrains type with an open anyOf vocabulary whose enumeration lists catalog and profile.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-mapping-schema.json"},"data/schema-evidence/metadata.json":{"constraints":["required == [\"title\",\"last-modified\",\"version\",\"oscal-version\"]"],"definition":"oscal-ap-oscal-metadata:metadata","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ap-oscal-metadata:metadata","additionalProperties":false,"description":"Provides information about the containing document, and defines concepts that are shared across the document.","properties":{"actions":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:action"},"minItems":1,"type":"array"},"document-ids":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:document-id"},"minItems":1,"type":"array"},"last-modified":{"$ref":"#/definitions/oscal-ap-oscal-metadata:last-modified"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"locations":{"items":{"additionalProperties":false,"description":"A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.","properties":{"address":{"$ref":"#/definitions/oscal-ap-oscal-metadata:address"},"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the location, which may be used by a tool for display and navigation.","title":"Location Title"},"urls":{"items":{"$ref":"#/definitions/URIDatatype","description":"The uniform resource locator (URL) for a web site or other resource associated with the location.","title":"Location URL"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique ID for the location, for reference.","title":"Location Universally Unique Identifier"}},"required":["uuid"],"title":"Location","type":"object"},"minItems":1,"type":"array"},"oscal-version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:oscal-version"},"parties":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:address"},"minItems":1,"type":"array"},"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"external-ids":{"items":{"additionalProperties":false,"description":"An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).","properties":{"id":{"$ref":"#/definitions/StringDatatype"},"scheme":{"anyOf":[{"$ref":"#/definitions/URIDatatype"},{"enum":["http://orcid.org/"]}],"description":"Indicates the type of external identifier.","title":"External Identifier Schema"}},"required":["id","scheme"],"title":"Party External Identifier","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"member-of-organizations":{"items":{"$ref":"#/definitions/UUIDDatatype","description":"A reference to another party by UUID, typically an organization, that this subject is associated with.","title":"Organizational Affiliation"},"minItems":1,"type":"array"},"name":{"$ref":"#/definitions/StringDatatype","description":"The full name of the party. This is typically the legal name associated with the party.","title":"Party Name"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the party.","title":"Party Short Name"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["person","organization"]}],"description":"A category describing the kind of party the object describes.","title":"Party Type"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique identifier for the party.","title":"Party Universally Unique Identifier"}}},{"additionalProperties":false,"properties":{"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"external-ids":{"items":{"additionalProperties":false,"description":"An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).","properties":{"id":{"$ref":"#/definitions/StringDatatype"},"scheme":{"anyOf":[{"$ref":"#/definitions/URIDatatype"},{"enum":["http://orcid.org/"]}],"description":"Indicates the type of external identifier.","title":"External Identifier Schema"}},"required":["id","scheme"],"title":"Party External Identifier","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"location-uuids":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:location-uuid"},"minItems":1,"type":"array"},"member-of-organizations":{"items":{"$ref":"#/definitions/UUIDDatatype","description":"A reference to another party by UUID, typically an organization, that this subject is associated with.","title":"Organizational Affiliation"},"minItems":1,"type":"array"},"name":{"$ref":"#/definitions/StringDatatype","description":"The full name of the party. This is typically the legal name associated with the party.","title":"Party Name"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the party.","title":"Party Short Name"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["person","organization"]}],"description":"A category describing the kind of party the object describes.","title":"Party Type"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique identifier for the party.","title":"Party Universally Unique Identifier"}}}],"description":"An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.","title":"Party","type":"object"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"published":{"$ref":"#/definitions/oscal-ap-oscal-metadata:published"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"responsible-parties":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:responsible-party"},"minItems":1,"type":"array"},"revisions":{"items":{"additionalProperties":false,"description":"An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).","properties":{"last-modified":{"$ref":"#/definitions/oscal-ap-oscal-metadata:last-modified"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"oscal-version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:oscal-version"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"published":{"$ref":"#/definitions/oscal-ap-oscal-metadata:published"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the document revision, which may be used by a tool for display and navigation.","title":"Document Title"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["version"],"title":"Revision History Entry","type":"object"},"minItems":1,"type":"array"},"roles":{"items":{"additionalProperties":false,"description":"Defines a function, which might be assigned to a party in a specific situation.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A summary of the role's purpose and associated responsibilities.","title":"Role Description"},"id":{"$ref":"#/definitions/TokenDatatype","description":"A unique identifier for the role.","title":"Role Identifier"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the role.","title":"Role Short Name"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the role, which may be used by a tool for display and navigation.","title":"Role Title"}},"required":["id","title"],"title":"Role","type":"object"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the document, which may be used by a tool for display and navigation.","title":"Document Title"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["title","last-modified","version","oscal-version"],"title":"Document Metadata","type":"object"},"model":"assessment-plan","note":"The shared oscal-metadata:metadata assembly. Every OSCAL document, a catalog among them, is required to carry a title, a last-modified timestamp, a version and the OSCAL version it conforms to. That is what makes a published guide citable as a document rather than as a copy.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_assessment-plan_schema.json at definitions/oscal-ap-oscal-metadata:metadata.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ap-schema.json"},"data/schema-evidence/observation.json":{"constraints":["required == [\"uuid\",\"description\",\"methods\",\"collected\"]","no property named 'target'","no property named 'control-id'","no property named 'objective-id'"],"definition":"oscal-ar-oscal-assessment-common:observation","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:observation","additionalProperties":false,"description":"Describes an individual observation.","properties":{"collected":{"$ref":"#/definitions/DateTimeWithTimezoneDatatype","description":"Date/time stamp identifying when the finding information was collected.","title":"Collected Field"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this assessment observation.","title":"Observation Description"},"expires":{"$ref":"#/definitions/DateTimeWithTimezoneDatatype","description":"Date/time identifying when the finding information is out-of-date and no longer valid. Typically used with continuous assessment scenarios.","title":"Expires Field"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"methods":{"items":{"anyOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["EXAMINE","INTERVIEW","TEST","UNKNOWN"]}],"description":"Identifies how the observation was made.","title":"Observation Method"},"minItems":1,"type":"array"},"origins":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:origin"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"relevant-evidence":{"items":{"additionalProperties":false,"description":"Links this observation to relevant evidence.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this evidence.","title":"Relevant Evidence Description"},"href":{"$ref":"#/definitions/URIReferenceDatatype","description":"A resolvable URL reference to relevant evidence.","title":"Relevant Evidence Reference"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["description"],"title":"Relevant Evidence","type":"object"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"subjects":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:subject-reference"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this observation.","title":"Observation Title"},"types":{"items":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["ssp-statement-issue","control-objective","mitigation","finding","discovery","historic"]}],"description":"Identifies the nature of the observation. More than one may be used to further qualify and enable filtering.","title":"Observation Type"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Observation Universally Unique Identifier"}},"required":["uuid","description","methods","collected"],"title":"Observation","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:observation definition from the OSCAL 1.2.1 assessment-results model, demonstrating that an observation requires uuid, description, methods, and collected, and defines no target, control-id, or objective-id property.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/poam-outcomes.json":{"constraints":["properties includes \"observations\"","properties includes \"findings\"","observations items ref the shared assessment-common observation","findings items ref the shared assessment-common finding"],"definition":"oscal-poam-oscal-poam:plan-of-action-and-milestones","fetched_at":"2026-08-18","fragment":{"properties":{"findings":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:finding"},"minItems":1,"type":"array"},"observations":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:observation"},"minItems":1,"type":"array"},"risks":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:risk"},"minItems":1,"type":"array"}},"required":["uuid","metadata","poam-items"]},"fragment_note":"Only required and the observations, findings and risks properties are carried.","model":"plan-of-action-and-milestones","note":"The root assembly of the OSCAL 1.2.1 plan-of-action-and-milestones model. It carries observations and findings as sibling arrays, so assessment results is not the only model in which an outcome can be recorded. Both models sit in the Assessment layer; no control-layer or implementation-layer model carries either.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-poam-schema.json"},"data/schema-evidence/result.json":{"constraints":["required includes \"reviewed-controls\""],"definition":"oscal-ar-oscal-ar:result","fetched_at":"2026-08-18","fragment":{"properties":{"reviewed-controls":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls"}},"required":["uuid","title","description","start","reviewed-controls"]},"fragment_note":"Only required and the reviewed-controls property are carried. The other properties of result are not relevant to this claim and are omitted.","model":"assessment-results","note":"The result assembly of the OSCAL 1.2.1 assessment-results model. Every result is required to declare the controls it reviewed, so the control frame is unavoidable at the result level. The referenced reviewed-controls assembly requires control-selections, and a selection may use include-all rather than naming individual controls, so the requirement can be met without listing any one control.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/reviewed-controls.json":{"constraints":["required == [\"control-selections\"]","control-selections items use anyOf with required [\"include-all\"] or [\"include-controls\"]"],"definition":"oscal-ar-oscal-assessment-common:reviewed-controls","fetched_at":"2026-08-18","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls","additionalProperties":false,"description":"Identifies the controls being assessed and their control objectives.","properties":{"control-objective-selections":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this collection of control objectives.","title":"Control Objectives Description"},"exclude-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ar-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this collection of control objectives.","title":"Control Objectives Description"},"exclude-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"include-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-objectives"]}],"description":"Identifies the control objectives of the assessment. In the assessment plan, these are the planned objectives. In the assessment results, these are the assessed objectives, and reflects any changes from the plan.","title":"Referenced Control Objectives","type":"object"},"minItems":1,"type":"array"},"control-selections":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of in-scope controls specified for assessment.","title":"Assessed Controls Description"},"exclude-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ar-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of in-scope controls specified for assessment.","title":"Assessed Controls Description"},"exclude-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"include-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-controls"]}],"description":"Identifies the controls being assessed. In the assessment plan, these are the planned controls. In the assessment results, these are the actual controls, and reflects any changes from the plan.","title":"Assessed Controls","type":"object"},"minItems":1,"type":"array"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of control objectives.","title":"Control Objective Description"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["control-selections"],"title":"Reviewed Controls and Control Objectives","type":"object"},"model":"assessment-results","note":"The reviewed-controls assembly of the OSCAL 1.2.1 assessment-results model. It requires control-selections, and each selection must carry either include-all or include-controls. So the requirement that a result declare the controls it reviewed can be satisfied with include-all, without naming any one control. The single assessment result in the three bodies of content does exactly that.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/six-questions.json":{"answer_states":[{"key":"filled","label":"Answered","meaning":"The published content answers this question."},{"key":"partial","label":"Partly answered","meaning":"The published content answers part of this question."},{"key":"empty-absent","label":"Not answered","meaning":"The published content does not answer the question or state a reason for the omission."}],"approaches":[{"key":"catalog-first","label":"Catalog-first","layer":"Control","one_line":"The rule is a catalog control; the check is a software component in a component definition.","option_letter":"A","primary_model":"catalog","repo":"https://github.com/awslabs/oscal-content-for-aws-services","serves_stakeholder_first":"publisher","status_annotation":"experimental, per publisher"},{"key":"component-first","label":"Component-first","layer":"Implementation","one_line":"The rule uses a proposed assembly on the product component; the check uses a proposed assembly on a validation component.","option_letter":"B","primary_model":"component-definition","repo":null,"serves_stakeholder_first":"implementer","status_annotation":"proposed schema"},{"key":"assessment-first","label":"Assessment-first","layer":"Assessment","one_line":"The rule is an assessment plan activity or step; a property identifies the check.","option_letter":"C","primary_model":"assessment-plan","repo":null,"serves_stakeholder_first":"assessor","status_annotation":"placeholder and synthetic identifiers"}],"carrier_note":"Each answer identifies the OSCAL model and assemblies representing the capability. Rules use catalog controls, component rules or assessment activities; the choice affects references to checks, claims and results.","empty_states":[{"key":"empty-absent","label":"Unanswered, no stated position","meaning":"The published content does not answer the question or state a reason for the omission.","rendering":"hollow with a light dotted fill"}],"finding":"Questions 1 and 2 are answered by all three approaches. No approach fully answers both 6a and 6b, and no approach answers every question.","legend":{"answers_title":"Is the question answered?","label":"How to read an answer","mechanism_title":"How the capability is enabled","why_one_block":"Each cell combines an answer state with mechanism badges. A shared legend explains both dimensions together.","why_uneven":"Answer states describe evidence coverage. Mechanism descriptions also explain schema and tool-support requirements, so the descriptions need additional detail."},"matrix":[{"approach":"catalog-first","assemblies":["control"],"mechanisms":["assembly","prop"],"model":"catalog","note":"One control per rule. Existing assemblies capture context around the rule's intent.","props":[{"name":"TechnicalControlId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"1","snippet_ids":["aws-acm2-control","aws-input-parameter"],"state":"filled"},{"approach":"component-first","assemblies":["component","rules"],"mechanisms":["proposed"],"model":"component-definition","note":"The proposed rules assembly sits on the component alongside control-implementations.","slot":"1","snippet_ids":["ibm-cos-component"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The activity defines the rule and the step describes the check. Without a parameter field, required values are recorded in text.","props":[{"name":"check","ns":"http://comply0.com/ns/oscal"}],"slot":"1","snippet_ids":["ez-stig-activity-v259312","ez-stig-sc28-v270747"],"state":"filled"},{"approach":"catalog-first","assemblies":["mapping","map"],"mechanisms":["assembly"],"model":"mapping-collection","note":"A separate mapping collection links rules to framework controls. The published corpus contains no such mapping document.","slot":"2","snippet_ids":["aws-acm-backmatter-source","aws-acm-service-rollup"],"state":"filled"},{"approach":"component-first","assemblies":["component","implemented-requirement","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"component-definition","note":"Existing assemblies link the component to the control. Linking an individual rule requires the proposed assembly.","slot":"2","snippet_ids":["ibm-statement-rules","ibm-cos-component"],"state":"filled"},{"approach":"assessment-first","assemblies":["reviewed-controls","activity","related-controls"],"mechanisms":["assembly"],"model":"assessment-plan","note":"Two levels: reviewed-controls defines the required plan scope; related-controls optionally links an activity to controls.","slot":"2","snippet_ids":["ez-stig-related-controls","ez-cisa-step-reviewed"],"state":"filled"},{"approach":"catalog-first","assemblies":["component","implemented-requirement"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"The check identifier resolves within the runtime to an executable machine check.","props":[{"name":"ConfigRuleId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"3","snippet_ids":["aws-acm2-control","aws-acm-rsa-check-component"],"state":"filled"},{"approach":"component-first","assemblies":["component","checks"],"mechanisms":["proposed"],"model":"component-definition","note":"The proposed schema places both composite-key fields on the check. The rule has no reference back to the check.","slot":"3","snippet_ids":["ibm-validation-ansible"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"Three conventions: CISA references an executable through a JSON string in a prop; STIG and CIS describe checks in prose.","props":[{"name":"check","ns":"http://comply0.com/ns/oscal"}],"slot":"3","snippet_ids":["ez-cis-step-props","ez-cis-remediation-step","ez-cisa-context-step"],"state":"partial"},{"approach":"catalog-first","assemblies":["implemented-requirement","by-component"],"mechanisms":["assembly"],"model":"system-security-plan","note":"The by-component response identifies a component, not an instance. An assessment plan cannot import a catalog directly.","slot":"4","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["implemented-requirement","by-component","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"system-security-plan","note":"In the SSP every subject is a component, the whole environment defaulting to This System, so the by-component response names what the rule runs against.","slot":"4","snippet_ids":["ibm-validation-ansible"],"state":"filled"},{"approach":"assessment-first","assemblies":["assessment-subjects","task","subjects"],"mechanisms":["assembly"],"model":"assessment-plan","note":"The plan defines subject scope; activity-associated tasks select targets. Both can identify inventory items, representing instances rather than classes.","slot":"4","snippet_ids":["ez-subjects-includeall","ez-subjects-explicit"],"state":"filled"},{"approach":"catalog-first","assemblies":["component"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"The content records inputs and outputs but not the engine. ConfigRuleId resolves within the engine. No assessor workflow is shown; an assessment plan cannot import a catalog directly.","paths":[{"assemblies":["component","by-component"],"in":{"slot":"3"},"key":"implementor","label":"Implementor's path","out":{"slot":"6a"}}],"props":[{"name":"ConfigRuleId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"5","snippet_ids":["aws-config-service-bare"],"state":"partial"},{"approach":"component-first","assemblies":["component"],"mechanisms":["assembly","proposed"],"model":"component-definition","note":"Each assessment-plan activity names its runner through the proposed assessment-asset-uuid and its checks through check-ids, and each observation carries the asset and check that produced it.","paths":[{"assemblies":["component","checks","by-component","implementing-rules"],"in":{"slot":"3"},"key":"implementor","label":"Implementor's path","out":{"slot":"6a"}},{"assemblies":["component","checks","assessment-assets","observation","assessment-check-id","result"],"copy":{"slot":"3"},"in":{"model":"assessment-plan"},"key":"assessor","label":"Assessor's path","out":{"slot":"6b"}}],"slot":"5","snippet_ids":["ibm-ap-activity","ibm-ap-task-subjects","ibm-ar-observation"],"state":"filled"},{"approach":"assessment-first","assemblies":["assessment-platforms","component","task"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The platform executes the check, a referenced component represents the plugin, and a task property identifies the platform.","paths":[{"assemblies":["activity","step","assessment-platforms","component","task","observation"],"in":{"model":"assessment-plan"},"key":"assessor","label":"Assessor's path","out":{"slot":"6b"}}],"props":[{"name":"assessment-platform","ns":"http://comply0.com/ns/oscal"}],"slot":"5","snippet_ids":["ez-cisa-context-activity","ez-cisa-assessment-assets","ez-cisa-task-timing"],"state":"partial"},{"approach":"catalog-first","assemblies":["implemented-requirement","by-component"],"mechanisms":["assembly"],"model":"system-security-plan","note":"The component definition describes how a component could satisfy a control, not a system's implementation. The corpus contains no system security plan.","slot":"6a","snippet_ids":["aws-acm-rsa-check-component","aws-acm-service-rollup"],"state":"partial"},{"approach":"component-first","assemblies":["implemented-requirement","by-component","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"system-security-plan","note":"The claim uses a by-component response. Identifying the supporting rule requires the proposed implementing-rules assembly.","slot":"6a","snippet_ids":[],"state":"empty-absent"},{"approach":"assessment-first","assemblies":["import-ssp","back-matter","resource"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The assessment plan references the document containing the implementation claim. A back-matter resource supports cases without a plan of record.","slot":"6a","snippet_ids":["ez-cisa-import-ssp","ez-cisa-ssp-resource","ez-cisa-no-ssp-resource","ez-stig-import-ssp"],"state":"partial"},{"approach":"catalog-first","assemblies":["finding"],"mechanisms":["assembly"],"model":"assessment-results","note":"No assessment results are published in the catalog-first OSCAL corpus.","slot":"6b","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["observation"],"mechanisms":["assembly","proposed"],"model":"assessment-results","note":"The result contains observations but no findings or objective status. The control reference must be recovered through the assessment plan.","slot":"6b","snippet_ids":["ibm-ar-observation"],"state":"partial"},{"approach":"assessment-first","assemblies":["finding","observation"],"mechanisms":["assembly"],"model":"assessment-results","note":"A separate results document imports the plan. Findings have targets and status; observations identify the executed activity as the subject.","slot":"6b","snippet_ids":["ez-cisa-ar-finding","ez-cisa-ar-observation"],"state":"filled"}],"mechanism_note":"Answer states describe coverage in the published corpus. Mechanism badges identify the OSCAL structures needed to represent an answer. Evidence coverage does not establish schema adoption or tool interoperability.","mechanism_states":[{"key":"assembly","label":"Released OSCAL assembly","meaning":"A released OSCAL assembly provides the capability without a schema change.","rendering":"a solid badge","short":"OSCAL assembly"},{"key":"proposed","label":"Proposed assembly","meaning":"The capability requires a proposed assembly. Interoperable use requires schema adoption and tool support for the new structure.","rendering":"a dashed badge","short":"Proposed"},{"key":"prop","label":"Namespaced property","meaning":"A property in the publisher's namespace provides the capability. Tools need a shared convention to interpret the property; the OSCAL schema does not define the meaning.","rendering":"a dotted badge","short":"Prop"}],"note":"The six questions and answer matrix compare OSCAL JSON examples, including content using proposed assemblies. tools/verify.py --matrix checks each cell against the example files. Notes describe supported capabilities and unresolved questions.","paths_note":"Each runner path shows one input document and one output document. The documents depend on whether the system owner or assessor runs the check.","proposed_assemblies":["assessment-check-id","associated-checks","checks","implementing-rules","result","rule-groups","rules"],"slots":[{"key":"rule","name":"What the rule requires","number":"1","optional":false,"question":"What condition must hold, and where is the requirement defined?","short":"Rule","why_separate":"A technology-specific requirement defines one testable condition. Parameter options and defaults belong with that definition where the selected model supports them."},{"binding_times":[{"authored_by":"Rule author","key":"inline","label":"Author-time, inline","mechanism":"The rule declares its control directly"},{"authored_by":"Rule author","key":"pointer","label":"Author-time, by pointer","mechanism":"A prop carries an external framework identifier that a consumer must resolve"},{"authored_by":"Rule author or third party","available_to":{"assessment-first":false,"catalog-first":true,"component-first":false},"key":"late","label":"Late, external","mechanism":"A separate artifact links a rule to a control after publication","why":"mapping-item.type is restricted by allOf to control and statement, and mapping-item has neither uuid nor href. External mappings therefore reach rules modelled as controls or control statements, not component rules or activities. This OSCAL schema constraint does not establish a preferred approach."}],"cost_of_leaving_empty":{"evidence":["observation.json","finding.json","finding-target.json"],"finding":"Not available. finding requires target; finding-target requires type, restricted by allOf to statement-id or objective-id, both control-derived.","observation":"Available. AR observation requires only uuid, description, methods and collected, with no control reference.","summary":"Without a control link, an assessor can record an observation but not a finding against a control statement or objective."},"key":"control-tie","name":"How the rule links to a control","number":"2","optional":true,"question":"Does this rule help satisfy a regulatory control, and which one?","short":"Control","why_separate":"A rule is finer-grained than a control and may serve several controls, one, or none. A control-linking mechanism is required, but using the mechanism is optional."},{"key":"check","name":"How the rule is tested","number":"3","optional":false,"question":"Which executable or procedure tests the rule?","short":"Check","why_separate":"A rule may have several checks, one per tool. The examples separate rule definitions from checks and reference external executables rather than embedding code in OSCAL."},{"key":"subject","name":"What the check runs against","not_established":true,"not_established_note":"The examples use assessment platforms, assets and components differently. A consistent distinction between the subject being assessed and the resources performing the assessment is not established here.","number":"4","optional":false,"question":"Is the subject a host, component, account or another resource?","short":"Subject","why_separate":"The subject identifies the assessed host, inventory item, component or account. Criterion 8 addresses response fidelity."},{"key":"actor","name":"What performs the check","not_established":true,"not_established_note":"The same distinction remains open in question 4. The approaches use different combinations of assessment-assets, assessment-platforms, uses-components, validation components, origin actors, task-level props and the method prop.","number":"5","optional":false,"question":"Which tool or person performs the check, and how is the runner identified?","short":"Runner","why_separate":"The runner may be a validation component, assessment platform, tool or person. The method prop identifies examine, interview or test."},{"group_name":"Implementation claims and assessment outcomes","key":"implementation-claim","name":"How the system claims it meets the rule","number":"6a","optional":false,"question":"How does the system owner describe implementation of the rule?","short":"Claim","why_separate":"The system owner provides a narrative claim of implementation and design intent per component. The SSP represents claims through implemented-requirement, statement and by-component."},{"group_name":"Implementation claims and assessment outcomes","key":"assessment-result","name":"How an assessment records the outcome","number":"6b","optional":false,"question":"Was the rule satisfied, when, and for which subject?","short":"Result","why_separate":"The assessor records evidence and a binary or graded outcome per subject at a point in time. The AR uses observation, finding and status. A desired-state rule has a binary satisfaction condition; the SSP implementation claim is narrative."}]},"data/snippets/aws-acm-backmatter-source.json":{"approach":"catalog-first","content":"{\n \"resources\": [\n {\n \"uuid\": \"ab8a6a36-2706-49e5-b87e-498c52ba6a61\",\n \"title\": \"AWS Regions Component Definition\",\n \"rlinks\": [\n {\n \"href\": \"../aws_regions.oscal.json\",\n \"media-type\": \"application/json\"\n }\n ]\n },\n {\n \"uuid\": \"f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"title\": \"AWS Security Hub Controls\",\n \"rlinks\": [\n {\n \"href\": \"../catalogs/aws_security-hub.oscal.json\",\n \"media-type\": \"application/json\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-backmatter-source","language":"json","pointer":"/component-definition/back-matter","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"Back-matter, source to the catalog"},"data/snippets/aws-acm-rsa-check-component.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"b5e8b205-cc1f-4bd0-9e51-4ebaab18f69a\",\n \"type\": \"software\",\n \"title\": \"acm-certificate-rsa-check\",\n \"description\": \"Checks if RSA certificates managed by AWS Certificate Manager (ACM) have a key length of at least '2048' bits. The rule is NON_COMPLIANT if the minimum key length is less than 2048 bits.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"ACM_CERTIFICATE_RSA_CHECK\"\n },\n {\n \"name\": \"asset-type\",\n \"value\": \"automated-inspection\"\n },\n {\n \"name\": \"ResourceType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"AWS::ACM::Certificate\"\n }\n ],\n \"responsible-roles\": [\n {\n \"role-id\": \"owner\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"4f227b9d-b47b-4c06-bb55-8f3a17e29b74\",\n \"source\": \"#f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"description\": \"Security Hub control implementation\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"4de99497-e4fe-4dfd-80a7-ebbd59f06364\",\n \"control-id\": \"ACM.2\",\n \"description\": \"Implemented via AWS Config Rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-rsa-check-component","language":"json","pointer":"/component-definition/components/2","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"3","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"acm-certificate-rsa-check, the check component"},"data/snippets/aws-acm-service-rollup.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"ae50c910-9057-4345-89d9-c2ae4c1f0b08\",\n \"source\": \"#f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"description\": \"AWS Security Hub control implementation\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"c3e6d492-b3b6-46d9-9e2a-7d6d9922f3fa\",\n \"control-id\": \"ACM.1\",\n \"description\": \"Security Hub control ACM.1\"\n },\n {\n \"uuid\": \"551c5fc8-569a-4ea5-a0d8-0b524e9f4205\",\n \"control-id\": \"ACM.2\",\n \"description\": \"Security Hub control ACM.2\"\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-service-rollup","language":"json","pointer":"/component-definition/components/0/control-implementations/0","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"AWS Certificate Manager, the service roll-up"},"data/snippets/aws-acm2-control.json":{"approach":"catalog-first","content":"{\n \"id\": \"ACM.2\",\n \"title\": \"ACM.2\",\n \"props\": [\n {\n \"name\": \"SeverityLabel\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"HIGH\"\n },\n {\n \"name\": \"TriggerType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Change Triggered\"\n },\n {\n \"name\": \"EvaluatedServices\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"ACM\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://docs.aws.amazon.com/console/securityhub/ACM.2/remediation\",\n \"rel\": \"remediation\"\n }\n ],\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"This control checks whether RSA certificates managed by AWS Certificate Manager use a key length of at least 2,048 bits. The control fails if the key length is smaller than 2,048 bits.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"RSA certificates managed by ACM should use a key length of at least 2,048 bits\"\n },\n {\n \"name\": \"guidance\",\n \"prose\": \"For information on how to correct this issue, consult the AWS Security Hub controls documentation.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"acm-certificate-rsa-check\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"acm-certificate-rsa-check\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm2-control","language":"json","pointer":"/catalog/groups/0/controls/1","section":null,"sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"ACM.2, the control"},"data/snippets/aws-config-service-bare.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"9a02ef98-02b2-49c4-a3ea-3c546e830a15\",\n \"type\": \"service\",\n \"title\": \"AWS Config\",\n \"description\": \"AWS Config is a service that continuously monitors and records your AWS resource configurations and allows you to automate the evaluation of recorded configurations against desired settings.\",\n \"props\": [\n {\n \"name\": \"service-id\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Config Service\"\n },\n {\n \"name\": \"version\",\n \"value\": \"2014-11-12\"\n },\n {\n \"name\": \"availability\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"REGIONAL\"\n },\n {\n \"name\": \"label\",\n \"value\": \"AWS Config\",\n \"class\": \"marketingName\",\n \"group\": \"marketing\"\n },\n {\n \"name\": \"apiEndpointPrefix\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"arnNamespace\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"cloudTrailEventSource\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"lifecycle-stage\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"generally-available\"\n },\n {\n \"name\": \"iamServicePrefix\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n }\n ],\n \"links\": \"...\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-config-service-bare","language":"json","pointer":"/component-definition/components/0","section":null,"sha256_of_source_file":"d5049e46d7a1251932be3e74c1f9bace606ac9b5f5542249ccb884171394a6e7","slot":"5","source":"AWS/oscal-content-for-aws-services-main/component-definitions/config.oscal.json","title":"AWS Config, the engine that runs the checks"},"data/snippets/aws-control-cloudtrail2.json":{"approach":"catalog-first","content":"{\n \"id\": \"CloudTrail.2\",\n \"title\": \"CloudTrail.2\",\n \"props\": [\n {\n \"name\": \"SeverityLabel\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"MEDIUM\"\n },\n {\n \"name\": \"TriggerType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Periodic\"\n },\n {\n \"name\": \"EvaluatedServices\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"CloudTrail\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://docs.aws.amazon.com/console/securityhub/CloudTrail.2/remediation\",\n \"rel\": \"remediation\"\n }\n ],\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"This AWS control checks whether AWS CloudTrail is configured to use the server side encryption (SSE) AWS Key Management Service (AWS KMS) customer master key (CMK) encryption. The check will pass if the KmsKeyId is defined.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"CloudTrail should have encryption at-rest enabled\"\n },\n {\n \"name\": \"guidance\",\n \"prose\": \"For information on how to correct this issue, consult the AWS Security Hub controls documentation.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"cloud-trail-encryption-enabled\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"cloud-trail-encryption-enabled\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-21T03:10:41+00:00","id":"aws-control-cloudtrail2","language":"json","pointer":"/catalog/groups/15/controls/2","section":null,"sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"CloudTrail.2, the control"},"data/snippets/aws-input-parameter.json":{"approach":"catalog-first","content":"[\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"IAM_PASSWORD_POLICY\"\n },\n {\n \"name\": \"asset-type\",\n \"value\": \"automated-inspection\"\n },\n {\n \"name\": \"MaxPasswordAge\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"90\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"PasswordReusePrevention\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"24\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"MinimumPasswordLength\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"14\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireNumbers\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireSymbols\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireLowercaseCharacters\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireUppercaseCharacters\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"MinimumPasswordLength\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"7\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"PasswordReusePrevention\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"4\",\n \"class\": \"InputParameter\"\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-input-parameter","language":"json","pointer":"/component-definition/components/2/props","section":null,"sha256_of_source_file":"940cab9d3328d5ff55e6c69fbfae6fd4e846873d07f70ef7c096651bc8f750ab","slot":"1","source":"AWS/oscal-content-for-aws-services-main/component-definitions/iam.oscal.json","title":"InputParameter props, the parameter mechanism"},"data/snippets/ez-cis-remediation-step.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"7be22348-467b-563a-9c21-d438e47df7df\",\n \"title\": \"Remediation for Ensure cramfs kernel module is not available\",\n \"description\": \"Run the following script to unload and disable the `cramfs` module:\\n\\n**- IF -** the `cramfs` kernel module is available in ANY installed kernel:\\n\\n- Create a file ending in `.conf` with `install cramfs /bin/false` in the `/etc/modprobe.d/` directory\\n- Create a file ending in `.conf` with `blacklist cramfs` in the `/etc/modprobe.d/` directory\\n- Run `modprobe -r cramfs 2>/dev/null; rmmod cramfs 2>/de [truncated]\",\n \"props\": [\n {\n \"name\": \"assessment-status\",\n \"value\": \"automated\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-rule-id\",\n \"value\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"step-type\",\n \"value\": \"remediation\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-remediation-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/1","section":null,"sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS remediation step"},"data/snippets/ez-cis-resolution-status.json":{"approach":"assessment-first","content":"{\n \"description\": \"CIS Controls v8.0 derived from benchmark cc8:controlURI paths. Provide a CIS Controls v8 OSCAL catalog via --cis-catalog-v8 for authoritative control-id resolution.\",\n \"props\": [\n {\n \"name\": \"framework\",\n \"value\": \"CIS Controls v8.0\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"resolution-status\",\n \"value\": \"synthetic-ids\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ],\n \"include-controls\": \"...\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-resolution-status","language":"json","pointer":"/assessment-plan/reviewed-controls/control-selections/0","section":null,"sha256_of_source_file":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8","slot":"meta","source":"Easy Dynamics/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","title":"CIS resolution status"},"data/snippets/ez-cis-step-props.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"5c4c3bec-7bbe-521d-9a90-c04102edce9b\",\n \"title\": \"Audit for Ensure cramfs kernel module is not available\",\n \"description\": \"## Description\\n\\nThe `cramfs` filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems. A `cramfs` image can be used without having to first decompress the image.\\n\\n## Audit\\n\\nRun the following script to verify:\\n\\n**- IF -** the `cramfs` kernel module is available in ANY installed kernel, verify:\\n\\n- An entry including `/bin/true` or `/bin/false` exists in a file w [truncated]\",\n \"props\": [\n {\n \"name\": \"assessment-status\",\n \"value\": \"automated\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-rule-id\",\n \"value\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"step-type\",\n \"value\": \"audit\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-control-uri\",\n \"value\": \"http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-control-uri\",\n \"value\": \"http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"CM-7\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"stig-finding-id\",\n \"value\": \"V-230498\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-safeguard-urn\",\n \"value\": \"urn:cisecurity.org:controls:8.0:4:8\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-safeguard-urn\",\n \"value\": \"urn:cisecurity.org:controls:7.0:9:2\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ],\n \"remarks\": \"Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-step-props","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0","section":null,"sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS audit step props"},"data/snippets/ez-cisa-ar-finding.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"b5d014ae-23b1-51b8-845a-972f40def692\",\n \"title\": \"MS.AAD.1.1v1: Legacy Authentication Blocking\",\n \"target\": {\n \"type\": \"objective-id\",\n \"status\": {\n \"state\": \"satisfied\"\n },\n \"target-id\": \"ms.aad.1.1v1\"\n },\n \"description\": \"Conditional Access policy confirmed blocking all legacy authentication protocols for all users.\",\n \"related-observations\": [\n {\n \"observation-uuid\": \"941e3133-152b-5301-8762-abd228b5ee80\"\n }\n ]\n}","extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ar-finding","language":"json","pointer":"/assessment-results/results/0/findings/0","section":null,"sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"A finding, targeting an objective"},"data/snippets/ez-cisa-ar-observation.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"941e3133-152b-5301-8762-abd228b5ee80\",\n \"title\": \"Observation: MS.AAD.1.1v1 - Legacy Authentication Blocking\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"remarks\": \"Legacy authentication is blocked tenant-wide via a Conditional Access policy in the enabled state. Control CM-7 is satisfied.\",\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"422ccfe4-7b60-4fe8-81ff-3d4464cc6e05\"\n }\n ],\n \"collected\": \"2026-03-05T15:30:00-05:00\",\n \"description\": \"Examiner queried the Conditional Access policy configuration via Microsoft Graph API. A policy targeting all users with a condition for legacy authentication protocols and a grant control of 'Block' was identified and confirmed enabled.\"\n}","extracted_at":"2026-08-22T18:43:41+00:00","id":"ez-cisa-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","section":null,"sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"The observation it rests on, and what was examined"},"data/snippets/ez-cisa-assessment-assets.json":{"approach":"assessment-first","content":"{\n \"components\": [\n {\n \"uuid\": \"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\",\n \"type\": \"software\",\n \"title\": \"ScubaGear Plugin\",\n \"description\": \"CLI plugin on Comply0 platform for verifying M365 configuration settings using CISA ScubaGear.\",\n \"props\": [\n {\n \"name\": \"context\",\n \"value\": \"{\\\"plugin-path\\\":\\\"Comply0.Kansa.Extensions.ScubaGear.dll\\\",\\\"script-path\\\":\\\"Resources\\\\\\\\Invoke-ScubaGear.ps1\\\",\\\"app-id\\\":\\\"c4d39d69-aea7-4acc-af2c-45c502d3a308\\\",\\\"opa-path\\\":\\\"/usr/local/bin\\\"}\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"status\": {\n \"state\": \"operational\"\n }\n }\n ],\n \"assessment-platforms\": [\n {\n \"uuid\": \"15000cf8-2f2a-4417-8b93-60a1f209ee95\",\n \"title\": \"Comply0 cATO Agent\",\n \"uses-components\": [\n {\n \"component-uuid\": \"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-assets"},"data/snippets/ez-cisa-context-activity.json":{"approach":"assessment-first","content":"[\n {\n \"name\": \"context\",\n \"value\": \"{\\\"ProductNames\\\":\\\"aad\\\",\\\"component-uuid\\\":\\\"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\\\"}\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n },\n {\n \"name\": \"check\",\n \"value\": \"MS.AAD\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n]","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA activity context prop"},"data/snippets/ez-cisa-context-step.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"4b7f6f09-84da-4c03-ba7b-d02ff52d5b69\",\n \"title\": \"MS.AAD.3.7v1\",\n \"description\": \"Managed devices SHOULD be required for authentication.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"EXAMINE\"\n },\n {\n \"name\": \"criticality\",\n \"ns\": \"http://cisa.gov/ns/oscal\",\n \"value\": \"SHOULD\"\n },\n {\n \"name\": \"context\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"{\\\"SkipHybridJoinCheck\\\":false}\"\n },\n {\n \"name\": \"check\",\n \"value\": \"MS.AAD.3.7\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://github.com/cisagov/ScubaGear/tree/main/PowerShell/ScubaGear/baselines/aad.md#msaad37v1\",\n \"rel\": \"canonical\"\n },\n {\n \"href\": \"https://attack.mitre.org/techniques/T1078/\",\n \"text\": \"T1078: Valid Accounts\",\n \"rel\": \"mitre\"\n },\n {\n \"href\": \"https://attack.mitre.org/techniques/T1078/004/\",\n \"text\": \"T1078.004: Cloud Accounts\",\n \"rel\": \"mitre\"\n }\n ],\n \"reviewed-controls\": {\n \"control-selections\": [\n {\n \"include-controls\": [\n {\n \"control-id\": \"ac-20\",\n \"statement-ids\": [\n \"ac-20_smt.b\"\n ]\n },\n {\n \"control-id\": \"ia-3\",\n \"statement-ids\": [\n \"ia-3_smt\"\n ]\n }\n ]\n }\n ]\n },\n \"remarks\": \"The security risk of an adversary authenticating to the tenant from their own device is reduced by requiring a managed device to authenticate. Managed devices are under the provisioning and control of the agency. [OMB-22-09](https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf) states, \\\"When authorizing users to access resources, agencies must consider at least one device-level signal [truncated]\"\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","section":null,"sha256_of_source_file":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653","slot":"3","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-maester.json","title":"CISA step context prop"},"data/snippets/ez-cisa-import-ssp.json":{"approach":"assessment-first","content":"{\n \"href\": \"#75e00698-e43b-4d6f-be7f-d1227a3a3e39\",\n \"remarks\": \"Link the SAP to the SSP.\"\n}","extracted_at":"2026-08-22T18:44:16+00:00","id":"ez-cisa-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"import-ssp, resolving to a resource in the same document"},"data/snippets/ez-cisa-no-ssp-resource.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"f56da5c6-da67-4c40-acc8-6814bf7aa374\",\n \"title\": \"System's Full Name\",\n \"description\": \"# USE THIS RESOURCE WHEN NO OSCAL-BASED SSP EXISTS\\n\\nBriefly describe the system. This will appear in the SAR.\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"no-oscal-ssp\"\n },\n {\n \"name\": \"import-profile\",\n \"ns\": \"https://fedramp.gov/ns/oscal\",\n \"value\": \"#890170c3-d4fa-4d25-ab96-8e4bf7cc237c\"\n },\n {\n \"name\": \"purpose\",\n \"ns\": \"https://fedramp.gov/ns/oscal\",\n \"value\": \"Briefly state the system's purpose. This will appear in the SAR.\"\n }\n ],\n \"remarks\": \"Only include this resource if no OSCAL-based SSP is available.\"\n}","extracted_at":"2026-08-22T18:46:12+00:00","id":"ez-cisa-no-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/0","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The alternative resource, where no OSCAL system security plan exists"},"data/snippets/ez-cisa-ssp-resource.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"75e00698-e43b-4d6f-be7f-d1227a3a3e39\",\n \"title\": \"Kalvico Enterprise ICAM SSP\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"oscal-ssp\"\n }\n ],\n \"rlinks\": [\n {\n \"href\": \"system-security-plan.json\",\n \"media-type\": \"application/oscal.catalog+json\"\n }\n ],\n \"remarks\": \"Use this to point to an OSCAL-based SSP.\"\n}","extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/1","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The resource a resolved import-ssp lands on"},"data/snippets/ez-cisa-step-reviewed.json":{"approach":"assessment-first","content":"{\n \"control-selections\": [\n {\n \"include-controls\": [\n {\n \"control-id\": \"cm-7\",\n \"statement-ids\": [\n \"cm-7_smt\"\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-step-reviewed","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0/reviewed-controls","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"2","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA step reviewed-controls"},"data/snippets/ez-cisa-task-timing.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"c2f71c67-3d4c-43ba-ad9d-949d0396413f\",\n \"type\": \"action\",\n \"title\": \"Automate assessment of ScubaGear tests using Comply0 Platform Assessment Agent\",\n \"description\": \"Execute CISA SCuBA assessment tests using the Comply0 cATO Agent with ScubaGear plugin.\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"value\": \"15000cf8-2f2a-4417-8b93-60a1f209ee95\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"timing\": {\n \"at-frequency\": {\n \"period\": 24,\n \"unit\": \"hours\"\n }\n },\n \"associated-activities\": [\n {\n \"activity-uuid\": \"760fe3fc-45af-4c62-b095-265a56a1dedf\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"4e391cf6-5549-46f3-b3d7-aad12cd5a226\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"2c69fb5c-056f-4788-be36-723b939a4766\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"04319877-e72d-4967-b968-4852e6738113\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"53852402-8cd6-4e1c-a559-f31bb004a66e\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"c98b996e-8dae-40ef-8b40-100ffbe9e5e3\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"5f62a033-3847-43ec-bafd-3dc1a7621029\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA task, with timing"},"data/snippets/ez-stig-activity-v259312.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"e69fb43b-9565-58f6-badc-e31834e575f6\",\n \"title\": \"V-259312: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"stig-group-id\",\n \"value\": \"V-259312\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-rule-id\",\n \"value\": \"SV-259312r961818_rule\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"category\",\n \"value\": \"CAT II\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"srg\",\n \"value\": \"SRG-APP-000501-DB-000336\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"sequence\",\n \"value\": \"101\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-000172\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"au-12\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"documentable\",\n \"value\": \"false\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"93fcfc80-5643-5c15-835d-aaa4d000daeb\",\n \"title\": \"Check: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"## Check\\n\\nExecute the following SQL the \\\"enterprisedb\\\" operating system user:\\n\\n```bash\\n> psql edb -c \\\"SHOW edb_audit_statement\\\"\\n```\\n\\nIf the result is not \\\"all\\\" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"check\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"assessment-method\",\n \"value\": \"TEST\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-000172\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"au-12\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n },\n {\n \"uuid\": \"e58bf90b-06dc-537f-81a9-68e61e87b7a7\",\n \"title\": \"Remediate: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"## Remediate\\n\\nExecute the following SQL as the \\\"enterprisedb\\\" operating system user:\\n\\n```bash\\n> psql edb -c \\\"ALTER SYSTEM SET edb_audit_statement = 'all'\\\"\\n> psql edb -c \\\"SELECT pg_reload_conf()\\\"\\n```\\n\\nor\\n\\nUpdate the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"remediate\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n }\n ],\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"au-12\"\n }\n ]\n }\n ]\n },\n \"remarks\": \"Source SRG: SRG-APP-000501-DB-000336\\nDPMS Target identifier: 5575\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-activity-v259312","language":"json","pointer":"/assessment-plan/local-definitions/activities/100","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG activity V-259312"},"data/snippets/ez-stig-import-ssp.json":{"approach":"assessment-first","content":"{\n \"href\": \"PLACEHOLDER\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"meta","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG import-ssp, an unresolved placeholder"},"data/snippets/ez-stig-related-controls.json":{"approach":"assessment-first","content":"{\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"au-12\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-related-controls","language":"json","pointer":"/assessment-plan/local-definitions/activities/100/related-controls","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"2","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG related-controls, the control tie"},"data/snippets/ez-stig-sc28-v270747.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"c8eaf2b1-c63f-5693-a1a5-e4e66a760c41\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system.\\n\\nThis requirement addresses protection of user-generated data, as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.\\n\\nSatisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS [truncated]\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"stig-group-id\",\n \"value\": \"V-270747\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-rule-id\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"category\",\n \"value\": \"CAT II\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"srg\",\n \"value\": \"SRG-OS-000185-GPOS-00079\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"sequence\",\n \"value\": \"102\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-001199\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002475\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002476\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-004910\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.1\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.3\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"documentable\",\n \"value\": \"false\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"0423503f-e675-545e-8a9b-740c1b5f51ce\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"## Check\\n\\nNote: If there is a documented and approved mission requirement for data-at-rest to not be encrypted, this requirement is not applicable.\\n\\nVerify Ubuntu 24.04 LTS prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption.\\n\\nDetermine the partition layout for the system with the following command:\\n\\n```bash\\n$ sudo fdisk -l\\n(..)\\nDisk /dev/vda: 15 GiB, 16106127360 bytes, 31457280 sectors\\nUnits: sectors of 1 * 512 = 512 bytes\\nSector size (logical/physical): 512 bytes / 512 bytes\\nI/O size (minimum/optimal): 512 bytes / 512 byte [truncated]\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"check\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"assessment-method\",\n \"value\": \"TEST\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-001199\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002475\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002476\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-004910\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.1\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.3\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n },\n {\n \"uuid\": \"0820d37b-cdcb-5e32-a660-e1111ad328dc\",\n \"title\": \"Remediate: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"## Remediate\\n\\nTo encrypt an entire partition, dedicate a partition for encryption in the partition layout.\\n\\nNote: Encrypting a partition in an already-installed system is more difficult because it will need to be resized and existing partitions changed.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"remediate\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n }\n ],\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n },\n {\n \"control-id\": \"sc-28.1\"\n },\n {\n \"control-id\": \"sc-28.3\"\n }\n ]\n }\n ]\n },\n \"remarks\": \"Source SRG: SRG-OS-000185-GPOS-00079\\nDPMS Target identifier: 5673\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-sc28-v270747","language":"json","pointer":"/assessment-plan/local-definitions/activities/101","section":null,"sha256_of_source_file":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","title":"STIG activity V-270747, SC-28"},"data/snippets/ez-subjects-explicit.json":{"approach":"assessment-first","content":"[\n {\n \"type\": \"inventory-item\",\n \"description\": \"The M365 tenant instance being assessed. Assume it's defined in SSP.\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n]","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"4","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-subjects, one inventory item"},"data/snippets/ez-subjects-includeall.json":{"approach":"assessment-first","content":"[\n {\n \"type\": \"component\",\n \"description\": \"Target system being assessed against the STIG.\",\n \"include-all\": {}\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-subjects-includeall","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"4","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG assessment-subjects, include-all"},"data/snippets/ibm-ap-activity.json":{"approach":"component-first","content":"[\n {\n \"activities\": [\n {\n \"uuid\": \"a1b2c3d4-1111-4aaa-8888-111111111111\",\n \"description\": \"Execute Ansible checks to validate the controls.\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"check-ids\": [\n \"check-1\",\n \"check-2\"\n ]\n },\n {\n \"uuid\": \"b2c3d4e5-2222-4bbb-9999-222222222222\",\n \"description\": \"Execute OSCAP checks to validate the controls.\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984e8\",\n \"check-ids\": [\n \"check-1\",\n \"check-3\"\n ]\n }\n ]\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-activity","language":"json","pointer":"/assessment-plan/local-defintions","section":null,"sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"5","source":"IBM/assessment-plan.json","title":"AP activity, binding check-ids"},"data/snippets/ibm-ap-task-subjects.json":{"approach":"component-first","content":"{\n \"uuid\": \"b3504d22-0e75-4dd7-9247-618661beba4e\",\n \"type\": \"action\",\n \"title\": \"Execute Ansible Checks\",\n \"description\": \"The assessor will execute the Ansible checks defined in the validation component using the Ansible assessment platform to collect evidence for the assessment.\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"value\": \"d8c9a1e5-1c3b-4f0b-9c8e-2a1b2c3d4e5f\"\n }\n ],\n \"timing\": {\n \"at-frequency\": {\n \"period\": 1,\n \"unit\": \"days\"\n }\n },\n \"associated-activities\": [\n {\n \"activity-uuid\": \"a1b2c3d4-1111-4aaa-8888-111111111111\",\n \"subjects\": [\n {\n \"subject-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984fe\"\n }\n ]\n },\n {\n \"activity-uuid\": \"b2c3d4e5-2222-4bbb-9999-222222222222\",\n \"subjects\": [\n {\n \"subject-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984ff\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-task-subjects","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"4","source":"IBM/assessment-plan.json","title":"AP task, subjects and platform"},"data/snippets/ibm-ar-observation.json":{"approach":"component-first","content":"{\n \"uuid\": \"6c0a18ff-36b4-45b2-9e8b-6e3011bee6b1\",\n \"description\": \"check-result\",\n \"assessment-check-id\": \"check-1\",\n \"assessment-asset/component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984e8\",\n \"result\": \"pass\",\n \"props\": [\n {\n \"name\": \"idref\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"xccdf_org.ssgproject.content_rule_package_prelink_removed\"\n },\n {\n \"name\": \"result\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"pass\"\n },\n {\n \"name\": \"time\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"2025-02-26T03:47:26-05:00\"\n },\n {\n \"name\": \"severity\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"medium\"\n }\n ],\n \"methods\": [\n \"TEST-AUTOMATED\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"c8ca2d73-c917-4901-9098-71b2c601f471\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2025-02-26T12:45:58+00:00\"\n}","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","section":null,"sha256_of_source_file":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806","slot":"6b","source":"IBM/assessment-result.json","title":"AR observation, carrying a result"},"data/snippets/ibm-cos-component.json":{"approach":"component-first","content":"{\n \"uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\",\n \"type\": \"service\",\n \"title\": \"COS\",\n \"description\": \"COS\",\n \"rules\": [\n {\n \"id\": \"cos_access_endpoint_type\",\n \"description\": \"Ensure Cloud Object Storage is accessible only by using {param: endpoint_access} endpoints\",\n \"params\": [\n {\n \"id\": \"endpoint_access\",\n \"label\": \"Endpoint Access type\",\n \"select\": {\n \"how-many\": \"one\",\n \"choice\": [\n \"public\",\n \"private\",\n \"direct\"\n ]\n }\n }\n ]\n },\n {\n \"id\": \"cos_encryption_hyperprotect_key_configured\",\n \"description\": \"Ensure Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"08159454-994c-49ed-8f78-f2293b1274a2\",\n \"source\": \"trestle://profiles/ACME_official/profile.json\",\n \"description\": \"ACME Official Profile\",\n \"set-parameters\": [\n {\n \"param-id\": \"endpoint_access\",\n \"values\": [\n \"private\"\n ]\n }\n ],\n \"implemented-requirements\": [\n {\n \"uuid\": \"c6ccfcbc-4553-40e6-b4e8-eadbff8d4756\",\n \"control-id\": \"ac-4\",\n \"description\": \"This control is implmeneted by ensuring the COS is only available on private endpoints.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"cos_access_endpoint_type\"\n }\n ]\n },\n {\n \"uuid\": \"455563ca-c454-41d5-aa3b-f57843d95aab\",\n \"control-id\": \"sc-28\",\n \"description\": \"Ensure that data is encrypted and the key is managed by the customer.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"cos_encryption_hyperprotect_key_configured\"\n }\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-cos-component","language":"json","pointer":"/component-definition/components/0","section":null,"sha256_of_source_file":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a","slot":"1","source":"IBM/cos-component-definition.json","title":"COS component, carrying rules"},"data/snippets/ibm-statement-rules.json":{"approach":"component-first","content":"{\n \"uuid\": \"c6ccfcbc-4553-40e6-b4e8-eadbff8d4756\",\n \"control-id\": \"ia-5.1\",\n \"description\": \"\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"08cc185d-27d8-4412-9cb4-25ebf1397a39\",\n \"description\": \"\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"idservice_password_min_length\"\n },\n {\n \"rule-id\": \"idservice_strong_pass_enabled\"\n }\n ]\n },\n {\n \"statement-id\": \"ia-5.1_smt.e\",\n \"uuid\": \"89f1f3be-d915-4134-94ab-577cba3f3c9a\",\n \"description\": \"\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"idservice_password_not_reuse_min_count\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-statement-rules","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/0","section":null,"sha256_of_source_file":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf","slot":"2","source":"IBM/idservice-component-definition.json","title":"implementing-rules on ia-5.1"},"data/snippets/ibm-validation-ansible.json":{"approach":"component-first","content":"{\n \"component-definition\": {\n \"uuid\": \"bbdf7ee6-3e0a-4065-8ecf-50f4129de473\",\n \"metadata\": {\n \"title\": \"Demo validation component definition\",\n \"last-modified\": \"2026-05-15T14:29:37+00:00\",\n \"version\": \"1.0\",\n \"oscal-version\": \"1.2.1\"\n },\n \"components\": [\n {\n \"uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"type\": \"validation\",\n \"title\": \"ANSIBLE\",\n \"description\": \"ANSIBLE\",\n \"checks\": [\n {\n \"id\": \"check-1\",\n \"description\": \"Check Cloud Object Storage is accessible only by using private endpoints\",\n \"rule-id\": \"cos_access_endpoint_type\",\n \"target-component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\"\n },\n {\n \"id\": \"check-2\",\n \"description\": \"Check Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)\",\n \"rule-id\": \"cos_encryption_hyperprotect_key_configured\",\n \"target-component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\"\n }\n ]\n }\n ]\n }\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-validation-ansible","language":"json","pointer":"$","section":null,"sha256_of_source_file":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","slot":"3","source":"IBM/ansible-validation-component-definition.json","title":"Ansible validation component, and its checks"},"data/source-files.json":{"excluded":[{"path":"disa/U_Readme_SRG_and_STIG.pdf","why":"About the STIG and SRG packages as a set rather than about any one guide, so it has no row in a table of one row per guide."},{"path":"oscal","why":"The OSCAL representations of this guidance are published separately. This table lists the documents read as input, not what was written from them."}],"files":[{"bytes":1032133,"guidance":"cis-postgresql-18","href":"sources/cis/CIS_PostgreSQL_18_Benchmark_v1.0.0.json","kind":"source","media":"json","media_label":"JSON document","mime":"application/json","name":"CIS_PostgreSQL_18_Benchmark_v1.0.0.json","publisher":"cis","sha256":"b72eda73c5bef60e2971c93261bc226594cfb8d8aa1be92deb6b2e121bf05379","size":"1.0 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":1506309,"guidance":"cis-postgresql-18","href":"sources/cis/CIS_PostgreSQL_18_Benchmark_v1.0.0.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"CIS_PostgreSQL_18_Benchmark_v1.0.0.pdf","publisher":"cis","sha256":"eae098af712ef333be2ebb146e72d8cdcba9f740f3a99e15de8363055f49f1b9","size":"1.5 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":6823924,"guidance":"cis-ubuntu-24-04","href":"sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","kind":"source","media":"json","media_label":"JSON document","mime":"application/json","name":"CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","publisher":"cis","sha256":"1a90fccb4442decd119382233ff8986caaaeede83dcf3c5ab22a87c747ab0c81","size":"6.8 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":10372494,"guidance":"cis-ubuntu-24-04","href":"sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.pdf","publisher":"cis","sha256":"8ebe23d21c23e383c81620ad04655e3b1d8fdf0b6eb9ddfdb7a97d0a5b5e7ef1","size":"10.4 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":640043,"guidance":"disa-ubuntu-22-04","href":"sources/disa/U_CAN_Ubuntu_22-04_LTS_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CAN_Ubuntu_22-04_LTS_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"73c26b6592dfc02f7f0eb456e0f89143ea1e2d8af7ebc61bd8bfae01f5a4c9d8","size":"640 kB","terms":"Public domain. A work of the United States Government."},{"bytes":658230,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml","publisher":"disa","sha256":"4c527cf0ed912947bb0c51be15f1a6bbc5a4bf05469ae083d94a01471edea77c","size":"658 kB","terms":"Public domain. A work of the United States Government."},{"bytes":934796,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1_Release_Memo.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_STIG_V1_Release_Memo.pdf","publisher":"disa","sha256":"9c3292baa367f97d0dc8c8a235a77dd49acfe53598d667902ab3e1e7d3d3d9a0","size":"935 kB","terms":"Public domain. A work of the United States Government."},{"bytes":425770,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_V1R5_Overview.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_V1R5_Overview.pdf","publisher":"disa","sha256":"7b4e8bc528e6e23c9bac33b760793d86e6d4954ff724f9db1e108ef071a22c8e","size":"426 kB","terms":"Public domain. A work of the United States Government."},{"bytes":301891,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_V1R5_Revision_History.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_V1R5_Revision_History.pdf","publisher":"disa","sha256":"3f00fb641e059376fb8b8d4404e3e2abf0a6a95950568740172086c441457a56","size":"302 kB","terms":"Public domain. A work of the United States Government."},{"bytes":456124,"guidance":"disa-postgres-16","href":"sources/disa/U_CD_Postgres_16_STIG_V1R2_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CD_Postgres_16_STIG_V1R2_Manual-xccdf.xml","publisher":"disa","sha256":"d468632da49f29b1616347dc7d79f429ff72ded2685a2ffb55b416d76192ce32","size":"456 kB","terms":"Public domain. A work of the United States Government."},{"bytes":432719,"guidance":"disa-epas","href":"sources/disa/U_EPAS_STIG_V2R1_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_EPAS_STIG_V2R1_Manual-xccdf.xml","publisher":"disa","sha256":"c9a9fb2f652495433a3639f740ef08d856c722be5d8bfdb729c87f843f3767ec","size":"433 kB","terms":"Public domain. A work of the United States Government."},{"bytes":936441,"guidance":"disa-windows-2019","href":"sources/disa/U_MS_Windows_Server_2019_STIG_V3R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2019_STIG_V3R8_Manual-xccdf.xml","publisher":"disa","sha256":"f483e86fdaf1caf0ad904b99ae117667fb61e48e0f62fbbcbd4ac30facef0e36","size":"936 kB","terms":"Public domain. A work of the United States Government."},{"bytes":906114,"guidance":"disa-windows-2022","href":"sources/disa/U_MS_Windows_Server_2022_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2022_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"991ad360c2ca40c5ab743b22b045ac9a98134a2c7360983ae32a1dac62de65de","size":"906 kB","terms":"Public domain. A work of the United States Government."},{"bytes":913750,"guidance":"disa-windows-2025","href":"sources/disa/U_MS_Windows_Server_2025_STIG_V1R1_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2025_STIG_V1R1_Manual-xccdf.xml","publisher":"disa","sha256":"5ae22836beba53091fa6269eaa974e54c226f3e2113cc9a3ec0183a8e16f51ee","size":"914 kB","terms":"Public domain. A work of the United States Government."},{"bytes":1267893,"guidance":"disa-rhel-8","href":"sources/disa/U_RHEL_8_STIG_V2R7_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_RHEL_8_STIG_V2R7_Manual-xccdf.xml","publisher":"disa","sha256":"9c5c57f34c78e3c70d5bc9755169b99f9e6965509b8e06f277c82982bccc8411","size":"1.3 MB","terms":"Public domain. A work of the United States Government."},{"bytes":1397262,"guidance":"disa-rhel-9","href":"sources/disa/U_RHEL_9_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_RHEL_9_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"bcb1c86161034ced8accca81f15efe40d4e4cfdce003b6b2b456cb49fcd094e3","size":"1.4 MB","terms":"Public domain. A work of the United States Government."}],"media_types":{"json":{"label":"JSON document","mime":"application/json"},"pdf":{"label":"PDF document","mime":"application/pdf"},"xml":{"label":"XML document","mime":"application/xml"}},"not_copied":[{"publisher":"cisa","what":"The SCuBA secure configuration baselines themselves","where":null,"where_label":null,"why":"The baselines are published by CISA and no copy of them is held here. What was read for this analysis was the baseline content as converted, and those conversions are published separately."},{"publisher":"aws","what":"The Security Hub controls, as published","where":"https://github.com/awslabs/oscal-content-for-aws-services","where_label":"oscal-content-for-aws-services","why":"This publisher ships its guidance as OSCAL already, so there is no separate source document to hold. The published content is linked rather than copied, so there is one copy to keep current."}],"not_shipped":[{"path":"cis","why":"Held locally, not redistributed. Download the Benchmarks from cisecurity.org into sources/cis/ under the filenames recorded here to rebuild anything that reads them."}],"note":"Every file under sources/, with its media type and size read from disk, and the benchmark row it belongs to. Built by tools/sources_files.py; verified by tools/verify.py --sources, which fails if a link points at a missing file, a file sits in the folder unlinked, or a file names a row that does not exist.","totals":{"bytes":29005893,"files":16,"size":"29.0 MB"}},"data/sources.json":{"columns":["Publisher","Guidance","Source form held"],"note":"The hardening guidance read as input to this analysis, one row per benchmark or guide rather than one per publisher, because the unit a reader recognises is the benchmark. Each row carries the documents read for it: a file icon downloads one file, a globe opens the publisher's page. What was written from this guidance, in OSCAL, is published separately and is not a column here; it is kept under 'publishers' so tools/verify.py --sources can still recompute it against the corpora.","publishers":{"aws":{"derivation":"AWS/oscal-content-for-aws-services-main: catalogs/*.oscal.json and component-definitions/*.oscal.json","full_name":"Amazon Web Services","name":"AWS","oscal_counts":{"catalogs":1,"component_definitions":230,"controls":452,"groups":77},"oscal_form":"one catalog of 452 controls across 77 groups, and 230 component definitions","source_counts":{}},"cis":{"derivation":"assessment-plan documents under Easy Dynamics/Center for Internet Security; source files under Hardening Guides/Center for Internet Security","full_name":"Center for Internet Security","name":"CIS","oscal_counts":{"assessment_plans":2},"oscal_form":"two assessment plans","source_counts":{"pdf":2,"xccdf_json":2}},"cisa":{"derivation":"assessment-plan documents under Easy Dynamics/CISA BOD 25-01; no publisher source material is present","full_name":"Cybersecurity and Infrastructure Security Agency","name":"CISA","oscal_counts":{"assessment_plans":4,"assessment_results":1},"oscal_form":"four assessment plans and one assessment result","source_counts":{}},"disa":{"derivation":"assessment-plan documents under Easy Dynamics/DISA; *-xccdf.xml under Hardening Guides/DISA","full_name":"Defense Information Systems Agency","name":"DISA","oscal_counts":{"assessment_plans":9},"oscal_form":"nine assessment plans","source_counts":{"xccdf_xml":9}}},"rows":[{"guidance":"Ubuntu Linux 24.04 LTS Benchmark","key":"cis-ubuntu-24-04","publisher":"cis","source_form":"XCCDF-derived JSON, and PDF","version":"v1.0.0"},{"guidance":"PostgreSQL 18 Benchmark","key":"cis-postgresql-18","publisher":"cis","source_form":"XCCDF-derived JSON, and PDF","version":"v1.0.0"},{"guidance":"Ubuntu 22.04 LTS STIG","key":"disa-ubuntu-22-04","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Ubuntu 24.04 LTS STIG","key":"disa-ubuntu-24-04","publisher":"disa","source_form":"XCCDF XML, and three release notes","version":"V1R5"},{"guidance":"Red Hat Enterprise Linux 8 STIG","key":"disa-rhel-8","publisher":"disa","source_form":"XCCDF XML","version":"V2R7"},{"guidance":"Red Hat Enterprise Linux 9 STIG","key":"disa-rhel-9","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Windows Server 2019 STIG","key":"disa-windows-2019","publisher":"disa","source_form":"XCCDF XML","version":"V3R8"},{"guidance":"Windows Server 2022 STIG","key":"disa-windows-2022","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Windows Server 2025 STIG","key":"disa-windows-2025","publisher":"disa","source_form":"XCCDF XML","version":"V1R1"},{"guidance":"PostgreSQL 16 STIG","key":"disa-postgres-16","publisher":"disa","source_form":"XCCDF XML","version":"V1R2"},{"guidance":"EDB Postgres Advanced Server STIG","key":"disa-epas","publisher":"disa","source_form":"XCCDF XML","version":"V2R1"},{"guidance":"BOD 25-01, the SCuBA baselines","key":"cisa-bod-25-01","links":[{"href":"https://www.cisa.gov/resources-tools/services/bod-25-01-implementing-secure-practices-cloud-services-required-configurations","kind":"web","label":"BOD 25-01, on the publisher's site"}],"publisher":"cisa","source_form":"None held here","version":null},{"guidance":"Security Hub security best-practice controls","key":"aws-security-hub","links":[{"href":"https://aws.github.io/aws-security-services-best-practices/guides/security-hub/","kind":"web","label":"Security Hub best practices, on the publisher's site"},{"href":"https://github.com/awslabs/oscal-content-for-aws-services","kind":"web","label":"The same controls as OSCAL, in the publisher's repository"}],"publisher":"aws","source_form":"Published as OSCAL, and linked","version":null}],"summary":"Hardening guidance used as input","summary_sub":"Two CIS Benchmarks, nine DISA STIGs, CISA BOD 25-01 and the AWS Security Hub controls, with the documents read for each."},"data/stakeholders.json":{"approaches":{"assessment-first":{"auditor":{"flows":[{"from":[{"model":"assessment-plan"}],"makes":"the observations","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor's run produces assessment results, not implementation claims. The workflow does not update the system security plan."},"benchmark":{"note":"The guidance provider writes activities and steps. The policy engine provider supplies executable checks.","writes":[{"model":"assessment-plan"}]},"engine":{"note":"The policy engine provider adds checks to the assessment plan. The plan identifies the engine in assessment-assets.","writes":[{"model":"assessment-plan"}]},"mapper":{"note":"The mapping provider edits the assessment plan, naming the framework controls covered by the activity.","writes":[{"model":"assessment-plan"}]},"owner":{"note":"The system owner supplies the profile and system security plan. The assessor's workflow does not depend on the owner's automation.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"note":"The technology provider writes activities and steps. The policy engine provider supplies executable checks.","writes":[{"model":"assessment-plan"}]}},"catalog-first":{"auditor":{"flows":[{"from":[{"kind":"software","model":"component-definition"}],"makes":"the findings","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor runs the checks independently. The resulting finding targets the system owner's implementation statement."},"benchmark":{"writes":[{"model":"catalog"}]},"engine":{"note":"The provider publishes checks as components of type software, referencing the guidance authors' catalog. System owners and auditors run the checks.","writes":[{"kind":"software","model":"component-definition"}]},"mapper":{"note":"The mapping provider writes a separate framework mapping. The published corpus contains no mapping collection for hardening guidance.","writes":[{"model":"mapping-collection"}]},"owner":{"flows":[{"from":[{"kind":"software","model":"component-definition"}],"makes":"the control-implementation responses","runtime":true,"to":[{"model":"system-security-plan"}]}],"note":"The system owner selects requirements and merges catalogs through a profile imported by the system security plan.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"writes":[{"model":"catalog"}]}},"component-first":{"auditor":{"flows":[{"from":[{"model":"assessment-plan"}],"makes":"the observations and findings","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"Observations roll up to control-level findings through check, rule and control."},"benchmark":{"writes":[{"kind":"software","model":"component-definition"}]},"engine":{"note":"Checks sit in a component of type validation and carry no framework tie.","writes":[{"kind":"validation","model":"component-definition"}]},"mapper":{"note":"The mapping provider publishes framework-to-framework mappings, its own document; product rules carry their framework tie.","writes":[{"model":"mapping-collection"}]},"owner":{"flows":[{"from":[{"kind":"validation","model":"component-definition"}],"makes":"the control-implementation responses","runtime":true,"to":[{"model":"system-security-plan"}]}],"note":"The owner also picks the validation components the assessment plan uses.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"note":"Each rule names its evidence type and carries the framework tie.","writes":[{"kind":"software","model":"component-definition"}]}}},"groups":[{"key":"guidance","label":"Hardening guidance authors","note":"Benchmark publishers and technology providers author guidance in the same OSCAL model for each approach."},{"key":"automation","label":"Automation providers and operators","note":"Providers build policy engines. System owners and auditors run checks to produce implementation responses or assessment results."}],"intro":"Seven parties publish, implement or assess hardening guidance. The table maps each party to OSCAL models and groups guidance authors separately from automation providers and operators.","note":"The mapping identifies the OSCAL models used by seven parties from guidance publication through audit. Component types distinguish guidance from checks where both use component definitions. Two groups identify guidance authors and automation providers and operators. Policy engine providers build tools; system owners and auditors execute the flows shown. Mapping providers are separate because guidance authors do not always publish framework mappings: STIGs carry CCIs, DISA's CCI list names the 800-53 controls, and third parties publish mappings through NIST's OLIR programme.","parties":[{"key":"regulatory","name":"Regulatory control providers","who":"NIST and other bodies publishing regulatory controls, such as SP 800-53"},{"key":"mapper","name":"Mapping providers","who":"Organisations linking guidance to frameworks through DISA's CCI list, NIST's OLIR programme or the Secure Controls Framework"},{"group":"guidance","key":"benchmark","name":"Technical hardening guidance providers","who":"CIS, DISA and other benchmark publishers"},{"group":"guidance","key":"software","name":"Technology providers","who":"Vendors publishing configuration guidance for hardware, software and services, independently or with benchmark publishers such as CIS"},{"group":"automation","key":"engine","name":"Policy engine providers","who":"Providers of assessment and checking tools such as OPA, Kyverno, ScubaGear and OpenSCAP"},{"group":"automation","key":"owner","name":"System owners","who":"Organisations implementing and documenting controls on a system"},{"group":"automation","key":"auditor","name":"Independent auditors","who":"Assessors running checks and reviewing results independently of system owners"}],"runtime":"A policy engine reads OSCAL, executes checks and writes OSCAL. Providers publish the checks; each flow identifies the party executing the checks."},"data/tradeoffs.json":{"approaches":{"assessment-first":{"cons":[{"body":"The activity title contains the required value, so changing the value requires editing the plan rather than resolving a profile.","title":"Required values lack resolvable parameters"},{"body":"The model provides activities and steps, so guidance nested four levels deep must be represented within those two structural tiers.","title":"Guide hierarchy is limited to two tiers"},{"body":"The published result references a plan absent from the corpus and assigns an observation a subject type not defined by the model.","title":"Published references and types need correction"}],"intro":"Publishing technical hardening guidance as an assessment plan has these strengths and risks.","pros":[{"body":"The assessment plan references implementation claims without adding claims, so adding or retiring a guide does not change the system security plan.","title":"Guidance stays outside the plan of record"},{"body":"A separate assessment results document imports a plan; the corpus includes findings that target objectives and reference supporting observations.","title":"Assessment results reference an assessment plan"},{"body":"An assessment subject can be an inventory item, allowing separate findings for two hosts running one operating system with different configurations.","title":"Subjects can identify individual hosts"},{"body":"Tasks carry schedules and identify execution platforms, placing the timing and runtime context for checks in the assessment plan.","title":"The plan records execution context"}]},"catalog-first":{"cons":[{"body":"The system security plan must address benchmark requirements alongside regulatory controls; whether each additional catalog requires a separate plan remains unsettled.","title":"Benchmark catalogs add maintenance work"},{"body":"Multiple frameworks and benchmarks require catalogs, profiles and mappings to be maintained together, increasing tool integration work and profile resolution complexity.","title":"Combined baselines complicate profile resolution"},{"body":"A by-component response identifies a component, not an instance, so one exception among a hundred hosts sharing that component cannot be distinguished.","title":"Responses do not identify individual instances"}],"intro":"Publishing technical hardening guidance as a catalog has these strengths and risks.","pros":[{"body":"Technical requirements use catalog controls and follow the same references through the remaining OSCAL models as regulatory controls.","title":"Technical and regulatory requirements use one model"},{"body":"A profile selects the hardening requirements an organisation adopts and sets organisationally defined parameters without changing the source catalog.","title":"Rules can be tailored"},{"body":"Controls, parts and nested groups represent checks, remediation and explanatory prose, including the structure of a thousand-page guide.","title":"Catalog structures represent guide content"},{"body":"A separate mapping-collection links guidance to a framework, allowing a third party to publish the mapping without owning either catalog.","title":"Third parties can publish framework mappings"}]},"component-first":{"cons":[{"body":"The proposal changes component definitions, system security plans, assessment plans and assessment results; existing schema support does not cover the proposed assemblies.","title":"Four models require schema changes"},{"body":"Rules describing the required component configuration enter the system security plan, which documents the system's implemented controls and current configuration.","title":"Desired state enters the plan of record"},{"body":"Rationale, audit procedure and remediation provide guidance context, but the published rules omit these fields and support remains proposed.","title":"Published rules omit guide context"},{"body":"A by-component response can reference a rule but not an individual instance, so exceptions remain associated with the component.","title":"Responses do not identify individual instances"},{"body":"Inventory items would also need implementing-rules support for a claim to identify a host rather than a component class.","title":"Host-level claims may require inventory support"}],"intro":"Publishing technical hardening rules in a component definition has these strengths and risks.","pros":[{"body":"A component definition describes how a product can meet controls; the proposed rules provide configuration requirements for automation in the same document.","title":"One artifact describes capability and supports automation"},{"body":"The product component holds the rule and a validation component holds the check; a second engine uses a second validation component.","title":"Rules and checks remain separate"},{"body":"The proposed implementing-rules assembly links a control implementation claim to the rule used to satisfy the control.","title":"Implementation claims can reference rules"},{"body":"Existing guidance directs technology providers to describe product capabilities in component definitions, where the proposal would also place hardening rules.","title":"Technology providers can extend component descriptions"}]}},"note":"Strengths and risks for each approach. Entry counts may differ; tools/approach_pages.py enforces prose budgets within and across approaches. Scenario figures remain on the scenario page. BUILD-LOG.md records the basis for each entry. Where present, schema_evidence identifies checked schema fragments and is not rendered."},"data/views.json":{"automation_argument":{"claim":"The automation argument treats applying and verifying hardening guidance as operational work, not just a finer-grained form of regulatory control. Automation coverage varies across the published guides.","claim_not_made":"Hardening guidance is never performed manually. The corpus includes manual procedures and does not support that claim.","evidence":[{"automated":"2271 activities carry method TEST","corpus":"STIG, all 9 files","manual":"none","stat_keys":["stig_method_test"]},{"automated":"576 steps","corpus":"CIS Ubuntu 24.04","manual":"40 steps","stat_keys":["cis_ubuntu_automated","cis_ubuntu_manual"]},{"automated":"0 steps","corpus":"CIS PostgreSQL 18","manual":"144 steps, covering every step; every activity carries method EXAMINE","note":"This guide provides a counterexample to the claim that all hardening procedures are automated.","stat_keys":["cis_postgres_automated","cis_postgres_manual"]}]},"crux":{"note":"Model placement alone does not establish whether guidance is binding. Every approach needs a way to distinguish requirements from optional configurations or assessment procedures."},"note":"Three editorial interpretations of a hardening rule, ordered by OSCAL layer rather than rank. The analysis uses a working definition without selecting an interpretation. Each view links to a stakeholder glossary term.","views":[{"aligned_approach":"catalog-first","definition":"A binding requirement, expressed as a shall. A rule differs from a regulatory control in specificity.","implies_layer":"Control","implies_model":"catalog","key":"requirement","label":"A requirement","stakeholder":"publisher"},{"aligned_approach":"component-first","definition":"A description of possible component configurations. The technology provider describes capabilities; the adopting organisation sets requirements.","implies_layer":"Implementation","implies_model":"component-definition","key":"capability","label":"A capability statement","stakeholder":"implementer"},{"aligned_approach":"assessment-first","definition":"A procedure for applying or verifying hardening guidance. Assessment activities and steps describe the work, with executable checks referenced for automation.","implies_layer":"Assessment","implies_model":"assessment-plan","key":"procedure","label":"An assessor's procedure","stakeholder":"assessor"}],"why_this_matters":"OSCAL has no dedicated core requirement-level field distinguishing shall, should and may. The gap affects every approach; model placement alone cannot establish whether guidance expresses requirements, capabilities or assessment procedures.","working_definition":{"status":"A working definition for comparing the three approaches without selecting an interpretation.","term":"rule","text":"One technical requirement or recommendation, finer-grained than a control, without any claim about whether it is binding."}}};
diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.js b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.js
index 96a90df..8fb4de7 100644
--- a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.js
+++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.js
@@ -1921,7 +1921,7 @@
document.documentElement.style.setProperty("--header-h", h.offsetHeight + "px");
}
/* --- the open questions:
The runtime. A policy engine reads OSCAL, executes checks and writes OSCAL. Providers publish the checks; each flow identifies the party executing the checks.
diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/examples.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/examples.json index 5910fec..5d245f2 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/examples.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/examples.json @@ -147,6 +147,12 @@ "bytes": 4275, "sha256": "06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806" }, + { + "approach": "component-first", + "path": "component-first/cos-ansible-validation-cd.json", + "bytes": 3332, + "sha256": "25fb1b83230e0c5df473013775b7b9769fb1b981d90b9d7539f57694ce3c89ec" + }, { "approach": "component-first", "path": "component-first/cos-component-definition.json", @@ -159,6 +165,12 @@ "bytes": 5230, "sha256": "36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf" }, + { + "approach": "component-first", + "path": "component-first/idservice-oscap-validation-cd.json", + "bytes": 6228, + "sha256": "b3f4d83f10133e7ee058b24eb1598f2f081704beaa68473a499c7d7b481a5d06" + }, { "approach": "component-first", "path": "component-first/oscap-validation-component-definition.json", diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/generated-pages.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/generated-pages.json index a842f5b..1d3e6ac 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/generated-pages.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/generated-pages.json @@ -4,6 +4,6 @@ "sha256": { "assessment-first": "78f38c7ef742a486d4860d618df1a78e4487fef226e77317a5621f5501bab18b", "catalog-first": "3319bcf155cdc7881b1dd1bfd42bdf9e679b2ed2ec5ec3b16576b04c15ed4ee8", - "component-first": "e169a9ca2c71028b41e0b0641dbba2a5086f6d453df2cf2eceefaf23df1d7827" + "component-first": "1049b6ef117611e6a1bd4db635f57d67895b7e3b6801a8d925a9c05c5901dc8e" } } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/oscal-artifacts.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/oscal-artifacts.json index f6926f6..b338767 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/oscal-artifacts.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/oscal-artifacts.json @@ -103,7 +103,7 @@ "totals": { "Assessment plan": 1, "Assessment results": 1, - "Component definition": 4 + "Component definition": 6 }, "files": [ { @@ -146,6 +146,22 @@ "href": "examples/component-first/assessment-result.json", "href_external": false }, + { + "file": "cos-ansible-validation-cd.json", + "model": "component-definition", + "model_label": "Component definition", + "title": "Demo component definition", + "counts": { + "components": 2, + "service": 1, + "validation": 1, + "rules": 2, + "implemented requirements": 2 + }, + "bytes": 3332, + "href": "examples/component-first/cos-ansible-validation-cd.json", + "href_external": false + }, { "file": "cos-component-definition.json", "model": "component-definition", @@ -176,6 +192,22 @@ "href": "examples/component-first/idservice-component-definition.json", "href_external": false }, + { + "file": "idservice-oscap-validation-cd.json", + "model": "component-definition", + "model_label": "Component definition", + "title": "Demo component definition", + "counts": { + "components": 2, + "service": 1, + "validation": 1, + "rules": 3, + "implemented requirements": 7 + }, + "bytes": 6228, + "href": "examples/component-first/idservice-oscap-validation-cd.json", + "href_external": false + }, { "file": "oscap-validation-component-definition.json", "model": "component-definition", diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/provenance.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/provenance.json index cde0f08..a5eb65f 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/provenance.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/provenance.json @@ -1,5 +1,5 @@ { - "generated_at": "2026-09-10T14:51:40+00:00", + "generated_at": "2026-10-09T18:46:33+00:00", "source_lock": "tools/source-lock.json", "source_inputs": { "version": 1, @@ -9,7 +9,7 @@ "approach": "component-first", "prefix": "IBM", "directory": "examples/component-first", - "expected_files": 6 + "expected_files": 8 }, { "key": "easy-dynamics", diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/questions.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/questions.json index 95d6218..e12d77c 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/questions.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/questions.json @@ -1,11 +1,11 @@ { - "note": "Editorial analysis questions maintained in this repository, grouped by issues shared across OSCAL and issues specific to each approach. Each question includes its reasoning; the OSCAL examples provide evidence without settling the design choices.", - "intro": "These questions identify unresolved design choices, not recommended changes. The analysis distinguishes what the OSCAL examples demonstrate from what remains open across models and approaches.", + "note": "Editorial analysis questions maintained in this repository, grouped by issues shared across all approaches and issues specific to each approach. Each question includes its reasoning; the OSCAL examples provide evidence without settling the design choices.", + "intro": "These questions identify unresolved design choices, not recommended changes. Each question sits under the approach where it is most acute, not exclusively; a question that applies to every approach sits in the shared section. The analysis distinguishes what the OSCAL examples demonstrate from what remains open across models and approaches.", "sections": [ { "key": "all", "label": "Across all three approaches", - "intro": "Gaps in the models themselves. None is answered by choosing an approach, and each changes what all three can express.", + "intro": "Questions shared by all three approaches. None is answered by choosing an approach, and each affects how the resulting artifacts are interpreted.", "questions": [ { "id": "xccdf", @@ -14,20 +14,36 @@ }, { "id": "rule-metadata", - "q": "Where does the metadata that describes a rule go?", - "why": "Rule metadata includes severity, weight, rationale and whether a check is automated or manual. The AWS and DISA OSCAL examples use namespaced properties for severity rather than a dedicated field. Consumers need shared conventions to interpret this content. Which metadata belongs on a rule, and whether shared namespaces or schema fields should carry it, remains open." + "q": "Where should rule metadata, including remediation, go?", + "why": "The DISA XCCDF benchmark carries the fields below, with distinct check and fix content. The AWS and DISA OSCAL examples use namespaced properties for severity rather than a dedicated field. The STIG and CIS assessment-plan examples include remediation as steps, but an AP step does not inherently distinguish a check from a fix; they rely on titles or step-type properties. Which metadata belongs in each OSCAL model, and how should consumers distinguish remediation from checks?", + "metadata": ["Severity", "Weight", "Version", "Title", "References", "Identifiers", "Vulnerability discussion", "Check content", "Fix text"] }, { - "id": "remediation", - "q": "Where does remediation land?", - "why": "The AWS catalog uses remediation links, while the STIG and CIS assessment plans carry remediation steps. The component-first examples do not carry remediation. These conventions do not provide a dedicated rule-remediation field. OSCAL's plan of action and milestones addresses a particular finding, not a reusable fix for every instance of a condition. Which structure should carry reusable remediation instructions remains open." + "id": "proposal-1", + "q": "What does an assessment-platform add when an assessment component already describes the runner?", + "why": "An OSCAL assessment plan can declare a runner as a component in assessment-assets, or describe an assessment-platform that includes a component. The examples do not establish what information the platform contributes beyond that component, such as execution context, or when that additional structure is needed. This choice applies regardless of where the hardening rule is modeled." + }, + { + "id": "proposal-3", + "q": "How should an assessment plan associate an assessment asset with its tasks or activities?", + "why": "Assessment results can associate a task and the assessment-platform that produced its results, using result origins and actors. An assessment plan has no corresponding way to say which component or assessment-platform should execute each task or activity before results exist. The component-first examples propose an assessment-asset-uuid and check-ids on each activity, naming the validation component that runs it and the checks it runs. The plan-side linkage is needed in all three approaches." + }, + { + "id": "proposal-4", + "q": "How should an observation identify the assessment asset and check that produced it when several assets are declared?", + "why": "An assessment result may hold observations from several assessment assets. In the current model, an observation can name the tool or assessment-platform that produced it through origin actors, but has no field naming the check it ran. The component-first examples propose an asset UUID and a check identifier on each observation, so a consumer can follow observation, asset, check, rule and control. The question applies to every approach that reports automated results." + }, + { + "id": "paper-comp-2", + "q": "Should desired-state values from benchmark guidance be replaced with actual-state values in the SSP?", + "why": "Benchmark guidance prescribes configuration values, while an SSP records the system owner's implementation claims, so every approach that produces SSP content faces this choice. In the component-first examples the SSP author copies a rule's parameters and may set a value equal to, stricter than or looser than the default. Replacing prescribed values could lose the benchmark baseline; keeping only prescribed values could misrepresent the implementation. How should tools keep the two meanings distinct?" } ] }, { "key": "catalog-first", "label": "Catalog-first", - "intro": "The rule is a control in a catalog. What is unsettled is how many documents that produces and where the outcome lands.", + "intro": "The rule is a control in a catalog. Open questions concern how catalogs combine, how many documents that produces and where outcomes land.", "questions": [ { "id": "one-ssp", @@ -36,12 +52,12 @@ }, { "id": "requirement-level", - "q": "If OSCAL gained a field for requirement level, how much of this disagreement would be left?", - "why": "OSCAL has no dedicated core field distinguishing shall, should and may. The examples can carry such labels in properties, but consumers need conventions to interpret them. Catalog-first puts benchmark and regulatory controls into the same profile. It remains unclear how much model-placement disagreement concerns binding force rather than document structure, and whether a shared requirement-level field would reduce it." + "q": "If OSCAL catalog controls gained a field for requirement level, how much of this disagreement would be left?", + "why": "OSCAL catalog controls have no dedicated core field distinguishing shall, should and may. The examples can carry such labels in properties, but consumers need conventions to interpret them. Catalog-first puts benchmark and regulatory controls into the same profile. It remains unclear how much model-placement disagreement concerns binding force rather than document structure, and whether a shared requirement-level field would reduce it." }, { "id": "control-type", - "q": "Should a control declare its type, so a regulatory control and a technical hardening control can be told apart?", + "q": "Should an OSCAL catalog control declare its type, so a regulatory control and a technical hardening control can be told apart?", "why": "The catalog/profile model can combine regulatory controls with technical hardening controls, but it has no dedicated core field distinguishing those kinds. Tools would need a shared property convention or schema support to report regulatory coverage separately from hardening coverage. This question concerns the kind of requirement, distinct from whether its requirement level is shall, should or may." }, { @@ -53,63 +69,48 @@ "id": "paper-cat-2", "q": "Where should benchmark outcomes be recorded, in SSP implementation claims or assessment results, and how should tools distinguish them?", "why": "An SSP by-component response describes an implementation claim, while assessment results record evidence and outcomes. A benchmark workflow may need both, but they answer different questions. Tools need to distinguish intended configuration from observed satisfaction and preserve the relationship between the two records." + }, + { + "id": "ssp-claim-evidence", + "q": "How should evidence be linked to an SSP implementation claim when a benchmark result is recorded there?", + "why": "An assessment-results observation can use relevant-evidence to point to supporting material. An SSP by-component implementation claim has no equivalent field for attaching evidence directly to the claim. If a benchmark outcome is recorded in the SSP, how should tools connect that claim to its supporting evidence without conflating it with an assessed result in an AR?" + }, + { + "id": "benchmark-vendor-catalogs", + "q": "How should an SSP combine benchmark and vendor catalogs that describe the same system recommendations?", + "why": "A benchmark and a vendor catalog may describe overlapping recommendations for the same system. An SSP responding to both needs to preserve which source supplied each recommendation while avoiding duplicate or conflicting implementation claims. It remains open whether one profile should reconcile those controls before the SSP imports it, or whether another convention should relate equivalent recommendations." } ] }, { "key": "component-first", "label": "Component-first", - "intro": "The rule sits on the component it configures. Open questions concern runner identification, importing component definitions and tailoring benchmark content.", + "intro": "The rule sits on the component it configures, and that component carries the tie to the framework. Open questions concern reaching other frameworks, copying component definitions into an SSP and tailoring benchmark content.", "questions": [ { "id": "which-cdef-maps", - "q": "Which component definition carries the tie to the framework, the one holding the rules or the one holding the checks?", - "why": "The control link is inline rather than held in a mapping collection. The software component definition holds rules, while the validation component definition holds checks; those artifacts may have different maintainers. A mapping provider could update either or both. The OSCAL examples do not establish which document should own that relationship or how duplicated mappings would stay consistent." - }, - { - "id": "proposal-1", - "q": "Should assessment platform usage be optional in an assessment plan?", - "why": "An assessment plan may describe a runner as a component, a platform using components, or a tool identified through properties. These alternatives leave open when an explicit assessment platform adds necessary information and when a component reference is sufficient for a consumer to execute or interpret a check." - }, - { - "id": "proposal-2", - "q": "When is an assessment component sufficient, and when is an assessment platform also needed?", - "why": "The OSCAL examples use different combinations of assessment-assets, assessment-platforms and components. They do not establish a shared rule for deciding whether a component alone identifies the runner or a platform must also describe its execution context. A consistent distinction would help consumers interpret equivalent workflows." - }, - { - "id": "proposal-3", - "q": "How should an assessment asset be associated with tasks or activities?", - "why": "A task identifies work to perform, while an assessment asset describes resources available to perform it. The component-first examples do not establish a complete, interoperable association between these structures. The question is which references should identify the runner for a particular task or activity." - }, - { - "id": "proposal-4", - "q": "How should an observation identify the assessment asset that produced it when several assets are declared?", - "why": "An assessment result may declare several assets, so naming an observation's producer requires an unambiguous relationship. The component-first result example does not establish a complete path from observation to producing asset. The open question is how consumers should recover that association without relying on tool-specific assumptions." + "q": "When the rule component carries the framework tie, how should another framework reach the same rules?", + "why": "In this approach the component definition holding the rules carries the tie to the framework through implemented-requirements; a check reaches a control only through check, rule and control, and a validation component carries no framework tie. A system held to another framework can override the tie in its SSP, or transpose results through a mapping collection between the two frameworks. Which route preserves rule-level precision, and who maintains it, remains open." }, { "id": "paper-comp-1", "q": "How should an SSP combine benchmark and vendor component definitions that describe the same system component?", - "why": "A system may use vendor component definitions alongside benchmark component definitions for the same software. Importing both can produce overlapping descriptions, rules and control implementations. It remains open whether an SSP should retain multiple OSCAL components, merge them, or use another convention to represent the single system component consistently." - }, - { - "id": "paper-comp-2", - "q": "Should desired-state values from benchmark component definitions be replaced with actual-state values in the SSP?", - "why": "Rules describe prescribed configuration, while an SSP records the system owner's implementation claims. Replacing prescribed values with actual values could lose the benchmark baseline; retaining only prescribed values could misrepresent implementation. The question is how to keep the two meanings distinct while preserving the relationship between benchmark requirements and the system." + "why": "A system may use vendor and benchmark component definitions for the same software, which can overlap in descriptions, rules and control implementations. OSCAL has no mechanism for importing a component definition, so the convention in this approach is to copy both into the SSP and merge them into one component, keeping only the rules that serve the profile's controls. What remains open is how a merged component records which source supplied each rule." }, { "id": "paper-comp-3", "q": "Which benchmark context should enter an SSP, and how should tools filter component-definition content during import?", - "why": "Benchmark content can include rules, parameters, rationale and procedural detail, not all of which serves the same purpose in an SSP. Import tooling needs a policy for retaining or omitting that context. The open issue is how to reduce duplication without losing information needed to interpret an implementation claim." + "why": "Benchmark content can include rules, parameters, rationale and procedural detail. The convention in this approach copies the rule identifier, description, parameter identifier and value, and the implementing-rules tie to controls; audit and remediation procedures are optional, at the SSP author's discretion. Copying duplicates content across every SSP that uses the component. Whether an import mechanism should replace copying, and what filtering it would need, remains open." }, { "id": "paper-comp-4", "q": "How should component definitions support benchmark selection, exclusions and parameter tailoring?", - "why": "The component-first examples place parameters on proposed rules and set-parameters on control implementations. Those structures address parameter values but do not provide a profile's selection and exclusion workflow. How component definitions should support benchmark tailoring, including the scope and persistence of tailoring decisions, remains open." + "why": "The component-first examples place parameters on proposed rules and set-parameters on control implementations. The convention in this approach is to tailor while copying: the SSP author drops rules that serve no selected control and sets parameter values, with no link back to the source component definition. That serves one system, but leaves open how tailoring decisions persist and stay auditable when the source component definition changes." }, { "id": "paper-comp-5", "q": "Should assessment plans or assessment results support importing component definitions with benchmark context?", - "why": "The component-first examples carry check content into an assessment plan through assessment assets. That demonstrates one encoding, not a dedicated import mechanism for all benchmark context. The question is whether plans or results should support such imports directly and which rules, parameters and provenance would need to survive." + "why": "The component-first examples carry checks into an assessment plan as assessment assets, while rules stay in the SSP and reach the plan and results through their imports, so SSP tailoring carries forward. That demonstrates one encoding, not a dedicated import mechanism. The question is whether plans or results should import component definitions directly, and which rules, parameters and provenance would need to survive." } ] }, @@ -121,7 +122,7 @@ { "id": "paper-ap-1", "q": "How should assessment-plan benchmarks support tailoring available through catalogs and profiles?", - "why": "Activities and steps have no parameter assembly, so the assessment-first examples place required values in text. Tailoring can therefore require editing procedural content rather than selecting controls or setting parameter values through a profile. The question is how to support reusable, auditable tailoring without losing the assessment workflow." + "why": "OSCAL assessment-plan activities and steps have no parameter assembly, so the assessment-first examples place required values in text. Tailoring can therefore require editing procedural content rather than selecting controls or setting parameter values through a profile. The question is how to support reusable, auditable tailoring without losing the assessment workflow." } ] } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/six-questions.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/six-questions.json index 8056f22..73fe775 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/six-questions.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/six-questions.json @@ -360,11 +360,11 @@ { "slot": "4", "approach": "component-first", - "state": "partial", + "state": "filled", "snippet_ids": [ "ibm-validation-ansible" ], - "note": "The proposed rule reference extends by-component. An assessor can include the component definition and associated checks in an assessment plan.", + "note": "In the SSP every subject is a component, the whole environment defaulting to This System, so the by-component response names what the rule runs against.", "mechanisms": [ "assembly", "proposed" @@ -443,7 +443,7 @@ "ibm-ap-task-subjects", "ibm-ar-observation" ], - "note": "The examples leave runner associations unresolved, including how an assessment asset links to a task or an observation.", + "note": "Each assessment-plan activity names its runner through the proposed assessment-asset-uuid and its checks through check-ids, and each observation carries the asset and check that produced it.", "mechanisms": [ "assembly", "proposed" diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/stakeholders.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/stakeholders.json index ebaf5e1..65bae13 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/stakeholders.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/stakeholders.json @@ -143,11 +143,10 @@ "mapper": { "writes": [ { - "model": "component-definition", - "kind": "software or validation" + "model": "mapping-collection" } ], - "note": "The mapping provider edits a component definition. Whether the rules or the checks carry the framework mapping remains open." + "note": "The mapping provider publishes framework-to-framework mappings, its own document; product rules carry their framework tie." }, "benchmark": { "writes": [ @@ -163,7 +162,8 @@ "model": "component-definition", "kind": "software" } - ] + ], + "note": "Each rule names its evidence type and carries the framework tie." }, "engine": { "writes": [ @@ -172,7 +172,7 @@ "kind": "validation" } ], - "note": "The provider publishes checks in a component of type validation. System owners and auditors run the checks." + "note": "Checks sit in a component of type validation and carry no framework tie." }, "owner": { "writes": [ @@ -199,7 +199,8 @@ ], "makes": "the control-implementation responses" } - ] + ], + "note": "The owner also picks the validation components the assessment plan uses." }, "auditor": { "flows": [ @@ -215,10 +216,10 @@ "model": "assessment-results" } ], - "makes": "the observations" + "makes": "the observations and findings" } ], - "note": "The auditor runs checks through an assessment plan, allowing the result to identify a host rather than a component." + "note": "Observations roll up to control-level findings through check, rule and control." } }, "assessment-first": { diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/component-first/cos-ansible-validation-cd.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/component-first/cos-ansible-validation-cd.json new file mode 100644 index 0000000..e470947 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/component-first/cos-ansible-validation-cd.json @@ -0,0 +1,96 @@ +{ + "component-definition": { + "uuid": "51f93843-4b96-4794-a590-1cbc6bad9b73", + "metadata": { + "title": "Demo component definition", + "last-modified": "2026-10-09T18:45:21+00:00", + "version": "1.0", + "oscal-version": "1.2.1" + }, + "components": [ + { + "uuid": "0c410eb1-52cd-40bc-bf1d-c80126a985f9", + "type": "service", + "title": "COS", + "description": "COS", + "rules": [ + { + "id": "cos_access_endpoint_type", + "description": "Ensure Cloud Object Storage is accessible only by using {param: endpoint_access} endpoints", + "params": [ + { + "id": "endpoint_access", + "label": "Endpoint Access type", + "select": { + "how-many": "one", + "choice": [ + "public", + "private", + "direct" + ] + } + } + ] + }, + { + "id": "cos_encryption_hyperprotect_key_configured", + "description": "Ensure Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)" + } + ], + "control-implementations": [ + { + "uuid": "08159454-994c-49ed-8f78-f2293b1274a2", + "source": "trestle://profiles/ACME_official/profile.json", + "description": "ACME Official Profile", + "set-parameters": [ + { + "param-id": "endpoint_access", + "values": [ + "private" + ] + } + ], + "implemented-requirements": [ + { + "uuid": "c6ccfcbc-4553-40e6-b4e8-eadbff8d4756", + "control-id": "ac-4", + "description": "This control is implmeneted by ensuring the COS is only available on private endpoints.", + "implementing-rules": [ + {"rule-id": "cos_access_endpoint_type"} + ] + }, + { + "uuid": "455563ca-c454-41d5-aa3b-f57843d95aab", + "control-id": "sc-28", + "description": "Ensure that data is encrypted and the key is managed by the customer.", + "implementing-rules": [ + {"rule-id": "cos_encryption_hyperprotect_key_configured"} + ] + } + ] + } + ] + }, + { + "uuid": "0c410eb1-52cd-40bc-bf1d-c80126a984f8", + "type": "validation", + "title": "ANSIBLE", + "description": "ANSIBLE", + "checks": [ + { + "id": "check-1", + "description": "Check Cloud Object Storage is accessible only by using private endpoints", + "rule-id": "cos_access_endpoint_type", + "target-component-uuid": "0c410eb1-52cd-40bc-bf1d-c80126a985f9" + }, + { + "id": "check-2", + "description": "Check Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)", + "rule-id": "cos_encryption_hyperprotect_key_configured", + "target-component-uuid": "0c410eb1-52cd-40bc-bf1d-c80126a985f9" + } + ] + } + ] + } +} \ No newline at end of file diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/component-first/idservice-oscap-validation-cd.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/component-first/idservice-oscap-validation-cd.json new file mode 100644 index 0000000..2f8000c --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/component-first/idservice-oscap-validation-cd.json @@ -0,0 +1,183 @@ +{ + "component-definition": { + "uuid": "5387e03f-f015-4c6c-a2b8-384f2319c087", + "metadata": { + "title": "Demo component definition", + "last-modified": "2026-10-09T18:45:21+00:00", + "version": "1.0", + "oscal-version": "1.2.1" + }, + "components": [ + { + "uuid": "0c410eb1-52cd-40bc-bf1d-c80126a984e9", + "type": "service", + "title": "IDSERVICE", + "description": "IDSERVICE", + "rules": [ + { + "id": "idservice_password_min_length", + "description": "Ensure min. length of password", + "params": [ + { + "id": "idservice_min_pass_len", + "label": "Min. password length", + "select": { + "how-many": "one", + "choice": [ + "8", + "12", + "16" + ] + } + } + ] + }, + { + "id": "idservice_password_not_reuse_min_count", + "description": "Ensure password is not reused below # count", + "params": [ + { + "id": "idservice_min_pass_reuse_count", + "label": "Min. password reuse count", + "select": { + "how-many": "one", + "choice": [ + "4", + "8" + ] + } + } + ] + }, + { + "id": "idservice_strong_pass_enabled", + "description": "Ensure strong password policy with mix of alphabets, digits, and special chars" + } + ], + "control-implementations": [ + { + "uuid": "08159454-994c-49ed-8f78-f2293b1274a2", + "source": "trestle://profiles/ACME_official/profile.json", + "description": "ACME Official Profile", + "set-parameters": [ + { + "param-id": "idservice_min_pass_len", + "values": [ + "8" + ] + }, + { + "param-id": "idservice_min_pass_reuse_count", + "values": [ + "4" + ] + } + ], + "implemented-requirements": [ + { + "uuid": "c6ccfcbc-4553-40e6-b4e8-eadbff8d4756", + "control-id": "ia-5.1", + "description": "", + "statements": [ + { + "statement-id": "ia-5.1_smt.a", + "uuid": "08cc185d-27d8-4412-9cb4-25ebf1397a39", + "description": "", + "implementing-rules": [ + {"rule-id": "idservice_password_min_length"}, + {"rule-id": "idservice_strong_pass_enabled"} + ] + }, + { + "statement-id": "ia-5.1_smt.e", + "uuid": "89f1f3be-d915-4134-94ab-577cba3f3c9a", + "description": "", + "implementing-rules": [ + {"rule-id": "idservice_password_not_reuse_min_count"} + ] + } + ] + }, + { + "uuid": "455563ca-c454-41d5-aa3b-f57843d95aab", + "control-id": "ia-5.4", + "description": "", + "implementing-rules": [ + {"rule-id": "idservice_password_min_length"}, + {"rule-id": "idservice_strong_pass_enabled"} + ] + }, + { + "uuid": "8d18be8a-232a-42dd-8554-f3ff42770915", + "control-id": "cc-1", + "description": "", + "implementing-rules": [ + {"rule-id": "idservice_password_min_length"}, + {"rule-id": "idservice_strong_pass_enabled"} + ] + }, + { + "uuid": "9fda67bf-8e40-47ea-830f-d045ce5113d9", + "control-id": "cc-2", + "description": "", + "implementing-rules":[ + {"rule-id":"idservice_password_min_length"} + ] + }, + { + "uuid": "2c457819-da30-44a3-9497-b2838f7cbdd1", + "control-id": "pr-1", + "description": "", + "implementing-rules":[ + {"rule-id":"idservice_password_min_length"} + ] + }, + { + "uuid": "a5cdefdc-7f6b-4ffa-849f-196785e6432f", + "control-id": "pr-2", + "description": "", + "implementing-rules":[ + {"rule-id":"idservice_password_not_reuse_min_count"} + ] + }, + { + "uuid": "1c4da059-486c-4383-b564-6aa57229ab6a", + "control-id": "sc-1", + "description": "", + "implementing-rules":[ + {"rule-id":"idservice_password_not_reuse_min_count"} + ] + } + ] + } + ] + }, + { + "uuid": "0c410eb1-52cd-40bc-bf1d-c80126a984e8", + "type": "validation", + "title": "OSCAP", + "description": "OSCAP", + "checks": [ + { + "id": "check-1", + "description": "Check min. length of password", + "rule-id": "idservice_password_min_length", + "target-component-uuid": "0c410eb1-52cd-40bc-bf1d-c80126a984f9" + }, + { + "id": "check-2", + "description": "Check password is not reused below # count", + "rule-id": "idservice_password_not_reuse_min_count", + "target-component-uuid": "0c410eb1-52cd-40bc-bf1d-c80126a984f9" + }, + { + "id": "check-3", + "description": "Check strong password policy with mix of alphabets, digits, and special chars", + "rule-id": "idservice_strong_pass_enabled", + "target-component-uuid": "0c410eb1-52cd-40bc-bf1d-c80126a984f9" + } + ] + } + ] + } +} \ No newline at end of file diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/source-lock.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/source-lock.json index 3e520b4..f6a0af5 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/source-lock.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/source-lock.json @@ -6,7 +6,7 @@ "approach": "component-first", "prefix": "IBM", "directory": "examples/component-first", - "expected_files": 6 + "expected_files": 8 }, { "key": "easy-dynamics", diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/test_source_inputs.py b/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/test_source_inputs.py index 34de8be..86f8968 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/test_source_inputs.py +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/test_source_inputs.py @@ -96,7 +96,7 @@ def test_published_lock_has_exact_source_identities(self): ibm, easy, aws = PINNED["sources"] self.assertEqual(PINNED["version"], 1) self.assertEqual((ibm["key"], ibm["prefix"], ibm["directory"], ibm["expected_files"]), - ("ibm", "IBM", "examples/component-first", 6)) + ("ibm", "IBM", "examples/component-first", 8)) self.assertEqual((easy["key"], easy["prefix"], easy["directory"], easy["expected_files"]), ("easy-dynamics", "Easy Dynamics", "examples/assessment-first", 19)) self.assertEqual(aws["prefix"], "AWS/oscal-content-for-aws-services-main") diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/verify.py b/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/verify.py index 3122bba..c03f71b 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/verify.py +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/tools/verify.py @@ -2049,7 +2049,7 @@ def _words(text: str) -> int: def check_questions() -> None: - """Four sections of editorial questions, with stable ids and reasoning.""" + """Shared and approach-specific questions with stable ids.""" print("\n[questions] editorial content and stable question identifiers") with open(os.path.join(DATA, "questions.json"), encoding="utf-8") as stream: q = json.load(stream) @@ -2057,7 +2057,7 @@ def check_questions() -> None: approaches = [a["key"] for a in json.load(stream)["approaches"]] check("questions carry no background attribution", not editorial_reference_paths(q)) secs = q["sections"] - check("four sections: one across the three, then one each", + check("four sections: shared questions, then one per approach", [s["key"] for s in secs] == ["all"] + approaches, str([s["key"] for s in secs])) for s in secs: @@ -2081,12 +2081,13 @@ def check_questions() -> None: check(f"{where}: says why it is open, in a paragraph", isinstance(reason, str) and 20 <= len(reason.split()) <= 90, f"{len(reason.split()) if isinstance(reason, str) else 0} words") - # IDs remain stable so existing deep links continue to resolve. + # IDs remain stable for questions retained after a reclassification. required = { - "all": {"xccdf", "rule-metadata", "remediation"}, - "catalog-first": {"one-ssp", "requirement-level", "control-type", "paper-cat-1", "paper-cat-2"}, - "component-first": {"which-cdef-maps", "proposal-1", "proposal-2", "proposal-3", - "proposal-4", "paper-comp-1", "paper-comp-2", "paper-comp-3", + "all": {"xccdf", "rule-metadata", "proposal-1", "proposal-3", "proposal-4", + "paper-comp-2"}, + "catalog-first": {"one-ssp", "requirement-level", "control-type", "paper-cat-1", "paper-cat-2", + "ssp-claim-evidence", "benchmark-vendor-catalogs"}, + "component-first": {"which-cdef-maps", "paper-comp-1", "paper-comp-3", "paper-comp-4", "paper-comp-5"}, "assessment-first": {"paper-ap-1"}, } @@ -2533,19 +2534,28 @@ def entries(e): # Editing somebody else's document is a heavier ask than shipping your own, # and the row said nothing at all about it. # - # So: exactly one approach gives this party a document of its own, and the - # other two give it a document to edit. Both are asserted, because a row - # with a model on it and no explanation of whose model it is would read as - # a fourth author of the same file. + # The component approach then moved again, on the approach's own account + # of its parties (issue 16): the technology provider ties each rule to the + # framework in its own component definition, the validation component + # carries no tie, and the mapping provider publishes mappings between + # frameworks, which is a mapping collection of its own. The tie stays + # inline; what the mapping provider ships there is the framework-to- + # framework mapping that transposes a plan of record to another regulation. + # + # So: two approaches give this party a document of its own, and the third + # gives it a document to edit. Both are asserted, because a row with a + # model on it and no explanation of whose model it is would read as a + # fourth author of the same file. MAPS_IN = {"catalog-first": "mapping-collection", - "component-first": "component-definition", + "component-first": "mapping-collection", "assessment-first": "assessment-plan"} + OWN_DOCUMENT = {"catalog-first", "component-first"} for key in sorted(sh["approaches"]): per = sh["approaches"][key] holders = sorted(k for k in keys if any(m["model"] == "mapping-collection" for m in entries(per[k]))) - wants = ["mapper"] if key == "catalog-first" else [] + wants = ["mapper"] if key in OWN_DOCUMENT else [] check(f"{key}: a mapping collection is the mapping provider's, or nobody's", holders == wants, str(holders)) named = [m["model"] for m in entries(per["mapper"])] @@ -2557,9 +2567,9 @@ def entries(e): # Whether it is the party's own document is not taken from the prose. # A document is somebody else's exactly when somebody else writes it, # and that is already in the table: the guidance authors and the engine - # provider write the component definition and the assessment plan, and - # nobody but the mapping provider writes a mapping collection. - own = key == "catalog-first" + # provider write the assessment plan, and nobody but the mapping + # provider writes a mapping collection. + own = key in OWN_DOCUMENT others = sorted(k for k in keys if k != "mapper" and any(m["model"] == MAPS_IN[key] for m in entries(per[k]))) check(f"{key}: the {MAPS_IN[key]} is "