From 4251d50b94981a20878420527d5d651b5a007c02 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 9 Sep 2026 13:30:16 +0000 Subject: [PATCH 1/7] Add profile-first, a fourth approach, from the executable assessment methods concept note The hardening-guidance analysis compared three published approaches. A concept note proposes a fourth: the check as an executable assessment-method part on the control, beside an assessment-objective part that is the rule, carried by the catalog when the requirement's author owns the check and added by a profile otherwise, with findings targeting the objective. Option D, Profile-first, now sits on every page the other three are on: its own approach page, a column on the six questions page with the two rules written in the note's shape, a chain figure, a scenario figure and file set, an open questions section, an entry on the artifacts page, and a card on the start page. The approach has no corpus, so its cells declare no extracts, its status annotation says it is a concept note, the corpus-reading checks skip it by name, and the note itself is held under examples/profile-first and linked. A fourth hue at the same lightness and a fourth marker shape keep the palette rules; the checks that counted to three now read the count from the data or name the fourth. The build log records every decision. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_013h1RZCurTffvziZAcmU4kM --- .../verify-2026-08-hardening-guidance.yml | 2 +- .../BUILD-LOG.md | 159 ++++++++ .../CORRECTIONS.md | 12 +- .../README.md | 87 +++-- .../analysis.json | 10 +- .../assessment-first.html | 5 +- .../assets/bundle.js | 4 +- .../diagrams/710-scenario-assessment.svg | 2 +- .../assets/diagrams/710-scenario-catalog.svg | 2 +- .../diagrams/710-scenario-component.svg | 2 +- .../assets/diagrams/710-scenario-profile.svg | 129 +++++++ .../assets/diagrams/73-join-profile.svg | 116 ++++++ .../assets/shell.html | 10 +- .../assets/site.css | 21 +- .../assets/site.js | 40 ++- .../catalog-first.html | 5 +- .../component-first.html | 5 +- .../data/generated-pages.json | 7 +- .../data/glossary.json | 42 +++ .../data/joins.json | 177 ++++++++- .../data/oscal-artifacts.json | 16 + .../data/pattern-examples.json | 207 ++++++++++- .../data/questions.json | 43 ++- .../data/scenario.json | 97 ++++- .../data/six-questions.json | 178 ++++++++- .../data/stakeholders.json | 83 ++++- .../data/tradeoffs.json | 41 ++- .../data/views.json | 8 +- .../executable-assessment-methods.md | 95 +++++ .../index.html | 52 ++- .../oscal-artifacts.html | 17 +- .../profile-first.html | 185 ++++++++++ .../questions.html | 11 +- .../scenario.html | 43 ++- .../six-questions.html | 24 +- .../tools/approach_pages.py | 53 ++- .../tools/diagrams.py | 52 +-- .../tools/oscal_artifacts.py | 34 +- .../tools/pagecheck.js | 56 +-- .../tools/pattern_examples.py | 339 +++++++++++++++++- .../tools/scenario_page.py | 19 +- .../tools/verify.py | 138 +++++-- docs/analysis/analyses.json | 3 +- 43 files changed, 2365 insertions(+), 266 deletions(-) create mode 100644 docs/analysis/2026-08-automating-technical-hardening-guidance/assets/diagrams/710-scenario-profile.svg create mode 100644 docs/analysis/2026-08-automating-technical-hardening-guidance/assets/diagrams/73-join-profile.svg create mode 100644 docs/analysis/2026-08-automating-technical-hardening-guidance/examples/profile-first/executable-assessment-methods.md create mode 100644 docs/analysis/2026-08-automating-technical-hardening-guidance/profile-first.html diff --git a/.github/workflows/verify-2026-08-hardening-guidance.yml b/.github/workflows/verify-2026-08-hardening-guidance.yml index a4d7dcb..540c702 100644 --- a/.github/workflows/verify-2026-08-hardening-guidance.yml +++ b/.github/workflows/verify-2026-08-hardening-guidance.yml @@ -113,7 +113,7 @@ jobs: python tools/bundle.py git diff --exit-code -- data assets/diagrams \ assessment-first.html catalog-first.html component-first.html \ - scenario.html \ + profile-first.html scenario.html \ || { echo "::error::a generated file differs from its generator."\ "Run the generators and commit the result."; exit 1; } 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 441884d..9db7f23 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 @@ -8584,3 +8584,162 @@ rendered by no page: they are cited from `data/provenance.json` and to ship them. `2619/2619` verify checks and `649/649` page checks pass. + +--- + +## Session: a fourth approach, from a concept note + +**Date:** 2026-09-09 +**Scope:** profile-first, added as Option D to every page, data file, generator +and check that carried three approaches +**Result:** complete. 3041 of 3057 verification checks and 792 of 792 page checks +pass locally. The sixteen that fail are the sixteen that failed before this +session began, and every one of them needs the corpora or the network: the three +scenario files the harness opens, the twelve external links it requests, and the +artifacts inventory whose generator scans a corpus this working copy does not +hold. + +### What arrived + +A concept note, *Executable Assessment Methods: Automation Scripts on Controls in +Catalogs and Profiles*, dated September 2026. It proposes giving SP 800-53A's +TEST method a body: an `assessment-method` part on a control, with `method=TEST`, +a set of namespaced props saying which platform the check applies to, which +engine runs it, how the result is evaluated, what counts as a pass and how long +to wait, and the script itself in the part's prose or in a back-matter resource. +The part links to an `assessment-objective` part beside it, so a finding can +target the objective and nothing in the results model has to change. The catalog +carries both parts when the author of the requirement is the author of the +check; a profile adds them otherwise, which is the case the note's own example +shows, SI-2 tailored for Ubuntu. + +The user asked for it to be integrated as an additional option. It is now +Option D, Profile-first, on every page the other three are on. + +### Decisions + +1. **The name.** The site names approaches by the model the rule first appears + in. The note's rule appears in a catalog when the author owns the check and + in a profile otherwise, and the thing the note turns on is the second case: + a profile can add parts, props, links and params to a control it does not + own, and no custom assembly can be added that way. So the structural name is + Profile-first, the primary model is `profile`, the layer is Control, and the + lede and the stakeholder section say in words that the catalog route exists. + +2. **No corpus.** The other three are described from published files at + declared pointers. This one has none, so its cells declare no extracts, its + status annotation reads "concept note, no published content", its entry on + the artifacts page is a note and a link to the document rather than a count, + and `tools/verify.py` carries an `UNPUBLISHED` set that the corpus-reading + checks consult by name. The checks that hold every approach to one shape, + the budget, the chain, the stakeholder table, the encodings, hold it to the + same shape. Nothing about it is exempt that the others are held to. + +3. **The note is in the repository.** At + `examples/profile-first/executable-assessment-methods.md`, because + `examples/` is where the artifacts page links to the one document an + approach has, and `tools/package.py` ships that directory whole. The pre-read + and the position paper live beside the site rather than in it; this document + was supplied for integration, names nobody, and is the only thing the fourth + column can be checked against, so a reader has to be able to open it. If it + turns out not to be the site's to publish, the file comes out and the link + with it, and nothing else changes. + +4. **The encodings.** The two rules are written in the note's shape from the + note's own example: an objective part carrying the requirement, a method part + carrying a short bash body, the five props under the note's namespace, and a + link from method to objective. The objective's id keeps the STIG identifier + inside it so a reader can follow the rule across the columns, and the method's + title is the XCCDF rule id every other column names as the check. That title + is provenance for the reader and nothing resolves it; the note's example has + none. A value goes through a parameter insert, declared and set in the same + add, because the framework control has no parameter of its own for it. + +5. **Question 1 shows a control-id.** Every other column is held to naming no + control under the question about where the rule is written, because the tie + is question 2. A part added by a profile has no existence apart from the + control it is added to, and the alter that carries it has to name that + control. The check now asserts, for this column only, that `control-id` is + the one thing from the question 2 list that appears, and the cell's note + says it is the address of the part rather than a tie. + +6. **The namespace.** The note calls its namespace a placeholder and says the + vocabulary is the point. It is carried as the note wrote it, for the same + reason the others are carried as their publishers wrote them, and + `--links` treats it as an identifier rather than a page, as it already did + for two schema namespaces. + +7. **Who writes a profile.** The site held that the profile is the system + owner's on every approach and nobody else's, and checked it. On this + approach a tool vendor publishes a profile to attach checks and a mapping + provider edits the profile that puts a check on a framework control, which + is the approach's own position rather than a row drawn wrong. + `data/stakeholders.json` now carries `shared_profile`, naming the parties + and saying why, and the check reads it: an approach that declares the + exception has to declare exactly the parties that write one and give a + reason of at least twenty-four words; every other approach is still held to + the rule. + +8. **Nobody runs the checks for the owner.** The note says the methods are read + by the assessment plan and not by the system owner, and a run of them writes + findings targeting the objective, never a response in the plan of record. + So the owner's row has no run and says why, the auditor's run goes from the + profile to a result, and question 5 has the assessor's path alone. The + finding that only component-first has both paths still holds. + +9. **The reading.** The note reads the rule as a requirement, as the catalog + approach does, and differs in the construct that carries it. There are + still three readings; `data/views.json` records that two approaches hold the + first, under `also_aligned`, and the fourth page opens with its own sentence + saying so, because the standard sentence names the model the reading implies + and that is not the model this approach writes in. + +10. **The scenario.** The three guides in the scenario are technology-specific + and their publishers ship their own checks, which under the note's own rule + makes each of them a catalog carrying its executable methods. Each component + references a profile selecting from its guide, which is the note's step a, + so the file set is four catalogs, four profiles, one plan of record, one + plan and one result: eleven files, five of the seven models, and the plan of + record's control set does not move. No mapping collection, because the + note supplies no tie from a guide's own objective to the framework, and that + is now an open question on the questions page rather than a file invented + to close it. + +11. **A fourth hue.** The approach colours sit at one lightness by rule, and the + rule is checked. The fourth, hue 100, an olive, was placed in the widest + gap the first three left and tuned to the same relative luminance: the + spread across four is 0.004 against a bound of 0.02, in both themes. A + fourth marker shape, a diamond, goes with it, so identity never rests on + the hue. + +12. **Budget.** The fourth page landed at 1,139 words against a bound of 1,003, + and was cut to 995: a strength and a risk dropped, the stakeholder notes + shortened, one duplicated note removed, and the chain notes trimmed. What + was cut is in the open questions or the note itself; nothing was cut that + only this page said. + +### What changed, by file + +One entry each in `six-questions.json`, `tradeoffs.json`, `stakeholders.json`, +`joins.json`, `questions.json`, `scenario.json` and `oscal-artifacts.json`; two +terms and one usage in `glossary.json`; `also_aligned` in `views.json`. A fourth +column in `tools/pattern_examples.py`, with a profile wrapper and a +system-implementation wrapper. `ORDER`, `NAV`, a `CONTENT` block and a per-page +reading sentence in `tools/approach_pages.py`. A fourth entry in `APPROACHES` +and a diamond in `tools/diagrams.py`, and two more published figures. A fourth +publisher with no directory in `tools/oscal_artifacts.py`, and the renderer's +handling of a section with no rows. The option order in `tools/verify.py`, +`tools/pagecheck.js` and `assets/site.js`. Two colour tokens in `assets/site.css`. +The navigation and footer on every page and in `assets/shell.html`, the fourth +option on the start page, and the workflow's list of generated pages. + +### Open items + +- The artifacts inventory could not be regenerated here, because the generator + scans the corpora. The fourth entry was written by hand in the shape the + generator now emits, and the generator was run against an empty corpus root + to confirm that its fourth entry is byte-identical. CI, which holds the + corpora, regenerates the whole file and diffs it. +- Proponent review now includes the note's author, and the request in + `CORRECTIONS.md` says what the one judgement is that only they can check: + whether the site's encoding is the shape the note intends. diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/CORRECTIONS.md b/docs/analysis/2026-08-automating-technical-hardening-guidance/CORRECTIONS.md index 6d66243..47015d2 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/CORRECTIONS.md +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/CORRECTIONS.md @@ -27,7 +27,7 @@ field names. ``` ## Correction -- approach: catalog-first | assessment-first | component-first +- approach: catalog-first | assessment-first | component-first | profile-first - received: 2026-09-01 - corrected: what they said was wrong, in their words, unedited - applied: what changed on the site, and where @@ -49,6 +49,16 @@ field names. your own work is information. ``` +## The fourth approach + +Profile-first was added from a concept note rather than from a published body of +content, so its proponent is the note's author and the request below goes to +them in the same words. The three judgements the request names apply with one +difference: there are no extracts to have chosen, because there is no corpus, +and the encodings on the six questions page are the site's own rendering of the +note's example. Whether that rendering is the shape the note intends is the +correction worth the most. + ## The request that has not been sent Recorded here so that when it goes out, what was asked is on the record too. The diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/README.md b/docs/analysis/2026-08-automating-technical-hardening-guidance/README.md index 57b7013..002a234 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/README.md +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/README.md @@ -5,10 +5,11 @@ Assessments. Three organizations have published working OSCAL content that answers the same question three different ways: **where does technical hardening guidance live in -OSCAL, and how does an automated check attach to it?** 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. +OSCAL, and how does an automated check attach to it?** A concept note proposes a +fourth way. This site puts the four side by side against the same six questions, +writes the same two rules out in all four shapes so that the only thing differing +between the columns is the modelling, and names the join key that makes each one +work. **The JSON on the question pages is ours.** The three groups ship content for different products, so quoting what each one published would set a certificate @@ -23,6 +24,17 @@ document with its contents counted from the file rather than described. Extracts at declared pointers into the published files are still carried where a claim rests on one, and they are still re-derived on every build. +**The fourth approach has no corpus.** Profile-first comes from a concept note, +*Executable Assessment Methods*, held at +`examples/profile-first/executable-assessment-methods.md` and linked from the +artifacts page, which is the one document that approach has. Its column on the +six questions page is the site's own encoding of the shape the note proposes, +written from the note's worked example; its cells declare no extracts, because +there is nothing to extract from; and its status annotation says so on every +card. Every check that reads a corpus skips it by name, and every check that +holds the approaches to one shape holds it to the same shape. The namespace on +its props is the note's own placeholder, carried as the note wrote it. + Published hardening guidance from four publishers was read as input: CIS, DISA, CISA and AWS. The introduction tabulates it one row per benchmark or guide, in a disclosure that is closed until it is wanted, and every row carries what stands @@ -59,13 +71,14 @@ reader prices it. ## Status -Ready to publish, not published. Eight pages, all built: `index.html`, -`six-questions.html`, the three approach pages, `scenario.html`, `questions.html` +Ready to publish, not published. Nine pages, all built: `index.html`, +`six-questions.html`, the four approach pages, `scenario.html`, `questions.html` and `oscal-artifacts.html`. What remains is not a build step: - **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. This is stated on the site rather than left implicit. + to the publishers of the three bodies of content or to the author of the + concept note, so none has been received and nobody has declined. This is + stated on the site rather than left implicit. - Four checks cannot run without network and are skipped locally. They run in CI. - Two more skip wherever the pre-read and the position paper are not on disk. Both are Word documents, both live beside the site rather than in it, and @@ -157,7 +170,7 @@ python tools/verify.py --matrix every matrix cell resolves and is classif python tools/verify.py --diagrams structure, colour, geometry, join literals python tools/verify.py --css colour lives only in the token block python tools/verify.py --links every internal link, anchor and path -python tools/verify.py --budget equal budget across the three approach pages +python tools/verify.py --budget equal budget across the four approach pages python tools/verify.py --a11y contrast, then axe-core over every page python tools/verify.py --bundle the offline fallback matches data/ python tools/verify.py --questions the reproduced material matches its source @@ -194,11 +207,11 @@ recomputed from the corpora rather than stated. ``` python tools/extract.py # rebuild data/snippets and data/provenance.json -python tools/pattern_examples.py # write the two rules in all three shapes -python tools/oscal_artifacts.py # inventory what the three groups have published +python tools/pattern_examples.py # write the two rules in all four shapes +python tools/oscal_artifacts.py # inventory what each approach has published python tools/sources_files.py # rebuild data/source-files.json from sources/ python tools/diagrams.py # rebuild every published SVG in assets/diagrams -python tools/approach_pages.py # rebuild the three approach pages +python tools/approach_pages.py # rebuild the four approach pages python tools/scenario_page.py # rebuild the worked scenario page python tools/bundle.py # rebuild the offline fallback python tools/verify.py --all # prove the site says what the files say @@ -248,13 +261,15 @@ data/ snippets/ 29 files, one per extract, never edited by hand schema-evidence/ 8 verbatim OSCAL 1.2.1 schema fragments with their constraints six-questions.json the six questions and the answer matrix, the central claim set - pattern-examples.json the two rules, written in all three shapes. Ours - oscal-artifacts.json what each of the three groups has published, counted + pattern-examples.json the two rules, written in all four shapes. Ours + oscal-artifacts.json what each approach has published, counted, and a note + for the one that has published nothing criteria.json the fifteen evaluation criteria, verbatim from the pre-read criteria-fill.json the forty-five cells, answered from the files sources.json the guidance read as input, one row per benchmark source-files.json every file under sources/, generated, with size and type - views.json the three views of what a rule is + views.json the three views of what a rule is, and which approaches + hold each; two hold the first glossary.json the vocabulary, including the terms the group has not settled. Rendered as term cards in place; there is no glossary page @@ -269,7 +284,7 @@ tools/ oscal_artifacts.py builds data/oscal-artifacts.json from the three corpora sources_files.py builds data/source-files.json from sources/ diagrams.py builds the published SVGs in assets/diagrams from data/ - approach_pages.py builds the three approach pages from one template + approach_pages.py builds the four approach pages from one template scenario_page.py builds scenario.html, the one page that carries figures bundle.py builds assets/bundle.js, the offline fallback svgrender.py rasterises the diagrams for the grayscale contact sheet @@ -282,12 +297,12 @@ Eight of those are generators and the files they produce must not be edited by hand: `data/snippets/*.json` and `data/provenance.json`, `data/pattern-examples.json`, `data/oscal-artifacts.json`, `data/source-files.json`, `assets/diagrams/*.svg`, `data/criteria-fill.json`, the -three approach pages, and `assets/bundle.js`. The workflow regenerates all of +four approach pages, and `assets/bundle.js`. The workflow regenerates all of them and fails if the result differs from what was committed. -`tools/diagrams.py` builds 19 diagrams and writes 9. The other 10, the base layer -map, the three stakeholder variants and the rest, were only ever on a component -gallery that has been removed. The builders are kept, because the drawing code +`tools/diagrams.py` builds 20 diagrams and writes 10. The other 10, the base +layer map, the four stakeholder variants and the rest, were only ever on a +component gallery that has been removed. The builders are kept, because the drawing code belongs in one place, and the `PUBLISHED` constant at the foot of the file is the list of what reaches `assets/diagrams/`. Add a name there to publish one. @@ -311,11 +326,11 @@ methodology page that has since been removed. The load-bearing ones: that page weighs nothing and states no position. Every other page is held to the rule. - **Equal budget is enforced by construction**, not by judgement. One generator - writes the three approach pages and refuses to write them if their word counts + writes the four approach pages and refuses to write them if their word counts differ by more than ten per cent. - **Non-verbal encoding counts as editorializing.** A badge, a hollow cell or a hatch fill argues in a channel a word count cannot see, so every annotation type - applies to all three approaches or to none. + applies to all four approaches or to none. - **Consequences, not verdicts.** State the cost; let the reader price it. - **Every figure carries its denominator**, and every figure is recomputed from the corpora on every build. @@ -365,12 +380,22 @@ A criterion cannot be added here. Editorial rule 4 forbids the site from authoring evaluation criteria, so a sixteenth goes to the working group and this site follows. -## Adding a fourth approach +## Adding an approach -The site is built so that this is a data change and a page, not a rewrite. +The site is built so that this is a data change and a page, not a rewrite. The +fourth approach was added this way, from a concept note rather than a corpus, +and the places that had to learn a fourth are recorded in `BUILD-LOG.md` under +that session: one entry in every per-approach data file, a fourth column in the +encoding generator, a fourth hue at the same lightness, a fourth marker shape, +and the checks that counted to three. 1. **Add the corpus.** Put the published files where `corpora_root` in - `tools/manifest.yaml` can reach them. + `tools/manifest.yaml` can reach them. An approach with no corpus, one that + exists as a proposal, skips this step and the next: its cells declare no + extracts, its status annotation says what it is, its `tools/verify.py` + entry goes into `UNPUBLISHED`, and the one document it does have goes under + `examples//` and is named in `UNPUBLISHED` in + `tools/oscal_artifacts.py` so the inventory page links it. 2. **Declare the extracts.** Add manifest entries with a source file, an RFC 6901 pointer, and the question each one illustrates. Run `python tools/extract.py`. 3. **Add the approach to `data/six-questions.json`.** One entry under `approaches` with @@ -379,7 +404,7 @@ The site is built so that this is a data change and a page, not a rewrite. annotation. Then one `matrix` cell for each of the seven question rows, each with a state, a note that becomes its tooltip, and the extracts that evidence it. An unanswered cell must say which of the three kinds of unanswered it is. -4. **Write the two rules in your shape.** Add a fourth column to +4. **Write the two rules in your shape.** Add a column to `tools/pattern_examples.py`: the same two rules, in the same order, for every question row the approach answers, each block naming the OSCAL construct that carries it and carrying your own namespace on any property that needs one. A @@ -398,12 +423,18 @@ cell, `--example` will reject a column whose rules do not match the others, `--budget` will reject an unequal page, and `--criteria` will reject a criteria table that does not answer all fifteen for the new approach. -Two more things. The inventory page needs a fourth entry in the `PUBLISHERS` list -in `tools/oscal_artifacts.py`, naming the corpus directory and the option letter; +Two more things. The inventory page needs an entry in the `PUBLISHERS` list in +`tools/oscal_artifacts.py`, naming the corpus directory and the option letter; everything else on that page is counted off the files and nothing about it is described by hand. And `sources/` lists the hardening guidance read as input, not the OSCAL written from it, so a new corpus does not go there. +The checks that count approaches read the count from `data/six-questions.json`, +with four exceptions that name them: the option-letter order in +`tools/verify.py`, `tools/pagecheck.js` and `assets/site.js`, the approach list +in `tools/diagrams.py` with its marker shape, and the approach colour tokens in +`assets/site.css`, which `--a11y` holds to one lightness. + ## License CC BY 4.0. See `LICENSE`. The site's own text, diagrams and encodings are under diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/analysis.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/analysis.json index 09072b0..83fc495 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/analysis.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/analysis.json @@ -6,23 +6,25 @@ "opened": "2026-08-12", "concluded": null, "forum": "OSCAL Foundation Technical Focus Group on Automated Assessments", - "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.", + "summary": "Three organizations have published working OSCAL content that answers the same question three different ways, and a concept note proposes a fourth. This site puts the four side by side against the same six questions, writes the same two rules out in all four shapes so that the only thing differing between the columns is the modelling, and names the join key that makes each one work.", "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" } + { "id": "c", "name": "Assessment-first", "path": "assessment-first.html" }, + { "id": "d", "name": "Profile-first", "path": "profile-first.html" } ], "recommendation": null, "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.", + "makesRecommendationNote": "By design, not because the effort is unfinished. The site states four 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.", "supersedes": null, "supersededBy": null, "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." + "Proponent review has not happened. No request for corrections has been sent to the publishers of the three bodies of content or to the author of the concept note, so none has been received and nobody has declined.", + "The fourth approach has no corpus. Its column rests on the concept note alone, so the checks that read a corpus skip it by name, and the OSCAL artifacts inventory for it is a note and a link rather than a count." ], "corpora": { diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/assessment-first.html b/docs/analysis/2026-08-automating-technical-hardening-guidance/assessment-first.html index 7dce04a..81803af 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/assessment-first.html +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/assessment-first.html @@ -40,6 +40,7 @@
  • Catalog-first
  • Component-first
  • Assessment-first
  • +
  • Profile-first
  • Open questions
  • OSCAL artifacts
  • @@ -164,8 +165,8 @@

    3. Tracing rules and checks from implementation to assessment

    nothing filled. One footer, one place. -->
    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 5e4227a..0e8cb2b 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: 73. Generated from data/ at 2026-08-25T15:35:51+00:00. + * Files: 75. Generated from data/ at 2026-09-09T13:29:30+00:00. */ -window.TFGBundle = {"assets/diagrams/710-scenario-assessment.svg":"\n One system, three hardening guides: the file set for the assessment first approach\n A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 11 files in total, across 5 of the seven models. 1 catalog file, the framework only, named NIST 800-53. 1 profile file, the High baseline, named 800-53 High. 0 mapping-collection files, none, the tie is on the activity. 0 component-definition files, none, the engines are named inside each plan. 1 system-security-plan file, one, answering 370 controls, named System SSP. 4 assessment-plan files, one for the framework assessment, one per guide, named 800-53 AP, CIS Ubuntu AP, DISA PgSQL AP, CISA SCuBA AP. 4 assessment-results files, one per plan, because a result names exactly one plan, named 800-53 AR, CIS Ubuntu AR, DISA PgSQL AR, CISA SCuBA AR. A model this approach does not use is drawn hollow and labelled none, so the absence is as visible as the presence. The tile is the same size in all three figures, so the area of ink is the comparison. The plan of record answers 370 controls, and none of the three guides enters it.\n \n \n11 files, across 5 of the seven models\nEach guide becomes an assessment plan. The framework side is unchanged, and each plan produces a result\nof its own.\n\nCONTROL LAYER\n\ncatalog\n\n\nNIST\n800-53\n1 file\nthe framework only\n\nprofile\n\n\n800-53\nHigh\n1 file\nthe High baseline\n\nmapping-collection\n\n0 files\nnone, the tie is on the\nactivity\n\nIMPLEMENTATION LAYER\n\ncomponent-definition\n\n0 files\nnone, the engines are named inside each plan\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, answering 370 controls\n\nASSESSMENT LAYER\n\nassessment-plan\n\n\n800-53 AP\n\n\nCIS Ubuntu\nAP\n\n\nDISA PgSQL\nAP\n\n\nCISA SCuBA\nAP\n4 files\none for the framework assessment, one per\nguide\n\nassessment-results\n\n\n800-53 AR\n\n\nCIS Ubuntu\nAR\n\n\nDISA PgSQL\nAR\n\n\nCISA SCuBA\nAR\n4 files\none per plan, because a result names exactly\none plan\n\nThe plan of record answers 370 controls, and none of the three guides enters it\n\n","assets/diagrams/710-scenario-catalog.svg":"\n One system, three hardening guides: the file set for the catalog first approach\n A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 18 files in total, across all seven models. 4 catalog files, one for the framework, one for each guide, named NIST 800-53, CIS Ubuntu, DISA PgSQL, CISA SCuBA. 5 profile files, one selection per catalog, and one to merge them, named 800-53 High, CIS Ubuntu, DISA PgSQL, CISA SCuBA, Org merged. 3 mapping-collection files, one per guide, tying its controls to the framework, named CIS to 800-53, STIG to 800-53, SCuBA to 800-53. 3 component-definition files, one per technology, carrying the check components, named Ubuntu checks (software), PgSQL checks (software), M365 checks (software). 1 system-security-plan file, one, answering 917 controls, named System SSP. 1 assessment-plan file, one, named System AP. 1 assessment-results file, one, named System AR. A model this approach does not use is drawn hollow and labelled none, so the absence is as visible as the presence. The tile is the same size in all three figures, so the area of ink is the comparison. The plan of record answers 917 controls, 370 from the framework and 547 from the guides.\n \n \n18 files, across all seven models\nEach guide is published as a catalog, selected by a profile of its own, and tied back to the framework\nby a mapping collection. The plan of record answers every control in the merged set.\n\nCONTROL LAYER\n\ncatalog\n\n\nNIST\n800-53\n\n\nCIS Ubuntu\n\n\nDISA PgSQL\n\n\nCISA SCuBA\n4 files\none for the framework, one for\neach guide\n\nprofile\n\n\n800-53\nHigh\n\n\nCIS Ubuntu\n\n\nDISA PgSQL\n\n\nCISA SCuBA\n\n\nOrg merged\n5 files\none selection per catalog, and\none to merge them\n\nmapping-collection\n\n\nCIS to\n800-53\n\n\nSTIG to\n800-53\n\n\nSCuBA to\n800-53\n3 files\none per guide, tying its\ncontrols to the framework\n\nIMPLEMENTATION LAYER\n\ncomponent-definition\n\n\nUbuntu\nchecks\nsoftware\n\n\nPgSQL\nchecks\nsoftware\n\n\nM365\nchecks\nsoftware\n3 files\none per technology, carrying the check\ncomponents\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, answering 917 controls\n\nASSESSMENT LAYER\n\nassessment-plan\n\n\nSystem AP\n1 file\none\n\nassessment-results\n\n\nSystem AR\n1 file\none\n\nThe plan of record answers 917 controls, 370 from the framework and 547 from the guides\n\n","assets/diagrams/710-scenario-component.svg":"\n One system, three hardening guides: the file set for the component first approach\n A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 11 files in total, across 6 of the seven models. 1 catalog file, the framework only, named NIST 800-53. 1 profile file, the High baseline, named 800-53 High. 0 mapping-collection files, none, the tie is inside the component definition. 6 component-definition files, three products carrying 547 rules, three engines carrying the checks, named Ubuntu (software), PostgreSQL (software), Microsoft 365 (software), Ubuntu checks (validation), PgSQL checks (validation), M365 checks (validation). 1 system-security-plan file, one, answering 370 controls and carrying 547 rules, named System SSP. 1 assessment-plan file, one, named System AP. 1 assessment-results file, one, named System AR. A model this approach does not use is drawn hollow and labelled none, so the absence is as visible as the presence. The tile is the same size in all three figures, so the area of ink is the comparison. The plan of record answers 370 controls, and carries 547 desired-state rules inside its components.\n \n \n11 files, across 6 of the seven models\nEach guide becomes rules on the component it configures, and each engine that tests them becomes a\ncomponent of its own. The framework side is unchanged.\n\nCONTROL LAYER\n\ncatalog\n\n\nNIST\n800-53\n1 file\nthe framework only\n\nprofile\n\n\n800-53\nHigh\n1 file\nthe High baseline\n\nmapping-collection\n\n0 files\nnone, the tie is inside the\ncomponent definition\n\nIMPLEMENTATION LAYER\n\ncomponent-definition\n\n\nUbuntu\nsoftware\n\n\nPostgreSQL\nsoftware\n\n\nMicrosoft\n365\nsoftware\n\n\nUbuntu\nchecks\nvalidation\n\n\nPgSQL\nchecks\nvalidation\n\n\nM365\nchecks\nvalidation\n6 files\nthree products carrying 547 rules, three\nengines carrying the checks\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, answering 370 controls and carrying 547\nrules\n\nASSESSMENT LAYER\n\nassessment-plan\n\n\nSystem AP\n1 file\none\n\nassessment-results\n\n\nSystem AR\n1 file\none\n\nThe plan of record answers 370 controls, and carries 547 desired-state rules inside its\ncomponents\n\n","assets/diagrams/73-join-assessment.svg":"\n Assessment-first (Option C): the chain from the rule to the claim and the result\n A chain of 6 steps, each drawn as one row per relationship, with the field that holds the pointer on the left and the field it resolves to on the right. Step 1, rule to check, is made of 2 relationships. no field in the assessment-plan containment to activities[].steps[].uuid in the assessment-plan. steps[].props[name=check].value in the assessment-plan, which holds SV-270747r1066730_rule, name match to no field in the nothing. Step 2, rule to control, is made of 1 relationship. activities[].related-controls.control-selections[].include-controls[].control-id in the assessment-plan, which holds sc-28, reference to controls[].id in the catalog. Step 3, check to runtime, is made of 1 relationship. assessment-platforms[].uses-components[].component-uuid in the assessment-plan, which holds 56270516-2673-4d4c-8d4f-52e4107f968d, reference to assessment-assets.components[].uuid in the assessment-plan. Step 4, runtime to claim, is made of 1 relationship. import-ssp.href in the assessment-plan, which holds #d381c885-4851-4931-828c-29bbb24fbaa3, reference to back-matter.resources[].uuid in the assessment-plan. Step 5, runtime to result, is made of 1 relationship. observations[].subjects[].subject-uuid in the assessment-results, which holds 61b3ec99-dfbe-4997-8a66-6f2279edb84b, reference to activities[].uuid in the assessment-plan. Step 6, result to control, is made of 1 relationship. findings[].target.target-id in the assessment-results, which holds sc-28_obj, reference to controls[].parts[objective].id in the catalog. Every value is rule 1, data at rest, as the six questions page encodes it for this approach.\n \n \n1. Rule to Check\nassessment-planno field\nassessment-planactivities[].steps[].uuid333ddd0f-22da-4c18-8bc3-98e808746bca\n\ninside\nassessment-plansteps[].props[name=check].valueSV-270747r1066730_rule\nnothing in OSCALno field\n\nby name\n2. Rule to Control\nassessment-planactivities[].related-controls.control-selections[].include-controls[].control-idsc-28\ncatalogthe framework catalogcontrols[].idsc-28\n\nresolves\n3. Check to Runtime\n\nassessment-planassessment-platforms[].uses-components[].component-uuid56270516-2673-4d4c-8d4f-52e4107f968d\nassessment-planassessment-assets.components[].uuid\n\nresolves\n4. Runtime to Claim\n\nassessment-planimport-ssp.href#d381c885-4851-4931-828c-29bbb24fbaa3\nassessment-planback-matter.resources[].uuidd381c885-4851-4931-828c-29bbb24fbaa3\n\nresolves\n5. Runtime to Result\n\nassessment-resultsobservations[].subjects[].subject-uuid61b3ec99-dfbe-4997-8a66-6f2279edb84b\nassessment-planactivities[].uuid61b3ec99-dfbe-4997-8a66-6f2279edb84b\n\nresolves\n6. Result to Control\nassessment-resultsfindings[].target.target-idsc-28_obj\ncatalogcontrols[].parts[objective].id\n\nresolves\n\n\nLegend\n\na document, or the fragment of one that holds\nthe field\n\nthe value, as the six questions page encodes\nit\n\na reference: the schema knows it is an\nidentifier and it resolves\n\na name match: equal by convention, and no\nschema can check it\n\ncontainment: nothing resolves, the child is\ninside the parent\n\nthe runtime, which reads OSCAL, executes, and\nwrites OSCAL\nEvery value is rule 1, data at rest, as\ndata/pattern-examples.json encodes it for this\napproach. The table above is the same chain\nwithout the values.\n\n\n","assets/diagrams/73-join-catalog.svg":"\n Catalog-first (Option A): the chain from the rule to the claim and the result\n A chain of 5 steps, each drawn as one row per relationship, with the field that holds the pointer on the left and the field it resolves to on the right. Step 1, rule to check, is made of 2 relationships. parts[assessment-method].props.TechnicalControlId in the catalog, which holds SV-270747r1066730_rule, name match to components[].title in the component-definition. implemented-requirements[].control-id in the component-definition, which holds UBTU-24-600090, reference to controls[].id in the catalog. Step 2, rule to control, is made of 2 relationships. maps[].sources[].id-ref in the mapping-collection, which holds UBTU-24-600090, reference to controls[].id in the catalog. maps[].targets[].id-ref in the mapping-collection, which holds sc-28, reference to controls[].id in the catalog. Step 3, check to runtime, is made of 1 relationship. components[].props.ConfigRuleId in the component-definition, which holds SV_270747R1066730_RULE, no join to no field in the nothing. Step 4, runtime to claim, is made of 2 relationships. implemented-requirements[].control-id in the system-security-plan, which holds UBTU-24-600090, reference to controls[].id in the catalog. by-components[].component-uuid in the system-security-plan, which holds 534b356b-0de1-48d4-8536-5d41ed717456, reference to system-implementation.components[].uuid in the system-security-plan. Step 5, claim to result, is made of 2 relationships. findings[].target.target-id in the assessment-results, which holds UBTU-24-600090_smt, reference to statements[].statement-id in the system-security-plan. related-observations[].observation-uuid in the assessment-results, which holds 28e28d31-4428-4ff5-8c9e-ea1198dfb552, reference to observations[].uuid in the assessment-results. Every value is rule 1, data at rest, as the six questions page encodes it for this approach.\n \n \n1. Rule to Check\ncatalogparts[assessment-method].props.TechnicalControlIdSV-270747r1066730_rule\ncomponent-definitioncomponents[].titleSV-270747r1066730_rule\n\nby name\ncomponent-definitionimplemented-requirements[].control-idUBTU-24-600090\ncatalogcontrols[].idUBTU-24-600090\n\nresolves\n2. Rule to Control\nmapping-collectionmaps[].sources[].id-refUBTU-24-600090\ncatalogcontrols[].idUBTU-24-600090\n\nresolves\nmapping-collectionmaps[].targets[].id-refsc-28\ncatalogthe framework catalogcontrols[].idsc-28\n\nresolves\n3. Check to Runtime\n\ncomponent-definitioncomponents[].props.ConfigRuleIdSV_270747R1066730_RULE\nnothing in OSCALno field\n\n\nnothing to resolve\n4. Runtime to Claim\n\nsystem-security-planimplemented-requirements[].control-idUBTU-24-600090\ncatalogcontrols[].idUBTU-24-600090\n\nresolves\nsystem-security-planby-components[].component-uuid534b356b-0de1-48d4-8536-5d41ed717456\nsystem-security-plansystem-implementation.components[].uuid\n\nresolves\n5. Claim to Result\nassessment-resultsfindings[].target.target-idUBTU-24-600090_smt\nsystem-security-planstatements[].statement-idUBTU-24-600090_smt\n\nresolves\nassessment-resultsrelated-observations[].observation-uuid28e28d31-4428-4ff5-8c9e-ea1198dfb552\nassessment-resultsobservations[].uuid\n\nresolves\n\n\nLegend\n\na document, or the fragment of one that holds\nthe field\n\nthe value, as the six questions page encodes\nit\n\na reference: the schema knows it is an\nidentifier and it resolves\n\na name match: equal by convention, and no\nschema can check it\n\nno join: there is no field on the far side\n\nthe runtime, which reads OSCAL, executes, and\nwrites OSCAL\nEvery value is rule 1, data at rest, as\ndata/pattern-examples.json encodes it for this\napproach. The table above is the same chain\nwithout the values.\n\n\n","assets/diagrams/73-join-component.svg":"\n Component-first (Option B): the chain from the rule to the claim and the result\n A chain of 6 steps, each drawn as one row per relationship, with the field that holds the pointer on the left and the field it resolves to on the right. Step 1, rule to check, is made of 2 relationships. checks[].rule-id in the component-definition, which holds ubtu24_data_at_rest_encrypted, composite key to components[].rules[].id in the component-definition. checks[].target-component-uuid in the component-definition, which holds 5ca997b3-bb3e-4c7a-8969-69ed44577d47, composite key to components[].uuid in the component-definition. Step 2, rule to control, is made of 2 relationships. implemented-requirements[].implementing-rules[].rule-id in the component-definition, which holds ubtu24_data_at_rest_encrypted, reference to components[].rules[].id in the component-definition. implemented-requirements[].control-id in the component-definition, which holds sc-28, reference to controls[].id in the catalog. Step 3, check to runtime, is made of 1 relationship. no field in the component-definition containment to components[].uuid in the component-definition. Step 4, runtime to claim, is made of 2 relationships. by-components[].implementing-rules[].rule-id in the system-security-plan, which holds ubtu24_data_at_rest_encrypted, reference to components[].rules[].id in the component-definition. by-components[].component-uuid in the system-security-plan, which holds 534b356b-0de1-48d4-8536-5d41ed717456, reference to system-implementation.components[].uuid in the system-security-plan. Step 5, runtime to result, is made of 2 relationships. observations[].assessment-check-id in the assessment-results, which holds SV-270747r1066730_rule, reference to checks[].id in the component-definition. observations[].subjects[].subject-uuid in the assessment-results, which holds 06297a03-cae0-414b-8332-2fc882f81aa1, reference to system-implementation.inventory-items[].uuid in the system-security-plan. Step 6, result to control, is made of 1 relationship. no field in the assessment-results no join to no field in the catalog. Every value is rule 1, data at rest, as the six questions page encodes it for this approach.\n \n \n1. Rule to Check\ncomponent-definitionchecks[].rule-idubtu24_data_at_rest_encrypted\ncomponent-definitioncomponents[].rules[].idubtu24_data_at_rest_encrypted\n\nhalf of the key\ncomponent-definitionchecks[].target-component-uuid5ca997b3-bb3e-4c7a-8969-69ed44577d47\ncomponent-definitioncomponents[].uuid5ca997b3-bb3e-4c7a-8969-69ed44577d47\n\nhalf of the key\n2. Rule to Control\ncomponent-definitionimplemented-requirements[].implementing-rules[].rule-idubtu24_data_at_rest_encrypted\ncomponent-definitioncomponents[].rules[].idubtu24_data_at_rest_encrypted\n\nresolves\ncomponent-definitionimplemented-requirements[].control-idsc-28\ncatalogthe framework catalogcontrols[].idsc-28\n\nresolves\n3. Check to Runtime\n\ncomponent-definitionno field\ncomponent-definitionthe validation componentcomponents[].uuidb3c8813d-d479-450a-8178-fbbf846faccf\n\ninside\n4. Runtime to Claim\n\nsystem-security-planby-components[].implementing-rules[].rule-idubtu24_data_at_rest_encrypted\ncomponent-definitioncomponents[].rules[].idubtu24_data_at_rest_encrypted\n\nresolves\nsystem-security-planby-components[].component-uuid534b356b-0de1-48d4-8536-5d41ed717456\nsystem-security-plansystem-implementation.components[].uuid\n\nresolves\n5. Runtime to Result\n\nassessment-resultsobservations[].assessment-check-idSV-270747r1066730_rule\ncomponent-definitionchecks[].idSV-270747r1066730_rule\n\nresolves\nassessment-resultsobservations[].subjects[].subject-uuid06297a03-cae0-414b-8332-2fc882f81aa1\nsystem-security-plansystem-implementation.inventory-items[].uuid\n\nresolves\n6. Result to Control\nassessment-resultsno field\ncatalogno field\n\n\nnothing to resolve\n\n\nLegend\n\na document, or the fragment of one that holds\nthe field\n\nthe value, as the six questions page encodes\nit\n\na reference: the schema knows it is an\nidentifier and it resolves\n\ndrawn twice where the key is composite and\nboth halves have to match\n\ncontainment: nothing resolves, the child is\ninside the parent\n\nno join: there is no field on the far side\n\nthe runtime, which reads OSCAL, executes, and\nwrites OSCAL\nEvery value is rule 1, data at rest, as\ndata/pattern-examples.json encodes it for this\napproach. The table above is the same chain\nwithout the values.\n\n\n","assets/diagrams/75-stakeholders.svg":"\n One recommendation, three stakeholders, three paths\n One recommendation sits on the left. Three paths lead out of it, one for each stakeholder, and the three are drawn at the same size and weight because none is ranked above another. The publisher's path runs from a recommendation written once to a versioned, tailorable, citable publication. The implementer's path runs from desired state to a configuration engine to applied state. The assessor's path runs from a check to execution or examination to evidence to a finding. This is an organizing structure, not a thesis: all three needs are real and can be true at once, and the site's question is which questions each approach answers, for which stakeholder, and what it costs to fill the rest. No approach is marked on this drawing.\n \n \n\n\n\none\nrecommendation\nPUBLISHER\n\na recommendation\nwritten once\n\na versioned,\ntailorable,\ncitable publication\n\n\nIMPLEMENTER\n\ndesired state\n\na configuration\nengine\n\n\napplied state\n\n\nASSESSOR\n\na check\n\nexecution, or\nexamination\n\n\nevidence\n\n\na finding\n\n\n\n\n\n\n","assets/diagrams/76-satisfaction-6a-6b.svg":"\n One rule, two satisfaction assertions: the implementation claim and the assessment result\n One rule sits at the top and two paths lead out of it, side by side and drawn at the same size. On the left is question 6a, the implementation claim, which answers how the rule is satisfied. It lives in the system security plan and runs implemented-requirement, then statement, then by-component. It is narrative, it is standing design intent, it is asserted by the system owner, it is expressed per component, and it fails when the narrative is vague. On the right is question 6b, the assessment result, which answers whether the rule was satisfied, when, and on what. It lives in assessment results and runs observation, then finding, then objective-status. It is evidenced, it is a point in time, it is asserted by the assessor, it is expressed per subject of several types, and it fails when the evidence is stale or the subject is wrong. A table beneath the figure sets out those six differences in full. A rule carrying desired state has a binary satisfaction condition, while the implementation statement expects a narrative one, and conflating the two is the modelling error the figure exists to mark. Both can be populated from one rule without contradiction, and an approach that populates only one is not wrong; it is unfinished in a nameable place.\n \n \n\none rule\none requirement, one condition\n\n\n\n\n\n6a\nImplementation claim\n"how it is satisfied"\nsystem-security-plan\n\nimplemented-requirement\n\n\nstatement\n\n\nby-component\nnarrative . standing . per component\n\n\n\n6b\nAssessment result\n"whether it was satisfied"\nassessment-results\n\nobservation\n\n\nfinding\n\n\nobjective-status\nevidenced . point in time . per subject\nThe six differences, from plan section 2.1\n\n6a. Implementation claim\n6b. Assessment result\nquestion answered\nHow is this satisfied?\nWas it satisfied, when, on what?\n\nwho asserts it\nthe system owner\nthe assessor\n\ntime\nstanding design intent\na point in time\n\nform\nnarrative, arguable\nbinary or graded, evidenced\n\ngranularity\nper component\nper subject, of several types\n\nfails when\nthe narrative is vague\nthe evidence is stale, or the subject\nis wrong\n\n\n","data/corpus-stats.json":{"cited_from_position_paper":{"benchmark_requirements":563,"combined":867,"note":"These three figures are NOT computed from the corpora. They come from Technology_Specific_Hardening_Guidance_in_OSCAL.docx, an Easy Dynamics position paper, and must be attributed as such at every appearance per editorial rule 10.","regulatory_controls":304,"source":"Technology_Specific_Hardening_Guidance_in_OSCAL.docx, Easy Dynamics position paper"},"generated_from":"tfg-automated-assessments","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 assessment plan files","value":5},{"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","value":11},{"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","value":0},{"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?","raised_by":["Brian Ruf","Anca Sailer"],"slots":["1","3","6a","6b"]},{"name":"Normativity","number":2,"question":"Can the artifact express must versus may? Can an auditor treat it as binding?","raised_by":["Brian Ruf"],"slots":["1"]},{"name":"Requirement level","number":3,"question":"Can shall, should and may be represented at all?","raised_by":["Raised in discussion"],"slots":["1"]},{"name":"Hierarchy support","number":4,"question":"Does the model natively carry deep benchmark hierarchies?","raised_by":["CIS, via Anca Sailer"],"slots":["1"]},{"name":"Tailoring","number":5,"question":"Can an organization select, exclude and parameterize at scale?","raised_by":["Position paper"],"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?","raised_by":["Pirooz Javan"],"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?","raised_by":["Position paper"],"slots":["6a"]},{"name":"Response fidelity","number":8,"question":"Can a system owner answer per host or inventory item, or only per component?","raised_by":["Pirooz Javan"],"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?","raised_by":["Vikas Agarwal"],"slots":["1","2","3","5","6b"]},{"name":"Schema change cost","number":10,"question":"How many models change, and what is the realistic ratification timeline?","raised_by":["Fritz Kunstler"],"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?","raised_by":["Position paper"],"slots":["1"]},{"name":"Cross-framework use","number":12,"question":"Does this help someone operating under SOC 2, ISO and FedRAMP at the same time?","raised_by":["Pirooz Javan"],"slots":["2"]},{"name":"Inspectability","number":13,"question":"Can an operator see what a check does before running it on their systems?","raised_by":["Raised in discussion"],"slots":["3"]},{"name":"Prop dependence","number":14,"question":"How much meaning lives in namespaced props rather than core schema?","raised_by":["Brian Ruf"],"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?","raised_by":["All"],"slots":["1","2","3","4","5","6a","6b"]}],"note":"The fifteen evaluation criteria, verbatim from section 6 of the working group pre-read. The site authors none of them. The raised_by field is retained as provenance and is NOT rendered: per the Gate 7 decision, no personal name appears on any page.","source":"Hardening-Guidance-Options-Comparison.docx, Section 6, Draft evaluation criteria","source_status":"Offered for the group to ratify, amend, or reject. Reproduced unchanged."},"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":309023,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","sha256":"d69fd8b49feb6cf83de9cf00ba0c1ee1068f8afb7a4591116ab0b0beb86b0550"},{"approach":"assessment-first","bytes":314033,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-maester.json","sha256":"49d218b196333445dd67178dd58aba441fc596a28d2221c1c724d8eba460ee57"},{"approach":"assessment-first","bytes":291731,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","sha256":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d"},{"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":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":1940350,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","sha256":"4bb6d17f71a90122b0a2dbfaa560a5e6f80d57fdeaeb3d5c5288c79f5764e329"},{"approach":"assessment-first","bytes":1858871,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","sha256":"f5f821b671f8494ef155c6c2bcf5e17ae4792fcf200d1115a4c596caa2d03630"},{"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/main/"},"note":"The published OSCAL held in this repository, copied from the corpora by tools/copy_examples.py so the inventory can link to a document rather than only count it. Catalog-first is not here: it is published in a public repository and is linked there instead."},"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":"69754a8b9eaca4d372faed1e23d33fc89b524d09b3569e5fbe06110c9d749696","catalog-first":"f2381215aa6af548dca3cb5c59fc8d985964db349332454ffdab843069c38e56","component-first":"fd739ade4dd4568f7cac3dec242a5630a67feeef85ba13d70429ce8e6618df24"},"written_by":"tools/approach_pages.py"},"data/glossary.json":{"note":"The site's vocabulary. Every OSCAL term used anywhere on the site is defined here once, and every first use links back. The 'rule' entry exists because the word carries three incompatible meanings in this working group and nobody has fixed them in writing.","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, and a position paper"},{"usage":"Colloquially, the check code itself","who":"Used loosely across the working group, and flagged in the record by its own author"},{"usage":"An AWS Config rule: a deployable resource with its own parameters","who":"AWS Config, the product"}],"see_also":["check","control","desired state","requirement level"],"site_usage":"One technical requirement or recommendation, at a granularity finer than a control, without any claim about whether it is binding. This is a working definition adopted so that three comparable pages can be written. It is not a position on which view is correct.","status":"contested","term":"rule"},{"other_usages":[],"see_also":["rule","validation component","assessment platform"],"settled_note":"The separation of rule from check is recorded as settled item 5 in the pre-read. The stated reason is schema flexibility rather than semantics.","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, on the grounds that a vendor describes what can be configured rather than what must be","who":"Catalog-first, Option A"}],"see_also":["actual state","rule","implementation claim"],"site_usage":"The configuration a rule prescribes. Distinct from actual state, which is what the system currently has.","status":"contested","term":"desired state"},{"other_usages":[],"see_also":["desired state","assessment result"],"site_usage":"The configuration a system currently has, as observed. Distinct from desired state, which is what a rule prescribes.","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":"The link from a rule to the regulatory control it serves. Optional by design: a rule may serve several controls, one, or none. Without it you can record an observation but not a finding.","status":"settled","term":"link to a control"},{"other_usages":[{"usage":"Hardening guidance, used interchangeably","who":"General usage in the group"}],"see_also":["rule","hardening guidance"],"site_usage":"A published set of technology-specific hardening guidance. CIS Benchmarks, DISA STIGs, CISA SCuBA baselines, and vendor hardening guides.","status":"settled","term":"benchmark"},{"other_usages":[],"see_also":["benchmark","rule"],"site_usage":"Synonym for benchmark as used on this site. Technology-specific guidance on how to configure a product securely.","status":"settled","term":"hardening guidance"},{"other_usages":[],"see_also":["rule","normativity"],"site_usage":"Whether a statement is a shall, a should, or a may. OSCAL has no field for it. The pre-read's criterion 3 records it as absent from OSCAL entirely, an orthogonal gap affecting every option. Because there is no direct channel, location has become the proxy for expressing it.","status":"not-established","term":"requirement level"},{"other_usages":[],"see_also":["requirement level","rule"],"site_usage":"Whether an artifact expresses something binding that an auditor can hold a system to. The question underneath the location debate.","status":"contested","term":"normativity"},{"external_link":"https://github.com/OSCAL-Foundation/Component-Definition-Focus-Group/discussions/2","other_usages":[],"see_also":[],"set_aside":true,"site_usage":"A Component Definition construct that groups components and carries its own control-implementations, expressing joint satisfaction. Whether it should also exist in the SSP, or be removed, is an open question in the Component Definition Focus Group. The site notes it and takes no position.","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, Option B, component-rules.md"},{"usage":"A component enumerating the compliance frameworks a service has been validated against.","who":"Catalog-first, Option A, docs/COMPONENTS.md, under Future Considerations and not shipped"}],"see_also":["check","component"],"site_usage":"Two incompatible senses are in use and the site always says which one it means.","status":"contested","term":"validation component"},{"not_established_note":"Evidence register item 8: agreed on 17 July to be posted to the NIST OSCAL team. Not established whether posted; no response in the record.","other_usages":[],"see_also":["assessment asset","component","actor"],"site_usage":"In OSCAL, an element of assessment-assets that may reference components via uses-components. The authoritative distinction between an assessment platform, an assessment asset and a component has never been established.","status":"not-established","term":"assessment platform"},{"not_established_note":"Evidence register item 8.","other_usages":[],"see_also":["assessment platform","component","actor"],"site_usage":"In OSCAL, the assessment-assets container holding components and assessment-platforms. Its relationship to the two is not authoritatively defined.","status":"not-established","term":"assessment asset"},{"not_established_note":"Evidence register item 8, plus the unresolved component granularity question recorded against Option B.","other_usages":[],"see_also":["assessment platform","assessment asset","validation component"],"site_usage":"A part of a system. Used across the Component Definition, SSP, Assessment Plan and Assessment Results models with related but not identical meanings. Its boundary against assessment platform and assessment asset is not established, and neither is its granularity: whether a single config rule is a component, or the policy engine is.","status":"not-established","term":"component"},{"not_established_note":"Evidence register item 8: which of these constructs names the thing that runs a check has never been authoritatively established. The site inventories what each approach uses and does not resolve it.","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 site's name for question 5, what performs the check: whatever or whoever performs a check. OSCAL has no single construct for it. The word is the site's own label, adopted because naming the question after any one of the available constructs would have picked a side in the question below.","status":"not-established","term":"actor"},{"other_usages":[],"see_also":["assessment result","system security plan"],"site_usage":"An assertion by the system owner of how a control is satisfied. Standing design intent, narrative, arguable, made per component. Lives in the SSP as implemented-requirement, statement and by-component. Question 6a, how the system claims it meets the rule.","status":"settled","term":"implementation claim"},{"other_usages":[],"see_also":["implementation claim","observation","finding"],"site_usage":"An assertion by the assessor of whether a control was satisfied, when, and on what. A point in time, evidenced, binary or graded, made per subject. Lives in the AR as observation, finding and status. Question 6b, how an assessment records the outcome.","status":"settled","term":"assessment result"},{"other_usages":[],"see_also":["finding","assessment result","link to a control"],"site_usage":"An AR element recording something that was seen. Requires only uuid, description, methods and collected, and carries no reference to a control. Available whether or not a rule has a link to a control.","status":"settled","term":"observation"},{"other_usages":[],"see_also":["observation","link to a control","assessment result"],"site_usage":"An AR element recording a conclusion about whether an objective is satisfied. Requires a target whose type is closed to statement-id or objective-id, both control-derived. Unavailable to a rule with no link to a control.","status":"settled","term":"finding"},{"other_usages":[],"see_also":["link to a control","catalog"],"site_usage":"An OSCAL model, GA since 1.2, describing how one collection of controls relates to another. The only native mechanism for a third party to add a link to a control after publication. Its mapping-item type is closed to control and statement, so it reaches only rules that are modelled as controls.","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 element of an assessment plan's local-definitions, containing steps. The group has never defined what distinguishes an activity from a step; the question was asked three separate times on 19 June and not answered.","status":"not-established","term":"activity"},{"other_usages":[],"see_also":["activity","assessment plan"],"site_usage":"A child of an activity in an assessment plan. See the activity entry: the boundary between the two is not established.","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 the three stakeholders. Writes a requirement or recommendation once so many organizations can version, tailor and cite it, knowing nothing about any particular system.","status":"settled","term":"publisher"},{"other_usages":[],"see_also":["publisher","assessor","desired state"],"site_usage":"One of the three stakeholders. Wants that statement as desired state, in a form a configuration engine can apply.","status":"settled","term":"implementer"},{"other_usages":[],"see_also":["publisher","implementer","check"],"site_usage":"One of the three stakeholders. Wants a check they can run, or evidence dense enough to reach the same conclusion by reading.","status":"settled","term":"assessor"}]},"data/joins.json":{"approaches":{"assessment-first":{"hops":[{"from":"rule","how":"containment","note":"The check is the first step, so nothing has to match. The step then names a check that resolves 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 tie sits on the activity, so there is no second document and no second identifier to keep in step.","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 plan names its platforms once, for every activity, so it cannot say which engine ran which 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":"One pointer for the whole plan. Where no plan of record exists the same 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 observation points back at the activity that ran. The thing observed is the thing planned.","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 the control objective, so a result reads against the framework with no 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 rule is an activity in the plan that assesses it, so it is introduced in the assessment layer and does not enter the implementation layer at all. Every step below starts from that uuid.","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}},"catalog-first":{"hops":[{"from":"rule","how":"name-match","note":"Two ties, opposite ways. The control names its check by title, which no schema can check; the check names its control by id, which resolves.","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 document of its own, written after both catalogs and by someone who owns neither.","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":"The prop names the rule the engine runs. The engine itself is nowhere in the content.","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 is against a component, not a host. A by-component takes no subject.","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 statement in the plan of record, which is what makes it an answer 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 rule is a control in a product catalog, in the same model and the same shape a regulatory control has. Every step below starts from that id.","slot":"1","value":"UBTU-24-600090"}},"component-first":{"hops":[{"from":"rule","how":"composite","note":"Both halves of the key sit on the check side. A rule id is unique only inside the component that declares it.","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":"Both sides in one document. The control implementation already ties component to control; naming the rule inside it is the proposal.","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 checks are inside the component that runs them. A second engine is a second 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 claim names the rule it rests on, so a reader gets from claim to check without leaving OSCAL.","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 names the check and the host, so two machines in one boundary can disagree and both be recorded.","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 result never states the control. It carries observations and no findings, so there is no status to hold one.","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 rule is a first-class entry on the component it configures, so it is introduced inside the document that describes the thing being hardened. Every step below starts from that id.","slot":"1","value":"ubtu24_data_at_rest_encrypted"}}},"how":[{"key":"containment","label":"Containment","meaning":"One is inside the other, so there is no key to match and nothing to dereference."},{"key":"reference","label":"Reference","meaning":"A field holds an identifier the schema knows is an identifier, and it resolves."},{"key":"name-match","label":"Name match","meaning":"Two strings are equal by convention. It holds where the two agree and breaks silently where they do not, and no schema can check it."},{"key":"composite","label":"Composite key","meaning":"Two fields have to match together. Either one alone resolves to the wrong thing or to nothing."},{"key":"none","label":"No join","meaning":"There is no field on either side. The relation has to be recovered by walking through something else, or it is simply not there."}],"intro":"The chain starts where the rule is introduced and runs to the claim and the result. What a step costs is how many relationships it is made of and how each one resolves.","note":"The six questions are answered one at a time, which hides the thing that decides whether the set works: what joins one answer to the next. This is the chain from the moment the rule is introduced to the moment something records that it was met, with every foreign key and the primary key it resolves to. Every literal is one of the two running rules as the six questions page encodes it, so the three chains can be read against each other; tools/verify.py fails the build if a value here is not in that encoding.","stages":[{"key":"rule","label":"Rule","meaning":"where the rule is introduced","slot":"1"},{"key":"control","label":"Control","meaning":"the regulation it serves","slot":"2"},{"key":"check","label":"Check","meaning":"how it is tested","slot":"3"},{"key":"runtime","label":"Runtime","meaning":"what executes the check","slot":"5"},{"key":"claim","label":"Claim","meaning":"the system's statement that it holds","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":"What joins one answer to the next"},"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/main/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/main/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/main/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/main/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/main/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":309023,"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":314033,"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":291731,"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":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":1940350,"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":1858871,"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}}]},"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":{"corpora_root":"../../tfg-automated-assessments","generated_at":"2026-08-22T18:46:12+00:00","snippet_count":34,"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-08-22T17:17:36+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":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","sha256_of_content":"60c8183fb14d09b5f27513b84f394bf8a48670eadaf2f73fd834bc7300011240","sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+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":"49d218b196333445dd67178dd58aba441fc596a28d2221c1c724d8eba460ee57","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-08-22T17:17:36+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":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"01c9afa2b4ee716f8534f4a2f12777d7202d741c06a7d5182619ca8f3afbc3fe","sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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":1084,"extracted_at":"2026-08-22T17:17:36+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"c07765f9cca980bb8a30cfec768b885b607686df348a53618ab6099994e9a6e7","sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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":14934,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-rules-md","language":"markdown","pointer":"$","sha256_of_content":"799c42a95dae88268f20e09566342953a98c580bdda0cadf5197ebf4026d5e31","sha256_of_source_file":"630c45450f3cea476cd9a7df7da1f49e22f854832907521656191714eb9bd57c","slot":"meta","source":"IBM/Automated-assessment.md","title":"IBM's proposed rule and check assemblies"},{"approach":"component-first","bytes":410,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-open-questions","language":"markdown","pointer":"$","sha256_of_content":"0a03c3d3f2910ae28141c1a2de1771455102cf284bfb78a790e88a82f3765eaa","sha256_of_source_file":"630c45450f3cea476cd9a7df7da1f49e22f854832907521656191714eb9bd57c","slot":"meta","source":"IBM/Automated-assessment.md","title":"IBM's open questions"},{"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"}]},"data/questions.json":{"intro":"Nothing here is a proposal. Where the site has a fact that bears on a question, the fact is stated and the question is left open. Most of what is unsettled is about OSCAL rather than about any one approach, which is why the first section is the longest.","note":"The open questions, in four sections: what is unsettled about OSCAL itself, then what is unsettled about each approach. Each is one line with the reasoning behind it. Questions reproduced from a source document keep that document's wording, including its errors, and are marked with where they came from, because rewriting someone else's question is a way of answering it.","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":"Asked on 20 March and never closed. Two answers are on the record, that XCCDF is obsolete and that a checklist item is not a control, and neither settled it. If the answer is that OSCAL should reference XCCDF rather than restate it, every approach on this site changes shape."},{"id":"rule-metadata","q":"Where does the metadata that describes a rule go?","why":"Every STIG rule carries a severity and a weight; every CIS recommendation carries a rationale and says whether its check is automated or manual. No released OSCAL model has a field for any of them, so AWS carries severity as a namespaced property on all 452 of its controls and the STIG conversion carries it in DISA's. Which of these belong to a rule, and whether the answer is a field, a shared namespace or a property per publisher, is unasked."},{"id":"remediation","q":"Where does remediation land?","why":"194 of 194 STIG rules ship a fix and 312 of 312 CIS recommendations ship a remediation, and no approach has a field for it. Catalog-first links out to documentation on all 452 controls, assessment-first writes a second step marked remediate, component-first does not carry it. OSCAL's own remediation lives in the plan of action and milestones, which answers what to do about this finding rather than how anyone fixes this condition."}]},{"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":"The working assumption is that a system holds one plan of record answering a profile that merges every catalog it is held to. What is being seen in practice is one plan of record per catalog. The two are not a matter of taste: they produce different file counts, a different place for a response to live, and a different answer to whether a benchmark outcome sits beside a regulatory one. The worked scenario on this site assumes convergence, which is why its figure is 18 files."},{"id":"requirement-level","q":"If OSCAL gained a field for requirement level, how much of this disagreement would be left?","why":"The pre-read's criterion 3 records that shall, should and may cannot be expressed in OSCAL at all, so placement is the only channel left for asserting that something is required. This approach is placement: a benchmark's recommendations become controls beside a framework's controls in one merged profile, and nothing on either says which is a shall and which is a may. Nobody has been asked how much of the disagreement would survive the field."},{"id":"control-type","q":"Should a control declare its type, so a regulatory control and a technical hardening control can be told apart?","why":"Once hardening guidance is published as a catalog, both kinds sit in the same merged profile and are answered in the same plan of record. Nothing on a control says which of the two it is, so a plan cannot report its regulatory coverage separately from its hardening coverage, and a reader cannot tell whether a gap is a missed regulation or a missed setting. The question above asks the same thing about level rather than about kind."},{"id":"paper-cat-1","q":"How should benchmark profiles compose with regulatory profiles when the combined control count approaches ~867+?","verbatim":"the position paper submitted to the working group","why":"Follows directly from the question above. If the merge happens, the profile it produces is large enough that resolution becomes the engineering problem."},{"id":"paper-cat-2","q":"Where do Benchmark results get captured: SSP Control implementations or ARs? How will tools manage this?","verbatim":"the position paper submitted to the working group","why":"The site's own answer is that a response is a by-component in the plan of record and a result is an assessment result, and that both exist. Which one a benchmark outcome belongs in is not settled."}]},{"intro":"The rule sits on the component it configures. Four of these are the proposal's own open questions, reproduced from it.","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":"There is no mapping collection in this approach: the tie is inline, so whoever holds it has their document edited by the mapping provider. Two documents could hold it and they belong to different parties. The software definition carries the rules and is the guidance author's; the validation definition carries the checks and is the engine provider's. The tie could sit on either, or on both, and nothing published settles it. The stakeholder table on the component-first page marks the type as unsettled for exactly this reason."},{"id":"proposal-1","q":"AP - Assessment Platform usage? make it optional?","verbatim":"the component-first proposal document","why":"Reproduced from the proposal's own list of open questions, in its own words. All four are about what runs a check and how it is tied to what it ran, which is the same thing the NIST team was asked on 17 July."},{"id":"proposal-2","q":"AP - Is assessment component sufficient or we need assessment platform also?","verbatim":"the component-first proposal document","why":"The proposal asks this of itself, and the three corpora answer it three ways, which is what makes it a question about OSCAL rather than about this approach."},{"id":"proposal-3","q":"AP - How is assessment asset associated to the tasks or activities? currently there seems to be no way.","verbatim":"the component-first proposal document","why":"The join between what runs and what it was told to run. The proposal records that there is no way to write it."},{"id":"proposal-4","q":"In AR there are multiple assessment assests defined. How is an obesrvation associated with an assessment asset?","verbatim":"the component-first proposal document","why":"The same gap on the result side: several assets are declared and nothing ties an observation to the one that produced it."},{"id":"paper-comp-1","q":"If Benchmarks are published as CDefs for software components and service providers publish CDefs for their software, can an SSP have multiple OSCAL components describing the system component?","verbatim":"the position paper submitted to the working group","why":"A system runs software from several vendors and is held to several benchmarks, so the plan of record would import definitions from both, and nothing says how they combine."},{"id":"paper-comp-2","q":"If Benchmark CDefs contain desired state, do the values get updated to actual state in the SSP?","verbatim":"the position paper submitted to the working group","why":"This is the desired-state risk the site records against this approach: rules describe how a component should be configured, and a plan of record describes how the system is."},{"id":"paper-comp-3","q":"What portion of the benchmark context gets pulled into the SSP? If not all, how will data get filtered out when importing a CDef into an SSP component?","verbatim":"the position paper submitted to the working group","why":"A thousand-page guide is mostly prose. What of it belongs in a plan of record, and what a tool should drop on import, is unanswered."},{"id":"paper-comp-4","q":"How could CDefs support the tailoring needs of benchmarks?","verbatim":"the position paper submitted to the working group","why":"The tailoring question, asked of this approach. It has a param on the rule and set-parameters on the control implementation, which is more than the assessment approach has and less than a profile."},{"id":"paper-comp-5","q":"Should ARs or APs support import of CDef with Benchmark context?","verbatim":"the position paper submitted to the working group","why":"The site's own encoding says yes for the assessment plan: the definition is carried in as an asset and the checks travel with it. Whether that is the intended route is the question."}]},{"intro":"The rule is an activity in an assessment plan. One question is on the record against this approach, and it is about tailoring.","key":"assessment-first","label":"Assessment-first","questions":[{"id":"paper-ap-1","q":"How should AP-based benchmarks handle tailoring needs that only the catalog/profile model natively supports?","verbatim":"the position paper submitted to the working group","why":"The same question as where a parameter goes, asked of this approach by name. An activity and a step have no parameter, so a value lives in the requirement text and tailoring means editing the sentence."}]}]},"data/quotes.json":{"note":"Every quotation gathered from the record. RETAINED AS PROVENANCE AND NO LONGER RENDERED. Per the Gate 7 decision the site carries no quotations at all, and characterizations trace to a JSON pointer into a shipped file or to a cited source document. The file is kept because deleting it would destroy the record of what was said and where, which a later session may need. tools/verify.py --quotes now asserts that no page renders any of it.","quotes":[{"affiliation":"IBM","context":"The warrant for treating rule and check as separate questions. Recorded by the group as already settled.","date":null,"id":"anca-rule-check-separation","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 3, settled item 5","speaker":"Anca Sailer","text":"a rule, which is unique, can be associated with a check ID in Ansible, with a check ID in Terraform, with a check ID in OPA, with a check ID in OpenSCAP. The reason is not semantics, the reason is schema flexibility."},{"affiliation":"IBM","context":"The rationale for proposing new assemblies rather than props.","date":null,"id":"anca-check-first-class","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B","speaker":"Anca Sailer","text":"Instead of abusing a property in order to do that, check is a first class citizen."},{"affiliation":"IBM","context":"Why CIS is drawn to the catalog. A structural requirement rather than a semantic argument.","date":"2026-03-20","id":"anca-cis-hierarchy","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A","speaker":"Anca Sailer","text":"their main complaint was the hierarchical structure. They wanted a native support for that hierarchy. And they found it in the catalog, and that's the reason why they go there. It is the CIS need for the hierarchy."},{"affiliation":"IBM","context":"One of three unreconciled statements of purpose.","date":"2026-03-20","id":"anca-purpose","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 4","speaker":"Anca Sailer","text":"The sufficient support in OSCAL so that we can communicate with each other, not to impose the processes on each other."},{"affiliation":"IBM","context":"The core claim for the component-first approach.","date":null,"id":"vikas-cdef-automation","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B","speaker":"Vikas Agarwal","text":"The component definition is used to specify how a component is implementing a control, and that is for documentation purpose. But that doesn't help me automate my processes. What we have done is, we have put that fine-grained rules inside that component definition, so that we can also automate."},{"affiliation":"IBM","context":"The clearest statement anywhere in the corpus of who authors question 1 versus question 3.","date":null,"id":"vikas-persona-split","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B","speaker":"Vikas Agarwal","text":"The rules are being created by the software component vendors. As a software vendor, I define all my rules. As a tool vendor, I define all my checks. And in the SSP and AP, I just pull the content."},{"affiliation":"IBM","context":"The instance-versus-library objection to the assessment-first approach.","date":null,"id":"vikas-instance-vs-library","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option C, objections","speaker":"Vikas Agarwal","text":"the assessment plan is for your specific instance when you are assessing it, and it will change from assessment to assessment. If I can generalize it and put it outside so that I can just refer it to the assessment plan and use it, that probably would be a better way."},{"affiliation":"IBM","context":"IBM's own statement of the schema change surface.","date":null,"id":"vikas-affects-all-models","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B","speaker":"Vikas Agarwal","text":"It's affecting all models, right? Starting from component definition to SSP to plan to results to POAM."},{"affiliation":"AWS","context":"The core claim for the catalog-first approach.","date":null,"id":"fritz-catalogs-for-requirements","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A","speaker":"Fritz Kunstler","text":"My perspective is that the catalogs should be used for basically any sort of control requirement, whether it's technical or governance related. I think the model serves both purposes effectively, and we should ideally use it instead of creating something new or similar with different names."},{"affiliation":"AWS","context":"The clearest statement of the view that a hardening rule is a requirement.","date":null,"id":"fritz-standard-setter","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A","speaker":"Fritz Kunstler","text":"AWS is the standard setter or the expert on how the services should be secured, the requirements for securing those services according to best practices, and those requirements are delivered in the form of controls. And that's what AWS calls them."},{"affiliation":"AWS","context":"Why the AWS catalog ships with no control tie. The stated reason question 2 is empty rather than absent.","date":null,"id":"fritz-stripped-props","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A","speaker":"Fritz Kunstler","text":"I intentionally stripped this out before I published it, because I didn't want to apply anything until we landed on a decision here."},{"affiliation":"AWS","context":"On the label applied to component-definition rule content. Supports the capability-statement view.","date":null,"id":"fritz-possible-state","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Fritz Kunstler","text":"Well, not desired state. It's possible state, I would say."},{"affiliation":"AWS","context":"The schema change cost objection, which is criterion 10.","date":null,"id":"fritz-cost-of-change","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Fritz Kunstler","text":"We have overwhelming evidence that changing OSCAL is unusually hard and time-consuming. The alternative is that we will be talking about this next year."},{"affiliation":"AWS","context":"On whether vendors must publish catalogs.","date":null,"id":"fritz-vendors-need-not","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A, unresolved","speaker":"Fritz Kunstler","text":"No, they don't. It's not that they must. My opinion is that yes, they can and should do that. But could you do it a different way? Yeah, you could do it a different way."},{"affiliation":null,"context":"The normativity objection, and the crux of what kind of thing a rule is.","date":null,"id":"brian-not-normative","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Brian Ruf","text":"there's nothing in this component definition that says you must do it this way. It may have the term rule in AWS's terminology, but it's not a rule from an auditor's perspective."},{"affiliation":null,"context":"One of three unreconciled statements of purpose.","date":"2026-03-20","id":"brian-not-wrong","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 4","speaker":"Brian Ruf","text":"I don't think that any of these are wrong. They're different ways to come at the same problem with different goals in mind."},{"affiliation":null,"context":"One of three unreconciled statements of purpose.","date":"2026-03-20","id":"dave-single-way","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 4","speaker":"Dave Waltermire","text":"Our goal should be to have a single, opinionated way of supporting all of the use cases that we're talking about."},{"affiliation":null,"context":"Unanswered since 20 March. If the answer is the shim, every option changes shape.","date":"2026-03-20","id":"dave-xccdf","source_document":"Hardening-Guidance-Options-Comparison.docx, A prior question that has never been answered","speaker":"Dave Waltermire","text":"Why are we trying to represent a checklist in OSCAL when we have something like XCCDF, which CIS and DISA already support? [...] We shouldn't be trying to make OSCAL the Uber data model to end all data models. [...] Do we provide, effectively, full-throated support for checklists, which is where this is kind of leaning, versus do we provide a lightweight shim in OSCAL that provides the connectivity to that external thing?"},{"affiliation":null,"context":"Independent validation of the assessment-first approach.","date":"2026-03-13","id":"dave-as-intended","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option C","speaker":"Dave Waltermire","text":"This looks right. This looks like you're using it as it was intended."},{"affiliation":null,"context":"The fit objection to the component-first approach.","date":null,"id":"banghart-not-meant","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Steven Banghart","text":"you're using component definition in a way that it wasn't meant to be used. You've successfully used it in this way. But we could make it better."},{"affiliation":"Easy Dynamics","context":"The core claim for the assessment-first approach.","date":"2026-03-13","id":"pranav-assessment-start","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option C","speaker":"Pranav Kothare","text":"We eliminate the idea of using catalogs and profiles because they just sort of play a part in defining the requirements for the compliance process. The real assessment piece should start from the assessment plan."},{"affiliation":"Easy Dynamics","context":"How the assessment-first approach indicates a check.","date":"2026-03-20","id":"pirooz-first-class-oscal","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option C","speaker":"Pirooz Javan","text":"Everything you're seeing here is first-class OSCAL. No props, no anything. We look at something like 2.1 as being an assessment plan with activities, eight steps in 2.1. The only prop you have to add is a context to say, go automate the assessment for this activity."},{"affiliation":"Easy Dynamics","context":"The response-fidelity objection, which is criterion 8 and question 4. Applies to any option that shifts requirements left.","date":null,"id":"pirooz-response-fidelity","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Pirooz Javan","text":"the AP has the subjects which are four ways where SSPs only allow you to respond by components. I think that's a limitation we also need to discuss."},{"affiliation":"Easy Dynamics","context":"Why resolving the question matters, and who bears the cost of not resolving it.","date":"2026-03-20","id":"pirooz-adoption-confusion","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 2","speaker":"Pirooz Javan","text":"When a group like CIS, who's very interested in adopting OSCAL, is hearing that their benchmark should be in catalogs from one person, in component definitions from another group, and in assessment plans from us, it creates a lot of confusion and concern around adopting OSCAL when the folks that are closest to it can't agree on methodologies."},{"affiliation":"Easy Dynamics","context":"The authoring burden objection, which is criterion 6.","date":null,"id":"pirooz-authoring-burden","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A, objections","speaker":"Pirooz Javan","text":"for a CIS that has 100 hardening guides, converting each of those to four or five different OSCAL files."},{"affiliation":"Easy Dynamics","context":"The capability-statement view of what a rule is. Note: this is an Easy Dynamics document and must be attributed as advocacy per editorial rule 10.","date":null,"id":"deck-may-be-configured","source_document":"Where-does-desired-state-go.pptx, slide 3","speaker":null,"text":"Software vendors secure configuration guidance/recommendations for how their software “may” be configured to meet regulatory requirements should do so in CDefs"},{"affiliation":"Easy Dynamics","context":"The statement that the control tie is optional by design. The warrant for question 2's treatment.","date":null,"id":"deck-optional-mapping","source_document":"Where-does-desired-state-go.pptx, slide 3","speaker":null,"text":"Not all implementations in a Cdef are required to map back to a control, but the option is there. This enables desired state configurations to support regulatory control responses in an SSP."},{"affiliation":"Easy Dynamics","context":"The sharpest statement in the corpus of the difference between an implementation claim and an assessment result.","date":null,"id":"deck-how-vs-passfail","source_document":"Where-does-desired-state-go.pptx, slide 1","speaker":null,"text":"Current SSP is intended to capture “how” a control is satisfied. Current desired state benchmarks are meant to be pass/fail"},{"affiliation":"Easy Dynamics","context":"Question 4, subject granularity. The same concern as criterion 8.","date":null,"id":"deck-by-component-granularity","source_document":"Where-does-desired-state-go.pptx, slide 1","speaker":null,"text":"Current SSP only provides system state through by-component responses – not granular enough"},{"affiliation":"OSCAL Foundation TFG","context":"OSCAL cannot express shall, should or may. The reason the normativity question cannot be settled inside the model.","date":"2026-08","id":"preread-requirement-level-absent","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 7, criterion 3 row","speaker":null,"text":"Absent from OSCAL entirely. An orthogonal gap affecting every option."},{"affiliation":"OSCAL Foundation TFG","context":"The pre-read's own conclusion, reached from the meeting record. The site reaches the same conclusion from the files.","date":"2026-08","id":"preread-no-ssp-no-ar","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 7","speaker":null,"text":"No option has a published SSP or a published assessment result. The group has been arguing about where content belongs for five months without ever seeing the two artifacts where the strongest objections on both sides would be resolved."},{"affiliation":"OSCAL Foundation TFG","context":"Questions 4 and 5 are the least-defined parts of OSCAL and the group has said so on the record.","date":"2026-08","id":"preread-platform-semantics","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 8, evidence register item 8","speaker":null,"text":"Authoritative semantics for assessment platform versus asset versus component. Pirooz and Vikas agreed to post for the NIST OSCAL team, 17 July. Not established whether posted; no response in the record"},{"affiliation":"AWS","context":"The publisher's own status disclaimer. Required alongside any AWS data-quality item per editorial rule 8.","date":null,"id":"aws-readme-experimental","source_document":"AWS/oscal-content-for-aws-services-main/README.md","speaker":null,"text":"Amazon Web Services (AWS) is offering _experimental_ Open Security Controls Assessment Language (OSCAL) content for public review and feedback."},{"affiliation":"AWS","context":"The stated design principle behind the catalog-first content.","date":null,"id":"aws-docs-core-oscal","source_document":"AWS/oscal-content-for-aws-services-main/docs/COMPONENTS.md","speaker":null,"text":"The AWS component definitions are designed to use core OSCAL to the greatest degree practical."},{"affiliation":"IBM","context":"The normative statement that checks live only on validation components. The typo is in the source.","date":null,"id":"ibm-checks-validation-only","source_document":"IBM/component-rules.md, line 39","speaker":null,"text":"Check defintions are only used to define checks for validation components (assessment tools)."},{"affiliation":"AWS","context":"Quoted in full rather than characterized. This is where AWS's own sense of a validation component appears, which is a component enumerating the frameworks a service has been validated against. It is listed as a future expansion and is not shipped. It is not IBM's sense of the term.","date":null,"id":"aws-docs-future-considerations","source_document":"AWS/oscal-content-for-aws-services-main/docs/COMPONENTS.md, Future Considerations","speaker":null,"text":"Depending on potential usefulness or customer demand, we may expand these component definitions. If any of the following efforts are valuable to you, please let us know. Compliance linkages. Compliance deployment automation. Compliance validation automation. Compliance documentation content. Compliance linkages. Under this expansion, AWS could create an additional OSCAL component definition that enumerates all applicable compliance frameworks as \"validation\" components. Each AWS region and service could then be linked to the frameworks where the region or service was found to be compliant. This would allow a machine-readable method of determining which services are validated under a particular framework and which are not. The resulting component definition relationships would expand as follows: Compliance deployment automation. This could provide automated deployment scripts that ensure a service is deployed consistent with the requirements of a specific framework. Compliance deployment validation. This could provide automated validation scripts that ensure a service continues to operate with a configuration consistent with the requirements of a specific framework. Compliance documentation content. This could provide documentation that describes the component configuration in alignment with the requirements of security frameworks that require such documentation."},{"affiliation":"IBM","context":"IBM's four self-identified open questions, verbatim including their typographic errors. All four concern questions 4 and 5.","date":null,"id":"ibm-open-questions","source_document":"IBM/component-rules.md, Open questions","speaker":null,"text":"1. Assessment Platform usage? make it optional? 2. Is assessment component sufficient or we need assessment platform also? 3. How is assessment asset associated the tasks or activities? currently there seems to be no way. 4. In AR there are multiple assessment assests defined. How is an obesrvation associated with an assessment asset? Currently there is no way to do it."}]},"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":"an activity names the control it serves through related-controls or reviewed-controls","model":"mapping-collection","what":"none, the tie is on the activity"},{"count":0,"detail":"assessment-assets carries the components that run the checks, so they need no document of their own","model":"component-definition","what":"none, the engines are named inside each plan"},{"count":1,"detail":"no guidance enters it; the plans point at it rather than adding to it","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, answering 370 controls"},{"count":4,"detail":"the three guides carry 547 requirements between them, as activities and steps, and each plan names 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 separate results rather than four sections of one, because a result names exactly one plan through import-ap and that field is neither an array nor optional","items":[{"name":"800-53 AR"},{"name":"CIS Ubuntu AR"},{"name":"DISA PgSQL AR"},{"name":"CISA SCuBA AR"}],"model":"assessment-results","what":"one per plan, because a result names exactly one plan"}],"plan_of_record":"The plan of record answers 370 controls, and none of the three guides enters it","rule":"Each guide becomes an assessment plan. The framework side is unchanged, and each plan produces a result of its own."},"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 the organisational profile that merges them, which is needed because a plan reaches all four through one import-profile and that field is a single required object","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 to merge them"},{"count":3,"detail":"without these the guide's controls and the framework's controls are two unrelated sets in the same plan","items":[{"name":"CIS to 800-53"},{"name":"STIG to 800-53"},{"name":"SCuBA to 800-53"}],"model":"mapping-collection","what":"one per guide, tying its controls to the framework"},{"count":3,"detail":"the control names the check by identifier and a software component of that name carries the runner detail","items":[{"kind":"software","name":"Ubuntu checks"},{"kind":"software","name":"PgSQL checks"},{"kind":"software","name":"M365 checks"}],"model":"component-definition","what":"one per technology, carrying the check components"},{"count":1,"detail":"370 from the framework and 547 from the guides, each needing a by-component response, and all of them reached through one import-profile because that field is a single required object","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, answering 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 plan of record answers 917 controls, 370 from the framework and 547 from the guides","rule":"Each guide is published as a catalog, selected by a profile of its own, and tied back to the framework by a mapping collection. The plan of record answers 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-implementation names the control the rule serves, so no second document carries the tie","model":"mapping-collection","what":"none, the tie is inside the component definition"},{"count":6,"detail":"Ubuntu, PostgreSQL and Microsoft 365, and one validation component definition per engine that tests them","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 carrying 547 rules, three engines carrying the checks"},{"count":1,"detail":"the control count does not move; the rules arrive inside system-implementation instead","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, answering 370 controls and carrying 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 plan of record answers 370 controls, and carries 547 desired-state rules inside its components","rule":"Each guide becomes rules on the component it configures, and each engine that tests them becomes a component of its own. The framework side is unchanged."}},"excluded_model":{"model":"plan-of-action-and-milestones","reason":"It records what was not met and what is being done about it. That is the same document in all three approaches, so it separates none of them."},"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":"One entry per file, so a reader can follow a particular document from the figure into the list beneath it. The names are shortened to fit a tile. Where a model has more than one kind of file in it, the kind is named too: a component definition holding the thing being configured is software, and one holding the checks that test it is validation, which is the distinction the whole approach rests on and is invisible from the file count alone.","models":["catalog","profile","mapping-collection","component-definition","system-security-plan","assessment-plan","assessment-results"],"note":"One system, one baseline, three hardening guides, modelled three ways. The point of the scenario is that the three approaches do not differ in what they can express so much as in how many documents it takes to express it, and what the plan of record ends up holding. Every count is either recomputed from a corpus in this repository, read from the NIST profile stored in data/scenario-evidence/, or forced by the OSCAL schemas, and each says which. What the schemas force is stated on the file rows it explains rather than in a section of its own.","summary":"A system under NIST SP 800-53 Revision 5 at the High baseline, running Ubuntu, PostgreSQL and Microsoft 365, hardened against a published guide for each. The same scenario is modelled in all three approaches, using every OSCAL model except the plan of action and milestones.","title":"One system, three hardening guides"},"data/schema-evidence/assessment-subject.json":{"constraints":["required includes \"type\"","type anyOf enum == [\"component\",\"inventory-item\",\"location\",\"party\",\"user\"]"],"definition":"oscal-ap-oscal-assessment-common:assessment-subject","fetched_at":"2026-08-21","fragment":{"$id":"#/definitions/oscal-ap-oscal-assessment-common:assessment-subject","additionalProperties":false,"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.","properties":{"description":{"description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description","type":"string"},"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"},"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":["type"],"title":"Subject of Assessment","type":"object"},"model":"assessment-plan","note":"The oscal-ap-oscal-assessment-common:assessment-subject definition. A subject is typed, and the vocabulary is component, inventory-item, location, party or user, so an assessment can be aimed at a particular host rather than at the class of thing the host is.","oscal_version":"1.1.3","provenance":"Taken from the offline OSCAL reference copy of the 1.1.3 schemas rather than from the published 1.2.1 set the other fragments here record, because 1.2.1 could not be fetched. The CI re-fetch compares it against 1.2.1.","schema_id":"http://csrc.nist.gov/ns/oscal/1.1.3/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-08-21","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 implemeting a given control.","title":"Component Universally Unique Identifier Reference"},"description":{"description":"An implementation statement that describes how a control or a control statement is implemented within the referenced system component.","title":"Control Implementation Description","type":"string"},"export":{"additionalProperties":false,"description":"Identifies content intended for external consumption, such as with leveraged organizations.","properties":{"description":{"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","type":"string"},"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":{"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","type":"string"},"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":{"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","type":"string"},"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":{"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","type":"string"},"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":{"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","type":"string"},"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.1.3","provenance":"Taken from the offline OSCAL reference copy of the 1.1.3 schemas rather than from the published 1.2.1 set the other fragments here record, because 1.2.1 could not be fetched. The CI re-fetch compares it against 1.2.1.","schema_id":"http://csrc.nist.gov/ns/oscal/1.1.3/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-08-21","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":{"description":"A name given to the location, which may be used by a tool for display and navigation.","title":"Location Title","type":"string"},"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":{"additionalProperties":false,"description":"An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.","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"},"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"}},"required":["uuid","type"],"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":{"description":"A name given to the document revision, which may be used by a tool for display and navigation.","title":"Document Title","type":"string"},"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":{"description":"A summary of the role's purpose and associated responsibilities.","title":"Role Description","type":"string"},"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":{"description":"A name given to the role, which may be used by a tool for display and navigation.","title":"Role Title","type":"string"}},"required":["id","title"],"title":"Role","type":"object"},"minItems":1,"type":"array"},"title":{"description":"A name given to the document, which may be used by a tool for display and navigation.","title":"Document Title","type":"string"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["title","last-modified","version","oscal-version"],"title":"Document Metadata","type":"object"},"model":"shared","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.1.3","provenance":"Read from the assessment-plan schema in the offline OSCAL reference copy. metadata is one assembly shared by all seven models, so the catalog carries this same definition; the catalog schema file itself could not be opened through the sync layer.","schema_id":"http://csrc.nist.gov/ns/oscal/1.1.3/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":"Nothing in the published content answers this and no reason is on the record."}],"approaches":[{"key":"catalog-first","label":"Catalog-first","layer":"Control","one_line":"The rule is a catalog control, the check is in a software component defined as 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 is a new assembly in a component definition, the check sits in a validation component definition.","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, the check is a new assembly beneath it.","option_letter":"C","primary_model":"assessment-plan","repo":null,"serves_stakeholder_first":"assessor","status_annotation":"placeholder and synthetic identifiers"}],"carrier_note":"Every answer names the OSCAL model it lives in and the assemblies inside it that carry the answer. The model is the first thing that differs between the three: the same requirement is a control in one, a component in another and an activity in the third, and everything downstream follows from that.","empty_states":[{"key":"empty-absent","label":"Unanswered, no stated position","meaning":"Nothing in the published content answers this question and no reason is on the record.","rendering":"hollow with a light dotted fill"}],"finding":"Questions 1 and 2 are answered by all three. Questions 6a and 6b are answered in full by none of them, and no column is complete from top to bottom.","legend":{"answers_title":"Is the question answered?","label":"How to read an answer","mechanism_title":"How the capability is enabled","why_one_block":"Two legends sitting apart read as two subjects, and they are two axes of one reading: every answer on this page carries a mark from the first group and, where it is answered at all, one or more badges from the second. They are one block for the same reason the two axes belong on one cell.","why_uneven":"The answer states are three words and the mechanisms carry a sentence each. That is deliberate rather than an oversight. Answered, partly answered and not answered mean what they say; Proposed does not tell a reader that no tool can read the content until the schema lands, and that is the sentence the page turns on."},"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":"Rules sits on the component as a sibling of control-implementations.","slot":"1","snippet_ids":["ibm-cos-component","ibm-rules-md"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The activity is the rule and its step is the check. No parameter field, so a value goes in the 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":"Made by the mapping model in its own document, not inline. No publisher has shipped one yet.","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":"The component ties to the control today. Tying the rule to it needs 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 scopes the plan, related-controls names what an activity is for. The scope is required, the tie is not.","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 identifier is the bridge to the runtime. It executes a 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":"Proposed schema. A composite key, both halves on the check side. The rule holds no pointer back.","slot":"3","snippet_ids":["ibm-validation-ansible"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"Three conventions. Only the CISA one reaches an executable, through a JSON string in a prop. STIG and CIS describe the check 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":"A by-component is the only shape available, and it names a component, not an instance. An assessor cannot introduce a catalog.","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 same by-component, plus the rule. An assessor can carry the definition into their own plan, and the checks travel with it.","slot":"4","snippet_ids":["ibm-validation-ansible"],"state":"partial"},{"approach":"assessment-first","assemblies":["assessment-subjects","task","subjects"],"mechanisms":["assembly"],"model":"assessment-plan","note":"Scope, then target. The plan names the subjects, each activity aims at some of them. Both name an inventory item, an instance rather than a class.","slot":"4","snippet_ids":["ez-subjects-includeall","ez-subjects-explicit"],"state":"filled"},{"approach":"catalog-first","assemblies":["component"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"Partly. The input and the output are written down; the machine between them is not. ConfigRuleId resolves inside the engine. No assessor's path: a catalog cannot be introduced into an assessment.","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":"Proposed schema. The proposal records four open questions about this, including how an asset is tied to a task.","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":"A chain. The platform runs, the component beneath it is the plugin, and a prop on the task says which 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":"Template level, not system level: a definition says how a component would satisfy a control. Only a plan of record says a system does, and none is published.","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 is a by-component response today. Naming the rule it rests on needs the proposed assembly.","slot":"6a","snippet_ids":[],"state":"empty-absent"},{"approach":"assessment-first","assemblies":["import-ssp","back-matter","resource"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"No claim of its own. It names the document holding one, and a resource for where no plan of record exists.","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":"The repository's own documentation lists compliance validation automation as a future consideration rather than shipping it.","slot":"6b","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["observation"],"mechanisms":["assembly","proposed"],"model":"assessment-results","note":"Observations and no findings, so no objective status. The control is recovered through the plan rather than stated.","slot":"6b","snippet_ids":["ibm-ar-observation"],"state":"partial"},{"approach":"assessment-first","assemblies":["finding","observation"],"mechanisms":["assembly"],"model":"assessment-results","note":"A result of its own, importing the plan. Findings carry a target and a status; an observation's subject is the activity that ran.","slot":"6b","snippet_ids":["ez-cisa-ar-finding","ez-cisa-ar-observation"],"state":"filled"}],"mechanism_note":"How a capability is enabled is a different question from whether it is answered. The answer states describe the published corpus. These describe the model: what an approach would have to rely on to carry the answer at all. An approach can answer everything and still rest on properties no other tool reads, and it can answer nothing while the mechanism it would use is already released.","mechanism_states":[{"key":"assembly","label":"Released OSCAL assembly","meaning":"The capability is carried by an OSCAL assembly that exists today. Adopting it changes no schema.","rendering":"a solid badge","short":"OSCAL assembly"},{"key":"proposed","label":"Proposed assembly","meaning":"The capability is carried by an assembly that does not exist yet. Adopting it means a schema change, and until that lands no tool can read it.","rendering":"a dashed badge","short":"Proposed"},{"key":"prop","label":"Namespaced property","meaning":"The capability is carried by a prop in the publisher's own namespace. The schema does not model it, so a tool that does not know that namespace cannot read it, and no two publishers have to agree.","rendering":"a dotted badge","short":"Prop"}],"note":"The six questions and the answer matrix. This is the site's central claim set. Every cell is asserted against the shipped files and is re-checked by tools/verify.py --matrix. Personal names and proponent organizations are not rendered anywhere on the site; where a cell state depends on a reason someone stated, the note cites the source document rather than the speaker.","paths_note":"A runner is the thing between an input and an output, and which documents those are depends on who runs it. Each path below is one file in, one file out.","proposed_assemblies":["assessment-check-id","associated-checks","checks","implementing-rules","result","rule-groups","rules"],"slots":[{"key":"rule","name":"The rule itself","number":"1","optional":false,"question":"What must be true, and where is that written down?","short":"Rule","why_separate":"The requirement itself, technology-specific, one per testable condition. Pre-read settled item 7 puts its parameters here: the definition declares the options and a default."},{"binding_times":[{"authored_by":"Whoever wrote the rule","key":"inline","label":"Author-time, inline","mechanism":"The rule declares its control directly"},{"authored_by":"Whoever wrote the rule","key":"pointer","label":"Author-time, by pointer","mechanism":"A prop carries an external framework identifier that a consumer must resolve"},{"authored_by":"Anyone, including a third party","available_to":{"assessment-first":false,"catalog-first":true,"component-first":false},"key":"late","label":"Late, external","mechanism":"A separate artifact ties rule to control after publication","why":"mapping-item.type is closed by allOf to control and statement, and mapping-item carries no uuid and no href, so this binding time reaches a rule only where the rule is already modelled as a control or a control statement. The gap is in OSCAL rather than in any approach, and it is not an argument for the one approach it happens to suit: it rewards whichever view of a rule already matches the schema's assumption."}],"cost_of_leaving_empty":{"evidence":["observation.json","finding.json","finding-target.json"],"finding":"Not available. finding requires target; finding-target requires type, closed by allOf to statement-id or objective-id, both control-derived.","observation":"Available. AR observation requires only uuid, description, methods and collected, and carries no control reference of any kind.","summary":"Without a link to a control you can record what you saw, but not whether it complied."},"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":"Optional by design. A rule is finer than a control and may serve several, one, or none. The mechanism must exist and must not be mandatory."},{"key":"check","name":"How the rule is tested","number":"3","optional":false,"question":"What check executes the rule within a runtime environment?","short":"Check","why_separate":"One rule, many checks, one per tool. Pre-read settled item 4 keeps the executable itself outside OSCAL, referenced. The warrant for separating this from question 1 is settled item 5."},{"key":"subject","name":"What the check runs against","not_established":true,"not_established_note":"Evidence register item 8: authoritative semantics for assessment platform versus asset versus component were to be posted to the NIST OSCAL team on 17 July. No response is in the record.","number":"4","optional":false,"question":"What exactly is being tested: a host, a component, an account?","short":"Subject","why_separate":"A host, an inventory item, a component, an account. This is criterion 8, response fidelity."},{"key":"actor","name":"What performs the check","not_established":true,"not_established_note":"Same as question 4. Three approaches use six different subsets of assessment-assets, assessment-platforms, uses-components, validation components, origin actors, task-level props and the method prop.","number":"5","optional":false,"question":"What or who runs the test, and how is that named?","short":"Runner","why_separate":"A validation component, an assessment platform, a tool, a person. Includes the method prop: examine, interview, or test."},{"group_name":"Whether the rule was met, claimed and recorded","key":"implementation-claim","name":"How the system claims it meets the rule","number":"6a","optional":false,"question":"How does a system say it satisfies this, in its own words?","short":"Claim","why_separate":"Asserted by the system owner. Standing design intent, narrative, arguable, per component. Lives in the SSP as implemented-requirement, statement and by-component."},{"group_name":"Whether the rule was met, claimed and recorded","key":"assessment-result","name":"How an assessment records the outcome","number":"6b","optional":false,"question":"Was it satisfied, when, and on what?","short":"Result","why_separate":"Asserted by the assessor. A point in time, evidenced, binary or graded, per subject. Lives in the AR as observation, finding and status. A rule carrying desired state has a binary satisfaction condition; the SSP's implementation statement expects a narrative one."}]},"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-08-22T17:17:36+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","section":null,"sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","section":null,"sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","section":null,"sha256_of_source_file":"49d218b196333445dd67178dd58aba441fc596a28d2221c1c724d8eba460ee57","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-08-22T17:17:36+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":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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 },\n {\n \"activity-uuid\": \"4e391cf6-5549-46f3-b3d7-aad12cd5a226\"\n },\n {\n \"activity-uuid\": \"2c69fb5c-056f-4788-be36-723b939a4766\"\n },\n {\n \"activity-uuid\": \"04319877-e72d-4967-b968-4852e6738113\"\n },\n {\n \"activity-uuid\": \"53852402-8cd6-4e1c-a559-f31bb004a66e\"\n },\n {\n \"activity-uuid\": \"c98b996e-8dae-40ef-8b40-100ffbe9e5e3\"\n },\n {\n \"activity-uuid\": \"5f62a033-3847-43ec-bafd-3dc1a7621029\"\n }\n ]\n}","extracted_at":"2026-08-22T17:17:36+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-open-questions.json":{"approach":"component-first","content":"## Open questions?\n\n1. AP - Assessment Platform usage? make it optional?\n2. AP - Is assessment component sufficient or we need assessment platform also?\n3. AP - How is assessment asset associated to the tasks or activities? currently there seems to be no way.\n4. In AR there are multiple assessment assests defined. How is an obesrvation associated with an assessment asset? Currently there is no way to do it.","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-open-questions","language":"markdown","pointer":"$","section":"Open questions?","sha256_of_source_file":"630c45450f3cea476cd9a7df7da1f49e22f854832907521656191714eb9bd57c","slot":"meta","source":"IBM/Automated-assessment.md","title":"IBM's open questions"},"data/snippets/ibm-rules-md.json":{"approach":"component-first","content":"# Automated Assessment\n\n## Objective\n\nCurrent OSCAL cDef and SSP models only provide support for a textual description of how a component (s/w, service, process, etc.) implements a catalog control. This may be sufficient for audit documentation requirements as part of an SSP, but does not enable automation of assessments.\n\nCatalog controls specify the requirements at a high-level which are technology/product/service/process agnostic. Each component implements the control requirements in its own way based on the product's design/implementation. What is required is a way to specify how a component implements a control (configuration settings, APIs, etc.) which can then be assessed to validate its compliance.\n\n### User Stories\n\nAs an OSCAL component vendor, I would like to specify concrete technical capabilities (rules) that my component provides to support control implementation requirements, which can then be evalauated to validate conformance to specific controls.\n\nAs an OSCAL component (assessment tool) vendor such as OpenSCAP, Kyverno, OPA policies, etc., I would like to specify validations (checks) that my tool implements for different component rules. These checks can be either automatically or manually executed and their results (pass, fail, N/A) validate whether a rule satisfies its stated intent or not.\n\n## Proposal\n\nAdd support for rules, checks, and related changes to different OSCAL models to help automation of assessments.\n\n### Adding Rules in OSCAL Component Defintion\n\nThe product vendors or service providers can specify their product’s compliance implementation by defining the mapping of the regulation controls to the product’s technical policy rules and their parameters. These rules can be thought of as configurations that can be performed on the service, across multiple services, or as behaviors of a product. Since the catalog or profile controls specify requirements at a coarser granularity and are technology agnostic, the rules capture the technology-specific implementation of those controls at a finer granularity such that they can be programmatically verified via checks based on evidence collected programmatically via APIs.\n\nA component provider needs to provide for a given control both (a) the specific rules with related parameters and values, as well as (b) the control responses as text describing how a control is implemented by that product or service.\n\n#### Rule assembly\n\nThe below structure gives the proposed rule structure in OSCAL.\n\n- rules [0 to ∞]\n - id [1]\n - title [0 or 1]\n - description [1]\n - audit-procedure [0 or 1]\n - remediation-procedure [0 or 1]\n - params [0 to ∞]\n - evidence-id [0 or 1]\n - props [0 to ∞]\n - links [0 to ∞]\n - remarks [0 or 1]\n\nEach rule will have:\n\n- id: textual id (not uuid) that uniquely identifies a rule in a component\n- title: a summary title for the rule\n- description: brief explanation of the aspect/objective that this rule supports\n- audit-procedure: textual description of how this rules can be validated\n- remediation-procedure: textual description of how this rule can be fixed if it is failing\n- params: any parameters associated with this rule. These parameter(s) will be used in the validation (check).\n- evidence-id: any linkage to evidence data structure or API that is used for evaluation\n\n#### Rule grouping assembly to organize rules\n\nRules can be grouped to better organize them.\n\n- rule-groups [0 to ∞]\n - id [1]\n - title [0 or 1]\n - description [1]\n - props [0 to ∞]\n - links [0 to ∞]\n - A choice of:\n - rule-groups [0 or 1]\n - rules [0 or 1]\n\n#### An example\n\n```JSON\n\"components\": [\n {\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 }\n]\n```\n\n\n#### Rule association to control or statements\n\nEach rule in a component can be associated to one or more controls/statements in implemented requirements. This enables automatation of control implmentation and assessments as the validaiton of a control/statement can now be computed using validation of its associated rules.\n\n- implementing-rules [0 to ∞]\n - rule-id [1]\n - remarks [0 or 1]\n\n```JSON\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 {\"rule-id\": \"cos_access_endpoint_type\"}\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 {\"rule-id\": \"cos_encryption_hyperprotect_key_configured\"}\n ]\n }\n ]\n }\n]\n```\n\n### Adding checks in OSCAL Component Defintion (only for components of type \"validation\")\n\nPolicy validation tools (assessment tools) vendors need to specify the policy checks that they implement and their mapping to different products' technical rules. These checks, tests the policy compliance, thus bridging the OSCAL compliance as code into the policy as code.\n\nPlease note that we don't capture the actual check code or policy as part of the OSCAL. These will be implemented in their respective policy lanaguages and executed accordingly. We only capture the check ids so that the results (against those ids) can be used to perform the aggregation.\n\nCheck defintions are only used to define checks for validation components (assessment tools) and they are not used in other component defintions (s/w, service, process, etc.).\n\n#### Check Assembly (only for validation components)\n\nThe below structure gives the proposed check structure in OSCAL.\n\n- checks [0 to ∞]\n - id [1]\n - title [0 or 1]\n - description [1]\n - rule-id [1]\n - target-component-uuid [1]\n - props [0 to ∞]\n - links [0 to ∞]\n - remarks [0 or 1]\n\nEach check will have:\n\n- id: uniquely identifies a check in a validation component. The validation results (pass, fail, etc.) as part of tool execution will be reported against this same id.\n- title: a summary title for the check\n- description: brief explanation of what this check does\n- rule-id: the rule for which this check provides the implementation.\n- target-component-uuid: the target component to which the above rule belongs. Rules are only considered unique within a component. Hence, both rule and traget component are required to uniquely identify the rule.\n\n```JSON\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\n### Component Defintion changes\n\nChanges in component defintion structure.\n\n- component\n - uuid [1]\n - type [1]\n - title [1]\n - description [1]\n - purpose [1]\n - **params [0 to ∞]**\n - **A choice of:**\n - **rule-groups [0 or 1]**\n - **rules [0 or 1]**\n - **checks [0 or 1]**\n - ...\n - control-implementations [0 or 1]\n - ...\n - source [1]\n - ....\n - set-params [0 to ∞]\n - implemented-requirements [1 to ∞]\n - ...\n - control-id [1]\n - ....\n - **implementing-rules [0 to ∞]**\n - set-params [0 to ∞]\n - ...\n - statements [0 to ∞]\n - statement-id [1]\n - ...\n - **implementing-rules [0 to ∞]**\n - ...\n\n### SSP changes\n\nSame changes will be applicable to component definition and implemented requirements section in SSP.\n\nOne difference to note here is that the component defintion created by vendor will include all possible rules for that component with their association to controls across multiple profiles/catalogs, but when including in the SSP, only those rules need to be selected which are applicable to the SSP (based on the controls in the imported profile). The vendor defined component definiton can be thought of as a library (of all possible rules) and the ones defined in SSP can be thought of as its instance (only including what is relevant).\n\n```JSON\n\"system-security-plan\": {\n \"uuid\": \"7550c0c0-31f9-46fd-b022-3a7ae0f3896f\",\n \"metadata\": ...,\n \"import-profile\": {\n \"href\": \"trestle://profiles/ACME_official/profile.json\"\n },\n \"system-characteristics\": ...,\n \"system-implementation\": {\n \"components\": [\n {\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 \"status\": {\n \"state\": \"operational\"\n }\n }\n ]\n },\n \"control-implementation\": {\n \"description\": \"This is the control implementation for the system.\",\n \"set-parameters\": [\n {\n \"param-id\": \"endpoint_access\",\n \"values\": [\n \"private\"\n ]\n }\n ],\n \"implemented-requirements\": [\n {\n \"uuid\": \"7ec5da9d-b53a-4030-802d-ad88a49d69d5\",\n \"control-id\": \"ac-4\",\n \"by-components\": [\n {\n \"component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\",\n \"uuid\": \"265e556d-f7c9-4e0d-acdd-48f1e30331ee\",\n \"description\": \"This control is implmeneted by ensuring the COS is only available on private endpoints.\",\n \"implementing-rules\": [\n {\"rule-id\": \"cos_access_endpoint_type\"}\n ],\n \"implementation-status\": {\n \"state\": \"implemented\"\n }\n }\n ]\n }\n ]\n }\n}\n```\n\n### Changes in Assessment Plan\n\nThe validation component can be included in the `assessment-plan->assessment-assets->components`. The check assembly will be included in this component. The original validation component defintion would contain all the checks provided (implemneted) by that specific tool, but when including in the AP, only those checks will be included that are required (same as in SSP for software/service component defintion).\n\n- assessment-plan\n - uuid\n - ....\n - local-definitions\n - activities\n - uuid\n - description\n - **assessment-asset-uuid [0 or 1]**\n - **check-ids [0 to ∞]**\n - ....\n - ...\n - assessment-assets\n - components\n - uuid\n - type\n - title\n - description\n - **checks [0 to ∞]**\n - ...\n\nValidation component and the corresponding checks to be executed (as part of activities) can be associated with `local-defintion->activities`\n\n```JSON\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 ]\n```\n\n`assessment-plan->tasks` can be used to define when/at what frequency to perform assessment acitivities such as run different assessment (validation) tools - OSCAP for Ubuntu OS, OpenShift Compliance Operator (OSCO) for OpenShift, etc. and which subjects each of these tools perform assessment for. This is done by associating the right activities with the tasks.\n\n### Changes in Assessment Result\n\nAdd assessment-check-id and assessment-asset-uuid to each observation to specify the check-id for which this observation is (and for which assest / assessment tool). Also, add result to capture the outcome (pass, fail, n/a).\n\n- observations [0 to ∞]\n - uuid\n - description\n - **assessment-check-id [0 or 1]**\n - **assessment-asset-uuid [0 or 1]**\n - **result [0 or 1]**\n - subjects [0 to 1]\n - ....\n\n```JSON\n {\n \"uuid\": \"6c0a18ff-36b4-45b2-9e8b-6e3011bee6b1\",\n \"description\": \"xccdf_org.ssgproject.content_rule_package_prelink_removed\",\n \"assessment-check-id\": \"xccdf_org.ssgproject.content_rule_package_prelink_removed\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"result\": \"pass\",\n \"props\": [],\n \"methods\": [\n \"TEST\"\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 }\n```\n\n## Open questions?\n\n1. AP - Assessment Platform usage? make it optional?\n2. AP - Is assessment component sufficient or we need assessment platform also?\n3. AP - How is assessment asset associated to the tasks or activities? currently there seems to be no way.\n4. In AR there are multiple assessment assests defined. How is an obesrvation associated with an assessment asset? Currently there is no way to do it.","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-rules-md","language":"markdown","pointer":"$","section":null,"sha256_of_source_file":"630c45450f3cea476cd9a7df7da1f49e22f854832907521656191714eb9bd57c","slot":"meta","source":"IBM/Automated-assessment.md","title":"IBM's proposed rule and check assemblies"},"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 only run here. There is no path from a check to a claim, so what comes out is a result and never the plan of record."},"benchmark":{"note":"Writes the activity and its steps. The check that runs them is the engine's.","writes":[{"model":"assessment-plan"}]},"engine":{"note":"The plan is the engine's, and the checks in it are what it adds. It is named inside the plan too, in assessment-assets.","writes":[{"model":"assessment-plan"}]},"mapper":{"note":"Edits the plan rather than writing one. Reviewed-controls on the activity names the framework controls the check covers.","writes":[{"model":"assessment-plan"}]},"owner":{"note":"The selection and the plan of record, and nothing beyond them. An assessor's run takes no dependency on what the owner automates, and cannot see it.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"note":"Writes the activity and its steps. The check that runs them is the engine's.","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 same checks, a different party running them. What comes out is a result, and its finding targets the statement the owner wrote."},"benchmark":{"writes":[{"model":"catalog"}]},"engine":{"note":"Builds the tool and runs nothing. What it ships is the check, as a component of type software. The catalog it points at is the guidance authors'.","writes":[{"kind":"software","model":"component-definition"}]},"mapper":{"note":"The one approach where the tie is a document of its own, and the mapping provider's to write. No publisher has shipped one for hardening guidance yet.","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 profile is always the owner's: the selection of what this system is held to, and the merge of the catalogs a plan can import.","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 run goes through the assessment plan, which is what lets the result name the host rather than the component."},"benchmark":{"writes":[{"kind":"software","model":"component-definition"}]},"engine":{"note":"A component of type validation rather than software, holding the checks. Builds it, runs nothing.","writes":[{"kind":"validation","model":"component-definition"}]},"mapper":{"note":"Edits a definition rather than writing one. Which of the two carries the tie, the rules or the checks, is an open question.","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":"One role, two kinds of organisation, the same model. Nothing downstream can tell which of them wrote a rule."},{"key":"automation","label":"Automation tools and who runs them","note":"The policy engine and the automation tool are the same thing. A provider builds it, and whoever runs it decides what comes out."}],"intro":"Seven parties touch a hardening rule between a published guide and an audited system, and each works in an OSCAL model. Two sets of them are grouped: the bodies that author guidance, and the automation.","note":"Seven parties touch a hardening rule between the body that writes it and the auditor who reads the outcome, and each one works in an OSCAL model. Which model is the whole of what an approach asks of a party, so this is a mapping rather than an argument. Two entries need their component type named, because the same model does two jobs for two different parties. Two sets of the seven are grouped. The bodies that author hardening guidance are one role played by two kinds of organisation. The automation is a policy engine and the two parties that run it: a provider builds the tool and runs nothing, which is why its flows name whoever executes them, and the system owner and the auditor are those parties. The mapping provider is a party of its own because a hardening guide does not always carry the tie to a framework: a STIG carries CCIs and it is DISA's separate CCI list that names the 800-53 controls, and third parties publish mappings of their own through NIST's OLIR programme. Whoever writes the guide is often not whoever ties it to the framework.","parties":[{"key":"regulatory","name":"Regulatory control providers","who":"NIST with SP 800-53, and bodies like it"},{"key":"mapper","name":"Mapping providers","who":"DISA's CCI list, NIST's OLIR programme, the Secure Controls Framework and bodies like them, tying a guide to a framework"},{"group":"guidance","key":"benchmark","name":"Technical hardening guidance providers","who":"CIS, DISA and other benchmark publishers"},{"group":"guidance","key":"software","name":"Software providers","who":"Vendors publishing secure configuration guidance for their own product, alone or with a body such as CIS"},{"group":"automation","key":"engine","name":"Policy engine providers","who":"OPA, Kyverno, ScubaGear, OpenSCAP and the like, assessing, auditing and checking"},{"group":"automation","key":"owner","name":"System owners","who":"Implementing these concepts on a real system"},{"group":"automation","key":"auditor","name":"Independent auditors","who":"Running the same checks independently of the system owner, and reading the outcome"}],"runtime":"A tool reads OSCAL, executes, and writes OSCAL. The party in this row builds it; the party on each flow runs it."},"data/tradeoffs.json":{"approaches":{"assessment-first":{"cons":[{"body":"A required value is written into the activity title, so selection means writing a plan rather than resolving a profile.","title":"No parameter to resolve"},{"body":"The model runs activity to step, and guidance that nests four levels deep has two of them to land in.","title":"Two tiers, where a guide is sometimes deeper"},{"body":"The result names a plan no file here carries and gives an observation a subject type the model does not define.","title":"The published set does not join up"}],"intro":"Considerations when introducing technical hardening guidance as an assessment plan have been captured","pros":[{"body":"The plan points at the document holding the claim rather than making one, so adding or retiring a guide touches the assessment plan alone.","title":"The plan of record does not move"},{"body":"A result is a document of its own importing a plan, and the corpus ships one whose findings target objectives and rest on observations.","title":"Plan to result is a lifecycle this layer has"},{"body":"A subject can be an inventory item, so two hosts of one operating system configured differently each carry their own finding.","title":"The subject is whatever was assessed"},{"body":"A task carries a schedule and names the platform that runs it, which no other approach expresses.","title":"Execution context travels with the plan"}]},"catalog-first":{"cons":[{"body":"Benchmark requirements join the regulatory controls the plan of record already answers, and whether each new catalog needs its own plan is unsettled.","title":"More models to keep"},{"body":"Several frameworks and several benchmarks multiply catalogs, profiles and mappings, raising the entry cost for tools and producing hard profile resolution cases.","title":"More complexity to resolve"},{"body":"A response is a by-component, so it names a component and never an instance, and one exception among a hundred hosts cannot be recorded.","title":"The response cannot be made per instance"}],"intro":"Considerations when introducing technical hardening controls as a catalog have been captured","pros":[{"body":"Technical requirements are defined in the catalog and tracked through the remaining models exactly as regulatory controls are.","title":"Requirements of any kind stay in one model"},{"body":"A profile gives a hardening guide organizationally defined parameters and selects the part of it an organisation holds itself to.","title":"Rules can be tailored"},{"body":"Controls, parts and nested groups carry checks, remediation and prose at the scale of a thousand-page guide.","title":"The catalog absorbs the shape of real guides"},{"body":"The tie to a framework is its own mapping-collection, so a third party can publish it without owning either catalog.","title":"The mapping is a document someone else can write"}]},"component-first":{"cons":[{"body":"The proposal changes the component definition, the plan of record, the assessment plan and the result, so today it is a proposal.","title":"Four models have to change"},{"body":"Rules describing how a component should be configured join a document whose job is to say how the system actually is today.","title":"Desired state enters the plan of record"},{"body":"Rationale, audit procedure and remediation are most of a published guide, and the shipped rules carry none of them.","title":"The fidelity fields are proposed, not carried"},{"body":"An exception reaches a rule but still not an instance, because the response is a by-component here too.","title":"The response is still not per instance"},{"body":"For a claim to reach a host rather than a class, implementing-rules would have to be carried by inventory items as well.","title":"Inventory items may need it too"}],"intro":"Considerations when introducing technical hardening rules into a component definition have been captured","pros":[{"body":"A component definition says how a component can meet a control, the world of possibility for software, and rules inside it make that document drive automation.","title":"One artifact serves the reader and the tool"},{"body":"The rule sits on the product and the check on a second component, so a second engine is a second component.","title":"The rule and the check are separate things"},{"body":"The proposed implementing-rules closes the distance between saying a control is implemented and saying which rule implements it.","title":"The claim can name the rule it rests on"},{"body":"Vendors are told to describe how their product can meet requirements in a component definition, so the rules land in one model.","title":"Vendors already have advice for this model"}]}},"note":"Strengths and risks per approach. The counts are not held equal: they were, three a side on every page, so that the shape of the block could not itself be an argument, and that rule was dropped when it started deciding what could be said. An approach has the risks it has. What is still held is that no approach is argued at greater length than another, which tools/approach_pages.py enforces across the three pages. No figures: the site describes one scenario, on one page, and every count belongs there. What each entry rests on is recorded in BUILD-LOG.md and, where it is a claim about what a model can express, in the schema_evidence field here, which is checked but not rendered."},"data/views.json":{"automation_argument":{"claim":"Hardening guidance is predominantly and increasingly automated, both to apply and to verify, which distinguishes it from a regulatory control in kind rather than in granularity.","claim_not_made":"That hardening guidance is never performed manually. The corpus contradicts that stronger form and the site does not assert it.","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, all of them, and every activity carries method EXAMINE","note":"The counterexample. Published because it is what makes the other two rows credible.","stat_keys":["cis_postgres_automated","cis_postgres_manual"]}]},"crux":{"note":"Brian Ruf's objection applies to any option, not only to the one it was raised against.","quote":"brian-not-normative"},"note":"Three views of what a hardening rule is. Each is internally coherent and each implies a different home. The site takes no position on which is correct and declares a working definition instead. Rendered in the order given, which is the order of the OSCAL layers and not a ranking. The advocate and quote fields are retained as provenance and are NOT rendered: per the Gate 7 decision, no personal name, proponent organization or quotation appears on any page. Each view also names the stakeholder it serves, joining to the glossary term of that name, because the three stakeholders and the three readings are the same three-way split seen from two sides.","views":[{"advocate":"Fritz Kunstler, AWS","aligned_approach":"catalog-first","definition":"Normative. A shall. A control by another name, differing from a regulatory control only in specificity.","implies_layer":"Control","implies_model":"catalog","key":"requirement","label":"A requirement","quote":"fritz-standard-setter","stakeholder":"publisher","supporting_quotes":["fritz-catalogs-for-requirements"]},{"advocate":"Anca Sailer and Vikas Agarwal, IBM","aligned_approach":"component-first","definition":"Descriptive. How a component may be configured. The vendor states what is possible; the organization decides what is required.","implies_layer":"Implementation","implies_model":"component-definition","key":"capability","label":"A capability statement","quote":"deck-may-be-configured","stakeholder":"implementer","supporting_quotes":["fritz-possible-state","vikas-cdef-automation"]},{"advocate":"Easy Dynamics","aligned_approach":"assessment-first","definition":"Guidance that is never performed by hand. It is automated to apply and automated to verify, so its natural expression is the thing that does the applying and the verifying.","implies_layer":"Assessment","implies_model":"assessment-plan","key":"procedure","label":"An assessor's procedure","quote":"pranav-assessment-start","stakeholder":"assessor","supporting_quotes":["dave-as-intended"]}],"why_this_matters":"OSCAL has no field for normativity. The pre-read's criterion 3 records requirement level as absent from OSCAL entirely, an orthogonal gap affecting every option. Location has therefore become the only channel available for expressing which of these three views an author holds.","working_definition":{"status":"A working definition adopted so that three comparable pages can be written. It is not a position on which of the three views is correct.","term":"rule","text":"One technical requirement or recommendation, at a granularity finer than a control, without any claim about whether it is binding."}}}; +window.TFGBundle = {"assets/diagrams/710-scenario-assessment.svg":"\n One system, three hardening guides: the file set for the assessment first approach\n A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 11 files in total, across 5 of the seven models. 1 catalog file, the framework only, named NIST 800-53. 1 profile file, the High baseline, named 800-53 High. 0 mapping-collection files, none, the tie is on the activity. 0 component-definition files, none, the engines are named inside each plan. 1 system-security-plan file, one, answering 370 controls, named System SSP. 4 assessment-plan files, one for the framework assessment, one per guide, named 800-53 AP, CIS Ubuntu AP, DISA PgSQL AP, CISA SCuBA AP. 4 assessment-results files, one per plan, because a result names exactly one plan, named 800-53 AR, CIS Ubuntu AR, DISA PgSQL AR, CISA SCuBA AR. A model this approach does not use is drawn hollow and labelled none, so the absence is as visible as the presence. The tile is the same size in all four figures, so the area of ink is the comparison. The plan of record answers 370 controls, and none of the three guides enters it.\n \n \n11 files, across 5 of the seven models\nEach guide becomes an assessment plan. The framework side is unchanged, and each plan produces a result\nof its own.\n\nCONTROL LAYER\n\ncatalog\n\n\nNIST\n800-53\n1 file\nthe framework only\n\nprofile\n\n\n800-53\nHigh\n1 file\nthe High baseline\n\nmapping-collection\n\n0 files\nnone, the tie is on the\nactivity\n\nIMPLEMENTATION LAYER\n\ncomponent-definition\n\n0 files\nnone, the engines are named inside each plan\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, answering 370 controls\n\nASSESSMENT LAYER\n\nassessment-plan\n\n\n800-53 AP\n\n\nCIS Ubuntu\nAP\n\n\nDISA PgSQL\nAP\n\n\nCISA SCuBA\nAP\n4 files\none for the framework assessment, one per\nguide\n\nassessment-results\n\n\n800-53 AR\n\n\nCIS Ubuntu\nAR\n\n\nDISA PgSQL\nAR\n\n\nCISA SCuBA\nAR\n4 files\none per plan, because a result names exactly\none plan\n\nThe plan of record answers 370 controls, and none of the three guides enters it\n\n","assets/diagrams/710-scenario-catalog.svg":"\n One system, three hardening guides: the file set for the catalog first approach\n A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 18 files in total, across all seven models. 4 catalog files, one for the framework, one for each guide, named NIST 800-53, CIS Ubuntu, DISA PgSQL, CISA SCuBA. 5 profile files, one selection per catalog, and one to merge them, named 800-53 High, CIS Ubuntu, DISA PgSQL, CISA SCuBA, Org merged. 3 mapping-collection files, one per guide, tying its controls to the framework, named CIS to 800-53, STIG to 800-53, SCuBA to 800-53. 3 component-definition files, one per technology, carrying the check components, named Ubuntu checks (software), PgSQL checks (software), M365 checks (software). 1 system-security-plan file, one, answering 917 controls, named System SSP. 1 assessment-plan file, one, named System AP. 1 assessment-results file, one, named System AR. A model this approach does not use is drawn hollow and labelled none, so the absence is as visible as the presence. The tile is the same size in all four figures, so the area of ink is the comparison. The plan of record answers 917 controls, 370 from the framework and 547 from the guides.\n \n \n18 files, across all seven models\nEach guide is published as a catalog, selected by a profile of its own, and tied back to the framework\nby a mapping collection. The plan of record answers every control in the merged set.\n\nCONTROL LAYER\n\ncatalog\n\n\nNIST\n800-53\n\n\nCIS Ubuntu\n\n\nDISA PgSQL\n\n\nCISA SCuBA\n4 files\none for the framework, one for\neach guide\n\nprofile\n\n\n800-53\nHigh\n\n\nCIS Ubuntu\n\n\nDISA PgSQL\n\n\nCISA SCuBA\n\n\nOrg merged\n5 files\none selection per catalog, and\none to merge them\n\nmapping-collection\n\n\nCIS to\n800-53\n\n\nSTIG to\n800-53\n\n\nSCuBA to\n800-53\n3 files\none per guide, tying its\ncontrols to the framework\n\nIMPLEMENTATION LAYER\n\ncomponent-definition\n\n\nUbuntu\nchecks\nsoftware\n\n\nPgSQL\nchecks\nsoftware\n\n\nM365\nchecks\nsoftware\n3 files\none per technology, carrying the check\ncomponents\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, answering 917 controls\n\nASSESSMENT LAYER\n\nassessment-plan\n\n\nSystem AP\n1 file\none\n\nassessment-results\n\n\nSystem AR\n1 file\none\n\nThe plan of record answers 917 controls, 370 from the framework and 547 from the guides\n\n","assets/diagrams/710-scenario-component.svg":"\n One system, three hardening guides: the file set for the component first approach\n A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 11 files in total, across 6 of the seven models. 1 catalog file, the framework only, named NIST 800-53. 1 profile file, the High baseline, named 800-53 High. 0 mapping-collection files, none, the tie is inside the component definition. 6 component-definition files, three products carrying 547 rules, three engines carrying the checks, named Ubuntu (software), PostgreSQL (software), Microsoft 365 (software), Ubuntu checks (validation), PgSQL checks (validation), M365 checks (validation). 1 system-security-plan file, one, answering 370 controls and carrying 547 rules, named System SSP. 1 assessment-plan file, one, named System AP. 1 assessment-results file, one, named System AR. A model this approach does not use is drawn hollow and labelled none, so the absence is as visible as the presence. The tile is the same size in all four figures, so the area of ink is the comparison. The plan of record answers 370 controls, and carries 547 desired-state rules inside its components.\n \n \n11 files, across 6 of the seven models\nEach guide becomes rules on the component it configures, and each engine that tests them becomes a\ncomponent of its own. The framework side is unchanged.\n\nCONTROL LAYER\n\ncatalog\n\n\nNIST\n800-53\n1 file\nthe framework only\n\nprofile\n\n\n800-53\nHigh\n1 file\nthe High baseline\n\nmapping-collection\n\n0 files\nnone, the tie is inside the\ncomponent definition\n\nIMPLEMENTATION LAYER\n\ncomponent-definition\n\n\nUbuntu\nsoftware\n\n\nPostgreSQL\nsoftware\n\n\nMicrosoft\n365\nsoftware\n\n\nUbuntu\nchecks\nvalidation\n\n\nPgSQL\nchecks\nvalidation\n\n\nM365\nchecks\nvalidation\n6 files\nthree products carrying 547 rules, three\nengines carrying the checks\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, answering 370 controls and carrying 547\nrules\n\nASSESSMENT LAYER\n\nassessment-plan\n\n\nSystem AP\n1 file\none\n\nassessment-results\n\n\nSystem AR\n1 file\none\n\nThe plan of record answers 370 controls, and carries 547 desired-state rules inside its\ncomponents\n\n","assets/diagrams/710-scenario-profile.svg":"\n One system, three hardening guides: the file set for the profile first approach\n A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 11 files in total, across 5 of the seven models. 4 catalog files, one for the framework, one per guide, carrying its checks, named NIST 800-53, CIS Ubuntu, DISA PgSQL, CISA SCuBA. 4 profile files, the High baseline, and one selection per guide, named 800-53 High, CIS Ubuntu, DISA PgSQL, CISA SCuBA. 0 mapping-collection files, none, the finding targets the guide's own objective. 0 component-definition files, none, the checks are parts on the controls. 1 system-security-plan file, one, answering 370 controls, named System SSP. 1 assessment-plan file, one, reading 547 methods through the components' profiles, named System AP. 1 assessment-results file, one, with a finding per objective, named System AR. A model this approach does not use is drawn hollow and labelled none, so the absence is as visible as the presence. The tile is the same size in all four figures, so the area of ink is the comparison. The plan of record answers 370 controls, and the 547 executable methods are read by the assessment plan through the components' profiles.\n \n \n11 files, across 5 of the seven models\nEach guide is published as a catalog whose controls carry their own executable methods, and each\ncomponent references a profile selecting from it. The framework side is unchanged and the plan of\nrecord's control set does not move.\n\nCONTROL LAYER\n\ncatalog\n\n\nNIST\n800-53\n\n\nCIS Ubuntu\n\n\nDISA PgSQL\n\n\nCISA SCuBA\n4 files\none for the framework, one per\nguide, carrying its checks\n\nprofile\n\n\n800-53\nHigh\n\n\nCIS Ubuntu\n\n\nDISA PgSQL\n\n\nCISA SCuBA\n4 files\nthe High baseline, and one\nselection per guide\n\nmapping-collection\n\n0 files\nnone, the finding targets the\nguide's own objective\n\nIMPLEMENTATION LAYER\n\ncomponent-definition\n\n0 files\nnone, the checks are parts on the controls\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, answering 370 controls\n\nASSESSMENT LAYER\n\nassessment-plan\n\n\nSystem AP\n1 file\none, reading 547 methods through the\ncomponents' profiles\n\nassessment-results\n\n\nSystem AR\n1 file\none, with a finding per objective\n\nThe plan of record answers 370 controls, and the 547 executable methods are read by the\nassessment plan through the components' profiles\n\n","assets/diagrams/73-join-assessment.svg":"\n Assessment-first (Option C): the chain from the rule to the claim and the result\n A chain of 6 steps, each drawn as one row per relationship, with the field that holds the pointer on the left and the field it resolves to on the right. Step 1, rule to check, is made of 2 relationships. no field in the assessment-plan containment to activities[].steps[].uuid in the assessment-plan. steps[].props[name=check].value in the assessment-plan, which holds SV-270747r1066730_rule, name match to no field in the nothing. Step 2, rule to control, is made of 1 relationship. activities[].related-controls.control-selections[].include-controls[].control-id in the assessment-plan, which holds sc-28, reference to controls[].id in the catalog. Step 3, check to runtime, is made of 1 relationship. assessment-platforms[].uses-components[].component-uuid in the assessment-plan, which holds 56270516-2673-4d4c-8d4f-52e4107f968d, reference to assessment-assets.components[].uuid in the assessment-plan. Step 4, runtime to claim, is made of 1 relationship. import-ssp.href in the assessment-plan, which holds #d381c885-4851-4931-828c-29bbb24fbaa3, reference to back-matter.resources[].uuid in the assessment-plan. Step 5, runtime to result, is made of 1 relationship. observations[].subjects[].subject-uuid in the assessment-results, which holds 61b3ec99-dfbe-4997-8a66-6f2279edb84b, reference to activities[].uuid in the assessment-plan. Step 6, result to control, is made of 1 relationship. findings[].target.target-id in the assessment-results, which holds sc-28_obj, reference to controls[].parts[objective].id in the catalog. Every value is rule 1, data at rest, as the six questions page encodes it for this approach.\n \n \n1. Rule to Check\nassessment-planno field\nassessment-planactivities[].steps[].uuid333ddd0f-22da-4c18-8bc3-98e808746bca\n\ninside\nassessment-plansteps[].props[name=check].valueSV-270747r1066730_rule\nnothing in OSCALno field\n\nby name\n2. Rule to Control\nassessment-planactivities[].related-controls.control-selections[].include-controls[].control-idsc-28\ncatalogthe framework catalogcontrols[].idsc-28\n\nresolves\n3. Check to Runtime\n\nassessment-planassessment-platforms[].uses-components[].component-uuid56270516-2673-4d4c-8d4f-52e4107f968d\nassessment-planassessment-assets.components[].uuid\n\nresolves\n4. Runtime to Claim\n\nassessment-planimport-ssp.href#d381c885-4851-4931-828c-29bbb24fbaa3\nassessment-planback-matter.resources[].uuidd381c885-4851-4931-828c-29bbb24fbaa3\n\nresolves\n5. Runtime to Result\n\nassessment-resultsobservations[].subjects[].subject-uuid61b3ec99-dfbe-4997-8a66-6f2279edb84b\nassessment-planactivities[].uuid61b3ec99-dfbe-4997-8a66-6f2279edb84b\n\nresolves\n6. Result to Control\nassessment-resultsfindings[].target.target-idsc-28_obj\ncatalogcontrols[].parts[objective].id\n\nresolves\n\n\nLegend\n\na document, or the fragment of one that holds\nthe field\n\nthe value, as the six questions page encodes\nit\n\na reference: the schema knows it is an\nidentifier and it resolves\n\na name match: equal by convention, and no\nschema can check it\n\ncontainment: nothing resolves, the child is\ninside the parent\n\nthe runtime, which reads OSCAL, executes, and\nwrites OSCAL\nEvery value is rule 1, data at rest, as\ndata/pattern-examples.json encodes it for this\napproach. The table above is the same chain\nwithout the values.\n\n\n","assets/diagrams/73-join-catalog.svg":"\n Catalog-first (Option A): the chain from the rule to the claim and the result\n A chain of 5 steps, each drawn as one row per relationship, with the field that holds the pointer on the left and the field it resolves to on the right. Step 1, rule to check, is made of 2 relationships. parts[assessment-method].props.TechnicalControlId in the catalog, which holds SV-270747r1066730_rule, name match to components[].title in the component-definition. implemented-requirements[].control-id in the component-definition, which holds UBTU-24-600090, reference to controls[].id in the catalog. Step 2, rule to control, is made of 2 relationships. maps[].sources[].id-ref in the mapping-collection, which holds UBTU-24-600090, reference to controls[].id in the catalog. maps[].targets[].id-ref in the mapping-collection, which holds sc-28, reference to controls[].id in the catalog. Step 3, check to runtime, is made of 1 relationship. components[].props.ConfigRuleId in the component-definition, which holds SV_270747R1066730_RULE, no join to no field in the nothing. Step 4, runtime to claim, is made of 2 relationships. implemented-requirements[].control-id in the system-security-plan, which holds UBTU-24-600090, reference to controls[].id in the catalog. by-components[].component-uuid in the system-security-plan, which holds 534b356b-0de1-48d4-8536-5d41ed717456, reference to system-implementation.components[].uuid in the system-security-plan. Step 5, claim to result, is made of 2 relationships. findings[].target.target-id in the assessment-results, which holds UBTU-24-600090_smt, reference to statements[].statement-id in the system-security-plan. related-observations[].observation-uuid in the assessment-results, which holds 28e28d31-4428-4ff5-8c9e-ea1198dfb552, reference to observations[].uuid in the assessment-results. Every value is rule 1, data at rest, as the six questions page encodes it for this approach.\n \n \n1. Rule to Check\ncatalogparts[assessment-method].props.TechnicalControlIdSV-270747r1066730_rule\ncomponent-definitioncomponents[].titleSV-270747r1066730_rule\n\nby name\ncomponent-definitionimplemented-requirements[].control-idUBTU-24-600090\ncatalogcontrols[].idUBTU-24-600090\n\nresolves\n2. Rule to Control\nmapping-collectionmaps[].sources[].id-refUBTU-24-600090\ncatalogcontrols[].idUBTU-24-600090\n\nresolves\nmapping-collectionmaps[].targets[].id-refsc-28\ncatalogthe framework catalogcontrols[].idsc-28\n\nresolves\n3. Check to Runtime\n\ncomponent-definitioncomponents[].props.ConfigRuleIdSV_270747R1066730_RULE\nnothing in OSCALno field\n\n\nnothing to resolve\n4. Runtime to Claim\n\nsystem-security-planimplemented-requirements[].control-idUBTU-24-600090\ncatalogcontrols[].idUBTU-24-600090\n\nresolves\nsystem-security-planby-components[].component-uuid534b356b-0de1-48d4-8536-5d41ed717456\nsystem-security-plansystem-implementation.components[].uuid\n\nresolves\n5. Claim to Result\nassessment-resultsfindings[].target.target-idUBTU-24-600090_smt\nsystem-security-planstatements[].statement-idUBTU-24-600090_smt\n\nresolves\nassessment-resultsrelated-observations[].observation-uuid28e28d31-4428-4ff5-8c9e-ea1198dfb552\nassessment-resultsobservations[].uuid\n\nresolves\n\n\nLegend\n\na document, or the fragment of one that holds\nthe field\n\nthe value, as the six questions page encodes\nit\n\na reference: the schema knows it is an\nidentifier and it resolves\n\na name match: equal by convention, and no\nschema can check it\n\nno join: there is no field on the far side\n\nthe runtime, which reads OSCAL, executes, and\nwrites OSCAL\nEvery value is rule 1, data at rest, as\ndata/pattern-examples.json encodes it for this\napproach. The table above is the same chain\nwithout the values.\n\n\n","assets/diagrams/73-join-component.svg":"\n Component-first (Option B): the chain from the rule to the claim and the result\n A chain of 6 steps, each drawn as one row per relationship, with the field that holds the pointer on the left and the field it resolves to on the right. Step 1, rule to check, is made of 2 relationships. checks[].rule-id in the component-definition, which holds ubtu24_data_at_rest_encrypted, composite key to components[].rules[].id in the component-definition. checks[].target-component-uuid in the component-definition, which holds 5ca997b3-bb3e-4c7a-8969-69ed44577d47, composite key to components[].uuid in the component-definition. Step 2, rule to control, is made of 2 relationships. implemented-requirements[].implementing-rules[].rule-id in the component-definition, which holds ubtu24_data_at_rest_encrypted, reference to components[].rules[].id in the component-definition. implemented-requirements[].control-id in the component-definition, which holds sc-28, reference to controls[].id in the catalog. Step 3, check to runtime, is made of 1 relationship. no field in the component-definition containment to components[].uuid in the component-definition. Step 4, runtime to claim, is made of 2 relationships. by-components[].implementing-rules[].rule-id in the system-security-plan, which holds ubtu24_data_at_rest_encrypted, reference to components[].rules[].id in the component-definition. by-components[].component-uuid in the system-security-plan, which holds 534b356b-0de1-48d4-8536-5d41ed717456, reference to system-implementation.components[].uuid in the system-security-plan. Step 5, runtime to result, is made of 2 relationships. observations[].assessment-check-id in the assessment-results, which holds SV-270747r1066730_rule, reference to checks[].id in the component-definition. observations[].subjects[].subject-uuid in the assessment-results, which holds 06297a03-cae0-414b-8332-2fc882f81aa1, reference to system-implementation.inventory-items[].uuid in the system-security-plan. Step 6, result to control, is made of 1 relationship. no field in the assessment-results no join to no field in the catalog. Every value is rule 1, data at rest, as the six questions page encodes it for this approach.\n \n \n1. Rule to Check\ncomponent-definitionchecks[].rule-idubtu24_data_at_rest_encrypted\ncomponent-definitioncomponents[].rules[].idubtu24_data_at_rest_encrypted\n\nhalf of the key\ncomponent-definitionchecks[].target-component-uuid5ca997b3-bb3e-4c7a-8969-69ed44577d47\ncomponent-definitioncomponents[].uuid5ca997b3-bb3e-4c7a-8969-69ed44577d47\n\nhalf of the key\n2. Rule to Control\ncomponent-definitionimplemented-requirements[].implementing-rules[].rule-idubtu24_data_at_rest_encrypted\ncomponent-definitioncomponents[].rules[].idubtu24_data_at_rest_encrypted\n\nresolves\ncomponent-definitionimplemented-requirements[].control-idsc-28\ncatalogthe framework catalogcontrols[].idsc-28\n\nresolves\n3. Check to Runtime\n\ncomponent-definitionno field\ncomponent-definitionthe validation componentcomponents[].uuidb3c8813d-d479-450a-8178-fbbf846faccf\n\ninside\n4. Runtime to Claim\n\nsystem-security-planby-components[].implementing-rules[].rule-idubtu24_data_at_rest_encrypted\ncomponent-definitioncomponents[].rules[].idubtu24_data_at_rest_encrypted\n\nresolves\nsystem-security-planby-components[].component-uuid534b356b-0de1-48d4-8536-5d41ed717456\nsystem-security-plansystem-implementation.components[].uuid\n\nresolves\n5. Runtime to Result\n\nassessment-resultsobservations[].assessment-check-idSV-270747r1066730_rule\ncomponent-definitionchecks[].idSV-270747r1066730_rule\n\nresolves\nassessment-resultsobservations[].subjects[].subject-uuid06297a03-cae0-414b-8332-2fc882f81aa1\nsystem-security-plansystem-implementation.inventory-items[].uuid\n\nresolves\n6. Result to Control\nassessment-resultsno field\ncatalogno field\n\n\nnothing to resolve\n\n\nLegend\n\na document, or the fragment of one that holds\nthe field\n\nthe value, as the six questions page encodes\nit\n\na reference: the schema knows it is an\nidentifier and it resolves\n\ndrawn twice where the key is composite and\nboth halves have to match\n\ncontainment: nothing resolves, the child is\ninside the parent\n\nno join: there is no field on the far side\n\nthe runtime, which reads OSCAL, executes, and\nwrites OSCAL\nEvery value is rule 1, data at rest, as\ndata/pattern-examples.json encodes it for this\napproach. The table above is the same chain\nwithout the values.\n\n\n","assets/diagrams/73-join-profile.svg":"\n Profile-first (Option D): the chain from the rule to the claim and the result\n A chain of 6 steps, each drawn as one row per relationship, with the field that holds the pointer on the left and the field it resolves to on the right. Step 1, rule to check, is made of 1 relationship. parts[assessment-method].links[rel=assessment-objective].href in the profile, which holds #sc-28_obj-ubtu-24-600090, reference to parts[assessment-objective].id in the profile. Step 2, rule to control, is made of 2 relationships. no field in the profile containment to alters[].control-id in the profile. alters[].control-id in the profile, which holds sc-28, reference to controls[].id in the catalog. Step 3, check to runtime, is made of 2 relationships. parts[assessment-method].props[name=language].value in the profile, which holds bash, no join to no field in the nothing. parts[assessment-method].props[name=evaluation].value in the profile, which holds exit-code, no join to no field in the nothing. Step 4, runtime to claim, is made of 1 relationship. no field in the profile no join to by-components[].description in the system-security-plan. Step 5, runtime to result, is made of 1 relationship. observations[].subjects[].subject-uuid in the assessment-results, which holds 06297a03-cae0-414b-8332-2fc882f81aa1, reference to system-implementation.inventory-items[].uuid in the system-security-plan. Step 6, result to control, is made of 1 relationship. findings[].target.target-id in the assessment-results, which holds sc-28_obj-ubtu-24-600090, reference to alters[].adds[].parts[].id in the profile. Every value is rule 1, data at rest, as the six questions page encodes it for this approach.\n \n \n1. Rule to Check\nprofileparts[assessment-method].links[rel=assessment-objective].href#sc-28_obj-ubtu-24-600090\nprofileparts[assessment-objective].idsc-28_obj-ubtu-24-600090\n\nresolves\n2. Rule to Control\nprofileno field\nprofilealters[].control-idsc-28\n\ninside\nprofilealters[].control-idsc-28\ncatalogthe framework catalogcontrols[].idsc-28\n\nresolves\n3. Check to Runtime\n\nprofileparts[assessment-method].props[name=language].valuebash\nnothing in OSCALno field\n\n\nnothing to resolve\nprofileparts[assessment-method].props[name=evaluation].valueexit-code\nnothing in OSCALno field\n\n\nnothing to resolve\n4. Runtime to Claim\n\nprofileno field\nsystem-security-planby-components[].description\n\n\nnothing to resolve\n5. Runtime to Result\n\nassessment-resultsobservations[].subjects[].subject-uuid06297a03-cae0-414b-8332-2fc882f81aa1\nsystem-security-plansystem-implementation.inventory-items[].uuid06297a03-cae0-414b-8332-2fc882f81aa1\n\nresolves\n6. Result to Control\nassessment-resultsfindings[].target.target-idsc-28_obj-ubtu-24-600090\nprofilealters[].adds[].parts[].idsc-28_obj-ubtu-24-600090\n\nresolves\n\n\nLegend\n\na document, or the fragment of one that holds\nthe field\n\nthe value, as the six questions page encodes\nit\n\na reference: the schema knows it is an\nidentifier and it resolves\n\ncontainment: nothing resolves, the child is\ninside the parent\n\nno join: there is no field on the far side\n\nthe runtime, which reads OSCAL, executes, and\nwrites OSCAL\nEvery value is rule 1, data at rest, as\ndata/pattern-examples.json encodes it for this\napproach. The table above is the same chain\nwithout the values.\n\n\n","assets/diagrams/75-stakeholders.svg":"\n One recommendation, three stakeholders, three paths\n One recommendation sits on the left. Three paths lead out of it, one for each stakeholder, and the three are drawn at the same size and weight because none is ranked above another. The publisher's path runs from a recommendation written once to a versioned, tailorable, citable publication. The implementer's path runs from desired state to a configuration engine to applied state. The assessor's path runs from a check to execution or examination to evidence to a finding. This is an organizing structure, not a thesis: all three needs are real and can be true at once, and the site's question is which questions each approach answers, for which stakeholder, and what it costs to fill the rest. No approach is marked on this drawing.\n \n \n\n\n\none\nrecommendation\nPUBLISHER\n\na recommendation\nwritten once\n\na versioned,\ntailorable,\ncitable publication\n\n\nIMPLEMENTER\n\ndesired state\n\na configuration\nengine\n\n\napplied state\n\n\nASSESSOR\n\na check\n\nexecution, or\nexamination\n\n\nevidence\n\n\na finding\n\n\n\n\n\n\n","assets/diagrams/76-satisfaction-6a-6b.svg":"\n One rule, two satisfaction assertions: the implementation claim and the assessment result\n One rule sits at the top and two paths lead out of it, side by side and drawn at the same size. On the left is question 6a, the implementation claim, which answers how the rule is satisfied. It lives in the system security plan and runs implemented-requirement, then statement, then by-component. It is narrative, it is standing design intent, it is asserted by the system owner, it is expressed per component, and it fails when the narrative is vague. On the right is question 6b, the assessment result, which answers whether the rule was satisfied, when, and on what. It lives in assessment results and runs observation, then finding, then objective-status. It is evidenced, it is a point in time, it is asserted by the assessor, it is expressed per subject of several types, and it fails when the evidence is stale or the subject is wrong. A table beneath the figure sets out those six differences in full. A rule carrying desired state has a binary satisfaction condition, while the implementation statement expects a narrative one, and conflating the two is the modelling error the figure exists to mark. Both can be populated from one rule without contradiction, and an approach that populates only one is not wrong; it is unfinished in a nameable place.\n \n \n\none rule\none requirement, one condition\n\n\n\n\n\n6a\nImplementation claim\n"how it is satisfied"\nsystem-security-plan\n\nimplemented-requirement\n\n\nstatement\n\n\nby-component\nnarrative . standing . per component\n\n\n\n6b\nAssessment result\n"whether it was satisfied"\nassessment-results\n\nobservation\n\n\nfinding\n\n\nobjective-status\nevidenced . point in time . per subject\nThe six differences, from plan section 2.1\n\n6a. Implementation claim\n6b. Assessment result\nquestion answered\nHow is this satisfied?\nWas it satisfied, when, on what?\n\nwho asserts it\nthe system owner\nthe assessor\n\ntime\nstanding design intent\na point in time\n\nform\nnarrative, arguable\nbinary or graded, evidenced\n\ngranularity\nper component\nper subject, of several types\n\nfails when\nthe narrative is vague\nthe evidence is stale, or the subject\nis wrong\n\n\n","data/corpus-stats.json":{"cited_from_position_paper":{"benchmark_requirements":563,"combined":867,"note":"These three figures are NOT computed from the corpora. They come from Technology_Specific_Hardening_Guidance_in_OSCAL.docx, an Easy Dynamics position paper, and must be attributed as such at every appearance per editorial rule 10.","regulatory_controls":304,"source":"Technology_Specific_Hardening_Guidance_in_OSCAL.docx, Easy Dynamics position paper"},"generated_from":"tfg-automated-assessments","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 assessment plan files","value":5},{"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","value":11},{"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","value":0},{"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?","raised_by":["Brian Ruf","Anca Sailer"],"slots":["1","3","6a","6b"]},{"name":"Normativity","number":2,"question":"Can the artifact express must versus may? Can an auditor treat it as binding?","raised_by":["Brian Ruf"],"slots":["1"]},{"name":"Requirement level","number":3,"question":"Can shall, should and may be represented at all?","raised_by":["Raised in discussion"],"slots":["1"]},{"name":"Hierarchy support","number":4,"question":"Does the model natively carry deep benchmark hierarchies?","raised_by":["CIS, via Anca Sailer"],"slots":["1"]},{"name":"Tailoring","number":5,"question":"Can an organization select, exclude and parameterize at scale?","raised_by":["Position paper"],"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?","raised_by":["Pirooz Javan"],"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?","raised_by":["Position paper"],"slots":["6a"]},{"name":"Response fidelity","number":8,"question":"Can a system owner answer per host or inventory item, or only per component?","raised_by":["Pirooz Javan"],"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?","raised_by":["Vikas Agarwal"],"slots":["1","2","3","5","6b"]},{"name":"Schema change cost","number":10,"question":"How many models change, and what is the realistic ratification timeline?","raised_by":["Fritz Kunstler"],"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?","raised_by":["Position paper"],"slots":["1"]},{"name":"Cross-framework use","number":12,"question":"Does this help someone operating under SOC 2, ISO and FedRAMP at the same time?","raised_by":["Pirooz Javan"],"slots":["2"]},{"name":"Inspectability","number":13,"question":"Can an operator see what a check does before running it on their systems?","raised_by":["Raised in discussion"],"slots":["3"]},{"name":"Prop dependence","number":14,"question":"How much meaning lives in namespaced props rather than core schema?","raised_by":["Brian Ruf"],"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?","raised_by":["All"],"slots":["1","2","3","4","5","6a","6b"]}],"note":"The fifteen evaluation criteria, verbatim from section 6 of the working group pre-read. The site authors none of them. The raised_by field is retained as provenance and is NOT rendered: per the Gate 7 decision, no personal name appears on any page.","source":"Hardening-Guidance-Options-Comparison.docx, Section 6, Draft evaluation criteria","source_status":"Offered for the group to ratify, amend, or reject. Reproduced unchanged."},"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":309023,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","sha256":"d69fd8b49feb6cf83de9cf00ba0c1ee1068f8afb7a4591116ab0b0beb86b0550"},{"approach":"assessment-first","bytes":314033,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-maester.json","sha256":"49d218b196333445dd67178dd58aba441fc596a28d2221c1c724d8eba460ee57"},{"approach":"assessment-first","bytes":291731,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","sha256":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d"},{"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":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":1940350,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","sha256":"4bb6d17f71a90122b0a2dbfaa560a5e6f80d57fdeaeb3d5c5288c79f5764e329"},{"approach":"assessment-first","bytes":1858871,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","sha256":"f5f821b671f8494ef155c6c2bcf5e17ae4792fcf200d1115a4c596caa2d03630"},{"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/main/"},"note":"The published OSCAL held in this repository, copied from the corpora by tools/copy_examples.py so the inventory can link to a document rather than only count it. Catalog-first is not here: it is published in a public repository and is linked there instead."},"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":"0ed6bfd853bdf97996b91081091962497e2360189c99afdcc20c0e5d6c86cbb1","catalog-first":"5fa8281a55085dbc46a4902084e3346ca0b81d51d5762b8ba0a46c58809a437e","component-first":"9d366a2413bfd65340030f71de9141ae2d0bb851114f282f03a90d1775416316","profile-first":"0709a97f7564fa0bb995019bac16c4d6de792f485bd55c004e7ceddc3f045d49"},"written_by":"tools/approach_pages.py"},"data/glossary.json":{"note":"The site's vocabulary. Every OSCAL term used anywhere on the site is defined here once, and every first use links back. The 'rule' entry exists because the word carries three incompatible meanings in this working group and nobody has fixed them in writing.","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, and a position paper"},{"usage":"An assessment objective on a control, with an executable assessment method beside it","who":"Profile-first, Option D"},{"usage":"Colloquially, the check code itself","who":"Used loosely across the working group, and flagged in the record by its own author"},{"usage":"An AWS Config rule: a deployable resource with its own parameters","who":"AWS Config, the product"}],"see_also":["check","control","desired state","requirement level"],"site_usage":"One technical requirement or recommendation, at a granularity finer than a control, without any claim about whether it is binding. This is a working definition adopted so that three comparable pages can be written. It is not a position on which view is correct.","status":"contested","term":"rule"},{"other_usages":[],"see_also":["rule","validation component","assessment platform"],"settled_note":"The separation of rule from check is recorded as settled item 5 in the pre-read. The stated reason is schema flexibility rather than semantics.","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, on the grounds that a vendor describes what can be configured rather than what must be","who":"Catalog-first, Option A"}],"see_also":["actual state","rule","implementation claim"],"site_usage":"The configuration a rule prescribes. Distinct from actual state, which is what the system currently has.","status":"contested","term":"desired state"},{"other_usages":[],"see_also":["desired state","assessment result"],"site_usage":"The configuration a system currently has, as observed. Distinct from desired state, which is what a rule prescribes.","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":"The link from a rule to the regulatory control it serves. Optional by design: a rule may serve several controls, one, or none. Without it you can record an observation but not a finding.","status":"settled","term":"link to a control"},{"other_usages":[{"usage":"Hardening guidance, used interchangeably","who":"General usage in the group"}],"see_also":["rule","hardening guidance"],"site_usage":"A published set of technology-specific hardening guidance. CIS Benchmarks, DISA STIGs, CISA SCuBA baselines, and vendor hardening guides.","status":"settled","term":"benchmark"},{"other_usages":[],"see_also":["benchmark","rule"],"site_usage":"Synonym for benchmark as used on this site. Technology-specific guidance on how to configure a product securely.","status":"settled","term":"hardening guidance"},{"other_usages":[],"see_also":["rule","normativity"],"site_usage":"Whether a statement is a shall, a should, or a may. OSCAL has no field for it. The pre-read's criterion 3 records it as absent from OSCAL entirely, an orthogonal gap affecting every option. Because there is no direct channel, location has become the proxy for expressing it.","status":"not-established","term":"requirement level"},{"other_usages":[],"see_also":["requirement level","rule"],"site_usage":"Whether an artifact expresses something binding that an auditor can hold a system to. The question underneath the location debate.","status":"contested","term":"normativity"},{"external_link":"https://github.com/OSCAL-Foundation/Component-Definition-Focus-Group/discussions/2","other_usages":[],"see_also":[],"set_aside":true,"site_usage":"A Component Definition construct that groups components and carries its own control-implementations, expressing joint satisfaction. Whether it should also exist in the SSP, or be removed, is an open question in the Component Definition Focus Group. The site notes it and takes no position.","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, Option B, component-rules.md"},{"usage":"A component enumerating the compliance frameworks a service has been validated against.","who":"Catalog-first, Option A, docs/COMPONENTS.md, under Future Considerations and not shipped"}],"see_also":["check","component"],"site_usage":"Two incompatible senses are in use and the site always says which one it means.","status":"contested","term":"validation component"},{"not_established_note":"Evidence register item 8: agreed on 17 July to be posted to the NIST OSCAL team. Not established whether posted; no response in the record.","other_usages":[],"see_also":["assessment asset","component","actor"],"site_usage":"In OSCAL, an element of assessment-assets that may reference components via uses-components. The authoritative distinction between an assessment platform, an assessment asset and a component has never been established.","status":"not-established","term":"assessment platform"},{"not_established_note":"Evidence register item 8.","other_usages":[],"see_also":["assessment platform","component","actor"],"site_usage":"In OSCAL, the assessment-assets container holding components and assessment-platforms. Its relationship to the two is not authoritatively defined.","status":"not-established","term":"assessment asset"},{"not_established_note":"Evidence register item 8, plus the unresolved component granularity question recorded against Option B.","other_usages":[],"see_also":["assessment platform","assessment asset","validation component"],"site_usage":"A part of a system. Used across the Component Definition, SSP, Assessment Plan and Assessment Results models with related but not identical meanings. Its boundary against assessment platform and assessment asset is not established, and neither is its granularity: whether a single config rule is a component, or the policy engine is.","status":"not-established","term":"component"},{"not_established_note":"Evidence register item 8: which of these constructs names the thing that runs a check has never been authoritatively established. The site inventories what each approach uses and does not resolve it.","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 site's name for question 5, what performs the check: whatever or whoever performs a check. OSCAL has no single construct for it. The word is the site's own label, adopted because naming the question after any one of the available constructs would have picked a side in the question below.","status":"not-established","term":"actor"},{"other_usages":[],"see_also":["assessment result","system security plan"],"site_usage":"An assertion by the system owner of how a control is satisfied. Standing design intent, narrative, arguable, made per component. Lives in the SSP as implemented-requirement, statement and by-component. Question 6a, how the system claims it meets the rule.","status":"settled","term":"implementation claim"},{"other_usages":[],"see_also":["implementation claim","observation","finding"],"site_usage":"An assertion by the assessor of whether a control was satisfied, when, and on what. A point in time, evidenced, binary or graded, made per subject. Lives in the AR as observation, finding and status. Question 6b, how an assessment records the outcome.","status":"settled","term":"assessment result"},{"other_usages":[],"see_also":["finding","assessment result","link to a control"],"site_usage":"An AR element recording something that was seen. Requires only uuid, description, methods and collected, and carries no reference to a control. Available whether or not a rule has a link to a control.","status":"settled","term":"observation"},{"other_usages":[],"see_also":["observation","link to a control","assessment result"],"site_usage":"An AR element recording a conclusion about whether an objective is satisfied. Requires a target whose type is closed to statement-id or objective-id, both control-derived. Unavailable to a rule with no link to a control.","status":"settled","term":"finding"},{"other_usages":[],"see_also":["link to a control","catalog"],"site_usage":"An OSCAL model, GA since 1.2, describing how one collection of controls relates to another. The only native mechanism for a third party to add a link to a control after publication. Its mapping-item type is closed to control and statement, so it reaches only rules that are modelled as controls.","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 element of an assessment plan's local-definitions, containing steps. The group has never defined what distinguishes an activity from a step; the question was asked three separate times on 19 June and not answered.","status":"not-established","term":"activity"},{"other_usages":[],"see_also":["activity","assessment plan"],"site_usage":"A child of an activity in an assessment plan. See the activity entry: the boundary between the two is not established.","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 the three stakeholders. Writes a requirement or recommendation once so many organizations can version, tailor and cite it, knowing nothing about any particular system.","status":"settled","term":"publisher"},{"other_usages":[],"see_also":["publisher","assessor","desired state"],"site_usage":"One of the three stakeholders. Wants that statement as desired state, in a form a configuration engine can apply.","status":"settled","term":"implementer"},{"other_usages":[],"see_also":["publisher","implementer","check"],"site_usage":"One of the three stakeholders. Wants a check they can run, or evidence dense enough to reach the same conclusion by reading.","status":"settled","term":"assessor"},{"other_usages":[],"see_also":["assessment method","finding","rule"],"site_usage":"A part on a control, named assessment-objective in the NIST catalogs, stating what an assessor determines. A finding can target its id. In the profile-first approach it is the rule, added to the control by the catalog or by a profile.","status":"settled","term":"assessment objective"},{"other_usages":[],"see_also":["assessment objective","executable assessment method","check"],"site_usage":"A part on a control, named assessment-method, carrying a method prop of EXAMINE, INTERVIEW or TEST. Catalog-first uses it to name the check; profile-first gives the TEST method a body and the props an executor needs to run it.","status":"settled","term":"assessment method"},{"other_usages":[{"usage":"A namespaced automation-script assembly on an implemented requirement","who":"An earlier draft the concept note itself sets aside"}],"see_also":["assessment method","check","profile"],"site_usage":"The profile-first construct: an assessment-method part with method TEST, namespaced props for platform, engine, evaluation rule, pass condition and timeout, and a script body in prose or in a back-matter resource. The namespace is a placeholder and the vocabulary has no owner, which is why the term is contested rather than settled.","status":"contested","term":"executable assessment method"}]},"data/joins.json":{"approaches":{"assessment-first":{"hops":[{"from":"rule","how":"containment","note":"The check is the first step, so nothing has to match. The step then names a check that resolves 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 tie sits on the activity, so there is no second document and no second identifier to keep in step.","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 plan names its platforms once, for every activity, so it cannot say which engine ran which 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":"One pointer for the whole plan. Where no plan of record exists the same 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 observation points back at the activity that ran. The thing observed is the thing planned.","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 the control objective, so a result reads against the framework with no 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 rule is an activity in the plan that assesses it, so it is introduced in the assessment layer and does not enter the implementation layer at all. Every step below starts from that uuid.","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}},"catalog-first":{"hops":[{"from":"rule","how":"name-match","note":"Two ties, opposite ways. The control names its check by title, which no schema can check; the check names its control by id, which resolves.","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 document of its own, written after both catalogs and by someone who owns neither.","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":"The prop names the rule the engine runs. The engine itself is nowhere in the content.","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 is against a component, not a host. A by-component takes no subject.","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 statement in the plan of record, which is what makes it an answer 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 rule is a control in a product catalog, in the same model and the same shape a regulatory control has. Every step below starts from that id.","slot":"1","value":"UBTU-24-600090"}},"component-first":{"hops":[{"from":"rule","how":"composite","note":"Both halves of the key sit on the check side. A rule id is unique only inside the component that declares it.","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":"Both sides in one document. The control implementation already ties component to control; naming the rule inside it is the proposal.","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 checks are inside the component that runs them. A second engine is a second 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 claim names the rule it rests on, so a reader gets from claim to check without leaving OSCAL.","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 names the check and the host, so two machines in one boundary can disagree and both be recorded.","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 result never states the control. It carries observations and no findings, so there is no status to hold one.","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 rule is a first-class entry on the component it configures, so it is introduced inside the document that describes the thing being hardened. Every step below starts from that id.","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},"profile-first":{"hops":[{"from":"rule","how":"reference","note":"Both parts sit in one alter, and the method links to the objective by id, inside one document.","pairs":[{"foreign":{"field":"parts[assessment-method].links[rel=assessment-objective].href","model":"profile","slot":"3","value":"#sc-28_obj-ubtu-24-600090"},"how":"reference","primary":{"field":"parts[assessment-objective].id","model":"profile","slot":"1","value":"sc-28_obj-ubtu-24-600090"}}],"to":"check"},{"from":"rule","how":"containment","note":"The parts are added to the control the alter names. Placing them is the tie, and no second identifier exists.","pairs":[{"foreign":{"field":"no field","model":"profile","slot":"1"},"how":"containment","primary":{"field":"alters[].control-id","model":"profile","slot":"2","value":"sc-28"}},{"foreign":{"field":"alters[].control-id","model":"profile","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":"The props name an engine by a token and say how to judge its result. The executor that honours them is outside OSCAL.","pairs":[{"foreign":{"field":"parts[assessment-method].props[name=language].value","model":"profile","slot":"3","value":"bash"},"how":"none","primary":{"field":"no field","model":"nothing","slot":"5"}},{"foreign":{"field":"parts[assessment-method].props[name=evaluation].value","model":"profile","slot":"3","value":"exit-code"},"how":"none","primary":{"field":"no field","model":"nothing","slot":"5"}}],"to":"runtime"},{"from":"runtime","how":"none","note":"The run writes no response. The plan of record is untouched by design, so nothing joins the check to the owner's claim.","pairs":[{"foreign":{"field":"no field","model":"profile","slot":"5"},"how":"none","primary":{"field":"by-components[].description","model":"system-security-plan","slot":"6a"}}],"to":"claim"},{"from":"runtime","how":"reference","note":"The observation names the host and carries the raw output as evidence, so two machines behind one component can disagree.","pairs":[{"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","value":"06297a03-cae0-414b-8332-2fc882f81aa1"}}],"to":"result"},{"from":"result","how":"reference","note":"The finding targets the objective the profile added, so a result reads against the framework with no plan of record.","pairs":[{"foreign":{"field":"findings[].target.target-id","model":"assessment-results","slot":"6b","value":"sc-28_obj-ubtu-24-600090"},"how":"reference","primary":{"field":"alters[].adds[].parts[].id","model":"profile","slot":"1","value":"sc-28_obj-ubtu-24-600090"}}],"to":"control"}],"introduced":{"field":"alters[].adds[].parts[].id","model":"profile","note":"The rule is an assessment objective part, added to the framework control by a profile. Every step below starts from that part id.","slot":"1","value":"sc-28_obj-ubtu-24-600090"}}},"how":[{"key":"containment","label":"Containment","meaning":"One is inside the other, so there is no key to match and nothing to dereference."},{"key":"reference","label":"Reference","meaning":"A field holds an identifier the schema knows is an identifier, and it resolves."},{"key":"name-match","label":"Name match","meaning":"Two strings are equal by convention. It holds where the two agree and breaks silently where they do not, and no schema can check it."},{"key":"composite","label":"Composite key","meaning":"Two fields have to match together. Either one alone resolves to the wrong thing or to nothing."},{"key":"none","label":"No join","meaning":"There is no field on either side. The relation has to be recovered by walking through something else, or it is simply not there."}],"intro":"The chain starts where the rule is introduced and runs to the claim and the result. What a step costs is how many relationships it is made of and how each one resolves.","note":"The six questions are answered one at a time, which hides the thing that decides whether the set works: what joins one answer to the next. This is the chain from the moment the rule is introduced to the moment something records that it was met, with every foreign key and the primary key it resolves to. Every literal is one of the two running rules as the six questions page encodes it, so the four chains can be read against each other; tools/verify.py fails the build if a value here is not in that encoding.","stages":[{"key":"rule","label":"Rule","meaning":"where the rule is introduced","slot":"1"},{"key":"control","label":"Control","meaning":"the regulation it serves","slot":"2"},{"key":"check","label":"Check","meaning":"how it is tested","slot":"3"},{"key":"runtime","label":"Runtime","meaning":"what executes the check","slot":"5"},{"key":"claim","label":"Claim","meaning":"the system's statement that it holds","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":"What joins one answer to the next"},"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/main/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/main/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/main/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/main/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/main/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":309023,"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":314033,"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":291731,"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":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":1940350,"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":1858871,"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}},{"document":{"href":"examples/profile-first/executable-assessment-methods.md","label":"Executable Assessment Methods, a concept note, September 2026"},"files":[],"full_name":"Option D","key":"profile-first","name":"Profile-first","note":"No OSCAL document has been published for this approach. What exists is a concept note, and the encodings on the six questions page are the site's own rendering of the shape that note proposes.","option":"Option D","repo":null,"rollup":null,"root":null,"totals":{}}]},"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."}],"profile-first":[{"content":"{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 }\n ]\n }\n ]\n }\n }\n}","focus":[[11,15]],"focus_key":"name=assessment-objective","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"An assessment objective part, added to the framework control by a profile. The requirement is the part's prose, and a value is a parameter the same add declares and sets."},{"content":"{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"ia-5.1\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"parts\": [\n {\n \"id\": \"ia-5.1_obj-ubtu-24-400320\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[20,24]],"focus_key":"name=assessment-objective","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"An assessment objective part, added to the framework control by a profile. The requirement is the part's prose, and a value is a parameter the same add declares and sets."}]},"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."}],"profile-first":[{"content":"{\n \"profile\": {\n \"imports\": [\n {\n \"href\": \"./NIST_SP-800-53_rev5_catalog.json\",\n \"include-controls\": [\n {\n \"with-ids\": [\n \"sc-28\",\n \"ia-5.1\"\n ]\n }\n ]\n }\n ],\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 }\n ]\n },\n {\n \"control-id\": \"ia-5.1\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"parts\": [\n {\n \"id\": \"ia-5.1_obj-ubtu-24-400320\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[19,19],[34,34]],"focus_key":"control-id","label":"Both rules and their control ties","rule":"both","shows":"The placement is the tie. The profile imports the framework catalog and alters the control by id, and the parts go inside the alter, so the only identifier in play is the control's own."}]},"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."}],"profile-first":[{"content":"{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 \"id\": \"sc-28_asm-ubtu-24-600090\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270747r1066730_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#sc-28_obj-ubtu-24-600090\"\n }\n ],\n \"prose\": \"```bash\\nlsblk -rno TYPE | grep -q '^crypt$'\\n```\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[16,58]],"focus_key":"name=assessment-method","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"An assessment method part beside the objective, with method TEST, a script body in its prose, five namespaced props saying how to run and judge it, and a link to the objective it tests."},{"content":"{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"ia-5.1\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"parts\": [\n {\n \"id\": \"ia-5.1_obj-ubtu-24-400320\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n },\n {\n \"id\": \"ia-5.1_asm-ubtu-24-400320\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270732r1066685_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#ia-5.1_obj-ubtu-24-400320\"\n }\n ],\n \"prose\": \"```bash\\nminlen=$(grep -E '^\\\\s*minlen' /etc/security/pwquality.conf | cut -d= -f2 | tr -d ' ')\\ntest \\\"${minlen:-0}\\\" -ge \\\"$password_min_length\\\"\\n```\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[25,67]],"focus_key":"name=assessment-method","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"An assessment method part beside the objective, with method TEST, a script body in its prose, five namespaced props saying how to run and judge it, and a link to the objective it tests."}]},"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."}],"profile-first":[{"content":"{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 \"id\": \"sc-28_asm-ubtu-24-600090\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270747r1066730_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#sc-28_obj-ubtu-24-600090\"\n }\n ],\n \"prose\": \"```bash\\nlsblk -rno TYPE | grep -q '^crypt$'\\n```\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[25,29]],"focus_key":"name=platform","label":"What the checks run against","rule":"both","shows":"Whatever component the platform prop matches, by convention."},{"content":"{\n \"system-security-plan\": {\n \"system-implementation\": {\n \"components\": [\n {\n \"uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"description\": \"Ubuntu 24.04 LTS as a component of the system.\",\n \"status\": {\n \"state\": \"operational\"\n }\n }\n ],\n \"inventory-items\": [\n {\n \"uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"description\": \"Application host 1, running Ubuntu 24.04 LTS.\",\n \"implemented-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[15,25]],"focus_key":"inventory-items","label":"The component it matches, in the plan of record","rule":"subject","shows":"The executor matches the method's platform against a component and runs the body on the inventory items that implement it. Nothing on either carries a CPE."}]},"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."}],"profile-first":[{"content":"{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 \"id\": \"sc-28_asm-ubtu-24-600090\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270747r1066730_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#sc-28_obj-ubtu-24-600090\"\n }\n ],\n \"prose\": \"```bash\\nlsblk -rno TYPE | grep -q '^crypt$'\\n```\"\n }\n ]\n }\n ]\n },\n {\n \"control-id\": \"ia-5.1\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"parts\": [\n {\n \"id\": \"ia-5.1_obj-ubtu-24-400320\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n },\n {\n \"id\": \"ia-5.1_asm-ubtu-24-400320\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270732r1066685_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#ia-5.1_obj-ubtu-24-400320\"\n }\n ],\n \"prose\": \"```bash\\nminlen=$(grep -E '^\\\\s*minlen' /etc/security/pwquality.conf | cut -d= -f2 | tr -d ' ')\\ntest \\\"${minlen:-0}\\\" -ge \\\"$password_min_length\\\"\\n```\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[20,50],[87,117]],"focus_key":"props","label":"What the run reads: the methods on the resolved profile","rule":"assessor-in","shows":"The methods the run is handed, each saying which engine runs it and how to judge the result."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for sc-28_obj-ubtu-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj-ubtu-24-600090\",\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 ia-5.1_obj-ubtu-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj-ubtu-24-400320\",\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 \"description\": \"The executable method ran on the host and exited 0.\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"relevant-evidence\": [\n {\n \"description\": \"Exit code 0, with standard output and standard error as the executor captured them.\"\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 \"description\": \"The executable method ran on the host and exited 0.\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"relevant-evidence\": [\n {\n \"description\": \"Exit code 0, with standard output and standard error as the executor captured them.\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[11,11],[27,27],[53,57],[73,77]],"focus_key":"target-id, relevant-evidence","label":"What the run produces: the finding and its observation","rule":"assessor-out","shows":"The finding targets the objective the profile added, and the observation names the host and carries the script's output as evidence."}]},"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."}],"profile-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 \"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}","focus":[[8,14]],"focus_key":"by-components","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A by-component response in the SSP, against the framework control, exactly as it would be without the approach. Nothing on it names the objective the check tested."},{"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 \"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}","focus":[[8,14]],"focus_key":"by-components","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A by-component response in the SSP, against the framework control, exactly as it would be without the approach. Nothing on it names the objective the check tested."}]},"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."}],"profile-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for sc-28_obj-ubtu-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj-ubtu-24-600090\",\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 \"description\": \"The executable method ran on the host and exited 0.\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"relevant-evidence\": [\n {\n \"description\": \"Exit code 0, with standard output and standard error as the executor captured them.\"\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 objective the profile added, over an observation that names the host and carries the output."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for ia-5.1_obj-ubtu-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj-ubtu-24-400320\",\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 \"description\": \"The executable method ran on the host and exited 0.\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"relevant-evidence\": [\n {\n \"description\": \"Exit code 0, with standard output and standard error as the executor captured them.\"\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 objective the profile added, over an observation that names the host and carries the output."}]}},"note":"Our own encodings. Two rules, written in all four 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 four columns is the modelling. Ubuntu because both rules are published for it, by DISA, and a reader can check them."}},"data/provenance.json":{"corpora_root":"../../tfg-automated-assessments","generated_at":"2026-08-22T18:46:12+00:00","snippet_count":34,"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-08-22T17:17:36+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":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","sha256_of_content":"60c8183fb14d09b5f27513b84f394bf8a48670eadaf2f73fd834bc7300011240","sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+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":"49d218b196333445dd67178dd58aba441fc596a28d2221c1c724d8eba460ee57","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-08-22T17:17:36+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":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"01c9afa2b4ee716f8534f4a2f12777d7202d741c06a7d5182619ca8f3afbc3fe","sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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":1084,"extracted_at":"2026-08-22T17:17:36+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"c07765f9cca980bb8a30cfec768b885b607686df348a53618ab6099994e9a6e7","sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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":14934,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-rules-md","language":"markdown","pointer":"$","sha256_of_content":"799c42a95dae88268f20e09566342953a98c580bdda0cadf5197ebf4026d5e31","sha256_of_source_file":"630c45450f3cea476cd9a7df7da1f49e22f854832907521656191714eb9bd57c","slot":"meta","source":"IBM/Automated-assessment.md","title":"IBM's proposed rule and check assemblies"},{"approach":"component-first","bytes":410,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-open-questions","language":"markdown","pointer":"$","sha256_of_content":"0a03c3d3f2910ae28141c1a2de1771455102cf284bfb78a790e88a82f3765eaa","sha256_of_source_file":"630c45450f3cea476cd9a7df7da1f49e22f854832907521656191714eb9bd57c","slot":"meta","source":"IBM/Automated-assessment.md","title":"IBM's open questions"},{"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"}]},"data/questions.json":{"intro":"Nothing here is a proposal. Where the site has a fact that bears on a question, the fact is stated and the question is left open. Most of what is unsettled is about OSCAL rather than about any one approach, which is why the first section is the longest.","note":"The open questions, in five sections: what is unsettled about OSCAL itself, then what is unsettled about each approach. Each is one line with the reasoning behind it. Questions reproduced from a source document keep that document's wording, including its errors, and are marked with where they came from, because rewriting someone else's question is a way of answering it.","sections":[{"intro":"Gaps in the models themselves. None is answered by choosing an approach, and each changes what all four can express.","key":"all","label":"Across all four approaches","questions":[{"id":"xccdf","q":"Should OSCAL carry this content at all, when XCCDF already does?","why":"Asked on 20 March and never closed. Two answers are on the record, that XCCDF is obsolete and that a checklist item is not a control, and neither settled it. If the answer is that OSCAL should reference XCCDF rather than restate it, every approach on this site changes shape."},{"id":"rule-metadata","q":"Where does the metadata that describes a rule go?","why":"Every STIG rule carries a severity and a weight; every CIS recommendation carries a rationale and says whether its check is automated or manual. No released OSCAL model has a field for any of them, so AWS carries severity as a namespaced property on all 452 of its controls and the STIG conversion carries it in DISA's. Which of these belong to a rule, and whether the answer is a field, a shared namespace or a property per publisher, is unasked."},{"id":"remediation","q":"Where does remediation land?","why":"194 of 194 STIG rules ship a fix and 312 of 312 CIS recommendations ship a remediation, and no approach has a field for it. Catalog-first links out to documentation on all 452 controls, assessment-first writes a second step marked remediate, component-first does not carry it. OSCAL's own remediation lives in the plan of action and milestones, which answers what to do about this finding rather than how anyone fixes this condition."}]},{"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":"The working assumption is that a system holds one plan of record answering a profile that merges every catalog it is held to. What is being seen in practice is one plan of record per catalog. The two are not a matter of taste: they produce different file counts, a different place for a response to live, and a different answer to whether a benchmark outcome sits beside a regulatory one. The worked scenario on this site assumes convergence, which is why its figure is 18 files."},{"id":"requirement-level","q":"If OSCAL gained a field for requirement level, how much of this disagreement would be left?","why":"The pre-read's criterion 3 records that shall, should and may cannot be expressed in OSCAL at all, so placement is the only channel left for asserting that something is required. This approach is placement: a benchmark's recommendations become controls beside a framework's controls in one merged profile, and nothing on either says which is a shall and which is a may. Nobody has been asked how much of the disagreement would survive the field."},{"id":"control-type","q":"Should a control declare its type, so a regulatory control and a technical hardening control can be told apart?","why":"Once hardening guidance is published as a catalog, both kinds sit in the same merged profile and are answered in the same plan of record. Nothing on a control says which of the two it is, so a plan cannot report its regulatory coverage separately from its hardening coverage, and a reader cannot tell whether a gap is a missed regulation or a missed setting. The question above asks the same thing about level rather than about kind."},{"id":"paper-cat-1","q":"How should benchmark profiles compose with regulatory profiles when the combined control count approaches ~867+?","verbatim":"the position paper submitted to the working group","why":"Follows directly from the question above. If the merge happens, the profile it produces is large enough that resolution becomes the engineering problem."},{"id":"paper-cat-2","q":"Where do Benchmark results get captured: SSP Control implementations or ARs? How will tools manage this?","verbatim":"the position paper submitted to the working group","why":"The site's own answer is that a response is a by-component in the plan of record and a result is an assessment result, and that both exist. Which one a benchmark outcome belongs in is not settled."}]},{"intro":"The rule sits on the component it configures. Four of these are the proposal's own open questions, reproduced from it.","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":"There is no mapping collection in this approach: the tie is inline, so whoever holds it has their document edited by the mapping provider. Two documents could hold it and they belong to different parties. The software definition carries the rules and is the guidance author's; the validation definition carries the checks and is the engine provider's. The tie could sit on either, or on both, and nothing published settles it. The stakeholder table on the component-first page marks the type as unsettled for exactly this reason."},{"id":"proposal-1","q":"AP - Assessment Platform usage? make it optional?","verbatim":"the component-first proposal document","why":"Reproduced from the proposal's own list of open questions, in its own words. All four are about what runs a check and how it is tied to what it ran, which is the same thing the NIST team was asked on 17 July."},{"id":"proposal-2","q":"AP - Is assessment component sufficient or we need assessment platform also?","verbatim":"the component-first proposal document","why":"The proposal asks this of itself, and the three corpora answer it three ways, which is what makes it a question about OSCAL rather than about this approach."},{"id":"proposal-3","q":"AP - How is assessment asset associated to the tasks or activities? currently there seems to be no way.","verbatim":"the component-first proposal document","why":"The join between what runs and what it was told to run. The proposal records that there is no way to write it."},{"id":"proposal-4","q":"In AR there are multiple assessment assests defined. How is an obesrvation associated with an assessment asset?","verbatim":"the component-first proposal document","why":"The same gap on the result side: several assets are declared and nothing ties an observation to the one that produced it."},{"id":"paper-comp-1","q":"If Benchmarks are published as CDefs for software components and service providers publish CDefs for their software, can an SSP have multiple OSCAL components describing the system component?","verbatim":"the position paper submitted to the working group","why":"A system runs software from several vendors and is held to several benchmarks, so the plan of record would import definitions from both, and nothing says how they combine."},{"id":"paper-comp-2","q":"If Benchmark CDefs contain desired state, do the values get updated to actual state in the SSP?","verbatim":"the position paper submitted to the working group","why":"This is the desired-state risk the site records against this approach: rules describe how a component should be configured, and a plan of record describes how the system is."},{"id":"paper-comp-3","q":"What portion of the benchmark context gets pulled into the SSP? If not all, how will data get filtered out when importing a CDef into an SSP component?","verbatim":"the position paper submitted to the working group","why":"A thousand-page guide is mostly prose. What of it belongs in a plan of record, and what a tool should drop on import, is unanswered."},{"id":"paper-comp-4","q":"How could CDefs support the tailoring needs of benchmarks?","verbatim":"the position paper submitted to the working group","why":"The tailoring question, asked of this approach. It has a param on the rule and set-parameters on the control implementation, which is more than the assessment approach has and less than a profile."},{"id":"paper-comp-5","q":"Should ARs or APs support import of CDef with Benchmark context?","verbatim":"the position paper submitted to the working group","why":"The site's own encoding says yes for the assessment plan: the definition is carried in as an asset and the checks travel with it. Whether that is the intended route is the question."}]},{"intro":"The rule is an activity in an assessment plan. One question is on the record against this approach, and it is about tailoring.","key":"assessment-first","label":"Assessment-first","questions":[{"id":"paper-ap-1","q":"How should AP-based benchmarks handle tailoring needs that only the catalog/profile model natively supports?","verbatim":"the position paper submitted to the working group","why":"The same question as where a parameter goes, asked of this approach by name. An activity and a step have no parameter, so a value lives in the requirement text and tailoring means editing the sentence."}]},{"intro":"The rule and the check are parts on a control. What is unsettled is who may put code there, who owns the vocabulary that runs it, and what the executor matches against.","key":"profile-first","label":"Profile-first","questions":[{"id":"executable-catalogs","q":"Who may put executable code on a control, and who signs it?","why":"A catalog or profile carrying executable methods is code, and an executor that resolves a profile from a URL and runs what it finds has installed a remote code path into every assessed system. The concept note asks for pinned hashes on every rlink, signed catalogs and profiles, an executor that refuses anything unverified, and read-only checks with remediation in a part of its own. None of that is agreed anywhere yet, and nothing in OSCAL distinguishes a part that describes from a part that executes."},{"id":"vocabulary-owner","q":"Who owns the vocabulary of platform, language, evaluation and pass condition?","why":"The five props carry everything an executor needs, and every one of them is a convention in a placeholder namespace. The note proposes Metaschema external constraints to hold the enumeration, the way FedRAMP holds its own vocabulary without forking the model, and names no body to publish them. Until one does, two vendors can ship two incompatible checks for one control and the profile author picks."},{"id":"platform-match","q":"What on a system security plan component does the platform CPE match against?","why":"The note matches the platform prop against the component in the plan of record, the way XCCDF matches its platform element. No field on an OSCAL component or inventory item carries a CPE, so the match is made on a convention the note leaves open, and it says itself that a plain token may serve as well. Which host a check runs on is decided wherever that convention is decided."},{"id":"profile-added-objective","q":"Does a finding resolve to an objective that only a profile added?","why":"The mechanism rests on findings targeting an objective id, and the objective exists only in the resolved profile: the catalog it imports has never heard of it. A consumer reading the result against the catalog alone, or against a profile resolved without the tool vendor's additions, finds no such objective. Whether every result reader resolves the profile first is not established."},{"id":"catalog-route-tie","q":"When a guide ships as a catalog with its own checks, what ties its objectives to the framework?","why":"The note answers the framework case by placement: a profile adds the check to the framework control, and the placement is the tie. Where the guide is its own catalog, as a benchmark with its own scripts would be, the finding targets the guide's objective and nothing in the note reaches the framework. A mapping collection reaches controls and statements, not parts, so that route is the one catalog-first already has and no wider."},{"id":"check-versions","q":"Is a changed check a new version of the catalog it sits in?","why":"The note accepts the coupling: a changed check is a new profile version, and a catalog that ships checks changes whenever one of them does. A benchmark already carries that coupling in its source material. A framework catalog does not, and the approach keeps it out of one by putting the checks in a profile, so the question is only open for the catalog route."}]}]},"data/quotes.json":{"note":"Every quotation gathered from the record. RETAINED AS PROVENANCE AND NO LONGER RENDERED. Per the Gate 7 decision the site carries no quotations at all, and characterizations trace to a JSON pointer into a shipped file or to a cited source document. The file is kept because deleting it would destroy the record of what was said and where, which a later session may need. tools/verify.py --quotes now asserts that no page renders any of it.","quotes":[{"affiliation":"IBM","context":"The warrant for treating rule and check as separate questions. Recorded by the group as already settled.","date":null,"id":"anca-rule-check-separation","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 3, settled item 5","speaker":"Anca Sailer","text":"a rule, which is unique, can be associated with a check ID in Ansible, with a check ID in Terraform, with a check ID in OPA, with a check ID in OpenSCAP. The reason is not semantics, the reason is schema flexibility."},{"affiliation":"IBM","context":"The rationale for proposing new assemblies rather than props.","date":null,"id":"anca-check-first-class","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B","speaker":"Anca Sailer","text":"Instead of abusing a property in order to do that, check is a first class citizen."},{"affiliation":"IBM","context":"Why CIS is drawn to the catalog. A structural requirement rather than a semantic argument.","date":"2026-03-20","id":"anca-cis-hierarchy","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A","speaker":"Anca Sailer","text":"their main complaint was the hierarchical structure. They wanted a native support for that hierarchy. And they found it in the catalog, and that's the reason why they go there. It is the CIS need for the hierarchy."},{"affiliation":"IBM","context":"One of three unreconciled statements of purpose.","date":"2026-03-20","id":"anca-purpose","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 4","speaker":"Anca Sailer","text":"The sufficient support in OSCAL so that we can communicate with each other, not to impose the processes on each other."},{"affiliation":"IBM","context":"The core claim for the component-first approach.","date":null,"id":"vikas-cdef-automation","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B","speaker":"Vikas Agarwal","text":"The component definition is used to specify how a component is implementing a control, and that is for documentation purpose. But that doesn't help me automate my processes. What we have done is, we have put that fine-grained rules inside that component definition, so that we can also automate."},{"affiliation":"IBM","context":"The clearest statement anywhere in the corpus of who authors question 1 versus question 3.","date":null,"id":"vikas-persona-split","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B","speaker":"Vikas Agarwal","text":"The rules are being created by the software component vendors. As a software vendor, I define all my rules. As a tool vendor, I define all my checks. And in the SSP and AP, I just pull the content."},{"affiliation":"IBM","context":"The instance-versus-library objection to the assessment-first approach.","date":null,"id":"vikas-instance-vs-library","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option C, objections","speaker":"Vikas Agarwal","text":"the assessment plan is for your specific instance when you are assessing it, and it will change from assessment to assessment. If I can generalize it and put it outside so that I can just refer it to the assessment plan and use it, that probably would be a better way."},{"affiliation":"IBM","context":"IBM's own statement of the schema change surface.","date":null,"id":"vikas-affects-all-models","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B","speaker":"Vikas Agarwal","text":"It's affecting all models, right? Starting from component definition to SSP to plan to results to POAM."},{"affiliation":"AWS","context":"The core claim for the catalog-first approach.","date":null,"id":"fritz-catalogs-for-requirements","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A","speaker":"Fritz Kunstler","text":"My perspective is that the catalogs should be used for basically any sort of control requirement, whether it's technical or governance related. I think the model serves both purposes effectively, and we should ideally use it instead of creating something new or similar with different names."},{"affiliation":"AWS","context":"The clearest statement of the view that a hardening rule is a requirement.","date":null,"id":"fritz-standard-setter","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A","speaker":"Fritz Kunstler","text":"AWS is the standard setter or the expert on how the services should be secured, the requirements for securing those services according to best practices, and those requirements are delivered in the form of controls. And that's what AWS calls them."},{"affiliation":"AWS","context":"Why the AWS catalog ships with no control tie. The stated reason question 2 is empty rather than absent.","date":null,"id":"fritz-stripped-props","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A","speaker":"Fritz Kunstler","text":"I intentionally stripped this out before I published it, because I didn't want to apply anything until we landed on a decision here."},{"affiliation":"AWS","context":"On the label applied to component-definition rule content. Supports the capability-statement view.","date":null,"id":"fritz-possible-state","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Fritz Kunstler","text":"Well, not desired state. It's possible state, I would say."},{"affiliation":"AWS","context":"The schema change cost objection, which is criterion 10.","date":null,"id":"fritz-cost-of-change","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Fritz Kunstler","text":"We have overwhelming evidence that changing OSCAL is unusually hard and time-consuming. The alternative is that we will be talking about this next year."},{"affiliation":"AWS","context":"On whether vendors must publish catalogs.","date":null,"id":"fritz-vendors-need-not","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A, unresolved","speaker":"Fritz Kunstler","text":"No, they don't. It's not that they must. My opinion is that yes, they can and should do that. But could you do it a different way? Yeah, you could do it a different way."},{"affiliation":null,"context":"The normativity objection, and the crux of what kind of thing a rule is.","date":null,"id":"brian-not-normative","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Brian Ruf","text":"there's nothing in this component definition that says you must do it this way. It may have the term rule in AWS's terminology, but it's not a rule from an auditor's perspective."},{"affiliation":null,"context":"One of three unreconciled statements of purpose.","date":"2026-03-20","id":"brian-not-wrong","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 4","speaker":"Brian Ruf","text":"I don't think that any of these are wrong. They're different ways to come at the same problem with different goals in mind."},{"affiliation":null,"context":"One of three unreconciled statements of purpose.","date":"2026-03-20","id":"dave-single-way","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 4","speaker":"Dave Waltermire","text":"Our goal should be to have a single, opinionated way of supporting all of the use cases that we're talking about."},{"affiliation":null,"context":"Unanswered since 20 March. If the answer is the shim, every option changes shape.","date":"2026-03-20","id":"dave-xccdf","source_document":"Hardening-Guidance-Options-Comparison.docx, A prior question that has never been answered","speaker":"Dave Waltermire","text":"Why are we trying to represent a checklist in OSCAL when we have something like XCCDF, which CIS and DISA already support? [...] We shouldn't be trying to make OSCAL the Uber data model to end all data models. [...] Do we provide, effectively, full-throated support for checklists, which is where this is kind of leaning, versus do we provide a lightweight shim in OSCAL that provides the connectivity to that external thing?"},{"affiliation":null,"context":"Independent validation of the assessment-first approach.","date":"2026-03-13","id":"dave-as-intended","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option C","speaker":"Dave Waltermire","text":"This looks right. This looks like you're using it as it was intended."},{"affiliation":null,"context":"The fit objection to the component-first approach.","date":null,"id":"banghart-not-meant","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Steven Banghart","text":"you're using component definition in a way that it wasn't meant to be used. You've successfully used it in this way. But we could make it better."},{"affiliation":"Easy Dynamics","context":"The core claim for the assessment-first approach.","date":"2026-03-13","id":"pranav-assessment-start","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option C","speaker":"Pranav Kothare","text":"We eliminate the idea of using catalogs and profiles because they just sort of play a part in defining the requirements for the compliance process. The real assessment piece should start from the assessment plan."},{"affiliation":"Easy Dynamics","context":"How the assessment-first approach indicates a check.","date":"2026-03-20","id":"pirooz-first-class-oscal","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option C","speaker":"Pirooz Javan","text":"Everything you're seeing here is first-class OSCAL. No props, no anything. We look at something like 2.1 as being an assessment plan with activities, eight steps in 2.1. The only prop you have to add is a context to say, go automate the assessment for this activity."},{"affiliation":"Easy Dynamics","context":"The response-fidelity objection, which is criterion 8 and question 4. Applies to any option that shifts requirements left.","date":null,"id":"pirooz-response-fidelity","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option B, objections","speaker":"Pirooz Javan","text":"the AP has the subjects which are four ways where SSPs only allow you to respond by components. I think that's a limitation we also need to discuss."},{"affiliation":"Easy Dynamics","context":"Why resolving the question matters, and who bears the cost of not resolving it.","date":"2026-03-20","id":"pirooz-adoption-confusion","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 2","speaker":"Pirooz Javan","text":"When a group like CIS, who's very interested in adopting OSCAL, is hearing that their benchmark should be in catalogs from one person, in component definitions from another group, and in assessment plans from us, it creates a lot of confusion and concern around adopting OSCAL when the folks that are closest to it can't agree on methodologies."},{"affiliation":"Easy Dynamics","context":"The authoring burden objection, which is criterion 6.","date":null,"id":"pirooz-authoring-burden","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 5, Option A, objections","speaker":"Pirooz Javan","text":"for a CIS that has 100 hardening guides, converting each of those to four or five different OSCAL files."},{"affiliation":"Easy Dynamics","context":"The capability-statement view of what a rule is. Note: this is an Easy Dynamics document and must be attributed as advocacy per editorial rule 10.","date":null,"id":"deck-may-be-configured","source_document":"Where-does-desired-state-go.pptx, slide 3","speaker":null,"text":"Software vendors secure configuration guidance/recommendations for how their software “may” be configured to meet regulatory requirements should do so in CDefs"},{"affiliation":"Easy Dynamics","context":"The statement that the control tie is optional by design. The warrant for question 2's treatment.","date":null,"id":"deck-optional-mapping","source_document":"Where-does-desired-state-go.pptx, slide 3","speaker":null,"text":"Not all implementations in a Cdef are required to map back to a control, but the option is there. This enables desired state configurations to support regulatory control responses in an SSP."},{"affiliation":"Easy Dynamics","context":"The sharpest statement in the corpus of the difference between an implementation claim and an assessment result.","date":null,"id":"deck-how-vs-passfail","source_document":"Where-does-desired-state-go.pptx, slide 1","speaker":null,"text":"Current SSP is intended to capture “how” a control is satisfied. Current desired state benchmarks are meant to be pass/fail"},{"affiliation":"Easy Dynamics","context":"Question 4, subject granularity. The same concern as criterion 8.","date":null,"id":"deck-by-component-granularity","source_document":"Where-does-desired-state-go.pptx, slide 1","speaker":null,"text":"Current SSP only provides system state through by-component responses – not granular enough"},{"affiliation":"OSCAL Foundation TFG","context":"OSCAL cannot express shall, should or may. The reason the normativity question cannot be settled inside the model.","date":"2026-08","id":"preread-requirement-level-absent","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 7, criterion 3 row","speaker":null,"text":"Absent from OSCAL entirely. An orthogonal gap affecting every option."},{"affiliation":"OSCAL Foundation TFG","context":"The pre-read's own conclusion, reached from the meeting record. The site reaches the same conclusion from the files.","date":"2026-08","id":"preread-no-ssp-no-ar","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 7","speaker":null,"text":"No option has a published SSP or a published assessment result. The group has been arguing about where content belongs for five months without ever seeing the two artifacts where the strongest objections on both sides would be resolved."},{"affiliation":"OSCAL Foundation TFG","context":"Questions 4 and 5 are the least-defined parts of OSCAL and the group has said so on the record.","date":"2026-08","id":"preread-platform-semantics","source_document":"Hardening-Guidance-Options-Comparison.docx, Section 8, evidence register item 8","speaker":null,"text":"Authoritative semantics for assessment platform versus asset versus component. Pirooz and Vikas agreed to post for the NIST OSCAL team, 17 July. Not established whether posted; no response in the record"},{"affiliation":"AWS","context":"The publisher's own status disclaimer. Required alongside any AWS data-quality item per editorial rule 8.","date":null,"id":"aws-readme-experimental","source_document":"AWS/oscal-content-for-aws-services-main/README.md","speaker":null,"text":"Amazon Web Services (AWS) is offering _experimental_ Open Security Controls Assessment Language (OSCAL) content for public review and feedback."},{"affiliation":"AWS","context":"The stated design principle behind the catalog-first content.","date":null,"id":"aws-docs-core-oscal","source_document":"AWS/oscal-content-for-aws-services-main/docs/COMPONENTS.md","speaker":null,"text":"The AWS component definitions are designed to use core OSCAL to the greatest degree practical."},{"affiliation":"IBM","context":"The normative statement that checks live only on validation components. The typo is in the source.","date":null,"id":"ibm-checks-validation-only","source_document":"IBM/component-rules.md, line 39","speaker":null,"text":"Check defintions are only used to define checks for validation components (assessment tools)."},{"affiliation":"AWS","context":"Quoted in full rather than characterized. This is where AWS's own sense of a validation component appears, which is a component enumerating the frameworks a service has been validated against. It is listed as a future expansion and is not shipped. It is not IBM's sense of the term.","date":null,"id":"aws-docs-future-considerations","source_document":"AWS/oscal-content-for-aws-services-main/docs/COMPONENTS.md, Future Considerations","speaker":null,"text":"Depending on potential usefulness or customer demand, we may expand these component definitions. If any of the following efforts are valuable to you, please let us know. Compliance linkages. Compliance deployment automation. Compliance validation automation. Compliance documentation content. Compliance linkages. Under this expansion, AWS could create an additional OSCAL component definition that enumerates all applicable compliance frameworks as \"validation\" components. Each AWS region and service could then be linked to the frameworks where the region or service was found to be compliant. This would allow a machine-readable method of determining which services are validated under a particular framework and which are not. The resulting component definition relationships would expand as follows: Compliance deployment automation. This could provide automated deployment scripts that ensure a service is deployed consistent with the requirements of a specific framework. Compliance deployment validation. This could provide automated validation scripts that ensure a service continues to operate with a configuration consistent with the requirements of a specific framework. Compliance documentation content. This could provide documentation that describes the component configuration in alignment with the requirements of security frameworks that require such documentation."},{"affiliation":"IBM","context":"IBM's four self-identified open questions, verbatim including their typographic errors. All four concern questions 4 and 5.","date":null,"id":"ibm-open-questions","source_document":"IBM/component-rules.md, Open questions","speaker":null,"text":"1. Assessment Platform usage? make it optional? 2. Is assessment component sufficient or we need assessment platform also? 3. How is assessment asset associated the tasks or activities? currently there seems to be no way. 4. In AR there are multiple assessment assests defined. How is an obesrvation associated with an assessment asset? Currently there is no way to do it."}]},"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":"an activity names the control it serves through related-controls or reviewed-controls","model":"mapping-collection","what":"none, the tie is on the activity"},{"count":0,"detail":"assessment-assets carries the components that run the checks, so they need no document of their own","model":"component-definition","what":"none, the engines are named inside each plan"},{"count":1,"detail":"no guidance enters it; the plans point at it rather than adding to it","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, answering 370 controls"},{"count":4,"detail":"the three guides carry 547 requirements between them, as activities and steps, and each plan names 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 separate results rather than four sections of one, because a result names exactly one plan through import-ap and that field is neither an array nor optional","items":[{"name":"800-53 AR"},{"name":"CIS Ubuntu AR"},{"name":"DISA PgSQL AR"},{"name":"CISA SCuBA AR"}],"model":"assessment-results","what":"one per plan, because a result names exactly one plan"}],"plan_of_record":"The plan of record answers 370 controls, and none of the three guides enters it","rule":"Each guide becomes an assessment plan. The framework side is unchanged, and each plan produces a result of its own."},"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 the organisational profile that merges them, which is needed because a plan reaches all four through one import-profile and that field is a single required object","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 to merge them"},{"count":3,"detail":"without these the guide's controls and the framework's controls are two unrelated sets in the same plan","items":[{"name":"CIS to 800-53"},{"name":"STIG to 800-53"},{"name":"SCuBA to 800-53"}],"model":"mapping-collection","what":"one per guide, tying its controls to the framework"},{"count":3,"detail":"the control names the check by identifier and a software component of that name carries the runner detail","items":[{"kind":"software","name":"Ubuntu checks"},{"kind":"software","name":"PgSQL checks"},{"kind":"software","name":"M365 checks"}],"model":"component-definition","what":"one per technology, carrying the check components"},{"count":1,"detail":"370 from the framework and 547 from the guides, each needing a by-component response, and all of them reached through one import-profile because that field is a single required object","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, answering 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 plan of record answers 917 controls, 370 from the framework and 547 from the guides","rule":"Each guide is published as a catalog, selected by a profile of its own, and tied back to the framework by a mapping collection. The plan of record answers 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-implementation names the control the rule serves, so no second document carries the tie","model":"mapping-collection","what":"none, the tie is inside the component definition"},{"count":6,"detail":"Ubuntu, PostgreSQL and Microsoft 365, and one validation component definition per engine that tests them","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 carrying 547 rules, three engines carrying the checks"},{"count":1,"detail":"the control count does not move; the rules arrive inside system-implementation instead","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, answering 370 controls and carrying 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 plan of record answers 370 controls, and carries 547 desired-state rules inside its components","rule":"Each guide becomes rules on the component it configures, and each engine that tests them becomes a component of its own. The framework side is unchanged."},"profile-first":{"files":[{"count":4,"detail":"800-53 Revision 5 untouched, and CIS Ubuntu, DISA PostgreSQL and CISA SCuBA each as a catalog whose controls carry an assessment objective and an executable assessment method, because the author of the requirement is the author of the check","items":[{"name":"NIST 800-53"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"}],"model":"catalog","what":"one for the framework, one per guide, carrying its checks"},{"count":4,"detail":"the High baseline the plan of record imports, and for each of the three guides the profile the component references, which is how the executor reaches a guide's methods without the guide entering the plan of record's own profile","items":[{"name":"800-53 High"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"}],"model":"profile","what":"the High baseline, and one selection per guide"},{"count":0,"detail":"where a profile adds a method to a framework control the placement is the tie; where the guide is its own catalog the note supplies no tie, and that is an open question on the questions page","model":"mapping-collection","what":"none, the finding targets the guide's own objective"},{"count":0,"detail":"the executor matches each method's platform prop against the plan of record's own components, so no definition carries the checks and none names the engine","model":"component-definition","what":"none, the checks are parts on the controls"},{"count":1,"detail":"no guidance enters it; the components reference the profiles the executor reads, and the responses stay per framework control","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, answering 370 controls"},{"count":1,"detail":"the plan imports the system security plan, and the executor resolves the profile each component references to find the methods whose platform matches it","items":[{"name":"System AP"}],"model":"assessment-plan","what":"one, reading 547 methods through the components' profiles"},{"count":1,"detail":"every finding targets an objective on a guide catalog's control, and every observation carries the script's raw output as evidence","items":[{"name":"System AR"}],"model":"assessment-results","what":"one, with a finding per objective"}],"plan_of_record":"The plan of record answers 370 controls, and the 547 executable methods are read by the assessment plan through the components' profiles","rule":"Each guide is published as a catalog whose controls carry their own executable methods, and each component references a profile selecting from it. The framework side is unchanged and the plan of record's control set does not move."}},"excluded_model":{"model":"plan-of-action-and-milestones","reason":"It records what was not met and what is being done about it. That is the same document in all four approaches, so it separates none of them."},"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":"One entry per file, so a reader can follow a particular document from the figure into the list beneath it. The names are shortened to fit a tile. Where a model has more than one kind of file in it, the kind is named too: a component definition holding the thing being configured is software, and one holding the checks that test it is validation, which is the distinction the whole approach rests on and is invisible from the file count alone.","models":["catalog","profile","mapping-collection","component-definition","system-security-plan","assessment-plan","assessment-results"],"note":"One system, one baseline, three hardening guides, modelled four ways. The point of the scenario is that the four approaches do not differ in what they can express so much as in how many documents it takes to express it, and what the plan of record ends up holding. Every count is either recomputed from a corpus in this repository, read from the NIST profile stored in data/scenario-evidence/, or forced by the OSCAL schemas, and each says which. What the schemas force is stated on the file rows it explains rather than in a section of its own.","summary":"A system under NIST SP 800-53 Revision 5 at the High baseline, running Ubuntu, PostgreSQL and Microsoft 365, hardened against a published guide for each. The same scenario is modelled in all four approaches, using every OSCAL model except the plan of action and milestones.","title":"One system, three hardening guides"},"data/schema-evidence/assessment-subject.json":{"constraints":["required includes \"type\"","type anyOf enum == [\"component\",\"inventory-item\",\"location\",\"party\",\"user\"]"],"definition":"oscal-ap-oscal-assessment-common:assessment-subject","fetched_at":"2026-08-21","fragment":{"$id":"#/definitions/oscal-ap-oscal-assessment-common:assessment-subject","additionalProperties":false,"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.","properties":{"description":{"description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description","type":"string"},"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"},"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":["type"],"title":"Subject of Assessment","type":"object"},"model":"assessment-plan","note":"The oscal-ap-oscal-assessment-common:assessment-subject definition. A subject is typed, and the vocabulary is component, inventory-item, location, party or user, so an assessment can be aimed at a particular host rather than at the class of thing the host is.","oscal_version":"1.1.3","provenance":"Taken from the offline OSCAL reference copy of the 1.1.3 schemas rather than from the published 1.2.1 set the other fragments here record, because 1.2.1 could not be fetched. The CI re-fetch compares it against 1.2.1.","schema_id":"http://csrc.nist.gov/ns/oscal/1.1.3/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-08-21","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 implemeting a given control.","title":"Component Universally Unique Identifier Reference"},"description":{"description":"An implementation statement that describes how a control or a control statement is implemented within the referenced system component.","title":"Control Implementation Description","type":"string"},"export":{"additionalProperties":false,"description":"Identifies content intended for external consumption, such as with leveraged organizations.","properties":{"description":{"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","type":"string"},"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":{"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","type":"string"},"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":{"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","type":"string"},"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":{"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","type":"string"},"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":{"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","type":"string"},"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.1.3","provenance":"Taken from the offline OSCAL reference copy of the 1.1.3 schemas rather than from the published 1.2.1 set the other fragments here record, because 1.2.1 could not be fetched. The CI re-fetch compares it against 1.2.1.","schema_id":"http://csrc.nist.gov/ns/oscal/1.1.3/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-08-21","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":{"description":"A name given to the location, which may be used by a tool for display and navigation.","title":"Location Title","type":"string"},"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":{"additionalProperties":false,"description":"An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.","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"},"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"}},"required":["uuid","type"],"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":{"description":"A name given to the document revision, which may be used by a tool for display and navigation.","title":"Document Title","type":"string"},"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":{"description":"A summary of the role's purpose and associated responsibilities.","title":"Role Description","type":"string"},"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":{"description":"A name given to the role, which may be used by a tool for display and navigation.","title":"Role Title","type":"string"}},"required":["id","title"],"title":"Role","type":"object"},"minItems":1,"type":"array"},"title":{"description":"A name given to the document, which may be used by a tool for display and navigation.","title":"Document Title","type":"string"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["title","last-modified","version","oscal-version"],"title":"Document Metadata","type":"object"},"model":"shared","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.1.3","provenance":"Read from the assessment-plan schema in the offline OSCAL reference copy. metadata is one assembly shared by all seven models, so the catalog carries this same definition; the catalog schema file itself could not be opened through the sync layer.","schema_id":"http://csrc.nist.gov/ns/oscal/1.1.3/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":"Nothing in the published content answers this and no reason is on the record."}],"approaches":[{"key":"catalog-first","label":"Catalog-first","layer":"Control","one_line":"The rule is a catalog control, the check is in a software component defined as 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 is a new assembly in a component definition, the check sits in a validation component definition.","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, the check is a new assembly beneath it.","option_letter":"C","primary_model":"assessment-plan","repo":null,"serves_stakeholder_first":"assessor","status_annotation":"placeholder and synthetic identifiers"},{"key":"profile-first","label":"Profile-first","layer":"Control","one_line":"The rule is an assessment objective on the control, the check an executable assessment method beside it, in a catalog or added by a profile.","option_letter":"D","primary_model":"profile","repo":null,"serves_stakeholder_first":"assessor","status_annotation":"concept note, no published content"}],"carrier_note":"Every answer names the OSCAL model it lives in and the assemblies inside it that carry the answer. The model is the first thing that differs between the four: the same requirement is a control in one, a component in another, an activity in a third and a part on a control in the fourth, and everything downstream follows from that.","empty_states":[{"key":"empty-absent","label":"Unanswered, no stated position","meaning":"Nothing in the published content answers this question and no reason is on the record.","rendering":"hollow with a light dotted fill"}],"finding":"Questions 1 and 2 are answered by all four. Question 6a is answered in full by none of them, and no column is complete from top to bottom.","legend":{"answers_title":"Is the question answered?","label":"How to read an answer","mechanism_title":"How the capability is enabled","why_one_block":"Two legends sitting apart read as two subjects, and they are two axes of one reading: every answer on this page carries a mark from the first group and, where it is answered at all, one or more badges from the second. They are one block for the same reason the two axes belong on one cell.","why_uneven":"The answer states are three words and the mechanisms carry a sentence each. That is deliberate rather than an oversight. Answered, partly answered and not answered mean what they say; Proposed does not tell a reader that no tool can read the content until the schema lands, and that is the sentence the page turns on."},"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":"Rules sits on the component as a sibling of control-implementations.","slot":"1","snippet_ids":["ibm-cos-component","ibm-rules-md"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The activity is the rule and its step is the check. No parameter field, so a value goes in the 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":"Made by the mapping model in its own document, not inline. No publisher has shipped one yet.","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":"The component ties to the control today. Tying the rule to it needs 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 scopes the plan, related-controls names what an activity is for. The scope is required, the tie is not.","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 identifier is the bridge to the runtime. It executes a 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":"Proposed schema. A composite key, both halves on the check side. The rule holds no pointer back.","slot":"3","snippet_ids":["ibm-validation-ansible"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"Three conventions. Only the CISA one reaches an executable, through a JSON string in a prop. STIG and CIS describe the check 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":"A by-component is the only shape available, and it names a component, not an instance. An assessor cannot introduce a catalog.","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 same by-component, plus the rule. An assessor can carry the definition into their own plan, and the checks travel with it.","slot":"4","snippet_ids":["ibm-validation-ansible"],"state":"partial"},{"approach":"assessment-first","assemblies":["assessment-subjects","task","subjects"],"mechanisms":["assembly"],"model":"assessment-plan","note":"Scope, then target. The plan names the subjects, each activity aims at some of them. Both name an inventory item, an instance rather than a class.","slot":"4","snippet_ids":["ez-subjects-includeall","ez-subjects-explicit"],"state":"filled"},{"approach":"catalog-first","assemblies":["component"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"Partly. The input and the output are written down; the machine between them is not. ConfigRuleId resolves inside the engine. No assessor's path: a catalog cannot be introduced into an assessment.","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":"Proposed schema. The proposal records four open questions about this, including how an asset is tied to a task.","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":"A chain. The platform runs, the component beneath it is the plugin, and a prop on the task says which 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":"Template level, not system level: a definition says how a component would satisfy a control. Only a plan of record says a system does, and none is published.","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 is a by-component response today. Naming the rule it rests on needs the proposed assembly.","slot":"6a","snippet_ids":[],"state":"empty-absent"},{"approach":"assessment-first","assemblies":["import-ssp","back-matter","resource"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"No claim of its own. It names the document holding one, and a resource for where no plan of record exists.","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":"The repository's own documentation lists compliance validation automation as a future consideration rather than shipping it.","slot":"6b","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["observation"],"mechanisms":["assembly","proposed"],"model":"assessment-results","note":"Observations and no findings, so no objective status. The control is recovered through the plan rather than stated.","slot":"6b","snippet_ids":["ibm-ar-observation"],"state":"partial"},{"approach":"assessment-first","assemblies":["finding","observation"],"mechanisms":["assembly"],"model":"assessment-results","note":"A result of its own, importing the plan. Findings carry a target and a status; an observation's subject is the activity that ran.","slot":"6b","snippet_ids":["ez-cisa-ar-finding","ez-cisa-ar-observation"],"state":"filled"},{"approach":"profile-first","assemblies":["alter","add","part"],"mechanisms":["assembly"],"model":"profile","note":"An assessment objective part, added to the framework control by the profile. Naming the control is the address of the part rather than a tie made later.","slot":"1","snippet_ids":[],"state":"filled"},{"approach":"profile-first","assemblies":["alter"],"mechanisms":["assembly"],"model":"profile","note":"Containment. The parts are added to the control the alter names, so placing the check is the tie and no second document or identifier carries it.","slot":"2","snippet_ids":[],"state":"filled"},{"approach":"profile-first","assemblies":["part"],"mechanisms":["assembly","prop"],"model":"profile","note":"An assessment method part with method TEST and a body in prose. Namespaced props say which engine runs the body and how its result is judged.","props":[{"name":"language","ns":"https://example.org/ns/oscal-automation"},{"name":"evaluation","ns":"https://example.org/ns/oscal-automation"},{"name":"pass-condition","ns":"https://example.org/ns/oscal-automation"}],"slot":"3","snippet_ids":[],"state":"filled"},{"approach":"profile-first","assemblies":["part"],"mechanisms":["assembly","prop"],"model":"profile","note":"The method names its platform as a CPE and the executor matches it to an SSP component. No component field carries a CPE, so the match is a convention.","props":[{"name":"platform","ns":"https://example.org/ns/oscal-automation"}],"slot":"4","snippet_ids":[],"state":"partial"},{"approach":"profile-first","assemblies":["part"],"mechanisms":["assembly","prop"],"model":"profile","note":"Four props tell an executor how to run the body and judge what comes back. The executor is a resolver outside OSCAL, and the vocabulary has no owner yet.","paths":[{"assemblies":["part","observation","finding"],"in":{"slot":"3"},"key":"assessor","label":"Assessor's path","out":{"slot":"6b"}}],"props":[{"name":"language","ns":"https://example.org/ns/oscal-automation"},{"name":"evaluation","ns":"https://example.org/ns/oscal-automation"},{"name":"pass-condition","ns":"https://example.org/ns/oscal-automation"},{"name":"timeout","ns":"https://example.org/ns/oscal-automation"}],"slot":"5","snippet_ids":[],"state":"partial"},{"approach":"profile-first","assemblies":["implemented-requirement","by-component"],"mechanisms":["assembly"],"model":"system-security-plan","note":"The plan of record is untouched by design, so the claim is the ordinary response against the framework control. Nothing on it names the objective the check tests.","slot":"6a","snippet_ids":[],"state":"partial"},{"approach":"profile-first","assemblies":["finding","observation"],"mechanisms":["assembly"],"model":"assessment-results","note":"A finding targeting the objective the profile added, resting on an observation that carries the raw output as evidence and names the host as its subject.","slot":"6b","snippet_ids":[],"state":"filled"}],"mechanism_note":"How a capability is enabled is a different question from whether it is answered. The answer states describe the published corpus. These describe the model: what an approach would have to rely on to carry the answer at all. An approach can answer everything and still rest on properties no other tool reads, and it can answer nothing while the mechanism it would use is already released.","mechanism_states":[{"key":"assembly","label":"Released OSCAL assembly","meaning":"The capability is carried by an OSCAL assembly that exists today. Adopting it changes no schema.","rendering":"a solid badge","short":"OSCAL assembly"},{"key":"proposed","label":"Proposed assembly","meaning":"The capability is carried by an assembly that does not exist yet. Adopting it means a schema change, and until that lands no tool can read it.","rendering":"a dashed badge","short":"Proposed"},{"key":"prop","label":"Namespaced property","meaning":"The capability is carried by a prop in the publisher's own namespace. The schema does not model it, so a tool that does not know that namespace cannot read it, and no two publishers have to agree.","rendering":"a dotted badge","short":"Prop"}],"note":"The six questions and the answer matrix. This is the site's central claim set. Every cell is asserted against the shipped files and is re-checked by tools/verify.py --matrix. Personal names and proponent organizations are not rendered anywhere on the site; where a cell state depends on a reason someone stated, the note cites the source document rather than the speaker.","paths_note":"A runner is the thing between an input and an output, and which documents those are depends on who runs it. Each path below is one file in, one file out.","proposed_assemblies":["assessment-check-id","associated-checks","checks","implementing-rules","result","rule-groups","rules"],"slots":[{"key":"rule","name":"The rule itself","number":"1","optional":false,"question":"What must be true, and where is that written down?","short":"Rule","why_separate":"The requirement itself, technology-specific, one per testable condition. Pre-read settled item 7 puts its parameters here: the definition declares the options and a default."},{"binding_times":[{"authored_by":"Whoever wrote the rule","key":"inline","label":"Author-time, inline","mechanism":"The rule declares its control directly"},{"authored_by":"Whoever wrote the rule","key":"pointer","label":"Author-time, by pointer","mechanism":"A prop carries an external framework identifier that a consumer must resolve"},{"authored_by":"Anyone, including a third party","available_to":{"assessment-first":false,"catalog-first":true,"component-first":false,"profile-first":false},"key":"late","label":"Late, external","mechanism":"A separate artifact ties rule to control after publication","why":"mapping-item.type is closed by allOf to control and statement, and mapping-item carries no uuid and no href, so this binding time reaches a rule only where the rule is already modelled as a control or a control statement. The gap is in OSCAL rather than in any approach, and it is not an argument for the one approach it happens to suit: it rewards whichever view of a rule already matches the schema's assumption."}],"cost_of_leaving_empty":{"evidence":["observation.json","finding.json","finding-target.json"],"finding":"Not available. finding requires target; finding-target requires type, closed by allOf to statement-id or objective-id, both control-derived.","observation":"Available. AR observation requires only uuid, description, methods and collected, and carries no control reference of any kind.","summary":"Without a link to a control you can record what you saw, but not whether it complied."},"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":"Optional by design. A rule is finer than a control and may serve several, one, or none. The mechanism must exist and must not be mandatory."},{"key":"check","name":"How the rule is tested","number":"3","optional":false,"question":"What check executes the rule within a runtime environment?","short":"Check","why_separate":"One rule, many checks, one per tool. Pre-read settled item 4 keeps the executable itself outside OSCAL, referenced. The warrant for separating this from question 1 is settled item 5."},{"key":"subject","name":"What the check runs against","not_established":true,"not_established_note":"Evidence register item 8: authoritative semantics for assessment platform versus asset versus component were to be posted to the NIST OSCAL team on 17 July. No response is in the record.","number":"4","optional":false,"question":"What exactly is being tested: a host, a component, an account?","short":"Subject","why_separate":"A host, an inventory item, a component, an account. This is criterion 8, response fidelity."},{"key":"actor","name":"What performs the check","not_established":true,"not_established_note":"Same as question 4. Three approaches use six different subsets of assessment-assets, assessment-platforms, uses-components, validation components, origin actors, task-level props and the method prop.","number":"5","optional":false,"question":"What or who runs the test, and how is that named?","short":"Runner","why_separate":"A validation component, an assessment platform, a tool, a person. Includes the method prop: examine, interview, or test."},{"group_name":"Whether the rule was met, claimed and recorded","key":"implementation-claim","name":"How the system claims it meets the rule","number":"6a","optional":false,"question":"How does a system say it satisfies this, in its own words?","short":"Claim","why_separate":"Asserted by the system owner. Standing design intent, narrative, arguable, per component. Lives in the SSP as implemented-requirement, statement and by-component."},{"group_name":"Whether the rule was met, claimed and recorded","key":"assessment-result","name":"How an assessment records the outcome","number":"6b","optional":false,"question":"Was it satisfied, when, and on what?","short":"Result","why_separate":"Asserted by the assessor. A point in time, evidenced, binary or graded, per subject. Lives in the AR as observation, finding and status. A rule carrying desired state has a binary satisfaction condition; the SSP's implementation statement expects a narrative one."}]},"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-08-22T17:17:36+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","section":null,"sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","section":null,"sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","section":null,"sha256_of_source_file":"49d218b196333445dd67178dd58aba441fc596a28d2221c1c724d8eba460ee57","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-08-22T17:17:36+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":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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 },\n {\n \"activity-uuid\": \"4e391cf6-5549-46f3-b3d7-aad12cd5a226\"\n },\n {\n \"activity-uuid\": \"2c69fb5c-056f-4788-be36-723b939a4766\"\n },\n {\n \"activity-uuid\": \"04319877-e72d-4967-b968-4852e6738113\"\n },\n {\n \"activity-uuid\": \"53852402-8cd6-4e1c-a559-f31bb004a66e\"\n },\n {\n \"activity-uuid\": \"c98b996e-8dae-40ef-8b40-100ffbe9e5e3\"\n },\n {\n \"activity-uuid\": \"5f62a033-3847-43ec-bafd-3dc1a7621029\"\n }\n ]\n}","extracted_at":"2026-08-22T17:17:36+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-08-22T17:17:36+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"b7457f9e8af8f4237f805930d2c51bd783c262de4912f5d6d68bc54e5d382c4d","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-open-questions.json":{"approach":"component-first","content":"## Open questions?\n\n1. AP - Assessment Platform usage? make it optional?\n2. AP - Is assessment component sufficient or we need assessment platform also?\n3. AP - How is assessment asset associated to the tasks or activities? currently there seems to be no way.\n4. In AR there are multiple assessment assests defined. How is an obesrvation associated with an assessment asset? Currently there is no way to do it.","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-open-questions","language":"markdown","pointer":"$","section":"Open questions?","sha256_of_source_file":"630c45450f3cea476cd9a7df7da1f49e22f854832907521656191714eb9bd57c","slot":"meta","source":"IBM/Automated-assessment.md","title":"IBM's open questions"},"data/snippets/ibm-rules-md.json":{"approach":"component-first","content":"# Automated Assessment\n\n## Objective\n\nCurrent OSCAL cDef and SSP models only provide support for a textual description of how a component (s/w, service, process, etc.) implements a catalog control. This may be sufficient for audit documentation requirements as part of an SSP, but does not enable automation of assessments.\n\nCatalog controls specify the requirements at a high-level which are technology/product/service/process agnostic. Each component implements the control requirements in its own way based on the product's design/implementation. What is required is a way to specify how a component implements a control (configuration settings, APIs, etc.) which can then be assessed to validate its compliance.\n\n### User Stories\n\nAs an OSCAL component vendor, I would like to specify concrete technical capabilities (rules) that my component provides to support control implementation requirements, which can then be evalauated to validate conformance to specific controls.\n\nAs an OSCAL component (assessment tool) vendor such as OpenSCAP, Kyverno, OPA policies, etc., I would like to specify validations (checks) that my tool implements for different component rules. These checks can be either automatically or manually executed and their results (pass, fail, N/A) validate whether a rule satisfies its stated intent or not.\n\n## Proposal\n\nAdd support for rules, checks, and related changes to different OSCAL models to help automation of assessments.\n\n### Adding Rules in OSCAL Component Defintion\n\nThe product vendors or service providers can specify their product’s compliance implementation by defining the mapping of the regulation controls to the product’s technical policy rules and their parameters. These rules can be thought of as configurations that can be performed on the service, across multiple services, or as behaviors of a product. Since the catalog or profile controls specify requirements at a coarser granularity and are technology agnostic, the rules capture the technology-specific implementation of those controls at a finer granularity such that they can be programmatically verified via checks based on evidence collected programmatically via APIs.\n\nA component provider needs to provide for a given control both (a) the specific rules with related parameters and values, as well as (b) the control responses as text describing how a control is implemented by that product or service.\n\n#### Rule assembly\n\nThe below structure gives the proposed rule structure in OSCAL.\n\n- rules [0 to ∞]\n - id [1]\n - title [0 or 1]\n - description [1]\n - audit-procedure [0 or 1]\n - remediation-procedure [0 or 1]\n - params [0 to ∞]\n - evidence-id [0 or 1]\n - props [0 to ∞]\n - links [0 to ∞]\n - remarks [0 or 1]\n\nEach rule will have:\n\n- id: textual id (not uuid) that uniquely identifies a rule in a component\n- title: a summary title for the rule\n- description: brief explanation of the aspect/objective that this rule supports\n- audit-procedure: textual description of how this rules can be validated\n- remediation-procedure: textual description of how this rule can be fixed if it is failing\n- params: any parameters associated with this rule. These parameter(s) will be used in the validation (check).\n- evidence-id: any linkage to evidence data structure or API that is used for evaluation\n\n#### Rule grouping assembly to organize rules\n\nRules can be grouped to better organize them.\n\n- rule-groups [0 to ∞]\n - id [1]\n - title [0 or 1]\n - description [1]\n - props [0 to ∞]\n - links [0 to ∞]\n - A choice of:\n - rule-groups [0 or 1]\n - rules [0 or 1]\n\n#### An example\n\n```JSON\n\"components\": [\n {\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 }\n]\n```\n\n\n#### Rule association to control or statements\n\nEach rule in a component can be associated to one or more controls/statements in implemented requirements. This enables automatation of control implmentation and assessments as the validaiton of a control/statement can now be computed using validation of its associated rules.\n\n- implementing-rules [0 to ∞]\n - rule-id [1]\n - remarks [0 or 1]\n\n```JSON\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 {\"rule-id\": \"cos_access_endpoint_type\"}\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 {\"rule-id\": \"cos_encryption_hyperprotect_key_configured\"}\n ]\n }\n ]\n }\n]\n```\n\n### Adding checks in OSCAL Component Defintion (only for components of type \"validation\")\n\nPolicy validation tools (assessment tools) vendors need to specify the policy checks that they implement and their mapping to different products' technical rules. These checks, tests the policy compliance, thus bridging the OSCAL compliance as code into the policy as code.\n\nPlease note that we don't capture the actual check code or policy as part of the OSCAL. These will be implemented in their respective policy lanaguages and executed accordingly. We only capture the check ids so that the results (against those ids) can be used to perform the aggregation.\n\nCheck defintions are only used to define checks for validation components (assessment tools) and they are not used in other component defintions (s/w, service, process, etc.).\n\n#### Check Assembly (only for validation components)\n\nThe below structure gives the proposed check structure in OSCAL.\n\n- checks [0 to ∞]\n - id [1]\n - title [0 or 1]\n - description [1]\n - rule-id [1]\n - target-component-uuid [1]\n - props [0 to ∞]\n - links [0 to ∞]\n - remarks [0 or 1]\n\nEach check will have:\n\n- id: uniquely identifies a check in a validation component. The validation results (pass, fail, etc.) as part of tool execution will be reported against this same id.\n- title: a summary title for the check\n- description: brief explanation of what this check does\n- rule-id: the rule for which this check provides the implementation.\n- target-component-uuid: the target component to which the above rule belongs. Rules are only considered unique within a component. Hence, both rule and traget component are required to uniquely identify the rule.\n\n```JSON\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\n### Component Defintion changes\n\nChanges in component defintion structure.\n\n- component\n - uuid [1]\n - type [1]\n - title [1]\n - description [1]\n - purpose [1]\n - **params [0 to ∞]**\n - **A choice of:**\n - **rule-groups [0 or 1]**\n - **rules [0 or 1]**\n - **checks [0 or 1]**\n - ...\n - control-implementations [0 or 1]\n - ...\n - source [1]\n - ....\n - set-params [0 to ∞]\n - implemented-requirements [1 to ∞]\n - ...\n - control-id [1]\n - ....\n - **implementing-rules [0 to ∞]**\n - set-params [0 to ∞]\n - ...\n - statements [0 to ∞]\n - statement-id [1]\n - ...\n - **implementing-rules [0 to ∞]**\n - ...\n\n### SSP changes\n\nSame changes will be applicable to component definition and implemented requirements section in SSP.\n\nOne difference to note here is that the component defintion created by vendor will include all possible rules for that component with their association to controls across multiple profiles/catalogs, but when including in the SSP, only those rules need to be selected which are applicable to the SSP (based on the controls in the imported profile). The vendor defined component definiton can be thought of as a library (of all possible rules) and the ones defined in SSP can be thought of as its instance (only including what is relevant).\n\n```JSON\n\"system-security-plan\": {\n \"uuid\": \"7550c0c0-31f9-46fd-b022-3a7ae0f3896f\",\n \"metadata\": ...,\n \"import-profile\": {\n \"href\": \"trestle://profiles/ACME_official/profile.json\"\n },\n \"system-characteristics\": ...,\n \"system-implementation\": {\n \"components\": [\n {\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 \"status\": {\n \"state\": \"operational\"\n }\n }\n ]\n },\n \"control-implementation\": {\n \"description\": \"This is the control implementation for the system.\",\n \"set-parameters\": [\n {\n \"param-id\": \"endpoint_access\",\n \"values\": [\n \"private\"\n ]\n }\n ],\n \"implemented-requirements\": [\n {\n \"uuid\": \"7ec5da9d-b53a-4030-802d-ad88a49d69d5\",\n \"control-id\": \"ac-4\",\n \"by-components\": [\n {\n \"component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\",\n \"uuid\": \"265e556d-f7c9-4e0d-acdd-48f1e30331ee\",\n \"description\": \"This control is implmeneted by ensuring the COS is only available on private endpoints.\",\n \"implementing-rules\": [\n {\"rule-id\": \"cos_access_endpoint_type\"}\n ],\n \"implementation-status\": {\n \"state\": \"implemented\"\n }\n }\n ]\n }\n ]\n }\n}\n```\n\n### Changes in Assessment Plan\n\nThe validation component can be included in the `assessment-plan->assessment-assets->components`. The check assembly will be included in this component. The original validation component defintion would contain all the checks provided (implemneted) by that specific tool, but when including in the AP, only those checks will be included that are required (same as in SSP for software/service component defintion).\n\n- assessment-plan\n - uuid\n - ....\n - local-definitions\n - activities\n - uuid\n - description\n - **assessment-asset-uuid [0 or 1]**\n - **check-ids [0 to ∞]**\n - ....\n - ...\n - assessment-assets\n - components\n - uuid\n - type\n - title\n - description\n - **checks [0 to ∞]**\n - ...\n\nValidation component and the corresponding checks to be executed (as part of activities) can be associated with `local-defintion->activities`\n\n```JSON\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 ]\n```\n\n`assessment-plan->tasks` can be used to define when/at what frequency to perform assessment acitivities such as run different assessment (validation) tools - OSCAP for Ubuntu OS, OpenShift Compliance Operator (OSCO) for OpenShift, etc. and which subjects each of these tools perform assessment for. This is done by associating the right activities with the tasks.\n\n### Changes in Assessment Result\n\nAdd assessment-check-id and assessment-asset-uuid to each observation to specify the check-id for which this observation is (and for which assest / assessment tool). Also, add result to capture the outcome (pass, fail, n/a).\n\n- observations [0 to ∞]\n - uuid\n - description\n - **assessment-check-id [0 or 1]**\n - **assessment-asset-uuid [0 or 1]**\n - **result [0 or 1]**\n - subjects [0 to 1]\n - ....\n\n```JSON\n {\n \"uuid\": \"6c0a18ff-36b4-45b2-9e8b-6e3011bee6b1\",\n \"description\": \"xccdf_org.ssgproject.content_rule_package_prelink_removed\",\n \"assessment-check-id\": \"xccdf_org.ssgproject.content_rule_package_prelink_removed\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"result\": \"pass\",\n \"props\": [],\n \"methods\": [\n \"TEST\"\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 }\n```\n\n## Open questions?\n\n1. AP - Assessment Platform usage? make it optional?\n2. AP - Is assessment component sufficient or we need assessment platform also?\n3. AP - How is assessment asset associated to the tasks or activities? currently there seems to be no way.\n4. In AR there are multiple assessment assests defined. How is an obesrvation associated with an assessment asset? Currently there is no way to do it.","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-rules-md","language":"markdown","pointer":"$","section":null,"sha256_of_source_file":"630c45450f3cea476cd9a7df7da1f49e22f854832907521656191714eb9bd57c","slot":"meta","source":"IBM/Automated-assessment.md","title":"IBM's proposed rule and check assemblies"},"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 only run here. There is no path from a check to a claim, so what comes out is a result and never the plan of record."},"benchmark":{"note":"Writes the activity and its steps. The check that runs them is the engine's.","writes":[{"model":"assessment-plan"}]},"engine":{"note":"The plan is the engine's, and the checks in it are what it adds. It is named inside the plan too, in assessment-assets.","writes":[{"model":"assessment-plan"}]},"mapper":{"note":"Edits the plan rather than writing one. Reviewed-controls on the activity names the framework controls the check covers.","writes":[{"model":"assessment-plan"}]},"owner":{"note":"The selection and the plan of record, and nothing beyond them. An assessor's run takes no dependency on what the owner automates, and cannot see it.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"note":"Writes the activity and its steps. The check that runs them is the engine's.","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 same checks, a different party running them. What comes out is a result, and its finding targets the statement the owner wrote."},"benchmark":{"writes":[{"model":"catalog"}]},"engine":{"note":"Builds the tool and runs nothing. What it ships is the check, as a component of type software. The catalog it points at is the guidance authors'.","writes":[{"kind":"software","model":"component-definition"}]},"mapper":{"note":"The one approach where the tie is a document of its own, and the mapping provider's to write. No publisher has shipped one for hardening guidance yet.","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 profile is always the owner's: the selection of what this system is held to, and the merge of the catalogs a plan can import.","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 run goes through the assessment plan, which is what lets the result name the host rather than the component."},"benchmark":{"writes":[{"kind":"software","model":"component-definition"}]},"engine":{"note":"A component of type validation rather than software, holding the checks. Builds it, runs nothing.","writes":[{"kind":"validation","model":"component-definition"}]},"mapper":{"note":"Edits a definition rather than writing one. Which of the two carries the tie, the rules or the checks, is an open question.","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"}]}},"profile-first":{"auditor":{"flows":[{"from":[{"model":"profile"}],"makes":"the findings","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The executor resolves the profiles, matches each method's platform to a component, runs the body and writes the finding."},"benchmark":{"note":"Ships the guide as a catalog carrying its own executable methods: the author of the requirement is the author of the check.","writes":[{"model":"catalog"}]},"engine":{"note":"Publishes a profile that imports a catalog untouched and adds executable methods for its engine.","writes":[{"model":"profile"}]},"mapper":{"note":"Edits the profile that puts the objective and the method on the framework control. Placing the part is the tie.","writes":[{"model":"profile"}]},"owner":{"note":"The selection and the plan of record. A run of the checks writes findings, not responses, so an owner who runs them is assessing.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"writes":[{"model":"catalog"}]}}},"groups":[{"key":"guidance","label":"Hardening guidance authors","note":"One role, two kinds of organisation, the same model. Nothing downstream can tell which of them wrote a rule."},{"key":"automation","label":"Automation tools and who runs them","note":"The policy engine and the automation tool are the same thing. A provider builds it, and whoever runs it decides what comes out."}],"intro":"Seven parties touch a hardening rule between a published guide and an audited system, and each works in an OSCAL model. Two sets of them are grouped: the bodies that author guidance, and the automation.","note":"Seven parties touch a hardening rule between the body that writes it and the auditor who reads the outcome, and each one works in an OSCAL model. Which model is the whole of what an approach asks of a party, so this is a mapping rather than an argument. Two entries need their component type named, because the same model does two jobs for two different parties. Two sets of the seven are grouped. The bodies that author hardening guidance are one role played by two kinds of organisation. The automation is a policy engine and the two parties that run it: a provider builds the tool and runs nothing, which is why its flows name whoever executes them, and the system owner and the auditor are those parties. The mapping provider is a party of its own because a hardening guide does not always carry the tie to a framework: a STIG carries CCIs and it is DISA's separate CCI list that names the 800-53 controls, and third parties publish mappings of their own through NIST's OLIR programme. Whoever writes the guide is often not whoever ties it to the framework. One approach lets parties other than the system owner write a profile, and shared_profile records which and why.","parties":[{"key":"regulatory","name":"Regulatory control providers","who":"NIST with SP 800-53, and bodies like it"},{"key":"mapper","name":"Mapping providers","who":"DISA's CCI list, NIST's OLIR programme, the Secure Controls Framework and bodies like them, tying a guide to a framework"},{"group":"guidance","key":"benchmark","name":"Technical hardening guidance providers","who":"CIS, DISA and other benchmark publishers"},{"group":"guidance","key":"software","name":"Software providers","who":"Vendors publishing secure configuration guidance for their own product, alone or with a body such as CIS"},{"group":"automation","key":"engine","name":"Policy engine providers","who":"OPA, Kyverno, ScubaGear, OpenSCAP and the like, assessing, auditing and checking"},{"group":"automation","key":"owner","name":"System owners","who":"Implementing these concepts on a real system"},{"group":"automation","key":"auditor","name":"Independent auditors","who":"Running the same checks independently of the system owner, and reading the outcome"}],"runtime":"A tool reads OSCAL, executes, and writes OSCAL. The party in this row builds it; the party on each flow runs it.","shared_profile":{"profile-first":{"parties":["mapper","engine"],"why":"The profile is still the system owner's selection, and it is also the document a third party adds a check with. A tool vendor publishes a profile that imports a catalog untouched and adds executable methods; a mapping provider edits the profile that puts a check on a framework control. The site records this as the approach's own position rather than as a row drawn wrong: tools/verify.py holds every other approach to the rule that nobody but the owner writes a profile."}}},"data/tradeoffs.json":{"approaches":{"assessment-first":{"cons":[{"body":"A required value is written into the activity title, so selection means writing a plan rather than resolving a profile.","title":"No parameter to resolve"},{"body":"The model runs activity to step, and guidance that nests four levels deep has two of them to land in.","title":"Two tiers, where a guide is sometimes deeper"},{"body":"The result names a plan no file here carries and gives an observation a subject type the model does not define.","title":"The published set does not join up"}],"intro":"Considerations when introducing technical hardening guidance as an assessment plan have been captured","pros":[{"body":"The plan points at the document holding the claim rather than making one, so adding or retiring a guide touches the assessment plan alone.","title":"The plan of record does not move"},{"body":"A result is a document of its own importing a plan, and the corpus ships one whose findings target objectives and rest on observations.","title":"Plan to result is a lifecycle this layer has"},{"body":"A subject can be an inventory item, so two hosts of one operating system configured differently each carry their own finding.","title":"The subject is whatever was assessed"},{"body":"A task carries a schedule and names the platform that runs it, which no other approach expresses.","title":"Execution context travels with the plan"}]},"catalog-first":{"cons":[{"body":"Benchmark requirements join the regulatory controls the plan of record already answers, and whether each new catalog needs its own plan is unsettled.","title":"More models to keep"},{"body":"Several frameworks and several benchmarks multiply catalogs, profiles and mappings, raising the entry cost for tools and producing hard profile resolution cases.","title":"More complexity to resolve"},{"body":"A response is a by-component, so it names a component and never an instance, and one exception among a hundred hosts cannot be recorded.","title":"The response cannot be made per instance"}],"intro":"Considerations when introducing technical hardening controls as a catalog have been captured","pros":[{"body":"Technical requirements are defined in the catalog and tracked through the remaining models exactly as regulatory controls are.","title":"Requirements of any kind stay in one model"},{"body":"A profile gives a hardening guide organizationally defined parameters and selects the part of it an organisation holds itself to.","title":"Rules can be tailored"},{"body":"Controls, parts and nested groups carry checks, remediation and prose at the scale of a thousand-page guide.","title":"The catalog absorbs the shape of real guides"},{"body":"The tie to a framework is its own mapping-collection, so a third party can publish it without owning either catalog.","title":"The mapping is a document someone else can write"}]},"component-first":{"cons":[{"body":"The proposal changes the component definition, the plan of record, the assessment plan and the result, so today it is a proposal.","title":"Four models have to change"},{"body":"Rules describing how a component should be configured join a document whose job is to say how the system actually is today.","title":"Desired state enters the plan of record"},{"body":"Rationale, audit procedure and remediation are most of a published guide, and the shipped rules carry none of them.","title":"The fidelity fields are proposed, not carried"},{"body":"An exception reaches a rule but still not an instance, because the response is a by-component here too.","title":"The response is still not per instance"},{"body":"For a claim to reach a host rather than a class, implementing-rules would have to be carried by inventory items as well.","title":"Inventory items may need it too"}],"intro":"Considerations when introducing technical hardening rules into a component definition have been captured","pros":[{"body":"A component definition says how a component can meet a control, the world of possibility for software, and rules inside it make that document drive automation.","title":"One artifact serves the reader and the tool"},{"body":"The rule sits on the product and the check on a second component, so a second engine is a second component.","title":"The rule and the check are separate things"},{"body":"The proposed implementing-rules closes the distance between saying a control is implemented and saying which rule implements it.","title":"The claim can name the rule it rests on"},{"body":"Vendors are told to describe how their product can meet requirements in a component definition, so the rules land in one model.","title":"Vendors already have advice for this model"}]},"profile-first":{"cons":[{"body":"A profile resolved from a URL and executed is a remote code path into every assessed system, with the profile author as its operator.","title":"The catalog becomes code"},{"body":"Language, evaluation and pass condition are conventions in a placeholder namespace, and an executor that does not know them can run nothing.","title":"The vocabulary has no owner"},{"body":"The platform prop is a CPE and nothing on an SSP component carries one, so which host runs a check is decided outside the schema.","title":"The subject is matched by convention"},{"body":"The finding targets the objective and the response the control, so the plan of record cannot say which checks its claim rests on.","title":"The claim never meets the result"}],"intro":"Considerations when attaching executable assessment methods to controls in a catalog or a profile have been captured","pros":[{"body":"A profile can add parts, props, links and params to a control, so a third party attaches a check to a catalog it does not own.","title":"The check travels with the requirement"},{"body":"A control's params reach the body as environment variables, so one script serves many controls and every organisation its own value.","title":"Parameters feed the script"},{"body":"The method links to an assessment objective, so a finding targets an objective id that every consumer built for 800-53A already reads.","title":"Findings need no new field"},{"body":"The methods sit on controls the assessment plan reads, so a guide with hundreds of checks adds no control to the system security plan.","title":"The plan of record does not grow"}]}},"note":"Strengths and risks per approach. The counts are not held equal: they were, three a side on every page, so that the shape of the block could not itself be an argument, and that rule was dropped when it started deciding what could be said. An approach has the risks it has. What is still held is that no approach is argued at greater length than another, which tools/approach_pages.py enforces across the four pages. No figures: the site describes one scenario, on one page, and every count belongs there. What each entry rests on is recorded in BUILD-LOG.md and, where it is a claim about what a model can express, in the schema_evidence field here, which is checked but not rendered."},"data/views.json":{"automation_argument":{"claim":"Hardening guidance is predominantly and increasingly automated, both to apply and to verify, which distinguishes it from a regulatory control in kind rather than in granularity.","claim_not_made":"That hardening guidance is never performed manually. The corpus contradicts that stronger form and the site does not assert it.","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, all of them, and every activity carries method EXAMINE","note":"The counterexample. Published because it is what makes the other two rows credible.","stat_keys":["cis_postgres_automated","cis_postgres_manual"]}]},"crux":{"note":"Brian Ruf's objection applies to any option, not only to the one it was raised against.","quote":"brian-not-normative"},"note":"Three views of what a hardening rule is. Each is internally coherent and each implies a different home. Four approaches share the three readings: aligned_approach names the approach a reading was stated for, and also_aligned names a later approach that holds the same reading of the rule and differs in the construct that carries it. The site takes no position on which is correct and declares a working definition instead. Rendered in the order given, which is the order of the OSCAL layers and not a ranking. The advocate and quote fields are retained as provenance and are NOT rendered: per the Gate 7 decision, no personal name, proponent organization or quotation appears on any page. Each view also names the stakeholder it serves, joining to the glossary term of that name, because the three stakeholders and the three readings are the same three-way split seen from two sides.","views":[{"advocate":"Fritz Kunstler, AWS","aligned_approach":"catalog-first","also_aligned":["profile-first"],"also_aligned_note":"Profile-first reads the rule the same way and puts it in the same layer. What differs is the construct: the rule is an assessment objective part on the control rather than a control of its own, so the check can sit beside it and a profile can add both.","definition":"Normative. A shall. A control by another name, differing from a regulatory control only in specificity.","implies_layer":"Control","implies_model":"catalog","key":"requirement","label":"A requirement","quote":"fritz-standard-setter","stakeholder":"publisher","supporting_quotes":["fritz-catalogs-for-requirements"]},{"advocate":"Anca Sailer and Vikas Agarwal, IBM","aligned_approach":"component-first","definition":"Descriptive. How a component may be configured. The vendor states what is possible; the organization decides what is required.","implies_layer":"Implementation","implies_model":"component-definition","key":"capability","label":"A capability statement","quote":"deck-may-be-configured","stakeholder":"implementer","supporting_quotes":["fritz-possible-state","vikas-cdef-automation"]},{"advocate":"Easy Dynamics","aligned_approach":"assessment-first","definition":"Guidance that is never performed by hand. It is automated to apply and automated to verify, so its natural expression is the thing that does the applying and the verifying.","implies_layer":"Assessment","implies_model":"assessment-plan","key":"procedure","label":"An assessor's procedure","quote":"pranav-assessment-start","stakeholder":"assessor","supporting_quotes":["dave-as-intended"]}],"why_this_matters":"OSCAL has no field for normativity. The pre-read's criterion 3 records requirement level as absent from OSCAL entirely, an orthogonal gap affecting every option. Location has therefore become the only channel available for expressing which of these three views an author holds.","working_definition":{"status":"A working definition adopted so that three comparable pages can be written. It is not a position on which of the three views is correct.","term":"rule","text":"One technical requirement or recommendation, at a granularity finer than a control, without any claim about whether it is binding."}}}; diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/diagrams/710-scenario-assessment.svg b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/diagrams/710-scenario-assessment.svg index 86727aa..a6ae40c 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/diagrams/710-scenario-assessment.svg +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/diagrams/710-scenario-assessment.svg @@ -1,6 +1,6 @@ One system, three hardening guides: the file set for the assessment first approach - A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 11 files in total, across 5 of the seven models. 1 catalog file, the framework only, named NIST 800-53. 1 profile file, the High baseline, named 800-53 High. 0 mapping-collection files, none, the tie is on the activity. 0 component-definition files, none, the engines are named inside each plan. 1 system-security-plan file, one, answering 370 controls, named System SSP. 4 assessment-plan files, one for the framework assessment, one per guide, named 800-53 AP, CIS Ubuntu AP, DISA PgSQL AP, CISA SCuBA AP. 4 assessment-results files, one per plan, because a result names exactly one plan, named 800-53 AR, CIS Ubuntu AR, DISA PgSQL AR, CISA SCuBA AR. A model this approach does not use is drawn hollow and labelled none, so the absence is as visible as the presence. The tile is the same size in all three figures, so the area of ink is the comparison. The plan of record answers 370 controls, and none of the three guides enters it. + A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 11 files in total, across 5 of the seven models. 1 catalog file, the framework only, named NIST 800-53. 1 profile file, the High baseline, named 800-53 High. 0 mapping-collection files, none, the tie is on the activity. 0 component-definition files, none, the engines are named inside each plan. 1 system-security-plan file, one, answering 370 controls, named System SSP. 4 assessment-plan files, one for the framework assessment, one per guide, named 800-53 AP, CIS Ubuntu AP, DISA PgSQL AP, CISA SCuBA AP. 4 assessment-results files, one per plan, because a result names exactly one plan, named 800-53 AR, CIS Ubuntu AR, DISA PgSQL AR, CISA SCuBA AR. A model this approach does not use is drawn hollow and labelled none, so the absence is as visible as the presence. The tile is the same size in all four figures, so the area of ink is the comparison. The plan of record answers 370 controls, and none of the three guides enters it. @@ -57,6 +56,7 @@
  • Catalog-first
  • Component-first
  • Assessment-first
  • +
  • Profile-first
  • Open questions
  • OSCAL artifacts
  • @@ -71,8 +71,8 @@
    diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.css b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.css index c0effc5..c6d797c 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.css +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.css @@ -147,16 +147,17 @@ on the three-readers figure, and nothing else. Three constraints decided them, in this order. - 1. Equal weight. All three sit at CIE L* 47 (light) / L* 71 (dark) and at + 1. Equal weight. All four sit at CIE L* 47 (light) / L* 71 (dark) and at the same chroma, so no approach is louder than another. Equal lightness is what neutrality requires here and it is the opposite of the question palette, whose whole point is a lightness ladder. - 2. No valence. The hues are 185, 265 and 340: teal, blue, mauve. A - 120-degree triad would have forced a red, a green and an amber onto - three positions in a live disagreement, which is an argument no word - count can see. + 2. No valence. The hues are 185, 265, 340 and 100: teal, blue, mauve, + olive. A 120-degree triad would have forced a red, a green and an + amber onto three positions in a live disagreement, which is an + argument no word count can see, and the fourth hue was chosen in the + widest gap the first three left rather than at a red or a green. 3. Hue is decorative. Because lightness is equal, dichromats cannot - separate these three, and that is accepted: approach identity on every + separate these four, and that is accepted: approach identity on every diagram is carried by outline offset, by a marker shape and by a written label. Colour only reinforces. verify.py --a11y asserts the equal-luminance property; verify.py --diagrams asserts that every @@ -170,6 +171,11 @@ --approach-assessment: #007E73; /* hue 185, 4.96:1 on --bg */ --approach-catalog: #3B74A5; /* hue 265, 4.97:1 on --bg */ --approach-component: #985C82; /* hue 340, 5.01:1 on --bg */ + /* The fourth arrived after the palette was built and took the hue the other + three had left widest open: 100, an olive, at the same L* 47 and the same + chroma, so the equal-weight rule holds for four as it held for three and + nothing the first three carried had to move. */ + --approach-profile: #777139; /* hue 100, 4.99:1 on --bg */ /* --- the three OSCAL layers --------------------------------------------- The model icons are coloured by layer, not by approach. A model belongs to @@ -292,10 +298,11 @@ --empty-absent-fill: #262D38; - /* Same three hues, lifted to L* 71 and held equal. 8.2:1 on --bg. */ + /* Same four hues, lifted to L* 71 and held equal. 8.1:1 on --bg. */ --approach-assessment: #00C3B3; --approach-catalog: #60B4FD; --approach-component: #EA91CA; + --approach-profile: #BAAF5D; /* The layers keep their hue and invert their lightness: the chip becomes a dark tint of the same hue and the ink lifts off it. Same three-way coding, 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 0fe03f0..9aaaa20 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 @@ -211,9 +211,10 @@ A cell used to carry one prose line describing the construct, and it read differently in every cell: sometimes an assembly name, sometimes a sentence about a document. The model was the thing it kept leaving out, and the model - is the first thing that differs between the three approaches: the same - requirement is a control in one, a component in another and an activity in - the third. So both are named, in the same order, in every cell. */ + is the first thing that differs between the approaches: the same + requirement is a control in one, a component in another, an activity in a + third and a part on a control in the fourth. So both are named, in the + same order, in every cell. */ /* --- lineage: what goes into the runner and what comes out -------------- Question 5 is the only one whose answer is a step rather than a place. The @@ -302,7 +303,8 @@ the same checks to produce a result, from a plan they own. Two paths, one file in and one file out each, and the difference between the approaches is which of the two they have: catalog-first has the implementer's, - assessment-first has the assessor's, component-first has both. + assessment-first and profile-first have the assessor's, component-first + has both. The tiles are anchors into the questions that hold the documents, because both ends are already answered on this page and this is the lineage between @@ -920,11 +922,13 @@ that repeats once per approach is a loop over one list in one order, so equal budget is a property of the code rather than a thing to remember. */ - /* The order the working group's pre-read puts the three in. The site no - longer shows the letters, but the order is still theirs rather than ours, - which is the point. One list, read by every renderer, so no component can - order the three differently from another. */ - var OPTION_ORDER = ["catalog-first", "component-first", "assessment-first"]; + /* The order the working group's pre-read puts the three in, with the + fourth, which arrived after the pre-read, after them. The site no longer + shows the letters, but the order is still theirs rather than ours, which + is the point. One list, read by every renderer, so no component can order + the four differently from another. */ + var OPTION_ORDER = ["catalog-first", "component-first", "assessment-first", + "profile-first"]; function el(tag, cls, text) { var n = document.createElement(tag); @@ -1317,6 +1321,24 @@ h.appendChild(el("span", "criteria-table__who", p.option)); sec.appendChild(h); + /* An approach that has published nothing has no rows to count, and + a section with no rows has to say why rather than end after its + heading. The data carries the note and the one document that does + exist, and the section shows both and nothing else. */ + if (!p.files.length) { + sec.appendChild(el("p", null, p.note || "Nothing published.")); + if (p.document) { + var pd = el("p", "small"); + var da = el("a", null, p.document.label); + da.href = BASE + "/" + p.document.href; + da.className = "artifact__link"; + pd.appendChild(da); + sec.appendChild(pd); + } + node.appendChild(sec); + return; + } + var totals = Object.keys(p.totals).map(function (k) { return p.totals[k] + " " + (p.totals[k] === 1 ? k.toLowerCase() : k.toLowerCase() + "s"); diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/catalog-first.html b/docs/analysis/2026-08-automating-technical-hardening-guidance/catalog-first.html index d4a98b1..d358c30 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/catalog-first.html +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/catalog-first.html @@ -40,6 +40,7 @@
  • Catalog-first
  • Component-first
  • Assessment-first
  • +
  • Profile-first
  • Open questions
  • OSCAL artifacts
  • @@ -163,8 +164,8 @@

    3. Tracing rules and checks from implementation to assessment

    nothing filled. One footer, one place. -->
    diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/component-first.html b/docs/analysis/2026-08-automating-technical-hardening-guidance/component-first.html index da1d398..2ec73cd 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/component-first.html +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/component-first.html @@ -40,6 +40,7 @@
  • Catalog-first
  • Component-first
  • Assessment-first
  • +
  • Profile-first
  • Open questions
  • OSCAL artifacts
  • @@ -174,8 +175,8 @@

    3. Tracing rules and checks from implementation to assessment

    nothing filled. One footer, one place. -->
    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 720770a..b781d5c 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 @@ -2,8 +2,9 @@ "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.", "written_by": "tools/approach_pages.py", "sha256": { - "assessment-first": "69754a8b9eaca4d372faed1e23d33fc89b524d09b3569e5fbe06110c9d749696", - "catalog-first": "f2381215aa6af548dca3cb5c59fc8d985964db349332454ffdab843069c38e56", - "component-first": "fd739ade4dd4568f7cac3dec242a5630a67feeef85ba13d70429ce8e6618df24" + "assessment-first": "0ed6bfd853bdf97996b91081091962497e2360189c99afdcc20c0e5d6c86cbb1", + "catalog-first": "5fa8281a55085dbc46a4902084e3346ca0b81d51d5762b8ba0a46c58809a437e", + "component-first": "9d366a2413bfd65340030f71de9141ae2d0bb851114f282f03a90d1775416316", + "profile-first": "0709a97f7564fa0bb995019bac16c4d6de792f485bd55c004e7ceddc3f045d49" } } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/glossary.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/glossary.json index 966fe98..fd97b19 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/glossary.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/glossary.json @@ -14,6 +14,10 @@ "usage": "A statement of how a component may be configured, descriptive rather than binding", "who": "Component-first, Option B, and a position paper" }, + { + "usage": "An assessment objective on a control, with an executable assessment method beside it", + "who": "Profile-first, Option D" + }, { "usage": "Colloquially, the check code itself", "who": "Used loosely across the working group, and flagged in the record by its own author" @@ -404,6 +408,44 @@ "implementer", "check" ] + }, + { + "term": "assessment objective", + "status": "settled", + "site_usage": "A part on a control, named assessment-objective in the NIST catalogs, stating what an assessor determines. A finding can target its id. In the profile-first approach it is the rule, added to the control by the catalog or by a profile.", + "other_usages": [], + "see_also": [ + "assessment method", + "finding", + "rule" + ] + }, + { + "term": "assessment method", + "status": "settled", + "site_usage": "A part on a control, named assessment-method, carrying a method prop of EXAMINE, INTERVIEW or TEST. Catalog-first uses it to name the check; profile-first gives the TEST method a body and the props an executor needs to run it.", + "other_usages": [], + "see_also": [ + "assessment objective", + "executable assessment method", + "check" + ] + }, + { + "term": "executable assessment method", + "status": "contested", + "site_usage": "The profile-first construct: an assessment-method part with method TEST, namespaced props for platform, engine, evaluation rule, pass condition and timeout, and a script body in prose or in a back-matter resource. The namespace is a placeholder and the vocabulary has no owner, which is why the term is contested rather than settled.", + "other_usages": [ + { + "usage": "A namespaced automation-script assembly on an implemented requirement", + "who": "An earlier draft the concept note itself sets aside" + } + ], + "see_also": [ + "assessment method", + "check", + "profile" + ] } ] } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/joins.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/joins.json index 40c476d..0bebc29 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/joins.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/joins.json @@ -1,5 +1,5 @@ { - "note": "The six questions are answered one at a time, which hides the thing that decides whether the set works: what joins one answer to the next. This is the chain from the moment the rule is introduced to the moment something records that it was met, with every foreign key and the primary key it resolves to. Every literal is one of the two running rules as the six questions page encodes it, so the three chains can be read against each other; tools/verify.py fails the build if a value here is not in that encoding.", + "note": "The six questions are answered one at a time, which hides the thing that decides whether the set works: what joins one answer to the next. This is the chain from the moment the rule is introduced to the moment something records that it was met, with every foreign key and the primary key it resolves to. Every literal is one of the two running rules as the six questions page encodes it, so the four chains can be read against each other; tools/verify.py fails the build if a value here is not in that encoding.", "title": "What joins one answer to the next", "intro": "The chain starts where the rule is introduced and runs to the claim and the result. What a step costs is how many relationships it is made of and how each one resolves.", "stages": [ @@ -648,6 +648,181 @@ ] } ] + }, + "profile-first": { + "introduced": { + "model": "profile", + "field": "alters[].adds[].parts[].id", + "value": "sc-28_obj-ubtu-24-600090", + "slot": "1", + "note": "The rule is an assessment objective part, added to the framework control by a profile. Every step below starts from that part id." + }, + "hops": [ + { + "from": "rule", + "to": "check", + "how": "reference", + "note": "Both parts sit in one alter, and the method links to the objective by id, inside one document.", + "pairs": [ + { + "foreign": { + "model": "profile", + "field": "parts[assessment-method].links[rel=assessment-objective].href", + "value": "#sc-28_obj-ubtu-24-600090", + "slot": "3" + }, + "primary": { + "model": "profile", + "field": "parts[assessment-objective].id", + "value": "sc-28_obj-ubtu-24-600090", + "slot": "1" + }, + "how": "reference" + } + ] + }, + { + "from": "rule", + "to": "control", + "how": "containment", + "note": "The parts are added to the control the alter names. Placing them is the tie, and no second identifier exists.", + "pairs": [ + { + "foreign": { + "model": "profile", + "field": "no field", + "slot": "1" + }, + "primary": { + "model": "profile", + "field": "alters[].control-id", + "value": "sc-28", + "slot": "2" + }, + "how": "containment" + }, + { + "foreign": { + "model": "profile", + "field": "alters[].control-id", + "value": "sc-28", + "slot": "2" + }, + "primary": { + "model": "catalog", + "field": "controls[].id", + "value": "sc-28", + "slot": "2", + "where": "the framework catalog" + }, + "how": "reference" + } + ] + }, + { + "from": "check", + "to": "runtime", + "how": "none", + "note": "The props name an engine by a token and say how to judge its result. The executor that honours them is outside OSCAL.", + "pairs": [ + { + "foreign": { + "model": "profile", + "field": "parts[assessment-method].props[name=language].value", + "value": "bash", + "slot": "3" + }, + "primary": { + "model": "nothing", + "field": "no field", + "slot": "5" + }, + "how": "none" + }, + { + "foreign": { + "model": "profile", + "field": "parts[assessment-method].props[name=evaluation].value", + "value": "exit-code", + "slot": "3" + }, + "primary": { + "model": "nothing", + "field": "no field", + "slot": "5" + }, + "how": "none" + } + ] + }, + { + "from": "runtime", + "to": "claim", + "how": "none", + "note": "The run writes no response. The plan of record is untouched by design, so nothing joins the check to the owner's claim.", + "pairs": [ + { + "foreign": { + "model": "profile", + "field": "no field", + "slot": "5" + }, + "primary": { + "model": "system-security-plan", + "field": "by-components[].description", + "slot": "6a" + }, + "how": "none" + } + ] + }, + { + "from": "runtime", + "to": "result", + "how": "reference", + "note": "The observation names the host and carries the raw output as evidence, so two machines behind one component can disagree.", + "pairs": [ + { + "foreign": { + "model": "assessment-results", + "field": "observations[].subjects[].subject-uuid", + "value": "06297a03-cae0-414b-8332-2fc882f81aa1", + "slot": "6b" + }, + "primary": { + "model": "system-security-plan", + "field": "system-implementation.inventory-items[].uuid", + "value": "06297a03-cae0-414b-8332-2fc882f81aa1", + "slot": "4" + }, + "how": "reference" + } + ] + }, + { + "from": "result", + "to": "control", + "how": "reference", + "note": "The finding targets the objective the profile added, so a result reads against the framework with no plan of record.", + "pairs": [ + { + "foreign": { + "model": "assessment-results", + "field": "findings[].target.target-id", + "value": "sc-28_obj-ubtu-24-600090", + "slot": "6b" + }, + "primary": { + "model": "profile", + "field": "alters[].adds[].parts[].id", + "value": "sc-28_obj-ubtu-24-600090", + "slot": "1" + }, + "how": "reference" + } + ] + } + ] } } } 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 4a4d41d..6605ff1 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 @@ -430,6 +430,22 @@ } ], "rollup": null + }, + { + "key": "profile-first", + "name": "Profile-first", + "full_name": "Option D", + "option": "Option D", + "repo": null, + "root": null, + "totals": {}, + "files": [], + "rollup": null, + "note": "No OSCAL document has been published for this approach. What exists is a concept note, and the encodings on the six questions page are the site's own rendering of the shape that note proposes.", + "document": { + "href": "examples/profile-first/executable-assessment-methods.md", + "label": "Executable Assessment Methods, a concept note, September 2026" + } } ] } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/pattern-examples.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/pattern-examples.json index 20c7b95..f36eb67 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/pattern-examples.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/pattern-examples.json @@ -1,8 +1,8 @@ { - "note": "Our own encodings. Two rules, written in all three shapes, so the only thing that changes between the columns is the modelling.", + "note": "Our own encodings. Two rules, written in all four shapes, so the only thing that changes between the columns is the modelling.", "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." + "why": "One target, so the only thing that changes between the four columns is the modelling. Ubuntu because both rules are published for it, by DISA, and a reader can check them." }, "rules": [ { @@ -122,6 +122,34 @@ ] ] } + ], + "profile-first": [ + { + "rule": "data-at-rest", + "label": "Rule 1, data at rest", + "shows": "An assessment objective part, added to the framework control by a profile. The requirement is the part's prose, and a value is a parameter the same add declares and sets.", + "content": "{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 }\n ]\n }\n ]\n }\n }\n}", + "focus_key": "name=assessment-objective", + "focus": [ + [ + 11, + 15 + ] + ] + }, + { + "rule": "password-min-length", + "label": "Rule 2, minimum password length", + "shows": "An assessment objective part, added to the framework control by a profile. The requirement is the part's prose, and a value is a parameter the same add declares and sets.", + "content": "{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"ia-5.1\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"parts\": [\n {\n \"id\": \"ia-5.1_obj-ubtu-24-400320\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}", + "focus_key": "name=assessment-objective", + "focus": [ + [ + 20, + 24 + ] + ] + } ] }, "2": { @@ -173,6 +201,25 @@ ] ] } + ], + "profile-first": [ + { + "rule": "both", + "label": "Both rules and their control ties", + "shows": "The placement is the tie. The profile imports the framework catalog and alters the control by id, and the parts go inside the alter, so the only identifier in play is the control's own.", + "content": "{\n \"profile\": {\n \"imports\": [\n {\n \"href\": \"./NIST_SP-800-53_rev5_catalog.json\",\n \"include-controls\": [\n {\n \"with-ids\": [\n \"sc-28\",\n \"ia-5.1\"\n ]\n }\n ]\n }\n ],\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 }\n ]\n },\n {\n \"control-id\": \"ia-5.1\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"parts\": [\n {\n \"id\": \"ia-5.1_obj-ubtu-24-400320\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}", + "focus_key": "control-id", + "focus": [ + [ + 19, + 19 + ], + [ + 34, + 34 + ] + ] + } ] }, "3": { @@ -272,6 +319,34 @@ ] ] } + ], + "profile-first": [ + { + "rule": "data-at-rest", + "label": "Rule 1, data at rest", + "shows": "An assessment method part beside the objective, with method TEST, a script body in its prose, five namespaced props saying how to run and judge it, and a link to the objective it tests.", + "content": "{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 \"id\": \"sc-28_asm-ubtu-24-600090\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270747r1066730_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#sc-28_obj-ubtu-24-600090\"\n }\n ],\n \"prose\": \"```bash\\nlsblk -rno TYPE | grep -q '^crypt$'\\n```\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}", + "focus_key": "name=assessment-method", + "focus": [ + [ + 16, + 58 + ] + ] + }, + { + "rule": "password-min-length", + "label": "Rule 2, minimum password length", + "shows": "An assessment method part beside the objective, with method TEST, a script body in its prose, five namespaced props saying how to run and judge it, and a link to the objective it tests.", + "content": "{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"ia-5.1\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"parts\": [\n {\n \"id\": \"ia-5.1_obj-ubtu-24-400320\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n },\n {\n \"id\": \"ia-5.1_asm-ubtu-24-400320\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270732r1066685_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#ia-5.1_obj-ubtu-24-400320\"\n }\n ],\n \"prose\": \"```bash\\nminlen=$(grep -E '^\\\\s*minlen' /etc/security/pwquality.conf | cut -d= -f2 | tr -d ' ')\\ntest \\\"${minlen:-0}\\\" -ge \\\"$password_min_length\\\"\\n```\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}", + "focus_key": "name=assessment-method", + "focus": [ + [ + 25, + 67 + ] + ] + } ] }, "4": { @@ -332,6 +407,34 @@ ] ] } + ], + "profile-first": [ + { + "rule": "both", + "label": "What the checks run against", + "shows": "Whatever component the platform prop matches, by convention.", + "content": "{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 \"id\": \"sc-28_asm-ubtu-24-600090\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270747r1066730_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#sc-28_obj-ubtu-24-600090\"\n }\n ],\n \"prose\": \"```bash\\nlsblk -rno TYPE | grep -q '^crypt$'\\n```\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}", + "focus_key": "name=platform", + "focus": [ + [ + 25, + 29 + ] + ] + }, + { + "rule": "subject", + "label": "The component it matches, in the plan of record", + "shows": "The executor matches the method's platform against a component and runs the body on the inventory items that implement it. Nothing on either carries a CPE.", + "content": "{\n \"system-security-plan\": {\n \"system-implementation\": {\n \"components\": [\n {\n \"uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"description\": \"Ubuntu 24.04 LTS as a component of the system.\",\n \"status\": {\n \"state\": \"operational\"\n }\n }\n ],\n \"inventory-items\": [\n {\n \"uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"description\": \"Application host 1, running Ubuntu 24.04 LTS.\",\n \"implemented-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n }\n ]\n }\n ]\n }\n }\n}", + "focus_key": "inventory-items", + "focus": [ + [ + 15, + 25 + ] + ] + } ] }, "5": { @@ -480,6 +583,50 @@ ] ] } + ], + "profile-first": [ + { + "rule": "assessor-in", + "label": "What the run reads: the methods on the resolved profile", + "shows": "The methods the run is handed, each saying which engine runs it and how to judge the result.", + "content": "{\n \"profile\": {\n \"modify\": {\n \"alters\": [\n {\n \"control-id\": \"sc-28\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"parts\": [\n {\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\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 \"id\": \"sc-28_asm-ubtu-24-600090\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270747r1066730_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#sc-28_obj-ubtu-24-600090\"\n }\n ],\n \"prose\": \"```bash\\nlsblk -rno TYPE | grep -q '^crypt$'\\n```\"\n }\n ]\n }\n ]\n },\n {\n \"control-id\": \"ia-5.1\",\n \"adds\": [\n {\n \"position\": \"ending\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"parts\": [\n {\n \"id\": \"ia-5.1_obj-ubtu-24-400320\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n },\n {\n \"id\": \"ia-5.1_asm-ubtu-24-400320\",\n \"name\": \"assessment-method\",\n \"title\": \"SV-270732r1066685_rule\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:*:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"language\",\n \"value\": \"bash\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"evaluation\",\n \"value\": \"exit-code\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"0\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"timeout\",\n \"value\": \"PT60S\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#ia-5.1_obj-ubtu-24-400320\"\n }\n ],\n \"prose\": \"```bash\\nminlen=$(grep -E '^\\\\s*minlen' /etc/security/pwquality.conf | cut -d= -f2 | tr -d ' ')\\ntest \\\"${minlen:-0}\\\" -ge \\\"$password_min_length\\\"\\n```\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}", + "focus_key": "props", + "focus": [ + [ + 20, + 50 + ], + [ + 87, + 117 + ] + ] + }, + { + "rule": "assessor-out", + "label": "What the run produces: the finding and its observation", + "shows": "The finding targets the objective the profile added, and the observation names the host and carries the script's output as evidence.", + "content": "{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for sc-28_obj-ubtu-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj-ubtu-24-600090\",\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 ia-5.1_obj-ubtu-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj-ubtu-24-400320\",\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 \"description\": \"The executable method ran on the host and exited 0.\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"relevant-evidence\": [\n {\n \"description\": \"Exit code 0, with standard output and standard error as the executor captured them.\"\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 \"description\": \"The executable method ran on the host and exited 0.\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"relevant-evidence\": [\n {\n \"description\": \"Exit code 0, with standard output and standard error as the executor captured them.\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}", + "focus_key": "target-id, relevant-evidence", + "focus": [ + [ + 11, + 11 + ], + [ + 27, + 27 + ], + [ + 53, + 57 + ], + [ + 73, + 77 + ] + ] + } ] }, "6a": { @@ -553,6 +700,34 @@ ] ] } + ], + "profile-first": [ + { + "rule": "data-at-rest", + "label": "Rule 1, data at rest", + "shows": "A by-component response in the SSP, against the framework control, exactly as it would be without the approach. Nothing on it names the objective the check tested.", + "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 \"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}", + "focus_key": "by-components", + "focus": [ + [ + 8, + 14 + ] + ] + }, + { + "rule": "password-min-length", + "label": "Rule 2, minimum password length", + "shows": "A by-component response in the SSP, against the framework control, exactly as it would be without the approach. Nothing on it names the objective the check tested.", + "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 \"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}", + "focus_key": "by-components", + "focus": [ + [ + 8, + 14 + ] + ] + } ] }, "6b": { @@ -639,6 +814,34 @@ ] ] } + ], + "profile-first": [ + { + "rule": "data-at-rest", + "label": "Rule 1, data at rest", + "shows": "A finding, targeting the objective the profile added, over an observation that names the host and carries the output.", + "content": "{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for sc-28_obj-ubtu-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj-ubtu-24-600090\",\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 \"description\": \"The executable method ran on the host and exited 0.\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"relevant-evidence\": [\n {\n \"description\": \"Exit code 0, with standard output and standard error as the executor captured them.\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}", + "focus_key": "findings", + "focus": [ + [ + 5, + 22 + ] + ] + }, + { + "rule": "password-min-length", + "label": "Rule 2, minimum password length", + "shows": "A finding, targeting the objective the profile added, over an observation that names the host and carries the output.", + "content": "{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for ia-5.1_obj-ubtu-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj-ubtu-24-400320\",\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 \"description\": \"The executable method ran on the host and exited 0.\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"relevant-evidence\": [\n {\n \"description\": \"Exit code 0, with standard output and standard error as the executor captured them.\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}", + "focus_key": "findings", + "focus": [ + [ + 5, + 22 + ] + ] + } ] } } 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 872a623..0e768ef 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": "The open questions, in four sections: what is unsettled about OSCAL itself, then what is unsettled about each approach. Each is one line with the reasoning behind it. Questions reproduced from a source document keep that document's wording, including its errors, and are marked with where they came from, because rewriting someone else's question is a way of answering it.", + "note": "The open questions, in five sections: what is unsettled about OSCAL itself, then what is unsettled about each approach. Each is one line with the reasoning behind it. Questions reproduced from a source document keep that document's wording, including its errors, and are marked with where they came from, because rewriting someone else's question is a way of answering it.", "intro": "Nothing here is a proposal. Where the site has a fact that bears on a question, the fact is stated and the question is left open. Most of what is unsettled is about OSCAL rather than about any one approach, which is why the first section is the longest.", "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.", + "label": "Across all four approaches", + "intro": "Gaps in the models themselves. None is answered by choosing an approach, and each changes what all four can express.", "questions": [ { "id": "xccdf", @@ -136,6 +136,43 @@ "verbatim": "the position paper submitted to the working group" } ] + }, + { + "key": "profile-first", + "label": "Profile-first", + "intro": "The rule and the check are parts on a control. What is unsettled is who may put code there, who owns the vocabulary that runs it, and what the executor matches against.", + "questions": [ + { + "id": "executable-catalogs", + "q": "Who may put executable code on a control, and who signs it?", + "why": "A catalog or profile carrying executable methods is code, and an executor that resolves a profile from a URL and runs what it finds has installed a remote code path into every assessed system. The concept note asks for pinned hashes on every rlink, signed catalogs and profiles, an executor that refuses anything unverified, and read-only checks with remediation in a part of its own. None of that is agreed anywhere yet, and nothing in OSCAL distinguishes a part that describes from a part that executes." + }, + { + "id": "vocabulary-owner", + "q": "Who owns the vocabulary of platform, language, evaluation and pass condition?", + "why": "The five props carry everything an executor needs, and every one of them is a convention in a placeholder namespace. The note proposes Metaschema external constraints to hold the enumeration, the way FedRAMP holds its own vocabulary without forking the model, and names no body to publish them. Until one does, two vendors can ship two incompatible checks for one control and the profile author picks." + }, + { + "id": "platform-match", + "q": "What on a system security plan component does the platform CPE match against?", + "why": "The note matches the platform prop against the component in the plan of record, the way XCCDF matches its platform element. No field on an OSCAL component or inventory item carries a CPE, so the match is made on a convention the note leaves open, and it says itself that a plain token may serve as well. Which host a check runs on is decided wherever that convention is decided." + }, + { + "id": "profile-added-objective", + "q": "Does a finding resolve to an objective that only a profile added?", + "why": "The mechanism rests on findings targeting an objective id, and the objective exists only in the resolved profile: the catalog it imports has never heard of it. A consumer reading the result against the catalog alone, or against a profile resolved without the tool vendor's additions, finds no such objective. Whether every result reader resolves the profile first is not established." + }, + { + "id": "catalog-route-tie", + "q": "When a guide ships as a catalog with its own checks, what ties its objectives to the framework?", + "why": "The note answers the framework case by placement: a profile adds the check to the framework control, and the placement is the tie. Where the guide is its own catalog, as a benchmark with its own scripts would be, the finding targets the guide's objective and nothing in the note reaches the framework. A mapping collection reaches controls and statements, not parts, so that route is the one catalog-first already has and no wider." + }, + { + "id": "check-versions", + "q": "Is a changed check a new version of the catalog it sits in?", + "why": "The note accepts the coupling: a changed check is a new profile version, and a catalog that ships checks changes whenever one of them does. A benchmark already carries that coupling in its source material. A framework catalog does not, and the approach keeps it out of one by putting the checks in a profile, so the question is only open for the catalog route." + } + ] } ] } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/scenario.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/scenario.json index feba94b..88e9480 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/scenario.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/scenario.json @@ -1,10 +1,10 @@ { - "note": "One system, one baseline, three hardening guides, modelled three ways. The point of the scenario is that the three approaches do not differ in what they can express so much as in how many documents it takes to express it, and what the plan of record ends up holding. Every count is either recomputed from a corpus in this repository, read from the NIST profile stored in data/scenario-evidence/, or forced by the OSCAL schemas, and each says which. What the schemas force is stated on the file rows it explains rather than in a section of its own.", + "note": "One system, one baseline, three hardening guides, modelled four ways. The point of the scenario is that the four approaches do not differ in what they can express so much as in how many documents it takes to express it, and what the plan of record ends up holding. Every count is either recomputed from a corpus in this repository, read from the NIST profile stored in data/scenario-evidence/, or forced by the OSCAL schemas, and each says which. What the schemas force is stated on the file rows it explains rather than in a section of its own.", "title": "One system, three hardening guides", - "summary": "A system under NIST SP 800-53 Revision 5 at the High baseline, running Ubuntu, PostgreSQL and Microsoft 365, hardened against a published guide for each. The same scenario is modelled in all three approaches, using every OSCAL model except the plan of action and milestones.", + "summary": "A system under NIST SP 800-53 Revision 5 at the High baseline, running Ubuntu, PostgreSQL and Microsoft 365, hardened against a published guide for each. The same scenario is modelled in all four approaches, using every OSCAL model except the plan of action and milestones.", "excluded_model": { "model": "plan-of-action-and-milestones", - "reason": "It records what was not met and what is being done about it. That is the same document in all three approaches, so it separates none of them." + "reason": "It records what was not met and what is being done about it. That is the same document in all four approaches, so it separates none of them." }, "framework": { "label": "NIST SP 800-53 Revision 5, High baseline", @@ -368,6 +368,97 @@ } ], "plan_of_record": "The plan of record answers 370 controls, and none of the three guides enters it" + }, + "profile-first": { + "rule": "Each guide is published as a catalog whose controls carry their own executable methods, and each component references a profile selecting from it. The framework side is unchanged and the plan of record's control set does not move.", + "files": [ + { + "model": "catalog", + "count": 4, + "what": "one for the framework, one per guide, carrying its checks", + "detail": "800-53 Revision 5 untouched, and CIS Ubuntu, DISA PostgreSQL and CISA SCuBA each as a catalog whose controls carry an assessment objective and an executable assessment method, because the author of the requirement is the author of the check", + "items": [ + { + "name": "NIST 800-53" + }, + { + "name": "CIS Ubuntu" + }, + { + "name": "DISA PgSQL" + }, + { + "name": "CISA SCuBA" + } + ] + }, + { + "model": "profile", + "count": 4, + "what": "the High baseline, and one selection per guide", + "detail": "the High baseline the plan of record imports, and for each of the three guides the profile the component references, which is how the executor reaches a guide's methods without the guide entering the plan of record's own profile", + "items": [ + { + "name": "800-53 High" + }, + { + "name": "CIS Ubuntu" + }, + { + "name": "DISA PgSQL" + }, + { + "name": "CISA SCuBA" + } + ] + }, + { + "model": "mapping-collection", + "count": 0, + "what": "none, the finding targets the guide's own objective", + "detail": "where a profile adds a method to a framework control the placement is the tie; where the guide is its own catalog the note supplies no tie, and that is an open question on the questions page" + }, + { + "model": "component-definition", + "count": 0, + "what": "none, the checks are parts on the controls", + "detail": "the executor matches each method's platform prop against the plan of record's own components, so no definition carries the checks and none names the engine" + }, + { + "model": "system-security-plan", + "count": 1, + "what": "one, answering 370 controls", + "detail": "no guidance enters it; the components reference the profiles the executor reads, and the responses stay per framework control", + "items": [ + { + "name": "System SSP" + } + ] + }, + { + "model": "assessment-plan", + "count": 1, + "what": "one, reading 547 methods through the components' profiles", + "detail": "the plan imports the system security plan, and the executor resolves the profile each component references to find the methods whose platform matches it", + "items": [ + { + "name": "System AP" + } + ] + }, + { + "model": "assessment-results", + "count": 1, + "what": "one, with a finding per objective", + "detail": "every finding targets an objective on a guide catalog's control, and every observation carries the script's raw output as evidence", + "items": [ + { + "name": "System AR" + } + ] + } + ], + "plan_of_record": "The plan of record answers 370 controls, and the 547 executable methods are read by the assessment plan through the components' profiles" } }, "items_note": "One entry per file, so a reader can follow a particular document from the figure into the list beneath it. The names are shortened to fit a tile. Where a model has more than one kind of file in it, the kind is named too: a component definition holding the thing being configured is software, and one holding the checks that test it is validation, which is the distinction the whole approach rests on and is invisible from the file count alone." 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 9f4f550..b632162 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 @@ -33,6 +33,17 @@ "repo": null, "status_annotation": "placeholder and synthetic identifiers", "one_line": "The rule is an assessment plan activity or step, the check is a new assembly beneath it." + }, + { + "key": "profile-first", + "label": "Profile-first", + "option_letter": "D", + "primary_model": "profile", + "layer": "Control", + "serves_stakeholder_first": "assessor", + "repo": null, + "status_annotation": "concept note, no published content", + "one_line": "The rule is an assessment objective on the control, the check an executable assessment method beside it, in a catalog or added by a profile." } ], "empty_states": [ @@ -81,7 +92,8 @@ "available_to": { "catalog-first": true, "component-first": false, - "assessment-first": false + "assessment-first": false, + "profile-first": false }, "why": "mapping-item.type is closed by allOf to control and statement, and mapping-item carries no uuid and no href, so this binding time reaches a rule only where the rule is already modelled as a control or a control statement. The gap is in OSCAL rather than in any approach, and it is not an argument for the one approach it happens to suit: it rewards whichever view of a rule already matches the schema's assumption." } @@ -645,9 +657,169 @@ "finding", "observation" ] + }, + { + "slot": "1", + "approach": "profile-first", + "state": "filled", + "snippet_ids": [], + "note": "An assessment objective part, added to the framework control by the profile. Naming the control is the address of the part rather than a tie made later.", + "mechanisms": [ + "assembly" + ], + "model": "profile", + "assemblies": [ + "alter", + "add", + "part" + ] + }, + { + "slot": "2", + "approach": "profile-first", + "state": "filled", + "snippet_ids": [], + "note": "Containment. The parts are added to the control the alter names, so placing the check is the tie and no second document or identifier carries it.", + "mechanisms": [ + "assembly" + ], + "model": "profile", + "assemblies": [ + "alter" + ] + }, + { + "slot": "3", + "approach": "profile-first", + "state": "filled", + "snippet_ids": [], + "note": "An assessment method part with method TEST and a body in prose. Namespaced props say which engine runs the body and how its result is judged.", + "mechanisms": [ + "assembly", + "prop" + ], + "model": "profile", + "assemblies": [ + "part" + ], + "props": [ + { + "name": "language", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "ns": "https://example.org/ns/oscal-automation" + } + ] + }, + { + "slot": "4", + "approach": "profile-first", + "state": "partial", + "snippet_ids": [], + "note": "The method names its platform as a CPE and the executor matches it to an SSP component. No component field carries a CPE, so the match is a convention.", + "mechanisms": [ + "assembly", + "prop" + ], + "model": "profile", + "assemblies": [ + "part" + ], + "props": [ + { + "name": "platform", + "ns": "https://example.org/ns/oscal-automation" + } + ] + }, + { + "slot": "5", + "approach": "profile-first", + "state": "partial", + "snippet_ids": [], + "note": "Four props tell an executor how to run the body and judge what comes back. The executor is a resolver outside OSCAL, and the vocabulary has no owner yet.", + "mechanisms": [ + "assembly", + "prop" + ], + "model": "profile", + "assemblies": [ + "part" + ], + "props": [ + { + "name": "language", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "timeout", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "paths": [ + { + "key": "assessor", + "label": "Assessor's path", + "in": { + "slot": "3" + }, + "out": { + "slot": "6b" + }, + "assemblies": [ + "part", + "observation", + "finding" + ] + } + ] + }, + { + "slot": "6a", + "approach": "profile-first", + "state": "partial", + "snippet_ids": [], + "note": "The plan of record is untouched by design, so the claim is the ordinary response against the framework control. Nothing on it names the objective the check tests.", + "mechanisms": [ + "assembly" + ], + "model": "system-security-plan", + "assemblies": [ + "implemented-requirement", + "by-component" + ] + }, + { + "slot": "6b", + "approach": "profile-first", + "state": "filled", + "snippet_ids": [], + "note": "A finding targeting the objective the profile added, resting on an observation that carries the raw output as evidence and names the host as its subject.", + "mechanisms": [ + "assembly" + ], + "model": "assessment-results", + "assemblies": [ + "finding", + "observation" + ] } ], - "finding": "Questions 1 and 2 are answered by all three. Questions 6a and 6b are answered in full by none of them, and no column is complete from top to bottom.", + "finding": "Questions 1 and 2 are answered by all four. Question 6a is answered in full by none of them, and no column is complete from top to bottom.", "answer_states": [ { "key": "filled", @@ -696,7 +868,7 @@ "why_uneven": "The answer states are three words and the mechanisms carry a sentence each. That is deliberate rather than an oversight. Answered, partly answered and not answered mean what they say; Proposed does not tell a reader that no tool can read the content until the schema lands, and that is the sentence the page turns on." }, "mechanism_note": "How a capability is enabled is a different question from whether it is answered. The answer states describe the published corpus. These describe the model: what an approach would have to rely on to carry the answer at all. An approach can answer everything and still rest on properties no other tool reads, and it can answer nothing while the mechanism it would use is already released.", - "carrier_note": "Every answer names the OSCAL model it lives in and the assemblies inside it that carry the answer. The model is the first thing that differs between the three: the same requirement is a control in one, a component in another and an activity in the third, and everything downstream follows from that.", + "carrier_note": "Every answer names the OSCAL model it lives in and the assemblies inside it that carry the answer. The model is the first thing that differs between the four: the same requirement is a control in one, a component in another, an activity in a third and a part on a control in the fourth, and everything downstream follows from that.", "proposed_assemblies": [ "assessment-check-id", "associated-checks", 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 6afd6e5..fcbc36b 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 @@ -1,5 +1,5 @@ { - "note": "Seven parties touch a hardening rule between the body that writes it and the auditor who reads the outcome, and each one works in an OSCAL model. Which model is the whole of what an approach asks of a party, so this is a mapping rather than an argument. Two entries need their component type named, because the same model does two jobs for two different parties. Two sets of the seven are grouped. The bodies that author hardening guidance are one role played by two kinds of organisation. The automation is a policy engine and the two parties that run it: a provider builds the tool and runs nothing, which is why its flows name whoever executes them, and the system owner and the auditor are those parties. The mapping provider is a party of its own because a hardening guide does not always carry the tie to a framework: a STIG carries CCIs and it is DISA's separate CCI list that names the 800-53 controls, and third parties publish mappings of their own through NIST's OLIR programme. Whoever writes the guide is often not whoever ties it to the framework.", + "note": "Seven parties touch a hardening rule between the body that writes it and the auditor who reads the outcome, and each one works in an OSCAL model. Which model is the whole of what an approach asks of a party, so this is a mapping rather than an argument. Two entries need their component type named, because the same model does two jobs for two different parties. Two sets of the seven are grouped. The bodies that author hardening guidance are one role played by two kinds of organisation. The automation is a policy engine and the two parties that run it: a provider builds the tool and runs nothing, which is why its flows name whoever executes them, and the system owner and the auditor are those parties. The mapping provider is a party of its own because a hardening guide does not always carry the tie to a framework: a STIG carries CCIs and it is DISA's separate CCI list that names the 800-53 controls, and third parties publish mappings of their own through NIST's OLIR programme. Whoever writes the guide is often not whoever ties it to the framework. One approach lets parties other than the system owner write a profile, and shared_profile records which and why.", "intro": "Seven parties touch a hardening rule between a published guide and an audited system, and each works in an OSCAL model. Two sets of them are grouped: the bodies that author guidance, and the automation.", "parties": [ { @@ -291,6 +291,76 @@ ], "note": "The only run here. There is no path from a check to a claim, so what comes out is a result and never the plan of record." } + }, + "profile-first": { + "regulatory": { + "writes": [ + { + "model": "catalog" + } + ] + }, + "mapper": { + "writes": [ + { + "model": "profile" + } + ], + "note": "Edits the profile that puts the objective and the method on the framework control. Placing the part is the tie." + }, + "benchmark": { + "writes": [ + { + "model": "catalog" + } + ], + "note": "Ships the guide as a catalog carrying its own executable methods: the author of the requirement is the author of the check." + }, + "software": { + "writes": [ + { + "model": "catalog" + } + ] + }, + "engine": { + "writes": [ + { + "model": "profile" + } + ], + "note": "Publishes a profile that imports a catalog untouched and adds executable methods for its engine." + }, + "owner": { + "writes": [ + { + "model": "profile" + }, + { + "model": "system-security-plan" + } + ], + "note": "The selection and the plan of record. A run of the checks writes findings, not responses, so an owner who runs them is assessing." + }, + "auditor": { + "flows": [ + { + "runtime": true, + "from": [ + { + "model": "profile" + } + ], + "to": [ + { + "model": "assessment-results" + } + ], + "makes": "the findings" + } + ], + "note": "The executor resolves the profiles, matches each method's platform to a component, runs the body and writes the finding." + } } }, "groups": [ @@ -305,5 +375,14 @@ "note": "The policy engine and the automation tool are the same thing. A provider builds it, and whoever runs it decides what comes out." } ], - "runtime": "A tool reads OSCAL, executes, and writes OSCAL. The party in this row builds it; the party on each flow runs it." + "runtime": "A tool reads OSCAL, executes, and writes OSCAL. The party in this row builds it; the party on each flow runs it.", + "shared_profile": { + "profile-first": { + "parties": [ + "mapper", + "engine" + ], + "why": "The profile is still the system owner's selection, and it is also the document a third party adds a check with. A tool vendor publishes a profile that imports a catalog untouched and adds executable methods; a mapping provider edits the profile that puts a check on a framework control. The site records this as the approach's own position rather than as a row drawn wrong: tools/verify.py holds every other approach to the rule that nobody but the owner writes a profile." + } + } } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/tradeoffs.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/tradeoffs.json index 4c98e83..9e8df4a 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/tradeoffs.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/tradeoffs.json @@ -1,5 +1,5 @@ { - "note": "Strengths and risks per approach. The counts are not held equal: they were, three a side on every page, so that the shape of the block could not itself be an argument, and that rule was dropped when it started deciding what could be said. An approach has the risks it has. What is still held is that no approach is argued at greater length than another, which tools/approach_pages.py enforces across the three pages. No figures: the site describes one scenario, on one page, and every count belongs there. What each entry rests on is recorded in BUILD-LOG.md and, where it is a claim about what a model can express, in the schema_evidence field here, which is checked but not rendered.", + "note": "Strengths and risks per approach. The counts are not held equal: they were, three a side on every page, so that the shape of the block could not itself be an argument, and that rule was dropped when it started deciding what could be said. An approach has the risks it has. What is still held is that no approach is argued at greater length than another, which tools/approach_pages.py enforces across the four pages. No figures: the site describes one scenario, on one page, and every count belongs there. What each entry rests on is recorded in BUILD-LOG.md and, where it is a claim about what a model can express, in the schema_evidence field here, which is checked but not rendered.", "approaches": { "catalog-first": { "intro": "Considerations when introducing technical hardening controls as a catalog have been captured", @@ -113,6 +113,45 @@ "body": "The result names a plan no file here carries and gives an observation a subject type the model does not define." } ] + }, + "profile-first": { + "intro": "Considerations when attaching executable assessment methods to controls in a catalog or a profile have been captured", + "pros": [ + { + "title": "The check travels with the requirement", + "body": "A profile can add parts, props, links and params to a control, so a third party attaches a check to a catalog it does not own." + }, + { + "title": "Parameters feed the script", + "body": "A control's params reach the body as environment variables, so one script serves many controls and every organisation its own value." + }, + { + "title": "Findings need no new field", + "body": "The method links to an assessment objective, so a finding targets an objective id that every consumer built for 800-53A already reads." + }, + { + "title": "The plan of record does not grow", + "body": "The methods sit on controls the assessment plan reads, so a guide with hundreds of checks adds no control to the system security plan." + } + ], + "cons": [ + { + "title": "The catalog becomes code", + "body": "A profile resolved from a URL and executed is a remote code path into every assessed system, with the profile author as its operator." + }, + { + "title": "The vocabulary has no owner", + "body": "Language, evaluation and pass condition are conventions in a placeholder namespace, and an executor that does not know them can run nothing." + }, + { + "title": "The subject is matched by convention", + "body": "The platform prop is a CPE and nothing on an SSP component carries one, so which host runs a check is decided outside the schema." + }, + { + "title": "The claim never meets the result", + "body": "The finding targets the objective and the response the control, so the plan of record cannot say which checks its claim rests on." + } + ] } } } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/views.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/views.json index e5a566c..bc54e9b 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/views.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/views.json @@ -1,5 +1,5 @@ { - "note": "Three views of what a hardening rule is. Each is internally coherent and each implies a different home. The site takes no position on which is correct and declares a working definition instead. Rendered in the order given, which is the order of the OSCAL layers and not a ranking. The advocate and quote fields are retained as provenance and are NOT rendered: per the Gate 7 decision, no personal name, proponent organization or quotation appears on any page. Each view also names the stakeholder it serves, joining to the glossary term of that name, because the three stakeholders and the three readings are the same three-way split seen from two sides.", + "note": "Three views of what a hardening rule is. Each is internally coherent and each implies a different home. Four approaches share the three readings: aligned_approach names the approach a reading was stated for, and also_aligned names a later approach that holds the same reading of the rule and differs in the construct that carries it. The site takes no position on which is correct and declares a working definition instead. Rendered in the order given, which is the order of the OSCAL layers and not a ranking. The advocate and quote fields are retained as provenance and are NOT rendered: per the Gate 7 decision, no personal name, proponent organization or quotation appears on any page. Each view also names the stakeholder it serves, joining to the glossary term of that name, because the three stakeholders and the three readings are the same three-way split seen from two sides.", "why_this_matters": "OSCAL has no field for normativity. The pre-read's criterion 3 records requirement level as absent from OSCAL entirely, an orthogonal gap affecting every option. Location has therefore become the only channel available for expressing which of these three views an author holds.", "views": [ { @@ -14,7 +14,11 @@ "quote": "fritz-standard-setter", "supporting_quotes": [ "fritz-catalogs-for-requirements" - ] + ], + "also_aligned": [ + "profile-first" + ], + "also_aligned_note": "Profile-first reads the rule the same way and puts it in the same layer. What differs is the construct: the rule is an assessment objective part on the control rather than a control of its own, so the check can sit beside it and a profile can add both." }, { "key": "capability", diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/profile-first/executable-assessment-methods.md b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/profile-first/executable-assessment-methods.md new file mode 100644 index 0000000..e3bb216 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/profile-first/executable-assessment-methods.md @@ -0,0 +1,95 @@ +# Executable Assessment Methods: Automation Scripts on Controls in Catalogs and Profiles + +*Concept note, September 2026.* + +SP 800-53A has always known three ways to assess a control: EXAMINE, INTERVIEW, TEST. When NIST published 800-53 in OSCAL, those methods went into the catalog as `assessment-method` parts on every control, next to the assessment objectives. The catalog states the requirement and, in the same document, how to check it. What the TEST method lacks is a body. It says "test the mechanism", and a human decides what that means for the system in front of them. + +This note proposes to give TEST a body: an executable assessment method, attached to a control as an OSCAL part, in the catalog when the author of the requirement supplies the check and in a profile when someone else supplies it for a specific platform. The mechanism is not tied to CIS, to benchmarks or to bash. It works for a Grundschutz-Baustein with a kubectl check, for 800-53 SI-2 with an apt check, for an ISO 27001 mapping with a KQL query against Sentinel, and for a CIS Benchmark rule with the SCE script CIS already ships. The script language, the execution engine and the evaluation rule are properties of the part; OSCAL provides the envelope and the identity. + +## What is wrong with the alternatives + +The recent hardening-guidance discussion weighed three homes for automated checks: the catalog or profile, the component definition, and the assessment plan. The component-definition route, which our own earlier draft took, attaches scripts to `implemented-requirement` elements. It works for a single vendor shipping a single file, and it ends there. An implemented requirement has no id a profile can alter, no objective a finding can target, no parameter a tailoring party can set. The custom `automation-script` assembly the draft introduced had to reinvent all three (`benchmark-rule-id`, `applicable-profiles`, an SSP switch), and every consumer has to learn a schema fork to read it. + +The assessment-plan route puts scripts where the assessment happens. That is correct for a one-off check an assessor writes for one system. For a check that belongs to the requirement, it means copying the script into every assessment plan for every system, with no upstream to pull updates from. + +The check belongs to the control. The control has an id, parts, params and links, and the profile and assessment layers already operate on all four. + +## The mechanism + +An executable assessment method is an `assessment-method` part with `method=TEST`, a set of namespaced props that describe how to run and evaluate it, and a body: either a fenced code block in `prose` or a link to a back-matter resource. NIST 800-53 SI-2 (Flaw Remediation), tailored for Ubuntu in a profile: + +```json +{ + "control-id": "si-2", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "si-2_obj-ubuntu-updates", + "name": "assessment-objective", + "prose": "Unattended security upgrades are enabled and no security update is pending." + }, + { + "id": "si-2_asm-ubuntu-updates", + "name": "assessment-method", + "props": [ + { "name": "method", "value": "TEST" }, + { "name": "platform", "value": "cpe:2.3:o:canonical:ubuntu_linux:22.04:*:*:*:*:*:*:*", "ns": "https://example.org/ns/oscal-automation" }, + { "name": "language", "value": "bash", "ns": "https://example.org/ns/oscal-automation" }, + { "name": "evaluation", "value": "exit-code", "ns": "https://example.org/ns/oscal-automation" }, + { "name": "pass-condition", "value": "0", "ns": "https://example.org/ns/oscal-automation" }, + { "name": "timeout", "value": "PT60S", "ns": "https://example.org/ns/oscal-automation" } + ], + "links": [ + { "rel": "assessment-objective", "href": "#si-2_obj-ubuntu-updates" } + ], + "prose": "```bash\nsystemctl is-enabled unattended-upgrades >/dev/null &&\ntest \"$(apt list --upgradable 2>/dev/null | grep -c -- '-security')\" -eq 0\n```" + } + ] + } + ] +} +``` + +The namespace is a placeholder; the vocabulary is the point. Five props carry everything an executor needs: which platform the check applies to (a CPE, matched against the component in the SSP, the same way XCCDF matches its `platform` element), which engine runs it, how the result is evaluated, what counts as pass, and how long to wait. The evaluation prop is an enumeration: `exit-code`, `stdout-regex`, `json-path`, `oval-result`, `inspec-profile`. Each value fixes the meaning of `pass-condition`. Metaschema external constraints enforce the enumeration on standard OSCAL, the way FedRAMP enforces its vocabulary without forking the model. + +Three further pieces of the standard model do work the custom assembly had to fake. + +The control's `params` feed the script. A Grundschutz requirement with a parameter for the maximum password age, a CIS rule with the kernel module name, an organizational policy with the list of approved ciphers: the profile sets the value with `set-parameter`, and the executor exports it to the script as an environment variable named after the param id. One script, many controls, many organizations. CIS ships 71 distinct SCE scripts for 129 of the 279 Ubuntu 22.04 rules; `nix_auditd_rule_chk.sh` alone serves 47 rules, each with its own exported value. That is the pattern, and OSCAL params are its native form. + +Back-matter resources hold the script bodies that are reused or too large for inline prose. An `rlink` with `media-type` and a SHA-256 hash, or `base64` for self-contained catalogs. The part links to the resource by uuid. One resource, 47 links. + +The `assessment-objective` part gives the check its identity in the results. Findings in the assessment-results model target an `objective-id`. A scripted method that links to its objective produces findings that every AR consumer built for 800-53A displays unchanged. + +## Catalog or profile + +Both, by who owns the check. + +The check goes into the catalog when the author of the requirement is also the author of the check and the requirement is already technology-specific. CIS Benchmarks are the obvious case: the recommendation and the SCE script are published by the same organization for the same platform, and separating them serves nobody. A Kubernetes-specific Baustein could ship its own checks the same way. + +The check goes into a profile when the catalog is technology-neutral or when someone other than the catalog author supplies it. 800-53 will never carry an apt command, and it should not. The organization that runs 800-53 moderate on Ubuntu writes a profile that imports the baseline and adds the checks. A tool vendor publishes "Grundschutz-Kompendium, SYS.1.6 with executable checks for Kubernetes", a profile that imports the BSI catalog untouched and adds a part to SYS.1.6.A17, the requirement that containers run without privileges, containing a kubectl query for `securityContext.privileged` across all namespaces. A second vendor ships the same for OpenShift, a third replaces bash with Ansible or OPA. The BSI catalog remains the BSI artifact. + +This division works only because the check is a part. A profile can add parts, props, links and params to a control; it cannot add an assembly the model does not know. Any design that models the check as a custom assembly is unalterable by profiles, and profiles are where most checks will be written. + +## The executor + +The tooling side is a resolver with six steps. a) Resolve the profile the SSP imports, and for each component, the profile the component references, if any. b) For each control and each component, select the `assessment-method` parts with `method=TEST` whose `platform` matches the component. c) Bind the control's params from the resolved profile to environment variables. d) Fetch the body from prose or back-matter, verify the hash, execute with the engine named in `language`, enforce the timeout. e) Apply the evaluation rule to the result. f) Write an observation with the raw output as `relevant-evidence` and a finding targeting the objective id. + +Nothing in the SSP changes. The 304-to-867 growth that discredited "benchmark as catalog" in the hardening discussion came from importing benchmark profiles into the SSP's own profile. Executable methods on controls do not touch the SSP's control set. They are read by the assessment plan, not by the system owner. + +## Security of executable catalogs + +A catalog with executable assessment methods is code. An organization that resolves a profile from a URL and runs what it finds has installed a remote code execution path into every assessed system, with the profile author as the operator. Pin the hash of every rlink, sign the catalog and the profile, and let the executor refuse anything unverified. Run checks read-only wherever the engine allows it; a remediation script is a different part with a different name (`remediation`, namespaced) and a different approval. Do not let the convenience of a self-updating check library become the reason an auditor's laptop can reconfigure production. + +## What it does not solve + +The mechanism does not standardize the scripts. Bash, PowerShell, InSpec, OPA, OVAL and KQL stay what they are; OSCAL wraps them. Two vendors can ship two incompatible checks for the same control, and the profile author picks. That is the same situation XCCDF has been in since 2005 with `check-content-ref`, and it has not stopped scanners from being built on it. + +Version coupling is real. A changed check is a new profile version, and a changed catalog check is a new catalog version. For catalogs that ship checks (benchmarks), that coupling already exists in the source material. For profiles, it is the same coupling any tailoring has. + +The `platform` prop as CPE is a convention until someone writes it down; CPE has its own maintenance problems and a plain token may serve as well. The evaluation vocabulary needs an owner. Both are conventions, not model gaps. + +## Recommendation + +Attach executable checks to controls as `assessment-method` parts with `method=TEST`, in the catalog when the requirement author owns the check and in a profile otherwise. Carry platform, engine, evaluation rule and pass condition as namespaced props, validated by external constraints. Feed scripts from control params, store shared bodies in back-matter with hashes, and link every method to an assessment objective so findings need no new field. Do not put checks into implemented requirements or assessment plans; nothing there can be tailored, mapped or targeted. The check is a property of the requirement. Model it where the requirement lives. diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/index.html b/docs/analysis/2026-08-automating-technical-hardening-guidance/index.html index a6d463e..c888ca2 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/index.html +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/index.html @@ -4,16 +4,16 @@ Automating Technical Hardening Guidance with OSCAL - + - + - + + + + + + + + +
    + +

    Profile-first

    +

    In this approach, the rule is an assessment objective part on a control and the check is an executable assessment method part beside it, carrying a script body. Both are added by the catalog when its author supplies the check, and by a profile otherwise.

    + +
    +

    1. The stakeholder mapping

    +
    +

    Three readings of what a hardening rule is are on the record, and this approach reads it as a requirement, as the catalog approach does. What differs is the construct: an assessment objective part on the control rather than a control of its own, added by the catalog or a profile. That is what decides the table below.

    +

    Seven parties touch a hardening rule between a published guide and an audited system, and each works in an OSCAL model. Two sets of them are grouped: the bodies that author guidance, and the automation.

    +
    + + + + + + + + + + + + + +
    PartyOSCAL model
    Regulatory control providersNIST with SP 800-53, and bodies like itcatalog
    Mapping providersDISA's CCI list, NIST's OLIR programme, the Secure Controls Framework and bodies like them, tying a guide to a frameworkprofileEdits the profile that puts the objective and the method on the framework control. Placing the part is the tie.
    Hardening guidance authorsOne role, two kinds of organisation, the same model. Nothing downstream can tell which of them wrote a rule.
    Technical hardening guidance providersCIS, DISA and other benchmark publisherscatalogShips the guide as a catalog carrying its own executable methods: the author of the requirement is the author of the check.
    Software providersVendors publishing secure configuration guidance for their own product, alone or with a body such as CIScatalog
    Automation tools and who runs themThe policy engine and the automation tool are the same thing. A provider builds it, and whoever runs it decides what comes out.
    Policy engine providersOPA, Kyverno, ScubaGear, OpenSCAP and the like, assessing, auditing and checkingprofilePublishes a profile that imports a catalog untouched and adds executable methods for its engine.
    System ownersImplementing these concepts on a real systemprofilesystem-security-planThe selection and the plan of record. A run of the checks writes findings, not responses, so an owner who runs them is assessing.
    Independent auditorsRunning the same checks independently of the system owner, and reading the outcomeruns the checks, making the findingsprofileruntime is read by the policy engine, which runs and writes assessment-resultsThe executor resolves the profiles, matches each method's platform to a component, runs the body and writes the finding.
    +

    The runtime. A tool reads OSCAL, executes, and writes OSCAL. The party in this row builds it; the party on each flow runs it.

    +
    +
    +

    2. Strengths and risks with this approach

    +
    +

    Considerations when attaching executable assessment methods to controls in a catalog or a profile have been captured

    +
    +
    +
    +

    2.1 Strengths4

    +
      +
    1. + +

      The check travels with the requirement

      +

      A profile can add parts, props, links and params to a control, so a third party attaches a check to a catalog it does not own.

      +
    2. +
    3. + +

      Parameters feed the script

      +

      A control's params reach the body as environment variables, so one script serves many controls and every organisation its own value.

      +
    4. +
    5. + +

      Findings need no new field

      +

      The method links to an assessment objective, so a finding targets an objective id that every consumer built for 800-53A already reads.

      +
    6. +
    7. + +

      The plan of record does not grow

      +

      The methods sit on controls the assessment plan reads, so a guide with hundreds of checks adds no control to the system security plan.

      +
    8. +
    +
    +
    +

    2.2 Risks4

    +
      +
    1. + +

      The catalog becomes code

      +

      A profile resolved from a URL and executed is a remote code path into every assessed system, with the profile author as its operator.

      +
    2. +
    3. + +

      The vocabulary has no owner

      +

      Language, evaluation and pass condition are conventions in a placeholder namespace, and an executor that does not know them can run nothing.

      +
    4. +
    5. + +

      The subject is matched by convention

      +

      The platform prop is a CPE and nothing on an SSP component carries one, so which host runs a check is decided outside the schema.

      +
    6. +
    7. + +

      The claim never meets the result

      +

      The finding targets the objective and the response the control, so the plan of record cannot say which checks its claim rests on.

      +
    8. +
    +
    +
    +
    +
    +

    3. Tracing rules and checks from implementation to assessment

    +
    +

    The chain starts where the rule is introduced and runs to the claim and the result. What a step costs is how many relationships it is made of and how each one resolves.

    +
      +
    1. Rule, as it is introduced. The rule is an assessment objective part, added to the framework control by a profile. Every step below starts from that part id. profile, alters[].adds[].parts[].id.
    2. +
    3. Rule to Check. Both parts sit in one alter, and the method links to the objective by id, inside one document.
    4. +
    5. Rule to Control. The parts are added to the control the alter names. Placing them is the tie, and no second identifier exists.
    6. +
    7. Check to Runtime. The props name an engine by a token and say how to judge its result. The executor that honours them is outside OSCAL.
    8. +
    9. Runtime to Claim. The run writes no response. The plan of record is untouched by design, so nothing joins the check to the owner's claim.
    10. +
    11. Runtime to Result. The observation names the host and carries the raw output as evidence, so two machines behind one component can disagree.
    12. +
    13. Result to Control. The finding targets the objective the profile added, so a result reads against the framework with no plan of record.
    14. +
    +
    +
    +
    +
    The same chain with the values, which are rule 1, data at rest, exactly as the six questions page encodes it for this approach. Every step is a field a consumer has to follow, so the number of steps is the cost of the chain and the way each one resolves is how much the schema can do to help.
    +
    +
    + +
    + + +
    + +
    + + + + + + + + diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/questions.html b/docs/analysis/2026-08-automating-technical-hardening-guidance/questions.html index 7764117..6ef3f8e 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/questions.html +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/questions.html @@ -4,16 +4,16 @@ Open questions | Automating Technical Hardening Guidance with OSCAL - + - + - +