diff --git a/.github/workflows/verify-2026-08-hardening-guidance.yml b/.github/workflows/verify-2026-08-hardening-guidance.yml index 10879e9..0257306 100644 --- a/.github/workflows/verify-2026-08-hardening-guidance.yml +++ b/.github/workflows/verify-2026-08-hardening-guidance.yml @@ -113,6 +113,7 @@ jobs: # A generated file that has been hand-edited is the one failure this # repository cannot detect by reading. Regenerate and diff. python tools/source_inputs.py --check + python tools/executable_first_corpus.py python tools/extract.py python tools/pattern_examples.py python tools/copy_examples.py @@ -122,8 +123,9 @@ jobs: python tools/approach_pages.py python tools/scenario_page.py python tools/bundle.py - outputs=(data assets/diagrams assets/bundle.js - assessment-first.html catalog-first.html component-first.html scenario.html) + outputs=(data assets/diagrams assets/bundle.js examples/executable-first/oscal + assessment-first.html catalog-first.html component-first.html + executable-first.html scenario.html) # git diff alone misses newly generated, untracked files. changes=$(git status --porcelain --untracked-files=all -- "${outputs[@]}") if [[ -n "$changes" ]]; then diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/BUILD-LOG.md b/docs/analysis/2026-08-automating-technical-hardening-guidance/BUILD-LOG.md index 6d3bd91..6fbcce6 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 @@ -8374,6 +8374,467 @@ packaging selects browser inputs rather than copying all build inputs. `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. + +## Session: a corpus for the fourth approach + +**Date:** 2026-09-09 +**Scope:** an OSCAL corpus for profile-first, generated in the concept note's +shape from guidance this repository holds, and the site's checks, extracts, +inventory and prose brought onto it +**Result:** complete. 3175 of 3191 verification checks and 792 of 792 page +checks pass locally. The sixteen that fail are the sixteen that failed before +the previous session began, and every one of them needs the corpora or the +network. All seven generated files validate under compliance-trestle 5.1.0, +which carries the OSCAL 1.2.1 schemas, and under the published JSON schemas +for the catalog, profile and mapping models. + +### What was asked + +The previous session added profile-first as Option D from a concept note and +nothing else, because its proponent had published no OSCAL. The three other +approaches are described from published corpora, and the fourth was described +from a note's worked example. The user asked whether the corpus could be +created. It could, from two things the repository already held under +`sources/`: the CIS Benchmark for Ubuntu 24.04 LTS as CIS-CAT's JSON, which +carries every audit procedure, the names of the Script Check Engine scripts and +the values exported to them, the benchmark's four profiles, and SP 800-53 +references in its own identifiers; and the DISA STIG for the same system as +XCCDF, whose CCI to control mapping the assessment-first corpus had already +published. + +### Decisions + +1. **Both routes, one per source.** The note names two routes. On the catalog + route the author of the requirement is the author of the check, which is + CIS's case: every recommendation becomes a control carrying `statement`, + `rationale`, `assessment-objective`, `assessment-method` and `remediation` + parts, the method carrying the note's props. On the profile route someone + else supplies the check, which is DISA's case against NIST: the STIG becomes + a profile importing the Revision 5 catalog by its published URL and adding, + to each of the 79 controls a rule's CCIs map to, an objective and a method + per rule. A rule serving more than one control puts its parts on the first + and links the others to the objective, so a finding has one target. +2. **Nothing is invented.** Every control, part, identifier, value and script + body is taken from the source file. Where the source does not say something + the corpus does not say it: the STIG carries no engine and no evaluation rule + because DISA publishes its checks as text, and the SCE scripts are resources + with a name and no hash because their bodies ship with CIS-CAT and are not + held. The README beside the corpus lists what is real, what is derived and + what is missing, and the missing hash is the gap the note's security + section says an executor must refuse. +3. **The one structural liberty is named.** One benchmark section holds + recommendations and a sub-section together, and an OSCAL group holds groups + or controls, never both. Its own recommendations sit in a sub-group whose + id ends in `_recommendations`. `--corpus` asserts there is exactly one. +4. **Provenance on the mapping is CIS's, not the site's.** The mapping + collection's method is `hybrid`, its rationale `semantic` and its status + `draft`, because CIS made the references and the generator transcribed + them; nothing was reviewed. +5. **The corpus is the site's and says so everywhere it is counted.** The + status annotation reads *generated corpus, not a proponent's publication*; + the inventory page keeps its note and now lists the seven files under it; + `examples/profile-first/README.md` explains the files; and the harness key + that used to say the approach was unpublished now says its corpus is + generated, which is the fact the checks turn on. +6. **The extracts come from the corpus.** The ten profile-first cells that + declared no extracts now declare them, at pointers into the generated files, + with a `site:` prefix on the source that `extract.py` resolves against this + repository rather than the corpora. The pointers are as fixed as any other: + the STIG rule for SC-28 is alter 63, the script resource is number 52. +7. **A generated corpus gets its own phase.** Nothing outside the site will + catch an error in a corpus the site wrote, so `--corpus` recomputes every + structural claim the README makes from the committed files, and its second + half fetches the NIST catalog to confirm that every control the profile + imports and every control the mapping targets exists there. `--conformance` + now drives trestle over all seven files rather than one, since each is a + claim of the site's. + +### Counts, recomputed by the generator + +| | | +|---|---| +| CIS controls | 312 | +| of which TEST / EXAMINE | 291 / 21 | +| methods carrying a bash body or script | 219 | +| methods carrying an evaluation rule and pass condition | 62 | +| parameters, one per exported value | 82 | +| SCE script resources | 90 | +| maps to SP 800-53 | 286, from 286 recommendations | +| STIG rules, as objectives | 194 | +| controls imported and altered | 79 | + +### What changed, by file + +`tools/profile_first_corpus.py`, new, and the seven files it writes under +`examples/profile-first/oscal/` with a README beside them. `tools/extract.py` +reads a `site:` source; `tools/manifest.yaml` gains ten entries and +`data/snippets/` ten files. `tools/oscal_artifacts.py` scans a site corpus, +summarises profiles and mapping collections, and counts controls at any depth. +`tools/verify.py` gains `--corpus`, and `--conformance` holds the generated +corpus to validation. `data/six-questions.json`, `data/scenario.json` and +`data/questions.json` say the corpus exists; `data/oscal-artifacts.json` and +`data/provenance.json` carry it. `assets/site.js` renders a note and a table +together. The workflow regenerates and diffs the corpus. + +### Open items + +- The mapping collection transcribes CIS's references and has been reviewed + by nobody, which its provenance says. The STIG's CCI mapping is DISA's as + published in the assessment-first corpus. Neither publisher has seen the + transcription, and `CORRECTIONS.md` says a correction from either is + recorded in the same form as the proponents'. +- The SCE script bodies and DISA's SCAP content are not held, so no method in + the corpus can be run end to end as the note describes. The corpus shows the + shape; whether an executor built to the note can consume it is still the + question only the note's author can answer. + +## Session: the check axis + +**Date:** 2026-09-09 +**Scope:** one axis across the four approaches, what the OSCAL carries about +the check, on the start page, with the same rule from two corpora side by side +**Result:** complete. The new `--carrier` phase and the page check pass; the +phases that read the pages pass as before, and the sixteen failures that need +the corpora or the network are unchanged. + +### What was asked + +The user looked for the comparison the site was meant to draw, between an +approach that carries rules and points at checks and one that carries the +automation scripts, and could not find it. It was there only by implication: +question 3 asks what check executes the rule, and its four cells describe a +reference, a proposed reference, a description and a script without saying +that those are three kinds of thing. The user chose to have it built as an +axis across the four rather than as a fifth approach. + +### Decisions + +1. **Three kinds, not two.** The published files do not split into rules and + scripts. Two approaches carry a reference an engine resolves. One carries a + description, and for CIS the description holds the script, so the script + is present and nothing says what runs it. The fourth carries the script + with props declaring platform, language, evaluation and pass condition, and + where the publisher gives no script, as DISA does not, the same construct + carries a description. So the axis is a reference, a description, or a + declared executable, and the fourth approach's rows say which of its two + sources shows which. +2. **The fusion is a row's consequence, not a fifth column.** Rule and script + on one control is what the generated CIS catalog is: objective part, method + part with the script, remediation part, parameter. It is shown once, under + the table, with the extract that carries it. +3. **Same rule, two corpora.** The assessment-first corpus holds the CIS + Ubuntu benchmark as an assessment plan and the generated corpus holds it as + a catalog. Recommendation 1.1.1.1 is shown from both, and the audit script + is the same text in both; what differs is the carrier. The STIG rule for + SC-28 is shown the same way, and there no script exists in either. +4. **Figures recomputed, and one difference reported as observed.** The plan + has 308 audit steps and 85 carry a script; the catalog has 84 methods + carrying one; 83 recommendations carry a script in both, 42 identical and + 41 differing. In every one of the 41 the plan's copy is shorter and lacks + angle brackets the benchmark's script has. The page reports that as the + observation it is and infers no cause. The harness recomputes every figure + and refuses any number in the sentence that is not a figure the file + carries. +5. **Consequences per kind, no ranking.** What follows from each kind is + stated in three short lists, and the kind badges are outlined rather than + coloured so they read as categories and not as verdicts. +6. **On the start page, linked from the six questions page.** The six + questions page is the grid and nothing else, by an earlier decision, so the + axis is section 6 of the start page and the grid's closing paragraph points + at it. + +### What changed, by file + +`data/check-carrier.json`, new. `renderCheckCarrier` in `assets/site.js` and +a `.carrier` block in `assets/site.css`. Section 6 and its contents entry in +`index.html`; one sentence in `six-questions.html`. `check_carrier` in +`tools/verify.py`; `checkCarrier`, an arrival anchor and three marker +attributes in `tools/pagecheck.js`. The bundle regenerated. + +## Session: code in OSCAL, three decisions + +**Date:** 2026-09-09 +**Scope:** section 6 of the start page restated as the proponent's thesis and +the decisions under it; the CIS benchmark generated a second time in the Rules +shape; a `--decisions` phase +**Result:** complete. The offline phases pass with the same sixteen failures +that need the corpora or the network, and the page check passes. + +### What was asked + +The user set the fourth approach's thesis above its placement: the check's +code belongs in the OSCAL document, and where it sits is secondary. Two more +things followed. The proponent had put code into OSCAL twice, in April on a +validation component in a typed `automation-scripts` assembly and in September +on a control in the released assessment-method part, and the user asked for +the choice between those two constructs, Rules against assessment-method, to +be a decision the site states. The two typed-assembly proposals, the published +rules and checks and the April automation-scripts, were to be one row labelled +Rules. + +### Decisions + +1. **Three decisions, stated in order.** What the document carries about the + check is decision 1 and keeps the previous session's axis. Which construct + carries it is decision 2. Where it sits is decision 3, and the construct + partly decides it, since a part sits only on a control in 1.2.1. +2. **Rules is one row with two proposals under it.** The published rules and + checks carry a reference; the April assembly carries the script; they are + two schemas sharing the idea of a typed object with identity. The row says + so, names both, and marks both proposed. +3. **The benchmark is generated in both constructs.** The generator now also + writes a validation component in the April shape, keyed to CIS Controls v8 + through the benchmark's own identifiers, with recommendations that name + none under a second control implementation sourced from the catalog beside + it. The file fails validation on the proposed field, the generator expects + it to, and the conformance check asserts that the assessment-method files + use no undefined assembly while this one uses the proposed one and nothing + else. Its audit scripts are the catalog's inline scripts as a set. +4. **A grid, construct by placement.** Six cells: released, proposed, empty, + or needs a schema change. Every document a cell names is referenced by + inventory key, so the link is the inventory's and the harness checks that + the file exists and that its validation status is what the cell says. +5. **The April document itself is not held yet.** It is named in the Rules + row and the grid as not held, and the cell will link it once it arrives. +6. **Nothing renamed yet.** The fourth option is still Profile-first on every + page, pending the user's word on the name. + +### Counts, recomputed + +| | | +|---|---| +| Implemented requirements in the Rules-shape file | 49 | +| Audit script objects, distinct scripts | 97, 85 | +| Remediation script objects | 67 | +| Audit objects carrying evaluation criteria | 66 | + +### What changed, by file + +`build_rules_cdef` and `EXPECT_INVALID` in `tools/profile_first_corpus.py`, +and the eighth file it writes. `data/decisions.json`, new. `renderDecisions` +in `assets/site.js`, a `.decisions` block in `assets/site.css`. Section 6 +restructured in `index.html` with three numbered subsections. `check_decisions` +and the two-construct conformance in `tools/verify.py`; the corpus phase +checks the Rules-shape file; `tools/pagecheck.js` checks the grid. Two extracts +from the Rules-shape file in `tools/manifest.yaml`; the inventory counts +automation scripts. READMEs updated. + +### Open items + +- The April component definition, to be held under `examples/` and cited. +- The name of the fourth option. +- The open questions page does not yet carry the three questions for the + Foundation that decisions 2 and 3 raise; they go in with the rename. + +## Session: the Rules shape stands on its own + +**Date:** 2026-09-09 +**Scope:** every reference to a document the site does not hold removed +**Result:** complete; the phases that read the data and the pages pass as before. + +The user chose to leave the April component definition out. The Rules-shape +file the generator writes stays, and is now described as what it is: the +site's own encoding of the Rules construct carrying code, written from the CIS +benchmark, and not a rendering of any document. The unheld placeholder in the +Rules row and in the grid cell is gone, the thesis states the idea without a +history, and the generator's remarks, the harness comments and the READMEs no +longer name a document that is not here. The name of the fourth option and +the open questions for the Foundation remain open. + +## Session: Executable-first, and the questions for the Foundation + +**Date:** 2026-09-09 +**Scope:** the fourth option renamed from Profile-first to Executable-first on +every page, data file, generator, check, diagram and path; three open +questions added +**Result:** complete. The offline phases pass with the sixteen failures that +need the corpora or the network, and the page check passes. + +### Decisions + +1. **Named by what it carries.** The other three are named by the model the + rule first appears in. The fourth says the model is secondary, so its name + says what it carries: the check's code, in the OSCAL. The start page's + section 4 states the exception; the page's lede names the three homes the + code can take, a catalog, a profile, or a typed assembly on a component. +2. **The primary model stays the profile.** The mechanism the concept note + turns on is still a profile adding parts to a control it does not own, and + the joins, the stakeholder flows and the scenario were built on that. The + rename changed the name, the key, the colour token, the marker's owner and + every path, and nothing about the modelling. +3. **Three questions, first in the section.** Whether a future version adds a + typed assembly or standardises the props on the released part; which + assemblies may carry an executable; and how an executable on a control + reaches the plan of record. Each points at the section 6 decision it comes + from, and each stays inside the length the questions page holds every + question to. + +### What changed, by file + +`executable-first.html`, `examples/executable-first/`, +`tools/executable_first_corpus.py` and the two diagrams, renamed. The key, +the label and the colour token in every data file, generator, check and +stylesheet. The uuid seed in the corpus generator, so every generated file +was rewritten and re-extracted. `data/questions.json`, three questions and a +new introduction. The workflow's regeneration list and diff paths. ## Session: the examples become curated, and validate ### Gate decision: the examples are curated, not verbatim @@ -8443,3 +8904,37 @@ report Metaschema constraint findings the JSON schema does not express: step, and prop names outside the allowed set. These are the publisher's modelling choices, they do not affect the verifier's checks, and they are left as they are. + +## Session: merging the source-lock refactor + +**Date:** 2026-09-16 +**Scope:** the fork's main, carrying the upstream refactor to locked source +inputs, the progress banner, the regression tests and the clear-language +rewrite of the three approaches, merged into the branch that carries the +fourth +**Result:** complete offline. The unit tests pass, the banner check passes, +every phase that does not need the public AWS cache passes with no failures, +and the page check passes. The cache could not be fetched from this +environment, so the snippet, statistics, conformance and example phases were +not run here; CI prepares the cache and runs them. + +### What the merge changed for the fourth approach + +- Extracts held in this repository keep their `site:` prefix, resolved before + the source lock is consulted, and the inventory scans the generated corpus + by path while every locked input goes through the lock. +- The manifest is JSON only now, so the extract of the concept note's + executor section is gone; the cell it evidenced keeps the props extract. + The regression test's snippet count is 43. +- The conformance phase validates every generated file with the published + schemas, like the other corpora, and expects the one Rules-shape file to + fail on its proposed assembly. +- The corpus phase reads the NIST Revision 5 catalog now committed under + `examples/` rather than fetching it, so it runs offline. +- The quotation register is gone, so the axis and decisions data are held to + the editorial-reference rule instead of to a name list. +- The three approaches' prose was rewritten shorter upstream, so the fourth + page's lede, reading sentence, tradeoff points and notes were trimmed to + stay inside the equal budget; nothing was dropped. +- Every page and the shell carry the progress banner and the new footer, with + the count corrected to four. 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 2b6b359..df5b28a 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 | executable-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,21 @@ field names. your own work is information. ``` +## The fourth approach + +Executable-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 corpus its extracts come from is the site's own, +written by `tools/executable_first_corpus.py` from the CIS Benchmark and the DISA +STIG for Ubuntu 24.04 in the shape the note proposes, so the three judgements +the request names apply with one difference: the extracts were chosen from +files the site wrote, and the judgement worth the most is whether the shape +those files give the note's mechanism, the parts, the props, the links and the +parameters, is the shape the note intends. Two publishers' guidance was +transcribed into that corpus, and `examples/executable-first/README.md` says what +of it is theirs and what is the generator's; a correction from either of them +about the transcription is recorded here in the same form. + ## 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 c3f6cb4..5fe563a 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/README.md +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/README.md @@ -5,9 +5,9 @@ Assessments. Three organizations have published OSCAL content addressing the question: **where does technical hardening guidance live in -OSCAL, and how does an automated check attach to it?** The analysis compares -three approaches against six questions, encodes -the same two rules in all three model structures to isolate modelling +OSCAL, and how does an automated check attach to it?** A concept note proposes +a fourth way. The analysis compares the four approaches against six questions, +encodes the same two rules in all four model structures to isolate modelling differences, and identifies the join key for each approach. **The JSON encodings on the question pages were authored for the analysis.** @@ -21,6 +21,25 @@ inventories the published content separately, one row per document, with contents counted from each file. Extracts supporting claims retain declared pointers into published files and are re-derived on every build. +**The fourth approach's corpus is the site's.** Executable-first comes from a +concept note, *Executable Assessment Methods*, held at +`examples/executable-first/executable-assessment-methods.md` and linked from the +artifacts page, and its proponent has published no OSCAL. So the site wrote a +corpus in the note's shape from two pieces of guidance it already held: the CIS +Benchmark for Ubuntu 24.04 becomes a catalog whose every recommendation carries +an objective and an executable method, with the benchmark's four profiles and +its own SP 800-53 references as a mapping collection; the DISA STIG for the same +system becomes a profile that imports the NIST catalog and adds an objective and +a method to each control a rule serves. `tools/executable_first_corpus.py` writes +the eight files under `examples/executable-first/oscal/`, seven in the +assessment-method shape and one, the same benchmark as a validation component +carrying an `automation-scripts` assembly, in the Rules shape, which is a +proposed assembly and fails validation as it must. `--corpus` recomputes what +they hold, and the status annotation on every card, the inventory page and +`examples/executable-first/README.md` say whose they are. The column on the six +questions page draws its extracts from those files, and the namespace on its +props is the note's own placeholder, carried as the note wrote it. + The analysis uses published hardening guidance from CIS, DISA, CISA, and AWS. The introduction lists one row per benchmark or guide in a collapsed disclosure, with links to source material. File icons download the 16 documents recorded @@ -51,14 +70,15 @@ implied recommendation. Costs are stated for readers to evaluate. ## Status -Active analysis with eight built pages: `index.html`, -`six-questions.html`, the three approach pages, `scenario.html`, `questions.html` +Active analysis with nine built pages: `index.html`, +`six-questions.html`, the four approach pages, `scenario.html`, `questions.html` and `oscal-artifacts.html`. Strict verification is not fully passing. Remaining review and verification items: - **Proponent review has not happened.** No correction requests have been sent - to the publishers; no corrections have been received, and no publisher has - declined review. The site states the review status. + to the publishers or to the author of the concept note; no corrections have + been received, and no publisher has declined review. The site states the + review status. - Schema, external-link and browser checks need their dependencies and network access; offline skips are not strict passes. - The examples are curated: four published assessment-plan schema defects were @@ -285,29 +305,31 @@ Every figure is recomputed from the corpora. ``` python tools/source_inputs.py --check # require prepared inputs; never fetch here +python tools/executable_first_corpus.py # write the executable-first corpus from sources/ 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/pattern_examples.py # write the two rules in all four shapes python tools/copy_examples.py # rebuild data/examples.json from verified inputs -python tools/oscal_artifacts.py # inventory what the three groups have published +python tools/oscal_artifacts.py # inventory what the four approaches have 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 --offline # verify offline; run strict separately ``` The workflow runs generators in the listed dependency order. The bundle runs -last to mirror all preceding output. Five generators accept `--check` to compare +last to mirror all preceding output. Six generators accept `--check` to compare without writing and exit non-zero for stale committed files: -`pattern_examples.py`, `copy_examples.py`, `oscal_artifacts.py`, `sources_files.py`, -and `bundle.py`. +`executable_first_corpus.py`, `pattern_examples.py`, `copy_examples.py`, +`oscal_artifacts.py`, `sources_files.py`, and `bundle.py`. `approach_pages.py` records generated-page hashes and refuses to overwrite hand-edited pages. Editing a generated page instead of source data stops the build rather than losing the edit. -`tools/manifest.yaml` declares 32 snippets, all JSON. Each entry names a published -OSCAL JSON source file, an RFC 6901 pointer, the illustrated question, and any +`tools/manifest.yaml` declares 43 snippets, all JSON. Each entry names an +OSCAL JSON source file, resolved through the source lock or, prefixed `site:`, +held in this repository, an RFC 6901 pointer, the illustrated question, and any trimming applied. Trimming is declared and marked in rendered output; there is no silent truncation. `data/provenance.json` records the SHA-256 of both the source file and the @@ -334,33 +356,45 @@ longer machine-checked by that phase. ``` data/ - snippets/ 32 JSON files, one per extract, never edited by hand + snippets/ 43 JSON 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 whose corpus the site generated examples.json committed local fingerprints and pinned public links criteria.json the 15 evaluation criteria, maintained as analysis content 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 + check-carrier.json the check axis: what each approach's OSCAL carries about + the check, the same rule from two corpora, and figures + the harness recomputes + decisions.json the construct decision, Rules against assessment-method, + the placement decision, and the grid that crosses them glossary.json the vocabulary, including the terms the group has not settled. Rendered as term cards in place; there is no glossary page questions.json editorial open questions and their reasoning, in four sections corpus-stats.json every figure cited, each with its derivation provenance.json generated +examples/ + executable-first/ the concept note, and under oscal/ the seven files + tools/executable_first_corpus.py writes in its shape tools/ source-lock.json tracked local inventories and pinned public archive metadata source_inputs.py explicit public fetch and offline input integrity checks - manifest.yaml the declarative extract manifest + manifest.yaml the declarative extract manifest; a source prefixed site: + is read from this repository rather than the source lock + executable_first_corpus.py builds examples/executable-first/oscal from sources/ extract.py builds data/snippets and data/provenance.json pattern_examples.py builds data/pattern-examples.json, the site's own encodings copy_examples.py builds data/examples.json from verified source inputs - oscal_artifacts.py builds data/oscal-artifacts.json from the three corpora + oscal_artifacts.py builds data/oscal-artifacts.json from the four 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 @@ -369,17 +403,17 @@ tools/ axe_run.mjs serves the site and runs axe-core over every page ``` -Nine tools run in the regeneration pipeline. Do not hand-edit generated files: -`data/snippets/*.json` and `data/provenance.json`, -`data/pattern-examples.json`, `data/examples.json`, `data/oscal-artifacts.json`, -`data/source-files.json`, `assets/diagrams/*.svg`, the -three approach pages, `scenario.html`, and `assets/bundle.js`. The workflow regenerates the files -and fails on differences from committed versions. +Ten tools run in the regeneration pipeline. Do not hand-edit generated files: +`examples/executable-first/oscal/*.json`, `data/snippets/*.json` and +`data/provenance.json`, `data/pattern-examples.json`, `data/examples.json`, +`data/oscal-artifacts.json`, `data/source-files.json`, `assets/diagrams/*.svg`, +the four approach pages, `scenario.html`, and `assets/bundle.js`. The workflow +regenerates the files and fails on differences from committed versions. The local files under `examples/` are authoritative inputs, not disposable generator output; their committed fingerprints must already pass source checks before regeneration. -`tools/diagrams.py` builds 19 diagrams and writes 9. The remaining 10 appeared +`tools/diagrams.py` builds 18 diagrams and writes 10. The remaining 8 appeared only in a removed component gallery, including the base layer map and three stakeholder variants. The builders remain together in the drawing code. `PUBLISHED`, at the foot of the file, lists diagrams written to @@ -401,11 +435,11 @@ seven rules. The rules also appeared on the removed methodology page. Key rules: prose per page, exempting file paths as provenance. Guidance publishers and source paths remain identified for provenance; the artifact inventory describes published content, not proponent positions. -- **Equal budget is enforced by construction.** One generator writes the three +- **Equal budget is enforced by construction.** One generator writes the four approach pages and rejects word-count differences above ten per cent. - **Non-verbal encoding counts as editorializing.** Badges, hollow cells, and hatch fills convey arguments outside word counts. Every annotation type - applies to all three approaches or none. + applies to all four approaches or 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. @@ -442,15 +476,29 @@ the manifest; run `python tools/verify.py --example` to check encodings. Submit changes to the 15 evaluation criteria or open questions for analysis review, and update their structural checks when the agreed structure changes. -## Adding a fourth approach +## Adding an approach -Adding an approach requires data changes and a page, not a site rewrite. +Adding an approach requires data changes and a page, not a site 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. **Define the source inputs.** Extend [tools/source-lock.json](tools/source-lock.json) and [tools/source_inputs.py](tools/source_inputs.py) together, with tests, to authorize the new local inventory or pinned public archive. Record fingerprints and publisher terms; never rely on a personal folder or upload a private corpus. Prepare public inputs explicitly and check them offline. + An approach with no published corpus, one that exists as a proposal, can + have one written in its shape from the guidance under `sources/`, as + executable-first has: the generator goes under `tools/`, its output under + `examples//oscal/`, the approach's key into `GENERATED` in + `tools/verify.py` and `SITE_CORPORA` in `tools/oscal_artifacts.py`, its + status annotation says the corpus is generated, and manifest sources + prefixed `site:` read from it. 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 illustrated question. Run `python tools/extract.py`. 3. **Add the approach to `data/six-questions.json`.** Add an `approaches` entry @@ -459,7 +507,7 @@ Adding an approach requires data changes and a page, not a site rewrite. `matrix` cell for each of the seven question rows, with a state, tooltip note, and supporting extracts. Classify unanswered cells using one of the three unanswered states. -4. **Encode the two rules in the approach's structure.** Add a fourth column to +4. **Encode the two rules in the approach's structure.** Add a column to `tools/pattern_examples.py`: the same two rules, in the same order, for every answered question row. Each block names the containing OSCAL construct and uses the approach's namespace on properties requiring a namespace. @@ -482,6 +530,12 @@ corpus directory and option letter. The inventory derives the remaining content from files rather than hand-authored descriptions. Keep the OSCAL corpus outside `sources/`, which lists input hardening guidance, not derived OSCAL content. +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 applies to analysis-authored text, diagrams, and encodings. See 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 ea375c1..ceae411 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": "Executable-first", "path": "executable-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 80ece04..738e19f 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 @@ -45,6 +45,7 @@
  • Catalog-first
  • Component-first
  • Assessment-first
  • +
  • Executable-first
  • Open questions
  • OSCAL artifacts
  • @@ -169,7 +170,7 @@

    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 b8390f3..e58d714 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/bundle.js +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/bundle.js @@ -10,6 +10,6 @@ * mirror is a build failure rather than a page that quietly shows old content. * * Regenerate: python tools/bundle.py - * Files: 71. Generated from data/ at 2026-09-10T14:55:11+00:00. + * Files: 86. Generated from data/ at 2026-09-16T16:07:24+00:00. */ -window.TFGBundle = {"analysis.json":{"approaches":[{"id":"a","name":"Catalog-first","path":"catalog-first.html"},{"id":"b","name":"Component-first","path":"component-first.html"},{"id":"c","name":"Assessment-first","path":"assessment-first.html"}],"concluded":null,"corpora":{"note":"Repository-defined inputs: 6 committed IBM and 18 committed Easy Dynamics JSON files, checked against data/examples.json fingerprints, plus 231 public AWS JSON files from the pinned archive and verified cache declared in the lock. Prepare explicitly with python tools/source_inputs.py --fetch; python tools/source_inputs.py --check verifies inputs offline. Missing or corrupt inputs fail rather than being skipped or counted as empty.","source_lock":"tools/source-lock.json"},"forum":"OSCAL Foundation Technical Focus Group on Automated Assessments","id":"2026-08-automating-technical-hardening-guidance","makesRecommendation":false,"makesRecommendationNote":"By design, not because the effort is unfinished. The site states three approaches in the terms their proponents use, prices what each one costs, and stops. A reader looking for a verdict should not infer that one is pending.","openItems":["Proponent review has not happened. No request for corrections has been sent to the publishers of the three bodies of content, so none has been received and nobody has declined."],"opened":"2026-08-12","question":"Where does technical hardening guidance live in OSCAL, and how does an automated check attach to it?","recommendation":null,"status":"active","summary":"Three organizations have published working OSCAL content that answers the same question three different ways. This site puts the three side by side against the same six questions, writes the same two rules out in all three shapes so that the only thing differing between the columns is the modelling, and names the join key that makes each one work.","supersededBy":null,"supersedes":null,"title":"Automating Technical Hardening Guidance with OSCAL","verification":{"command":"python tools/verify.py --all","note":"Every figure and extract on the site is recomputed from a published file. A skipped check is reported separately and never counted as a pass.","workflow":".github/workflows/verify-2026-08-hardening-guidance.yml"}},"assets/diagrams/710-scenario-assessment.svg":"\n 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, framework mappings are on activities. 0 component-definition files, none, engines are identified in each plan. 1 system-security-plan file, one, addressing 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; each result references 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 system security plan addresses 370 controls; all three guides remain in assessment plans.\n \n \n11 files, across 5 of the seven models\nEach guide becomes an assessment plan with a separate assessment results document. The framework catalog\nand baseline profile remain 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, framework mappings are\non activities\n\nIMPLEMENTATION LAYER\n\ncomponent-definition\n\n0 files\nnone, engines are identified in each plan\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, addressing 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; each result references exactly\none plan\n\nThe system security plan addresses 370 controls; all three guides remain in assessment plans\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 merged selection, named 800-53 High, CIS Ubuntu, DISA PgSQL, CISA SCuBA, Org merged. 3 mapping-collection files, one per guide, linking guidance controls to framework controls, named CIS to 800-53, STIG to 800-53, SCuBA to 800-53. 3 component-definition files, one per technology, containing check components, named Ubuntu checks (software), PgSQL checks (software), M365 checks (software). 1 system-security-plan file, one, addressing 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 system security plan addresses 917 controls: 370 from the framework and 547 from the guides.\n \n \n18 files, across all seven models\nEach guide becomes a catalog with a selection profile and a mapping collection linking guidance to the\nframework. The system security plan addresses 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 merged selection\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, linking\nguidance controls to 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, containing check\ncomponents\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, addressing 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 system security plan addresses 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, framework mappings are inside component definitions. 6 component-definition files, three products with 547 rules, three engines with checks, named Ubuntu (software), PostgreSQL (software), Microsoft 365 (software), Ubuntu checks (validation), PgSQL checks (validation), M365 checks (validation). 1 system-security-plan file, one, addressing 370 controls and containing 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 system security plan addresses 370 controls and contains 547 desired-state rules in components.\n \n \n11 files, across 6 of the seven models\nEach guide becomes rules on the component being configured. Each checking engine becomes a separate\nvalidation component. The framework catalog and baseline profile remain 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, framework mappings are\ninside component definitions\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 with 547 rules, three engines\nwith checks\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, addressing 370 controls and containing\n547 rules\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 system security plan addresses 370 controls and contains 547 desired-state rules in\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":{"generated_from":"repository-defined inputs in tools/source-lock.json","note":"Every figure the site cites, with the derivation that tools/verify.py --stats recomputes from the source corpora. A mismatch is a hard failure.","stats":[{"derivation":"len(catalog.groups) in AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","key":"aws_groups","label":"groups in the AWS Security Hub catalog","value":77},{"derivation":"sum(len(g.controls) for g in catalog.groups) in aws_security-hub.oscal.json","key":"aws_controls","label":"controls in the AWS Security Hub catalog","value":452},{"derivation":"count of AWS/oscal-content-for-aws-services-main/component-definitions/*.oscal.json","key":"aws_cdef_files","label":"AWS component definition files","value":230},{"derivation":"count of components with type == 'software' across all AWS component-definitions","key":"aws_software_components","label":"AWS Config rules modelled as software components","value":429},{"derivation":"count of software-component implemented-requirements where catalog control's assessment-method part title == component title","key":"aws_title_matches","label":"software component titles matching the catalog TechnicalControlId, out of 429","value":429},{"derivation":"452 minus the count of distinct control-ids cited by software components","key":"aws_controls_without_check","label":"catalog controls with no software check component","value":29},{"derivation":"452 minus the count of distinct control-ids cited by any component","key":"aws_controls_unreferenced","label":"catalog controls referenced by no component at all","value":14},{"derivation":"sum(len(component.rules)) across cos- and idservice-component-definition.json","key":"ibm_rules","label":"rules in the IBM component definitions","value":5},{"derivation":"sum(len(component.checks)) across ansible- and oscap-validation-component-definition.json","key":"ibm_checks","label":"checks in the IBM validation component definitions","value":5},{"derivation":"count of distinct implemented-requirements.control-id across cos and idservice","key":"ibm_control_ids","label":"distinct control-ids covered by the IBM component definitions","value":9},{"derivation":"sum(len(assessment-plan.local-definitions.activities)) across the 15 Easy Dynamics assessment plans","key":"ez_activities","label":"assessment plan activities across the Easy Dynamics corpus","value":2425},{"derivation":"sum(len(activity.steps)) across the 15 Easy Dynamics assessment plans","key":"ez_steps","label":"assessment plan steps across the Easy Dynamics corpus","value":5694},{"derivation":"count of activity props where name == 'method' and value == 'TEST' across the 9 STIG files; no other method value occurs","key":"stig_method_test","label":"STIG activities carrying method TEST, out of 2271","value":2271},{"derivation":"count of step props where name == 'assessment-status' and value == 'automated' in CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","key":"cis_ubuntu_automated","label":"CIS Ubuntu 24.04 steps marked automated","value":576},{"derivation":"same file, value == 'manual'","key":"cis_ubuntu_manual","label":"CIS Ubuntu 24.04 steps marked manual","value":40},{"derivation":"count of step props where name == 'assessment-status' and value == 'automated' in CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","key":"cis_postgres_automated","label":"CIS PostgreSQL 18 steps marked automated","value":0},{"derivation":"same file, value == 'manual'","key":"cis_postgres_manual","label":"CIS PostgreSQL 18 steps marked manual","value":144},{"derivation":"count of Easy Dynamics/STIG_XCCDF to OSCAL Assessment Plans/*.json","key":"stig_files","label":"STIG assessment plan files","value":9},{"derivation":"count of STIG files where assessment-plan.import-ssp.href == 'PLACEHOLDER'","key":"stig_placeholder","label":"STIG files whose import-ssp.href is the literal string PLACEHOLDER","value":9},{"derivation":"count of AWS/oscal-content-for-aws-services-main/catalogs/*.oscal.json","key":"aws_catalog_files","label":"AWS catalog files","value":1},{"derivation":"count of files under Easy Dynamics/** whose root element is assessment-plan. The corpus also holds one assessment-results file and two non-OSCAL benchmark files, which this does not count","key":"ez_files","label":"Easy Dynamics assessment plan files","value":15},{"derivation":"count of IBM/*component-definition.json","key":"ibm_cdef_files","label":"IBM component definition files","value":4},{"derivation":"count of IBM/assessment-plan.json","key":"ibm_ap_files","label":"IBM assessment plan files","value":1},{"derivation":"count of IBM/assessment-result.json","key":"ibm_ar_files","label":"IBM assessment result files","value":1},{"derivation":"recursive count of every props array across Easy Dynamics/**/*.json","key":"ez_props","label":"props across the Easy Dynamics assessment plans","value":55458},{"derivation":"recursive count of every props array across AWS/oscal-content-for-aws-services-main/**/*.json","key":"aws_props","label":"props across the AWS catalog and component definitions","value":6094},{"derivation":"recursive count of every props array across IBM/*component-definition.json","key":"ibm_cdef_props","label":"props across the four IBM component definitions","value":0},{"derivation":"sum(1 for g in catalog.groups if g.groups) in aws_security-hub.oscal.json","key":"aws_nested_groups","label":"AWS catalog groups that themselves contain groups","value":0},{"derivation":"sum(len(c.params) for g in catalog.groups for c in g.controls)","key":"aws_control_params","label":"params declared on AWS catalog controls","value":0},{"derivation":"count of AWS/**/*.json whose root key is profile","key":"aws_profile_files","label":"profile files in the AWS corpus","value":0},{"derivation":"count of Easy Dynamics/CISA BOD 25-01/*.json","key":"cisa_files","label":"CISA BOD 25-01 files: four assessment plans, one assessment result and the sample SSP they import","value":6},{"derivation":"count of step props named criticality with value SHALL in Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","key":"cisa_criticality_shall","label":"steps carrying criticality SHALL in ap-cisa-scuba-agnostic.json","value":73},{"derivation":"count of step props named criticality with value SHOULD in the same file","key":"cisa_criticality_should","label":"steps carrying criticality SHOULD in ap-cisa-scuba-agnostic.json","value":55},{"derivation":"count of objects carrying a string type together with include-all or include-subjects, where type is component","key":"ez_subjects_component","label":"assessment-subject blocks typed component across the Easy Dynamics corpus","value":2407},{"derivation":"same walk, where type is inventory-item","key":"ez_subjects_inventory_item","label":"assessment-subject blocks typed inventory-item across the Easy Dynamics corpus, including the one on each CISA associated activity","value":26},{"derivation":"len(assessment-results.results[0].findings) in IBM/assessment-result.json. The file also carries a findings array at the document root, outside results, where the model does not define one","key":"ibm_ar_findings","label":"findings inside the result object of the IBM assessment result","value":0},{"derivation":"len(assessment-results.results[0].observations) in IBM/assessment-result.json","key":"ibm_ar_observations","label":"observations in the IBM assessment result","value":1},{"derivation":"sum(1 for a in every assessment-plan.local-definitions.activities if a.related-controls) across Easy Dynamics/**/*.json","key":"ez_activities_with_related_controls","label":"assessment plan activities carrying related-controls, out of 2425","value":2279},{"derivation":"sum(1 for ir in every control-implementation.implemented-requirements if not ir.implementing-rules) across IBM/*component-definition.json","key":"ibm_ir_without_rules","label":"IBM implemented-requirements listing no implementing rule, out of 9","value":1},{"derivation":"count of assessment plans under Easy Dynamics/Center for Internet Security/","key":"cis_ap_files","label":"CIS assessment plan files","value":2},{"derivation":"size of the set of control-id values under reviewed-controls.control-selections[].include-controls[] in the two CIS plans","key":"cis_control_ids","label":"distinct control ids referenced across the CIS assessment plans","value":82},{"derivation":"distinct control ids under a control-selection whose props carry resolution-status = synthetic-ids","key":"cis_synthetic_ids","label":"control ids the content itself flags as synthetic","value":53},{"derivation":"count, not set size, of include-control entries under a control-selection flagged resolution-status = synthetic-ids","key":"cis_synthetic_refs","label":"references to those 53 synthetic control ids","value":84},{"derivation":"count of props name=step-type value=remediate across the 15 Easy Dynamics assessment plans","key":"ez_step_type_remediate","label":"steps carrying step-type remediate, all in the STIG plans","value":2271},{"derivation":"count of props name=step-type value=remediation across the 15 Easy Dynamics assessment plans","key":"ez_step_type_remediation","label":"steps carrying step-type remediation, all in the CIS plans","value":380},{"derivation":"count of props name=step-type value=check across the 15 Easy Dynamics assessment plans","key":"ez_step_type_check","label":"steps carrying step-type check, all in the STIG plans","value":2271},{"derivation":"count of props name=step-type value=audit across the 15 Easy Dynamics assessment plans","key":"ez_step_type_audit","label":"steps carrying step-type audit, all in the CIS plans","value":380},{"derivation":"size of the set of sorted step-type value sets, grouped by the directory each plan sits in","key":"ez_step_type_vocabularies","label":"distinct step-type vocabularies in use across the two benchmark families","value":2},{"derivation":"count of files under Easy Dynamics/** whose root element is assessment-results","key":"ez_ar_files","label":"assessment results in the corpus","value":1},{"derivation":"count of files in Easy Dynamics/** whose root element is system-security-plan","key":"ez_ssp_files","label":"system security plans in the corpus: the sample SSP the CISA plans import","value":1},{"derivation":"count of role-id keys valued 'owner' at any depth in AWS/**/component-definitions/*.oscal.json","key":"aws_owner_refs","label":"references to role-id owner across the AWS component definitions","value":429},{"derivation":"count of AWS component definition files containing at least one role-id valued 'owner'","key":"aws_files_referencing_owner","label":"component definition files referencing role-id owner","value":67},{"derivation":"count of metadata.roles entries with id 'author', by file","key":"aws_files_declaring_author","label":"component definition files declaring the role author","value":230},{"derivation":"size of the set of metadata.roles[].id across all 230 AWS component definition files","key":"aws_roles_declared","label":"distinct roles declared anywhere in the AWS component definitions","value":1},{"derivation":"count of control parts with name='guidance' in aws_security-hub.oscal.json","key":"aws_guidance_parts","label":"guidance parts across the catalog controls, one per control","value":452},{"derivation":"size of the set of prose values among control parts named 'guidance'","key":"aws_guidance_distinct","label":"distinct guidance prose strings among the guidance parts","value":1},{"derivation":"count of catalog.groups entries whose id is exactly 'TestControl'","key":"aws_test_groups","label":"catalog groups with the id TestControl","value":1},{"derivation":"sum(len(g.controls)) over catalog groups with id 'TestControl'","key":"aws_test_controls","label":"controls inside the TestControl group","value":1},{"derivation":"count of TestControl controls with a rel='remediation' link whose href does not contain the control's own service prefix","key":"aws_test_controls_mislinked","label":"TestControl controls whose remediation link names a different control","value":1},{"derivation":"count of files in AWS/** whose root element is system-security-plan","key":"aws_ssp_files","label":"system security plans in the corpus","value":0},{"derivation":"count of files in AWS/** whose root element is assessment-plan","key":"aws_ap_files","label":"assessment plans in the corpus","value":0},{"derivation":"count of files in AWS/** whose root element is assessment-results","key":"aws_ar_files","label":"assessment results in the corpus","value":0},{"derivation":"size of the set of component-definition.uuid across IBM/*component-definition.json","key":"ibm_document_uuids","label":"distinct document uuids across the 4 IBM component definition files","value":1},{"derivation":"sum(len(c.checks)) over components in IBM/oscap-validation-component-definition.json","key":"ibm_oscap_checks","label":"checks in the OSCAP validation component","value":3},{"derivation":"count of OSCAP checks whose target-component-uuid is not a component uuid declared in any of the 4 IBM component definitions","key":"ibm_oscap_checks_dangling","label":"OSCAP checks whose target-component-uuid resolves to no component","value":3},{"derivation":"sum(len(c.checks)) over components in IBM/ansible-validation-component-definition.json","key":"ibm_ansible_checks","label":"checks in the ANSIBLE validation component","value":2},{"derivation":"count of ANSIBLE checks whose target-component-uuid is not a component uuid declared in any of the 4 IBM component definitions","key":"ibm_ansible_checks_dangling","label":"ANSIBLE checks whose target-component-uuid resolves to no component","value":0},{"derivation":"1 if the IBM assessment plan carries a 'local-defintions' key and no 'local-definitions' key, else 0","key":"ibm_ap_local_definitions_misspelled","label":"assessment plans spelling local-definitions without its second i","value":1},{"derivation":"count of files in IBM/*.json whose root element is system-security-plan","key":"ibm_ssp_files","label":"system security plans in the corpus","value":0},{"derivation":"count of Easy Dynamics assessment plan files whose text contains the key \"step-type\"","key":"ez_files_with_step_type","label":"assessment plans using step-type at all","value":11}]},"data/criteria.json":{"criteria":[{"name":"Triad fidelity","number":1,"question":"Does the option keep regulator, implementer and assessor roles separable?","slots":["1","3","6a","6b"]},{"name":"Normativity","number":2,"question":"Can the artifact express must versus may? Can an auditor treat it as binding?","slots":["1"]},{"name":"Requirement level","number":3,"question":"Can shall, should and may be represented at all?","slots":["1"]},{"name":"Hierarchy support","number":4,"question":"Does the model natively carry deep benchmark hierarchies?","slots":["1"]},{"name":"Tailoring","number":5,"question":"Can an organization select, exclude and parameterize at scale?","slots":["1"]},{"name":"Authoring burden","number":6,"question":"How many OSCAL artifacts must a benchmark author produce per benchmark, multiplied across roughly 100 CIS guides?","slots":["1","2","3","4","5","6a","6b"]},{"name":"SSP impact","number":7,"question":"How many additional items enter the SSP? Does the SSP end up mixing desired and actual state?","slots":["6a"]},{"name":"Response fidelity","number":8,"question":"Can a system owner answer per host or inventory item, or only per component?","slots":["4"]},{"name":"Traceability","number":9,"question":"Can a consumer traverse control to rule to check to activity to task to observation using core schema only?","slots":["1","2","3","5","6b"]},{"name":"Schema change cost","number":10,"question":"How many models change, and what is the realistic ratification timeline?","slots":["1","2","3","4","5","6a","6b"]},{"name":"Update decoupling","number":11,"question":"When a benchmark revises independently of the regulation, what has to change downstream?","slots":["1"]},{"name":"Cross-framework use","number":12,"question":"Does this help someone operating under SOC 2, ISO and FedRAMP at the same time?","slots":["2"]},{"name":"Inspectability","number":13,"question":"Can an operator see what a check does before running it on their systems?","slots":["3"]},{"name":"Prop dependence","number":14,"question":"How much meaning lives in namespaced props rather than core schema?","slots":["1","2","3","4","5","6a","6b"]},{"name":"Existing content","number":15,"question":"Is there working end-to-end content today, including an SSP and an AR?","slots":["1","2","3","4","5","6a","6b"]}],"note":"Fifteen evaluation criteria maintained in this repository for comparing the three approaches. The questions and slot mappings define the analysis scope."},"data/examples.json":{"cis_derived":["assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json"],"files":[{"approach":"assessment-first","bytes":308830,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","sha256":"521acdef03590676c0a041bf920e36a7575c63683f04e787909d3c4dcc10ea66"},{"approach":"assessment-first","bytes":325728,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-maester.json","sha256":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653"},{"approach":"assessment-first","bytes":293862,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","sha256":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e"},{"approach":"assessment-first","bytes":298328,"path":"assessment-first/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","sha256":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d"},{"approach":"assessment-first","bytes":19829,"path":"assessment-first/CISA BOD 25-01/assessment-plan.json","sha256":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee"},{"approach":"assessment-first","bytes":39652,"path":"assessment-first/CISA BOD 25-01/sample-ssp.json","sha256":"2309e2f7ad9e8a468ac38fa7584094cab3e1bc20fc1d8ae108836f4e65ecf66d"},{"approach":"assessment-first","bytes":1032133,"path":"assessment-first/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1.0.0.json","sha256":"b72eda73c5bef60e2971c93261bc226594cfb8d8aa1be92deb6b2e121bf05379"},{"approach":"assessment-first","bytes":423087,"path":"assessment-first/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","sha256":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8"},{"approach":"assessment-first","bytes":6823924,"path":"assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","sha256":"1a90fccb4442decd119382233ff8986caaaeede83dcf3c5ab22a87c747ab0c81"},{"approach":"assessment-first","bytes":1768114,"path":"assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","sha256":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c"},{"approach":"assessment-first","bytes":821083,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","sha256":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6"},{"approach":"assessment-first","bytes":823183,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","sha256":"e1eed16a4a0f6d6b6025ce05c16832458bbcd4ba16d597340d0c764333197841"},{"approach":"assessment-first","bytes":2454926,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel8.json","sha256":"54cd0e15efb7c96347cfd16012d6fc81b93861079ce8a2ccf4e61eac57b538f7"},{"approach":"assessment-first","bytes":3051725,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel9.json","sha256":"9fbd810f7c658809a3be29bdb9bc14dfdafabbe289482454208f86b3646c7783"},{"approach":"assessment-first","bytes":1310065,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu22.json","sha256":"46738bf619cdfbef00913d761586633bec301e4aae5050a30c823f27509c7e7d"},{"approach":"assessment-first","bytes":1341083,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","sha256":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e"},{"approach":"assessment-first","bytes":1940344,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","sha256":"24dead32391e392f3d25501b0581fef5a719add51667c98920ad01f2d9273207"},{"approach":"assessment-first","bytes":1858865,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","sha256":"bfe441c22311614bc30cd080a57b5242129137912400a73a3e731a9f7a9abd7a"},{"approach":"assessment-first","bytes":1867817,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2025.json","sha256":"b8e54f5a9f6e554cd58bfe0c6b5be46085af5b760786ff6c933b1be7f8150bf8"},{"approach":"component-first","bytes":1106,"path":"component-first/ansible-validation-component-definition.json","sha256":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd"},{"approach":"component-first","bytes":5105,"path":"component-first/assessment-plan.json","sha256":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6"},{"approach":"component-first","bytes":4275,"path":"component-first/assessment-result.json","sha256":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806"},{"approach":"component-first","bytes":2525,"path":"component-first/cos-component-definition.json","sha256":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a"},{"approach":"component-first","bytes":5230,"path":"component-first/idservice-component-definition.json","sha256":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf"},{"approach":"component-first","bytes":1297,"path":"component-first/oscap-validation-component-definition.json","sha256":"9efe6492ede4a21a743db6afe6bf05efda79c206d00dc6ee40e89f16145323f3"}],"link_only":{"catalog-first":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/"},"note":"The curated OSCAL examples committed in this repository, indexed by tools/copy_examples.py with the path, byte count and SHA-256 of each. Every build re-verifies the files against this index, so an edit is only accepted through an explicit --rebaseline run recorded in BUILD-LOG.md. Catalog-first is not here: it is published in a public repository and linked at the locked revision instead.","shared":[{"bytes":10442037,"path":"NIST_SP-800-53_rev5_catalog.json","sha256":"01f37cf90ea99d92242c936cbfbdebcc338eef1f71454e2acac36cc56e9bc062"}]},"data/generated-pages.json":{"note":"The hash of each approach page as this tool last wrote it. tools/approach_pages.py compares the page on disk against this before overwriting, so a hand edit to a generated page stops the build instead of disappearing into it.","sha256":{"assessment-first":"78f38c7ef742a486d4860d618df1a78e4487fef226e77317a5621f5501bab18b","catalog-first":"3319bcf155cdc7881b1dd1bfd42bdf9e679b2ed2ec5ec3b16576b04c15ed4ee8","component-first":"e169a9ca2c71028b41e0b0641dbba2a5086f6d453df2cf2eceefaf23df1d7827"},"written_by":"tools/approach_pages.py"},"data/glossary.json":{"note":"Definitions used by this analysis, with links from first uses. Alternative meanings and unresolved distinctions are identified without selecting an approach.","terms":[{"other_usages":[{"usage":"A normative requirement, a shall, equivalent to a control","who":"Catalog-first, Option A"},{"usage":"A statement of how a component may be configured, descriptive rather than binding","who":"Component-first, Option B"},{"usage":"Colloquially, the check code itself","who":"Ambiguous usage; this analysis distinguishes rule from check"},{"usage":"An AWS Config rule: a deployable resource with parameters","who":"AWS Config, the product"}],"see_also":["check","control","desired state","requirement level"],"site_usage":"One technical requirement or recommendation, finer-grained than a control, without any claim about whether it is binding. A working definition for comparing approaches, not selecting an interpretation.","status":"contested","term":"rule"},{"other_usages":[],"see_also":["rule","validation component","assessment platform"],"site_usage":"An executable or procedural test that determines whether a rule is satisfied. One rule may have many checks, one per tool.","status":"settled","term":"check"},{"other_usages":[{"usage":"Possible state: a technology provider describes available configurations rather than required configurations","who":"Alternative interpretation of component configuration"}],"see_also":["actual state","rule","implementation claim"],"site_usage":"The configuration prescribed by a rule, distinct from the system's observed configuration, or actual state.","status":"contested","term":"desired state"},{"other_usages":[],"see_also":["desired state","assessment result"],"site_usage":"The system's observed configuration, distinct from the configuration prescribed by a rule, or desired state.","status":"settled","term":"actual state"},{"other_usages":[],"see_also":["rule","link to a control","catalog"],"site_usage":"A requirement from a regulatory framework, such as NIST SP 800-53. Coarser than a rule. One control is typically served by many rules.","status":"settled","term":"control"},{"other_usages":[],"see_also":["control","mapping collection","finding","observation"],"site_usage":"An optional relationship from a rule to regulatory controls. A rule may serve several controls, one, or none. A rule without a control link can have observations but no control-targeted finding.","status":"settled","term":"link to a control"},{"other_usages":[{"usage":"Hardening guidance, used interchangeably","who":"This analysis"}],"see_also":["rule","hardening guidance"],"site_usage":"A published set of technology-specific hardening guidance, including CIS Benchmarks, DISA STIGs, CISA SCuBA baselines and technology provider guides.","status":"settled","term":"benchmark"},{"other_usages":[],"see_also":["benchmark","rule"],"site_usage":"Technology-specific guidance for configuring hardware, software or services securely. Used as a synonym for benchmark in this analysis.","status":"settled","term":"hardening guidance"},{"other_usages":[],"see_also":["rule","normativity"],"site_usage":"Whether a statement is a shall, should or may. OSCAL has no dedicated core requirement-level field across these approaches. Properties can carry such labels, but consumers need shared conventions to interpret them; model placement alone does not establish requirement level.","status":"not-established","term":"requirement level"},{"other_usages":[],"see_also":["requirement level","rule"],"site_usage":"Whether an artifact expresses binding requirements against which an auditor can assess a system. Normativity is part of the debate over model placement.","status":"contested","term":"normativity"},{"other_usages":[],"see_also":[],"set_aside":true,"site_usage":"A Component Definition construct grouping components and control-implementations to express joint satisfaction. Whether capabilities should be added to the SSP or removed from Component Definition remains an open design question in this analysis. No position is selected.","status":"contested","term":"capability"},{"other_usages":[{"usage":"A component whose purpose is to run checks rather than to be checked. Type validation, carrying a checks array.","who":"Component-first examples using proposed assemblies"},{"usage":"A component enumerating the compliance frameworks a service has been validated against.","who":"Alternative interpretation, not demonstrated by the OSCAL examples"}],"see_also":["check","component"],"site_usage":"Two distinct meanings are used: a component running checks, or a component describing validation against frameworks. This analysis identifies the intended meaning.","status":"contested","term":"validation component"},{"not_established_note":"The open question is when a component alone identifies a runner and when an assessment platform adds necessary execution context.","other_usages":[],"see_also":["assessment asset","component","actor"],"site_usage":"An OSCAL assessment-assets element that may reference components through uses-components. The examples do not establish a consistent convention for distinguishing assessment platforms, assessment assets and components in runner descriptions.","status":"not-established","term":"assessment platform"},{"not_established_note":"A consumer still needs to associate each task or observation with the asset used.","other_usages":[],"see_also":["assessment platform","component","actor"],"site_usage":"The OSCAL assessment-assets container holds components and assessment-platforms. The examples do not establish a consistent convention for identifying runners across these structures.","status":"not-established","term":"assessment asset"},{"not_established_note":"The examples leave open whether components should represent individual rules, products or policy engines and how consumers reconcile those levels.","other_usages":[],"see_also":["assessment platform","assessment asset","validation component"],"site_usage":"A part of a system, with related meanings across Component Definition, SSP, Assessment Plan and Assessment Results models. The distinction from assessment platforms and assets remains unresolved, as does granularity: a component may represent a configuration rule or a policy engine.","status":"not-established","term":"component"},{"not_established_note":"The examples use different runner-identification conventions. No single convention is established here for associating a task or observation with its producer.","other_usages":[{"usage":"An assessment platform, optionally reaching components through uses-components","who":"OSCAL assessment-assets"},{"usage":"A component of type validation, carrying the checks it runs","who":"Component-first, Option B, proposed schema"},{"usage":"An origin actor on an assessment result","who":"OSCAL assessment-results"},{"usage":"A tool named in a prop at task level","who":"The assessment plans in two of the three corpora"}],"see_also":["assessment platform","assessment asset","component","check"],"site_usage":"The tool or person performing a check, addressed by question 5. Actor is a neutral label in this analysis because no single OSCAL construct covers all uses.","status":"not-established","term":"actor"},{"other_usages":[],"see_also":["assessment result","system security plan"],"site_usage":"The system owner's narrative assertion of control implementation and design intent per component. The SSP represents claims through implemented-requirement, statement and by-component. Addressed by question 6a.","status":"settled","term":"implementation claim"},{"other_usages":[],"see_also":["implementation claim","observation","finding"],"site_usage":"The assessor's evidence-based record of whether a control was satisfied for a subject at a point in time. The AR uses observation, finding and status for binary or graded outcomes. Addressed by question 6b.","status":"settled","term":"assessment result"},{"other_usages":[],"see_also":["finding","assessment result","link to a control"],"site_usage":"An AR element recording observed evidence. Requires uuid, description, methods and collected, with no control reference. Observations are available for rules with or without control links.","status":"settled","term":"observation"},{"other_usages":[],"see_also":["observation","link to a control","assessment result"],"site_usage":"An AR element recording whether an objective is satisfied. The required target type is restricted to statement-id or objective-id, both control-derived. A rule without a control link cannot have a finding.","status":"settled","term":"finding"},{"other_usages":[],"see_also":["link to a control","catalog"],"site_usage":"An OSCAL model, GA since 1.2, relating collections of controls. Third parties can publish mappings after the source catalogs. The mapping-item type permits control and statement targets, not component rules or activities.","status":"settled","term":"mapping collection"},{"other_usages":[],"see_also":["profile","control"],"site_usage":"OSCAL model, Control layer. A structured set of controls and control enhancements.","status":"settled","term":"catalog"},{"other_usages":[],"see_also":["catalog"],"site_usage":"OSCAL model, Control layer. A baseline or overlay that selects and customizes controls from catalogs.","status":"settled","term":"profile"},{"other_usages":[],"see_also":["system security plan","component"],"site_usage":"OSCAL model, Implementation layer. Describes how components implement controls.","status":"settled","term":"component definition"},{"other_usages":[],"see_also":["component definition","implementation claim"],"site_usage":"OSCAL model, Implementation layer. Documents how a particular system implements required controls. Abbreviated SSP.","status":"settled","term":"system security plan"},{"other_usages":[],"see_also":["assessment result","activity","step"],"site_usage":"OSCAL model, Assessment layer. Defines how controls will be assessed, through activities, steps and tasks. Abbreviated AP or SAP.","status":"settled","term":"assessment plan"},{"other_usages":[],"see_also":["step","assessment plan"],"site_usage":"An assessment plan local-definitions element containing steps. How to divide a benchmark procedure between activities and steps remains an analysis question.","status":"not-established","term":"activity"},{"other_usages":[],"see_also":["activity","assessment plan"],"site_usage":"A child of an assessment plan activity. The examples do not establish one consistent boundary between the work represented by an activity and its steps.","status":"not-established","term":"step"},{"other_usages":[],"see_also":["assessment plan","observation","finding"],"site_usage":"OSCAL model, Assessment layer. Documents the results of control assessments, as observations and findings. Abbreviated AR or SAR.","status":"settled","term":"assessment results"},{"other_usages":[],"see_also":["assessment results"],"site_usage":"OSCAL model, Assessment layer. Documents remediation plans for identified issues. Abbreviated POA&M.","status":"settled","term":"plan of action and milestones"},{"other_usages":[],"see_also":["implementer","assessor"],"site_usage":"One of three stakeholder roles. Publishes requirements or recommendations for organisations to version, tailor and cite without depending on a specific system.","status":"settled","term":"publisher"},{"other_usages":[],"see_also":["publisher","assessor","desired state"],"site_usage":"One of three stakeholder roles. Uses requirements as desired-state configuration that a configuration engine can apply.","status":"settled","term":"implementer"},{"other_usages":[],"see_also":["publisher","implementer","check"],"site_usage":"One of three stakeholder roles. Runs checks or reviews sufficient evidence to determine whether requirements are satisfied.","status":"settled","term":"assessor"}]},"data/joins.json":{"approaches":{"assessment-first":{"hops":[{"from":"rule","how":"containment","note":"The activity contains the check as the first step. A property on the step identifies an executable check resolved outside OSCAL.","pairs":[{"foreign":{"field":"no field","model":"assessment-plan","slot":"1"},"how":"containment","primary":{"field":"activities[].steps[].uuid","model":"assessment-plan","slot":"3","value":"333ddd0f-22da-4c18-8bc3-98e808746bca"}},{"foreign":{"field":"steps[].props[name=check].value","model":"assessment-plan","slot":"3","value":"SV-270747r1066730_rule"},"how":"name-match","primary":{"field":"no field","model":"nothing","slot":"5"}}],"to":"check"},{"from":"rule","how":"reference","note":"The activity references the framework control through related-controls, without a separate mapping document or an additional mapping identifier to maintain.","pairs":[{"foreign":{"field":"activities[].related-controls.control-selections[].include-controls[].control-id","model":"assessment-plan","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"reference","note":"The example plan identifies platforms for the assessment as a whole. The platform reference does not identify the engine used for each check.","pairs":[{"foreign":{"field":"assessment-platforms[].uses-components[].component-uuid","model":"assessment-plan","slot":"5","value":"56270516-2673-4d4c-8d4f-52e4107f968d"},"how":"reference","primary":{"field":"assessment-assets.components[].uuid","model":"assessment-plan","slot":"5"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The plan references one system security plan through a back-matter resource. Where no plan of record exists, the resource can describe the system in prose.","pairs":[{"foreign":{"field":"import-ssp.href","model":"assessment-plan","slot":"6a","value":"#d381c885-4851-4931-828c-29bbb24fbaa3"},"how":"reference","primary":{"field":"back-matter.resources[].uuid","model":"assessment-plan","slot":"6a","value":"d381c885-4851-4931-828c-29bbb24fbaa3"}}],"to":"claim"},{"from":"runtime","how":"reference","note":"The example observation references the planned activity as the subject. The reference identifies the activity, not an inventory item assessed by the check.","pairs":[{"foreign":{"field":"observations[].subjects[].subject-uuid","model":"assessment-results","slot":"6b","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"},"how":"reference","primary":{"field":"activities[].uuid","model":"assessment-plan","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}}],"to":"result"},{"from":"result","how":"reference","note":"The finding targets a framework control objective. The target links the result to the framework without depending on an implementation statement in a plan of record.","pairs":[{"foreign":{"field":"findings[].target.target-id","model":"assessment-results","slot":"6b","value":"sc-28_obj"},"how":"reference","primary":{"field":"controls[].parts[objective].id","model":"catalog","slot":"2"}}],"to":"control"}],"introduced":{"field":"activities[].uuid","model":"assessment-plan","note":"The assessment plan defines the rule as an activity in the assessment layer, outside the implementation claim. The chain starts from the activity uuid.","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}},"catalog-first":{"hops":[{"from":"rule","how":"name-match","note":"The control references the check by title, a match not enforced by the schema. The check references the control by a resolvable id.","pairs":[{"foreign":{"field":"parts[assessment-method].props.TechnicalControlId","model":"catalog","slot":"1","value":"SV-270747r1066730_rule"},"how":"name-match","primary":{"field":"components[].title","model":"component-definition","slot":"3","value":"SV-270747r1066730_rule"}},{"foreign":{"field":"implemented-requirements[].control-id","model":"component-definition","slot":"3","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}}],"to":"check"},{"from":"rule","how":"reference","note":"A separate mapping collection links the catalogs. A third party can publish the mapping after both catalogs are published without owning either source.","pairs":[{"foreign":{"field":"maps[].sources[].id-ref","model":"mapping-collection","slot":"2","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}},{"foreign":{"field":"maps[].targets[].id-ref","model":"mapping-collection","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"none","note":"ConfigRuleId identifies the executable rule, but the content does not identify the engine that executes the check.","pairs":[{"foreign":{"field":"components[].props.ConfigRuleId","model":"component-definition","slot":"3","value":"SV_270747R1066730_RULE"},"how":"none","primary":{"field":"no field","model":"nothing","slot":"5"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The claim references a component, not a host. The by-component assembly has no assessment subject field for an individual instance.","pairs":[{"foreign":{"field":"implemented-requirements[].control-id","model":"system-security-plan","slot":"6a","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}},{"foreign":{"field":"by-components[].component-uuid","model":"system-security-plan","slot":"6a","value":"534b356b-0de1-48d4-8536-5d41ed717456"},"how":"reference","primary":{"field":"system-implementation.components[].uuid","model":"system-security-plan","slot":"6a"}}],"to":"claim"},{"from":"claim","how":"reference","note":"The finding targets the implementation statement in the system security plan and references supporting observations, connecting the assessment outcome to the claim.","pairs":[{"foreign":{"field":"findings[].target.target-id","model":"assessment-results","slot":"6b","value":"UBTU-24-600090_smt"},"how":"reference","primary":{"field":"statements[].statement-id","model":"system-security-plan","slot":"6a","value":"UBTU-24-600090_smt"}},{"foreign":{"field":"related-observations[].observation-uuid","model":"assessment-results","slot":"6b","value":"28e28d31-4428-4ff5-8c9e-ea1198dfb552"},"how":"reference","primary":{"field":"observations[].uuid","model":"assessment-results","slot":"6b"}}],"to":"result"}],"introduced":{"field":"controls[].id","model":"catalog","note":"The product catalog defines the rule as a control, using the same OSCAL structure as a regulatory control. The chain starts from the control id.","slot":"1","value":"UBTU-24-600090"}},"component-first":{"hops":[{"from":"rule","how":"composite","note":"The check references both a rule id and a target component uuid. A rule id is unique only within the declaring component.","pairs":[{"foreign":{"field":"checks[].rule-id","model":"component-definition","slot":"3","value":"ubtu24_data_at_rest_encrypted"},"how":"composite","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"checks[].target-component-uuid","model":"component-definition","slot":"3","value":"5ca997b3-bb3e-4c7a-8969-69ed44577d47"},"how":"composite","primary":{"field":"components[].uuid","model":"component-definition","slot":"1","value":"5ca997b3-bb3e-4c7a-8969-69ed44577d47"}}],"to":"check"},{"from":"rule","how":"reference","note":"The component definition contains both references. Control implementations already link components to controls; the proposed implementing-rules assembly adds references to individual rules.","pairs":[{"foreign":{"field":"implemented-requirements[].implementing-rules[].rule-id","model":"component-definition","slot":"2","value":"ubtu24_data_at_rest_encrypted"},"how":"reference","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"implemented-requirements[].control-id","model":"component-definition","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"containment","note":"The validation component contains the checks executed by the engine. Each additional engine is represented by a separate validation component.","pairs":[{"foreign":{"field":"no field","model":"component-definition","slot":"3"},"how":"containment","primary":{"field":"components[].uuid","model":"component-definition","slot":"5","value":"b3c8813d-d479-450a-8178-fbbf846faccf","where":"the validation component"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The proposed implementing-rules assembly references the rule supporting the claim, allowing a consumer to trace the claim to the check through OSCAL references.","pairs":[{"foreign":{"field":"by-components[].implementing-rules[].rule-id","model":"system-security-plan","slot":"6a","value":"ubtu24_data_at_rest_encrypted"},"how":"reference","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"by-components[].component-uuid","model":"system-security-plan","slot":"6a","value":"534b356b-0de1-48d4-8536-5d41ed717456"},"how":"reference","primary":{"field":"system-implementation.components[].uuid","model":"system-security-plan","slot":"6a"}}],"to":"claim"},{"from":"runtime","how":"reference","note":"The observation identifies the check and host, allowing different outcomes for two machines within the same system boundary to be recorded separately.","pairs":[{"foreign":{"field":"observations[].assessment-check-id","model":"assessment-results","slot":"6b","value":"SV-270747r1066730_rule"},"how":"reference","primary":{"field":"checks[].id","model":"component-definition","slot":"3","value":"SV-270747r1066730_rule"}},{"foreign":{"field":"observations[].subjects[].subject-uuid","model":"assessment-results","slot":"6b","value":"06297a03-cae0-414b-8332-2fc882f81aa1"},"how":"reference","primary":{"field":"system-implementation.inventory-items[].uuid","model":"system-security-plan","slot":"4"}}],"to":"result"},{"from":"result","how":"none","note":"The example result contains observations but no findings. No finding target identifies the control, and no finding status records whether the objective was satisfied.","pairs":[{"foreign":{"field":"no field","model":"assessment-results","slot":"6b"},"how":"none","primary":{"field":"no field","model":"catalog","slot":"2"}}],"to":"control"}],"introduced":{"field":"components[].rules[].id","model":"component-definition","note":"The proposed rules assembly defines the rule on the product component. The chain starts from the rule id within that component definition.","slot":"1","value":"ubtu24_data_at_rest_encrypted"}}},"how":[{"key":"containment","label":"Containment","meaning":"A parent contains the child directly; no key matching or dereferencing is needed."},{"key":"reference","label":"Reference","meaning":"A schema-defined identifier reference resolves to a target identifier."},{"key":"name-match","label":"Name match","meaning":"Two strings match by convention. The schema does not enforce the relationship, so a mismatch may go undetected."},{"key":"composite","label":"Composite key","meaning":"Two fields jointly identify a target. Either field alone may identify the wrong target or no target."},{"key":"none","label":"No join","meaning":"No field directly connects the entries. A consumer must follow other relationships, or the connection is absent."}],"intro":"The chain connects a rule to checks, implementation claims and assessment results. Each step identifies the relationships a consumer must resolve and the fields used to resolve those relationships.","note":"The join chain connects rule definitions, checks, implementation claims and assessment results. Each relationship identifies a foreign key and the corresponding primary key. Values match the two example rules on the six questions page; tools/verify.py checks each value against those encodings.","stages":[{"key":"rule","label":"Rule","meaning":"where the rule is introduced","slot":"1"},{"key":"control","label":"Control","meaning":"the framework control served by the rule","slot":"2"},{"key":"check","label":"Check","meaning":"the test of the rule","slot":"3"},{"key":"runtime","label":"Runtime","meaning":"what executes the check","slot":"5"},{"key":"claim","label":"Claim","meaning":"the system owner's statement of implementation","slot":"6a"},{"key":"result","label":"Result","meaning":"what an assessment recorded","slot":"6b"}],"step_order":[["rule","check"],["rule","control"],["check","runtime"],["runtime","claim"],["runtime","result"],["claim","result"],["result","control"]],"title":"How the answers connect"},"data/model-icons.json":{"icons":{"assessment-plan":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"height":"30","rx":"3","soft":false,"stroke-width":"2.27","tag":"rect","width":"24","x":"20","y":"18"},{"d":"M26 15H38V19H26V15Z","soft":false,"stroke-linejoin":"round","stroke-width":"2.27","tag":"path"},{"d":"M26 26L38 26","soft":true,"stroke-linecap":"round","stroke-width":"2.27","tag":"path"},{"d":"M26 32L34 32","soft":true,"stroke-linecap":"round","stroke-width":"2.27","tag":"path"},{"cx":"36","cy":"38","r":"5","soft":false,"stroke-width":"2.27","tag":"circle"},{"d":"M36 36V38H38","soft":false,"stroke-linecap":"round","stroke-width":"1.70","tag":"path"}],"source":"assessment_plan_model.svg","view_box":"11.1907 10.6907 41.6186 41.6186"},"assessment-results":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"height":"32","rx":"3","soft":false,"stroke-width":"2.21","tag":"rect","width":"28","x":"18","y":"16"},{"d":"M24 24L27 27L33 21","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M24 34L27 37L33 31","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M37 24L40 24","soft":true,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M37 34L40 34","soft":true,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"}],"source":"assessment_results_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"catalog":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"d":"M18 18H30L34 22V48L27 45H18V18Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.08","tag":"path"},{"d":"M46 18H34L30 22V48L37 45H46V18Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.08","tag":"path"},{"d":"M22 26L28 26","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M22 32L28 32","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M36 26L42 26","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M36 32L42 32","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"}],"source":"catalog_model.svg","view_box":"13.0728 14.0728 37.8544 37.8544"},"component-definition":{"authored_box":"0 0 64 64","layer":"implementation","shapes":[{"d":"M32 16L46 24V40L32 48L18 40V24L32 16Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M32 16V32M32 32L46 24M32 32L18 24","soft":true,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 32L32 40L46 32","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"}],"source":"component_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"mapping-collection":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"cx":"22","cy":"22","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"cx":"42","cy":"22","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"cx":"32","cy":"42","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"d":"M26 24L38 24","soft":true,"stroke-dasharray":"2 2","stroke-width":"2.08","tag":"path"},{"d":"M25 26L29 38","soft":true,"stroke-width":"2.08","tag":"path"},{"d":"M39 26L35 38","soft":true,"stroke-width":"2.08","tag":"path"}],"source":"control_mapping_model.svg","view_box":"13.0728 13.0728 37.8544 37.8544"},"plan-of-action-and-milestones":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"cx":"32","cy":"32","r":"16","soft":false,"stroke-width":"3.25","tag":"circle"},{"cx":"32","cy":"32","r":"10","soft":true,"stroke-width":"3.25","tag":"circle"},{"cx":"32","cy":"32","fill":"ink","r":"3","soft":false,"tag":"circle"},{"d":"M32 12V8M32 56V52M12 32H8M56 32H52","soft":false,"stroke-linecap":"round","stroke-width":"3.25","tag":"path"}],"source":"plan_of_action_and_milestones_model.svg","view_box":"1.7625 1.7625 60.475 60.475"},"profile":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"d":"M18 20H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 32H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 44H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"cx":"26","cy":"20","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"},{"cx":"38","cy":"32","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"},{"cx":"30","cy":"44","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"}],"source":"profile_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"system-security-plan":{"authored_box":"0 0 64 64","layer":"implementation","shapes":[{"d":"M20 16H36L44 24V48H20V16Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M36 16V24H44","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M32 30V40M32 30L28 31L26 33L26 36L28 39L32 42L36 39L38 36L38 33L36 31L32 30Z","soft":true,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"}],"source":"system_security_plan_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"}},"layers":{"assessment":{"label":"Assessment layer","models":["assessment-plan","assessment-results","plan-of-action-and-milestones"]},"control":{"label":"Control layer","models":["catalog","profile","mapping-collection"]},"implementation":{"label":"Implementation layer","models":["component-definition","system-security-plan"]}},"note":"One icon per OSCAL model, generated by tools/model_icons.py from the authored files in assets/images. Geometry only: the colour is a layer token applied by the stylesheet, and the chip behind the glyph is a CSS box. Do not edit this file; edit the SVG and regenerate."},"data/oscal-artifacts.json":{"note":"tools/oscal_artifacts.py: author data/oscal-artifacts.json.","publishers":[{"files":[{"bytes":924964,"counts":{"controls":452,"groups":77},"file":"catalogs/aws_security-hub.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/catalogs/aws_security-hub.oscal.json","href_external":true,"model":"catalog","model_label":"Catalog","title":"AWS Security Hub Controls"},{"bytes":16118,"counts":{"components":3,"implemented requirements":4,"service":1,"software":2},"file":"component-definitions/acm.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/acm.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Certificate Manager"},{"bytes":27913,"counts":{"components":8,"implemented requirements":12,"service":2,"software":6},"file":"component-definitions/cloudtrail.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/cloudtrail.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS CloudTrail"},{"bytes":12332,"counts":{"components":1,"service":1},"file":"component-definitions/config.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/config.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Config"},{"bytes":43914,"counts":{"components":18,"implemented requirements":43,"service":1,"software":17},"file":"component-definitions/iam.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/iam.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Identity and Access Management"}],"full_name":"Option A","key":"catalog-first","name":"Catalog-first","option":"Option A","repo":"https://github.com/awslabs/oscal-content-for-aws-services","rollup":{"components":861,"count":230,"model_label":"Component definition","note":"One per service. Four are listed above as examples; the rest follow the same shape.","software":429},"root":"AWS/oscal-content-for-aws-services-main","totals":{"Catalog":1,"Component definition":230}},{"files":[{"bytes":1106,"counts":{"components":1,"validation":1},"file":"ansible-validation-component-definition.json","href":"examples/component-first/ansible-validation-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo validation component definition"},{"bytes":5105,"counts":{"activities":0,"tasks":1},"file":"assessment-plan.json","href":"examples/component-first/assessment-plan.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"Assessment Plan"},{"bytes":4275,"counts":{"findings":0,"observations":1,"results":1},"file":"assessment-result.json","href":"examples/component-first/assessment-result.json","href_external":false,"model":"assessment-results","model_label":"Assessment results","title":"Assessment Result"},{"bytes":2525,"counts":{"components":1,"implemented requirements":2,"rules":2,"service":1},"file":"cos-component-definition.json","href":"examples/component-first/cos-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":5230,"counts":{"components":1,"implemented requirements":7,"rules":3,"service":1},"file":"idservice-component-definition.json","href":"examples/component-first/idservice-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":1297,"counts":{"components":1,"validation":1},"file":"oscap-validation-component-definition.json","href":"examples/component-first/oscap-validation-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo validation component definition"}],"full_name":"Option B","key":"component-first","name":"Component-first","option":"Option B","repo":null,"rollup":null,"root":"IBM","totals":{"Assessment plan":1,"Assessment results":1,"Component definition":4}},{"files":[{"bytes":308830,"counts":{"activities":7,"steps":128,"tasks":0},"file":"CISA BOD 25-01/ap-cisa-scuba-agnostic.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-agnostic.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":325728,"counts":{"activities":7,"steps":128,"tasks":1},"file":"CISA BOD 25-01/ap-cisa-scuba-maester.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-maester.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":293862,"counts":{"activities":7,"steps":128,"tasks":1},"file":"CISA BOD 25-01/ap-cisa-scuba-scubagear.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-scubagear.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":298328,"counts":{"findings":128,"observations":128,"results":1},"file":"CISA BOD 25-01/ar-cisa-scuba-scubagear.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ar-cisa-scuba-scubagear.json","href_external":false,"model":"assessment-results","model_label":"Assessment results","title":"CISA SCuBA Assessment Results - M365 Tenant"},{"bytes":19829,"counts":{"activities":8,"steps":8,"tasks":1},"file":"CISA BOD 25-01/assessment-plan.json","href":"examples/assessment-first/CISA%20BOD%2025-01/assessment-plan.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"Entra ID cATO Assessment Plan"},{"bytes":39652,"counts":{},"file":"CISA BOD 25-01/sample-ssp.json","href":"examples/assessment-first/CISA%20BOD%2025-01/sample-ssp.json","href_external":false,"model":"system-security-plan","model_label":"System security plan","title":"Sample ScubaGear System Security Plan"},{"bytes":423087,"counts":{"activities":72,"steps":144,"tasks":8},"file":"Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","href":"examples/assessment-first/Center%20for%20Internet%20Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CIS PostgreSQL 18 Benchmark"},{"bytes":1768114,"counts":{"activities":53,"steps":616,"tasks":7},"file":"Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","href":"examples/assessment-first/Center%20for%20Internet%20Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CIS Ubuntu Linux 24.04 LTS Benchmark"},{"bytes":821083,"counts":{"activities":118,"steps":236,"tasks":2},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/epas.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Postgres Advanced Server"},{"bytes":823183,"counts":{"activities":111,"steps":222,"tasks":2},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/postgres16.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Postgres 16"},{"bytes":2454926,"counts":{"activities":366,"steps":732,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel8.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/rhel8.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Red Hat Enterprise Linux 8"},{"bytes":3051725,"counts":{"activities":446,"steps":892,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel9.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/rhel9.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Red Hat Enterprise Linux 9"},{"bytes":1310065,"counts":{"activities":188,"steps":376,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu22.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/ubuntu22.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Ubuntu 22.04 LTS"},{"bytes":1341083,"counts":{"activities":194,"steps":388,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/ubuntu24.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Ubuntu 24.04 LTS"},{"bytes":1940344,"counts":{"activities":282,"steps":564,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2019.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2019"},{"bytes":1858865,"counts":{"activities":282,"steps":564,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2022.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2022"},{"bytes":1867817,"counts":{"activities":284,"steps":568,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2025.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2025.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2025"}],"full_name":"Option C","key":"assessment-first","name":"Assessment-first","option":"Option C","repo":null,"rollup":null,"root":"Easy Dynamics","totals":{"Assessment plan":15,"Assessment results":1,"System security plan":1}}]},"data/pattern-examples.json":{"benchmark_id":"CAN_Ubuntu_24-04_STIG","examples":{"1":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"steps\": [\n {\n \"uuid\": \"333ddd0f-22da-4c18-8bc3-98e808746bca\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"props","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"An activity. The requirement is the activity title, the work is in its steps, and the identifiers stay in the publisher's own namespace."},{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"steps\": [\n {\n \"uuid\": \"fd6c19bf-7c7f-4376-8dc0-674fd0421f64\",\n \"title\": \"Check: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270732r1066685_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"props","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"An activity. The requirement is the activity title, the work is in its steps, and the identifiers stay in the publisher's own namespace."}],"catalog-first":[{"content":"{\n \"catalog\": {\n \"groups\": [\n {\n \"id\": \"ubuntu-24-04\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"controls\": [\n {\n \"id\": \"UBTU-24-600090\",\n \"title\": \"Data at rest\",\n \"parts\": [\n {\n \"name\": \"statement\",\n \"prose\": \"Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"SV-270747r1066730_rule\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV-270747r1066730_rule\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[19,26]],"focus_key":"props","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A control. The requirement is the control's statement, the check is named in an assessment-method part, and a value, where there is one, is a control parameter."},{"content":"{\n \"catalog\": {\n \"groups\": [\n {\n \"id\": \"ubuntu-24-04\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"controls\": [\n {\n \"id\": \"UBTU-24-400320\",\n \"title\": \"Minimum password length\",\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"The required length is a parameter of the control, so tailoring it is a profile edit rather than a change to the requirement.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"Ubuntu 24.04 LTS must enforce a minimum {{ insert: param, password_min_length }}-character password length.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"SV-270732r1066685_rule\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV-270732r1066685_rule\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ],\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\",\n \"values\": [\n \"15\"\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[23,30]],"focus_key":"props","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A control. The requirement is the control's statement, the check is named in an assessment-method part, and a value, where there is one, is a control parameter."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"5ca997b3-bb3e-4c7a-8969-69ed44577d47\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"description\": \"Ubuntu 24.04 LTS as a component of the system.\",\n \"rules\": [\n {\n \"id\": \"ubtu24_data_at_rest_encrypted\",\n \"description\": \"Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\"\n }\n ]\n }\n ]\n }\n}","focus":[[9,14]],"focus_key":"rules","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A rules entry on the component the rule applies to. The rule is first-class rather than a prop, and a value is a rule param set by the control implementation."},{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"da810545-1635-4323-8e22-a74ddbe2c31d\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"description\": \"Ubuntu 24.04 LTS as a component of the system.\",\n \"rules\": [\n {\n \"id\": \"ubtu24_password_min_length\",\n \"description\": \"Passwords must be at least {param: password_min_length} characters.\",\n \"params\": [\n {\n \"id\": \"password_min_length\",\n \"label\": \"Minimum password length\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[9,20]],"focus_key":"rules","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A rules entry on the component the rule applies to. The rule is first-class rather than a prop, and a value is a rule param set by the control implementation."}]},"2":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"reviewed-controls\": {\n \"control-selections\": [\n {\n \"description\": \"The controls this assessment may touch.\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n },\n {\n \"control-id\": \"ia-5.1\"\n }\n ]\n }\n ]\n },\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule, derived from its CCI references.\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n }\n ]\n }\n ]\n }\n },\n {\n \"uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule, derived from its CCI references.\",\n \"include-controls\": [\n {\n \"control-id\": \"ia-5.1\"\n }\n ]\n }\n ]\n }\n }\n ]\n }\n }\n}","focus":[[23,34],[39,50]],"focus_key":"related-controls","label":"Both rules and their control ties","rule":"both","shows":"Named on the activity itself. No second document and no second identifier, so nothing can fall out of step, and nothing else can reuse the tie."}],"catalog-first":[{"content":"{\n \"mapping-collection\": {\n \"uuid\": \"d958a01a-6d1a-46fc-8289-ab967af8b955\",\n \"metadata\": {\n \"title\": \"Ubuntu 24.04 LTS product catalog mapped to NIST SP 800-53 Revision 5\",\n \"last-modified\": \"2026-08-20T12:00:00Z\",\n \"version\": \"1.0.0\",\n \"oscal-version\": \"1.2.2\"\n },\n \"provenance\": {\n \"method\": \"human\",\n \"matching-rationale\": \"semantic\",\n \"status\": \"draft\",\n \"mapping-description\": \"Each hardening control is narrower than the framework control it supports, so every map below is a subset relationship.\"\n },\n \"mappings\": [\n {\n \"uuid\": \"f60ce697-4c9d-48e2-8136-f7d3bcb895d7\",\n \"source-resource\": {\n \"type\": \"catalog\",\n \"href\": \"#ubuntu-24-04-product-catalog\"\n },\n \"target-resource\": {\n \"type\": \"catalog\",\n \"href\": \"#nist-800-53-rev5\"\n },\n \"maps\": [\n {\n \"uuid\": \"74734a70-2c15-4634-8fe1-eb70dacc4b33\",\n \"relationship\": \"subset-of\",\n \"matching-rationale\": \"semantic\",\n \"sources\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"UBTU-24-600090\"\n }\n ],\n \"targets\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"sc-28\"\n }\n ]\n },\n {\n \"uuid\": \"da49a963-4911-47d7-837b-da3c516a4708\",\n \"relationship\": \"subset-of\",\n \"matching-rationale\": \"semantic\",\n \"sources\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"UBTU-24-400320\"\n }\n ],\n \"targets\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"ia-5.1\"\n }\n ]\n }\n ]\n }\n ],\n \"back-matter\": {\n \"resources\": [\n {\n \"uuid\": \"13c89eb4-c309-466f-8e39-83e272663a37\",\n \"title\": \"Ubuntu 24.04 LTS product catalog\",\n \"rlinks\": [\n {\n \"href\": \"./ubuntu-24-04-catalog.json\"\n }\n ]\n },\n {\n \"uuid\": \"6d874b7d-f632-43ee-8043-8f0d5bd5fbe2\",\n \"title\": \"NIST SP 800-53 Revision 5\",\n \"rlinks\": [\n {\n \"href\": \"./NIST_SP-800-53_rev5_catalog.json\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[27,62]],"focus_key":"maps","label":"Both rules and their control ties","rule":"both","shows":"A whole document of its own. Metadata and a four-field provenance block come before the first map, and both ends of a map must be a control or a statement."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"type\": \"operating-system\",\n \"title\": \"Ubuntu 24.04 LTS\",\n \"control-implementations\": [\n {\n \"uuid\": \"1cc70653-88aa-408e-80ce-fdf004c2e3e1\",\n \"source\": \"trestle://profiles/nist_800_53_rev5/profile.json\",\n \"description\": \"NIST SP 800-53 Revision 5\",\n \"set-parameters\": [\n {\n \"param-id\": \"password_min_length\",\n \"values\": [\n \"15\"\n ]\n }\n ],\n \"implemented-requirements\": [\n {\n \"uuid\": \"891fbbe5-51fa-4d63-8c75-36beb7b9c70b\",\n \"control-id\": \"sc-28\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n },\n {\n \"uuid\": \"53dc0fa3-7de4-4969-86d9-0dba5044e0b3\",\n \"control-id\": \"ia-5.1\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_password_min_length\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[21,40]],"focus_key":"implemented-requirements","label":"Both rules and their control ties","rule":"both","shows":"No second document, and two ties in one place. The implemented requirement ties the component to the control, which OSCAL already does; implementing-rules ties the rule to it, which it does not."}]},"3":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"333ddd0f-22da-4c18-8bc3-98e808746bca\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"Verify the block device carrying user data is encrypted. If it is not, this is a finding.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[14,27]],"focus_key":"steps","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"The steps are the check, and a check prop names it. Put that prop on the step and the plan can ask for one item; put it on the activity and one invocation covers every step beneath. The runner decides which."},{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"fd6c19bf-7c7f-4376-8dc0-674fd0421f64\",\n \"title\": \"Check: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\",\n \"description\": \"Verify the configured minimum password length is 15 or greater. If it is not, this is a finding.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270732r1066685_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[14,27]],"focus_key":"steps","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"The steps are the check, and a check prop names it. Put that prop on the step and the plan can ask for one item; put it on the activity and one invocation covers every step beneath. The runner decides which."},{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"201588f5-0638-4c98-89d7-e4c215e62171\",\n \"title\": \"Assess Ubuntu 24.04 LTS\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"check\",\n \"value\": \"CAN_Ubuntu_24-04_STIG\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"410c472a-0935-48ee-8543-e39e02365bfd\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\"\n },\n {\n \"uuid\": \"cbcc6a87-99c5-4002-8990-cb54ee8a7377\",\n \"title\": \"V-270732: Ubuntu 24.04 LTS must enforce a minimum 15-character password length.\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[13,17]],"focus_key":"name=check","label":"Multiple tests, with the check at the activity level","rule":"placement","shows":"The same two checks named on the activity instead, for a runner that executes in bulk. One invocation, every step beneath it."}],"catalog-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"272c65cb-9a6d-4344-8938-2e6203673884\",\n \"type\": \"software\",\n \"title\": \"SV-270747r1066730_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-600090.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270747R1066730_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"9133615a-9ffc-4656-8ca7-2b249482ee22\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"b971b7c8-6b4f-4188-8ceb-968a4aacb040\",\n \"control-id\": \"UBTU-24-600090\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[9,15]],"focus_key":"props","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"The check is a software component whose title is the identifier the control's assessment-method part named."},{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"65157847-efa3-4d97-8e62-f6148c556255\",\n \"type\": \"software\",\n \"title\": \"SV-270732r1066685_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-400320.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270732R1066685_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"2293c543-d5f7-45e3-8ef3-3917f9e5ccc1\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"3f57d132-ea15-4517-8398-778950a14382\",\n \"control-id\": \"UBTU-24-400320\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[9,15]],"focus_key":"props","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"The check is a software component whose title is the identifier the control's assessment-method part named."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted on the target host.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"5ca997b3-bb3e-4c7a-8969-69ed44577d47\"\n }\n ]\n }\n ]\n }\n}","focus":[[15,22]],"focus_key":"checks","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"Two components, not one. The rule sits on the product; the check sits on a second component of type validation, one per engine, and reaches back by rule id and the uuid of the component the rule belongs to."},{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"checks\": [\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length on the target host.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"da810545-1635-4323-8e22-a74ddbe2c31d\"\n }\n ]\n }\n ]\n }\n}","focus":[[15,22]],"focus_key":"checks","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"Two components, not one. The rule sits on the product; the check sits on a second component of type validation, one per engine, and reaches back by rule id and the uuid of the component the rule belongs to."}]},"4":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"assessment-subjects\": [\n {\n \"type\": \"inventory-item\",\n \"description\": \"The instances this assessment may touch.\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ],\n \"tasks\": [\n {\n \"uuid\": \"068cacee-b6b7-49c7-844e-e80c42f25fb7\",\n \"type\": \"action\",\n \"title\": \"Assess Ubuntu 24.04 LTS\",\n \"associated-activities\": [\n {\n \"activity-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[3,14]],"focus_key":"assessment-subjects","label":"What the checks run against","rule":"both","shows":"One host, named explicitly as an inventory item."}],"catalog-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"83fd01c4-5007-4281-84bc-2fa040f75e14\",\n \"control-id\": \"UBTU-24-600090\",\n \"by-components\": [\n {\n \"uuid\": \"013a942e-ff7e-466d-821e-c84498c1b9be\",\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"description\": \"The rule was implemented.\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[8,14]],"focus_key":"by-components","label":"What the checks run against","rule":"both","shows":"Every component the catalog applies to, taken together."}],"component-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"c1ea1b60-eab2-46d3-8134-89ac8affdc8a\",\n \"control-id\": \"UBTU-24-600090\",\n \"by-components\": [\n {\n \"uuid\": \"f473f847-a826-48e5-8d9f-53ae40333b88\",\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"description\": \"The rule was implemented.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[8,19]],"focus_key":"by-components","label":"What the checks run against","rule":"both","shows":"The components carrying the rules, named by uuid."},{"content":"{\n \"assessment-plan\": {\n \"assessment-assets\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Copied from the component definition the system owner used.\",\n \"status\": {\n \"state\": \"operational\"\n },\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n },\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[13,26]],"focus_key":"checks","label":"The same component, copied into the assessor's plan","rule":"assessor","shows":"The component definition carried into an assessment plan as an asset. The checks travel with the component that runs them, and each names the component it tests."}]},"5":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"local-definitions\": {\n \"activities\": [\n {\n \"uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"steps\": [\n {\n \"uuid\": \"333ddd0f-22da-4c18-8bc3-98e808746bca\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"props\": [\n {\n \"name\": \"check\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ]\n }\n ]\n }\n ]\n },\n \"assessment-assets\": {\n \"components\": [\n {\n \"uuid\": \"56270516-2673-4d4c-8d4f-52e4107f968d\",\n \"type\": \"validation\",\n \"title\": \"The check runner plugin\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"status\": {\n \"state\": \"operational\"\n },\n \"props\": [\n {\n \"name\": \"context\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"{\\\"plugin-path\\\": \\\"runner.plugin\\\", \\\"opa-path\\\": \\\"/usr/local/bin\\\"}\"\n }\n ]\n }\n ],\n \"assessment-platforms\": [\n {\n \"uuid\": \"97f00129-f4ab-424f-8cd0-5ad1fc54f667\",\n \"title\": \"The scanning platform\",\n \"uses-components\": [\n {\n \"component-uuid\": \"56270516-2673-4d4c-8d4f-52e4107f968d\"\n }\n ]\n }\n ]\n },\n \"tasks\": [\n {\n \"uuid\": \"fa3faf4f-3ac3-432c-8d2f-4401173822ea\",\n \"type\": \"action\",\n \"title\": \"Execute the checks\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"97f00129-f4ab-424f-8cd0-5ad1fc54f667\"\n }\n ],\n \"associated-activities\": [\n {\n \"activity-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-all\": {}\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[13,17]],"focus_key":"name=check","label":"What the run reads: the checks and the platform","rule":"assessor-in","shows":"The checks and what runs them, in one plan the assessor owns."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for UBTU-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\"\n }\n ]\n },\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for UBTU-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"title\": \"Observation: SV-270747r1066730_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n },\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"title\": \"Observation: SV-270732r1066685_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[11,11],[27,27],[52,52],[69,69]],"focus_key":"target-id, subject-uuid","label":"What the run produces: the observation","rule":"assessor-out","shows":"The observation names the activity that ran. No plan of record has to exist for it to resolve."}],"catalog-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"272c65cb-9a6d-4344-8938-2e6203673884\",\n \"type\": \"software\",\n \"title\": \"SV-270747r1066730_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-600090.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270747R1066730_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"9133615a-9ffc-4656-8ca7-2b249482ee22\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"b971b7c8-6b4f-4188-8ceb-968a4aacb040\",\n \"control-id\": \"UBTU-24-600090\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n },\n {\n \"uuid\": \"65157847-efa3-4d97-8e62-f6148c556255\",\n \"type\": \"software\",\n \"title\": \"SV-270732r1066685_rule\",\n \"description\": \"Config rule that evaluates UBTU-24-400320.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"SV_270732R1066685_RULE\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"2293c543-d5f7-45e3-8ef3-3917f9e5ccc1\",\n \"source\": \"#ubuntu-24-04-product-catalog\",\n \"description\": \"Ubuntu 24.04 LTS product catalog\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"3f57d132-ea15-4517-8398-778950a14382\",\n \"control-id\": \"UBTU-24-400320\",\n \"description\": \"This Config rule evaluates the control.\"\n }\n ]\n }\n ]\n }\n ]\n }\n}","focus":[[10,14],[37,41]],"focus_key":"name=ConfigRuleId","label":"What the run reads: the check components","rule":"implementor-in","shows":"The check components the run is handed. What runs them is never named."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"UBTU-24-600090\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-600090_smt\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\"\n }\n ]\n }\n ]\n },\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"UBTU-24-400320\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-400320_smt\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18],[29,35]],"focus_key":"by-components","label":"What the run produces: the response in the plan of record","rule":"implementor-out","shows":"A by-component saying the control is met. Nothing on it names the check that produced it."}],"component-first":[{"content":"{\n \"component-definition\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Runs the checks for the Ubuntu 24.04 LTS rules.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n }\n ],\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted on the target host.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"5ca997b3-bb3e-4c7a-8969-69ed44577d47\"\n },\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length on the target host.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"da810545-1635-4323-8e22-a74ddbe2c31d\"\n }\n ]\n }\n ]\n }\n}","focus":[[15,28]],"focus_key":"checks","label":"What the run reads: the checks it is handed","rule":"implementor-in","shows":"The checks the run is handed, each naming its rule and its subject."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"sc-28\",\n \"statements\": [\n {\n \"statement-id\": \"sc-28_smt.a\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n }\n ]\n }\n ]\n },\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"ia-5.1\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_password_min_length\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[17,21],[39,43]],"focus_key":"implementing-rules","label":"What the run produces: the assertion in the plan of record","rule":"implementor-out","shows":"The response the run writes, carrying implementing-rules so the assertion and its check travel together."},{"content":"{\n \"assessment-plan\": {\n \"assessment-assets\": {\n \"components\": [\n {\n \"uuid\": \"b3c8813d-d479-450a-8178-fbbf846faccf\",\n \"type\": \"validation\",\n \"title\": \"Ansible check runner\",\n \"description\": \"Copied from the component definition the system owner used.\",\n \"status\": {\n \"state\": \"operational\"\n },\n \"checks\": [\n {\n \"id\": \"SV-270747r1066730_rule\",\n \"description\": \"Evaluates ubtu24_data_at_rest_encrypted.\",\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n },\n {\n \"id\": \"SV-270732r1066685_rule\",\n \"description\": \"Evaluates ubtu24_password_min_length.\",\n \"rule-id\": \"ubtu24_password_min_length\",\n \"target-component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\"\n }\n ]\n }\n ]\n }\n }\n}","focus":[[13,26]],"focus_key":"checks","label":"What the run reads: the same checks, in the assessor's plan","rule":"assessor-in","shows":"The same definition, taken into a plan the assessor owns. The checks travel with it."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"description\": \"SV-270747r1066730_rule\",\n \"assessment-check-id\": \"SV-270747r1066730_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n },\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"description\": \"SV-270732r1066685_rule\",\n \"assessment-check-id\": \"SV-270732r1066685_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[9,9],[10,10],[25,25],[26,26]],"focus_key":"assessment-check-id, result","label":"What the run produces: the observation","rule":"assessor-out","shows":"The check identifier joins back to what ran, and the subject is a host rather than a component."}]},"6a":{"assessment-first":[{"content":"{\n \"assessment-plan\": {\n \"import-ssp\": {\n \"href\": \"#d381c885-4851-4931-828c-29bbb24fbaa3\"\n },\n \"back-matter\": {\n \"resources\": [\n {\n \"uuid\": \"d381c885-4851-4931-828c-29bbb24fbaa3\",\n \"title\": \"Ubuntu 24.04 LTS system security plan\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"oscal-ssp\"\n }\n ],\n \"rlinks\": [\n {\n \"href\": \"system-security-plan.json\",\n \"media-type\": \"application/oscal.ssp+json\"\n }\n ],\n \"remarks\": \"Use this to point to an OSCAL-based SSP.\"\n },\n {\n \"uuid\": \"8bb824b6-255b-434c-8f68-e639deb75f89\",\n \"title\": \"System's full name\",\n \"description\": \"Use this resource when no OSCAL-based SSP exists. Briefly describe the system. This appears in the assessment result.\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"no-oscal-ssp\"\n }\n ],\n \"remarks\": \"Only include this resource if no OSCAL-based SSP is available.\"\n }\n ]\n }\n }\n}","focus":[[3,5]],"focus_key":"import-ssp","label":"One pointer, covering both rules","rule":"both","shows":"Not the claim, but where it lives. import-ssp resolves to a back-matter resource naming the system security plan, and a second resource covers the case where no OSCAL one exists."}],"catalog-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"UBTU-24-600090\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-600090_smt\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"by-components","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A by-component response in the SSP, against the product control."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"UBTU-24-400320\",\n \"statements\": [\n {\n \"statement-id\": \"UBTU-24-400320_smt\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\"\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[12,18]],"focus_key":"by-components","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A by-component response in the SSP, against the product control."}],"component-first":[{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"ce9ecf48-a1d4-4256-8f42-f4e8e8c1039b\",\n \"control-id\": \"sc-28\",\n \"statements\": [\n {\n \"statement-id\": \"sc-28_smt.a\",\n \"uuid\": \"88b72faf-1412-441f-8f07-6f310c4d9894\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"7fc3a542-51ab-4e00-849a-5a70b88da698\",\n \"description\": \"User data is held on an encrypted volume, and the key is held in the organisation's key management service.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_data_at_rest_encrypted\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[17,21]],"focus_key":"implementing-rules","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"The same shape, against the framework control, and carrying implementing-rules so the claim names the rule it rests on."},{"content":"{\n \"system-security-plan\": {\n \"control-implementation\": {\n \"implemented-requirements\": [\n {\n \"uuid\": \"b0ad1d94-4104-40b4-8fb6-b4ac25ae3002\",\n \"control-id\": \"ia-5.1\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"c6f82298-2ee6-47d6-88ca-b4806fef5898\",\n \"by-components\": [\n {\n \"component-uuid\": \"534b356b-0de1-48d4-8536-5d41ed717456\",\n \"uuid\": \"77329122-9641-434e-8640-ba2f22ac8afc\",\n \"description\": \"Password policy is enforced centrally and sets a minimum length of 15 characters.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"ubtu24_password_min_length\"\n }\n ]\n }\n ]\n }\n ]\n }\n ]\n }\n }\n}","focus":[[17,21]],"focus_key":"implementing-rules","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"The same shape, against the framework control, and carrying implementing-rules so the claim names the rule it rests on."}]},"6b":{"assessment-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for UBTU-24-600090\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"sc-28_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"title\": \"Observation: SV-270747r1066730_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"61b3ec99-dfbe-4997-8a66-6f2279edb84b\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A finding, targeting the framework control's statement."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for UBTU-24-400320\",\n \"target\": {\n \"type\": \"objective-id\",\n \"target-id\": \"ia-5.1_obj\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"title\": \"Observation: SV-270732r1066685_rule\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"0831127f-cb3c-427c-8c44-ecf893587311\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A finding, targeting the framework control's statement."}],"catalog-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"e98ff33c-cc09-4d29-847c-5ab99cd2a5d6\",\n \"title\": \"Result for UBTU-24-600090\",\n \"target\": {\n \"type\": \"statement-id\",\n \"target-id\": \"UBTU-24-600090_smt\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"title\": \"Observation for UBTU-24-600090\",\n \"description\": \"The configuration rule was evaluated on the component.\",\n \"methods\": [\n \"TEST\"\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"A finding, targeting the product control's statement."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"findings\": [\n {\n \"uuid\": \"b875b658-e6c9-4c84-8e92-08cdec285155\",\n \"title\": \"Result for UBTU-24-400320\",\n \"target\": {\n \"type\": \"statement-id\",\n \"target-id\": \"UBTU-24-400320_smt\",\n \"status\": {\n \"state\": \"satisfied\"\n }\n },\n \"related-observations\": [\n {\n \"observation-uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\"\n }\n ]\n }\n ],\n \"observations\": [\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"title\": \"Observation for UBTU-24-400320\",\n \"description\": \"The configuration rule was evaluated on the component.\",\n \"methods\": [\n \"TEST\"\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[5,22]],"focus_key":"findings","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"A finding, targeting the product control's statement."}],"component-first":[{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"observations\": [\n {\n \"uuid\": \"28e28d31-4428-4ff5-8c9e-ea1198dfb552\",\n \"description\": \"SV-270747r1066730_rule\",\n \"assessment-check-id\": \"SV-270747r1066730_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[10,10]],"focus_key":"result","label":"Rule 1, data at rest","rule":"data-at-rest","shows":"An observation carrying the check id and its result."},{"content":"{\n \"assessment-results\": {\n \"results\": [\n {\n \"observations\": [\n {\n \"uuid\": \"c89cd6c4-2897-4f8c-8c62-c019f478eb0a\",\n \"description\": \"SV-270732r1066685_rule\",\n \"assessment-check-id\": \"SV-270732r1066685_rule\",\n \"result\": \"pass\",\n \"methods\": [\n \"TEST\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"06297a03-cae0-414b-8332-2fc882f81aa1\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2026-08-20T12:00:00Z\"\n }\n ]\n }\n ]\n }\n}","focus":[[10,10]],"focus_key":"result","label":"Rule 2, minimum password length","rule":"password-min-length","shows":"An observation carrying the check id and its result."}]}},"note":"Our own encodings. Two rules, written in all three shapes, so the only thing that changes between the columns is the modelling.","rules":[{"check_id":"SV-270747r1066730_rule","control":"sc-28","key":"data-at-rest","label":"Rule 1, data at rest","statement":"Ubuntu 24.04 LTS handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.","stig":{"category":"CAT II","group":"V-270747","id":"UBTU-24-600090","rule":"SV-270747r1066730_rule","severity":"medium"},"why_chosen":"A binary condition with no value to set. It is the simple case, and it is the one all three approaches already have an analogue for."},{"check_id":"SV-270732r1066685_rule","control":"ia-5.1","key":"password-min-length","label":"Rule 2, minimum password length","statement":"Ubuntu 24.04 LTS must enforce a minimum 15-character password length.","stig":{"category":"CAT II","group":"V-270732","id":"UBTU-24-400320","rule":"SV-270732r1066685_rule","severity":"medium"},"why_chosen":"The same shape as the first rule but carrying a value, so it is the rule that shows where each approach puts a parameter. Publishers disagree on the number, which is why the number has to live somewhere addressable."}],"target":{"title":"Ubuntu 24.04 LTS","why":"One target, so the only thing that changes between the three columns is the modelling. Ubuntu because both rules are published for it, by DISA, and a reader can check them."}},"data/provenance.json":{"generated_at":"2026-09-10T14:51:40+00:00","snippet_count":32,"snippets":[{"approach":"assessment-first","bytes":4370,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-activity-v259312","language":"json","pointer":"/assessment-plan/local-definitions/activities/100","sha256_of_content":"f2968c0009fd012a241dc8e3e86173ac47bb4475624d3ccd01d77efd53964e31","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG activity V-259312"},{"approach":"assessment-first","bytes":6648,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-sc28-v270747","language":"json","pointer":"/assessment-plan/local-definitions/activities/101","sha256_of_content":"f6505f9312ba86546b17001b14b7ad797cd83fb68699749488086edb5ac0e8f2","sha256_of_source_file":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","title":"STIG activity V-270747, SC-28"},{"approach":"assessment-first","bytes":1976,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-step-props","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0","sha256_of_content":"e369bbc630cc85afc2a07e99fca48e213cabd815f4bc02ef1ec15034d2b7c33a","sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS audit step props"},{"approach":"assessment-first","bytes":999,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-remediation-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/1","sha256_of_content":"953c73006718d3632307bf47755dc4924e6164f3c03a53e96a3f3d058a4883bd","sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS remediation step"},{"approach":"assessment-first","bytes":270,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","sha256_of_content":"c3298e80edbf681c6da3e2965d161f81804db9d940539e41f77a19cf21e544e0","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA activity context prop"},{"approach":"assessment-first","bytes":928,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","sha256_of_content":"60c8183fb14d09b5f27513b84f394bf8a48670eadaf2f73fd834bc7300011240","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-assets"},{"approach":"assessment-first","bytes":1828,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","sha256_of_content":"ec5873d16ce6100d9be8cce518945b3aee95c50d2ae1ace4e298b860f8433b8f","sha256_of_source_file":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653","slot":"3","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-maester.json","title":"CISA step context prop"},{"approach":"assessment-first","bytes":243,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-related-controls","language":"json","pointer":"/assessment-plan/local-definitions/activities/100/related-controls","sha256_of_content":"2f52e4b5053678f3323139865183d634ff1206753079feff31bcaff76f53c93e","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"2","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG related-controls, the control tie"},{"approach":"assessment-first","bytes":197,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-step-reviewed","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0/reviewed-controls","sha256_of_content":"52c2919dc4f34fd2fbc5907450582b436e7e929a031c2bdb5a9c83d4ae18b30d","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"2","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA step reviewed-controls"},{"approach":"assessment-first","bytes":127,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-subjects-includeall","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"60d2f0f2a596673779c7804e0c6ea2bcc0609b41d54dc4d3c698be49bf268a82","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"4","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG assessment-subjects, include-all"},{"approach":"assessment-first","bytes":277,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"01c9afa2b4ee716f8534f4a2f12777d7202d741c06a7d5182619ca8f3afbc3fe","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"4","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-subjects, one inventory item"},{"approach":"assessment-first","bytes":2946,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"e5939a58c062351efa21b423729e40beeb72d3e13dd32757af065e4709dfbd60","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA task, with timing"},{"approach":"assessment-first","bytes":27,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","sha256_of_content":"84d4c12b8a05a19b8f99d8305498e5760d8bb8dfe987a2ecf4c38abd43d7557b","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"meta","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG import-ssp, an unresolved placeholder"},{"approach":"assessment-first","bytes":94,"extracted_at":"2026-08-22T18:44:16+00:00","id":"ez-cisa-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","sha256_of_content":"b26671d77e040a71e3470a5a13e0f043d7b130bf7b7688629f6405f136b1b7d2","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"import-ssp, resolving to a resource in the same document"},{"approach":"assessment-first","bytes":357,"extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/1","sha256_of_content":"401a0f63ea6221c571902ef0ba27bd50cce9fe2baa09b0cf520e48fa20539f1d","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The resource a resolved import-ssp lands on"},{"approach":"assessment-first","bytes":686,"extracted_at":"2026-08-22T18:46:12+00:00","id":"ez-cisa-no-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/0","sha256_of_content":"e0431570c0eb7d51ecec3ca35a340ae8c920c4c6afc08bb6a36760af82ef1e18","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The alternative resource, where no OSCAL system security plan exists"},{"approach":"assessment-first","bytes":466,"extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ar-finding","language":"json","pointer":"/assessment-results/results/0/findings/0","sha256_of_content":"4e3cfedd3c68517765d05d2cd46cdc0124a29c593c889cba16035c8ab84c1fe0","sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"A finding, targeting an objective"},{"approach":"assessment-first","bytes":762,"extracted_at":"2026-08-22T18:43:41+00:00","id":"ez-cisa-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","sha256_of_content":"631850409afd117649f1abec4da6e649bab0d2d4226d2a28f77d9918ec506b3a","sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"The observation it rests on, and what was examined"},{"approach":"assessment-first","bytes":469,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-resolution-status","language":"json","pointer":"/assessment-plan/reviewed-controls/control-selections/0","sha256_of_content":"4befe7d29d300effc4bdd88c120c2c1f1c00497fc28990444f62c198bc111d04","sha256_of_source_file":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8","slot":"meta","source":"Easy Dynamics/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","title":"CIS resolution status"},{"approach":"catalog-first","bytes":1402,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm2-control","language":"json","pointer":"/catalog/groups/0/controls/1","sha256_of_content":"a7f2e132f5d8e27309dbec9c9b114ed87105ee326046773c5cfe05f5da5b1ab4","sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"ACM.2, the control"},{"approach":"catalog-first","bytes":1177,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-rsa-check-component","language":"json","pointer":"/component-definition/components/2","sha256_of_content":"c4df1c40cb50ca7dd6e7d18862853fef78189e789623abf1c177ea49c9d0b3a1","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"3","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"acm-certificate-rsa-check, the check component"},{"approach":"catalog-first","bytes":538,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-backmatter-source","language":"json","pointer":"/component-definition/back-matter","sha256_of_content":"5e916dfa3cdf4d22fbbf601a1f6b18bc69b0a65d9367e906c26ba11901ab03cd","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"Back-matter, source to the catalog"},{"approach":"catalog-first","bytes":1444,"extracted_at":"2026-08-21T03:10:41+00:00","id":"aws-control-cloudtrail2","language":"json","pointer":"/catalog/groups/15/controls/2","sha256_of_content":"ae48dd920cb756ba4afaec14989d62d63c1954361757346114e807768609940b","sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"CloudTrail.2, the control"},{"approach":"catalog-first","bytes":1439,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-input-parameter","language":"json","pointer":"/component-definition/components/2/props","sha256_of_content":"b8d9cec13e53ca016cfe380b637fec8adfe353e9098e37d90bd28cacf98dcee1","sha256_of_source_file":"940cab9d3328d5ff55e6c69fbfae6fd4e846873d07f70ef7c096651bc8f750ab","slot":"1","source":"AWS/oscal-content-for-aws-services-main/component-definitions/iam.oscal.json","title":"InputParameter props, the parameter mechanism"},{"approach":"catalog-first","bytes":493,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-service-rollup","language":"json","pointer":"/component-definition/components/0/control-implementations/0","sha256_of_content":"dd53d5bd8e01cbaa2b198cf7504ece6374b931ec86c373ae5c9003e34d75dd44","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"AWS Certificate Manager, the service roll-up"},{"approach":"catalog-first","bytes":1367,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-config-service-bare","language":"json","pointer":"/component-definition/components/0","sha256_of_content":"3b3b0c533e8fe9ebc892b5cdf0003bb265591ae3486e5d6317aa847480d88541","sha256_of_source_file":"d5049e46d7a1251932be3e74c1f9bace606ac9b5f5542249ccb884171394a6e7","slot":"5","source":"AWS/oscal-content-for-aws-services-main/component-definitions/config.oscal.json","title":"AWS Config, the engine that runs the checks"},{"approach":"component-first","bytes":1909,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-cos-component","language":"json","pointer":"/component-definition/components/0","sha256_of_content":"63bda68a0ec328946a2ba363442053d4976a7ea78ccc27da761f4dbfc9feae4b","sha256_of_source_file":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a","slot":"1","source":"IBM/cos-component-definition.json","title":"COS component, carrying rules"},{"approach":"component-first","bytes":686,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-statement-rules","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/0","sha256_of_content":"d835c9264269a53f2fbbb988dfe83509b7610a445742300ace8703259dbb3edd","sha256_of_source_file":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf","slot":"2","source":"IBM/idservice-component-definition.json","title":"implementing-rules on ia-5.1"},{"approach":"component-first","bytes":1106,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-validation-ansible","language":"json","pointer":"$","sha256_of_content":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","sha256_of_source_file":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","slot":"3","source":"IBM/ansible-validation-component-definition.json","title":"Ansible validation component, and its checks"},{"approach":"component-first","bytes":624,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-activity","language":"json","pointer":"/assessment-plan/local-defintions","sha256_of_content":"b0157c12fb61e61809b3970895e3d1e9bba4b8c8bfe31c7f20e01ac292c1b252","sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"5","source":"IBM/assessment-plan.json","title":"AP activity, binding check-ids"},{"approach":"component-first","bytes":907,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-task-subjects","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"9852eeea94dab48f8ee5f7351c3ecc86a42be3e2dfd594626cae759ba163e9cd","sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"4","source":"IBM/assessment-plan.json","title":"AP task, subjects and platform"},{"approach":"component-first","bytes":1125,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","sha256_of_content":"eb0d665abc0dc6c1d6528291f5888816e6db04a427d7aaa6bd52bc395d1f9595","sha256_of_source_file":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806","slot":"6b","source":"IBM/assessment-result.json","title":"AR observation, carrying a result"}],"source_inputs":{"sources":[{"approach":"component-first","directory":"examples/component-first","expected_files":6,"key":"ibm","prefix":"IBM"},{"approach":"assessment-first","directory":"examples/assessment-first","expected_files":19,"key":"easy-dynamics","prefix":"Easy Dynamics"},{"approach":"catalog-first","archive_bytes":379596,"archive_sha256":"f309b59344560b88a699c5908fbc70c51c7a0e8e0339d901b1285b9c8d804a18","directory":".cache/oscal-sources/aws/4a1779ffb556c4ab8fb3dad94a19d4d198116803","file_base":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/","json_files":231,"key":"aws","prefix":"AWS/oscal-content-for-aws-services-main","repository":"awslabs/oscal-content-for-aws-services","revision":"4a1779ffb556c4ab8fb3dad94a19d4d198116803","url":"https://codeload.github.com/awslabs/oscal-content-for-aws-services/tar.gz/4a1779ffb556c4ab8fb3dad94a19d4d198116803"}],"version":1},"source_lock":"tools/source-lock.json"},"data/questions.json":{"intro":"These questions identify unresolved design choices, not recommended changes. The analysis distinguishes what the OSCAL examples demonstrate from what remains open across models and approaches.","note":"Editorial analysis questions maintained in this repository, grouped by issues shared across OSCAL and issues specific to each approach. Each question includes its reasoning; the OSCAL examples provide evidence without settling the design choices.","sections":[{"intro":"Gaps in the models themselves. None is answered by choosing an approach, and each changes what all three can express.","key":"all","label":"Across all three approaches","questions":[{"id":"xccdf","q":"Should OSCAL carry this content at all, when XCCDF already does?","why":"XCCDF already represents benchmark checklists. OSCAL could carry equivalent content or connect checklist references to implementation and assessment records. These choices produce different artifacts, translation work and maintenance obligations. The OSCAL examples do not establish which boundary best supports interoperable hardening workflows."},{"id":"rule-metadata","q":"Where does the metadata that describes a rule go?","why":"Rule metadata includes severity, weight, rationale and whether a check is automated or manual. The AWS and DISA OSCAL examples use namespaced properties for severity rather than a dedicated field. Consumers need shared conventions to interpret this content. Which metadata belongs on a rule, and whether shared namespaces or schema fields should carry it, remains open."},{"id":"remediation","q":"Where does remediation land?","why":"The AWS catalog uses remediation links, while the STIG and CIS assessment plans carry remediation steps. The component-first examples do not carry remediation. These conventions do not provide a dedicated rule-remediation field. OSCAL's plan of action and milestones addresses a particular finding, not a reusable fix for every instance of a condition. Which structure should carry reusable remediation instructions remains open."}]},{"intro":"The rule is a control in a catalog. What is unsettled is how many documents that produces and where the outcome lands.","key":"catalog-first","label":"Catalog-first","questions":[{"id":"one-ssp","q":"Do many catalogs converge into one profile and one plan of record, or does each catalog need its own?","why":"A single plan of record could answer a profile merging the catalogs that apply to a system. Separate plans could instead answer each catalog. These structures produce different file counts and response locations, and change whether benchmark outcomes sit beside regulatory outcomes. The worked scenario assumes convergence and counts 18 files; the question is whether that structure meets implementation and assessment needs."},{"id":"requirement-level","q":"If OSCAL gained a field for requirement level, how much of this disagreement would be left?","why":"OSCAL has no dedicated core field distinguishing shall, should and may. The examples can carry such labels in properties, but consumers need conventions to interpret them. Catalog-first puts benchmark and regulatory controls into the same profile. It remains unclear how much model-placement disagreement concerns binding force rather than document structure, and whether a shared requirement-level field would reduce it."},{"id":"control-type","q":"Should a control declare its type, so a regulatory control and a technical hardening control can be told apart?","why":"The catalog/profile model can combine regulatory controls with technical hardening controls, but it has no dedicated core field distinguishing those kinds. Tools would need a shared property convention or schema support to report regulatory coverage separately from hardening coverage. This question concerns the kind of requirement, distinct from whether its requirement level is shall, should or may."},{"id":"paper-cat-1","q":"How should benchmark profiles compose with regulatory profiles as the number of controls grows?","why":"Combining benchmark and regulatory controls increases the work of resolving imports, selections, exclusions and parameter values. The question is how tools should compose and maintain those profiles at scale without obscuring which source supplied a requirement or how a tailoring decision changes downstream content."},{"id":"paper-cat-2","q":"Where should benchmark outcomes be recorded, in SSP implementation claims or assessment results, and how should tools distinguish them?","why":"An SSP by-component response describes an implementation claim, while assessment results record evidence and outcomes. A benchmark workflow may need both, but they answer different questions. Tools need to distinguish intended configuration from observed satisfaction and preserve the relationship between the two records."}]},{"intro":"The rule sits on the component it configures. Open questions concern runner identification, importing component definitions and tailoring benchmark content.","key":"component-first","label":"Component-first","questions":[{"id":"which-cdef-maps","q":"Which component definition carries the tie to the framework, the one holding the rules or the one holding the checks?","why":"The control link is inline rather than held in a mapping collection. The software component definition holds rules, while the validation component definition holds checks; those artifacts may have different maintainers. A mapping provider could update either or both. The OSCAL examples do not establish which document should own that relationship or how duplicated mappings would stay consistent."},{"id":"proposal-1","q":"Should assessment platform usage be optional in an assessment plan?","why":"An assessment plan may describe a runner as a component, a platform using components, or a tool identified through properties. These alternatives leave open when an explicit assessment platform adds necessary information and when a component reference is sufficient for a consumer to execute or interpret a check."},{"id":"proposal-2","q":"When is an assessment component sufficient, and when is an assessment platform also needed?","why":"The OSCAL examples use different combinations of assessment-assets, assessment-platforms and components. They do not establish a shared rule for deciding whether a component alone identifies the runner or a platform must also describe its execution context. A consistent distinction would help consumers interpret equivalent workflows."},{"id":"proposal-3","q":"How should an assessment asset be associated with tasks or activities?","why":"A task identifies work to perform, while an assessment asset describes resources available to perform it. The component-first examples do not establish a complete, interoperable association between these structures. The question is which references should identify the runner for a particular task or activity."},{"id":"proposal-4","q":"How should an observation identify the assessment asset that produced it when several assets are declared?","why":"An assessment result may declare several assets, so naming an observation's producer requires an unambiguous relationship. The component-first result example does not establish a complete path from observation to producing asset. The open question is how consumers should recover that association without relying on tool-specific assumptions."},{"id":"paper-comp-1","q":"How should an SSP combine benchmark and vendor component definitions that describe the same system component?","why":"A system may use vendor component definitions alongside benchmark component definitions for the same software. Importing both can produce overlapping descriptions, rules and control implementations. It remains open whether an SSP should retain multiple OSCAL components, merge them, or use another convention to represent the single system component consistently."},{"id":"paper-comp-2","q":"Should desired-state values from benchmark component definitions be replaced with actual-state values in the SSP?","why":"Rules describe prescribed configuration, while an SSP records the system owner's implementation claims. Replacing prescribed values with actual values could lose the benchmark baseline; retaining only prescribed values could misrepresent implementation. The question is how to keep the two meanings distinct while preserving the relationship between benchmark requirements and the system."},{"id":"paper-comp-3","q":"Which benchmark context should enter an SSP, and how should tools filter component-definition content during import?","why":"Benchmark content can include rules, parameters, rationale and procedural detail, not all of which serves the same purpose in an SSP. Import tooling needs a policy for retaining or omitting that context. The open issue is how to reduce duplication without losing information needed to interpret an implementation claim."},{"id":"paper-comp-4","q":"How should component definitions support benchmark selection, exclusions and parameter tailoring?","why":"The component-first examples place parameters on proposed rules and set-parameters on control implementations. Those structures address parameter values but do not provide a profile's selection and exclusion workflow. How component definitions should support benchmark tailoring, including the scope and persistence of tailoring decisions, remains open."},{"id":"paper-comp-5","q":"Should assessment plans or assessment results support importing component definitions with benchmark context?","why":"The component-first examples carry check content into an assessment plan through assessment assets. That demonstrates one encoding, not a dedicated import mechanism for all benchmark context. The question is whether plans or results should support such imports directly and which rules, parameters and provenance would need to survive."}]},{"intro":"The rule is an activity in an assessment plan. The open question concerns tailoring requirements without losing their assessment context.","key":"assessment-first","label":"Assessment-first","questions":[{"id":"paper-ap-1","q":"How should assessment-plan benchmarks support tailoring available through catalogs and profiles?","why":"Activities and steps have no parameter assembly, so the assessment-first examples place required values in text. Tailoring can therefore require editing procedural content rather than selecting controls or setting parameter values through a profile. The question is how to support reusable, auditable tailoring without losing the assessment workflow."}]}]},"data/scenario-evidence/nist-high-baseline.json":{"counts":{"base":188,"controls":370,"enhancements":182,"families":18},"fetched_at":"2026-08-23","note":"The control identifiers selected by the NIST SP 800-53 Revision 5 HIGH baseline profile. Stored so the scenario's control count can be recomputed here rather than quoted from memory.","oscal_version":"1.2.2","pointer":"/profile/imports/0/include-controls/0/with-ids","profile_last_modified":"2026-05-11","profile_version":"5.2.0","source":"https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_HIGH-baseline_profile.json","title":"Electronic (OSCAL) Version of NIST Special Publication 800-53 Revision 5.1.1 HIGH IMPACT BASELINE","with_ids":["ac-1","ac-2","ac-2.1","ac-2.2","ac-2.3","ac-2.4","ac-2.5","ac-2.11","ac-2.12","ac-2.13","ac-3","ac-4","ac-4.4","ac-5","ac-6","ac-6.1","ac-6.2","ac-6.3","ac-6.5","ac-6.7","ac-6.9","ac-6.10","ac-7","ac-8","ac-10","ac-11","ac-11.1","ac-12","ac-14","ac-17","ac-17.1","ac-17.2","ac-17.3","ac-17.4","ac-18","ac-18.1","ac-18.3","ac-18.4","ac-18.5","ac-19","ac-19.5","ac-20","ac-20.1","ac-20.2","ac-21","ac-22","at-1","at-2","at-2.2","at-2.3","at-3","at-4","au-1","au-2","au-3","au-3.1","au-4","au-5","au-5.1","au-5.2","au-6","au-6.1","au-6.3","au-6.5","au-6.6","au-7","au-7.1","au-8","au-9","au-9.2","au-9.3","au-9.4","au-10","au-11","au-12","au-12.1","au-12.3","ca-1","ca-2","ca-2.1","ca-2.2","ca-3","ca-3.6","ca-5","ca-6","ca-7","ca-7.1","ca-7.4","ca-8","ca-8.1","ca-9","cm-1","cm-2","cm-2.2","cm-2.3","cm-2.7","cm-3","cm-3.1","cm-3.2","cm-3.4","cm-3.6","cm-4","cm-4.1","cm-4.2","cm-5","cm-5.1","cm-6","cm-6.1","cm-6.2","cm-7","cm-7.1","cm-7.2","cm-7.5","cm-8","cm-8.1","cm-8.2","cm-8.3","cm-8.4","cm-9","cm-10","cm-11","cm-12","cm-12.1","cp-1","cp-2","cp-2.1","cp-2.2","cp-2.3","cp-2.5","cp-2.8","cp-3","cp-3.1","cp-4","cp-4.1","cp-4.2","cp-6","cp-6.1","cp-6.2","cp-6.3","cp-7","cp-7.1","cp-7.2","cp-7.3","cp-7.4","cp-8","cp-8.1","cp-8.2","cp-8.3","cp-8.4","cp-9","cp-9.1","cp-9.2","cp-9.3","cp-9.5","cp-9.8","cp-10","cp-10.2","cp-10.4","ia-1","ia-2","ia-2.1","ia-2.2","ia-2.5","ia-2.8","ia-2.12","ia-3","ia-4","ia-4.4","ia-5","ia-5.1","ia-5.2","ia-5.6","ia-6","ia-7","ia-8","ia-8.1","ia-8.2","ia-8.4","ia-11","ia-12","ia-12.2","ia-12.3","ia-12.4","ia-12.5","ir-1","ir-2","ir-2.1","ir-2.2","ir-3","ir-3.2","ir-4","ir-4.1","ir-4.4","ir-4.11","ir-5","ir-5.1","ir-6","ir-6.1","ir-6.3","ir-7","ir-7.1","ir-8","ma-1","ma-2","ma-2.2","ma-3","ma-3.1","ma-3.2","ma-3.3","ma-4","ma-4.3","ma-5","ma-5.1","ma-6","mp-1","mp-2","mp-3","mp-4","mp-5","mp-6","mp-6.1","mp-6.2","mp-6.3","mp-7","pe-1","pe-2","pe-3","pe-3.1","pe-4","pe-5","pe-6","pe-6.1","pe-6.4","pe-8","pe-8.1","pe-9","pe-10","pe-11","pe-11.1","pe-12","pe-13","pe-13.1","pe-13.2","pe-14","pe-15","pe-15.1","pe-16","pe-17","pe-18","pl-1","pl-2","pl-4","pl-4.1","pl-8","pl-10","pl-11","ps-1","ps-2","ps-3","ps-4","ps-4.2","ps-5","ps-6","ps-7","ps-8","ps-9","ra-1","ra-2","ra-3","ra-3.1","ra-5","ra-5.2","ra-5.4","ra-5.5","ra-5.11","ra-7","ra-9","sa-1","sa-2","sa-3","sa-4","sa-4.1","sa-4.2","sa-4.5","sa-4.9","sa-4.10","sa-5","sa-8","sa-9","sa-9.2","sa-10","sa-11","sa-15","sa-15.3","sa-16","sa-17","sa-21","sa-22","sc-1","sc-2","sc-3","sc-4","sc-5","sc-7","sc-7.3","sc-7.4","sc-7.5","sc-7.7","sc-7.8","sc-7.18","sc-7.21","sc-8","sc-8.1","sc-10","sc-12","sc-12.1","sc-13","sc-15","sc-17","sc-18","sc-20","sc-21","sc-22","sc-23","sc-24","sc-28","sc-28.1","sc-39","si-1","si-2","si-2.2","si-3","si-4","si-4.2","si-4.4","si-4.5","si-4.10","si-4.12","si-4.14","si-4.20","si-4.22","si-5","si-5.1","si-6","si-7","si-7.1","si-7.2","si-7.5","si-7.7","si-7.15","si-8","si-8.2","si-10","si-11","si-12","si-16","sr-1","sr-2","sr-2.1","sr-3","sr-5","sr-6","sr-8","sr-9","sr-9.1","sr-10","sr-11","sr-11.1","sr-11.2","sr-12"]},"data/scenario.json":{"approaches":{"assessment-first":{"files":[{"count":1,"detail":"800-53 Revision 5","items":[{"name":"NIST 800-53"}],"model":"catalog","what":"the framework only"},{"count":1,"detail":"","items":[{"name":"800-53 High"}],"model":"profile","what":"the High baseline"},{"count":0,"detail":"activities identify related controls; reviewed-controls defines the assessment plan's control scope","model":"mapping-collection","what":"none, framework mappings are on activities"},{"count":0,"detail":"assessment-assets contains the components running checks; separate component definition documents are not needed","model":"component-definition","what":"none, engines are identified in each plan"},{"count":1,"detail":"assessment plans reference the system security plan without adding guidance to the implementation claims","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 370 controls"},{"count":4,"detail":"the three guides contain 547 requirements as activities and steps; each assessment plan references one system security plan through import-ssp","items":[{"name":"800-53 AP"},{"name":"CIS Ubuntu AP"},{"name":"DISA PgSQL AP"},{"name":"CISA SCuBA AP"}],"model":"assessment-plan","what":"one for the framework assessment, one per guide"},{"count":4,"detail":"four results documents, not four sections in one document; import-ap is a single required object referencing exactly one assessment plan","items":[{"name":"800-53 AR"},{"name":"CIS Ubuntu AR"},{"name":"DISA PgSQL AR"},{"name":"CISA SCuBA AR"}],"model":"assessment-results","what":"one per plan; each result references exactly one plan"}],"plan_of_record":"The system security plan addresses 370 controls; all three guides remain in assessment plans","rule":"Each guide becomes an assessment plan with a separate assessment results document. The framework catalog and baseline profile remain unchanged."},"catalog-first":{"files":[{"count":4,"detail":"800-53 Revision 5, CIS Ubuntu, DISA PostgreSQL, CISA SCuBA","items":[{"name":"NIST 800-53"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"}],"model":"catalog","what":"one for the framework, one for each guide"},{"count":5,"detail":"the High baseline, three guide selections and an organisational profile merging all four selections; import-profile is a single required object in the system security plan","items":[{"name":"800-53 High"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"},{"name":"Org merged"}],"model":"profile","what":"one selection per catalog and one merged selection"},{"count":3,"detail":"without mappings, guidance controls and framework controls remain two unrelated sets in the system security plan","items":[{"name":"CIS to 800-53"},{"name":"STIG to 800-53"},{"name":"SCuBA to 800-53"}],"model":"mapping-collection","what":"one per guide, linking guidance controls to framework controls"},{"count":3,"detail":"the control references a check identifier; a software component with a matching name describes the check's execution","items":[{"kind":"software","name":"Ubuntu checks"},{"kind":"software","name":"PgSQL checks"},{"kind":"software","name":"M365 checks"}],"model":"component-definition","what":"one per technology, containing check components"},{"count":1,"detail":"370 framework controls and 547 guidance controls, each requiring a by-component response; one import-profile references the merged profile because the field is a single required object","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 917 controls"},{"count":1,"detail":"","items":[{"name":"System AP"}],"model":"assessment-plan","what":"one"},{"count":1,"detail":"","items":[{"name":"System AR"}],"model":"assessment-results","what":"one"}],"plan_of_record":"The system security plan addresses 917 controls: 370 from the framework and 547 from the guides","rule":"Each guide becomes a catalog with a selection profile and a mapping collection linking guidance to the framework. The system security plan addresses every control in the merged set."},"component-first":{"files":[{"count":1,"detail":"800-53 Revision 5","items":[{"name":"NIST 800-53"}],"model":"catalog","what":"the framework only"},{"count":1,"detail":"","items":[{"name":"800-53 High"}],"model":"profile","what":"the High baseline"},{"count":0,"detail":"control implementations identify the controls served by the rules; no separate document carries the mapping","model":"mapping-collection","what":"none, framework mappings are inside component definitions"},{"count":6,"detail":"Ubuntu, PostgreSQL and Microsoft 365, with one validation component definition per checking engine","items":[{"kind":"software","name":"Ubuntu"},{"kind":"software","name":"PostgreSQL"},{"kind":"software","name":"Microsoft 365"},{"kind":"validation","name":"Ubuntu checks"},{"kind":"validation","name":"PgSQL checks"},{"kind":"validation","name":"M365 checks"}],"model":"component-definition","what":"three products with 547 rules, three engines with checks"},{"count":1,"detail":"the control count remains unchanged; rules are included in system-implementation","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 370 controls and containing 547 rules"},{"count":1,"detail":"","items":[{"name":"System AP"}],"model":"assessment-plan","what":"one"},{"count":1,"detail":"","items":[{"name":"System AR"}],"model":"assessment-results","what":"one"}],"plan_of_record":"The system security plan addresses 370 controls and contains 547 desired-state rules in components","rule":"Each guide becomes rules on the component being configured. Each checking engine becomes a separate validation component. The framework catalog and baseline profile remain unchanged."}},"excluded_model":{"model":"plan-of-action-and-milestones","reason":"The plan of action and milestones records unmet requirements and remediation. The document serves the same purpose in all three approaches and is excluded from the comparison."},"framework":{"base":188,"controls":370,"derivation":"count of /profile/imports/0/include-controls/0/with-ids in the published HIGH baseline profile, version 5.2.0","enhancements":182,"families":18,"label":"NIST SP 800-53 Revision 5, High baseline","source":"data/scenario-evidence/nist-high-baseline.json"},"hardening":[{"count_rule":"audit-steps","derivation":"count of steps titled 'Audit for ...' in Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json. The file carries 616 steps, one audit and one remediation for each recommendation, in 53 activities.","grouping":53,"grouping_label":"sections","key":"cis-ubuntu","label":"CIS Ubuntu 24.04 LTS Benchmark","requirements":308,"source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","technology":"Ubuntu"},{"count_rule":"step-type-check","derivation":"count of props step-type=check in Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json. The file carries 111 activities and 222 steps, one check and one remediate for each.","grouping":111,"grouping_label":"activities, one per requirement","key":"disa-postgres","label":"DISA STIG PostgreSQL 16","requirements":111,"source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","technology":"PostgreSQL"},{"count_rule":"steps","derivation":"count of steps in Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json, which carries 128 steps across 7 activities, one activity per Microsoft 365 service.","grouping":7,"grouping_label":"services","key":"cisa-bod-25-01","label":"CISA BOD 25-01 SCuBA","requirements":128,"source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","technology":"Microsoft 365"}],"items_note":"Each entry represents one file, with a name shortened for the diagram tile. Component-first distinguishes the product component, of type software, from the checking component, of type validation. File counts alone do not show component types.","models":["catalog","profile","mapping-collection","component-definition","system-security-plan","assessment-plan","assessment-results"],"note":"One system, one baseline and three hardening guides, modelled with each approach. The scenario compares document counts and system security plan content, not overall capability. Counts derive from the corpus, the NIST profile in data/scenario-evidence/, or OSCAL schema constraints. Each file row records the applicable constraint.","summary":"A system follows the NIST SP 800-53 Revision 5 High baseline and hardening guides for Ubuntu, PostgreSQL and Microsoft 365. The three approaches model the same requirements, using every OSCAL model except the plan of action and milestones.","title":"One system, three hardening guides"},"data/schema-evidence/assessment-subject.json":{"constraints":["anyOf requires include-all or include-subjects","each selection branch has optional type with anyOf enum [\"component\",\"inventory-item\",\"location\",\"party\",\"user\"]"],"definition":"oscal-ap-oscal-assessment-common:assessment-subject","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ap-oscal-assessment-common:assessment-subject","anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description"},"exclude-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ap-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["component","inventory-item","location","party","user"]}],"description":"Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.","title":"Subject Type"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description"},"exclude-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"include-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["component","inventory-item","location","party","user"]}],"description":"Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.","title":"Subject Type"}},"required":["include-subjects"]}],"description":"Identifies system elements being assessed, such as components, inventory items, and locations. In the assessment plan, this identifies a planned assessment subject. In the assessment results this is an actual assessment subject, and reflects any changes from the plan. exactly what will be the focus of this assessment. Any subjects not identified in this way are out-of-scope.","title":"Subject of Assessment","type":"object"},"model":"assessment-plan","note":"OSCAL 1.2.1 assessment subjects select all subjects or an explicit set. The optional type vocabulary includes component, inventory-item, location, party and user, supporting assessment of individual hosts.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_assessment-plan_schema.json at definitions/oscal-ap-oscal-assessment-common:assessment-subject.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ap-schema.json"},"data/schema-evidence/by-component.json":{"constraints":["required == [\"component-uuid\",\"uuid\",\"description\"]","has property \"component-uuid\"","has no property \"subject\", \"subject-uuid\", \"inventory-item-uuid\" or \"type\""],"definition":"oscal-ssp-oscal-ssp:by-component","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ssp-oscal-ssp:by-component","additionalProperties":false,"description":"Defines how the referenced component implements a set of controls.","properties":{"component-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to the component that is implementing a given control.","title":"Component Universally Unique Identifier Reference"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes how a control or a control statement is implemented within the referenced system component.","title":"Control Implementation Description"},"export":{"additionalProperties":false,"description":"Identifies content intended for external consumption, such as with leveraged organizations.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that can be available to another system leveraging this system.","title":"Control Implementation Export Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided":{"items":{"additionalProperties":false,"description":"Describes a capability which may be inherited by a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that can be provided to another system leveraging this system.","title":"Provided Control Implementation Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Provided Universally Unique Identifier"}},"required":["uuid","description"],"title":"Provided Control Implementation","type":"object"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsibilities":{"items":{"additionalProperties":false,"description":"Describes a control implementation responsibility imposed on a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that a leveraging system must implement to satisfy the control provided by a leveraged system.","title":"Control Implementation Responsibility Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.","title":"Provided UUID"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Responsibility Universally Unique Identifier"}},"required":["uuid","description"],"title":"Control Implementation Responsibility","type":"object"},"minItems":1,"type":"array"}},"title":"Export","type":"object"},"implementation-status":{"$ref":"#/definitions/oscal-ssp-oscal-implementation-common:implementation-status"},"inherited":{"items":{"additionalProperties":false,"description":"Describes a control implementation inherited by a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is inheriting from a leveraged system.","title":"Inherited Control Implementation Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.","title":"Provided UUID"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Inherited Universally Unique Identifier"}},"required":["uuid","description"],"title":"Inherited Control Implementation","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"satisfied":{"items":{"additionalProperties":false,"description":"Describes how this system satisfies a responsibility imposed by a leveraged system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is implementing based on a requirement from a leveraged system.","title":"Satisfied Control Implementation Responsibility Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsibility-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system.","title":"Responsibility UUID"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Satisfied Universally Unique Identifier"}},"required":["uuid","description"],"title":"Satisfied Control Implementation Responsibility","type":"object"},"minItems":1,"type":"array"},"set-parameters":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-implementation-common:set-parameter"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"By-Component Universally Unique Identifier"}},"required":["component-uuid","uuid","description"],"title":"Component Control Implementation","type":"object"},"model":"system-security-plan","note":"The oscal-ssp-oscal-ssp:by-component definition, which is the only way a system security plan responds to a control. It is keyed by component-uuid and has no subject of any kind: no inventory-item, no location, no party, no user. A plan can describe inventory items elsewhere, in system-implementation, but a control response cannot be made against one, so two hosts of the same component share a single response.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_ssp_schema.json at definitions/oscal-ssp-oscal-ssp:by-component.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ssp-schema.json"},"data/schema-evidence/finding-target.json":{"constraints":["required == [\"type\",\"target-id\",\"status\"]","type is constrained by allOf to enum [\"statement-id\",\"objective-id\"]","status.required includes \"state\"","status.state enum == [\"satisfied\",\"not-satisfied\"]"],"definition":"oscal-ar-oscal-assessment-common:finding-target","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:finding-target","additionalProperties":false,"description":"Captures an assessor's conclusions regarding the degree to which an objective is satisfied.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the assessor's conclusions regarding the degree to which an objective is satisfied.","title":"Objective Status Description"},"implementation-status":{"$ref":"#/definitions/oscal-ar-oscal-implementation-common:implementation-status"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"status":{"additionalProperties":false,"description":"A determination of if the objective is satisfied or not within a given system.","properties":{"reason":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["pass","fail","other"]}],"description":"The reason the objective was given it's status.","title":"Objective Status Reason"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"state":{"allOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["satisfied","not-satisfied"]}],"description":"An indication as to whether the objective is satisfied or not.","title":"Objective Status State"}},"required":["state"],"title":"Objective Status","type":"object"},"target-id":{"$ref":"#/definitions/TokenDatatype","description":"A machine-oriented identifier reference for a specific target qualified by the type.","title":"Finding Target Identifier Reference"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this objective status.","title":"Objective Status Title"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["statement-id","objective-id"]}],"description":"Identifies the type of the target.","title":"Finding Target Type"}},"required":["type","target-id","status"],"title":"Objective Status","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:finding-target definition from the OSCAL 1.2.1 assessment-results model, demonstrating that a finding target requires type, target-id, and status, restricts type by allOf to the closed enumeration statement-id or objective-id, and requires a status.state drawn from the closed enumeration satisfied or not-satisfied.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/finding.json":{"constraints":["required includes \"target\""],"definition":"oscal-ar-oscal-assessment-common:finding","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:finding","additionalProperties":false,"description":"Describes an individual finding.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this finding.","title":"Finding Description"},"implementation-statement-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related.","title":"Implementation Statement UUID"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"origins":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:origin"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"related-observations":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:related-observation"},"minItems":1,"type":"array"},"related-risks":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:associated-risk"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"target":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:finding-target"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this finding.","title":"Finding Title"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Finding Universally Unique Identifier"}},"required":["uuid","title","description","target"],"title":"Finding","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:finding definition from the OSCAL 1.2.1 assessment-results model, demonstrating that every finding must carry a target.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/mapping-item.json":{"constraints":["required == [\"type\",\"id-ref\"]","type is constrained by allOf to enum [\"control\",\"statement\"]","no property named 'uuid'","no property named 'href'"],"definition":"oscal-mapping-oscal-mapping-common:mapping-item","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-mapping-oscal-mapping-common:mapping-item","additionalProperties":false,"description":"A specific edge within a source or target that is the subject of a mapping.","properties":{"id-ref":{"$ref":"#/definitions/StringDatatype","description":"A reference to an identified subject that is of the specified type .","title":"Subject Identifier Reference"},"links":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:remarks"},"type":{"allOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["control","statement"]}],"description":"The semantic type of the subject.","title":"Subject Type"}},"required":["type","id-ref"],"title":"Mapping Entry Item (source or target)","type":"object"},"model":"mapping-collection","note":"The oscal-mapping-oscal-mapping-common:mapping-item definition from the OSCAL 1.2.1 mapping-collection model, demonstrating that a mapping item requires only type and id-ref, restricts type by allOf to the closed enumeration control or statement, and defines no uuid or href property.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-mapping-schema.json"},"data/schema-evidence/mapping-resource-reference.json":{"constraints":["required == [\"type\",\"href\"]","type uses anyOf (open vocabulary) with enum [\"catalog\",\"profile\"]"],"definition":"oscal-mapping-oscal-mapping-common:mapping-resource-reference","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-mapping-oscal-mapping-common:mapping-resource-reference","additionalProperties":false,"description":"A reference to a resource that is either the source or the target of a mapping.","properties":{"href":{"$ref":"#/definitions/URIReferenceDatatype","description":"A resolvable URL reference to the base catalog or profile that this profile is tailoring.","title":"Catalog or Profile Reference"},"links":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:link"},"minItems":1,"type":"array"},"ns":{"$ref":"#/definitions/URIDatatype","description":"An optional namespace qualifying the resource's type.","title":"Resource Type Namespace"},"props":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["catalog","profile"]}],"description":"The semantic type of the resource.","title":"Resource Type"}},"required":["type","href"],"title":"Mapped Resource Reference","type":"object"},"model":"mapping-collection","note":"The oscal-mapping-oscal-mapping-common:mapping-resource-reference definition from the OSCAL 1.2.1 mapping-collection model, demonstrating that a mapped resource reference requires type and href and constrains type with an open anyOf vocabulary whose enumeration lists catalog and profile.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-mapping-schema.json"},"data/schema-evidence/metadata.json":{"constraints":["required == [\"title\",\"last-modified\",\"version\",\"oscal-version\"]"],"definition":"oscal-ap-oscal-metadata:metadata","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ap-oscal-metadata:metadata","additionalProperties":false,"description":"Provides information about the containing document, and defines concepts that are shared across the document.","properties":{"actions":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:action"},"minItems":1,"type":"array"},"document-ids":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:document-id"},"minItems":1,"type":"array"},"last-modified":{"$ref":"#/definitions/oscal-ap-oscal-metadata:last-modified"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"locations":{"items":{"additionalProperties":false,"description":"A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.","properties":{"address":{"$ref":"#/definitions/oscal-ap-oscal-metadata:address"},"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the location, which may be used by a tool for display and navigation.","title":"Location Title"},"urls":{"items":{"$ref":"#/definitions/URIDatatype","description":"The uniform resource locator (URL) for a web site or other resource associated with the location.","title":"Location URL"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique ID for the location, for reference.","title":"Location Universally Unique Identifier"}},"required":["uuid"],"title":"Location","type":"object"},"minItems":1,"type":"array"},"oscal-version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:oscal-version"},"parties":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:address"},"minItems":1,"type":"array"},"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"external-ids":{"items":{"additionalProperties":false,"description":"An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).","properties":{"id":{"$ref":"#/definitions/StringDatatype"},"scheme":{"anyOf":[{"$ref":"#/definitions/URIDatatype"},{"enum":["http://orcid.org/"]}],"description":"Indicates the type of external identifier.","title":"External Identifier Schema"}},"required":["id","scheme"],"title":"Party External Identifier","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"member-of-organizations":{"items":{"$ref":"#/definitions/UUIDDatatype","description":"A reference to another party by UUID, typically an organization, that this subject is associated with.","title":"Organizational Affiliation"},"minItems":1,"type":"array"},"name":{"$ref":"#/definitions/StringDatatype","description":"The full name of the party. This is typically the legal name associated with the party.","title":"Party Name"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the party.","title":"Party Short Name"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["person","organization"]}],"description":"A category describing the kind of party the object describes.","title":"Party Type"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique identifier for the party.","title":"Party Universally Unique Identifier"}}},{"additionalProperties":false,"properties":{"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"external-ids":{"items":{"additionalProperties":false,"description":"An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).","properties":{"id":{"$ref":"#/definitions/StringDatatype"},"scheme":{"anyOf":[{"$ref":"#/definitions/URIDatatype"},{"enum":["http://orcid.org/"]}],"description":"Indicates the type of external identifier.","title":"External Identifier Schema"}},"required":["id","scheme"],"title":"Party External Identifier","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"location-uuids":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:location-uuid"},"minItems":1,"type":"array"},"member-of-organizations":{"items":{"$ref":"#/definitions/UUIDDatatype","description":"A reference to another party by UUID, typically an organization, that this subject is associated with.","title":"Organizational Affiliation"},"minItems":1,"type":"array"},"name":{"$ref":"#/definitions/StringDatatype","description":"The full name of the party. This is typically the legal name associated with the party.","title":"Party Name"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the party.","title":"Party Short Name"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["person","organization"]}],"description":"A category describing the kind of party the object describes.","title":"Party Type"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique identifier for the party.","title":"Party Universally Unique Identifier"}}}],"description":"An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.","title":"Party","type":"object"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"published":{"$ref":"#/definitions/oscal-ap-oscal-metadata:published"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"responsible-parties":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:responsible-party"},"minItems":1,"type":"array"},"revisions":{"items":{"additionalProperties":false,"description":"An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).","properties":{"last-modified":{"$ref":"#/definitions/oscal-ap-oscal-metadata:last-modified"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"oscal-version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:oscal-version"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"published":{"$ref":"#/definitions/oscal-ap-oscal-metadata:published"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the document revision, which may be used by a tool for display and navigation.","title":"Document Title"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["version"],"title":"Revision History Entry","type":"object"},"minItems":1,"type":"array"},"roles":{"items":{"additionalProperties":false,"description":"Defines a function, which might be assigned to a party in a specific situation.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A summary of the role's purpose and associated responsibilities.","title":"Role Description"},"id":{"$ref":"#/definitions/TokenDatatype","description":"A unique identifier for the role.","title":"Role Identifier"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the role.","title":"Role Short Name"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the role, which may be used by a tool for display and navigation.","title":"Role Title"}},"required":["id","title"],"title":"Role","type":"object"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the document, which may be used by a tool for display and navigation.","title":"Document Title"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["title","last-modified","version","oscal-version"],"title":"Document Metadata","type":"object"},"model":"assessment-plan","note":"The shared oscal-metadata:metadata assembly. Every OSCAL document, a catalog among them, is required to carry a title, a last-modified timestamp, a version and the OSCAL version it conforms to. That is what makes a published guide citable as a document rather than as a copy.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_assessment-plan_schema.json at definitions/oscal-ap-oscal-metadata:metadata.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ap-schema.json"},"data/schema-evidence/observation.json":{"constraints":["required == [\"uuid\",\"description\",\"methods\",\"collected\"]","no property named 'target'","no property named 'control-id'","no property named 'objective-id'"],"definition":"oscal-ar-oscal-assessment-common:observation","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:observation","additionalProperties":false,"description":"Describes an individual observation.","properties":{"collected":{"$ref":"#/definitions/DateTimeWithTimezoneDatatype","description":"Date/time stamp identifying when the finding information was collected.","title":"Collected Field"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this assessment observation.","title":"Observation Description"},"expires":{"$ref":"#/definitions/DateTimeWithTimezoneDatatype","description":"Date/time identifying when the finding information is out-of-date and no longer valid. Typically used with continuous assessment scenarios.","title":"Expires Field"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"methods":{"items":{"anyOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["EXAMINE","INTERVIEW","TEST","UNKNOWN"]}],"description":"Identifies how the observation was made.","title":"Observation Method"},"minItems":1,"type":"array"},"origins":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:origin"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"relevant-evidence":{"items":{"additionalProperties":false,"description":"Links this observation to relevant evidence.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this evidence.","title":"Relevant Evidence Description"},"href":{"$ref":"#/definitions/URIReferenceDatatype","description":"A resolvable URL reference to relevant evidence.","title":"Relevant Evidence Reference"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["description"],"title":"Relevant Evidence","type":"object"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"subjects":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:subject-reference"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this observation.","title":"Observation Title"},"types":{"items":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["ssp-statement-issue","control-objective","mitigation","finding","discovery","historic"]}],"description":"Identifies the nature of the observation. More than one may be used to further qualify and enable filtering.","title":"Observation Type"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Observation Universally Unique Identifier"}},"required":["uuid","description","methods","collected"],"title":"Observation","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:observation definition from the OSCAL 1.2.1 assessment-results model, demonstrating that an observation requires uuid, description, methods, and collected, and defines no target, control-id, or objective-id property.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/poam-outcomes.json":{"constraints":["properties includes \"observations\"","properties includes \"findings\"","observations items ref the shared assessment-common observation","findings items ref the shared assessment-common finding"],"definition":"oscal-poam-oscal-poam:plan-of-action-and-milestones","fetched_at":"2026-08-18","fragment":{"properties":{"findings":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:finding"},"minItems":1,"type":"array"},"observations":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:observation"},"minItems":1,"type":"array"},"risks":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:risk"},"minItems":1,"type":"array"}},"required":["uuid","metadata","poam-items"]},"fragment_note":"Only required and the observations, findings and risks properties are carried.","model":"plan-of-action-and-milestones","note":"The root assembly of the OSCAL 1.2.1 plan-of-action-and-milestones model. It carries observations and findings as sibling arrays, so assessment results is not the only model in which an outcome can be recorded. Both models sit in the Assessment layer; no control-layer or implementation-layer model carries either.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-poam-schema.json"},"data/schema-evidence/result.json":{"constraints":["required includes \"reviewed-controls\""],"definition":"oscal-ar-oscal-ar:result","fetched_at":"2026-08-18","fragment":{"properties":{"reviewed-controls":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls"}},"required":["uuid","title","description","start","reviewed-controls"]},"fragment_note":"Only required and the reviewed-controls property are carried. The other properties of result are not relevant to this claim and are omitted.","model":"assessment-results","note":"The result assembly of the OSCAL 1.2.1 assessment-results model. Every result is required to declare the controls it reviewed, so the control frame is unavoidable at the result level. The referenced reviewed-controls assembly requires control-selections, and a selection may use include-all rather than naming individual controls, so the requirement can be met without listing any one control.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/reviewed-controls.json":{"constraints":["required == [\"control-selections\"]","control-selections items use anyOf with required [\"include-all\"] or [\"include-controls\"]"],"definition":"oscal-ar-oscal-assessment-common:reviewed-controls","fetched_at":"2026-08-18","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls","additionalProperties":false,"description":"Identifies the controls being assessed and their control objectives.","properties":{"control-objective-selections":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this collection of control objectives.","title":"Control Objectives Description"},"exclude-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ar-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this collection of control objectives.","title":"Control Objectives Description"},"exclude-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"include-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-objectives"]}],"description":"Identifies the control objectives of the assessment. In the assessment plan, these are the planned objectives. In the assessment results, these are the assessed objectives, and reflects any changes from the plan.","title":"Referenced Control Objectives","type":"object"},"minItems":1,"type":"array"},"control-selections":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of in-scope controls specified for assessment.","title":"Assessed Controls Description"},"exclude-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ar-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of in-scope controls specified for assessment.","title":"Assessed Controls Description"},"exclude-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"include-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-controls"]}],"description":"Identifies the controls being assessed. In the assessment plan, these are the planned controls. In the assessment results, these are the actual controls, and reflects any changes from the plan.","title":"Assessed Controls","type":"object"},"minItems":1,"type":"array"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of control objectives.","title":"Control Objective Description"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["control-selections"],"title":"Reviewed Controls and Control Objectives","type":"object"},"model":"assessment-results","note":"The reviewed-controls assembly of the OSCAL 1.2.1 assessment-results model. It requires control-selections, and each selection must carry either include-all or include-controls. So the requirement that a result declare the controls it reviewed can be satisfied with include-all, without naming any one control. The single assessment result in the three bodies of content does exactly that.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/six-questions.json":{"answer_states":[{"key":"filled","label":"Answered","meaning":"The published content answers this question."},{"key":"partial","label":"Partly answered","meaning":"The published content answers part of this question."},{"key":"empty-absent","label":"Not answered","meaning":"The published content does not answer the question or state a reason for the omission."}],"approaches":[{"key":"catalog-first","label":"Catalog-first","layer":"Control","one_line":"The rule is a catalog control; the check is a software component in a component definition.","option_letter":"A","primary_model":"catalog","repo":"https://github.com/awslabs/oscal-content-for-aws-services","serves_stakeholder_first":"publisher","status_annotation":"experimental, per publisher"},{"key":"component-first","label":"Component-first","layer":"Implementation","one_line":"The rule uses a proposed assembly on the product component; the check uses a proposed assembly on a validation component.","option_letter":"B","primary_model":"component-definition","repo":null,"serves_stakeholder_first":"implementer","status_annotation":"proposed schema"},{"key":"assessment-first","label":"Assessment-first","layer":"Assessment","one_line":"The rule is an assessment plan activity or step; a property identifies the check.","option_letter":"C","primary_model":"assessment-plan","repo":null,"serves_stakeholder_first":"assessor","status_annotation":"placeholder and synthetic identifiers"}],"carrier_note":"Each answer identifies the OSCAL model and assemblies representing the capability. Rules use catalog controls, component rules or assessment activities; the choice affects references to checks, claims and results.","empty_states":[{"key":"empty-absent","label":"Unanswered, no stated position","meaning":"The published content does not answer the question or state a reason for the omission.","rendering":"hollow with a light dotted fill"}],"finding":"Questions 1 and 2 are answered by all three approaches. No approach fully answers both 6a and 6b, and no approach answers every question.","legend":{"answers_title":"Is the question answered?","label":"How to read an answer","mechanism_title":"How the capability is enabled","why_one_block":"Each cell combines an answer state with mechanism badges. A shared legend explains both dimensions together.","why_uneven":"Answer states describe evidence coverage. Mechanism descriptions also explain schema and tool-support requirements, so the descriptions need additional detail."},"matrix":[{"approach":"catalog-first","assemblies":["control"],"mechanisms":["assembly","prop"],"model":"catalog","note":"One control per rule. Existing assemblies capture context around the rule's intent.","props":[{"name":"TechnicalControlId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"1","snippet_ids":["aws-acm2-control","aws-input-parameter"],"state":"filled"},{"approach":"component-first","assemblies":["component","rules"],"mechanisms":["proposed"],"model":"component-definition","note":"The proposed rules assembly sits on the component alongside control-implementations.","slot":"1","snippet_ids":["ibm-cos-component"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The activity defines the rule and the step describes the check. Without a parameter field, required values are recorded in text.","props":[{"name":"check","ns":"http://comply0.com/ns/oscal"}],"slot":"1","snippet_ids":["ez-stig-activity-v259312","ez-stig-sc28-v270747"],"state":"filled"},{"approach":"catalog-first","assemblies":["mapping","map"],"mechanisms":["assembly"],"model":"mapping-collection","note":"A separate mapping collection links rules to framework controls. The published corpus contains no such mapping document.","slot":"2","snippet_ids":["aws-acm-backmatter-source","aws-acm-service-rollup"],"state":"filled"},{"approach":"component-first","assemblies":["component","implemented-requirement","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"component-definition","note":"Existing assemblies link the component to the control. Linking an individual rule requires the proposed assembly.","slot":"2","snippet_ids":["ibm-statement-rules","ibm-cos-component"],"state":"filled"},{"approach":"assessment-first","assemblies":["reviewed-controls","activity","related-controls"],"mechanisms":["assembly"],"model":"assessment-plan","note":"Two levels: reviewed-controls defines the required plan scope; related-controls optionally links an activity to controls.","slot":"2","snippet_ids":["ez-stig-related-controls","ez-cisa-step-reviewed"],"state":"filled"},{"approach":"catalog-first","assemblies":["component","implemented-requirement"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"The check identifier resolves within the runtime to an executable machine check.","props":[{"name":"ConfigRuleId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"3","snippet_ids":["aws-acm2-control","aws-acm-rsa-check-component"],"state":"filled"},{"approach":"component-first","assemblies":["component","checks"],"mechanisms":["proposed"],"model":"component-definition","note":"The proposed schema places both composite-key fields on the check. The rule has no reference back to the check.","slot":"3","snippet_ids":["ibm-validation-ansible"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"Three conventions: CISA references an executable through a JSON string in a prop; STIG and CIS describe checks in prose.","props":[{"name":"check","ns":"http://comply0.com/ns/oscal"}],"slot":"3","snippet_ids":["ez-cis-step-props","ez-cis-remediation-step","ez-cisa-context-step"],"state":"partial"},{"approach":"catalog-first","assemblies":["implemented-requirement","by-component"],"mechanisms":["assembly"],"model":"system-security-plan","note":"The by-component response identifies a component, not an instance. An assessment plan cannot import a catalog directly.","slot":"4","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["implemented-requirement","by-component","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"system-security-plan","note":"The proposed rule reference extends by-component. An assessor can include the component definition and associated checks in an assessment plan.","slot":"4","snippet_ids":["ibm-validation-ansible"],"state":"partial"},{"approach":"assessment-first","assemblies":["assessment-subjects","task","subjects"],"mechanisms":["assembly"],"model":"assessment-plan","note":"The plan defines subject scope; activity-associated tasks select targets. Both can identify inventory items, representing instances rather than classes.","slot":"4","snippet_ids":["ez-subjects-includeall","ez-subjects-explicit"],"state":"filled"},{"approach":"catalog-first","assemblies":["component"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"The content records inputs and outputs but not the engine. ConfigRuleId resolves within the engine. No assessor workflow is shown; an assessment plan cannot import a catalog directly.","paths":[{"assemblies":["component","by-component"],"in":{"slot":"3"},"key":"implementor","label":"Implementor's path","out":{"slot":"6a"}}],"props":[{"name":"ConfigRuleId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"5","snippet_ids":["aws-config-service-bare"],"state":"partial"},{"approach":"component-first","assemblies":["component"],"mechanisms":["assembly","proposed"],"model":"component-definition","note":"The examples leave runner associations unresolved, including how an assessment asset links to a task or an observation.","paths":[{"assemblies":["component","checks","by-component","implementing-rules"],"in":{"slot":"3"},"key":"implementor","label":"Implementor's path","out":{"slot":"6a"}},{"assemblies":["component","checks","assessment-assets","observation","assessment-check-id","result"],"copy":{"slot":"3"},"in":{"model":"assessment-plan"},"key":"assessor","label":"Assessor's path","out":{"slot":"6b"}}],"slot":"5","snippet_ids":["ibm-ap-activity","ibm-ap-task-subjects","ibm-ar-observation"],"state":"filled"},{"approach":"assessment-first","assemblies":["assessment-platforms","component","task"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The platform executes the check, a referenced component represents the plugin, and a task property identifies the platform.","paths":[{"assemblies":["activity","step","assessment-platforms","component","task","observation"],"in":{"model":"assessment-plan"},"key":"assessor","label":"Assessor's path","out":{"slot":"6b"}}],"props":[{"name":"assessment-platform","ns":"http://comply0.com/ns/oscal"}],"slot":"5","snippet_ids":["ez-cisa-context-activity","ez-cisa-assessment-assets","ez-cisa-task-timing"],"state":"partial"},{"approach":"catalog-first","assemblies":["implemented-requirement","by-component"],"mechanisms":["assembly"],"model":"system-security-plan","note":"The component definition describes how a component could satisfy a control, not a system's implementation. The corpus contains no system security plan.","slot":"6a","snippet_ids":["aws-acm-rsa-check-component","aws-acm-service-rollup"],"state":"partial"},{"approach":"component-first","assemblies":["implemented-requirement","by-component","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"system-security-plan","note":"The claim uses a by-component response. Identifying the supporting rule requires the proposed implementing-rules assembly.","slot":"6a","snippet_ids":[],"state":"empty-absent"},{"approach":"assessment-first","assemblies":["import-ssp","back-matter","resource"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The assessment plan references the document containing the implementation claim. A back-matter resource supports cases without a plan of record.","slot":"6a","snippet_ids":["ez-cisa-import-ssp","ez-cisa-ssp-resource","ez-cisa-no-ssp-resource","ez-stig-import-ssp"],"state":"partial"},{"approach":"catalog-first","assemblies":["finding"],"mechanisms":["assembly"],"model":"assessment-results","note":"No assessment results are published in the catalog-first OSCAL corpus.","slot":"6b","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["observation"],"mechanisms":["assembly","proposed"],"model":"assessment-results","note":"The result contains observations but no findings or objective status. The control reference must be recovered through the assessment plan.","slot":"6b","snippet_ids":["ibm-ar-observation"],"state":"partial"},{"approach":"assessment-first","assemblies":["finding","observation"],"mechanisms":["assembly"],"model":"assessment-results","note":"A separate results document imports the plan. Findings have targets and status; observations identify the executed activity as the subject.","slot":"6b","snippet_ids":["ez-cisa-ar-finding","ez-cisa-ar-observation"],"state":"filled"}],"mechanism_note":"Answer states describe coverage in the published corpus. Mechanism badges identify the OSCAL structures needed to represent an answer. Evidence coverage does not establish schema adoption or tool interoperability.","mechanism_states":[{"key":"assembly","label":"Released OSCAL assembly","meaning":"A released OSCAL assembly provides the capability without a schema change.","rendering":"a solid badge","short":"OSCAL assembly"},{"key":"proposed","label":"Proposed assembly","meaning":"The capability requires a proposed assembly. Interoperable use requires schema adoption and tool support for the new structure.","rendering":"a dashed badge","short":"Proposed"},{"key":"prop","label":"Namespaced property","meaning":"A property in the publisher's namespace provides the capability. Tools need a shared convention to interpret the property; the OSCAL schema does not define the meaning.","rendering":"a dotted badge","short":"Prop"}],"note":"The six questions and answer matrix compare OSCAL JSON examples, including content using proposed assemblies. tools/verify.py --matrix checks each cell against the example files. Notes describe supported capabilities and unresolved questions.","paths_note":"Each runner path shows one input document and one output document. The documents depend on whether the system owner or assessor runs the check.","proposed_assemblies":["assessment-check-id","associated-checks","checks","implementing-rules","result","rule-groups","rules"],"slots":[{"key":"rule","name":"What the rule requires","number":"1","optional":false,"question":"What condition must hold, and where is the requirement defined?","short":"Rule","why_separate":"A technology-specific requirement defines one testable condition. Parameter options and defaults belong with that definition where the selected model supports them."},{"binding_times":[{"authored_by":"Rule author","key":"inline","label":"Author-time, inline","mechanism":"The rule declares its control directly"},{"authored_by":"Rule author","key":"pointer","label":"Author-time, by pointer","mechanism":"A prop carries an external framework identifier that a consumer must resolve"},{"authored_by":"Rule author or third party","available_to":{"assessment-first":false,"catalog-first":true,"component-first":false},"key":"late","label":"Late, external","mechanism":"A separate artifact links a rule to a control after publication","why":"mapping-item.type is restricted by allOf to control and statement, and mapping-item has neither uuid nor href. External mappings therefore reach rules modelled as controls or control statements, not component rules or activities. This OSCAL schema constraint does not establish a preferred approach."}],"cost_of_leaving_empty":{"evidence":["observation.json","finding.json","finding-target.json"],"finding":"Not available. finding requires target; finding-target requires type, restricted by allOf to statement-id or objective-id, both control-derived.","observation":"Available. AR observation requires only uuid, description, methods and collected, with no control reference.","summary":"Without a control link, an assessor can record an observation but not a finding against a control statement or objective."},"key":"control-tie","name":"How the rule links to a control","number":"2","optional":true,"question":"Does this rule help satisfy a regulatory control, and which one?","short":"Control","why_separate":"A rule is finer-grained than a control and may serve several controls, one, or none. A control-linking mechanism is required, but using the mechanism is optional."},{"key":"check","name":"How the rule is tested","number":"3","optional":false,"question":"Which executable or procedure tests the rule?","short":"Check","why_separate":"A rule may have several checks, one per tool. The examples separate rule definitions from checks and reference external executables rather than embedding code in OSCAL."},{"key":"subject","name":"What the check runs against","not_established":true,"not_established_note":"The examples use assessment platforms, assets and components differently. A consistent distinction between the subject being assessed and the resources performing the assessment is not established here.","number":"4","optional":false,"question":"Is the subject a host, component, account or another resource?","short":"Subject","why_separate":"The subject identifies the assessed host, inventory item, component or account. Criterion 8 addresses response fidelity."},{"key":"actor","name":"What performs the check","not_established":true,"not_established_note":"The same distinction remains open in question 4. The approaches use different combinations of assessment-assets, assessment-platforms, uses-components, validation components, origin actors, task-level props and the method prop.","number":"5","optional":false,"question":"Which tool or person performs the check, and how is the runner identified?","short":"Runner","why_separate":"The runner may be a validation component, assessment platform, tool or person. The method prop identifies examine, interview or test."},{"group_name":"Implementation claims and assessment outcomes","key":"implementation-claim","name":"How the system claims it meets the rule","number":"6a","optional":false,"question":"How does the system owner describe implementation of the rule?","short":"Claim","why_separate":"The system owner provides a narrative claim of implementation and design intent per component. The SSP represents claims through implemented-requirement, statement and by-component."},{"group_name":"Implementation claims and assessment outcomes","key":"assessment-result","name":"How an assessment records the outcome","number":"6b","optional":false,"question":"Was the rule satisfied, when, and for which subject?","short":"Result","why_separate":"The assessor records evidence and a binary or graded outcome per subject at a point in time. The AR uses observation, finding and status. A desired-state rule has a binary satisfaction condition; the SSP implementation claim is narrative."}]},"data/snippets/aws-acm-backmatter-source.json":{"approach":"catalog-first","content":"{\n \"resources\": [\n {\n \"uuid\": \"ab8a6a36-2706-49e5-b87e-498c52ba6a61\",\n \"title\": \"AWS Regions Component Definition\",\n \"rlinks\": [\n {\n \"href\": \"../aws_regions.oscal.json\",\n \"media-type\": \"application/json\"\n }\n ]\n },\n {\n \"uuid\": \"f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"title\": \"AWS Security Hub Controls\",\n \"rlinks\": [\n {\n \"href\": \"../catalogs/aws_security-hub.oscal.json\",\n \"media-type\": \"application/json\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-backmatter-source","language":"json","pointer":"/component-definition/back-matter","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"Back-matter, source to the catalog"},"data/snippets/aws-acm-rsa-check-component.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"b5e8b205-cc1f-4bd0-9e51-4ebaab18f69a\",\n \"type\": \"software\",\n \"title\": \"acm-certificate-rsa-check\",\n \"description\": \"Checks if RSA certificates managed by AWS Certificate Manager (ACM) have a key length of at least '2048' bits. The rule is NON_COMPLIANT if the minimum key length is less than 2048 bits.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"ACM_CERTIFICATE_RSA_CHECK\"\n },\n {\n \"name\": \"asset-type\",\n \"value\": \"automated-inspection\"\n },\n {\n \"name\": \"ResourceType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"AWS::ACM::Certificate\"\n }\n ],\n \"responsible-roles\": [\n {\n \"role-id\": \"owner\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"4f227b9d-b47b-4c06-bb55-8f3a17e29b74\",\n \"source\": \"#f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"description\": \"Security Hub control implementation\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"4de99497-e4fe-4dfd-80a7-ebbd59f06364\",\n \"control-id\": \"ACM.2\",\n \"description\": \"Implemented via AWS Config Rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-rsa-check-component","language":"json","pointer":"/component-definition/components/2","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"3","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"acm-certificate-rsa-check, the check component"},"data/snippets/aws-acm-service-rollup.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"ae50c910-9057-4345-89d9-c2ae4c1f0b08\",\n \"source\": \"#f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"description\": \"AWS Security Hub control implementation\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"c3e6d492-b3b6-46d9-9e2a-7d6d9922f3fa\",\n \"control-id\": \"ACM.1\",\n \"description\": \"Security Hub control ACM.1\"\n },\n {\n \"uuid\": \"551c5fc8-569a-4ea5-a0d8-0b524e9f4205\",\n \"control-id\": \"ACM.2\",\n \"description\": \"Security Hub control ACM.2\"\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-service-rollup","language":"json","pointer":"/component-definition/components/0/control-implementations/0","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"AWS Certificate Manager, the service roll-up"},"data/snippets/aws-acm2-control.json":{"approach":"catalog-first","content":"{\n \"id\": \"ACM.2\",\n \"title\": \"ACM.2\",\n \"props\": [\n {\n \"name\": \"SeverityLabel\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"HIGH\"\n },\n {\n \"name\": \"TriggerType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Change Triggered\"\n },\n {\n \"name\": \"EvaluatedServices\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"ACM\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://docs.aws.amazon.com/console/securityhub/ACM.2/remediation\",\n \"rel\": \"remediation\"\n }\n ],\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"This control checks whether RSA certificates managed by AWS Certificate Manager use a key length of at least 2,048 bits. The control fails if the key length is smaller than 2,048 bits.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"RSA certificates managed by ACM should use a key length of at least 2,048 bits\"\n },\n {\n \"name\": \"guidance\",\n \"prose\": \"For information on how to correct this issue, consult the AWS Security Hub controls documentation.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"acm-certificate-rsa-check\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"acm-certificate-rsa-check\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm2-control","language":"json","pointer":"/catalog/groups/0/controls/1","section":null,"sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"ACM.2, the control"},"data/snippets/aws-config-service-bare.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"9a02ef98-02b2-49c4-a3ea-3c546e830a15\",\n \"type\": \"service\",\n \"title\": \"AWS Config\",\n \"description\": \"AWS Config is a service that continuously monitors and records your AWS resource configurations and allows you to automate the evaluation of recorded configurations against desired settings.\",\n \"props\": [\n {\n \"name\": \"service-id\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Config Service\"\n },\n {\n \"name\": \"version\",\n \"value\": \"2014-11-12\"\n },\n {\n \"name\": \"availability\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"REGIONAL\"\n },\n {\n \"name\": \"label\",\n \"value\": \"AWS Config\",\n \"class\": \"marketingName\",\n \"group\": \"marketing\"\n },\n {\n \"name\": \"apiEndpointPrefix\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"arnNamespace\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"cloudTrailEventSource\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"lifecycle-stage\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"generally-available\"\n },\n {\n \"name\": \"iamServicePrefix\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n }\n ],\n \"links\": \"...\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-config-service-bare","language":"json","pointer":"/component-definition/components/0","section":null,"sha256_of_source_file":"d5049e46d7a1251932be3e74c1f9bace606ac9b5f5542249ccb884171394a6e7","slot":"5","source":"AWS/oscal-content-for-aws-services-main/component-definitions/config.oscal.json","title":"AWS Config, the engine that runs the checks"},"data/snippets/aws-control-cloudtrail2.json":{"approach":"catalog-first","content":"{\n \"id\": \"CloudTrail.2\",\n \"title\": \"CloudTrail.2\",\n \"props\": [\n {\n \"name\": \"SeverityLabel\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"MEDIUM\"\n },\n {\n \"name\": \"TriggerType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Periodic\"\n },\n {\n \"name\": \"EvaluatedServices\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"CloudTrail\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://docs.aws.amazon.com/console/securityhub/CloudTrail.2/remediation\",\n \"rel\": \"remediation\"\n }\n ],\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"This AWS control checks whether AWS CloudTrail is configured to use the server side encryption (SSE) AWS Key Management Service (AWS KMS) customer master key (CMK) encryption. The check will pass if the KmsKeyId is defined.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"CloudTrail should have encryption at-rest enabled\"\n },\n {\n \"name\": \"guidance\",\n \"prose\": \"For information on how to correct this issue, consult the AWS Security Hub controls documentation.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"cloud-trail-encryption-enabled\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"cloud-trail-encryption-enabled\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-21T03:10:41+00:00","id":"aws-control-cloudtrail2","language":"json","pointer":"/catalog/groups/15/controls/2","section":null,"sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"CloudTrail.2, the control"},"data/snippets/aws-input-parameter.json":{"approach":"catalog-first","content":"[\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"IAM_PASSWORD_POLICY\"\n },\n {\n \"name\": \"asset-type\",\n \"value\": \"automated-inspection\"\n },\n {\n \"name\": \"MaxPasswordAge\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"90\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"PasswordReusePrevention\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"24\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"MinimumPasswordLength\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"14\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireNumbers\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireSymbols\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireLowercaseCharacters\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireUppercaseCharacters\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"MinimumPasswordLength\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"7\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"PasswordReusePrevention\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"4\",\n \"class\": \"InputParameter\"\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-input-parameter","language":"json","pointer":"/component-definition/components/2/props","section":null,"sha256_of_source_file":"940cab9d3328d5ff55e6c69fbfae6fd4e846873d07f70ef7c096651bc8f750ab","slot":"1","source":"AWS/oscal-content-for-aws-services-main/component-definitions/iam.oscal.json","title":"InputParameter props, the parameter mechanism"},"data/snippets/ez-cis-remediation-step.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"7be22348-467b-563a-9c21-d438e47df7df\",\n \"title\": \"Remediation for Ensure cramfs kernel module is not available\",\n \"description\": \"Run the following script to unload and disable the `cramfs` module:\\n\\n**- IF -** the `cramfs` kernel module is available in ANY installed kernel:\\n\\n- Create a file ending in `.conf` with `install cramfs /bin/false` in the `/etc/modprobe.d/` directory\\n- Create a file ending in `.conf` with `blacklist cramfs` in the `/etc/modprobe.d/` directory\\n- Run `modprobe -r cramfs 2>/dev/null; rmmod cramfs 2>/de [truncated]\",\n \"props\": [\n {\n \"name\": \"assessment-status\",\n \"value\": \"automated\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-rule-id\",\n \"value\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"step-type\",\n \"value\": \"remediation\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-remediation-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/1","section":null,"sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS remediation step"},"data/snippets/ez-cis-resolution-status.json":{"approach":"assessment-first","content":"{\n \"description\": \"CIS Controls v8.0 derived from benchmark cc8:controlURI paths. Provide a CIS Controls v8 OSCAL catalog via --cis-catalog-v8 for authoritative control-id resolution.\",\n \"props\": [\n {\n \"name\": \"framework\",\n \"value\": \"CIS Controls v8.0\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"resolution-status\",\n \"value\": \"synthetic-ids\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ],\n \"include-controls\": \"...\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-resolution-status","language":"json","pointer":"/assessment-plan/reviewed-controls/control-selections/0","section":null,"sha256_of_source_file":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8","slot":"meta","source":"Easy Dynamics/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","title":"CIS resolution status"},"data/snippets/ez-cis-step-props.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"5c4c3bec-7bbe-521d-9a90-c04102edce9b\",\n \"title\": \"Audit for Ensure cramfs kernel module is not available\",\n \"description\": \"## Description\\n\\nThe `cramfs` filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems. A `cramfs` image can be used without having to first decompress the image.\\n\\n## Audit\\n\\nRun the following script to verify:\\n\\n**- IF -** the `cramfs` kernel module is available in ANY installed kernel, verify:\\n\\n- An entry including `/bin/true` or `/bin/false` exists in a file w [truncated]\",\n \"props\": [\n {\n \"name\": \"assessment-status\",\n \"value\": \"automated\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-rule-id\",\n \"value\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"step-type\",\n \"value\": \"audit\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-control-uri\",\n \"value\": \"http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-control-uri\",\n \"value\": \"http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"CM-7\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"stig-finding-id\",\n \"value\": \"V-230498\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-safeguard-urn\",\n \"value\": \"urn:cisecurity.org:controls:8.0:4:8\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-safeguard-urn\",\n \"value\": \"urn:cisecurity.org:controls:7.0:9:2\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ],\n \"remarks\": \"Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-step-props","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0","section":null,"sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS audit step props"},"data/snippets/ez-cisa-ar-finding.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"b5d014ae-23b1-51b8-845a-972f40def692\",\n \"title\": \"MS.AAD.1.1v1: Legacy Authentication Blocking\",\n \"target\": {\n \"type\": \"objective-id\",\n \"status\": {\n \"state\": \"satisfied\"\n },\n \"target-id\": \"ms.aad.1.1v1\"\n },\n \"description\": \"Conditional Access policy confirmed blocking all legacy authentication protocols for all users.\",\n \"related-observations\": [\n {\n \"observation-uuid\": \"941e3133-152b-5301-8762-abd228b5ee80\"\n }\n ]\n}","extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ar-finding","language":"json","pointer":"/assessment-results/results/0/findings/0","section":null,"sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"A finding, targeting an objective"},"data/snippets/ez-cisa-ar-observation.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"941e3133-152b-5301-8762-abd228b5ee80\",\n \"title\": \"Observation: MS.AAD.1.1v1 - Legacy Authentication Blocking\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"remarks\": \"Legacy authentication is blocked tenant-wide via a Conditional Access policy in the enabled state. Control CM-7 is satisfied.\",\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"422ccfe4-7b60-4fe8-81ff-3d4464cc6e05\"\n }\n ],\n \"collected\": \"2026-03-05T15:30:00-05:00\",\n \"description\": \"Examiner queried the Conditional Access policy configuration via Microsoft Graph API. A policy targeting all users with a condition for legacy authentication protocols and a grant control of 'Block' was identified and confirmed enabled.\"\n}","extracted_at":"2026-08-22T18:43:41+00:00","id":"ez-cisa-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","section":null,"sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"The observation it rests on, and what was examined"},"data/snippets/ez-cisa-assessment-assets.json":{"approach":"assessment-first","content":"{\n \"components\": [\n {\n \"uuid\": \"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\",\n \"type\": \"software\",\n \"title\": \"ScubaGear Plugin\",\n \"description\": \"CLI plugin on Comply0 platform for verifying M365 configuration settings using CISA ScubaGear.\",\n \"props\": [\n {\n \"name\": \"context\",\n \"value\": \"{\\\"plugin-path\\\":\\\"Comply0.Kansa.Extensions.ScubaGear.dll\\\",\\\"script-path\\\":\\\"Resources\\\\\\\\Invoke-ScubaGear.ps1\\\",\\\"app-id\\\":\\\"c4d39d69-aea7-4acc-af2c-45c502d3a308\\\",\\\"opa-path\\\":\\\"/usr/local/bin\\\"}\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"status\": {\n \"state\": \"operational\"\n }\n }\n ],\n \"assessment-platforms\": [\n {\n \"uuid\": \"15000cf8-2f2a-4417-8b93-60a1f209ee95\",\n \"title\": \"Comply0 cATO Agent\",\n \"uses-components\": [\n {\n \"component-uuid\": \"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-assets"},"data/snippets/ez-cisa-context-activity.json":{"approach":"assessment-first","content":"[\n {\n \"name\": \"context\",\n \"value\": \"{\\\"ProductNames\\\":\\\"aad\\\",\\\"component-uuid\\\":\\\"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\\\"}\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n },\n {\n \"name\": \"check\",\n \"value\": \"MS.AAD\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n]","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA activity context prop"},"data/snippets/ez-cisa-context-step.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"4b7f6f09-84da-4c03-ba7b-d02ff52d5b69\",\n \"title\": \"MS.AAD.3.7v1\",\n \"description\": \"Managed devices SHOULD be required for authentication.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"EXAMINE\"\n },\n {\n \"name\": \"criticality\",\n \"ns\": \"http://cisa.gov/ns/oscal\",\n \"value\": \"SHOULD\"\n },\n {\n \"name\": \"context\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"{\\\"SkipHybridJoinCheck\\\":false}\"\n },\n {\n \"name\": \"check\",\n \"value\": \"MS.AAD.3.7\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://github.com/cisagov/ScubaGear/tree/main/PowerShell/ScubaGear/baselines/aad.md#msaad37v1\",\n \"rel\": \"canonical\"\n },\n {\n \"href\": \"https://attack.mitre.org/techniques/T1078/\",\n \"text\": \"T1078: Valid Accounts\",\n \"rel\": \"mitre\"\n },\n {\n \"href\": \"https://attack.mitre.org/techniques/T1078/004/\",\n \"text\": \"T1078.004: Cloud Accounts\",\n \"rel\": \"mitre\"\n }\n ],\n \"reviewed-controls\": {\n \"control-selections\": [\n {\n \"include-controls\": [\n {\n \"control-id\": \"ac-20\",\n \"statement-ids\": [\n \"ac-20_smt.b\"\n ]\n },\n {\n \"control-id\": \"ia-3\",\n \"statement-ids\": [\n \"ia-3_smt\"\n ]\n }\n ]\n }\n ]\n },\n \"remarks\": \"The security risk of an adversary authenticating to the tenant from their own device is reduced by requiring a managed device to authenticate. Managed devices are under the provisioning and control of the agency. [OMB-22-09](https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf) states, \\\"When authorizing users to access resources, agencies must consider at least one device-level signal [truncated]\"\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","section":null,"sha256_of_source_file":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653","slot":"3","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-maester.json","title":"CISA step context prop"},"data/snippets/ez-cisa-import-ssp.json":{"approach":"assessment-first","content":"{\n \"href\": \"#75e00698-e43b-4d6f-be7f-d1227a3a3e39\",\n \"remarks\": \"Link the SAP to the SSP.\"\n}","extracted_at":"2026-08-22T18:44:16+00:00","id":"ez-cisa-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"import-ssp, resolving to a resource in the same document"},"data/snippets/ez-cisa-no-ssp-resource.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"f56da5c6-da67-4c40-acc8-6814bf7aa374\",\n \"title\": \"System's Full Name\",\n \"description\": \"# USE THIS RESOURCE WHEN NO OSCAL-BASED SSP EXISTS\\n\\nBriefly describe the system. This will appear in the SAR.\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"no-oscal-ssp\"\n },\n {\n \"name\": \"import-profile\",\n \"ns\": \"https://fedramp.gov/ns/oscal\",\n \"value\": \"#890170c3-d4fa-4d25-ab96-8e4bf7cc237c\"\n },\n {\n \"name\": \"purpose\",\n \"ns\": \"https://fedramp.gov/ns/oscal\",\n \"value\": \"Briefly state the system's purpose. This will appear in the SAR.\"\n }\n ],\n \"remarks\": \"Only include this resource if no OSCAL-based SSP is available.\"\n}","extracted_at":"2026-08-22T18:46:12+00:00","id":"ez-cisa-no-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/0","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The alternative resource, where no OSCAL system security plan exists"},"data/snippets/ez-cisa-ssp-resource.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"75e00698-e43b-4d6f-be7f-d1227a3a3e39\",\n \"title\": \"Kalvico Enterprise ICAM SSP\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"oscal-ssp\"\n }\n ],\n \"rlinks\": [\n {\n \"href\": \"system-security-plan.json\",\n \"media-type\": \"application/oscal.catalog+json\"\n }\n ],\n \"remarks\": \"Use this to point to an OSCAL-based SSP.\"\n}","extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/1","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The resource a resolved import-ssp lands on"},"data/snippets/ez-cisa-step-reviewed.json":{"approach":"assessment-first","content":"{\n \"control-selections\": [\n {\n \"include-controls\": [\n {\n \"control-id\": \"cm-7\",\n \"statement-ids\": [\n \"cm-7_smt\"\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-step-reviewed","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0/reviewed-controls","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"2","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA step reviewed-controls"},"data/snippets/ez-cisa-task-timing.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"c2f71c67-3d4c-43ba-ad9d-949d0396413f\",\n \"type\": \"action\",\n \"title\": \"Automate assessment of ScubaGear tests using Comply0 Platform Assessment Agent\",\n \"description\": \"Execute CISA SCuBA assessment tests using the Comply0 cATO Agent with ScubaGear plugin.\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"value\": \"15000cf8-2f2a-4417-8b93-60a1f209ee95\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"timing\": {\n \"at-frequency\": {\n \"period\": 24,\n \"unit\": \"hours\"\n }\n },\n \"associated-activities\": [\n {\n \"activity-uuid\": \"760fe3fc-45af-4c62-b095-265a56a1dedf\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"4e391cf6-5549-46f3-b3d7-aad12cd5a226\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"2c69fb5c-056f-4788-be36-723b939a4766\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"04319877-e72d-4967-b968-4852e6738113\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"53852402-8cd6-4e1c-a559-f31bb004a66e\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"c98b996e-8dae-40ef-8b40-100ffbe9e5e3\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"5f62a033-3847-43ec-bafd-3dc1a7621029\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA task, with timing"},"data/snippets/ez-stig-activity-v259312.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"e69fb43b-9565-58f6-badc-e31834e575f6\",\n \"title\": \"V-259312: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"stig-group-id\",\n \"value\": \"V-259312\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-rule-id\",\n \"value\": \"SV-259312r961818_rule\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"category\",\n \"value\": \"CAT II\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"srg\",\n \"value\": \"SRG-APP-000501-DB-000336\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"sequence\",\n \"value\": \"101\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-000172\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"au-12\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"documentable\",\n \"value\": \"false\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"93fcfc80-5643-5c15-835d-aaa4d000daeb\",\n \"title\": \"Check: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"## Check\\n\\nExecute the following SQL the \\\"enterprisedb\\\" operating system user:\\n\\n```bash\\n> psql edb -c \\\"SHOW edb_audit_statement\\\"\\n```\\n\\nIf the result is not \\\"all\\\" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"check\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"assessment-method\",\n \"value\": \"TEST\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-000172\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"au-12\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n },\n {\n \"uuid\": \"e58bf90b-06dc-537f-81a9-68e61e87b7a7\",\n \"title\": \"Remediate: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"## Remediate\\n\\nExecute the following SQL as the \\\"enterprisedb\\\" operating system user:\\n\\n```bash\\n> psql edb -c \\\"ALTER SYSTEM SET edb_audit_statement = 'all'\\\"\\n> psql edb -c \\\"SELECT pg_reload_conf()\\\"\\n```\\n\\nor\\n\\nUpdate the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"remediate\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n }\n ],\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"au-12\"\n }\n ]\n }\n ]\n },\n \"remarks\": \"Source SRG: SRG-APP-000501-DB-000336\\nDPMS Target identifier: 5575\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-activity-v259312","language":"json","pointer":"/assessment-plan/local-definitions/activities/100","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG activity V-259312"},"data/snippets/ez-stig-import-ssp.json":{"approach":"assessment-first","content":"{\n \"href\": \"PLACEHOLDER\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"meta","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG import-ssp, an unresolved placeholder"},"data/snippets/ez-stig-related-controls.json":{"approach":"assessment-first","content":"{\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"au-12\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-related-controls","language":"json","pointer":"/assessment-plan/local-definitions/activities/100/related-controls","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"2","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG related-controls, the control tie"},"data/snippets/ez-stig-sc28-v270747.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"c8eaf2b1-c63f-5693-a1a5-e4e66a760c41\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system.\\n\\nThis requirement addresses protection of user-generated data, as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.\\n\\nSatisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS [truncated]\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"stig-group-id\",\n \"value\": \"V-270747\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-rule-id\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"category\",\n \"value\": \"CAT II\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"srg\",\n \"value\": \"SRG-OS-000185-GPOS-00079\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"sequence\",\n \"value\": \"102\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-001199\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002475\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002476\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-004910\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.1\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.3\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"documentable\",\n \"value\": \"false\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"0423503f-e675-545e-8a9b-740c1b5f51ce\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"## Check\\n\\nNote: If there is a documented and approved mission requirement for data-at-rest to not be encrypted, this requirement is not applicable.\\n\\nVerify Ubuntu 24.04 LTS prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption.\\n\\nDetermine the partition layout for the system with the following command:\\n\\n```bash\\n$ sudo fdisk -l\\n(..)\\nDisk /dev/vda: 15 GiB, 16106127360 bytes, 31457280 sectors\\nUnits: sectors of 1 * 512 = 512 bytes\\nSector size (logical/physical): 512 bytes / 512 bytes\\nI/O size (minimum/optimal): 512 bytes / 512 byte [truncated]\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"check\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"assessment-method\",\n \"value\": \"TEST\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-001199\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002475\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002476\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-004910\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.1\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.3\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n },\n {\n \"uuid\": \"0820d37b-cdcb-5e32-a660-e1111ad328dc\",\n \"title\": \"Remediate: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"## Remediate\\n\\nTo encrypt an entire partition, dedicate a partition for encryption in the partition layout.\\n\\nNote: Encrypting a partition in an already-installed system is more difficult because it will need to be resized and existing partitions changed.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"remediate\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n }\n ],\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n },\n {\n \"control-id\": \"sc-28.1\"\n },\n {\n \"control-id\": \"sc-28.3\"\n }\n ]\n }\n ]\n },\n \"remarks\": \"Source SRG: SRG-OS-000185-GPOS-00079\\nDPMS Target identifier: 5673\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-sc28-v270747","language":"json","pointer":"/assessment-plan/local-definitions/activities/101","section":null,"sha256_of_source_file":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","title":"STIG activity V-270747, SC-28"},"data/snippets/ez-subjects-explicit.json":{"approach":"assessment-first","content":"[\n {\n \"type\": \"inventory-item\",\n \"description\": \"The M365 tenant instance being assessed. Assume it's defined in SSP.\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n]","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"4","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-subjects, one inventory item"},"data/snippets/ez-subjects-includeall.json":{"approach":"assessment-first","content":"[\n {\n \"type\": \"component\",\n \"description\": \"Target system being assessed against the STIG.\",\n \"include-all\": {}\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-subjects-includeall","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"4","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG assessment-subjects, include-all"},"data/snippets/ibm-ap-activity.json":{"approach":"component-first","content":"[\n {\n \"activities\": [\n {\n \"uuid\": \"a1b2c3d4-1111-4aaa-8888-111111111111\",\n \"description\": \"Execute Ansible checks to validate the controls.\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"check-ids\": [\n \"check-1\",\n \"check-2\"\n ]\n },\n {\n \"uuid\": \"b2c3d4e5-2222-4bbb-9999-222222222222\",\n \"description\": \"Execute OSCAP checks to validate the controls.\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984e8\",\n \"check-ids\": [\n \"check-1\",\n \"check-3\"\n ]\n }\n ]\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-activity","language":"json","pointer":"/assessment-plan/local-defintions","section":null,"sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"5","source":"IBM/assessment-plan.json","title":"AP activity, binding check-ids"},"data/snippets/ibm-ap-task-subjects.json":{"approach":"component-first","content":"{\n \"uuid\": \"b3504d22-0e75-4dd7-9247-618661beba4e\",\n \"type\": \"action\",\n \"title\": \"Execute Ansible Checks\",\n \"description\": \"The assessor will execute the Ansible checks defined in the validation component using the Ansible assessment platform to collect evidence for the assessment.\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"value\": \"d8c9a1e5-1c3b-4f0b-9c8e-2a1b2c3d4e5f\"\n }\n ],\n \"timing\": {\n \"at-frequency\": {\n \"period\": 1,\n \"unit\": \"days\"\n }\n },\n \"associated-activities\": [\n {\n \"activity-uuid\": \"a1b2c3d4-1111-4aaa-8888-111111111111\",\n \"subjects\": [\n {\n \"subject-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984fe\"\n }\n ]\n },\n {\n \"activity-uuid\": \"b2c3d4e5-2222-4bbb-9999-222222222222\",\n \"subjects\": [\n {\n \"subject-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984ff\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-task-subjects","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"4","source":"IBM/assessment-plan.json","title":"AP task, subjects and platform"},"data/snippets/ibm-ar-observation.json":{"approach":"component-first","content":"{\n \"uuid\": \"6c0a18ff-36b4-45b2-9e8b-6e3011bee6b1\",\n \"description\": \"check-result\",\n \"assessment-check-id\": \"check-1\",\n \"assessment-asset/component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984e8\",\n \"result\": \"pass\",\n \"props\": [\n {\n \"name\": \"idref\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"xccdf_org.ssgproject.content_rule_package_prelink_removed\"\n },\n {\n \"name\": \"result\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"pass\"\n },\n {\n \"name\": \"time\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"2025-02-26T03:47:26-05:00\"\n },\n {\n \"name\": \"severity\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"medium\"\n }\n ],\n \"methods\": [\n \"TEST-AUTOMATED\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"c8ca2d73-c917-4901-9098-71b2c601f471\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2025-02-26T12:45:58+00:00\"\n}","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","section":null,"sha256_of_source_file":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806","slot":"6b","source":"IBM/assessment-result.json","title":"AR observation, carrying a result"},"data/snippets/ibm-cos-component.json":{"approach":"component-first","content":"{\n \"uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\",\n \"type\": \"service\",\n \"title\": \"COS\",\n \"description\": \"COS\",\n \"rules\": [\n {\n \"id\": \"cos_access_endpoint_type\",\n \"description\": \"Ensure Cloud Object Storage is accessible only by using {param: endpoint_access} endpoints\",\n \"params\": [\n {\n \"id\": \"endpoint_access\",\n \"label\": \"Endpoint Access type\",\n \"select\": {\n \"how-many\": \"one\",\n \"choice\": [\n \"public\",\n \"private\",\n \"direct\"\n ]\n }\n }\n ]\n },\n {\n \"id\": \"cos_encryption_hyperprotect_key_configured\",\n \"description\": \"Ensure Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"08159454-994c-49ed-8f78-f2293b1274a2\",\n \"source\": \"trestle://profiles/ACME_official/profile.json\",\n \"description\": \"ACME Official Profile\",\n \"set-parameters\": [\n {\n \"param-id\": \"endpoint_access\",\n \"values\": [\n \"private\"\n ]\n }\n ],\n \"implemented-requirements\": [\n {\n \"uuid\": \"c6ccfcbc-4553-40e6-b4e8-eadbff8d4756\",\n \"control-id\": \"ac-4\",\n \"description\": \"This control is implmeneted by ensuring the COS is only available on private endpoints.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"cos_access_endpoint_type\"\n }\n ]\n },\n {\n \"uuid\": \"455563ca-c454-41d5-aa3b-f57843d95aab\",\n \"control-id\": \"sc-28\",\n \"description\": \"Ensure that data is encrypted and the key is managed by the customer.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"cos_encryption_hyperprotect_key_configured\"\n }\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-cos-component","language":"json","pointer":"/component-definition/components/0","section":null,"sha256_of_source_file":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a","slot":"1","source":"IBM/cos-component-definition.json","title":"COS component, carrying rules"},"data/snippets/ibm-statement-rules.json":{"approach":"component-first","content":"{\n \"uuid\": \"c6ccfcbc-4553-40e6-b4e8-eadbff8d4756\",\n \"control-id\": \"ia-5.1\",\n \"description\": \"\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"08cc185d-27d8-4412-9cb4-25ebf1397a39\",\n \"description\": \"\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"idservice_password_min_length\"\n },\n {\n \"rule-id\": \"idservice_strong_pass_enabled\"\n }\n ]\n },\n {\n \"statement-id\": \"ia-5.1_smt.e\",\n \"uuid\": \"89f1f3be-d915-4134-94ab-577cba3f3c9a\",\n \"description\": \"\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"idservice_password_not_reuse_min_count\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-statement-rules","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/0","section":null,"sha256_of_source_file":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf","slot":"2","source":"IBM/idservice-component-definition.json","title":"implementing-rules on ia-5.1"},"data/snippets/ibm-validation-ansible.json":{"approach":"component-first","content":"{\n \"component-definition\": {\n \"uuid\": \"bbdf7ee6-3e0a-4065-8ecf-50f4129de473\",\n \"metadata\": {\n \"title\": \"Demo validation component definition\",\n \"last-modified\": \"2026-05-15T14:29:37+00:00\",\n \"version\": \"1.0\",\n \"oscal-version\": \"1.2.1\"\n },\n \"components\": [\n {\n \"uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"type\": \"validation\",\n \"title\": \"ANSIBLE\",\n \"description\": \"ANSIBLE\",\n \"checks\": [\n {\n \"id\": \"check-1\",\n \"description\": \"Check Cloud Object Storage is accessible only by using private endpoints\",\n \"rule-id\": \"cos_access_endpoint_type\",\n \"target-component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\"\n },\n {\n \"id\": \"check-2\",\n \"description\": \"Check Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)\",\n \"rule-id\": \"cos_encryption_hyperprotect_key_configured\",\n \"target-component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\"\n }\n ]\n }\n ]\n }\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-validation-ansible","language":"json","pointer":"$","section":null,"sha256_of_source_file":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","slot":"3","source":"IBM/ansible-validation-component-definition.json","title":"Ansible validation component, and its checks"},"data/source-files.json":{"excluded":[{"path":"disa/U_Readme_SRG_and_STIG.pdf","why":"About the STIG and SRG packages as a set rather than about any one guide, so it has no row in a table of one row per guide."},{"path":"oscal","why":"The OSCAL representations of this guidance are published separately. This table lists the documents read as input, not what was written from them."}],"files":[{"bytes":1032133,"guidance":"cis-postgresql-18","href":"sources/cis/CIS_PostgreSQL_18_Benchmark_v1.0.0.json","kind":"source","media":"json","media_label":"JSON document","mime":"application/json","name":"CIS_PostgreSQL_18_Benchmark_v1.0.0.json","publisher":"cis","sha256":"b72eda73c5bef60e2971c93261bc226594cfb8d8aa1be92deb6b2e121bf05379","size":"1.0 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":1506309,"guidance":"cis-postgresql-18","href":"sources/cis/CIS_PostgreSQL_18_Benchmark_v1.0.0.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"CIS_PostgreSQL_18_Benchmark_v1.0.0.pdf","publisher":"cis","sha256":"eae098af712ef333be2ebb146e72d8cdcba9f740f3a99e15de8363055f49f1b9","size":"1.5 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":6823924,"guidance":"cis-ubuntu-24-04","href":"sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","kind":"source","media":"json","media_label":"JSON document","mime":"application/json","name":"CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","publisher":"cis","sha256":"1a90fccb4442decd119382233ff8986caaaeede83dcf3c5ab22a87c747ab0c81","size":"6.8 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":10372494,"guidance":"cis-ubuntu-24-04","href":"sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.pdf","publisher":"cis","sha256":"8ebe23d21c23e383c81620ad04655e3b1d8fdf0b6eb9ddfdb7a97d0a5b5e7ef1","size":"10.4 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":640043,"guidance":"disa-ubuntu-22-04","href":"sources/disa/U_CAN_Ubuntu_22-04_LTS_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CAN_Ubuntu_22-04_LTS_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"73c26b6592dfc02f7f0eb456e0f89143ea1e2d8af7ebc61bd8bfae01f5a4c9d8","size":"640 kB","terms":"Public domain. A work of the United States Government."},{"bytes":658230,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml","publisher":"disa","sha256":"4c527cf0ed912947bb0c51be15f1a6bbc5a4bf05469ae083d94a01471edea77c","size":"658 kB","terms":"Public domain. A work of the United States Government."},{"bytes":934796,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1_Release_Memo.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_STIG_V1_Release_Memo.pdf","publisher":"disa","sha256":"9c3292baa367f97d0dc8c8a235a77dd49acfe53598d667902ab3e1e7d3d3d9a0","size":"935 kB","terms":"Public domain. A work of the United States Government."},{"bytes":425770,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_V1R5_Overview.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_V1R5_Overview.pdf","publisher":"disa","sha256":"7b4e8bc528e6e23c9bac33b760793d86e6d4954ff724f9db1e108ef071a22c8e","size":"426 kB","terms":"Public domain. A work of the United States Government."},{"bytes":301891,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_V1R5_Revision_History.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_V1R5_Revision_History.pdf","publisher":"disa","sha256":"3f00fb641e059376fb8b8d4404e3e2abf0a6a95950568740172086c441457a56","size":"302 kB","terms":"Public domain. A work of the United States Government."},{"bytes":456124,"guidance":"disa-postgres-16","href":"sources/disa/U_CD_Postgres_16_STIG_V1R2_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CD_Postgres_16_STIG_V1R2_Manual-xccdf.xml","publisher":"disa","sha256":"d468632da49f29b1616347dc7d79f429ff72ded2685a2ffb55b416d76192ce32","size":"456 kB","terms":"Public domain. A work of the United States Government."},{"bytes":432719,"guidance":"disa-epas","href":"sources/disa/U_EPAS_STIG_V2R1_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_EPAS_STIG_V2R1_Manual-xccdf.xml","publisher":"disa","sha256":"c9a9fb2f652495433a3639f740ef08d856c722be5d8bfdb729c87f843f3767ec","size":"433 kB","terms":"Public domain. A work of the United States Government."},{"bytes":936441,"guidance":"disa-windows-2019","href":"sources/disa/U_MS_Windows_Server_2019_STIG_V3R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2019_STIG_V3R8_Manual-xccdf.xml","publisher":"disa","sha256":"f483e86fdaf1caf0ad904b99ae117667fb61e48e0f62fbbcbd4ac30facef0e36","size":"936 kB","terms":"Public domain. A work of the United States Government."},{"bytes":906114,"guidance":"disa-windows-2022","href":"sources/disa/U_MS_Windows_Server_2022_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2022_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"991ad360c2ca40c5ab743b22b045ac9a98134a2c7360983ae32a1dac62de65de","size":"906 kB","terms":"Public domain. A work of the United States Government."},{"bytes":913750,"guidance":"disa-windows-2025","href":"sources/disa/U_MS_Windows_Server_2025_STIG_V1R1_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2025_STIG_V1R1_Manual-xccdf.xml","publisher":"disa","sha256":"5ae22836beba53091fa6269eaa974e54c226f3e2113cc9a3ec0183a8e16f51ee","size":"914 kB","terms":"Public domain. A work of the United States Government."},{"bytes":1267893,"guidance":"disa-rhel-8","href":"sources/disa/U_RHEL_8_STIG_V2R7_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_RHEL_8_STIG_V2R7_Manual-xccdf.xml","publisher":"disa","sha256":"9c5c57f34c78e3c70d5bc9755169b99f9e6965509b8e06f277c82982bccc8411","size":"1.3 MB","terms":"Public domain. A work of the United States Government."},{"bytes":1397262,"guidance":"disa-rhel-9","href":"sources/disa/U_RHEL_9_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_RHEL_9_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"bcb1c86161034ced8accca81f15efe40d4e4cfdce003b6b2b456cb49fcd094e3","size":"1.4 MB","terms":"Public domain. A work of the United States Government."}],"media_types":{"json":{"label":"JSON document","mime":"application/json"},"pdf":{"label":"PDF document","mime":"application/pdf"},"xml":{"label":"XML document","mime":"application/xml"}},"not_copied":[{"publisher":"cisa","what":"The SCuBA secure configuration baselines themselves","where":null,"where_label":null,"why":"The baselines are published by CISA and no copy of them is held here. What was read for this analysis was the baseline content as converted, and those conversions are published separately."},{"publisher":"aws","what":"The Security Hub controls, as published","where":"https://github.com/awslabs/oscal-content-for-aws-services","where_label":"oscal-content-for-aws-services","why":"This publisher ships its guidance as OSCAL already, so there is no separate source document to hold. The published content is linked rather than copied, so there is one copy to keep current."}],"not_shipped":[{"path":"cis","why":"Held locally, not redistributed. Download the Benchmarks from cisecurity.org into sources/cis/ under the filenames recorded here to rebuild anything that reads them."}],"note":"Every file under sources/, with its media type and size read from disk, and the benchmark row it belongs to. Built by tools/sources_files.py; verified by tools/verify.py --sources, which fails if a link points at a missing file, a file sits in the folder unlinked, or a file names a row that does not exist.","totals":{"bytes":29005893,"files":16,"size":"29.0 MB"}},"data/sources.json":{"columns":["Publisher","Guidance","Source form held"],"note":"The hardening guidance read as input to this analysis, one row per benchmark or guide rather than one per publisher, because the unit a reader recognises is the benchmark. Each row carries the documents read for it: a file icon downloads one file, a globe opens the publisher's page. What was written from this guidance, in OSCAL, is published separately and is not a column here; it is kept under 'publishers' so tools/verify.py --sources can still recompute it against the corpora.","publishers":{"aws":{"derivation":"AWS/oscal-content-for-aws-services-main: catalogs/*.oscal.json and component-definitions/*.oscal.json","full_name":"Amazon Web Services","name":"AWS","oscal_counts":{"catalogs":1,"component_definitions":230,"controls":452,"groups":77},"oscal_form":"one catalog of 452 controls across 77 groups, and 230 component definitions","source_counts":{}},"cis":{"derivation":"assessment-plan documents under Easy Dynamics/Center for Internet Security; source files under Hardening Guides/Center for Internet Security","full_name":"Center for Internet Security","name":"CIS","oscal_counts":{"assessment_plans":2},"oscal_form":"two assessment plans","source_counts":{"pdf":2,"xccdf_json":2}},"cisa":{"derivation":"assessment-plan documents under Easy Dynamics/CISA BOD 25-01; no publisher source material is present","full_name":"Cybersecurity and Infrastructure Security Agency","name":"CISA","oscal_counts":{"assessment_plans":4,"assessment_results":1},"oscal_form":"four assessment plans and one assessment result","source_counts":{}},"disa":{"derivation":"assessment-plan documents under Easy Dynamics/DISA; *-xccdf.xml under Hardening Guides/DISA","full_name":"Defense Information Systems Agency","name":"DISA","oscal_counts":{"assessment_plans":9},"oscal_form":"nine assessment plans","source_counts":{"xccdf_xml":9}}},"rows":[{"guidance":"Ubuntu Linux 24.04 LTS Benchmark","key":"cis-ubuntu-24-04","publisher":"cis","source_form":"XCCDF-derived JSON, and PDF","version":"v1.0.0"},{"guidance":"PostgreSQL 18 Benchmark","key":"cis-postgresql-18","publisher":"cis","source_form":"XCCDF-derived JSON, and PDF","version":"v1.0.0"},{"guidance":"Ubuntu 22.04 LTS STIG","key":"disa-ubuntu-22-04","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Ubuntu 24.04 LTS STIG","key":"disa-ubuntu-24-04","publisher":"disa","source_form":"XCCDF XML, and three release notes","version":"V1R5"},{"guidance":"Red Hat Enterprise Linux 8 STIG","key":"disa-rhel-8","publisher":"disa","source_form":"XCCDF XML","version":"V2R7"},{"guidance":"Red Hat Enterprise Linux 9 STIG","key":"disa-rhel-9","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Windows Server 2019 STIG","key":"disa-windows-2019","publisher":"disa","source_form":"XCCDF XML","version":"V3R8"},{"guidance":"Windows Server 2022 STIG","key":"disa-windows-2022","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Windows Server 2025 STIG","key":"disa-windows-2025","publisher":"disa","source_form":"XCCDF XML","version":"V1R1"},{"guidance":"PostgreSQL 16 STIG","key":"disa-postgres-16","publisher":"disa","source_form":"XCCDF XML","version":"V1R2"},{"guidance":"EDB Postgres Advanced Server STIG","key":"disa-epas","publisher":"disa","source_form":"XCCDF XML","version":"V2R1"},{"guidance":"BOD 25-01, the SCuBA baselines","key":"cisa-bod-25-01","links":[{"href":"https://www.cisa.gov/resources-tools/services/bod-25-01-implementing-secure-practices-cloud-services-required-configurations","kind":"web","label":"BOD 25-01, on the publisher's site"}],"publisher":"cisa","source_form":"None held here","version":null},{"guidance":"Security Hub security best-practice controls","key":"aws-security-hub","links":[{"href":"https://aws.github.io/aws-security-services-best-practices/guides/security-hub/","kind":"web","label":"Security Hub best practices, on the publisher's site"},{"href":"https://github.com/awslabs/oscal-content-for-aws-services","kind":"web","label":"The same controls as OSCAL, in the publisher's repository"}],"publisher":"aws","source_form":"Published as OSCAL, and linked","version":null}],"summary":"Hardening guidance used as input","summary_sub":"Two CIS Benchmarks, nine DISA STIGs, CISA BOD 25-01 and the AWS Security Hub controls, with the documents read for each."},"data/stakeholders.json":{"approaches":{"assessment-first":{"auditor":{"flows":[{"from":[{"model":"assessment-plan"}],"makes":"the observations","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor's run produces assessment results, not implementation claims. The workflow does not update the system security plan."},"benchmark":{"note":"The guidance provider writes activities and steps. The policy engine provider supplies executable checks.","writes":[{"model":"assessment-plan"}]},"engine":{"note":"The policy engine provider adds checks to the assessment plan. The plan identifies the engine in assessment-assets.","writes":[{"model":"assessment-plan"}]},"mapper":{"note":"The mapping provider edits the assessment plan, naming the framework controls covered by the activity.","writes":[{"model":"assessment-plan"}]},"owner":{"note":"The system owner supplies the profile and system security plan. The assessor's workflow does not depend on the owner's automation.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"note":"The technology provider writes activities and steps. The policy engine provider supplies executable checks.","writes":[{"model":"assessment-plan"}]}},"catalog-first":{"auditor":{"flows":[{"from":[{"kind":"software","model":"component-definition"}],"makes":"the findings","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor runs the checks independently. The resulting finding targets the system owner's implementation statement."},"benchmark":{"writes":[{"model":"catalog"}]},"engine":{"note":"The provider publishes checks as components of type software, referencing the guidance authors' catalog. System owners and auditors run the checks.","writes":[{"kind":"software","model":"component-definition"}]},"mapper":{"note":"The mapping provider writes a separate framework mapping. The published corpus contains no mapping collection for hardening guidance.","writes":[{"model":"mapping-collection"}]},"owner":{"flows":[{"from":[{"kind":"software","model":"component-definition"}],"makes":"the control-implementation responses","runtime":true,"to":[{"model":"system-security-plan"}]}],"note":"The system owner selects requirements and merges catalogs through a profile imported by the system security plan.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"writes":[{"model":"catalog"}]}},"component-first":{"auditor":{"flows":[{"from":[{"model":"assessment-plan"}],"makes":"the observations","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor runs checks through an assessment plan, allowing the result to identify a host rather than a component."},"benchmark":{"writes":[{"kind":"software","model":"component-definition"}]},"engine":{"note":"The provider publishes checks in a component of type validation. System owners and auditors run the checks.","writes":[{"kind":"validation","model":"component-definition"}]},"mapper":{"note":"The mapping provider edits a component definition. Whether the rules or the checks carry the framework mapping remains open.","writes":[{"kind":"software or validation","model":"component-definition"}]},"owner":{"flows":[{"from":[{"kind":"validation","model":"component-definition"}],"makes":"the control-implementation responses","runtime":true,"to":[{"model":"system-security-plan"}]}],"writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"writes":[{"kind":"software","model":"component-definition"}]}}},"groups":[{"key":"guidance","label":"Hardening guidance authors","note":"Benchmark publishers and technology providers author guidance in the same OSCAL model for each approach."},{"key":"automation","label":"Automation providers and operators","note":"Providers build policy engines. System owners and auditors run checks to produce implementation responses or assessment results."}],"intro":"Seven parties publish, implement or assess hardening guidance. The table maps each party to OSCAL models and groups guidance authors separately from automation providers and operators.","note":"The mapping identifies the OSCAL models used by seven parties from guidance publication through audit. Component types distinguish guidance from checks where both use component definitions. Two groups identify guidance authors and automation providers and operators. Policy engine providers build tools; system owners and auditors execute the flows shown. Mapping providers are separate because guidance authors do not always publish framework mappings: STIGs carry CCIs, DISA's CCI list names the 800-53 controls, and third parties publish mappings through NIST's OLIR programme.","parties":[{"key":"regulatory","name":"Regulatory control providers","who":"NIST and other bodies publishing regulatory controls, such as SP 800-53"},{"key":"mapper","name":"Mapping providers","who":"Organisations linking guidance to frameworks through DISA's CCI list, NIST's OLIR programme or the Secure Controls Framework"},{"group":"guidance","key":"benchmark","name":"Technical hardening guidance providers","who":"CIS, DISA and other benchmark publishers"},{"group":"guidance","key":"software","name":"Technology providers","who":"Vendors publishing configuration guidance for hardware, software and services, independently or with benchmark publishers such as CIS"},{"group":"automation","key":"engine","name":"Policy engine providers","who":"Providers of assessment and checking tools such as OPA, Kyverno, ScubaGear and OpenSCAP"},{"group":"automation","key":"owner","name":"System owners","who":"Organisations implementing and documenting controls on a system"},{"group":"automation","key":"auditor","name":"Independent auditors","who":"Assessors running checks and reviewing results independently of system owners"}],"runtime":"A policy engine reads OSCAL, executes checks and writes OSCAL. Providers publish the checks; each flow identifies the party executing the checks."},"data/tradeoffs.json":{"approaches":{"assessment-first":{"cons":[{"body":"The activity title contains the required value, so changing the value requires editing the plan rather than resolving a profile.","title":"Required values lack resolvable parameters"},{"body":"The model provides activities and steps, so guidance nested four levels deep must be represented within those two structural tiers.","title":"Guide hierarchy is limited to two tiers"},{"body":"The published result references a plan absent from the corpus and assigns an observation a subject type not defined by the model.","title":"Published references and types need correction"}],"intro":"Publishing technical hardening guidance as an assessment plan has these strengths and risks.","pros":[{"body":"The assessment plan references implementation claims without adding claims, so adding or retiring a guide does not change the system security plan.","title":"Guidance stays outside the plan of record"},{"body":"A separate assessment results document imports a plan; the corpus includes findings that target objectives and reference supporting observations.","title":"Assessment results reference an assessment plan"},{"body":"An assessment subject can be an inventory item, allowing separate findings for two hosts running one operating system with different configurations.","title":"Subjects can identify individual hosts"},{"body":"Tasks carry schedules and identify execution platforms, placing the timing and runtime context for checks in the assessment plan.","title":"The plan records execution context"}]},"catalog-first":{"cons":[{"body":"The system security plan must address benchmark requirements alongside regulatory controls; whether each additional catalog requires a separate plan remains unsettled.","title":"Benchmark catalogs add maintenance work"},{"body":"Multiple frameworks and benchmarks require catalogs, profiles and mappings to be maintained together, increasing tool integration work and profile resolution complexity.","title":"Combined baselines complicate profile resolution"},{"body":"A by-component response identifies a component, not an instance, so one exception among a hundred hosts sharing that component cannot be distinguished.","title":"Responses do not identify individual instances"}],"intro":"Publishing technical hardening guidance as a catalog has these strengths and risks.","pros":[{"body":"Technical requirements use catalog controls and follow the same references through the remaining OSCAL models as regulatory controls.","title":"Technical and regulatory requirements use one model"},{"body":"A profile selects the hardening requirements an organisation adopts and sets organisationally defined parameters without changing the source catalog.","title":"Rules can be tailored"},{"body":"Controls, parts and nested groups represent checks, remediation and explanatory prose, including the structure of a thousand-page guide.","title":"Catalog structures represent guide content"},{"body":"A separate mapping-collection links guidance to a framework, allowing a third party to publish the mapping without owning either catalog.","title":"Third parties can publish framework mappings"}]},"component-first":{"cons":[{"body":"The proposal changes component definitions, system security plans, assessment plans and assessment results; existing schema support does not cover the proposed assemblies.","title":"Four models require schema changes"},{"body":"Rules describing the required component configuration enter the system security plan, which documents the system's implemented controls and current configuration.","title":"Desired state enters the plan of record"},{"body":"Rationale, audit procedure and remediation provide guidance context, but the published rules omit these fields and support remains proposed.","title":"Published rules omit guide context"},{"body":"A by-component response can reference a rule but not an individual instance, so exceptions remain associated with the component.","title":"Responses do not identify individual instances"},{"body":"Inventory items would also need implementing-rules support for a claim to identify a host rather than a component class.","title":"Host-level claims may require inventory support"}],"intro":"Publishing technical hardening rules in a component definition has these strengths and risks.","pros":[{"body":"A component definition describes how a product can meet controls; the proposed rules provide configuration requirements for automation in the same document.","title":"One artifact describes capability and supports automation"},{"body":"The product component holds the rule and a validation component holds the check; a second engine uses a second validation component.","title":"Rules and checks remain separate"},{"body":"The proposed implementing-rules assembly links a control implementation claim to the rule used to satisfy the control.","title":"Implementation claims can reference rules"},{"body":"Existing guidance directs technology providers to describe product capabilities in component definitions, where the proposal would also place hardening rules.","title":"Technology providers can extend component descriptions"}]}},"note":"Strengths and risks for each approach. Entry counts may differ; tools/approach_pages.py enforces prose budgets within and across approaches. Scenario figures remain on the scenario page. BUILD-LOG.md records the basis for each entry. Where present, schema_evidence identifies checked schema fragments and is not rendered."},"data/views.json":{"automation_argument":{"claim":"The automation argument treats applying and verifying hardening guidance as operational work, not just a finer-grained form of regulatory control. Automation coverage varies across the published guides.","claim_not_made":"Hardening guidance is never performed manually. The corpus includes manual procedures and does not support that claim.","evidence":[{"automated":"2271 activities carry method TEST","corpus":"STIG, all 9 files","manual":"none","stat_keys":["stig_method_test"]},{"automated":"576 steps","corpus":"CIS Ubuntu 24.04","manual":"40 steps","stat_keys":["cis_ubuntu_automated","cis_ubuntu_manual"]},{"automated":"0 steps","corpus":"CIS PostgreSQL 18","manual":"144 steps, covering every step; every activity carries method EXAMINE","note":"This guide provides a counterexample to the claim that all hardening procedures are automated.","stat_keys":["cis_postgres_automated","cis_postgres_manual"]}]},"crux":{"note":"Model placement alone does not establish whether guidance is binding. Every approach needs a way to distinguish requirements from optional configurations or assessment procedures."},"note":"Three editorial interpretations of a hardening rule, ordered by OSCAL layer rather than rank. The analysis uses a working definition without selecting an interpretation. Each view links to a stakeholder glossary term.","views":[{"aligned_approach":"catalog-first","definition":"A binding requirement, expressed as a shall. A rule differs from a regulatory control in specificity.","implies_layer":"Control","implies_model":"catalog","key":"requirement","label":"A requirement","stakeholder":"publisher"},{"aligned_approach":"component-first","definition":"A description of possible component configurations. The technology provider describes capabilities; the adopting organisation sets requirements.","implies_layer":"Implementation","implies_model":"component-definition","key":"capability","label":"A capability statement","stakeholder":"implementer"},{"aligned_approach":"assessment-first","definition":"A procedure for applying or verifying hardening guidance. Assessment activities and steps describe the work, with executable checks referenced for automation.","implies_layer":"Assessment","implies_model":"assessment-plan","key":"procedure","label":"An assessor's procedure","stakeholder":"assessor"}],"why_this_matters":"OSCAL has no dedicated core requirement-level field distinguishing shall, should and may. The gap affects every approach; model placement alone cannot establish whether guidance expresses requirements, capabilities or assessment procedures.","working_definition":{"status":"A working definition for comparing the three approaches without selecting an interpretation.","term":"rule","text":"One technical requirement or recommendation, finer-grained than a control, without any claim about whether it is binding."}}}; +window.TFGBundle = {"analysis.json":{"approaches":[{"id":"a","name":"Catalog-first","path":"catalog-first.html"},{"id":"b","name":"Component-first","path":"component-first.html"},{"id":"c","name":"Assessment-first","path":"assessment-first.html"},{"id":"d","name":"Executable-first","path":"executable-first.html"}],"concluded":null,"corpora":{"note":"Repository-defined inputs: 6 committed IBM and 18 committed Easy Dynamics JSON files, checked against data/examples.json fingerprints, plus 231 public AWS JSON files from the pinned archive and verified cache declared in the lock. Prepare explicitly with python tools/source_inputs.py --fetch; python tools/source_inputs.py --check verifies inputs offline. Missing or corrupt inputs fail rather than being skipped or counted as empty.","source_lock":"tools/source-lock.json"},"forum":"OSCAL Foundation Technical Focus Group on Automated Assessments","id":"2026-08-automating-technical-hardening-guidance","makesRecommendation":false,"makesRecommendationNote":"By design, not because the effort is unfinished. The site states 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.","openItems":["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."],"opened":"2026-08-12","question":"Where does technical hardening guidance live in OSCAL, and how does an automated check attach to it?","recommendation":null,"status":"active","summary":"Three organizations have published working OSCAL content that answers the same question three different ways, 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.","supersededBy":null,"supersedes":null,"title":"Automating Technical Hardening Guidance with OSCAL","verification":{"command":"python tools/verify.py --all","note":"Every figure and extract on the site is recomputed from a published file. A skipped check is reported separately and never counted as a pass.","workflow":".github/workflows/verify-2026-08-hardening-guidance.yml"}},"assets/diagrams/710-scenario-assessment.svg":"\n 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, framework mappings are on activities. 0 component-definition files, none, engines are identified in each plan. 1 system-security-plan file, one, addressing 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; each result references 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 system security plan addresses 370 controls; all three guides remain in assessment plans.\n \n \n11 files, across 5 of the seven models\nEach guide becomes an assessment plan with a separate assessment results document. The framework catalog\nand baseline profile remain 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, framework mappings are\non activities\n\nIMPLEMENTATION LAYER\n\ncomponent-definition\n\n0 files\nnone, engines are identified in each plan\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, addressing 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; each result references exactly\none plan\n\nThe system security plan addresses 370 controls; all three guides remain in assessment plans\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 merged selection, named 800-53 High, CIS Ubuntu, DISA PgSQL, CISA SCuBA, Org merged. 3 mapping-collection files, one per guide, linking guidance controls to framework controls, named CIS to 800-53, STIG to 800-53, SCuBA to 800-53. 3 component-definition files, one per technology, containing check components, named Ubuntu checks (software), PgSQL checks (software), M365 checks (software). 1 system-security-plan file, one, addressing 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 system security plan addresses 917 controls: 370 from the framework and 547 from the guides.\n \n \n18 files, across all seven models\nEach guide becomes a catalog with a selection profile and a mapping collection linking guidance to the\nframework. The system security plan addresses 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 merged selection\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, linking\nguidance controls to 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, containing check\ncomponents\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, addressing 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 system security plan addresses 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, framework mappings are inside component definitions. 6 component-definition files, three products with 547 rules, three engines with checks, named Ubuntu (software), PostgreSQL (software), Microsoft 365 (software), Ubuntu checks (validation), PgSQL checks (validation), M365 checks (validation). 1 system-security-plan file, one, addressing 370 controls and containing 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 system security plan addresses 370 controls and contains 547 desired-state rules in components.\n \n \n11 files, across 6 of the seven models\nEach guide becomes rules on the component being configured. Each checking engine becomes a separate\nvalidation component. The framework catalog and baseline profile remain 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, framework mappings are\ninside component definitions\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 with 547 rules, three engines\nwith checks\n\nsystem-security-plan\n\n\nSystem SSP\n1 file\none, addressing 370 controls and containing\n547 rules\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 system security plan addresses 370 controls and contains 547 desired-state rules in\ncomponents\n\n","assets/diagrams/710-scenario-executable.svg":"\n One system, three hardening guides: the file set for the executable first approach\n A count of the OSCAL files this approach needs for the scenario, drawn as one tile per file. 14 files in total, across 6 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. 3 mapping-collection files, one per guide, from the guide's own framework references, named CIS to 800-53, STIG to 800-53, SCuBA to 800-53. 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 \n14 files, across 6 of the seven models\nEach guide is published as a catalog whose controls carry their own executable methods, each component\nreferences a profile selecting from it, and each guide's own framework references become a mapping\ncollection. The plan of record'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\n\nCIS to\n800-53\n\n\nSTIG to\n800-53\n\n\nSCuBA to\n800-53\n3 files\none per guide, from the\nguide's own framework\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-executable.svg":"\n Executable-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/check-carrier.json":{"columns":["Approach","Carries","In which construct","Who owns the executable","Rule and check in one document","What an executor needs beyond the OSCAL"],"consequences":[{"follows":["The OSCAL stays small, and the executable is maintained where it runs.","A reader of the OSCAL alone cannot tell what the check does or judge whether it tests the rule.","The identifier means something to one engine, so a second engine needs a second identifier and a second document."],"kind":"reference"},{"follows":["Everything the publisher wrote travels with the plan, script included, and a person can follow it.","A tool that wants to run the script has to find it in the text and decide for itself what the output means.","Two documents converted from the same guidance can differ in the script, and nothing in the model says which text is the script."],"kind":"description"},{"follows":["The document says enough to run the check and judge the result without asking the publisher.","The publisher, or the profile's author, maintains the script, and the vocabulary of the props has to be agreed and owned.","A script in the document can be hashed and refused when the hash fails, and a linked script without a hash is the gap that shows."],"kind":"executable"}],"figures":{"cis_catalog_methods_linking_script":211,"cis_catalog_methods_with_script":84,"cis_catalog_methods_without_script":93,"cis_plan_audit_steps":308,"cis_plan_rules_with_script":85,"cis_shared_differ":41,"cis_shared_differ_shorter_in_plan":41,"cis_shared_identical":42,"cis_shared_rules_with_script":83,"note":"Recomputed by tools/verify.py --carrier from the CIS assessment plan under examples/assessment-first and the generated catalog under examples/executable-first. A fenced bash block whose first line is a shebang counts as a script.","stig_plan_activities":194,"stig_profile_objectives":194,"text":"The CIS assessment plan has 308 audit steps and 85 of them carry a script; the generated catalog has 84 methods carrying one, and 83 recommendations carry a script in both. In 42 of those the script is the same text. In 41 the plan's copy is shorter, and every one of the 41 lacks angle brackets the benchmark's script has. A further 211 catalog methods link to a script by name, and 93 carry no script at all. The STIG is 194 rules in both corpora, and none of them carries a script in either."},"fusion":{"label":"Both, on one control","snippet_ids":["pf-cis-objective-and-param"],"text":"The generated CIS catalog is the case where the rule and the script sit together. The rule is an assessment objective part on the control, the check is an assessment method part beside it carrying the script, a remediation part follows, and the value the script reads is a parameter of the same control. A finding targets the objective, so nothing in the results model has to know the script exists. The same shape reached by a profile is the fourth approach's second route, and the same shape with a reference in place of the script is what the catalog approach's method part already does."},"intro":["The six questions ask where the rule is written and what check executes it. Put across the four approaches, the answers to the check question are not four constructs holding the same thing. They hold three kinds of thing, and which kind decides who has to hold the rest.","A reference names a check an engine owns. A description carries text a person or a tool follows, and the text may contain a script. A declared executable carries the script, or a link to it, with what an executor needs to run it and judge what comes back. The published files show all three, and the corpus generated for the fourth approach shows the third beside the second on the same guidance."],"kinds":[{"key":"reference","label":"A reference","meaning":"An identifier naming a check the engine owns. The OSCAL says which check; the executable is elsewhere and the identifier means something to one engine."},{"key":"description","label":"A description","meaning":"Text a person or a tool follows. It may contain a script, and nothing in the OSCAL says what runs the script or what its output means."},{"key":"executable","label":"A declared executable","meaning":"The script, or a link to it, with props that say which platform it applies to, what runs it, how the output is judged and what counts as a pass."}],"note":"One axis across the four approaches: what the OSCAL carries about the check. The six questions ask where the rule is written and what check executes it; this file asks what kind of thing the answer to the check question is, because a reference, a description and a declared executable put different work on different parties. Rendered by renderCheckCarrier on the start page. Every row cites extracts by id, every figure is recomputed by tools/verify.py --carrier from the files under examples/, and the pairs put the same rule from two corpora side by side. The site takes no position on which kind is right; the consequences are stated and the reader weighs them.","pairs":[{"key":"cis-1-1-1-1","left":{"approach":"assessment-first","says":"A step. The script is inside the description, after the audit text, and the prop beside it says automated. Nothing says what runs it or what its output means.","snippet_id":"ez-cis-step-props"},"right":{"approach":"executable-first","says":"A method. The same script is the body, and four props say the platform, the language, that the output is matched against a pattern, and the pattern.","snippet_id":"pf-cis-method-1-1-1-1"},"shared_token":"cramfs","title":"One CIS recommendation, in two corpora","what":"Recommendation 1.1.1.1 of the Ubuntu benchmark, the cramfs kernel module, as the assessment-first corpus publishes it and as the generated executable-first corpus carries it. The audit script is the same text in both. What differs is what the OSCAL says about it."},{"key":"stig-v-270747","left":{"approach":"assessment-first","says":"An activity carrying the rule, with a check step holding DISA's text and a prop naming the method TEST.","snippet_id":"ez-stig-sc28-v270747"},"right":{"approach":"executable-first","says":"A method beside an objective the profile added to SC-28, holding the same text. With no script to declare, no language, evaluation or pass condition can be set, and the construct carries a description.","snippet_id":"pf-stig-method-sc-28"},"shared_token":"UBTU-24-600090","title":"One STIG rule, in two corpora","what":"Rule V-270747 of the Ubuntu STIG, data at rest, as an activity in the assessment-first corpus and as a method the generated profile adds to SC-28. DISA publishes the check as text, so neither corpus holds a script for it."}],"rows":[{"approach":"catalog-first","construct":"A prop on a check component naming a Config rule by identifier. The control names the check; the check names the rule the engine runs.","kind":"reference","needs":"The engine, and the meaning of the identifier inside it.","one_document":"No. The rule is in the catalog and the check is in a component definition.","owner":"The cloud provider's rule engine.","snippet_ids":["aws-acm-rsa-check-component"]},{"approach":"component-first","construct":"A check on a validation component, carrying a rule id and a check id in a proposed assembly.","kind":"reference","needs":"A schema that defines the assemblies, and the tool the check id belongs to.","one_document":"No. The rule sits on the target component and the check on the validation component.","owner":"The validation tool and its content: OpenSCAP or Ansible in the published files.","snippet_ids":["ibm-validation-ansible"]},{"approach":"assessment-first","construct":"An activity step whose description holds the audit text, with a prop saying automated. For CIS the description holds the script; for the STIG it holds the check text; for CISA a prop holds a JSON string naming the check.","kind":"description","needs":"A convention per publisher for where the script is in the text and how its output is judged.","one_document":"Yes. The rule is the activity and the check is its step.","owner":"Whoever reads the description. Nothing names an engine.","snippet_ids":["ez-cis-step-props","ez-cisa-context-step"]},{"approach":"executable-first","construct":"An assessment-method part beside the objective, with the script in its prose or linked as a resource, and props for platform, language, evaluation and pass condition.","kind":"executable","needs":"An executor that reads the props, and a namespace with an owner. Where the publisher gives no script, as the STIG does not, the method carries a description.","one_document":"Yes. Objective and method are parts of one control, in the catalog or added to it by a profile.","owner":"The publisher of the guidance on the catalog route; the party writing the profile otherwise.","snippet_ids":["pf-cis-method-1-1-1-1","pf-stig-method-sc-28"]}],"title":"Rules, scripts, or both: what the OSCAL carries about the check"},"data/corpus-stats.json":{"generated_from":"repository-defined inputs in tools/source-lock.json","note":"Every figure the site cites, with the derivation that tools/verify.py --stats recomputes from the source corpora. A mismatch is a hard failure.","stats":[{"derivation":"len(catalog.groups) in AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","key":"aws_groups","label":"groups in the AWS Security Hub catalog","value":77},{"derivation":"sum(len(g.controls) for g in catalog.groups) in aws_security-hub.oscal.json","key":"aws_controls","label":"controls in the AWS Security Hub catalog","value":452},{"derivation":"count of AWS/oscal-content-for-aws-services-main/component-definitions/*.oscal.json","key":"aws_cdef_files","label":"AWS component definition files","value":230},{"derivation":"count of components with type == 'software' across all AWS component-definitions","key":"aws_software_components","label":"AWS Config rules modelled as software components","value":429},{"derivation":"count of software-component implemented-requirements where catalog control's assessment-method part title == component title","key":"aws_title_matches","label":"software component titles matching the catalog TechnicalControlId, out of 429","value":429},{"derivation":"452 minus the count of distinct control-ids cited by software components","key":"aws_controls_without_check","label":"catalog controls with no software check component","value":29},{"derivation":"452 minus the count of distinct control-ids cited by any component","key":"aws_controls_unreferenced","label":"catalog controls referenced by no component at all","value":14},{"derivation":"sum(len(component.rules)) across cos- and idservice-component-definition.json","key":"ibm_rules","label":"rules in the IBM component definitions","value":5},{"derivation":"sum(len(component.checks)) across ansible- and oscap-validation-component-definition.json","key":"ibm_checks","label":"checks in the IBM validation component definitions","value":5},{"derivation":"count of distinct implemented-requirements.control-id across cos and idservice","key":"ibm_control_ids","label":"distinct control-ids covered by the IBM component definitions","value":9},{"derivation":"sum(len(assessment-plan.local-definitions.activities)) across the 15 Easy Dynamics assessment plans","key":"ez_activities","label":"assessment plan activities across the Easy Dynamics corpus","value":2425},{"derivation":"sum(len(activity.steps)) across the 15 Easy Dynamics assessment plans","key":"ez_steps","label":"assessment plan steps across the Easy Dynamics corpus","value":5694},{"derivation":"count of activity props where name == 'method' and value == 'TEST' across the 9 STIG files; no other method value occurs","key":"stig_method_test","label":"STIG activities carrying method TEST, out of 2271","value":2271},{"derivation":"count of step props where name == 'assessment-status' and value == 'automated' in CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","key":"cis_ubuntu_automated","label":"CIS Ubuntu 24.04 steps marked automated","value":576},{"derivation":"same file, value == 'manual'","key":"cis_ubuntu_manual","label":"CIS Ubuntu 24.04 steps marked manual","value":40},{"derivation":"count of step props where name == 'assessment-status' and value == 'automated' in CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","key":"cis_postgres_automated","label":"CIS PostgreSQL 18 steps marked automated","value":0},{"derivation":"same file, value == 'manual'","key":"cis_postgres_manual","label":"CIS PostgreSQL 18 steps marked manual","value":144},{"derivation":"count of Easy Dynamics/STIG_XCCDF to OSCAL Assessment Plans/*.json","key":"stig_files","label":"STIG assessment plan files","value":9},{"derivation":"count of STIG files where assessment-plan.import-ssp.href == 'PLACEHOLDER'","key":"stig_placeholder","label":"STIG files whose import-ssp.href is the literal string PLACEHOLDER","value":9},{"derivation":"count of AWS/oscal-content-for-aws-services-main/catalogs/*.oscal.json","key":"aws_catalog_files","label":"AWS catalog files","value":1},{"derivation":"count of files under Easy Dynamics/** whose root element is assessment-plan. The corpus also holds one assessment-results file and two non-OSCAL benchmark files, which this does not count","key":"ez_files","label":"Easy Dynamics assessment plan files","value":15},{"derivation":"count of IBM/*component-definition.json","key":"ibm_cdef_files","label":"IBM component definition files","value":4},{"derivation":"count of IBM/assessment-plan.json","key":"ibm_ap_files","label":"IBM assessment plan files","value":1},{"derivation":"count of IBM/assessment-result.json","key":"ibm_ar_files","label":"IBM assessment result files","value":1},{"derivation":"recursive count of every props array across Easy Dynamics/**/*.json","key":"ez_props","label":"props across the Easy Dynamics assessment plans","value":55458},{"derivation":"recursive count of every props array across AWS/oscal-content-for-aws-services-main/**/*.json","key":"aws_props","label":"props across the AWS catalog and component definitions","value":6094},{"derivation":"recursive count of every props array across IBM/*component-definition.json","key":"ibm_cdef_props","label":"props across the four IBM component definitions","value":0},{"derivation":"sum(1 for g in catalog.groups if g.groups) in aws_security-hub.oscal.json","key":"aws_nested_groups","label":"AWS catalog groups that themselves contain groups","value":0},{"derivation":"sum(len(c.params) for g in catalog.groups for c in g.controls)","key":"aws_control_params","label":"params declared on AWS catalog controls","value":0},{"derivation":"count of AWS/**/*.json whose root key is profile","key":"aws_profile_files","label":"profile files in the AWS corpus","value":0},{"derivation":"count of Easy Dynamics/CISA BOD 25-01/*.json","key":"cisa_files","label":"CISA BOD 25-01 files: four assessment plans, one assessment result and the sample SSP they import","value":6},{"derivation":"count of step props named criticality with value SHALL in Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","key":"cisa_criticality_shall","label":"steps carrying criticality SHALL in ap-cisa-scuba-agnostic.json","value":73},{"derivation":"count of step props named criticality with value SHOULD in the same file","key":"cisa_criticality_should","label":"steps carrying criticality SHOULD in ap-cisa-scuba-agnostic.json","value":55},{"derivation":"count of objects carrying a string type together with include-all or include-subjects, where type is component","key":"ez_subjects_component","label":"assessment-subject blocks typed component across the Easy Dynamics corpus","value":2407},{"derivation":"same walk, where type is inventory-item","key":"ez_subjects_inventory_item","label":"assessment-subject blocks typed inventory-item across the Easy Dynamics corpus, including the one on each CISA associated activity","value":26},{"derivation":"len(assessment-results.results[0].findings) in IBM/assessment-result.json. The file also carries a findings array at the document root, outside results, where the model does not define one","key":"ibm_ar_findings","label":"findings inside the result object of the IBM assessment result","value":0},{"derivation":"len(assessment-results.results[0].observations) in IBM/assessment-result.json","key":"ibm_ar_observations","label":"observations in the IBM assessment result","value":1},{"derivation":"sum(1 for a in every assessment-plan.local-definitions.activities if a.related-controls) across Easy Dynamics/**/*.json","key":"ez_activities_with_related_controls","label":"assessment plan activities carrying related-controls, out of 2425","value":2279},{"derivation":"sum(1 for ir in every control-implementation.implemented-requirements if not ir.implementing-rules) across IBM/*component-definition.json","key":"ibm_ir_without_rules","label":"IBM implemented-requirements listing no implementing rule, out of 9","value":1},{"derivation":"count of assessment plans under Easy Dynamics/Center for Internet Security/","key":"cis_ap_files","label":"CIS assessment plan files","value":2},{"derivation":"size of the set of control-id values under reviewed-controls.control-selections[].include-controls[] in the two CIS plans","key":"cis_control_ids","label":"distinct control ids referenced across the CIS assessment plans","value":82},{"derivation":"distinct control ids under a control-selection whose props carry resolution-status = synthetic-ids","key":"cis_synthetic_ids","label":"control ids the content itself flags as synthetic","value":53},{"derivation":"count, not set size, of include-control entries under a control-selection flagged resolution-status = synthetic-ids","key":"cis_synthetic_refs","label":"references to those 53 synthetic control ids","value":84},{"derivation":"count of props name=step-type value=remediate across the 15 Easy Dynamics assessment plans","key":"ez_step_type_remediate","label":"steps carrying step-type remediate, all in the STIG plans","value":2271},{"derivation":"count of props name=step-type value=remediation across the 15 Easy Dynamics assessment plans","key":"ez_step_type_remediation","label":"steps carrying step-type remediation, all in the CIS plans","value":380},{"derivation":"count of props name=step-type value=check across the 15 Easy Dynamics assessment plans","key":"ez_step_type_check","label":"steps carrying step-type check, all in the STIG plans","value":2271},{"derivation":"count of props name=step-type value=audit across the 15 Easy Dynamics assessment plans","key":"ez_step_type_audit","label":"steps carrying step-type audit, all in the CIS plans","value":380},{"derivation":"size of the set of sorted step-type value sets, grouped by the directory each plan sits in","key":"ez_step_type_vocabularies","label":"distinct step-type vocabularies in use across the two benchmark families","value":2},{"derivation":"count of files under Easy Dynamics/** whose root element is assessment-results","key":"ez_ar_files","label":"assessment results in the corpus","value":1},{"derivation":"count of files in Easy Dynamics/** whose root element is system-security-plan","key":"ez_ssp_files","label":"system security plans in the corpus: the sample SSP the CISA plans import","value":1},{"derivation":"count of role-id keys valued 'owner' at any depth in AWS/**/component-definitions/*.oscal.json","key":"aws_owner_refs","label":"references to role-id owner across the AWS component definitions","value":429},{"derivation":"count of AWS component definition files containing at least one role-id valued 'owner'","key":"aws_files_referencing_owner","label":"component definition files referencing role-id owner","value":67},{"derivation":"count of metadata.roles entries with id 'author', by file","key":"aws_files_declaring_author","label":"component definition files declaring the role author","value":230},{"derivation":"size of the set of metadata.roles[].id across all 230 AWS component definition files","key":"aws_roles_declared","label":"distinct roles declared anywhere in the AWS component definitions","value":1},{"derivation":"count of control parts with name='guidance' in aws_security-hub.oscal.json","key":"aws_guidance_parts","label":"guidance parts across the catalog controls, one per control","value":452},{"derivation":"size of the set of prose values among control parts named 'guidance'","key":"aws_guidance_distinct","label":"distinct guidance prose strings among the guidance parts","value":1},{"derivation":"count of catalog.groups entries whose id is exactly 'TestControl'","key":"aws_test_groups","label":"catalog groups with the id TestControl","value":1},{"derivation":"sum(len(g.controls)) over catalog groups with id 'TestControl'","key":"aws_test_controls","label":"controls inside the TestControl group","value":1},{"derivation":"count of TestControl controls with a rel='remediation' link whose href does not contain the control's own service prefix","key":"aws_test_controls_mislinked","label":"TestControl controls whose remediation link names a different control","value":1},{"derivation":"count of files in AWS/** whose root element is system-security-plan","key":"aws_ssp_files","label":"system security plans in the corpus","value":0},{"derivation":"count of files in AWS/** whose root element is assessment-plan","key":"aws_ap_files","label":"assessment plans in the corpus","value":0},{"derivation":"count of files in AWS/** whose root element is assessment-results","key":"aws_ar_files","label":"assessment results in the corpus","value":0},{"derivation":"size of the set of component-definition.uuid across IBM/*component-definition.json","key":"ibm_document_uuids","label":"distinct document uuids across the 4 IBM component definition files","value":1},{"derivation":"sum(len(c.checks)) over components in IBM/oscap-validation-component-definition.json","key":"ibm_oscap_checks","label":"checks in the OSCAP validation component","value":3},{"derivation":"count of OSCAP checks whose target-component-uuid is not a component uuid declared in any of the 4 IBM component definitions","key":"ibm_oscap_checks_dangling","label":"OSCAP checks whose target-component-uuid resolves to no component","value":3},{"derivation":"sum(len(c.checks)) over components in IBM/ansible-validation-component-definition.json","key":"ibm_ansible_checks","label":"checks in the ANSIBLE validation component","value":2},{"derivation":"count of ANSIBLE checks whose target-component-uuid is not a component uuid declared in any of the 4 IBM component definitions","key":"ibm_ansible_checks_dangling","label":"ANSIBLE checks whose target-component-uuid resolves to no component","value":0},{"derivation":"1 if the IBM assessment plan carries a 'local-defintions' key and no 'local-definitions' key, else 0","key":"ibm_ap_local_definitions_misspelled","label":"assessment plans spelling local-definitions without its second i","value":1},{"derivation":"count of files in IBM/*.json whose root element is system-security-plan","key":"ibm_ssp_files","label":"system security plans in the corpus","value":0},{"derivation":"count of Easy Dynamics assessment plan files whose text contains the key \"step-type\"","key":"ez_files_with_step_type","label":"assessment plans using step-type at all","value":11}]},"data/criteria.json":{"criteria":[{"name":"Triad fidelity","number":1,"question":"Does the option keep regulator, implementer and assessor roles separable?","slots":["1","3","6a","6b"]},{"name":"Normativity","number":2,"question":"Can the artifact express must versus may? Can an auditor treat it as binding?","slots":["1"]},{"name":"Requirement level","number":3,"question":"Can shall, should and may be represented at all?","slots":["1"]},{"name":"Hierarchy support","number":4,"question":"Does the model natively carry deep benchmark hierarchies?","slots":["1"]},{"name":"Tailoring","number":5,"question":"Can an organization select, exclude and parameterize at scale?","slots":["1"]},{"name":"Authoring burden","number":6,"question":"How many OSCAL artifacts must a benchmark author produce per benchmark, multiplied across roughly 100 CIS guides?","slots":["1","2","3","4","5","6a","6b"]},{"name":"SSP impact","number":7,"question":"How many additional items enter the SSP? Does the SSP end up mixing desired and actual state?","slots":["6a"]},{"name":"Response fidelity","number":8,"question":"Can a system owner answer per host or inventory item, or only per component?","slots":["4"]},{"name":"Traceability","number":9,"question":"Can a consumer traverse control to rule to check to activity to task to observation using core schema only?","slots":["1","2","3","5","6b"]},{"name":"Schema change cost","number":10,"question":"How many models change, and what is the realistic ratification timeline?","slots":["1","2","3","4","5","6a","6b"]},{"name":"Update decoupling","number":11,"question":"When a benchmark revises independently of the regulation, what has to change downstream?","slots":["1"]},{"name":"Cross-framework use","number":12,"question":"Does this help someone operating under SOC 2, ISO and FedRAMP at the same time?","slots":["2"]},{"name":"Inspectability","number":13,"question":"Can an operator see what a check does before running it on their systems?","slots":["3"]},{"name":"Prop dependence","number":14,"question":"How much meaning lives in namespaced props rather than core schema?","slots":["1","2","3","4","5","6a","6b"]},{"name":"Existing content","number":15,"question":"Is there working end-to-end content today, including an SSP and an AR?","slots":["1","2","3","4","5","6a","6b"]}],"note":"Fifteen evaluation criteria maintained in this repository for comparing the three approaches. The questions and slot mappings define the analysis scope."},"data/decisions.json":{"constructs":{"columns":["Aspect","Rules","assessment-method"],"intro":"Two constructs can carry code. A typed assembly, which the site calls Rules after the field name the published proposal uses, adds objects to the schema with their own fields and identity: rules and checks in the published component-first files, and an automation-scripts assembly in the file the generator writes from the CIS benchmark in that shape. The assessment-method part is released OSCAL, extended by props in a namespace and by links, and it is what the concept note and the generated catalog use. The table states each aspect for both and ranks neither.","label":"Which construct carries it","options":[{"consequences":["A validator checks the executor fields themselves, so a document that validates is a document an executor can read.","Nothing validates until a version ships the assembly, and two proposals with different fields are two versions to agree on.","A rule is an object with its own id, so it can sit on a component and be named from a plan or a result without going through a control."],"instances":[{"carries":"reference","file":"oscap-validation-component-definition.json","label":"rules and checks on validation components, published","publisher":"component-first","status":"proposed"},{"carries":"executable","file":"cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json","label":"the same assembly written from the CIS benchmark by the generator","publisher":"executable-first","status":"generated"}],"instances_differ":"The two instances are two schemas. The published one names a rule and a check, each with an id, and the check points at content the tool owns. The generated one names a script object with a type, a language, the profiles it applies to, evaluation criteria and the script as payload. They share the idea of a typed object with identity and nothing else, and neither validates under 1.2.1.","key":"rules","label":"Rules","meaning":"A typed assembly added to the schema, with its own identity and its own fields for what the check is and how it is run."},{"consequences":["Every file validates today, and a finding targets the objective part beside the method with no change to the results model.","A validator checks that a part and its props exist and nothing about what the props say, so the executor's vocabulary has to be agreed outside the schema.","A part sits on a control and nowhere else in 1.2.1, so the code is addressed through a requirement and reaches a component only through a profile the system's plan imports."],"instances":[{"carries":"reference","file":"catalogs/aws_security-hub.oscal.json","label":"assessment-method parts naming the check by identifier, published","publisher":"catalog-first","status":"released"},{"carries":"executable","file":"cis-ubuntu-24-04-lts-benchmark-catalog.json","label":"executable assessment methods on every recommendation, generated from the CIS benchmark","publisher":"executable-first","status":"generated"},{"carries":"description","file":"nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","label":"executable assessment methods added to SP 800-53 controls by a profile, generated from the STIG","publisher":"executable-first","status":"generated"}],"instances_differ":"One released construct, used three ways: to name a check by identifier, to carry a script with the props an executor needs, and to carry check text where the publisher gives no script. The part is the same in all three; what changes is what its prose and props hold.","key":"assessment-method","label":"assessment-method","meaning":"The released part on a control, with its method prop, carrying the body in prose or a linked resource and the executor's needs as props in a namespace."}],"rows":[{"aspect":"What it is","method":"The released assessment-method part on a control, with a method prop.","rules":"A typed assembly of its own, added to the schema."},{"aspect":"Schema","method":"No change. Every file validates under 1.2.1.","rules":"New fields and a new version. Nothing validates until it ships."},{"aspect":"What a validator checks","method":"That a part and its props exist. Nothing about what the props say.","rules":"The fields themselves: type, language, criteria, payload."},{"aspect":"Identity","method":"A part id, addressed through the control it sits on.","rules":"An object with its own id, referenceable from any document."},{"aspect":"Where it can sit","method":"On a control, in a catalog or a profile. Nowhere else in 1.2.1.","rules":"Wherever the schema author puts it. On a component in both instances so far."},{"aspect":"Fit with results","method":"A finding targets the objective part beside it, unchanged.","rules":"Its own vocabulary. A finding needs a way to name a rule."},{"aspect":"Remediation","method":"A remediation part, in prose or a linked resource.","rules":"A second script object, typed."},{"aspect":"Shown carrying","method":"A reference in the published catalog; the script and a description in the generated files.","rules":"A reference in the published files; the script in the generated file."}]},"figures":{"catalog_inline_audit_scripts":85,"note":"Recomputed by tools/verify.py --decisions from the generated Rules-shape component definition and the generated catalog.","rules_audit_scripts":97,"rules_distinct_audit_scripts":85,"rules_evaluated":66,"rules_remediation_scripts":67,"rules_requirements":49,"text":"Written from one benchmark in both constructs, the Rules-shape file carries 97 audit script objects and 67 remediation script objects under 49 implemented requirements, and 66 of the audit objects carry evaluation criteria. The 97 are 85 distinct scripts, because a recommendation that names two CIS Controls is carried under both and the shape has no link between two requirements' scripts. The catalog beside it carries the same 85 scripts inline, one per method, and links the others by name."},"note":"Decisions 2 and 3 of the start page's section on code in OSCAL. Decision 1, what the OSCAL carries about the check, is data/check-carrier.json. This file holds the construct decision, Rules against assessment-method, and the placement decision, and the grid that crosses them. Every document a cell names is referenced by inventory key into data/oscal-artifacts.json or by a path under examples/, so the renderer resolves the link and tools/verify.py --decisions checks that it exists and that its status is what the cell says. The site takes no position on either decision; the consequences are stated and no option is ranked.","placements":{"cells":[{"construct":"rules","documents":[],"note":"No document places a typed rule assembly on a control.","placement":"control","status":"empty"},{"construct":"rules","documents":[{"file":"oscap-validation-component-definition.json","label":"rules and checks, published","publisher":"component-first"},{"file":"cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json","label":"automation-scripts, generated from the CIS benchmark","publisher":"executable-first"}],"note":"Both instances put the assembly on a validation component, one carrying a reference and one the script.","placement":"component","status":"proposed"},{"construct":"rules","documents":[],"note":"No document places a typed rule assembly on an activity.","placement":"activity","status":"empty"},{"construct":"assessment-method","documents":[{"file":"catalogs/aws_security-hub.oscal.json","label":"naming the check, published","publisher":"catalog-first"},{"file":"cis-ubuntu-24-04-lts-benchmark-catalog.json","label":"carrying the script, generated","publisher":"executable-first"},{"file":"nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","label":"added by a profile, generated","publisher":"executable-first"}],"note":"The part is released here. The published catalog names a check by identifier; the generated files carry the script and the check text.","placement":"control","status":"released"},{"construct":"assessment-method","documents":[],"note":"An implemented requirement has a description, props, links, set-parameters and statements, and no parts. A part can be carried here only in a later version.","placement":"component","status":"needs-schema"},{"construct":"assessment-method","documents":[],"note":"An activity and a step have props, links and a description, and no parts. The assessment-first corpus carries descriptions here, which is the second kind on the axis above and neither construct.","placement":"activity","status":"needs-schema"}],"grid_label":"Construct by placement, and what occupies each cell","intro":"Three homes have been used or proposed. The construct decides part of this: a part can only sit where parts are allowed, which in 1.2.1 means a control, while a new assembly sits wherever its schema puts it. What the placement decides is what the code is coupled to and how it reaches the system's plan of record.","label":"Where it sits","options":[{"couples_to":"A requirement. The code says which control it tests, and the platform it runs on is a prop repeated on every method.","key":"control","label":"On a control","models":["catalog","profile"],"reaches_ssp":"Through the profile the plan of record imports. Nothing on the system's by-component names the objective."},{"couples_to":"A platform. The component is the thing the code runs on, stated once, and the control is a reference on the requirement.","key":"component","label":"On a component","models":["component-definition"],"reaches_ssp":"Through by-component, which is where the system's own responses live."},{"couples_to":"One assessment. The code is part of a plan for one system at one time.","key":"activity","label":"On an activity","models":["assessment-plan"],"reaches_ssp":"Not at all. The plan imports the plan of record and adds nothing to it."}],"statuses":[{"key":"released","label":"Released","meaning":"A released assembly carries it and a held file validates."},{"key":"proposed","label":"Proposed","meaning":"A held file does it with an assembly 1.2.1 does not define, and fails validation as it must."},{"key":"needs-schema","label":"Needs a schema change","meaning":"No held file, and the released schema has no place for it here."},{"key":"empty","label":"Empty","meaning":"No held file, and nothing in either proposal prevents it."}]},"thesis":["The fourth approach's thesis is that the check's code travels in the OSCAL document. Two constructs can carry it, a typed assembly of its own or the released assessment-method part, and it can sit on a control, a component or an activity. Neither of those is the idea. They are decisions under it, and this section states each one with its consequences.","Three decisions, then. What the document carries about the check, which is the axis above. Which construct carries it, where the two candidates are a new typed assembly or the released part. And where it sits, which the construct partly decides."]},"data/examples.json":{"cis_derived":["assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json"],"files":[{"approach":"assessment-first","bytes":308830,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","sha256":"521acdef03590676c0a041bf920e36a7575c63683f04e787909d3c4dcc10ea66"},{"approach":"assessment-first","bytes":325728,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-maester.json","sha256":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653"},{"approach":"assessment-first","bytes":293862,"path":"assessment-first/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","sha256":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e"},{"approach":"assessment-first","bytes":298328,"path":"assessment-first/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","sha256":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d"},{"approach":"assessment-first","bytes":19829,"path":"assessment-first/CISA BOD 25-01/assessment-plan.json","sha256":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee"},{"approach":"assessment-first","bytes":39652,"path":"assessment-first/CISA BOD 25-01/sample-ssp.json","sha256":"2309e2f7ad9e8a468ac38fa7584094cab3e1bc20fc1d8ae108836f4e65ecf66d"},{"approach":"assessment-first","bytes":1032133,"path":"assessment-first/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1.0.0.json","sha256":"b72eda73c5bef60e2971c93261bc226594cfb8d8aa1be92deb6b2e121bf05379"},{"approach":"assessment-first","bytes":423087,"path":"assessment-first/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","sha256":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8"},{"approach":"assessment-first","bytes":6823924,"path":"assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","sha256":"1a90fccb4442decd119382233ff8986caaaeede83dcf3c5ab22a87c747ab0c81"},{"approach":"assessment-first","bytes":1768114,"path":"assessment-first/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","sha256":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c"},{"approach":"assessment-first","bytes":821083,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","sha256":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6"},{"approach":"assessment-first","bytes":823183,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","sha256":"e1eed16a4a0f6d6b6025ce05c16832458bbcd4ba16d597340d0c764333197841"},{"approach":"assessment-first","bytes":2454926,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel8.json","sha256":"54cd0e15efb7c96347cfd16012d6fc81b93861079ce8a2ccf4e61eac57b538f7"},{"approach":"assessment-first","bytes":3051725,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel9.json","sha256":"9fbd810f7c658809a3be29bdb9bc14dfdafabbe289482454208f86b3646c7783"},{"approach":"assessment-first","bytes":1310065,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu22.json","sha256":"46738bf619cdfbef00913d761586633bec301e4aae5050a30c823f27509c7e7d"},{"approach":"assessment-first","bytes":1341083,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","sha256":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e"},{"approach":"assessment-first","bytes":1940344,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","sha256":"24dead32391e392f3d25501b0581fef5a719add51667c98920ad01f2d9273207"},{"approach":"assessment-first","bytes":1858865,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","sha256":"bfe441c22311614bc30cd080a57b5242129137912400a73a3e731a9f7a9abd7a"},{"approach":"assessment-first","bytes":1867817,"path":"assessment-first/DISA/STIG_XCCDF to OSCAL Assessment Plans/win2025.json","sha256":"b8e54f5a9f6e554cd58bfe0c6b5be46085af5b760786ff6c933b1be7f8150bf8"},{"approach":"component-first","bytes":1106,"path":"component-first/ansible-validation-component-definition.json","sha256":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd"},{"approach":"component-first","bytes":5105,"path":"component-first/assessment-plan.json","sha256":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6"},{"approach":"component-first","bytes":4275,"path":"component-first/assessment-result.json","sha256":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806"},{"approach":"component-first","bytes":2525,"path":"component-first/cos-component-definition.json","sha256":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a"},{"approach":"component-first","bytes":5230,"path":"component-first/idservice-component-definition.json","sha256":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf"},{"approach":"component-first","bytes":1297,"path":"component-first/oscap-validation-component-definition.json","sha256":"9efe6492ede4a21a743db6afe6bf05efda79c206d00dc6ee40e89f16145323f3"}],"link_only":{"catalog-first":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/"},"note":"The curated OSCAL examples committed in this repository, indexed by tools/copy_examples.py with the path, byte count and SHA-256 of each. Every build re-verifies the files against this index, so an edit is only accepted through an explicit --rebaseline run recorded in BUILD-LOG.md. Catalog-first is not here: it is published in a public repository and linked at the locked revision instead.","shared":[{"bytes":10442037,"path":"NIST_SP-800-53_rev5_catalog.json","sha256":"01f37cf90ea99d92242c936cbfbdebcc338eef1f71454e2acac36cc56e9bc062"}]},"data/generated-pages.json":{"note":"The hash of each approach page as this tool last wrote it. tools/approach_pages.py compares the page on disk against this before overwriting, so a hand edit to a generated page stops the build instead of disappearing into it.","sha256":{"assessment-first":"14f367b74552ad49311d12046f092f794ce8b22dbe63c6ab4f7e661d911d9477","catalog-first":"60a60d7e48e4c6bf2d6f397412d7c71758845761caa85b263e39bd37d72053ca","component-first":"a4c2a1fb4bdfb31e1d10f8db8d3d26cbf51000be581724b7fee08398225168e7","executable-first":"55a9067b341ac7034c1215f806ab1f9e1566c821d01b7fe463db2ab313737c5d"},"written_by":"tools/approach_pages.py"},"data/glossary.json":{"note":"Definitions used by this analysis, with links from first uses. Alternative meanings and unresolved distinctions are identified without selecting an approach.","terms":[{"other_usages":[{"usage":"A normative requirement, a shall, equivalent to a control","who":"Catalog-first, Option A"},{"usage":"A statement of how a component may be configured, descriptive rather than binding","who":"Component-first, Option B"},{"usage":"An assessment objective on a control, with an executable assessment method beside it","who":"Executable-first, Option D"},{"usage":"Colloquially, the check code itself","who":"Ambiguous usage; this analysis distinguishes rule from check"},{"usage":"An AWS Config rule: a deployable resource with parameters","who":"AWS Config, the product"}],"see_also":["check","control","desired state","requirement level"],"site_usage":"One technical requirement or recommendation, finer-grained than a control, without any claim about whether it is binding. A working definition for comparing approaches, not selecting an interpretation.","status":"contested","term":"rule"},{"other_usages":[],"see_also":["rule","validation component","assessment platform"],"site_usage":"An executable or procedural test that determines whether a rule is satisfied. One rule may have many checks, one per tool.","status":"settled","term":"check"},{"other_usages":[{"usage":"Possible state: a technology provider describes available configurations rather than required configurations","who":"Alternative interpretation of component configuration"}],"see_also":["actual state","rule","implementation claim"],"site_usage":"The configuration prescribed by a rule, distinct from the system's observed configuration, or actual state.","status":"contested","term":"desired state"},{"other_usages":[],"see_also":["desired state","assessment result"],"site_usage":"The system's observed configuration, distinct from the configuration prescribed by a rule, or desired state.","status":"settled","term":"actual state"},{"other_usages":[],"see_also":["rule","link to a control","catalog"],"site_usage":"A requirement from a regulatory framework, such as NIST SP 800-53. Coarser than a rule. One control is typically served by many rules.","status":"settled","term":"control"},{"other_usages":[],"see_also":["control","mapping collection","finding","observation"],"site_usage":"An optional relationship from a rule to regulatory controls. A rule may serve several controls, one, or none. A rule without a control link can have observations but no control-targeted finding.","status":"settled","term":"link to a control"},{"other_usages":[{"usage":"Hardening guidance, used interchangeably","who":"This analysis"}],"see_also":["rule","hardening guidance"],"site_usage":"A published set of technology-specific hardening guidance, including CIS Benchmarks, DISA STIGs, CISA SCuBA baselines and technology provider guides.","status":"settled","term":"benchmark"},{"other_usages":[],"see_also":["benchmark","rule"],"site_usage":"Technology-specific guidance for configuring hardware, software or services securely. Used as a synonym for benchmark in this analysis.","status":"settled","term":"hardening guidance"},{"other_usages":[],"see_also":["rule","normativity"],"site_usage":"Whether a statement is a shall, should or may. OSCAL has no dedicated core requirement-level field across these approaches. Properties can carry such labels, but consumers need shared conventions to interpret them; model placement alone does not establish requirement level.","status":"not-established","term":"requirement level"},{"other_usages":[],"see_also":["requirement level","rule"],"site_usage":"Whether an artifact expresses binding requirements against which an auditor can assess a system. Normativity is part of the debate over model placement.","status":"contested","term":"normativity"},{"other_usages":[],"see_also":[],"set_aside":true,"site_usage":"A Component Definition construct grouping components and control-implementations to express joint satisfaction. Whether capabilities should be added to the SSP or removed from Component Definition remains an open design question in this analysis. No position is selected.","status":"contested","term":"capability"},{"other_usages":[{"usage":"A component whose purpose is to run checks rather than to be checked. Type validation, carrying a checks array.","who":"Component-first examples using proposed assemblies"},{"usage":"A component enumerating the compliance frameworks a service has been validated against.","who":"Alternative interpretation, not demonstrated by the OSCAL examples"}],"see_also":["check","component"],"site_usage":"Two distinct meanings are used: a component running checks, or a component describing validation against frameworks. This analysis identifies the intended meaning.","status":"contested","term":"validation component"},{"not_established_note":"The open question is when a component alone identifies a runner and when an assessment platform adds necessary execution context.","other_usages":[],"see_also":["assessment asset","component","actor"],"site_usage":"An OSCAL assessment-assets element that may reference components through uses-components. The examples do not establish a consistent convention for distinguishing assessment platforms, assessment assets and components in runner descriptions.","status":"not-established","term":"assessment platform"},{"not_established_note":"A consumer still needs to associate each task or observation with the asset used.","other_usages":[],"see_also":["assessment platform","component","actor"],"site_usage":"The OSCAL assessment-assets container holds components and assessment-platforms. The examples do not establish a consistent convention for identifying runners across these structures.","status":"not-established","term":"assessment asset"},{"not_established_note":"The examples leave open whether components should represent individual rules, products or policy engines and how consumers reconcile those levels.","other_usages":[],"see_also":["assessment platform","assessment asset","validation component"],"site_usage":"A part of a system, with related meanings across Component Definition, SSP, Assessment Plan and Assessment Results models. The distinction from assessment platforms and assets remains unresolved, as does granularity: a component may represent a configuration rule or a policy engine.","status":"not-established","term":"component"},{"not_established_note":"The examples use different runner-identification conventions. No single convention is established here for associating a task or observation with its producer.","other_usages":[{"usage":"An assessment platform, optionally reaching components through uses-components","who":"OSCAL assessment-assets"},{"usage":"A component of type validation, carrying the checks it runs","who":"Component-first, Option B, proposed schema"},{"usage":"An origin actor on an assessment result","who":"OSCAL assessment-results"},{"usage":"A tool named in a prop at task level","who":"The assessment plans in two of the three corpora"}],"see_also":["assessment platform","assessment asset","component","check"],"site_usage":"The tool or person performing a check, addressed by question 5. Actor is a neutral label in this analysis because no single OSCAL construct covers all uses.","status":"not-established","term":"actor"},{"other_usages":[],"see_also":["assessment result","system security plan"],"site_usage":"The system owner's narrative assertion of control implementation and design intent per component. The SSP represents claims through implemented-requirement, statement and by-component. Addressed by question 6a.","status":"settled","term":"implementation claim"},{"other_usages":[],"see_also":["implementation claim","observation","finding"],"site_usage":"The assessor's evidence-based record of whether a control was satisfied for a subject at a point in time. The AR uses observation, finding and status for binary or graded outcomes. Addressed by question 6b.","status":"settled","term":"assessment result"},{"other_usages":[],"see_also":["finding","assessment result","link to a control"],"site_usage":"An AR element recording observed evidence. Requires uuid, description, methods and collected, with no control reference. Observations are available for rules with or without control links.","status":"settled","term":"observation"},{"other_usages":[],"see_also":["observation","link to a control","assessment result"],"site_usage":"An AR element recording whether an objective is satisfied. The required target type is restricted to statement-id or objective-id, both control-derived. A rule without a control link cannot have a finding.","status":"settled","term":"finding"},{"other_usages":[],"see_also":["link to a control","catalog"],"site_usage":"An OSCAL model, GA since 1.2, relating collections of controls. Third parties can publish mappings after the source catalogs. The mapping-item type permits control and statement targets, not component rules or activities.","status":"settled","term":"mapping collection"},{"other_usages":[],"see_also":["profile","control"],"site_usage":"OSCAL model, Control layer. A structured set of controls and control enhancements.","status":"settled","term":"catalog"},{"other_usages":[],"see_also":["catalog"],"site_usage":"OSCAL model, Control layer. A baseline or overlay that selects and customizes controls from catalogs.","status":"settled","term":"profile"},{"other_usages":[],"see_also":["system security plan","component"],"site_usage":"OSCAL model, Implementation layer. Describes how components implement controls.","status":"settled","term":"component definition"},{"other_usages":[],"see_also":["component definition","implementation claim"],"site_usage":"OSCAL model, Implementation layer. Documents how a particular system implements required controls. Abbreviated SSP.","status":"settled","term":"system security plan"},{"other_usages":[],"see_also":["assessment result","activity","step"],"site_usage":"OSCAL model, Assessment layer. Defines how controls will be assessed, through activities, steps and tasks. Abbreviated AP or SAP.","status":"settled","term":"assessment plan"},{"other_usages":[],"see_also":["step","assessment plan"],"site_usage":"An assessment plan local-definitions element containing steps. How to divide a benchmark procedure between activities and steps remains an analysis question.","status":"not-established","term":"activity"},{"other_usages":[],"see_also":["activity","assessment plan"],"site_usage":"A child of an assessment plan activity. The examples do not establish one consistent boundary between the work represented by an activity and its steps.","status":"not-established","term":"step"},{"other_usages":[],"see_also":["assessment plan","observation","finding"],"site_usage":"OSCAL model, Assessment layer. Documents the results of control assessments, as observations and findings. Abbreviated AR or SAR.","status":"settled","term":"assessment results"},{"other_usages":[],"see_also":["assessment results"],"site_usage":"OSCAL model, Assessment layer. Documents remediation plans for identified issues. Abbreviated POA&M.","status":"settled","term":"plan of action and milestones"},{"other_usages":[],"see_also":["implementer","assessor"],"site_usage":"One of three stakeholder roles. Publishes requirements or recommendations for organisations to version, tailor and cite without depending on a specific system.","status":"settled","term":"publisher"},{"other_usages":[],"see_also":["publisher","assessor","desired state"],"site_usage":"One of three stakeholder roles. Uses requirements as desired-state configuration that a configuration engine can apply.","status":"settled","term":"implementer"},{"other_usages":[],"see_also":["publisher","implementer","check"],"site_usage":"One of three stakeholder roles. Runs checks or reviews sufficient evidence to determine whether requirements are satisfied.","status":"settled","term":"assessor"},{"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 executable-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; executable-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 executable-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 activity contains the check as the first step. A property on the step identifies an executable check resolved outside OSCAL.","pairs":[{"foreign":{"field":"no field","model":"assessment-plan","slot":"1"},"how":"containment","primary":{"field":"activities[].steps[].uuid","model":"assessment-plan","slot":"3","value":"333ddd0f-22da-4c18-8bc3-98e808746bca"}},{"foreign":{"field":"steps[].props[name=check].value","model":"assessment-plan","slot":"3","value":"SV-270747r1066730_rule"},"how":"name-match","primary":{"field":"no field","model":"nothing","slot":"5"}}],"to":"check"},{"from":"rule","how":"reference","note":"The activity references the framework control through related-controls, without a separate mapping document or an additional mapping identifier to maintain.","pairs":[{"foreign":{"field":"activities[].related-controls.control-selections[].include-controls[].control-id","model":"assessment-plan","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"reference","note":"The example plan identifies platforms for the assessment as a whole. The platform reference does not identify the engine used for each check.","pairs":[{"foreign":{"field":"assessment-platforms[].uses-components[].component-uuid","model":"assessment-plan","slot":"5","value":"56270516-2673-4d4c-8d4f-52e4107f968d"},"how":"reference","primary":{"field":"assessment-assets.components[].uuid","model":"assessment-plan","slot":"5"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The plan references one system security plan through a back-matter resource. Where no plan of record exists, the resource can describe the system in prose.","pairs":[{"foreign":{"field":"import-ssp.href","model":"assessment-plan","slot":"6a","value":"#d381c885-4851-4931-828c-29bbb24fbaa3"},"how":"reference","primary":{"field":"back-matter.resources[].uuid","model":"assessment-plan","slot":"6a","value":"d381c885-4851-4931-828c-29bbb24fbaa3"}}],"to":"claim"},{"from":"runtime","how":"reference","note":"The example observation references the planned activity as the subject. The reference identifies the activity, not an inventory item assessed by the check.","pairs":[{"foreign":{"field":"observations[].subjects[].subject-uuid","model":"assessment-results","slot":"6b","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"},"how":"reference","primary":{"field":"activities[].uuid","model":"assessment-plan","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}}],"to":"result"},{"from":"result","how":"reference","note":"The finding targets a framework control objective. The target links the result to the framework without depending on an implementation statement in a plan of record.","pairs":[{"foreign":{"field":"findings[].target.target-id","model":"assessment-results","slot":"6b","value":"sc-28_obj"},"how":"reference","primary":{"field":"controls[].parts[objective].id","model":"catalog","slot":"2"}}],"to":"control"}],"introduced":{"field":"activities[].uuid","model":"assessment-plan","note":"The assessment plan defines the rule as an activity in the assessment layer, outside the implementation claim. The chain starts from the activity uuid.","slot":"1","value":"61b3ec99-dfbe-4997-8a66-6f2279edb84b"}},"catalog-first":{"hops":[{"from":"rule","how":"name-match","note":"The control references the check by title, a match not enforced by the schema. The check references the control by a resolvable id.","pairs":[{"foreign":{"field":"parts[assessment-method].props.TechnicalControlId","model":"catalog","slot":"1","value":"SV-270747r1066730_rule"},"how":"name-match","primary":{"field":"components[].title","model":"component-definition","slot":"3","value":"SV-270747r1066730_rule"}},{"foreign":{"field":"implemented-requirements[].control-id","model":"component-definition","slot":"3","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}}],"to":"check"},{"from":"rule","how":"reference","note":"A separate mapping collection links the catalogs. A third party can publish the mapping after both catalogs are published without owning either source.","pairs":[{"foreign":{"field":"maps[].sources[].id-ref","model":"mapping-collection","slot":"2","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}},{"foreign":{"field":"maps[].targets[].id-ref","model":"mapping-collection","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"none","note":"ConfigRuleId identifies the executable rule, but the content does not identify the engine that executes the check.","pairs":[{"foreign":{"field":"components[].props.ConfigRuleId","model":"component-definition","slot":"3","value":"SV_270747R1066730_RULE"},"how":"none","primary":{"field":"no field","model":"nothing","slot":"5"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The claim references a component, not a host. The by-component assembly has no assessment subject field for an individual instance.","pairs":[{"foreign":{"field":"implemented-requirements[].control-id","model":"system-security-plan","slot":"6a","value":"UBTU-24-600090"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"1","value":"UBTU-24-600090"}},{"foreign":{"field":"by-components[].component-uuid","model":"system-security-plan","slot":"6a","value":"534b356b-0de1-48d4-8536-5d41ed717456"},"how":"reference","primary":{"field":"system-implementation.components[].uuid","model":"system-security-plan","slot":"6a"}}],"to":"claim"},{"from":"claim","how":"reference","note":"The finding targets the implementation statement in the system security plan and references supporting observations, connecting the assessment outcome to the claim.","pairs":[{"foreign":{"field":"findings[].target.target-id","model":"assessment-results","slot":"6b","value":"UBTU-24-600090_smt"},"how":"reference","primary":{"field":"statements[].statement-id","model":"system-security-plan","slot":"6a","value":"UBTU-24-600090_smt"}},{"foreign":{"field":"related-observations[].observation-uuid","model":"assessment-results","slot":"6b","value":"28e28d31-4428-4ff5-8c9e-ea1198dfb552"},"how":"reference","primary":{"field":"observations[].uuid","model":"assessment-results","slot":"6b"}}],"to":"result"}],"introduced":{"field":"controls[].id","model":"catalog","note":"The product catalog defines the rule as a control, using the same OSCAL structure as a regulatory control. The chain starts from the control id.","slot":"1","value":"UBTU-24-600090"}},"component-first":{"hops":[{"from":"rule","how":"composite","note":"The check references both a rule id and a target component uuid. A rule id is unique only within the declaring component.","pairs":[{"foreign":{"field":"checks[].rule-id","model":"component-definition","slot":"3","value":"ubtu24_data_at_rest_encrypted"},"how":"composite","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"checks[].target-component-uuid","model":"component-definition","slot":"3","value":"5ca997b3-bb3e-4c7a-8969-69ed44577d47"},"how":"composite","primary":{"field":"components[].uuid","model":"component-definition","slot":"1","value":"5ca997b3-bb3e-4c7a-8969-69ed44577d47"}}],"to":"check"},{"from":"rule","how":"reference","note":"The component definition contains both references. Control implementations already link components to controls; the proposed implementing-rules assembly adds references to individual rules.","pairs":[{"foreign":{"field":"implemented-requirements[].implementing-rules[].rule-id","model":"component-definition","slot":"2","value":"ubtu24_data_at_rest_encrypted"},"how":"reference","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"implemented-requirements[].control-id","model":"component-definition","slot":"2","value":"sc-28"},"how":"reference","primary":{"field":"controls[].id","model":"catalog","slot":"2","value":"sc-28","where":"the framework catalog"}}],"to":"control"},{"from":"check","how":"containment","note":"The validation component contains the checks executed by the engine. Each additional engine is represented by a separate validation component.","pairs":[{"foreign":{"field":"no field","model":"component-definition","slot":"3"},"how":"containment","primary":{"field":"components[].uuid","model":"component-definition","slot":"5","value":"b3c8813d-d479-450a-8178-fbbf846faccf","where":"the validation component"}}],"to":"runtime"},{"from":"runtime","how":"reference","note":"The proposed implementing-rules assembly references the rule supporting the claim, allowing a consumer to trace the claim to the check through OSCAL references.","pairs":[{"foreign":{"field":"by-components[].implementing-rules[].rule-id","model":"system-security-plan","slot":"6a","value":"ubtu24_data_at_rest_encrypted"},"how":"reference","primary":{"field":"components[].rules[].id","model":"component-definition","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},{"foreign":{"field":"by-components[].component-uuid","model":"system-security-plan","slot":"6a","value":"534b356b-0de1-48d4-8536-5d41ed717456"},"how":"reference","primary":{"field":"system-implementation.components[].uuid","model":"system-security-plan","slot":"6a"}}],"to":"claim"},{"from":"runtime","how":"reference","note":"The observation identifies the check and host, allowing different outcomes for two machines within the same system boundary to be recorded separately.","pairs":[{"foreign":{"field":"observations[].assessment-check-id","model":"assessment-results","slot":"6b","value":"SV-270747r1066730_rule"},"how":"reference","primary":{"field":"checks[].id","model":"component-definition","slot":"3","value":"SV-270747r1066730_rule"}},{"foreign":{"field":"observations[].subjects[].subject-uuid","model":"assessment-results","slot":"6b","value":"06297a03-cae0-414b-8332-2fc882f81aa1"},"how":"reference","primary":{"field":"system-implementation.inventory-items[].uuid","model":"system-security-plan","slot":"4"}}],"to":"result"},{"from":"result","how":"none","note":"The example result contains observations but no findings. No finding target identifies the control, and no finding status records whether the objective was satisfied.","pairs":[{"foreign":{"field":"no field","model":"assessment-results","slot":"6b"},"how":"none","primary":{"field":"no field","model":"catalog","slot":"2"}}],"to":"control"}],"introduced":{"field":"components[].rules[].id","model":"component-definition","note":"The proposed rules assembly defines the rule on the product component. The chain starts from the rule id within that component definition.","slot":"1","value":"ubtu24_data_at_rest_encrypted"}},"executable-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 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, and the plan of record is untouched, 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":"A parent contains the child directly; no key matching or dereferencing is needed."},{"key":"reference","label":"Reference","meaning":"A schema-defined identifier reference resolves to a target identifier."},{"key":"name-match","label":"Name match","meaning":"Two strings match by convention. The schema does not enforce the relationship, so a mismatch may go undetected."},{"key":"composite","label":"Composite key","meaning":"Two fields jointly identify a target. Either field alone may identify the wrong target or no target."},{"key":"none","label":"No join","meaning":"No field directly connects the entries. A consumer must follow other relationships, or the connection is absent."}],"intro":"The chain connects a rule to checks, implementation claims and assessment results. Each step identifies the relationships a consumer must resolve and the fields used to resolve those relationships.","note":"The join chain connects rule definitions, checks, implementation claims and assessment results. Each relationship identifies a foreign key and the corresponding primary key. Values match the two example rules on the six questions page; tools/verify.py checks each value against those encodings.","stages":[{"key":"rule","label":"Rule","meaning":"where the rule is introduced","slot":"1"},{"key":"control","label":"Control","meaning":"the framework control served by the rule","slot":"2"},{"key":"check","label":"Check","meaning":"the test of the rule","slot":"3"},{"key":"runtime","label":"Runtime","meaning":"what executes the check","slot":"5"},{"key":"claim","label":"Claim","meaning":"the system owner's statement of implementation","slot":"6a"},{"key":"result","label":"Result","meaning":"what an assessment recorded","slot":"6b"}],"step_order":[["rule","check"],["rule","control"],["check","runtime"],["runtime","claim"],["runtime","result"],["claim","result"],["result","control"]],"title":"How the answers connect"},"data/model-icons.json":{"icons":{"assessment-plan":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"height":"30","rx":"3","soft":false,"stroke-width":"2.27","tag":"rect","width":"24","x":"20","y":"18"},{"d":"M26 15H38V19H26V15Z","soft":false,"stroke-linejoin":"round","stroke-width":"2.27","tag":"path"},{"d":"M26 26L38 26","soft":true,"stroke-linecap":"round","stroke-width":"2.27","tag":"path"},{"d":"M26 32L34 32","soft":true,"stroke-linecap":"round","stroke-width":"2.27","tag":"path"},{"cx":"36","cy":"38","r":"5","soft":false,"stroke-width":"2.27","tag":"circle"},{"d":"M36 36V38H38","soft":false,"stroke-linecap":"round","stroke-width":"1.70","tag":"path"}],"source":"assessment_plan_model.svg","view_box":"11.1907 10.6907 41.6186 41.6186"},"assessment-results":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"height":"32","rx":"3","soft":false,"stroke-width":"2.21","tag":"rect","width":"28","x":"18","y":"16"},{"d":"M24 24L27 27L33 21","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M24 34L27 37L33 31","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M37 24L40 24","soft":true,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M37 34L40 34","soft":true,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"}],"source":"assessment_results_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"catalog":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"d":"M18 18H30L34 22V48L27 45H18V18Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.08","tag":"path"},{"d":"M46 18H34L30 22V48L37 45H46V18Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.08","tag":"path"},{"d":"M22 26L28 26","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M22 32L28 32","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M36 26L42 26","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"},{"d":"M36 32L42 32","soft":true,"stroke-linecap":"round","stroke-width":"2.08","tag":"path"}],"source":"catalog_model.svg","view_box":"13.0728 14.0728 37.8544 37.8544"},"component-definition":{"authored_box":"0 0 64 64","layer":"implementation","shapes":[{"d":"M32 16L46 24V40L32 48L18 40V24L32 16Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M32 16V32M32 32L46 24M32 32L18 24","soft":true,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 32L32 40L46 32","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"}],"source":"component_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"mapping-collection":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"cx":"22","cy":"22","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"cx":"42","cy":"22","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"cx":"32","cy":"42","r":"5","soft":false,"stroke-width":"2.08","tag":"circle"},{"d":"M26 24L38 24","soft":true,"stroke-dasharray":"2 2","stroke-width":"2.08","tag":"path"},{"d":"M25 26L29 38","soft":true,"stroke-width":"2.08","tag":"path"},{"d":"M39 26L35 38","soft":true,"stroke-width":"2.08","tag":"path"}],"source":"control_mapping_model.svg","view_box":"13.0728 13.0728 37.8544 37.8544"},"plan-of-action-and-milestones":{"authored_box":"0 0 64 64","layer":"assessment","shapes":[{"cx":"32","cy":"32","r":"16","soft":false,"stroke-width":"3.25","tag":"circle"},{"cx":"32","cy":"32","r":"10","soft":true,"stroke-width":"3.25","tag":"circle"},{"cx":"32","cy":"32","fill":"ink","r":"3","soft":false,"tag":"circle"},{"d":"M32 12V8M32 56V52M12 32H8M56 32H52","soft":false,"stroke-linecap":"round","stroke-width":"3.25","tag":"path"}],"source":"plan_of_action_and_milestones_model.svg","view_box":"1.7625 1.7625 60.475 60.475"},"profile":{"authored_box":"0 0 64 64","layer":"control","shapes":[{"d":"M18 20H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 32H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"d":"M18 44H46","soft":false,"stroke-linecap":"round","stroke-width":"2.21","tag":"path"},{"cx":"26","cy":"20","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"},{"cx":"38","cy":"32","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"},{"cx":"30","cy":"44","fill":"chip","r":"4","soft":true,"stroke-width":"2.21","tag":"circle"}],"source":"profile_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"},"system-security-plan":{"authored_box":"0 0 64 64","layer":"implementation","shapes":[{"d":"M20 16H36L44 24V48H20V16Z","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M36 16V24H44","soft":false,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"},{"d":"M32 30V40M32 30L28 31L26 33L26 36L28 39L32 42L36 39L38 36L38 33L36 31L32 30Z","soft":true,"stroke-linecap":"round","stroke-linejoin":"round","stroke-width":"2.21","tag":"path"}],"source":"system_security_plan_model.svg","view_box":"11.8161 11.8161 40.3678 40.3678"}},"layers":{"assessment":{"label":"Assessment layer","models":["assessment-plan","assessment-results","plan-of-action-and-milestones"]},"control":{"label":"Control layer","models":["catalog","profile","mapping-collection"]},"implementation":{"label":"Implementation layer","models":["component-definition","system-security-plan"]}},"note":"One icon per OSCAL model, generated by tools/model_icons.py from the authored files in assets/images. Geometry only: the colour is a layer token applied by the stylesheet, and the chip behind the glyph is a CSS box. Do not edit this file; edit the SVG and regenerate."},"data/oscal-artifacts.json":{"note":"tools/oscal_artifacts.py: author data/oscal-artifacts.json.","publishers":[{"files":[{"bytes":924964,"counts":{"controls":452,"groups":77},"file":"catalogs/aws_security-hub.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/catalogs/aws_security-hub.oscal.json","href_external":true,"model":"catalog","model_label":"Catalog","title":"AWS Security Hub Controls"},{"bytes":16118,"counts":{"components":3,"implemented requirements":4,"service":1,"software":2},"file":"component-definitions/acm.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/acm.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Certificate Manager"},{"bytes":27913,"counts":{"components":8,"implemented requirements":12,"service":2,"software":6},"file":"component-definitions/cloudtrail.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/cloudtrail.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS CloudTrail"},{"bytes":12332,"counts":{"components":1,"service":1},"file":"component-definitions/config.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/config.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Config"},{"bytes":43914,"counts":{"components":18,"implemented requirements":43,"service":1,"software":17},"file":"component-definitions/iam.oscal.json","href":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/component-definitions/iam.oscal.json","href_external":true,"model":"component-definition","model_label":"Component definition","title":"AWS Identity and Access Management"}],"full_name":"Option A","key":"catalog-first","name":"Catalog-first","option":"Option A","repo":"https://github.com/awslabs/oscal-content-for-aws-services","rollup":{"components":861,"count":230,"model_label":"Component definition","note":"One per service. Four are listed above as examples; the rest follow the same shape.","software":429},"root":"AWS/oscal-content-for-aws-services-main","totals":{"Catalog":1,"Component definition":230}},{"files":[{"bytes":1106,"counts":{"components":1,"validation":1},"file":"ansible-validation-component-definition.json","href":"examples/component-first/ansible-validation-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo validation component definition"},{"bytes":5105,"counts":{"activities":0,"tasks":1},"file":"assessment-plan.json","href":"examples/component-first/assessment-plan.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"Assessment Plan"},{"bytes":4275,"counts":{"findings":0,"observations":1,"results":1},"file":"assessment-result.json","href":"examples/component-first/assessment-result.json","href_external":false,"model":"assessment-results","model_label":"Assessment results","title":"Assessment Result"},{"bytes":2525,"counts":{"components":1,"implemented requirements":2,"rules":2,"service":1},"file":"cos-component-definition.json","href":"examples/component-first/cos-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":5230,"counts":{"components":1,"implemented requirements":7,"rules":3,"service":1},"file":"idservice-component-definition.json","href":"examples/component-first/idservice-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo component definition"},{"bytes":1297,"counts":{"components":1,"validation":1},"file":"oscap-validation-component-definition.json","href":"examples/component-first/oscap-validation-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"Demo validation component definition"}],"full_name":"Option B","key":"component-first","name":"Component-first","option":"Option B","repo":null,"rollup":null,"root":"IBM","totals":{"Assessment plan":1,"Assessment results":1,"Component definition":4}},{"files":[{"bytes":308830,"counts":{"activities":7,"steps":128,"tasks":0},"file":"CISA BOD 25-01/ap-cisa-scuba-agnostic.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-agnostic.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":325728,"counts":{"activities":7,"steps":128,"tasks":1},"file":"CISA BOD 25-01/ap-cisa-scuba-maester.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-maester.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":293862,"counts":{"activities":7,"steps":128,"tasks":1},"file":"CISA BOD 25-01/ap-cisa-scuba-scubagear.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ap-cisa-scuba-scubagear.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CISA SCuBA Assessment Plan"},{"bytes":298328,"counts":{"findings":128,"observations":128,"results":1},"file":"CISA BOD 25-01/ar-cisa-scuba-scubagear.json","href":"examples/assessment-first/CISA%20BOD%2025-01/ar-cisa-scuba-scubagear.json","href_external":false,"model":"assessment-results","model_label":"Assessment results","title":"CISA SCuBA Assessment Results - M365 Tenant"},{"bytes":19829,"counts":{"activities":8,"steps":8,"tasks":1},"file":"CISA BOD 25-01/assessment-plan.json","href":"examples/assessment-first/CISA%20BOD%2025-01/assessment-plan.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"Entra ID cATO Assessment Plan"},{"bytes":39652,"counts":{},"file":"CISA BOD 25-01/sample-ssp.json","href":"examples/assessment-first/CISA%20BOD%2025-01/sample-ssp.json","href_external":false,"model":"system-security-plan","model_label":"System security plan","title":"Sample ScubaGear System Security Plan"},{"bytes":423087,"counts":{"activities":72,"steps":144,"tasks":8},"file":"Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","href":"examples/assessment-first/Center%20for%20Internet%20Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CIS PostgreSQL 18 Benchmark"},{"bytes":1768114,"counts":{"activities":53,"steps":616,"tasks":7},"file":"Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","href":"examples/assessment-first/Center%20for%20Internet%20Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"CIS Ubuntu Linux 24.04 LTS Benchmark"},{"bytes":821083,"counts":{"activities":118,"steps":236,"tasks":2},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/epas.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Postgres Advanced Server"},{"bytes":823183,"counts":{"activities":111,"steps":222,"tasks":2},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/postgres16.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Postgres 16"},{"bytes":2454926,"counts":{"activities":366,"steps":732,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel8.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/rhel8.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Red Hat Enterprise Linux 8"},{"bytes":3051725,"counts":{"activities":446,"steps":892,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/rhel9.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/rhel9.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Red Hat Enterprise Linux 9"},{"bytes":1310065,"counts":{"activities":188,"steps":376,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu22.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/ubuntu22.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Ubuntu 22.04 LTS"},{"bytes":1341083,"counts":{"activities":194,"steps":388,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/ubuntu24.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Ubuntu 24.04 LTS"},{"bytes":1940344,"counts":{"activities":282,"steps":564,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2019.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2019.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2019"},{"bytes":1858865,"counts":{"activities":282,"steps":564,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2022.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2022.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2022"},{"bytes":1867817,"counts":{"activities":284,"steps":568,"tasks":3},"file":"DISA/STIG_XCCDF to OSCAL Assessment Plans/win2025.json","href":"examples/assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/win2025.json","href_external":false,"model":"assessment-plan","model_label":"Assessment plan","title":"STIG Windows Server 2025"}],"full_name":"Option C","key":"assessment-first","name":"Assessment-first","option":"Option C","repo":null,"rollup":null,"root":"Easy Dynamics","totals":{"Assessment plan":15,"Assessment results":1,"System security plan":1}},{"document":{"href":"examples/executable-first/executable-assessment-methods.md","label":"Executable Assessment Methods, a concept note, September 2026"},"files":[{"bytes":498246,"counts":{"automation scripts":164,"components":1,"implemented requirements":49,"validation":1},"file":"cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json","href":"examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json","href_external":false,"model":"component-definition","model_label":"Component definition","title":"CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, as a validation component carrying automation scripts"},{"bytes":1849732,"counts":{"controls":312,"groups":7},"file":"cis-ubuntu-24-04-lts-benchmark-catalog.json","href":"examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","href_external":false,"model":"catalog","model_label":"Catalog","title":"CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, as a catalog with executable assessment methods"},{"bytes":27613,"counts":{"controls selected":251,"imports":1},"file":"cis-ubuntu-24-04-lts-level-1-server-profile.json","href":"examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-server-profile.json","href_external":false,"model":"profile","model_label":"Profile","title":"CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 1 - Server"},{"bytes":26951,"counts":{"controls selected":245,"imports":1},"file":"cis-ubuntu-24-04-lts-level-1-workstation-profile.json","href":"examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-workstation-profile.json","href_external":false,"model":"profile","model_label":"Profile","title":"CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 1 - Workstation"},{"bytes":34758,"counts":{"controls selected":312,"imports":1},"file":"cis-ubuntu-24-04-lts-level-2-server-profile.json","href":"examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-server-profile.json","href_external":false,"model":"profile","model_label":"Profile","title":"CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 2 - Server"},{"bytes":34483,"counts":{"controls selected":309,"imports":1},"file":"cis-ubuntu-24-04-lts-level-2-workstation-profile.json","href":"examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-workstation-profile.json","href_external":false,"model":"profile","model_label":"Profile","title":"CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 2 - Workstation"},{"bytes":175398,"counts":{"mappings":1,"maps":286},"file":"cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json","href":"examples/executable-first/oscal/cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json","href_external":false,"model":"mapping-collection","model_label":"Mapping collection","title":"CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0 mapped to NIST SP 800-53 Revision 5"},{"bytes":849310,"counts":{"controls altered":79,"controls selected":79,"imports":1,"parts added":582},"file":"nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","href":"examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","href_external":false,"model":"profile","model_label":"Profile","title":"NIST SP 800-53 Revision 5, with the Canonical Ubuntu 24.04 LTS Security Technical Implementation Guide V1R5 as executable assessment methods"}],"full_name":"Option D","key":"executable-first","name":"Executable-first","note":"No proponent has published OSCAL for this approach. What exists is a concept note, linked below, and the documents listed here were generated by tools/executable_first_corpus.py from the CIS Benchmark and the DISA STIG for Ubuntu 24.04 in the shape the note proposes. They are counted like any other corpus and they are the site's, not a proponent's.","option":"Option D","repo":null,"rollup":null,"root":null,"totals":{"Catalog":1,"Component definition":1,"Mapping collection":1,"Profile":5}}]},"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."}],"executable-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."}],"executable-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."}],"executable-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."}],"executable-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."}],"executable-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."}],"executable-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."}],"executable-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":{"generated_at":"2026-09-16T16:07:24+00:00","snippet_count":43,"snippets":[{"approach":"assessment-first","bytes":4370,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-activity-v259312","language":"json","pointer":"/assessment-plan/local-definitions/activities/100","sha256_of_content":"f2968c0009fd012a241dc8e3e86173ac47bb4475624d3ccd01d77efd53964e31","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG activity V-259312"},{"approach":"assessment-first","bytes":6648,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-sc28-v270747","language":"json","pointer":"/assessment-plan/local-definitions/activities/101","sha256_of_content":"f6505f9312ba86546b17001b14b7ad797cd83fb68699749488086edb5ac0e8f2","sha256_of_source_file":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","title":"STIG activity V-270747, SC-28"},{"approach":"assessment-first","bytes":1976,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-step-props","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0","sha256_of_content":"e369bbc630cc85afc2a07e99fca48e213cabd815f4bc02ef1ec15034d2b7c33a","sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS audit step props"},{"approach":"assessment-first","bytes":999,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-remediation-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/1","sha256_of_content":"953c73006718d3632307bf47755dc4924e6164f3c03a53e96a3f3d058a4883bd","sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS remediation step"},{"approach":"assessment-first","bytes":270,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","sha256_of_content":"c3298e80edbf681c6da3e2965d161f81804db9d940539e41f77a19cf21e544e0","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA activity context prop"},{"approach":"assessment-first","bytes":928,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","sha256_of_content":"60c8183fb14d09b5f27513b84f394bf8a48670eadaf2f73fd834bc7300011240","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-assets"},{"approach":"assessment-first","bytes":1828,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","sha256_of_content":"ec5873d16ce6100d9be8cce518945b3aee95c50d2ae1ace4e298b860f8433b8f","sha256_of_source_file":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653","slot":"3","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-maester.json","title":"CISA step context prop"},{"approach":"assessment-first","bytes":243,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-related-controls","language":"json","pointer":"/assessment-plan/local-definitions/activities/100/related-controls","sha256_of_content":"2f52e4b5053678f3323139865183d634ff1206753079feff31bcaff76f53c93e","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"2","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG related-controls, the control tie"},{"approach":"assessment-first","bytes":197,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-step-reviewed","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0/reviewed-controls","sha256_of_content":"52c2919dc4f34fd2fbc5907450582b436e7e929a031c2bdb5a9c83d4ae18b30d","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"2","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA step reviewed-controls"},{"approach":"assessment-first","bytes":127,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-subjects-includeall","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"60d2f0f2a596673779c7804e0c6ea2bcc0609b41d54dc4d3c698be49bf268a82","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"4","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG assessment-subjects, include-all"},{"approach":"assessment-first","bytes":277,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","sha256_of_content":"01c9afa2b4ee716f8534f4a2f12777d7202d741c06a7d5182619ca8f3afbc3fe","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"4","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-subjects, one inventory item"},{"approach":"assessment-first","bytes":2946,"extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"e5939a58c062351efa21b423729e40beeb72d3e13dd32757af065e4709dfbd60","sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA task, with timing"},{"approach":"assessment-first","bytes":27,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","sha256_of_content":"84d4c12b8a05a19b8f99d8305498e5760d8bb8dfe987a2ecf4c38abd43d7557b","sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"meta","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG import-ssp, an unresolved placeholder"},{"approach":"assessment-first","bytes":94,"extracted_at":"2026-08-22T18:44:16+00:00","id":"ez-cisa-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","sha256_of_content":"b26671d77e040a71e3470a5a13e0f043d7b130bf7b7688629f6405f136b1b7d2","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"import-ssp, resolving to a resource in the same document"},{"approach":"assessment-first","bytes":357,"extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/1","sha256_of_content":"401a0f63ea6221c571902ef0ba27bd50cce9fe2baa09b0cf520e48fa20539f1d","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The resource a resolved import-ssp lands on"},{"approach":"assessment-first","bytes":686,"extracted_at":"2026-08-22T18:46:12+00:00","id":"ez-cisa-no-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/0","sha256_of_content":"e0431570c0eb7d51ecec3ca35a340ae8c920c4c6afc08bb6a36760af82ef1e18","sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The alternative resource, where no OSCAL system security plan exists"},{"approach":"assessment-first","bytes":466,"extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ar-finding","language":"json","pointer":"/assessment-results/results/0/findings/0","sha256_of_content":"4e3cfedd3c68517765d05d2cd46cdc0124a29c593c889cba16035c8ab84c1fe0","sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"A finding, targeting an objective"},{"approach":"assessment-first","bytes":762,"extracted_at":"2026-08-22T18:43:41+00:00","id":"ez-cisa-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","sha256_of_content":"631850409afd117649f1abec4da6e649bab0d2d4226d2a28f77d9918ec506b3a","sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"The observation it rests on, and what was examined"},{"approach":"assessment-first","bytes":469,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-resolution-status","language":"json","pointer":"/assessment-plan/reviewed-controls/control-selections/0","sha256_of_content":"4befe7d29d300effc4bdd88c120c2c1f1c00497fc28990444f62c198bc111d04","sha256_of_source_file":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8","slot":"meta","source":"Easy Dynamics/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","title":"CIS resolution status"},{"approach":"catalog-first","bytes":1402,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm2-control","language":"json","pointer":"/catalog/groups/0/controls/1","sha256_of_content":"a7f2e132f5d8e27309dbec9c9b114ed87105ee326046773c5cfe05f5da5b1ab4","sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"ACM.2, the control"},{"approach":"catalog-first","bytes":1177,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-rsa-check-component","language":"json","pointer":"/component-definition/components/2","sha256_of_content":"c4df1c40cb50ca7dd6e7d18862853fef78189e789623abf1c177ea49c9d0b3a1","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"3","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"acm-certificate-rsa-check, the check component"},{"approach":"catalog-first","bytes":538,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-backmatter-source","language":"json","pointer":"/component-definition/back-matter","sha256_of_content":"5e916dfa3cdf4d22fbbf601a1f6b18bc69b0a65d9367e906c26ba11901ab03cd","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"Back-matter, source to the catalog"},{"approach":"catalog-first","bytes":1444,"extracted_at":"2026-08-21T03:10:41+00:00","id":"aws-control-cloudtrail2","language":"json","pointer":"/catalog/groups/15/controls/2","sha256_of_content":"ae48dd920cb756ba4afaec14989d62d63c1954361757346114e807768609940b","sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"CloudTrail.2, the control"},{"approach":"catalog-first","bytes":1439,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-input-parameter","language":"json","pointer":"/component-definition/components/2/props","sha256_of_content":"b8d9cec13e53ca016cfe380b637fec8adfe353e9098e37d90bd28cacf98dcee1","sha256_of_source_file":"940cab9d3328d5ff55e6c69fbfae6fd4e846873d07f70ef7c096651bc8f750ab","slot":"1","source":"AWS/oscal-content-for-aws-services-main/component-definitions/iam.oscal.json","title":"InputParameter props, the parameter mechanism"},{"approach":"catalog-first","bytes":493,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-service-rollup","language":"json","pointer":"/component-definition/components/0/control-implementations/0","sha256_of_content":"dd53d5bd8e01cbaa2b198cf7504ece6374b931ec86c373ae5c9003e34d75dd44","sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"AWS Certificate Manager, the service roll-up"},{"approach":"catalog-first","bytes":1367,"extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-config-service-bare","language":"json","pointer":"/component-definition/components/0","sha256_of_content":"3b3b0c533e8fe9ebc892b5cdf0003bb265591ae3486e5d6317aa847480d88541","sha256_of_source_file":"d5049e46d7a1251932be3e74c1f9bace606ac9b5f5542249ccb884171394a6e7","slot":"5","source":"AWS/oscal-content-for-aws-services-main/component-definitions/config.oscal.json","title":"AWS Config, the engine that runs the checks"},{"approach":"component-first","bytes":1909,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-cos-component","language":"json","pointer":"/component-definition/components/0","sha256_of_content":"63bda68a0ec328946a2ba363442053d4976a7ea78ccc27da761f4dbfc9feae4b","sha256_of_source_file":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a","slot":"1","source":"IBM/cos-component-definition.json","title":"COS component, carrying rules"},{"approach":"component-first","bytes":686,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-statement-rules","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/0","sha256_of_content":"d835c9264269a53f2fbbb988dfe83509b7610a445742300ace8703259dbb3edd","sha256_of_source_file":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf","slot":"2","source":"IBM/idservice-component-definition.json","title":"implementing-rules on ia-5.1"},{"approach":"component-first","bytes":1106,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-validation-ansible","language":"json","pointer":"$","sha256_of_content":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","sha256_of_source_file":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","slot":"3","source":"IBM/ansible-validation-component-definition.json","title":"Ansible validation component, and its checks"},{"approach":"component-first","bytes":624,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-activity","language":"json","pointer":"/assessment-plan/local-defintions","sha256_of_content":"b0157c12fb61e61809b3970895e3d1e9bba4b8c8bfe31c7f20e01ac292c1b252","sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"5","source":"IBM/assessment-plan.json","title":"AP activity, binding check-ids"},{"approach":"component-first","bytes":907,"extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-task-subjects","language":"json","pointer":"/assessment-plan/tasks/0","sha256_of_content":"9852eeea94dab48f8ee5f7351c3ecc86a42be3e2dfd594626cae759ba163e9cd","sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"4","source":"IBM/assessment-plan.json","title":"AP task, subjects and platform"},{"approach":"component-first","bytes":1125,"extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","sha256_of_content":"eb0d665abc0dc6c1d6528291f5888816e6db04a427d7aaa6bd52bc395d1f9595","sha256_of_source_file":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806","slot":"6b","source":"IBM/assessment-result.json","title":"AR observation, carrying a result"},{"approach":"executable-first","bytes":2634,"extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-objective-and-param","language":"json","pointer":"/catalog/groups/0/groups/0/groups/0/controls/0","sha256_of_content":"f51d91c1bf53c2d13b49e35d056769df229e33d46bbf399f74821ff6232dc97e","sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"1","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"CIS 1.1.1.1 as a control: the objective, and the exported value as a parameter"},{"approach":"executable-first","bytes":1644,"extracted_at":"2026-09-16T16:07:24+00:00","id":"pf-stig-objective-sc-28","language":"json","pointer":"/profile/modify/alters/63/adds/0/parts/0","sha256_of_content":"f10c8fd914a74654b6c3042dd642e7ee9d893857edaf19096677e82f53be56eb","sha256_of_source_file":"ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697","slot":"1","source":"site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","title":"STIG V-270747 as an objective a profile adds to SC-28"},{"approach":"executable-first","bytes":1584,"extracted_at":"2026-09-16T16:07:24+00:00","id":"pf-stig-import","language":"json","pointer":"/profile/imports/0","sha256_of_content":"35e6ca62136b9af1bc1fdb3afc5e499b32115cb4c65ec727cce05d23d46c95f0","sha256_of_source_file":"ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697","slot":"2","source":"site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","title":"The profile imports the framework catalog and names the controls it alters"},{"approach":"executable-first","bytes":328,"extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-map-1-1-1-1","language":"json","pointer":"/mapping-collection/mappings/0/maps/0","sha256_of_content":"28e1c3ca334610c990206f86fa6034c129b7d3298e36c2505af6c3c6a3276415","sha256_of_source_file":"de1c04d1ffb7b1e82b8a1e3b41fc848a782790868c419e7e56bf96fedcb3a7ed","slot":"2","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json","title":"CIS 1.1.1.1 mapped to CM-7, from the benchmark's own reference"},{"approach":"executable-first","bytes":1779,"extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-method-1-1-1-1","language":"json","pointer":"/catalog/groups/0/groups/0/groups/0/controls/0/parts/3","sha256_of_content":"e474fa62ef41be7f1002a306ea121c2c711171eac381315af0f648ff622fe1a4","sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"3","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"CIS 1.1.1.1 assessment method, carrying the published audit script"},{"approach":"executable-first","bytes":387,"extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-script-resource","language":"json","pointer":"/catalog/back-matter/resources/52","sha256_of_content":"3c190001f21fcdb1840ed9c12fcf5f95df549387249ff713b6878a2fb7d7e9c6","sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"3","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"The SCE script the method links to, as a back-matter resource"},{"approach":"executable-first","bytes":957,"extracted_at":"2026-09-16T16:07:24+00:00","id":"pf-stig-method-sc-28","language":"json","pointer":"/profile/modify/alters/63/adds/0/parts/1","sha256_of_content":"a0be2fa7f915335f745e451621b93bfcac31a2e3ca269db5861dc88c8ea1b264","sha256_of_source_file":"ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697","slot":"3","source":"site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","title":"STIG V-270747 check text as a method beside its objective"},{"approach":"executable-first","bytes":144,"extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-platform","language":"json","pointer":"/catalog/groups/0/groups/0/groups/0/controls/0/parts/3/props/1","sha256_of_content":"3659c3ae2934d01de667ac7f07e65de3ba833dd78c69db7bfc62eb176b9d3ffe","sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"4","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"The platform a method applies to"},{"approach":"executable-first","bytes":557,"extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-run-props","language":"json","pointer":"/catalog/groups/0/groups/0/groups/0/controls/0/parts/3/props","sha256_of_content":"92190f0d9ea4b021732deda21c1a5299b1f26a05bdeb071bfb69afd2492cdf12","sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"5","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"What an executor reads: the method's props"},{"approach":"executable-first","bytes":2090,"extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-rules-requirement","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/18","sha256_of_content":"3f4904a75d7438c1c0a6ef4e98ec5475d5295d78d2ce4d52b4ea39b12492e0d2","sha256_of_source_file":"4e08c03e080234a07ed6155e06f6b0c0756e64d28210c33473c92ffa2cb95929","slot":"3","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json","title":"CIS Control 8.9 as an implemented requirement carrying an audit and a remediation script, the Rules shape"},{"approach":"executable-first","bytes":1203,"extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-rules-script-1-1-1-1","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/8/automation-scripts/0","sha256_of_content":"cd7cf55a6c63c52a8fea1db4bac816192aab98d6627cfc1a35f4af2e0a09ee21","sha256_of_source_file":"4e08c03e080234a07ed6155e06f6b0c0756e64d28210c33473c92ffa2cb95929","slot":"3","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json","title":"CIS 1.1.1.1 audit script as an automation-scripts object, the Rules shape"}],"source_inputs":{"sources":[{"approach":"component-first","directory":"examples/component-first","expected_files":6,"key":"ibm","prefix":"IBM"},{"approach":"assessment-first","directory":"examples/assessment-first","expected_files":19,"key":"easy-dynamics","prefix":"Easy Dynamics"},{"approach":"catalog-first","archive_bytes":379596,"archive_sha256":"f309b59344560b88a699c5908fbc70c51c7a0e8e0339d901b1285b9c8d804a18","directory":".cache/oscal-sources/aws/4a1779ffb556c4ab8fb3dad94a19d4d198116803","file_base":"https://github.com/awslabs/oscal-content-for-aws-services/blob/4a1779ffb556c4ab8fb3dad94a19d4d198116803/","json_files":231,"key":"aws","prefix":"AWS/oscal-content-for-aws-services-main","repository":"awslabs/oscal-content-for-aws-services","revision":"4a1779ffb556c4ab8fb3dad94a19d4d198116803","url":"https://codeload.github.com/awslabs/oscal-content-for-aws-services/tar.gz/4a1779ffb556c4ab8fb3dad94a19d4d198116803"}],"version":1},"source_lock":"tools/source-lock.json"},"data/questions.json":{"intro":"These questions identify unresolved design choices, not recommended changes. The analysis distinguishes what the OSCAL examples demonstrate from what remains open across models and approaches.","note":"Editorial analysis questions maintained in this repository, grouped by issues shared across OSCAL and issues specific to each approach. Each question includes its reasoning; the OSCAL examples provide evidence without settling the design choices.","sections":[{"intro":"Gaps in the models themselves. None is answered by choosing an approach, and each changes what all 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":"XCCDF already represents benchmark checklists. OSCAL could carry equivalent content or connect checklist references to implementation and assessment records. These choices produce different artifacts, translation work and maintenance obligations. The OSCAL examples do not establish which boundary best supports interoperable hardening workflows."},{"id":"rule-metadata","q":"Where does the metadata that describes a rule go?","why":"Rule metadata includes severity, weight, rationale and whether a check is automated or manual. The AWS and DISA OSCAL examples use namespaced properties for severity rather than a dedicated field. Consumers need shared conventions to interpret this content. Which metadata belongs on a rule, and whether shared namespaces or schema fields should carry it, remains open."},{"id":"remediation","q":"Where does remediation land?","why":"The AWS catalog uses remediation links, while the STIG and CIS assessment plans carry remediation steps. The component-first examples do not carry remediation. These conventions do not provide a dedicated rule-remediation field. OSCAL's plan of action and milestones addresses a particular finding, not a reusable fix for every instance of a condition. Which structure should carry reusable remediation instructions remains open."}]},{"intro":"The rule is a control in a catalog. What is unsettled is how many documents that produces and where the outcome lands.","key":"catalog-first","label":"Catalog-first","questions":[{"id":"one-ssp","q":"Do many catalogs converge into one profile and one plan of record, or does each catalog need its own?","why":"A single plan of record could answer a profile merging the catalogs that apply to a system. Separate plans could instead answer each catalog. These structures produce different file counts and response locations, and change whether benchmark outcomes sit beside regulatory outcomes. The worked scenario assumes convergence and counts 18 files; the question is whether that structure meets implementation and assessment needs."},{"id":"requirement-level","q":"If OSCAL gained a field for requirement level, how much of this disagreement would be left?","why":"OSCAL has no dedicated core field distinguishing shall, should and may. The examples can carry such labels in properties, but consumers need conventions to interpret them. Catalog-first puts benchmark and regulatory controls into the same profile. It remains unclear how much model-placement disagreement concerns binding force rather than document structure, and whether a shared requirement-level field would reduce it."},{"id":"control-type","q":"Should a control declare its type, so a regulatory control and a technical hardening control can be told apart?","why":"The catalog/profile model can combine regulatory controls with technical hardening controls, but it has no dedicated core field distinguishing those kinds. Tools would need a shared property convention or schema support to report regulatory coverage separately from hardening coverage. This question concerns the kind of requirement, distinct from whether its requirement level is shall, should or may."},{"id":"paper-cat-1","q":"How should benchmark profiles compose with regulatory profiles as the number of controls grows?","why":"Combining benchmark and regulatory controls increases the work of resolving imports, selections, exclusions and parameter values. The question is how tools should compose and maintain those profiles at scale without obscuring which source supplied a requirement or how a tailoring decision changes downstream content."},{"id":"paper-cat-2","q":"Where should benchmark outcomes be recorded, in SSP implementation claims or assessment results, and how should tools distinguish them?","why":"An SSP by-component response describes an implementation claim, while assessment results record evidence and outcomes. A benchmark workflow may need both, but they answer different questions. Tools need to distinguish intended configuration from observed satisfaction and preserve the relationship between the two records."}]},{"intro":"The rule sits on the component it configures. Open questions concern runner identification, importing component definitions and tailoring benchmark content.","key":"component-first","label":"Component-first","questions":[{"id":"which-cdef-maps","q":"Which component definition carries the tie to the framework, the one holding the rules or the one holding the checks?","why":"The control link is inline rather than held in a mapping collection. The software component definition holds rules, while the validation component definition holds checks; those artifacts may have different maintainers. A mapping provider could update either or both. The OSCAL examples do not establish which document should own that relationship or how duplicated mappings would stay consistent."},{"id":"proposal-1","q":"Should assessment platform usage be optional in an assessment plan?","why":"An assessment plan may describe a runner as a component, a platform using components, or a tool identified through properties. These alternatives leave open when an explicit assessment platform adds necessary information and when a component reference is sufficient for a consumer to execute or interpret a check."},{"id":"proposal-2","q":"When is an assessment component sufficient, and when is an assessment platform also needed?","why":"The OSCAL examples use different combinations of assessment-assets, assessment-platforms and components. They do not establish a shared rule for deciding whether a component alone identifies the runner or a platform must also describe its execution context. A consistent distinction would help consumers interpret equivalent workflows."},{"id":"proposal-3","q":"How should an assessment asset be associated with tasks or activities?","why":"A task identifies work to perform, while an assessment asset describes resources available to perform it. The component-first examples do not establish a complete, interoperable association between these structures. The question is which references should identify the runner for a particular task or activity."},{"id":"proposal-4","q":"How should an observation identify the assessment asset that produced it when several assets are declared?","why":"An assessment result may declare several assets, so naming an observation's producer requires an unambiguous relationship. The component-first result example does not establish a complete path from observation to producing asset. The open question is how consumers should recover that association without relying on tool-specific assumptions."},{"id":"paper-comp-1","q":"How should an SSP combine benchmark and vendor component definitions that describe the same system component?","why":"A system may use vendor component definitions alongside benchmark component definitions for the same software. Importing both can produce overlapping descriptions, rules and control implementations. It remains open whether an SSP should retain multiple OSCAL components, merge them, or use another convention to represent the single system component consistently."},{"id":"paper-comp-2","q":"Should desired-state values from benchmark component definitions be replaced with actual-state values in the SSP?","why":"Rules describe prescribed configuration, while an SSP records the system owner's implementation claims. Replacing prescribed values with actual values could lose the benchmark baseline; retaining only prescribed values could misrepresent implementation. The question is how to keep the two meanings distinct while preserving the relationship between benchmark requirements and the system."},{"id":"paper-comp-3","q":"Which benchmark context should enter an SSP, and how should tools filter component-definition content during import?","why":"Benchmark content can include rules, parameters, rationale and procedural detail, not all of which serves the same purpose in an SSP. Import tooling needs a policy for retaining or omitting that context. The open issue is how to reduce duplication without losing information needed to interpret an implementation claim."},{"id":"paper-comp-4","q":"How should component definitions support benchmark selection, exclusions and parameter tailoring?","why":"The component-first examples place parameters on proposed rules and set-parameters on control implementations. Those structures address parameter values but do not provide a profile's selection and exclusion workflow. How component definitions should support benchmark tailoring, including the scope and persistence of tailoring decisions, remains open."},{"id":"paper-comp-5","q":"Should assessment plans or assessment results support importing component definitions with benchmark context?","why":"The component-first examples carry check content into an assessment plan through assessment assets. That demonstrates one encoding, not a dedicated import mechanism for all benchmark context. The question is whether plans or results should support such imports directly and which rules, parameters and provenance would need to survive."}]},{"intro":"The rule is an activity in an assessment plan. The open question concerns tailoring requirements without losing their assessment context.","key":"assessment-first","label":"Assessment-first","questions":[{"id":"paper-ap-1","q":"How should assessment-plan benchmarks support tailoring available through catalogs and profiles?","why":"Activities and steps have no parameter assembly, so the assessment-first examples place required values in text. Tailoring can therefore require editing procedural content rather than selecting controls or setting parameter values through a profile. The question is how to support reusable, auditable tailoring without losing the assessment workflow."}]},{"intro":"The check's code travels in the OSCAL document. What is unsettled is which construct carries it, where it may sit, who may put code there, who owns the vocabulary that runs it, and what the executor matches against.","key":"executable-first","label":"Executable-first","questions":[{"id":"typed-assembly-or-props","q":"Does a future version add a typed assembly for the executable, or standardise the props on the released part?","why":"Two constructs carry code today. A typed assembly, the Rules construct, gives a validator the executor fields themselves and needs a version to ship; the released assessment-method part validates now and gives a validator nothing beyond the existence of a prop. The start page's section 6 states the trade aspect by aspect. Which side a future version takes decides whether the vocabulary lives in the schema or beside it, and neither the concept note nor the published proposal has been put to the Foundation as a schema change."},{"id":"which-assemblies-carry-code","q":"Which assemblies may carry an executable: a part on a control, an implemented requirement, a by-component, an activity?","why":"In 1.2.1 a part sits on a control and nowhere else, so the released construct is bound to the control layer, and an implemented requirement, a by-component and an activity have props, links and a description but no parts. The Rules construct sits wherever its schema puts it, on a component in both instances so far. Each home couples the code to something different, a requirement, a platform, or one assessment. The grid in section 6 shows two of six cells occupied."},{"id":"executable-reaches-ssp","q":"How does an executable on a control reach the system's plan of record?","why":"A check on a component reaches the system security plan through by-component, where the system's own responses live. A check on a control reaches it only through the profile the plan imports, and nothing on the by-component names the objective the check tests, which is why question 6a, how a system says it satisfies the rule in its own words, is the fourth approach's weakest cell. Whether a by-component may name an objective, or a part may sit on an implemented requirement, is the same question from the implementation layer."},{"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, does a mapping collection carry its tie 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 the note supplies no tie. The generated corpus turns the benchmark's own SP 800-53 references into a mapping collection, which reaches controls and statements and not parts, so it ties the recommendation and not the objective beside it. Whether that is the route the note intends is open."},{"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."},{"id":"param-names","q":"How does a parameter reach a script that expects a fixed variable name?","why":"The note exports every param on a control as an environment variable named after the param id. CIS-CAT's scripts read one variable, XCCDF_VALUE_REGEX, and OSCAL parameter ids are unique across a document, so the 82 controls that export a value cannot each declare a parameter of that name. The generated corpus carries the variable's name as the parameter's class, and the note's convention has no answer for it yet."}]}]},"data/scenario-evidence/nist-high-baseline.json":{"counts":{"base":188,"controls":370,"enhancements":182,"families":18},"fetched_at":"2026-08-23","note":"The control identifiers selected by the NIST SP 800-53 Revision 5 HIGH baseline profile. Stored so the scenario's control count can be recomputed here rather than quoted from memory.","oscal_version":"1.2.2","pointer":"/profile/imports/0/include-controls/0/with-ids","profile_last_modified":"2026-05-11","profile_version":"5.2.0","source":"https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_HIGH-baseline_profile.json","title":"Electronic (OSCAL) Version of NIST Special Publication 800-53 Revision 5.1.1 HIGH IMPACT BASELINE","with_ids":["ac-1","ac-2","ac-2.1","ac-2.2","ac-2.3","ac-2.4","ac-2.5","ac-2.11","ac-2.12","ac-2.13","ac-3","ac-4","ac-4.4","ac-5","ac-6","ac-6.1","ac-6.2","ac-6.3","ac-6.5","ac-6.7","ac-6.9","ac-6.10","ac-7","ac-8","ac-10","ac-11","ac-11.1","ac-12","ac-14","ac-17","ac-17.1","ac-17.2","ac-17.3","ac-17.4","ac-18","ac-18.1","ac-18.3","ac-18.4","ac-18.5","ac-19","ac-19.5","ac-20","ac-20.1","ac-20.2","ac-21","ac-22","at-1","at-2","at-2.2","at-2.3","at-3","at-4","au-1","au-2","au-3","au-3.1","au-4","au-5","au-5.1","au-5.2","au-6","au-6.1","au-6.3","au-6.5","au-6.6","au-7","au-7.1","au-8","au-9","au-9.2","au-9.3","au-9.4","au-10","au-11","au-12","au-12.1","au-12.3","ca-1","ca-2","ca-2.1","ca-2.2","ca-3","ca-3.6","ca-5","ca-6","ca-7","ca-7.1","ca-7.4","ca-8","ca-8.1","ca-9","cm-1","cm-2","cm-2.2","cm-2.3","cm-2.7","cm-3","cm-3.1","cm-3.2","cm-3.4","cm-3.6","cm-4","cm-4.1","cm-4.2","cm-5","cm-5.1","cm-6","cm-6.1","cm-6.2","cm-7","cm-7.1","cm-7.2","cm-7.5","cm-8","cm-8.1","cm-8.2","cm-8.3","cm-8.4","cm-9","cm-10","cm-11","cm-12","cm-12.1","cp-1","cp-2","cp-2.1","cp-2.2","cp-2.3","cp-2.5","cp-2.8","cp-3","cp-3.1","cp-4","cp-4.1","cp-4.2","cp-6","cp-6.1","cp-6.2","cp-6.3","cp-7","cp-7.1","cp-7.2","cp-7.3","cp-7.4","cp-8","cp-8.1","cp-8.2","cp-8.3","cp-8.4","cp-9","cp-9.1","cp-9.2","cp-9.3","cp-9.5","cp-9.8","cp-10","cp-10.2","cp-10.4","ia-1","ia-2","ia-2.1","ia-2.2","ia-2.5","ia-2.8","ia-2.12","ia-3","ia-4","ia-4.4","ia-5","ia-5.1","ia-5.2","ia-5.6","ia-6","ia-7","ia-8","ia-8.1","ia-8.2","ia-8.4","ia-11","ia-12","ia-12.2","ia-12.3","ia-12.4","ia-12.5","ir-1","ir-2","ir-2.1","ir-2.2","ir-3","ir-3.2","ir-4","ir-4.1","ir-4.4","ir-4.11","ir-5","ir-5.1","ir-6","ir-6.1","ir-6.3","ir-7","ir-7.1","ir-8","ma-1","ma-2","ma-2.2","ma-3","ma-3.1","ma-3.2","ma-3.3","ma-4","ma-4.3","ma-5","ma-5.1","ma-6","mp-1","mp-2","mp-3","mp-4","mp-5","mp-6","mp-6.1","mp-6.2","mp-6.3","mp-7","pe-1","pe-2","pe-3","pe-3.1","pe-4","pe-5","pe-6","pe-6.1","pe-6.4","pe-8","pe-8.1","pe-9","pe-10","pe-11","pe-11.1","pe-12","pe-13","pe-13.1","pe-13.2","pe-14","pe-15","pe-15.1","pe-16","pe-17","pe-18","pl-1","pl-2","pl-4","pl-4.1","pl-8","pl-10","pl-11","ps-1","ps-2","ps-3","ps-4","ps-4.2","ps-5","ps-6","ps-7","ps-8","ps-9","ra-1","ra-2","ra-3","ra-3.1","ra-5","ra-5.2","ra-5.4","ra-5.5","ra-5.11","ra-7","ra-9","sa-1","sa-2","sa-3","sa-4","sa-4.1","sa-4.2","sa-4.5","sa-4.9","sa-4.10","sa-5","sa-8","sa-9","sa-9.2","sa-10","sa-11","sa-15","sa-15.3","sa-16","sa-17","sa-21","sa-22","sc-1","sc-2","sc-3","sc-4","sc-5","sc-7","sc-7.3","sc-7.4","sc-7.5","sc-7.7","sc-7.8","sc-7.18","sc-7.21","sc-8","sc-8.1","sc-10","sc-12","sc-12.1","sc-13","sc-15","sc-17","sc-18","sc-20","sc-21","sc-22","sc-23","sc-24","sc-28","sc-28.1","sc-39","si-1","si-2","si-2.2","si-3","si-4","si-4.2","si-4.4","si-4.5","si-4.10","si-4.12","si-4.14","si-4.20","si-4.22","si-5","si-5.1","si-6","si-7","si-7.1","si-7.2","si-7.5","si-7.7","si-7.15","si-8","si-8.2","si-10","si-11","si-12","si-16","sr-1","sr-2","sr-2.1","sr-3","sr-5","sr-6","sr-8","sr-9","sr-9.1","sr-10","sr-11","sr-11.1","sr-11.2","sr-12"]},"data/scenario.json":{"approaches":{"assessment-first":{"files":[{"count":1,"detail":"800-53 Revision 5","items":[{"name":"NIST 800-53"}],"model":"catalog","what":"the framework only"},{"count":1,"detail":"","items":[{"name":"800-53 High"}],"model":"profile","what":"the High baseline"},{"count":0,"detail":"activities identify related controls; reviewed-controls defines the assessment plan's control scope","model":"mapping-collection","what":"none, framework mappings are on activities"},{"count":0,"detail":"assessment-assets contains the components running checks; separate component definition documents are not needed","model":"component-definition","what":"none, engines are identified in each plan"},{"count":1,"detail":"assessment plans reference the system security plan without adding guidance to the implementation claims","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 370 controls"},{"count":4,"detail":"the three guides contain 547 requirements as activities and steps; each assessment plan references one system security plan through import-ssp","items":[{"name":"800-53 AP"},{"name":"CIS Ubuntu AP"},{"name":"DISA PgSQL AP"},{"name":"CISA SCuBA AP"}],"model":"assessment-plan","what":"one for the framework assessment, one per guide"},{"count":4,"detail":"four results documents, not four sections in one document; import-ap is a single required object referencing exactly one assessment plan","items":[{"name":"800-53 AR"},{"name":"CIS Ubuntu AR"},{"name":"DISA PgSQL AR"},{"name":"CISA SCuBA AR"}],"model":"assessment-results","what":"one per plan; each result references exactly one plan"}],"plan_of_record":"The system security plan addresses 370 controls; all three guides remain in assessment plans","rule":"Each guide becomes an assessment plan with a separate assessment results document. The framework catalog and baseline profile remain unchanged."},"catalog-first":{"files":[{"count":4,"detail":"800-53 Revision 5, CIS Ubuntu, DISA PostgreSQL, CISA SCuBA","items":[{"name":"NIST 800-53"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"}],"model":"catalog","what":"one for the framework, one for each guide"},{"count":5,"detail":"the High baseline, three guide selections and an organisational profile merging all four selections; import-profile is a single required object in the system security plan","items":[{"name":"800-53 High"},{"name":"CIS Ubuntu"},{"name":"DISA PgSQL"},{"name":"CISA SCuBA"},{"name":"Org merged"}],"model":"profile","what":"one selection per catalog and one merged selection"},{"count":3,"detail":"without mappings, guidance controls and framework controls remain two unrelated sets in the system security plan","items":[{"name":"CIS to 800-53"},{"name":"STIG to 800-53"},{"name":"SCuBA to 800-53"}],"model":"mapping-collection","what":"one per guide, linking guidance controls to framework controls"},{"count":3,"detail":"the control references a check identifier; a software component with a matching name describes the check's execution","items":[{"kind":"software","name":"Ubuntu checks"},{"kind":"software","name":"PgSQL checks"},{"kind":"software","name":"M365 checks"}],"model":"component-definition","what":"one per technology, containing check components"},{"count":1,"detail":"370 framework controls and 547 guidance controls, each requiring a by-component response; one import-profile references the merged profile because the field is a single required object","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 917 controls"},{"count":1,"detail":"","items":[{"name":"System AP"}],"model":"assessment-plan","what":"one"},{"count":1,"detail":"","items":[{"name":"System AR"}],"model":"assessment-results","what":"one"}],"plan_of_record":"The system security plan addresses 917 controls: 370 from the framework and 547 from the guides","rule":"Each guide becomes a catalog with a selection profile and a mapping collection linking guidance to the framework. The system security plan addresses every control in the merged set."},"component-first":{"files":[{"count":1,"detail":"800-53 Revision 5","items":[{"name":"NIST 800-53"}],"model":"catalog","what":"the framework only"},{"count":1,"detail":"","items":[{"name":"800-53 High"}],"model":"profile","what":"the High baseline"},{"count":0,"detail":"control implementations identify the controls served by the rules; no separate document carries the mapping","model":"mapping-collection","what":"none, framework mappings are inside component definitions"},{"count":6,"detail":"Ubuntu, PostgreSQL and Microsoft 365, with one validation component definition per checking engine","items":[{"kind":"software","name":"Ubuntu"},{"kind":"software","name":"PostgreSQL"},{"kind":"software","name":"Microsoft 365"},{"kind":"validation","name":"Ubuntu checks"},{"kind":"validation","name":"PgSQL checks"},{"kind":"validation","name":"M365 checks"}],"model":"component-definition","what":"three products with 547 rules, three engines with checks"},{"count":1,"detail":"the control count remains unchanged; rules are included in system-implementation","items":[{"name":"System SSP"}],"model":"system-security-plan","what":"one, addressing 370 controls and containing 547 rules"},{"count":1,"detail":"","items":[{"name":"System AP"}],"model":"assessment-plan","what":"one"},{"count":1,"detail":"","items":[{"name":"System AR"}],"model":"assessment-results","what":"one"}],"plan_of_record":"The system security plan addresses 370 controls and contains 547 desired-state rules in components","rule":"Each guide becomes rules on the component being configured. Each checking engine becomes a separate validation component. The framework catalog and baseline profile remain unchanged."},"executable-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":3,"detail":"CIS names SP 800-53 controls in its recommendations' identifiers, the STIG names CCIs, and SCuBA names controls on every step, so each guide's own references become a mapping collection from its objectives' controls to the framework; where a profile adds the check to the framework control instead, the placement is the tie and nothing is mapped","items":[{"name":"CIS to 800-53"},{"name":"STIG to 800-53"},{"name":"SCuBA to 800-53"}],"model":"mapping-collection","what":"one per guide, from the guide's own framework references"},{"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, each component references a profile selecting from it, and each guide's own framework references become a mapping collection. The plan of record's control set does not move."}},"excluded_model":{"model":"plan-of-action-and-milestones","reason":"The plan of action and milestones records unmet requirements and remediation. The document serves the same purpose in all four approaches and is excluded from the comparison."},"framework":{"base":188,"controls":370,"derivation":"count of /profile/imports/0/include-controls/0/with-ids in the published HIGH baseline profile, version 5.2.0","enhancements":182,"families":18,"label":"NIST SP 800-53 Revision 5, High baseline","source":"data/scenario-evidence/nist-high-baseline.json"},"hardening":[{"count_rule":"audit-steps","derivation":"count of steps titled 'Audit for ...' in Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json. The file carries 616 steps, one audit and one remediation for each recommendation, in 53 activities.","grouping":53,"grouping_label":"sections","key":"cis-ubuntu","label":"CIS Ubuntu 24.04 LTS Benchmark","requirements":308,"source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","technology":"Ubuntu"},{"count_rule":"step-type-check","derivation":"count of props step-type=check in Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json. The file carries 111 activities and 222 steps, one check and one remediate for each.","grouping":111,"grouping_label":"activities, one per requirement","key":"disa-postgres","label":"DISA STIG PostgreSQL 16","requirements":111,"source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/postgres16.json","technology":"PostgreSQL"},{"count_rule":"steps","derivation":"count of steps in Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json, which carries 128 steps across 7 activities, one activity per Microsoft 365 service.","grouping":7,"grouping_label":"services","key":"cisa-bod-25-01","label":"CISA BOD 25-01 SCuBA","requirements":128,"source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-agnostic.json","technology":"Microsoft 365"}],"items_note":"Each entry represents one file, with a name shortened for the diagram tile. Component-first distinguishes the product component, of type software, from the checking component, of type validation. File counts alone do not show component types.","models":["catalog","profile","mapping-collection","component-definition","system-security-plan","assessment-plan","assessment-results"],"note":"One system, one baseline and three hardening guides, modelled with each of the four approaches. The scenario compares document counts and system security plan content, not overall capability. Counts derive from the corpus, the NIST profile in data/scenario-evidence/, or OSCAL schema constraints. Each file row records the applicable constraint.","summary":"A system follows the NIST SP 800-53 Revision 5 High baseline and hardening guides for Ubuntu, PostgreSQL and Microsoft 365. The four approaches model the same requirements, using every OSCAL model except the plan of action and milestones.","title":"One system, three hardening guides"},"data/schema-evidence/assessment-subject.json":{"constraints":["anyOf requires include-all or include-subjects","each selection branch has optional type with anyOf enum [\"component\",\"inventory-item\",\"location\",\"party\",\"user\"]"],"definition":"oscal-ap-oscal-assessment-common:assessment-subject","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ap-oscal-assessment-common:assessment-subject","anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description"},"exclude-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ap-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["component","inventory-item","location","party","user"]}],"description":"Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.","title":"Subject Type"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the collection of subjects being included in this assessment.","title":"Include Subjects Description"},"exclude-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"include-subjects":{"items":{"$ref":"#/definitions/oscal-ap-oscal-assessment-common:select-subject-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["component","inventory-item","location","party","user"]}],"description":"Indicates the type of assessment subject, such as a component, inventory, item, location, or party represented by this selection statement.","title":"Subject Type"}},"required":["include-subjects"]}],"description":"Identifies system elements being assessed, such as components, inventory items, and locations. In the assessment plan, this identifies a planned assessment subject. In the assessment results this is an actual assessment subject, and reflects any changes from the plan. exactly what will be the focus of this assessment. Any subjects not identified in this way are out-of-scope.","title":"Subject of Assessment","type":"object"},"model":"assessment-plan","note":"OSCAL 1.2.1 assessment subjects select all subjects or an explicit set. The optional type vocabulary includes component, inventory-item, location, party and user, supporting assessment of individual hosts.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_assessment-plan_schema.json at definitions/oscal-ap-oscal-assessment-common:assessment-subject.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ap-schema.json"},"data/schema-evidence/by-component.json":{"constraints":["required == [\"component-uuid\",\"uuid\",\"description\"]","has property \"component-uuid\"","has no property \"subject\", \"subject-uuid\", \"inventory-item-uuid\" or \"type\""],"definition":"oscal-ssp-oscal-ssp:by-component","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ssp-oscal-ssp:by-component","additionalProperties":false,"description":"Defines how the referenced component implements a set of controls.","properties":{"component-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to the component that is implementing a given control.","title":"Component Universally Unique Identifier Reference"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes how a control or a control statement is implemented within the referenced system component.","title":"Control Implementation Description"},"export":{"additionalProperties":false,"description":"Identifies content intended for external consumption, such as with leveraged organizations.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that can be available to another system leveraging this system.","title":"Control Implementation Export Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided":{"items":{"additionalProperties":false,"description":"Describes a capability which may be inherited by a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that can be provided to another system leveraging this system.","title":"Provided Control Implementation Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Provided Universally Unique Identifier"}},"required":["uuid","description"],"title":"Provided Control Implementation","type":"object"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsibilities":{"items":{"additionalProperties":false,"description":"Describes a control implementation responsibility imposed on a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of the control or control statement implementation that a leveraging system must implement to satisfy the control provided by a leveraged system.","title":"Control Implementation Responsibility Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.","title":"Provided UUID"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Responsibility Universally Unique Identifier"}},"required":["uuid","description"],"title":"Control Implementation Responsibility","type":"object"},"minItems":1,"type":"array"}},"title":"Export","type":"object"},"implementation-status":{"$ref":"#/definitions/oscal-ssp-oscal-implementation-common:implementation-status"},"inherited":{"items":{"additionalProperties":false,"description":"Describes a control implementation inherited by a leveraging system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is inheriting from a leveraged system.","title":"Inherited Control Implementation Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"provided-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system.","title":"Provided UUID"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Inherited Universally Unique Identifier"}},"required":["uuid","description"],"title":"Inherited Control Implementation","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"satisfied":{"items":{"additionalProperties":false,"description":"Describes how this system satisfies a responsibility imposed by a leveraged system.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"An implementation statement that describes the aspects of a control or control statement implementation that a leveraging system is implementing based on a requirement from a leveraged system.","title":"Satisfied Control Implementation Responsibility Description"},"links":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:remarks"},"responsibility-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system.","title":"Responsibility UUID"},"responsible-roles":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-metadata:responsible-role"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Satisfied Universally Unique Identifier"}},"required":["uuid","description"],"title":"Satisfied Control Implementation Responsibility","type":"object"},"minItems":1,"type":"array"},"set-parameters":{"items":{"$ref":"#/definitions/oscal-ssp-oscal-implementation-common:set-parameter"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"By-Component Universally Unique Identifier"}},"required":["component-uuid","uuid","description"],"title":"Component Control Implementation","type":"object"},"model":"system-security-plan","note":"The oscal-ssp-oscal-ssp:by-component definition, which is the only way a system security plan responds to a control. It is keyed by component-uuid and has no subject of any kind: no inventory-item, no location, no party, no user. A plan can describe inventory items elsewhere, in system-implementation, but a control response cannot be made against one, so two hosts of the same component share a single response.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_ssp_schema.json at definitions/oscal-ssp-oscal-ssp:by-component.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ssp-schema.json"},"data/schema-evidence/finding-target.json":{"constraints":["required == [\"type\",\"target-id\",\"status\"]","type is constrained by allOf to enum [\"statement-id\",\"objective-id\"]","status.required includes \"state\"","status.state enum == [\"satisfied\",\"not-satisfied\"]"],"definition":"oscal-ar-oscal-assessment-common:finding-target","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:finding-target","additionalProperties":false,"description":"Captures an assessor's conclusions regarding the degree to which an objective is satisfied.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of the assessor's conclusions regarding the degree to which an objective is satisfied.","title":"Objective Status Description"},"implementation-status":{"$ref":"#/definitions/oscal-ar-oscal-implementation-common:implementation-status"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"status":{"additionalProperties":false,"description":"A determination of if the objective is satisfied or not within a given system.","properties":{"reason":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["pass","fail","other"]}],"description":"The reason the objective was given it's status.","title":"Objective Status Reason"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"state":{"allOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["satisfied","not-satisfied"]}],"description":"An indication as to whether the objective is satisfied or not.","title":"Objective Status State"}},"required":["state"],"title":"Objective Status","type":"object"},"target-id":{"$ref":"#/definitions/TokenDatatype","description":"A machine-oriented identifier reference for a specific target qualified by the type.","title":"Finding Target Identifier Reference"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this objective status.","title":"Objective Status Title"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["statement-id","objective-id"]}],"description":"Identifies the type of the target.","title":"Finding Target Type"}},"required":["type","target-id","status"],"title":"Objective Status","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:finding-target definition from the OSCAL 1.2.1 assessment-results model, demonstrating that a finding target requires type, target-id, and status, restricts type by allOf to the closed enumeration statement-id or objective-id, and requires a status.state drawn from the closed enumeration satisfied or not-satisfied.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/finding.json":{"constraints":["required includes \"target\""],"definition":"oscal-ar-oscal-assessment-common:finding","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:finding","additionalProperties":false,"description":"Describes an individual finding.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this finding.","title":"Finding Description"},"implementation-statement-uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related.","title":"Implementation Statement UUID"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"origins":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:origin"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"related-observations":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:related-observation"},"minItems":1,"type":"array"},"related-risks":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:associated-risk"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"target":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:finding-target"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this finding.","title":"Finding Title"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Finding Universally Unique Identifier"}},"required":["uuid","title","description","target"],"title":"Finding","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:finding definition from the OSCAL 1.2.1 assessment-results model, demonstrating that every finding must carry a target.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/mapping-item.json":{"constraints":["required == [\"type\",\"id-ref\"]","type is constrained by allOf to enum [\"control\",\"statement\"]","no property named 'uuid'","no property named 'href'"],"definition":"oscal-mapping-oscal-mapping-common:mapping-item","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-mapping-oscal-mapping-common:mapping-item","additionalProperties":false,"description":"A specific edge within a source or target that is the subject of a mapping.","properties":{"id-ref":{"$ref":"#/definitions/StringDatatype","description":"A reference to an identified subject that is of the specified type .","title":"Subject Identifier Reference"},"links":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:remarks"},"type":{"allOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["control","statement"]}],"description":"The semantic type of the subject.","title":"Subject Type"}},"required":["type","id-ref"],"title":"Mapping Entry Item (source or target)","type":"object"},"model":"mapping-collection","note":"The oscal-mapping-oscal-mapping-common:mapping-item definition from the OSCAL 1.2.1 mapping-collection model, demonstrating that a mapping item requires only type and id-ref, restricts type by allOf to the closed enumeration control or statement, and defines no uuid or href property.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-mapping-schema.json"},"data/schema-evidence/mapping-resource-reference.json":{"constraints":["required == [\"type\",\"href\"]","type uses anyOf (open vocabulary) with enum [\"catalog\",\"profile\"]"],"definition":"oscal-mapping-oscal-mapping-common:mapping-resource-reference","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-mapping-oscal-mapping-common:mapping-resource-reference","additionalProperties":false,"description":"A reference to a resource that is either the source or the target of a mapping.","properties":{"href":{"$ref":"#/definitions/URIReferenceDatatype","description":"A resolvable URL reference to the base catalog or profile that this profile is tailoring.","title":"Catalog or Profile Reference"},"links":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:link"},"minItems":1,"type":"array"},"ns":{"$ref":"#/definitions/URIDatatype","description":"An optional namespace qualifying the resource's type.","title":"Resource Type Namespace"},"props":{"items":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-mapping-oscal-metadata:remarks"},"type":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["catalog","profile"]}],"description":"The semantic type of the resource.","title":"Resource Type"}},"required":["type","href"],"title":"Mapped Resource Reference","type":"object"},"model":"mapping-collection","note":"The oscal-mapping-oscal-mapping-common:mapping-resource-reference definition from the OSCAL 1.2.1 mapping-collection model, demonstrating that a mapped resource reference requires type and href and constrains type with an open anyOf vocabulary whose enumeration lists catalog and profile.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-mapping-schema.json"},"data/schema-evidence/metadata.json":{"constraints":["required == [\"title\",\"last-modified\",\"version\",\"oscal-version\"]"],"definition":"oscal-ap-oscal-metadata:metadata","fetched_at":"2026-09-09","fragment":{"$id":"#/definitions/oscal-ap-oscal-metadata:metadata","additionalProperties":false,"description":"Provides information about the containing document, and defines concepts that are shared across the document.","properties":{"actions":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:action"},"minItems":1,"type":"array"},"document-ids":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:document-id"},"minItems":1,"type":"array"},"last-modified":{"$ref":"#/definitions/oscal-ap-oscal-metadata:last-modified"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"locations":{"items":{"additionalProperties":false,"description":"A physical point of presence, which may be associated with people, organizations, or other concepts within the current or linked OSCAL document.","properties":{"address":{"$ref":"#/definitions/oscal-ap-oscal-metadata:address"},"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the location, which may be used by a tool for display and navigation.","title":"Location Title"},"urls":{"items":{"$ref":"#/definitions/URIDatatype","description":"The uniform resource locator (URL) for a web site or other resource associated with the location.","title":"Location URL"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique ID for the location, for reference.","title":"Location Universally Unique Identifier"}},"required":["uuid"],"title":"Location","type":"object"},"minItems":1,"type":"array"},"oscal-version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:oscal-version"},"parties":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:address"},"minItems":1,"type":"array"},"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"external-ids":{"items":{"additionalProperties":false,"description":"An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).","properties":{"id":{"$ref":"#/definitions/StringDatatype"},"scheme":{"anyOf":[{"$ref":"#/definitions/URIDatatype"},{"enum":["http://orcid.org/"]}],"description":"Indicates the type of external identifier.","title":"External Identifier Schema"}},"required":["id","scheme"],"title":"Party External Identifier","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"member-of-organizations":{"items":{"$ref":"#/definitions/UUIDDatatype","description":"A reference to another party by UUID, typically an organization, that this subject is associated with.","title":"Organizational Affiliation"},"minItems":1,"type":"array"},"name":{"$ref":"#/definitions/StringDatatype","description":"The full name of the party. This is typically the legal name associated with the party.","title":"Party Name"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the party.","title":"Party Short Name"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["person","organization"]}],"description":"A category describing the kind of party the object describes.","title":"Party Type"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique identifier for the party.","title":"Party Universally Unique Identifier"}}},{"additionalProperties":false,"properties":{"email-addresses":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:email-address"},"minItems":1,"type":"array"},"external-ids":{"items":{"additionalProperties":false,"description":"An identifier for a person or organization using a designated scheme. e.g. an Open Researcher and Contributor ID (ORCID).","properties":{"id":{"$ref":"#/definitions/StringDatatype"},"scheme":{"anyOf":[{"$ref":"#/definitions/URIDatatype"},{"enum":["http://orcid.org/"]}],"description":"Indicates the type of external identifier.","title":"External Identifier Schema"}},"required":["id","scheme"],"title":"Party External Identifier","type":"object"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"location-uuids":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:location-uuid"},"minItems":1,"type":"array"},"member-of-organizations":{"items":{"$ref":"#/definitions/UUIDDatatype","description":"A reference to another party by UUID, typically an organization, that this subject is associated with.","title":"Organizational Affiliation"},"minItems":1,"type":"array"},"name":{"$ref":"#/definitions/StringDatatype","description":"The full name of the party. This is typically the legal name associated with the party.","title":"Party Name"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the party.","title":"Party Short Name"},"telephone-numbers":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:telephone-number"},"minItems":1,"type":"array"},"type":{"allOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["person","organization"]}],"description":"A category describing the kind of party the object describes.","title":"Party Type"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A unique identifier for the party.","title":"Party Universally Unique Identifier"}}}],"description":"An organization or person, which may be associated with roles or other concepts within the current or linked OSCAL document.","title":"Party","type":"object"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"published":{"$ref":"#/definitions/oscal-ap-oscal-metadata:published"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"responsible-parties":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:responsible-party"},"minItems":1,"type":"array"},"revisions":{"items":{"additionalProperties":false,"description":"An entry in a sequential list of revisions to the containing document, expected to be in reverse chronological order (i.e. latest first).","properties":{"last-modified":{"$ref":"#/definitions/oscal-ap-oscal-metadata:last-modified"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"oscal-version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:oscal-version"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"published":{"$ref":"#/definitions/oscal-ap-oscal-metadata:published"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the document revision, which may be used by a tool for display and navigation.","title":"Document Title"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["version"],"title":"Revision History Entry","type":"object"},"minItems":1,"type":"array"},"roles":{"items":{"additionalProperties":false,"description":"Defines a function, which might be assigned to a party in a specific situation.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A summary of the role's purpose and associated responsibilities.","title":"Role Description"},"id":{"$ref":"#/definitions/TokenDatatype","description":"A unique identifier for the role.","title":"Role Identifier"},"links":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ap-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ap-oscal-metadata:remarks"},"short-name":{"$ref":"#/definitions/StringDatatype","description":"A short common name, abbreviation, or acronym for the role.","title":"Role Short Name"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the role, which may be used by a tool for display and navigation.","title":"Role Title"}},"required":["id","title"],"title":"Role","type":"object"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"A name given to the document, which may be used by a tool for display and navigation.","title":"Document Title"},"version":{"$ref":"#/definitions/oscal-ap-oscal-metadata:version"}},"required":["title","last-modified","version","oscal-version"],"title":"Document Metadata","type":"object"},"model":"assessment-plan","note":"The shared oscal-metadata:metadata assembly. Every OSCAL document, a catalog among them, is required to carry a title, a last-modified timestamp, a version and the OSCAL version it conforms to. That is what makes a published guide citable as a document rather than as a copy.","oscal_version":"1.2.1","provenance":"Extracted from https://github.com/usnistgov/OSCAL/releases/download/v1.2.1/oscal_assessment-plan_schema.json at definitions/oscal-ap-oscal-metadata:metadata.","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ap-schema.json"},"data/schema-evidence/observation.json":{"constraints":["required == [\"uuid\",\"description\",\"methods\",\"collected\"]","no property named 'target'","no property named 'control-id'","no property named 'objective-id'"],"definition":"oscal-ar-oscal-assessment-common:observation","fetched_at":"2026-08-12","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:observation","additionalProperties":false,"description":"Describes an individual observation.","properties":{"collected":{"$ref":"#/definitions/DateTimeWithTimezoneDatatype","description":"Date/time stamp identifying when the finding information was collected.","title":"Collected Field"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this assessment observation.","title":"Observation Description"},"expires":{"$ref":"#/definitions/DateTimeWithTimezoneDatatype","description":"Date/time identifying when the finding information is out-of-date and no longer valid. Typically used with continuous assessment scenarios.","title":"Expires Field"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"methods":{"items":{"anyOf":[{"$ref":"#/definitions/StringDatatype"},{"enum":["EXAMINE","INTERVIEW","TEST","UNKNOWN"]}],"description":"Identifies how the observation was made.","title":"Observation Method"},"minItems":1,"type":"array"},"origins":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:origin"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"relevant-evidence":{"items":{"additionalProperties":false,"description":"Links this observation to relevant evidence.","properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this evidence.","title":"Relevant Evidence Description"},"href":{"$ref":"#/definitions/URIReferenceDatatype","description":"A resolvable URL reference to relevant evidence.","title":"Relevant Evidence Reference"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["description"],"title":"Relevant Evidence","type":"object"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"},"subjects":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:subject-reference"},"minItems":1,"type":"array"},"title":{"$ref":"#/definitions/MarkupLineDatatype","description":"The title for this observation.","title":"Observation Title"},"types":{"items":{"anyOf":[{"$ref":"#/definitions/TokenDatatype"},{"enum":["ssp-statement-issue","control-objective","mitigation","finding","discovery","historic"]}],"description":"Identifies the nature of the observation. More than one may be used to further qualify and enable filtering.","title":"Observation Type"},"minItems":1,"type":"array"},"uuid":{"$ref":"#/definitions/UUIDDatatype","description":"A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.","title":"Observation Universally Unique Identifier"}},"required":["uuid","description","methods","collected"],"title":"Observation","type":"object"},"model":"assessment-results","note":"The oscal-ar-oscal-assessment-common:observation definition from the OSCAL 1.2.1 assessment-results model, demonstrating that an observation requires uuid, description, methods, and collected, and defines no target, control-id, or objective-id property.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/poam-outcomes.json":{"constraints":["properties includes \"observations\"","properties includes \"findings\"","observations items ref the shared assessment-common observation","findings items ref the shared assessment-common finding"],"definition":"oscal-poam-oscal-poam:plan-of-action-and-milestones","fetched_at":"2026-08-18","fragment":{"properties":{"findings":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:finding"},"minItems":1,"type":"array"},"observations":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:observation"},"minItems":1,"type":"array"},"risks":{"items":{"$ref":"#/definitions/oscal-poam-oscal-assessment-common:risk"},"minItems":1,"type":"array"}},"required":["uuid","metadata","poam-items"]},"fragment_note":"Only required and the observations, findings and risks properties are carried.","model":"plan-of-action-and-milestones","note":"The root assembly of the OSCAL 1.2.1 plan-of-action-and-milestones model. It carries observations and findings as sibling arrays, so assessment results is not the only model in which an outcome can be recorded. Both models sit in the Assessment layer; no control-layer or implementation-layer model carries either.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-poam-schema.json"},"data/schema-evidence/result.json":{"constraints":["required includes \"reviewed-controls\""],"definition":"oscal-ar-oscal-ar:result","fetched_at":"2026-08-18","fragment":{"properties":{"reviewed-controls":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls"}},"required":["uuid","title","description","start","reviewed-controls"]},"fragment_note":"Only required and the reviewed-controls property are carried. The other properties of result are not relevant to this claim and are omitted.","model":"assessment-results","note":"The result assembly of the OSCAL 1.2.1 assessment-results model. Every result is required to declare the controls it reviewed, so the control frame is unavoidable at the result level. The referenced reviewed-controls assembly requires control-selections, and a selection may use include-all rather than naming individual controls, so the requirement can be met without listing any one control.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/schema-evidence/reviewed-controls.json":{"constraints":["required == [\"control-selections\"]","control-selections items use anyOf with required [\"include-all\"] or [\"include-controls\"]"],"definition":"oscal-ar-oscal-assessment-common:reviewed-controls","fetched_at":"2026-08-18","fragment":{"$id":"#/definitions/oscal-ar-oscal-assessment-common:reviewed-controls","additionalProperties":false,"description":"Identifies the controls being assessed and their control objectives.","properties":{"control-objective-selections":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this collection of control objectives.","title":"Control Objectives Description"},"exclude-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ar-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of this collection of control objectives.","title":"Control Objectives Description"},"exclude-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"include-objectives":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-objective-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-objectives"]}],"description":"Identifies the control objectives of the assessment. In the assessment plan, these are the planned objectives. In the assessment results, these are the assessed objectives, and reflects any changes from the plan.","title":"Referenced Control Objectives","type":"object"},"minItems":1,"type":"array"},"control-selections":{"items":{"anyOf":[{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of in-scope controls specified for assessment.","title":"Assessed Controls Description"},"exclude-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"include-all":{"$ref":"#/definitions/oscal-ar-oscal-control-common:include-all"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-all"]},{"additionalProperties":false,"properties":{"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of in-scope controls specified for assessment.","title":"Assessed Controls Description"},"exclude-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"include-controls":{"items":{"$ref":"#/definitions/oscal-ar-oscal-assessment-common:select-control-by-id"},"minItems":1,"type":"array"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["include-controls"]}],"description":"Identifies the controls being assessed. In the assessment plan, these are the planned controls. In the assessment results, these are the actual controls, and reflects any changes from the plan.","title":"Assessed Controls","type":"object"},"minItems":1,"type":"array"},"description":{"$ref":"#/definitions/MarkupMultilineDatatype","description":"A human-readable description of control objectives.","title":"Control Objective Description"},"links":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:link"},"minItems":1,"type":"array"},"props":{"items":{"$ref":"#/definitions/oscal-ar-oscal-metadata:property"},"minItems":1,"type":"array"},"remarks":{"$ref":"#/definitions/oscal-ar-oscal-metadata:remarks"}},"required":["control-selections"],"title":"Reviewed Controls and Control Objectives","type":"object"},"model":"assessment-results","note":"The reviewed-controls assembly of the OSCAL 1.2.1 assessment-results model. It requires control-selections, and each selection must carry either include-all or include-controls. So the requirement that a result declare the controls it reviewed can be satisfied with include-all, without naming any one control. The single assessment result in the three bodies of content does exactly that.","oscal_version":"1.2.1","schema_id":"http://csrc.nist.gov/ns/oscal/1.2.1/oscal-ar-schema.json"},"data/six-questions.json":{"answer_states":[{"key":"filled","label":"Answered","meaning":"The published content answers this question."},{"key":"partial","label":"Partly answered","meaning":"The published content answers part of this question."},{"key":"empty-absent","label":"Not answered","meaning":"The published content does not answer the question or state a reason for the omission."}],"approaches":[{"key":"catalog-first","label":"Catalog-first","layer":"Control","one_line":"The rule is a catalog control; the check is a software component in a component definition.","option_letter":"A","primary_model":"catalog","repo":"https://github.com/awslabs/oscal-content-for-aws-services","serves_stakeholder_first":"publisher","status_annotation":"experimental, per publisher"},{"key":"component-first","label":"Component-first","layer":"Implementation","one_line":"The rule uses a proposed assembly on the product component; the check uses a proposed assembly on a validation component.","option_letter":"B","primary_model":"component-definition","repo":null,"serves_stakeholder_first":"implementer","status_annotation":"proposed schema"},{"key":"assessment-first","label":"Assessment-first","layer":"Assessment","one_line":"The rule is an assessment plan activity or step; a property identifies the check.","option_letter":"C","primary_model":"assessment-plan","repo":null,"serves_stakeholder_first":"assessor","status_annotation":"placeholder and synthetic identifiers"},{"key":"executable-first","label":"Executable-first","layer":"Control","one_line":"The rule is an assessment objective part on a control; the check is an executable assessment method beside it, or a typed assembly on a component.","option_letter":"D","primary_model":"profile","repo":null,"serves_stakeholder_first":"assessor","status_annotation":"generated corpus, not a proponent's publication"}],"carrier_note":"Each answer identifies the OSCAL model and assemblies representing the capability. Rules use catalog controls, component rules, assessment activities or assessment objective parts on a control; the choice affects references to checks, claims and results.","empty_states":[{"key":"empty-absent","label":"Unanswered, no stated position","meaning":"The published content does not answer the question or state a reason for the omission.","rendering":"hollow with a light dotted fill"}],"finding":"Questions 1 and 2 are answered by all 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":"Each cell combines an answer state with mechanism badges. A shared legend explains both dimensions together.","why_uneven":"Answer states describe evidence coverage. Mechanism descriptions also explain schema and tool-support requirements, so the descriptions need additional detail."},"matrix":[{"approach":"catalog-first","assemblies":["control"],"mechanisms":["assembly","prop"],"model":"catalog","note":"One control per rule. Existing assemblies capture context around the rule's intent.","props":[{"name":"TechnicalControlId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"1","snippet_ids":["aws-acm2-control","aws-input-parameter"],"state":"filled"},{"approach":"component-first","assemblies":["component","rules"],"mechanisms":["proposed"],"model":"component-definition","note":"The proposed rules assembly sits on the component alongside control-implementations.","slot":"1","snippet_ids":["ibm-cos-component"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The activity defines the rule and the step describes the check. Without a parameter field, required values are recorded in text.","props":[{"name":"check","ns":"http://comply0.com/ns/oscal"}],"slot":"1","snippet_ids":["ez-stig-activity-v259312","ez-stig-sc28-v270747"],"state":"filled"},{"approach":"catalog-first","assemblies":["mapping","map"],"mechanisms":["assembly"],"model":"mapping-collection","note":"A separate mapping collection links rules to framework controls. The published corpus contains no such mapping document.","slot":"2","snippet_ids":["aws-acm-backmatter-source","aws-acm-service-rollup"],"state":"filled"},{"approach":"component-first","assemblies":["component","implemented-requirement","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"component-definition","note":"Existing assemblies link the component to the control. Linking an individual rule requires the proposed assembly.","slot":"2","snippet_ids":["ibm-statement-rules","ibm-cos-component"],"state":"filled"},{"approach":"assessment-first","assemblies":["reviewed-controls","activity","related-controls"],"mechanisms":["assembly"],"model":"assessment-plan","note":"Two levels: reviewed-controls defines the required plan scope; related-controls optionally links an activity to controls.","slot":"2","snippet_ids":["ez-stig-related-controls","ez-cisa-step-reviewed"],"state":"filled"},{"approach":"catalog-first","assemblies":["component","implemented-requirement"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"The check identifier resolves within the runtime to an executable machine check.","props":[{"name":"ConfigRuleId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"3","snippet_ids":["aws-acm2-control","aws-acm-rsa-check-component"],"state":"filled"},{"approach":"component-first","assemblies":["component","checks"],"mechanisms":["proposed"],"model":"component-definition","note":"The proposed schema places both composite-key fields on the check. The rule has no reference back to the check.","slot":"3","snippet_ids":["ibm-validation-ansible"],"state":"filled"},{"approach":"assessment-first","assemblies":["activity","step"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"Three conventions: CISA references an executable through a JSON string in a prop; STIG and CIS describe checks in prose.","props":[{"name":"check","ns":"http://comply0.com/ns/oscal"}],"slot":"3","snippet_ids":["ez-cis-step-props","ez-cis-remediation-step","ez-cisa-context-step"],"state":"partial"},{"approach":"catalog-first","assemblies":["implemented-requirement","by-component"],"mechanisms":["assembly"],"model":"system-security-plan","note":"The by-component response identifies a component, not an instance. An assessment plan cannot import a catalog directly.","slot":"4","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["implemented-requirement","by-component","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"system-security-plan","note":"The proposed rule reference extends by-component. An assessor can include the component definition and associated checks in an assessment plan.","slot":"4","snippet_ids":["ibm-validation-ansible"],"state":"partial"},{"approach":"assessment-first","assemblies":["assessment-subjects","task","subjects"],"mechanisms":["assembly"],"model":"assessment-plan","note":"The plan defines subject scope; activity-associated tasks select targets. Both can identify inventory items, representing instances rather than classes.","slot":"4","snippet_ids":["ez-subjects-includeall","ez-subjects-explicit"],"state":"filled"},{"approach":"catalog-first","assemblies":["component"],"mechanisms":["assembly","prop"],"model":"component-definition","note":"The content records inputs and outputs but not the engine. ConfigRuleId resolves within the engine. No assessor workflow is shown; an assessment plan cannot import a catalog directly.","paths":[{"assemblies":["component","by-component"],"in":{"slot":"3"},"key":"implementor","label":"Implementor's path","out":{"slot":"6a"}}],"props":[{"name":"ConfigRuleId","ns":"http://aws.amazon.com/ns/oscal"}],"slot":"5","snippet_ids":["aws-config-service-bare"],"state":"partial"},{"approach":"component-first","assemblies":["component"],"mechanisms":["assembly","proposed"],"model":"component-definition","note":"The examples leave runner associations unresolved, including how an assessment asset links to a task or an observation.","paths":[{"assemblies":["component","checks","by-component","implementing-rules"],"in":{"slot":"3"},"key":"implementor","label":"Implementor's path","out":{"slot":"6a"}},{"assemblies":["component","checks","assessment-assets","observation","assessment-check-id","result"],"copy":{"slot":"3"},"in":{"model":"assessment-plan"},"key":"assessor","label":"Assessor's path","out":{"slot":"6b"}}],"slot":"5","snippet_ids":["ibm-ap-activity","ibm-ap-task-subjects","ibm-ar-observation"],"state":"filled"},{"approach":"assessment-first","assemblies":["assessment-platforms","component","task"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The platform executes the check, a referenced component represents the plugin, and a task property identifies the platform.","paths":[{"assemblies":["activity","step","assessment-platforms","component","task","observation"],"in":{"model":"assessment-plan"},"key":"assessor","label":"Assessor's path","out":{"slot":"6b"}}],"props":[{"name":"assessment-platform","ns":"http://comply0.com/ns/oscal"}],"slot":"5","snippet_ids":["ez-cisa-context-activity","ez-cisa-assessment-assets","ez-cisa-task-timing"],"state":"partial"},{"approach":"catalog-first","assemblies":["implemented-requirement","by-component"],"mechanisms":["assembly"],"model":"system-security-plan","note":"The component definition describes how a component could satisfy a control, not a system's implementation. The corpus contains no system security plan.","slot":"6a","snippet_ids":["aws-acm-rsa-check-component","aws-acm-service-rollup"],"state":"partial"},{"approach":"component-first","assemblies":["implemented-requirement","by-component","implementing-rules"],"mechanisms":["assembly","proposed"],"model":"system-security-plan","note":"The claim uses a by-component response. Identifying the supporting rule requires the proposed implementing-rules assembly.","slot":"6a","snippet_ids":[],"state":"empty-absent"},{"approach":"assessment-first","assemblies":["import-ssp","back-matter","resource"],"mechanisms":["assembly","prop"],"model":"assessment-plan","note":"The assessment plan references the document containing the implementation claim. A back-matter resource supports cases without a plan of record.","slot":"6a","snippet_ids":["ez-cisa-import-ssp","ez-cisa-ssp-resource","ez-cisa-no-ssp-resource","ez-stig-import-ssp"],"state":"partial"},{"approach":"catalog-first","assemblies":["finding"],"mechanisms":["assembly"],"model":"assessment-results","note":"No assessment results are published in the catalog-first OSCAL corpus.","slot":"6b","snippet_ids":[],"state":"empty-absent"},{"approach":"component-first","assemblies":["observation"],"mechanisms":["assembly","proposed"],"model":"assessment-results","note":"The result contains observations but no findings or objective status. The control reference must be recovered through the assessment plan.","slot":"6b","snippet_ids":["ibm-ar-observation"],"state":"partial"},{"approach":"assessment-first","assemblies":["finding","observation"],"mechanisms":["assembly"],"model":"assessment-results","note":"A separate results document imports the plan. Findings have targets and status; observations identify the executed activity as the subject.","slot":"6b","snippet_ids":["ez-cisa-ar-finding","ez-cisa-ar-observation"],"state":"filled"},{"approach":"executable-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":["pf-cis-objective-and-param","pf-stig-objective-sc-28"],"state":"filled"},{"approach":"executable-first","assemblies":["alter"],"mechanisms":["assembly"],"model":"profile","note":"Placement where a profile adds the check to the framework control; a mapping collection where the guide is its own catalog and publishes its framework references.","slot":"2","snippet_ids":["pf-stig-import","pf-cis-map-1-1-1-1"],"state":"filled"},{"approach":"executable-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":["pf-cis-method-1-1-1-1","pf-cis-script-resource","pf-stig-method-sc-28"],"state":"filled"},{"approach":"executable-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":["pf-cis-platform"],"state":"partial"},{"approach":"executable-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":["pf-cis-run-props"],"state":"partial"},{"approach":"executable-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":"executable-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":"Answer states describe coverage in the published corpus. Mechanism badges identify the OSCAL structures needed to represent an answer. Evidence coverage does not establish schema adoption or tool interoperability.","mechanism_states":[{"key":"assembly","label":"Released OSCAL assembly","meaning":"A released OSCAL assembly provides the capability without a schema change.","rendering":"a solid badge","short":"OSCAL assembly"},{"key":"proposed","label":"Proposed assembly","meaning":"The capability requires a proposed assembly. Interoperable use requires schema adoption and tool support for the new structure.","rendering":"a dashed badge","short":"Proposed"},{"key":"prop","label":"Namespaced property","meaning":"A property in the publisher's namespace provides the capability. Tools need a shared convention to interpret the property; the OSCAL schema does not define the meaning.","rendering":"a dotted badge","short":"Prop"}],"note":"The six questions and answer matrix compare OSCAL JSON examples, including content using proposed assemblies. tools/verify.py --matrix checks each cell against the example files. Notes describe supported capabilities and unresolved questions.","paths_note":"Each runner path shows one input document and one output document. The documents depend on whether the system owner or assessor runs the check.","proposed_assemblies":["assessment-check-id","associated-checks","checks","implementing-rules","result","rule-groups","rules"],"slots":[{"key":"rule","name":"What the rule requires","number":"1","optional":false,"question":"What condition must hold, and where is the requirement defined?","short":"Rule","why_separate":"A technology-specific requirement defines one testable condition. Parameter options and defaults belong with that definition where the selected model supports them."},{"binding_times":[{"authored_by":"Rule author","key":"inline","label":"Author-time, inline","mechanism":"The rule declares its control directly"},{"authored_by":"Rule author","key":"pointer","label":"Author-time, by pointer","mechanism":"A prop carries an external framework identifier that a consumer must resolve"},{"authored_by":"Rule author or third party","available_to":{"assessment-first":false,"catalog-first":true,"component-first":false,"executable-first":false},"key":"late","label":"Late, external","mechanism":"A separate artifact links a rule to a control after publication","why":"mapping-item.type is restricted by allOf to control and statement, and mapping-item has neither uuid nor href. External mappings therefore reach rules modelled as controls or control statements, not component rules or activities. This OSCAL schema constraint does not establish a preferred approach."}],"cost_of_leaving_empty":{"evidence":["observation.json","finding.json","finding-target.json"],"finding":"Not available. finding requires target; finding-target requires type, restricted by allOf to statement-id or objective-id, both control-derived.","observation":"Available. AR observation requires only uuid, description, methods and collected, with no control reference.","summary":"Without a control link, an assessor can record an observation but not a finding against a control statement or objective."},"key":"control-tie","name":"How the rule links to a control","number":"2","optional":true,"question":"Does this rule help satisfy a regulatory control, and which one?","short":"Control","why_separate":"A rule is finer-grained than a control and may serve several controls, one, or none. A control-linking mechanism is required, but using the mechanism is optional."},{"key":"check","name":"How the rule is tested","number":"3","optional":false,"question":"Which executable or procedure tests the rule?","short":"Check","why_separate":"A rule may have several checks, one per tool. The examples separate rule definitions from checks and reference external executables rather than embedding code in OSCAL."},{"key":"subject","name":"What the check runs against","not_established":true,"not_established_note":"The examples use assessment platforms, assets and components differently. A consistent distinction between the subject being assessed and the resources performing the assessment is not established here.","number":"4","optional":false,"question":"Is the subject a host, component, account or another resource?","short":"Subject","why_separate":"The subject identifies the assessed host, inventory item, component or account. Criterion 8 addresses response fidelity."},{"key":"actor","name":"What performs the check","not_established":true,"not_established_note":"The same distinction remains open in question 4. The approaches use different combinations of assessment-assets, assessment-platforms, uses-components, validation components, origin actors, task-level props and the method prop.","number":"5","optional":false,"question":"Which tool or person performs the check, and how is the runner identified?","short":"Runner","why_separate":"The runner may be a validation component, assessment platform, tool or person. The method prop identifies examine, interview or test."},{"group_name":"Implementation claims and assessment outcomes","key":"implementation-claim","name":"How the system claims it meets the rule","number":"6a","optional":false,"question":"How does the system owner describe implementation of the rule?","short":"Claim","why_separate":"The system owner provides a narrative claim of implementation and design intent per component. The SSP represents claims through implemented-requirement, statement and by-component."},{"group_name":"Implementation claims and assessment outcomes","key":"assessment-result","name":"How an assessment records the outcome","number":"6b","optional":false,"question":"Was the rule satisfied, when, and for which subject?","short":"Result","why_separate":"The assessor records evidence and a binary or graded outcome per subject at a point in time. The AR uses observation, finding and status. A desired-state rule has a binary satisfaction condition; the SSP implementation claim is narrative."}]},"data/snippets/aws-acm-backmatter-source.json":{"approach":"catalog-first","content":"{\n \"resources\": [\n {\n \"uuid\": \"ab8a6a36-2706-49e5-b87e-498c52ba6a61\",\n \"title\": \"AWS Regions Component Definition\",\n \"rlinks\": [\n {\n \"href\": \"../aws_regions.oscal.json\",\n \"media-type\": \"application/json\"\n }\n ]\n },\n {\n \"uuid\": \"f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"title\": \"AWS Security Hub Controls\",\n \"rlinks\": [\n {\n \"href\": \"../catalogs/aws_security-hub.oscal.json\",\n \"media-type\": \"application/json\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-backmatter-source","language":"json","pointer":"/component-definition/back-matter","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"Back-matter, source to the catalog"},"data/snippets/aws-acm-rsa-check-component.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"b5e8b205-cc1f-4bd0-9e51-4ebaab18f69a\",\n \"type\": \"software\",\n \"title\": \"acm-certificate-rsa-check\",\n \"description\": \"Checks if RSA certificates managed by AWS Certificate Manager (ACM) have a key length of at least '2048' bits. The rule is NON_COMPLIANT if the minimum key length is less than 2048 bits.\",\n \"props\": [\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"ACM_CERTIFICATE_RSA_CHECK\"\n },\n {\n \"name\": \"asset-type\",\n \"value\": \"automated-inspection\"\n },\n {\n \"name\": \"ResourceType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"AWS::ACM::Certificate\"\n }\n ],\n \"responsible-roles\": [\n {\n \"role-id\": \"owner\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"4f227b9d-b47b-4c06-bb55-8f3a17e29b74\",\n \"source\": \"#f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"description\": \"Security Hub control implementation\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"4de99497-e4fe-4dfd-80a7-ebbd59f06364\",\n \"control-id\": \"ACM.2\",\n \"description\": \"Implemented via AWS Config Rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-rsa-check-component","language":"json","pointer":"/component-definition/components/2","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"3","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"acm-certificate-rsa-check, the check component"},"data/snippets/aws-acm-service-rollup.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"ae50c910-9057-4345-89d9-c2ae4c1f0b08\",\n \"source\": \"#f32021d5-0666-4698-8a41-2e733c2035f3\",\n \"description\": \"AWS Security Hub control implementation\",\n \"implemented-requirements\": [\n {\n \"uuid\": \"c3e6d492-b3b6-46d9-9e2a-7d6d9922f3fa\",\n \"control-id\": \"ACM.1\",\n \"description\": \"Security Hub control ACM.1\"\n },\n {\n \"uuid\": \"551c5fc8-569a-4ea5-a0d8-0b524e9f4205\",\n \"control-id\": \"ACM.2\",\n \"description\": \"Security Hub control ACM.2\"\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm-service-rollup","language":"json","pointer":"/component-definition/components/0/control-implementations/0","section":null,"sha256_of_source_file":"5d4722e62660af4e0ab9a0acd08c337a860c674a748b9e6a0f41bcba47457fb1","slot":"2","source":"AWS/oscal-content-for-aws-services-main/component-definitions/acm.oscal.json","title":"AWS Certificate Manager, the service roll-up"},"data/snippets/aws-acm2-control.json":{"approach":"catalog-first","content":"{\n \"id\": \"ACM.2\",\n \"title\": \"ACM.2\",\n \"props\": [\n {\n \"name\": \"SeverityLabel\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"HIGH\"\n },\n {\n \"name\": \"TriggerType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Change Triggered\"\n },\n {\n \"name\": \"EvaluatedServices\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"ACM\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://docs.aws.amazon.com/console/securityhub/ACM.2/remediation\",\n \"rel\": \"remediation\"\n }\n ],\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"This control checks whether RSA certificates managed by AWS Certificate Manager use a key length of at least 2,048 bits. The control fails if the key length is smaller than 2,048 bits.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"RSA certificates managed by ACM should use a key length of at least 2,048 bits\"\n },\n {\n \"name\": \"guidance\",\n \"prose\": \"For information on how to correct this issue, consult the AWS Security Hub controls documentation.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"acm-certificate-rsa-check\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"acm-certificate-rsa-check\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-acm2-control","language":"json","pointer":"/catalog/groups/0/controls/1","section":null,"sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"ACM.2, the control"},"data/snippets/aws-config-service-bare.json":{"approach":"catalog-first","content":"{\n \"uuid\": \"9a02ef98-02b2-49c4-a3ea-3c546e830a15\",\n \"type\": \"service\",\n \"title\": \"AWS Config\",\n \"description\": \"AWS Config is a service that continuously monitors and records your AWS resource configurations and allows you to automate the evaluation of recorded configurations against desired settings.\",\n \"props\": [\n {\n \"name\": \"service-id\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Config Service\"\n },\n {\n \"name\": \"version\",\n \"value\": \"2014-11-12\"\n },\n {\n \"name\": \"availability\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"REGIONAL\"\n },\n {\n \"name\": \"label\",\n \"value\": \"AWS Config\",\n \"class\": \"marketingName\",\n \"group\": \"marketing\"\n },\n {\n \"name\": \"apiEndpointPrefix\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"arnNamespace\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"cloudTrailEventSource\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n },\n {\n \"name\": \"lifecycle-stage\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"generally-available\"\n },\n {\n \"name\": \"iamServicePrefix\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"config\"\n }\n ],\n \"links\": \"...\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-config-service-bare","language":"json","pointer":"/component-definition/components/0","section":null,"sha256_of_source_file":"d5049e46d7a1251932be3e74c1f9bace606ac9b5f5542249ccb884171394a6e7","slot":"5","source":"AWS/oscal-content-for-aws-services-main/component-definitions/config.oscal.json","title":"AWS Config, the engine that runs the checks"},"data/snippets/aws-control-cloudtrail2.json":{"approach":"catalog-first","content":"{\n \"id\": \"CloudTrail.2\",\n \"title\": \"CloudTrail.2\",\n \"props\": [\n {\n \"name\": \"SeverityLabel\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"MEDIUM\"\n },\n {\n \"name\": \"TriggerType\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"Periodic\"\n },\n {\n \"name\": \"EvaluatedServices\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"CloudTrail\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://docs.aws.amazon.com/console/securityhub/CloudTrail.2/remediation\",\n \"rel\": \"remediation\"\n }\n ],\n \"parts\": [\n {\n \"name\": \"overview\",\n \"prose\": \"This AWS control checks whether AWS CloudTrail is configured to use the server side encryption (SSE) AWS Key Management Service (AWS KMS) customer master key (CMK) encryption. The check will pass if the KmsKeyId is defined.\"\n },\n {\n \"name\": \"statement\",\n \"prose\": \"CloudTrail should have encryption at-rest enabled\"\n },\n {\n \"name\": \"guidance\",\n \"prose\": \"For information on how to correct this issue, consult the AWS Security Hub controls documentation.\"\n },\n {\n \"name\": \"assessment-method\",\n \"title\": \"cloud-trail-encryption-enabled\",\n \"props\": [\n {\n \"name\": \"TechnicalControlId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"cloud-trail-encryption-enabled\",\n \"class\": \"config-rule\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-21T03:10:41+00:00","id":"aws-control-cloudtrail2","language":"json","pointer":"/catalog/groups/15/controls/2","section":null,"sha256_of_source_file":"916b0d94359061632f068b2c131c0538c59231c1a065026f83a898f1a4334d33","slot":"1","source":"AWS/oscal-content-for-aws-services-main/catalogs/aws_security-hub.oscal.json","title":"CloudTrail.2, the control"},"data/snippets/aws-input-parameter.json":{"approach":"catalog-first","content":"[\n {\n \"name\": \"ConfigRuleId\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"IAM_PASSWORD_POLICY\"\n },\n {\n \"name\": \"asset-type\",\n \"value\": \"automated-inspection\"\n },\n {\n \"name\": \"MaxPasswordAge\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"90\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"PasswordReusePrevention\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"24\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"MinimumPasswordLength\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"14\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireNumbers\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireSymbols\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireLowercaseCharacters\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"RequireUppercaseCharacters\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"true\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"MinimumPasswordLength\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"7\",\n \"class\": \"InputParameter\"\n },\n {\n \"name\": \"PasswordReusePrevention\",\n \"ns\": \"http://aws.amazon.com/ns/oscal\",\n \"value\": \"4\",\n \"class\": \"InputParameter\"\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"aws-input-parameter","language":"json","pointer":"/component-definition/components/2/props","section":null,"sha256_of_source_file":"940cab9d3328d5ff55e6c69fbfae6fd4e846873d07f70ef7c096651bc8f750ab","slot":"1","source":"AWS/oscal-content-for-aws-services-main/component-definitions/iam.oscal.json","title":"InputParameter props, the parameter mechanism"},"data/snippets/ez-cis-remediation-step.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"7be22348-467b-563a-9c21-d438e47df7df\",\n \"title\": \"Remediation for Ensure cramfs kernel module is not available\",\n \"description\": \"Run the following script to unload and disable the `cramfs` module:\\n\\n**- IF -** the `cramfs` kernel module is available in ANY installed kernel:\\n\\n- Create a file ending in `.conf` with `install cramfs /bin/false` in the `/etc/modprobe.d/` directory\\n- Create a file ending in `.conf` with `blacklist cramfs` in the `/etc/modprobe.d/` directory\\n- Run `modprobe -r cramfs 2>/dev/null; rmmod cramfs 2>/de [truncated]\",\n \"props\": [\n {\n \"name\": \"assessment-status\",\n \"value\": \"automated\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-rule-id\",\n \"value\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"step-type\",\n \"value\": \"remediation\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-remediation-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/1","section":null,"sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS remediation step"},"data/snippets/ez-cis-resolution-status.json":{"approach":"assessment-first","content":"{\n \"description\": \"CIS Controls v8.0 derived from benchmark cc8:controlURI paths. Provide a CIS Controls v8 OSCAL catalog via --cis-catalog-v8 for authoritative control-id resolution.\",\n \"props\": [\n {\n \"name\": \"framework\",\n \"value\": \"CIS Controls v8.0\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"resolution-status\",\n \"value\": \"synthetic-ids\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ],\n \"include-controls\": \"...\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-resolution-status","language":"json","pointer":"/assessment-plan/reviewed-controls/control-selections/0","section":null,"sha256_of_source_file":"96220c0786192c3892ada09458a78bebb4d3f3bd20ed8f2cf8f9d776b8cd8fa8","slot":"meta","source":"Easy Dynamics/Center for Internet Security/CIS_PostgreSQL_18_Benchmark_v1_0_0_OSCAL_AP.json","title":"CIS resolution status"},"data/snippets/ez-cis-step-props.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"5c4c3bec-7bbe-521d-9a90-c04102edce9b\",\n \"title\": \"Audit for Ensure cramfs kernel module is not available\",\n \"description\": \"## Description\\n\\nThe `cramfs` filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems. A `cramfs` image can be used without having to first decompress the image.\\n\\n## Audit\\n\\nRun the following script to verify:\\n\\n**- IF -** the `cramfs` kernel module is available in ANY installed kernel, verify:\\n\\n- An entry including `/bin/true` or `/bin/false` exists in a file w [truncated]\",\n \"props\": [\n {\n \"name\": \"assessment-status\",\n \"value\": \"automated\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-rule-id\",\n \"value\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"step-type\",\n \"value\": \"audit\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-control-uri\",\n \"value\": \"http://cisecurity.org/20-cc/v7.0/control/9/subcontrol/2\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-control-uri\",\n \"value\": \"http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"CM-7\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"stig-finding-id\",\n \"value\": \"V-230498\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-safeguard-urn\",\n \"value\": \"urn:cisecurity.org:controls:8.0:4:8\",\n \"ns\": \"https://cisecurity.org/ns\"\n },\n {\n \"name\": \"cis-safeguard-urn\",\n \"value\": \"urn:cisecurity.org:controls:7.0:9:2\",\n \"ns\": \"https://cisecurity.org/ns\"\n }\n ],\n \"remarks\": \"Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-cis-step-props","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0","section":null,"sha256_of_source_file":"741bbe5e1b651aa74a0298942a91170df9348e8124746c0a16a0ccca911c803c","slot":"3","source":"Easy Dynamics/Center for Internet Security/CIS_Ubuntu_Linux_24_04_LTS_Benchmark_v2_OSCAL_AP.json","title":"CIS audit step props"},"data/snippets/ez-cisa-ar-finding.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"b5d014ae-23b1-51b8-845a-972f40def692\",\n \"title\": \"MS.AAD.1.1v1: Legacy Authentication Blocking\",\n \"target\": {\n \"type\": \"objective-id\",\n \"status\": {\n \"state\": \"satisfied\"\n },\n \"target-id\": \"ms.aad.1.1v1\"\n },\n \"description\": \"Conditional Access policy confirmed blocking all legacy authentication protocols for all users.\",\n \"related-observations\": [\n {\n \"observation-uuid\": \"941e3133-152b-5301-8762-abd228b5ee80\"\n }\n ]\n}","extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ar-finding","language":"json","pointer":"/assessment-results/results/0/findings/0","section":null,"sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"A finding, targeting an objective"},"data/snippets/ez-cisa-ar-observation.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"941e3133-152b-5301-8762-abd228b5ee80\",\n \"title\": \"Observation: MS.AAD.1.1v1 - Legacy Authentication Blocking\",\n \"types\": [\n \"finding\"\n ],\n \"methods\": [\n \"TEST\"\n ],\n \"remarks\": \"Legacy authentication is blocked tenant-wide via a Conditional Access policy in the enabled state. Control CM-7 is satisfied.\",\n \"subjects\": [\n {\n \"type\": \"assessment-activity\",\n \"subject-uuid\": \"422ccfe4-7b60-4fe8-81ff-3d4464cc6e05\"\n }\n ],\n \"collected\": \"2026-03-05T15:30:00-05:00\",\n \"description\": \"Examiner queried the Conditional Access policy configuration via Microsoft Graph API. A policy targeting all users with a condition for legacy authentication protocols and a grant control of 'Block' was identified and confirmed enabled.\"\n}","extracted_at":"2026-08-22T18:43:41+00:00","id":"ez-cisa-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","section":null,"sha256_of_source_file":"2e13fc65380024e6da79f539fec07f906659c100ae0cec555ed0541d5fce973d","slot":"6b","source":"Easy Dynamics/CISA BOD 25-01/ar-cisa-scuba-scubagear.json","title":"The observation it rests on, and what was examined"},"data/snippets/ez-cisa-assessment-assets.json":{"approach":"assessment-first","content":"{\n \"components\": [\n {\n \"uuid\": \"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\",\n \"type\": \"software\",\n \"title\": \"ScubaGear Plugin\",\n \"description\": \"CLI plugin on Comply0 platform for verifying M365 configuration settings using CISA ScubaGear.\",\n \"props\": [\n {\n \"name\": \"context\",\n \"value\": \"{\\\"plugin-path\\\":\\\"Comply0.Kansa.Extensions.ScubaGear.dll\\\",\\\"script-path\\\":\\\"Resources\\\\\\\\Invoke-ScubaGear.ps1\\\",\\\"app-id\\\":\\\"c4d39d69-aea7-4acc-af2c-45c502d3a308\\\",\\\"opa-path\\\":\\\"/usr/local/bin\\\"}\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"status\": {\n \"state\": \"operational\"\n }\n }\n ],\n \"assessment-platforms\": [\n {\n \"uuid\": \"15000cf8-2f2a-4417-8b93-60a1f209ee95\",\n \"title\": \"Comply0 cATO Agent\",\n \"uses-components\": [\n {\n \"component-uuid\": \"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-assessment-assets","language":"json","pointer":"/assessment-plan/assessment-assets","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-assets"},"data/snippets/ez-cisa-context-activity.json":{"approach":"assessment-first","content":"[\n {\n \"name\": \"context\",\n \"value\": \"{\\\"ProductNames\\\":\\\"aad\\\",\\\"component-uuid\\\":\\\"abe8d6c2-8508-4d22-aa2b-5e001ff3c6f7\\\"}\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n },\n {\n \"name\": \"check\",\n \"value\": \"MS.AAD\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n]","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-activity","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/props","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA activity context prop"},"data/snippets/ez-cisa-context-step.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"4b7f6f09-84da-4c03-ba7b-d02ff52d5b69\",\n \"title\": \"MS.AAD.3.7v1\",\n \"description\": \"Managed devices SHOULD be required for authentication.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"EXAMINE\"\n },\n {\n \"name\": \"criticality\",\n \"ns\": \"http://cisa.gov/ns/oscal\",\n \"value\": \"SHOULD\"\n },\n {\n \"name\": \"context\",\n \"ns\": \"http://comply0.com/ns/oscal\",\n \"value\": \"{\\\"SkipHybridJoinCheck\\\":false}\"\n },\n {\n \"name\": \"check\",\n \"value\": \"MS.AAD.3.7\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"links\": [\n {\n \"href\": \"https://github.com/cisagov/ScubaGear/tree/main/PowerShell/ScubaGear/baselines/aad.md#msaad37v1\",\n \"rel\": \"canonical\"\n },\n {\n \"href\": \"https://attack.mitre.org/techniques/T1078/\",\n \"text\": \"T1078: Valid Accounts\",\n \"rel\": \"mitre\"\n },\n {\n \"href\": \"https://attack.mitre.org/techniques/T1078/004/\",\n \"text\": \"T1078.004: Cloud Accounts\",\n \"rel\": \"mitre\"\n }\n ],\n \"reviewed-controls\": {\n \"control-selections\": [\n {\n \"include-controls\": [\n {\n \"control-id\": \"ac-20\",\n \"statement-ids\": [\n \"ac-20_smt.b\"\n ]\n },\n {\n \"control-id\": \"ia-3\",\n \"statement-ids\": [\n \"ia-3_smt\"\n ]\n }\n ]\n }\n ]\n },\n \"remarks\": \"The security risk of an adversary authenticating to the tenant from their own device is reduced by requiring a managed device to authenticate. Managed devices are under the provisioning and control of the agency. [OMB-22-09](https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf) states, \\\"When authorizing users to access resources, agencies must consider at least one device-level signal [truncated]\"\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-context-step","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/10","section":null,"sha256_of_source_file":"0dac47d1c7ba18908c0bd48a8c4676e3c862a8b99dcbb14dc5eb73123b753653","slot":"3","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-maester.json","title":"CISA step context prop"},"data/snippets/ez-cisa-import-ssp.json":{"approach":"assessment-first","content":"{\n \"href\": \"#75e00698-e43b-4d6f-be7f-d1227a3a3e39\",\n \"remarks\": \"Link the SAP to the SSP.\"\n}","extracted_at":"2026-08-22T18:44:16+00:00","id":"ez-cisa-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"import-ssp, resolving to a resource in the same document"},"data/snippets/ez-cisa-no-ssp-resource.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"f56da5c6-da67-4c40-acc8-6814bf7aa374\",\n \"title\": \"System's Full Name\",\n \"description\": \"# USE THIS RESOURCE WHEN NO OSCAL-BASED SSP EXISTS\\n\\nBriefly describe the system. This will appear in the SAR.\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"no-oscal-ssp\"\n },\n {\n \"name\": \"import-profile\",\n \"ns\": \"https://fedramp.gov/ns/oscal\",\n \"value\": \"#890170c3-d4fa-4d25-ab96-8e4bf7cc237c\"\n },\n {\n \"name\": \"purpose\",\n \"ns\": \"https://fedramp.gov/ns/oscal\",\n \"value\": \"Briefly state the system's purpose. This will appear in the SAR.\"\n }\n ],\n \"remarks\": \"Only include this resource if no OSCAL-based SSP is available.\"\n}","extracted_at":"2026-08-22T18:46:12+00:00","id":"ez-cisa-no-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/0","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The alternative resource, where no OSCAL system security plan exists"},"data/snippets/ez-cisa-ssp-resource.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"75e00698-e43b-4d6f-be7f-d1227a3a3e39\",\n \"title\": \"Kalvico Enterprise ICAM SSP\",\n \"props\": [\n {\n \"name\": \"type\",\n \"value\": \"oscal-ssp\"\n }\n ],\n \"rlinks\": [\n {\n \"href\": \"system-security-plan.json\",\n \"media-type\": \"application/oscal.catalog+json\"\n }\n ],\n \"remarks\": \"Use this to point to an OSCAL-based SSP.\"\n}","extracted_at":"2026-08-22T18:43:40+00:00","id":"ez-cisa-ssp-resource","language":"json","pointer":"/assessment-plan/back-matter/resources/1","section":null,"sha256_of_source_file":"97dad5eeba5efdb6b45ce22b92b9316df1479808bca698235c7dfc2d00ed37ee","slot":"6a","source":"Easy Dynamics/CISA BOD 25-01/assessment-plan.json","title":"The resource a resolved import-ssp lands on"},"data/snippets/ez-cisa-step-reviewed.json":{"approach":"assessment-first","content":"{\n \"control-selections\": [\n {\n \"include-controls\": [\n {\n \"control-id\": \"cm-7\",\n \"statement-ids\": [\n \"cm-7_smt\"\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-step-reviewed","language":"json","pointer":"/assessment-plan/local-definitions/activities/0/steps/0/reviewed-controls","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"2","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA step reviewed-controls"},"data/snippets/ez-cisa-task-timing.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"c2f71c67-3d4c-43ba-ad9d-949d0396413f\",\n \"type\": \"action\",\n \"title\": \"Automate assessment of ScubaGear tests using Comply0 Platform Assessment Agent\",\n \"description\": \"Execute CISA SCuBA assessment tests using the Comply0 cATO Agent with ScubaGear plugin.\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"value\": \"15000cf8-2f2a-4417-8b93-60a1f209ee95\",\n \"ns\": \"http://comply0.com/ns/oscal\"\n }\n ],\n \"timing\": {\n \"at-frequency\": {\n \"period\": 24,\n \"unit\": \"hours\"\n }\n },\n \"associated-activities\": [\n {\n \"activity-uuid\": \"760fe3fc-45af-4c62-b095-265a56a1dedf\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"4e391cf6-5549-46f3-b3d7-aad12cd5a226\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"2c69fb5c-056f-4788-be36-723b939a4766\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"04319877-e72d-4967-b968-4852e6738113\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"53852402-8cd6-4e1c-a559-f31bb004a66e\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"c98b996e-8dae-40ef-8b40-100ffbe9e5e3\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n },\n {\n \"activity-uuid\": \"5f62a033-3847-43ec-bafd-3dc1a7621029\",\n \"subjects\": [\n {\n \"type\": \"inventory-item\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-cisa-task-timing","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"5","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA task, with timing"},"data/snippets/ez-stig-activity-v259312.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"e69fb43b-9565-58f6-badc-e31834e575f6\",\n \"title\": \"V-259312: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"stig-group-id\",\n \"value\": \"V-259312\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-rule-id\",\n \"value\": \"SV-259312r961818_rule\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"category\",\n \"value\": \"CAT II\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"srg\",\n \"value\": \"SRG-APP-000501-DB-000336\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"sequence\",\n \"value\": \"101\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-000172\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"au-12\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"documentable\",\n \"value\": \"false\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"93fcfc80-5643-5c15-835d-aaa4d000daeb\",\n \"title\": \"Check: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"## Check\\n\\nExecute the following SQL the \\\"enterprisedb\\\" operating system user:\\n\\n```bash\\n> psql edb -c \\\"SHOW edb_audit_statement\\\"\\n```\\n\\nIf the result is not \\\"all\\\" or if the current setting for this requirement has not been noted and approved by the organization in the system documentation, this is a finding.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"check\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"assessment-method\",\n \"value\": \"TEST\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-000172\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"au-12\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n },\n {\n \"uuid\": \"e58bf90b-06dc-537f-81a9-68e61e87b7a7\",\n \"title\": \"Remediate: The EDB Postgres Advanced Server must generate audit records when security objects are deleted.\",\n \"description\": \"## Remediate\\n\\nExecute the following SQL as the \\\"enterprisedb\\\" operating system user:\\n\\n```bash\\n> psql edb -c \\\"ALTER SYSTEM SET edb_audit_statement = 'all'\\\"\\n> psql edb -c \\\"SELECT pg_reload_conf()\\\"\\n```\\n\\nor\\n\\nUpdate the system documentation to note the organizationally approved setting and corresponding justification of the setting for this requirement.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"remediate\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"EPAS-00-011400\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n }\n ],\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"au-12\"\n }\n ]\n }\n ]\n },\n \"remarks\": \"Source SRG: SRG-APP-000501-DB-000336\\nDPMS Target identifier: 5575\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-activity-v259312","language":"json","pointer":"/assessment-plan/local-definitions/activities/100","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG activity V-259312"},"data/snippets/ez-stig-import-ssp.json":{"approach":"assessment-first","content":"{\n \"href\": \"PLACEHOLDER\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-import-ssp","language":"json","pointer":"/assessment-plan/import-ssp","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"meta","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG import-ssp, an unresolved placeholder"},"data/snippets/ez-stig-related-controls.json":{"approach":"assessment-first","content":"{\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"au-12\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-related-controls","language":"json","pointer":"/assessment-plan/local-definitions/activities/100/related-controls","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"2","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG related-controls, the control tie"},"data/snippets/ez-stig-sc28-v270747.json":{"approach":"assessment-first","content":"{\n \"uuid\": \"c8eaf2b1-c63f-5693-a1a5-e4e66a760c41\",\n \"title\": \"V-270747: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system.\\n\\nThis requirement addresses protection of user-generated data, as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.\\n\\nSatisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS [truncated]\",\n \"props\": [\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"stig-group-id\",\n \"value\": \"V-270747\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-rule-id\",\n \"value\": \"SV-270747r1066730_rule\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"category\",\n \"value\": \"CAT II\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"srg\",\n \"value\": \"SRG-OS-000185-GPOS-00079\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"sequence\",\n \"value\": \"102\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-001199\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002475\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002476\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-004910\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.1\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.3\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"documentable\",\n \"value\": \"false\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ],\n \"steps\": [\n {\n \"uuid\": \"0423503f-e675-545e-8a9b-740c1b5f51ce\",\n \"title\": \"Check: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"## Check\\n\\nNote: If there is a documented and approved mission requirement for data-at-rest to not be encrypted, this requirement is not applicable.\\n\\nVerify Ubuntu 24.04 LTS prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption.\\n\\nDetermine the partition layout for the system with the following command:\\n\\n```bash\\n$ sudo fdisk -l\\n(..)\\nDisk /dev/vda: 15 GiB, 16106127360 bytes, 31457280 sectors\\nUnits: sectors of 1 * 512 = 512 bytes\\nSector size (logical/physical): 512 bytes / 512 bytes\\nI/O size (minimum/optimal): 512 bytes / 512 byte [truncated]\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"check\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"assessment-method\",\n \"value\": \"TEST\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-001199\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002475\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-002476\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"cci\",\n \"value\": \"CCI-004910\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.1\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"nist-control\",\n \"value\": \"sc-28.3\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n },\n {\n \"uuid\": \"0820d37b-cdcb-5e32-a660-e1111ad328dc\",\n \"title\": \"Remediate: Ubuntu 24.04 LTS handling data requiring \\\"data at rest\\\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\",\n \"description\": \"## Remediate\\n\\nTo encrypt an entire partition, dedicate a partition for encryption in the partition layout.\\n\\nNote: Encrypting a partition in an already-installed system is more difficult because it will need to be resized and existing partitions changed.\",\n \"props\": [\n {\n \"name\": \"step-type\",\n \"value\": \"remediate\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"stig-id\",\n \"value\": \"UBTU-24-600090\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n },\n {\n \"name\": \"severity\",\n \"value\": \"medium\",\n \"ns\": \"https://public.cyber.mil/stigs/ns\"\n }\n ]\n }\n ],\n \"related-controls\": {\n \"control-selections\": [\n {\n \"description\": \"NIST SP 800-53 controls associated with this STIG rule (derived from CCI references).\",\n \"include-controls\": [\n {\n \"control-id\": \"sc-28\"\n },\n {\n \"control-id\": \"sc-28.1\"\n },\n {\n \"control-id\": \"sc-28.3\"\n }\n ]\n }\n ]\n },\n \"remarks\": \"Source SRG: SRG-OS-000185-GPOS-00079\\nDPMS Target identifier: 5673\"\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-stig-sc28-v270747","language":"json","pointer":"/assessment-plan/local-definitions/activities/101","section":null,"sha256_of_source_file":"aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e","slot":"1","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/ubuntu24.json","title":"STIG activity V-270747, SC-28"},"data/snippets/ez-subjects-explicit.json":{"approach":"assessment-first","content":"[\n {\n \"type\": \"inventory-item\",\n \"description\": \"The M365 tenant instance being assessed. Assume it's defined in SSP.\",\n \"include-subjects\": [\n {\n \"subject-uuid\": \"791778c1-234b-4e30-8490-07ad2e6fec92\",\n \"type\": \"inventory-item\"\n }\n ]\n }\n]","extracted_at":"2026-09-10T14:51:40+00:00","id":"ez-subjects-explicit","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"f6e67d58433922c3e6eef8253904ae7b127964f6919d8d74fa38d613947e971e","slot":"4","source":"Easy Dynamics/CISA BOD 25-01/ap-cisa-scuba-scubagear.json","title":"CISA assessment-subjects, one inventory item"},"data/snippets/ez-subjects-includeall.json":{"approach":"assessment-first","content":"[\n {\n \"type\": \"component\",\n \"description\": \"Target system being assessed against the STIG.\",\n \"include-all\": {}\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"ez-subjects-includeall","language":"json","pointer":"/assessment-plan/assessment-subjects","section":null,"sha256_of_source_file":"997ecb028020fdacee66352651a5992e5a1ec1b964d1b332d6c7a5480b7897b6","slot":"4","source":"Easy Dynamics/DISA/STIG_XCCDF to OSCAL Assessment Plans/epas.json","title":"STIG assessment-subjects, include-all"},"data/snippets/ibm-ap-activity.json":{"approach":"component-first","content":"[\n {\n \"activities\": [\n {\n \"uuid\": \"a1b2c3d4-1111-4aaa-8888-111111111111\",\n \"description\": \"Execute Ansible checks to validate the controls.\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"check-ids\": [\n \"check-1\",\n \"check-2\"\n ]\n },\n {\n \"uuid\": \"b2c3d4e5-2222-4bbb-9999-222222222222\",\n \"description\": \"Execute OSCAP checks to validate the controls.\",\n \"assessment-asset-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984e8\",\n \"check-ids\": [\n \"check-1\",\n \"check-3\"\n ]\n }\n ]\n }\n]","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-activity","language":"json","pointer":"/assessment-plan/local-defintions","section":null,"sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"5","source":"IBM/assessment-plan.json","title":"AP activity, binding check-ids"},"data/snippets/ibm-ap-task-subjects.json":{"approach":"component-first","content":"{\n \"uuid\": \"b3504d22-0e75-4dd7-9247-618661beba4e\",\n \"type\": \"action\",\n \"title\": \"Execute Ansible Checks\",\n \"description\": \"The assessor will execute the Ansible checks defined in the validation component using the Ansible assessment platform to collect evidence for the assessment.\",\n \"props\": [\n {\n \"name\": \"assessment-platform\",\n \"value\": \"d8c9a1e5-1c3b-4f0b-9c8e-2a1b2c3d4e5f\"\n }\n ],\n \"timing\": {\n \"at-frequency\": {\n \"period\": 1,\n \"unit\": \"days\"\n }\n },\n \"associated-activities\": [\n {\n \"activity-uuid\": \"a1b2c3d4-1111-4aaa-8888-111111111111\",\n \"subjects\": [\n {\n \"subject-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984fe\"\n }\n ]\n },\n {\n \"activity-uuid\": \"b2c3d4e5-2222-4bbb-9999-222222222222\",\n \"subjects\": [\n {\n \"subject-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984ff\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-ap-task-subjects","language":"json","pointer":"/assessment-plan/tasks/0","section":null,"sha256_of_source_file":"fd50fa2d32cb8a19d9baab6bc4679d863e0b8bddc7902a01c34b25927f61b7d6","slot":"4","source":"IBM/assessment-plan.json","title":"AP task, subjects and platform"},"data/snippets/ibm-ar-observation.json":{"approach":"component-first","content":"{\n \"uuid\": \"6c0a18ff-36b4-45b2-9e8b-6e3011bee6b1\",\n \"description\": \"check-result\",\n \"assessment-check-id\": \"check-1\",\n \"assessment-asset/component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984e8\",\n \"result\": \"pass\",\n \"props\": [\n {\n \"name\": \"idref\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"xccdf_org.ssgproject.content_rule_package_prelink_removed\"\n },\n {\n \"name\": \"result\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"pass\"\n },\n {\n \"name\": \"time\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"2025-02-26T03:47:26-05:00\"\n },\n {\n \"name\": \"severity\",\n \"ns\": \"https://oscal-compass.github.io/compliance-trestle/schemas/oscal/ar/OpenSCAP\",\n \"value\": \"medium\"\n }\n ],\n \"methods\": [\n \"TEST-AUTOMATED\"\n ],\n \"subjects\": [\n {\n \"subject-uuid\": \"c8ca2d73-c917-4901-9098-71b2c601f471\",\n \"type\": \"inventory-item\"\n }\n ],\n \"collected\": \"2025-02-26T12:45:58+00:00\"\n}","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-ar-observation","language":"json","pointer":"/assessment-results/results/0/observations/0","section":null,"sha256_of_source_file":"06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806","slot":"6b","source":"IBM/assessment-result.json","title":"AR observation, carrying a result"},"data/snippets/ibm-cos-component.json":{"approach":"component-first","content":"{\n \"uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\",\n \"type\": \"service\",\n \"title\": \"COS\",\n \"description\": \"COS\",\n \"rules\": [\n {\n \"id\": \"cos_access_endpoint_type\",\n \"description\": \"Ensure Cloud Object Storage is accessible only by using {param: endpoint_access} endpoints\",\n \"params\": [\n {\n \"id\": \"endpoint_access\",\n \"label\": \"Endpoint Access type\",\n \"select\": {\n \"how-many\": \"one\",\n \"choice\": [\n \"public\",\n \"private\",\n \"direct\"\n ]\n }\n }\n ]\n },\n {\n \"id\": \"cos_encryption_hyperprotect_key_configured\",\n \"description\": \"Ensure Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)\"\n }\n ],\n \"control-implementations\": [\n {\n \"uuid\": \"08159454-994c-49ed-8f78-f2293b1274a2\",\n \"source\": \"trestle://profiles/ACME_official/profile.json\",\n \"description\": \"ACME Official Profile\",\n \"set-parameters\": [\n {\n \"param-id\": \"endpoint_access\",\n \"values\": [\n \"private\"\n ]\n }\n ],\n \"implemented-requirements\": [\n {\n \"uuid\": \"c6ccfcbc-4553-40e6-b4e8-eadbff8d4756\",\n \"control-id\": \"ac-4\",\n \"description\": \"This control is implmeneted by ensuring the COS is only available on private endpoints.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"cos_access_endpoint_type\"\n }\n ]\n },\n {\n \"uuid\": \"455563ca-c454-41d5-aa3b-f57843d95aab\",\n \"control-id\": \"sc-28\",\n \"description\": \"Ensure that data is encrypted and the key is managed by the customer.\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"cos_encryption_hyperprotect_key_configured\"\n }\n ]\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-22T16:15:34+00:00","id":"ibm-cos-component","language":"json","pointer":"/component-definition/components/0","section":null,"sha256_of_source_file":"4944f506f1f2127950e0fb2cd8e251e66e4ec5a83c5e9126ef147117ad233f4a","slot":"1","source":"IBM/cos-component-definition.json","title":"COS component, carrying rules"},"data/snippets/ibm-statement-rules.json":{"approach":"component-first","content":"{\n \"uuid\": \"c6ccfcbc-4553-40e6-b4e8-eadbff8d4756\",\n \"control-id\": \"ia-5.1\",\n \"description\": \"\",\n \"statements\": [\n {\n \"statement-id\": \"ia-5.1_smt.a\",\n \"uuid\": \"08cc185d-27d8-4412-9cb4-25ebf1397a39\",\n \"description\": \"\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"idservice_password_min_length\"\n },\n {\n \"rule-id\": \"idservice_strong_pass_enabled\"\n }\n ]\n },\n {\n \"statement-id\": \"ia-5.1_smt.e\",\n \"uuid\": \"89f1f3be-d915-4134-94ab-577cba3f3c9a\",\n \"description\": \"\",\n \"implementing-rules\": [\n {\n \"rule-id\": \"idservice_password_not_reuse_min_count\"\n }\n ]\n }\n ]\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-statement-rules","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/0","section":null,"sha256_of_source_file":"36b8140ae1272f5e6fef535409375e3cbbd0f0e8387b378ee7d550a3a1760eaf","slot":"2","source":"IBM/idservice-component-definition.json","title":"implementing-rules on ia-5.1"},"data/snippets/ibm-validation-ansible.json":{"approach":"component-first","content":"{\n \"component-definition\": {\n \"uuid\": \"bbdf7ee6-3e0a-4065-8ecf-50f4129de473\",\n \"metadata\": {\n \"title\": \"Demo validation component definition\",\n \"last-modified\": \"2026-05-15T14:29:37+00:00\",\n \"version\": \"1.0\",\n \"oscal-version\": \"1.2.1\"\n },\n \"components\": [\n {\n \"uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a984f8\",\n \"type\": \"validation\",\n \"title\": \"ANSIBLE\",\n \"description\": \"ANSIBLE\",\n \"checks\": [\n {\n \"id\": \"check-1\",\n \"description\": \"Check Cloud Object Storage is accessible only by using private endpoints\",\n \"rule-id\": \"cos_access_endpoint_type\",\n \"target-component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\"\n },\n {\n \"id\": \"check-2\",\n \"description\": \"Check Cloud Object Storage is enabled with customer-managed encryption and Keep Your Own Key (KYOK)\",\n \"rule-id\": \"cos_encryption_hyperprotect_key_configured\",\n \"target-component-uuid\": \"0c410eb1-52cd-40bc-bf1d-c80126a985f9\"\n }\n ]\n }\n ]\n }\n}","extracted_at":"2026-08-20T22:38:41+00:00","id":"ibm-validation-ansible","language":"json","pointer":"$","section":null,"sha256_of_source_file":"f22d30678a24146f1be62758a843ad1f34c34eb6a2c00b1008e84a163c4cadbd","slot":"3","source":"IBM/ansible-validation-component-definition.json","title":"Ansible validation component, and its checks"},"data/snippets/pf-cis-map-1-1-1-1.json":{"approach":"executable-first","content":"{\n \"uuid\": \"15411d58-ef50-5bd9-9ac0-f4d53602cc2c\",\n \"relationship\": \"subset-of\",\n \"sources\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\"\n }\n ],\n \"targets\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"cm-7\"\n }\n ]\n}","extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-map-1-1-1-1","language":"json","pointer":"/mapping-collection/mappings/0/maps/0","section":null,"sha256_of_source_file":"de1c04d1ffb7b1e82b8a1e3b41fc848a782790868c419e7e56bf96fedcb3a7ed","slot":"2","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json","title":"CIS 1.1.1.1 mapped to CM-7, from the benchmark's own reference"},"data/snippets/pf-cis-method-1-1-1-1.json":{"approach":"executable-first","content":"{\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_asm\",\n \"name\": \"assessment-method\",\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:*:*:*:lts:*:*:*\",\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\": \"stdout-regex\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"\\\\*\\\\* PASS \\\\*\\\\*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_obj\"\n },\n {\n \"rel\": \"script\",\n \"href\": \"#57406427-e772-5765-9a71-89d9da9cd0b3\"\n }\n ],\n \"prose\": \"Run 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 within the `/etc/modprobe.d/` directory\\n\\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\\n\\n- The module is not loaded in the running kernel\\n\\n**- IF -** the `cramfs` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\\n\\n```bash\\n#!/usr/bin/env bash\\n\\n{\\n a_output=() a_output2=() a_output3=() l_dl=\\\"\\\" l_mod_name=\\\"cramfs\\\" l_mod_type=\\\"fs\\\"\\n l_mod_path=\\\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\\\"\\n f_ [truncated]\"\n}","extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-method-1-1-1-1","language":"json","pointer":"/catalog/groups/0/groups/0/groups/0/controls/0/parts/3","section":null,"sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"3","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"CIS 1.1.1.1 assessment method, carrying the published audit script"},"data/snippets/pf-cis-objective-and-param.json":{"approach":"executable-first","content":"{\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"title\": \"1.1.1.1 Ensure cramfs kernel module is not available\",\n \"params\": [\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_xccdf-value-regex\",\n \"class\": \"XCCDF_VALUE_REGEX\",\n \"label\": \"Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX\",\n \"values\": [\n \"cramfs:fs\"\n ]\n }\n ],\n \"links\": [\n {\n \"rel\": \"reference\",\n \"href\": \"http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8\"\n }\n ],\n \"parts\": [\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_smt\",\n \"name\": \"statement\",\n \"prose\": \"...\"\n },\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_rationale\",\n \"name\": \"rationale\",\n \"prose\": \"...\"\n },\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_obj\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ensure cramfs kernel module is not available\"\n },\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_asm\",\n \"name\": \"assessment-method\",\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:*:*:*:lts:*:*:*\",\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\": \"stdout-regex\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"\\\\*\\\\* PASS \\\\*\\\\*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_obj\"\n },\n {\n \"rel\": \"script\",\n \"href\": \"#57406427-e772-5765-9a71-89d9da9cd0b3\"\n }\n ],\n \"prose\": \"...\"\n },\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_rem\",\n \"name\": \"remediation\",\n \"ns\": \"https://example.org/ns/oscal-automation\",\n \"prose\": \"...\"\n }\n ]\n}","extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-objective-and-param","language":"json","pointer":"/catalog/groups/0/groups/0/groups/0/controls/0","section":null,"sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"1","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"CIS 1.1.1.1 as a control: the objective, and the exported value as a parameter"},"data/snippets/pf-cis-platform.json":{"approach":"executable-first","content":"{\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n}","extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-platform","language":"json","pointer":"/catalog/groups/0/groups/0/groups/0/controls/0/parts/3/props/1","section":null,"sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"4","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"The platform a method applies to"},"data/snippets/pf-cis-run-props.json":{"approach":"executable-first","content":"[\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*\",\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\": \"stdout-regex\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"\\\\*\\\\* PASS \\\\*\\\\*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n]","extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-run-props","language":"json","pointer":"/catalog/groups/0/groups/0/groups/0/controls/0/parts/3/props","section":null,"sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"5","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"What an executor reads: the method's props"},"data/snippets/pf-cis-script-resource.json":{"approach":"executable-first","content":"{\n \"uuid\": \"57406427-e772-5765-9a71-89d9da9cd0b3\",\n \"title\": \"nix_module_chk_v3.sh\",\n \"description\": \"Script Check Engine script, named by the check expression of 13 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.\",\n \"rlinks\": [\n {\n \"href\": \"nix_module_chk_v3.sh\",\n \"media-type\": \"application/x-sh\"\n }\n ]\n}","extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-cis-script-resource","language":"json","pointer":"/catalog/back-matter/resources/52","section":null,"sha256_of_source_file":"d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2","slot":"3","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json","title":"The SCE script the method links to, as a back-matter resource"},"data/snippets/pf-rules-requirement.json":{"approach":"executable-first","content":"{\n \"uuid\": \"ddc6b3e7-be8e-5726-a50d-11556f483150\",\n \"control-id\": \"cisc-008.009\",\n \"description\": \"6.1.3.3 Ensure journald is configured to send logs to rsyslog\",\n \"automation-scripts\": [\n {\n \"uuid\": \"c337f042-ddc5-5936-9a71-70bfd4d11ed0\",\n \"benchmark-rule-id\": \"6.1.3.3\",\n \"script-type\": \"audit\",\n \"language\": \"bash\",\n \"applicable-profiles\": [\n \"Level 1 - Server\",\n \"Level 2 - Server\",\n \"Level 1 - Workstation\",\n \"Level 2 - Workstation\"\n ],\n \"evaluation-criteria\": {\n \"method\": \"stdout-regex\",\n \"pass-condition\": \"^\\\\*\\\\* PASS \\\\*\\\\*$\",\n \"fail-condition\": \"^\\\\*\\\\* FAIL \\\\*\\\\*$\"\n },\n \"payload\": \"#!/usr/bin/env bash\\n\\n{\\n a_output=() a_output2=() l_analyze_cmd=\\\"$(readlink -f /bin/systemd-analyze)\\\" l_systemd_config_file=\\\"systemd/journald.conf\\\"\\n a_parameters=(\\\"ForwardToSyslog=yes\\\")\\n f_config_file_parameter_chk()\\n {\\n l_used_parameter_setting=\\\"\\\"\\n while IFS= read -r l_file; do\\n l_file=\\\"$(tr -d '# ' <<< \\\"$l_file\\\")\\\"\\n l_used_parameter_setting=\\\"$(grep -PHs -- '^\\\\h*'\\\"$l_parameter_name\\\"'\\\\b' \\\"$l_file\\\" | tail -n 1)\\\"\\n [ -n \\\"$l_used_parameter_setting\\\" ] && break [truncated]\"\n },\n {\n \"uuid\": \"64454ac1-9539-51e5-8366-3bf5798e7935\",\n \"benchmark-rule-id\": \"6.1.3.3\",\n \"script-type\": \"remediation\",\n \"language\": \"bash\",\n \"applicable-profiles\": [\n \"Level 1 - Server\",\n \"Level 2 - Server\",\n \"Level 1 - Workstation\",\n \"Level 2 - Workstation\"\n ],\n \"payload\": \"#!/usr/bin/env bash\\n\\n{\\n a_settings=(\\\"ForwardToSyslog=yes\\\")\\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\\n if grep -Psq -- '^\\\\h*\\\\[Journal\\\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\\n printf '%s\\\\n' \\\"\\\" \\\"${a_settings[@]}\\\" >> /etc/systemd/journald.conf.d/60-journald.conf\\n else\\n printf '%s\\\\n' \\\"\\\" \\\"[Journal]\\\" \\\"${a_settings[@]}\\\" >> /etc/systemd/journald.conf.d/60-journald.conf\\n fi\\n}\\n\"\n }\n ],\n \"props\": \"...\"\n}","extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-rules-requirement","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/18","section":null,"sha256_of_source_file":"4e08c03e080234a07ed6155e06f6b0c0756e64d28210c33473c92ffa2cb95929","slot":"3","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json","title":"CIS Control 8.9 as an implemented requirement carrying an audit and a remediation script, the Rules shape"},"data/snippets/pf-rules-script-1-1-1-1.json":{"approach":"executable-first","content":"{\n \"uuid\": \"a377e3f3-6e54-5ebf-9010-96b245f533da\",\n \"benchmark-rule-id\": \"1.1.1.1\",\n \"script-type\": \"audit\",\n \"language\": \"bash\",\n \"applicable-profiles\": [\n \"Level 1 - Server\",\n \"Level 2 - Server\",\n \"Level 1 - Workstation\",\n \"Level 2 - Workstation\"\n ],\n \"evaluation-criteria\": {\n \"method\": \"stdout-regex\",\n \"pass-condition\": \"^\\\\*\\\\* PASS \\\\*\\\\*$\",\n \"fail-condition\": \"^\\\\*\\\\* FAIL \\\\*\\\\*$\"\n },\n \"payload\": \"#!/usr/bin/env bash\\n\\n{\\n a_output=() a_output2=() a_output3=() l_dl=\\\"\\\" l_mod_name=\\\"cramfs\\\" l_mod_type=\\\"fs\\\"\\n l_mod_path=\\\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\\\"\\n f_module_chk()\\n {\\n l_dl=\\\"y\\\" a_showconfig=()\\n while IFS= read -r l_showconfig; do\\n a_showconfig+=(\\\"$l_showconfig\\\")\\n done < <(modprobe --showconfig | grep -P -- '\\\\b(install|blacklist)\\\\h+'\\\"${l_mod_chk_name//-/_}\\\"'\\\\b')\\n if ! lsmod | grep \\\"$l_mod_chk_name\\\" &> /dev/null; then\\n a_output+=(\\\" - kernel module: \\\\\\\"$l_mod_name\\\\\\\" is not loaded\\\")\\n else\\n a_output2+=(\\\" - kernel module: \\\\\\\"$l_mod_name\\\\\\\" is loaded\\\")\\n fi\\n if grep -Pq -- '\\\\binstall\\\\h+'\\\"${l_mod_chk_nam [truncated]\"\n}","extracted_at":"2026-09-09T20:09:56+00:00","id":"pf-rules-script-1-1-1-1","language":"json","pointer":"/component-definition/components/0/control-implementations/0/implemented-requirements/8/automation-scripts/0","section":null,"sha256_of_source_file":"4e08c03e080234a07ed6155e06f6b0c0756e64d28210c33473c92ffa2cb95929","slot":"3","source":"site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json","title":"CIS 1.1.1.1 audit script as an automation-scripts object, the Rules shape"},"data/snippets/pf-stig-import.json":{"approach":"executable-first","content":"{\n \"href\": \"https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json\",\n \"include-controls\": [\n {\n \"with-ids\": [\n \"ac-10\",\n \"ac-11\",\n \"ac-11.1\",\n \"ac-12\",\n \"ac-17.1\",\n \"ac-17.2\",\n \"ac-2.2\",\n \"ac-2.3\",\n \"ac-2.4\",\n \"ac-3\",\n \"ac-3.4\",\n \"ac-6.10\",\n \"ac-6.8\",\n \"ac-6.9\",\n \"ac-7\",\n \"ac-8\",\n \"au-12\",\n \"au-12.3\",\n \"au-14.1\",\n \"au-3\",\n \"au-3.1\",\n \"au-4\",\n \"au-4.1\",\n \"au-5\",\n \"au-5.1\",\n \"au-6.4\",\n \"au-7\",\n \"au-7.1\",\n \"au-8\",\n \"au-9\",\n \"au-9.3\",\n \"cm-14\",\n \"cm-3.5\",\n \"cm-5.1\",\n \"cm-5.6\",\n \"cm-6\",\n \"cm-7\",\n \"cm-7.2\",\n \"cm-7.5\",\n \"cm-7.9\",\n \"ia-11\",\n \"ia-2\",\n \"ia-2.1\",\n \"ia-2.12\",\n \"ia-2.2\",\n \"ia-2.5\",\n \"ia-2.6\",\n \"ia-3\",\n \"ia-5.1\",\n \"ia-5.13\",\n \"ia-5.2\",\n \"ia-7\",\n \"ia-8\",\n \"ma-3.5\",\n \"ma-4\",\n \"ma-4.1\",\n \"ma-4.6\",\n \"sc-10\",\n \"sc-11\",\n \"sc-13\",\n \"sc-17\",\n \"sc-23.5\",\n \"sc-24\",\n \"sc-28\",\n \"sc-28.1\",\n \"sc-28.3\",\n \"sc-3\",\n \"sc-4\",\n \"sc-45\",\n \"sc-45.1\",\n \"sc-5\",\n \"sc-5.2\",\n \"sc-8\",\n \"sc-8.1\",\n \"sc-8.2\",\n \"si-11\",\n \"si-16\",\n \"si-2.6\",\n \"si-6\"\n ]\n }\n ]\n}","extracted_at":"2026-09-16T16:07:24+00:00","id":"pf-stig-import","language":"json","pointer":"/profile/imports/0","section":null,"sha256_of_source_file":"ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697","slot":"2","source":"site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","title":"The profile imports the framework catalog and names the controls it alters"},"data/snippets/pf-stig-method-sc-28.json":{"approach":"executable-first","content":"{\n \"id\": \"sc-28_asm-ubtu-24-600090\",\n \"name\": \"assessment-method\",\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:*:*:*:lts:*:*:*\",\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\": \"Note: 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$ sudo fdisk -l \\n(..) \\nDisk /dev/vda: 15 GiB, 16106127360 bytes, 31457280 sectors \\nUnits: sectors of 1 * 512 = 512 bytes \\nSector siz [truncated]\"\n}","extracted_at":"2026-09-16T16:07:24+00:00","id":"pf-stig-method-sc-28","language":"json","pointer":"/profile/modify/alters/63/adds/0/parts/1","section":null,"sha256_of_source_file":"ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697","slot":"3","source":"site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","title":"STIG V-270747 check text as a method beside its objective"},"data/snippets/pf-stig-objective-sc-28.json":{"approach":"executable-first","content":"{\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\n \"props\": [\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\": \"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 \"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 \"parts\": [\n {\n \"id\": \"sc-28_dsc-ubtu-24-600090\",\n \"name\": \"guidance\",\n \"prose\": \"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 configura [truncated]\"\n }\n ]\n}","extracted_at":"2026-09-16T16:07:24+00:00","id":"pf-stig-objective-sc-28","language":"json","pointer":"/profile/modify/alters/63/adds/0/parts/0","section":null,"sha256_of_source_file":"ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697","slot":"1","source":"site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json","title":"STIG V-270747 as an objective a profile adds to SC-28"},"data/source-files.json":{"excluded":[{"path":"disa/U_Readme_SRG_and_STIG.pdf","why":"About the STIG and SRG packages as a set rather than about any one guide, so it has no row in a table of one row per guide."},{"path":"oscal","why":"The OSCAL representations of this guidance are published separately. This table lists the documents read as input, not what was written from them."}],"files":[{"bytes":1032133,"guidance":"cis-postgresql-18","href":"sources/cis/CIS_PostgreSQL_18_Benchmark_v1.0.0.json","kind":"source","media":"json","media_label":"JSON document","mime":"application/json","name":"CIS_PostgreSQL_18_Benchmark_v1.0.0.json","publisher":"cis","sha256":"b72eda73c5bef60e2971c93261bc226594cfb8d8aa1be92deb6b2e121bf05379","size":"1.0 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":1506309,"guidance":"cis-postgresql-18","href":"sources/cis/CIS_PostgreSQL_18_Benchmark_v1.0.0.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"CIS_PostgreSQL_18_Benchmark_v1.0.0.pdf","publisher":"cis","sha256":"eae098af712ef333be2ebb146e72d8cdcba9f740f3a99e15de8363055f49f1b9","size":"1.5 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":6823924,"guidance":"cis-ubuntu-24-04","href":"sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","kind":"source","media":"json","media_label":"JSON document","mime":"application/json","name":"CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json","publisher":"cis","sha256":"1a90fccb4442decd119382233ff8986caaaeede83dcf3c5ab22a87c747ab0c81","size":"6.8 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":10372494,"guidance":"cis-ubuntu-24-04","href":"sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.pdf","publisher":"cis","sha256":"8ebe23d21c23e383c81620ad04655e3b1d8fdf0b6eb9ddfdb7a97d0a5b5e7ef1","size":"10.4 MB","terms":"Reproduced here with the publisher's participation in this review. The Benchmarks carry CIS's own Agreed Terms of Use; consult the publisher before reusing them elsewhere."},{"bytes":640043,"guidance":"disa-ubuntu-22-04","href":"sources/disa/U_CAN_Ubuntu_22-04_LTS_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CAN_Ubuntu_22-04_LTS_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"73c26b6592dfc02f7f0eb456e0f89143ea1e2d8af7ebc61bd8bfae01f5a4c9d8","size":"640 kB","terms":"Public domain. A work of the United States Government."},{"bytes":658230,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml","publisher":"disa","sha256":"4c527cf0ed912947bb0c51be15f1a6bbc5a4bf05469ae083d94a01471edea77c","size":"658 kB","terms":"Public domain. A work of the United States Government."},{"bytes":934796,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1_Release_Memo.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_STIG_V1_Release_Memo.pdf","publisher":"disa","sha256":"9c3292baa367f97d0dc8c8a235a77dd49acfe53598d667902ab3e1e7d3d3d9a0","size":"935 kB","terms":"Public domain. A work of the United States Government."},{"bytes":425770,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_V1R5_Overview.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_V1R5_Overview.pdf","publisher":"disa","sha256":"7b4e8bc528e6e23c9bac33b760793d86e6d4954ff724f9db1e108ef071a22c8e","size":"426 kB","terms":"Public domain. A work of the United States Government."},{"bytes":301891,"guidance":"disa-ubuntu-24-04","href":"sources/disa/U_CAN_Ubuntu_24-04_LTS_V1R5_Revision_History.pdf","kind":"source","media":"pdf","media_label":"PDF document","mime":"application/pdf","name":"U_CAN_Ubuntu_24-04_LTS_V1R5_Revision_History.pdf","publisher":"disa","sha256":"3f00fb641e059376fb8b8d4404e3e2abf0a6a95950568740172086c441457a56","size":"302 kB","terms":"Public domain. A work of the United States Government."},{"bytes":456124,"guidance":"disa-postgres-16","href":"sources/disa/U_CD_Postgres_16_STIG_V1R2_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_CD_Postgres_16_STIG_V1R2_Manual-xccdf.xml","publisher":"disa","sha256":"d468632da49f29b1616347dc7d79f429ff72ded2685a2ffb55b416d76192ce32","size":"456 kB","terms":"Public domain. A work of the United States Government."},{"bytes":432719,"guidance":"disa-epas","href":"sources/disa/U_EPAS_STIG_V2R1_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_EPAS_STIG_V2R1_Manual-xccdf.xml","publisher":"disa","sha256":"c9a9fb2f652495433a3639f740ef08d856c722be5d8bfdb729c87f843f3767ec","size":"433 kB","terms":"Public domain. A work of the United States Government."},{"bytes":936441,"guidance":"disa-windows-2019","href":"sources/disa/U_MS_Windows_Server_2019_STIG_V3R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2019_STIG_V3R8_Manual-xccdf.xml","publisher":"disa","sha256":"f483e86fdaf1caf0ad904b99ae117667fb61e48e0f62fbbcbd4ac30facef0e36","size":"936 kB","terms":"Public domain. A work of the United States Government."},{"bytes":906114,"guidance":"disa-windows-2022","href":"sources/disa/U_MS_Windows_Server_2022_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2022_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"991ad360c2ca40c5ab743b22b045ac9a98134a2c7360983ae32a1dac62de65de","size":"906 kB","terms":"Public domain. A work of the United States Government."},{"bytes":913750,"guidance":"disa-windows-2025","href":"sources/disa/U_MS_Windows_Server_2025_STIG_V1R1_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_MS_Windows_Server_2025_STIG_V1R1_Manual-xccdf.xml","publisher":"disa","sha256":"5ae22836beba53091fa6269eaa974e54c226f3e2113cc9a3ec0183a8e16f51ee","size":"914 kB","terms":"Public domain. A work of the United States Government."},{"bytes":1267893,"guidance":"disa-rhel-8","href":"sources/disa/U_RHEL_8_STIG_V2R7_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_RHEL_8_STIG_V2R7_Manual-xccdf.xml","publisher":"disa","sha256":"9c5c57f34c78e3c70d5bc9755169b99f9e6965509b8e06f277c82982bccc8411","size":"1.3 MB","terms":"Public domain. A work of the United States Government."},{"bytes":1397262,"guidance":"disa-rhel-9","href":"sources/disa/U_RHEL_9_STIG_V2R8_Manual-xccdf.xml","kind":"source","media":"xml","media_label":"XML document","mime":"application/xml","name":"U_RHEL_9_STIG_V2R8_Manual-xccdf.xml","publisher":"disa","sha256":"bcb1c86161034ced8accca81f15efe40d4e4cfdce003b6b2b456cb49fcd094e3","size":"1.4 MB","terms":"Public domain. A work of the United States Government."}],"media_types":{"json":{"label":"JSON document","mime":"application/json"},"pdf":{"label":"PDF document","mime":"application/pdf"},"xml":{"label":"XML document","mime":"application/xml"}},"not_copied":[{"publisher":"cisa","what":"The SCuBA secure configuration baselines themselves","where":null,"where_label":null,"why":"The baselines are published by CISA and no copy of them is held here. What was read for this analysis was the baseline content as converted, and those conversions are published separately."},{"publisher":"aws","what":"The Security Hub controls, as published","where":"https://github.com/awslabs/oscal-content-for-aws-services","where_label":"oscal-content-for-aws-services","why":"This publisher ships its guidance as OSCAL already, so there is no separate source document to hold. The published content is linked rather than copied, so there is one copy to keep current."}],"not_shipped":[{"path":"cis","why":"Held locally, not redistributed. Download the Benchmarks from cisecurity.org into sources/cis/ under the filenames recorded here to rebuild anything that reads them."}],"note":"Every file under sources/, with its media type and size read from disk, and the benchmark row it belongs to. Built by tools/sources_files.py; verified by tools/verify.py --sources, which fails if a link points at a missing file, a file sits in the folder unlinked, or a file names a row that does not exist.","totals":{"bytes":29005893,"files":16,"size":"29.0 MB"}},"data/sources.json":{"columns":["Publisher","Guidance","Source form held"],"note":"The hardening guidance read as input to this analysis, one row per benchmark or guide rather than one per publisher, because the unit a reader recognises is the benchmark. Each row carries the documents read for it: a file icon downloads one file, a globe opens the publisher's page. What was written from this guidance, in OSCAL, is published separately and is not a column here; it is kept under 'publishers' so tools/verify.py --sources can still recompute it against the corpora.","publishers":{"aws":{"derivation":"AWS/oscal-content-for-aws-services-main: catalogs/*.oscal.json and component-definitions/*.oscal.json","full_name":"Amazon Web Services","name":"AWS","oscal_counts":{"catalogs":1,"component_definitions":230,"controls":452,"groups":77},"oscal_form":"one catalog of 452 controls across 77 groups, and 230 component definitions","source_counts":{}},"cis":{"derivation":"assessment-plan documents under Easy Dynamics/Center for Internet Security; source files under Hardening Guides/Center for Internet Security","full_name":"Center for Internet Security","name":"CIS","oscal_counts":{"assessment_plans":2},"oscal_form":"two assessment plans","source_counts":{"pdf":2,"xccdf_json":2}},"cisa":{"derivation":"assessment-plan documents under Easy Dynamics/CISA BOD 25-01; no publisher source material is present","full_name":"Cybersecurity and Infrastructure Security Agency","name":"CISA","oscal_counts":{"assessment_plans":4,"assessment_results":1},"oscal_form":"four assessment plans and one assessment result","source_counts":{}},"disa":{"derivation":"assessment-plan documents under Easy Dynamics/DISA; *-xccdf.xml under Hardening Guides/DISA","full_name":"Defense Information Systems Agency","name":"DISA","oscal_counts":{"assessment_plans":9},"oscal_form":"nine assessment plans","source_counts":{"xccdf_xml":9}}},"rows":[{"guidance":"Ubuntu Linux 24.04 LTS Benchmark","key":"cis-ubuntu-24-04","publisher":"cis","source_form":"XCCDF-derived JSON, and PDF","version":"v1.0.0"},{"guidance":"PostgreSQL 18 Benchmark","key":"cis-postgresql-18","publisher":"cis","source_form":"XCCDF-derived JSON, and PDF","version":"v1.0.0"},{"guidance":"Ubuntu 22.04 LTS STIG","key":"disa-ubuntu-22-04","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Ubuntu 24.04 LTS STIG","key":"disa-ubuntu-24-04","publisher":"disa","source_form":"XCCDF XML, and three release notes","version":"V1R5"},{"guidance":"Red Hat Enterprise Linux 8 STIG","key":"disa-rhel-8","publisher":"disa","source_form":"XCCDF XML","version":"V2R7"},{"guidance":"Red Hat Enterprise Linux 9 STIG","key":"disa-rhel-9","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Windows Server 2019 STIG","key":"disa-windows-2019","publisher":"disa","source_form":"XCCDF XML","version":"V3R8"},{"guidance":"Windows Server 2022 STIG","key":"disa-windows-2022","publisher":"disa","source_form":"XCCDF XML","version":"V2R8"},{"guidance":"Windows Server 2025 STIG","key":"disa-windows-2025","publisher":"disa","source_form":"XCCDF XML","version":"V1R1"},{"guidance":"PostgreSQL 16 STIG","key":"disa-postgres-16","publisher":"disa","source_form":"XCCDF XML","version":"V1R2"},{"guidance":"EDB Postgres Advanced Server STIG","key":"disa-epas","publisher":"disa","source_form":"XCCDF XML","version":"V2R1"},{"guidance":"BOD 25-01, the SCuBA baselines","key":"cisa-bod-25-01","links":[{"href":"https://www.cisa.gov/resources-tools/services/bod-25-01-implementing-secure-practices-cloud-services-required-configurations","kind":"web","label":"BOD 25-01, on the publisher's site"}],"publisher":"cisa","source_form":"None held here","version":null},{"guidance":"Security Hub security best-practice controls","key":"aws-security-hub","links":[{"href":"https://aws.github.io/aws-security-services-best-practices/guides/security-hub/","kind":"web","label":"Security Hub best practices, on the publisher's site"},{"href":"https://github.com/awslabs/oscal-content-for-aws-services","kind":"web","label":"The same controls as OSCAL, in the publisher's repository"}],"publisher":"aws","source_form":"Published as OSCAL, and linked","version":null}],"summary":"Hardening guidance used as input","summary_sub":"Two CIS Benchmarks, nine DISA STIGs, CISA BOD 25-01 and the AWS Security Hub controls, with the documents read for each."},"data/stakeholders.json":{"approaches":{"assessment-first":{"auditor":{"flows":[{"from":[{"model":"assessment-plan"}],"makes":"the observations","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor's run produces assessment results, not implementation claims. The workflow does not update the system security plan."},"benchmark":{"note":"The guidance provider writes activities and steps. The policy engine provider supplies executable checks.","writes":[{"model":"assessment-plan"}]},"engine":{"note":"The policy engine provider adds checks to the assessment plan. The plan identifies the engine in assessment-assets.","writes":[{"model":"assessment-plan"}]},"mapper":{"note":"The mapping provider edits the assessment plan, naming the framework controls covered by the activity.","writes":[{"model":"assessment-plan"}]},"owner":{"note":"The system owner supplies the profile and system security plan. The assessor's workflow does not depend on the owner's automation.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"note":"The technology provider writes activities and steps. The policy engine provider supplies executable checks.","writes":[{"model":"assessment-plan"}]}},"catalog-first":{"auditor":{"flows":[{"from":[{"kind":"software","model":"component-definition"}],"makes":"the findings","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor runs the checks independently. The resulting finding targets the system owner's implementation statement."},"benchmark":{"writes":[{"model":"catalog"}]},"engine":{"note":"The provider publishes checks as components of type software, referencing the guidance authors' catalog. System owners and auditors run the checks.","writes":[{"kind":"software","model":"component-definition"}]},"mapper":{"note":"The mapping provider writes a separate framework mapping. The published corpus contains no mapping collection for hardening guidance.","writes":[{"model":"mapping-collection"}]},"owner":{"flows":[{"from":[{"kind":"software","model":"component-definition"}],"makes":"the control-implementation responses","runtime":true,"to":[{"model":"system-security-plan"}]}],"note":"The system owner selects requirements and merges catalogs through a profile imported by the system security plan.","writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"writes":[{"model":"catalog"}]}},"component-first":{"auditor":{"flows":[{"from":[{"model":"assessment-plan"}],"makes":"the observations","runtime":true,"to":[{"model":"assessment-results"}]}],"note":"The auditor runs checks through an assessment plan, allowing the result to identify a host rather than a component."},"benchmark":{"writes":[{"kind":"software","model":"component-definition"}]},"engine":{"note":"The provider publishes checks in a component of type validation. System owners and auditors run the checks.","writes":[{"kind":"validation","model":"component-definition"}]},"mapper":{"note":"The mapping provider edits a component definition. Whether the rules or the checks carry the framework mapping remains open.","writes":[{"kind":"software or validation","model":"component-definition"}]},"owner":{"flows":[{"from":[{"kind":"validation","model":"component-definition"}],"makes":"the control-implementation responses","runtime":true,"to":[{"model":"system-security-plan"}]}],"writes":[{"model":"profile"},{"model":"system-security-plan"}]},"regulatory":{"writes":[{"model":"catalog"}]},"software":{"writes":[{"kind":"software","model":"component-definition"}]}},"executable-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 whose controls carry their own executable methods.","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. Running 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":"Benchmark publishers and technology providers author guidance in the same OSCAL model for each approach."},{"key":"automation","label":"Automation providers and operators","note":"Providers build policy engines. System owners and auditors run checks to produce implementation responses or assessment results."}],"intro":"Seven parties publish, implement or assess hardening guidance. The table maps each party to OSCAL models and groups guidance authors separately from automation providers and operators.","note":"The mapping identifies the OSCAL models used by seven parties from guidance publication through audit. Component types distinguish guidance from checks where both use component definitions. Two groups identify guidance authors and automation providers and operators. Policy engine providers build tools; system owners and auditors execute the flows shown. Mapping providers are separate because guidance authors do not always publish framework mappings: STIGs carry CCIs, DISA's CCI list names the 800-53 controls, and third parties publish mappings through NIST's OLIR programme.","parties":[{"key":"regulatory","name":"Regulatory control providers","who":"NIST and other bodies publishing regulatory controls, such as SP 800-53"},{"key":"mapper","name":"Mapping providers","who":"Organisations linking guidance to frameworks through DISA's CCI list, NIST's OLIR programme or the Secure Controls Framework"},{"group":"guidance","key":"benchmark","name":"Technical hardening guidance providers","who":"CIS, DISA and other benchmark publishers"},{"group":"guidance","key":"software","name":"Technology providers","who":"Vendors publishing configuration guidance for hardware, software and services, independently or with benchmark publishers such as CIS"},{"group":"automation","key":"engine","name":"Policy engine providers","who":"Providers of assessment and checking tools such as OPA, Kyverno, ScubaGear and OpenSCAP"},{"group":"automation","key":"owner","name":"System owners","who":"Organisations implementing and documenting controls on a system"},{"group":"automation","key":"auditor","name":"Independent auditors","who":"Assessors running checks and reviewing results independently of system owners"}],"runtime":"A policy engine reads OSCAL, executes checks and writes OSCAL. Providers publish the checks; each flow identifies the party executing the checks.","shared_profile":{"executable-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":"The activity title contains the required value, so changing the value requires editing the plan rather than resolving a profile.","title":"Required values lack resolvable parameters"},{"body":"The model provides activities and steps, so guidance nested four levels deep must be represented within those two structural tiers.","title":"Guide hierarchy is limited to two tiers"},{"body":"The published result references a plan absent from the corpus and assigns an observation a subject type not defined by the model.","title":"Published references and types need correction"}],"intro":"Publishing technical hardening guidance as an assessment plan has these strengths and risks.","pros":[{"body":"The assessment plan references implementation claims without adding claims, so adding or retiring a guide does not change the system security plan.","title":"Guidance stays outside the plan of record"},{"body":"A separate assessment results document imports a plan; the corpus includes findings that target objectives and reference supporting observations.","title":"Assessment results reference an assessment plan"},{"body":"An assessment subject can be an inventory item, allowing separate findings for two hosts running one operating system with different configurations.","title":"Subjects can identify individual hosts"},{"body":"Tasks carry schedules and identify execution platforms, placing the timing and runtime context for checks in the assessment plan.","title":"The plan records execution context"}]},"catalog-first":{"cons":[{"body":"The system security plan must address benchmark requirements alongside regulatory controls; whether each additional catalog requires a separate plan remains unsettled.","title":"Benchmark catalogs add maintenance work"},{"body":"Multiple frameworks and benchmarks require catalogs, profiles and mappings to be maintained together, increasing tool integration work and profile resolution complexity.","title":"Combined baselines complicate profile resolution"},{"body":"A by-component response identifies a component, not an instance, so one exception among a hundred hosts sharing that component cannot be distinguished.","title":"Responses do not identify individual instances"}],"intro":"Publishing technical hardening guidance as a catalog has these strengths and risks.","pros":[{"body":"Technical requirements use catalog controls and follow the same references through the remaining OSCAL models as regulatory controls.","title":"Technical and regulatory requirements use one model"},{"body":"A profile selects the hardening requirements an organisation adopts and sets organisationally defined parameters without changing the source catalog.","title":"Rules can be tailored"},{"body":"Controls, parts and nested groups represent checks, remediation and explanatory prose, including the structure of a thousand-page guide.","title":"Catalog structures represent guide content"},{"body":"A separate mapping-collection links guidance to a framework, allowing a third party to publish the mapping without owning either catalog.","title":"Third parties can publish framework mappings"}]},"component-first":{"cons":[{"body":"The proposal changes component definitions, system security plans, assessment plans and assessment results; existing schema support does not cover the proposed assemblies.","title":"Four models require schema changes"},{"body":"Rules describing the required component configuration enter the system security plan, which documents the system's implemented controls and current configuration.","title":"Desired state enters the plan of record"},{"body":"Rationale, audit procedure and remediation provide guidance context, but the published rules omit these fields and support remains proposed.","title":"Published rules omit guide context"},{"body":"A by-component response can reference a rule but not an individual instance, so exceptions remain associated with the component.","title":"Responses do not identify individual instances"},{"body":"Inventory items would also need implementing-rules support for a claim to identify a host rather than a component class.","title":"Host-level claims may require inventory support"}],"intro":"Publishing technical hardening rules in a component definition has these strengths and risks.","pros":[{"body":"A component definition describes how a product can meet controls; the proposed rules provide configuration requirements for automation in the same document.","title":"One artifact describes capability and supports automation"},{"body":"The product component holds the rule and a validation component holds the check; a second engine uses a second validation component.","title":"Rules and checks remain separate"},{"body":"The proposed implementing-rules assembly links a control implementation claim to the rule used to satisfy the control.","title":"Implementation claims can reference rules"},{"body":"Existing guidance directs technology providers to describe product capabilities in component definitions, where the proposal would also place hardening rules.","title":"Technology providers can extend component descriptions"}]},"executable-first":{"cons":[{"body":"A profile resolved from a URL and executed is a remote code path into every assessed system, operated by the profile author.","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 runs nothing.","title":"The vocabulary has no owner"},{"body":"The platform prop is a CPE that no SSP component carries, so which host runs a check is decided outside the schema.","title":"The subject is a convention"},{"body":"The finding targets the objective and the response the control, so the plan of record cannot name the checks behind its claim.","title":"Claim and result never meet"}],"intro":"Considerations when attaching executable assessment methods to controls in a catalog or a profile have been captured","pros":[{"body":"A profile adds parts to a control, so a third party attaches a check to a catalog it does not own.","title":"The check travels with the rule"},{"body":"A control's params reach the script as environment variables, so one script serves many controls with each organisation's own value.","title":"Parameters feed the script"},{"body":"The method links to an assessment objective, so a finding targets an objective id every 800-53A consumer already reads.","title":"Findings need no new field"},{"body":"Methods sit on controls the assessment plan reads, so hundreds of checks add no control to the plan of record.","title":"The plan of record stays put"}]}},"note":"Strengths and risks for each approach. Entry counts may differ; tools/approach_pages.py enforces prose budgets within and across approaches. Scenario figures remain on the scenario page. BUILD-LOG.md records the basis for each entry. Where present, schema_evidence identifies checked schema fragments and is not rendered."},"data/views.json":{"automation_argument":{"claim":"The automation argument treats applying and verifying hardening guidance as operational work, not just a finer-grained form of regulatory control. Automation coverage varies across the published guides.","claim_not_made":"Hardening guidance is never performed manually. The corpus includes manual procedures and does not support that claim.","evidence":[{"automated":"2271 activities carry method TEST","corpus":"STIG, all 9 files","manual":"none","stat_keys":["stig_method_test"]},{"automated":"576 steps","corpus":"CIS Ubuntu 24.04","manual":"40 steps","stat_keys":["cis_ubuntu_automated","cis_ubuntu_manual"]},{"automated":"0 steps","corpus":"CIS PostgreSQL 18","manual":"144 steps, covering every step; every activity carries method EXAMINE","note":"This guide provides a counterexample to the claim that all hardening procedures are automated.","stat_keys":["cis_postgres_automated","cis_postgres_manual"]}]},"crux":{"note":"Model placement alone does not establish whether guidance is binding. Every approach needs a way to distinguish requirements from optional configurations or assessment procedures."},"note":"Three editorial interpretations of a hardening rule, ordered by OSCAL layer rather than rank. The analysis uses a working definition without selecting an interpretation. Each view links to a stakeholder glossary term. 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 and differs in the construct that carries it.","views":[{"aligned_approach":"catalog-first","also_aligned":["executable-first"],"also_aligned_note":"Executable-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":"A binding requirement, expressed as a shall. A rule differs from a regulatory control in specificity.","implies_layer":"Control","implies_model":"catalog","key":"requirement","label":"A requirement","stakeholder":"publisher"},{"aligned_approach":"component-first","definition":"A description of possible component configurations. The technology provider describes capabilities; the adopting organisation sets requirements.","implies_layer":"Implementation","implies_model":"component-definition","key":"capability","label":"A capability statement","stakeholder":"implementer"},{"aligned_approach":"assessment-first","definition":"A procedure for applying or verifying hardening guidance. Assessment activities and steps describe the work, with executable checks referenced for automation.","implies_layer":"Assessment","implies_model":"assessment-plan","key":"procedure","label":"An assessor's procedure","stakeholder":"assessor"}],"why_this_matters":"OSCAL has no dedicated core requirement-level field distinguishing shall, should and may. The gap affects every approach; model placement alone cannot establish whether guidance expresses requirements, capabilities or assessment procedures.","working_definition":{"status":"A working definition for comparing the three approaches without selecting an interpretation.","term":"rule","text":"One technical requirement or recommendation, finer-grained than a control, without any claim about whether it is binding."}}}; diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/diagrams/710-scenario-assessment.svg b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/diagrams/710-scenario-assessment.svg index 595664f..9d5fde1 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, framework mappings are on activities. 0 component-definition files, none, engines are identified in each plan. 1 system-security-plan file, one, addressing 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; each result references 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 system security plan addresses 370 controls; all three guides remain in assessment plans. + 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, framework mappings are on activities. 0 component-definition files, none, engines are identified in each plan. 1 system-security-plan file, one, addressing 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; each result references 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 system security plan addresses 370 controls; all three guides remain in assessment plans. @@ -62,6 +61,7 @@
  • Catalog-first
  • Component-first
  • Assessment-first
  • +
  • Executable-first
  • Open questions
  • OSCAL artifacts
  • @@ -76,7 +76,7 @@
    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 b35551a..cbfd5b7 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 @@ -151,16 +151,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 @@ -174,6 +175,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-executable: #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 @@ -299,10 +305,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-executable: #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, @@ -1991,3 +1998,65 @@ figcaption { lists have to start level. */ .card:has(.answers) { display: flex; flex-direction: column; } .card:has(.answers) .answers { margin-top: auto; } + +/* --- .carrier : the check axis on the start page --------------------------- + Three kinds of thing an OSCAL document carries about a check, tabled across + the four approaches, then the same rule from two corpora side by side. The + kind badges are outlined rather than filled so the three read as categories + and not as verdicts, and no kind takes an approach colour. */ +.carrier-kinds { display: grid; gap: var(--s2) var(--s4); grid-template-columns: max-content 1fr; margin-block: var(--s5); max-width: var(--measure-wide, 72rem); } +.carrier-kinds dt { margin: 0; } +.carrier-kinds dd { margin: 0; font-size: var(--fs-sm); color: var(--text-muted); } +.carrier-kind { + display: inline-block; border: 1px solid var(--border-strong); border-radius: var(--radius); + padding: 0 var(--s2); font-size: var(--fs-xs); font-weight: 650; white-space: nowrap; + color: var(--text); background: var(--bg); +} +.carrier-kind--executable { border-style: double; border-width: 3px; padding-block: 0; } +.carrier-kind--description { border-style: dashed; } +.carrier.matrix { min-width: 900px; } +.carrier.matrix td { font-size: var(--fs-sm); } +.carrier__approach { font-weight: 650; text-decoration: none; } +.carrier__approach:hover, .carrier__approach:focus-visible { text-decoration: underline; } +.carrier-extracts { display: grid; gap: var(--s4); grid-template-columns: repeat(auto-fit, minmax(300px, 1fr)); margin-block: var(--s5); } +.carrier-extracts__label, .carrier-pair__label, .carrier-consequences__label { margin: 0 0 var(--s2); font-size: var(--fs-sm); } +.carrier-extracts .snippet, .carrier-pair .snippet, .carrier-fusion .snippet { margin-top: var(--s3); } +.carrier-fusion, .carrier-pair { margin-block: var(--s7); } +.carrier-fusion > p, .carrier-pair > p { max-width: var(--measure); } +.carrier-pair__sides { display: grid; gap: var(--s4); grid-template-columns: repeat(auto-fit, minmax(320px, 1fr)); margin-top: var(--s4); } +.carrier-pair__side { border: 1px solid var(--border); border-radius: var(--radius); padding: var(--s4); background: var(--bg); min-width: 0; } +.carrier-pair__says { margin: 0; font-size: var(--fs-sm); color: var(--text-muted); } +.carrier-figures { max-width: var(--measure); font-size: var(--fs-sm); color: var(--text-muted); } +.carrier-consequences { display: grid; gap: var(--s4); grid-template-columns: repeat(auto-fit, minmax(260px, 1fr)); margin-block: var(--s5); } +.carrier-consequences__kind ul { margin: 0; padding-left: 1.2em; font-size: var(--fs-sm); } +.carrier-consequences__kind li + li { margin-top: var(--s2); } + +/* --- .decisions : construct and placement, decisions 2 and 3 --------------- + Status chips are outlined like the kind badges and carry a distinct border + style each, so the grid reads without colour. */ +.dstatus { + display: inline-block; border: 1px solid var(--border-strong); border-radius: var(--radius); + padding: 0 var(--s2); font-size: var(--fs-xs); font-weight: 650; white-space: nowrap; + color: var(--text); background: var(--bg); +} +.dstatus--released { border-width: 2px; } +.dstatus--proposed { border-style: dashed; } +.dstatus--needs-schema { border-style: dotted; color: var(--text-muted); } +.dstatus--empty { border-color: var(--border); color: var(--text-muted); } +.decisions.matrix { min-width: 760px; } +.decisions.matrix td { font-size: var(--fs-sm); } +.decisions--grid td[data-state] { vertical-align: top; } +.decisions__note { margin: var(--s2) 0 0; font-size: var(--fs-sm); color: var(--text-muted); } +.decisions__docs, .decisions__instances { margin: var(--s2) 0 0; padding-left: 1.1em; font-size: var(--fs-sm); } +.decisions__docs li + li, .decisions__instances li + li { margin-top: var(--s1, 0.25rem); } +.decisions__doc--unheld, .decisions__doc--missing { color: var(--text-muted); } +.decisions__options { display: grid; gap: var(--s4); grid-template-columns: repeat(auto-fit, minmax(300px, 1fr)); margin-block: var(--s5); } +.decisions__option { border: 1px solid var(--border); border-radius: var(--radius); padding: var(--s4); background: var(--bg); min-width: 0; } +.decisions__label { margin: 0; font-size: var(--fs-sm); } +.decisions__differ { font-size: var(--fs-sm); color: var(--text-muted); } +.decisions__consequences { margin: var(--s3) 0 0; padding-left: 1.1em; font-size: var(--fs-sm); } +.decisions__consequences li + li { margin-top: var(--s2); } +.decisions__placements, .decisions__statuses { display: grid; gap: var(--s2) var(--s4); grid-template-columns: max-content 1fr; margin-block: var(--s5); max-width: var(--measure-wide, 72rem); } +.decisions__placements dt, .decisions__statuses dt { margin: 0; font-size: var(--fs-sm); } +.decisions__placements dd, .decisions__statuses dd { margin: 0; font-size: var(--fs-sm); color: var(--text-muted); } +.decisions__placements dd span { display: block; } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.js b/docs/analysis/2026-08-automating-technical-hardening-guidance/assets/site.js index 96a90df..1b56e0f 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 @@ -246,9 +246,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 @@ -337,7 +338,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 executable-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 @@ -959,9 +961,11 @@ 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. */ - /* Option-letter order: A, B, C. 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"]; + /* Option-letter order: A, B, C, then D, which arrived later. 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", + "executable-first"]; function el(tag, cls, text) { var n = document.createElement(tag); @@ -1346,6 +1350,25 @@ h.appendChild(el("span", "criteria-table__who", p.option)); sec.appendChild(h); + /* An approach whose proponent has published nothing says so before + its rows, and links the one document the proponent does have. The + rows beneath are then the corpus the site generated in that + approach's shape, counted like any other and labelled here as the + site's. A section with no rows at all ends after the note. */ + if (p.note) sec.appendChild(el("p", null, p.note)); + 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); + } + if (!p.files.length) { + 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"); @@ -1864,6 +1887,379 @@ }); } + /* --- the check axis: reference, description, or declared executable ----- + The six questions put four constructs against the check question, and the + answers hold three kinds of thing. This block names the axis, tables it, + and puts the same rule from two corpora side by side, with the extracts + rendered the way they are everywhere else. Nothing here is typed: the + rows, the pairs and the figures come from data/check-carrier.json and the + figures are recomputed by the harness. */ + function renderCheckCarrier(node) { + Promise.all([load("check-carrier.json"), load("six-questions.json")]) + .then(function (both) { + var d = both[0], sq = both[1]; + var byKey = {}; + sq.approaches.forEach(function (a) { byKey[a.key] = a; }); + var kindByKey = {}; + d.kinds.forEach(function (k) { kindByKey[k.key] = k; }); + node.textContent = ""; + + function approachName(key) { + var a = byKey[key] || {}; + var link = el("a", "carrier__approach approach-" + key.replace("-first", ""), + a.label || key); + link.href = "./" + key + ".html"; + return link; + } + function kindBadge(key) { + var k = kindByKey[key] || { label: key }; + return el("span", "carrier-kind carrier-kind--" + key, k.label); + } + function statusSnippet(id, approachKey) { + var det = document.createElement("details"); + det.className = "snippet"; + det.dataset.snippet = id; + var a = byKey[approachKey]; + if (a && a.status_annotation) det.dataset.status = a.status_annotation; + renderSnippet(det); + return det; + } + + (d.intro || []).forEach(function (p) { + node.appendChild(el("p", null, p)); + }); + + /* The three kinds, once, before the table that uses them. */ + var kinds = el("dl", "carrier-kinds"); + d.kinds.forEach(function (k) { + var dt = el("dt"); + dt.appendChild(kindBadge(k.key)); + kinds.appendChild(dt); + kinds.appendChild(el("dd", null, k.meaning)); + }); + node.appendChild(kinds); + + var wrap = el("div", "table-wrap"); + var t = document.createElement("table"); + t.className = "matrix carrier"; + t.setAttribute("aria-label", d.title); + var thead = document.createElement("thead"); + var hr = document.createElement("tr"); + d.columns.forEach(function (c) { + var th = document.createElement("th"); + th.scope = "col"; + th.textContent = c; + hr.appendChild(th); + }); + thead.appendChild(hr); + t.appendChild(thead); + var tb = document.createElement("tbody"); + approachOrder(sq).forEach(function (ap) { + var r = d.rows.filter(function (x) { return x.approach === ap.key; })[0]; + if (!r) return; + var tr = document.createElement("tr"); + tr.dataset.approach = ap.key; + var th = document.createElement("th"); + th.scope = "row"; + th.appendChild(approachName(ap.key)); + tr.appendChild(th); + var kd = document.createElement("td"); + kd.setAttribute("data-label", d.columns[1]); + kd.appendChild(kindBadge(r.kind)); + tr.appendChild(kd); + [["construct", 2], ["owner", 3], ["one_document", 4], ["needs", 5]] + .forEach(function (f) { + var td = document.createElement("td"); + td.setAttribute("data-label", d.columns[f[1]]); + td.textContent = r[f[0]]; + tr.appendChild(td); + }); + tb.appendChild(tr); + }); + t.appendChild(tb); + wrap.appendChild(t); + node.appendChild(wrap); + + /* The extracts each row rests on, under the table rather than in it: a + code block in a table cell is wider than the cell. */ + var ex = el("div", "carrier-extracts"); + approachOrder(sq).forEach(function (ap) { + var r = d.rows.filter(function (x) { return x.approach === ap.key; })[0]; + if (!r || !(r.snippet_ids || []).length) return; + var grp = el("div", "carrier-extracts__group"); + grp.dataset.approach = ap.key; + var lab = el("p", "carrier-extracts__label"); + lab.appendChild(approachName(ap.key)); + lab.appendChild(document.createTextNode(", what the row rests on")); + grp.appendChild(lab); + r.snippet_ids.forEach(function (id) { + grp.appendChild(statusSnippet(id, ap.key)); + }); + ex.appendChild(grp); + }); + node.appendChild(ex); + + /* The fusion: both kinds on one control. */ + if (d.fusion) { + var fu = el("div", "carrier-fusion"); + var fh = el("h3", null, d.fusion.label); + fu.appendChild(fh); + fu.appendChild(el("p", null, d.fusion.text)); + (d.fusion.snippet_ids || []).forEach(function (id) { + fu.appendChild(statusSnippet(id, "executable-first")); + }); + node.appendChild(fu); + } + + /* The same rule, two corpora, side by side. */ + (d.pairs || []).forEach(function (p) { + var sec = el("div", "carrier-pair"); + sec.dataset.pair = p.key; + sec.appendChild(el("h3", null, p.title)); + sec.appendChild(el("p", null, p.what)); + var grid = el("div", "carrier-pair__sides"); + [p.left, p.right].forEach(function (side) { + var box = el("div", "carrier-pair__side"); + box.dataset.approach = side.approach; + var lab = el("p", "carrier-pair__label"); + lab.appendChild(approachName(side.approach)); + box.appendChild(lab); + box.appendChild(el("p", "carrier-pair__says", side.says)); + box.appendChild(statusSnippet(side.snippet_id, side.approach)); + grid.appendChild(box); + }); + sec.appendChild(grid); + node.appendChild(sec); + }); + + if (d.figures && d.figures.text) { + var fig = el("p", "carrier-figures", d.figures.text); + node.appendChild(fig); + } + + /* What follows from each kind. Consequences, stated once per kind, and + no kind is ranked above another. */ + var cons = el("div", "carrier-consequences"); + (d.consequences || []).forEach(function (c) { + var box = el("div", "carrier-consequences__kind"); + box.dataset.kind = c.kind; + var lab = el("p", "carrier-consequences__label"); + lab.appendChild(kindBadge(c.kind)); + box.appendChild(lab); + var ul = el("ul"); + c.follows.forEach(function (f) { ul.appendChild(el("li", null, f)); }); + box.appendChild(ul); + cons.appendChild(box); + }); + node.appendChild(cons); + }).catch(function (e) { + fail(node, "check-carrier: " + (e && e.message ? e.message : String(e))); + }); + } + + /* --- decisions 2 and 3: construct, and placement ------------------------- + Two blocks, one hook each, so the static headings that number them can + sit above. Documents are named by inventory key and resolved against + data/oscal-artifacts.json, so a cell links to the same row the inventory + page shows and never carries a path of its own. */ + function renderDecisions(node) { + var which = node.dataset.decisions; + Promise.all([load("decisions.json"), load("oscal-artifacts.json"), + load("check-carrier.json")]) + .then(function (all) { + var d = all[0], inv = all[1], cc = all[2]; + var kindByKey = {}; + cc.kinds.forEach(function (k) { kindByKey[k.key] = k; }); + var files = {}; + inv.publishers.forEach(function (p) { + p.files.forEach(function (f) { files[p.key + "|" + f.file] = f; }); + }); + node.textContent = ""; + + function kindBadge(key) { + var k = kindByKey[key] || { label: key }; + return el("span", "carrier-kind carrier-kind--" + key, k.label); + } + function statusChip(key, label) { + return el("span", "dstatus dstatus--" + key, label || key); + } + function docLink(doc) { + if (doc.held === false) { + var s = el("span", "decisions__doc decisions__doc--unheld", doc.label); + s.title = "Not held in this repository"; + return s; + } + var f = files[doc.publisher + "|" + doc.file]; + if (!f) { + return el("span", "decisions__doc decisions__doc--missing", + doc.label + " (not in the inventory)"); + } + var a = el("a", "decisions__doc", doc.label); + a.href = f.href; + if (f.href_external) { a.target = "_blank"; a.rel = "noopener"; } + a.title = f.title || f.file; + return a; + } + + if (which === "thesis") { + (d.thesis || []).forEach(function (p) { node.appendChild(el("p", null, p)); }); + return; + } + + if (which === "construct") { + var c = d.constructs; + node.appendChild(el("p", null, c.intro)); + var wrap = el("div", "table-wrap"); + var t = document.createElement("table"); + t.className = "matrix decisions"; + t.setAttribute("aria-label", c.label); + var thead = document.createElement("thead"); + var hr = document.createElement("tr"); + c.columns.forEach(function (col) { + var th = document.createElement("th"); + th.scope = "col"; + th.textContent = col; + hr.appendChild(th); + }); + thead.appendChild(hr); + t.appendChild(thead); + var tb = document.createElement("tbody"); + c.rows.forEach(function (r) { + var tr = document.createElement("tr"); + var th = document.createElement("th"); + th.scope = "row"; + th.textContent = r.aspect; + tr.appendChild(th); + [["rules", 1], ["method", 2]].forEach(function (f) { + var td = document.createElement("td"); + td.setAttribute("data-label", c.columns[f[1]]); + td.textContent = r[f[0]]; + tr.appendChild(td); + }); + tb.appendChild(tr); + }); + t.appendChild(tb); + wrap.appendChild(t); + node.appendChild(wrap); + + var opts = el("div", "decisions__options"); + c.options.forEach(function (o) { + var box = el("div", "decisions__option"); + box.dataset.construct = o.key; + var lab = el("p", "decisions__label"); + lab.appendChild(el("strong", null, o.label)); + lab.appendChild(document.createTextNode(". " + o.meaning)); + box.appendChild(lab); + var ul = el("ul", "decisions__instances"); + o.instances.forEach(function (i) { + var li = el("li"); + li.appendChild(docLink(i)); + li.appendChild(document.createTextNode(" ")); + li.appendChild(kindBadge(i.carries)); + li.appendChild(document.createTextNode(" ")); + li.appendChild(statusChip(i.status)); + ul.appendChild(li); + }); + box.appendChild(ul); + box.appendChild(el("p", "decisions__differ", o.instances_differ)); + var cl = el("ul", "decisions__consequences"); + o.consequences.forEach(function (x) { cl.appendChild(el("li", null, x)); }); + box.appendChild(cl); + opts.appendChild(box); + }); + node.appendChild(opts); + return; + } + + if (which === "placement") { + var p = d.placements; + node.appendChild(el("p", null, p.intro)); + var dl = el("dl", "decisions__placements"); + p.options.forEach(function (o) { + var dt = el("dt"); + dt.appendChild(el("strong", null, o.label)); + dt.appendChild(document.createTextNode(" (" + o.models.join(", ") + ")")); + dl.appendChild(dt); + var dd = el("dd"); + dd.appendChild(el("span", null, "Couples the code to: " + o.couples_to + " ")); + dd.appendChild(el("span", null, "Reaches the plan of record: " + o.reaches_ssp)); + dl.appendChild(dd); + }); + node.appendChild(dl); + + var byCell = {}; + p.cells.forEach(function (x) { byCell[x.construct + "|" + x.placement] = x; }); + var wrap2 = el("div", "table-wrap"); + var g = document.createElement("table"); + g.className = "matrix decisions decisions--grid"; + g.setAttribute("aria-label", p.grid_label); + var gh = document.createElement("thead"); + var ghr = document.createElement("tr"); + var corner = document.createElement("th"); + corner.scope = "col"; + corner.textContent = "Construct"; + ghr.appendChild(corner); + p.options.forEach(function (o) { + var th = document.createElement("th"); + th.scope = "col"; + th.textContent = o.label; + ghr.appendChild(th); + }); + gh.appendChild(ghr); + g.appendChild(gh); + var gb = document.createElement("tbody"); + var statusLabel = {}; + p.statuses.forEach(function (s) { statusLabel[s.key] = s.label; }); + d.constructs.options.forEach(function (o) { + var tr = document.createElement("tr"); + tr.dataset.construct = o.key; + var th = document.createElement("th"); + th.scope = "row"; + th.textContent = o.label; + tr.appendChild(th); + p.options.forEach(function (pl) { + var cell = byCell[o.key + "|" + pl.key]; + var td = document.createElement("td"); + td.setAttribute("data-label", pl.label); + td.dataset.placement = pl.key; + if (!cell) { td.textContent = "?"; tr.appendChild(td); return; } + td.dataset.state = cell.status; + td.appendChild(statusChip(cell.status, statusLabel[cell.status])); + td.appendChild(el("p", "decisions__note", cell.note)); + if (cell.documents.length) { + var ul = el("ul", "decisions__docs"); + cell.documents.forEach(function (doc) { + var li = el("li"); + li.appendChild(docLink(doc)); + ul.appendChild(li); + }); + td.appendChild(ul); + } + tr.appendChild(td); + }); + gb.appendChild(tr); + }); + g.appendChild(gb); + wrap2.appendChild(g); + node.appendChild(wrap2); + + var leg = el("dl", "decisions__statuses"); + p.statuses.forEach(function (s) { + var dt = el("dt"); + dt.appendChild(statusChip(s.key, s.label)); + leg.appendChild(dt); + leg.appendChild(el("dd", null, s.meaning)); + }); + node.appendChild(leg); + if (d.figures && d.figures.text) { + node.appendChild(el("p", "carrier-figures", d.figures.text)); + } + } + }).catch(function (e) { + fail(node, "decisions: " + (e && e.message ? e.message : String(e))); + }); + } + function renderAnswersLegend(node) { load("six-questions.json").then(function (a) { /* Silence was the wrong failure mode. This used to be a bare `if`, so a @@ -1994,6 +2390,8 @@ document.querySelectorAll("[data-question-list]").forEach(renderQuestionList); document.querySelectorAll("[data-approach-cards]").forEach(renderApproachCards); document.querySelectorAll("[data-sources]").forEach(renderSources); + document.querySelectorAll("[data-check-carrier]").forEach(renderCheckCarrier); + document.querySelectorAll("[data-decisions]").forEach(renderDecisions); document.querySelectorAll("[data-answers-legend]").forEach(renderAnswersLegend); document.querySelectorAll(".tabs").forEach(initTabs); initGlossary(); 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 1b3ebeb..fbd6e32 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 @@ -45,6 +45,7 @@
  • Catalog-first
  • Component-first
  • Assessment-first
  • +
  • Executable-first
  • Open questions
  • OSCAL artifacts
  • @@ -168,7 +169,7 @@

    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 b9633e7..e440409 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 @@ -45,6 +45,7 @@
  • Catalog-first
  • Component-first
  • Assessment-first
  • +
  • Executable-first
  • Open questions
  • OSCAL artifacts
  • @@ -179,7 +180,7 @@

    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/check-carrier.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/check-carrier.json new file mode 100644 index 0000000..3db1e78 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/check-carrier.json @@ -0,0 +1,151 @@ +{ + "note": "One axis across the four approaches: what the OSCAL carries about the check. The six questions ask where the rule is written and what check executes it; this file asks what kind of thing the answer to the check question is, because a reference, a description and a declared executable put different work on different parties. Rendered by renderCheckCarrier on the start page. Every row cites extracts by id, every figure is recomputed by tools/verify.py --carrier from the files under examples/, and the pairs put the same rule from two corpora side by side. The site takes no position on which kind is right; the consequences are stated and the reader weighs them.", + "title": "Rules, scripts, or both: what the OSCAL carries about the check", + "intro": [ + "The six questions ask where the rule is written and what check executes it. Put across the four approaches, the answers to the check question are not four constructs holding the same thing. They hold three kinds of thing, and which kind decides who has to hold the rest.", + "A reference names a check an engine owns. A description carries text a person or a tool follows, and the text may contain a script. A declared executable carries the script, or a link to it, with what an executor needs to run it and judge what comes back. The published files show all three, and the corpus generated for the fourth approach shows the third beside the second on the same guidance." + ], + "kinds": [ + { + "key": "reference", + "label": "A reference", + "meaning": "An identifier naming a check the engine owns. The OSCAL says which check; the executable is elsewhere and the identifier means something to one engine." + }, + { + "key": "description", + "label": "A description", + "meaning": "Text a person or a tool follows. It may contain a script, and nothing in the OSCAL says what runs the script or what its output means." + }, + { + "key": "executable", + "label": "A declared executable", + "meaning": "The script, or a link to it, with props that say which platform it applies to, what runs it, how the output is judged and what counts as a pass." + } + ], + "columns": [ + "Approach", + "Carries", + "In which construct", + "Who owns the executable", + "Rule and check in one document", + "What an executor needs beyond the OSCAL" + ], + "rows": [ + { + "approach": "catalog-first", + "kind": "reference", + "construct": "A prop on a check component naming a Config rule by identifier. The control names the check; the check names the rule the engine runs.", + "owner": "The cloud provider's rule engine.", + "one_document": "No. The rule is in the catalog and the check is in a component definition.", + "needs": "The engine, and the meaning of the identifier inside it.", + "snippet_ids": ["aws-acm-rsa-check-component"] + }, + { + "approach": "component-first", + "kind": "reference", + "construct": "A check on a validation component, carrying a rule id and a check id in a proposed assembly.", + "owner": "The validation tool and its content: OpenSCAP or Ansible in the published files.", + "one_document": "No. The rule sits on the target component and the check on the validation component.", + "needs": "A schema that defines the assemblies, and the tool the check id belongs to.", + "snippet_ids": ["ibm-validation-ansible"] + }, + { + "approach": "assessment-first", + "kind": "description", + "construct": "An activity step whose description holds the audit text, with a prop saying automated. For CIS the description holds the script; for the STIG it holds the check text; for CISA a prop holds a JSON string naming the check.", + "owner": "Whoever reads the description. Nothing names an engine.", + "one_document": "Yes. The rule is the activity and the check is its step.", + "needs": "A convention per publisher for where the script is in the text and how its output is judged.", + "snippet_ids": ["ez-cis-step-props", "ez-cisa-context-step"] + }, + { + "approach": "executable-first", + "kind": "executable", + "construct": "An assessment-method part beside the objective, with the script in its prose or linked as a resource, and props for platform, language, evaluation and pass condition.", + "owner": "The publisher of the guidance on the catalog route; the party writing the profile otherwise.", + "one_document": "Yes. Objective and method are parts of one control, in the catalog or added to it by a profile.", + "needs": "An executor that reads the props, and a namespace with an owner. Where the publisher gives no script, as the STIG does not, the method carries a description.", + "snippet_ids": ["pf-cis-method-1-1-1-1", "pf-stig-method-sc-28"] + } + ], + "fusion": { + "label": "Both, on one control", + "text": "The generated CIS catalog is the case where the rule and the script sit together. The rule is an assessment objective part on the control, the check is an assessment method part beside it carrying the script, a remediation part follows, and the value the script reads is a parameter of the same control. A finding targets the objective, so nothing in the results model has to know the script exists. The same shape reached by a profile is the fourth approach's second route, and the same shape with a reference in place of the script is what the catalog approach's method part already does.", + "snippet_ids": ["pf-cis-objective-and-param"] + }, + "pairs": [ + { + "key": "cis-1-1-1-1", + "title": "One CIS recommendation, in two corpora", + "what": "Recommendation 1.1.1.1 of the Ubuntu benchmark, the cramfs kernel module, as the assessment-first corpus publishes it and as the generated executable-first corpus carries it. The audit script is the same text in both. What differs is what the OSCAL says about it.", + "shared_token": "cramfs", + "left": { + "approach": "assessment-first", + "snippet_id": "ez-cis-step-props", + "says": "A step. The script is inside the description, after the audit text, and the prop beside it says automated. Nothing says what runs it or what its output means." + }, + "right": { + "approach": "executable-first", + "snippet_id": "pf-cis-method-1-1-1-1", + "says": "A method. The same script is the body, and four props say the platform, the language, that the output is matched against a pattern, and the pattern." + } + }, + { + "key": "stig-v-270747", + "title": "One STIG rule, in two corpora", + "what": "Rule V-270747 of the Ubuntu STIG, data at rest, as an activity in the assessment-first corpus and as a method the generated profile adds to SC-28. DISA publishes the check as text, so neither corpus holds a script for it.", + "shared_token": "UBTU-24-600090", + "left": { + "approach": "assessment-first", + "snippet_id": "ez-stig-sc28-v270747", + "says": "An activity carrying the rule, with a check step holding DISA's text and a prop naming the method TEST." + }, + "right": { + "approach": "executable-first", + "snippet_id": "pf-stig-method-sc-28", + "says": "A method beside an objective the profile added to SC-28, holding the same text. With no script to declare, no language, evaluation or pass condition can be set, and the construct carries a description." + } + } + ], + "figures": { + "note": "Recomputed by tools/verify.py --carrier from the CIS assessment plan under examples/assessment-first and the generated catalog under examples/executable-first. A fenced bash block whose first line is a shebang counts as a script.", + "cis_plan_audit_steps": 308, + "cis_plan_rules_with_script": 85, + "cis_catalog_methods_with_script": 84, + "cis_shared_rules_with_script": 83, + "cis_shared_identical": 42, + "cis_shared_differ": 41, + "cis_shared_differ_shorter_in_plan": 41, + "cis_catalog_methods_linking_script": 211, + "cis_catalog_methods_without_script": 93, + "stig_plan_activities": 194, + "stig_profile_objectives": 194, + "text": "The CIS assessment plan has 308 audit steps and 85 of them carry a script; the generated catalog has 84 methods carrying one, and 83 recommendations carry a script in both. In 42 of those the script is the same text. In 41 the plan's copy is shorter, and every one of the 41 lacks angle brackets the benchmark's script has. A further 211 catalog methods link to a script by name, and 93 carry no script at all. The STIG is 194 rules in both corpora, and none of them carries a script in either." + }, + "consequences": [ + { + "kind": "reference", + "follows": [ + "The OSCAL stays small, and the executable is maintained where it runs.", + "A reader of the OSCAL alone cannot tell what the check does or judge whether it tests the rule.", + "The identifier means something to one engine, so a second engine needs a second identifier and a second document." + ] + }, + { + "kind": "description", + "follows": [ + "Everything the publisher wrote travels with the plan, script included, and a person can follow it.", + "A tool that wants to run the script has to find it in the text and decide for itself what the output means.", + "Two documents converted from the same guidance can differ in the script, and nothing in the model says which text is the script." + ] + }, + { + "kind": "executable", + "follows": [ + "The document says enough to run the check and judge the result without asking the publisher.", + "The publisher, or the profile's author, maintains the script, and the vocabulary of the props has to be agreed and owned.", + "A script in the document can be hashed and refused when the hash fails, and a linked script without a hash is the gap that shows." + ] + } + ] +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/decisions.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/decisions.json new file mode 100644 index 0000000..f0641bf --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/decisions.json @@ -0,0 +1,154 @@ +{ + "note": "Decisions 2 and 3 of the start page's section on code in OSCAL. Decision 1, what the OSCAL carries about the check, is data/check-carrier.json. This file holds the construct decision, Rules against assessment-method, and the placement decision, and the grid that crosses them. Every document a cell names is referenced by inventory key into data/oscal-artifacts.json or by a path under examples/, so the renderer resolves the link and tools/verify.py --decisions checks that it exists and that its status is what the cell says. The site takes no position on either decision; the consequences are stated and no option is ranked.", + "thesis": [ + "The fourth approach's thesis is that the check's code travels in the OSCAL document. Two constructs can carry it, a typed assembly of its own or the released assessment-method part, and it can sit on a control, a component or an activity. Neither of those is the idea. They are decisions under it, and this section states each one with its consequences.", + "Three decisions, then. What the document carries about the check, which is the axis above. Which construct carries it, where the two candidates are a new typed assembly or the released part. And where it sits, which the construct partly decides." + ], + "constructs": { + "label": "Which construct carries it", + "intro": "Two constructs can carry code. A typed assembly, which the site calls Rules after the field name the published proposal uses, adds objects to the schema with their own fields and identity: rules and checks in the published component-first files, and an automation-scripts assembly in the file the generator writes from the CIS benchmark in that shape. The assessment-method part is released OSCAL, extended by props in a namespace and by links, and it is what the concept note and the generated catalog use. The table states each aspect for both and ranks neither.", + "options": [ + { + "key": "rules", + "label": "Rules", + "meaning": "A typed assembly added to the schema, with its own identity and its own fields for what the check is and how it is run.", + "instances": [ + { + "label": "rules and checks on validation components, published", + "publisher": "component-first", + "file": "oscap-validation-component-definition.json", + "carries": "reference", + "status": "proposed" + }, + { + "label": "the same assembly written from the CIS benchmark by the generator", + "publisher": "executable-first", + "file": "cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json", + "carries": "executable", + "status": "generated" + } + ], + "instances_differ": "The two instances are two schemas. The published one names a rule and a check, each with an id, and the check points at content the tool owns. The generated one names a script object with a type, a language, the profiles it applies to, evaluation criteria and the script as payload. They share the idea of a typed object with identity and nothing else, and neither validates under 1.2.1.", + "consequences": [ + "A validator checks the executor fields themselves, so a document that validates is a document an executor can read.", + "Nothing validates until a version ships the assembly, and two proposals with different fields are two versions to agree on.", + "A rule is an object with its own id, so it can sit on a component and be named from a plan or a result without going through a control." + ] + }, + { + "key": "assessment-method", + "label": "assessment-method", + "meaning": "The released part on a control, with its method prop, carrying the body in prose or a linked resource and the executor's needs as props in a namespace.", + "instances": [ + { + "label": "assessment-method parts naming the check by identifier, published", + "publisher": "catalog-first", + "file": "catalogs/aws_security-hub.oscal.json", + "carries": "reference", + "status": "released" + }, + { + "label": "executable assessment methods on every recommendation, generated from the CIS benchmark", + "publisher": "executable-first", + "file": "cis-ubuntu-24-04-lts-benchmark-catalog.json", + "carries": "executable", + "status": "generated" + }, + { + "label": "executable assessment methods added to SP 800-53 controls by a profile, generated from the STIG", + "publisher": "executable-first", + "file": "nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", + "carries": "description", + "status": "generated" + } + ], + "instances_differ": "One released construct, used three ways: to name a check by identifier, to carry a script with the props an executor needs, and to carry check text where the publisher gives no script. The part is the same in all three; what changes is what its prose and props hold.", + "consequences": [ + "Every file validates today, and a finding targets the objective part beside the method with no change to the results model.", + "A validator checks that a part and its props exist and nothing about what the props say, so the executor's vocabulary has to be agreed outside the schema.", + "A part sits on a control and nowhere else in 1.2.1, so the code is addressed through a requirement and reaches a component only through a profile the system's plan imports." + ] + } + ], + "columns": ["Aspect", "Rules", "assessment-method"], + "rows": [ + {"aspect": "What it is", "rules": "A typed assembly of its own, added to the schema.", "method": "The released assessment-method part on a control, with a method prop."}, + {"aspect": "Schema", "rules": "New fields and a new version. Nothing validates until it ships.", "method": "No change. Every file validates under 1.2.1."}, + {"aspect": "What a validator checks", "rules": "The fields themselves: type, language, criteria, payload.", "method": "That a part and its props exist. Nothing about what the props say."}, + {"aspect": "Identity", "rules": "An object with its own id, referenceable from any document.", "method": "A part id, addressed through the control it sits on."}, + {"aspect": "Where it can sit", "rules": "Wherever the schema author puts it. On a component in both instances so far.", "method": "On a control, in a catalog or a profile. Nowhere else in 1.2.1."}, + {"aspect": "Fit with results", "rules": "Its own vocabulary. A finding needs a way to name a rule.", "method": "A finding targets the objective part beside it, unchanged."}, + {"aspect": "Remediation", "rules": "A second script object, typed.", "method": "A remediation part, in prose or a linked resource."}, + {"aspect": "Shown carrying", "rules": "A reference in the published files; the script in the generated file.", "method": "A reference in the published catalog; the script and a description in the generated files."} + ] + }, + "placements": { + "label": "Where it sits", + "intro": "Three homes have been used or proposed. The construct decides part of this: a part can only sit where parts are allowed, which in 1.2.1 means a control, while a new assembly sits wherever its schema puts it. What the placement decides is what the code is coupled to and how it reaches the system's plan of record.", + "options": [ + { + "key": "control", + "label": "On a control", + "models": ["catalog", "profile"], + "couples_to": "A requirement. The code says which control it tests, and the platform it runs on is a prop repeated on every method.", + "reaches_ssp": "Through the profile the plan of record imports. Nothing on the system's by-component names the objective." + }, + { + "key": "component", + "label": "On a component", + "models": ["component-definition"], + "couples_to": "A platform. The component is the thing the code runs on, stated once, and the control is a reference on the requirement.", + "reaches_ssp": "Through by-component, which is where the system's own responses live." + }, + { + "key": "activity", + "label": "On an activity", + "models": ["assessment-plan"], + "couples_to": "One assessment. The code is part of a plan for one system at one time.", + "reaches_ssp": "Not at all. The plan imports the plan of record and adds nothing to it." + } + ], + "grid_label": "Construct by placement, and what occupies each cell", + "statuses": [ + {"key": "released", "label": "Released", "meaning": "A released assembly carries it and a held file validates."}, + {"key": "proposed", "label": "Proposed", "meaning": "A held file does it with an assembly 1.2.1 does not define, and fails validation as it must."}, + {"key": "needs-schema", "label": "Needs a schema change", "meaning": "No held file, and the released schema has no place for it here."}, + {"key": "empty", "label": "Empty", "meaning": "No held file, and nothing in either proposal prevents it."} + ], + "cells": [ + {"construct": "rules", "placement": "control", "status": "empty", + "note": "No document places a typed rule assembly on a control.", "documents": []}, + {"construct": "rules", "placement": "component", "status": "proposed", + "note": "Both instances put the assembly on a validation component, one carrying a reference and one the script.", + "documents": [ + {"publisher": "component-first", "file": "oscap-validation-component-definition.json", "label": "rules and checks, published"}, + {"publisher": "executable-first", "file": "cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json", "label": "automation-scripts, generated from the CIS benchmark"} + ]}, + {"construct": "rules", "placement": "activity", "status": "empty", + "note": "No document places a typed rule assembly on an activity.", "documents": []}, + {"construct": "assessment-method", "placement": "control", "status": "released", + "note": "The part is released here. The published catalog names a check by identifier; the generated files carry the script and the check text.", + "documents": [ + {"publisher": "catalog-first", "file": "catalogs/aws_security-hub.oscal.json", "label": "naming the check, published"}, + {"publisher": "executable-first", "file": "cis-ubuntu-24-04-lts-benchmark-catalog.json", "label": "carrying the script, generated"}, + {"publisher": "executable-first", "file": "nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", "label": "added by a profile, generated"} + ]}, + {"construct": "assessment-method", "placement": "component", "status": "needs-schema", + "note": "An implemented requirement has a description, props, links, set-parameters and statements, and no parts. A part can be carried here only in a later version.", + "documents": []}, + {"construct": "assessment-method", "placement": "activity", "status": "needs-schema", + "note": "An activity and a step have props, links and a description, and no parts. The assessment-first corpus carries descriptions here, which is the second kind on the axis above and neither construct.", + "documents": []} + ] + }, + "figures": { + "note": "Recomputed by tools/verify.py --decisions from the generated Rules-shape component definition and the generated catalog.", + "rules_requirements": 49, + "rules_audit_scripts": 97, + "rules_distinct_audit_scripts": 85, + "rules_remediation_scripts": 67, + "rules_evaluated": 66, + "catalog_inline_audit_scripts": 85, + "text": "Written from one benchmark in both constructs, the Rules-shape file carries 97 audit script objects and 67 remediation script objects under 49 implemented requirements, and 66 of the audit objects carry evaluation criteria. The 97 are 85 distinct scripts, because a recommendation that names two CIS Controls is carried under both and the shape has no link between two requirements' scripts. The catalog beside it carries the same 85 scripts inline, one per method, and links the others by name." + } +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/generated-pages.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/generated-pages.json index a842f5b..eae32a1 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": "78f38c7ef742a486d4860d618df1a78e4487fef226e77317a5621f5501bab18b", - "catalog-first": "3319bcf155cdc7881b1dd1bfd42bdf9e679b2ed2ec5ec3b16576b04c15ed4ee8", - "component-first": "e169a9ca2c71028b41e0b0641dbba2a5086f6d453df2cf2eceefaf23df1d7827" + "assessment-first": "14f367b74552ad49311d12046f092f794ce8b22dbe63c6ab4f7e661d911d9477", + "catalog-first": "60a60d7e48e4c6bf2d6f397412d7c71758845761caa85b263e39bd37d72053ca", + "component-first": "a4c2a1fb4bdfb31e1d10f8db8d3d26cbf51000be581724b7fee08398225168e7", + "executable-first": "55a9067b341ac7034c1215f806ab1f9e1566c821d01b7fe463db2ab313737c5d" } } 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 e72099a..ab907fc 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" }, + { + "usage": "An assessment objective on a control, with an executable assessment method beside it", + "who": "Executable-first, Option D" + }, { "usage": "Colloquially, the check code itself", "who": "Ambiguous usage; this analysis distinguishes rule from check" @@ -402,6 +406,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 executable-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; executable-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 executable-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 be0eb87..ce09afb 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 @@ -648,6 +648,181 @@ ] } ] + }, + "executable-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 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, and the plan of record is untouched, 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 f6926f6..5ccfde5 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 @@ -441,6 +441,136 @@ } ], "rollup": null + }, + { + "key": "executable-first", + "name": "Executable-first", + "full_name": "Option D", + "option": "Option D", + "repo": null, + "root": null, + "totals": { + "Catalog": 1, + "Component definition": 1, + "Mapping collection": 1, + "Profile": 5 + }, + "files": [ + { + "file": "cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json", + "model": "component-definition", + "model_label": "Component definition", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, as a validation component carrying automation scripts", + "counts": { + "components": 1, + "validation": 1, + "automation scripts": 164, + "implemented requirements": 49 + }, + "bytes": 498246, + "href": "examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json", + "href_external": false + }, + { + "file": "cis-ubuntu-24-04-lts-benchmark-catalog.json", + "model": "catalog", + "model_label": "Catalog", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, as a catalog with executable assessment methods", + "counts": { + "groups": 7, + "controls": 312 + }, + "bytes": 1849732, + "href": "examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "href_external": false + }, + { + "file": "cis-ubuntu-24-04-lts-level-1-server-profile.json", + "model": "profile", + "model_label": "Profile", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 1 - Server", + "counts": { + "imports": 1, + "controls selected": 251 + }, + "bytes": 27613, + "href": "examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-server-profile.json", + "href_external": false + }, + { + "file": "cis-ubuntu-24-04-lts-level-1-workstation-profile.json", + "model": "profile", + "model_label": "Profile", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 1 - Workstation", + "counts": { + "imports": 1, + "controls selected": 245 + }, + "bytes": 26951, + "href": "examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-workstation-profile.json", + "href_external": false + }, + { + "file": "cis-ubuntu-24-04-lts-level-2-server-profile.json", + "model": "profile", + "model_label": "Profile", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 2 - Server", + "counts": { + "imports": 1, + "controls selected": 312 + }, + "bytes": 34758, + "href": "examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-server-profile.json", + "href_external": false + }, + { + "file": "cis-ubuntu-24-04-lts-level-2-workstation-profile.json", + "model": "profile", + "model_label": "Profile", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 2 - Workstation", + "counts": { + "imports": 1, + "controls selected": 309 + }, + "bytes": 34483, + "href": "examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-workstation-profile.json", + "href_external": false + }, + { + "file": "cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json", + "model": "mapping-collection", + "model_label": "Mapping collection", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0 mapped to NIST SP 800-53 Revision 5", + "counts": { + "mappings": 1, + "maps": 286 + }, + "bytes": 175398, + "href": "examples/executable-first/oscal/cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json", + "href_external": false + }, + { + "file": "nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", + "model": "profile", + "model_label": "Profile", + "title": "NIST SP 800-53 Revision 5, with the Canonical Ubuntu 24.04 LTS Security Technical Implementation Guide V1R5 as executable assessment methods", + "counts": { + "imports": 1, + "controls selected": 79, + "controls altered": 79, + "parts added": 582 + }, + "bytes": 849310, + "href": "examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", + "href_external": false + } + ], + "rollup": null, + "note": "No proponent has published OSCAL for this approach. What exists is a concept note, linked below, and the documents listed here were generated by tools/executable_first_corpus.py from the CIS Benchmark and the DISA STIG for Ubuntu 24.04 in the shape the note proposes. They are counted like any other corpus and they are the site's, not a proponent's.", + "document": { + "href": "examples/executable-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..4fe2ece 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 @@ ] ] } + ], + "executable-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 @@ ] ] } + ], + "executable-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 @@ ] ] } + ], + "executable-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 @@ ] ] } + ], + "executable-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 @@ ] ] } + ], + "executable-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 @@ ] ] } + ], + "executable-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 @@ ] ] } + ], + "executable-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/provenance.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/provenance.json index cde0f08..609f7dd 100644 --- a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/provenance.json +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/provenance.json @@ -1,5 +1,5 @@ { - "generated_at": "2026-09-10T14:51:40+00:00", + "generated_at": "2026-09-16T16:07:24+00:00", "source_lock": "tools/source-lock.json", "source_inputs": { "version": 1, @@ -33,7 +33,7 @@ } ] }, - "snippet_count": 32, + "snippet_count": 43, "snippets": [ { "id": "ez-stig-activity-v259312", @@ -450,6 +450,149 @@ "sha256_of_source_file": "06a6ae6a9756dbf9aed6c5c67822e35a4ca324cb2baae47cfed32003b0c57806", "sha256_of_content": "eb0d665abc0dc6c1d6528291f5888816e6db04a427d7aaa6bd52bc395d1f9595", "extracted_at": "2026-08-22T16:15:34+00:00" + }, + { + "id": "pf-cis-objective-and-param", + "slot": "1", + "approach": "executable-first", + "title": "CIS 1.1.1.1 as a control: the objective, and the exported value as a parameter", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/groups/0/groups/0/groups/0/controls/0", + "language": "json", + "bytes": 2634, + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "sha256_of_content": "f51d91c1bf53c2d13b49e35d056769df229e33d46bbf399f74821ff6232dc97e", + "extracted_at": "2026-09-09T20:09:56+00:00" + }, + { + "id": "pf-stig-objective-sc-28", + "slot": "1", + "approach": "executable-first", + "title": "STIG V-270747 as an objective a profile adds to SC-28", + "source": "site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", + "pointer": "/profile/modify/alters/63/adds/0/parts/0", + "language": "json", + "bytes": 1644, + "sha256_of_source_file": "ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697", + "sha256_of_content": "f10c8fd914a74654b6c3042dd642e7ee9d893857edaf19096677e82f53be56eb", + "extracted_at": "2026-09-16T16:07:24+00:00" + }, + { + "id": "pf-stig-import", + "slot": "2", + "approach": "executable-first", + "title": "The profile imports the framework catalog and names the controls it alters", + "source": "site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", + "pointer": "/profile/imports/0", + "language": "json", + "bytes": 1584, + "sha256_of_source_file": "ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697", + "sha256_of_content": "35e6ca62136b9af1bc1fdb3afc5e499b32115cb4c65ec727cce05d23d46c95f0", + "extracted_at": "2026-09-16T16:07:24+00:00" + }, + { + "id": "pf-cis-map-1-1-1-1", + "slot": "2", + "approach": "executable-first", + "title": "CIS 1.1.1.1 mapped to CM-7, from the benchmark's own reference", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json", + "pointer": "/mapping-collection/mappings/0/maps/0", + "language": "json", + "bytes": 328, + "sha256_of_source_file": "de1c04d1ffb7b1e82b8a1e3b41fc848a782790868c419e7e56bf96fedcb3a7ed", + "sha256_of_content": "28e1c3ca334610c990206f86fa6034c129b7d3298e36c2505af6c3c6a3276415", + "extracted_at": "2026-09-09T20:09:56+00:00" + }, + { + "id": "pf-cis-method-1-1-1-1", + "slot": "3", + "approach": "executable-first", + "title": "CIS 1.1.1.1 assessment method, carrying the published audit script", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/groups/0/groups/0/groups/0/controls/0/parts/3", + "language": "json", + "bytes": 1779, + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "sha256_of_content": "e474fa62ef41be7f1002a306ea121c2c711171eac381315af0f648ff622fe1a4", + "extracted_at": "2026-09-09T20:09:56+00:00" + }, + { + "id": "pf-cis-script-resource", + "slot": "3", + "approach": "executable-first", + "title": "The SCE script the method links to, as a back-matter resource", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/back-matter/resources/52", + "language": "json", + "bytes": 387, + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "sha256_of_content": "3c190001f21fcdb1840ed9c12fcf5f95df549387249ff713b6878a2fb7d7e9c6", + "extracted_at": "2026-09-09T20:09:56+00:00" + }, + { + "id": "pf-stig-method-sc-28", + "slot": "3", + "approach": "executable-first", + "title": "STIG V-270747 check text as a method beside its objective", + "source": "site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", + "pointer": "/profile/modify/alters/63/adds/0/parts/1", + "language": "json", + "bytes": 957, + "sha256_of_source_file": "ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697", + "sha256_of_content": "a0be2fa7f915335f745e451621b93bfcac31a2e3ca269db5861dc88c8ea1b264", + "extracted_at": "2026-09-16T16:07:24+00:00" + }, + { + "id": "pf-cis-platform", + "slot": "4", + "approach": "executable-first", + "title": "The platform a method applies to", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/groups/0/groups/0/groups/0/controls/0/parts/3/props/1", + "language": "json", + "bytes": 144, + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "sha256_of_content": "3659c3ae2934d01de667ac7f07e65de3ba833dd78c69db7bfc62eb176b9d3ffe", + "extracted_at": "2026-09-09T20:09:56+00:00" + }, + { + "id": "pf-cis-run-props", + "slot": "5", + "approach": "executable-first", + "title": "What an executor reads: the method's props", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/groups/0/groups/0/groups/0/controls/0/parts/3/props", + "language": "json", + "bytes": 557, + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "sha256_of_content": "92190f0d9ea4b021732deda21c1a5299b1f26a05bdeb071bfb69afd2492cdf12", + "extracted_at": "2026-09-09T20:09:56+00:00" + }, + { + "id": "pf-rules-requirement", + "slot": "3", + "approach": "executable-first", + "title": "CIS Control 8.9 as an implemented requirement carrying an audit and a remediation script, the Rules shape", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json", + "pointer": "/component-definition/components/0/control-implementations/0/implemented-requirements/18", + "language": "json", + "bytes": 2090, + "sha256_of_source_file": "4e08c03e080234a07ed6155e06f6b0c0756e64d28210c33473c92ffa2cb95929", + "sha256_of_content": "3f4904a75d7438c1c0a6ef4e98ec5475d5295d78d2ce4d52b4ea39b12492e0d2", + "extracted_at": "2026-09-09T20:09:56+00:00" + }, + { + "id": "pf-rules-script-1-1-1-1", + "slot": "3", + "approach": "executable-first", + "title": "CIS 1.1.1.1 audit script as an automation-scripts object, the Rules shape", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json", + "pointer": "/component-definition/components/0/control-implementations/0/implemented-requirements/8/automation-scripts/0", + "language": "json", + "bytes": 1203, + "sha256_of_source_file": "4e08c03e080234a07ed6155e06f6b0c0756e64d28210c33473c92ffa2cb95929", + "sha256_of_content": "cd7cf55a6c63c52a8fea1db4bac816192aab98d6627cfc1a35f4af2e0a09ee21", + "extracted_at": "2026-09-09T20:09:56+00:00" } ] } diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/questions.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/questions.json index 95d6218..77e043f 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 @@ -4,8 +4,8 @@ "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", @@ -124,6 +124,63 @@ "why": "Activities and steps have no parameter assembly, so the assessment-first examples place required values in text. Tailoring can therefore require editing procedural content rather than selecting controls or setting parameter values through a profile. The question is how to support reusable, auditable tailoring without losing the assessment workflow." } ] + }, + { + "key": "executable-first", + "label": "Executable-first", + "intro": "The check's code travels in the OSCAL document. What is unsettled is which construct carries it, where it may sit, who may put code there, who owns the vocabulary that runs it, and what the executor matches against.", + "questions": [ + { + "id": "typed-assembly-or-props", + "q": "Does a future version add a typed assembly for the executable, or standardise the props on the released part?", + "why": "Two constructs carry code today. A typed assembly, the Rules construct, gives a validator the executor fields themselves and needs a version to ship; the released assessment-method part validates now and gives a validator nothing beyond the existence of a prop. The start page's section 6 states the trade aspect by aspect. Which side a future version takes decides whether the vocabulary lives in the schema or beside it, and neither the concept note nor the published proposal has been put to the Foundation as a schema change." + }, + { + "id": "which-assemblies-carry-code", + "q": "Which assemblies may carry an executable: a part on a control, an implemented requirement, a by-component, an activity?", + "why": "In 1.2.1 a part sits on a control and nowhere else, so the released construct is bound to the control layer, and an implemented requirement, a by-component and an activity have props, links and a description but no parts. The Rules construct sits wherever its schema puts it, on a component in both instances so far. Each home couples the code to something different, a requirement, a platform, or one assessment. The grid in section 6 shows two of six cells occupied." + }, + { + "id": "executable-reaches-ssp", + "q": "How does an executable on a control reach the system's plan of record?", + "why": "A check on a component reaches the system security plan through by-component, where the system's own responses live. A check on a control reaches it only through the profile the plan imports, and nothing on the by-component names the objective the check tests, which is why question 6a, how a system says it satisfies the rule in its own words, is the fourth approach's weakest cell. Whether a by-component may name an objective, or a part may sit on an implemented requirement, is the same question from the implementation layer." + }, + { + "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, does a mapping collection carry its tie 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 the note supplies no tie. The generated corpus turns the benchmark's own SP 800-53 references into a mapping collection, which reaches controls and statements and not parts, so it ties the recommendation and not the objective beside it. Whether that is the route the note intends is open." + }, + { + "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." + }, + { + "id": "param-names", + "q": "How does a parameter reach a script that expects a fixed variable name?", + "why": "The note exports every param on a control as an environment variable named after the param id. CIS-CAT's scripts read one variable, XCCDF_VALUE_REGEX, and OSCAL parameter ids are unique across a document, so the 82 controls that export a value cannot each declare a parameter of that name. The generated corpus carries the variable's name as the parameter's class, and the note's convention has no answer for it yet." + } + ] } ] } 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 3d5b859..4059b48 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 and three hardening guides, modelled with each approach. The scenario compares document counts and system security plan content, not overall capability. Counts derive from the corpus, the NIST profile in data/scenario-evidence/, or OSCAL schema constraints. Each file row records the applicable constraint.", + "note": "One system, one baseline and three hardening guides, modelled with each of the four approaches. The scenario compares document counts and system security plan content, not overall capability. Counts derive from the corpus, the NIST profile in data/scenario-evidence/, or OSCAL schema constraints. Each file row records the applicable constraint.", "title": "One system, three hardening guides", - "summary": "A system follows the NIST SP 800-53 Revision 5 High baseline and hardening guides for Ubuntu, PostgreSQL and Microsoft 365. The three approaches model the same requirements, using every OSCAL model except the plan of action and milestones.", + "summary": "A system follows the NIST SP 800-53 Revision 5 High baseline and hardening guides for Ubuntu, PostgreSQL and Microsoft 365. The four approaches model the same requirements, using every OSCAL model except the plan of action and milestones.", "excluded_model": { "model": "plan-of-action-and-milestones", - "reason": "The plan of action and milestones records unmet requirements and remediation. The document serves the same purpose in all three approaches and is excluded from the comparison." + "reason": "The plan of action and milestones records unmet requirements and remediation. The document serves the same purpose in all four approaches and is excluded from the comparison." }, "framework": { "label": "NIST SP 800-53 Revision 5, High baseline", @@ -368,6 +368,108 @@ } ], "plan_of_record": "The system security plan addresses 370 controls; all three guides remain in assessment plans" + }, + "executable-first": { + "rule": "Each guide is published as a catalog whose controls carry their own executable methods, each component references a profile selecting from it, and each guide's own framework references become a mapping collection. 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": 3, + "what": "one per guide, from the guide's own framework references", + "detail": "CIS names SP 800-53 controls in its recommendations' identifiers, the STIG names CCIs, and SCuBA names controls on every step, so each guide's own references become a mapping collection from its objectives' controls to the framework; where a profile adds the check to the framework control instead, the placement is the tie and nothing is mapped", + "items": [ + { + "name": "CIS to 800-53" + }, + { + "name": "STIG to 800-53" + }, + { + "name": "SCuBA to 800-53" + } + ] + }, + { + "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": "Each entry represents one file, with a name shortened for the diagram tile. Component-first distinguishes the product component, of type software, from the checking component, of type validation. File counts alone do not show component types." diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/six-questions.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/six-questions.json index 8056f22..0e84bf7 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; a property identifies the check." + }, + { + "key": "executable-first", + "label": "Executable-first", + "option_letter": "D", + "primary_model": "profile", + "layer": "Control", + "serves_stakeholder_first": "assessor", + "repo": null, + "status_annotation": "generated corpus, not a proponent's publication", + "one_line": "The rule is an assessment objective part on a control; the check is an executable assessment method beside it, or a typed assembly on a component." } ], "empty_states": [ @@ -81,7 +92,8 @@ "available_to": { "catalog-first": true, "component-first": false, - "assessment-first": false + "assessment-first": false, + "executable-first": false }, "why": "mapping-item.type is restricted by allOf to control and statement, and mapping-item has neither uuid nor href. External mappings therefore reach rules modelled as controls or control statements, not component rules or activities. This OSCAL schema constraint does not establish a preferred approach." } @@ -644,9 +656,183 @@ "finding", "observation" ] + }, + { + "slot": "1", + "approach": "executable-first", + "state": "filled", + "snippet_ids": [ + "pf-cis-objective-and-param", + "pf-stig-objective-sc-28" + ], + "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": "executable-first", + "state": "filled", + "snippet_ids": [ + "pf-stig-import", + "pf-cis-map-1-1-1-1" + ], + "note": "Placement where a profile adds the check to the framework control; a mapping collection where the guide is its own catalog and publishes its framework references.", + "mechanisms": [ + "assembly" + ], + "model": "profile", + "assemblies": [ + "alter" + ] + }, + { + "slot": "3", + "approach": "executable-first", + "state": "filled", + "snippet_ids": [ + "pf-cis-method-1-1-1-1", + "pf-cis-script-resource", + "pf-stig-method-sc-28" + ], + "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": "executable-first", + "state": "partial", + "snippet_ids": [ + "pf-cis-platform" + ], + "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": "executable-first", + "state": "partial", + "snippet_ids": [ + "pf-cis-run-props" + ], + "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": "executable-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": "executable-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 approaches. No approach fully answers both 6a and 6b, and no approach answers every question.", + "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", @@ -695,7 +881,7 @@ "why_uneven": "Answer states describe evidence coverage. Mechanism descriptions also explain schema and tool-support requirements, so the descriptions need additional detail." }, "mechanism_note": "Answer states describe coverage in the published corpus. Mechanism badges identify the OSCAL structures needed to represent an answer. Evidence coverage does not establish schema adoption or tool interoperability.", - "carrier_note": "Each answer identifies the OSCAL model and assemblies representing the capability. Rules use catalog controls, component rules or assessment activities; the choice affects references to checks, claims and results.", + "carrier_note": "Each answer identifies the OSCAL model and assemblies representing the capability. Rules use catalog controls, component rules, assessment activities or assessment objective parts on a control; the choice affects references to checks, claims and results.", "proposed_assemblies": [ "assessment-check-id", "associated-checks", diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-map-1-1-1-1.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-map-1-1-1-1.json new file mode 100644 index 0000000..89dc75f --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-map-1-1-1-1.json @@ -0,0 +1,13 @@ +{ + "id": "pf-cis-map-1-1-1-1", + "slot": "2", + "approach": "executable-first", + "title": "CIS 1.1.1.1 mapped to CM-7, from the benchmark's own reference", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json", + "pointer": "/mapping-collection/mappings/0/maps/0", + "section": null, + "language": "json", + "content": "{\n \"uuid\": \"15411d58-ef50-5bd9-9ac0-f4d53602cc2c\",\n \"relationship\": \"subset-of\",\n \"sources\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\"\n }\n ],\n \"targets\": [\n {\n \"type\": \"control\",\n \"id-ref\": \"cm-7\"\n }\n ]\n}", + "sha256_of_source_file": "de1c04d1ffb7b1e82b8a1e3b41fc848a782790868c419e7e56bf96fedcb3a7ed", + "extracted_at": "2026-09-09T20:09:56+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-method-1-1-1-1.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-method-1-1-1-1.json new file mode 100644 index 0000000..adfd42c --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-method-1-1-1-1.json @@ -0,0 +1,13 @@ +{ + "id": "pf-cis-method-1-1-1-1", + "slot": "3", + "approach": "executable-first", + "title": "CIS 1.1.1.1 assessment method, carrying the published audit script", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/groups/0/groups/0/groups/0/controls/0/parts/3", + "section": null, + "language": "json", + "content": "{\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_asm\",\n \"name\": \"assessment-method\",\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:*:*:*:lts:*:*:*\",\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\": \"stdout-regex\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"\\\\*\\\\* PASS \\\\*\\\\*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_obj\"\n },\n {\n \"rel\": \"script\",\n \"href\": \"#57406427-e772-5765-9a71-89d9da9cd0b3\"\n }\n ],\n \"prose\": \"Run 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 within the `/etc/modprobe.d/` directory\\n\\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\\n\\n- The module is not loaded in the running kernel\\n\\n**- IF -** the `cramfs` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\\n\\n```bash\\n#!/usr/bin/env bash\\n\\n{\\n a_output=() a_output2=() a_output3=() l_dl=\\\"\\\" l_mod_name=\\\"cramfs\\\" l_mod_type=\\\"fs\\\"\\n l_mod_path=\\\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\\\"\\n f_ [truncated]\"\n}", + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "extracted_at": "2026-09-09T20:09:56+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-objective-and-param.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-objective-and-param.json new file mode 100644 index 0000000..4ac14f8 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-objective-and-param.json @@ -0,0 +1,13 @@ +{ + "id": "pf-cis-objective-and-param", + "slot": "1", + "approach": "executable-first", + "title": "CIS 1.1.1.1 as a control: the objective, and the exported value as a parameter", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/groups/0/groups/0/groups/0/controls/0", + "section": null, + "language": "json", + "content": "{\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available\",\n \"title\": \"1.1.1.1 Ensure cramfs kernel module is not available\",\n \"params\": [\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_xccdf-value-regex\",\n \"class\": \"XCCDF_VALUE_REGEX\",\n \"label\": \"Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX\",\n \"values\": [\n \"cramfs:fs\"\n ]\n }\n ],\n \"links\": [\n {\n \"rel\": \"reference\",\n \"href\": \"http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8\"\n }\n ],\n \"parts\": [\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_smt\",\n \"name\": \"statement\",\n \"prose\": \"...\"\n },\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_rationale\",\n \"name\": \"rationale\",\n \"prose\": \"...\"\n },\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_obj\",\n \"name\": \"assessment-objective\",\n \"prose\": \"Ensure cramfs kernel module is not available\"\n },\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_asm\",\n \"name\": \"assessment-method\",\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:*:*:*:lts:*:*:*\",\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\": \"stdout-regex\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"\\\\*\\\\* PASS \\\\*\\\\*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n ],\n \"links\": [\n {\n \"rel\": \"assessment-objective\",\n \"href\": \"#xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_obj\"\n },\n {\n \"rel\": \"script\",\n \"href\": \"#57406427-e772-5765-9a71-89d9da9cd0b3\"\n }\n ],\n \"prose\": \"...\"\n },\n {\n \"id\": \"xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_rem\",\n \"name\": \"remediation\",\n \"ns\": \"https://example.org/ns/oscal-automation\",\n \"prose\": \"...\"\n }\n ]\n}", + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "extracted_at": "2026-09-09T20:09:56+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-platform.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-platform.json new file mode 100644 index 0000000..d950cd8 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-platform.json @@ -0,0 +1,13 @@ +{ + "id": "pf-cis-platform", + "slot": "4", + "approach": "executable-first", + "title": "The platform a method applies to", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/groups/0/groups/0/groups/0/controls/0/parts/3/props/1", + "section": null, + "language": "json", + "content": "{\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n}", + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "extracted_at": "2026-09-09T20:09:56+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-run-props.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-run-props.json new file mode 100644 index 0000000..d6c4e39 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-run-props.json @@ -0,0 +1,13 @@ +{ + "id": "pf-cis-run-props", + "slot": "5", + "approach": "executable-first", + "title": "What an executor reads: the method's props", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/groups/0/groups/0/groups/0/controls/0/parts/3/props", + "section": null, + "language": "json", + "content": "[\n {\n \"name\": \"method\",\n \"value\": \"TEST\"\n },\n {\n \"name\": \"platform\",\n \"value\": \"cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*\",\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\": \"stdout-regex\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n },\n {\n \"name\": \"pass-condition\",\n \"value\": \"\\\\*\\\\* PASS \\\\*\\\\*\",\n \"ns\": \"https://example.org/ns/oscal-automation\"\n }\n]", + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "extracted_at": "2026-09-09T20:09:56+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-script-resource.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-script-resource.json new file mode 100644 index 0000000..24e97f6 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-cis-script-resource.json @@ -0,0 +1,13 @@ +{ + "id": "pf-cis-script-resource", + "slot": "3", + "approach": "executable-first", + "title": "The SCE script the method links to, as a back-matter resource", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json", + "pointer": "/catalog/back-matter/resources/52", + "section": null, + "language": "json", + "content": "{\n \"uuid\": \"57406427-e772-5765-9a71-89d9da9cd0b3\",\n \"title\": \"nix_module_chk_v3.sh\",\n \"description\": \"Script Check Engine script, named by the check expression of 13 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.\",\n \"rlinks\": [\n {\n \"href\": \"nix_module_chk_v3.sh\",\n \"media-type\": \"application/x-sh\"\n }\n ]\n}", + "sha256_of_source_file": "d7635aa96f844e3e957ae145e05da19f4792a11878f194a43b2216de125431c2", + "extracted_at": "2026-09-09T20:09:56+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-rules-requirement.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-rules-requirement.json new file mode 100644 index 0000000..cafe61a --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-rules-requirement.json @@ -0,0 +1,13 @@ +{ + "id": "pf-rules-requirement", + "slot": "3", + "approach": "executable-first", + "title": "CIS Control 8.9 as an implemented requirement carrying an audit and a remediation script, the Rules shape", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json", + "pointer": "/component-definition/components/0/control-implementations/0/implemented-requirements/18", + "section": null, + "language": "json", + "content": "{\n \"uuid\": \"ddc6b3e7-be8e-5726-a50d-11556f483150\",\n \"control-id\": \"cisc-008.009\",\n \"description\": \"6.1.3.3 Ensure journald is configured to send logs to rsyslog\",\n \"automation-scripts\": [\n {\n \"uuid\": \"c337f042-ddc5-5936-9a71-70bfd4d11ed0\",\n \"benchmark-rule-id\": \"6.1.3.3\",\n \"script-type\": \"audit\",\n \"language\": \"bash\",\n \"applicable-profiles\": [\n \"Level 1 - Server\",\n \"Level 2 - Server\",\n \"Level 1 - Workstation\",\n \"Level 2 - Workstation\"\n ],\n \"evaluation-criteria\": {\n \"method\": \"stdout-regex\",\n \"pass-condition\": \"^\\\\*\\\\* PASS \\\\*\\\\*$\",\n \"fail-condition\": \"^\\\\*\\\\* FAIL \\\\*\\\\*$\"\n },\n \"payload\": \"#!/usr/bin/env bash\\n\\n{\\n a_output=() a_output2=() l_analyze_cmd=\\\"$(readlink -f /bin/systemd-analyze)\\\" l_systemd_config_file=\\\"systemd/journald.conf\\\"\\n a_parameters=(\\\"ForwardToSyslog=yes\\\")\\n f_config_file_parameter_chk()\\n {\\n l_used_parameter_setting=\\\"\\\"\\n while IFS= read -r l_file; do\\n l_file=\\\"$(tr -d '# ' <<< \\\"$l_file\\\")\\\"\\n l_used_parameter_setting=\\\"$(grep -PHs -- '^\\\\h*'\\\"$l_parameter_name\\\"'\\\\b' \\\"$l_file\\\" | tail -n 1)\\\"\\n [ -n \\\"$l_used_parameter_setting\\\" ] && break [truncated]\"\n },\n {\n \"uuid\": \"64454ac1-9539-51e5-8366-3bf5798e7935\",\n \"benchmark-rule-id\": \"6.1.3.3\",\n \"script-type\": \"remediation\",\n \"language\": \"bash\",\n \"applicable-profiles\": [\n \"Level 1 - Server\",\n \"Level 2 - Server\",\n \"Level 1 - Workstation\",\n \"Level 2 - Workstation\"\n ],\n \"payload\": \"#!/usr/bin/env bash\\n\\n{\\n a_settings=(\\\"ForwardToSyslog=yes\\\")\\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\\n if grep -Psq -- '^\\\\h*\\\\[Journal\\\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\\n printf '%s\\\\n' \\\"\\\" \\\"${a_settings[@]}\\\" >> /etc/systemd/journald.conf.d/60-journald.conf\\n else\\n printf '%s\\\\n' \\\"\\\" \\\"[Journal]\\\" \\\"${a_settings[@]}\\\" >> /etc/systemd/journald.conf.d/60-journald.conf\\n fi\\n}\\n\"\n }\n ],\n \"props\": \"...\"\n}", + "sha256_of_source_file": "4e08c03e080234a07ed6155e06f6b0c0756e64d28210c33473c92ffa2cb95929", + "extracted_at": "2026-09-09T20:09:56+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-rules-script-1-1-1-1.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-rules-script-1-1-1-1.json new file mode 100644 index 0000000..74595cb --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-rules-script-1-1-1-1.json @@ -0,0 +1,13 @@ +{ + "id": "pf-rules-script-1-1-1-1", + "slot": "3", + "approach": "executable-first", + "title": "CIS 1.1.1.1 audit script as an automation-scripts object, the Rules shape", + "source": "site:examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json", + "pointer": "/component-definition/components/0/control-implementations/0/implemented-requirements/8/automation-scripts/0", + "section": null, + "language": "json", + "content": "{\n \"uuid\": \"a377e3f3-6e54-5ebf-9010-96b245f533da\",\n \"benchmark-rule-id\": \"1.1.1.1\",\n \"script-type\": \"audit\",\n \"language\": \"bash\",\n \"applicable-profiles\": [\n \"Level 1 - Server\",\n \"Level 2 - Server\",\n \"Level 1 - Workstation\",\n \"Level 2 - Workstation\"\n ],\n \"evaluation-criteria\": {\n \"method\": \"stdout-regex\",\n \"pass-condition\": \"^\\\\*\\\\* PASS \\\\*\\\\*$\",\n \"fail-condition\": \"^\\\\*\\\\* FAIL \\\\*\\\\*$\"\n },\n \"payload\": \"#!/usr/bin/env bash\\n\\n{\\n a_output=() a_output2=() a_output3=() l_dl=\\\"\\\" l_mod_name=\\\"cramfs\\\" l_mod_type=\\\"fs\\\"\\n l_mod_path=\\\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\\\"\\n f_module_chk()\\n {\\n l_dl=\\\"y\\\" a_showconfig=()\\n while IFS= read -r l_showconfig; do\\n a_showconfig+=(\\\"$l_showconfig\\\")\\n done < <(modprobe --showconfig | grep -P -- '\\\\b(install|blacklist)\\\\h+'\\\"${l_mod_chk_name//-/_}\\\"'\\\\b')\\n if ! lsmod | grep \\\"$l_mod_chk_name\\\" &> /dev/null; then\\n a_output+=(\\\" - kernel module: \\\\\\\"$l_mod_name\\\\\\\" is not loaded\\\")\\n else\\n a_output2+=(\\\" - kernel module: \\\\\\\"$l_mod_name\\\\\\\" is loaded\\\")\\n fi\\n if grep -Pq -- '\\\\binstall\\\\h+'\\\"${l_mod_chk_nam [truncated]\"\n}", + "sha256_of_source_file": "4e08c03e080234a07ed6155e06f6b0c0756e64d28210c33473c92ffa2cb95929", + "extracted_at": "2026-09-09T20:09:56+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-stig-import.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-stig-import.json new file mode 100644 index 0000000..58dd883 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-stig-import.json @@ -0,0 +1,13 @@ +{ + "id": "pf-stig-import", + "slot": "2", + "approach": "executable-first", + "title": "The profile imports the framework catalog and names the controls it alters", + "source": "site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", + "pointer": "/profile/imports/0", + "section": null, + "language": "json", + "content": "{\n \"href\": \"https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json\",\n \"include-controls\": [\n {\n \"with-ids\": [\n \"ac-10\",\n \"ac-11\",\n \"ac-11.1\",\n \"ac-12\",\n \"ac-17.1\",\n \"ac-17.2\",\n \"ac-2.2\",\n \"ac-2.3\",\n \"ac-2.4\",\n \"ac-3\",\n \"ac-3.4\",\n \"ac-6.10\",\n \"ac-6.8\",\n \"ac-6.9\",\n \"ac-7\",\n \"ac-8\",\n \"au-12\",\n \"au-12.3\",\n \"au-14.1\",\n \"au-3\",\n \"au-3.1\",\n \"au-4\",\n \"au-4.1\",\n \"au-5\",\n \"au-5.1\",\n \"au-6.4\",\n \"au-7\",\n \"au-7.1\",\n \"au-8\",\n \"au-9\",\n \"au-9.3\",\n \"cm-14\",\n \"cm-3.5\",\n \"cm-5.1\",\n \"cm-5.6\",\n \"cm-6\",\n \"cm-7\",\n \"cm-7.2\",\n \"cm-7.5\",\n \"cm-7.9\",\n \"ia-11\",\n \"ia-2\",\n \"ia-2.1\",\n \"ia-2.12\",\n \"ia-2.2\",\n \"ia-2.5\",\n \"ia-2.6\",\n \"ia-3\",\n \"ia-5.1\",\n \"ia-5.13\",\n \"ia-5.2\",\n \"ia-7\",\n \"ia-8\",\n \"ma-3.5\",\n \"ma-4\",\n \"ma-4.1\",\n \"ma-4.6\",\n \"sc-10\",\n \"sc-11\",\n \"sc-13\",\n \"sc-17\",\n \"sc-23.5\",\n \"sc-24\",\n \"sc-28\",\n \"sc-28.1\",\n \"sc-28.3\",\n \"sc-3\",\n \"sc-4\",\n \"sc-45\",\n \"sc-45.1\",\n \"sc-5\",\n \"sc-5.2\",\n \"sc-8\",\n \"sc-8.1\",\n \"sc-8.2\",\n \"si-11\",\n \"si-16\",\n \"si-2.6\",\n \"si-6\"\n ]\n }\n ]\n}", + "sha256_of_source_file": "ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697", + "extracted_at": "2026-09-16T16:07:24+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-stig-method-sc-28.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-stig-method-sc-28.json new file mode 100644 index 0000000..1e512cb --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-stig-method-sc-28.json @@ -0,0 +1,13 @@ +{ + "id": "pf-stig-method-sc-28", + "slot": "3", + "approach": "executable-first", + "title": "STIG V-270747 check text as a method beside its objective", + "source": "site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", + "pointer": "/profile/modify/alters/63/adds/0/parts/1", + "section": null, + "language": "json", + "content": "{\n \"id\": \"sc-28_asm-ubtu-24-600090\",\n \"name\": \"assessment-method\",\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:*:*:*:lts:*:*:*\",\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\": \"Note: 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$ sudo fdisk -l \\n(..) \\nDisk /dev/vda: 15 GiB, 16106127360 bytes, 31457280 sectors \\nUnits: sectors of 1 * 512 = 512 bytes \\nSector siz [truncated]\"\n}", + "sha256_of_source_file": "ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697", + "extracted_at": "2026-09-16T16:07:24+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-stig-objective-sc-28.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-stig-objective-sc-28.json new file mode 100644 index 0000000..28855f2 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/snippets/pf-stig-objective-sc-28.json @@ -0,0 +1,13 @@ +{ + "id": "pf-stig-objective-sc-28", + "slot": "1", + "approach": "executable-first", + "title": "STIG V-270747 as an objective a profile adds to SC-28", + "source": "site:examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json", + "pointer": "/profile/modify/alters/63/adds/0/parts/0", + "section": null, + "language": "json", + "content": "{\n \"id\": \"sc-28_obj-ubtu-24-600090\",\n \"name\": \"assessment-objective\",\n \"props\": [\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\": \"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 \"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 \"parts\": [\n {\n \"id\": \"sc-28_dsc-ubtu-24-600090\",\n \"name\": \"guidance\",\n \"prose\": \"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 configura [truncated]\"\n }\n ]\n}", + "sha256_of_source_file": "ab9a524515cc43bd1a4a2798dd09782f9d962802c89ed661ffa10887c1e8a697", + "extracted_at": "2026-09-16T16:07:24+00:00" +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/data/stakeholders.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/data/stakeholders.json index ebaf5e1..0632d98 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 @@ -291,6 +291,76 @@ ], "note": "The auditor's run produces assessment results, not implementation claims. The workflow does not update the system security plan." } + }, + "executable-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 whose controls carry their own executable methods." + }, + "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. Running 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": "Providers build policy engines. System owners and auditors run checks to produce implementation responses or assessment results." } ], - "runtime": "A policy engine reads OSCAL, executes checks and writes OSCAL. Providers publish the checks; each flow identifies the party executing the checks." + "runtime": "A policy engine reads OSCAL, executes checks and writes OSCAL. Providers publish the checks; each flow identifies the party executing the checks.", + "shared_profile": { + "executable-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 fe8a76e..7c344db 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 @@ -113,6 +113,45 @@ "body": "The published result references a plan absent from the corpus and assigns an observation a subject type not defined by the model." } ] + }, + "executable-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 rule", + "body": "A profile adds parts 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 script as environment variables, so one script serves many controls with each organisation's own value." + }, + { + "title": "Findings need no new field", + "body": "The method links to an assessment objective, so a finding targets an objective id every 800-53A consumer already reads." + }, + { + "title": "The plan of record stays put", + "body": "Methods sit on controls the assessment plan reads, so hundreds of checks add no control to the plan of record." + } + ], + "cons": [ + { + "title": "The catalog becomes code", + "body": "A profile resolved from a URL and executed is a remote code path into every assessed system, operated by the profile author." + }, + { + "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 runs nothing." + }, + { + "title": "The subject is a convention", + "body": "The platform prop is a CPE that no SSP component carries, so which host runs a check is decided outside the schema." + }, + { + "title": "Claim and result never meet", + "body": "The finding targets the objective and the response the control, so the plan of record cannot name the checks behind its claim." + } + ] } } } 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 e15eff9..18f619f 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 editorial interpretations of a hardening rule, ordered by OSCAL layer rather than rank. The analysis uses a working definition without selecting an interpretation. Each view links to a stakeholder glossary term.", + "note": "Three editorial interpretations of a hardening rule, ordered by OSCAL layer rather than rank. The analysis uses a working definition without selecting an interpretation. Each view links to a stakeholder glossary term. 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 and differs in the construct that carries it.", "why_this_matters": "OSCAL has no dedicated core requirement-level field distinguishing shall, should and may. The gap affects every approach; model placement alone cannot establish whether guidance expresses requirements, capabilities or assessment procedures.", "views": [ { @@ -9,7 +9,11 @@ "stakeholder": "publisher", "implies_layer": "Control", "implies_model": "catalog", - "aligned_approach": "catalog-first" + "aligned_approach": "catalog-first", + "also_aligned": [ + "executable-first" + ], + "also_aligned_note": "Executable-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/executable-first/README.md b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/README.md new file mode 100644 index 0000000..49854e2 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/README.md @@ -0,0 +1,93 @@ +# Executable-first: the concept note, and a corpus generated in its shape + +No proponent has published OSCAL for the executable-first approach. What its +proponent has published is the concept note in this directory, +`executable-assessment-methods.md`. Everything under `oscal/` was written by +`tools/executable_first_corpus.py`, from two pieces of published hardening +guidance this repository already holds, in the shape the note proposes. The +files are the site's, and the site says so wherever it counts them. + +## What is here + +| File | Model | From | +|---|---|---| +| `cis-ubuntu-24-04-lts-benchmark-catalog.json` | catalog | `sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json` | +| `cis-ubuntu-24-04-lts-level-1-server-profile.json`, and the three beside it | profile | the benchmark's own four profiles | +| `cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json` | mapping-collection | the SP 800-53 references in the benchmark's own identifiers | +| `nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json` | profile | `sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml`, and the CCI to control mapping in the STIG's published OSCAL conversion | +| `cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json` | component-definition, Rules shape | the same benchmark file, as a validation component carrying an `automation-scripts` assembly | + +Two routes, because the note names two, and then the same benchmark once more +in the other construct. + +**The Rules shape**, for the second construct the site compares. The benchmark +becomes a validation component whose implemented requirements are keyed to the +CIS Controls v8 safeguards the benchmark names in its own identifiers, and +each carries an +`automation-scripts` object per audit or remediation script: type, language, +the benchmark profiles it applies to, evaluation criteria where the script +prints the result line, and the script as payload. Recommendations that name +no CIS Control sit under a second control implementation whose source is the +catalog beside the file. OSCAL 1.2.1 does not define `automation-scripts`, so +this file fails validation, the generator expects it to, and `--conformance` +checks that it does. A recommendation naming two safeguards is carried under +both, because the shape has no link between two requirements' scripts. + +**The catalog route**, where the author of the requirement is the author of the +check. Every CIS recommendation is a control carrying an `assessment-objective` +part, an `assessment-method` part with `method` TEST or EXAMINE as the benchmark +says, the audit procedure as its body, and a `remediation` part. The method +carries the note's props: `platform`, the CPE the benchmark publishes; +`language` bash where the audit is a bash script or a Script Check Engine +script is named; and `evaluation` and `pass-condition` where the script prints +the audit result line CIS's scripts print. Each SCE script the benchmark's +check expression names is a back-matter resource the method links to, and the +value CIS-CAT exports to it is a parameter of the control. The benchmark's four +profiles are four OSCAL profiles, and its own SP 800-53 references are a mapping +collection. + +**The profile route**, where someone other than the catalog author supplies the +check. The STIG becomes a profile that imports the NIST Revision 5 catalog and +adds, to each control a rule's CCIs map to, an objective carrying the rule and +a method carrying DISA's check text. A rule that serves more than one control +puts its parts on the first and links the others to the objective. + +## What is real and what is derived + +Every control, part, identifier, value and script body is taken from the +source file. The shape is the generator's. Three things are worth knowing +before reading the files as if a publisher had shipped them. + +- CIS's audit prose is XHTML in the benchmark file and OSCAL prose is Markdown, + so it is converted: paragraphs, lists, emphasis, inline code and fenced + blocks. Nothing is reworded. +- One benchmark section holds recommendations and a sub-section together, + which an OSCAL group cannot. Its own recommendations sit in a sub-group whose + id ends in `_recommendations`. That is the one place the structure is not + CIS's. +- The STIG carries no CPE, so its methods take the platform CIS publishes for + the same operating system. + +## What is not here + +- The SCE script bodies ship with CIS-CAT and are not in the benchmark file. + Their resources carry a name and no hash, which is exactly the gap the note's + security section says an executor must refuse. +- DISA publishes the STIG's checks as text a person follows. The SCAP content + that automates them ships separately and is not held, so the STIG's methods + name no engine and no evaluation rule. +- No system security plan, assessment plan or assessment result. Nothing has + been run. + +## Checking it + +``` +python tools/executable_first_corpus.py --check the committed files are what the generator writes +python tools/executable_first_corpus.py --validate every file against OSCAL 1.2.1, if trestle is on the path +python tools/verify.py --corpus the counts, the links and the structure, recomputed +``` + +The seven assessment-method files validate under compliance-trestle 5.1.0, +which carries the OSCAL 1.2.1 schemas, and under the published JSON schemas +for the catalog, profile and mapping models. The Rules-shape file fails, on +the `automation-scripts` field, and that is the expected result. diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/executable-assessment-methods.md b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/executable-assessment-methods.md new file mode 100644 index 0000000..e3bb216 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-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/examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json new file mode 100644 index 0000000..9f54f36 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-automation-scripts-component-definition.json @@ -0,0 +1,3079 @@ +{ + "component-definition": { + "uuid": "c728973f-f325-58bf-b310-61a7320908ca", + "metadata": { + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, as a validation component carrying automation scripts", + "published": "2026-03-16T00:00:00Z", + "last-modified": "2026-09-09T00:00:00Z", + "version": "1.0.0", + "oscal-version": "1.2.1", + "remarks": "Generated by tools/executable_first_corpus.py from the same benchmark file as the catalog beside it, in the Rules shape: an automation-scripts assembly on the implemented requirements of a validation component, the site's own encoding of that construct. OSCAL 1.2.1 does not define that assembly, so this file does not validate, and it is not meant to. Every script, identifier, profile and rationale is taken from the benchmark file; the requirements are keyed to CIS Controls v8 through the references in the benchmark's own identifiers, and the recommendations that name none sit under a second control implementation whose source is the catalog beside this file." + }, + "components": [ + { + "uuid": "02685b37-4136-5b6f-a41c-5df91ee32941", + "type": "validation", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark bash automation", + "description": "The audit and remediation scripts the benchmark publishes, one script object each, on the CIS Control each recommendation names.", + "props": [ + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "control-implementations": [ + { + "uuid": "0d934cb6-d4df-532a-b3e3-cba869a37442", + "source": "http://cisecurity.org/20-cc/v8.0/", + "description": "Scripts keyed to the CIS Controls v8 safeguards the benchmark's recommendations reference.", + "implemented-requirements": [ + { + "uuid": "47a922a3-22eb-5eef-9230-b6a4e393a4a4", + "control-id": "cisc-003.003", + "description": "1.1.2.1.3 Ensure nosuid option set on /tmp partition; 1.1.2.1.4 Ensure noexec option set on /tmp partition; 1.1.2.2.2 Ensure nodev option set on /dev/shm partition; 1.1.2.2.3 Ensure nosuid option set on /dev/shm partition; 1.1.2.2.4 Ensure noexec option set on /dev/shm partition; 1.1.2.3.1 Ensure separate partition exists for /home; 1.1.2.3.2 Ensure nodev option set on /home partition; 1.1.2.3.3 Ensure nosuid option set on /home partition; 1.1.2.4.1 Ensure separate partition exists for /var; 1.1.2.4.2 Ensure nodev option set on /var partition; 1.1.2.4.3 Ensure nosuid option set on /var partition; 1.1.2.5.1 Ensure separate partition exists for /var/tmp; 1.1.2.5.2 Ensure nodev option set on /var/tmp partition; 1.1.2.5.3 Ensure nosuid option set on /var/tmp partition; 1.1.2.5.4 Ensure noexec option set on /var/tmp partition; 1.1.2.6.2 Ensure nodev option set on /var/log partition; 1.1.2.6.3 Ensure nosuid option set on /var/log partition; 1.1.2.6.4 Ensure noexec option set on /var/log partition; 1.1.2.7.2 Ensure nodev option set on /var/log/audit partition; 1.1.2.7.3 Ensure nosuid option set on /var/log/audit partition; 1.1.2.7.4 Ensure noexec option set on /var/log/audit partition; 1.3.1.1 Ensure AppArmor is installed; 1.3.1.2 Ensure AppArmor is enabled in the bootloader configuration; 1.3.1.3 Ensure all AppArmor Profiles are in enforce or complain mode; 1.3.1.4 Ensure all AppArmor Profiles are enforcing; 1.4.1 Ensure bootloader password is set; 1.4.2 Ensure access to bootloader config is configured; 1.6.4 Ensure access to /etc/motd is configured; 1.6.5 Ensure access to /etc/issue is configured; 1.6.6 Ensure access to /etc/issue.net is configured; 2.4.1.2 Ensure permissions on /etc/crontab are configured; 2.4.1.3 Ensure permissions on /etc/cron.hourly are configured; 2.4.1.4 Ensure permissions on /etc/cron.daily are configured; 2.4.1.5 Ensure permissions on /etc/cron.weekly are configured; 2.4.1.6 Ensure permissions on /etc/cron.monthly are configured; 2.4.1.7 Ensure permissions on /etc/cron.d are configured; 2.4.1.8 Ensure crontab is restricted to authorized users; 2.4.2.1 Ensure at is restricted to authorized users; 5.1.1 Ensure permissions on /etc/ssh/sshd_config are configured; 5.1.2 Ensure permissions on SSH private host key files are configured; 5.1.3 Ensure permissions on SSH public host key files are configured; 5.1.4 Ensure sshd access is configured; 5.2.7 Ensure access to the su command is restricted; 5.3.2.1 Ensure pam_unix module is enabled; 5.4.2.2 Ensure root is the only GID 0 account; 5.4.2.3 Ensure group root is the only GID 0 group; 5.4.2.4 Ensure root account access is controlled; 5.4.2.6 Ensure root user umask is configured; 5.4.2.7 Ensure system accounts do not have a valid login shell; 5.4.2.8 Ensure accounts without a valid login shell are locked; 5.4.3.3 Ensure default user umask is configured; 6.1.1.2 Ensure journald log file access is configured; 6.1.3.4 Ensure rsyslog log file creation mode is configured; 6.1.4.1 Ensure access to all logfiles has been configured; 6.2.3.20 Ensure the audit configuration is immutable; 6.2.4.1 Ensure audit log files mode is configured; 6.2.4.2 Ensure audit log files owner is configured; 6.2.4.3 Ensure audit log files group owner is configured; 6.2.4.4 Ensure the audit log file directory mode is configured; 6.2.4.5 Ensure audit configuration files mode is configured; 6.2.4.6 Ensure audit configuration files owner is configured; 6.2.4.7 Ensure audit configuration files group owner is configured; 6.2.4.8 Ensure audit tools mode is configured; 6.2.4.9 Ensure audit tools owner is configured; 6.2.4.10 Ensure audit tools group owner is configured; 7.1.1 Ensure permissions on /etc/passwd are configured; 7.1.2 Ensure permissions on /etc/passwd- are configured; 7.1.3 Ensure permissions on /etc/group are configured; 7.1.4 Ensure permissions on /etc/group- are configured; 7.1.5 Ensure permissions on /etc/shadow are configured; 7.1.6 Ensure permissions on /etc/shadow- are configured; 7.1.7 Ensure permissions on /etc/gshadow are configured; 7.1.8 Ensure permissions on /etc/gshadow- are configured; 7.1.9 Ensure permissions on /etc/shells are configured; 7.1.10 Ensure permissions on /etc/security/opasswd are configured; 7.1.11 Ensure world writable files and directories are secured; 7.1.12 Ensure no files or directories without an owner and a group exist; 7.1.13 Ensure SUID and SGID files are reviewed; 7.2.3 Ensure all groups in /etc/passwd exist in /etc/group; 7.2.4 Ensure shadow group is empty; 7.2.9 Ensure local interactive user home directories are configured; 7.2.10 Ensure local interactive user dot files access is configured", + "automation-scripts": [ + { + "uuid": "6957b05d-453a-5649-a3c4-95fe2a7effca", + "benchmark-rule-id": "2.4.1.8", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n [ ! -e \"/etc/cron.deny\" ] && touch /etc/cron.allow\n chmod u-x,g-wx,o-rwx /etc/cron.allow\n if grep -Pq -- '^\\h*crontab\\:' /etc/group; then\n chown root:crontab /etc/cron.allow\n else\n chown root:root /etc/cron.allow\n fi\n}\n" + }, + { + "uuid": "c276c865-be91-51ae-a436-c3fbd868ba24", + "benchmark-rule-id": "2.4.1.8", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n if [ -e \"/etc/cron.deny\" ]; then\n chmod u-x,g-wx,o-rwx /etc/cron.deny\n if grep -Pq -- '^\\h*crontab\\:' /etc/group; then\n chown root:crontab /etc/cron.deny\n else\n chown root:root /etc/cron.deny\n fi\n fi\n}\n" + }, + { + "uuid": "b026b27a-bb21-57f1-8d38-e09999503e81", + "benchmark-rule-id": "2.4.2.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n grep -Pq -- '^daemon\\b' /etc/group && l_group=\"daemon\" || l_group=\"root\"\n [ ! -e \"/etc/at.allow\" ] && touch /etc/at.allow\n chown root:\"$l_group\" /etc/at.allow\n chmod u-x,g-wx,o-rwx /etc/at.allow\n [ -e \"/etc/at.deny\" ] && chown root:\"$l_group\" /etc/at.deny\n [ -e \"/etc/at.deny\" ] && chmod u-x,g-wx,o-rwx /etc/at.deny\n}\n" + }, + { + "uuid": "bf596455-43f4-50aa-99b2-e123729c982f", + "benchmark-rule-id": "5.1.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n perm_mask='0177' && maxperm=\"$( printf '%o' $(( 0777 & ~$perm_mask)) )\"\n f_sshd_files_chk()\n {\n while IFS=: read -r l_mode l_user l_group; do\n a_out2=()\n [ $(( $l_mode & $perm_mask )) -gt 0 ] && a_out2+=(\" Is mode: \\\"$l_mode\\\"\" \\\n \" should be mode: \\\"$maxperm\\\" or more restrictive\")\n [ \"$l_user\" != \"root\" ] && a_out2+=(\" Is owned by \\\"$l_user\\\" should be owned by \\\"root\\\"\")\n [ \"$l_group\" != \"root\" ] && a_out2+=(\" Is group owned by \\\"$l_user\\\" should be group owned by \\\"root\\\"\")\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\":\" \"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\":\" \" Correct: mode ($l_mode), owner ($l_user)\" \\\n \" and group owner ($l_group) configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\") \n }\n [ -e \"/etc/ssh/sshd_config\" ] && l_file=\"/etc/ssh/sshd_config\" && f_sshd_files_chk\n while IFS= read -r -d $'\\0' l_file; do\n [ -e \"$l_file\" ] && f_sshd_files_chk\n done < <(find /etc/ssh/sshd_config.d -type f -name '*.conf' \\( -perm /077 -o ! -user root -o ! -group root \\) -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "441abfa1-9170-5741-9fbe-f98cc8987d2b", + "benchmark-rule-id": "5.1.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n chmod u-x,og-rwx /etc/ssh/sshd_config\n chown root:root /etc/ssh/sshd_config\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n chmod u-x,og-rwx \"$l_file\"\n chown root:root \"$l_file\"\n fi\n done < <(find /etc/ssh/sshd_config.d -type f -print0 2>/dev/null)\n}\n" + }, + { + "uuid": "fb14b0c4-a0bc-52ea-8670-edc511deffaf", + "benchmark-rule-id": "5.1.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n l_ssh_group_name=\"$(awk -F: '($1 ~ /^(ssh_keys|_?ssh)$/) {print $1}' /etc/group)\"\n f_file_chk()\n {\n while IFS=: read -r l_file_mode l_file_owner l_file_group; do\n a_out2=()\n [ \"$l_file_group\" = \"$l_ssh_group_name\" ] && l_pmask=\"0137\" || l_pmask=\"0177\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n if [ $(( $l_file_mode & $l_pmask )) -gt 0 ]; then\n a_out2+=(\" Mode: \\\"$l_file_mode\\\" should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n fi\n if [ \"$l_file_owner\" != \"root\" ]; then\n a_out2+=(\" Owned by: \\\"$l_file_owner\\\" should be owned by \\\"root\\\"\")\n fi\n if [[ ! \"$l_file_group\" =~ ($l_ssh_group_name|root) ]]; then\n a_out2+=(\" Owned by group \\\"$l_file_group\\\" should be group owned by: \\\"$l_ssh_group_name\\\" or \\\"root\\\"\")\n fi\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\"\" \\\n \" Correct: mode: \\\"$l_file_mode\\\", owner: \\\"$l_file_owner\\\" and group owner: \\\"$l_file_group\\\" configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\")\n }\n while IFS= read -r -d $'\\0' l_file; do \n if ssh-keygen -lf &>/dev/null \"$l_file\"; then \n file \"$l_file\" | grep -Piq -- '\\bopenssh\\h+([^#\\n\\r]+\\h+)?private\\h+key\\b' && f_file_chk\n fi\n done < <(find -L /etc/ssh -xdev -type f -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "1d4c8629-7cee-59d3-b160-f6eb03a44c41", + "benchmark-rule-id": "5.1.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ssh_group_name=\"$(awk -F: '($1 ~ /^(ssh_keys|_?ssh)$/) {print $1}' /etc/group)\"\n f_file_access_fix()\n {\n while IFS=: read -r l_file_mode l_file_owner l_file_group; do\n a_out2=()\n [ \"$l_file_group\" = \"$l_ssh_group_name\" ] && l_pmask=\"0137\" || l_pmask=\"0177\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n if [ $(( $l_file_mode & $l_pmask )) -gt 0 ]; then\n a_out2+=(\" Mode: \\\"$l_file_mode\\\" should be mode: \\\"$l_maxperm\\\" or more restrictive\" \\\n \" updating to mode: \\:$l_maxperm\\\"\")\n if [ \"l_file_group\" = \"$l_ssh_group_name\" ]; then\n chmod u-x,g-wx,o-rwx \"$l_file\"\n else\n chmod u-x,go-rwx \"$l_file\"\n fi\n fi\n if [ \"$l_file_owner\" != \"root\" ]; then\n a_out2+=(\" Owned by: \\\"$l_file_owner\\\" should be owned by \\\"root\\\"\" \\\n \" Changing ownership to \\\"root\\\"\")\n chown root \"$l_file\"\n fi\n if [[ ! \"$l_file_group\" =~ ($l_ssh_group_name|root) ]]; then\n [ -n \"$l_ssh_group_name\" ] && l_new_group=\"$l_ssh_group_name\" || l_new_group=\"root\"\n a_out2+=(\" Owned by group \\\"$l_file_group\\\" should be group owned by: \\\"$l_ssh_group_name\\\" or \\\"root\\\"\" \\\n \" Changing group ownership to \\\"$l_new_group\\\"\")\n chgrp \"$l_new_group\" \"$l_file\"\n fi\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\"\" \"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\"\" \\\n \"Correct: mode: \\\"$l_file_mode\\\", owner: \\\"$l_file_owner\\\", and group owner: \\\"$l_file_group\\\" configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\")\n }\n while IFS= read -r -d $'\\0' l_file; do \n if ssh-keygen -lf &>/dev/null \"$l_file\"; then \n file \"$l_file\" | grep -Piq -- '\\bopenssh\\h+([^#\\n\\r]+\\h+)?private\\h+key\\b' && f_file_access_fix\n fi\n done < <(find -L /etc/ssh -xdev -type f -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le \"0\" ]; then\n printf '%s\\n' \"\" \" - No access changes required\" \"\"\n else\n printf '%s\\n' \"\" \" - Remediation results:\" \"${a_output2[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "8ce33ded-8985-54d9-ba9b-536ef6fa8431", + "benchmark-rule-id": "5.1.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n l_pmask=\"0133\"; l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n f_file_chk()\n {\n while IFS=: read -r l_file_mode l_file_owner l_file_group; do\n a_out2=()\n if [ $(( $l_file_mode & $l_pmask )) -gt 0 ]; then\n a_out2+=(\" Mode: \\\"$l_file_mode\\\" should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n fi\n if [ \"$l_file_owner\" != \"root\" ]; then\n a_out2+=(\" Owned by: \\\"$l_file_owner\\\" should be owned by: \\\"root\\\"\")\n fi\n if [ \"$l_file_group\" != \"root\" ]; then\n a_out2+=(\" Owned by group \\\"$l_file_group\\\" should be group owned by group: \\\"root\\\"\")\n fi\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\"\" \"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\"\" \\\n \" Correct: mode: \\\"$l_file_mode\\\", owner: \\\"$l_file_owner\\\" and group owner: \\\"$l_file_group\\\" configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\")\n }\n while IFS= read -r -d $'\\0' l_file; do \n if ssh-keygen -lf &>/dev/null \"$l_file\"; then \n file \"$l_file\" | grep -Piq -- '\\bopenssh\\h+([^#\\n\\r]+\\h+)?public\\h+key\\b' && f_file_chk\n fi\n done < <(find -L /etc/ssh -xdev -type f -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n [ \"${#a_output[@]}\" -le 0 ] && a_output+=(\" - No openSSH public keys found\")\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "eceeb8e2-8264-50cd-bffb-0163c77b22a6", + "benchmark-rule-id": "5.1.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n l_pmask=\"0133\"; l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n f_file_access_fix()\n {\n while IFS=: read -r l_file_mode l_file_owner l_file_group; do\n a_out2=()\n [ $(( $l_file_mode & $l_pmask )) -gt 0 ] && \\\n a_out2+=(\" Mode: \\\"$l_file_mode\\\" should be mode: \\\"$l_maxperm\\\" or more restrictive\" \\\n \" updating to mode: \\\"$l_maxperm\\\"\") && chmod u-x,go-wx \"$l_file\"\n [ \"$l_file_owner\" != \"root\" ] && \\\n a_out2+=(\" Owned by: \\\"$l_file_owner\\\" should be owned by \\\"root\\\"\" \\\n \" Changing ownership to \\\"root\\\"\") && chown root \"$l_file\"\n [ \"$l_file_group\" != \"root\" ] && \\\n a_out2+=(\" Owned by group \\\"$l_file_group\\\" should be group owned by: \\\"root\\\"\" \\\n \" Changing group ownership to \\\"root\\\"\") && chgrp root \"$l_file\"\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\"\" \"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\"\" \\\n \" Correct: mode: \\\"$l_file_mode\\\", owner: \\\"$l_file_owner\\\", and group owner: \\\"$l_file_group\\\" configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\")\n }\n while IFS= read -r -d $'\\0' l_file; do \n if ssh-keygen -lf &>/dev/null \"$l_file\"; then \n file \"$l_file\" | grep -Piq -- '\\bopenssh\\h+([^#\\n\\r]+\\h+)?public\\h+key\\b' && f_file_access_fix\n fi\n done < <(find -L /etc/ssh -xdev -type f -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le \"0\" ]; then\n printf '%s\\n' \"\" \" - No access changes required\" \"\"\n else\n printf '%s\\n' \" - Remediation results:\" \"${a_output2[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "dec1f83c-c81a-576b-bbec-81c279677b31", + "benchmark-rule-id": "5.4.2.7", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_valid_shells=\"^($(awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n awk -v pat=\"$l_valid_shells\" -F: '($1!~/^(root|halt|sync|shutdown|nfsnobody)$/ && ($3<'\"$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\"' || $3 == 65534) && $(NF) ~ pat) {print \"Service account: \\\"\" $1 \"\\\" has a valid shell: \" $7}' /etc/passwd\n}\n" + }, + { + "uuid": "8f1eef7f-e276-5d44-9144-d460b8be51e9", + "benchmark-rule-id": "5.4.2.7", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n awk -v pat=\"$l_valid_shells\" -F: '($1!~/^(root|halt|sync|shutdown|nfsnobody)$/ && ($3<'\"$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\"' || $3 == 65534) && $(NF) ~ pat) {system (\"usermod -s '\"$(command -v nologin)\"' \" $1)}' /etc/passwd\n}\n" + }, + { + "uuid": "fbe0953f-b55c-5bee-b179-9efbd860c037", + "benchmark-rule-id": "5.4.2.8", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_valid_shells=\"^($(awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n while IFS= read -r l_user; do\n passwd -S \"$l_user\" | awk '$2 !~ /^L/ {print \"Account: \\\"\" $1 \"\\\" does not have a valid login shell and is not locked\"}'\n done < <(awk -v pat=\"$l_valid_shells\" -F: '($1 != \"root\" && $(NF) !~ pat) {print $1}' /etc/passwd)\n}\n" + }, + { + "uuid": "d9e64dda-4cae-5d4f-bcb8-1fbafe724e86", + "benchmark-rule-id": "5.4.2.8", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_valid_shells=\"^($(awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n while IFS= read -r l_user; do\n passwd -S \"$l_user\" | awk '$2 !~ /^L/ {system (\"usermod -L \" $1)}'\n done < <(awk -v pat=\"$l_valid_shells\" -F: '($1 != \"root\" && $(NF) !~ pat) {print $1}' /etc/passwd)\n}\n" + }, + { + "uuid": "b8503450-7e2e-5b04-bf5f-ff4184c6e275", + "benchmark-rule-id": "5.4.3.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{ \n l_output=\"\" l_output2=\"\"\n file_umask_chk()\n {\n if grep -Psiq -- '^\\h*umask\\h+(0?[0-7][2-7]7|u(=[rwx]{0,3}),g=([rx]{0,2}),o=)(\\h*#.*)?$' \"$l_file\"; then\n l_output=\"$l_output\\n - umask is set correctly in \\\"$l_file\\\"\"\n elif grep -Psiq -- '^\\h*umask\\h+(([0-7][0-7][01][0-7]\\b|[0-7][0-7][0-7][0-6]\\b)|([0-7][01][0-7]\\b|[0-7][0-7][0-6]\\b)|(u=[rwx]{1,3},)?(((g=[rx]?[rx]?w[rx]?[rx]?\\b)(,o=[rwx]{1,3})?)|((g=[wrx]{1,3},)?o=[wrx]{1,3}\\b)))' \"$l_file\"; then\n l_output2=\"$l_output2\\n - umask is incorrectly set in \\\"$l_file\\\"\"\n fi\n }\n while IFS= read -r -d $'\\0' l_file; do\n file_umask_chk\n done < <(find /etc/profile.d/ -type f -name '*.sh' -print0)\n [ -z \"$l_output\" ] && l_file=\"/etc/profile\" && file_umask_chk\n [ -z \"$l_output\" ] && l_file=\"/etc/bashrc\" && file_umask_chk\n [ -z \"$l_output\" ] && l_file=\"/etc/bash.bashrc\" && file_umask_chk\n [ -z \"$l_output\" ] && l_file=\"/etc/pam.d/postlogin\"\n if [ -z \"$l_output\" ]; then\n if grep -Psiq -- '^\\h*session\\h+[^#\\n\\r]+\\h+pam_umask\\.so\\h+([^#\\n\\r]+\\h+)?umask=(0?[0-7][2-7]7)\\b' \"$l_file\"; then\n l_output1=\"$l_output1\\n - umask is set correctly in \\\"$l_file\\\"\"\n elif grep -Psiq '^\\h*session\\h+[^#\\n\\r]+\\h+pam_umask\\.so\\h+([^#\\n\\r]+\\h+)?umask=(([0-7][0-7][01][0-7]\\b|[0-7][0-7][0-7][0-6]\\b)|([0-7][01][0-7]\\b))' \"$l_file\"; then\n l_output2=\"$l_output2\\n - umask is incorrectly set in \\\"$l_file\\\"\"\n fi\n fi\n [ -z \"$l_output\" ] && l_file=\"/etc/login.defs\" && file_umask_chk\n [ -z \"$l_output\" ] && l_file=\"/etc/default/login\" && file_umask_chk\n [[ -z \"$l_output\" && -z \"$l_output2\" ]] && l_output2=\"$l_output2\\n - umask is not set\"\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\"\n [ -n \"$l_output\" ] && echo -e \"\\n- * Correctly configured * :\\n$l_output\\n\"\n fi\n}\n" + }, + { + "uuid": "2f05b142-538e-5275-ac38-22eac2024e27", + "benchmark-rule-id": "5.4.3.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" l_out=\"\"\n file_umask_chk()\n {\n if grep -Psiq -- '^\\h*umask\\h+(0?[0-7][2-7]7|u(=[rwx]{0,3}),g=([rx]{0,2}),o=)(\\h*#.*)?$' \"$l_file\"; then\n l_out=\"$l_out\\n - umask is set correctly in \\\"$l_file\\\"\"\n elif grep -Psiq -- '^\\h*umask\\h+(([0-7][0-7][01][0-7]\\b|[0-7][0-7][0-7][0-6]\\b)|([0-7][01][0-7]\\b|[0-7][0-7][0-6]\\b)|(u=[rwx]{1,3},)?(((g=[rx]?[rx]?w[rx]?[rx]?\\b)(,o=[rwx]{1,3})?)|((g=[wrx]{1,3},)?o=[wrx]{1,3}\\b)))' \"$l_file\"; then\n l_output2=\"$l_output2\\n - \\\"$l_file\\\"\"\n fi\n }\n while IFS= read -r -d $'\\0' l_file; do\n file_umask_chk\n done < <(find /etc/profile.d/ -type f -name '*.sh' -print0)\n [ -n \"$l_out\" ] && l_output=\"$l_out\"\n l_file=\"/etc/profile\" && file_umask_chk\n l_file=\"/etc/bashrc\" && file_umask_chk\n l_file=\"/etc/bash.bashrc\" && file_umask_chk\n l_file=\"/etc/pam.d/postlogin\"\n if grep -Psiq '^\\h*session\\h+[^#\\n\\r]+\\h+pam_umask\\.so\\h+([^#\\n\\r]+\\h+)?umask=(([0-7][0-7][01][0-7]\\b|[0-7][0-7][0-7][0-6]\\b)|([0-7][01][0-7]\\b))' \"$l_file\"; then\n l_output2=\"$l_output2\\n - \\\"$l_file\\\"\"\n fi\n l_file=\"/etc/login.defs\" && file_umask_chk\n l_file=\"/etc/default/login\" && file_umask_chk\n if [ -z \"$l_output2\" ]; then\n echo -e \" - No files contain a UMASK that is not restrictive enough\\n No UMASK updates required to existing files\"\n else\n echo -e \"\\n - UMASK is not restrictive enough in the following file(s):$l_output2\\n\\n- Remediation Procedure:\\n - Update these files and comment out the UMASK line\\n or update umask to be \\\"0027\\\" or more restrictive\"\n fi\n if [ -n \"$l_output\" ]; then\n echo -e \"$l_output\"\n else\n echo -e \" - Configure UMASK in a file in the \\\"/etc/profile.d/\\\" directory ending in \\\".sh\\\"\\n\\n Example Command (Hash to represent being run at a root prompt):\\n\\n# printf '%s\\\\\\n' \\\"umask 027\\\" > /etc/profile.d/50-systemwide_umask.sh\\n\"\n fi\n}\n" + }, + { + "uuid": "45b529fd-699d-5d9c-bb65-fece14c52cc1", + "benchmark-rule-id": "6.1.1.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=()\n l_systemd_config_file=\"/etc/tmpfiles.d/systemd.conf\" l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\"\n f_file_chk()\n {\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n if [ $(( $l_mode & $l_perm_mask )) -le 0 ] || [[ \"$l_type\" = \"Directory\" && \"$l_mode\" =~ 275(0|5) ]]; then\n a_out+=(\" - $l_type \\\"$l_logfile\\\" access is:\" \\\n \" mode: \\\"$l_mode\\\", owned by: \\\"$l_user\\\", and group owned by: \\\"$l_group\\\"\")\n else\n a_out2+=(\" - $l_type \\\"$l_logfile\\\" access is:\" \\\n \" mode: \\\"$l_mode\\\", owned by: \\\"$l_user\\\", and group owned by: \\\"$l_group\\\"\" \\\n \" should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n fi\n }\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\" a_out=() a_out2=()\n l_logfile_perms_line=\"$(awk '($1~/^(f|d)$/ && $2~/\\/\\S+/ && $3~/[0-9]{3,}/){print $2 \":\" $3 \":\" $4 \":\" $5}' \"$l_file\")\"\n while IFS=: read -r l_logfile l_mode l_user l_group; do\n if [ -d \"$l_logfile\" ]; then\n l_perm_mask=\"0027\" l_type=\"Directory\"\n grep -Psq '^(\\/run|\\/var\\/lib\\/systemd)\\b' <<< \"$l_logfile\" && l_perm_mask=\"0022\"\n else\n l_perm_mask=\"0137\" l_type=\"File\"\n fi\n grep -Psq '^(\\/run|\\/var\\/lib\\/systemd)\\b' <<< \"$l_logfile\" && l_perm_mask=\"0022\"\n f_file_chk\n done <<< \"$l_logfile_perms_line\"\n [ \"${#a_out[@]}\" -gt \"0\" ] && a_output+=(\" - File: \\\"$l_file\\\" sets:\" \"${a_out[@]}\")\n [ \"${#a_out2[@]}\" -gt \"0\" ] && a_output2+=(\" - File: \\\"$l_file\\\" sets:\" \"${a_out2[@]}\")\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** REVIEW **\" \\\n \" - Review file access to ensure they are set IAW site policy:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi \n}\n" + }, + { + "uuid": "2d5d3a3f-5b45-56b6-80fe-4988bc10e922", + "benchmark-rule-id": "6.1.3.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\"\n l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\") l_parameter_name='\\$FileCreateMode'\n f_parameter_chk()\n {\n l_perm_mask=\"0137\"; l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n l_mode=\"$(awk '{print $2}' <<< \"$l_used_parameter_setting\" | xargs)\"\n if [ $(( $l_mode & $l_perm_mask )) -gt 0 ]; then\n a_output2+=(\" - Parameter: \\\"${l_parameter_name//\\\\/}\\\" is incorrectly set to mode: \\\"$l_file_mode\\\"\" \\\n \" in the file: \\\"$l_file\\\"\" \" Should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n else\n a_output+=(\" - Parameter: \\\"${l_parameter_name//\\\\/}\\\" is correctly set to mode: \\\"$l_file_mode\\\"\" \\\n \" in the file: \\\"$l_file\\\"\" \" Should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n fi\n }\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[*]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n\n if [ -n \"$l_used_parameter_setting\" ]; then\n f_parameter_chk\n else\n a_output2+=(\" - Parameter: \\\"${l_parameter_name//\\\\/}\\\" is not set in a configuration file\" \\\n \" *** Note: \\\"${l_parameter_name//\\\\/}\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "9270f0af-54ce-57b4-a46a-a7d85c7c65f3", + "benchmark-rule-id": "6.1.3.4", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n [ ! -d \"/etc/rsyslog.d/\" ] && mkdir /etc/rsyslog.d/\n printf '%s\\n' \"\" \"\\$FileCreateMode 0640\" >> /etc/rsyslog.d/60-rsyslog.conf\n}\n" + }, + { + "uuid": "293fdf33-ad46-5515-8a1c-86e02e6c256b", + "benchmark-rule-id": "6.1.4.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n f_file_test_chk()\n {\n a_out2=() \n maxperm=\"$( printf '%o' $(( 0777 & ~$perm_mask)) )\"\n [ $(( $l_mode & $perm_mask )) -gt 0 ] && \\\n a_out2+=(\" o Mode: \\\"$l_mode\\\" should be \\\"$maxperm\\\" or more restrictive\")\n [[ ! \"$l_user\" =~ $l_auser ]] && \\\n a_out2+=(\" o Owned by: \\\"$l_user\\\" and should be owned by \\\"${l_auser//|/ or }\\\"\")\n [[ ! \"$l_group\" =~ $l_agroup ]] && \\\n a_out2+=(\" o Group owned by: \\\"$l_group\\\" and should be group owned by \\\"${l_agroup//|/ or }\\\"\")\n [ \"${#a_out2[@]}\" -gt 0 ] && a_output2+=(\" - File: \\\"$l_fname\\\" is:\" \"${a_out2[@]}\")\n }\n while IFS= read -r -d $'\\0' l_file; do\n while IFS=: read -r l_fname l_mode l_user l_group; do\n if grep -Pq -- '\\/(apt)\\h*$' <<< \"$(dirname \"$l_fname\")\"; then\n perm_mask='0133' l_auser=\"root\" l_agroup=\"(root|adm)\"; f_file_test_chk\n else\n case \"$(basename \"$l_fname\")\" in\n lastlog | lastlog.* | wtmp | wtmp.* | wtmp-* | btmp | btmp.* | btmp-* | README)\n perm_mask='0113' l_auser=\"root\" l_agroup=\"(root|utmp)\"\n f_file_test_chk ;;\n cloud-init.log* | localmessages* | waagent.log*)\n perm_mask='0133' l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n file_test_chk ;;\n secure{,*.*,.*,-*} | auth.log | syslog | messages)\n perm_mask='0137' l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n f_file_test_chk ;;\n SSSD | sssd)\n perm_mask='0117' l_auser=\"(root|SSSD)\" l_agroup=\"(root|SSSD)\"\n f_file_test_chk ;;\n gdm | gdm3)\n perm_mask='0117' l_auser=\"root\" l_agroup=\"(root|gdm|gdm3)\"\n f_file_test_chk ;;\n *.journal | *.journal~)\n perm_mask='0137' l_auser=\"root\" l_agroup=\"(root|systemd-journal)\"\n f_file_test_chk ;;\n *)\n perm_mask='0137' l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n if [ \"$l_user\" = \"root\" ] || ! grep -Pq -- \"^\\h*$(awk -F: '$1==\"'\"$l_user\"'\" {print $7}' /etc/passwd)\\b\" /etc/shells; then\n ! grep -Pq -- \"$l_auser\" <<< \"$l_user\" && l_auser=\"(root|syslog|$l_user)\"\n ! grep -Pq -- \"$l_agroup\" <<< \"$l_group\" && l_agroup=\"(root|adm|$l_group)\"\n fi\n f_file_test_chk ;;\n esac\n fi\n done < <(stat -Lc '%n:%#a:%U:%G' \"$l_file\")\n done < <(find -L /var/log -type f \\( -perm /0137 -o ! -user root -o ! -group root \\) -print0)\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n a_output+=(\" - All files in \\\"/var/log/\\\" have appropriate permissions and ownership\")\n printf '\\n%s' \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '\\n%s' \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "6f81ad05-00a6-58f5-b4e5-f38f00fa761d", + "benchmark-rule-id": "6.1.4.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=()\n f_file_test_fix()\n {\n a_out2=()\n maxperm=\"$( printf '%o' $(( 0777 & ~$perm_mask)) )\"\n if [ $(( $l_mode & $perm_mask )) -gt 0 ]; then\n a_out2+=(\" o Mode: \\\"$l_mode\\\" should be \\\"$maxperm\\\" or more restrictive\" \" x Removing excess permissions\")\n chmod \"$l_rperms\" \"$l_fname\"\n fi\n if [[ ! \"$l_user\" =~ $l_auser ]]; then\n a_out2+=(\" o Owned by: \\\"$l_user\\\" and should be owned by \\\"${l_auser//|/ or }\\\"\" \" x Changing ownership to: \\\"$l_fix_account\\\"\")\n chown \"$l_fix_account\" \"$l_fname\"\n fi\n if [[ ! \"$l_group\" =~ $l_agroup ]]; then\n a_out2+=(\" o Group owned by: \\\"$l_group\\\" and should be group owned by \\\"${l_agroup//|/ or }\\\"\" \" x Changing group ownership to: \\\"$l_fix_account\\\"\")\n chgrp \"$l_fix_account\" \"$l_fname\"\n fi\n [ \"${#a_out2[@]}\" -gt 0 ] && a_output2+=(\" - File: \\\"$l_fname\\\" is:\" \"${a_out2[@]}\")\n }\n l_fix_account='root'\n while IFS= read -r -d $'\\0' l_file; do\n while IFS=: read -r l_fname l_mode l_user l_group; do\n if grep -Pq -- '\\/(apt)\\h*$' <<< \"$(dirname \"$l_fname\")\"; then\n perm_mask='0133' l_rperms=\"u-x,go-wx\" l_auser=\"root\" l_agroup=\"(root|adm)\"; f_file_test_fix\n else\n case \"$(basename \"$l_fname\")\" in\n lastlog | lastlog.* | wtmp | wtmp.* | wtmp-* | btmp | btmp.* | btmp-* | README)\n perm_mask='0113' l_rperms=\"ug-x,o-wx\" l_auser=\"root\" l_agroup=\"(root|utmp)\"\n f_file_test_fix ;;\n cloud-init.log* | localmessages* | waagent.log*)\n perm_mask='0133' l_rperms=\"u-x,go-wx\" l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n file_test_fix ;;\n secure | auth.log | syslog | messages)\n perm_mask='0137' l_rperms=\"u-x,g-wx,o-rwx\" l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n f_file_test_fix ;;\n SSSD | sssd)\n perm_mask='0117' l_rperms=\"ug-x,o-rwx\" l_auser=\"(root|SSSD)\" l_agroup=\"(root|SSSD)\"\n f_file_test_fix ;;\n gdm | gdm3)\n perm_mask='0117' l_rperms=\"ug-x,o-rwx\" l_auser=\"root\" l_agroup=\"(root|gdm|gdm3)\"\n f_file_test_fix ;;\n *.journal | *.journal~)\n perm_mask='0137' l_rperms=\"u-x,g-wx,o-rwx\" l_auser=\"root\" l_agroup=\"(root|systemd-journal)\" \n f_file_test_fix ;;\n *)\n perm_mask='0137' l_rperms=\"u-x,g-wx,o-rwx\" l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n if [ \"$l_user\" = \"root\" ] || ! grep -Pq -- \"^\\h*$(awk -F: '$1==\"'\"$l_user\"'\" {print $7}' /etc/passwd)\\b\" /etc/shells; then\n ! grep -Pq -- \"$l_auser\" <<< \"$l_user\" && l_auser=\"(root|syslog|$l_user)\"\n ! grep -Pq -- \"$l_agroup\" <<< \"$l_group\" && l_agroup=\"(root|adm|$l_group)\"\n fi\n f_file_test_fix ;;\n esac\n fi\n done < <(stat -Lc '%n:%#a:%U:%G' \"$l_file\")\n done < <(find -L /var/log -type f \\( -perm /0137 -o ! -user root -o ! -group root \\) -print0)\n if [ \"${#a_output2[@]}\" -le 0 ]; then # If all files passed, then we report no changes\n a_output+=(\" - All files in \\\"/var/log/\\\" have appropriate permissions and ownership\")\n printf '\\n%s' \"- All files in \\\"/var/log/\\\" have appropriate permissions and ownership\" \" o No changes required\" \"\"\n else\n printf '\\n%s' \"${a_output2[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "f15cc444-6ac2-5aa7-ab1f-4290c19836c2", + "benchmark-rule-id": "6.2.4.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_perm_mask=\"0137\"\n if [ -e \"/etc/audit/auditd.conf\" ]; then\n l_audit_log_directory=\"$(dirname \"$(awk -F= '/^\\s*log_file\\s*/{print $2}' /etc/audit/auditd.conf | xargs)\")\"\n if [ -d \"$l_audit_log_directory\" ]; then\n l_maxperm=\"$(printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n a_files=()\n while IFS= read -r -d $'\\0' l_file; do\n [ -e \"$l_file\" ] && a_files+=(\"$l_file\")\n done < <(find \"$l_audit_log_directory\" -maxdepth 1 -type f -perm /\"$l_perm_mask\" -print0)\n\t\t if (( \"${#a_files[@]}\" > 0 )); then\n for l_file in \"${a_files[@]}\"; do\n l_file_mode=\"$(stat -Lc '%#a' \"$l_file\")\"\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - File: \\\"$l_file\\\" is mode: \\\"$l_file_mode\\\"\\n (should be mode: \\\"$l_maxperm\\\" or more restrictive)\\n\"\n done\n else\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - All files in \\\"$l_audit_log_directory\\\" are mode: \\\"$l_maxperm\\\" or more restrictive\"\n fi\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Log file directory not set in \\\"/etc/audit/auditd.conf\\\" please set log file directory\"\n fi\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - File: \\\"/etc/audit/auditd.conf\\\" not found.\\n - ** Verify auditd is installed **\"\n fi\n}\n" + }, + { + "uuid": "2db1a94b-ff7f-557a-8957-78281b5b00b2", + "benchmark-rule-id": "6.2.4.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n if [ -e \"/etc/audit/auditd.conf\" ]; then\n l_audit_log_directory=\"$(dirname \"$(awk -F= '/^\\s*log_file\\s*/{print $2}' /etc/audit/auditd.conf | xargs)\")\"\n if [ -d \"$l_audit_log_directory\" ]; then\n while IFS= read -r -d $'\\0' l_file; do\n l_output2=\"$l_output2\\n - File: \\\"$l_file\\\" is owned by user: \\\"$(stat -Lc '%U' \"$l_file\")\\\"\\n (should be owned by user: \\\"root\\\")\\n\"\n done < <(find \"$l_audit_log_directory\" -maxdepth 1 -type f ! -user root -print0)\n else\n l_output2=\"$l_output2\\n - Log file directory not set in \\\"/etc/audit/auditd.conf\\\" please set log file directory\"\n fi\n else\n l_output2=\"$l_output2\\n - File: \\\"/etc/audit/auditd.conf\\\" not found.\\n - ** Verify auditd is installed **\"\n fi\n if [ -z \"$l_output2\" ]; then\n l_output=\"$l_output\\n - All files in \\\"$l_audit_log_directory\\\" are owned by user: \\\"root\\\"\\n\"\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :$l_output\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :$l_output2\\n\"\n fi\n}\n" + }, + { + "uuid": "00323dbe-2507-5177-93f9-294bf6cf95a1", + "benchmark-rule-id": "6.2.4.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n if [ -e /etc/audit/auditd.conf ]; then\n l_fpath=\"$(dirname \"$(awk -F \"=\" '/^\\s*log_file/ {print $2}' /etc/audit/auditd.conf | xargs)\")\"\n find -L \"$l_fpath\" -not -path \"$l_fpath\"/lost+found -type f \\( ! -group root -a ! -group adm \\) -exec ls -l {} +\n fi\n}\n" + }, + { + "uuid": "1f3fb8dc-1f54-5db6-9a8b-83a8353fde72", + "benchmark-rule-id": "6.2.4.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_perm_mask=\"0027\"\n if [ -e \"/etc/audit/auditd.conf\" ]; then\n l_audit_log_directory=\"$(dirname \"$(awk -F= '/^\\s*log_file\\s*/{print $2}' /etc/audit/auditd.conf | xargs)\")\"\n if [ -d \"$l_audit_log_directory\" ]; then\n l_maxperm=\"$(printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n l_directory_mode=\"$(stat -Lc '%#a' \"$l_audit_log_directory\")\"\n if [ $(( $l_directory_mode & $l_perm_mask )) -gt 0 ]; then\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Directory: \\\"$l_audit_log_directory\\\" is mode: \\\"$l_directory_mode\\\"\\n (should be mode: \\\"$l_maxperm\\\" or more restrictive)\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - Directory: \\\"$l_audit_log_directory\\\" is mode: \\\"$l_directory_mode\\\"\\n (should be mode: \\\"$l_maxperm\\\" or more restrictive)\\n\"\n fi \n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Log file directory not set in \\\"/etc/audit/auditd.conf\\\" please set log file directory\"\n fi\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - File: \\\"/etc/audit/auditd.conf\\\" not found\\n - ** Verify auditd is installed **\"\n fi\n}\n" + }, + { + "uuid": "6edeec05-147c-5729-9101-2b692d35bda5", + "benchmark-rule-id": "6.2.4.5", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" l_perm_mask=\"0137\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n while IFS= read -r -d $'\\0' l_fname; do\n l_mode=$(stat -Lc '%#a' \"$l_fname\")\n if [ $(( \"$l_mode\" & \"$l_perm_mask\" )) -gt 0 ]; then\n l_output2=\"$l_output2\\n - file: \\\"$l_fname\\\" is mode: \\\"$l_mode\\\" (should be mode: \\\"$l_maxperm\\\" or more restrictive)\"\n fi\n done < <(find /etc/audit/ -type f \\( -name \"*.conf\" -o -name '*.rules' \\) -print0)\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - All audit configuration files are mode: \\\"$l_maxperm\\\" or more restrictive\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n$l_output2\"\n fi\n}\n" + }, + { + "uuid": "60ab3f97-aac8-5d1c-9be0-8869d9498044", + "benchmark-rule-id": "6.2.4.8", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" l_perm_mask=\"0022\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n a_audit_tools=(\"/sbin/auditctl\" \"/sbin/aureport\" \"/sbin/ausearch\" \"/sbin/autrace\" \"/sbin/auditd\" \"/sbin/augenrules\")\n for l_audit_tool in \"${a_audit_tools[@]}\"; do\n l_mode=\"$(stat -Lc '%#a' \"$l_audit_tool\")\"\n if [ $(( \"$l_mode\" & \"$l_perm_mask\" )) -gt 0 ]; then\n l_output2=\"$l_output2\\n - Audit tool \\\"$l_audit_tool\\\" is mode: \\\"$l_mode\\\" and should be mode: \\\"$l_maxperm\\\" or more restrictive\"\n else\n l_output=\"$l_output\\n - Audit tool \\\"$l_audit_tool\\\" is correctly configured to mode: \\\"$l_mode\\\"\"\n fi\n done\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :$l_output\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :$l_output2\\n\"\n [ -n \"$l_output\" ] && echo -e \"\\n - * Correctly configured * :\\n$l_output\\n\"\n fi\n unset a_audit_tools\n}\n" + }, + { + "uuid": "2e5aab65-8394-5be3-b844-85541edb11b5", + "benchmark-rule-id": "7.1.11", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n l_smask='01000'\n a_file=(); a_dir=() # Initialize arrays\n a_path=(! -path \"/run/user/*\" -a ! -path \"/proc/*\" -a ! -path \"*/containerd/*\" -a ! -path \"*/kubelet/pods/*\" -a ! -path \"*/kubelet/plugins/*\" -a ! -path \"/sys/*\" -a ! -path \"/snap/*\")\n while IFS= read -r l_mount; do\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n [ -f \"$l_file\" ] && a_file+=(\"$l_file\") # Add WR files\n if [ -d \"$l_file\" ]; then # Add directories w/o sticky bit\n l_mode=\"$(stat -Lc '%#a' \"$l_file\")\"\n [ ! $(( $l_mode & $l_smask )) -gt 0 ] && a_dir+=(\"$l_file\")\n fi\n fi\n done < <(find \"$l_mount\" -xdev \\( \"${a_path[@]}\" \\) \\( -type f -o -type d \\) -perm -0002 -print0 2> /dev/null)\n done < <(findmnt -Dkerno fstype,target | awk '($1 !~ /^\\s*(nfs|proc|smb|vfat|iso9660|efivarfs|selinuxfs)/ && $2 !~ /^(\\/run\\/user\\/|\\/tmp|\\/var\\/tmp)/){print $2}')\n if ! (( ${#a_file[@]} > 0 )); then\n l_output=\"$l_output\\n - No world writable files exist on the local filesystem.\"\n else\n l_output2=\"$l_output2\\n - There are \\\"$(printf '%s' \"${#a_file[@]}\")\\\" World writable files on the system.\\n - The following is a list of World writable files:\\n$(printf '%s\\n' \"${a_file[@]}\")\\n - end of list\\n\"\n fi\n if ! (( ${#a_dir[@]} > 0 )); then\n l_output=\"$l_output\\n - Sticky bit is set on world writable directories on the local filesystem.\"\n else\n l_output2=\"$l_output2\\n - There are \\\"$(printf '%s' \"${#a_dir[@]}\")\\\" World writable directories without the sticky bit on the system.\\n - The following is a list of World writable directories without the sticky bit:\\n$(printf '%s\\n' \"${a_dir[@]}\")\\n - end of list\\n\"\n fi\n unset a_path; unset a_arr; unset a_file; unset a_dir # Remove arrays\n # If l_output2 is empty, we pass\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\"\n [ -n \"$l_output\" ] && echo -e \"- * Correctly configured * :\\n$l_output\\n\"\n fi\n}\n" + }, + { + "uuid": "05fc9b7c-4dc8-5ae8-a646-c81ab11c4f14", + "benchmark-rule-id": "7.1.11", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_smask='01000'\n a_file=(); a_dir=() # Initialize arrays\n a_path=(! -path \"/run/user/*\" -a ! -path \"/proc/*\" -a ! -path \"*/containerd/*\" -a ! -path \"*/kubelet/pods/*\" -a ! -path \"*/kubelet/plugins/*\" -a ! -path \"/sys/*\" -a ! -path \"/snap/*\")\n while IFS= read -r l_mount; do\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n l_mode=\"$(stat -Lc '%#a' \"$l_file\")\"\n if [ -f \"$l_file\" ]; then # Remove excess permissions from WW files\n echo -e \" - File: \\\"$l_file\\\" is mode: \\\"$l_mode\\\"\\n - removing write permission on \\\"$l_file\\\" from \\\"other\\\"\"\n chmod o-w \"$l_file\"\n fi\n if [ -d \"$l_file\" ]; then # Add sticky bit\n if [ ! $(( $l_mode & $l_smask )) -gt 0 ]; then\n echo -e \" - Directory: \\\"$l_file\\\" is mode: \\\"$l_mode\\\" and doesn't have the sticky bit set\\n - Adding the sticky bit\"\n chmod a+t \"$l_file\"\n fi\n fi\n fi\n done < <(find \"$l_mount\" -xdev \\( \"${a_path[@]}\" \\) \\( -type f -o -type d \\) -perm -0002 -print0 2> /dev/null)\n done < <(findmnt -Dkerno fstype,target | awk '($1 !~ /^\\s*(nfs|proc|smb|vfat|iso9660|efivarfs|selinuxfs)/ && $2 !~ /^(\\/run\\/user\\/|\\/tmp|\\/var\\/tmp)/){print $2}') \n}\n" + }, + { + "uuid": "c5a09c8c-214a-5862-9d64-83c0f69dd3d9", + "benchmark-rule-id": "7.1.12", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n a_nouser=(); a_nogroup=() # Initialize arrays\n a_path=(! -path \"/run/user/*\" -a ! -path \"/proc/*\" -a ! -path \"*/containerd/*\" -a ! -path \"*/kubelet/pods/*\" -a ! -path \"*/kubelet/plugins/*\" -a ! -path \"/sys/fs/cgroup/memory/*\" -a ! -path \"/var/*/private/*\")\n while IFS= read -r l_mount; do\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n while IFS=: read -r l_user l_group; do\n [ \"$l_user\" = \"UNKNOWN\" ] && a_nouser+=(\"$l_file\")\n [ \"$l_group\" = \"UNKNOWN\" ] && a_nogroup+=(\"$l_file\")\n done < <(stat -Lc '%U:%G' \"$l_file\")\n fi\n done < <(find \"$l_mount\" -xdev \\( \"${a_path[@]}\" \\) \\( -type f -o -type d \\) \\( -nouser -o -nogroup \\) -print0 2> /dev/null)\n done < <(findmnt -Dkerno fstype,target | awk '($1 !~ /^\\s*(nfs|proc|smb|vfat|iso9660|efivarfs|selinuxfs)/ && $2 !~ /^\\/run\\/user\\//){print $2}')\n if ! (( ${#a_nouser[@]} > 0 )); then\n l_output=\"$l_output\\n - No files or directories without a owner exist on the local filesystem.\"\n else\n l_output2=\"$l_output2\\n - There are \\\"$(printf '%s' \"${#a_nouser[@]}\")\\\" unowned files or directories on the system.\\n - The following is a list of unowned files and/or directories:\\n$(printf '%s\\n' \"${a_nouser[@]}\")\\n - end of list\"\n fi\n if ! (( ${#a_nogroup[@]} > 0 )); then\n l_output=\"$l_output\\n - No files or directories without a group exist on the local filesystem.\"\n else\n l_output2=\"$l_output2\\n - There are \\\"$(printf '%s' \"${#a_nogroup[@]}\")\\\" ungrouped files or directories on the system.\\n - The following is a list of ungrouped files and/or directories:\\n$(printf '%s\\n' \"${a_nogroup[@]}\")\\n - end of list\"\n fi \n unset a_path; unset a_arr ; unset a_nouser; unset a_nogroup # Remove arrays\n if [ -z \"$l_output2\" ]; then # If l_output2 is empty, we pass\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\"\n [ -n \"$l_output\" ] && echo -e \"\\n- * Correctly configured * :\\n$l_output\\n\"\n fi\n}\n" + }, + { + "uuid": "71e60a19-516e-57d5-8df1-dc2064e15cac", + "benchmark-rule-id": "7.1.13", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n a_suid=(); a_sgid=() # initialize arrays\n while IFS= read -r l_mount; do\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n l_mode=\"$(stat -Lc '%#a' \"$l_file\")\"\n [ $(( $l_mode & 04000 )) -gt 0 ] && a_suid+=(\"$l_file\")\n [ $(( $l_mode & 02000 )) -gt 0 ] && a_sgid+=(\"$l_file\")\n fi\n done < <(find \"$l_mount\" -xdev -type f \\( -perm -2000 -o -perm -4000 \\) -print0 2>/dev/null)\n done < <(findmnt -Dkerno fstype,target,options | awk '($1 !~ /^\\s*(nfs|proc|smb|vfat|iso9660|efivarfs|selinuxfs)/ && $2 !~ /^\\/run\\/user\\// && $3 !~/noexec/ && $3 !~/nosuid/) {print $2}')\n if ! (( ${#a_suid[@]} > 0 )); then\n l_output=\"$l_output\\n - No executable SUID files exist on the system\"\n else\n l_output2=\"$l_output2\\n - List of \\\"$(printf '%s' \"${#a_suid[@]}\")\\\" SUID executable files:\\n$(printf '%s\\n' \"${a_suid[@]}\")\\n - end of list -\\n\"\n fi\n if ! (( ${#a_sgid[@]} > 0 )); then\n l_output=\"$l_output\\n - No SGID files exist on the system\"\n else\n l_output2=\"$l_output2\\n - List of \\\"$(printf '%s' \"${#a_sgid[@]}\")\\\" SGID executable files:\\n$(printf '%s\\n' \"${a_sgid[@]}\")\\n - end of list -\\n\"\n fi\n [ -n \"$l_output2\" ] && l_output2=\"$l_output2\\n- Review the preceding list(s) of SUID and/or SGID files to\\n- ensure that no rogue programs have been introduced onto the system.\\n\" \n unset a_arr; unset a_suid; unset a_sgid # Remove arrays\n # If l_output2 is empty, Nothing to report\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n$l_output2\\n\"\n [ -n \"$l_output\" ] && echo -e \"$l_output\\n\"\n fi\n}\n" + }, + { + "uuid": "48fdb5bc-8aaa-5796-a9d0-0029b9599816", + "benchmark-rule-id": "7.2.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_passwd_group_gid=(\"$(awk -F: '{print $4}' /etc/passwd | sort -u)\")\n a_group_gid=(\"$(awk -F: '{print $3}' /etc/group | sort -u)\")\n a_passwd_group_diff=(\"$(printf '%s\\n' \"${a_group_gid[@]}\" \"${a_passwd_group_gid[@]}\" | sort | uniq -u)\")\n while IFS= read -r l_gid; do\n awk -F: '($4 == '\"$l_gid\"') {print \" - User: \\\"\" $1 \"\\\" has GID: \\\"\" $4 \"\\\" which does not exist in /etc/group\" }' /etc/passwd\n done < <(printf '%s\\n' \"${a_passwd_group_gid[@]}\" \"${a_passwd_group_diff[@]}\" | sort | uniq -D | uniq)\n unset a_passwd_group_gid; unset a_group_gid; unset a_passwd_group_diff\n}\n" + }, + { + "uuid": "e15fe889-6e5e-5e8e-a964-7d67a76f8218", + "benchmark-rule-id": "7.2.9", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" l_heout2=\"\" l_hoout2=\"\" l_haout2=\"\"\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n unset a_uarr && a_uarr=() # Clear and initialize array\n while read -r l_epu l_eph; do # Populate array with users and user home location\n a_uarr+=(\"$l_epu $l_eph\")\n done <<< \"$(awk -v pat=\"$l_valid_shells\" -F: '$(NF) ~ pat { print $1 \" \" $(NF-1) }' /etc/passwd)\"\n l_asize=\"${#a_uarr[@]}\" # Here if we want to look at number of users before proceeding \n [ \"$l_asize \" -gt \"10000\" ] && echo -e \"\\n ** INFO **\\n - \\\"$l_asize\\\" Local interactive users found on the system\\n - This may be a long running check\\n\"\n while read -r l_user l_home; do\n if [ -d \"$l_home\" ]; then\n l_mask='0027'\n l_max=\"$( printf '%o' $(( 0777 & ~$l_mask)) )\"\n while read -r l_own l_mode; do\n [ \"$l_user\" != \"$l_own\" ] && l_hoout2=\"$l_hoout2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" is owned by: \\\"$l_own\\\"\"\n if [ $(( $l_mode & $l_mask )) -gt 0 ]; then\n l_haout2=\"$l_haout2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" is mode: \\\"$l_mode\\\" should be mode: \\\"$l_max\\\" or more restrictive\"\n fi\n done <<< \"$(stat -Lc '%U %#a' \"$l_home\")\"\n else\n l_heout2=\"$l_heout2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" Doesn't exist\"\n fi\n done <<< \"$(printf '%s\\n' \"${a_uarr[@]}\")\"\n [ -z \"$l_heout2\" ] && l_output=\"$l_output\\n - home directories exist\" || l_output2=\"$l_output2$l_heout2\"\n [ -z \"$l_hoout2\" ] && l_output=\"$l_output\\n - own their home directory\" || l_output2=\"$l_output2$l_hoout2\"\n [ -z \"$l_haout2\" ] && l_output=\"$l_output\\n - home directories are mode: \\\"$l_max\\\" or more restrictive\" || l_output2=\"$l_output2$l_haout2\"\n [ -n \"$l_output\" ] && l_output=\" - All local interactive users:$l_output\"\n if [ -z \"$l_output2\" ]; then # If l_output2 is empty, we pass\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :\\n$l_output\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\"\n [ -n \"$l_output\" ] && echo -e \"\\n- * Correctly configured * :\\n$l_output\"\n fi\n}\n" + }, + { + "uuid": "1c09c1ac-45ae-5925-98fe-517d955d5991", + "benchmark-rule-id": "7.2.9", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_output2=\"\"\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n unset a_uarr && a_uarr=() # Clear and initialize array\n while read -r l_epu l_eph; do # Populate array with users and user home location\n a_uarr+=(\"$l_epu $l_eph\")\n done <<< \"$(awk -v pat=\"$l_valid_shells\" -F: '$(NF) ~ pat { print $1 \" \" $(NF-1) }' /etc/passwd)\"\n l_asize=\"${#a_uarr[@]}\" # Here if we want to look at number of users before proceeding \n [ \"$l_asize \" -gt \"10000\" ] && echo -e \"\\n ** INFO **\\n - \\\"$l_asize\\\" Local interactive users found on the system\\n - This may be a long running process\\n\"\n while read -r l_user l_home; do\n if [ -d \"$l_home\" ]; then\n l_mask='0027'\n l_max=\"$( printf '%o' $(( 0777 & ~$l_mask)) )\"\n while read -r l_own l_mode; do\n if [ \"$l_user\" != \"$l_own\" ]; then\n l_output2=\"$l_output2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" is owned by: \\\"$l_own\\\"\\n - changing ownership to: \\\"$l_user\\\"\\n\"\n chown \"$l_user\" \"$l_home\"\n fi\n if [ $(( $l_mode & $l_mask )) -gt 0 ]; then\n l_output2=\"$l_output2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" is mode: \\\"$l_mode\\\" should be mode: \\\"$l_max\\\" or more restrictive\\n - removing excess permissions\\n\"\n chmod g-w,o-rwx \"$l_home\"\n fi\n done <<< \"$(stat -Lc '%U %#a' \"$l_home\")\"\n else\n l_output2=\"$l_output2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" Doesn't exist\\n - Please create a home in accordance with local site policy\"\n fi\n done <<< \"$(printf '%s\\n' \"${a_uarr[@]}\")\"\n if [ -z \"$l_output2\" ]; then # If l_output2 is empty, we pass\n echo -e \" - No modification needed to local interactive users home directories\"\n else\n echo -e \"\\n$l_output2\"\n fi\n}\n" + }, + { + "uuid": "504c660d-b4c8-573b-b492-4c9f897eed02", + "benchmark-rule-id": "7.2.10", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=(); a_output3=()\n l_maxsize=\"1000\" # Maximum number of local interactive users before warning (Default 1,000)\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n a_user_and_home=() # Create array with local users and their home directories\n while read -r l_local_user l_local_user_home; do # Populate array with users and user home location\n [[ -n \"$l_local_user\" && -n \"$l_local_user_home\" ]] && a_user_and_home+=(\"$l_local_user:$l_local_user_home\")\n done <<< \"$(awk -v pat=\"$l_valid_shells\" -F: '$(NF) ~ pat { print $1 \" \" $(NF-1) }' /etc/passwd)\"\n l_asize=\"${#a_user_and_home[@]}\" # Here if we want to look at number of users before proceeding \n [ \"${#a_user_and_home[@]}\" -gt \"$l_maxsize\" ] && printf '%s\\n' \"\" \" ** INFO **\" \\\n \" - \\\"$l_asize\\\" Local interactive users found on the system\" \\\n \" - This may be a long running check\" \"\"\n file_access_chk()\n {\n a_access_out=()\n l_max=\"$( printf '%o' $(( 0777 & ~$l_mask)) )\"\n if [ $(( $l_mode & $l_mask )) -gt 0 ]; then\n a_access_out+=(\" - File: \\\"$l_hdfile\\\" is mode: \\\"$l_mode\\\" and should be mode: \\\"$l_max\\\" or more restrictive\")\n fi\n if [[ ! \"$l_owner\" =~ ($l_user) ]]; then\n a_access_out+=(\" - File: \\\"$l_hdfile\\\" owned by: \\\"$l_owner\\\" and should be owned by \\\"${l_user//|/ or }\\\"\")\n fi\n if [[ ! \"$l_gowner\" =~ ($l_group) ]]; then\n a_access_out+=(\" - File: \\\"$l_hdfile\\\" group owned by: \\\"$l_gowner\\\" and should be group owned by \\\"${l_group//|/ or }\\\"\")\n fi\n }\n while IFS=: read -r l_user l_home; do\n a_dot_file=(); a_netrc=(); a_netrc_warn=(); a_bhout=(); a_hdirout=()\n if [ -d \"$l_home\" ]; then\n l_group=\"$(id -gn \"$l_user\" | xargs)\";l_group=\"${l_group// /|}\"\n while IFS= read -r -d $'\\0' l_hdfile; do\n while read -r l_mode l_owner l_gowner; do\n case \"$(basename \"$l_hdfile\")\" in\n .forward | .rhost )\n a_dot_file+=(\" - File: \\\"$l_hdfile\\\" exists\") ;;\n .netrc )\n l_mask='0177'; file_access_chk\n if [ \"${#a_access_out[@]}\" -gt 0 ]; then\n a_netrc+=(\"${a_access_out[@]}\")\n else\n a_netrc_warn+=(\" - File: \\\"$l_hdfile\\\" exists\")\n fi ;;\n .bash_history )\n l_mask='0177'; file_access_chk\n [ \"${#a_access_out[@]}\" -gt 0 ] && a_bhout+=(\"${a_access_out[@]}\") ;;\n * )\n l_mask='0133'; file_access_chk\n [ \"${#a_access_out[@]}\" -gt 0 ] && a_hdirout+=(\"${a_access_out[@]}\") ;;\n esac\n done < <(stat -Lc '%#a %U %G' \"$l_hdfile\")\n done < <(find \"$l_home\" -xdev -type f -name '.*' -print0)\n fi\n if [[ \"${#a_dot_file[@]}\" -gt 0 || \"${#a_netrc[@]}\" -gt 0 || \"${#a_bhout[@]}\" -gt 0 || \"${#a_hdirout[@]}\" -gt 0 ]]; then\n a_output2+=(\" - User: \\\"$l_user\\\" Home Directory: \\\"$l_home\\\"\" \"${a_dot_file[@]}\" \"${a_netrc[@]}\" \"${a_bhout[@]}\" \"${a_hdirout[@]}\")\n fi\n [ \"${#a_netrc_warn[@]}\" -gt 0 ] && a_output3+=(\" - User: \\\"$l_user\\\" Home Directory: \\\"$l_home\\\"\" \"${a_netrc_warn[@]}\")\n done <<< \"$(printf '%s\\n' \"${a_user_and_home[@]}\")\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then # If l_output2 is empty, we pass\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \" ** WARNING **\" \"${a_output3[@]}\"\n printf '%s\\n' \"- Audit Result:\" \" ** PASS **\"\n else\n printf '%s\\n' \"- Audit Result:\" \" ** FAIL **\" \" - * Reasons for audit failure * :\" \"${a_output2[@]}\" \"\"\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \" ** WARNING **\" \"${a_output3[@]}\"\n fi\n}\n" + }, + { + "uuid": "63fd7b52-82a6-5201-88de-04efcc2c6314", + "benchmark-rule-id": "7.2.10", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=(); a_output3=()\n l_maxsize=\"1000\" # Maximum number of local interactive users before warning (Default 1,000)\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n a_user_and_home=() # Create array with local users and their home directories\n while read -r l_local_user l_local_user_home; do # Populate array with users and user home location\n [[ -n \"$l_local_user\" && -n \"$l_local_user_home\" ]] && a_user_and_home+=(\"$l_local_user:$l_local_user_home\")\n done <<< \"$(awk -v pat=\"$l_valid_shells\" -F: '$(NF) ~ pat { print $1 \" \" $(NF-1) }' /etc/passwd)\"\n l_asize=\"${#a_user_and_home[@]}\" # Here if we want to look at number of users before proceeding \n [ \"${#a_user_and_home[@]}\" -gt \"$l_maxsize\" ] && printf '%s\\n' \"\" \" ** INFO **\" \\\n \" - \\\"$l_asize\\\" Local interactive users found on the system\" \\\n \" - This may be a long running check\" \"\"\n file_access_fix()\n {\n a_access_out=()\n l_max=\"$( printf '%o' $(( 0777 & ~$l_mask)) )\"\n if [ $(( $l_mode & $l_mask )) -gt 0 ]; then\n printf '%s\\n' \"\" \" - File: \\\"$l_hdfile\\\" is mode: \\\"$l_mode\\\" and should be mode: \\\"$l_max\\\" or more restrictive\" \\\n \" Updating file: \\\"$l_hdfile\\\" to be mode: \\\"$l_max\\\" or more restrictive\"\n chmod \"$l_change\" \"$l_hdfile\"\n fi\n if [[ ! \"$l_owner\" =~ ($l_user) ]]; then\n printf '%s\\n' \"\" \" - File: \\\"$l_hdfile\\\" owned by: \\\"$l_owner\\\" and should be owned by \\\"${l_user//|/ or }\\\"\" \\\n \" Updating file: \\\"$l_hdfile\\\" to be owned by \\\"${l_user//|/ or }\\\"\"\n chown \"$l_user\" \"$l_hdfile\"\n fi\n if [[ ! \"$l_gowner\" =~ ($l_group) ]]; then\n printf '%s\\n' \"\" \" - File: \\\"$l_hdfile\\\" group owned by: \\\"$l_gowner\\\" and should be group owned by \\\"${l_group//|/ or }\\\"\" \\\n \" Updating file: \\\"$l_hdfile\\\" to be group owned by \\\"${l_group//|/ or }\\\"\"\n chgrp \"$l_group\" \"$l_hdfile\"\n fi\n }\n while IFS=: read -r l_user l_home; do\n a_dot_file=(); a_netrc=(); a_netrc_warn=(); a_bhout=(); a_hdirout=()\n if [ -d \"$l_home\" ]; then\n l_group=\"$(id -gn \"$l_user\" | xargs)\";l_group=\"${l_group// /|}\"\n while IFS= read -r -d $'\\0' l_hdfile; do\n while read -r l_mode l_owner l_gowner; do\n case \"$(basename \"$l_hdfile\")\" in\n .forward | .rhost )\n a_dot_file+=(\" - File: \\\"$l_hdfile\\\" exists\" \" Please review and manually delete this file\") ;;\n .netrc )\n l_mask='0177'; l_change=\"u-x,go-rwx\"; file_access_fix\n a_netrc_warn+=(\" - File: \\\"$l_hdfile\\\" exists\") ;;\n .bash_history )\n l_mask='0177'; l_change=\"u-x,go-rwx\"; file_access_fix ;;\n * )\n l_mask='0133'; l_change=\"u-x,go-wx\"; file_access_fix ;;\n esac\n done < <(stat -Lc '%#a %U %G' \"$l_hdfile\")\n done < <(find \"$l_home\" -xdev -type f -name '.*' -print0)\n fi\n [ \"${#a_dot_file[@]}\" -gt 0 ] && a_output2+=(\" - User: \\\"$l_user\\\" Home Directory: \\\"$l_home\\\"\" \"${a_dot_file[@]}\")\n [ \"${#a_netrc_warn[@]}\" -gt 0 ] && a_output3+=(\" - User: \\\"$l_user\\\" Home Directory: \\\"$l_home\\\"\" \"${a_netrc_warn[@]}\")\n done <<< \"$(printf '%s\\n' \"${a_user_and_home[@]}\")\"\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" ** WARNING **\" \"${a_output3[@]}\" \"\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\"\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "1.1.2.1.3: Since the `/tmp` filesystem is only intended for temporary file storage, set this option to ensure that users cannot create `setuid` files in `/tmp`.\n\n1.1.2.1.4: Since the `/tmp` filesystem is only intended for temporary file storage, set this option to ensure that users cannot run executable binaries from `/tmp`.\n\n1.1.2.2.2: Since the `/dev/shm` filesystem is not intended to support devices, set this option to ensure that users cannot attempt to create special devices in `/dev/shm` partitions.\n\n1.1.2.2.3: Setting this option on a file system prevents users from introducing privileged programs onto the system and allowing non-root users to execute them.\n\n1.1.2.2.4: Setting this option on a file system prevents users from executing programs from shared memory. This deters users from introducing potentially malicious software on the system.\n\n1.1.2.3.1: The default installation only creates a single `/` partition. Since the `/home` directory contains user generated data, there is a risk of resource exhaustion. It will essentially have the whole disk available to fill up and impact the system as a whole. In addition, other operations on the system could fill up the disk unrelated to `/home` and impact all local users.\n\nConfiguring `/home` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attacker's ability to create exploits on the system. In the case of `/home` options such as `usrquota/grpquota` may be considered to limit the impact that users can have on each other with regards to disk resource exhaustion. Other options allow for specific behavior. See `man mount` for exact details regarding filesystem-independent and filesystem-specific options.\n\nAs `/home` contains user data, care should be taken to ensure the security and integrity of the data and mount point.\n\n1.1.2.3.2: Since the `/home` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/home`.\n\n1.1.2.3.3: Since the `/home` filesystem is only intended for user file storage, set this option to ensure that users cannot create `setuid` files in `/home`.\n\n1.1.2.4.1: The reasoning for mounting `/var` on a separate partition is as follows.\n\nThe default installation only creates a single `/` partition. Since the `/var` directory may contain world writable files and directories, there is a risk of resource exhaustion. It will essentially have the whole disk available to fill up and impact the system. In addition, other operations on the system could fill up the disk unrelated to `/var` and cause unintended behavior across the system as the disk is full. See `man auditd.conf` for details.\n\nConfiguring `/var` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attacker's ability to create exploits on the system. Other options allow for specific behavior. See `man mount` for exact details regarding filesystem-independent and filesystem-specific options.\n\nAn example of exploiting `/var` may be an attacker establishing a hard-link to a system `setuid` program and waiting for it to be updated. Once the program is updated, the hard-link can be broken and the attacker would have their own copy of the program. If the program happened to have a security vulnerability, the attacker could continue to exploit the known flaw.\n\n1.1.2.4.2: Since the `/var` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/var`.\n\n1.1.2.4.3: Since the `/var` filesystem is only intended for variable files such as logs, set this option to ensure that users cannot create `setuid` files in `/var`.\n\n1.1.2.5.1: The default installation only creates a single `/` partition. Since the `/var/tmp` directory is world-writable, there is a risk of resource exhaustion. In addition, other operations on the system could fill up the disk unrelated to `/var/tmp` and cause potential disruption to daemons as the disk is full.\n\nConfiguring `/var/tmp` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attacker's ability to create exploits on the system.\n\n1.1.2.5.2: Since the `/var/tmp` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/var/tmp`.\n\n1.1.2.5.3: Since the `/var/tmp` filesystem is only intended for temporary file storage, set this option to ensure that users cannot create `setuid` files in `/var/tmp`.\n\n1.1.2.5.4: Since the `/var/tmp` filesystem is only intended for temporary file storage, set this option to ensure that users cannot run executable binaries from `/var/tmp`.\n\n1.1.2.6.2: Since the `/var/log` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/var/log`.\n\n1.1.2.6.3: Since the `/var/log` filesystem is only intended for log files, set this option to ensure that users cannot create `setuid` files in `/var/log`.\n\n1.1.2.6.4: Since the `/var/log` filesystem is only intended for log files, set this option to ensure that users cannot run executable binaries from `/var/log`.\n\n1.1.2.7.2: Since the `/var/log/audit` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/var/log/audit`.\n\n1.1.2.7.3: Since the `/var/log/audit` filesystem is only intended for variable files such as logs, set this option to ensure that users cannot create `setuid` files in `/var/log/audit`.\n\n1.1.2.7.4: Since the `/var/log/audit` filesystem is only intended for audit logs, set this option to ensure that users cannot run executable binaries from `/var/log/audit`.\n\n1.3.1.1: Without a Mandatory Access Control system installed only the default Discretionary Access Control system will be available.\n\n1.3.1.2: AppArmor must be enabled at boot time in your bootloader configuration to ensure that the controls it provides are not overridden.\n\n1.3.1.3: Security configuration requirements vary from site to site. Some sites may mandate a policy that is stricter than the default policy, which is perfectly acceptable. This item is intended to ensure that any policies that exist on the system are activated.\n\n1.3.1.4: Security configuration requirements vary from site to site. Some sites may mandate a policy that is stricter than the default policy, which is perfectly acceptable. This item is intended to ensure that any policies that exist on the system are activated.\n\n1.4.1: Requiring a boot password upon execution of the boot loader will prevent an unauthorized user from entering boot parameters or changing the boot partition. This prevents users from weakening security (e.g. turning off AppArmor at boot time).\n\n1.4.2: Setting the permissions to read and write for root only prevents non-root users from seeing the boot parameters or changing them. Non-root users who read the boot parameters may be able to identify weaknesses in security upon boot and be able to exploit them.\n\n1.6.4: **- IF -** the `/etc/motd` file does not have the correct access configured, it could be modified by unauthorized users with incorrect or misleading information.\n\n1.6.5: **- IF -** the `/etc/issue` file does not have the correct access configured, it could be modified by unauthorized users with incorrect or misleading information.\n\n1.6.6: **- IF -** the `/etc/issue.net` file does not have the correct access configured, it could be modified by unauthorized users with incorrect or misleading information.\n\n2.4.1.2: This file contains information on what system jobs are run by cron. Write access to these files could provide unprivileged users with the ability to elevate their privileges. Read access to these files could provide users with the ability to gain insight on system jobs that run on the system and could provide them a way to gain unauthorized privileged access.\n\n2.4.1.3: Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.\n\n2.4.1.4: Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.\n\n2.4.1.5: Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.\n\n2.4.1.6: Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.\n\n2.4.1.7: Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.\n\n2.4.1.8: On many systems, only the system administrator is authorized to schedule `cron` jobs. Using the `cron.allow` file to control who can run `cron` jobs enforces this policy. It is easier to manage an allow list than a deny list. In a deny list, you could potentially add a user ID to the system and forget to add it to the deny files.\n\n2.4.2.1: On many systems, only the system administrator is authorized to schedule `at` jobs. Using the `at.allow` file to control who can run `at` jobs enforces this policy. It is easier to manage an allow list than a deny list. In a deny list, you could potentially add a user ID to the system and forget to add it to the deny files.\n\n5.1.1: configuration specifications for `sshd` need to be protected from unauthorized changes by non-privileged users.\n\n5.1.2: If an unauthorized user obtains the private SSH host key file, the host could be impersonated\n\n5.1.3: If a public host key file is modified by an unauthorized user, the SSH service may be compromised.\n\n5.1.4: Restricting which users can remotely access the system via SSH will help ensure that only authorized users access the system.\n\n5.2.7: Restricting the use of `su` , and using `sudo` in its place, provides system administrators better control of the escalation of user privileges to execute privileged commands. The sudo utility also provides a better logging and audit mechanism, as it can log each command executed via `sudo` , whereas `su` can only record that a user executed the `su` program.\n\n5.3.2.1: The system should only provide access after performing authentication of a user.\n\n5.4.2.2: Using GID 0 for the `root` account helps prevent `root` -owned files from accidentally becoming accessible to non-privileged users.\n\n5.4.2.3: Using GID 0 for the `root` group helps prevent `root` group owned files from accidentally becoming accessible to non-privileged users.\n\n5.4.2.4: Access to `root` should be secured at all times.\n\n5.4.2.6: Setting a secure value for `umask` ensures that users make a conscious choice about their file permissions. A permissive `umask` value could result in directories or files with excessive permissions that can be read and/or written to by unauthorized users.\n\n5.4.2.7: It is important to make sure that accounts that are not being used by regular users are prevented from being used to provide an interactive shell. By default, most distributions set the password field for these accounts to an invalid string, but it is also recommended that the shell field in the password file be set to the `nologin` shell. This prevents the account from potentially being used to run any commands.\n\n5.4.2.8: It is important to make sure that accounts that are not being used by regular users are prevented from being used to provide an interactive shell. By default, most distributions set the password field for these accounts to an invalid string, but it is also recommended that the shell field in the password file be set to the `nologin` shell. This prevents the account from potentially being used to run any commands.\n\n5.4.3.3: Setting a secure default value for `umask` ensures that users make a conscious choice about their file permissions. A permissive `umask` value could result in directories or files with excessive permissions that can be read and/or written to by unauthorized users.\n\n6.1.1.2: It is important to ensure that log files have the correct permissions to ensure that sensitive data is archived and protected.\n\n6.1.3.4: It is important to ensure that log files have the correct permissions to ensure that sensitive data is archived and protected.\n\n6.1.4.1: It is important that log files have the correct permissions to ensure that sensitive data is protected and that only the appropriate users / groups have access to them.\n\n6.2.3.20: In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. Users would most likely notice a system reboot and that could alert administrators of an attempt to make unauthorized audit changes.\n\n6.2.4.1: Access to audit records can reveal system and configuration data to attackers, potentially compromising its confidentiality.\n\n6.2.4.2: Access to audit records can reveal system and configuration data to attackers, potentially compromising its confidentiality.\n\n6.2.4.3: Access to audit records can reveal system and configuration data to attackers, potentially compromising its confidentiality.\n\n6.2.4.4: Audit information includes all information including: audit records, audit settings and audit reports. This information is needed to successfully audit system activity. This information must be protected from unauthorized modification or deletion. If this information were to be compromised, forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.\n\n6.2.4.5: Access to the audit configuration files could allow unauthorized personnel to prevent the auditing of critical events.\n\nMisconfigured audit configuration files may prevent the auditing of critical events or impact the system's performance by overwhelming the audit log. Misconfiguration of the audit configuration files may also make it more difficult to establish and investigate events relating to an incident.\n\n6.2.4.6: Access to the audit configuration files could allow unauthorized personnel to prevent the auditing of critical events.\n\nMisconfigured audit configuration files may prevent the auditing of critical events or impact the system's performance by overwhelming the audit log. Misconfiguration of the audit configuration files may also make it more difficult to establish and investigate events relating to an incident.\n\n6.2.4.7: Access to the audit configuration files could allow unauthorized personnel to prevent the auditing of critical events.\n\nMisconfigured audit configuration files may prevent the auditing of critical events or impact the system's performance by overwhelming the audit log. Misconfiguration of the audit configuration files may also make it more difficult to establish and investigate events relating to an incident.\n\n6.2.4.8: Protecting audit information includes identifying and protecting the tools used to view and manipulate log data. Protecting audit tools is necessary to prevent unauthorized operation on audit information.\n\n6.2.4.9: Protecting audit information includes identifying and protecting the tools used to view and manipulate log data. Protecting audit tools is necessary to prevent unauthorized operation on audit information.\n\n6.2.4.10: Protecting audit information includes identifying and protecting the tools used to view and manipulate log data. Protecting audit tools is necessary to prevent unauthorized operation on audit information.\n\n7.1.1: It is critical to ensure that the `/etc/passwd` file is protected from unauthorized write access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.\n\n7.1.2: It is critical to ensure that the `/etc/passwd-` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.\n\n7.1.3: The `/etc/group` file needs to be protected from unauthorized changes by non-privileged users, but needs to be readable as this information is used with many non-privileged programs.\n\n7.1.4: It is critical to ensure that the `/etc/group-` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.\n\n7.1.5: If attackers can gain read access to the `/etc/shadow` file, they can easily run a password cracking program against the hashed password to break it. Other security information that is stored in the `/etc/shadow` file (such as expiration) could also be useful to subvert the user accounts.\n\n7.1.6: It is critical to ensure that the `/etc/shadow-` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.\n\n7.1.7: If attackers can gain read access to the `/etc/gshadow` file, they can easily run a password cracking program against the hashed password to break it. Other security information that is stored in the `/etc/gshadow` file (such as group administrators) could also be useful to subvert the group.\n\n7.1.8: It is critical to ensure that the `/etc/gshadow-` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.\n\n7.1.9: It is critical to ensure that the `/etc/shells` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.\n\n7.1.10: It is critical to ensure that `/etc/security/opasswd` is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.\n\n7.1.11: Data in world-writable files can be modified and compromised by any user on the system. World writable files may also indicate an incorrectly written script or program that could potentially be the cause of a larger compromise to the system's integrity.\n\nThis feature prevents the ability to delete or rename files in world writable directories (such as `/tmp` ) that are owned by another user.\n\n7.1.12: A new user or group who is assigned a deleted user's user ID or group ID may then end up \"owning\" a deleted user or group's files, and thus have more access on the system than was intended.\n\n7.1.13: There are valid reasons for SUID and SGID programs, but it is important to identify and review such programs to ensure they are legitimate. Review the files returned by the action in the audit section and check to see if system binaries have a different checksum than what from the package. This is an indication that the binary may have been replaced.\n\n7.2.3: Groups defined in the `/etc/passwd` file but not in the `/etc/group` file pose a threat to system security since group permissions are not properly managed.\n\n7.2.4: Any users assigned to the shadow group would be granted read access to the /etc/shadow file. If attackers can gain read access to the `/etc/shadow` file, they can easily run a password cracking program against the hashed passwords to break them. Other security information that is stored in the `/etc/shadow` file (such as expiration) could also be useful to subvert additional user accounts.\n\n7.2.9: Since the user is accountable for files stored in the user home directory, the user must be the owner of the directory. Group or world-writable user home directories may enable malicious users to steal or modify other users' data or to gain another user's system privileges. If the user's home directory does not exist or is unassigned, the user will be placed in \"/\" and will not be able to write any files or have local environment variables set.\n\n7.2.10: User configuration files with excessive or incorrect access may enable malicious users to steal or modify other users' data or to gain another user's system privileges.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "bc81cf44-7259-54d1-8b51-6263f76437ea", + "control-id": "cisc-003.010", + "description": "5.1.6 Ensure sshd Ciphers are configured; 5.1.12 Ensure sshd KexAlgorithms is configured; 5.1.15 Ensure sshd MACs are configured", + "props": [ + { + "name": "rationale", + "value": "5.1.6: Weak ciphers that are used for authentication to the cryptographic module cannot be relied upon to provide confidentiality or integrity, and system data may be compromised.\n\n- The Triple DES ciphers, as used in SSH, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain clear text data via a birthday attack against a long-duration encrypted session, aka a \"Sweet32\" attack.\n\n- Error handling in the SSH protocol; Client and Server, when using a block cipher algorithm in Cipher Block Chaining (CBC) mode, makes it easier for remote attackers to recover certain plain text data from an arbitrary block of cipher text in an SSH session via unknown vectors.\n\n5.1.12: Key exchange methods that are considered weak should be removed. A key exchange method may be weak because too few bits are used, or the hashing algorithm is considered too weak. Using weak algorithms could expose connections to man-in-the-middle attacks\n\n5.1.15: MD5 and 96-bit MAC algorithms are considered weak and have been shown to increase exploitability in SSH downgrade attacks. Weak algorithms continue to have a great deal of attention as a weak spot that can be exploited with expanded computing power. An attacker that breaks the algorithm could take advantage of a MiTM position to decrypt the SSH tunnel and capture credentials and information.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "df1ff59e-e5dd-5ce4-92f1-8fa560b01c51", + "control-id": "cisc-003.011", + "description": "5.3.3.3.3 Ensure pam_pwhistory includes use_authtok; 5.3.3.4.3 Ensure pam_unix includes a strong password hashing algorithm; 5.3.3.4.4 Ensure pam_unix includes use_authtok; 5.4.1.4 Ensure strong password hashing algorithm is configured; 7.2.1 Ensure accounts in /etc/passwd use shadowed passwords", + "props": [ + { + "name": "rationale", + "value": "5.3.3.3.3: `use_authtok` allows multiple pam modules to confirm a new password before it is accepted.\n\n5.3.3.4.3: The `SHA-512` and `yescrypt` algorithms provide a stronger hash than other algorithms used by Linux for password hash generation. A stronger hash provides additional protection to the system by increasing the level of effort needed for an attacker to successfully determine local user passwords.\n\n**Note:** These changes only apply to the local system.\n\n5.3.3.4.4: `use_authtok` allows multiple pam modules to confirm a new password before it is accepted.\n\n5.4.1.4: The `SHA-512` and `yescrypt` algorithms provide a stronger hash than other algorithms used by Linux for password hash generation. A stronger hash provides additional protection to the system by increasing the level of effort needed for an attacker to successfully determine local group passwords.\n\n7.2.1: The `/etc/passwd` file also contains information like user ID's and group ID's that are used by many system programs. Therefore, the `/etc/passwd` file must remain world readable. In spite of encoding the password with a randomly-generated one-way hash function, an attacker could still break the system if they got access to the `/etc/passwd` file. This can be mitigated by using shadowed passwords, thus moving the passwords in the `/etc/passwd` file to `/etc/shadow`. The `/etc/shadow` file is set so only root will be able to read and write. This helps mitigate the risk of an attacker gaining access to the encoded passwords with which to perform a dictionary attack.\n\n**Note:**\n\n- All accounts must have passwords or be locked to prevent the account from being used by an unauthorized user.\n\n- A user account with an empty second field in `/etc/passwd` allows the account to be logged into by providing only the username.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "680817ba-2903-513e-a777-ddc4ad400d40", + "control-id": "cisc-003.014", + "description": "1.5.4 Ensure prelink is not installed; 6.3.1 Ensure AIDE is installed", + "props": [ + { + "name": "rationale", + "value": "1.5.4: The prelinking feature can interfere with the operation of AIDE, because it changes binaries. Prelinking can also increase the vulnerability of the system if a malicious user is able to compromise a common library such as libc.\n\n6.3.1: By monitoring the filesystem state compromised files can be detected to prevent or limit the exposure of accidental or malicious misconfigurations or modified binaries.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "60ec065e-6bdf-500d-ad88-d7d2d7e27d49", + "control-id": "cisc-004.001", + "description": "5.4.1.3 Ensure password expiration warning days is configured", + "props": [ + { + "name": "rationale", + "value": "5.4.1.3: Providing an advance warning that a password will be expiring gives users time to think of a secure password. Users caught unaware may choose a simple password or write it down where it may be discovered.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "eafb2720-525d-542f-958e-0abcd223541e", + "control-id": "cisc-004.003", + "description": "1.7.4 Ensure GDM screen locks when the user is idle; 1.7.5 Ensure GDM screen locks cannot be overridden; 5.4.3.2 Ensure default user shell timeout is configured", + "automation-scripts": [ + { + "uuid": "dfd0d4ec-335a-502a-acca-2bf23de44d0a", + "benchmark-rule-id": "1.7.5", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=()\n f_check_setting() \n {\n grep -Psrilq -- \"^\\h*$2\\b\" /etc/dconf/db/local.d/locks/* && \\\n echo \"- \\\"$3\\\" is locked\" || echo \"- \\\"$3\\\" is not locked or not set\"\n }\n declare -A settings=(\n [\"idle-delay\"]=\"/org/gnome/desktop/session/idle-delay\"\n [\"lock-delay\"]=\"/org/gnome/desktop/screensaver/lock-delay\"\n )\n for setting in \"${!settings[@]}\"; do\n result=$(f_check_setting \"$setting\" \"${settings[$setting]}\" \"$setting\")\n if [[ $result == *\"is not locked\"* || $result == *\"not set to false\"* ]]; then\n a_output2+=(\"$result\")\n else\n a_output+=(\"$result\")\n fi\n done\n printf '%s\\n' \"\" \"- Audit Result:\"\n if [ \"${#a_output2[@]}\" -gt 0 ]; then\n printf '%s\\n' \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\"\n else\n printf '%s\\n' \" ** PASS **\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "c9893968-a87d-5d19-aafd-6f2fcc52d195", + "benchmark-rule-id": "5.4.3.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n output1=\"\" output2=\"\"\n [ -f /etc/bashrc ] && BRC=\"/etc/bashrc\"\n for f in \"$BRC\" /etc/profile /etc/profile.d/*.sh ; do\n grep -Pq '^\\s*([^#]+\\s+)?TMOUT=(900|[1-8][0-9][0-9]|[1-9][0-9]|[1-9])\\b' \"$f\" && grep -Pq '^\\s*([^#]+;\\s*)?readonly\\s+TMOUT(\\s+|\\s*;|\\s*$|=(900|[1-8][0-9][0-9]|[1-9][0-9]|[1-9]))\\b' \"$f\" && grep -Pq '^\\s*([^#]+;\\s*)?export\\s+TMOUT(\\s+|\\s*;|\\s*$|=(900|[1-8][0-9][0-9]|[1-9][0-9]|[1-9]))\\b' \"$f\" && \n output1=\"$f\"\n done\n grep -Pq '^\\s*([^#]+\\s+)?TMOUT=(9[0-9][1-9]|9[1-9][0-9]|0+|[1-9]\\d{3,})\\b' /etc/profile /etc/profile.d/*.sh \"$BRC\" && output2=$(grep -Ps '^\\s*([^#]+\\s+)?TMOUT=(9[0-9][1-9]|9[1-9][0-9]|0+|[1-9]\\d{3,})\\b' /etc/profile /etc/profile.d/*.sh $BRC)\n if [ -n \"$output1\" ] && [ -z \"$output2\" ]; then\n echo -e \"\\nPASSED\\n\\nTMOUT is configured in: \\\"$output1\\\"\\n\"\n else\n [ -z \"$output1\" ] && echo -e \"\\nFAILED\\n\\nTMOUT is not configured\\n\"\n [ -n \"$output2\" ] && echo -e \"\\nFAILED\\n\\nTMOUT is incorrectly configured in: \\\"$output2\\\"\\n\"\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "1.7.4: Setting a lock-out value reduces the window of opportunity for unauthorized user access to another user's session that has been left unattended.\n\n1.7.5: Setting a lock-out value reduces the window of opportunity for unauthorized user access to another user's session that has been left unattended.\n\nWithout locking down the system settings, user settings take precedence over the system settings.\n\n5.4.3.2: Setting a timeout value reduces the window of opportunity for unauthorized user access to another user's shell session that has been left unattended. It also ends the inactive session and releases the resources associated with that session.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "0aad09e7-d405-56e9-b50b-03a4e796401d", + "control-id": "cisc-004.004", + "description": "4.1.1 Ensure a single firewall configuration utility is in use; 4.2.1 Ensure ufw is installed; 4.2.2 Ensure iptables-persistent is not installed with ufw; 4.2.3 Ensure ufw service is enabled; 4.2.4 Ensure ufw loopback traffic is configured; 4.2.5 Ensure ufw outbound connections are configured; 4.2.6 Ensure ufw firewall rules exist for all open ports; 4.2.7 Ensure ufw default deny firewall policy; 4.3.1 Ensure nftables is installed; 4.3.2 Ensure ufw is uninstalled or disabled with nftables; 4.3.3 Ensure iptables are flushed with nftables; 4.3.4 Ensure a nftables table exists; 4.3.5 Ensure nftables base chains exist; 4.3.6 Ensure nftables loopback traffic is configured; 4.3.7 Ensure nftables outbound and established connections are configured; 4.3.8 Ensure nftables default deny firewall policy; 4.3.9 Ensure nftables service is enabled; 4.3.10 Ensure nftables rules are permanent; 4.4.1.1 Ensure iptables packages are installed; 4.4.1.2 Ensure nftables is not in use with iptables; 4.4.1.3 Ensure ufw is not in use with iptables; 4.4.2.1 Ensure iptables default deny firewall policy; 4.4.2.2 Ensure iptables loopback traffic is configured; 4.4.2.3 Ensure iptables outbound and established connections are configured; 4.4.2.4 Ensure iptables firewall rules exist for all open ports; 4.4.3.1 Ensure ip6tables default deny firewall policy; 4.4.3.2 Ensure ip6tables loopback traffic is configured; 4.4.3.3 Ensure ip6tables outbound and established connections are configured; 4.4.3.4 Ensure ip6tables firewall rules exist for all open ports", + "automation-scripts": [ + { + "uuid": "3650ff5d-aec8-5039-8d89-c21295961bda", + "benchmark-rule-id": "4.1.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n active_firewall=() firewalls=(\"ufw\" \"nftables\" \"iptables\")\n # Determine which firewall is in use\n for firewall in \"${firewalls[@]}\"; do\n case $firewall in\n nftables)\n cmd=\"nft\" ;;\n *)\n cmd=$firewall ;;\n esac \n if command -v $cmd &> /dev/null && systemctl is-enabled --quiet $firewall && systemctl is-active --quiet $firewall; then\n active_firewall+=(\"$firewall\")\n fi\n done\n # Display audit results\n if [ ${#active_firewall[@]} -eq 1 ]; then\n printf '%s\\n' \"\" \"Audit Results:\" \" ** PASS **\" \" - A single firewall is in use follow the recommendation in ${active_firewall[0]} subsection ONLY\"\n elif [ ${#active_firewall[@]} -eq 0 ]; then\n printf '%s\\n' \"\" \" Audit Results:\" \" ** FAIL **\" \"- No firewall in use or unable to determine firewall status\"\n else\n printf '%s\\n' \"\" \" Audit Results:\" \" ** FAIL **\" \" - Multiple firewalls are in use: ${active_firewall[*]}\"\n fi \n}\n" + }, + { + "uuid": "08138afd-8e46-5131-a4a9-1c90887e9e56", + "benchmark-rule-id": "4.2.6", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n unset a_ufwout;unset a_openports\n while read -r l_ufwport; do\n [ -n \"$l_ufwport\" ] && a_ufwout+=(\"$l_ufwport\")\n done < <(ufw status verbose | grep -Po '^\\h*\\d+\\b' | sort -u)\n while read -r l_openport; do\n [ -n \"$l_openport\" ] && a_openports+=(\"$l_openport\")\n done < <(ss -tuln | awk '($5!~/%lo:/ && $5!~/127.0.0.1:/ && $5!~/\\[?::1\\]?:/) {split($5, a, \":\"); print a[2]}' | sort -u)\n a_diff=(\"$(printf '%s\\n' \"${a_openports[@]}\" \"${a_ufwout[@]}\" \"${a_ufwout[@]}\" | sort | uniq -u)\")\n if [[ -n \"${a_diff[*]}\" ]]; then\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n- The following port(s) don't have a rule in UFW: $(printf '%s\\n' \\\\n\"${a_diff[*]}\")\\n- End List\"\n else\n echo -e \"\\n - Audit Passed -\\n- All open ports have a rule in UFW\\n\"\n fi\n}\n" + }, + { + "uuid": "8094ded5-947e-59c6-812f-2fcf10ba6330", + "benchmark-rule-id": "4.4.3.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n" + }, + { + "uuid": "c8c28d8e-458c-50ed-858a-9cd652c1328e", + "benchmark-rule-id": "4.4.3.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n} \n" + }, + { + "uuid": "bdec0667-e615-5ad3-ad07-f1daee8e7b2d", + "benchmark-rule-id": "4.4.3.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n" + }, + { + "uuid": "30f5fc3a-7ad5-5701-86d6-02acf334b26d", + "benchmark-rule-id": "4.4.3.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "4.1.1: Proper configuration of a single firewall utility minimizes cyber threats and protects services and data, while avoiding vulnerabilities like open ports or exposed services. Standardizing on a single tool simplifies management, reduces errors, and fortifies security across Linux systems.\n\n4.2.1: A firewall utility is required to configure the Linux kernel's netfilter framework via the iptables or nftables back-end.\n\nThe Linux kernel's netfilter framework host-based firewall can protect against threats originating from within a corporate network to include malicious mobile code and poorly configured software on a host.\n\n**Note:** Only one firewall utility should be installed and configured. `UFW` is dependent on the iptables package\n\n4.2.2: Running both `ufw` and the services included in the iptables-persistent package may lead to conflict\n\n4.2.3: The ufw service must be enabled and running in order for ufw to protect the system\n\n4.2.4: Loopback traffic is generated between processes on machine and is typically critical to operation of the system. The loopback interface is the only place that loopback network (127.0.0.0/8 for IPv4 and ::1/128 for IPv6) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.\n\n4.2.5: If rules are not in place for new outbound connections all packets will be dropped by the default policy preventing network usage.\n\n4.2.6: To reduce the attack surface of a system, all services and ports should be blocked unless required.\n\n- Any ports that have been opened on non-loopback addresses need firewall rules to govern traffic.\n\n- Without a firewall rule configured for open ports, the default firewall policy will drop all packets to these ports.\n\n- Required ports should have a firewall rule created to allow approved connections in accordance with local site policy.\n\n- Unapproved ports should have an explicit deny rule created.\n\n4.2.7: With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to allow list acceptable usage than to deny list unacceptable usage.\n\n4.3.1: nftables is a subsystem of the Linux kernel that can protect against threats originating from within a corporate network to include malicious mobile code and poorly configured software on a host.\n\n4.3.2: Running both the `nftables` service and `ufw` may lead to conflict and unexpected results.\n\n4.3.3: It is possible to mix iptables and nftables. However, this increases complexity and also the chance to introduce errors. For simplicity flush out all iptables rules, and ensure it is not loaded\n\n4.3.4: nftables doesn't have any default tables. Without a table being built, nftables will not filter network traffic.\n\n4.3.5: If a base chain doesn't exist with a hook for input, forward, and delete, packets that would flow through those chains will not be touched by nftables.\n\n4.3.6: Loopback traffic is generated between processes on machine and is typically critical to the operation of the system. The loopback interface is the only place that loopback network traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.\n\n4.3.7: If rules are not in place for new outbound, and established connections all packets will be dropped by the default policy preventing network usage.\n\n4.3.8: There are two policies: accept (Default) and drop. If the policy is set to `accept`, the firewall will accept any packet that is not configured to be denied and the packet will continue transversing the network stack.\n\nIt is easier to allow list acceptable usage than to deny list unacceptable usage.\n\n**Note:**\n\n- Allow port 22(ssh) needs to be updated to only allow systems requiring ssh connectivity to connect, as per site policy.\n\n- Changing firewall settings while connected over network can result in being locked out of the system.\n\n4.3.9: The nftables service restores the nftables rules from the rules files referenced in the `/etc/nftables.conf` file during boot or the starting of the nftables service\n\n4.3.10: Changes made to nftables ruleset only affect the live system, you will also need to configure the nftables ruleset to apply on boot\n\n4.4.1.1: A method of configuring and maintaining firewall rules is necessary to configure a Host Based Firewall.\n\n4.4.1.2: Running both `iptables` and `nftables` may lead to conflict.\n\n4.4.1.3: Running `iptables.persistent` with `ufw` enabled may lead to conflict and unexpected results.\n\n4.4.2.1: With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to allow list acceptable usage than to deny list unacceptable usage.\n\n4.4.2.2: Loopback traffic is generated between processes on machine and is typically critical to the operation of the system. The loopback interface is the only place that loopback network (127.0.0.0/8) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.\n\n4.4.2.3: If rules are not in place for new outbound, and established connections all packets will be dropped by the default policy preventing network usage.\n\n4.4.2.4: Without a firewall rule configured for open ports default firewall policy will drop all packets to these ports.\n\n4.4.3.1: With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to allow list acceptable usage than to deny list unacceptable usage.\n\n4.4.3.2: Loopback traffic is generated between processes on machine and is typically critical to operation of the system. The loopback interface is the only place that loopback network (::1) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.\n\n4.4.3.3: If rules are not in place for new outbound, and established connections all packets will be dropped by the default policy preventing network usage.\n\n4.4.3.4: Without a firewall rule configured for open ports default firewall policy will drop all packets to these ports.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "e35fd0d7-df50-57d0-af2d-1634c8b8b85d", + "control-id": "cisc-004.005", + "description": "4.1.1 Ensure a single firewall configuration utility is in use; 4.2.1 Ensure ufw is installed; 4.2.2 Ensure iptables-persistent is not installed with ufw; 4.2.3 Ensure ufw service is enabled; 4.2.4 Ensure ufw loopback traffic is configured; 4.2.5 Ensure ufw outbound connections are configured; 4.2.7 Ensure ufw default deny firewall policy; 4.3.1 Ensure nftables is installed; 4.3.2 Ensure ufw is uninstalled or disabled with nftables; 4.3.3 Ensure iptables are flushed with nftables; 4.3.4 Ensure a nftables table exists; 4.3.5 Ensure nftables base chains exist; 4.3.6 Ensure nftables loopback traffic is configured; 4.3.7 Ensure nftables outbound and established connections are configured; 4.3.8 Ensure nftables default deny firewall policy; 4.3.9 Ensure nftables service is enabled; 4.3.10 Ensure nftables rules are permanent; 4.4.1.1 Ensure iptables packages are installed; 4.4.1.2 Ensure nftables is not in use with iptables; 4.4.1.3 Ensure ufw is not in use with iptables; 4.4.2.1 Ensure iptables default deny firewall policy; 4.4.2.2 Ensure iptables loopback traffic is configured; 4.4.2.3 Ensure iptables outbound and established connections are configured; 4.4.2.4 Ensure iptables firewall rules exist for all open ports; 4.4.3.1 Ensure ip6tables default deny firewall policy; 4.4.3.2 Ensure ip6tables loopback traffic is configured; 4.4.3.3 Ensure ip6tables outbound and established connections are configured; 4.4.3.4 Ensure ip6tables firewall rules exist for all open ports", + "automation-scripts": [ + { + "uuid": "fc8450f6-363c-5b8b-a61d-4bc4d2dd0f62", + "benchmark-rule-id": "4.1.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n active_firewall=() firewalls=(\"ufw\" \"nftables\" \"iptables\")\n # Determine which firewall is in use\n for firewall in \"${firewalls[@]}\"; do\n case $firewall in\n nftables)\n cmd=\"nft\" ;;\n *)\n cmd=$firewall ;;\n esac \n if command -v $cmd &> /dev/null && systemctl is-enabled --quiet $firewall && systemctl is-active --quiet $firewall; then\n active_firewall+=(\"$firewall\")\n fi\n done\n # Display audit results\n if [ ${#active_firewall[@]} -eq 1 ]; then\n printf '%s\\n' \"\" \"Audit Results:\" \" ** PASS **\" \" - A single firewall is in use follow the recommendation in ${active_firewall[0]} subsection ONLY\"\n elif [ ${#active_firewall[@]} -eq 0 ]; then\n printf '%s\\n' \"\" \" Audit Results:\" \" ** FAIL **\" \"- No firewall in use or unable to determine firewall status\"\n else\n printf '%s\\n' \"\" \" Audit Results:\" \" ** FAIL **\" \" - Multiple firewalls are in use: ${active_firewall[*]}\"\n fi \n}\n" + }, + { + "uuid": "3514a41c-7cde-5a3a-8929-3b7419fc52b8", + "benchmark-rule-id": "4.4.3.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n" + }, + { + "uuid": "a72c151e-fc8c-5f23-a8ae-7b854a26ecd2", + "benchmark-rule-id": "4.4.3.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n} \n" + }, + { + "uuid": "f5ce03b6-5219-5d3f-b95e-6bd54a49689b", + "benchmark-rule-id": "4.4.3.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n" + }, + { + "uuid": "8895f834-1986-514f-ad55-ee06fc98669c", + "benchmark-rule-id": "4.4.3.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "4.1.1: Proper configuration of a single firewall utility minimizes cyber threats and protects services and data, while avoiding vulnerabilities like open ports or exposed services. Standardizing on a single tool simplifies management, reduces errors, and fortifies security across Linux systems.\n\n4.2.1: A firewall utility is required to configure the Linux kernel's netfilter framework via the iptables or nftables back-end.\n\nThe Linux kernel's netfilter framework host-based firewall can protect against threats originating from within a corporate network to include malicious mobile code and poorly configured software on a host.\n\n**Note:** Only one firewall utility should be installed and configured. `UFW` is dependent on the iptables package\n\n4.2.2: Running both `ufw` and the services included in the iptables-persistent package may lead to conflict\n\n4.2.3: The ufw service must be enabled and running in order for ufw to protect the system\n\n4.2.4: Loopback traffic is generated between processes on machine and is typically critical to operation of the system. The loopback interface is the only place that loopback network (127.0.0.0/8 for IPv4 and ::1/128 for IPv6) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.\n\n4.2.5: If rules are not in place for new outbound connections all packets will be dropped by the default policy preventing network usage.\n\n4.2.7: With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to allow list acceptable usage than to deny list unacceptable usage.\n\n4.3.1: nftables is a subsystem of the Linux kernel that can protect against threats originating from within a corporate network to include malicious mobile code and poorly configured software on a host.\n\n4.3.2: Running both the `nftables` service and `ufw` may lead to conflict and unexpected results.\n\n4.3.3: It is possible to mix iptables and nftables. However, this increases complexity and also the chance to introduce errors. For simplicity flush out all iptables rules, and ensure it is not loaded\n\n4.3.4: nftables doesn't have any default tables. Without a table being built, nftables will not filter network traffic.\n\n4.3.5: If a base chain doesn't exist with a hook for input, forward, and delete, packets that would flow through those chains will not be touched by nftables.\n\n4.3.6: Loopback traffic is generated between processes on machine and is typically critical to the operation of the system. The loopback interface is the only place that loopback network traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.\n\n4.3.7: If rules are not in place for new outbound, and established connections all packets will be dropped by the default policy preventing network usage.\n\n4.3.8: There are two policies: accept (Default) and drop. If the policy is set to `accept`, the firewall will accept any packet that is not configured to be denied and the packet will continue transversing the network stack.\n\nIt is easier to allow list acceptable usage than to deny list unacceptable usage.\n\n**Note:**\n\n- Allow port 22(ssh) needs to be updated to only allow systems requiring ssh connectivity to connect, as per site policy.\n\n- Changing firewall settings while connected over network can result in being locked out of the system.\n\n4.3.9: The nftables service restores the nftables rules from the rules files referenced in the `/etc/nftables.conf` file during boot or the starting of the nftables service\n\n4.3.10: Changes made to nftables ruleset only affect the live system, you will also need to configure the nftables ruleset to apply on boot\n\n4.4.1.1: A method of configuring and maintaining firewall rules is necessary to configure a Host Based Firewall.\n\n4.4.1.2: Running both `iptables` and `nftables` may lead to conflict.\n\n4.4.1.3: Running `iptables.persistent` with `ufw` enabled may lead to conflict and unexpected results.\n\n4.4.2.1: With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to allow list acceptable usage than to deny list unacceptable usage.\n\n4.4.2.2: Loopback traffic is generated between processes on machine and is typically critical to the operation of the system. The loopback interface is the only place that loopback network (127.0.0.0/8) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.\n\n4.4.2.3: If rules are not in place for new outbound, and established connections all packets will be dropped by the default policy preventing network usage.\n\n4.4.2.4: Without a firewall rule configured for open ports default firewall policy will drop all packets to these ports.\n\n4.4.3.1: With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to allow list acceptable usage than to deny list unacceptable usage.\n\n4.4.3.2: Loopback traffic is generated between processes on machine and is typically critical to operation of the system. The loopback interface is the only place that loopback network (::1) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.\n\n4.4.3.3: If rules are not in place for new outbound, and established connections all packets will be dropped by the default policy preventing network usage.\n\n4.4.3.4: Without a firewall rule configured for open ports default firewall policy will drop all packets to these ports.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "3bb31b19-1253-5e1d-a3fe-f8d0ecdaa9c0", + "control-id": "cisc-004.008", + "description": "1.1.1.1 Ensure cramfs kernel module is not available; 1.1.1.2 Ensure freevxfs kernel module is not available; 1.1.1.3 Ensure hfs kernel module is not available; 1.1.1.4 Ensure hfsplus kernel module is not available; 1.1.1.5 Ensure jffs2 kernel module is not available; 1.1.1.6 Ensure overlayfs kernel module is not available; 1.1.1.7 Ensure squashfs kernel module is not available; 1.1.1.8 Ensure udf kernel module is not available; 1.1.1.10 Ensure unused filesystems kernel modules are not available; 1.1.2.1.1 Ensure /tmp is a separate partition; 1.1.2.1.2 Ensure nodev option set on /tmp partition; 1.1.2.2.1 Ensure /dev/shm is a separate partition; 1.5.2 Ensure ptrace_scope is restricted; 1.5.5 Ensure Automatic Error Reporting is not enabled; 1.7.1 Ensure GDM is removed; 1.7.10 Ensure XDMCP is not enabled; 2.1.2 Ensure avahi daemon services are not in use; 2.1.3 Ensure dhcp server services are not in use; 2.1.4 Ensure dns server services are not in use; 2.1.5 Ensure dnsmasq services are not in use; 2.1.6 Ensure ftp server services are not in use; 2.1.7 Ensure ldap server services are not in use; 2.1.8 Ensure message access server services are not in use; 2.1.9 Ensure network file system services are not in use; 2.1.10 Ensure nis server services are not in use; 2.1.11 Ensure print server services are not in use; 2.1.12 Ensure rpcbind services are not in use; 2.1.13 Ensure rsync services are not in use; 2.1.14 Ensure samba file server services are not in use; 2.1.15 Ensure snmp services are not in use; 2.1.16 Ensure tftp server services are not in use; 2.1.17 Ensure web proxy server services are not in use; 2.1.18 Ensure web server services are not in use; 2.1.19 Ensure xinetd services are not in use; 2.1.20 Ensure X window server services are not in use; 2.1.21 Ensure mail transfer agent is configured for local-only mode; 2.1.22 Ensure only approved services are listening on a network interface; 2.2.1 Ensure NIS Client is not installed; 2.2.2 Ensure rsh client is not installed; 2.2.3 Ensure talk client is not installed; 2.2.4 Ensure telnet client is not installed; 2.2.5 Ensure ldap client is not installed; 2.2.6 Ensure ftp client is not installed; 3.1.1 Ensure IPv6 status is identified; 3.1.2 Ensure wireless interfaces are disabled; 3.1.3 Ensure bluetooth services are not in use; 3.2.1 Ensure dccp kernel module is not available; 3.2.2 Ensure tipc kernel module is not available; 3.2.3 Ensure rds kernel module is not available; 3.2.4 Ensure sctp kernel module is not available; 3.3.1 Ensure ip forwarding is disabled; 3.3.2 Ensure packet redirect sending is disabled; 3.3.3 Ensure bogus icmp responses are ignored; 3.3.4 Ensure broadcast icmp requests are ignored; 3.3.5 Ensure icmp redirects are not accepted; 3.3.6 Ensure secure icmp redirects are not accepted; 3.3.7 Ensure reverse path filtering is enabled; 3.3.8 Ensure source routed packets are not accepted; 3.3.10 Ensure tcp syn cookies is enabled; 3.3.11 Ensure ipv6 router advertisements are not accepted; 5.1.8 Ensure sshd DisableForwarding is enabled; 6.1.2.1.4 Ensure systemd-journal-remote service is not in use; 6.1.3.7 Ensure rsyslog is not configured to receive logs from a remote client", + "automation-scripts": [ + { + "uuid": "a377e3f3-6e54-5ebf-9010-96b245f533da", + "benchmark-rule-id": "1.1.1.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"cramfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "b070b425-1998-53e0-b6ac-2195503d8d44", + "benchmark-rule-id": "1.1.1.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"cramfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "e5edd559-63f0-534c-adb1-2e6a4caea395", + "benchmark-rule-id": "1.1.1.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"freevxfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "b09bd83c-ff4b-57a5-b5e7-becc7cd59bd6", + "benchmark-rule-id": "1.1.1.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"freevxfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "d2b4a788-5b66-5c67-a4e4-d5976d692fc9", + "benchmark-rule-id": "1.1.1.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"hfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "22af0962-83be-5f59-a4b7-87cec02cb696", + "benchmark-rule-id": "1.1.1.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"hfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "63f6dbb3-b4d1-5c7d-8344-3ab35884276b", + "benchmark-rule-id": "1.1.1.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"hfsplus\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "7df13606-8011-521a-8cfe-b4c08c9a12de", + "benchmark-rule-id": "1.1.1.4", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"hfsplus\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "91fceca7-1dc4-5082-8d12-f4ac59428b95", + "benchmark-rule-id": "1.1.1.5", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"jffs2\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "5f211d11-d393-55c2-8c68-43bb65212218", + "benchmark-rule-id": "1.1.1.5", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"jffs2\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "94a05e8e-5870-5a25-976c-d36439da5544", + "benchmark-rule-id": "1.1.1.6", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"overlayfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "a30081c9-fccb-5d74-bdba-fe3bb7c995ba", + "benchmark-rule-id": "1.1.1.6", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"overlayfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "c32359fa-5788-5180-8042-ce79cf4b2538", + "benchmark-rule-id": "1.1.1.7", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"squashfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "f326e85c-f262-510f-9ef2-7eede6fa66f8", + "benchmark-rule-id": "1.1.1.7", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"squashfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "5376efd7-cc0c-5064-b3da-56cd320e3cb2", + "benchmark-rule-id": "1.1.1.8", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"udf\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "a3fbde1c-ebaa-537d-9cdf-aebb09cbeb6b", + "benchmark-rule-id": "1.1.1.8", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"udf\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "d816b261-877c-5f58-b472-c2fc4390e8c9", + "benchmark-rule-id": "1.1.1.10", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=(); a_output3=(); l_dl=\"\" # Initialize arrays and clear variables\n l_mod_name=\"gfs2\" # set module name\n l_mod_type=\"fs\" # set module type\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" # Set to ignore duplicate checks\n a_showconfig=() # Create array with modprobe output\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_name\" &> /dev/null; then # Check if the module is currently loaded\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n echo -e \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "cea0c613-d479-5821-abe7-8a1eba4e7e6b", + "benchmark-rule-id": "1.5.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_parlist=(\"kernel.yama.ptrace_scope=(1|2|3)\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_kernel_parameter_chk\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "b03b2c9e-ccc2-5a17-b3e3-1ab4c691f5a1", + "benchmark-rule-id": "1.7.10", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n while IFS= read -r l_file; do\n awk '/\\[xdmcp\\]/{ f = 1;next } /\\[/{ f = 0 } f {if (/^\\s*Enable\\s*=\\s*true/) print \"The file: \\\"'\"$l_file\"'\\\" includes: \\\"\" $0 \"\\\" in the \\\"[xdmcp]\\\" block\"}' \"$l_file\"\n done < <(grep -Psil -- '^\\h*\\[xdmcp\\]' /etc/{gdm3,gdm}/{custom,daemon}.conf)\n}\n" + }, + { + "uuid": "73e1309a-df22-53a6-838f-71c0a9f2b404", + "benchmark-rule-id": "2.1.21", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_port_list=(\"25\" \"465\" \"587\")\n for l_port_number in \"${a_port_list[@]}\"; do\n if ss -plntu | grep -P -- ':'\"$l_port_number\"'\\b' | grep -Pvq -- '\\h+(127\\.0\\.0\\.1|\\[?::1\\]?):'\"$l_port_number\"'\\b'; then\n a_output2+=(\" - Port \\\"$l_port_number\\\" is listening on a non-loopback network interface\")\n else\n a_output+=(\" - Port \\\"$l_port_number\\\" is not listening on a non-loopback network interface\")\n fi\n done\n if command -v postconf &> /dev/null; then\n l_interfaces=\"$(postconf -n inet_interfaces)\"\n elif command -v exim &> /dev/null; then\n l_interfaces=\"$(exim -bP local_interfaces)\"\n elif command -v sendmail &> /dev/null; then\n l_interfaces=\"$(grep -i \"0 DaemonPortOptions=\" /etc/mail/sendmail.cr | grep -oP '?<=Addr=)[^,+]+')\"\n fi\n if [ -n \"$l_interfaces\" ]; then\n if grep -Pqi '\\ball\\b' <<< \"$l_interfaces\"; then\n a_output2+=(\" - MTA is bound to all network interfaces\")\n elif ! grep -Pqi '(inet_interfaces\\h*=\\h*)?(0\\.0\\.0\\.0|::1|loopback-only)' <<< \"$l_interfaces\"; then\n a_output2+=(\" - MTA is bound to a network interface\" \" \\\"$l_interfaces\\\"\")\n else\n a_output+=(\" - MTA is not bound to a non loopback network interface\" \" \\\"$l_interfaces\\\"\")\n fi\n else\n a_output+=(\" - MTA not detected or in use\")\n fi\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" * Reasons for audit failure *\" \"${a_output2[@]}\" \"\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "35ce05fe-51e1-5952-8ef3-8f3ce1a6d59c", + "benchmark-rule-id": "3.1.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_output=\"- IPv6 is not enabled\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_output=\"- IPv6 is not enabled\"\n fi\n [ -z \"$l_output\" ] && l_output=\"- IPv6 is enabled\"\n echo -e \"\\n$l_output\\n\"\n}\n" + }, + { + "uuid": "9e651bc7-0e69-5282-b693-74280e4283ab", + "benchmark-rule-id": "3.1.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n module_chk()\n {\n # Check how module will be loaded\n l_loadable=\"$(modprobe -n -v \"$l_mname\")\"\n if grep -Pq -- '^\\h*install \\/bin\\/(true|false)' <<< \"$l_loadable\"; then\n l_output=\"$l_output\\n - module: \\\"$l_mname\\\" is not loadable: \\\"$l_loadable\\\"\"\n else\n l_output2=\"$l_output2\\n - module: \\\"$l_mname\\\" is loadable: \\\"$l_loadable\\\"\"\n fi\n # Check is the module currently loaded\n if ! lsmod | grep \"$l_mname\" > /dev/null 2>&1; then\n l_output=\"$l_output\\n - module: \\\"$l_mname\\\" is not loaded\"\n else\n l_output2=\"$l_output2\\n - module: \\\"$l_mname\\\" is loaded\"\n fi\n # Check if the module is deny listed\n if modprobe --showconfig | grep -Pq -- \"^\\h*blacklist\\h+$l_mname\\b\"; then\n l_output=\"$l_output\\n - module: \\\"$l_mname\\\" is deny listed in: \\\"$(grep -Pl -- \"^\\h*blacklist\\h+$l_mname\\b\" /etc/modprobe.d/*)\\\"\"\n else\n l_output2=\"$l_output2\\n - module: \\\"$l_mname\\\" is not deny listed\"\n fi\n }\n if [ -n \"$(find /sys/class/net/*/ -type d -name wireless)\" ]; then\n l_dname=$(for driverdir in $(find /sys/class/net/*/ -type d -name wireless | xargs -0 dirname); do basename \"$(readlink -f \"$driverdir\"/device/driver/module)\";done | sort -u)\n for l_mname in $l_dname; do\n module_chk\n done\n fi\n # Report results. If no failures output in l_output2, we pass\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\"\n if [ -z \"$l_output\" ]; then\n echo -e \"\\n - System has no wireless NICs installed\"\n else\n echo -e \"\\n$l_output\\n\"\n fi\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Reason(s) for audit failure:\\n$l_output2\\n\"\n [ -n \"$l_output\" ] && echo -e \"\\n- Correctly set:\\n$l_output\\n\"\n fi\n}\n" + }, + { + "uuid": "b0610d33-17e2-54f6-baf0-e4f153daf639", + "benchmark-rule-id": "3.1.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server" + ], + "payload": "#!/usr/bin/env bash\n\n{\n module_fix()\n {\n if ! modprobe -n -v \"$l_mname\" | grep -P -- '^\\h*install \\/bin\\/(true|false)'; then\n echo -e \" - setting module: \\\"$l_mname\\\" to be un-loadable\"\n echo -e \"install $l_mname /bin/false\" >> /etc/modprobe.d/\"$l_mname\".conf\n fi\n if lsmod | grep \"$l_mname\" > /dev/null 2>&1; then\n echo -e \" - unloading module \\\"$l_mname\\\"\"\n modprobe -r \"$l_mname\"\n fi\n if ! grep -Pq -- \"^\\h*blacklist\\h+$l_mname\\b\" /etc/modprobe.d/*; then\n echo -e \" - deny listing \\\"$l_mname\\\"\"\n echo -e \"blacklist $l_mname\" >> /etc/modprobe.d/\"$l_mname\".conf\n fi\n }\n if [ -n \"$(find /sys/class/net/*/ -type d -name wireless)\" ]; then\n l_dname=$(for driverdir in $(find /sys/class/net/*/ -type d -name wireless | xargs -0 dirname); do basename \"$(readlink -f \"$driverdir\"/device/driver/module)\";done | sort -u)\n for l_mname in $l_dname; do\n module_fix\n done\n fi\n}\n" + }, + { + "uuid": "f1a41c54-bc9f-504f-b075-e2cd8bb131ff", + "benchmark-rule-id": "3.2.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"dccp\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "8c9d5948-9b3a-5f4f-8d87-a60b3f499dd4", + "benchmark-rule-id": "3.2.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"dccp\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "80674ce1-7db0-5b9b-8489-5d7b5f7c9ddc", + "benchmark-rule-id": "3.2.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"tipc\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "44b7611b-85d5-5912-9058-765642054385", + "benchmark-rule-id": "3.2.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"tipc\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "93112d9c-bc5d-5f96-a55b-9e8e5023ad15", + "benchmark-rule-id": "3.2.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"rds\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "63755a75-2942-5336-a9cd-158152c8ca3c", + "benchmark-rule-id": "3.2.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"rds\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "71f47127-8cb8-5f88-bebf-1f4f3ef548d2", + "benchmark-rule-id": "3.2.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"sctp\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "697a00ff-de05-500a-8baf-426d2495e1e8", + "benchmark-rule-id": "3.2.4", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"sctp\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "5f6dfcc0-f434-5370-9fb7-9309f8b0d29b", + "benchmark-rule-id": "3.3.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.ip_forward=0\" \"net.ipv6.conf.all.forwarding=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "6d244858-6161-5603-b5f7-5567ce6f99fa", + "benchmark-rule-id": "3.3.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.ip_forward=0\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "a3bb8a88-4be3-5fce-b2ea-764510548524", + "benchmark-rule-id": "3.3.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash \n\n{\n sysctl -w net.ipv6.conf.all.forwarding=0\n sysctl -w net.ipv6.route.flush=1\n}\n" + }, + { + "uuid": "aa90e493-a718-5f31-8913-ee44e5fd39ef", + "benchmark-rule-id": "3.3.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.send_redirects=0\" \"net.ipv4.conf.default.send_redirects=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "7208a9c6-a9b1-5cc5-98df-b8e88e7fcdfd", + "benchmark-rule-id": "3.3.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.send_redirects=0\n sysctl -w net.ipv4.conf.default.send_redirects=0\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "ad0a768a-96f8-5938-be98-2adcd49a818a", + "benchmark-rule-id": "3.3.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.icmp_ignore_bogus_error_responses=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "135d3426-68b3-5790-8329-51be5831b7fc", + "benchmark-rule-id": "3.3.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "ba866d9b-067b-5b88-8a2a-a6fb8b3f173b", + "benchmark-rule-id": "3.3.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.icmp_echo_ignore_broadcasts=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "70dee9ab-729f-5733-a03d-039f8b73aaf2", + "benchmark-rule-id": "3.3.4", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "25c99ca3-70ff-5bbd-9445-2511b7fbe624", + "benchmark-rule-id": "3.3.5", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.accept_redirects=0\" \"net.ipv4.conf.default.accept_redirects=0\" \"net.ipv6.conf.all.accept_redirects=0\" \"net.ipv6.conf.default.accept_redirects=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "22db20bb-1857-5322-920b-3c42c7c911b2", + "benchmark-rule-id": "3.3.5", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.accept_redirects=0\n sysctl -w net.ipv4.conf.default.accept_redirects=0\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "471e6433-ddff-5489-9e63-96666097c515", + "benchmark-rule-id": "3.3.5", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv6.conf.all.accept_redirects=0\n sysctl -w net.ipv6.conf.default.accept_redirects=0\n sysctl -w net.ipv6.route.flush=1\n}\n" + }, + { + "uuid": "c2e0c5fa-033d-5193-a0cd-1ca813a682f2", + "benchmark-rule-id": "3.3.6", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.secure_redirects=0\" \"net.ipv4.conf.default.secure_redirects=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "f1b19370-b924-549a-be69-d907b00416c4", + "benchmark-rule-id": "3.3.6", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.secure_redirects=0\n sysctl -w net.ipv4.conf.default.secure_redirects=0\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "13f5ad1f-b43c-5648-bd5e-b7a092e1dbb3", + "benchmark-rule-id": "3.3.7", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.rp_filter=1\" \"net.ipv4.conf.default.rp_filter=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "426aa349-18bb-525d-8dad-4df2a2c1d0c9", + "benchmark-rule-id": "3.3.7", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.rp_filter=1\n sysctl -w net.ipv4.conf.default.rp_filter=1\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "230b2d1e-bfc1-5f00-9f58-1ebc90c1c6b8", + "benchmark-rule-id": "3.3.8", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.accept_source_route=0\" \"net.ipv4.conf.default.accept_source_route=0\" \"net.ipv6.conf.all.accept_source_route=0\" \"net.ipv6.conf.default.accept_source_route=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "d28f90bf-5aa2-5124-ae6c-2847b4ce3928", + "benchmark-rule-id": "3.3.8", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.accept_source_route=0\n sysctl -w net.ipv4.conf.default.accept_source_route=0\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "66451270-1828-59cd-91ba-0edd06054d66", + "benchmark-rule-id": "3.3.8", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv6.conf.all.accept_source_route=0\n sysctl -w net.ipv6.conf.default.accept_source_route=0\n sysctl -w net.ipv6.route.flush=1\n}\n" + }, + { + "uuid": "1939088b-5e7c-57e2-bb20-110524508c59", + "benchmark-rule-id": "3.3.10", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.tcp_syncookies=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "be030aee-dab4-5398-a170-a2f3e111915a", + "benchmark-rule-id": "3.3.10", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.tcp_syncookies=1\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "436a4103-b731-5b77-9cf8-9b1f3847546d", + "benchmark-rule-id": "3.3.11", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv6.conf.all.accept_ra=0\" \"net.ipv6.conf.default.accept_ra=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "1fafe853-d9ab-51d6-8ea8-1a5ccd3a0926", + "benchmark-rule-id": "3.3.11", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv6.conf.all.accept_ra=0\n sysctl -w net.ipv6.conf.default.accept_ra=0\n sysctl -w net.ipv6.route.flush=1\n}\n" + }, + { + "uuid": "a6027e3e-0619-5b3a-bc76-0fbe2c3b5162", + "benchmark-rule-id": "6.1.3.7", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=()\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\")\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n for l_logfile in \"${a_config_files[@]}\"; do\n l_fail=\"$(grep -Psi -- '^\\h*module\\(load=\\\"?imtcp\\\"?\\)' \"$l_logfile\")\"\n [ -n \"$l_fail\" ] && a_output2+=(\"- Advanced format entry to accept incoming logs: \\\"$l_fail\\\"\" \"found in: \\\"$l_logfile\\\"\")\n l_fail=\"$(grep -Psi -- '^\\h*input\\(type=\\\"?imtcp\\\"?\\b' \"$l_logfile\")\"\n [ -n \"$l_fail\" ] && a_output2+=(\"- Advanced format entry to accept incoming logs: \\\"$l_fail\\\"\" \"found in: \\\"$l_logfile\\\"\")\n l_fail=\"$(grep -Psi -- '^\\h*module\\(load=\\\"?imtcp\\\"?\\)' \"$l_logfile\")\"\n [ -n \"$l_fail\" ] && a_output2+=(\"- Obsolete format entry to accept incoming logs: \\\"$l_fail\\\"\" \"found in: \\\"$l_logfile\\\"\")\n l_fail=\"$(grep -Psi -- '^\\h*input\\(type=\\\"?imtcp\\\"?\\b' \"$l_logfile\")\"\n [ -n \"$l_fail\" ] && a_output2+=(\"- Obsolete format entry to accept incoming logs: \\\"$l_fail\\\"\" \"found in: \\\"$l_logfile\\\"\")\n done\n if [ \"${#a_output2[@]}\" -le \"0\" ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \" - No entries to accept incoming logs found\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "1.1.1.1: Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\n\n1.1.1.2: Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\n\n1.1.1.3: Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\n\n1.1.1.4: Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\n\n1.1.1.5: Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\n\n1.1.1.6: The `overlayfs` has known CVE's: CVE-2023-32629, CVE-2023-2640, CVE-2023-0386. Disabling the `overlayfs` reduces the local attack surface by removing support for unnecessary filesystem types and mitigates potential risks associated with unauthorized execution of setuid files, enhancing the overall system security.\n\n1.1.1.7: Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\n\n1.1.1.8: Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.\n\n1.1.1.10: While loadable filesystem kernel modules are a convenient method of modifying the running kernel, this can be abused by attackers on a compromised system to prevent detection of their processes or files, allowing them to maintain control over the system. Many rootkits make use of loadable filesystem kernel modules in this way.\n\nRemoving support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it. The following filesystem kernel modules have known CVE's and should be made unavailable if no dependencies exist:\n\n- `afs` - CVE-2022-37402\n\n- `ceph` - CVE-2022-0670\n\n- `cifs` - CVE-2022-29869\n\n- `exfat` CVE-2022-29973\n\n- `ext` CVE-2022-1184\n\n- `fat` CVE-2022-22043\n\n- `fscache` CVE-2022-3630\n\n- `fuse` CVE-2023-0386\n\n- `gfs2` CVE-2023-3212\n\n- `nfs_common` CVE-2023-6660\n\n- `nfsd` CVE-2022-43945\n\n- `smbfs_common` CVE-2022-2585\n\n1.1.2.1.1: Making `/tmp` its own file system allows an administrator to set additional mount options such as the `noexec` option on the mount, making `/tmp` useless for an attacker to install executable code. It would also prevent an attacker from establishing a hard link to a system `setuid` program and wait for it to be updated. Once the program was updated, the hard link would be broken, and the attacker would have his own copy of the program. If the program happened to have a security vulnerability, the attacker could continue to exploit the known flaw.\n\nThis can be accomplished by either mounting `tmpfs` to `/tmp`, or creating a separate partition for `/tmp`.\n\n1.1.2.1.2: Since the `/tmp` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/tmp`.\n\n1.1.2.2.1: Making `/dev/shm` its own file system allows an administrator to set additional mount options such as the `noexec` option on the mount, making `/dev/shm` useless for an attacker to install executable code. It would also prevent an attacker from establishing a hard link to a system `setuid` program and wait for it to be updated. Once the program was updated, the hard link would be broken and the attacker would have his own copy of the program. If the program happened to have a security vulnerability, the attacker could continue to exploit the known flaw.\n\nThis can be accomplished by mounting `tmpfs` to `/dev/shm`.\n\n1.5.2: If one application is compromised, it would be possible for an attacker to attach to other running processes (e.g. Bash, Firefox, SSH sessions, GPG agent, etc) to extract additional credentials and continue to expand the scope of their attack.\n\nEnabling restricted mode will limit the ability of a compromised process to PTRACE_ATTACH on other processes running under the same user. With restricted mode, ptrace will continue to work with root user.\n\n1.5.5: Apport collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material.\n\n1.7.1: If a Graphical User Interface (GUI) is not required, it should be removed to reduce the attack surface of the system.\n\n1.7.10: XDMCP is inherently insecure.\n\n- XDMCP is not a ciphered protocol. This may allow an attacker to capture keystrokes entered by a user\n\n- XDMCP is vulnerable to man-in-the-middle attacks. This may allow an attacker to steal the credentials of legitimate users by impersonating the XDMCP server.\n\n2.1.2: Automatic discovery of network services is not normally required for system functionality. It is recommended to remove this package to reduce the potential attack surface.\n\n2.1.3: Unless a system is specifically set up to act as a DHCP server, it is recommended that this package be removed to reduce the potential attack surface.\n\n2.1.4: Unless a system is specifically designated to act as a DNS server, it is recommended that the package be deleted to reduce the potential attack surface.\n\n2.1.5: Unless a system is specifically designated to act as a DNS caching, DNS forwarding and/or DHCP server, it is recommended that the package be removed to reduce the potential attack surface.\n\n2.1.6: FTP does not protect the confidentiality of data or authentication credentials. It is recommended SFTP be used if file transfer is required. Unless there is a need to run the system as a FTP server (for example, to allow anonymous downloads), it is recommended that the package be deleted to reduce the potential attack surface.\n\n2.1.7: If the system will not need to act as an LDAP server, it is recommended that the software be removed to reduce the potential attack surface.\n\n2.1.8: Unless POP3 and/or IMAP servers are to be provided by this system, it is recommended that the package be removed to reduce the potential attack surface.\n\n**Note:** Several IMAP/POP3 servers exist and can use other service names. These should also be audited and the packages removed if not required.\n\n2.1.9: If the system does not export NFS shares, it is recommended that the `nfs-kernel-server` package be removed to reduce the remote attack surface.\n\n2.1.10: `ypserv.service` is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally has been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that `ypserv.service` be removed and other, more secure services be used\n\n2.1.11: If the system does not need to print jobs or accept print jobs from other systems, it is recommended that CUPS be removed to reduce the potential attack surface.\n\n2.1.12: A small request (~82 bytes via UDP) sent to the Portmapper generates a large response (7x to 28x amplification), which makes it a suitable tool for DDoS attacks. If `rpcbind` is not required, it is recommended to remove `rpcbind` package to reduce the potential attack surface.\n\n2.1.13: `rsync.service` presents a security risk as the `rsync` protocol is unencrypted.\n\nThe `rsync` package should be removed to reduce the attack area of the system.\n\n2.1.14: If there is no need to mount directories and file systems to Windows systems, then this service should be deleted to reduce the potential attack surface.\n\n2.1.15: The SNMP server can communicate using `SNMPv1`, which transmits data in the clear and does not require authentication to execute commands. `SNMPv3` replaces the simple/clear text password sharing used in `SNMPv2` with more securely encoded parameters. If the the SNMP service is not required, the `snmpd` package should be removed to reduce the attack surface of the system.\n\n**Note:** If SNMP is required:\n\n- The server should be configured for `SNMP v3` only. `User Authentication` and `Message Encryption` should be configured.\n\n- If `SNMP v2` is **absolutely** necessary, modify the community strings' values.\n\n2.1.16: Unless there is a need to run the system as a TFTP server, it is recommended that the package be removed to reduce the potential attack surface.\n\nTFTP does not have built-in encryption, access control or authentication. This makes it very easy for an attacker to exploit TFTP to gain access to files\n\n2.1.17: Unless a system is specifically set up to act as a proxy server, it is recommended that the squid package be removed to reduce the potential attack surface.\n\n**Note:** Several HTTP proxy servers exist. These should be checked and removed unless required.\n\n2.1.18: Unless there is a local site approved requirement to run a web server service on the system, web server packages should be removed to reduce the potential attack surface.\n\n2.1.19: If there are no `xinetd` services required, it is recommended that the package be removed to reduce the attack surface are of the system.\n\n**Note:** If an `xinetd` service or services are required, ensure that any `xinetd` service not required is stopped and masked\n\n2.1.20: Unless your organization specifically requires graphical login access via X Windows, remove it to reduce the potential attack surface.\n\n2.1.21: The software for all Mail Transfer Agents is complex and most have a long history of security issues. While it is important to ensure that the system can process local mail messages, it is not necessary to have the MTA's daemon listening on a port unless the server is intended to be a mail server that receives and processes mail from other systems.\n\n2.1.22: Services listening on the system pose a potential risk as an attack vector. These services should be reviewed, and if not required, the service should be stopped, and the package containing the service should be removed. If required packages have a dependency, the service should be stopped and masked to reduce the attack surface of the system.\n\n2.2.1: The NIS service is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally has been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that the service be removed.\n\n2.2.2: These legacy clients contain numerous security exposures and have been replaced with the more secure SSH package. Even if the server is removed, it is best to ensure the clients are also removed to prevent users from inadvertently attempting to use these commands and therefore exposing their credentials. Note that removing the `rsh-client` package removes the clients for `rsh` , `rcp` and `rlogin` .\n\n2.2.3: The software presents a security risk as it uses unencrypted protocols for communication.\n\n2.2.4: The `telnet` protocol is insecure and unencrypted. The use of an unencrypted transmission medium could allow an unauthorized user to steal credentials. The `ssh` package provides an encrypted session and stronger security and is included in most Linux distributions.\n\n2.2.5: If the system will not need to act as an LDAP client, it is recommended that the software be removed to reduce the potential attack surface.\n\n2.2.6: Unless there is a need to run the system using Internet standard File Transfer Protocol (for example, to allow anonymous downloads), it is recommended that the package be removed to reduce the potential attack surface.\n\n3.1.1: IETF RFC 4038 recommends that applications are built with an assumption of dual stack. It is recommended that IPv6 be enabled and configured in accordance with Benchmark recommendations.\n\n**- IF -** dual stack and IPv6 are not used in your environment, IPv6 may be disabled to reduce the attack surface of the system, and recommendations pertaining to IPv6 can be skipped.\n\n**Note:** It is recommended that IPv6 be enabled and configured unless this is against local site policy\n\n3.1.2: **-IF-** wireless is not to be used, wireless devices can be disabled to reduce the potential attack surface.\n\n3.1.3: An attacker may be able to find a way to access or corrupt your data. One example of this type of activity is `bluesnarfing`, which refers to attackers using a Bluetooth connection to steal information off of your Bluetooth device. Also, viruses or other malicious code can take advantage of Bluetooth technology to infect other devices. If you are infected, your data may be corrupted, compromised, stolen, or lost.\n\n3.2.1: **- IF -** the protocol is not required, it is recommended that the drivers not be installed to reduce the potential attack surface.\n\n3.2.2: **- IF -** the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface.\n\n3.2.3: **- IF -** the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface.\n\n3.2.4: **- IF -** the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface.\n\n3.3.1: Setting `net.ipv4.ip_forward` and `net.ipv6.conf.all.forwarding` to `0` ensures that a system with multiple interfaces (for example, a hard proxy), will never be able to forward packets, and therefore, never serve as a router.\n\n3.3.2: An attacker could use a compromised host to send invalid ICMP redirects to other router devices in an attempt to corrupt routing and have users access a system set up by the attacker as opposed to a valid system.\n\n3.3.3: Some routers (and some attackers) will send responses that violate RFC-1122 and attempt to fill up a log file system with many useless error messages.\n\n3.3.4: Accepting ICMP echo and timestamp requests with broadcast or multicast destinations for your network could be used to trick your host into starting (or participating) in a Smurf attack. A Smurf attack relies on an attacker sending large amounts of ICMP broadcast messages with a spoofed source address. All hosts receiving this message and responding would send echo-reply messages back to the spoofed address, which is probably not routable. If many hosts respond to the packets, the amount of traffic on the network could be significantly multiplied.\n\n3.3.5: ICMP redirect messages are packets that convey routing information and tell your host (acting as a router) to send packets via an alternate path. It is a way of allowing an outside routing device to update your system routing tables. By setting `net.ipv4.conf.all.accept_redirects`, `net.ipv4.conf.default.accept_redirects`, `net.ipv6.conf.all.accept_redirects`, and `net.ipv6.conf.default.accept_redirects` to `0`, the system will not accept any ICMP redirect messages, and therefore, won't allow outsiders to update the system's routing tables.\n\n3.3.6: It is still possible for even known gateways to be compromised. Setting `net.ipv4.conf.all.secure_redirects` and `net.ipv4.conf.default.secure_redirects` to `0` protects the system from routing table updates by possibly compromised known gateways.\n\n3.3.7: Setting `net.ipv4.conf.all.rp_filter` and `net.ipv4.conf.default.rp_filter` to `1` is a good way to deter attackers from sending your system bogus packets that cannot be responded to. One instance where this feature breaks down is if asymmetrical routing is employed. This would occur when using dynamic routing protocols (bgp, ospf, etc) on your system. If you are using asymmetrical routing on your system, you will not be able to enable this feature without breaking the routing.\n\n3.3.8: Setting `net.ipv4.conf.all.accept_source_route`, `net.ipv4.conf.default.accept_source_route`, `net.ipv6.conf.all.accept_source_route` and `net.ipv6.conf.default.accept_source_route` to `0` disables the system from accepting source routed packets. Assume this system was capable of routing packets to Internet routable addresses on one interface and private addresses on another interface. Assume that the private addresses were not routable to the Internet routable addresses and vice versa. Under normal routing circumstances, an attacker from the Internet routable addresses could not use the system as a way to reach the private address systems. If, however, source routed packets were allowed, they could be used to gain access to the private address systems as the route could be specified, rather than rely on routing protocols that did not allow this routing.\n\n3.3.10: Attackers use SYN flood attacks to perform a denial of service attacked on a system by sending many SYN packets without completing the three way handshake. This will quickly use up slots in the kernel's half-open connection queue and prevent legitimate connections from succeeding. Setting `net.ipv4.tcp_syncookies` to `1` enables SYN cookies, allowing the system to keep accepting valid connections, even if under a denial of service attack.\n\n3.3.11: It is recommended that systems do not accept router advertisements as they could be tricked into routing traffic to compromised machines. Setting hard routes within the system (usually a single default route to a trusted router) protects the system from bad routes. Setting `net.ipv6.conf.all.accept_ra` and `net.ipv6.conf.default.accept_ra` to `0` disables the system's ability to accept IPv6 router advertisements.\n\n5.1.8: Disable X11 forwarding unless there is an operational requirement to use X11 applications directly. There is a small risk that the remote X11 servers of users who are logged in via SSH with X11 forwarding could be compromised by other users on the X11 server. Note that even if X11 forwarding is disabled, users can always install their own forwarders.\n\nanyone with root privilege on the the intermediate server can make free use of ssh-agent to authenticate them to other servers\n\nLeaving port forwarding enabled can expose the organization to security risks and backdoors. SSH connections are protected with strong encryption. This makes their contents invisible to most deployed network monitoring and traffic filtering solutions. This invisibility carries considerable risk potential if it is used for malicious purposes such as data exfiltration. Cybercriminals or malware could exploit SSH to hide their unauthorized communications, or to exfiltrate stolen data from the target network.\n\n6.1.2.1.4: If a client is configured to also receive data, thus turning it into a server, the client system is acting outside it's operational boundary.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used.\n\n6.1.3.7: If a client is configured to also receive data, thus turning it into a server, the client system is acting outside its operational boundary.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "7aa9e790-b12e-5e68-b700-7728e0cdcdb5", + "control-id": "cisc-005.002", + "description": "5.1.9 Ensure sshd GSSAPIAuthentication is disabled; 5.1.11 Ensure sshd IgnoreRhosts is enabled; 5.1.19 Ensure sshd PermitEmptyPasswords is disabled; 5.1.22 Ensure sshd UsePAM is enabled; 5.3.2.3 Ensure pam_pwquality module is enabled; 5.3.2.4 Ensure pam_pwhistory module is enabled; 5.3.3.2.1 Ensure password number of changed characters is configured; 5.3.3.2.2 Ensure minimum password length is configured; 5.3.3.2.3 Ensure password complexity is configured; 5.3.3.2.4 Ensure password same consecutive characters is configured; 5.3.3.2.5 Ensure password maximum sequential characters is configured; 5.3.3.2.6 Ensure password dictionary check is enabled; 5.3.3.2.7 Ensure password quality checking is enforced; 5.3.3.2.8 Ensure password quality is enforced for the root user; 5.3.3.3.1 Ensure password history remember is configured; 5.3.3.3.2 Ensure password history is enforced for the root user; 5.3.3.4.1 Ensure pam_unix does not include nullok; 5.3.3.4.2 Ensure pam_unix does not include remember; 5.4.1.1 Ensure password expiration is configured; 5.4.1.2 Ensure minimum password days is configured; 5.4.1.5 Ensure inactive password lock is configured; 5.4.1.6 Ensure all users last password change date is in the past; 7.2.2 Ensure /etc/shadow password fields are not empty", + "automation-scripts": [ + { + "uuid": "5e4e0e5c-1b5a-5860-b172-276df338bf63", + "benchmark-rule-id": "5.3.2.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n arr=('Name: Pwquality password strength checking' 'Default: yes' 'Priority: 1024' 'Conflicts: cracklib' 'Password-Type: Primary' 'Password:' ' requisite pam_pwquality.so retry=3')\n printf '%s\\n' \"${arr[@]}\" > /usr/share/pam-configs/pwquality\n}\n" + }, + { + "uuid": "75e33fb0-7073-54c3-9918-1a7e2da3536a", + "benchmark-rule-id": "5.3.2.4", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n arr=('Name: pwhistory password history checking' 'Default: yes' 'Priority: 1024' 'Password-Type: Primary' 'Password:' ' requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok')\n printf '%s\\n' \"${arr[@]}\" > /usr/share/pam-configs/pwhistory\n}\n" + }, + { + "uuid": "81745ef9-766b-5cb8-b295-9820281746e1", + "benchmark-rule-id": "5.3.3.2.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*difok\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"difok = 2\" > /etc/security/pwquality.conf.d/50-pwdifok.conf\n}\n" + }, + { + "uuid": "0b6a0628-992a-572a-a502-4f1ad61d75c0", + "benchmark-rule-id": "5.3.3.2.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*minlen\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"minlen = 14\" > /etc/security/pwquality.conf.d/50-pwlength.conf\n}\n" + }, + { + "uuid": "0dbb9d6a-4dfd-5c6e-996c-122be0304c33", + "benchmark-rule-id": "5.3.3.2.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*minclass\\s*=/# &/' /etc/security/pwquality.conf\n sed -ri 's/^\\s*[dulo]credit\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"minclass = 3\" > /etc/security/pwquality.conf.d/50-pwcomplexity.conf\n}\n" + }, + { + "uuid": "300f0ca8-bd86-5969-a344-e591029a16c2", + "benchmark-rule-id": "5.3.3.2.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*minclass\\s*=/# &/' /etc/security/pwquality.conf\n sed -ri 's/^\\s*[dulo]credit\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '%s\\n' \"dcredit = -1\" \"ucredit = -1\" \"lcredit = -1\" > /etc/security/pwquality.conf.d/50-pwcomplexity.conf\n}\n" + }, + { + "uuid": "645c8315-80e0-5262-9044-bb9a46c4fdd7", + "benchmark-rule-id": "5.3.3.2.4", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*maxrepeat\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"maxrepeat = 3\" > /etc/security/pwquality.conf.d/50-pwrepeat.conf\n}\n" + }, + { + "uuid": "bf6446c3-f9fe-5123-9ea4-84eff9c5ba92", + "benchmark-rule-id": "5.3.3.2.5", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*maxsequence\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"maxsequence = 3\" > /etc/security/pwquality.conf.d/50-pwmaxsequence.conf\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "5.1.9: Allowing GSSAPI authentication through SSH exposes the system's GSSAPI to remote hosts, and should be disabled to reduce the attack surface of the system\n\n5.1.11: Setting this parameter forces users to enter a password when authenticating with SSH.\n\n5.1.19: Disallowing remote shell access to accounts that have an empty password reduces the probability of unauthorized access to the system.\n\n5.1.22: When `usePAM` is set to `yes`, PAM runs through account and session types properly. This is important if you want to restrict access to services based off of IP, time or other factors of the account. Additionally, you can make sure users inherit certain environment variables on login or disallow access to the server\n\n5.3.2.3: Use of a unique, complex passwords helps to increase the time and resources required to compromise the password.\n\n5.3.2.4: Use of a unique, complex passwords helps to increase the time and resources required to compromise the password.\n\n5.3.3.2.1: Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.\n\n5.3.3.2.2: Strong passwords help protect systems from password attacks. Types of password attacks include dictionary attacks, which attempt to use common words and phrases, and brute force attacks, which try every possible combination of characters. Also attackers may try to obtain the account database so they can use tools to discover the accounts and passwords.\n\n5.3.3.2.3: Strong passwords protect systems from being hacked through brute force methods.\n\nRequiring at least one non-alphabetic character increases the search space beyond pure dictionary words, which makes the resulting password harder to crack.\n\nForcing users to choose an excessively complex password, e.g. some combination of upper-case, lower-case, numbers, and special characters, has a negative impact. It places an extra burden on users and many will use predictable patterns (for example, a capital letter in the first position, followed by lowercase letters, then one or two numbers, and a “special character” at the end). Attackers know this, so dictionary attacks will often contain these common patterns and use the most common substitutions like, $ for s, @ for a, 1 for l, 0 for o.\n\n5.3.3.2.4: Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.\n\n5.3.3.2.5: Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.\n\n5.3.3.2.6: If the operating system allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity for successful guesses, and brute-force attacks.\n\n5.3.3.2.7: Strong passwords help protect systems from password attacks. Types of password attacks include dictionary attacks, which attempt to use common words and phrases, and brute force attacks, which try every possible combination of characters. Also attackers may try to obtain the account database so they can use tools to discover the accounts and passwords.\n\n5.3.3.2.8: Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.\n\n5.3.3.3.1: Requiring users not to reuse their passwords make it less likely that an attacker will be able to guess the password or use a compromised password.\n\n**Note:** These change only apply to accounts configured on the local system.\n\n5.3.3.3.2: Requiring users not to reuse their passwords make it less likely that an attacker will be able to guess the password or use a compromised password\n\n**Note:** These change only apply to accounts configured on the local system.\n\n5.3.3.4.1: Using a strong password is essential to helping protect personal and sensitive information from unauthorized access\n\n5.3.3.4.2: The `remember=n` argument should be removed to ensure a strong password hashing algorithm is being used. A stronger hash provides additional protection to the system by increasing the level of effort needed for an attacker to successfully determine local user's old passwords stored in `/etc/security/opasswd`.\n\n5.4.1.1: The window of opportunity for an attacker to leverage compromised credentials or successfully compromise credentials via an online brute force attack is limited by the age of the password. Therefore, reducing the maximum age of a password also reduces an attacker's window of opportunity.\n\nWe recommend a yearly password change. This is primarily because for all their good intentions users will share credentials across accounts. Therefore, even if a breach is publicly identified, the user may not see this notification, or forget they have an account on that site. This could leave a shared credential vulnerable indefinitely. Having an organizational policy of a 1-year (annual) password expiration is a reasonable compromise to mitigate this with minimal user burden.\n\n5.4.1.2: Users may have favorite passwords that they like to use because they are easy to remember and they believe that their password choice is secure from compromise. Unfortunately, passwords are compromised and if an attacker is targeting a specific individual user account, with foreknowledge of data about that user, reuse of old, potentially compromised passwords, may cause a security breach.\n\nBy restricting the frequency of password changes, an administrator can prevent users from repeatedly changing their password in an attempt to circumvent password reuse controls\n\n5.4.1.5: Inactive accounts pose a threat to system security since the users are not logging in to notice failed login attempts or other anomalies.\n\n5.4.1.6: If a user's recorded password change date is in the future, then they could bypass any set password expiration.\n\n7.2.2: All accounts must have passwords or be locked to prevent the account from being used by an unauthorized user.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "ed97669c-67ef-573e-8edf-18f5d7914846", + "control-id": "cisc-005.004", + "description": "5.1.20 Ensure sshd PermitRootLogin is disabled; 5.2.1 Ensure sudo is installed; 5.2.2 Ensure sudo commands use pty; 5.2.4 Ensure users must provide password for privilege escalation; 5.2.5 Ensure re-authentication for privilege escalation is not disabled globally; 5.2.6 Ensure sudo authentication timeout is configured correctly", + "props": [ + { + "name": "rationale", + "value": "5.1.20: Disallowing `root` logins over SSH requires system admins to authenticate using their own individual account, then escalating to `root`. This limits opportunity for non-repudiation and provides a clear audit trail in the event of a security incident.\n\n5.2.1: `sudo` supports a plug-in architecture for security policies and input/output logging. Third parties can develop and distribute their own policy and I/O logging plug-ins to work seamlessly with the `sudo` front end. The default security policy is `sudoers`, which is configured via the file `/etc/sudoers` and any entries in `/etc/sudoers.d`.\n\nThe security policy determines what privileges, if any, a user has to run `sudo`. The policy may require that users authenticate themselves with a password or another authentication mechanism. If authentication is required, `sudo` will exit if the user's password is not entered within a configurable time limit. This limit is policy-specific.\n\n5.2.2: Attackers can run a malicious program using `sudo` which would fork a background process that remains even when the main program has finished executing.\n\n5.2.4: Without (re-)authentication, users may access resources or perform tasks for which they do not have authorization.\n\nWhen operating systems provide the capability to escalate a functional capability, it is critical the user (re-)authenticate.\n\n5.2.5: Without re-authentication, users may access resources or perform tasks for which they do not have authorization.\n\nWhen operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate.\n\n5.2.6: Setting a timeout value reduces the window of opportunity for unauthorized privileged access to another user.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "1f98df6b-b249-5e5b-ba40-55c3c8a342b9", + "control-id": "cisc-006.002", + "description": "5.3.2.2 Ensure pam_faillock module is enabled; 5.3.3.1.1 Ensure password failed attempts lockout is configured; 5.3.3.1.2 Ensure password unlock time is configured; 5.3.3.1.3 Ensure password failed attempts lockout includes root account", + "automation-scripts": [ + { + "uuid": "57c02c6c-69e1-5880-a95a-1ebbc5b02b8a", + "benchmark-rule-id": "5.3.2.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n arr=('Name: Enable pam_faillock to deny access' 'Default: yes' 'Priority: 0' 'Auth-Type: Primary' 'Auth:' ' [default=die] pam_faillock.so authfail') \n printf '%s\\n' \"${arr[@]}\" > /usr/share/pam-configs/faillock\n}\n" + }, + { + "uuid": "27684fb5-9626-5ffd-8053-16b85711dafd", + "benchmark-rule-id": "5.3.2.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n arr=('Name: Notify of failed login attempts and reset count upon success' 'Default: yes' 'Priority: 1024' 'Auth-Type: Primary' 'Auth:' ' requisite pam_faillock.so preauth' 'Account-Type: Primary' 'Account:' ' required pam_faillock.so') \n printf '%s\\n' \"${arr[@]}\" > /usr/share/pam-configs/faillock_notify\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "5.3.2.2: Locking out user IDs after n unsuccessful consecutive login attempts mitigates brute force password attacks against your systems.\n\n5.3.3.1.1: Locking out user IDs after *n* unsuccessful consecutive login attempts mitigates brute force password attacks against your systems.\n\n5.3.3.1.2: Locking out user IDs after *n* unsuccessful consecutive login attempts mitigates brute force password attacks against your systems.\n\n5.3.3.1.3: Locking out user IDs after n unsuccessful consecutive login attempts mitigates brute force password attacks against your systems.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "2ae47f55-5378-54f6-902c-5374c0c7161e", + "control-id": "cisc-007.003", + "description": "1.2.1.1 Ensure GPG keys are configured; 1.2.1.2 Ensure package manager repositories are configured; 1.2.2.1 Ensure updates, patches, and additional security software are installed", + "props": [ + { + "name": "rationale", + "value": "1.2.1.1: It is important to ensure that updates are obtained from a valid source to protect against spoofing that could lead to the inadvertent installation of malware on the system.\n\n1.2.1.2: If a system's package repositories are misconfigured important patches may not be identified or a rogue repository could introduce compromised software.\n\n1.2.2.1: Newer patches may contain security enhancements that would not be available through the latest full update. As a result, it is recommended that the latest software patches be used to take advantage of the latest functionality. As with any software installation, organizations need to determine if a given update meets their requirements and verify the compatibility and supportability of any additional software against the update revision that is selected.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "89fbf1bd-ce58-5c32-887d-0e9b939099ec", + "control-id": "cisc-007.004", + "description": "1.2.1.1 Ensure GPG keys are configured; 1.2.1.2 Ensure package manager repositories are configured; 1.2.2.1 Ensure updates, patches, and additional security software are installed", + "props": [ + { + "name": "rationale", + "value": "1.2.1.1: It is important to ensure that updates are obtained from a valid source to protect against spoofing that could lead to the inadvertent installation of malware on the system.\n\n1.2.1.2: If a system's package repositories are misconfigured important patches may not be identified or a rogue repository could introduce compromised software.\n\n1.2.2.1: Newer patches may contain security enhancements that would not be available through the latest full update. As a result, it is recommended that the latest software patches be used to take advantage of the latest functionality. As with any software installation, organizations need to determine if a given update meets their requirements and verify the compatibility and supportability of any additional software against the update revision that is selected.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "0e94fd11-210f-5a23-bace-e5ca956e3d57", + "control-id": "cisc-008.002", + "description": "5.1.14 Ensure sshd LogLevel is configured; 6.1.1.1 Ensure journald service is enabled and active; 6.1.1.3 Ensure journald log file rotation is configured; 6.1.2.2 Ensure journald ForwardToSyslog is disabled; 6.1.2.3 Ensure journald Compress is configured; 6.1.2.4 Ensure journald Storage is configured; 6.1.2.1.1 Ensure systemd-journal-remote is installed; 6.1.2.1.2 Ensure systemd-journal-upload authentication is configured; 6.1.2.1.3 Ensure systemd-journal-upload is enabled and active; 6.1.3.1 Ensure rsyslog is installed; 6.1.3.2 Ensure rsyslog service is enabled and active; 6.1.3.3 Ensure journald is configured to send logs to rsyslog; 6.1.3.4 Ensure rsyslog log file creation mode is configured; 6.1.3.5 Ensure rsyslog logging is configured; 6.1.3.6 Ensure rsyslog is configured to send logs to a remote log host; 6.2.1.2 Ensure auditd service is enabled and active; 6.2.1.3 Ensure auditing for processes that start prior to auditd is enabled; 6.2.1.4 Ensure audit_backlog_limit is sufficient; 6.2.2.3 Ensure system is disabled when audit logs are full; 6.2.2.4 Ensure system warns when audit logs are low on space; 6.2.3.15 Ensure successful and unsuccessful attempts to use the chcon command are collected; 6.2.3.16 Ensure successful and unsuccessful attempts to use the setfacl command are collected; 6.2.3.17 Ensure successful and unsuccessful attempts to use the chacl command are collected; 6.2.3.18 Ensure successful and unsuccessful attempts to use the usermod command are collected", + "automation-scripts": [ + { + "uuid": "e05259b5-b903-5f7a-b223-4e092be2b52a", + "benchmark-rule-id": "6.1.1.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"SystemMaxUse=^.+$\" \"SystemKeepFree=^.+$\" \"RuntimeMaxUse=^.+$\" \"RuntimeKeepFree=^.+$\" \"MaxFileSec=^.+$\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: ***\" \" \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "1510de9e-6752-57c9-a0b8-d5bc2bacff89", + "benchmark-rule-id": "6.1.2.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"ForwardToSyslog=no\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "d2159c0d-c9fe-5398-891a-6079ad29657f", + "benchmark-rule-id": "6.1.2.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_settings=(\"ForwardToSyslog=no\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n" + }, + { + "uuid": "c93f7336-1b70-50e1-8dd0-507b449c8755", + "benchmark-rule-id": "6.1.2.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"Compress=yes\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "f6116ea4-62d3-548c-b72a-4effec43ec05", + "benchmark-rule-id": "6.1.2.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_settings=(\"Compress=yes\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n" + }, + { + "uuid": "22f18222-c5c5-5b9b-87f7-fe2a6995d283", + "benchmark-rule-id": "6.1.2.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"Storage=persistent\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "cdc7c4c5-755f-5c92-841c-c6906cb9b72d", + "benchmark-rule-id": "6.1.2.4", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_settings=(\"Storage=persistent\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n" + }, + { + "uuid": "0e388c60-876d-5214-b4a0-5a627e9396c0", + "benchmark-rule-id": "6.1.2.1.2", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journal-upload.conf\"\n a_parameters=(\"URL=^.+$\" \"ServerKeyFile=^.+$\" \"ServerCertificateFile=^.+$\" \"TrustedCertificateFile=^.+$\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: ***\" \" \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "27b94633-9047-56e0-9f4a-2e942226a1b3", + "benchmark-rule-id": "6.1.2.1.2", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_settings=(\"URL=192.168.50.42\" \"ServerKeyFile=/etc/ssl/private/journal-upload.pem\" \\\n \"ServerCertificateFile=/etc/ssl/certs/journal-upload.pem\" \"TrustedCertificateFile=/etc/ssl/ca/trusted.pem\")\n [ ! -d /etc/systemd/journal-upload.conf.d/ ] && mkdir /etc/systemd/journal-upload.conf.d/\n if grep -Psq -- '^\\h*\\[Upload\\]' /etc/systemd/journal-upload.conf.d/60-journald_upload.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journal-upload.conf.d/60-journald_upload.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journal-upload.conf.d/60-journald_upload.conf\n fi\n}\n" + }, + { + "uuid": "2fe8b1e6-9a68-5da5-bf2e-9ae8c1a2f652", + "benchmark-rule-id": "6.1.3.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"ForwardToSyslog=yes\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "2e39f74d-eb3c-500a-a66a-b830bd3ebf66", + "benchmark-rule-id": "6.1.3.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_settings=(\"ForwardToSyslog=yes\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n" + }, + { + "uuid": "e84891bf-8bce-5836-9a14-03a5dbf69db1", + "benchmark-rule-id": "6.1.3.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\"\n l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\") l_parameter_name='\\$FileCreateMode'\n f_parameter_chk()\n {\n l_perm_mask=\"0137\"; l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n l_mode=\"$(awk '{print $2}' <<< \"$l_used_parameter_setting\" | xargs)\"\n if [ $(( $l_mode & $l_perm_mask )) -gt 0 ]; then\n a_output2+=(\" - Parameter: \\\"${l_parameter_name//\\\\/}\\\" is incorrectly set to mode: \\\"$l_file_mode\\\"\" \\\n \" in the file: \\\"$l_file\\\"\" \" Should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n else\n a_output+=(\" - Parameter: \\\"${l_parameter_name//\\\\/}\\\" is correctly set to mode: \\\"$l_file_mode\\\"\" \\\n \" in the file: \\\"$l_file\\\"\" \" Should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n fi\n }\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[*]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n\n if [ -n \"$l_used_parameter_setting\" ]; then\n f_parameter_chk\n else\n a_output2+=(\" - Parameter: \\\"${l_parameter_name//\\\\/}\\\" is not set in a configuration file\" \\\n \" *** Note: \\\"${l_parameter_name//\\\\/}\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "d5e56089-f79c-5071-b3cb-4095416232f6", + "benchmark-rule-id": "6.1.3.4", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n [ ! -d \"/etc/rsyslog.d/\" ] && mkdir /etc/rsyslog.d/\n printf '%s\\n' \"\" \"\\$FileCreateMode 0640\" >> /etc/rsyslog.d/60-rsyslog.conf\n}\n" + }, + { + "uuid": "d7dfdaaa-4994-50f4-b6c1-acc3c49f6fd9", + "benchmark-rule-id": "6.1.3.5", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\")\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n for l_logfile in \"${a_config_files[@]}\"; do\n grep -PHs -- '^\\h*[^#\\n\\r\\/:]+\\/var\\/log\\/.*$' \"$l_logfile\"\n done\n}\n" + }, + { + "uuid": "0732c2cd-54d3-5ce9-ac0f-575d5329cfcc", + "benchmark-rule-id": "6.1.3.6", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\")\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n for l_logfile in \"${a_config_files[@]}\"; do\n grep -Hs -- \"^*.*[^I][^I]*@\" \"$l_logfile\"\n done\n}\n" + }, + { + "uuid": "54cba5f5-8e5b-53c9-8fa7-52f922d11266", + "benchmark-rule-id": "6.1.3.6", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\")\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n for l_logfile in \"${a_config_files[@]}\"; do\n grep -PHsi -- '^\\s*([^#]+\\s+)?action\\(([^#]+\\s+)?\\btarget=\\\"?[^#\"]+\\\"?\\b' \"$l_logfile\"\n done\n}\n" + }, + { + "uuid": "a073d16b-4874-5947-99b7-4d50df37d4ee", + "benchmark-rule-id": "6.1.3.6", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_parameters=('*.* action(type=\"omfwd\" target=\"loghost.example.com\" port=\"514\" protocol=\"tcp\"' \\\n ' action.resumeRetryCount=\"100\"' ' queue.type=\"LinkedList\" queue.size=\"1000\")')\n [ ! -d \"/etc/rsyslog.d/\" ] && mkdir /etc/rsyslod.d/\n printf '%s\\n' \"\" \"${a_parameters[@]}\" >> /etc/rsyslog.d/60-rsyslog.conf\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "5.1.14: The `INFO` level is the basic level that only records login activity of SSH users. In many situations, such as Incident Response, it is important to determine when a particular user was active on a system. The logout record can eliminate those users who disconnected, which helps narrow the field.\n\nThe `VERBOSE` level specifies that login and logout activity as well as the key fingerprint for any SSH key used for login will be logged. This information is important for SSH key management, especially in legacy environments.\n\n6.1.1.1: If the `systemd-journald` service is not enabled to start on boot, the system will not capture logging events.\n\n6.1.1.3: By keeping the log files smaller and more manageable, a system administrator can easily archive these files to another system and spend less time looking through inordinately large log files.\n\n6.1.2.2: **- IF -** `journald` is the method for capturing logs, all logs of the system should be handled by `journald` and not forwarded to other logging mechanisms.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used.\n\n6.1.2.3: Uncompressed large files may unexpectedly fill a filesystem leading to resource unavailability. Compressing logs prior to write can prevent sudden, unexpected filesystem impacts.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used.\n\n6.1.2.4: Writing log data to disk will provide the ability to forensically reconstruct events which may have impacted the operations or security of a system even after a system crash or reboot.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used.\n\n6.1.2.1.1: Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local system.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used.\n\n6.1.2.1.2: Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local system.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used.\n\n6.1.2.1.3: Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local system.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used.\n\n6.1.3.1: The security enhancements of `rsyslog` such as connection-oriented (i.e. TCP) transmission of logs, the option to log to database formats, and the encryption of log data en route to a central logging server) justify installing and configuring the package.\n\n6.1.3.2: If the `rsyslog` service is not enabled to start on boot, the system will not capture logging events.\n\n6.1.3.3: **- IF -** `rsyslog` is the preferred method for capturing logs, all logs of the system should be sent to it for further processing.\n\n**Note:** This recommendation **only applies if `rsyslog` is the chosen method for client side logging**. Do not apply this recommendation if `systemd-journald` is used.\n\n6.1.3.4: It is important to ensure that log files have the correct permissions to ensure that sensitive data is archived and protected.\n\n6.1.3.5: A great deal of important security-related information is sent via `rsyslog` (e.g., successful and failed su attempts, failed login attempts, root login attempts, etc.).\n\n6.1.3.6: Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local system.\n\n6.2.1.2: The capturing of system events provides system administrators with information to allow them to determine if unauthorized access to their system is occurring.\n\n6.2.1.3: Audit events need to be captured on processes that start up prior to `auditd` , so that potential malicious activity cannot go undetected.\n\n6.2.1.4: If an audit event is logged which would grow the queue beyond the `audit_backlog_limit`, then a failure occurs, auditd records will be lost, and potential malicious activity could go undetected.\n\n6.2.2.3: In high security contexts, the risk of detecting unauthorized access or nonrepudiation exceeds the benefit of the system's availability.\n\n6.2.2.4: In high security contexts, the risk of detecting unauthorized access or nonrepudiation exceeds the benefit of the system's availability.\n\n6.2.3.15: The `chcon` command is used to change file security context. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\n6.2.3.16: This utility sets Access Control Lists (ACLs) of files and directories. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\n6.2.3.17: `chacl` changes the ACL(s) for a file or directory. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\n6.2.3.18: The `usermod` command modifies the system account files to reflect the changes that are specified on the command line. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter).", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "17665183-9a21-5f4a-8bae-08c496c01749", + "control-id": "cisc-008.003", + "description": "1.1.2.6.1 Ensure separate partition exists for /var/log; 1.1.2.7.1 Ensure separate partition exists for /var/log/audit; 6.1.2.3 Ensure journald Compress is configured; 6.1.3.8 Ensure logrotate is configured; 6.2.2.1 Ensure audit log storage size is configured; 6.2.2.2 Ensure audit logs are not automatically deleted; 6.2.2.3 Ensure system is disabled when audit logs are full; 6.2.2.4 Ensure system warns when audit logs are low on space", + "automation-scripts": [ + { + "uuid": "650daa8e-2452-51f5-975a-f7fef04b1203", + "benchmark-rule-id": "6.1.2.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"Compress=yes\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "85c37e02-cde7-5b0d-87f7-f6fcd07da93b", + "benchmark-rule-id": "6.1.2.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_settings=(\"Compress=yes\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n" + }, + { + "uuid": "1d4e90ea-b797-5264-afc2-72c7db20a972", + "benchmark-rule-id": "6.1.3.8", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_config_file=\"/etc/logrotate.conf\"\n l_include=\"$(awk '$1~/^\\s*include$/{print$2}' \"$l_config_file\" 2>/dev/null)\"\n [ -d \"$l_include\" ] && l_include=\"$l_include/*\"\n $l_analyze_cmd cat-config \"$l_config_file\" $l_include\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "1.1.2.6.1: The default installation only creates a single `/` partition. Since the `/var/log` directory contains log files which can grow quite large, there is a risk of resource exhaustion. It will essentially have the whole disk available to fill up and impact the system as a whole.\n\nConfiguring `/var/log` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attackers ability to create exploits on the system. Other options allow for specific behavior. See `man mount` for exact details regarding filesystem-independent and filesystem-specific options.\n\nAs `/var/log` contains log files, care should be taken to ensure the security and integrity of the data and mount point.\n\n1.1.2.7.1: The default installation only creates a single `/` partition. Since the `/var/log/audit` directory contains the `audit.log` file which can grow quite large, there is a risk of resource exhaustion. It will essentially have the whole disk available to fill up and impact the system as a whole. In addition, other operations on the system could fill up the disk unrelated to `/var/log/audit` and cause `auditd` to trigger its `space_left_action` as the disk is full. See `man auditd.conf` for details.\n\nConfiguring `/var/log/audit` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attacker's ability to create exploits on the system. Other options allow for specific behavior. See `man mount` for exact details regarding filesystem-independent and filesystem-specific options.\n\nAs `/var/log/audit` contains audit logs, care should be taken to ensure the security and integrity of the data and mount point.\n\n6.1.2.3: Uncompressed large files may unexpectedly fill a filesystem leading to resource unavailability. Compressing logs prior to write can prevent sudden, unexpected filesystem impacts.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used.\n\n6.1.3.8: By keeping the log files smaller and more manageable, a system administrator can easily archive these files to another system and spend less time looking through inordinately large log files.\n\n6.2.2.1: It is important that an appropriate size is determined for log files so that they do not impact the system and audit data is not lost.\n\n6.2.2.2: In high security contexts, the benefits of maintaining a long audit history exceed the cost of storing the audit history.\n\n6.2.2.3: In high security contexts, the risk of detecting unauthorized access or nonrepudiation exceeds the benefit of the system's availability.\n\n6.2.2.4: In high security contexts, the risk of detecting unauthorized access or nonrepudiation exceeds the benefit of the system's availability.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "d502334c-68cf-51fc-aad4-a5c3a3144840", + "control-id": "cisc-008.004", + "description": "2.3.1.1 Ensure a single time synchronization daemon is in use; 2.3.2.1 Ensure systemd-timesyncd configured with authorized timeserver; 2.3.2.2 Ensure systemd-timesyncd is enabled and running; 2.3.3.1 Ensure chrony is configured with authorized timeserver; 2.3.3.2 Ensure chrony is running as user _chrony; 2.3.3.3 Ensure chrony is enabled and running", + "automation-scripts": [ + { + "uuid": "c06abf22-3ae4-551d-80ed-c026695b8fb9", + "benchmark-rule-id": "2.3.1.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n service_not_enabled_chk()\n {\n l_out2=\"\"\n if systemctl is-enabled \"$l_service_name\" 2>/dev/null | grep -q 'enabled'; then\n l_out2=\"$l_out2\\n - Daemon: \\\"$l_service_name\\\" is enabled on the system\"\n fi\n if systemctl is-active \"$l_service_name\" 2>/dev/null | grep -q '^active'; then\n l_out2=\"$l_out2\\n - Daemon: \\\"$l_service_name\\\" is active on the system\"\n fi\n } \n l_service_name=\"systemd-timesyncd.service\" # Check systemd-timesyncd daemon\n service_not_enabled_chk\n if [ -n \"$l_out2\" ]; then\n l_timesyncd=\"y\"\n l_out_tsd=\"$l_out2\"\n else\n l_timesyncd=\"n\"\n l_out_tsd=\"\\n - Daemon: \\\"$l_service_name\\\" is not enabled and not active on the system\"\n fi\n l_service_name=\"chrony.service\" # Check chrony\n service_not_enabled_chk\n if [ -n \"$l_out2\" ]; then\n l_chrony=\"y\"\n l_out_chrony=\"$l_out2\"\n else\n l_chrony=\"n\"\n l_out_chrony=\"\\n - Daemon: \\\"$l_service_name\\\" is not enabled and not active on the system\"\n fi\n l_status=\"$l_timesyncd$l_chrony\"\n case \"$l_status\" in\n yy)\n l_output2=\" - More than one time sync daemon is in use on the system$l_out_tsd$l_out_chrony\"\n ;;\n nn)\n l_output2=\" - No time sync daemon is in use on the system$l_out_tsd$l_out_chrony\"\n ;;\n yn|ny)\n l_output=\" - Only one time sync daemon is in use on the system$l_out_tsd$l_out_chrony\"\n ;;\n *)\n l_output2=\" - Unable to determine time sync daemon(s) status\"\n ;;\n esac\n\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\\n\"\n fi\n}\n" + }, + { + "uuid": "dd795a67-508e-5cda-962d-525dcba33878", + "benchmark-rule-id": "2.3.2.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_parlist=(\"NTP=[^#\\n\\r]+\" \"FallbackNTP=[^#\\n\\r]+\")\n l_systemd_config_file=\"/etc/systemd/timesyncd.conf\" # Main systemd configuration file\n f_config_file_parameter_chk()\n {\n unset A_out; declare -A A_out # Check config file(s) setting\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_systemd_parameter=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n grep -Piq -- \"^\\h*$l_systemd_parameter_name\\b\" <<< \"$l_systemd_parameter\" && A_out+=([\"$l_systemd_parameter\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdanalyze\" cat-config \"$l_systemd_config_file\" | grep -Pio '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_systemd_file_parameter_name l_systemd_file_parameter_value; do\n l_systemd_file_parameter_name=\"${l_systemd_file_parameter_name// /}\"\n l_systemd_file_parameter_value=\"${l_systemd_file_parameter_value// /}\"\n if grep -Piq \"\\b$l_systemd_parameter_value\\b\" <<< \"$l_systemd_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_systemd_parameter_name\\\" is correctly set to \\\"$l_systemd_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_systemd_parameter_name\\\" is incorrectly set to \\\"$l_systemd_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\" and should have a value matching: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Pio -- \"^\\h*$l_systemd_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_systemd_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_systemd_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n l_systemdanalyze=\"$(readlink -f /bin/systemd-analyze)\"\n while IFS=\"=\" read -r l_systemd_parameter_name l_systemd_parameter_value; do # Assess and check parameters\n l_systemd_parameter_name=\"${l_systemd_parameter_name// /}\"; l_systemd_parameter_value=\"${l_systemd_parameter_value// /}\"\n l_value_out=\"${l_systemd_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "768368d8-19f7-55a4-b178-4e95f8530864", + "benchmark-rule-id": "2.3.2.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_settings=(\"NTP=time.nist.gov\" \"FallbackNTP=time-a-g.nist.gov time-b-g.nist.gov time-c-g.nist.gov\")\n [ ! -d /etc/systemd/timesyncd.conf.d/ ] && mkdir /etc/systemd/timesyncd.conf.d/\n if grep -Psq -- '^\\h*\\[Time\\]' /etc/systemd/timesyncd.conf.d/60-timesyncd.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/timesyncd.conf.d/60-timesyncd.conf\n else\n printf '%s\\n' \"\" \"[Time]\" \"${a_settings[@]}\" >> /etc/systemd/timesyncd.conf.d/60-timesyncd.conf\n fi\n}\n" + }, + { + "uuid": "f49f966d-e9f0-581c-9cde-8fb57bd067ac", + "benchmark-rule-id": "2.3.3.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_config_files=(\"/etc/chrony/chrony.conf\") \n l_include='(confdir|sourcedir)' l_parameter_name='(server|pool)' l_parameter_value='.+'\n while IFS= read -r l_conf_loc; do\n l_dir=\"\" l_ext=\"\"\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n if [[ -n \"$l_dir\" && -n \"$l_ext\" ]]; then\n while IFS= read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n fi\n done < <(awk '$1~/^\\s*'\"$l_include\"'$/{print $2}' \"${a_config_files[*]}\" 2>/dev/null)\n for l_file in \"${a_config_files[@]}\"; do\n l_parameter_line=\"$(grep -Psi '^\\h*'\"$l_parameter_name\"'(\\h+|\\h*:\\h*)'\"$l_parameter_value\"'\\b' \"$l_file\")\"\n [ -n \"$l_parameter_line\" ] && a_output+=(\" - Parameter: \\\"$(tr -d '()' <<< ${l_parameter_name//|/ or })\\\"\" \\\n \" Exists in the file: \\\"$l_file\\\" as:\" \"$l_parameter_line\")\n done\n [ \"${#a_output[@]}\" -le \"0\" ] && a_output2+=(\" - Parameter: \\\"$(tr -d '()' <<< ${l_parameter_name//|/ or })\\\"\" \\\n \" Does not exist in the chrony configuration\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n fi\n}\n" + }, + { + "uuid": "0e9f309a-49b0-5f3a-90f9-6738d3e1c0cd", + "benchmark-rule-id": "2.3.3.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n [ ! -d \"/etc/chrony/sources.d/\" ] && mkdir /etc/chrony/sources.d/\n printf '%s\\n' \"\" \"#The maxsources option is unique to the pool directive\" \\\n \"pool time.nist.gov iburst maxsources 4\" >> /etc/chrony/sources.d/60-sources.sources\n chronyc reload sources &>/dev/null\n}\n" + }, + { + "uuid": "14a5635a-21f4-5eed-82e8-7f7f1c586bab", + "benchmark-rule-id": "2.3.3.1", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n [ ! -d \"/etc/chrony/sources.d/\" ] && mkdir /etc/chrony/sources.d/\n printf '%s\\n' \"\" \"server time-a-g.nist.gov iburst\" \"server 132.163.97.3 iburst\" \\\n \"server time-d-b.nist.gov iburst\" >> /etc/chrony/sources.d/60-sources.sources\n chronyc reload sources &>/dev/null\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "2.3.1.1: Time synchronization is important to support time sensitive security mechanisms and ensures log files have consistent time records across the enterprise, which aids in forensic investigations.\n\n2.3.2.1: Time synchronization is important to support time sensitive security mechanisms and to ensure log files have consistent time records across the enterprise to aid in forensic investigations\n\n2.3.2.2: systemd-timesyncd needs to be enabled and running in order to synchronize the system to a timeserver.\n\nTime synchronization is important to support time sensitive security mechanisms and to ensure log files have consistent time records across the enterprise to aid in forensic investigations\n\n2.3.3.1: Time synchronization is important to support time sensitive security mechanisms and to ensure log files have consistent time records across the enterprise to aid in forensic investigations\n\n2.3.3.2: The `chronyd` service should run with only the required privlidges\n\n2.3.3.3: chrony needs to be enabled and running in order to synchronize the system to a timeserver.\n\nTime synchronization is important to support time sensitive security mechanisms and to ensure log files have consistent time records across the enterprise to aid in forensic investigations", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "65b2956b-9dcc-51c2-a86b-27a74629e5c8", + "control-id": "cisc-008.005", + "description": "3.3.9 Ensure suspicious packets are logged; 5.1.16 Ensure sshd MaxAuthTries is configured; 5.2.3 Ensure sudo log file exists; 6.2.1.1 Ensure auditd packages are installed; 6.2.3.1 Ensure changes to system administration scope (sudoers) is collected; 6.2.3.2 Ensure actions as another user are always logged; 6.2.3.3 Ensure events that modify the sudo log file are collected; 6.2.3.4 Ensure events that modify date and time information are collected; 6.2.3.5 Ensure events that modify the system's network environment are collected; 6.2.3.6 Ensure use of privileged commands are collected; 6.2.3.7 Ensure unsuccessful file access attempts are collected; 6.2.3.8 Ensure events that modify user/group information are collected; 6.2.3.9 Ensure discretionary access control permission modification events are collected; 6.2.3.10 Ensure successful file system mounts are collected; 6.2.3.11 Ensure session initiation information is collected; 6.2.3.12 Ensure login and logout events are collected; 6.2.3.13 Ensure file deletion events by users are collected; 6.2.3.14 Ensure events that modify the system's Mandatory Access Controls are collected; 6.2.3.19 Ensure kernel module loading unloading and modification is collected; 6.2.3.20 Ensure the audit configuration is immutable; 6.2.3.21 Ensure the running and on disk configuration is the same; 6.3.2 Ensure filesystem integrity is regularly checked", + "automation-scripts": [ + { + "uuid": "37e3936a-cac1-5d2f-accc-551f59858f49", + "benchmark-rule-id": "3.3.9", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.log_martians=1\" \"net.ipv4.conf.default.log_martians=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "f1e96053-54bc-5015-8e92-009967d2a0bc", + "benchmark-rule-id": "3.3.9", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.log_martians=1\n sysctl -w net.ipv4.conf.default.log_martians=1\n sysctl -w net.ipv4.route.flush=1\n}\n" + }, + { + "uuid": "9e579bc9-0593-599f-9fb6-64104d588c24", + "benchmark-rule-id": "6.2.3.6", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n for PARTITION in $(findmnt -n -l -k -it $(awk '/nodev/ { print $2 }' /proc/filesystems | paste -sd,) | grep -Pv \"noexec|nosuid\" | awk '{print $1}'); do\n for PRIVILEGED in $(find \"${PARTITION}\" -xdev -perm /6000 -type f); do\n grep -qr \"${PRIVILEGED}\" /etc/audit/rules.d && printf \"OK: '${PRIVILEGED}' found in auditing rules.\\n\" || printf \"Warning: '${PRIVILEGED}' not found in on disk configuration.\\n\"\n done\n done\n}\n" + }, + { + "uuid": "78f8c68c-ed25-5f08-a0fe-7306780b7963", + "benchmark-rule-id": "6.2.3.6", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n RUNNING=$(auditctl -l)\n [ -n \"${RUNNING}\" ] && for PARTITION in $(findmnt -n -l -k -it $(awk '/nodev/ { print $2 }' /proc/filesystems | paste -sd,) | grep -Pv \"noexec|nosuid\" | awk '{print $1}'); do\n for PRIVILEGED in $(find \"${PARTITION}\" -xdev -perm /6000 -type f); do\n printf -- \"${RUNNING}\" | grep -q \"${PRIVILEGED}\" && printf \"OK: '${PRIVILEGED}' found in auditing rules.\\n\" || printf \"Warning: '${PRIVILEGED}' not found in running configuration.\\n\"\n done\n done \\\n || printf \"ERROR: Variable 'RUNNING' is unset.\\n\"\n}\n" + }, + { + "uuid": "e4d3840d-22c5-5e75-9db7-df13b2ffe412", + "benchmark-rule-id": "6.2.3.6", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n AUDIT_RULE_FILE=\"/etc/audit/rules.d/50-privileged.rules\"\n NEW_DATA=()\n for PARTITION in $(findmnt -n -l -k -it $(awk '/nodev/ { print $2 }' /proc/filesystems | paste -sd,) | grep -Pv \"noexec|nosuid\" | awk '{print $1}'); do\n readarray -t DATA < <(find \"${PARTITION}\" -xdev -perm /6000 -type f | awk -v UID_MIN=${UID_MIN} '{print \"-a always,exit -F path=\" $1 \" -F perm=x -F auid>=\"UID_MIN\" -F auid!=unset -k privileged\" }')\n for ENTRY in \"${DATA[@]}\"; do\n NEW_DATA+=(\"${ENTRY}\")\n done\n done\n readarray &> /dev/null -t OLD_DATA < \"${AUDIT_RULE_FILE}\"\n COMBINED_DATA=( \"${OLD_DATA[@]}\" \"${NEW_DATA[@]}\" )\n printf '%s\\n' \"${COMBINED_DATA[@]}\" | sort -u > \"${AUDIT_RULE_FILE}\"\n}\n" + }, + { + "uuid": "e053196a-9439-5d16-9748-5acc71e5d4fc", + "benchmark-rule-id": "6.2.3.19", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n awk '/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F auid!=unset/||/ -F auid!=-1/||/ -F auid!=4294967295/) \\\n &&/ -S/ \\\n &&(/init_module/ \\\n ||/finit_module/ \\\n ||/delete_module/ \\\n ||/create_module/ \\\n ||/query_module/) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/kmod/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n" + }, + { + "uuid": "c8d9d2f0-0c1c-5a27-b637-5550e273e2f8", + "benchmark-rule-id": "6.2.3.19", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n auditctl -l | awk '/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F auid!=unset/||/ -F auid!=-1/||/ -F auid!=4294967295/) \\\n &&/ -S/ \\\n &&(/init_module/ \\\n ||/finit_module/ \\\n ||/delete_module/ \\\n ||/create_module/ \\\n ||/query_module/) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/kmod/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n" + }, + { + "uuid": "2ea97418-5006-57df-9e1b-1243536d57e8", + "benchmark-rule-id": "6.2.3.19", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_files=(\"/usr/sbin/lsmod\" \"/usr/sbin/rmmod\" \"/usr/sbin/insmod\" \"/usr/sbin/modinfo\" \"/usr/sbin/modprobe\" \"/usr/sbin/depmod\")\n for l_file in \"${a_files[@]}\"; do\n if [ \"$(readlink -f \"$l_file\")\" = \"$(readlink -f /bin/kmod)\" ]; then\n printf \"OK: \\\"$l_file\\\"\\n\"\n else\n printf \"Issue with symlink for file: \\\"$l_file\\\"\\n\"\n fi\n done\n}\n" + }, + { + "uuid": "dfda9f59-7993-5af8-ac31-751def09155b", + "benchmark-rule-id": "6.2.3.19", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && printf \"\n -a always,exit -F arch=b64 -S init_module,finit_module,delete_module,create_module,query_module -F auid>=${UID_MIN} -F auid!=unset -k kernel_modules\n -a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=${UID_MIN} -F auid!=unset -k kernel_modules\n \" >> /etc/audit/rules.d/50-kernel_modules.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "3.3.9: Setting `net.ipv4.conf.all.log_martians` and `net.ipv4.conf.default.log_martians` to `1` enables this feature. Logging these packets allows an administrator to investigate the possibility that an attacker is sending spoofed packets to their system.\n\n5.1.16: Setting the `MaxAuthTries` parameter to a low number will minimize the risk of successful brute force attacks to the SSH server. While the recommended setting is 4, set the number based on site policy.\n\n5.2.3: A sudo log file simplifies auditing of sudo commands\n\n6.2.1.1: The capturing of system events provides system administrators with information to allow them to determine if unauthorized access to their system is occurring.\n\n6.2.3.1: Changes in the `/etc/sudoers` and `/etc/sudoers.d` files can indicate that an unauthorized change has been made to the scope of system administrator activity.\n\n6.2.3.2: Creating an audit log of users with temporary elevated privileges and the operation(s) they performed is essential to reporting. Administrators will want to correlate the events written to the audit trail with the records written to `sudo`'s logfile to verify if unauthorized commands have been executed.\n\n6.2.3.3: Changes in `/var/log/sudo.log` indicate that an administrator has executed a command or the log file itself has been tampered with. Administrators will want to correlate the events written to the audit trail with the records written to `/var/log/sudo.log` to verify if unauthorized commands have been executed.\n\n6.2.3.4: Unexpected changes in system date and/or time could be a sign of malicious activity on the system.\n\n6.2.3.5: Monitoring system events that change network environments, such as `sethostname` and `setdomainname`, helps identify unauthorized alterations to host and domain names, which could compromise security settings reliant on these names. Changes to `/etc/hosts` can signal unauthorized attempts to alter machine associations with IP addresses, potentially redirecting users and processes to unintended destinations. Surveillance of `/etc/issue` and `/etc/issue.net` is crucial to detect intruders inserting false information to deceive users. Monitoring `/etc/network/` reveals modifications to network interfaces or scripts that may jeopardize system availability or security. Additionally, tracking changes in the `/etc/netplan/` directory ensures swift detection of unauthorized adjustments to network configurations. All audit records should be appropriately tagged for relevance\n\n6.2.3.6: Execution of privileged commands by non-privileged users could be an indication of someone trying to gain unauthorized access to the system.\n\n6.2.3.7: Failed attempts to open, create or truncate files could be an indication that an individual or process is trying to gain unauthorized access to the system.\n\n6.2.3.8: Unexpected changes to these files could be an indication that the system has been compromised and that an unauthorized user is attempting to hide their activities or compromise additional accounts.\n\n6.2.3.9: Monitoring for changes in file attributes could alert a system administrator to activity that could indicate intruder activity or policy violation.\n\n6.2.3.10: It is highly unusual for a non privileged user to `mount` file systems to the system. While tracking `mount` commands gives the system administrator evidence that external media may have been mounted (based on a review of the source of the mount and confirming it's an external media type), it does not conclusively indicate that data was exported to the media. System administrators who wish to determine if data were exported, would also have to track successful `open`, `creat` and `truncate` system calls requiring write access to a file under the mount point of the external media file system. This could give a fair indication that a write occurred. The only way to truly prove it, would be to track successful writes to the external media. Tracking write system calls could quickly fill up the audit log and is not recommended. Recommendations on configuration options to track data export to media is beyond the scope of this document.\n\n6.2.3.11: Monitoring these files for changes could alert a system administrator to logins occurring at unusual hours, which could indicate intruder activity (i.e. a user logging in at a time when they do not normally log in).\n\n6.2.3.12: Monitoring login/logout events could provide a system administrator with information associated with brute force attacks against user logins.\n\n6.2.3.13: Monitoring these calls from non-privileged users could provide a system administrator with evidence that inappropriate removal of files and file attributes associated with protected files is occurring. While this audit option will look at all events, system administrators will want to look for specific privileged files that are being deleted or altered.\n\n6.2.3.14: Changes to files in the `/etc/apparmor/` and `/etc/apparmor.d/` directories could indicate that an unauthorized user is attempting to modify access controls and change security contexts, leading to a compromise of the system.\n\n6.2.3.19: Monitoring the use of all the various ways to manipulate kernel modules could provide system administrators with evidence that an unauthorized change was made to a kernel module, possibly compromising the security of the system.\n\n6.2.3.20: In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. Users would most likely notice a system reboot and that could alert administrators of an attempt to make unauthorized audit changes.\n\n6.2.3.21: Configuration differences between what is currently running and what is on disk could cause unexpected problems or may give a false impression of compliance requirements.\n\n6.3.2: Periodic file checking allows the system administrator to determine on a regular basis if critical files have been changed in an unauthorized fashion.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "ddc6b3e7-be8e-5726-a50d-11556f483150", + "control-id": "cisc-008.009", + "description": "6.1.3.3 Ensure journald is configured to send logs to rsyslog", + "automation-scripts": [ + { + "uuid": "c337f042-ddc5-5936-9a71-70bfd4d11ed0", + "benchmark-rule-id": "6.1.3.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"ForwardToSyslog=yes\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + }, + { + "uuid": "64454ac1-9539-51e5-8366-3bf5798e7935", + "benchmark-rule-id": "6.1.3.3", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_settings=(\"ForwardToSyslog=yes\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "6.1.3.3: **- IF -** `rsyslog` is the preferred method for capturing logs, all logs of the system should be sent to it for further processing.\n\n**Note:** This recommendation **only applies if `rsyslog` is the chosen method for client side logging**. Do not apply this recommendation if `systemd-journald` is used.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "f6a17996-181c-5ff4-ab57-593af5405f63", + "control-id": "cisc-010.003", + "description": "1.1.1.9 Ensure usb-storage kernel module is not available; 1.7.6 Ensure GDM automatic mounting of removable media is disabled; 1.7.8 Ensure GDM autorun-never is enabled; 1.7.9 Ensure GDM autorun-never is not overridden; 2.1.1 Ensure autofs services are not in use", + "automation-scripts": [ + { + "uuid": "a46c0492-80bc-55b5-b106-b116e521c4cd", + "benchmark-rule-id": "1.1.1.9", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"usb-storage\" l_mod_type=\"drivers\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n" + }, + { + "uuid": "1d9061a4-6137-5590-a97b-0d12e6c1bd9c", + "benchmark-rule-id": "1.1.1.9", + "script-type": "remediation", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"usb-storage\" l_mod_type=\"drivers\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\" \n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n" + }, + { + "uuid": "26e43f75-f8d3-521d-80c7-e6c0ac17bc23", + "benchmark-rule-id": "1.7.9", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n # Function to check and report if a specific setting is locked and set to true\n check_setting() {\n grep -Psrilq \"^\\h*$1\\h*=\\h*true\\b\" /etc/dconf/db/local.d/locks/* 2> /dev/null && echo \"- \\\"$3\\\" is locked and set to false\" || echo \"- \\\"$3\\\" is not locked or not set to false\" \n }\n # Array of settings to check\n declare -A settings=([\"autorun-never\"]=\"org/gnome/desktop/media-handling\")\n # Check GNOME Desktop Manager configurations\n l_output=() l_output2=()\n for setting in \"${!settings[@]}\"; do\n result=$(check_setting \"$setting\")\n l_output+=(\"$result\")\n if [[ $result == *\"is not locked\"* || $result == *\"not set to true\"* ]]; then\n l_output2+=(\"$result\")\n fi\n done\n # Report results\n if [ ${#l_output2[@]} -ne 0 ]; then\n printf '%s\\n' \"- Audit Result:\" \" ** FAIL **\"\n printf '%s\\n' \"- Reason(s) for audit failure:\"\n for msg in \"${l_output2[@]}\"; do\n printf '%s\\n' \"$msg\"\n done\n else\n printf '%s\\n' \"- Audit Result:\" \" ** PASS **\"\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "1.1.1.9: Restricting USB access on the system will decrease the physical attack surface for a device and diminish the possible vectors to introduce malware.\n\n1.7.6: With automounting enabled anyone with physical access could attach a USB drive or disc and have its contents available in system even if they lacked permissions to mount it themselves.\n\n1.7.8: Malware on removable media may taking advantage of Autorun features when the media is inserted into a system and execute.\n\n1.7.9: Malware on removable media may taking advantage of Autorun features when the media is inserted into a system and execute.\n\n2.1.1: With automounting enabled anyone with physical access could attach a USB drive or disc and have its contents available in the filesystem even if they lacked permissions to mount it themselves.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "b30c61e0-c285-5053-9d55-40766aa24f70", + "control-id": "cisc-010.005", + "description": "1.5.1 Ensure address space layout randomization is enabled", + "automation-scripts": [ + { + "uuid": "90c0e634-bc73-5fad-a785-67aa7950223f", + "benchmark-rule-id": "1.5.1", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_parlist=(kernel.randomize_va_space=2)\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_kernel_parameter_chk\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "1.5.1: Randomly placing virtual memory regions will make it difficult to write memory page exploits as the memory placement will be consistently shifting.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "0ee363c1-62e7-51d6-afc0-852e302bcdb0", + "control-id": "cisc-014.006", + "description": "7.2.3 Ensure all groups in /etc/passwd exist in /etc/group", + "automation-scripts": [ + { + "uuid": "c735be85-9c85-5144-b9e8-ab8b87012088", + "benchmark-rule-id": "7.2.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n a_passwd_group_gid=(\"$(awk -F: '{print $4}' /etc/passwd | sort -u)\")\n a_group_gid=(\"$(awk -F: '{print $3}' /etc/group | sort -u)\")\n a_passwd_group_diff=(\"$(printf '%s\\n' \"${a_group_gid[@]}\" \"${a_passwd_group_gid[@]}\" | sort | uniq -u)\")\n while IFS= read -r l_gid; do\n awk -F: '($4 == '\"$l_gid\"') {print \" - User: \\\"\" $1 \"\\\" has GID: \\\"\" $4 \"\\\" which does not exist in /etc/group\" }' /etc/passwd\n done < <(printf '%s\\n' \"${a_passwd_group_gid[@]}\" \"${a_passwd_group_diff[@]}\" | sort | uniq -D | uniq)\n unset a_passwd_group_gid; unset a_group_gid; unset a_passwd_group_diff\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "7.2.3: Groups defined in the `/etc/passwd` file but not in the `/etc/group` file pose a threat to system security since group permissions are not properly managed.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + } + ] + }, + { + "uuid": "753e0b76-af3a-55a8-bb97-e782faadfbf1", + "source": "cis-ubuntu-24-04-lts-benchmark-catalog.json", + "description": "Recommendations that reference no CIS Control, keyed to the catalog beside this file, one requirement per recommendation.", + "implemented-requirements": [ + { + "uuid": "c587f90f-9b71-5c29-bf3e-f71772a6c509", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted", + "description": "1.5.3 Ensure core dumps are restricted", + "automation-scripts": [ + { + "uuid": "0f8e486d-4601-585e-a7b0-bf53f4572c95", + "benchmark-rule-id": "1.5.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_parlist=(\"fs.suid_dumpable=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_kernel_parameter_chk()\n { \n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_kernel_parameter_chk\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "1.5.3: Setting a hard limit on core dumps prevents users from overriding the soft variable. If core dumps are required, consider setting limits for user groups (see `limits.conf(5)` ). In addition, setting the `fs.suid_dumpable` variable to 0 will prevent setuid programs from dumping core.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "b88adced-8fbd-5dd0-a853-a6d736ef73e7", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly", + "description": "1.6.1 Ensure message of the day is configured properly", + "props": [ + { + "name": "rationale", + "value": "1.6.1: Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the \" `uname -a` \" command once they have logged in.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "31853c30-bba3-5f9a-b40d-603c518e83a5", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly", + "description": "1.6.2 Ensure local login warning banner is configured properly", + "props": [ + { + "name": "rationale", + "value": "1.6.2: Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the \" `uname -a` \" command once they have logged in.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "528eade4-b96c-5882-93a4-b7216a4f1eca", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly", + "description": "1.6.3 Ensure remote login warning banner is configured properly", + "props": [ + { + "name": "rationale", + "value": "1.6.3: Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the \" `uname -a` \" command once they have logged in.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "a9af0706-9403-5143-9385-1c74864479d8", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured", + "description": "1.7.2 Ensure GDM login banner is configured", + "props": [ + { + "name": "rationale", + "value": "1.7.2: Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "81aaa336-2d44-560b-a5bc-97e390fdde1a", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled", + "description": "1.7.3 Ensure GDM disable-user-list option is enabled", + "props": [ + { + "name": "rationale", + "value": "1.7.3: Displaying the user list eliminates half of the Userid/Password equation that an unauthorized person would need to log on.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "3daa64d4-34ae-525e-a1f7-66541b6acaa4", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden", + "description": "1.7.7 Ensure GDM disabling automatic mounting of removable media is not overridden", + "automation-scripts": [ + { + "uuid": "66843069-ddba-5926-83e4-0699721c56c5", + "benchmark-rule-id": "1.7.7", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=()\n check_setting() \n {\n grep -Psrilq \"^\\h*$1\\h*=\\h*false\\b\" /etc/dconf/db/local.d/locks/* 2> /dev/null && \\\n echo \"- \\\"$3\\\" is locked and set to false\" || echo \"- \\\"$3\\\" is not locked or not set to false\" \n }\n declare -A settings=(\n [\"automount\"]=\"org/gnome/desktop/media-handling\"\n [\"automount-open\"]=\"org/gnome/desktop/media-handling\"\n )\n for setting in \"${!settings[@]}\"; do\n result=$(check_setting \"$setting\" \"${settings[$setting]}\" \"$setting\")\n if [[ $result == *\"is not locked\"* || $result == *\"not set to false\"* ]]; then\n a_output2+=(\"$result\")\n else\n a_output+=(\"$result\")\n fi\n done\n printf '%s\\n' \"\" \"- Audit Result:\"\n if [ \"${#a_output2[@]}\" -gt 0 ]; then\n printf '%s\\n' \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\"\n else\n printf '%s\\n' \" ** PASS **\" \"${a_output[@]}\"\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "1.7.7: With automounting enabled anyone with physical access could attach a USB drive or disc and have its contents available in system even if they lacked permissions to mount it themselves.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "91293f9a-637e-584b-9595-298aa08993e3", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active", + "description": "2.4.1.1 Ensure cron daemon is enabled and active", + "props": [ + { + "name": "rationale", + "value": "2.4.1.1: While there may not be user jobs that need to be run on the system, the system does have maintenance jobs that may include security monitoring that have to run, and `cron` is used to execute them.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "cc3cc11f-724e-5bca-b5f3-a1de688186ad", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured", + "description": "5.1.5 Ensure sshd Banner is configured", + "props": [ + { + "name": "rationale", + "value": "5.1.5: Banners are used to warn connecting users of the particular site's policy regarding connection. Presenting a warning message prior to the normal user login may assist the prosecution of trespassers on the computer system.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "a428b3f4-9812-573c-9f3f-dfa3cc0bc97d", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured", + "description": "5.1.7 Ensure sshd ClientAliveInterval and ClientAliveCountMax are configured", + "props": [ + { + "name": "rationale", + "value": "5.1.7: In order to prevent resource exhaustion, appropriate values should be set for both `ClientAliveInterval` and `ClientAliveCountMax`. Specifically, looking at the source code, `ClientAliveCountMax` must be greater than zero in order to utilize the ability of SSH to drop idle connections. If connections are allowed to stay open indefinitely, this can potentially be used as a DDOS attack or simple resource exhaustion could occur over unreliable networks.\n\nThe example set here is a 45 second timeout. Consult your site policy for network timeouts and apply as appropriate.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "3b635849-2749-52a8-bd14-cca8dcbb1749", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled", + "description": "5.1.10 Ensure sshd HostbasedAuthentication is disabled", + "props": [ + { + "name": "rationale", + "value": "5.1.10: Even though the `.rhosts` files are ineffective if support is disabled in `/etc/pam.conf`, disabling the ability to use `.rhosts` files in SSH provides an additional layer of protection.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "05437a8e-eec8-5adc-b99f-cda8890c7a3b", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured", + "description": "5.1.13 Ensure sshd LoginGraceTime is configured", + "props": [ + { + "name": "rationale", + "value": "5.1.13: Setting the `LoginGraceTime` parameter to a low number will minimize the risk of successful brute force attacks to the SSH server. It will also limit the number of concurrent unauthenticated connections While the recommended setting is 60 seconds (1 Minute), set the number based on site policy.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "b499282c-6a8d-5f4f-90bf-4b5a27d51159", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured", + "description": "5.1.17 Ensure sshd MaxSessions is configured", + "props": [ + { + "name": "rationale", + "value": "5.1.17: To protect a system from denial of service due to a large number of concurrent sessions, use the rate limiting function of MaxSessions to protect availability of sshd logins and prevent overwhelming the daemon.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "8334c2a8-da2c-5fa9-bf82-e94642d1955d", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured", + "description": "5.1.18 Ensure sshd MaxStartups is configured", + "props": [ + { + "name": "rationale", + "value": "5.1.18: To protect a system from denial of service due to a large number of pending authentication connection attempts, use the rate limiting function of MaxStartups to protect availability of sshd logins and prevent overwhelming the daemon.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "394b7258-16c8-54f2-949e-6f44b36087f0", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled", + "description": "5.1.21 Ensure sshd PermitUserEnvironment is disabled", + "props": [ + { + "name": "rationale", + "value": "5.1.21: Permitting users the ability to set environment variables through the SSH daemon could potentially allow users to bypass security controls (e.g. setting an execution path that has SSH executing trojan'd programs)", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "65a998f8-4ce0-5b4b-9e86-0d6f07362259", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed", + "description": "5.3.1.1 Ensure latest version of pam is installed", + "props": [ + { + "name": "rationale", + "value": "5.3.1.1: To ensure the system has full functionality and access to the options covered by this Benchmark the latest version of `libpam-runtime` should be installed on the system", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "ae89dd7a-85eb-5cab-833a-85c90dc7c5ed", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed", + "description": "5.3.1.2 Ensure libpam-modules is installed", + "props": [ + { + "name": "rationale", + "value": "5.3.1.2: To ensure the system has full functionality and access to the PAM options covered by this Benchmark", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "2b6ae4cb-001f-5f21-8a8d-daa820d36ce6", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed", + "description": "5.3.1.3 Ensure libpam-pwquality is installed", + "props": [ + { + "name": "rationale", + "value": "5.3.1.3: Strong passwords reduce the risk of systems being hacked through brute force methods.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "a4c300ad-3eb7-5b84-98c4-3143c32c92bc", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account", + "description": "5.4.2.1 Ensure root is the only UID 0 account", + "props": [ + { + "name": "rationale", + "value": "5.4.2.1: This access must be limited to only the default `root` account and only from the system console. Administrative access must be through an unprivileged account using an approved mechanism as noted in Item 5.6 Ensure access to the su command is restricted.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "e730c9d6-400f-51e8-9dba-751ac7885d2b", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity", + "description": "5.4.2.5 Ensure root path integrity", + "automation-scripts": [ + { + "uuid": "2ff25730-daf4-502c-8d6f-b55b076d0905", + "benchmark-rule-id": "5.4.2.5", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output2=\"\"\n l_pmask=\"0022\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n l_root_path=\"$(sudo -Hiu root env | grep '^PATH' | cut -d= -f2)\"\n unset a_path_loc && IFS=\":\" read -ra a_path_loc <<< \"$l_root_path\"\n grep -q \"::\" <<< \"$l_root_path\" && l_output2=\"$l_output2\\n - root's path contains a empty directory (::)\"\n grep -Pq \":\\h*$\" <<< \"$l_root_path\" && l_output2=\"$l_output2\\n - root's path contains a trailing (:)\"\n grep -Pq '(\\h+|:)\\.(:|\\h*$)' <<< \"$l_root_path\" && l_output2=\"$l_output2\\n - root's path contains current working directory (.)\"\n while read -r l_path; do\n if [ -d \"$l_path\" ]; then\n while read -r l_fmode l_fown; do\n [ \"$l_fown\" != \"root\" ] && l_output2=\"$l_output2\\n - Directory: \\\"$l_path\\\" is owned by: \\\"$l_fown\\\" should be owned by \\\"root\\\"\"\n [ $(( $l_fmode & $l_pmask )) -gt 0 ] && l_output2=\"$l_output2\\n - Directory: \\\"$l_path\\\" is mode: \\\"$l_fmode\\\" and should be mode: \\\"$l_maxperm\\\" or more restrictive\"\n done <<< \"$(stat -Lc '%#a %U' \"$l_path\")\"\n else\n l_output2=\"$l_output2\\n - \\\"$l_path\\\" is not a directory\"\n fi\n done <<< \"$(printf \"%s\\n\" \"${a_path_loc[@]}\")\"\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n *** PASS ***\\n - Root's path is correctly configured\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\\n\"\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "5.4.2.5: Including the current working directory (.) or other writable directory in `root`'s executable path makes it likely that an attacker can gain superuser access by forcing an administrator operating as `root` to execute a Trojan horse program.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "ff610345-ac2c-5295-aa76-8f014c35d438", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells", + "description": "5.4.3.1 Ensure nologin is not listed in /etc/shells", + "props": [ + { + "name": "rationale", + "value": "5.4.3.1: A user can use `chsh` to change their configured shell.\n\nIf a user has a shell configured that isn't in in `/etc/shells`, then the system assumes that they're somehow restricted. In the case of `chsh` it means that the user cannot change that value.\n\nOther programs might query that list and apply similar restrictions.\n\nBy putting `nologin` in `/etc/shells`, any user that has `nologin` as its shell is considered a full, unrestricted user. This is not the expected behavior for `nologin`.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "ef795229-cb02-52ff-b62e-8153ad6a8b9c", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use", + "description": "6.1.1.4 Ensure only one logging system is in use", + "automation-scripts": [ + { + "uuid": "8459ce18-6d12-53af-a24e-b2736209b371", + "benchmark-rule-id": "6.1.1.4", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" # Check the status of rsyslog and journald\n if systemctl is-active --quiet rsyslog; then\n l_output=\"$l_output\\n - rsyslog is in use\\n- follow the recommendations in Configure rsyslog subsection only\"\n elif systemctl is-active --quiet systemd-journald; then\n l_output=\"$l_output\\n - journald is in use\\n- follow the recommendations in Configure journald subsection only\"\n else\n echo -e “unable to determine system logging”\n l_output2=\"$l_output2\\n - unable to determine system logging\\n- Configure only ONE system logging: rsyslog OR journald\"\n fi\n if [ -z \"$l_output2\" ]; then # Provide audit results\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Reason(s) for audit failure:\\n$l_output2\"\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "6.1.1.4: Configuring only one logging service either `rsyslog` **- OR -** `journald` avoids redundancy, optimizes resources, simplifies configuration and management, and ensures consistency.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "20965e7f-0adc-5d19-a70a-60b6b0c42604", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools", + "description": "6.3.3 Ensure cryptographic mechanisms are used to protect the integrity of audit tools", + "automation-scripts": [ + { + "uuid": "3f809d17-0a61-529e-9c1d-253f17d18396", + "benchmark-rule-id": "6.3.3", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 2 - Server", + "Level 2 - Workstation" + ], + "evaluation-criteria": { + "method": "stdout-regex", + "pass-condition": "^\\*\\* PASS \\*\\*$", + "fail-condition": "^\\*\\* FAIL \\*\\*$" + }, + "payload": "#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_tool_dir=\"$(readlink -f /sbin)\"\n a_items=(\"p\" \"i\" \"n\" \"u\" \"g\" \"s\" \"b\" \"acl\" \"xattrs\" \"sha512\")\n l_aide_cmd=\"$(whereis aide | awk '{print $2}')\"\n a_audit_files=(\"auditctl\" \"auditd\" \"ausearch\" \"aureport\" \"autrace\" \"augenrules\")\n if [ -f \"$l_aide_cmd\" ] && command -v \"$l_aide_cmd\" &>/dev/null; then\n a_aide_conf_files=(\"$(find -L /etc -type f -name 'aide.conf')\")\n f_file_par_chk()\n {\n a_out2=()\n for l_item in \"${a_items[@]}\"; do\n ! grep -Psiq -- '(\\h+|\\+)'\"$l_item\"'(\\h+|\\+)' <<< \"$l_out\" && \\\n a_out2+=(\" - Missing the \\\"$l_item\\\" option\")\n done\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - Audit tool file: \\\"$l_file\\\"\" \"${a_out2[@]}\")\n else\n a_output+=(\" - Audit tool file: \\\"$l_file\\\" includes:\" \" \\\"${a_items[*]}\\\"\")\n fi\n }\n for l_file in \"${a_audit_files[@]}\"; do\n if [ -f \"$l_tool_dir/$l_file\" ]; then\n l_out=\"$(\"$l_aide_cmd\" --config \"${a_aide_conf_files[@]}\" -p f:\"$l_tool_dir/$l_file\")\"\n f_file_par_chk\n else\n a_output+=(\" - Audit tool file \\\"$l_file\\\" doesn't exist\")\n fi\n done\n else\n a_output2+=(\" - The command \\\"aide\\\" was not found\" \" Please install AIDE\")\n fi\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "6.3.3: Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.\n\nAttackers may replace the audit tools or inject code into the existing tools with the purpose of providing the capability to hide or erase system activity from the audit logs.\n\nAudit tools should be cryptographically signed in order to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "f7a8e386-4fe6-5e77-a702-1ef1fc2cb609", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist", + "description": "7.2.5 Ensure no duplicate UIDs exist", + "automation-scripts": [ + { + "uuid": "40c5a005-6c56-5433-a2f9-1b4f93d86cb0", + "benchmark-rule-id": "7.2.5", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n while read -r l_count l_uid; do\n if [ \"$l_count\" -gt 1 ]; then\n echo -e \"Duplicate UID: \\\"$l_uid\\\" Users: \\\"$(awk -F: '($3 == n) { print $1 }' n=$l_uid /etc/passwd | xargs)\\\"\"\n fi\n done < <(cut -f3 -d\":\" /etc/passwd | sort -n | uniq -c)\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "7.2.5: Users must be assigned unique UIDs for accountability and to ensure appropriate access protections.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "b88e339d-1b00-57e6-afed-1a1ceac8e8e4", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist", + "description": "7.2.6 Ensure no duplicate GIDs exist", + "automation-scripts": [ + { + "uuid": "d877e767-64fc-5ca0-8534-d439cbdcd0e2", + "benchmark-rule-id": "7.2.6", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n while read -r l_count l_gid; do\n if [ \"$l_count\" -gt 1 ]; then\n echo -e \"Duplicate GID: \\\"$l_gid\\\" Groups: \\\"$(awk -F: '($3 == n) { print $1 }' n=$l_gid /etc/group | xargs)\\\"\"\n fi\n done < <(cut -f3 -d\":\" /etc/group | sort -n | uniq -c)\n} \n" + } + ], + "props": [ + { + "name": "rationale", + "value": "7.2.6: User groups must be assigned unique GIDs for accountability and to ensure appropriate access protections.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "92846d98-94d2-5058-a252-8a6a42dac558", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist", + "description": "7.2.7 Ensure no duplicate user names exist", + "automation-scripts": [ + { + "uuid": "0820be2b-c534-5ad0-93f2-8397d06ab1f1", + "benchmark-rule-id": "7.2.7", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n while read -r l_count l_user; do\n if [ \"$l_count\" -gt 1 ]; then\n echo -e \"Duplicate User: \\\"$l_user\\\" Users: \\\"$(awk -F: '($1 == n) { print $1 }' n=$l_user /etc/passwd | xargs)\\\"\"\n fi\n done < <(cut -f1 -d\":\" /etc/group | sort -n | uniq -c)\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "7.2.7: If a user is assigned a duplicate user name, it will create and have access to files with the first UID for that username in `/etc/passwd` . For example, if \"test4\" has a UID of 1000 and a subsequent \"test4\" entry has a UID of 2000, logging in as \"test4\" will use UID 1000. Effectively, the UID is shared, which is a security problem.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + }, + { + "uuid": "b006c514-73ff-5569-a371-db4dcac131ef", + "control-id": "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist", + "description": "7.2.8 Ensure no duplicate group names exist", + "automation-scripts": [ + { + "uuid": "d7550151-f750-58ea-b82e-495d6389264d", + "benchmark-rule-id": "7.2.8", + "script-type": "audit", + "language": "bash", + "applicable-profiles": [ + "Level 1 - Server", + "Level 2 - Server", + "Level 1 - Workstation", + "Level 2 - Workstation" + ], + "payload": "#!/usr/bin/env bash\n\n{\n while read -r l_count l_group; do\n if [ \"$l_count\" -gt 1 ]; then\n echo -e \"Duplicate Group: \\\"$l_group\\\" Groups: \\\"$(awk -F: '($1 == n) { print $1 }' n=$l_group /etc/group | xargs)\\\"\"\n fi\n done < <(cut -f1 -d\":\" /etc/group | sort -n | uniq -c)\n}\n" + } + ], + "props": [ + { + "name": "rationale", + "value": "7.2.8: If a group is assigned a duplicate group name, it will create and have access to files with the first GID for that group in `/etc/group` . Effectively, the GID is shared, which is a security problem.", + "ns": "https://cisecurity.org/ns/oscal" + } + ] + } + ] + } + ] + } + ] + } +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json new file mode 100644 index 0000000..867c988 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-benchmark-catalog.json @@ -0,0 +1,22341 @@ +{ + "catalog": { + "uuid": "6c8f81ec-89be-52b0-ba59-68f9b1e4ae83", + "metadata": { + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, as a catalog with executable assessment methods", + "published": "2026-03-16T00:00:00Z", + "last-modified": "2026-09-09T00:00:00Z", + "version": "1.0.0", + "oscal-version": "1.2.1", + "links": [ + { + "rel": "source", + "href": "#c54b4287-f421-5f90-a4d1-4b94f3d30a9a" + }, + { + "rel": "source", + "href": "#93b2e475-6325-556c-b6bd-49e0c2bd2b3d" + } + ], + "remarks": "Generated by tools/executable_first_corpus.py from the benchmark file named in back-matter. Every control, part, identifier, value and script body is taken from that file. The shape, an assessment objective and an executable assessment method on every control, is the one the concept note on executable assessment methods proposes, and the generator chose it, not CIS. One section of the benchmark holds recommendations and a sub-section together, which an OSCAL group cannot, so its own recommendations sit in a sub-group named after it." + }, + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_1_Initial_Setup", + "title": "Initial Setup", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1_Filesystem", + "title": "Filesystem", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1.1_Configure_Filesystem_Kernel_Modules", + "title": "Configure Filesystem Kernel Modules", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available", + "title": "1.1.1.1 Ensure cramfs kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "cramfs:fs" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The `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." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure cramfs kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run 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 within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `cramfs` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"cramfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "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\n- Create a file ending in `.conf` with `blacklist cramfs` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r cramfs 2>/dev/null; rmmod cramfs 2>/dev/null` to remove `cramfs` from the kernel\n\n**- IF -** the `cramfs` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"cramfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available", + "title": "1.1.1.2 Ensure freevxfs kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "freevxfs:fs" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The `freevxfs` filesystem type is a free version of the Veritas type filesystem. This is the primary filesystem type for HP-UX operating systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure freevxfs kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `freevxfs` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `freevxfs` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"freevxfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `freevxfs` module:\n\n**- IF -** the `freevxfs` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install freevxfs /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist freevxfs` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r freevxfs 2>/dev/null; rmmod freevxfs 2>/dev/null` to remove `freevxfs` from the kernel\n\n**- IF -** the `freevxfs` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"freevxfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available", + "title": "1.1.1.3 Ensure hfs kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "hfs:fs" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The `hfs` filesystem type is a hierarchical filesystem that allows you to mount Mac OS filesystems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure hfs kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `hfs` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `hfs` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"hfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `hfs` module:\n\n**- IF -** the `hfs` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install hfs /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist hfs` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r hfs 2>/dev/null; rmmod hfs 2>/dev/null` to remove `hfs` from the kernel\n\n**- IF -** the `hfs` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"hfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available", + "title": "1.1.1.4 Ensure hfsplus kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "hfsplus:fs" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The `hfsplus` filesystem type is a hierarchical filesystem designed to replace `hfs` that allows you to mount Mac OS filesystems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure hfsplus kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `hfsplus` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `hfsplus` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"hfsplus\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `hfsplus` module:\n\n**- IF -** the `hfsplus` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install hfsplus /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist hfsplus` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r hfsplus 2>/dev/null; rmmod hfsplus 2>/dev/null` to remove `hfsplus` from the kernel\n\n**- IF -** the `hfsplus` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"hfsplus\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available", + "title": "1.1.1.5 Ensure jffs2 kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "jffs2:fs" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The `jffs2` (journaling flash filesystem 2) filesystem type is a log-structured filesystem used in flash memory devices." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure jffs2 kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `jffs2` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `jffs2` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"jffs2\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `jffs2` module:\n\n**- IF -** the `jffs2` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install jffs2 /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist jffs2` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r jffs2 2>/dev/null; rmmod jffs2 2>/dev/null` to remove `jffs2` from the kernel\n\n**- IF -** the `jffs2` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"jffs2\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available", + "title": "1.1.1.6 Ensure overlayfs kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "overlayfs:fs" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "`overlayfs` is a Linux filesystem that layers multiple filesystems to create a single unified view which allows a user to \"merge\" several mount points into a unified filesystem." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "The `overlayfs` has known CVE's: CVE-2023-32629, CVE-2023-2640, CVE-2023-0386. Disabling the `overlayfs` reduces the local attack surface by removing support for unnecessary filesystem types and mitigates potential risks associated with unauthorized execution of setuid files, enhancing the overall system security." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure overlayfs kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `overlayfs` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `overlayfs` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"overlayfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `overlayfs` module:\n\n**- IF -** the `overlayfs` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install overlayfs /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist overlayfs` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r overlayfs 2>/dev/null; rmmod overlayfs 2>/dev/null` to remove `overlayfs` from the kernel\n\n**- IF -** the `overlayfs` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"overlayfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```\n\nImpact:\n\n**WARNING:** **If Container applications such as Docker, Kubernetes, Podman, Linux Containers (LXC), etc. are in use proceed with caution and consider the impact on containerized workloads, as disabling the `overlayfs` may severely disrupt containerization.**" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available", + "title": "1.1.1.7 Ensure squashfs kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "squashfs:fs" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The `squashfs` filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems. A `squashfs` image can be used without having to first decompress the image." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure squashfs kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `squashfs` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `squashfs` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"squashfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```\n\n**Note:** On operating systems where `squashfs` is pre-build into the kernel:\n\n- This is considered an acceptable \"passing\" state\n\n- The kernel **should not** be re-compiled to remove `squashfs`\n\n- This audit will return a passing state with \"module: \"squashfs\" doesn't exist in ...\"" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `udf` module:\n\n**- IF -** the `squashfs` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install squashfs /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist squashfs` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r squashfs 2>/dev/null; rmmod squashfs 2>/dev/null` to remove `squashfs` from the kernel\n\n**- IF -** the `squashfs` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"squashfs\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```\n\nImpact:\n\nAs Snap packages utilize `squashfs` as a compressed filesystem, disabling `squashfs` will cause Snap packages to fail.\n\n`Snap` application packages of software are self-contained and work across a range of Linux distributions. This is unlike traditional Linux package management approaches, like APT or RPM, which require specifically adapted packages per Linux distribution on an application update and delay therefore application deployment from developers to their software's end-user. Snaps themselves have no dependency on any external store (\"App store\"), can be obtained from any source and can be therefore used for upstream software deployment." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available", + "title": "1.1.1.8 Ensure udf kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "udf:fs" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The `udf` filesystem type is the universal disk format used to implement ISO/IEC 13346 and ECMA-167 specifications. This is an open vendor filesystem type for data storage on a broad range of media. This filesystem type is necessary to support writing DVDs and newer optical disc formats." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure udf kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `udf` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `udf` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"udf\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `udf` module:\n\n**- IF -** the `udf` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install udf /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist udf` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r udf 2>/dev/null; rmmod udf 2>/dev/null` to remove `udf` from the kernel\n\n**- IF -** the `udf` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"udf\" l_mod_type=\"fs\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```\n\nImpact:\n\nMicrosoft Azure requires the usage of `udf`.\n\n`udf` **should not** be disabled on systems run on Microsoft Azure." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available", + "title": "1.1.1.9 Ensure usb-storage kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "usb-storage:drivers" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/10/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "USB storage provides a means to transfer and store files ensuring persistence and availability of the files independent of network connection status. Its popularity and utility has led to USB-based malware being a simple and common means for network infiltration and a first step to establishing a persistent threat within a networked environment." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "Restricting USB access on the system will decrease the physical attack surface for a device and diminish the possible vectors to introduce malware." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure usb-storage kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `usb-storage` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `usb-storage` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"usb-storage\" l_mod_type=\"drivers\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `usb-storage` module:\n\n**- IF -** the `usb-storage` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install usb-storage /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist usb-storage` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r usb-storage 2>/dev/null; rmmod usb-storage 2>/dev/null` to remove `usb-storage` from the kernel\n\n**- IF -** the `usb-storage` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"usb-storage\" l_mod_type=\"drivers\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```\n\nImpact:\n\nDisabling the `usb-storage` module will disable any usage of USB storage devices.\n\nIf requirements and local site policy allow the use of such devices, other solutions should be configured accordingly instead. One example of a commonly used solution is `USBGuard`." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available", + "title": "1.1.1.10 Ensure unused filesystems kernel modules are not available", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available_smt", + "name": "statement", + "prose": "Filesystem kernel modules are pieces of code that can be dynamically loaded into the Linux kernel to extend its filesystem capabilities, or so-called base kernel, of an operating system. Filesystem kernel modules are typically used to add support for new hardware (as device drivers), or for adding system calls." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available_rationale", + "name": "rationale", + "prose": "While loadable filesystem kernel modules are a convenient method of modifying the running kernel, this can be abused by attackers on a compromised system to prevent detection of their processes or files, allowing them to maintain control over the system. Many rootkits make use of loadable filesystem kernel modules in this way.\n\nRemoving support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it. The following filesystem kernel modules have known CVE's and should be made unavailable if no dependencies exist:\n\n- `afs` - CVE-2022-37402\n\n- `ceph` - CVE-2022-0670\n\n- `cifs` - CVE-2022-29869\n\n- `exfat` CVE-2022-29973\n\n- `ext` CVE-2022-1184\n\n- `fat` CVE-2022-22043\n\n- `fscache` CVE-2022-3630\n\n- `fuse` CVE-2023-0386\n\n- `gfs2` CVE-2023-3212\n\n- `nfs_common` CVE-2023-6660\n\n- `nfsd` CVE-2022-43945\n\n- `smbfs_common` CVE-2022-2585" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure unused filesystems kernel modules are not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available_obj" + } + ], + "prose": "Run the following script to:\n\n- Look at the filesystem kernel modules available to the currently running kernel.\n\n- Exclude mounted filesystem kernel modules that don't currently have a CVE\n\n- List filesystem kernel modules that are not fully disabled, or are loaded into the kernel\n\nReview the generated output\n\n```\n#! /usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_modprope_config=(); a_excluded=(); a_available_modules=()\n a_ignore=(\"xfs\" \"vfat\" \"ext2\" \"ext3\" \"ext4\")\n a_cve_exists=(\"afs\" \"ceph\" \"cifs\" \"exfat\" \"ext\" \"fat\" \"fscache\" \"fuse\" \"gfs2\" \"nfs_common\" \"nfsd\" \"smbfs_common\")\n f_module_chk()\n {\n l_out2=\"\"; grep -Pq -- \"\\b$l_mod_name\\b\" <<< \"${a_cve_exists[*]}\" && l_out2=\" <- CVE exists!\"\n if ! grep -Pq -- '\\bblacklist\\h+'\"$l_mod_name\"'\\b' <<< \"${a_modprope_config[*]}\"; then\n a_output2+=(\" - Kernel module: \\\"$l_mod_name\\\" is not fully disabled $l_out2\")\n elif ! grep -Pq -- '\\binstall\\h+'\"$l_mod_name\"'\\h+(\\/usr)?\\/bin\\/(false|true)\\b' <<< \"${a_modprope_config[*]}\"; then\n a_output2+=(\" - Kernel module: \\\"$l_mod_name\\\" is not fully disabled $l_out2\")\n fi\n if lsmod | grep \"$l_mod_name\" &> /dev/null; then # Check if the module is currently loaded\n l_output2+=(\" - Kernel module: \\\"$l_mod_name\\\" is loaded\" \"\")\n fi\n }\n while IFS= read -r -d $'\\0' l_module_dir; do\n a_available_modules+=(\"$(basename \"$l_module_dir\")\")\n done < <(find \"$(readlink -f /lib/modules/\"$(uname -r)\"/kernel/fs)\" -mindepth 1 -maxdepth 1 -type d ! -empty -print0)\n while IFS= read -r l_exclude; do\n if grep -Pq -- \"\\b$l_exclude\\b\" <<< \"${a_cve_exists[*]}\"; then\n a_output2+=(\" - ** WARNING: kernel module: \\\"$l_exclude\\\" has a CVE and is currently mounted! **\")\n elif\n grep -Pq -- \"\\b$l_exclude\\b\" <<< \"${a_available_modules[*]}\"; then\n a_output+=(\" - Kernel module: \\\"$l_exclude\\\" is currently mounted - do NOT unload or disable\")\n fi\n ! grep -Pq -- \"\\b$l_exclude\\b\" <<< \"${a_ignore[*]}\" && a_ignore+=(\"$l_exclude\")\n done < <(findmnt -knD | awk '{print $2}' | sort -u)\n while IFS= read -r l_config; do\n a_modprope_config+=(\"$l_config\")\n done < <(modprobe --showconfig | grep -P '^\\h*(blacklist|install)')\n for l_mod_name in \"${a_available_modules[@]}\"; do # Iterate over all filesystem modules\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_name=\"${l_mod_name::-2}\"\n if grep -Pq -- \"\\b$l_mod_name\\b\" <<< \"${a_ignore[*]}\"; then\n a_excluded+=(\" - Kernel module: \\\"$l_mod_name\\\"\")\n else\n f_module_chk\n fi\n done\n [ \"${#a_excluded[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \\\n \"The following intentionally skipped\" \\\n \"${a_excluded[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \" - No unused filesystem kernel modules are enabled\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"-- Audit Result: --\" \" ** REVIEW the following **\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"-- Correctly set: --\" \"${a_output[@]}\" \"\"\n fi\n}\n```\n\n**WARNING**: disabling or denylisting filesystem modules that are in use on the system may be FATAL. It is extremely important to thoroughly review this list." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** the module is available in the running kernel:\n\n- Unload the filesystem kernel module from the kernel\n\n- Create a file ending in `.conf` with install filesystem kernel modules `/bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with deny list filesystem kernel modules in the `/etc/modprobe.d/` directory\n\n**WARNING**: unloading, disabling or denylisting filesystem modules that are in use on the system maybe FATAL. It is extremely important to thoroughly review the filesystems returned by the audit before following the remediation procedure.\n\n*Example of unloading the `gfs2`kernel module:*\n\n```\n# modprobe -r gfs2 2>/dev/null\n# rmmod gfs2 2>/dev/null\n```\n\n*Example of fully disabling the `gfs2` kernel module:*\n\n```\n# printf '%s\\n' \"blacklist gfs2\" \"install gfs2 /bin/false\" >> /etc/modprobe.d/gfs2.conf\n```\n\n**Note:**\n\n- Disabling a kernel module by modifying the command above for each unused filesystem kernel module\n\n- The example `gfs2` must be updated with the appropriate module name for the command or example script bellow to run correctly.\n\n**Below is an example Script that can be modified to use on various filesystem kernel modules manual remediation process:**\n\n*Example Script*\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=(); a_output3=(); l_dl=\"\" # Initialize arrays and clear variables\n l_mod_name=\"gfs2\" # set module name\n l_mod_type=\"fs\" # set module type\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" # Set to ignore duplicate checks\n a_showconfig=() # Create array with modprobe output\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_name\" &> /dev/null; then # Check if the module is currently loaded\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n echo -e \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```\n\nImpact:\n\nThis list may be quite extensive and covering all edges cases is difficult. Therefore, it's crucial to carefully consider the implications and dependencies before making any changes to the filesystem kernel module configurations." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1.2_Configure_Filesystem_Partitions", + "title": "Configure Filesystem Partitions", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1.2.1_Configure_tmp", + "title": "Configure /tmp", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition", + "title": "1.1.2.1.1 Ensure /tmp is a separate partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_exists_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/tmp" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition_smt", + "name": "statement", + "prose": "The `/tmp` directory is a world-writable directory used for temporary storage by all users and some applications.\n\n**- IF -** an entry for `/tmp` exists in `/etc/fstab` it will take precedence over entries in systemd default unit file.\n\n**Note:** In an environment where the main system is diskless and connected to iSCSI, entries in `/etc/fstab` may not take precedence.\n\n`/tmp` can be configured to use `tmpfs`.\n\n`tmpfs` puts everything into the kernel internal caches and grows and shrinks to accommodate the files it contains and is able to swap unneeded pages out to swap space. It has maximum size limits which can be adjusted on the fly via `mount -o remount`.\n\nSince `tmpfs` lives completely in the page cache and on swap, all `tmpfs` pages will be shown as \"Shmem\" in `/proc/meminfo` and \"Shared\" in `free`. Notice that these counters also include shared memory. The most reliable way to get the count is using `df` and `du`.\n\n`tmpfs` has three mount options for sizing:\n\n- `size`: The limit of allocated bytes for this `tmpfs` instance. The default is half of your physical RAM without swap. If you oversize your `tmpfs` instances the machine will deadlock since the OOM handler will not be able to free that memory.\n\n- `nr_blocks`: The same as size, but in blocks of PAGE_SIZE.\n\n- `nr_inodes`: The maximum number of inodes for this instance. The default is half of the number of your physical RAM pages, or (on a machine with highmem) the number of lowmem RAM pages, whichever is the lower.\n\nThese parameters accept a suffix k, m or g and can be changed on remount. The size parameter also accepts a suffix % to limit this `tmpfs` instance to that percentage of your physical RAM. The default, when neither `size` nor `nr_blocks` is specified, is `size=50%`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition_rationale", + "name": "rationale", + "prose": "Making `/tmp` its own file system allows an administrator to set additional mount options such as the `noexec` option on the mount, making `/tmp` useless for an attacker to install executable code. It would also prevent an attacker from establishing a hard link to a system `setuid` program and wait for it to be updated. Once the program was updated, the hard link would be broken, and the attacker would have his own copy of the program. If the program happened to have a security vulnerability, the attacker could continue to exploit the known flaw.\n\nThis can be accomplished by either mounting `tmpfs` to `/tmp`, or creating a separate partition for `/tmp`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition_obj", + "name": "assessment-objective", + "prose": "Ensure /tmp is a separate partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition_obj" + }, + { + "rel": "script", + "href": "#42b4ed84-8173-56f8-a824-927d22ea68c0" + } + ], + "prose": "Run the following command and verify the output shows that `/tmp` is mounted. Particular requirements pertaining to mount options are covered in ensuing sections.\n\n```\n# findmnt -kn /tmp\n```\n\n*Example output:*\n\n```\n/tmp tmpfs tmpfs rw,nosuid,nodev,noexec\n```\n\nEnsure that systemd will mount the `/tmp` partition at boot time.\n\n```\n# systemctl is-enabled tmp.mount\n```\n\n*Example output:*\n\n```\ngenerated\n```\n\nVerify output is not `masked` or `disabled`.\n\n**Note:** By default, systemd will output `generated` if there is an entry in `/etc/fstab` for `/tmp`. This just means systemd will use the entry in `/etc/fstab` instead of its default unit file configuration for `/tmp`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "First ensure that systemd is correctly configured to ensure that `/tmp` will be mounted at boot time.\n\n```\n# systemctl unmask tmp.mount\n```\n\nFor specific configuration requirements of the `/tmp` mount for your environment, modify `/etc/fstab`.\n\nExample of using `tmpfs` with specific mount options:\n\n```\ntmpfs\t/tmp\ttmpfs defaults,rw,nosuid,nodev,noexec,relatime,size=2G 0 0\n```\n\n**Note:** the `size=2G` is an example of setting a specific size for `tmpfs`.\n\nExample of using a volume or disk with specific mount options. The source location of the volume or disk will vary depending on your environment:\n\n```\n /tmp defaults,nodev,nosuid,noexec 0 0\n```\n\nImpact:\n\nBy design files saved to `/tmp` should have no expectation of surviving a reboot of the system. `tmpfs` is ram based and all files stored to `tmpfs` will be lost when the system is rebooted.\n\nIf files need to be persistent through a reboot, they should be saved to `/var/tmp` not `/tmp`.\n\nSince the `/tmp` directory is intended to be world-writable, there is a risk of resource exhaustion if it is not bound to `tmpfs` or a separate partition.\n\nRunning out of `/tmp` space is a problem regardless of what kind of filesystem lies under it, but in a configuration where `/tmp` is not a separate file system it will essentially have the whole disk available, as the default installation only creates a single `/` partition. On the other hand, a RAM-based `/tmp` (as with `tmpfs`) will almost certainly be much smaller, which can lead to applications filling up the filesystem much more easily. Another alternative is to create a dedicated partition for `/tmp` from a separate volume or disk. One of the downsides of a disk-based dedicated partition is that it will be slower than `tmpfs` which is RAM-based." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition", + "title": "1.1.2.1.2 Ensure nodev option set on /tmp partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/tmp:nodev" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition_smt", + "name": "statement", + "prose": "The `nodev` mount option specifies that the filesystem cannot contain special devices." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition_rationale", + "name": "rationale", + "prose": "Since the `/tmp` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/tmp`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nodev option set on /tmp partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/tmp`, verify that the `nodev` option is set.\n\nRun the following command to verify that the `nodev` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /tmp | grep -v nodev\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/tmp`.\n\nEdit the `/etc/fstab` file and add `nodev` to the fourth field (mounting options) for the `/tmp` partition.\n\n*Example:*\n\n```\n /tmp defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/tmp` with the configured options:\n\n```\n# mount -o remount /tmp\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition", + "title": "1.1.2.1.3 Ensure nosuid option set on /tmp partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/tmp:nosuid" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition_smt", + "name": "statement", + "prose": "The `nosuid` mount option specifies that the filesystem cannot contain `setuid` files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition_rationale", + "name": "rationale", + "prose": "Since the `/tmp` filesystem is only intended for temporary file storage, set this option to ensure that users cannot create `setuid` files in `/tmp`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nosuid option set on /tmp partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/tmp`, verify that the `nosuid` option is set.\n\nRun the following command to verify that the `nosuid` mount option is set.\n\nExample:\n\n```\n# findmnt -kn /tmp | grep -v nosuid\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/tmp`.\n\nEdit the `/etc/fstab` file and add `nosuid` to the fourth field (mounting options) for the `/tmp` partition.\n\nExample:\n\n```\n /tmp defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/tmp` with the configured options:\n\n```\n# mount -o remount /tmp\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition", + "title": "1.1.2.1.4 Ensure noexec option set on /tmp partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/tmp:noexec" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition_smt", + "name": "statement", + "prose": "The `noexec` mount option specifies that the filesystem cannot contain executable binaries." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition_rationale", + "name": "rationale", + "prose": "Since the `/tmp` filesystem is only intended for temporary file storage, set this option to ensure that users cannot run executable binaries from `/tmp`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition_obj", + "name": "assessment-objective", + "prose": "Ensure noexec option set on /tmp partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/tmp`, verify that the `noexec` option is set.\n\nRun the following command to verify that the `noexec` mount option is set.\n\nExample:\n\n```\n# findmnt -kn /tmp | grep -v noexec\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/tmp`.\n\nEdit the `/etc/fstab` file and add `noexec` to the fourth field (mounting options) for the `/tmp` partition.\n\nExample:\n\n```\n /tmp defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/tmp` with the configured options:\n\n```\n# mount -o remount /tmp\n```\n\nImpact:\n\nSetting the `noexec` option on `/tmp` may prevent installation and/or updating of some 3rd party software." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1.2.2_Configure_devshm", + "title": "Configure /dev/shm", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition", + "title": "1.1.2.2.1 Ensure /dev/shm is a separate partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_exists_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/dev/shm" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition_smt", + "name": "statement", + "prose": "The `/dev/shm` directory is a world-writable directory that can function as shared memory that facilitates inter process communication (IPC)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition_rationale", + "name": "rationale", + "prose": "Making `/dev/shm` its own file system allows an administrator to set additional mount options such as the `noexec` option on the mount, making `/dev/shm` useless for an attacker to install executable code. It would also prevent an attacker from establishing a hard link to a system `setuid` program and wait for it to be updated. Once the program was updated, the hard link would be broken and the attacker would have his own copy of the program. If the program happened to have a security vulnerability, the attacker could continue to exploit the known flaw.\n\nThis can be accomplished by mounting `tmpfs` to `/dev/shm`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition_obj", + "name": "assessment-objective", + "prose": "Ensure /dev/shm is a separate partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition_obj" + }, + { + "rel": "script", + "href": "#42b4ed84-8173-56f8-a824-927d22ea68c0" + } + ], + "prose": "**-IF-** `/dev/shm` is to be used on the system, run the following command and verify the output shows that `/dev/shm` is mounted. Particular requirements pertaining to mount options are covered in ensuing sections.\n\n```\n# findmnt -kn /dev/shm\n```\n\n*Example output:*\n\n```\n/dev/shm tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,seclabel\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "For specific configuration requirements of the `/dev/shm` mount for your environment, modify `/etc/fstab`.\n\n*Example:*\n\n```\ntmpfs\t/dev/shm\ttmpfs defaults,rw,nosuid,nodev,noexec,relatime,size=2G 0 0\n```\n\nImpact:\n\nSince the `/dev/shm` directory is intended to be world-writable, there is a risk of resource exhaustion if it is not bound to a separate partition.\n\n`/dev/shm` utilizing `tmpfs` can be resized using the `size={size}` parameter in the relevant entry in `/etc/fstab`." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition", + "title": "1.1.2.2.2 Ensure nodev option set on /dev/shm partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/dev/shm:nodev" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition_smt", + "name": "statement", + "prose": "The `nodev` mount option specifies that the filesystem cannot contain special devices." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition_rationale", + "name": "rationale", + "prose": "Since the `/dev/shm` filesystem is not intended to support devices, set this option to ensure that users cannot attempt to create special devices in `/dev/shm` partitions." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nodev option set on /dev/shm partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/dev/shm`, verify that the `nodev` option is set.\n\n```\n# findmnt -kn /dev/shm | grep -v 'nodev'\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/dev/shm`.\n\nEdit the `/etc/fstab` file and add `nodev` to the fourth field (mounting options) for the `/dev/shm` partition. See the `fstab(5)` manual page for more information.\n\n*Example:*\n\n```\ntmpfs /dev/shm tmpfs defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/dev/shm` with the configured options:\n\n```\n# mount -o remount /dev/shm\n```\n\n**Note:** It is recommended to use `tmpfs` as the device/filesystem type as `/dev/shm` is used as shared memory space by applications." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition", + "title": "1.1.2.2.3 Ensure nosuid option set on /dev/shm partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/dev/shm:nosuid" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition_smt", + "name": "statement", + "prose": "The `nosuid` mount option specifies that the filesystem cannot contain `setuid` files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition_rationale", + "name": "rationale", + "prose": "Setting this option on a file system prevents users from introducing privileged programs onto the system and allowing non-root users to execute them." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nosuid option set on /dev/shm partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/dev/shm`, verify that the `nosuid` option is set.\n\n```\n# findmnt -kn /dev/shm | grep -v 'nosuid'\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/dev/shm`.\n\nEdit the `/etc/fstab` file and add `nosuid` to the fourth field (mounting options) for the `/dev/shm` partition. See the `fstab(5)` manual page for more information.\n\n*Example:*\n\n```\ntmpfs /dev/shm tmpfs defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/dev/shm` with the configured options:\n\n```\n# mount -o remount /dev/shm\n```\n\n**Note:** It is recommended to use `tmpfs` as the device/filesystem type as `/dev/shm` is used as shared memory space by applications." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition", + "title": "1.1.2.2.4 Ensure noexec option set on /dev/shm partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/dev/shm:noexec" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition_smt", + "name": "statement", + "prose": "The `noexec` mount option specifies that the filesystem cannot contain executable binaries." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition_rationale", + "name": "rationale", + "prose": "Setting this option on a file system prevents users from executing programs from shared memory. This deters users from introducing potentially malicious software on the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition_obj", + "name": "assessment-objective", + "prose": "Ensure noexec option set on /dev/shm partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/dev/shm`, verify that the `noexec` option is set.\n\n```\n# findmnt -kn /dev/shm | grep -v 'noexec'\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/dev/shm`.\n\nEdit the `/etc/fstab` file and add `noexec` to the fourth field (mounting options) for the `/dev/shm` partition.\n\n*Example:*\n\n```\ntmpfs /dev/shm tmpfs defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/dev/shm` with the configured options:\n\n```\n# mount -o remount /dev/shm\n```\n\n**Note:** It is recommended to use `tmpfs` as the device/filesystem type as `/dev/shm` is used as shared memory space by applications." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1.2.3_Configure_home", + "title": "Configure /home", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home", + "title": "1.1.2.3.1 Ensure separate partition exists for /home", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_exists_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/home" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home_smt", + "name": "statement", + "prose": "The `/home` directory is used to support disk storage needs of local users." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home_rationale", + "name": "rationale", + "prose": "The default installation only creates a single `/` partition. Since the `/home` directory contains user generated data, there is a risk of resource exhaustion. It will essentially have the whole disk available to fill up and impact the system as a whole. In addition, other operations on the system could fill up the disk unrelated to `/home` and impact all local users.\n\nConfiguring `/home` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attacker's ability to create exploits on the system. In the case of `/home` options such as `usrquota/grpquota` may be considered to limit the impact that users can have on each other with regards to disk resource exhaustion. Other options allow for specific behavior. See `man mount` for exact details regarding filesystem-independent and filesystem-specific options.\n\nAs `/home` contains user data, care should be taken to ensure the security and integrity of the data and mount point." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home_obj", + "name": "assessment-objective", + "prose": "Ensure separate partition exists for /home" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home_obj" + }, + { + "rel": "script", + "href": "#42b4ed84-8173-56f8-a824-927d22ea68c0" + } + ], + "prose": "Run the following command and verify output shows `/home` is mounted:\n\n```\n# findmnt -kn /home\n\n/home /dev/sdb ext4 rw,nosuid,nodev,noexec,relatime,seclabel\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "For new installations, during installation create a custom partition setup and specify a separate partition for `/home`.\n\nFor systems that were previously installed, create a new partition and configure `/etc/fstab` as appropriate.\n\nImpact:\n\nResizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition", + "title": "1.1.2.3.2 Ensure nodev option set on /home partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/home:nodev" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition_smt", + "name": "statement", + "prose": "The `nodev` mount option specifies that the filesystem cannot contain special devices." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition_rationale", + "name": "rationale", + "prose": "Since the `/home` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/home`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nodev option set on /home partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/home`, verify that the `nodev` option is set.\n\nRun the following command to verify that the `nodev` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /home | grep -v nodev\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/home`.\n\nEdit the `/etc/fstab` file and add `nodev` to the fourth field (mounting options) for the `/home` partition.\n\n*Example:*\n\n```\n /home defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/home` with the configured options:\n\n```\n# mount -o remount /home\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition", + "title": "1.1.2.3.3 Ensure nosuid option set on /home partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/home:nosuid" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition_smt", + "name": "statement", + "prose": "The `nosuid` mount option specifies that the filesystem cannot contain `setuid` files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition_rationale", + "name": "rationale", + "prose": "Since the `/home` filesystem is only intended for user file storage, set this option to ensure that users cannot create `setuid` files in `/home`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nosuid option set on /home partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/home`, verify that the `nosuid` option is set.\n\nRun the following command to verify that the `nosuid` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /home | grep -v nosuid\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/home`.\n\nEdit the `/etc/fstab` file and add `nosuid` to the fourth field (mounting options) for the `/home` partition.\n\n*Example:*\n\n```\n /home defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/home` with the configured options:\n\n```\n# mount -o remount /home\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1.2.4_Configure_var", + "title": "Configure /var", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var", + "title": "1.1.2.4.1 Ensure separate partition exists for /var", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_exists_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var_smt", + "name": "statement", + "prose": "The `/var` directory is used by daemons and other system services to temporarily store dynamic data. Some directories created by these processes may be world-writable." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var_rationale", + "name": "rationale", + "prose": "The reasoning for mounting `/var` on a separate partition is as follows.\n\nThe default installation only creates a single `/` partition. Since the `/var` directory may contain world writable files and directories, there is a risk of resource exhaustion. It will essentially have the whole disk available to fill up and impact the system. In addition, other operations on the system could fill up the disk unrelated to `/var` and cause unintended behavior across the system as the disk is full. See `man auditd.conf` for details.\n\nConfiguring `/var` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attacker's ability to create exploits on the system. Other options allow for specific behavior. See `man mount` for exact details regarding filesystem-independent and filesystem-specific options.\n\nAn example of exploiting `/var` may be an attacker establishing a hard-link to a system `setuid` program and waiting for it to be updated. Once the program is updated, the hard-link can be broken and the attacker would have their own copy of the program. If the program happened to have a security vulnerability, the attacker could continue to exploit the known flaw." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var_obj", + "name": "assessment-objective", + "prose": "Ensure separate partition exists for /var" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var_obj" + }, + { + "rel": "script", + "href": "#42b4ed84-8173-56f8-a824-927d22ea68c0" + } + ], + "prose": "Run the following command and verify output shows `/var` is mounted.\n\n*Example:*\n\n```\n# findmnt -kn /var\n\n/var /dev/sdb ext4 rw,nosuid,nodev,noexec,relatime,seclabel\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "For new installations, during installation create a custom partition setup and specify a separate partition for `/var`.\n\nFor systems that were previously installed, create a new partition and configure `/etc/fstab` as appropriate.\n\nImpact:\n\nResizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition", + "title": "1.1.2.4.2 Ensure nodev option set on /var partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var:nodev" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition_smt", + "name": "statement", + "prose": "The `nodev` mount option specifies that the filesystem cannot contain special devices." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition_rationale", + "name": "rationale", + "prose": "Since the `/var` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/var`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nodev option set on /var partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var`, verify that the `nodev` option is set.\n\nRun the following command to verify that the `nodev` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var | grep -v nodev\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var`.\n\nEdit the `/etc/fstab` file and add `nodev` to the fourth field (mounting options) for the `/var` partition.\n\n*Example:*\n\n```\n /var defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var` with the configured options:\n\n```\n# mount -o remount /var\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition", + "title": "1.1.2.4.3 Ensure nosuid option set on /var partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var:nosuid" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition_smt", + "name": "statement", + "prose": "The `nosuid` mount option specifies that the filesystem cannot contain `setuid` files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition_rationale", + "name": "rationale", + "prose": "Since the `/var` filesystem is only intended for variable files such as logs, set this option to ensure that users cannot create `setuid` files in `/var`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nosuid option set on /var partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var`, verify that the `nosuid` option is set.\n\nRun the following command to verify that the `nosuid` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var | grep -v nosuid\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var`.\n\nEdit the `/etc/fstab` file and add `nosuid` to the fourth field (mounting options) for the `/var` partition.\n\n*Example:*\n\n```\n /var defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var` with the configured options:\n\n```\n# mount -o remount /var\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1.2.5_Configure_vartmp", + "title": "Configure /var/tmp", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp", + "title": "1.1.2.5.1 Ensure separate partition exists for /var/tmp", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_exists_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/tmp" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp_smt", + "name": "statement", + "prose": "The `/var/tmp` directory is a world-writable directory used for temporary storage by all users and some applications. Temporary files residing in `/var/tmp` are to be preserved between reboots." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp_rationale", + "name": "rationale", + "prose": "The default installation only creates a single `/` partition. Since the `/var/tmp` directory is world-writable, there is a risk of resource exhaustion. In addition, other operations on the system could fill up the disk unrelated to `/var/tmp` and cause potential disruption to daemons as the disk is full.\n\nConfiguring `/var/tmp` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attacker's ability to create exploits on the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp_obj", + "name": "assessment-objective", + "prose": "Ensure separate partition exists for /var/tmp" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp_obj" + }, + { + "rel": "script", + "href": "#42b4ed84-8173-56f8-a824-927d22ea68c0" + } + ], + "prose": "Run the following command and verify output shows `/var/tmp` is mounted.\n\n*Example:*\n\n```\n# findmnt -kn /var/tmp\n\n/var/tmp /dev/sdb ext4 rw,nosuid,nodev,noexec,relatime,seclabel\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "For new installations, during installation create a custom partition setup and specify a separate partition for `/var/tmp`.\n\nFor systems that were previously installed, create a new partition and configure `/etc/fstab` as appropriate.\n\nImpact:\n\nResizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition", + "title": "1.1.2.5.2 Ensure nodev option set on /var/tmp partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/tmp:nodev" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition_smt", + "name": "statement", + "prose": "The `nodev` mount option specifies that the filesystem cannot contain special devices." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition_rationale", + "name": "rationale", + "prose": "Since the `/var/tmp` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/var/tmp`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nodev option set on /var/tmp partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var/tmp`, verify that the `nodev` option is set.\n\nRun the following command to verify that the `nodev` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var/tmp | grep -v nodev\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var/tmp`.\n\nEdit the `/etc/fstab` file and add `nodev` to the fourth field (mounting options) for the `/var/tmp` partition.\n\n*Example:*\n\n```\n /var/tmp defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var/tmp` with the configured options:\n\n```\n# mount -o remount /var/tmp\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition", + "title": "1.1.2.5.3 Ensure nosuid option set on /var/tmp partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/tmp:nosuid" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition_smt", + "name": "statement", + "prose": "The `nosuid` mount option specifies that the filesystem cannot contain `setuid` files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition_rationale", + "name": "rationale", + "prose": "Since the `/var/tmp` filesystem is only intended for temporary file storage, set this option to ensure that users cannot create `setuid` files in `/var/tmp`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nosuid option set on /var/tmp partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var/tmp`, verify that the `nosuid` option is set.\n\nRun the following command to verify that the `nosuid` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var/tmp | grep -v nosuid\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var/tmp`.\n\nEdit the `/etc/fstab` file and add `nosuid` to the fourth field (mounting options) for the `/var/tmp` partition.\n\n*Example:*\n\n```\n /var/tmp defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var/tmp` with the configured options:\n\n```\n# mount -o remount /var/tmp\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition", + "title": "1.1.2.5.4 Ensure noexec option set on /var/tmp partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/tmp:noexec" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition_smt", + "name": "statement", + "prose": "The `noexec` mount option specifies that the filesystem cannot contain executable binaries." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition_rationale", + "name": "rationale", + "prose": "Since the `/var/tmp` filesystem is only intended for temporary file storage, set this option to ensure that users cannot run executable binaries from `/var/tmp`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition_obj", + "name": "assessment-objective", + "prose": "Ensure noexec option set on /var/tmp partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var/tmp`, verify that the `noexec` option is set.\n\nRun the following command to verify that the `noexec` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var/tmp | grep -v noexec\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var/tmp`.\n\nEdit the `/etc/fstab` file and add `noexec` to the fourth field (mounting options) for the `/var/tmp` partition.\n\n*Example:*\n\n```\n /var/tmp defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var/tmp` with the configured options:\n\n```\n# mount -o remount /var/tmp\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1.2.6_Configure_varlog", + "title": "Configure /var/log", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog", + "title": "1.1.2.6.1 Ensure separate partition exists for /var/log", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_exists_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/log" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog_smt", + "name": "statement", + "prose": "The `/var/log` directory is used by system services to store log data." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog_rationale", + "name": "rationale", + "prose": "The default installation only creates a single `/` partition. Since the `/var/log` directory contains log files which can grow quite large, there is a risk of resource exhaustion. It will essentially have the whole disk available to fill up and impact the system as a whole.\n\nConfiguring `/var/log` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attackers ability to create exploits on the system. Other options allow for specific behavior. See `man mount` for exact details regarding filesystem-independent and filesystem-specific options.\n\nAs `/var/log` contains log files, care should be taken to ensure the security and integrity of the data and mount point." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog_obj", + "name": "assessment-objective", + "prose": "Ensure separate partition exists for /var/log" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog_obj" + }, + { + "rel": "script", + "href": "#42b4ed84-8173-56f8-a824-927d22ea68c0" + } + ], + "prose": "Run the following command and verify output shows `/var/log` is mounted:\n\n```\n# findmnt -kn /var/log\n\n/var/log /dev/sdb ext4 rw,nosuid,nodev,noexec,relatime,seclabel\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "For new installations, during installation create a custom partition setup and specify a separate partition for `/var/log` .\n\nFor systems that were previously installed, create a new partition and configure `/etc/fstab` as appropriate.\n\nImpact:\n\nResizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing, or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition", + "title": "1.1.2.6.2 Ensure nodev option set on /var/log partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/log:nodev" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition_smt", + "name": "statement", + "prose": "The `nodev` mount option specifies that the filesystem cannot contain special devices." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition_rationale", + "name": "rationale", + "prose": "Since the `/var/log` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/var/log`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nodev option set on /var/log partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var/log`, verify that the `nodev` option is set.\n\nRun the following command to verify that the `nodev` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var/log | grep -v nodev\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var/log`.\n\nEdit the `/etc/fstab` file and add `nodev` to the fourth field (mounting options) for the `/var/log` partition.\n\n*Example:*\n\n```\n /var/log defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var/log` with the configured options:\n\n```\n# mount -o remount /var/log\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition", + "title": "1.1.2.6.3 Ensure nosuid option set on /var/log partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/log:nosuid" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition_smt", + "name": "statement", + "prose": "The `nosuid` mount option specifies that the filesystem cannot contain `setuid` files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition_rationale", + "name": "rationale", + "prose": "Since the `/var/log` filesystem is only intended for log files, set this option to ensure that users cannot create `setuid` files in `/var/log`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nosuid option set on /var/log partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var/log`, verify that the `nosuid` option is set.\n\nRun the following command to verify that the `nosuid` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var/log | grep -v nosuid\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var/log`.\n\nEdit the `/etc/fstab` file and add `nosuid` to the fourth field (mounting options) for the `/var/log` partition.\n\n*Example:*\n\n```\n /var/log defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var/log` with the configured options:\n\n```\n# mount -o remount /var/log\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition", + "title": "1.1.2.6.4 Ensure noexec option set on /var/log partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/log:noexec" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition_smt", + "name": "statement", + "prose": "The `noexec` mount option specifies that the filesystem cannot contain executable binaries." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition_rationale", + "name": "rationale", + "prose": "Since the `/var/log` filesystem is only intended for log files, set this option to ensure that users cannot run executable binaries from `/var/log`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition_obj", + "name": "assessment-objective", + "prose": "Ensure noexec option set on /var/log partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var/log`, verify that the `noexec` option is set.\n\nRun the following command to verify that the `noexec` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var/log | grep -v noexec\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var/log`.\n\nEdit the `/etc/fstab` file and add `noexec` to the fourth field (mounting options) for the `/var/log` partition.\n\n*Example:*\n\n```\n /var/log defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var/log` with the configured options:\n\n```\n# mount -o remount /var/log\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.1.2.7_Configure_varlogaudit", + "title": "Configure /var/log/audit", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit", + "title": "1.1.2.7.1 Ensure separate partition exists for /var/log/audit", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_exists_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/log/audit" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit_smt", + "name": "statement", + "prose": "The auditing daemon, `auditd`, stores log data in the `/var/log/audit` directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit_rationale", + "name": "rationale", + "prose": "The default installation only creates a single `/` partition. Since the `/var/log/audit` directory contains the `audit.log` file which can grow quite large, there is a risk of resource exhaustion. It will essentially have the whole disk available to fill up and impact the system as a whole. In addition, other operations on the system could fill up the disk unrelated to `/var/log/audit` and cause `auditd` to trigger its `space_left_action` as the disk is full. See `man auditd.conf` for details.\n\nConfiguring `/var/log/audit` as its own file system allows an administrator to set additional mount options such as `noexec/nosuid/nodev`. These options limit an attacker's ability to create exploits on the system. Other options allow for specific behavior. See `man mount` for exact details regarding filesystem-independent and filesystem-specific options.\n\nAs `/var/log/audit` contains audit logs, care should be taken to ensure the security and integrity of the data and mount point." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit_obj", + "name": "assessment-objective", + "prose": "Ensure separate partition exists for /var/log/audit" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit_obj" + }, + { + "rel": "script", + "href": "#42b4ed84-8173-56f8-a824-927d22ea68c0" + } + ], + "prose": "Run the following command and verify output shows `/var/log/audit` is mounted:\n\n```\n# findmnt -kn /var/log/audit\n\n/var/log/audit /dev/sdb ext4 rw,nosuid,nodev,noexec,relatime,seclabel\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "For new installations, during installation create a custom partition setup and specify a separate partition for `/var/log/audit`.\n\nFor systems that were previously installed, create a new partition and configure `/etc/fstab` as appropriate.\n\nImpact:\n\nResizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition", + "title": "1.1.2.7.2 Ensure nodev option set on /var/log/audit partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/log/audit:nodev" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition_smt", + "name": "statement", + "prose": "The `nodev` mount option specifies that the filesystem cannot contain special devices." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition_rationale", + "name": "rationale", + "prose": "Since the `/var/log/audit` filesystem is not intended to support devices, set this option to ensure that users cannot create a block or character special devices in `/var/log/audit`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nodev option set on /var/log/audit partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var/log/audit`, verify that the `nodev` option is set.\n\nRun the following command to verify that the `nodev` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var/log/audit | grep -v nodev\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var/log/audit`.\n\nEdit the `/etc/fstab` file and add `nodev` to the fourth field (mounting options) for the `/var/log/audit` partition.\n\n*Example:*\n\n```\n /var/log/audit defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var/log/audit` with the configured options:\n\n```\n# mount -o remount /var/log/audit\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition", + "title": "1.1.2.7.3 Ensure nosuid option set on /var/log/audit partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/log/audit:nosuid" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition_smt", + "name": "statement", + "prose": "The `nosuid` mount option specifies that the filesystem cannot contain `setuid` files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition_rationale", + "name": "rationale", + "prose": "Since the `/var/log/audit` filesystem is only intended for variable files such as logs, set this option to ensure that users cannot create `setuid` files in `/var/log/audit`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition_obj", + "name": "assessment-objective", + "prose": "Ensure nosuid option set on /var/log/audit partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var/log/audit`, verify that the `nosuid` option is set.\n\nRun the following command to verify that the `nosuid` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var/log/audit | grep -v nosuid\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var/log/audit`.\n\nEdit the `/etc/fstab` file and add `nosuid` to the fourth field (mounting options) for the `/var/log/audit` partition.\n\n*Example:*\n\n```\n /var/log/audit defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var/log/audit` with the configured options:\n\n```\n# mount -o remount /var/log/audit\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition", + "title": "1.1.2.7.4 Ensure noexec option set on /var/log/audit partition", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_mount_point_option_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/var/log/audit:noexec" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition_smt", + "name": "statement", + "prose": "The `noexec` mount option specifies that the filesystem cannot contain executable binaries." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition_rationale", + "name": "rationale", + "prose": "Since the `/var/log/audit` filesystem is only intended for audit logs, set this option to ensure that users cannot run executable binaries from `/var/log/audit`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition_obj", + "name": "assessment-objective", + "prose": "Ensure noexec option set on /var/log/audit partition" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition_obj" + }, + { + "rel": "script", + "href": "#504ee9c5-f07f-5edd-bb9a-22368a870987" + } + ], + "prose": "**- IF -** a separate partition exists for `/var/log/audit`, verify that the `noexec` option is set.\n\nRun the following command to verify that the `noexec` mount option is set.\n\n*Example:*\n\n```\n# findmnt -kn /var/log/audit | grep -v noexec\n\nNothing should be returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a separate partition exists for `/var/log/audit`.\n\nEdit the `/etc/fstab` file and add `noexec` to the fourth field (mounting options) for the `/var/log/audit` partition.\n\n*Example:*\n\n```\n /var/log/audit defaults,rw,nosuid,nodev,noexec,relatime 0 0\n```\n\nRun the following command to remount `/var/log/audit` with the configured options:\n\n```\n# mount -o remount /var/log/audit\n```" + } + ] + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.2_Package_Management", + "title": "Package Management", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.2.1_Configure_Package_Repositories", + "title": "Configure Package Repositories", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured", + "title": "1.2.1.1 Ensure GPG keys are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/7/subcontrol/3" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/7/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured_smt", + "name": "statement", + "prose": "Most package managers implement GPG key signing to verify package integrity during installation." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured_rationale", + "name": "rationale", + "prose": "It is important to ensure that updates are obtained from a valid source to protect against spoofing that could lead to the inadvertent installation of malware on the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure GPG keys are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured_obj" + } + ], + "prose": "Verify GPG keys are configured correctly for your package manager:\n\n```\n# apt-key list\n```\n\n**Note:**\n\n- `apt-key list` is deprecated. Manage keyring files in `trusted.gpg.d` instead (see apt-key(8)).\n\n- With the deprecation of `apt-key` it is recommended to use the `Signed-By` option in `sources.list` to require a repository to pass apt-secure(8) verification with a certain set of keys rather than all trusted keys apt has configured.\n\n**- OR -**\n\n- Run the following script and verify GPG keys are configured correctly for your package manager:\n\n```\n#! /usr/bin/env bash\n\n{\n for file in /etc/apt/trusted.gpg.d/*.{gpg,asc} /etc/apt/sources.list.d/*.{gpg,asc} ; do\n if [ -f \"$file\" ]; then\n echo -e \"File: $file\"\n gpg --list-packets \"$file\" 2>/dev/null | awk '/keyid/ && !seen[$NF]++ {print \"keyid:\", $NF}'\n gpg --list-packets \"$file\" 2>/dev/null | awk '/Signed-By:/ {print \"signed-by:\", $NF}'\n echo -e\n fi\n done\n}\n```\n\n- REVIEW and VERIFY to ensure that GPG keys are configured correctly for your package manager IAW site policy." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Update your package manager GPG keys in accordance with site policy." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured", + "title": "1.2.1.2 Ensure package manager repositories are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/7/subcontrol/3" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/7/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured_smt", + "name": "statement", + "prose": "Systems need to have package manager repositories configured to ensure they receive the latest patches and updates." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured_rationale", + "name": "rationale", + "prose": "If a system's package repositories are misconfigured important patches may not be identified or a rogue repository could introduce compromised software." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure package manager repositories are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured_obj" + } + ], + "prose": "Run the following command and verify package repositories are configured correctly:\n\n```\n# apt-cache policy\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure your package manager repositories according to site policy." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.2.2_Configure_Package_Updates", + "title": "Configure Package Updates", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed", + "title": "1.2.2.1 Ensure updates, patches, and additional security software are installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/7/subcontrol/3" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/7/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed_smt", + "name": "statement", + "prose": "Periodically patches are released for included software either due to security flaws or to include additional functionality." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed_rationale", + "name": "rationale", + "prose": "Newer patches may contain security enhancements that would not be available through the latest full update. As a result, it is recommended that the latest software patches be used to take advantage of the latest functionality. As with any software installation, organizations need to determine if a given update meets their requirements and verify the compatibility and supportability of any additional software against the update revision that is selected." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed_obj", + "name": "assessment-objective", + "prose": "Ensure updates, patches, and additional security software are installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed_obj" + } + ], + "prose": "Verify there are no updates or patches to install:\n\n```\n# apt update\n# apt -s upgrade\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to update all packages following local site policy guidance on applying updates and patches:\n\n```\n# apt update\n\n# apt upgrade\n - OR -\n# apt dist-upgrade\n```" + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.3_Mandatory_Access_Control", + "title": "Mandatory Access Control", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.3.1_Configure_AppArmor", + "title": "Configure AppArmor", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed", + "title": "1.3.1.1 Ensure AppArmor is installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed_smt", + "name": "statement", + "prose": "AppArmor provides Mandatory Access Controls." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed_rationale", + "name": "rationale", + "prose": "Without a Mandatory Access Control system installed only the default Discretionary Access Control system will be available." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure AppArmor is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed_obj" + } + ], + "prose": "Run the following command to verify that `apparmor` is installed:\n\n```\n# dpkg-query -s apparmor &>/dev/null && echo \"apparmor is installed\"\n\napparmor is installed\n```\n\nRun the following command to verify that `apparmor-utils` is installed:\n\n```\n# dpkg-query -s apparmor-utils &>/dev/null && echo \"apparmor-utils is installed\"\n\napparmor-utils is installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install AppArmor.\n\n```\n# apt install apparmor apparmor-utils\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration", + "title": "1.3.1.2 Ensure AppArmor is enabled in the bootloader configuration", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration_smt", + "name": "statement", + "prose": "Configure AppArmor to be enabled at boot time and verify that it has not been overwritten by the bootloader boot parameters.\n\n**Note:** This recommendation is designed around the grub bootloader, if LILO or another bootloader is in use in your environment enact equivalent settings." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration_rationale", + "name": "rationale", + "prose": "AppArmor must be enabled at boot time in your bootloader configuration to ensure that the controls it provides are not overridden." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration_obj", + "name": "assessment-objective", + "prose": "Ensure AppArmor is enabled in the bootloader configuration" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration_obj" + } + ], + "prose": "Run the following command to verify that all `linux` lines have the `apparmor=1` parameter set:\n\n```\n# grep \"^\\s*linux\" /boot/grub/grub.cfg | grep -v \"apparmor=1\"\n```\n\nNothing should be returned.\n\nRun the following command to verify that all `linux` lines have the `security=apparmor` parameter set:\n\n```\n# grep \"^\\s*linux\" /boot/grub/grub.cfg | grep -v \"security=apparmor\"\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/default/grub` and add the `apparmor=1` and `security=apparmor` parameters to the `GRUB_CMDLINE_LINUX=` line\n\n```\nGRUB_CMDLINE_LINUX=\"apparmor=1 security=apparmor\"\n```\n\nRun the following command to update the `grub2` configuration:\n\n```\n# update-grub\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode", + "title": "1.3.1.3 Ensure all AppArmor Profiles are in enforce or complain mode", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_apparmor_profiles_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "complain" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode_smt", + "name": "statement", + "prose": "AppArmor profiles define what resources applications are able to access." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode_rationale", + "name": "rationale", + "prose": "Security configuration requirements vary from site to site. Some sites may mandate a policy that is stricter than the default policy, which is perfectly acceptable. This item is intended to ensure that any policies that exist on the system are activated." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode_obj", + "name": "assessment-objective", + "prose": "Ensure all AppArmor Profiles are in enforce or complain mode" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode_obj" + }, + { + "rel": "script", + "href": "#b82274ce-0bb5-507b-b87e-750b2ca253ef" + } + ], + "prose": "Run the following command and verify that profiles are loaded, and are in either enforce or complain mode:\n\n```\n# apparmor_status | grep profiles\n```\n\nReview output and ensure that profiles are loaded, and in either enforce or complain mode:\n\n```\n37 profiles are loaded.\n35 profiles are in enforce mode.\n2 profiles are in complain mode.\n4 processes have profiles defined.\n```\n\nRun the following command and verify no processes are unconfined\n\n```\n# apparmor_status | grep processes\n```\n\nReview the output and ensure no processes are unconfined:\n\n```\n4 processes have profiles defined.\n4 processes are in enforce mode.\n0 processes are in complain mode.\n0 processes are unconfined but have a profile defined.\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to set all profiles to enforce mode:\n\n```\n# aa-enforce /etc/apparmor.d/*\n```\n\n**- OR -**\n\nRun the following command to set all profiles to complain mode:\n\n```\n# aa-complain /etc/apparmor.d/*\n```\n\n**Note:** Any unconfined processes may need to have a profile created or activated for them and then be restarted." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing", + "title": "1.3.1.4 Ensure all AppArmor Profiles are enforcing", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_apparmor_profiles_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "enforce" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing_smt", + "name": "statement", + "prose": "AppArmor profiles define what resources applications are able to access." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing_rationale", + "name": "rationale", + "prose": "Security configuration requirements vary from site to site. Some sites may mandate a policy that is stricter than the default policy, which is perfectly acceptable. This item is intended to ensure that any policies that exist on the system are activated." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing_obj", + "name": "assessment-objective", + "prose": "Ensure all AppArmor Profiles are enforcing" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing_obj" + }, + { + "rel": "script", + "href": "#b82274ce-0bb5-507b-b87e-750b2ca253ef" + } + ], + "prose": "Run the following commands and verify that profiles are loaded and are not in complain mode:\n\n```\n# apparmor_status | grep profiles\n```\n\nReview output and ensure that profiles are loaded, and in enforce mode:\n\n```\n34 profiles are loaded.\n34 profiles are in enforce mode.\n0 profiles are in complain mode.\n2 processes have profiles defined.\n```\n\nRun the following command and verify that no processes are unconfined:\n\n```\napparmor_status | grep processes\n```\n\nReview the output and ensure no processes are unconfined:\n\n```\n2 processes have profiles defined.\n2 processes are in enforce mode.\n0 processes are in complain mode.\n0 processes are unconfined but have a profile defined.\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to set all profiles to enforce mode:\n\n```\n# aa-enforce /etc/apparmor.d/*\n```\n\n**Note:** Any unconfined processes may need to have a profile created or activated for them and then be restarted" + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.4_Configure_Bootloader", + "title": "Configure Bootloader", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set", + "title": "1.4.1 Ensure bootloader password is set", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set_smt", + "name": "statement", + "prose": "Setting the boot loader password will require that anyone rebooting the system must enter a password before being able to set command line boot parameters" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set_rationale", + "name": "rationale", + "prose": "Requiring a boot password upon execution of the boot loader will prevent an unauthorized user from entering boot parameters or changing the boot partition. This prevents users from weakening security (e.g. turning off AppArmor at boot time)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set_obj", + "name": "assessment-objective", + "prose": "Ensure bootloader password is set" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set_obj" + } + ], + "prose": "Run the following commands and verify output matches:\n\n```\n# grep \"^set superusers\" /boot/grub/grub.cfg\n\nset superusers=\"\"\n```\n\n```\n# awk -F. '/^\\s*password/ {print $1\".\"$2\".\"$3}' /boot/grub/grub.cfg\n\npassword_pbkdf2 grub.pbkdf2.sha512\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Create an encrypted password with `grub-mkpasswd-pbkdf2`:\n\n```\n# grub-mkpasswd-pbkdf2 --iteration-count=600000 --salt=64\n\nEnter password: \nReenter password: \nPBKDF2 hash of your password is \n```\n\nAdd the following into a custom `/etc/grub.d` configuration file:\n\n```\ncat <\"\npassword_pbkdf2 \nEOF\n```\n\nThe superuser/user information and password should not be contained in the `/etc/grub.d/00_header` file as this file could be overwritten in a package update.\n\nIf there is a requirement to be able to boot/reboot without entering the password, edit `/etc/grub.d/10_linux` and add `--unrestricted` to the line `CLASS=`\n\n*Example:*\n\n```\nCLASS=\"--class gnu-linux --class gnu --class os --unrestricted\"\n```\n\nRun the following command to update the `grub2` configuration:\n\n```\n# update-grub\n```\n\nImpact:\n\nIf password protection is enabled, only the designated superuser can edit a GRUB 2 menu item by pressing \"e\" or access the GRUB 2 command line by pressing \"c\"\n\nIf GRUB 2 is set up to boot automatically to a password-protected menu entry the user has no option to back out of the password prompt to select another menu entry. Holding the SHIFT key will not display the menu in this case. The user must enter the correct username and password. If unable to do so, the configuration files will have to be edited via a LiveCD or other means to fix the problem\n\nYou can add `--unrestricted` to the menu entries to allow the system to boot without entering a password. A password will still be required to edit menu items.\n\nMore Information: [https://help.ubuntu.com/community/Grub2/Passwords](https://help.ubuntu.com/community/Grub2/Passwords)" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured", + "title": "1.4.2 Ensure access to bootloader config is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured_smt", + "name": "statement", + "prose": "The grub configuration file contains information on boot settings and passwords for unlocking boot options." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured_rationale", + "name": "rationale", + "prose": "Setting the permissions to read and write for root only prevents non-root users from seeing the boot parameters or changing them. Non-root users who read the boot parameters may be able to identify weaknesses in security upon boot and be able to exploit them." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure access to bootloader config is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command and verify `Uid` and `Gid` are both `0/root` and `Access` is `0600` or more restrictive.\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /boot/grub/grub.cfg\n\nAccess: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to set permissions on your grub configuration:\n\n```\n# chown root:root /boot/grub/grub.cfg\n# chmod u-x,go-rwx /boot/grub/grub.cfg\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.5_Configure_Additional_Process_Hardening", + "title": "Configure Additional Process Hardening", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled", + "title": "1.5.1 Ensure address space layout randomization is enabled", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_kernel_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "kernel.randomize_va_space=2" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/10/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled_smt", + "name": "statement", + "prose": "Address space layout randomization (ASLR) is an exploit mitigation technique which randomly arranges the address space of key data areas of a process." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled_rationale", + "name": "rationale", + "prose": "Randomly placing virtual memory regions will make it difficult to write memory page exploits as the memory placement will be consistently shifting." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure address space layout randomization is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameter is set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `kernel.randomize_va_space` is set to `2`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_parlist=(kernel.randomize_va_space=2)\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_kernel_parameter_chk\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameter in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `kernel.randomize_va_space = 2`\n\n*Example:*\n\n```\n# printf \"%s\\n\" \"kernel.randomize_va_space = 2\" >> /etc/sysctl.d/60-kernel_sysctl.conf\n```\n\nRun the following command to set the active kernel parameter:\n\n```\n# sysctl -w kernel.randomize_va_space=2\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted", + "title": "1.5.2 Ensure ptrace_scope is restricted", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_kernel_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "kernel.yama.ptrace_scope=(1|2|3)" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted_smt", + "name": "statement", + "prose": "The `ptrace()` system call provides a means by which one process (the \"tracer\") may observe and control the execution of another process (the \"tracee\"), and examine and change the tracee's memory and registers.\n\nThe sysctl settings (writable only with CAP_SYS_PTRACE) are:\n\n- `0` - classic ptrace permissions: a process can PTRACE_ATTACH to any other process running under the same uid, as long as it is dumpable (i.e. did not transition uids, start privileged, or have called prctl(PR_SET_DUMPABLE...) already). Similarly, PTRACE_TRACEME is unchanged.\n\n- `1` - restricted ptrace: a process must have a predefined relationship with the inferior it wants to call PTRACE_ATTACH on. By default, this relationship is that of only its descendants when the above classic criteria is also met. To change the relationship, an inferior can call prctl(PR_SET_PTRACER, debugger, ...) to declare an allowed debugger PID to call PTRACE_ATTACH on the inferior. Using PTRACE_TRACEME is unchanged.\n\n- `2` - admin-only attach: only processes with CAP_SYS_PTRACE may use ptrace with PTRACE_ATTACH, or through children calling PTRACE_TRACEME.\n\n- `3` - no attach: no processes may use ptrace with PTRACE_ATTACH nor via PTRACE_TRACEME. Once set, this sysctl value cannot be changed." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted_rationale", + "name": "rationale", + "prose": "If one application is compromised, it would be possible for an attacker to attach to other running processes (e.g. Bash, Firefox, SSH sessions, GPG agent, etc) to extract additional credentials and continue to expand the scope of their attack.\n\nEnabling restricted mode will limit the ability of a compromised process to PTRACE_ATTACH on other processes running under the same user. With restricted mode, ptrace will continue to work with root user." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted_obj", + "name": "assessment-objective", + "prose": "Ensure ptrace_scope is restricted" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameter is set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `kernel.yama.ptrace_scope` is set to a value of: `1`, `2`, or `3`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_parlist=(\"kernel.yama.ptrace_scope=(1|2|3)\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_kernel_parameter_chk\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the `kernel.yama.ptrace_scope` parameter in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf` to a value of `1`, `2`, or `3`:\n\n```\nkernel.yama.ptrace_scope = 1\n - OR -\nkernel.yama.ptrace_scope = 2\n - OR -\nkernel.yama.ptrace_scope = 3\n```\n\n*Example:*\n\n```\n# printf \"%s\\n\" \"kernel.yama.ptrace_scope = 1\" >> /etc/sysctl.d/60-kernel_sysctl.conf\n```\n\nRun the following command to set the active kernel parameter:\n\n```\n# sysctl -w kernel.yama.ptrace_scope=1\n```\n\n**Note:**\n\n- If a value of `2` or `3` is preferred, or required by local site policy, replace the `1` with the desired value of `2` or `3` in the example above\n\n- If this setting appears in a canonically later file, or later in the same file, the setting will be overwritten" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted", + "title": "1.5.3 Ensure core dumps are restricted", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_kernel_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "fs.suid_dumpable=0" + ] + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted_smt", + "name": "statement", + "prose": "A core dump is the memory of an executable program. It is generally used to determine why a program aborted. It can also be used to glean confidential information from a core file. The system provides the ability to set a soft limit for core dumps, but this can be overridden by the user." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted_rationale", + "name": "rationale", + "prose": "Setting a hard limit on core dumps prevents users from overriding the soft variable. If core dumps are required, consider setting limits for user groups (see `limits.conf(5)` ). In addition, setting the `fs.suid_dumpable` variable to 0 will prevent setuid programs from dumping core." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted_obj", + "name": "assessment-objective", + "prose": "Ensure core dumps are restricted" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following command and verify output matches:\n\n```\n# grep -Ps -- '^\\h*\\*\\h+hard\\h+core\\h+0\\b' /etc/security/limits.conf /etc/security/limits.d/*\n\n* hard core 0\n```\n\nRun the following script to verify `fs.suid_dumpable = 0`:\n\nRun the following script to verify the following kernel parameter is set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `fs.suid_dumpable` is set to `0`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_parlist=(\"fs.suid_dumpable=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_kernel_parameter_chk\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```\n\nRun the following command to check if systemd-coredump is installed:\n\n```\n# systemctl list-unit-files | grep coredump\n```\n\nif anything is returned systemd-coredump is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Add the following line to `/etc/security/limits.conf` or a `/etc/security/limits.d/*` file:\n\n```\n* hard core 0\n```\n\nSet the following parameter in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `fs.suid_dumpable = 0`\n\n*Example:*\n\n```\n# printf \"\\n%s\" \"fs.suid_dumpable = 0\" >> /etc/sysctl.d/60-fs_sysctl.conf\n```\n\nRun the following command to set the active kernel parameter:\n\n```\n# sysctl -w fs.suid_dumpable=0\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten\n\n**-IF-** systemd-coredump is installed:\n\nedit `/etc/systemd/coredump.conf` and add/modify the following lines:\n\n```\nStorage=none\nProcessSizeMax=0\n```\n\nRun the command:\n\n```\nsystemctl daemon-reload\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed", + "title": "1.5.4 Ensure prelink is not installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/14" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed_smt", + "name": "statement", + "prose": "`prelink` is a program that modifies ELF shared libraries and ELF dynamically linked binaries in such a way that the time needed for the dynamic linker to perform relocations at startup significantly decreases." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed_rationale", + "name": "rationale", + "prose": "The prelinking feature can interfere with the operation of AIDE, because it changes binaries. Prelinking can also increase the vulnerability of the system if a malicious user is able to compromise a common library such as libc." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed_obj", + "name": "assessment-objective", + "prose": "Ensure prelink is not installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed_obj" + } + ], + "prose": "Verify `prelink` is not installed:\n\n```\n# dpkg-query -s prelink &>/dev/null && echo \"prelink is installed\"\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to restore binaries to normal:\n\n```\n# prelink -ua\n```\n\nUninstall `prelink` using the appropriate package manager or manual installation:\n\n```\n# apt purge prelink\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled", + "title": "1.5.5 Ensure Automatic Error Reporting is not enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled_smt", + "name": "statement", + "prose": "The Apport Error Reporting Service automatically generates crash reports for debugging" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled_rationale", + "name": "rationale", + "prose": "Apport collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure Automatic Error Reporting is not enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled_obj" + } + ], + "prose": "Run the following command to verify that the Apport Error Reporting Service is not enabled:\n\n```\n# dpkg-query -s apport &> /dev/null && grep -Psi -- '^\\h*enabled\\h*=\\h*[^0]\\b' /etc/default/apport\n```\n\nNothing should be returned\n\nRun the following command to verify that the apport service is not active:\n\n```\n# systemctl is-active apport.service | grep '^active'\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/default/apport` and add or edit the enabled parameter to equal `0`:\n\n```\nenabled=0\n```\n\nRun the following commands to stop and mask the apport service\n\n```\n# systemctl stop apport.service\n# systemctl mask apport.service\n```\n\n**- OR -**\n\nRun the following command to remove the apport package:\n\n```\n# apt purge apport\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.6_Configure_Command_Line_Warning_Banners", + "title": "Configure Command Line Warning Banners", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly", + "title": "1.6.1 Ensure message of the day is configured properly", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly_smt", + "name": "statement", + "prose": "The contents of the `/etc/motd` file are displayed to users after login and function as a message of the day for authenticated users.\n\nUnix-based systems have typically displayed information about the OS release and patch level upon logging in to the system. This information can be useful to developers who are developing software for a particular OS platform. If `mingetty(8)` supports the following options, they display operating system information: `\\m` - machine architecture `\\r` - operating system release `\\s` - operating system name `\\v` - operating system version" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly_rationale", + "name": "rationale", + "prose": "Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the \" `uname -a` \" command once they have logged in." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly_obj", + "name": "assessment-objective", + "prose": "Ensure message of the day is configured properly" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly_obj" + }, + { + "rel": "script", + "href": "#81f9478a-4a96-5c9e-89a8-b7c88600513b" + } + ], + "prose": "Run the following command and verify that the contents match site policy:\n\n```\n# cat /etc/motd\n```\n\nRun the following command and verify no results are returned:\n\n```\n# grep -E -i \"(\\\\\\v|\\\\\\r|\\\\\\m|\\\\\\s|$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed -e 's/\"//g'))\" /etc/motd\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/motd` file with the appropriate contents according to your site policy, remove any instances of `\\m` , `\\r` , `\\s` , `\\v` or references to the `OS platform`\n\n**- OR -**\n\n**- IF -** the `motd` is not used, this file can be removed.\n\nRun the following command to remove the `motd` file:\n\n```\n# rm /etc/motd\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly", + "title": "1.6.2 Ensure local login warning banner is configured properly", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly_smt", + "name": "statement", + "prose": "The contents of the `/etc/issue` file are displayed to users prior to login for local terminals.\n\nUnix-based systems have typically displayed information about the OS release and patch level upon logging in to the system. This information can be useful to developers who are developing software for a particular OS platform. If `mingetty(8)` supports the following options, they display operating system information: `\\m` - machine architecture `\\r` - operating system release `\\s` - operating system name `\\v` - operating system version - or the operating system's name" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly_rationale", + "name": "rationale", + "prose": "Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the \" `uname -a` \" command once they have logged in." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly_obj", + "name": "assessment-objective", + "prose": "Ensure local login warning banner is configured properly" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly_obj" + }, + { + "rel": "script", + "href": "#3535fabd-c67e-59e2-a8a6-24f9ad1ff515" + } + ], + "prose": "Run the following command and verify that the contents match site policy:\n\n```\n# cat /etc/issue\n```\n\nRun the following command and verify no results are returned:\n\n```\n# grep -E -i \"(\\\\\\v|\\\\\\r|\\\\\\m|\\\\\\s|$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed -e 's/\"//g'))\" /etc/issue\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/issue` file with the appropriate contents according to your site policy, remove any instances of `\\m` , `\\r` , `\\s` , `\\v` or references to the `OS platform`\n\n*Example:*\n\n```\n# echo \"Authorized users only. All activity may be monitored and reported.\" > /etc/issue\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly", + "title": "1.6.3 Ensure remote login warning banner is configured properly", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly_smt", + "name": "statement", + "prose": "The contents of the `/etc/issue.net` file are displayed to users prior to login for remote connections from configured services.\n\nUnix-based systems have typically displayed information about the OS release and patch level upon logging in to the system. This information can be useful to developers who are developing software for a particular OS platform. If `mingetty(8)` supports the following options, they display operating system information: `\\m` - machine architecture `\\r` - operating system release `\\s` - operating system name `\\v` - operating system version" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly_rationale", + "name": "rationale", + "prose": "Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the \" `uname -a` \" command once they have logged in." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly_obj", + "name": "assessment-objective", + "prose": "Ensure remote login warning banner is configured properly" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly_obj" + }, + { + "rel": "script", + "href": "#62cbc0bc-3992-5e32-9def-f6b4a58c417c" + } + ], + "prose": "Run the following command and verify that the contents match site policy:\n\n```\n# cat /etc/issue.net\n```\n\nRun the following command and verify no results are returned:\n\n```\n# grep -E -i \"(\\\\\\v|\\\\\\r|\\\\\\m|\\\\\\s|$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed -e 's/\"//g'))\" /etc/issue.net\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/issue.net` file with the appropriate contents according to your site policy, remove any instances of `\\m` , `\\r` , `\\s` , `\\v` or references to the `OS platform`\n\n*Example:*\n\n```\n# echo \"Authorized users only. All activity may be monitored and reported.\" > /etc/issue.net\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured", + "title": "1.6.4 Ensure access to /etc/motd is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured_smt", + "name": "statement", + "prose": "The contents of the `/etc/motd` file are displayed to users after login and function as a message of the day for authenticated users." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured_rationale", + "name": "rationale", + "prose": "**- IF -** the `/etc/motd` file does not have the correct access configured, it could be modified by unauthorized users with incorrect or misleading information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure access to /etc/motd is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command and verify that if `/etc/motd` exists, `Access` is `644` or more restrictive, `Uid` and `Gid` are both `0/root`:\n\n```\n# [ -e /etc/motd ] && stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: { %g/ %G)' /etc/motd\n\nAccess: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)\n -- OR --\nNothing is returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to set mode, owner, and group on `/etc/motd`:\n\n```\n# chown root:root $(readlink -e /etc/motd)\n# chmod u-x,go-wx $(readlink -e /etc/motd)\n```\n\n**- OR -**\n\nRun the following command to remove the `/etc/motd` file:\n\n```\n# rm /etc/motd\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured", + "title": "1.6.5 Ensure access to /etc/issue is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured_smt", + "name": "statement", + "prose": "The contents of the `/etc/issue` file are displayed to users prior to login for local terminals." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured_rationale", + "name": "rationale", + "prose": "**- IF -** the `/etc/issue` file does not have the correct access configured, it could be modified by unauthorized users with incorrect or misleading information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure access to /etc/issue is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command and verify `Access` is `644` or more restrictive and `Uid` and `Gid` are both `0/root`:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: { %g/ %G)' /etc/issue\n\nAccess: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: { 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to set mode, owner, and group on `/etc/issue`:\n\n```\n# chown root:root $(readlink -e /etc/issue)\n# chmod u-x,go-wx $(readlink -e /etc/issue)\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured", + "title": "1.6.6 Ensure access to /etc/issue.net is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured_smt", + "name": "statement", + "prose": "The contents of the `/etc/issue.net` file are displayed to users prior to login for remote connections from configured services." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured_rationale", + "name": "rationale", + "prose": "**- IF -** the `/etc/issue.net` file does not have the correct access configured, it could be modified by unauthorized users with incorrect or misleading information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure access to /etc/issue.net is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command and verify `Access` is `644` or more restrictive and `Uid` and `Gid` are both `0/root`:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: { %g/ %G)' /etc/issue.net\n\nAccess: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to set mode, owner, and group on `/etc/issue.net`:\n\n```\n# chown root:root $(readlink -e /etc/issue.net)\n# chmod u-x,go-wx $(readlink -e /etc/issue.net)\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_1.7_Configure_GNOME_Display_Manager", + "title": "Configure GNOME Display Manager", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.1_Ensure_GDM_is_removed", + "title": "1.7.1 Ensure GDM is removed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.1_Ensure_GDM_is_removed_smt", + "name": "statement", + "prose": "The GNOME Display Manager (GDM) is a program that manages graphical display servers and handles graphical user logins." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.1_Ensure_GDM_is_removed_rationale", + "name": "rationale", + "prose": "If a Graphical User Interface (GUI) is not required, it should be removed to reduce the attack surface of the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.1_Ensure_GDM_is_removed_obj", + "name": "assessment-objective", + "prose": "Ensure GDM is removed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.1_Ensure_GDM_is_removed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.1_Ensure_GDM_is_removed_obj" + } + ], + "prose": "Run the following command and verify `gdm3` is not installed:\n\n```\n# dpkg-query -W -f='${binary:Package}\\t${Status}\\t${db:Status-Status}\\n' gdm3\n\ngdm3 unknown ok not-installed not-installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.1_Ensure_GDM_is_removed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to uninstall `gdm3` and remove unused dependencies:\n\n```\n# apt purge gdm3\n# apt autoremove gdm3\n```\n\nImpact:\n\nRemoving the GNOME Display manager will remove the Graphical User Interface (GUI) from the system." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured", + "title": "1.7.2 Ensure GDM login banner is configured", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured_smt", + "name": "statement", + "prose": "GDM is the GNOME Display Manager which handles graphical login for GNOME based systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured_rationale", + "name": "rationale", + "prose": "Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure GDM login banner is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured_obj" + }, + { + "rel": "script", + "href": "#d08e5b09-61d3-5699-a968-17aecd7a5c7b" + } + ], + "prose": "Run the following commands to verify that the text banner on the login screen is enabled and set:\n\n```\n# gsettings get org.gnome.login-screen banner-message-enable\ntrue\n```\n\n```\n# gsettings get org.gnome.login-screen banner-message-text\n'Authorized uses only. All activity may be monitored and reported'\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** A user profile is already created run the following commands to set and enable the text banner message on the login screen:\n\n```\n# gsettings set org.gnome.login-screen banner-message-text 'Authorized uses only. All activity may be monitored and reported'\n```\n\n```\n# gsettings set org.gnome.login-screen banner-message-enable true\n```\n\n**Note:**\n\n- `banner-message-text` may be set in accordance with local site policy\n\n- `gsettings` commands in this section MUST be done from a command window on a graphical desktop or an error will be returned.\n\n- The system must be restarted after all `gsettings` configurations have been set in order for CIS-CAT Assessor to appropriately assess.\n\n**- OR/IF -** A user profile does not exist:\n\n- Create or edit the gdm profile in the `/etc/dconf/profile/gdm` with the following lines:\n\n```\nuser-db:user\nsystem-db:gdm\nfile-db:/usr/share/gdm/greeter-dconf-defaults\n```\n\n**Note:** gdm is the name of a dconf database.\n\n- Create a gdm keyfile for machine-wide settings in `/etc/dconf/db/gdm.d/01-banner-message`:\n\n```\n[org/gnome/login-screen]\nbanner-message-enable=true\nbanner-message-text='Type the banner message here.'\n```\n\n- Update the system databases\n\n```\n# dconf update\n```\n\n**Note:**\n\n- Users must log out and back in again before the system-wide settings take effect.\n\n- There is no character limit for the banner message. gnome-shell autodetects longer stretches of text and enters two column mode.\n\n- The banner message cannot be read from an external file." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled", + "title": "1.7.3 Ensure GDM disable-user-list option is enabled", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled_smt", + "name": "statement", + "prose": "GDM is the GNOME Display Manager which handles graphical login for GNOME based systems.\n\nThe `disable-user-list` option controls if a list of users is displayed on the login screen" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled_rationale", + "name": "rationale", + "prose": "Displaying the user list eliminates half of the Userid/Password equation that an unauthorized person would need to log on." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure GDM disable-user-list option is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled_obj" + }, + { + "rel": "script", + "href": "#1eaf90f5-94bd-526f-b160-5c0ba9494520" + } + ], + "prose": "Run the following command and to verify that the `disable-user-list` option is enabled:\n\n```\n# gsettings get org.gnome.login-screen disable-user-list\ntrue\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** A user profile exists run the following command to enable the `disable-user-list`:\n\n```\n# gsettings set org.gnome.login-screen disable-user-list true\n```\n\n**Note:**\n\n- `gsettings` commands in this section MUST be done from a command window on a graphical desktop or an error will be returned.\n\n- The system must be restarted after all `gsettings` configurations have been set in order for CIS-CAT Assessor to appropriately assess.\n\n**- OR/IF -** A user profile does not exist:\n\n- Create or edit the gdm profile in `/etc/dconf/profile/gdm` with the following lines:\n\n```\nuser-db:user\nsystem-db:gdm\nfile-db:/usr/share/gdm/greeter-dconf-defaults\n```\n\n**Note:** gdm is the name of a dconf database.\n\n- Create a gdm keyfile for machine-wide settings in `/etc/dconf/db/gdm.d/00-login-screen`:\n\n```\n[org/gnome/login-screen]\n# Do not show the user list\ndisable-user-list=true\n```\n\n- Update the system databases:\n\n```\n# dconf update\n```\n\n**Note:** When the user profile is created or changed, the user will need to log out and log in again before the changes will be applied." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle", + "title": "1.7.4 Ensure GDM screen locks when the user is idle", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle_smt", + "name": "statement", + "prose": "GNOME Desktop Manager can make the screen lock automatically whenever the user is idle for some amount of time." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle_rationale", + "name": "rationale", + "prose": "Setting a lock-out value reduces the window of opportunity for unauthorized user access to another user's session that has been left unattended." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle_obj", + "name": "assessment-objective", + "prose": "Ensure GDM screen locks when the user is idle" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle_obj" + }, + { + "rel": "script", + "href": "#b0b32250-cdfe-514d-8426-62bcd570ee9f" + } + ], + "prose": "Run the following commands to verify that the screen locks when the user is idle:\n\n```\n# gsettings get org.gnome.desktop.screensaver lock-delay\nuint32 5\n```\n\n```\n# gsettings get org.gnome.desktop.session idle-delay\nuint32 900\n```\n\n**Notes:**\n\n- `lock-delay=uint32 {n}` - should be 5 seconds or less and follow local site policy\n\n- `idle-delay=uint32 {n}` - Should be 900 seconds (15 minutes) or less, not `0` (disabled) and follow local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** A user profile is already created run the following commands to enable screen locks when the user is idle:\n\n```\n# gsettings set org.gnome.desktop.screensaver lock-delay 5\n```\n\n```\n# gsettings set org.gnome.desktop.session idle-delay 900\n```\n\n**Note:**\n\n- `gsettings` commands in this section MUST be done from a command window on a graphical desktop or an error will be returned.\n\n- The system must be restarted after all `gsettings` configurations have been set in order for CIS-CAT Assessor to appropriately assess.\n\n**- OR/IF-** A user profile does not exist:\n\n- Create or edit the user profile in the `/etc/dconf/profile/` and verify it includes the following:\n\n```\nuser-db:user\nsystem-db:{NAME_OF_DCONF_DATABASE}\n```\n\n**Note:** `local` is the name of a dconf database used in the examples.\n\n-\nCreate the directory `/etc/dconf/db/local.d/` if it doesn't already exist:\n\n-\nCreate the key file `/etc/dconf/db/local.d/00-screensaver` to provide information for the `local` database:\n\n*Example key file:*\n\n```\n# Specify the dconf path\n[org/gnome/desktop/session]\n\n# Number of seconds of inactivity before the screen goes blank\n# Set to 0 seconds if you want to deactivate the screensaver.\nidle-delay=uint32 180\n\n# Specify the dconf path\n[org/gnome/desktop/screensaver]\n\n# Number of seconds after the screen is blank before locking the screen\nlock-delay=uint32 0\n```\n\n**Note:** You must include the uint32 along with the integer key values as shown.\n\n- Run the following command to update the system databases:\n\n```\n# dconf update\n```\n\n- Users must log out and back in again before the system-wide settings take effect." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden", + "title": "1.7.5 Ensure GDM screen locks cannot be overridden", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden_smt", + "name": "statement", + "prose": "GNOME Desktop Manager can lock down specific settings by using the lockdown mode in dconf to prevent users from changing specific settings.\n\nTo lock down a dconf key or subpath, create a locks subdirectory in the keyfile directory. The files inside this directory contain a list of keys or subpaths to lock. Just as with the keyfiles, you may add any number of files to this directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden_rationale", + "name": "rationale", + "prose": "Setting a lock-out value reduces the window of opportunity for unauthorized user access to another user's session that has been left unattended.\n\nWithout locking down the system settings, user settings take precedence over the system settings." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden_obj", + "name": "assessment-objective", + "prose": "Ensure GDM screen locks cannot be overridden" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden_obj" + }, + { + "rel": "script", + "href": "#b8bba142-3ae6-54d4-891f-19905e3768fc" + } + ], + "prose": "Run the following script to verify that the screen lock cannot be overridden:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=()\n f_check_setting()\n {\n grep -Psrilq -- \"^\\h*$2\\b\" /etc/dconf/db/local.d/locks/* && \\\n echo \"- \\\"$3\\\" is locked\" || echo \"- \\\"$3\\\" is not locked or not set\"\n }\n declare -A settings=(\n [\"idle-delay\"]=\"/org/gnome/desktop/session/idle-delay\"\n [\"lock-delay\"]=\"/org/gnome/desktop/screensaver/lock-delay\"\n )\n for setting in \"${!settings[@]}\"; do\n result=$(f_check_setting \"$setting\" \"${settings[$setting]}\" \"$setting\")\n if [[ $result == *\"is not locked\"* || $result == *\"not set to false\"* ]]; then\n a_output2+=(\"$result\")\n else\n a_output+=(\"$result\")\n fi\n done\n printf '%s\\n' \"\" \"- Audit Result:\"\n if [ \"${#a_output2[@]}\" -gt 0 ]; then\n printf '%s\\n' \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\"\n else\n printf '%s\\n' \" ** PASS **\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "- To prevent the user from overriding these settings, create the file `/etc/dconf/db/local.d/locks/00-screensaver` with the following content:\n\n```\n# Lock desktop screensaver settings\n/org/gnome/desktop/session/idle-delay\n/org/gnome/desktop/screensaver/lock-delay\n```\n\n- Update the system databases:\n\n```\n# dconf update\n```\n\n**Note:**\n\n- A user profile must exist in order to apply locks.\n\n- Users must log out and back in again before the system-wide settings take effect." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled", + "title": "1.7.6 Ensure GDM automatic mounting of removable media is disabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/10/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled_smt", + "name": "statement", + "prose": "By default GNOME automatically mounts removable media when inserted as a convenience to the user." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled_rationale", + "name": "rationale", + "prose": "With automounting enabled anyone with physical access could attach a USB drive or disc and have its contents available in system even if they lacked permissions to mount it themselves." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure GDM automatic mounting of removable media is disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled_obj" + }, + { + "rel": "script", + "href": "#e0939ee2-6da4-5eb2-9964-47e83340beff" + } + ], + "prose": "Run the following commands to verify automatic mounting is disabled:\n\n```\n# gsettings get org.gnome.desktop.media-handling automount\nfalse\n```\n\n```\n# gsettings get org.gnome.desktop.media-handling automount-open\nfalse\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** A user profile exists run the following commands to ensure automatic mounting is disabled:\n\n```\n# gsettings set org.gnome.desktop.media-handling automount false\n# gsettings set org.gnome.desktop.media-handling automount-open false\n```\n\n**Note:**\n\n- `gsettings` commands in this section MUST be done from a command window on a graphical desktop or an error will be returned.\n\n- The system must be restarted after all `gsettings` configurations have been set in order for CIS-CAT Assessor to appropriately assess.\n\n**- OR/IF -** A user profile does not exist:\n\n- Create a file `/etc/dconf/db/local.d/00-media-automount` with following content:\n\n```\n[org/gnome/desktop/media-handling]\nautomount=false\nautomount-open=false\n```\n\n- After creating the file, apply the changes using below command :\n\n```\n# dconf update\n```\n\n**Note:** Users must log out and back in again before the system-wide settings take effect.\n\nImpact:\n\nThe use of portable hard drives is very common for workstation users. If your organization allows the use of portable storage or media on workstations and physical access controls to workstations is considered adequate there is little value add in turning off automounting." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden", + "title": "1.7.7 Ensure GDM disabling automatic mounting of removable media is not overridden", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden_smt", + "name": "statement", + "prose": "By default GNOME automatically mounts removable media when inserted as a convenience to the user.\n\nBy using the lockdown mode in dconf, you can prevent users from changing specific settings. To lock down a dconf key or subpath, create a locks subdirectory in the keyfile directory. The files inside this directory contain a list of keys or subpaths to lock. Just as with the keyfiles, you may add any number of files to this directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden_rationale", + "name": "rationale", + "prose": "With automounting enabled anyone with physical access could attach a USB drive or disc and have its contents available in system even if they lacked permissions to mount it themselves." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden_obj", + "name": "assessment-objective", + "prose": "Ensure GDM disabling automatic mounting of removable media is not overridden" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden_obj" + }, + { + "rel": "script", + "href": "#1175b087-5c60-5b14-8344-6f57ee739247" + } + ], + "prose": "Run the following script to verify automatic mounting of removable media is not overridden and correctly configured in a configuration file:\n\n- `automount=false`\n\n- `automount-open=false`\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=()\n check_setting()\n {\n grep -Psrilq \"^\\h*$1\\h*=\\h*false\\b\" /etc/dconf/db/local.d/locks/* 2> /dev/null && \\\n echo \"- \\\"$3\\\" is locked and set to false\" || echo \"- \\\"$3\\\" is not locked or not set to false\"\n }\n declare -A settings=(\n [\"automount\"]=\"org/gnome/desktop/media-handling\"\n [\"automount-open\"]=\"org/gnome/desktop/media-handling\"\n )\n for setting in \"${!settings[@]}\"; do\n result=$(check_setting \"$setting\" \"${settings[$setting]}\" \"$setting\")\n if [[ $result == *\"is not locked\"* || $result == *\"not set to false\"* ]]; then\n a_output2+=(\"$result\")\n else\n a_output+=(\"$result\")\n fi\n done\n printf '%s\\n' \"\" \"- Audit Result:\"\n if [ \"${#a_output2[@]}\" -gt 0 ]; then\n printf '%s\\n' \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\"\n else\n printf '%s\\n' \" ** PASS **\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "- To prevent the user from overriding these settings, create the file `/etc/dconf/db/local.d/locks/00-media-automount` with the following content:\n\n```\n[org/gnome/desktop/media-handling]\nautomount=false\nautomount-open=false\n```\n\n- Update the systems databases:\n\n```\n# dconf update\n```\n\n**Note:**\n\n- A user profile must exist in order to apply locks.\n\n- Users must log out and back in again before the system-wide settings take effect.\n\nImpact:\n\nThe use of portable hard drives is very common for workstation users" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled", + "title": "1.7.8 Ensure GDM autorun-never is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/10/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled_smt", + "name": "statement", + "prose": "The `autorun-never` setting allows the GNOME Desktop Display Manager to disable autorun through GDM." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled_rationale", + "name": "rationale", + "prose": "Malware on removable media may taking advantage of Autorun features when the media is inserted into a system and execute." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure GDM autorun-never is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled_obj" + }, + { + "rel": "script", + "href": "#ae5daade-80d9-5815-ad3d-1392a03d779d" + } + ], + "prose": "Run the following command to verify that `autorun-never` is set to `true` for GDM:\n\n```\n# gsettings get org.gnome.desktop.media-handling autorun-never\ntrue\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** A user profile exists run the following command to set `autorun-never` to `true` for GDM users:\n\n```\n# gsettings set org.gnome.desktop.media-handling autorun-never true\n```\n\n**Note:**\n\n- `gsettings` commands in this section MUST be done from a command window on a graphical desktop or an error will be returned.\n\n- The system must be restarted after all `gsettings` configurations have been set in order for CIS-CAT Assessor to appropriately assess.\n\n**- OR/IF -** A user profile does not exist:\n\n- create the file `/etc/dconf/db/local.d/locks/00-media-autorun` with the following content:\n\n```\n[org/gnome/desktop/media-handling]\nautorun-never=true\n```\n\n- Update the systems databases:\n\n```\n# dconf update\n```\n\n**Note:** Users must log out and back in again before the system-wide settings take effect." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden", + "title": "1.7.9 Ensure GDM autorun-never is not overridden", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/10/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden_smt", + "name": "statement", + "prose": "The autorun-never setting allows the GNOME Desktop Display Manager to disable autorun through GDM.\n\nBy using the lockdown mode in dconf, you can prevent users from changing specific settings.\n\nTo lock down a dconf key or subpath, create a locks subdirectory in the keyfile directory. The files inside this directory contain a list of keys or subpaths to lock. Just as with the keyfiles, you may add any number of files to this directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden_rationale", + "name": "rationale", + "prose": "Malware on removable media may taking advantage of Autorun features when the media is inserted into a system and execute." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden_obj", + "name": "assessment-objective", + "prose": "Ensure GDM autorun-never is not overridden" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden_obj" + }, + { + "rel": "script", + "href": "#10bf0fcd-7392-5205-a09f-65e2d016d1d0" + } + ], + "prose": "Run the following script to verify that `autorun-never=true` cannot be overridden:\n\n```bash\n#!/usr/bin/env bash\n\n{\n # Function to check and report if a specific setting is locked and set to true\n check_setting() {\n grep -Psrilq \"^\\h*$1\\h*=\\h*true\\b\" /etc/dconf/db/local.d/locks/* 2> /dev/null && echo \"- \\\"$3\\\" is locked and set to false\" || echo \"- \\\"$3\\\" is not locked or not set to false\"\n }\n # Array of settings to check\n declare -A settings=([\"autorun-never\"]=\"org/gnome/desktop/media-handling\")\n # Check GNOME Desktop Manager configurations\n l_output=() l_output2=()\n for setting in \"${!settings[@]}\"; do\n result=$(check_setting \"$setting\")\n l_output+=(\"$result\")\n if [[ $result == *\"is not locked\"* || $result == *\"not set to true\"* ]]; then\n l_output2+=(\"$result\")\n fi\n done\n # Report results\n if [ ${#l_output2[@]} -ne 0 ]; then\n printf '%s\\n' \"- Audit Result:\" \" ** FAIL **\"\n printf '%s\\n' \"- Reason(s) for audit failure:\"\n for msg in \"${l_output2[@]}\"; do\n printf '%s\\n' \"$msg\"\n done\n else\n printf '%s\\n' \"- Audit Result:\" \" ** PASS **\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "- To prevent the user from overriding these settings, create the file `/etc/dconf/db/local.d/locks/00-media-autorun` with the following content:\n\n```\n[org/gnome/desktop/media-handling]\nautorun-never=true\n```\n\n- Update the systems databases:\n\n```\n# dconf update\n```\n\n**Note:**\n\n- A user profile must exist in order to apply locks.\n\n- Users must log out and back in again before the system-wide settings take effect." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled", + "title": "1.7.10 Ensure XDMCP is not enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled_smt", + "name": "statement", + "prose": "X Display Manager Control Protocol (XDMCP) is designed to provide authenticated access to display management services for remote displays" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled_rationale", + "name": "rationale", + "prose": "XDMCP is inherently insecure.\n\n- XDMCP is not a ciphered protocol. This may allow an attacker to capture keystrokes entered by a user\n\n- XDMCP is vulnerable to man-in-the-middle attacks. This may allow an attacker to steal the credentials of legitimate users by impersonating the XDMCP server." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure XDMCP is not enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled_obj" + }, + { + "rel": "script", + "href": "#d83d68a0-3dc5-57a7-a576-b8e59aa271ab" + } + ], + "prose": "Run the following script and verify the output:\n\n```bash\n#!/usr/bin/env bash\n\n{\n while IFS= read -r l_file; do\n awk '/\\[xdmcp\\]/{ f = 1;next } /\\[/{ f = 0 } f {if (/^\\s*Enable\\s*=\\s*true/) print \"The file: \\\"'\"$l_file\"'\\\" includes: \\\"\" $0 \"\\\" in the \\\"[xdmcp]\\\" block\"}' \"$l_file\"\n done < <(grep -Psil -- '^\\h*\\[xdmcp\\]' /etc/{gdm3,gdm}/{custom,daemon}.conf)\n}\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit all files returned by the audit and remove or commend out the `Enable=true` line in the `[xdmcp]` block:\n\n*Example file:*\n\n```\n# GDM configuration storage\n#\n# See /usr/share/gdm/gdm.schemas for a list of available options.\n\n[daemon]\n# Uncomment the line below to force the login screen to use Xorg\n#WaylandEnable=false\n\n# Enabling automatic login\n# AutomaticLoginEnable = true\n# AutomaticLogin = user1\n\n# Enabling timed login\n# TimedLoginEnable = true\n# TimedLogin = user1\n# TimedLoginDelay = 10\n\n[security]\n\n[xdmcp]\n# Enable=true <- **This line should be removed or commented out**\n\n[chooser]\n\n[debug]\n# Uncomment the line below to turn on debugging\n# More verbose logs\n# Additionally lets the X server dump core if it crashes\n#Enable=true\n```" + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_2_Services", + "title": "Services", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_2.1_Configure_Server_Services", + "title": "Configure Server Services", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use", + "title": "2.1.1 Ensure autofs services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/10/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use_smt", + "name": "statement", + "prose": "`autofs` allows automatic mounting of devices, typically including CD/DVDs and USB drives." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "With automounting enabled anyone with physical access could attach a USB drive or disc and have its contents available in the filesystem even if they lacked permissions to mount it themselves." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure autofs services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use_obj" + } + ], + "prose": "As a preference `autofs` should not be installed unless other packages depend on it.\n\nRun the following command to verify `autofs` is not installed:\n\n```\n# dpkg-query -s autofs &>/dev/null && echo \"autofs is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `autofs.service` is not enabled:\n\n```\n# systemctl is-enabled autofs.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify the `autofs.service` is not active:\n\n```\n# systemctl is-active autofs.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `autofs.service` and remove the `autofs` package:\n\n```\n# systemctl stop autofs.service\n# apt purge autofs\n```\n\n**- OR -**\n\n**- IF -** the `autofs` package is required as a dependency:\n\nRun the following commands to stop and mask `autofs.service`:\n\n```\n# systemctl stop autofs.service\n# systemctl mask autofs.service\n```\n\nImpact:\n\nThe use of portable hard drives is very common for workstation users. If your organization allows the use of portable storage or media on workstations and physical access controls to workstations is considered adequate there is little value add in turning off automounting.\n\nThere may be packages that are dependent on the `autofs` package. If the `autofs` package is removed, these dependent packages will be removed as well. Before removing the `autofs` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `autofs.service` leaving the `autofs` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use", + "title": "2.1.2 Ensure avahi daemon services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use_smt", + "name": "statement", + "prose": "Avahi is a free zeroconf implementation, including a system for multicast DNS/DNS-SD service discovery. Avahi allows programs to publish and discover services and hosts running on a local network with no specific configuration. For example, a user can plug a computer into a network and Avahi automatically finds printers to print to, files to look at and people to talk to, as well as network services running on the machine." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "Automatic discovery of network services is not normally required for system functionality. It is recommended to remove this package to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure avahi daemon services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `avahi-daemon` is not installed:\n\n```\n# dpkg-query -s avahi-daemon &>/dev/null && echo \"avahi-daemon is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the `avahi` package is required as a dependency:\n\nRun the following command to verify `avahi-daemon.socket` and `avahi-daemon.service` are not enabled:\n\n```\n# systemctl is-enabled avahi-daemon.socket avahi-daemon.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify `avahi-daemon.socket` and `avahi-daemon.service` are not active:\n\n```\n# systemctl is-active avahi-daemon.socket avahi-daemon.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `avahi-daemon.socket` and `avahi-daemon.service`, and remove the `avahi-daemon` package:\n\n```\n# systemctl stop avahi-daemon.socket avahi-daemon.service\n# apt purge avahi-daemon\n```\n\n**- OR -**\n\n**- IF -** the `avahi-daemon` package is required as a dependency:\n\nRun the following commands to stop and mask the `avahi-daemon.socket` and `avahi-daemon.service`:\n\n```\n# systemctl stop avahi-daemon.socket avahi-daemon.service\n# systemctl mask avahi-daemon.socket avahi-daemon.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `avahi` package. If the `avahi` package is removed, these dependent packages will be removed as well. Before removing the `avahi` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `avahi-daemon.socket` and `avahi-daemon.service` leaving the `avahi` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use", + "title": "2.1.3 Ensure dhcp server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "The Dynamic Host Configuration Protocol (DHCP) is a service that allows machines to be dynamically assigned IP addresses. There are two versions of the DHCP protocol `DHCPv4` and `DHCPv6`. At startup the server may be started for one or the other via the `-4` or `-6` arguments." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "Unless a system is specifically set up to act as a DHCP server, it is recommended that this package be removed to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure dhcp server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following commands to verify `isc-dhcp-server` is not installed:\n\n```\n# dpkg-query -s isc-dhcp-server &>/dev/null && echo \"isc-dhcp-server is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `isc-dhcp-server.service` and `isc-dhcp-server6.service` are not enabled:\n\n```\n# systemctl is-enabled isc-dhcp-server.service isc-dhcp-server6.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify `isc-dhcp-server.service` and `isc-dhcp-server6.service` are not active:\n\n```\n# systemctl is-active isc-dhcp-server.service isc-dhcp-server6.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `isc-dhcp-server.service` and `isc-dhcp-server6.service` and remove the `isc-dhcp-server` package:\n\n```\n# systemctl stop isc-dhcp-server.service isc-dhcp-server6.service\n# apt purge isc-dhcp-server\n```\n\n**- OR -**\n\n**- IF -** the `isc-dhcp-server` package is required as a dependency:\n\nRun the following commands to stop and mask `isc-dhcp-server.service` and `isc-dhcp-server6.service`:\n\n```\n# systemctl stop isc-dhcp-server.service isc-dhcp-server6.service\n# systemctl mask isc-dhcp-server isc-dhcp-server6.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `isc-dhcp-server` package. If the `isc-dhcp-server` package is removed, these dependent packages will be removed as well. Before removing the `isc-dhcp-server` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `isc-dhcp-server.service` and `isc-dhcp-server6.service` leaving the `isc-dhcp-server` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use", + "title": "2.1.4 Ensure dns server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "The Domain Name System (DNS) is a hierarchical naming system that maps names to IP addresses for computers, services and other resources connected to a network.\n\n**Note:** `bind9` is the package and `bind.service` is the alias for `named.service`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "Unless a system is specifically designated to act as a DNS server, it is recommended that the package be deleted to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure dns server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `bind9` is not installed:\n\n```\n# dpkg-query -s bind9 &>/dev/null && echo \"bind9 is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `named.service` is not enabled:\n\n```\n# systemctl is-enabled named.service 2>/dev/null | grep 'enabled'\n\nNothing should be returned\n```\n\nRun the following command to verify the `named.service` is not active:\n\n```\n# systemctl is-active named.service 2>/dev/null | grep '^active'\n\nNothing should be returned\n```\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `named.service` and remove the `bind9` package:\n\n```\n# systemctl stop named.service\n# apt purge bind9\n```\n\n**- OR -**\n\n**- IF -** the `bind9` package is required as a dependency:\n\nRun the following commands to stop and mask `bind9.service`:\n\n```\n# systemctl stop named.service\n# systemctl mask named.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `bind9` package. If the `bind9` package is removed, these dependent packages will be removed as well. Before removing the `bind9` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask `named.service` leaving the `bind9` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use", + "title": "2.1.5 Ensure dnsmasq services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use_smt", + "name": "statement", + "prose": "`dnsmasq` is a lightweight tool that provides DNS caching, DNS forwarding and DHCP (Dynamic Host Configuration Protocol) services." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "Unless a system is specifically designated to act as a DNS caching, DNS forwarding and/or DHCP server, it is recommended that the package be removed to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure dnsmasq services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use_obj" + } + ], + "prose": "Run one of the following commands to verify `dnsmasq` is not installed:\n\n```\n# dpkg-query -s dnsmasq &>/dev/null && echo \"dnsmasq is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `dnsmasq.service` is not enabled:\n\n```\n# systemctl is-enabled dnsmasq.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify the `dnsmasq.service` is not active:\n\n```\n# systemctl is-active dnsmasq.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `dnsmasq.service` and remove `dnsmasq` package:\n\n```\n# systemctl stop dnsmasq.service\n# apt purge dnsmasq\n```\n\n**- OR -**\n\n**- IF -** the `dnsmasq` package is required as a dependency:\n\nRun the following commands to stop and mask the `dnsmasq.service`:\n\n```\n# systemctl stop dnsmasq.service\n# systemctl mask dnsmasq.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `dnsmasq` package. If the `dnsmasq` package is removed, these dependent packages will be removed as well. Before removing the `dnsmasq` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `dnsmasq.service` leaving the `dnsmasq` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use", + "title": "2.1.6 Ensure ftp server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "The File Transfer Protocol (FTP) provides networked computers with the ability to transfer files. `vsftpd` is the Very Secure File Transfer Protocol Daemon." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "FTP does not protect the confidentiality of data or authentication credentials. It is recommended SFTP be used if file transfer is required. Unless there is a need to run the system as a FTP server (for example, to allow anonymous downloads), it is recommended that the package be deleted to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure ftp server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `vsftpd` is not installed:\n\n```\n# dpkg-query -s vsftpd &>/dev/null && echo \"vsftpd is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `vsftpd` service is not enabled:\n\n```\n# systemctl is-enabled vsftpd.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify the `vsftpd` service is not active:\n\n```\n# systemctl is-active vsftpd.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:**\n\n- Other ftp server packages may exist. They should also be audited, if not required and authorized by local site policy\n\n- If the package is required for a dependency:\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `vsftpd.service` and remove the `vsftpd` package:\n\n```\n# systemctl stop vsftpd.service\n# apt purge vsftpd\n```\n\n**- OR -**\n\n**- IF -** the `vsftpd` package is required as a dependency:\n\nRun the following commands to stop and mask the `vsftpd.service`:\n\n```\n# systemctl stop vsftpd.service\n# systemctl mask vsftpd.service\n```\n\n**Note:** Other ftp server packages may exist. If not required and authorized by local site policy, they should also be removed. If the package is required for a dependency, the service should be stopped and masked.\n\nImpact:\n\nThere may be packages that are dependent on the `vsftpd` package. If the `vsftpd` package is removed, these dependent packages will be removed as well. Before removing the `vsftpd` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `vsftpd.service` leaving the `vsftpd` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use", + "title": "2.1.7 Ensure ldap server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "The Lightweight Directory Access Protocol (LDAP) was introduced as a replacement for NIS/YP. It is a service that provides a method for looking up information from a central database." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "If the system will not need to act as an LDAP server, it is recommended that the software be removed to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure ldap server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `slapd` is not installed:\n\n```\n# dpkg-query -s slapd &>/dev/null && echo \"slapd is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `slapd.service` is not enabled:\n\n```\n# systemctl is-enabled slapd.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify `slapd.service` is not active:\n\n```\n# systemctl is-active slapd.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `slapd.service` and remove the `slapd` package:\n\n```\n# systemctl stop slapd.service\n# apt purge slapd\n```\n\n**- OR -**\n\n**- IF -** the `slapd` package is required as a dependency:\n\nRun the following commands to stop and mask `slapd.service`:\n\n```\n# systemctl stop slapd.service\n# systemctl mask slapd.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `slapd` package. If the `slapd` package is removed, these dependent packages will be removed as well. Before removing the `slapd` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `slapd.service` leaving the `slapd` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use", + "title": "2.1.8 Ensure message access server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "`dovecot-imapd` and `dovecot-pop3d` are an open source IMAP and POP3 server for Linux based systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "Unless POP3 and/or IMAP servers are to be provided by this system, it is recommended that the package be removed to reduce the potential attack surface.\n\n**Note:** Several IMAP/POP3 servers exist and can use other service names. These should also be audited and the packages removed if not required." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure message access server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `dovecot-imapd` and `dovecot-pop3d` are not installed:\n\n```\n# dpkg-query -s dovecot-imapd &>/dev/null && echo \"dovecot-imapd is installed\"\n```\n\nNothing should be returned.\n\n```\n# dpkg-query -s dovecot-pop3d &>/dev/null && echo \"dovecot-pop3d is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** a package is installed **and** is required for dependencies:\n\nRun the following commands to verify `dovecot.socket` and `dovecot.service` are not enabled:\n\n```\n# systemctl is-enabled dovecot.socket dovecot.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify `dovecot.socket` and `dovecot.service` are not active:\n\n```\n# systemctl is-active dovecot.socket dovecot.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run one of the following commands to remove `dovecot-imapd` and `dovecot-pop3d`:\n\nRun the following commands to stop `dovecot.socket` and `dovecot.service`, and remove the `dovecot-imapd` and `dovecot-pop3d` packages:\n\n```\n# systemctl stop dovecot.socket dovecot.service\n# apt purge dovecot-imapd dovecot-pop3d\n```\n\n**- OR -**\n\n**- IF -** a package is installed **and** is required for dependencies:\n\nRun the following commands to stop and mask `dovecot.socket` and `dovecot.service`:\n\n```\n# systemctl stop dovecot.socket dovecot.service\n# systemctl mask dovecot.socket dovecot.service\n```\n\nImpact:\n\nThere may be packages that are dependent on `dovecot-imapd` and/or `dovecot-pop3d` packages. If `dovecot-imapd` and `dovecot-pop3d` packages are removed, these dependent packages will be removed as well. Before removing `dovecot-imapd` and/or `dovecot-pop3d` packages, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask `dovecot.socket` and `dovecot.service` leaving `dovecot-imapd` and/or `dovecot-pop3d` packages installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use", + "title": "2.1.9 Ensure network file system services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use_smt", + "name": "statement", + "prose": "The Network File System (NFS) is one of the first and most widely distributed file systems in the UNIX environment. It provides the ability for systems to mount file systems of other servers through the network." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "If the system does not export NFS shares, it is recommended that the `nfs-kernel-server` package be removed to reduce the remote attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure network file system services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `nfs-kernel-server` is not installed:\n\n```\n# dpkg-query -s nfs-kernel-server &>/dev/null && echo \"nfs-kernel-server is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** package is required for dependencies:\n\nRun the following command to verify that the `nfs-server.service` is not enabled:\n\n```\n# systemctl is-enabled nfs-server.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify the `nfs-server.service` is not active:\n\n```\n# systemctl is-active nfs-server.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to stop `nfs-server.service` and remove `nfs-kernel-server` package:\n\n```\n# systemctl stop nfs-server.service\n# apt purge nfs-kernel-server\n```\n\n**- OR -**\n\n**- IF -** the `nfs-kernel-server` package is required as a dependency:\n\nRun the following commands to stop and mask the `nfs-server.service`:\n\n```\n# systemctl stop nfs-server.service\n# systemctl mask nfs-server.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `nfs-kernel-server` package. If the `nfs-kernel-server` package is removed, these dependent packages will be removed as well. Before removing the `nfs-kernel-server` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `nfs-server.service` leaving the `nfs-kernel-server` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use", + "title": "2.1.10 Ensure nis server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "The Network Information Service (NIS) (formally known as Yellow Pages) is a client-server directory service protocol for distributing system configuration files. The NIS server is a collection of programs that allow for the distribution of configuration files. The NIS client (`ypbind`) was used to bind a machine to an NIS server and receive the distributed configuration files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "`ypserv.service` is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally has been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that `ypserv.service` be removed and other, more secure services be used" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure nis server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `ypserv` is not installed:\n\n```\n# dpkg-query -s ypserv &>/dev/null && echo \"ypserv is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `ypserv.service` is not enabled:\n\n```\n# systemctl is-enabled ypserv.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify `ypserv.service` is not active:\n\n```\n# systemctl is-active ypserv.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `ypserv.service` and remove `ypserv` package:\n\n```\n# systemctl stop ypserv.service\n# apt purge ypserv\n```\n\n**- OR -**\n\n**- IF -** the `ypserv` package is required as a dependency:\n\nRun the following commands to stop and mask `ypserv.service`:\n\n```\n# systemctl stop ypserv.service\n# systemctl mask ypserv.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `ypserv` package. If the `ypserv` package is removed, these dependent packages will be removed as well. Before removing the `ypserv` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `ypserv.service` leaving the `ypserv` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use", + "title": "2.1.11 Ensure print server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "The Common Unix Print System (CUPS) provides the ability to print to both local and network printers. A system running CUPS can also accept print jobs from remote systems and print them to local printers. It also provides a web based remote administration capability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "If the system does not need to print jobs or accept print jobs from other systems, it is recommended that CUPS be removed to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure print server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `cups` is not Installed:\n\n```\n# dpkg-query -s cups &>/dev/null && echo \"cups is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the `cups` package is required as a dependency:\n\nRun the following command to verify the `cups.socket` and `cups.service` are not enabled:\n\n```\n# systemctl is-enabled cups.socket cups.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify the `cups.socket` and `cups.service` are not active:\n\n```\n# systemctl is-active cups.socket cups.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `cups.socket` and `cups.service`, and remove the `cups` package:\n\n```\n# systemctl stop cups.socket cups.service\n# apt purge cups\n```\n\n**- OR -**\n\n**- IF -** the `cups` package is required as a dependency:\n\nRun the following commands to stop and mask the `cups.socket` and `cups.service`:\n\n```\n# systemctl stop cups.socket cups.service\n# systemctl mask cups.socket cups.service\n```\n\nImpact:\n\nRemoving the cups package, or disabling `cups.socket` and/or `cups.service` will prevent printing from the system, a common task for workstation systems.\n\nThere may be packages that are dependent on the `cups` package. If the `cups` package is removed, these dependent packages will be removed as well. Before removing the `cups` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask `cups.socket` and `cups.service` leaving the `cups` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use", + "title": "2.1.12 Ensure rpcbind services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use_smt", + "name": "statement", + "prose": "The `rpcbind` utility maps RPC services to the ports on which they listen. RPC processes notify `rpcbind` when they start, registering the ports they are listening on and the RPC program numbers they expect to serve. The client system then contacts `rpcbind` on the server with a particular RPC program number. The `rpcbind.service` redirects the client to the proper port number so it can communicate with the requested service.\n\nPortmapper is an RPC service, which always listens on tcp and udp 111, and is used to map other RPC services (such as nfs, nlockmgr, quotad, mountd, etc.) to their corresponding port number on the server. When a remote host makes an RPC call to that server, it first consults with portmap to determine where the RPC server is listening." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "A small request (~82 bytes via UDP) sent to the Portmapper generates a large response (7x to 28x amplification), which makes it a suitable tool for DDoS attacks. If `rpcbind` is not required, it is recommended to remove `rpcbind` package to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure rpcbind services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `rpcbind` package is not installed:\n\n```\n# dpkg-query -s rpcbind &>/dev/null && echo \"rpcbind is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the `rpcbind` package is required as a dependency:\n\nRun the following command to verify `rpcbind.socket` and `rpcbind.service` are not enabled:\n\n```\n# systemctl is-enabled rpcbind.socket rpcbind.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify `rpcbind.socket` and `rpcbind.service` are not active:\n\n```\n# systemctl is-active rpcbind.socket rpcbind.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `rpcbind.socket` and `rpcbind.service`, and remove the `rpcbind` package:\n\n```\n# systemctl stop rpcbind.socket rpcbind.service\n# apt purge rpcbind\n```\n\n**- OR -**\n\n**- IF -** the `rpcbind` package is required as a dependency:\n\nRun the following commands to stop and mask the `rpcbind.socket` and `rpcbind.service`:\n\n```\n# systemctl stop rpcbind.socket rpcbind.service\n# systemctl mask rpcbind.socket rpcbind.service\n```\n\nImpact:\n\nMany of the libvirt packages used by Enterprise Linux virtualization, and the `nfs-utils` package used for The Network File System (NFS), are dependent on the `rpcbind` package. If the `rpcbind` package is removed, these dependent packages will be removed as well. Before removing the `rpcbind` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `rpcbind.socket` and `rpcbind.service` leaving the `rpcbind` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use", + "title": "2.1.13 Ensure rsync services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use_smt", + "name": "statement", + "prose": "The `rsync` service can be used to synchronize files between systems over network links." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "`rsync.service` presents a security risk as the `rsync` protocol is unencrypted.\n\nThe `rsync` package should be removed to reduce the attack area of the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure rsync services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `rsync` is not installed:\n\n```\n# dpkg-query -s rsync &>/dev/null && echo \"rsync is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the `rsync` package is required as a dependency:\n\nRun the following command to verify `rsync.service` is not enabled:\n\n```\n# systemctl is-enabled rsync.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify `rsync.service` is not active:\n\n```\n# systemctl is-active rsync.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `rsync.service`, and remove the `rsync` package:\n\n```\n# systemctl stop rsync.service\n# apt purge rsync\n```\n\n**- OR -**\n\n**- IF -** the `rsync` package is required as a dependency:\n\nRun the following commands to stop and mask `rsync.service`:\n\n```\n# systemctl stop rsync.service\n# systemctl mask rsync.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `rsync` package. If the `rsync` package is removed, these dependent packages will be removed as well. Before removing the `rsync` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask `rsync.service` leaving the `rsync` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use", + "title": "2.1.14 Ensure samba file server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "The Samba daemon allows system administrators to configure their Linux systems to share file systems and directories with Windows desktops. Samba will advertise the file systems and directories via the Server Message Block (SMB) protocol. Windows desktop users will be able to mount these directories and file systems as letter drives on their systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "If there is no need to mount directories and file systems to Windows systems, then this service should be deleted to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure samba file server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `samba` is not installed:\n\n```\n# dpkg-query -s samba &>/dev/null && echo \"samba is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `smbd.service` is not enabled:\n\n```\n# systemctl is-enabled smbd.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify the `smbd.service` is not active:\n\n```\n# systemctl is-active smbd.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `smbd.service` and remove `samba` package:\n\n```\n# systemctl stop smbd.service\n# apt purge samba\n```\n\n**- OR -**\n\n**- IF -** the `samba` package is required as a dependency:\n\nRun the following commands to stop and mask the `smbd.service`:\n\n```\n# systemctl stop smbd.service\n# systemctl mask smbd.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `samba` package. If the `samba` package is removed, these dependent packages will be removed as well. Before removing the `samba` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `smbd.service` leaving the `samba` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use", + "title": "2.1.15 Ensure snmp services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use_smt", + "name": "statement", + "prose": "Simple Network Management Protocol (SNMP) is a widely used protocol for monitoring the health and welfare of network equipment, computer equipment and devices like UPSs.\n\nNet-SNMP is a suite of applications used to implement SNMPv1 (RFC 1157), SNMPv2 (RFCs 1901-1908), and SNMPv3 (RFCs 3411-3418) using both IPv4 and IPv6.\n\nSupport for SNMPv2 classic (a.k.a. \"SNMPv2 historic\" - RFCs 1441-1452) was dropped with the 4.0 release of the UCD-snmp package.\n\nThe Simple Network Management Protocol (SNMP) server is used to listen for SNMP commands from an SNMP management system, execute the commands or collect the information and then send results back to the requesting system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "The SNMP server can communicate using `SNMPv1`, which transmits data in the clear and does not require authentication to execute commands. `SNMPv3` replaces the simple/clear text password sharing used in `SNMPv2` with more securely encoded parameters. If the the SNMP service is not required, the `snmpd` package should be removed to reduce the attack surface of the system.\n\n**Note:** If SNMP is required:\n\n- The server should be configured for `SNMP v3` only. `User Authentication` and `Message Encryption` should be configured.\n\n- If `SNMP v2` is **absolutely** necessary, modify the community strings' values." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure snmp services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `snmpd` is not installed:\n\n```\n# dpkg-query -s snmpd &>/dev/null && echo \"snmpd is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify the `snmpd.service` is not enabled:\n\n```\n# systemctl is-enabled snmpd.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify the `snmpd.service` is not active:\n\n```\n# systemctl is-active snmpd.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `snmpd.service` and remove the `snmpd` package:\n\n```\n# systemctl stop snmpd.service\n# apt purge snmpd\n```\n\n**- OR -** If the package is required for dependencies:\n\nRun the following commands to stop and mask the `snmpd.service`:\n\n```\n# systemctl stop snmpd.service\n# systemctl mask snmpd.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `snmpd` package. If the `snmpd` package is removed, these packages will be removed as well.\n\nBefore removing the `snmpd` package, review any dependent packages to determine if they are required on the system. If a dependent package is required, stop and mask the `snmpd.service` leaving the `snmpd` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use", + "title": "2.1.16 Ensure tftp server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "Trivial File Transfer Protocol (TFTP) is a simple protocol for exchanging files between two TCP/IP machines. TFTP servers allow connections from a TFTP Client for sending and receiving files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "Unless there is a need to run the system as a TFTP server, it is recommended that the package be removed to reduce the potential attack surface.\n\nTFTP does not have built-in encryption, access control or authentication. This makes it very easy for an attacker to exploit TFTP to gain access to files" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure tftp server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `tftpd-hpa` is not installed:\n\n```\n# dpkg-query -s tftpd-hpa &>/dev/null && echo \"tftpd-hpa is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `tftpd-hpa.service` is not enabled:\n\n```\n# systemctl is-enabled tftpd-hpa.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify the `tftpd-hpa.service` is not active:\n\n```\n# systemctl is-active tftpd-hpa.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `tftpd-hpa.service`, and remove the `tftpd-hpa` package:\n\n```\n# systemctl stop tftpd-hpa.service\n# apt purge tftpd-hpa\n```\n\n**- OR -**\n\n**- IF -** the `tftpd-hpa` package is required as a dependency:\n\nRun the following commands to stop and mask `tftpd-hpa.service`:\n\n```\n# systemctl stop tftpd-hpa.service\n# systemctl mask tftpd-hpa.service\n```\n\nImpact:\n\nTFTP is often used to provide files for network booting such as for PXE based installation of servers.\n\nThere may be packages that are dependent on the `tftpd-hpa` package. If the `tftpd-hpa` package is removed, these dependent packages will be removed as well. Before removing the `tftpd-hpa` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask `tftpd-hpa.service` leaving the `tftpd-hpa` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use", + "title": "2.1.17 Ensure web proxy server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "Squid is a standard proxy server used in many distributions and environments." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "Unless a system is specifically set up to act as a proxy server, it is recommended that the squid package be removed to reduce the potential attack surface.\n\n**Note:** Several HTTP proxy servers exist. These should be checked and removed unless required." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure web proxy server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `squid` is not installed:\n\n```\n# dpkg-query -s squid &>/dev/null && echo \"squid is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the package is required for dependencies:\n\nRun the following command to verify `squid.service` is not enabled:\n\n```\n# systemctl is-enabled squid.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify the `squid.service` is not active:\n\n```\n# systemctl is-active squid.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `squid.service` and remove the `squid` package:\n\n```\n# systemctl stop squid.service\n# apt purge squid\n```\n\n**- OR -** If the `squid` package is required as a dependency:\n\nRun the following commands to stop and mask the `squid.service`:\n\n```\n# systemctl stop squid.service\n# systemctl mask squid.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `squid` package. If the `squid` package is removed, these dependent packages will be removed as well. Before removing the `squid` package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `squid.service` leaving the `squid` package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use", + "title": "2.1.18 Ensure web server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "Web servers provide the ability to host web site content." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "Unless there is a local site approved requirement to run a web server service on the system, web server packages should be removed to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure web server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `apache2` is not installed:\n\n```\n# dpkg-query -s apache2 &>/dev/null && echo \"apache2 is installed\"\n```\n\nNothing should be returned.\n\nRun the following command to verify `nginx` is not installed:\n\n```\n# dpkg-query -s nginx &>/dev/null && echo \"nginx is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** a package is installed **and** is required for dependencies:\n\nRun the following command to verify `apache2.socket`, `apache2.service`, and `nginx.service` are not enabled:\n\n```\n# systemctl is-enabled apache2.socket apache2.service nginx.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify `apache2.socket`, `apache2.service`, and `nginx.service` are not active:\n\n```\n# systemctl is-active apache2.socket apache2.service nginx.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:**\n\n- Other web server packages may exist. They should also be audited, if not required and authorized by local site policy\n\n- If the package is required for a dependency:\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `httpd.socket`, `httpd.service`, and `nginx.service`, and remove `apache2` and `nginx` packages:\n\n```\n# systemctl stop apache2.socket apache2.service nginx.service\n# apt purge apache2 nginx\n```\n\n**- OR -**\n\n**- IF -** a package is installed **and** is required for dependencies:\n\nRun the following commands to stop and mask `apache2.socket`, `apache2.service`, and `nginx.service`:\n\n```\n# systemctl stop apache2.socket apache2.service nginx.service\n# systemctl mask apache2.socket apache2.service nginx.service\n```\n\n**Note:** Other web server packages may exist. If not required and authorized by local site policy, they should also be removed. If the package is required for a dependency, the service and socket should be stopped and masked.\n\nImpact:\n\nRemoval of web server packages will remove that ability for the server to host web services.\n\n**- IF -** the web server package is required for a dependency, any related service or socket should be stopped and masked.\n\n**Note:** If the remediation steps to mask a service are followed and that package is not installed on the system, the service and/or socket will still be masked. If the package is installed due to an approved requirement to host a web server, the associated service and/or socket would need to be unmasked before it could be enabled and/or started." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use", + "title": "2.1.19 Ensure xinetd services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use_smt", + "name": "statement", + "prose": "The eXtended InterNET Daemon (`xinetd`) is an open source super daemon that replaced the original `inetd` daemon. The `xinetd` daemon listens for well known services and dispatches the appropriate daemon to properly respond to service requests." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "If there are no `xinetd` services required, it is recommended that the package be removed to reduce the attack surface are of the system.\n\n**Note:** If an `xinetd` service or services are required, ensure that any `xinetd` service not required is stopped and masked" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure xinetd services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify the `xinetd` package is not installed:\n\n```\n# dpkg-query -s xinetd &>/dev/null && echo \"xinetd is installed\"\n```\n\nNothing should be returned.\n\n**-OR-**\n\n**-IF-** the `xinetd` package is required as a dependency:\n\nRun the following command to verify `xinetd.service` is not enabled:\n\n```\n# systemctl is-enabled xinetd.service 2>/dev/null | grep 'enabled'\n\nNothing should be returned\n```\n\nRun the following command to verify `xinetd.service` is not active:\n\n```\n# systemctl is-active xinetd.service 2>/dev/null | grep '^active'\n\nNothing should be returned\n```\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `xinetd.service`, and remove the `xinetd` package:\n\n```\n# systemctl stop xinetd.service\n# apt purge xinetd\n```\n\n**-OR-**\n\n**-IF-** the `xinetd` package is required as a dependency:\n\nRun the following commands to stop and mask the `xinetd.service`:\n\n```\n# systemctl stop xinetd.service\n# systemctl mask xinetd.service\n```\n\nImpact:\n\nThere may be packages that are dependent on the `xinetd` package. If the `xinetd` package is removed, these dependent packages will be removed as well. Before removing the `xinetd` package, review any dependent packages to determine if they are required on the system.\n\n**-IF-** a dependent package is required: stop and mask xinetd.service leaving the xinetd package installed." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.20_Ensure_X_window_server_services_are_not_in_use", + "title": "2.1.20 Ensure X window server services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.20_Ensure_X_window_server_services_are_not_in_use_smt", + "name": "statement", + "prose": "The X Window System provides a Graphical User Interface (GUI) where users can have multiple windows in which to run programs and various add on. The X Windows system is typically used on workstations where users login, but not on servers where users typically do not login." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.20_Ensure_X_window_server_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "Unless your organization specifically requires graphical login access via X Windows, remove it to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.20_Ensure_X_window_server_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure X window server services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.20_Ensure_X_window_server_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.20_Ensure_X_window_server_services_are_not_in_use_obj" + } + ], + "prose": "**- IF -** a Graphical Desktop Manager or X-Windows server is not required and approved by local site policy:\n\nRun the following command to Verify X Windows Server is not installed.\n\n```\ndpkg-query -s xserver-common &>/dev/null && echo \"xserver-common is installed\"\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.20_Ensure_X_window_server_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** a Graphical Desktop Manager or X-Windows server is not required and approved by local site policy:\n\nRun the following command to remove the X Windows Server package:\n\n```\n# apt purge xserver-common\n```\n\nImpact:\n\nIf a Graphical Desktop Manager (GDM) is in use on the system, there may be a dependency on the `xorg-x11-server-common` package. If the GDM is required and approved by local site policy, the package should **not** be removed.\n\nMany Linux systems run applications which require a Java runtime. Some Linux Java packages have a dependency on specific X Windows xorg-x11-fonts. One workaround to avoid this dependency is to use the \"headless\" Java packages for your specific Java runtime." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode", + "title": "2.1.21 Ensure mail transfer agent is configured for local-only mode", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode_smt", + "name": "statement", + "prose": "Mail Transfer Agents (MTA), such as sendmail and Postfix, are used to listen for incoming mail and transfer the messages to the appropriate user or mail server. If the system is not intended to be a mail server, it is recommended that the MTA be configured to only process local mail." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode_rationale", + "name": "rationale", + "prose": "The software for all Mail Transfer Agents is complex and most have a long history of security issues. While it is important to ensure that the system can process local mail messages, it is not necessary to have the MTA's daemon listening on a port unless the server is intended to be a mail server that receives and processes mail from other systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode_obj", + "name": "assessment-objective", + "prose": "Ensure mail transfer agent is configured for local-only mode" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode_obj" + }, + { + "rel": "script", + "href": "#f3b68e83-292c-5797-8dd6-c9cbb3509fbe" + } + ], + "prose": "Run the following script to verify that the MTA is not listening on any non-loopback address ( `127.0.0.1` or `::1`\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_port_list=(\"25\" \"465\" \"587\")\n for l_port_number in \"${a_port_list[@]}\"; do\n if ss -plntu | grep -P -- ':'\"$l_port_number\"'\\b' | grep -Pvq -- '\\h+(127\\.0\\.0\\.1|\\[?::1\\]?):'\"$l_port_number\"'\\b'; then\n a_output2+=(\" - Port \\\"$l_port_number\\\" is listening on a non-loopback network interface\")\n else\n a_output+=(\" - Port \\\"$l_port_number\\\" is not listening on a non-loopback network interface\")\n fi\n done\n if command -v postconf &> /dev/null; then\n l_interfaces=\"$(postconf -n inet_interfaces)\"\n elif command -v exim &> /dev/null; then\n l_interfaces=\"$(exim -bP local_interfaces)\"\n elif command -v sendmail &> /dev/null; then\n l_interfaces=\"$(grep -i \"0 DaemonPortOptions=\" /etc/mail/sendmail.cr | grep -oP '?<=Addr=)[^,+]+')\"\n fi\n if [ -n \"$l_interfaces\" ]; then\n if grep -Pqi '\\ball\\b' <<< \"$l_interfaces\"; then\n a_output2+=(\" - MTA is bound to all network interfaces\")\n elif ! grep -Pqi '(inet_interfaces\\h*=\\h*)?(0\\.0\\.0\\.0|::1|loopback-only)' <<< \"$l_interfaces\"; then\n a_output2+=(\" - MTA is bound to a network interface\" \" \\\"$l_interfaces\\\"\")\n else\n a_output+=(\" - MTA is not bound to a non loopback network interface\" \" \\\"$l_interfaces\\\"\")\n fi\n else\n a_output+=(\" - MTA not detected or in use\")\n fi\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" * Reasons for audit failure *\" \"${a_output2[@]}\" \"\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/postfix/main.cf` and add the following line to the RECEIVING MAIL section. If the line already exists, change it to look like the line below:\n\n```\ninet_interfaces = loopback-only\n```\n\nRun the following command to restart `postfix`:\n\n```\n# systemctl restart postfix\n```\n\n**Note:**\n\n- This recommendation is designed around the postfix mail server.\n\n- Depending on your environment you may have an alternative MTA installed such as exim4. If this is the case consult the documentation for your installed MTA to configure the recommended state." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface", + "title": "2.1.22 Ensure only approved services are listening on a network interface", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface_smt", + "name": "statement", + "prose": "A network port is identified by its number, the associated IP address, and the type of the communication protocol such as TCP or UDP.\n\nA listening port is a network port on which an application or process listens on, acting as a communication endpoint.\n\nEach listening port can be open or closed (filtered) using a firewall. In general terms, an open port is a network port that accepts incoming packets from remote locations." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface_rationale", + "name": "rationale", + "prose": "Services listening on the system pose a potential risk as an attack vector. These services should be reviewed, and if not required, the service should be stopped, and the package containing the service should be removed. If required packages have a dependency, the service should be stopped and masked to reduce the attack surface of the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface_obj", + "name": "assessment-objective", + "prose": "Ensure only approved services are listening on a network interface" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface_obj" + } + ], + "prose": "Run the following command:\n\n```\n# ss -plntu\n```\n\nReview the output to ensure:\n\n- All services listed are required on the system and approved by local site policy.\n\n- Both the port and interface the service is listening on are approved by local site policy.\n\n- If a listed service is not required:\n\n- Remove the package containing the service\n\n- **- IF -** the service's package is required for a dependency, stop and mask the service and/or socket" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop the service and remove the package containing the service:\n\n```\n# systemctl stop .socket .service\n# apt purge \n```\n\n**- OR -** If required packages have a dependency:\n\nRun the following commands to stop and mask the service and socket:\n\n```\n# systemctl stop .socket .service\n# systemctl mask .socket .service\n```\n\n**Note:** replace `` with the appropriate service name.\n\nImpact:\n\nThere may be packages that are dependent on the service's package. If the service's package is removed, these dependent packages will be removed as well. Before removing the service's package, review any dependent packages to determine if they are required on the system.\n\n**- IF -** a dependent package is required: stop and mask the `.socket` and `.service` leaving the service's package installed." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_2.2_Configure_Client_Services", + "title": "Configure Client Services", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed", + "title": "2.2.1 Ensure NIS Client is not installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed_smt", + "name": "statement", + "prose": "The Network Information Service (NIS), formerly known as Yellow Pages, is a client-server directory service protocol used to distribute system configuration files. The NIS client was used to bind a machine to an NIS server and receive the distributed configuration files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed_rationale", + "name": "rationale", + "prose": "The NIS service is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally has been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that the service be removed." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed_obj", + "name": "assessment-objective", + "prose": "Ensure NIS Client is not installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed_obj" + } + ], + "prose": "Verify `nis` is not installed. Use the following command to provide the needed information:\n\n```\n# dpkg-query -s nis &>/dev/null && echo \"nis is installed\"\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Uninstall `nis`:\n\n```\n# apt purge nis\n```\n\nImpact:\n\nMany insecure service clients are used as troubleshooting tools and in testing environments. Uninstalling them can inhibit capability to test and troubleshoot. If they are required it is advisable to remove the clients after use to prevent accidental or intentional misuse." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed", + "title": "2.2.2 Ensure rsh client is not installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed_smt", + "name": "statement", + "prose": "The `rsh-client` package contains the client commands for the rsh services." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed_rationale", + "name": "rationale", + "prose": "These legacy clients contain numerous security exposures and have been replaced with the more secure SSH package. Even if the server is removed, it is best to ensure the clients are also removed to prevent users from inadvertently attempting to use these commands and therefore exposing their credentials. Note that removing the `rsh-client` package removes the clients for `rsh` , `rcp` and `rlogin` ." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed_obj", + "name": "assessment-objective", + "prose": "Ensure rsh client is not installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed_obj" + } + ], + "prose": "Verify `rsh-client` is not installed. Use the following command to provide the needed information:\n\n```\n# dpkg-query -s rsh-client &>/dev/null && echo \"rsh-client is installed\"\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Uninstall `rsh`:\n\n```\n# apt purge rsh-client\n```\n\nImpact:\n\nMany insecure service clients are used as troubleshooting tools and in testing environments. Uninstalling them can inhibit capability to test and troubleshoot. If they are required it is advisable to remove the clients after use to prevent accidental or intentional misuse." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed", + "title": "2.2.3 Ensure talk client is not installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed_smt", + "name": "statement", + "prose": "The `talk` software makes it possible for users to send and receive messages across systems through a terminal session. The `talk` client, which allows initialization of talk sessions, is installed by default." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed_rationale", + "name": "rationale", + "prose": "The software presents a security risk as it uses unencrypted protocols for communication." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed_obj", + "name": "assessment-objective", + "prose": "Ensure talk client is not installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed_obj" + } + ], + "prose": "Verify `talk` is not installed. The following command may provide the needed information:\n\n```\n# dpkg-query -s talk &>/dev/null && echo \"talk is installed\"\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Uninstall `talk`:\n\n```\n# apt purge talk\n```\n\nImpact:\n\nMany insecure service clients are used as troubleshooting tools and in testing environments. Uninstalling them can inhibit capability to test and troubleshoot. If they are required it is advisable to remove the clients after use to prevent accidental or intentional misuse." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed", + "title": "2.2.4 Ensure telnet client is not installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed_smt", + "name": "statement", + "prose": "The `inetutils-telnet` package contains the `telnet` client, which allows users to start connections to other systems via the telnet protocol." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed_rationale", + "name": "rationale", + "prose": "The `telnet` protocol is insecure and unencrypted. The use of an unencrypted transmission medium could allow an unauthorized user to steal credentials. The `ssh` package provides an encrypted session and stronger security and is included in most Linux distributions." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed_obj", + "name": "assessment-objective", + "prose": "Ensure telnet client is not installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed_obj" + } + ], + "prose": "Verify `inetutils-telnet` & `telnet` are not installed. Use the following command to provide the needed information:\n\n```\n# dpkg-query -l | grep -E 'telnet|inetutils-telnet' &>/dev/null && echo \"telnet is installed\"\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to uninstall `telnet` & `inetutils-telnet`:\n\n```\n# apt purge telnet\n# apt purge inetutils-telnet\n```\n\nImpact:\n\nMany insecure service clients are used as troubleshooting tools and in testing environments. Uninstalling them can inhibit capability to test and troubleshoot. If they are required it is advisable to remove the clients after use to prevent accidental or intentional misuse." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed", + "title": "2.2.5 Ensure ldap client is not installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed_smt", + "name": "statement", + "prose": "The Lightweight Directory Access Protocol (LDAP) was introduced as a replacement for NIS/YP. It is a service that provides a method for looking up information from a central database." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed_rationale", + "name": "rationale", + "prose": "If the system will not need to act as an LDAP client, it is recommended that the software be removed to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed_obj", + "name": "assessment-objective", + "prose": "Ensure ldap client is not installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed_obj" + } + ], + "prose": "Verify that `ldap-utils` is not installed. Use the following command to provide the needed information:\n\n```\n# dpkg-query -s ldap-utils &>/dev/null && echo \"ldap-utils is installed\"\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Uninstall `ldap-utils`:\n\n```\n# apt purge ldap-utils\n```\n\nImpact:\n\nRemoving the LDAP client will prevent or inhibit using LDAP for authentication in your environment." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed", + "title": "2.2.6 Ensure ftp client is not installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed_smt", + "name": "statement", + "prose": "`tnftp` an enhanced FTP client, is the user interface to the Internet standard File Transfer Protocol. The program allows a user to transfer files to and from a remote network site." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed_rationale", + "name": "rationale", + "prose": "Unless there is a need to run the system using Internet standard File Transfer Protocol (for example, to allow anonymous downloads), it is recommended that the package be removed to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed_obj", + "name": "assessment-objective", + "prose": "Ensure ftp client is not installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed_obj" + } + ], + "prose": "Verify `tnftp` & `ftp` is not installed. Use the following command to provide the needed information:\n\n```\n# dpkg-query -l | grep -E 'ftp|tnftp' &>/dev/null && echo \"ftp is installed\"\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to uninstall `tnftp` & `ftp`:\n\n```\n# apt purge ftp\n# apt purge tnftp\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_2.3_Configure_Time_Synchronization", + "title": "Configure Time Synchronization", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_2.3.1_Ensure_time_synchronization_is_in_use", + "title": "Ensure time synchronization is in use", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use", + "title": "2.3.1.1 Ensure a single time synchronization daemon is in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use_smt", + "name": "statement", + "prose": "System time should be synchronized between all systems in an environment. This is typically done by establishing an authoritative time server or set of servers and having all systems synchronize their clocks to them.\n\n**Note:**\n\n- **On virtual systems where host based time synchronization is available consult your virtualization software documentation and verify that host based synchronization is in use and follows local site policy. In this scenario, this section should be skipped**\n\n- Only **one** time synchronization method should be in use on the system. Configuring multiple time synchronization methods could lead to unexpected or unreliable results" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use_rationale", + "name": "rationale", + "prose": "Time synchronization is important to support time sensitive security mechanisms and ensures log files have consistent time records across the enterprise, which aids in forensic investigations." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure a single time synchronization daemon is in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use_obj" + }, + { + "rel": "script", + "href": "#2686ef59-353f-5c13-9942-df354bf7ec50" + } + ], + "prose": "On physical systems, and virtual systems where host based time synchronization is not available.\n\n**One** of the two time synchronization daemons should be available; **`chrony`** or **`systemd-timesyncd`**\n\nRun the following script to verify that a single time synchronization daemon is available on the system:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n service_not_enabled_chk()\n {\n l_out2=\"\"\n if systemctl is-enabled \"$l_service_name\" 2>/dev/null | grep -q 'enabled'; then\n l_out2=\"$l_out2\\n - Daemon: \\\"$l_service_name\\\" is enabled on the system\"\n fi\n if systemctl is-active \"$l_service_name\" 2>/dev/null | grep -q '^active'; then\n l_out2=\"$l_out2\\n - Daemon: \\\"$l_service_name\\\" is active on the system\"\n fi\n }\n l_service_name=\"systemd-timesyncd.service\" # Check systemd-timesyncd daemon\n service_not_enabled_chk\n if [ -n \"$l_out2\" ]; then\n l_timesyncd=\"y\"\n l_out_tsd=\"$l_out2\"\n else\n l_timesyncd=\"n\"\n l_out_tsd=\"\\n - Daemon: \\\"$l_service_name\\\" is not enabled and not active on the system\"\n fi\n l_service_name=\"chrony.service\" # Check chrony\n service_not_enabled_chk\n if [ -n \"$l_out2\" ]; then\n l_chrony=\"y\"\n l_out_chrony=\"$l_out2\"\n else\n l_chrony=\"n\"\n l_out_chrony=\"\\n - Daemon: \\\"$l_service_name\\\" is not enabled and not active on the system\"\n fi\n l_status=\"$l_timesyncd$l_chrony\"\n case \"$l_status\" in\n yy)\n l_output2=\" - More than one time sync daemon is in use on the system$l_out_tsd$l_out_chrony\"\n ;;\n nn)\n l_output2=\" - No time sync daemon is in use on the system$l_out_tsd$l_out_chrony\"\n ;;\n yn|ny)\n l_output=\" - Only one time sync daemon is in use on the system$l_out_tsd$l_out_chrony\"\n ;;\n *)\n l_output2=\" - Unable to determine time sync daemon(s) status\"\n ;;\n esac\n\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\\n\"\n fi\n}\n```\n\n**Note:** Follow the guidance in the subsection for the time synchronization daemon available on the system and skip the other time synchronization daemon subsection." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "On physical systems, and virtual systems where host based time synchronization is not available.\n\nSelect **one** of the two time synchronization daemons; **`chrony (1)`** or **`systemd-timesyncd (2)`** and following the remediation procedure for the selected daemon.\n\n**Note:** enabling more than one synchronization daemon could lead to unexpected or unreliable results:\n\n- **`chrony`**\n\nRun the following command to install `chrony`:\n\n```\n# apt install chrony\n```\n\nRun the following commands to stop and mask the `systemd-timesyncd` daemon:\n\n```\n# systemctl stop systemd-timesyncd.service\n\n# systemctl mask systemd-timesyncd.service\n```\n\n**Note:**\n\n- Subsection: ***Configure chrony*** should be followed\n\n- Subsection: ***Configure systemd-timesyncd*** should be skipped\n\n- **`systemd-timesyncd`**\n\nRun the following command to remove the chrony package:\n\n```\n# apt purge chrony\n# apt autoremove chrony\n```\n\n**Note:**\n\n- Subsection: ***Configure systemd-timesyncd*** should be followed\n\n- Subsection: ***Configure chrony*** should be skipped" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_2.3.2_Configure_systemd-timesyncd", + "title": "Configure systemd-timesyncd", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver", + "title": "2.3.2.1 Ensure systemd-timesyncd configured with authorized timeserver", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver_smt", + "name": "statement", + "prose": "`NTP=`\n\n- A space-separated list of NTP server host names or IP addresses. During runtime this list is combined with any per-interface NTP servers acquired from systemd-networkd.service(8). systemd-timesyncd will contact all configured system or per-interface servers in turn, until one responds. When the empty string is assigned, the list of NTP servers is reset, and all prior assignments will have no effect. This setting defaults to an empty list.\n\n`FallbackNTP=`\n\n- A space-separated list of NTP server host names or IP addresses to be used as the fallback NTP servers. Any per-interface NTP servers obtained from systemd-networkd.service(8) take precedence over this setting, as do any servers set via NTP= above. This setting is hence only relevant if no other NTP server information is known. When the empty string is assigned, the list of NTP servers is reset, and all prior assignments will have no effect. If this option is not given, a compiled-in list of NTP servers is used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver_rationale", + "name": "rationale", + "prose": "Time synchronization is important to support time sensitive security mechanisms and to ensure log files have consistent time records across the enterprise to aid in forensic investigations" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver_obj", + "name": "assessment-objective", + "prose": "Ensure systemd-timesyncd configured with authorized timeserver" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver_obj" + }, + { + "rel": "script", + "href": "#b3f0988f-8e03-56a7-94fe-2a8b0c83dd45" + } + ], + "prose": "Run the following command to verify the `NTP` **and/or** `FallbackNTP` option is set to local site approved authoritative time server(s):\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); a_parlist=(\"NTP=[^#\\n\\r]+\" \"FallbackNTP=[^#\\n\\r]+\")\n l_systemd_config_file=\"/etc/systemd/timesyncd.conf\" # Main systemd configuration file\n f_config_file_parameter_chk()\n {\n unset A_out; declare -A A_out # Check config file(s) setting\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_systemd_parameter=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n grep -Piq -- \"^\\h*$l_systemd_parameter_name\\b\" <<< \"$l_systemd_parameter\" && A_out+=([\"$l_systemd_parameter\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdanalyze\" cat-config \"$l_systemd_config_file\" | grep -Pio '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_systemd_file_parameter_name l_systemd_file_parameter_value; do\n l_systemd_file_parameter_name=\"${l_systemd_file_parameter_name// /}\"\n l_systemd_file_parameter_value=\"${l_systemd_file_parameter_value// /}\"\n if grep -Piq \"\\b$l_systemd_parameter_value\\b\" <<< \"$l_systemd_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_systemd_parameter_name\\\" is correctly set to \\\"$l_systemd_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_systemd_parameter_name\\\" is incorrectly set to \\\"$l_systemd_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\" and should have a value matching: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Pio -- \"^\\h*$l_systemd_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_systemd_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_systemd_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n l_systemdanalyze=\"$(readlink -f /bin/systemd-analyze)\"\n while IFS=\"=\" read -r l_systemd_parameter_name l_systemd_parameter_value; do # Assess and check parameters\n l_systemd_parameter_name=\"${l_systemd_parameter_name// /}\"; l_systemd_parameter_value=\"${l_systemd_parameter_value// /}\"\n l_value_out=\"${l_systemd_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```\n\n*Example output:*\n\n```\n- Audit Result:\n ** PASS **\n - \"NTP\" is correctly set to \"time.nist.gov\"\n in \"/etc/systemd/timesyncd.conf.d/60-timesyncd.conf\"\n - \"FallbackNTP\" is correctly set to \"time-a-g.nist.gov\"\n in \"/etc/systemd/timesyncd.conf.d/60-timesyncd.conf\"\n```\n\n**Note:** Please ensure the output for `NTP` and/or `FallbackNTP` is in accordance with local site policy. The timeservers in the example output are provided as an example of possible timeservers and they may not follow local site policy." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set `NTP` and/or `FallbackNPT` parameters to local site approved authoritative time server(s) in `/etc/systemd/timesyncd.conf` or a file in `/etc/systemd/timesyncd.conf.d/` ending in `.conf` in the `[Time]` section:\n\n*Example file:*\n\n```\n[Time]\nNTP=time.nist.gov # Uses the generic name for NIST's time servers\nFallbackNTP=time-a-g.nist.gov time-b-g.nist.gov time-c-g.nist.gov # Space separated list of NIST time servers\n```\n\n*Example script to create systemd drop-in configuration file:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_settings=(\"NTP=time.nist.gov\" \"FallbackNTP=time-a-g.nist.gov time-b-g.nist.gov time-c-g.nist.gov\")\n [ ! -d /etc/systemd/timesyncd.conf.d/ ] && mkdir /etc/systemd/timesyncd.conf.d/\n if grep -Psq -- '^\\h*\\[Time\\]' /etc/systemd/timesyncd.conf.d/60-timesyncd.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/timesyncd.conf.d/60-timesyncd.conf\n else\n printf '%s\\n' \"\" \"[Time]\" \"${a_settings[@]}\" >> /etc/systemd/timesyncd.conf.d/60-timesyncd.conf\n fi\n}\n```\n\n**Note:** If this setting appears in a canonically later file, or later in the same file, the setting will be overwritten\n\nRun to following command to update the parameters in the service:\n\n```\n# systemctl reload-or-restart systemd-journald\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running", + "title": "2.3.2.2 Ensure systemd-timesyncd is enabled and running", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running_smt", + "name": "statement", + "prose": "systemd-timesyncd is a daemon that has been added for synchronizing the system clock across the network" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running_rationale", + "name": "rationale", + "prose": "systemd-timesyncd needs to be enabled and running in order to synchronize the system to a timeserver.\n\nTime synchronization is important to support time sensitive security mechanisms and to ensure log files have consistent time records across the enterprise to aid in forensic investigations" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running_obj", + "name": "assessment-objective", + "prose": "Ensure systemd-timesyncd is enabled and running" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running_obj" + } + ], + "prose": "**- IF -** systemd-timesyncd is in use on the system, run the following commands:\n\nRun the following command to verify that the `systemd-timesyncd` service is enabled:\n\n```\n# systemctl is-enabled systemd-timesyncd.service\n\nenabled\n```\n\nRun the following command to verify that the `systemd-timesyncd` service is active:\n\n```\n# systemctl is-active systemd-timesyncd.service\n\nactive\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** `systemd-timesyncd` is in use on the system, run the following commands:\n\nRun the following command to unmask `systemd-timesyncd.service`:\n\n```\n# systemctl unmask systemd-timesyncd.service\n```\n\nRun the following command to enable and start `systemd-timesyncd.service`:\n\n```\n# systemctl --now enable systemd-timesyncd.service\n```\n\n**- OR -**\n\nIf another time synchronization service is in use on the system, run the following command to stop and mask `systemd-timesyncd`:\n\n```\n# systemctl --now mask systemd-timesyncd.service\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_2.3.3_Configure_chrony", + "title": "Configure chrony", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver", + "title": "2.3.3.1 Ensure chrony is configured with authorized timeserver", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_chrony_timeserver_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "/etc/chrony/chrony.conf" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver_smt", + "name": "statement", + "prose": "-\nserver\n\n- The server directive specifies an NTP server which can be used as a time source. The client-server relationship is strictly hierarchical: a client might synchronize its system time to that of the server, but the server’s system time will never be influenced by that of a client.\n\n- This directive can be used multiple times to specify multiple servers.\n\n- The directive is immediately followed by either the name of the server, or its IP address.\n\n-\npool\n\n- The syntax of this directive is similar to that for the server directive, except that it is used to specify a pool of NTP servers rather than a single NTP server. The pool name is expected to resolve to multiple addresses which might change over time.\n\n- This directive can be used multiple times to specify multiple pools.\n\n- All options valid in the server directive can be used in this directive too." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver_rationale", + "name": "rationale", + "prose": "Time synchronization is important to support time sensitive security mechanisms and to ensure log files have consistent time records across the enterprise to aid in forensic investigations" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver_obj", + "name": "assessment-objective", + "prose": "Ensure chrony is configured with authorized timeserver" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver_obj" + }, + { + "rel": "script", + "href": "#8cb0ff77-5776-5be3-b783-b088b579b951" + } + ], + "prose": "**- IF -** `chrony` is in use on the system, run the following script to ensure `chrony` is configured with an authorized timeserver:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_config_files=(\"/etc/chrony/chrony.conf\")\n l_include='(confdir|sourcedir)' l_parameter_name='(server|pool)' l_parameter_value='.+'\n while IFS= read -r l_conf_loc; do\n l_dir=\"\" l_ext=\"\"\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n if [[ -n \"$l_dir\" && -n \"$l_ext\" ]]; then\n while IFS= read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n fi\n done < <(awk '$1~/^\\s*'\"$l_include\"'$/{print $2}' \"${a_config_files[*]}\" 2>/dev/null)\n for l_file in \"${a_config_files[@]}\"; do\n l_parameter_line=\"$(grep -Psi '^\\h*'\"$l_parameter_name\"'(\\h+|\\h*:\\h*)'\"$l_parameter_value\"'\\b' \"$l_file\")\"\n [ -n \"$l_parameter_line\" ] && a_output+=(\" - Parameter: \\\"$(tr -d '()' <<< ${l_parameter_name//|/ or })\\\"\" \\\n \" Exists in the file: \\\"$l_file\\\" as:\" \"$l_parameter_line\")\n done\n [ \"${#a_output[@]}\" -le \"0\" ] && a_output2+=(\" - Parameter: \\\"$(tr -d '()' <<< ${l_parameter_name//|/ or })\\\"\" \\\n \" Does not exist in the chrony configuration\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/chrony/chrony.conf` or a file ending in `.sources` in `/etc/chrony/sources.d/` and add or edit server or pool lines as appropriate according to local site policy:\n\nEdit the `Chrony` configuration and add or edit the server and/or pool lines returned by the Audit Procedure as appropriate according to local site policy\n\n```\n<[server|pool]> <[remote-server|remote-pool]>\n```\n\n*Example script to add a drop-in configuration for the `pool` directive:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n [ ! -d \"/etc/chrony/sources.d/\" ] && mkdir /etc/chrony/sources.d/\n printf '%s\\n' \"\" \"#The maxsources option is unique to the pool directive\" \\\n \"pool time.nist.gov iburst maxsources 4\" >> /etc/chrony/sources.d/60-sources.sources\n chronyc reload sources &>/dev/null\n}\n```\n\n*Example script to add a drop-in configuration for the `server` directive:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n [ ! -d \"/etc/chrony/sources.d/\" ] && mkdir /etc/chrony/sources.d/\n printf '%s\\n' \"\" \"server time-a-g.nist.gov iburst\" \"server 132.163.97.3 iburst\" \\\n \"server time-d-b.nist.gov iburst\" >> /etc/chrony/sources.d/60-sources.sources\n chronyc reload sources &>/dev/null\n}\n```\n\nRun the following command to reload the `chronyd` config:\n\n```\n# systemctl reload-or-restart chronyd\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony", + "title": "2.3.3.2 Ensure chrony is running as user _chrony", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_service_owned_by_user_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "[c]hronyd:_chrony" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony_smt", + "name": "statement", + "prose": "The `chrony` package is installed with a dedicated user account `_chrony`. This account is granted the access required by the `chronyd` service" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony_rationale", + "name": "rationale", + "prose": "The `chronyd` service should run with only the required privlidges" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony_obj", + "name": "assessment-objective", + "prose": "Ensure chrony is running as user _chrony" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony_obj" + }, + { + "rel": "script", + "href": "#493dae7a-ddc4-5ca6-95da-e85f143fbb0f" + } + ], + "prose": "**- IF -** `chrony` is in use on the system, run the following command to verify the `chronyd` service is being run as the `_chrony` user:\n\n```\n# ps -ef | awk '(/[c]hronyd/ && $1!=\"_chrony\") { print $1 }'\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Add or edit the `user` line to `/etc/chrony/chrony.conf` or a file ending in `.conf` in `/etc/chrony/conf.d/`:\n\n```\nuser _chrony\n```\n\n**- OR -**\n\nIf another time synchronization service is in use on the system, run the following command to remove `chrony` from the system:\n\n```\n# apt purge chrony\n# apt autoremove chrony\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running", + "title": "2.3.3.3 Ensure chrony is enabled and running", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running_smt", + "name": "statement", + "prose": "chrony is a daemon for synchronizing the system clock across the network" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running_rationale", + "name": "rationale", + "prose": "chrony needs to be enabled and running in order to synchronize the system to a timeserver.\n\nTime synchronization is important to support time sensitive security mechanisms and to ensure log files have consistent time records across the enterprise to aid in forensic investigations" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running_obj", + "name": "assessment-objective", + "prose": "Ensure chrony is enabled and running" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running_obj" + } + ], + "prose": "**- IF -** chrony is in use on the system, run the following commands:\n\nRun the following command to verify that the `chrony` service is enabled:\n\n```\n# systemctl is-enabled chrony.service\n\nenabled\n```\n\nRun the following command to verify that the `chrony` service is active:\n\n```\n# systemctl is-active chrony.service\n\nactive\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** `chrony` is in use on the system, run the following commands:\n\nRun the following command to unmask `chrony.service`:\n\n```\n# systemctl unmask chrony.service\n```\n\nRun the following command to enable and start `chrony.service`:\n\n```\n# systemctl --now enable chrony.service\n```\n\n**- OR -**\n\nIf another time synchronization service is in use on the system, run the following command to remove `chrony`:\n\n```\n# apt purge chrony\n# apt autoremove chrony\n```" + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_2.4_Job_Schedulers", + "title": "Job Schedulers", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_2.4.1_Configure_cron", + "title": "Configure cron", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active", + "title": "2.4.1.1 Ensure cron daemon is enabled and active", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active_smt", + "name": "statement", + "prose": "The `cron` daemon is used to execute batch jobs on the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active_rationale", + "name": "rationale", + "prose": "While there may not be user jobs that need to be run on the system, the system does have maintenance jobs that may include security monitoring that have to run, and `cron` is used to execute them." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active_obj", + "name": "assessment-objective", + "prose": "Ensure cron daemon is enabled and active" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active_obj" + } + ], + "prose": "**- IF -** cron is installed on the system:\n\nRun the following command to verify `cron` is enabled:\n\n```\n# systemctl list-unit-files | awk '$1~/^crond?\\.service/{print $2}'\n\nenabled\n```\n\nRun the following command to verify that `cron` is active:\n\n```\n# systemctl list-units | awk '$1~/^crond?\\.service/{print $3}'\n\nactive\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** cron is installed on the system:\n\nRun the following commands to unmask, enable, and start `cron`:\n\n```\n# systemctl unmask \"$(systemctl list-unit-files | awk '$1~/^crond?\\.service/{print $1}')\"\n# systemctl --now enable \"$(systemctl list-unit-files | awk '$1~/^crond?\\.service/{print $1}')\"\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured", + "title": "2.4.1.2 Ensure permissions on /etc/crontab are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured_smt", + "name": "statement", + "prose": "The `/etc/crontab` file is used by `cron` to control its own jobs. The commands in this item make sure that root is the user and group owner of the file and that only the owner can access the file." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured_rationale", + "name": "rationale", + "prose": "This file contains information on what system jobs are run by cron. Write access to these files could provide unprivileged users with the ability to elevate their privileges. Read access to these files could provide users with the ability to gain insight on system jobs that run on the system and could provide them a way to gain unauthorized privileged access." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/crontab are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "**- IF -** cron is installed on the system:\n\nRun the following command and verify `Uid` and `Gid` are both `0/root` and `Access` does not grant permissions to `group` or `other` :\n\n```\n# stat -Lc 'Access: (%a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/crontab\n\nAccess: (600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** cron is installed on the system:\n\nRun the following commands to set ownership and permissions on `/etc/crontab`:\n\n```\n# chown root:root /etc/crontab\n# chmod og-rwx /etc/crontab\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured", + "title": "2.4.1.3 Ensure permissions on /etc/cron.hourly are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured_smt", + "name": "statement", + "prose": "This directory contains system `cron` jobs that need to run on an hourly basis. The files in this directory cannot be manipulated by the `crontab` command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured_rationale", + "name": "rationale", + "prose": "Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/cron.hourly are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "**- IF -** cron is installed on the system:\n\nRun the following command and verify `Uid` and `Gid` are both `0/root` and `Access` does not grant permissions to `group` or `other`:\n\n```\n# stat -Lc 'Access: (%a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/cron.hourly/\n\nAccess: (700/drwx------) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** cron is installed on the system:\n\nRun the following commands to set ownership and permissions on the `/etc/cron.hourly` directory:\n\n```\n# chown root:root /etc/cron.hourly/\n# chmod og-rwx /etc/cron.hourly/\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured", + "title": "2.4.1.4 Ensure permissions on /etc/cron.daily are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured_smt", + "name": "statement", + "prose": "The `/etc/cron.daily` directory contains system cron jobs that need to run on a daily basis. The files in this directory cannot be manipulated by the `crontab` command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured_rationale", + "name": "rationale", + "prose": "Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/cron.daily are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "**- IF -** cron is installed on the system:\n\nRun the following command and verify `Uid` and `Gid` are both `0/root` and `Access` does not grant permissions to `group` or `other`:\n\n```\n# stat -Lc 'Access: (%a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/cron.daily/\n\nAccess: (700/drwx------) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** cron is installed on the system:\n\nRun the following commands to set ownership and permissions on the `/etc/cron.daily` directory:\n\n```\n# chown root:root /etc/cron.daily/\n# chmod og-rwx /etc/cron.daily/\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured", + "title": "2.4.1.5 Ensure permissions on /etc/cron.weekly are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured_smt", + "name": "statement", + "prose": "The `/etc/cron.weekly` directory contains system cron jobs that need to run on a weekly basis. The files in this directory cannot be manipulated by the `crontab` command but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured_rationale", + "name": "rationale", + "prose": "Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/cron.weekly are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "**- IF -** cron is installed on the system:\n\nRun the following command and verify `Uid` and `Gid` are both `0/root` and `Access` does not grant permissions to `group` or `other`:\n\n```\n# stat -Lc 'Access: (%a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/cron.weekly/\n\nAccess: (700/drwx------) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** cron is installed on the system:\n\nRun the following commands to set ownership and permissions on the `/etc/cron.weekly` directory:\n\n```\n# chown root:root /etc/cron.weekly/\n# chmod og-rwx /etc/cron.weekly/\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured", + "title": "2.4.1.6 Ensure permissions on /etc/cron.monthly are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured_smt", + "name": "statement", + "prose": "The `/etc/cron.monthly` directory contains system cron jobs that need to run on a monthly basis. The files in this directory cannot be manipulated by the `crontab` command but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured_rationale", + "name": "rationale", + "prose": "Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/cron.monthly are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "**- IF -** cron is installed on the system:\n\nRun the following command and verify `Uid` and `Gid` are both `0/root` and `Access` does not grant permissions to `group` or `other`:\n\n```\n# stat -Lc 'Access: (%a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/cron.monthly/\n\nAccess: (700/drwx------) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** cron is installed on the system:\n\nRun the following commands to set ownership and permissions on the `/etc/cron.monthly` directory:\n\n```\n# chown root:root /etc/cron.monthly/\n# chmod og-rwx /etc/cron.monthly/\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured", + "title": "2.4.1.7 Ensure permissions on /etc/cron.d are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured_smt", + "name": "statement", + "prose": "The `/etc/cron.d` directory contains system `cron` jobs that need to run in a similar manner to the hourly, daily weekly and monthly jobs from `/etc/crontab`, but require more granular control as to when they run. The files in this directory cannot be manipulated by the `crontab` command but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured_rationale", + "name": "rationale", + "prose": "Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/cron.d are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "**- IF -** cron is installed on the system:\n\nRun the following command and verify `Uid` and `Gid` are both `0/root` and `Access` does not grant permissions to `group` or `other`:\n\n```\n# stat -Lc 'Access: (%a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/cron.d/\n\nAccess: (700/drwx------) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** cron is installed on the system:\n\nRun the following commands to set ownership and permissions on the `/etc/cron.d` directory:\n\n```\n# chown root:root /etc/cron.d/\n# chmod og-rwx /etc/cron.d/\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users", + "title": "2.4.1.8 Ensure crontab is restricted to authorized users", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_crontab_access_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "0137" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users_smt", + "name": "statement", + "prose": "`crontab` is the program used to install, deinstall, or list the tables used to drive the cron daemon. Each user can have their own crontab, and though these are files in `/var/spool/cron/crontabs`, they are not intended to be edited directly.\n\nIf the `/etc/cron.allow` file exists, then you must be listed (one user per line) therein in order to be allowed to use this command. If the `/etc/cron.allow` file does not exist but the `/etc/cron.deny` file does exist, then you must not be listed in the `/etc/cron.deny` file in order to use this command.\n\nIf neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to use this command.\n\nIf both files exist then `/etc/cron.allow` takes precedence. Which means that `/etc/cron.deny` is not considered and your user must be listed in `/etc/cron.allow` in order to be able to use the crontab.\n\nRegardless of the existence of any of these files, the root administrative user is always allowed to setup a crontab.\n\nThe files `/etc/cron.allow` and `/etc/cron.deny`, if they exist, must be either world-readable, or readable by group `crontab`. If they are not, then cron will deny access to all users until the permissions are fixed.\n\nThere is one file for each user's crontab under the `/var/spool/cron/crontabs` directory. Users are not allowed to edit the files under that directory directly to ensure that only users allowed by the system to run periodic tasks can add them, and only syntactically correct crontabs will be written there. This is enforced by having the directory writable only by the `crontab` group and configuring crontab command with the setgid bid set for that specific group.\n\n**Note:**\n\n- Even though a given user is not listed in `cron.allow`, cron jobs can still be run as that user\n\n- The files `/etc/cron.allow` and `/etc/cron.deny`, if they exist, only controls administrative access to the crontab command for scheduling and modifying cron jobs" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users_rationale", + "name": "rationale", + "prose": "On many systems, only the system administrator is authorized to schedule `cron` jobs. Using the `cron.allow` file to control who can run `cron` jobs enforces this policy. It is easier to manage an allow list than a deny list. In a deny list, you could potentially add a user ID to the system and forget to add it to the deny files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users_obj", + "name": "assessment-objective", + "prose": "Ensure crontab is restricted to authorized users" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users_obj" + }, + { + "rel": "script", + "href": "#cf2a8e9a-3c5c-53bf-ba7d-7c3228bec943" + } + ], + "prose": "**- IF -** cron is installed on the system:\n\nRun the following command to verify `/etc/cron.allow`:\n\n- Exists\n\n- Is mode `0640` or more restrictive\n\n- Is owned by the user `root`\n\n- Is group owned by the group `root` **- OR -** the group `crontab`\n\n```\n# stat -Lc 'Access: (%a/%A) Owner: (%U) Group: (%G)' /etc/cron.allow\n```\n\nVerify the returned value is:\n\n```\nAccess: (640/-rw-r-----) Owner: (root) Group: (root)\n- OR -\nAccess: (640/-rw-r-----) Owner: (root) Group: (crontab)\n```\n\nRun the following command to verify either `cron.deny` doesn't exist or is:\n\n- Mode `0640` or more restrictive\n\n- Owned by the user `root`\n\n- Is group owned by the group `root` **- OR -** the group `crontab`\n\n```\n# [ -e \"/etc/cron.deny\" ] && stat -Lc 'Access: (%a/%A) Owner: (%U) Group: (%G)' /etc/cron.deny\n```\n\nVerify either nothing is returned **- OR -** returned value is one of the following:\n\n```\nAccess: (640/-rw-r-----) Owner: (root) Group: (root)\n- OR -\nAccess: (640/-rw-r-----) Owner: (root) Group: (crontab)\n```\n\n**Note:** On systems where cron is configured to use the group `crontab`, if the group `crontab` is not set as the owner of `cron.allow`, then cron will deny access to all users and you will see an error similar to:\n\n```\nYou () are not allowed to use this program (crontab)\nSee crontab(1) for more information\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** cron is installed on the system:\n\nRun the following script to:\n\n- Create `/etc/cron.allow` if it doesn't exist\n\n- Change owner to user `root`\n\n- Change group owner to group `root` **- OR -** group `crontab` if it exists\n\n- Change mode to `640` or more restrictive\n\n```bash\n#!/usr/bin/env bash\n\n{\n [ ! -e \"/etc/cron.deny\" ] && touch /etc/cron.allow\n chmod u-x,g-wx,o-rwx /etc/cron.allow\n if grep -Pq -- '^\\h*crontab\\:' /etc/group; then\n chown root:crontab /etc/cron.allow\n else\n chown root:root /etc/cron.allow\n fi\n}\n```\n\n**- IF -** `/etc/cron.deny` exists, run the following script to:\n\n- Change owner to user `root`\n\n- Change group owner to group `root` **- OR -** group `crontab` if it exists\n\n- Change mode to `640` or more restrictive\n\n```bash\n#!/usr/bin/env bash\n\n{\n if [ -e \"/etc/cron.deny\" ]; then\n chmod u-x,g-wx,o-rwx /etc/cron.deny\n if grep -Pq -- '^\\h*crontab\\:' /etc/group; then\n chown root:crontab /etc/cron.deny\n else\n chown root:root /etc/cron.deny\n fi\n fi\n}\n```\n\n**Note:** On systems where cron is configured to use the group `crontab`, if the group `crontab` is not set as the owner of `cron.allow`, then cron will deny access to all users and you will see an error similar to:\n\n```\nYou () are not allowed to use this program (crontab)\nSee crontab(1) for more information\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_2.4.2_Configure_at", + "title": "Configure at", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users", + "title": "2.4.2.1 Ensure at is restricted to authorized users", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users_smt", + "name": "statement", + "prose": "`at` allows fairly complex time specifications, extending the POSIX.2 standard. It accepts times of the form HH:MM to run a job at a specific time of day. (If that time is already past, the next day is assumed.) You may also specify midnight, noon, or teatime (4pm) and you can have a time-of-day suffixed with AM or PM for running in the morning or the evening. You can also say what day the job will be run, by giving a date in the form month-name day with an optional year, or giving a date of the form MMDD[CC]YY, MM/DD/[CC]YY, DD.MM.[CC]YY or [CC]YY-MM-DD. The specification of a date must follow the specification of the time of day. You can also give times like now + count time-units, where the time-units can be minutes, hours, days, or weeks and you can tell at to run the job today by suffixing the time with today and to run the job tomorrow by suffixing the time with tomorrow.\n\nThe `/etc/at.allow` and `/etc/at.deny` files determine which user can submit commands for later execution via at or batch. The format of the files is a list of usernames, one on each line. Whitespace is not permitted. If the file `/etc/at.allow` exists, only usernames mentioned in it are allowed to use at. If `/etc/at.allow` does not exist, `/etc/at.deny` is checked, every username not mentioned in it is then allowed to use at. An empty `/etc/at.deny` means that every user may use at. If neither file exists, only the superuser is allowed to use at." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users_rationale", + "name": "rationale", + "prose": "On many systems, only the system administrator is authorized to schedule `at` jobs. Using the `at.allow` file to control who can run `at` jobs enforces this policy. It is easier to manage an allow list than a deny list. In a deny list, you could potentially add a user ID to the system and forget to add it to the deny files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users_obj", + "name": "assessment-objective", + "prose": "Ensure at is restricted to authorized users" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "**- IF -** at is installed on the system:\n\nRun the following command to verify `/etc/at.allow`:\n\n- Exists\n\n- Is mode `0640` or more restrictive\n\n- Is owned by the user `root`\n\n- Is group owned by the group `daemon` or group `root`\n\n```\n# stat -Lc 'Access: (%a/%A) Owner: (%U) Group: (%G)' /etc/at.allow\n\nAccess: (640/-rw-r-----) Owner: (root) Group: (daemon)\n-OR-\nAccess: (640/-rw-r-----) Owner: (root) Group: (root)\n```\n\nVerify mode is `640` or more restrictive, owner is `root`, and group is `daemon` or `root`\n\nRun the following command to verify `at.deny` doesn't exist, **-OR-** is:\n\n- Mode `0640` or more restrictive\n\n- Owned by the user `root`\n\n- Group owned by the group `daemon` or group `root`\n\n```\n# [ -e \"/etc/at.deny\" ] && stat -Lc 'Access: (%a/%A) Owner: (%U) Group: (%G)' /etc/at.deny\n\nAccess: (640/-rw-r-----) Owner: (root) Group: (daemon)\n-OR-\nAccess: (640/-rw-r-----) Owner: (root) Group: (root)\n-OR-\nNothing is returned\n```\n\nIf a value is returned, verify mode is 640 or more restrictive, owner is `root`, and group is `daemon` or `root`" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** at is installed on the system:\n\nRun the following script to:\n\n- `/etc/at.allow`:\n\n- Create the file if it doesn't exist\n\n- Change owner or user `root`\n\n- If group `daemon` exists, change to group `daemon`, else change group to `root`\n\n- Change mode to `640` or more restrictive\n\n- **- IF -** `/etc/at.deny` exists:\n\n- Change owner or user `root`\n\n- If group `daemon` exists, change to group `daemon`, else change group to `root`\n\n- Change mode to `640` or more restrictive\n\n```bash\n#!/usr/bin/env bash\n\n{\n grep -Pq -- '^daemon\\b' /etc/group && l_group=\"daemon\" || l_group=\"root\"\n [ ! -e \"/etc/at.allow\" ] && touch /etc/at.allow\n chown root:\"$l_group\" /etc/at.allow\n chmod u-x,g-wx,o-rwx /etc/at.allow\n [ -e \"/etc/at.deny\" ] && chown root:\"$l_group\" /etc/at.deny\n [ -e \"/etc/at.deny\" ] && chmod u-x,g-wx,o-rwx /etc/at.deny\n}\n```" + } + ] + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_3_Network", + "title": "Network", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_3.1_Configure_Network_Devices", + "title": "Configure Network Devices", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified", + "title": "3.1.1 Ensure IPv6 status is identified", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified_smt", + "name": "statement", + "prose": "Internet Protocol Version 6 (IPv6) is the most recent version of Internet Protocol (IP). It's designed to supply IP addressing and additional security to support the predicted growth of connected devices. IPv6 is based on 128-bit addressing and can support 340 undecillion, which is 340,282,366,920,938,463,463,374,607,431,768,211,456 unique addresses.\n\nFeatures of IPv6\n\n- Hierarchical addressing and routing infrastructure\n\n- Statefull and Stateless configuration\n\n- Support for quality of service (QoS)\n\n- An ideal protocol for neighboring node interaction" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified_rationale", + "name": "rationale", + "prose": "IETF RFC 4038 recommends that applications are built with an assumption of dual stack. It is recommended that IPv6 be enabled and configured in accordance with Benchmark recommendations.\n\n**- IF -** dual stack and IPv6 are not used in your environment, IPv6 may be disabled to reduce the attack surface of the system, and recommendations pertaining to IPv6 can be skipped.\n\n**Note:** It is recommended that IPv6 be enabled and configured unless this is against local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified_obj", + "name": "assessment-objective", + "prose": "Ensure IPv6 status is identified" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified_obj" + }, + { + "rel": "script", + "href": "#a1587053-8ee8-519f-a5fa-90a621907ce1" + } + ], + "prose": "Run the following script to identify if IPv6 is enabled on the system:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_output=\"- IPv6 is not enabled\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_output=\"- IPv6 is not enabled\"\n fi\n [ -z \"$l_output\" ] && l_output=\"- IPv6 is enabled\"\n echo -e \"\\n$l_output\\n\"\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Enable or disable IPv6 in accordance with system requirements and local site policy\n\nImpact:\n\nIETF RFC 4038 recommends that applications are built with an assumption of dual stack.\n\nWhen enabled, IPv6 will require additional configuration to reduce risk to the system." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled", + "title": "3.1.2 Ensure wireless interfaces are disabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled_smt", + "name": "statement", + "prose": "Wireless networking is used when wired networks are unavailable." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled_rationale", + "name": "rationale", + "prose": "**-IF-** wireless is not to be used, wireless devices can be disabled to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure wireless interfaces are disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled_obj" + }, + { + "rel": "script", + "href": "#1f5cef69-4a5c-5158-b8a9-1cb2e1b4b1e6" + } + ], + "prose": "Run the following script to verify no wireless interfaces are active on the system:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n module_chk()\n {\n # Check how module will be loaded\n l_loadable=\"$(modprobe -n -v \"$l_mname\")\"\n if grep -Pq -- '^\\h*install \\/bin\\/(true|false)' <<< \"$l_loadable\"; then\n l_output=\"$l_output\\n - module: \\\"$l_mname\\\" is not loadable: \\\"$l_loadable\\\"\"\n else\n l_output2=\"$l_output2\\n - module: \\\"$l_mname\\\" is loadable: \\\"$l_loadable\\\"\"\n fi\n # Check is the module currently loaded\n if ! lsmod | grep \"$l_mname\" > /dev/null 2>&1; then\n l_output=\"$l_output\\n - module: \\\"$l_mname\\\" is not loaded\"\n else\n l_output2=\"$l_output2\\n - module: \\\"$l_mname\\\" is loaded\"\n fi\n # Check if the module is deny listed\n if modprobe --showconfig | grep -Pq -- \"^\\h*blacklist\\h+$l_mname\\b\"; then\n l_output=\"$l_output\\n - module: \\\"$l_mname\\\" is deny listed in: \\\"$(grep -Pl -- \"^\\h*blacklist\\h+$l_mname\\b\" /etc/modprobe.d/*)\\\"\"\n else\n l_output2=\"$l_output2\\n - module: \\\"$l_mname\\\" is not deny listed\"\n fi\n }\n if [ -n \"$(find /sys/class/net/*/ -type d -name wireless)\" ]; then\n l_dname=$(for driverdir in $(find /sys/class/net/*/ -type d -name wireless | xargs -0 dirname); do basename \"$(readlink -f \"$driverdir\"/device/driver/module)\";done | sort -u)\n for l_mname in $l_dname; do\n module_chk\n done\n fi\n # Report results. If no failures output in l_output2, we pass\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\"\n if [ -z \"$l_output\" ]; then\n echo -e \"\\n - System has no wireless NICs installed\"\n else\n echo -e \"\\n$l_output\\n\"\n fi\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Reason(s) for audit failure:\\n$l_output2\\n\"\n [ -n \"$l_output\" ] && echo -e \"\\n- Correctly set:\\n$l_output\\n\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to disable any wireless interfaces:\n\n```bash\n#!/usr/bin/env bash\n\n{\n module_fix()\n {\n if ! modprobe -n -v \"$l_mname\" | grep -P -- '^\\h*install \\/bin\\/(true|false)'; then\n echo -e \" - setting module: \\\"$l_mname\\\" to be un-loadable\"\n echo -e \"install $l_mname /bin/false\" >> /etc/modprobe.d/\"$l_mname\".conf\n fi\n if lsmod | grep \"$l_mname\" > /dev/null 2>&1; then\n echo -e \" - unloading module \\\"$l_mname\\\"\"\n modprobe -r \"$l_mname\"\n fi\n if ! grep -Pq -- \"^\\h*blacklist\\h+$l_mname\\b\" /etc/modprobe.d/*; then\n echo -e \" - deny listing \\\"$l_mname\\\"\"\n echo -e \"blacklist $l_mname\" >> /etc/modprobe.d/\"$l_mname\".conf\n fi\n }\n if [ -n \"$(find /sys/class/net/*/ -type d -name wireless)\" ]; then\n l_dname=$(for driverdir in $(find /sys/class/net/*/ -type d -name wireless | xargs -0 dirname); do basename \"$(readlink -f \"$driverdir\"/device/driver/module)\";done | sort -u)\n for l_mname in $l_dname; do\n module_fix\n done\n fi\n}\n```\n\nImpact:\n\nMany if not all laptop workstations and some desktop workstations will connect via wireless requiring these interfaces be enabled." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use", + "title": "3.1.3 Ensure bluetooth services are not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use_smt", + "name": "statement", + "prose": "Bluetooth is a short-range wireless technology standard that is used for exchanging data between devices over short distances. It employs UHF radio waves in the ISM bands, from 2.402 GHz to 2.48 GHz. It is mainly used as an alternative to wire connections." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use_rationale", + "name": "rationale", + "prose": "An attacker may be able to find a way to access or corrupt your data. One example of this type of activity is `bluesnarfing`, which refers to attackers using a Bluetooth connection to steal information off of your Bluetooth device. Also, viruses or other malicious code can take advantage of Bluetooth technology to infect other devices. If you are infected, your data may be corrupted, compromised, stolen, or lost." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure bluetooth services are not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use_obj" + } + ], + "prose": "Run the following command to verify the `bluez` package is not installed:\n\n```\n# dpkg-query -s bluez &>/dev/null && echo \"bluez is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\n**- IF -** the `bluez` package is required as a dependency:\n\nRun the following command to verify `bluetooth.service` is not enabled:\n\n```\n# systemctl is-enabled bluetooth.service 2>/dev/null | grep 'enabled'\n```\n\nNothing should be returned.\n\nRun the following command to verify `bluetooth.service` is not active:\n\n```\n# systemctl is-active bluetooth.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned.\n\n**Note:** If the package is required for a dependency\n\n- Ensure the dependent package is approved by local site policy\n\n- Ensure stopping and masking the service and/or socket meets local site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop `bluetooth.service`, and remove the `bluez` package:\n\n```\n# systemctl stop bluetooth.service\n# apt purge bluez\n```\n\n**- OR -**\n\n**- IF -** the `bluez` package is required as a dependency:\n\nRun the following commands to stop and mask `bluetooth.service`:\n\n```\n# systemctl stop bluetooth.service\n# systemctl mask bluetooth.service\n```\n\n**Note:** A reboot may be required\n\nImpact:\n\nMany personal electronic devices (PEDs) use Bluetooth technology. For example, you may be able to operate your computer with a wireless keyboard. Disabling Bluetooth will prevent these devices from connecting to the system.\n\nThere may be packages that are dependent on the `bluez` package. If the `bluez` package is removed, these dependent packages will be removed as well. Before removing the `bluez` package, review any dependent packages to determine if they are required on the system.\n\n**-IF-** a dependent package is required: stop and mask `bluetooth.service` leaving the `bluez` package installed." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_3.2_Configure_Network_Kernel_Modules", + "title": "Configure Network Kernel Modules", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available", + "title": "3.2.1 Ensure dccp kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "dccp:net" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The Datagram Congestion Control Protocol (DCCP) is a transport layer protocol that supports streaming media and telephony. DCCP provides a way to gain access to congestion control, without having to do it at the application layer, but does not provide in-sequence delivery." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "**- IF -** the protocol is not required, it is recommended that the drivers not be installed to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure dccp kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `dccp` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `dccp` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"dccp\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `dccp` module:\n\n**- IF -** the `dccp` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install dccp /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist dccp` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r dccp 2>/dev/null; rmmod dccp 2>/dev/null` to remove `dccp` from the kernel\n\n**- IF -** the `dccp` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"dccp\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available", + "title": "3.2.2 Ensure tipc kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "tipc:net" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The Transparent Inter-Process Communication (TIPC) protocol is designed to provide communication between cluster nodes." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "**- IF -** the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure tipc kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `tipc` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `tipc` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"tipc\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `tipc` module:\n\n**- IF -** the `tipc` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install tipc /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist tipc` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r tipc 2>/dev/null; rmmod tipc 2>/dev/null` to remove `tipc` from the kernel\n\n**- IF -** the `tipc` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"tipc\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available", + "title": "3.2.3 Ensure rds kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "rds:net" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The Reliable Datagram Sockets (RDS) protocol is a transport layer protocol designed to provide low-latency, high-bandwidth communications between cluster nodes. It was developed by the Oracle Corporation." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "**- IF -** the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure rds kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `rds` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `rds` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"rds\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `rds` module:\n\n**- IF -** the `rds` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install rds /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist rds` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r rds 2>/dev/null; rmmod rds 2>/dev/null` to remove `rds` from the kernel\n\n**- IF -** the `rds` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"rds\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available", + "title": "3.2.4 Ensure sctp kernel module is not available", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_module_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "sctp:net" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available_smt", + "name": "statement", + "prose": "The Stream Control Transmission Protocol (SCTP) is a transport layer protocol used to support message oriented communication, with several streams of messages in one connection. It serves a similar function as TCP and UDP, incorporating features of both. It is message-oriented like UDP, and ensures reliable in-sequence transport of messages with congestion control like TCP." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available_rationale", + "name": "rationale", + "prose": "**- IF -** the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available_obj", + "name": "assessment-objective", + "prose": "Ensure sctp kernel module is not available" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available_obj" + }, + { + "rel": "script", + "href": "#57406427-e772-5765-9a71-89d9da9cd0b3" + } + ], + "prose": "Run the following script to verify:\n\n**- IF -** the `sctp` kernel module is available in ANY installed kernel, verify:\n\n- An entry including `/bin/true` or `/bin/false` exists in a file within the `/etc/modprobe.d/` directory\n\n- The module is deny listed in a file within the `/etc/modprobe.d/` directory\n\n- The module is not loaded in the running kernel\n\n**- IF -** the `sctp` kernel module is not available on the system, or pre-compiled into the kernel, no additional configuration is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"sctp\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_chk()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if ! lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loaded\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loaded\")\n fi\n if grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is not loadable\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is loadable\")\n fi\n if grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" is deny listed\")\n else\n a_output2+=(\" - kernel module: \\\"$l_mod_name\\\" is not deny listed\")\n fi\n }\n for l_mod_base_directory in $l_mod_path; do\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_chk\n else\n a_output+=(\" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\")\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"- Correctly set:\" \"${a_output[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to unload and disable the `sctp` module:\n\n**- IF -** the `sctp` kernel module is available in ANY installed kernel:\n\n- Create a file ending in `.conf` with `install sctp /bin/false` in the `/etc/modprobe.d/` directory\n\n- Create a file ending in `.conf` with `blacklist sctp` in the `/etc/modprobe.d/` directory\n\n- Run `modprobe -r sctp 2>/dev/null; rmmod sctp 2>/dev/null` to remove `sctp` from the kernel\n\n**- IF -** the `sctp` kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=() a_output3=() l_dl=\"\" l_mod_name=\"sctp\" l_mod_type=\"net\"\n l_mod_path=\"$(readlink -f /lib/modules/**/kernel/$l_mod_type | sort -u)\"\n f_module_fix()\n {\n l_dl=\"y\" a_showconfig=()\n while IFS= read -r l_showconfig; do\n a_showconfig+=(\"$l_showconfig\")\n done < <(modprobe --showconfig | grep -P -- '\\b(install|blacklist)\\h+'\"${l_mod_chk_name//-/_}\"'\\b')\n if lsmod | grep \"$l_mod_chk_name\" &> /dev/null; then\n a_output2+=(\" - unloading kernel module: \\\"$l_mod_name\\\"\")\n modprobe -r \"$l_mod_chk_name\" 2>/dev/null; rmmod \"$l_mod_name\" 2>/dev/null\n fi\n if ! grep -Pq -- '\\binstall\\h+'\"${l_mod_chk_name//-/_}\"'\\h+(\\/usr)?\\/bin\\/(true|false)\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - setting kernel module: \\\"$l_mod_name\\\" to \\\"$(readlink -f /bin/false)\\\"\")\n printf '%s\\n' \"install $l_mod_chk_name $(readlink -f /bin/false)\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n if ! grep -Pq -- '\\bblacklist\\h+'\"${l_mod_chk_name//-/_}\"'\\b' <<< \"${a_showconfig[*]}\"; then\n a_output2+=(\" - denylisting kernel module: \\\"$l_mod_name\\\"\")\n printf '%s\\n' \"blacklist $l_mod_chk_name\" >> /etc/modprobe.d/\"$l_mod_name\".conf\n fi\n }\n for l_mod_base_directory in $l_mod_path; do # Check if the module exists on the system\n if [ -d \"$l_mod_base_directory/${l_mod_name/-/\\/}\" ] && [ -n \"$(ls -A \"$l_mod_base_directory/${l_mod_name/-/\\/}\")\" ]; then\n a_output3+=(\" - \\\"$l_mod_base_directory\\\"\")\n l_mod_chk_name=\"$l_mod_name\"\n [[ \"$l_mod_name\" =~ overlay ]] && l_mod_chk_name=\"${l_mod_name::-2}\"\n [ \"$l_dl\" != \"y\" ] && f_module_fix\n else\n printf '%s\\n' \" - kernel module: \\\"$l_mod_name\\\" doesn't exist in \\\"$l_mod_base_directory\\\"\"\n fi\n done\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" -- INFO --\" \" - module: \\\"$l_mod_name\\\" exists in:\" \"${a_output3[@]}\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\" || printf '%s\\n' \"\" \" - No changes needed\"\n printf '%s\\n' \"\" \" - remediation of kernel module: \\\"$l_mod_name\\\" complete\" \"\"\n}\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_3.3_Configure_Network_Kernel_Parameters", + "title": "Configure Network Kernel Parameters", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled", + "title": "3.3.1 Ensure ip forwarding is disabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled_smt", + "name": "statement", + "prose": "The `net.ipv4.ip_forward` and `net.ipv6.conf.all.forwarding` flags are used to tell the system whether it can forward packets or not." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled_rationale", + "name": "rationale", + "prose": "Setting `net.ipv4.ip_forward` and `net.ipv6.conf.all.forwarding` to `0` ensures that a system with multiple interfaces (for example, a hard proxy), will never be able to forward packets, and therefore, never serve as a router." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure ip forwarding is disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameters are set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.ip_forward` is set to `0`\n\n- `net.ipv6.conf.all.forwarding` is set to `0`\n\n**Note:**\n\n- kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n- IPv6 kernel parameters only apply to systems where IPv6 is enabled\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.ip_forward=0\" \"net.ipv6.conf.all.forwarding=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameter in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.ip_forward = 0`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.ip_forward = 0\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.ip_forward=0\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**- IF -** IPv6 is enabled on the system:\n\nSet the following parameter in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv6.conf.all.forwarding = 0`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv6.conf.all.forwarding = 0\" >> /etc/sysctl.d/60-netipv6_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv6.conf.all.forwarding=0\n sysctl -w net.ipv6.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten\n\nImpact:\n\nIP forwarding is required on systems configured to act as a router. If these parameters are disabled, the system will not be able to perform as a router.\n\nMany Cloud Service Provider (CSP) hosted systems require IP forwarding to be enabled. If the system is running on a CSP platform, this requirement should be reviewed before disabling IP forwarding." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled", + "title": "3.3.2 Ensure packet redirect sending is disabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled_smt", + "name": "statement", + "prose": "ICMP Redirects are used to send routing information to other hosts. As a host itself does not act as a router (in a host only configuration), there is no need to send redirects." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled_rationale", + "name": "rationale", + "prose": "An attacker could use a compromised host to send invalid ICMP redirects to other router devices in an attempt to corrupt routing and have users access a system set up by the attacker as opposed to a valid system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure packet redirect sending is disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameters are set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.conf.all.send_redirects` is set to `0`\n\n- `net.ipv4.conf.default.send_redirects` is set to `0`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.send_redirects=0\" \"net.ipv4.conf.default.send_redirects=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameters in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.conf.all.send_redirects = 0`\n\n- `net.ipv4.conf.default.send_redirects = 0`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.conf.all.send_redirects = 0\" \"net.ipv4.conf.default.send_redirects = 0\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.send_redirects=0\n sysctl -w net.ipv4.conf.default.send_redirects=0\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten\n\nImpact:\n\nIP forwarding is required on systems configured to act as a router. If these parameters are disabled, the system will not be able to perform as a router." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored", + "title": "3.3.3 Ensure bogus icmp responses are ignored", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_kernel_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "net.ipv4.icmp_ignore_bogus_error_responses=1" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored_smt", + "name": "statement", + "prose": "Setting `net.ipv4.icmp_ignore_bogus_error_responses` to `1` prevents the kernel from logging bogus responses (RFC-1122 non-compliant) from broadcast reframes, keeping file systems from filling up with useless log messages." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored_rationale", + "name": "rationale", + "prose": "Some routers (and some attackers) will send responses that violate RFC-1122 and attempt to fill up a log file system with many useless error messages." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored_obj", + "name": "assessment-objective", + "prose": "Ensure bogus icmp responses are ignored" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameter is set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.icmp_ignore_bogus_error_responses` is set to `1`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.icmp_ignore_bogus_error_responses=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameter in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.icmp_ignore_bogus_error_responses = 1`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.icmp_ignore_bogus_error_responses = 1\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored", + "title": "3.3.4 Ensure broadcast icmp requests are ignored", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_kernel_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "net.ipv4.icmp_echo_ignore_broadcasts=1" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored_smt", + "name": "statement", + "prose": "Setting `net.ipv4.icmp_echo_ignore_broadcasts` to `1` will cause the system to ignore all ICMP echo and timestamp requests to broadcast and multicast addresses." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored_rationale", + "name": "rationale", + "prose": "Accepting ICMP echo and timestamp requests with broadcast or multicast destinations for your network could be used to trick your host into starting (or participating) in a Smurf attack. A Smurf attack relies on an attacker sending large amounts of ICMP broadcast messages with a spoofed source address. All hosts receiving this message and responding would send echo-reply messages back to the spoofed address, which is probably not routable. If many hosts respond to the packets, the amount of traffic on the network could be significantly multiplied." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored_obj", + "name": "assessment-objective", + "prose": "Ensure broadcast icmp requests are ignored" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameter is set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.icmp_echo_ignore_broadcasts` is set to `1`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.icmp_echo_ignore_broadcasts=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameter in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.icmp_echo_ignore_broadcasts = 1`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.icmp_echo_ignore_broadcasts = 1\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted", + "title": "3.3.5 Ensure icmp redirects are not accepted", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted_smt", + "name": "statement", + "prose": "ICMP redirect messages are packets that convey routing information and tell your host (acting as a router) to send packets via an alternate path. It is a way of allowing an outside routing device to update your system routing tables." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted_rationale", + "name": "rationale", + "prose": "ICMP redirect messages are packets that convey routing information and tell your host (acting as a router) to send packets via an alternate path. It is a way of allowing an outside routing device to update your system routing tables. By setting `net.ipv4.conf.all.accept_redirects`, `net.ipv4.conf.default.accept_redirects`, `net.ipv6.conf.all.accept_redirects`, and `net.ipv6.conf.default.accept_redirects` to `0`, the system will not accept any ICMP redirect messages, and therefore, won't allow outsiders to update the system's routing tables." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted_obj", + "name": "assessment-objective", + "prose": "Ensure icmp redirects are not accepted" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameters are set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.conf.all.accept_redirects` is set to `0`\n\n- `net.ipv4.conf.default.accept_redirects` is set to `0`\n\n- `net.ipv6.conf.all.accept_redirects` is set to `0`\n\n- `net.ipv6.conf.default.accept_redirects` is set to `0`\n\n**Note:**\n\n- kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n- IPv6 kernel parameters only apply to systems where IPv6 is enabled\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.accept_redirects=0\" \"net.ipv4.conf.default.accept_redirects=0\" \"net.ipv6.conf.all.accept_redirects=0\" \"net.ipv6.conf.default.accept_redirects=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameters in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.conf.all.accept_redirects = 0`\n\n- `net.ipv4.conf.default.accept_redirects = 0`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.conf.all.accept_redirects = 0\" \"net.ipv4.conf.default.accept_redirects = 0\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.accept_redirects=0\n sysctl -w net.ipv4.conf.default.accept_redirects=0\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**- IF -** IPv6 is enabled on the system:\n\nSet the following parameters in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv6.conf.all.accept_redirects = 0`\n\n- `net.ipv6.conf.default.accept_redirects = 0`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv6.conf.all.accept_redirects = 0\" \"net.ipv6.conf.default.accept_redirects = 0\" >> /etc/sysctl.d/60-netipv6_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv6.conf.all.accept_redirects=0\n sysctl -w net.ipv6.conf.default.accept_redirects=0\n sysctl -w net.ipv6.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted", + "title": "3.3.6 Ensure secure icmp redirects are not accepted", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted_smt", + "name": "statement", + "prose": "Secure ICMP redirects are the same as ICMP redirects, except they come from gateways listed on the default gateway list. It is assumed that these gateways are known to your system, and that they are likely to be secure." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted_rationale", + "name": "rationale", + "prose": "It is still possible for even known gateways to be compromised. Setting `net.ipv4.conf.all.secure_redirects` and `net.ipv4.conf.default.secure_redirects` to `0` protects the system from routing table updates by possibly compromised known gateways." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted_obj", + "name": "assessment-objective", + "prose": "Ensure secure icmp redirects are not accepted" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameters are set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.conf.all.secure_redirects` is set to `0`\n\n- `net.ipv4.conf.default.secure_redirects` is set to `0`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.secure_redirects=0\" \"net.ipv4.conf.default.secure_redirects=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameters in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.conf.all.secure_redirects = 0`\n\n- `net.ipv4.conf.default.secure_redirects = 0`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.conf.all.secure_redirects = 0\" \"net.ipv4.conf.default.secure_redirects = 0\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.secure_redirects=0\n sysctl -w net.ipv4.conf.default.secure_redirects=0\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled", + "title": "3.3.7 Ensure reverse path filtering is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled_smt", + "name": "statement", + "prose": "Setting `net.ipv4.conf.all.rp_filter` and `net.ipv4.conf.default.rp_filter` to `1` forces the Linux kernel to utilize reverse path filtering on a received packet to determine if the packet was valid. Essentially, with reverse path filtering, if the return packet does not go out the same interface that the corresponding source packet came from, the packet is dropped (and logged if `log_martians` is set)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled_rationale", + "name": "rationale", + "prose": "Setting `net.ipv4.conf.all.rp_filter` and `net.ipv4.conf.default.rp_filter` to `1` is a good way to deter attackers from sending your system bogus packets that cannot be responded to. One instance where this feature breaks down is if asymmetrical routing is employed. This would occur when using dynamic routing protocols (bgp, ospf, etc) on your system. If you are using asymmetrical routing on your system, you will not be able to enable this feature without breaking the routing." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure reverse path filtering is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameters are set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.conf.all.rp_filter` is set to `1`\n\n- `net.ipv4.conf.default.rp_filter` is set to `1`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.rp_filter=1\" \"net.ipv4.conf.default.rp_filter=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameters in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.conf.all.rp_filter = 1`\n\n- `net.ipv4.conf.default.rp_filter = 1`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.conf.all.rp_filter = 1\" \"net.ipv4.conf.default.rp_filter = 1\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.rp_filter=1\n sysctl -w net.ipv4.conf.default.rp_filter=1\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten\n\nImpact:\n\nIf you are using asymmetrical routing on your system, you will not be able to enable this feature without breaking the routing." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted", + "title": "3.3.8 Ensure source routed packets are not accepted", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted_smt", + "name": "statement", + "prose": "In networking, source routing allows a sender to partially or fully specify the route packets take through a network. In contrast, non-source routed packets travel a path determined by routers in the network. In some cases, systems may not be routable or reachable from some locations (e.g. private addresses vs. Internet routable), and so source routed packets would need to be used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted_rationale", + "name": "rationale", + "prose": "Setting `net.ipv4.conf.all.accept_source_route`, `net.ipv4.conf.default.accept_source_route`, `net.ipv6.conf.all.accept_source_route` and `net.ipv6.conf.default.accept_source_route` to `0` disables the system from accepting source routed packets. Assume this system was capable of routing packets to Internet routable addresses on one interface and private addresses on another interface. Assume that the private addresses were not routable to the Internet routable addresses and vice versa. Under normal routing circumstances, an attacker from the Internet routable addresses could not use the system as a way to reach the private address systems. If, however, source routed packets were allowed, they could be used to gain access to the private address systems as the route could be specified, rather than rely on routing protocols that did not allow this routing." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted_obj", + "name": "assessment-objective", + "prose": "Ensure source routed packets are not accepted" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameters are set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.conf.all.accept_source_route` is set to `0`\n\n- `net.ipv4.conf.default.accept_source_route` is set to `0`\n\n- `net.ipv6.conf.all.accept_source_route` is set to `0`\n\n- `net.ipv6.conf.default.accept_source_route` is set to `0`\n\n**Note:**\n\n- kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n- IPv6 kernel parameters only apply to systems where IPv6 is enabled\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.accept_source_route=0\" \"net.ipv4.conf.default.accept_source_route=0\" \"net.ipv6.conf.all.accept_source_route=0\" \"net.ipv6.conf.default.accept_source_route=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameters in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.conf.all.accept_source_route = 0`\n\n- `net.ipv4.conf.default.accept_source_route = 0`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.conf.all.accept_source_route = 0\" \"net.ipv4.conf.default.accept_source_route = 0\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.accept_source_route=0\n sysctl -w net.ipv4.conf.default.accept_source_route=0\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**- IF -** IPv6 is enabled on the system:\n\nSet the following parameters in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv6.conf.all.accept_source_route = 0`\n\n- `net.ipv6.conf.default.accept_source_route = 0`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv6.conf.all.accept_source_route = 0\" \"net.ipv6.conf.default.accept_source_route = 0\" >> /etc/sysctl.d/60-netipv6_sysctl.conf\n```\n\nRun the following command to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv6.conf.all.accept_source_route=0\n sysctl -w net.ipv6.conf.default.accept_source_route=0\n sysctl -w net.ipv6.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged", + "title": "3.3.9 Ensure suspicious packets are logged", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged_smt", + "name": "statement", + "prose": "When enabled, this feature logs packets with un-routable source addresses to the kernel log." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged_rationale", + "name": "rationale", + "prose": "Setting `net.ipv4.conf.all.log_martians` and `net.ipv4.conf.default.log_martians` to `1` enables this feature. Logging these packets allows an administrator to investigate the possibility that an attacker is sending spoofed packets to their system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged_obj", + "name": "assessment-objective", + "prose": "Ensure suspicious packets are logged" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameters are set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.conf.all.log_martians` is set to `1`\n\n- `net.ipv4.conf.default.log_martians` is set to `1`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.conf.all.log_martians=1\" \"net.ipv4.conf.default.log_martians=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameters in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.conf.all.log_martians = 1`\n\n- `net.ipv4.conf.default.log_martians = 1`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.conf.all.log_martians = 1\" \"net.ipv4.conf.default.log_martians = 1\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.conf.all.log_martians=1\n sysctl -w net.ipv4.conf.default.log_martians=1\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled", + "title": "3.3.10 Ensure tcp syn cookies is enabled", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_kernel_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "net.ipv4.tcp_syncookies=1" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled_smt", + "name": "statement", + "prose": "When `tcp_syncookies` is set, the kernel will handle TCP SYN packets normally until the half-open connection queue is full, at which time, the SYN cookie functionality kicks in. SYN cookies work by not using the SYN queue at all. Instead, the kernel simply replies to the SYN with a SYN/ACK, but will include a specially crafted TCP sequence number that encodes the source and destination IP address and port number and the time the packet was sent. A legitimate connection would send the ACK packet of the three way handshake with the specially crafted sequence number. This allows the system to verify that it has received a valid response to a SYN cookie and allow the connection, even though there is no corresponding SYN in the queue." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled_rationale", + "name": "rationale", + "prose": "Attackers use SYN flood attacks to perform a denial of service attacked on a system by sending many SYN packets without completing the three way handshake. This will quickly use up slots in the kernel's half-open connection queue and prevent legitimate connections from succeeding. Setting `net.ipv4.tcp_syncookies` to `1` enables SYN cookies, allowing the system to keep accepting valid connections, even if under a denial of service attack." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure tcp syn cookies is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameter is set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv4.tcp_syncookies` is set to `1`\n\n**Note:** kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv4.tcp_syncookies=1\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameter in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv4.tcp_syncookies = 1`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv4.tcp_syncookies = 1\" >> /etc/sysctl.d/60-netipv4_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv4.tcp_syncookies=1\n sysctl -w net.ipv4.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted", + "title": "3.3.11 Ensure ipv6 router advertisements are not accepted", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted_smt", + "name": "statement", + "prose": "Routers periodically multicast Router Advertisement messages to announce their availability and convey information to neighboring nodes that enable them to be automatically configured on the network.\n\n`net.ipv6.conf.all.accept_ra` and `net.ipv6.conf.default.accept_ra` determine the systems ability to accept these advertisements" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted_rationale", + "name": "rationale", + "prose": "It is recommended that systems do not accept router advertisements as they could be tricked into routing traffic to compromised machines. Setting hard routes within the system (usually a single default route to a trusted router) protects the system from bad routes. Setting `net.ipv6.conf.all.accept_ra` and `net.ipv6.conf.default.accept_ra` to `0` disables the system's ability to accept IPv6 router advertisements." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted_obj", + "name": "assessment-objective", + "prose": "Ensure ipv6 router advertisements are not accepted" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted_obj" + }, + { + "rel": "script", + "href": "#2e8cc4e6-e832-5237-8072-747bc9b921b0" + } + ], + "prose": "Run the following script to verify the following kernel parameters are set in the running configuration and correctly loaded from a kernel parameter configuration file:\n\n- `net.ipv6.conf.all.accept_ra` is set to `0`\n\n- `net.ipv6.conf.default.accept_ra` is set to `0`\n\n**Note:**\n\n- kernel parameters are loaded by file and parameter order precedence. The following script observes this precedence as part of the auditing procedure. The parameters being checked may be set correctly in a file. If that file is superseded, the parameter is overridden by an incorrect setting later in that file, or in a canonically later file, that \"correct\" setting will be ignored both by the script and by the system during a normal kernel parameter load sequence.\n\n- IPv6 kernel parameters only apply to systems where IPv6 is enabled\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ipv6_disabled=\"\"\n a_parlist=(\"net.ipv6.conf.all.accept_ra=0\" \"net.ipv6.conf.default.accept_ra=0\")\n l_ufwscf=\"$([ -f /etc/default/ufw ] && awk -F= '/^\\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)\"\n f_ipv6_chk()\n {\n l_ipv6_disabled=\"no\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_disabled=\"yes\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_disabled=\"yes\"\n fi\n }\n f_kernel_parameter_chk()\n {\n l_running_parameter_value=\"$(sysctl \"$l_parameter_name\" | awk -F= '{print $2}' | xargs)\" # Check running configuration\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_running_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_running_parameter_value\\\"\"\n \" in the running configuration\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_running_parameter_value\\\"\" \\\n \" in the running configuration\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n unset A_out; declare -A A_out # Check durable setting (files)\n while read -r l_out; do\n if [ -n \"$l_out\" ]; then\n if [[ $l_out =~ ^\\s*# ]]; then\n l_file=\"${l_out//# /}\"\n else\n l_kpar=\"$(awk -F= '{print $1}' <<< \"$l_out\" | xargs)\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_file\")\n fi\n fi\n done < <(\"$l_systemdsysctl\" --cat-config | grep -Po '^\\h*([^#\\n\\r]+|#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b)')\n if [ -n \"$l_ufwscf\" ]; then # Account for systems with UFW (Not covered by systemd-sysctl --cat-config)\n l_kpar=\"$(grep -Po \"^\\h*$l_parameter_name\\b\" \"$l_ufwscf\" | xargs)\"\n l_kpar=\"${l_kpar//\\//.}\"\n [ \"$l_kpar\" = \"$l_parameter_name\" ] && A_out+=([\"$l_kpar\"]=\"$l_ufwscf\")\n fi\n if (( ${#A_out[@]} > 0 )); then # Assess output from files and generate output\n while IFS=\"=\" read -r l_fkpname l_file_parameter_value; do\n l_fkpname=\"${l_fkpname// /}\"; l_file_parameter_value=\"${l_file_parameter_value// /}\"\n if grep -Pq -- '\\b'\"$l_parameter_value\"'\\b' <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - \\\"$l_parameter_name\\\" is correctly set to \\\"$l_file_parameter_value\\\"\" \\\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is incorrectly set to \\\"$l_file_parameter_value\\\"\"\n \" in \\\"$(printf '%s' \"${A_out[@]}\")\\\"\" \\\n \" and should have a value of: \\\"$l_value_out\\\"\")\n fi\n done < <(grep -Po -- \"^\\h*$l_parameter_name\\h*=\\h*\\H+\" \"${A_out[@]}\")\n else\n a_output2+=(\" - \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" ** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure **\")\n fi\n }\n l_systemdsysctl=\"$(readlink -f /lib/systemd/systemd-sysctl)\"\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n if grep -q '^net.ipv6.' <<< \"$l_parameter_name\"; then\n [ -z \"$l_ipv6_disabled\" ] && f_ipv6_chk\n if [ \"$l_ipv6_disabled\" = \"yes\" ]; then\n a_output+=(\" - IPv6 is disabled on the system, \\\"$l_parameter_name\\\" is not applicable\")\n else\n f_kernel_parameter_chk\n fi\n else\n f_kernel_parameter_chk\n fi\n done < <(printf '%s\\n' \"${a_parlist[@]}\")\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** IPv6 is enabled on the system:\n\nSet the following parameters in `/etc/sysctl.conf` or a file in `/etc/sysctl.d/` ending in `.conf`:\n\n- `net.ipv6.conf.all.accept_ra = 0`\n\n- `net.ipv6.conf.default.accept_ra = 0`\n\n*Example:*\n\n```\n# printf '%s\\n' \"net.ipv6.conf.all.accept_ra = 0\" \"net.ipv6.conf.default.accept_ra = 0\" >> /etc/sysctl.d/60-netipv6_sysctl.conf\n```\n\nRun the following script to set the active kernel parameters:\n\n```bash\n#!/usr/bin/env bash\n\n{\n sysctl -w net.ipv6.conf.all.accept_ra=0\n sysctl -w net.ipv6.conf.default.accept_ra=0\n sysctl -w net.ipv6.route.flush=1\n}\n```\n\n**Note:** If these settings appear in a canonically later file, or later in the same file, these settings will be overwritten" + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_4_Host_Based_Firewall", + "title": "Host Based Firewall", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_4.1_Configure_a_single_firewall_utility", + "title": "Configure a single firewall utility", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use", + "title": "4.1.1 Ensure a single firewall configuration utility is in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use_smt", + "name": "statement", + "prose": "In Linux security, employing a single, effective firewall configuration utility ensures that only legitimate traffic gets processed, reducing the system’s exposure to potential threats. The choice between `ufw`, `nftables`, and `iptables` depends on organizational needs.\n\n**Note:** `iptables` is being phased out, and support for `iptables` will be reduced over time. It is recommended to transition towards either `nftables` or `ufw` as the default firewall management tool." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use_rationale", + "name": "rationale", + "prose": "Proper configuration of a single firewall utility minimizes cyber threats and protects services and data, while avoiding vulnerabilities like open ports or exposed services. Standardizing on a single tool simplifies management, reduces errors, and fortifies security across Linux systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure a single firewall configuration utility is in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use_obj" + }, + { + "rel": "script", + "href": "#59138dc1-7e43-501a-ad77-9ed031fe40aa" + } + ], + "prose": "Run the following script to verify that a single firewall utility is in use on the system:\n\n```bash\n#!/usr/bin/env bash\n\n{\n active_firewall=() firewalls=(\"ufw\" \"nftables\" \"iptables\")\n # Determine which firewall is in use\n for firewall in \"${firewalls[@]}\"; do\n case $firewall in\n nftables)\n cmd=\"nft\" ;;\n *)\n cmd=$firewall ;;\n esac\n if command -v $cmd &> /dev/null && systemctl is-enabled --quiet $firewall && systemctl is-active --quiet $firewall; then\n active_firewall+=(\"$firewall\")\n fi\n done\n # Display audit results\n if [ ${#active_firewall[@]} -eq 1 ]; then\n printf '%s\\n' \"\" \"Audit Results:\" \" ** PASS **\" \" - A single firewall is in use follow the recommendation in ${active_firewall[0]} subsection ONLY\"\n elif [ ${#active_firewall[@]} -eq 0 ]; then\n printf '%s\\n' \"\" \" Audit Results:\" \" ** FAIL **\" \"- No firewall in use or unable to determine firewall status\"\n else\n printf '%s\\n' \"\" \" Audit Results:\" \" ** FAIL **\" \" - Multiple firewalls are in use: ${active_firewall[*]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Remediating to a single firewall configuration is a complex process and involves several steps. The following provides the basic steps to follow for a single firewall configuration:\n\n-\nDetermine which firewall utility best fits organizational needs\n\n-\nFollow the recommendations in the subsequent subsection for the single firewall to be used\n\n**Note:** Review the firewall subsection overview for the selected firewall to be used, it contains a script to\nsimplify this process.\n\n-\nReturn to this recommendation to ensure a single firewall configuration utility is in use\n\nImpact:\n\nThe use of more than one firewall utility may produce unexpected results." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_4.2_Configure_UncomplicatedFirewall", + "title": "Configure UncomplicatedFirewall", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed", + "title": "4.2.1 Ensure ufw is installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed_smt", + "name": "statement", + "prose": "The Uncomplicated Firewall (ufw) is a frontend for iptables and is particularly well-suited for host-based firewalls. ufw provides a framework for managing netfilter, as well as a command-line interface for manipulating the firewall" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed_rationale", + "name": "rationale", + "prose": "A firewall utility is required to configure the Linux kernel's netfilter framework via the iptables or nftables back-end.\n\nThe Linux kernel's netfilter framework host-based firewall can protect against threats originating from within a corporate network to include malicious mobile code and poorly configured software on a host.\n\n**Note:** Only one firewall utility should be installed and configured. `UFW` is dependent on the iptables package" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure ufw is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed_obj" + }, + { + "rel": "script", + "href": "#cbb382ff-7f3d-5d6d-baeb-e04e2e9a3d0f" + } + ], + "prose": "Run the following command to verify that Uncomplicated Firewall (UFW) is installed:\n\n```\n# dpkg-query -s ufw &>/dev/null && echo \"ufw is installed\"\n\nufw is installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to install Uncomplicated Firewall (UFW):\n\n```\n# apt install ufw\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw", + "title": "4.2.2 Ensure iptables-persistent is not installed with ufw", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw_smt", + "name": "statement", + "prose": "The `iptables-persistent` is a boot-time loader for netfilter rules, iptables plugin" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw_rationale", + "name": "rationale", + "prose": "Running both `ufw` and the services included in the iptables-persistent package may lead to conflict" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw_obj", + "name": "assessment-objective", + "prose": "Ensure iptables-persistent is not installed with ufw" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw_obj" + }, + { + "rel": "script", + "href": "#cbb382ff-7f3d-5d6d-baeb-e04e2e9a3d0f" + } + ], + "prose": "Run the following command to verify that the `iptables-persistent` package is not installed:\n\n```\n# dpkg-query -s iptables-persistent &>/dev/null && echo \"iptables-persistent is installed\"\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to remove the `iptables-persistent` package:\n\n```\n# apt purge iptables-persistent\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled", + "title": "4.2.3 Ensure ufw service is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled_smt", + "name": "statement", + "prose": "UncomplicatedFirewall (ufw) is a frontend for iptables. ufw provides a framework for managing netfilter, as well as a command-line and available graphical user interface for manipulating the firewall.\n\n**Note:**\n\n- When running ufw enable or starting ufw via its initscript, ufw will flush its chains. This is required so ufw can maintain a consistent state, but it may drop existing connections (eg ssh). ufw does support adding rules before enabling the firewall.\n\n- Run the following command before running `ufw enable`.\n\n```\n# ufw allow proto tcp from any to any port 22\n```\n\n- The rules will still be flushed, but the ssh port will be open after enabling the firewall. Please note that once ufw is 'enabled', ufw will not flush the chains when adding or removing rules (but will when modifying a rule or changing the default policy)\n\n- By default, ufw will prompt when enabling the firewall while running under ssh. This can be disabled by using `ufw --force enable`" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled_rationale", + "name": "rationale", + "prose": "The ufw service must be enabled and running in order for ufw to protect the system" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure ufw service is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled_obj" + }, + { + "rel": "script", + "href": "#cbb382ff-7f3d-5d6d-baeb-e04e2e9a3d0f" + }, + { + "rel": "script", + "href": "#3cabd680-cf22-51ac-8f50-287b791fba0e" + } + ], + "prose": "Run the following command to verify that the `ufw` daemon is enabled:\n\n```\n# systemctl is-enabled ufw.service\n\nenabled\n```\n\nRun the following command to verify that the `ufw` daemon is active:\n\n```\n# systemctl is-active ufw\n\nactive\n```\n\nRun the following command to verify ufw is active\n\n```\n# ufw status\n\nStatus: active\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to unmask the `ufw` daemon:\n\n```\n# systemctl unmask ufw.service\n```\n\nRun the following command to enable and start the `ufw` daemon:\n\n```\n# systemctl --now enable ufw.service\n\nactive\n```\n\nRun the following command to enable ufw:\n\n```\n# ufw enable\n```\n\nImpact:\n\nChanging firewall settings while connected over network can result in being locked out of the system." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured", + "title": "4.2.4 Ensure ufw loopback traffic is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured_smt", + "name": "statement", + "prose": "Configure the loopback interface to accept traffic. Configure all other interfaces to deny traffic to the loopback network (127.0.0.0/8 for IPv4 and ::1/128 for IPv6)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured_rationale", + "name": "rationale", + "prose": "Loopback traffic is generated between processes on machine and is typically critical to operation of the system. The loopback interface is the only place that loopback network (127.0.0.0/8 for IPv4 and ::1/128 for IPv6) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure ufw loopback traffic is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured_obj" + }, + { + "rel": "script", + "href": "#a1587053-8ee8-519f-a5fa-90a621907ce1" + }, + { + "rel": "script", + "href": "#cbb382ff-7f3d-5d6d-baeb-e04e2e9a3d0f" + }, + { + "rel": "script", + "href": "#d5717121-c357-535f-9766-d54b266aed20" + } + ], + "prose": "Run the following command and verify loopback interface to accept traffic:\n\n```\n# grep -P -- 'lo|127.0.0.0' /etc/ufw/before.rules\n```\n\nOutput includes:\n\n```\n# allow all on loopback\n-A ufw-before-input -i lo -j ACCEPT\n-A ufw-before-output -o lo -j ACCEPT\n```\n\nRun the following command and verify all other interfaces deny traffic to the loopback network (127.0.0.0/8 for IPv4 and ::1/128 for IPv6)\n\n```\n# ufw status verbose\n\nTo Action From\n-- ------ ----\nAnywhere DENY IN 127.0.0.0/8\nAnywhere (v6) DENY IN ::1\n```\n\n**Note:** `ufw status` only shows rules added with `ufw` and not the rules found in the `/etc/ufw` rules files where allow all on loopback is configured by default." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to configure the loopback interface to accept traffic:\n\n```\n# ufw allow in on lo\n# ufw allow out on lo\n```\n\nRun the following commands to configure all other interfaces to deny traffic to the loopback network:\n\n```\n# ufw deny in from 127.0.0.0/8\n# ufw deny in from ::1\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured", + "title": "4.2.5 Ensure ufw outbound connections are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured_smt", + "name": "statement", + "prose": "Configure the firewall rules for new outbound connections.\n\n**Note:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system.\n\n- Unlike iptables, when a new outbound rule is added, ufw automatically takes care of associated established connections, so no rules for the latter kind are required." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured_rationale", + "name": "rationale", + "prose": "If rules are not in place for new outbound connections all packets will be dropped by the default policy preventing network usage." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure ufw outbound connections are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured_obj" + } + ], + "prose": "Run the following command and verify all rules for new outbound connections match site policy:\n\n```\n# ufw status numbered\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure ufw in accordance with site policy. The following commands will implement a policy to allow all outbound connections on all interfaces:\n\n```\n# ufw allow out on all\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports", + "title": "4.2.6 Ensure ufw firewall rules exist for all open ports", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports_smt", + "name": "statement", + "prose": "Services and ports can be accepted or explicitly rejected.\n\n**Note:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system\n\n- The remediation command opens up the port to traffic from all sources. Consult ufw documentation and set any restrictions in compliance with site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports_rationale", + "name": "rationale", + "prose": "To reduce the attack surface of a system, all services and ports should be blocked unless required.\n\n- Any ports that have been opened on non-loopback addresses need firewall rules to govern traffic.\n\n- Without a firewall rule configured for open ports, the default firewall policy will drop all packets to these ports.\n\n- Required ports should have a firewall rule created to allow approved connections in accordance with local site policy.\n\n- Unapproved ports should have an explicit deny rule created." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports_obj", + "name": "assessment-objective", + "prose": "Ensure ufw firewall rules exist for all open ports" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports_obj" + }, + { + "rel": "script", + "href": "#cbb382ff-7f3d-5d6d-baeb-e04e2e9a3d0f" + }, + { + "rel": "script", + "href": "#231cebf0-c7e6-560c-8766-202efb1ad849" + } + ], + "prose": "Run the following script to verify a firewall rule exists for all open ports:\n\n```bash\n#!/usr/bin/env bash\n\n{\n unset a_ufwout;unset a_openports\n while read -r l_ufwport; do\n [ -n \"$l_ufwport\" ] && a_ufwout+=(\"$l_ufwport\")\n done < <(ufw status verbose | grep -Po '^\\h*\\d+\\b' | sort -u)\n while read -r l_openport; do\n [ -n \"$l_openport\" ] && a_openports+=(\"$l_openport\")\n done < <(ss -tuln | awk '($5!~/%lo:/ && $5!~/127.0.0.1:/ && $5!~/\\[?::1\\]?:/) {split($5, a, \":\"); print a[2]}' | sort -u)\n a_diff=(\"$(printf '%s\\n' \"${a_openports[@]}\" \"${a_ufwout[@]}\" \"${a_ufwout[@]}\" | sort | uniq -u)\")\n if [[ -n \"${a_diff[*]}\" ]]; then\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n- The following port(s) don't have a rule in UFW: $(printf '%s\\n' \\\\n\"${a_diff[*]}\")\\n- End List\"\n else\n echo -e \"\\n - Audit Passed -\\n- All open ports have a rule in UFW\\n\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "For each port identified in the audit which does not have a firewall rule, evaluate the service listening on the port and add a rule for accepting or denying inbound connections in accordance with local site policy:\n\n*Examples:*\n\n```\n# ufw allow in /\n\n# ufw deny in /\n```\n\n**Note:** Examples create rules for from any, to any. More specific rules should be concentered when allowing inbound traffic e.g only traffic from this network.\n\n*Example to allow traffic on port 443 using the tcp protocol from the 192.168.1.0 network:*\n\n```\nufw allow from 192.168.1.0/24 to any proto tcp port 443\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy", + "title": "4.2.7 Ensure ufw default deny firewall policy", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy_smt", + "name": "statement", + "prose": "A default deny policy on connections ensures that any unconfigured network usage will be rejected.\n\n**Note:** Any port or protocol without a explicit allow before the default deny will be blocked" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy_rationale", + "name": "rationale", + "prose": "With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to allow list acceptable usage than to deny list unacceptable usage." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy_obj", + "name": "assessment-objective", + "prose": "Ensure ufw default deny firewall policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy_obj" + }, + { + "rel": "script", + "href": "#cbb382ff-7f3d-5d6d-baeb-e04e2e9a3d0f" + }, + { + "rel": "script", + "href": "#d5717121-c357-535f-9766-d54b266aed20" + } + ], + "prose": "Run the following command and verify that the default policy for **incoming** , **outgoing** , and **routed** directions is **deny** , **reject** , or **disabled**:\n\n```\n# ufw status verbose | grep Default:\n```\n\n*Example output:*\n\n```\nDefault: deny (incoming), deny (outgoing), disabled (routed)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to implement a default *deny* policy:\n\n```\n# ufw default deny incoming\n# ufw default deny outgoing\n# ufw default deny routed\n```\n\nImpact:\n\nAny port and protocol not explicitly allowed will be blocked. The following rules should be considered before applying the default deny.\n\n```\nufw allow out http\nufw allow out https\nufw allow out ntp # Network Time Protocol\nufw allow out to any port 53 # DNS\nufw allow out to any port 853 # DNS over TLS\nufw logging on\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_4.3_Configure_nftables", + "title": "Configure nftables", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed", + "title": "4.3.1 Ensure nftables is installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed_smt", + "name": "statement", + "prose": "nftables provides a new in-kernel packet classification framework that is based on a network-specific Virtual Machine (VM) and a new nft userspace command line tool. nftables reuses the existing Netfilter subsystems such as the existing hook infrastructure, the connection tracking system, NAT, userspace queuing and logging subsystem.\n\n**Notes:**\n\n- nftables is available in Linux kernel 3.13 and newer\n\n- Only one firewall utility should be installed and configured\n\n- Changing firewall settings while connected over the network can result in being locked out of the system" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed_rationale", + "name": "rationale", + "prose": "nftables is a subsystem of the Linux kernel that can protect against threats originating from within a corporate network to include malicious mobile code and poorly configured software on a host." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure nftables is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed_obj" + }, + { + "rel": "script", + "href": "#f3cc5685-0c0f-5c1d-956a-62c6b9201ab2" + } + ], + "prose": "Run the following command to verify that `nftables` is installed:\n\n```\n# dpkg-query -s nftables &>/dev/null && echo \"nftables is installed\"\n\nnftables is installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to install `nftables`:\n\n```\n# apt install nftables\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables", + "title": "4.3.2 Ensure ufw is uninstalled or disabled with nftables", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables_smt", + "name": "statement", + "prose": "Uncomplicated Firewall (UFW) is a program for managing a netfilter firewall designed to be easy to use." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables_rationale", + "name": "rationale", + "prose": "Running both the `nftables` service and `ufw` may lead to conflict and unexpected results." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables_obj", + "name": "assessment-objective", + "prose": "Ensure ufw is uninstalled or disabled with nftables" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables_obj" + }, + { + "rel": "script", + "href": "#f3cc5685-0c0f-5c1d-956a-62c6b9201ab2" + }, + { + "rel": "script", + "href": "#ac7bc4ba-ad76-51ad-a186-141ae169ea70" + } + ], + "prose": "Run the following commands to verify that `ufw` is **either** not installed or inactive. Only one of the following needs to pass.\n\nRun the following command to verify that `ufw` is not installed:\n\n```\n# dpkg-query -s ufw &>/dev/null && echo \"ufw is installed\"\n```\n\nNothing should be returned\n\n**-OR-**\n\nRun the following commands to verify `ufw` is disabled and `ufw.service` is not enabled:\n\n```\n# ufw status\n\nStatus: inactive\n```\n\n```\n# systemctl is-enabled ufw.service\n\nmasked\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run **one** of the following to either remove `ufw` **or** disable `ufw` and mask `ufw.service`:\n\nRun the following command to remove `ufw`:\n\n```\n# apt purge ufw\n```\n\n**-OR-**\n\nRun the following commands to disable `ufw` and mask `ufw.service`:\n\n```\n# ufw disable\n# systemctl stop ufw.service\n# systemctl mask ufw.service\n```\n\n**Note:** `ufw disable` needs to be run before `systemctl mask ufw.service` in order to correctly disable `UFW`" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables", + "title": "4.3.3 Ensure iptables are flushed with nftables", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables_smt", + "name": "statement", + "prose": "nftables is a replacement for iptables, ip6tables, ebtables and arptables" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables_rationale", + "name": "rationale", + "prose": "It is possible to mix iptables and nftables. However, this increases complexity and also the chance to introduce errors. For simplicity flush out all iptables rules, and ensure it is not loaded" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables_obj", + "name": "assessment-objective", + "prose": "Ensure iptables are flushed with nftables" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables_obj" + } + ], + "prose": "Run the following commands to ensure no iptables rules exist\n\nFor iptables:\n\n```\n# iptables -L\n```\n\nNo rules should be returned\n\nFor ip6tables:\n\n```\n# ip6tables -L\n```\n\nNo rules should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to flush iptables:\n\nFor iptables:\n\n```\n# iptables -F\n```\n\nFor ip6tables:\n\n```\n# ip6tables -F\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists", + "title": "4.3.4 Ensure a nftables table exists", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nft_tables.sh as XCCDF_VALUE_REGEX", + "values": [ + "^table\\s+\\S+\\s+\\S+" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists_smt", + "name": "statement", + "prose": "Tables hold chains. Each table only has one address family and only applies to packets of this family. Tables can have one of five families." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists_rationale", + "name": "rationale", + "prose": "nftables doesn't have any default tables. Without a table being built, nftables will not filter network traffic." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists_obj", + "name": "assessment-objective", + "prose": "Ensure a nftables table exists" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists_obj" + }, + { + "rel": "script", + "href": "#f3cc5685-0c0f-5c1d-956a-62c6b9201ab2" + }, + { + "rel": "script", + "href": "#4f790ecf-e162-54ca-8796-5676a1223901" + } + ], + "prose": "Run the following command to verify that a nftables table exists:\n\n```\n# nft list tables\n```\n\nReturn should include a list of nftables:\n\n*Example:*\n\n```\ntable inet filter\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to create a table in nftables\n\n```\n# nft create table inet \n```\n\n*Example:*\n\n```\n# nft create table inet filter\n```\n\nImpact:\n\nAdding rules to a running nftables can cause loss of connectivity to the system" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist", + "title": "4.3.5 Ensure nftables base chains exist", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist_smt", + "name": "statement", + "prose": "Chains are containers for rules. They exist in two kinds, base chains and regular chains. A base chain is an entry point for packets from the networking stack, a regular chain may be used as jump target and is used for better rule organization." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist_rationale", + "name": "rationale", + "prose": "If a base chain doesn't exist with a hook for input, forward, and delete, packets that would flow through those chains will not be touched by nftables." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist_obj", + "name": "assessment-objective", + "prose": "Ensure nftables base chains exist" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist_obj" + }, + { + "rel": "script", + "href": "#f3cc5685-0c0f-5c1d-956a-62c6b9201ab2" + }, + { + "rel": "script", + "href": "#a43ed1b1-a76a-5e9d-ae1f-22b31f714fc0" + } + ], + "prose": "Run the following commands and verify that base chains exist for `INPUT`.\n\n```\n# nft list ruleset | grep 'hook input'\n\ntype filter hook input priority 0;\n```\n\nRun the following commands and verify that base chains exist for `FORWARD`.\n\n```\n# nft list ruleset | grep 'hook forward'\n\ntype filter hook forward priority 0;\n```\n\nRun the following commands and verify that base chains exist for `OUTPUT`.\n\n```\n# nft list ruleset | grep 'hook output'\n\ntype filter hook output priority 0;\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to create the base chains:\n\n```\n# nft create chain inet
    { type filter hook <(input|forward|output)> priority 0 \\; }\n```\n\n*Example:*\n\n```\n# nft create chain inet filter input { type filter hook input priority 0 \\; }\n\n# nft create chain inet filter forward { type filter hook forward priority 0 \\; }\n\n# nft create chain inet filter output { type filter hook output priority 0 \\; }\n```\n\nImpact:\n\nIf configuring nftables over ssh, `creating` a `base chain` with a policy of `drop` will cause loss of connectivity.\n\nEnsure that a rule allowing ssh has been added to the base chain prior to setting the base chain's policy to drop" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured", + "title": "4.3.6 Ensure nftables loopback traffic is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured_smt", + "name": "statement", + "prose": "Configure the loopback interface to accept traffic. Configure all other interfaces to deny traffic to the loopback network" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured_rationale", + "name": "rationale", + "prose": "Loopback traffic is generated between processes on machine and is typically critical to the operation of the system. The loopback interface is the only place that loopback network traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure nftables loopback traffic is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured_obj" + }, + { + "rel": "script", + "href": "#f3cc5685-0c0f-5c1d-956a-62c6b9201ab2" + }, + { + "rel": "script", + "href": "#3017a433-7b16-5895-8da4-830e2c0e9700" + } + ], + "prose": "Run the following commands to verify that the loopback interface is configured:\n\nRun the following command to verify the loopback interface is configured to accept network traffic:\n\n```\n# nft list ruleset | awk '/hook input/,/}/' | grep 'iif \"lo\" accept'\n```\n\n*Example output:*\n\n```\niif \"lo\" accept\n```\n\nRun the following command to verify network traffic from an iPv4 loopback interface is configured to drop:\n\n```\n# nft list ruleset | awk '/hook input/,/}/' | grep 'ip saddr'\n```\n\n*Example output:*\n\n```\nip saddr 127.0.0.0/8 counter packets 0 bytes 0 drop\n```\n\n**- IF -** IPv6 is enabled on the system:\n\nRun the following command to verify network traffic from an iPv6 loopback interface is configured to drop:\n\n```\n# nft list ruleset | awk '/hook input/,/}/' | grep 'ip6 saddr'\n```\n\n*Example output:*\n\n```\nip6 saddr ::1 counter packets 0 bytes 0 drop\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to implement the loopback rules:\n\n```\n# nft add rule inet filter input iif lo accept\n```\n\n```\n# nft add rule inet filter input ip saddr 127.0.0.0/8 counter drop\n```\n\n**- IF -** IPv6 is enabled on the system:\n\nRun the following command to implement the IPv6 loopback rule:\n\n```\n# nft add rule inet filter input ip6 saddr ::1 counter drop\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured", + "title": "4.3.7 Ensure nftables outbound and established connections are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured_smt", + "name": "statement", + "prose": "Configure the firewall rules for new outbound, and established connections" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured_rationale", + "name": "rationale", + "prose": "If rules are not in place for new outbound, and established connections all packets will be dropped by the default policy preventing network usage." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure nftables outbound and established connections are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured_obj" + } + ], + "prose": "Run the following commands and verify all rules for established incoming connections match site policy: site policy:\n\n```\n# nft list ruleset | awk '/hook input/,/}/' | grep -E 'ip protocol (tcp|udp) ct state'\n```\n\nOutput should be similar to:\n\n```\nip protocol tcp ct state established accept\nip protocol udp ct state established accept\n```\n\nRun the folllowing command and verify all rules for new and established outbound connections match site policy\n\n```\n# nft list ruleset | awk '/hook output/,/}/' | grep -E 'ip protocol (tcp|udp) ct state'\n```\n\nOutput should be similar to:\n\n```\nip protocol tcp ct state established,related,new accept\nip protocol udp ct state established,related,new accept\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure nftables in accordance with site policy. The following commands will implement a policy to allow all outbound connections and all established connections:\n\n```\n# nft add rule inet filter input ip protocol tcp ct state established accept\n\n# nft add rule inet filter input ip protocol udp ct state established accept\n\n# nft add rule inet filter output ip protocol tcp ct state new,related,established accept\n\n# nft add rule inet filter output ip protocol udp ct state new,related,established accept\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy", + "title": "4.3.8 Ensure nftables default deny firewall policy", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy_smt", + "name": "statement", + "prose": "Base chain policy is the default verdict that will be applied to packets reaching the end of the chain." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy_rationale", + "name": "rationale", + "prose": "There are two policies: accept (Default) and drop. If the policy is set to `accept`, the firewall will accept any packet that is not configured to be denied and the packet will continue transversing the network stack.\n\nIt is easier to allow list acceptable usage than to deny list unacceptable usage.\n\n**Note:**\n\n- Allow port 22(ssh) needs to be updated to only allow systems requiring ssh connectivity to connect, as per site policy.\n\n- Changing firewall settings while connected over network can result in being locked out of the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy_obj", + "name": "assessment-objective", + "prose": "Ensure nftables default deny firewall policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy_obj" + }, + { + "rel": "script", + "href": "#f3cc5685-0c0f-5c1d-956a-62c6b9201ab2" + }, + { + "rel": "script", + "href": "#961d523c-1913-5b74-8444-fd2ecd8a1a27" + } + ], + "prose": "Run the following commands and verify that base chains contain a policy of `DROP`.\n\n```\n# nft list ruleset | grep 'hook input'\n\ntype filter hook input priority 0; policy drop;\n```\n\n```\n# nft list ruleset | grep 'hook forward'\n\ntype filter hook forward priority 0; policy drop;\n```\n\n```\n# nft list ruleset | grep 'hook output'\n\ntype filter hook output priority 0; policy drop;\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command for the base chains with the input, forward, and output hooks to implement a default DROP policy:\n\n```\n# nft chain
    { policy drop \\; }\n```\n\n*Example:*\n\n```\n# nft chain inet filter input { policy drop \\; }\n\n# nft chain inet filter forward { policy drop \\; }\n\n# nft chain inet filter output { policy drop \\; }\n```\n\nImpact:\n\nIf configuring nftables over ssh, creating a base chain with a policy of drop will cause loss of connectivity.\n\nEnsure that a rule allowing ssh has been added to the base chain prior to setting the base chain's policy to drop" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled", + "title": "4.3.9 Ensure nftables service is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled_smt", + "name": "statement", + "prose": "The nftables service allows for the loading of nftables rulesets during boot, or starting on the nftables service" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled_rationale", + "name": "rationale", + "prose": "The nftables service restores the nftables rules from the rules files referenced in the `/etc/nftables.conf` file during boot or the starting of the nftables service" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure nftables service is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled_obj" + }, + { + "rel": "script", + "href": "#f3cc5685-0c0f-5c1d-956a-62c6b9201ab2" + } + ], + "prose": "Run the following command and verify that the nftables service is enabled:\n\n```\n# systemctl is-enabled nftables\n\nenabled\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to enable the nftables service:\n\n```\n# systemctl enable nftables\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent", + "title": "4.3.10 Ensure nftables rules are permanent", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent_smt", + "name": "statement", + "prose": "nftables is a subsystem of the Linux kernel providing filtering and classification of network packets/datagrams/frames.\n\nThe nftables service reads the `/etc/nftables.conf` file for a nftables file or files to include in the nftables ruleset.\n\nA nftables ruleset containing the input, forward, and output base chains allow network traffic to be filtered.\n\n**Note:** Saving the script and following the instruction in the Configure nftables section overview will implement the rules in the configure nftable section, open port 22(ssh) from anywhere, and applies nftables ruleset on boot." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent_rationale", + "name": "rationale", + "prose": "Changes made to nftables ruleset only affect the live system, you will also need to configure the nftables ruleset to apply on boot" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent_obj", + "name": "assessment-objective", + "prose": "Ensure nftables rules are permanent" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent_obj" + }, + { + "rel": "script", + "href": "#f3cc5685-0c0f-5c1d-956a-62c6b9201ab2" + } + ], + "prose": "Run the following commands to verify that input, forward, and output base chains are configured to be applied to a nftables ruleset on boot:\n\nRun the following command to verify the input base chain:\n\n```\n# [ -n \"$(grep -E '^\\s*include' /etc/nftables.conf)\" ] && awk '/hook input/,/}/' $(awk '$1 ~ /^\\s*include/ { gsub(\"\\\"\",\"\",$2);print $2 }' /etc/nftables.conf)\n```\n\nOutput should be similar to:\n\n```\n type filter hook input priority 0; policy drop;\n\n # Ensure loopback traffic is configured\n iif \"lo\" accept\n ip saddr 127.0.0.0/8 counter packets 0 bytes 0 drop\n ip6 saddr ::1 counter packets 0 bytes 0 drop\n\n # Ensure established connections are configured\n ip protocol tcp ct state established accept\n ip protocol udp ct state established accept\n\n # Accept port 22(SSH) traffic from anywhere\n tcp dport ssh accept\n```\n\nReview the input base chain to ensure that it follows local site policy\n\nRun the following command to verify the forward base chain:\n\n```\n# [ -n \"$(grep -E '^\\s*include' /etc/nftables.conf)\" ] && awk '/hook forward/,/}/' $(awk '$1 ~ /^\\s*include/ { gsub(\"\\\"\",\"\",$2);print $2 }' /etc/nftables.conf)\n```\n\nOutput should be similar to:\n\n```\n # Base chain for hook forward named forward (Filters forwarded network packets)\n chain forward {\n type filter hook forward priority 0; policy drop;\n }\n```\n\nReview the forward base chain to ensure that it follows local site policy.\n\nRun the following command to verify the forward base chain:\n\n```\n# [ -n \"$(grep -E '^\\s*include' /etc/nftables.conf)\" ] && awk '/hook output/,/}/' $(awk '$1 ~ /^\\s*include/ { gsub(\"\\\"\",\"\",$2);print $2 }' /etc/nftables.conf)\n```\n\nOutput should be similar to:\n\n```\n # Base chain for hook output named output (Filters outbound network packets)\n chain output {\n type filter hook output priority 0; policy drop;\n # Ensure outbound and established connections are configured\n ip protocol tcp ct state established,related,new accept\n ip protocol udp ct state established,related,new accept\n\n }\n```\n\nReview the output base chain to ensure that it follows local site policy." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/nftables.conf` file and un-comment or add a line with `include ` for each nftables file you want included in the nftables ruleset on boot\n\n*Example:*\n\n```\n# vi /etc/nftables.conf\n```\n\nAdd the line:\n\n```\ninclude \"/etc/nftables.rules\"\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_4.4_Configure_iptables", + "title": "Configure iptables", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_4.4.1_Configure_iptables_software", + "title": "Configure iptables software", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed", + "title": "4.4.1.1 Ensure iptables packages are installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed_smt", + "name": "statement", + "prose": "`iptables` is a utility program that allows a system administrator to configure the tables provided by the Linux kernel firewall, implemented as different Netfilter modules, and the chains and rules it stores. Different kernel modules and programs are used for different protocols; `iptables` applies to IPv4, ip6tables to IPv6, arptables to ARP, and ebtables to Ethernet frames." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed_rationale", + "name": "rationale", + "prose": "A method of configuring and maintaining firewall rules is necessary to configure a Host Based Firewall." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed_obj", + "name": "assessment-objective", + "prose": "Ensure iptables packages are installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed_obj" + }, + { + "rel": "script", + "href": "#80cb14a1-10b1-5f05-896a-d9de8c0264f6" + } + ], + "prose": "Run the following command to verify that `iptables` is installed:\n\n```\n# dpkg-query -s iptables &>/dev/null && echo \"iptables is installed\"\n\niptables is installed\n```\n\nRun the following command to verify that `iptables-persistent` is installed:\n\n```\n# dpkg-query -s iptables-persistent &>/dev/null && echo \"iptables-persistent is installed\"\n\niptables-persistent is installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to install `iptables` and `iptables-persistent`\n\n```\n# apt install iptables iptables-persistent\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables", + "title": "4.4.1.2 Ensure nftables is not in use with iptables", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables_smt", + "name": "statement", + "prose": "`nftables` is a subsystem of the Linux kernel providing filtering and classification of network packets/datagrams/frames and is the successor to iptables." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables_rationale", + "name": "rationale", + "prose": "Running both `iptables` and `nftables` may lead to conflict." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables_obj", + "name": "assessment-objective", + "prose": "Ensure nftables is not in use with iptables" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables_obj" + }, + { + "rel": "script", + "href": "#80cb14a1-10b1-5f05-896a-d9de8c0264f6" + } + ], + "prose": "Run the following commend to verify that `nftables` is not installed:\n\n```\n# dpkg-query -s nftables &>/dev/null && echo \"nftables is installed\"\n```\n\nNothing should be returned\n\n**- OR -**\n\nRun the following command to verify `nftables.service` is not enabled:\n\n```\n# systemctl is-enabled nftables.service 2>/dev/null | grep '^enabled'\n```\n\nNothing should be returned\n\nRun the following command to verify `nftables.service` is not active:\n\n```\n# systemctl is-active nftables.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to remove `nftables`:\n\n```\n# apt purge nftables\n```\n\n**- OR -**\n\nRun the following commands to stop and mask `nftables.service`:\n\n```\n# systemctl stop nftables.service\n# systemctl mask nftables.service\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables", + "title": "4.4.1.3 Ensure ufw is not in use with iptables", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables_smt", + "name": "statement", + "prose": "Uncomplicated Firewall (UFW) is a program for managing a netfilter firewall designed to be easy to use.\n\n- Uses a command-line interface consisting of a small number of simple commands\n\n- Uses iptables for configuration" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables_rationale", + "name": "rationale", + "prose": "Running `iptables.persistent` with `ufw` enabled may lead to conflict and unexpected results." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables_obj", + "name": "assessment-objective", + "prose": "Ensure ufw is not in use with iptables" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables_obj" + }, + { + "rel": "script", + "href": "#80cb14a1-10b1-5f05-896a-d9de8c0264f6" + }, + { + "rel": "script", + "href": "#ac7bc4ba-ad76-51ad-a186-141ae169ea70" + } + ], + "prose": "Run the following commands to verify that `ufw` is **either** not installed or disabled. **Only one of the following needs to pass**.\n\nRun the following command to verify that `ufw` is not installed:\n\n```\n# dpkg-query -s ufw &>/dev/null && echo \"ufw is installed\"\n```\n\nNothing should be returned.\n\n**- OR -**\n\nRun the following command to verify ufw is disabled:\n\n```\n# ufw status\n\nStatus: inactive\n```\n\nRun the following commands to verify that the `ufw.service` is not enabled:\n\n```\n# systemctl is-enabled ufw 2>dev/null | grep '^enabled'\n```\n\nNothing should be returned\n\nRun the following command to verify `ufw.service` is not active:\n\n```\n# systemctl is-active ufw.service 2>/dev/null | grep '^active'\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to remove `ufw`:\n\n```\n# apt purge ufw\n```\n\n**- OR -**\n\nRun the following commands to disable ufw, and stop and mask `ufw.service`:\n\n```\n# ufw disable\n# systemctl stop ufw.service\n# systemctl mask ufw.service\n```\n\n**Note:** `ufw disable` needs to be run before `systemctl mask ufw.service` in order to correctly disable `UFW`" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_4.4.2_Configure_IPv4_iptables", + "title": "Configure IPv4 iptables", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy", + "title": "4.4.2.1 Ensure iptables default deny firewall policy", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy_smt", + "name": "statement", + "prose": "A default deny all policy on connections ensures that any unconfigured network usage will be rejected.\n\n**Notes:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system\n\n- Remediation will only affect the active system firewall, be sure to configure the default policy in your firewall management to apply on boot as well" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy_rationale", + "name": "rationale", + "prose": "With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to allow list acceptable usage than to deny list unacceptable usage." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy_obj", + "name": "assessment-objective", + "prose": "Ensure iptables default deny firewall policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy_obj" + }, + { + "rel": "script", + "href": "#80cb14a1-10b1-5f05-896a-d9de8c0264f6" + }, + { + "rel": "script", + "href": "#0f5a5341-15bb-5e72-afb4-f5f30d078f90" + } + ], + "prose": "Run the following command and verify that the policy for the `INPUT` , `OUTPUT` , and `FORWARD` chains is `DROP` or `REJECT` :\n\n```\n# iptables -L\nChain INPUT (policy DROP)\nChain FORWARD (policy DROP)\nChain OUTPUT (policy DROP)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to implement a default DROP policy:\n\n```\n# iptables -P INPUT DROP\n# iptables -P OUTPUT DROP\n# iptables -P FORWARD DROP\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured", + "title": "4.4.2.2 Ensure iptables loopback traffic is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured_smt", + "name": "statement", + "prose": "Configure the loopback interface to accept traffic. Configure all other interfaces to deny traffic to the loopback network (127.0.0.0/8).\n\n**Note:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system\n\n- Remediation will only affect the active system firewall, be sure to configure the default policy in your firewall management to apply on boot as well" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured_rationale", + "name": "rationale", + "prose": "Loopback traffic is generated between processes on machine and is typically critical to the operation of the system. The loopback interface is the only place that loopback network (127.0.0.0/8) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure iptables loopback traffic is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured_obj" + }, + { + "rel": "script", + "href": "#80cb14a1-10b1-5f05-896a-d9de8c0264f6" + }, + { + "rel": "script", + "href": "#5cf2a45e-b702-50b3-bac8-cd40feac3a2f" + }, + { + "rel": "script", + "href": "#a547fb1c-fae3-5b3a-9a83-e8cfddd2799f" + } + ], + "prose": "Run the following commands and verify output includes the listed rules in order (`pkts` and `bytes` counts may differ, `prot` may be `all` or `0`):\n\n```\n# iptables -L INPUT -v -n\nChain INPUT (policy DROP 0 packets, 0 bytes)\n pkts bytes target prot opt in out source destination\n 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0\n 0 0 DROP all -- * * 127.0.0.0/8 0.0.0.0/0\n\n # iptables -L OUTPUT -v -n\nChain OUTPUT (policy DROP 0 packets, 0 bytes)\n pkts bytes target prot opt in out source destination\n 0 0 ACCEPT all -- * lo 0.0.0.0/0 0.0.0.0/0\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to implement the loopback rules:\n\n```\n# iptables -A INPUT -i lo -j ACCEPT\n# iptables -A OUTPUT -o lo -j ACCEPT\n# iptables -A INPUT -s 127.0.0.0/8 -j DROP\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured", + "title": "4.4.2.3 Ensure iptables outbound and established connections are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured_smt", + "name": "statement", + "prose": "Configure the firewall rules for new outbound, and established connections.\n\n**Note:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system\n\n- Remediation will only affect the active system firewall, be sure to configure the default policy in your firewall management to apply on boot as well" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured_rationale", + "name": "rationale", + "prose": "If rules are not in place for new outbound, and established connections all packets will be dropped by the default policy preventing network usage." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure iptables outbound and established connections are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured_obj" + } + ], + "prose": "Run the following command and verify all rules for new outbound, and established connections match site policy:\n\n```\n# iptables -L -v -n\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure iptables in accordance with site policy. The following commands will implement a policy to allow all outbound connections and all established connections:\n\n```\n# iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -j ACCEPT\n# iptables -A OUTPUT -p udp -m state --state NEW,ESTABLISHED -j ACCEPT\n# iptables -A INPUT -p tcp -m state --state ESTABLISHED -j ACCEPT\n# iptables -A INPUT -p udp -m state --state ESTABLISHED -j ACCEPT\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports", + "title": "4.4.2.4 Ensure iptables firewall rules exist for all open ports", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports_smt", + "name": "statement", + "prose": "Any ports that have been opened on non-loopback addresses need firewall rules to govern traffic.\n\n**Notes:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system\n\n- Remediation will only affect the active system firewall, be sure to configure the default policy in your firewall management to apply on boot as well\n\n- The remediation command opens up the port to traffic from all sources. Consult iptables documentation and set any restrictions in compliance with site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports_rationale", + "name": "rationale", + "prose": "Without a firewall rule configured for open ports default firewall policy will drop all packets to these ports." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports_obj", + "name": "assessment-objective", + "prose": "Ensure iptables firewall rules exist for all open ports" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports_obj" + }, + { + "rel": "script", + "href": "#80cb14a1-10b1-5f05-896a-d9de8c0264f6" + }, + { + "rel": "script", + "href": "#5a54c70b-4dab-5cb3-9ab7-e0ffad1a76bc" + } + ], + "prose": "Run the following command to determine open ports:\n\n```\n# ss -4tuln\n\nNetid State Recv-Q Send-Q Local Address:Port Peer Address:Port\nudp UNCONN 0 0 *:68 *:*\nudp UNCONN 0 0 *:123 *:*\ntcp LISTEN 0 128 *:22 *:*\n```\n\nRun the following command to determine firewall rules:\n\n```\n# iptables -L INPUT -v -n\nChain INPUT (policy DROP 0 packets, 0 bytes)\n pkts bytes target prot opt in out source destination\n 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0\n 0 0 DROP all -- * * 127.0.0.0/8 0.0.0.0/0\n 0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 state NEW\n```\n\nVerify all open ports listening on non-localhost addresses have at least one firewall rule.\n\nThe last line identified by the `tcp dpt:22 state NEW` identifies it as a firewall rule for new connections on tcp port 22." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "For each port identified in the audit which does not have a firewall rule establish a proper rule for accepting inbound connections:\n\n```\n# iptables -A INPUT -p --dport -m state --state NEW -j ACCEPT\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_4.4.3_Configure_IPv6__ip6tables", + "title": "Configure IPv6 ip6tables", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy", + "title": "4.4.3.1 Ensure ip6tables default deny firewall policy", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy_smt", + "name": "statement", + "prose": "A default deny all policy on connections ensures that any unconfigured network usage will be rejected.\n\n**Note:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system\n\n- Remediation will only affect the active system firewall, be sure to configure the default policy in your firewall management to apply on boot as well" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy_rationale", + "name": "rationale", + "prose": "With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to allow list acceptable usage than to deny list unacceptable usage." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy_obj", + "name": "assessment-objective", + "prose": "Ensure ip6tables default deny firewall policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy_obj" + }, + { + "rel": "script", + "href": "#80cb14a1-10b1-5f05-896a-d9de8c0264f6" + }, + { + "rel": "script", + "href": "#ddfb5558-71c5-5ed4-9f77-3d23499e5934" + }, + { + "rel": "script", + "href": "#a1587053-8ee8-519f-a5fa-90a621907ce1" + } + ], + "prose": "Run the following command and verify that the policy for the INPUT, OUTPUT, and FORWARD chains is DROP or REJECT:\n\n```\n# ip6tables -L\nChain INPUT (policy DROP)\nChain FORWARD (policy DROP)\nChain OUTPUT (policy DROP)\n```\n\n**- OR -**\n\nVerify IPv6 is disabled:\n\nRun the following script. Output will confirm if IPv6 is enabled on the system.\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** IPv6 is enabled on your system:\n\nRun the following commands to implement a default DROP policy:\n\n```\n# ip6tables -P INPUT DROP\n# ip6tables -P OUTPUT DROP\n# ip6tables -P FORWARD DROP\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured", + "title": "4.4.3.2 Ensure ip6tables loopback traffic is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured_smt", + "name": "statement", + "prose": "Configure the loopback interface to accept traffic. Configure all other interfaces to deny traffic to the loopback network (::1).\n\n**Note:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system\n\n- Remediation will only affect the active system firewall, be sure to configure the default policy in your firewall management to apply on boot as well" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured_rationale", + "name": "rationale", + "prose": "Loopback traffic is generated between processes on machine and is typically critical to operation of the system. The loopback interface is the only place that loopback network (::1) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure ip6tables loopback traffic is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured_obj" + }, + { + "rel": "script", + "href": "#80cb14a1-10b1-5f05-896a-d9de8c0264f6" + }, + { + "rel": "script", + "href": "#2aa5c2ae-c45b-5110-a8e4-5ff5055d0b44" + }, + { + "rel": "script", + "href": "#a1587053-8ee8-519f-a5fa-90a621907ce1" + } + ], + "prose": "Run the following commands and verify output includes the listed rules in order (packet and byte counts may differ):\n\n```\n# ip6tables -L INPUT -v -n\nChain INPUT (policy DROP 0 packets, 0 bytes)\npkts bytes target prot opt in out source destination\n 0 0 ACCEPT all lo * ::/0 ::/0\n 0 0 DROP all * * ::1 ::/0\n\n# ip6tables -L OUTPUT -v -n\nChain OUTPUT (policy DROP 0 packets, 0 bytes)\npkts bytes target prot opt in out source destination\n 0 0 ACCEPT all * lo ::/0 ::/0\n```\n\n**- OR -**\n\nVerify IPv6 is disabled:\n\nRun the following script. Output will confirm if IPv6 is enabled on the system.\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to implement the loopback rules:\n\n```\n# ip6tables -A INPUT -i lo -j ACCEPT\n# ip6tables -A OUTPUT -o lo -j ACCEPT\n# ip6tables -A INPUT -s ::1 -j DROP\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured", + "title": "4.4.3.3 Ensure ip6tables outbound and established connections are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured_smt", + "name": "statement", + "prose": "Configure the firewall rules for new outbound, and established IPv6 connections.\n\n**Note:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system\n\n- Remediation will only affect the active system firewall, be sure to configure the default policy in your firewall management to apply on boot as well" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured_rationale", + "name": "rationale", + "prose": "If rules are not in place for new outbound, and established connections all packets will be dropped by the default policy preventing network usage." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure ip6tables outbound and established connections are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured_obj" + } + ], + "prose": "Run the following command and verify all rules for new outbound, and established connections match site policy:\n\n```\n# ip6tables -L -v -n\n```\n\n**- OR -**\n\nVerify IPv6 is disabled:\n\nRun the following script. Output will confirm if IPv6 is enabled on the system.\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure iptables in accordance with site policy. The following commands will implement a policy to allow all outbound connections and all established connections:\n\n```\n# ip6tables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -j ACCEPT\n# ip6tables -A OUTPUT -p udp -m state --state NEW,ESTABLISHED -j ACCEPT\n# ip6tables -A INPUT -p tcp -m state --state ESTABLISHED -j ACCEPT\n# ip6tables -A INPUT -p udp -m state --state ESTABLISHED -j ACCEPT\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports", + "title": "4.4.3.4 Ensure ip6tables firewall rules exist for all open ports", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/4" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports_smt", + "name": "statement", + "prose": "Any ports that have been opened on non-loopback addresses need firewall rules to govern traffic.\n\n**Notes:**\n\n- Changing firewall settings while connected over network can result in being locked out of the system\n\n- Remediation will only affect the active system firewall, be sure to configure the default policy in your firewall management to apply on boot as well\n\n- The remediation command opens up the port to traffic from all sources. Consult iptables documentation and set any restrictions in compliance with site policy" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports_rationale", + "name": "rationale", + "prose": "Without a firewall rule configured for open ports default firewall policy will drop all packets to these ports." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports_obj", + "name": "assessment-objective", + "prose": "Ensure ip6tables firewall rules exist for all open ports" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports_obj" + }, + { + "rel": "script", + "href": "#80cb14a1-10b1-5f05-896a-d9de8c0264f6" + }, + { + "rel": "script", + "href": "#dd79f8f2-4ddb-5def-a3b5-ee16e8fbd6f5" + }, + { + "rel": "script", + "href": "#a1587053-8ee8-519f-a5fa-90a621907ce1" + } + ], + "prose": "Run the following command to determine open ports:\n\n```\n# ss -6tuln\n\nNetid State Recv-Q Send-Q Local Address:Port Peer Address:Port\nudp UNCONN 0 0 ::1:123 :::*\nudp UNCONN 0 0 :::123 :::*\ntcp LISTEN 0 128 :::22 :::*\ntcp LISTEN 0 20 ::1:25 :::*\n```\n\nRun the following command to determine firewall rules:\n\n```\n# ip6tables -L INPUT -v -n\n\nChain INPUT (policy DROP 0 packets, 0 bytes)\n pkts bytes target prot opt in out source destination\n 0 0 ACCEPT all lo * ::/0 ::/0\n 0 0 DROP all * * ::1 ::/0\n 0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:22 state NEW\n```\n\nVerify all open ports listening on non-localhost addresses have at least one firewall rule.\n\nThe last line identified by the \"tcp dpt:22 state NEW\" identifies it as a firewall rule for new connections on tcp port 22.\n\n**- OR -** verify IPv6 is not enabled:\n\nRun the following script. Output will confirm if IPv6 is enabled on the system:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_ipv6_enabled=\"is\"\n ! grep -Pqs -- '^\\h*0\\b' /sys/module/ipv6/parameters/disable && l_ipv6_enabled=\"is not\"\n if sysctl net.ipv6.conf.all.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.all\\.disable_ipv6\\h*=\\h*1\\b\" && \\\n sysctl net.ipv6.conf.default.disable_ipv6 | grep -Pqs -- \"^\\h*net\\.ipv6\\.conf\\.default\\.disable_ipv6\\h*=\\h*1\\b\"; then\n l_ipv6_enabled=\"is not\"\n fi\n echo -e \" - IPv6 $l_ipv6_enabled enabled on the system\"\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "For each port identified in the audit which does not have a firewall rule establish a proper rule for accepting inbound connections:\n\n```\n# ip6tables -A INPUT -p --dport -m state --state NEW -j ACCEPT\n```" + } + ] + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5_Access_Control", + "title": "Access Control", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.1_Configure_SSH_Server", + "title": "Configure SSH Server", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured", + "title": "5.1.1 Ensure permissions on /etc/ssh/sshd_config are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured_smt", + "name": "statement", + "prose": "The file `/etc/ssh/sshd_config`, and files ending in `.conf` in the `/etc/ssh/sshd_config.d` directory, contain configuration specifications for `sshd`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured_rationale", + "name": "rationale", + "prose": "configuration specifications for `sshd` need to be protected from unauthorized changes by non-privileged users." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/ssh/sshd_config are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured_obj" + }, + { + "rel": "script", + "href": "#c1a75251-7d45-5b0b-83b5-714fef3c3f89" + }, + { + "rel": "script", + "href": "#b33b3e27-0307-555d-85f8-633bc01ca592" + }, + { + "rel": "script", + "href": "#003b6f15-7428-5b5b-96c0-6a7b522244f9" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following script and verify `/etc/ssh/sshd_config` and files ending in `.conf` in the `/etc/ssh/sshd_config.d` directory are:\n\n- Mode `0600` or more restrictive\n\n- Owned by the `root` user\n\n- Group owned by the group `root`.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n perm_mask='0177' && maxperm=\"$( printf '%o' $(( 0777 & ~$perm_mask)) )\"\n f_sshd_files_chk()\n {\n while IFS=: read -r l_mode l_user l_group; do\n a_out2=()\n [ $(( $l_mode & $perm_mask )) -gt 0 ] && a_out2+=(\" Is mode: \\\"$l_mode\\\"\" \\\n \" should be mode: \\\"$maxperm\\\" or more restrictive\")\n [ \"$l_user\" != \"root\" ] && a_out2+=(\" Is owned by \\\"$l_user\\\" should be owned by \\\"root\\\"\")\n [ \"$l_group\" != \"root\" ] && a_out2+=(\" Is group owned by \\\"$l_user\\\" should be group owned by \\\"root\\\"\")\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\":\" \"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\":\" \" Correct: mode ($l_mode), owner ($l_user)\" \\\n \" and group owner ($l_group) configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\")\n }\n [ -e \"/etc/ssh/sshd_config\" ] && l_file=\"/etc/ssh/sshd_config\" && f_sshd_files_chk\n while IFS= read -r -d $'\\0' l_file; do\n [ -e \"$l_file\" ] && f_sshd_files_chk\n done < <(find /etc/ssh/sshd_config.d -type f -name '*.conf' \\( -perm /077 -o ! -user root -o ! -group root \\) -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```\n\n**- IF -** other locations are listed in an `Include` statement, `*.conf` files in these locations should also be checked." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to set ownership and permissions on `/etc/ssh/sshd_config` and files ending in `.conf` in the `/etc/ssh/sshd_config.d` directory:\n\n```bash\n#!/usr/bin/env bash\n\n{\n chmod u-x,og-rwx /etc/ssh/sshd_config\n chown root:root /etc/ssh/sshd_config\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n chmod u-x,og-rwx \"$l_file\"\n chown root:root \"$l_file\"\n fi\n done < <(find /etc/ssh/sshd_config.d -type f -print0 2>/dev/null)\n}\n```\n\n**- IF -** other locations are listed in an `Include` statement, `*.conf` files in these locations access should also be modified." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured", + "title": "5.1.2 Ensure permissions on SSH private host key files are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured_smt", + "name": "statement", + "prose": "An SSH private key is one of two files used in SSH public key authentication. In this authentication method, the possession of the private key is proof of identity. Only a private key that corresponds to a public key will be able to authenticate successfully. The private keys need to be stored and handled carefully, and no copies of the private key should be distributed." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured_rationale", + "name": "rationale", + "prose": "If an unauthorized user obtains the private SSH host key file, the host could be impersonated" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on SSH private host key files are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured_obj" + }, + { + "rel": "script", + "href": "#1dc0ec4f-7928-5d29-8db7-362548b598e4" + } + ], + "prose": "Run the following script to verify SSH private host key files are owned by the root user and either:\n\n- owned by the group root and mode `0600` or more restrictive\n\n**- OR -**\n\n- owned by the group designated to own openSSH private keys and mode `0640` or more restrictive\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n l_ssh_group_name=\"$(awk -F: '($1 ~ /^(ssh_keys|_?ssh)$/) {print $1}' /etc/group)\"\n f_file_chk()\n {\n while IFS=: read -r l_file_mode l_file_owner l_file_group; do\n a_out2=()\n [ \"$l_file_group\" = \"$l_ssh_group_name\" ] && l_pmask=\"0137\" || l_pmask=\"0177\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n if [ $(( $l_file_mode & $l_pmask )) -gt 0 ]; then\n a_out2+=(\" Mode: \\\"$l_file_mode\\\" should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n fi\n if [ \"$l_file_owner\" != \"root\" ]; then\n a_out2+=(\" Owned by: \\\"$l_file_owner\\\" should be owned by \\\"root\\\"\")\n fi\n if [[ ! \"$l_file_group\" =~ ($l_ssh_group_name|root) ]]; then\n a_out2+=(\" Owned by group \\\"$l_file_group\\\" should be group owned by: \\\"$l_ssh_group_name\\\" or \\\"root\\\"\")\n fi\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\"\" \\\n \" Correct: mode: \\\"$l_file_mode\\\", owner: \\\"$l_file_owner\\\" and group owner: \\\"$l_file_group\\\" configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\")\n }\n while IFS= read -r -d $'\\0' l_file; do\n if ssh-keygen -lf &>/dev/null \"$l_file\"; then\n file \"$l_file\" | grep -Piq -- '\\bopenssh\\h+([^#\\n\\r]+\\h+)?private\\h+key\\b' && f_file_chk\n fi\n done < <(find -L /etc/ssh -xdev -type f -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to set mode, ownership, and group on the private SSH host key files:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=(); l_ssh_group_name=\"$(awk -F: '($1 ~ /^(ssh_keys|_?ssh)$/) {print $1}' /etc/group)\"\n f_file_access_fix()\n {\n while IFS=: read -r l_file_mode l_file_owner l_file_group; do\n a_out2=()\n [ \"$l_file_group\" = \"$l_ssh_group_name\" ] && l_pmask=\"0137\" || l_pmask=\"0177\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n if [ $(( $l_file_mode & $l_pmask )) -gt 0 ]; then\n a_out2+=(\" Mode: \\\"$l_file_mode\\\" should be mode: \\\"$l_maxperm\\\" or more restrictive\" \\\n \" updating to mode: \\:$l_maxperm\\\"\")\n if [ \"l_file_group\" = \"$l_ssh_group_name\" ]; then\n chmod u-x,g-wx,o-rwx \"$l_file\"\n else\n chmod u-x,go-rwx \"$l_file\"\n fi\n fi\n if [ \"$l_file_owner\" != \"root\" ]; then\n a_out2+=(\" Owned by: \\\"$l_file_owner\\\" should be owned by \\\"root\\\"\" \\\n \" Changing ownership to \\\"root\\\"\")\n chown root \"$l_file\"\n fi\n if [[ ! \"$l_file_group\" =~ ($l_ssh_group_name|root) ]]; then\n [ -n \"$l_ssh_group_name\" ] && l_new_group=\"$l_ssh_group_name\" || l_new_group=\"root\"\n a_out2+=(\" Owned by group \\\"$l_file_group\\\" should be group owned by: \\\"$l_ssh_group_name\\\" or \\\"root\\\"\" \\\n \" Changing group ownership to \\\"$l_new_group\\\"\")\n chgrp \"$l_new_group\" \"$l_file\"\n fi\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\"\" \"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\"\" \\\n \"Correct: mode: \\\"$l_file_mode\\\", owner: \\\"$l_file_owner\\\", and group owner: \\\"$l_file_group\\\" configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\")\n }\n while IFS= read -r -d $'\\0' l_file; do\n if ssh-keygen -lf &>/dev/null \"$l_file\"; then\n file \"$l_file\" | grep -Piq -- '\\bopenssh\\h+([^#\\n\\r]+\\h+)?private\\h+key\\b' && f_file_access_fix\n fi\n done < <(find -L /etc/ssh -xdev -type f -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le \"0\" ]; then\n printf '%s\\n' \"\" \" - No access changes required\" \"\"\n else\n printf '%s\\n' \"\" \" - Remediation results:\" \"${a_output2[@]}\" \"\"\n fi\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured", + "title": "5.1.3 Ensure permissions on SSH public host key files are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured_smt", + "name": "statement", + "prose": "An SSH public key is one of two files used in SSH public key authentication. In this authentication method, a public key is a key that can be used for verifying digital signatures generated using a corresponding private key. Only a public key that corresponds to a private key will be able to authenticate successfully." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured_rationale", + "name": "rationale", + "prose": "If a public host key file is modified by an unauthorized user, the SSH service may be compromised." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on SSH public host key files are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured_obj" + }, + { + "rel": "script", + "href": "#57a1abd0-77da-5198-8396-c7cc0177fd96" + } + ], + "prose": "Run the following command and verify Access does not grant write or execute permissions to group or other for all returned files:\n\nRun the following script to verify SSH public host key files are mode `0644` or more restrictive, owned by the `root` user, and owned by the `root` group:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n l_pmask=\"0133\"; l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n f_file_chk()\n {\n while IFS=: read -r l_file_mode l_file_owner l_file_group; do\n a_out2=()\n if [ $(( $l_file_mode & $l_pmask )) -gt 0 ]; then\n a_out2+=(\" Mode: \\\"$l_file_mode\\\" should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n fi\n if [ \"$l_file_owner\" != \"root\" ]; then\n a_out2+=(\" Owned by: \\\"$l_file_owner\\\" should be owned by: \\\"root\\\"\")\n fi\n if [ \"$l_file_group\" != \"root\" ]; then\n a_out2+=(\" Owned by group \\\"$l_file_group\\\" should be group owned by group: \\\"root\\\"\")\n fi\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\"\" \"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\"\" \\\n \" Correct: mode: \\\"$l_file_mode\\\", owner: \\\"$l_file_owner\\\" and group owner: \\\"$l_file_group\\\" configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\")\n }\n while IFS= read -r -d $'\\0' l_file; do\n if ssh-keygen -lf &>/dev/null \"$l_file\"; then\n file \"$l_file\" | grep -Piq -- '\\bopenssh\\h+([^#\\n\\r]+\\h+)?public\\h+key\\b' && f_file_chk\n fi\n done < <(find -L /etc/ssh -xdev -type f -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n [ \"${#a_output[@]}\" -le 0 ] && a_output+=(\" - No openSSH public keys found\")\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to set mode, ownership, and group on the public SSH host key files:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n l_pmask=\"0133\"; l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n f_file_access_fix()\n {\n while IFS=: read -r l_file_mode l_file_owner l_file_group; do\n a_out2=()\n [ $(( $l_file_mode & $l_pmask )) -gt 0 ] && \\\n a_out2+=(\" Mode: \\\"$l_file_mode\\\" should be mode: \\\"$l_maxperm\\\" or more restrictive\" \\\n \" updating to mode: \\\"$l_maxperm\\\"\") && chmod u-x,go-wx \"$l_file\"\n [ \"$l_file_owner\" != \"root\" ] && \\\n a_out2+=(\" Owned by: \\\"$l_file_owner\\\" should be owned by \\\"root\\\"\" \\\n \" Changing ownership to \\\"root\\\"\") && chown root \"$l_file\"\n [ \"$l_file_group\" != \"root\" ] && \\\n a_out2+=(\" Owned by group \\\"$l_file_group\\\" should be group owned by: \\\"root\\\"\" \\\n \" Changing group ownership to \\\"root\\\"\") && chgrp root \"$l_file\"\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - File: \\\"$l_file\\\"\" \"${a_out2[@]}\")\n else\n a_output+=(\" - File: \\\"$l_file\\\"\" \\\n \" Correct: mode: \\\"$l_file_mode\\\", owner: \\\"$l_file_owner\\\", and group owner: \\\"$l_file_group\\\" configured\")\n fi\n done < <(stat -Lc '%#a:%U:%G' \"$l_file\")\n }\n while IFS= read -r -d $'\\0' l_file; do\n if ssh-keygen -lf &>/dev/null \"$l_file\"; then\n file \"$l_file\" | grep -Piq -- '\\bopenssh\\h+([^#\\n\\r]+\\h+)?public\\h+key\\b' && f_file_access_fix\n fi\n done < <(find -L /etc/ssh -xdev -type f -print0 2>/dev/null)\n if [ \"${#a_output2[@]}\" -le \"0\" ]; then\n printf '%s\\n' \"\" \" - No access changes required\" \"\"\n else\n printf '%s\\n' \" - Remediation results:\" \"${a_output2[@]}\" \"\"\n fi\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured", + "title": "5.1.4 Ensure sshd access is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured_smt", + "name": "statement", + "prose": "There are several options available to limit which users and group can access the system via SSH. It is recommended that at least one of the following options be leveraged:\n\n- `AllowUsers`:\n\n- The `AllowUsers` variable gives the system administrator the option of allowing specific users to `ssh` into the system. The list consists of space separated user names. Numeric user IDs are not recognized with this variable. If a system administrator wants to restrict user access further by only allowing the allowed users to log in from a particular host, the entry can be specified in the form of user@host.\n\n- `AllowGroups`:\n\n- The `AllowGroups` variable gives the system administrator the option of allowing specific groups of users to `ssh` into the system. The list consists of space separated group names. Numeric group IDs are not recognized with this variable.\n\n- `DenyUsers`:\n\n- The `DenyUsers` variable gives the system administrator the option of denying specific users to `ssh` into the system. The list consists of space separated user names. Numeric user IDs are not recognized with this variable. If a system administrator wants to restrict user access further by specifically denying a user's access from a particular host, the entry can be specified in the form of user@host.\n\n- `DenyGroups`:\n\n- The `DenyGroups` variable gives the system administrator the option of denying specific groups of users to `ssh` into the system. The list consists of space separated group names. Numeric group IDs are not recognized with this variable." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured_rationale", + "name": "rationale", + "prose": "Restricting which users can remotely access the system via SSH will help ensure that only authorized users access the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd access is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command and verify the output:\n\n```\n# sshd -T | grep -Pi -- '^\\h*(allow|deny)(users|groups)\\h+\\H+'\n```\n\nVerify that the output matches at least one of the following lines:\n\n```\nallowusers \n-OR-\nallowgroups \n-OR-\ndenyusers \n-OR-\ndenygroups \n```\n\nReview the list(s) to ensure included users and/or groups follow local site policy\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep -Pi -- '^\\h*(allow|deny)(users|groups)\\h+\\H+'\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set one or more of the parameters above any `Include` and `Match` set statements as follows:\n\n```\nAllowUsers \n - AND/OR -\nAllowGroups \n```\n\n**Note:**\n\n- First occurrence of a option takes precedence, `Match` set statements withstanding. If `Include` locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a `.conf` file in a `Include` directory.\n\n- **Be advised** that these options are \"ANDed\" together. If both `AllowUsers` and `AllowGroups` are set, connections will be limited to the list of users that are also a member of an allowed group. It is recommended that only one be set for clarity and ease of administration.\n\n- It is easier to manage an allow list than a deny list. In a deny list, you could potentially add a user or group and forget to add it to the deny list." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured", + "title": "5.1.5 Ensure sshd Banner is configured", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured_smt", + "name": "statement", + "prose": "The `Banner` parameter specifies a file whose contents must be sent to the remote user before authentication is permitted. By default, no banner is displayed." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured_rationale", + "name": "rationale", + "prose": "Banners are used to warn connecting users of the particular site's policy regarding connection. Presenting a warning message prior to the normal user login may assist the prosecution of trespassers on the computer system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd Banner is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command to verify `Banner` is set:\n\n```\n# sshd -T | grep -Pi -- '^banner\\h+\\/\\H+'\n```\n\n*Example:*\n\n```\nbanner /etc/issue.net\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep -Pi -- '^banner\\h+\\/\\H+'\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain).\n\nRun the following command and verify that the contents or the file being called by the `Banner` argument match site policy:\n\n```\n# [ -e \"$(sshd -T | awk '$1 == \"banner\" {print $2}')\" ] && cat \"$(sshd -T | awk '$1 == \"banner\" {print $2}')\"\n```\n\nRun the following command and verify no results are returned:\n\n```\n# grep -Psi -- \"(\\\\\\v|\\\\\\r|\\\\\\m|\\\\\\s|\\b$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed -e 's/\"//g')\\b)\" \"$(sshd -T | awk '$1 == \"banner\" {print $2}')\"\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `Banner` parameter above any `Include` and `Match` entries as follows:\n\n```\nBanner /etc/issue.net\n```\n\n**Note:** First occurrence of a option takes precedence, Match set statements withstanding. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location.\n\nEdit the file being called by the `Banner` argument with the appropriate contents according to your site policy, remove any instances of `\\m` , `\\r` , `\\s` , `\\v` or references to the `OS platform`\n\n*Example:*\n\n```\n# printf '%s\\n' \"Authorized users only. All activity may be monitored and reported.\" > \"$(sshd -T | awk '$1 == \"banner\" {print $2}')\"\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured", + "title": "5.1.6 Ensure sshd Ciphers are configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_sshd_config_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "ciphers:not_match:3des-cbc,aes128-cbc,aes192-cbc,aes256-cbc,arcfour,arcfour128,arcfour256,blowfish-cbc,cast128-cbc,rijndael-cbc@lysator\\.liu\\.se" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/10" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured_smt", + "name": "statement", + "prose": "This variable limits the ciphers that SSH can use during communication.\n\n**Notes:**\n\n- Some organizations may have stricter requirements for approved ciphers.\n\n- Ensure that ciphers used are in compliance with site policy.\n\n- The only \"strong\" ciphers currently FIPS 140 compliant are:\n\n- [aes256-gcm@openssh.com](mailto:aes256-gcm@openssh.com)\n\n- [aes128-gcm@openssh.com](mailto:aes128-gcm@openssh.com)\n\n- aes256-ctr\n\n- aes192-ctr\n\n- aes128-ctr" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured_rationale", + "name": "rationale", + "prose": "Weak ciphers that are used for authentication to the cryptographic module cannot be relied upon to provide confidentiality or integrity, and system data may be compromised.\n\n- The Triple DES ciphers, as used in SSH, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain clear text data via a birthday attack against a long-duration encrypted session, aka a \"Sweet32\" attack.\n\n- Error handling in the SSH protocol; Client and Server, when using a block cipher algorithm in Cipher Block Chaining (CBC) mode, makes it easier for remote attackers to recover certain plain text data from an arbitrary block of cipher text in an SSH session via unknown vectors." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd Ciphers are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + } + ], + "prose": "Run the following command to verify none of the \"weak\" ciphers are being used:\n\n```\n# sshd -T | grep -Pi -- '^ciphers\\h+\\\"?([^#\\n\\r]+,)?((3des|blowfish|cast128|aes(128|192|256))-cbc|arcfour(128|256)?|rijndael-cbc@lysator\\.liu\\.se|chacha20-poly1305@openssh\\.com)\\b'\n```\n\n**- IF -** a line is returned, review the list of ciphers. If the line includes `chacha20-poly1305@openssh.com`, review `CVE-2023-48795` and verify the system has been patched. No ciphers in the list below should be returned as they're considered \"weak\":\n\n```\n3des-cbc\naes128-cbc\naes192-cbc\naes256-cbc\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the /etc/ssh/sshd_config file and add/modify the `Ciphers` line to contain a comma separated list of the site unapproved (weak) Ciphers preceded with a `-` above any `Include` entries:\n\n*Example:*\n\n```\nCiphers -3des-cbc,aes128-cbc,aes192-cbc,aes256-cbc,chacha20-poly1305@openssh.com\n```\n\n**- IF -** `CVE-2023-48795` has been addressed, and it meets local site policy, `chacha20-poly1305@openssh.com` may be removed from the list of excluded ciphers.\n\n**Note:** First occurrence of an option takes precedence. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured", + "title": "5.1.7 Ensure sshd ClientAliveInterval and ClientAliveCountMax are configured", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured_smt", + "name": "statement", + "prose": "**Note:** To clarify, the two settings described below are only meant for idle connections from a protocol perspective and are not meant to check if the user is active or not. An idle user does not mean an idle connection. SSH does not and never had, intentionally, the capability to drop idle users. In SSH versions before `8.2p1` there was a bug that caused these values to behave in such a manner that they were abused to disconnect idle users. This bug has been resolved in `8.2p1` and thus it can no longer be abused disconnect idle users.\n\nThe two options `ClientAliveInterval` and `ClientAliveCountMax` control the timeout of SSH sessions. Taken directly from `man 5 sshd_config`:\n\n-\n`ClientAliveInterval` Sets a timeout interval in seconds after which if no data has been received from the client, sshd(8) will send a message through the encrypted channel to request a response from the client. The default is 0, indicating that these messages will not be sent to the client.\n\n-\n`ClientAliveCountMax` Sets the number of client alive messages which may be sent without sshd(8) receiving any messages back from the client. If this threshold is reached while client alive messages are being sent, sshd will disconnect the client, terminating the session. It is important to note that the use of client alive messages is very different from TCPKeepAlive. The client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option en‐abled by TCPKeepAlive is spoofable. The client alive mechanism is valuable when the client or server depend on knowing when a connection has become unresponsive.\nThe default value is 3. If ClientAliveInterval is set to 15, and ClientAliveCountMax is left at the default, unresponsive SSH clients will be disconnected after approximately 45 seconds. Setting a zero ClientAliveCountMax disables connection termination." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured_rationale", + "name": "rationale", + "prose": "In order to prevent resource exhaustion, appropriate values should be set for both `ClientAliveInterval` and `ClientAliveCountMax`. Specifically, looking at the source code, `ClientAliveCountMax` must be greater than zero in order to utilize the ability of SSH to drop idle connections. If connections are allowed to stay open indefinitely, this can potentially be used as a DDOS attack or simple resource exhaustion could occur over unreliable networks.\n\nThe example set here is a 45 second timeout. Consult your site policy for network timeouts and apply as appropriate." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd ClientAliveInterval and ClientAliveCountMax are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command and verify `ClientAliveInterval` and `ClientAliveCountMax` are greater than zero:\n\n```\n# sshd -T | grep -Pi -- '(clientaliveinterval|clientalivecountmax)'\n```\n\n*Example Output:*\n\n```\nclientaliveinterval 15\nclientalivecountmax 3\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep -Pi -- '(clientaliveinterval|clientalivecountmax)'\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `ClientAliveInterval` and `ClientAliveCountMax` parameters above any `Include` and `Match` entries according to site policy.\n\n*Example:*\n\n```\nClientAliveInterval 15\nClientAliveCountMax 3\n```\n\n**Note:** First occurrence of a option takes precedence, Match set statements withstanding. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled", + "title": "5.1.8 Ensure sshd DisableForwarding is enabled", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_sshd_config_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "disableforwarding:match:yes" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled_smt", + "name": "statement", + "prose": "The `DisableForwarding` parameter disables all forwarding features, including X11, ssh-agent(1), TCP and StreamLocal. This option overrides all other forwarding-related options and may simplify restricted configurations.\n\n- X11Forwarding provides the ability to tunnel X11 traffic through the connection to enable remote graphic connections.\n\n- ssh-agent is a program to hold private keys used for public key authentication. Through use of environment variables the agent can be located and automatically used for authentication when logging in to other machines using ssh.\n\n- SSH port forwarding is a mechanism in SSH for tunneling application ports from the client to the server, or servers to clients. It can be used for adding encryption to legacy applications, going through firewalls, and some system administrators and IT professionals use it for opening backdoors into the internal network from their home machines." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled_rationale", + "name": "rationale", + "prose": "Disable X11 forwarding unless there is an operational requirement to use X11 applications directly. There is a small risk that the remote X11 servers of users who are logged in via SSH with X11 forwarding could be compromised by other users on the X11 server. Note that even if X11 forwarding is disabled, users can always install their own forwarders.\n\nanyone with root privilege on the the intermediate server can make free use of ssh-agent to authenticate them to other servers\n\nLeaving port forwarding enabled can expose the organization to security risks and backdoors. SSH connections are protected with strong encryption. This makes their contents invisible to most deployed network monitoring and traffic filtering solutions. This invisibility carries considerable risk potential if it is used for malicious purposes such as data exfiltration. Cybercriminals or malware could exploit SSH to hide their unauthorized communications, or to exfiltrate stolen data from the target network." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure sshd DisableForwarding is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + } + ], + "prose": "Run the following command to verify `DisableForwarding` is set to `yes`:\n\n```\n# sshd -T | grep -i disableforwarding\n\ndisableforwarding yes\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `DisableForwarding` parameter to `yes` above any `Include` entry as follows:\n\n```\nDisableForwarding yes\n```\n\n**Note:** First occurrence of a option takes precedence. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location.\n\nImpact:\n\nSSH tunnels are widely used in many corporate environments. In some environments the applications themselves may have very limited native support for security. By utilizing tunneling, compliance with SOX, HIPAA, PCI-DSS, and other standards can be achieved without having to modify the applications." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled", + "title": "5.1.9 Ensure sshd GSSAPIAuthentication is disabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled_smt", + "name": "statement", + "prose": "The `GSSAPIAuthentication` parameter specifies whether user authentication based on GSSAPI is allowed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled_rationale", + "name": "rationale", + "prose": "Allowing GSSAPI authentication through SSH exposes the system's GSSAPI to remote hosts, and should be disabled to reduce the attack surface of the system" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure sshd GSSAPIAuthentication is disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command to verify `GSSAPIAuthentication` is set to `no`:\n\n```\n# sshd -T | grep gssapiauthentication\n\ngssapiauthentication no\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep gssapiauthentication\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `GSSAPIAuthentication` parameter to `no` above any `Include` and `Match` entries as follows:\n\n```\nGSSAPIAuthentication no\n```\n\n**Note:** First occurrence of an option takes precedence, `Match` set statements withstanding. If `Include` locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in `Include` location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled", + "title": "5.1.10 Ensure sshd HostbasedAuthentication is disabled", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled_smt", + "name": "statement", + "prose": "The `HostbasedAuthentication` parameter specifies if authentication is allowed through trusted hosts via the user of `.rhosts`, or `/etc/hosts.equiv`, along with successful public key client host authentication." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled_rationale", + "name": "rationale", + "prose": "Even though the `.rhosts` files are ineffective if support is disabled in `/etc/pam.conf`, disabling the ability to use `.rhosts` files in SSH provides an additional layer of protection." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure sshd HostbasedAuthentication is disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command to verify `HostbasedAuthentication` is set to `no`:\n\n```\n# sshd -T | grep hostbasedauthentication\n\nhostbasedauthentication no\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep hostbasedauthentication\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `HostbasedAuthentication` parameter to `no` above any `Include` and `Match` entries as follows:\n\n```\nHostbasedAuthentication no\n```\n\n**Note:** First occurrence of a option takes precedence, `Match` set statements withstanding. If `Include` locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in `Include` location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled", + "title": "5.1.11 Ensure sshd IgnoreRhosts is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled_smt", + "name": "statement", + "prose": "The `IgnoreRhosts` parameter specifies that `.rhosts` and `.shosts` files will not be used in `RhostsRSAAuthentication` or `HostbasedAuthentication`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled_rationale", + "name": "rationale", + "prose": "Setting this parameter forces users to enter a password when authenticating with SSH." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure sshd IgnoreRhosts is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command to verify `IgnoreRhosts` is set to `yes`:\n\n```\n# sshd -T | grep ignorerhosts\n\nignorerhosts yes\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep ignorerhosts\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `IgnoreRhosts` parameter to `yes` above any `Include` and `Match` entries as follows:\n\n```\nIgnoreRhosts yes\n```\n\n**Note:** First occurrence of a option takes precedence, `Match` set statements withstanding. If `Include` locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in `Include` location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured", + "title": "5.1.12 Ensure sshd KexAlgorithms is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_sshd_config_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "kexalgorithms:not_match:diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/10" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured_smt", + "name": "statement", + "prose": "Key exchange is any method in cryptography by which cryptographic keys are exchanged between two parties, allowing use of a cryptographic algorithm. If the sender and receiver wish to exchange encrypted messages, each must be equipped to encrypt messages to be sent and decrypt messages received\n\n**Notes:**\n\n- Kex algorithms have a higher preference the earlier they appear in the list\n\n- Some organizations may have stricter requirements for approved Key exchange algorithms\n\n- Ensure that Key exchange algorithms used are in compliance with site policy\n\n- The only Key Exchange Algorithms currently FIPS 140 approved are:\n\n- ecdh-sha2-nistp256\n\n- ecdh-sha2-nistp384\n\n- ecdh-sha2-nistp521\n\n- diffie-hellman-group-exchange-sha256\n\n- diffie-hellman-group16-sha512\n\n- diffie-hellman-group18-sha512\n\n- diffie-hellman-group14-sha256" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured_rationale", + "name": "rationale", + "prose": "Key exchange methods that are considered weak should be removed. A key exchange method may be weak because too few bits are used, or the hashing algorithm is considered too weak. Using weak algorithms could expose connections to man-in-the-middle attacks" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd KexAlgorithms is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + } + ], + "prose": "Run the following command to verify none of the \"weak\" Key Exchange algorithms are being used:\n\n```\n# sshd -T | grep -Pi -- 'kexalgorithms\\h+([^#\\n\\r]+,)?(diffie-hellman-group1-sha1|diffie-hellman-group14-sha1|diffie-hellman-group-exchange-sha1)\\b'\n\nNothing should be returned\n```\n\nThe following are considered \"weak\" Key Exchange Algorithms, and should not be used:\n\n```\ndiffie-hellman-group1-sha1\ndiffie-hellman-group14-sha1\ndiffie-hellman-group-exchange-sha1\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file and add/modify the `KexAlgorithms` line to contain a comma separated list of the site unapproved (weak) KexAlgorithms preceded with a `-` above any `Include` entries:\n\n*Example:*\n\n```\nKexAlgorithms -diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1\n```\n\n**Note:** First occurrence of an option takes precedence. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured", + "title": "5.1.13 Ensure sshd LoginGraceTime is configured", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured_smt", + "name": "statement", + "prose": "The `LoginGraceTime` parameter specifies the time allowed for successful authentication to the SSH server. The longer the Grace period is the more open unauthenticated connections can exist. Like other session controls in this session the Grace Period should be limited to appropriate organizational limits to ensure the service is available for needed access." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured_rationale", + "name": "rationale", + "prose": "Setting the `LoginGraceTime` parameter to a low number will minimize the risk of successful brute force attacks to the SSH server. It will also limit the number of concurrent unauthenticated connections While the recommended setting is 60 seconds (1 Minute), set the number based on site policy." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd LoginGraceTime is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + } + ], + "prose": "Run the following command and verify that output `LoginGraceTime` is between `1` and `60` seconds:\n\n```\n# sshd -T | grep logingracetime\n\nlogingracetime 60\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `LoginGraceTime` parameter to `60` seconds or less above any `Include` entry as follows:\n\n```\nLoginGraceTime 60\n```\n\n**Note:** First occurrence of a option takes precedence. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured", + "title": "5.1.14 Ensure sshd LogLevel is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured_smt", + "name": "statement", + "prose": "SSH provides several logging levels with varying amounts of verbosity. The `DEBUG` options are specifically not recommended other than strictly for debugging SSH communications. These levels provide so much data that it is difficult to identify important security information, and may violate the privacy of users." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured_rationale", + "name": "rationale", + "prose": "The `INFO` level is the basic level that only records login activity of SSH users. In many situations, such as Incident Response, it is important to determine when a particular user was active on a system. The logout record can eliminate those users who disconnected, which helps narrow the field.\n\nThe `VERBOSE` level specifies that login and logout activity as well as the key fingerprint for any SSH key used for login will be logged. This information is important for SSH key management, especially in legacy environments." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd LogLevel is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command and verify that output matches `loglevel VERBOSE` or `loglevel INFO`:\n\n```\n# sshd -T | grep loglevel\n\nloglevel VERBOSE\n - OR -\nloglevel INFO\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep loglevel\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `LogLevel` parameter to `VERBOSE` or `INFO` above any `Include` and `Match` entries as follows:\n\n```\nLogLevel VERBOSE\n - OR -\nLogLevel INFO\n```\n\n**Note:** First occurrence of an option takes precedence, `Match` set statements withstanding. If `Include` locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in `Include` location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured", + "title": "5.1.15 Ensure sshd MACs are configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_sshd_config_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "macs:not_match:hmac-md5,hmac-md5-96,hmac-ripemd160,hmac-sha1-96,umac-64@openssh\\.com,hmac-md5-etm@openssh\\.com,hmac-md5-96-etm@openssh\\.com,hmac-ripemd160-etm@openssh\\.com,hmac-sha1-96-etm@openssh\\.com,umac-64-etm@openssh\\.com,umac-128-etm@openssh\\.com" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/10" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured_smt", + "name": "statement", + "prose": "This variable limits the types of MAC algorithms that SSH can use during communication.\n\n**Notes:**\n\n- Some organizations may have stricter requirements for approved MACs.\n\n- Ensure that MACs used are in compliance with site policy.\n\n- The only \"strong\" MACs currently FIPS 140 approved are:\n\n- HMAC-SHA1\n\n- HMAC-SHA2-256\n\n- HMAC-SHA2-384\n\n- HMAC-SHA2-512" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured_rationale", + "name": "rationale", + "prose": "MD5 and 96-bit MAC algorithms are considered weak and have been shown to increase exploitability in SSH downgrade attacks. Weak algorithms continue to have a great deal of attention as a weak spot that can be exploited with expanded computing power. An attacker that breaks the algorithm could take advantage of a MiTM position to decrypt the SSH tunnel and capture credentials and information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd MACs are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + } + ], + "prose": "Run the following command to verify none of the \"weak\" MACs are being used:\n\n```\n# sshd -T | grep -Pi -- 'macs\\h+([^#\\n\\r]+,)?(hmac-md5|hmac-md5-96|hmac-ripemd160|hmac-sha1-96|umac-64@openssh\\.com|hmac-md5-etm@openssh\\.com|hmac-md5-96-etm@openssh\\.com|hmac-ripemd160-etm@openssh\\.com|hmac-sha1-96-etm@openssh\\.com|umac-64-etm@openssh\\.com|umac-128-etm@openssh\\.com)\\b'\n\nNothing should be returned\n```\n\n**Note:** Review `CVE-2023-48795` and verify the system has been patched. If the system has not been patched, review the use of the Encrypt Then Mac (etm) MACs.\n\nThe following are considered \"weak\" MACs, and should not be used:\n\n```\nhmac-md5\nhmac-md5-96\nhmac-ripemd160\nhmac-sha1-96\numac-64@openssh.com\nhmac-md5-etm@openssh.com\nhmac-md5-96-etm@openssh.com\nhmac-ripemd160-etm@openssh.com\nhmac-sha1-96-etm@openssh.com\numac-64-etm@openssh.com\numac-128-etm@openssh.com\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file and add/modify the `MACs` line to contain a comma separated list of the site unapproved (weak) MACs preceded with a `-` above any `Include` entries:\n\n*Example:*\n\n```\nMACs -hmac-md5,hmac-md5-96,hmac-ripemd160,hmac-sha1-96,umac-64@openssh.com,hmac-md5-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com\n```\n\n**- IF -** `CVE-2023-48795` has not been reviewed and addressed, the following `etm` MACs should be added to the exclude list: [hmac-sha1-etm@openssh.com](mailto:hmac-sha1-etm@openssh.com),[hmac-sha2-256-etm@openssh.com](mailto:hmac-sha2-256-etm@openssh.com),[hmac-sha2-512-etm@openssh.com](mailto:hmac-sha2-512-etm@openssh.com)\n\n**Note:** First occurrence of an option takes precedence. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured", + "title": "5.1.16 Ensure sshd MaxAuthTries is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured_smt", + "name": "statement", + "prose": "The `MaxAuthTries` parameter specifies the maximum number of authentication attempts permitted per connection. When the login failure count reaches half the number, error messages will be written to the `syslog` file detailing the login failure." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured_rationale", + "name": "rationale", + "prose": "Setting the `MaxAuthTries` parameter to a low number will minimize the risk of successful brute force attacks to the SSH server. While the recommended setting is 4, set the number based on site policy." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd MaxAuthTries is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command and verify that `MaxAuthTries` is `4` or less:\n\n```\n# sshd -T | grep maxauthtries\n\nmaxauthtries 4\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep maxauthtries\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `MaxAuthTries` parameter to `4` or less above any `Include` and `Match` entries as follows:\n\n```\nMaxAuthTries 4\n```\n\n**Note:** First occurrence of an option takes precedence, `Match` set statements withstanding. If `Include` locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in `Include` location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured", + "title": "5.1.17 Ensure sshd MaxSessions is configured", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured_smt", + "name": "statement", + "prose": "The `MaxSessions` parameter specifies the maximum number of open sessions permitted from a given connection." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured_rationale", + "name": "rationale", + "prose": "To protect a system from denial of service due to a large number of concurrent sessions, use the rate limiting function of MaxSessions to protect availability of sshd logins and prevent overwhelming the daemon." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd MaxSessions is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command and verify that `MaxSessions` is `10` or less:\n\n```\n# sshd -T | grep -i maxsessions\n\nmaxsessions 10\n```\n\nRun the following command and verify the output:\n\n```\ngrep -Psi -- '^\\h*MaxSessions\\h+\\\"?(1[1-9]|[2-9][0-9]|[1-9][0-9][0-9]+)\\b' /etc/ssh/sshd_config /etc/ssh/sshd_config.d/*.conf\n\nNothing should be returned\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep maxsessions\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `MaxSessions` parameter to `10` or less above any `Include` and `Match` entries as follows:\n\n```\nMaxSessions 10\n```\n\n**Note:** First occurrence of an option takes precedence, `Match` set statements withstanding. If `Include` locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in `Include` location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured", + "title": "5.1.18 Ensure sshd MaxStartups is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_sshd_config_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "MaxStartups::10:30:60" + ] + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured_smt", + "name": "statement", + "prose": "The `MaxStartups` parameter specifies the maximum number of concurrent unauthenticated connections to the SSH daemon." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured_rationale", + "name": "rationale", + "prose": "To protect a system from denial of service due to a large number of pending authentication connection attempts, use the rate limiting function of MaxStartups to protect availability of sshd logins and prevent overwhelming the daemon." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure sshd MaxStartups is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + } + ], + "prose": "Run the following command to verify `MaxStartups` is `10:30:60` or more restrictive:\n\n```\n# sshd -T | awk '$1 ~ /^\\s*maxstartups/{split($2, a, \":\");{if(a[1] > 10 || a[2] > 30 || a[3] > 60) print $0}}'\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `MaxStartups` parameter to `10:30:60` or more restrictive above any `Include` entries as follows:\n\n```\nMaxStartups 10:30:60\n```\n\n**Note:** First occurrence of a option takes precedence. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled", + "title": "5.1.19 Ensure sshd PermitEmptyPasswords is disabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled_smt", + "name": "statement", + "prose": "The `PermitEmptyPasswords` parameter specifies if the SSH server allows login to accounts with empty password strings." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled_rationale", + "name": "rationale", + "prose": "Disallowing remote shell access to accounts that have an empty password reduces the probability of unauthorized access to the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure sshd PermitEmptyPasswords is disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command to verify `PermitEmptyPasswords` is set to `no`:\n\n```\n# sshd -T | grep permitemptypasswords\n\npermitemptypasswords no\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep permitemptypasswords\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/ssh/sshd_config` and set the `PermitEmptyPasswords` parameter to `no` above any `Include` and `Match` entries as follows:\n\n```\nPermitEmptyPasswords no\n```\n\n**Note:** First occurrence of an option takes precedence, `Match` set statements withstanding. If `Include` locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in `Include` location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled", + "title": "5.1.20 Ensure sshd PermitRootLogin is disabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled_smt", + "name": "statement", + "prose": "The `PermitRootLogin` parameter specifies if the root user can log in using SSH. The default is `prohibit-password`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled_rationale", + "name": "rationale", + "prose": "Disallowing `root` logins over SSH requires system admins to authenticate using their own individual account, then escalating to `root`. This limits opportunity for non-repudiation and provides a clear audit trail in the event of a security incident." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure sshd PermitRootLogin is disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + }, + { + "rel": "script", + "href": "#c20cb629-62df-5989-a424-ccc908ff76c9" + } + ], + "prose": "Run the following command to verify `PermitRootLogin` is set to `no`:\n\n```\n# sshd -T | grep permitrootlogin\n\npermitrootlogin no\n```\n\n**- IF -** `Match` set statements are used in your environment, specify the connection parameters to use for the `-T` extended test mode and run the audit to verify the setting is not incorrectly configured in a match block\n\n*Example additional audit needed for a match block for the user `sshuser`:*\n\n```\n# sshd -T -C user=sshuser | grep permitrootlogin\n```\n\n**Note:** If provided, any Match directives in the configuration file that would apply are applied before the configuration is written to standard output. The connection parameters are supplied as keyword=value pairs and may be supplied in any order, either with multiple `-C` options or as a comma-separated list. The keywords are `addr` (source address), `user` (user), `host` (resolved source host name), `laddr` (local address), `lport` (local port number), and `rdomain` (routing domain)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `PermitRootLogin` parameter to `no` above any `Include` and `Match` entries as follows:\n\n```\nPermitRootLogin no\n```\n\n**Note:** First occurrence of an option takes precedence, `Match` set statements withstanding. If `Include` locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in `Include` location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled", + "title": "5.1.21 Ensure sshd PermitUserEnvironment is disabled", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_sshd_config_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "permituserenvironment:match:no" + ] + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled_smt", + "name": "statement", + "prose": "The `PermitUserEnvironment` option allows users to present environment options to the SSH daemon." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled_rationale", + "name": "rationale", + "prose": "Permitting users the ability to set environment variables through the SSH daemon could potentially allow users to bypass security controls (e.g. setting an execution path that has SSH executing trojan'd programs)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure sshd PermitUserEnvironment is disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + } + ], + "prose": "Run the following command to verify `PermitUserEnviroment` is set to `no`:\n\n```\n# sshd -T | grep permituserenvironment\n\npermituserenvironment no\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `PermitUserEnvironment` parameter to `no` above any `Include` entries as follows:\n\n```\nPermitUserEnvironment no\n```\n\n**Note:** First occurrence of an option takes precedence. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled", + "title": "5.1.22 Ensure sshd UsePAM is enabled", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_sshd_config_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "usepam:match:yes" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled_smt", + "name": "statement", + "prose": "The `UsePAM` directive enables the Pluggable Authentication Module (PAM) interface. If set to `yes` this will enable PAM authentication using `ChallengeResponseAuthentication` and `PasswordAuthentication` directives in addition to PAM account and session module processing for all authentication types." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled_rationale", + "name": "rationale", + "prose": "When `usePAM` is set to `yes`, PAM runs through account and session types properly. This is important if you want to restrict access to services based off of IP, time or other factors of the account. Additionally, you can make sure users inherit certain environment variables on login or disallow access to the server" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure sshd UsePAM is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled_obj" + }, + { + "rel": "script", + "href": "#8a22716d-41ec-59bb-92f7-dc0ea7be08c9" + } + ], + "prose": "Run the following command to verify `UsePAM` is set to `yes`:\n\n```\n# sshd -T | grep -i usepam\n\nusepam yes\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/ssh/sshd_config` file to set the `UsePAM` parameter to `yes` above any `Include` entries as follows:\n\n```\nUsePAM yes\n```\n\n**Note:** First occurrence of an option takes precedence. If Include locations are enabled, used, and order of precedence is understood in your environment, the entry may be created in a file in Include location." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.2_Configure_privilege_escalation", + "title": "Configure privilege escalation", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed", + "title": "5.2.1 Ensure sudo is installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed_smt", + "name": "statement", + "prose": "`sudo` allows a permitted user to execute a command as the superuser or another user, as specified by the security policy. The invoking user's real (not effective) user ID is used to determine the user name with which to query the security policy." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed_rationale", + "name": "rationale", + "prose": "`sudo` supports a plug-in architecture for security policies and input/output logging. Third parties can develop and distribute their own policy and I/O logging plug-ins to work seamlessly with the `sudo` front end. The default security policy is `sudoers`, which is configured via the file `/etc/sudoers` and any entries in `/etc/sudoers.d`.\n\nThe security policy determines what privileges, if any, a user has to run `sudo`. The policy may require that users authenticate themselves with a password or another authentication mechanism. If authentication is required, `sudo` will exit if the user's password is not entered within a configurable time limit. This limit is policy-specific." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure sudo is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed_obj" + } + ], + "prose": "Run the following command to verify that either `sudo` is installed:\n\n```\n# dpkg-query -s sudo &>/dev/null && echo \"sudo is installed\"\n\nsudo is installed\n```\n\n**- OR -**\n\nRun the following command to verify that either `sudo-ldap` is installed:\n\n```\n# dpkg-query -s sudo-ldap &>/dev/null && echo \"sudo-ldap is installed\"\n\nsudo-ldap is installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "First determine is LDAP functionality is required. If so, then install `sudo-ldap`, else install `sudo`.\n\n*Example:*\n\n```\n# apt install sudo\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty", + "title": "5.2.2 Ensure sudo commands use pty", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty_smt", + "name": "statement", + "prose": "`sudo` can be configured to run only from a pseudo terminal (`pseudo-pty`)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty_rationale", + "name": "rationale", + "prose": "Attackers can run a malicious program using `sudo` which would fork a background process that remains even when the main program has finished executing." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty_obj", + "name": "assessment-objective", + "prose": "Ensure sudo commands use pty" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty_obj" + } + ], + "prose": "Verify that `sudo` can only run other commands from a pseudo terminal.\n\nRun the following command to verify `Defaults use_pty` is set:\n\n```\n# grep -rPi -- '^\\h*Defaults\\h+([^#\\n\\r]+,\\h*)?use_pty\\b' /etc/sudoers*\n```\n\nVerify the output matches:\n\n```\n/etc/sudoers:Defaults use_pty\n```\n\nRun the follow command to to verify `Defaults !use_pty` is not set:\n\n```\n# grep -rPi -- '^\\h*Defaults\\h+([^#\\n\\r]+,\\h*)?!use_pty\\b' /etc/sudoers*\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the file `/etc/sudoers` with `visudo` or a file in `/etc/sudoers.d/` with `visudo -f ` and add the following line:\n\n```\nDefaults use_pty\n```\n\nEdit the file `/etc/sudoers` with `visudo` and any files in `/etc/sudoers.d/` with `visudo -f ` and remove any occurrence of `!use_pty`\n\n**Note:**\n\n- sudo will read each file in `/etc/sudoers.d`, skipping file names that end in `~` or contain a `.` character to avoid causing problems with package manager or editor temporary/backup files.\n\n- Files are parsed in sorted lexical order. That is, `/etc/sudoers.d/01_first` will be parsed before `/etc/sudoers.d/10_second`.\n\n- Be aware that because the sorting is lexical, not numeric, `/etc/sudoers.d/1_whoops` would be loaded after `/etc/sudoers.d/10_second`.\n\n- Using a consistent number of leading zeroes in the file names can be used to avoid such problems.\n\nImpact:\n\n**WARNING:** Editing the `sudo` configuration incorrectly can cause `sudo` to stop functioning. Always use `visudo` to modify `sudo` configuration files." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists", + "title": "5.2.3 Ensure sudo log file exists", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists_smt", + "name": "statement", + "prose": "sudo can use a custom log file" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists_rationale", + "name": "rationale", + "prose": "A sudo log file simplifies auditing of sudo commands" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists_obj", + "name": "assessment-objective", + "prose": "Ensure sudo log file exists" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists_obj" + } + ], + "prose": "Run the following command to verify that sudo has a custom log file configured:\n\n```\n# grep -rPsi \"^\\h*Defaults\\h+([^#]+,\\h*)?logfile\\h*=\\h*(\\\"|\\')?\\H+(\\\"|\\')?(,\\h*\\H+\\h*)*\\h*(#.*)?$\" /etc/sudoers*\n```\n\nVerify the output matches:\n\n```\nDefaults logfile=\"/var/log/sudo.log\"\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the file `/etc/sudoers` or a file in `/etc/sudoers.d/` with `visudo` or `visudo -f ` and add the following line:\n\nExample:\n\n```\nDefaults logfile=\"/var/log/sudo.log\"\n```\n\n**Note:**\n\n- sudo will read each file in `/etc/sudoers.d`, skipping file names that end in `~` or contain a `.` character to avoid causing problems with package manager or editor temporary/backup files.\n\n- Files are parsed in sorted lexical order. That is, `/etc/sudoers.d/01_first` will be parsed before `/etc/sudoers.d/10_second`.\n\n- Be aware that because the sorting is lexical, not numeric, `/etc/sudoers.d/1_whoops` would be loaded after `/etc/sudoers.d/10_second`.\n\n- Using a consistent number of leading zeroes in the file names can be used to avoid such problems.\n\nImpact:\n\n**WARNING:** Editing the `sudo` configuration incorrectly can cause `sudo` to stop functioning. Always use `visudo` to modify `sudo` configuration files." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation", + "title": "5.2.4 Ensure users must provide password for privilege escalation", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation_smt", + "name": "statement", + "prose": "The operating system must be configured so that users must provide a password for privilege escalation." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation_rationale", + "name": "rationale", + "prose": "Without (re-)authentication, users may access resources or perform tasks for which they do not have authorization.\n\nWhen operating systems provide the capability to escalate a functional capability, it is critical the user (re-)authenticate." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation_obj", + "name": "assessment-objective", + "prose": "Ensure users must provide password for privilege escalation" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation_obj" + } + ], + "prose": "**Note:** If passwords are not being used for authentication, this is not applicable.\n\nVerify the operating system requires users to supply a password for privilege escalation.\n\nCheck the configuration of the `/etc/sudoers` and `/etc/sudoers.d/*` files with the following command:\n\n```\n# grep -r \"^[^#].*NOPASSWD\" /etc/sudoers*\n```\n\nIf any line is found refer to the remediation procedure below." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Based on the outcome of the audit procedure, use `visudo -f ` to edit the relevant sudoers file.\n\nRemove any line with occurrences of `NOPASSWD` tags in the file.\n\nImpact:\n\nThis will prevent automated processes from being able to elevate privileges." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally", + "title": "5.2.5 Ensure re-authentication for privilege escalation is not disabled globally", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally_smt", + "name": "statement", + "prose": "The operating system must be configured so that users must re-authenticate for privilege escalation." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally_rationale", + "name": "rationale", + "prose": "Without re-authentication, users may access resources or perform tasks for which they do not have authorization.\n\nWhen operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally_obj", + "name": "assessment-objective", + "prose": "Ensure re-authentication for privilege escalation is not disabled globally" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally_obj" + } + ], + "prose": "Verify the operating system requires users to re-authenticate for privilege escalation.\n\nCheck the configuration of the `/etc/sudoers` and `/etc/sudoers.d/*` files with the following command:\n\n```\n# grep -r \"^[^#].*\\!authenticate\" /etc/sudoers*\n```\n\nIf any line is found with a `!authenticate` tag, refer to the remediation procedure below." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the operating system to require users to reauthenticate for privilege escalation.\n\nBased on the outcome of the audit procedure, use `visudo -f ` to edit the relevant sudoers file.\n\nRemove any occurrences of `!authenticate` tags in the file(s)." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly", + "title": "5.2.6 Ensure sudo authentication timeout is configured correctly", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/4" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly_smt", + "name": "statement", + "prose": "`sudo` caches used credentials for a default of 15 minutes. This is for ease of use when there are multiple administrative tasks to perform. The timeout can be modified to suit local security policies.\n\nThis default is distribution specific. See audit section for further information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly_rationale", + "name": "rationale", + "prose": "Setting a timeout value reduces the window of opportunity for unauthorized privileged access to another user." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly_obj", + "name": "assessment-objective", + "prose": "Ensure sudo authentication timeout is configured correctly" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly_obj" + } + ], + "prose": "Ensure that the caching timeout is no more than 15 minutes.\n\nExample:\n\n```\n# grep -roP \"timestamp_timeout=\\K[0-9]*\" /etc/sudoers*\n```\n\nIf there is no `timestamp_timeout` configured in `/etc/sudoers*` then the default is 15 minutes. This default can be checked with:\n\n```\n# sudo -V | grep \"Authentication timestamp timeout:\"\n```\n\n**NOTE:** A value of `-1` means that the timeout is disabled. Depending on the configuration of the `timestamp_type`, this could mean for all terminals / processes of that user and not just that one single terminal session." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "If the currently configured timeout is larger than 15 minutes, edit the file listed in the audit section with `visudo -f ` and modify the entry `timestamp_timeout=` to 15 minutes or less as per your site policy. The value is in minutes. This particular entry may appear on it's own, or on the same line as `env_reset`. See the following two examples:\n\n```\nDefaults env_reset, timestamp_timeout=15\n```\n\n```\nDefaults timestamp_timeout=15\nDefaults env_reset\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted", + "title": "5.2.7 Ensure access to the su command is restricted", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted_smt", + "name": "statement", + "prose": "The `su` command allows a user to run a command or shell as another user. The program has been superseded by `sudo`, which allows for more granular control over privileged access. Normally, the `su` command can be executed by any user. By uncommenting the `pam_wheel.so` statement in `/etc/pam.d/su`, the `su` command will only allow users in a specific groups to execute `su`. This group should be empty to reinforce the use of `sudo` for privileged access." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted_rationale", + "name": "rationale", + "prose": "Restricting the use of `su` , and using `sudo` in its place, provides system administrators better control of the escalation of user privileges to execute privileged commands. The sudo utility also provides a better logging and audit mechanism, as it can log each command executed via `sudo` , whereas `su` can only record that a user executed the `su` program." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted_obj", + "name": "assessment-objective", + "prose": "Ensure access to the su command is restricted" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted_obj" + } + ], + "prose": "Run the following command:\n\n```\n# grep -Pi '^\\h*auth\\h+(?:required|requisite)\\h+pam_wheel\\.so\\h+(?:[^#\\n\\r]+\\h+)?((?!\\2)(use_uid\\b|group=\\H+\\b))\\h+(?:[^#\\n\\r]+\\h+)?((?!\\1)(use_uid\\b|group=\\H+\\b))(\\h+.*)?$' /etc/pam.d/su\n```\n\nVerify the output matches:\n\n```\nauth required pam_wheel.so use_uid group=\n```\n\nRun the following command and verify that the group specified in `` contains no users:\n\n```\n# grep /etc/group\n```\n\nVerify the output does not contain any users in the relevant group:\n\n```\n:x::\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Create an empty group that will be specified for use of the `su` command. The group should be named according to site policy.\n\nExample:\n\n```\n# groupadd sugroup\n```\n\nAdd the following line to the `/etc/pam.d/su` file, specifying the empty group:\n\n```\nauth required pam_wheel.so use_uid group=sugroup\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.3_Pluggable_Authentication_Modules", + "title": "Pluggable Authentication Modules", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.3.1_Configure_PAM_software_packages", + "title": "Configure PAM software packages", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed", + "title": "5.3.1.1 Ensure latest version of pam is installed", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed_smt", + "name": "statement", + "prose": "Updated versions of PAM include additional functionality" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed_rationale", + "name": "rationale", + "prose": "To ensure the system has full functionality and access to the options covered by this Benchmark the latest version of `libpam-runtime` should be installed on the system" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure latest version of pam is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed_obj" + } + ], + "prose": "Run the following command to verify the version of `libpam-runtime` on the system:\n\n```\n# dpkg-query -s libpam-runtime | grep -P -- '^(Status|Version)\\b'\n```\n\nThe output should be similar to:\n\n```\nStatus: install ok installed\nVersion: 1.5.3-5\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** the version of `libpam-runtime` on the system is less than version `1.5.3-5`:\n\nRun the following command to update to the latest version of `PAM`:\n\n```\n# apt upgrade libpam-runtime\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed", + "title": "5.3.1.2 Ensure libpam-modules is installed", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed_smt", + "name": "statement", + "prose": "Pluggable Authentication Modules for PAM" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed_rationale", + "name": "rationale", + "prose": "To ensure the system has full functionality and access to the PAM options covered by this Benchmark" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure libpam-modules is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed_obj" + } + ], + "prose": "Run the following command to verify `libpam-modules` is installed and version `1.5.3-5` or later:\n\n```\n# dpkg-query -s libpam-modules | grep -P -- '^(Status|Version)\\b'\n```\n\nThe output should be similar to:\n\n```\nStatus: install ok installed\nVersion: 1.5.3-5\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** the version of `libpam-modules` on the system is less than version `1.5.3-5`:\n\nRun the following command to update to the latest version of `PAM`:\n\n```\n# apt upgrade libpam-modules\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed", + "title": "5.3.1.3 Ensure libpam-pwquality is installed", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed_smt", + "name": "statement", + "prose": "`libpwquality` provides common functions for password quality checking and scoring them based on their apparent randomness. The library also provides a function for generating random passwords with good pronounceability.\n\nThis module can be plugged into the password stack of a given service to provide some plug-in strength-checking for passwords. The code was originally based on `pam_cracklib` module and the module is backwards compatible with its options." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed_rationale", + "name": "rationale", + "prose": "Strong passwords reduce the risk of systems being hacked through brute force methods." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure libpam-pwquality is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed_obj" + } + ], + "prose": "Run the following command to verify `libpam-pwquality` is installed:\n\n```\n# dpkg-query -s libpam-pwquality | grep -P -- '^(Status|Version)\\b'\n```\n\nThe output should be similar to:\n\n```\nStatus: install ok installed\nVersion: 1.4.5-3+build1\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to install `libpam-pwquality`:\n\n```\n# apt install libpam-pwquality\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.3.2_Configure_pam-auth-update_profiles", + "title": "Configure pam-auth-update profiles", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled", + "title": "5.3.2.1 Ensure pam_unix module is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled_smt", + "name": "statement", + "prose": "`pam_unix` is the standard Unix authentication module. It uses standard calls from the system's libraries to retrieve and set account information as well as authentication. Usually this is obtained from the `/etc/passwd` and if shadow is enabled, the `/etc/shadow` file as well.\n\nThe account component performs the task of establishing the status of the user's account and password based on the following shadow elements: `expire`, `last_change`, `max_change`, `min_change`, `warn_change`. In the case of the latter, it may offer advice to the user on changing their password or, through the `PAM_AUTHTOKEN_REQD` return, delay giving service to the user until they have established a new password. The entries listed above are documented in the shadow(5) manual page. Should the user's record not contain one or more of these entries, the corresponding shadow check is not performed.\n\nThe authentication component performs the task of checking the users credentials (password). The default action of this module is to not permit the user access to a service if their official password is blank." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled_rationale", + "name": "rationale", + "prose": "The system should only provide access after performing authentication of a user." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure pam_unix module is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled_obj" + } + ], + "prose": "Run the following command to verify that `pam_unix` is enabled:\n\n```\n# grep -P -- '\\bpam_unix\\.so\\b' /etc/pam.d/common-{account,session,auth,password}\n```\n\nOutput should be simular to:\n\n```\n/etc/pam.d/common-account:account [success=1 new_authtok_reqd=done default=ignore] pam_unix.so\n/etc/pam.d/common-session:session required pam_unix.so\n/etc/pam.d/common-auth:auth [success=2 default=ignore] pam_unix.so try_first_pass\n/etc/pam.d/common-password:password [success=1 default=ignore] pam_unix.so obscure use_authtok try_first_pass yescrypt\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to enable the `pam_unix` module:\n\n```\n# pam-auth-update --enable unix\n```\n\n**Note:** If a site specific custom profile is being used in your environment to configure PAM that includes the configuration for the `pam_faillock` module, enable that module instead" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled", + "title": "5.3.2.2 Ensure pam_faillock module is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/6/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled_smt", + "name": "statement", + "prose": "The `pam_faillock.so` module maintains a list of failed authentication attempts per user during a specified interval and locks the account in case there were more than the configured number of consecutive failed authentications (this is defined by the `deny` parameter in the faillock configuration). It stores the failure records into per-user files in the tally directory." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled_rationale", + "name": "rationale", + "prose": "Locking out user IDs after n unsuccessful consecutive login attempts mitigates brute force password attacks against your systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure pam_faillock module is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled_obj" + } + ], + "prose": "Run the following commands to verify that `pam_faillock` is enabled:\n\n```\n# grep -P -- '\\bpam_faillock\\.so\\b' /etc/pam.d/common-{auth,account}\n```\n\nOutput should be similar to:\n\n```\n/etc/pam.d/common-auth:auth requisite pam_faillock.so preauth\n/etc/pam.d/common-auth:auth [default=die] pam_faillock.so authfail\n/etc/pam.d/common-account:account required pam_faillock.so\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Create two pam-auth-update profiles in `/usr/share/pam-configs/`:\n\n- Create the `faillock` profile in `/usr/share/pam-configs/` with the following lines:\n\n```\nName: Enable pam_faillock to deny access\nDefault: yes\nPriority: 0\nAuth-Type: Primary\nAuth:\n [default=die] pam_faillock.so authfail\n```\n\n*Example Script:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n arr=('Name: Enable pam_faillock to deny access' 'Default: yes' 'Priority: 0' 'Auth-Type: Primary' 'Auth:' ' [default=die] pam_faillock.so authfail')\n printf '%s\\n' \"${arr[@]}\" > /usr/share/pam-configs/faillock\n}\n```\n\n- Create the `faillock_notify` profile in `/usr/share/pam-configs/` with the following lines:\n\n```\nName: Notify of failed login attempts and reset count upon success\nDefault: yes\nPriority: 1024\nAuth-Type: Primary\nAuth:\n requisite pam_faillock.so preauth\nAccount-Type: Primary\nAccount:\n required pam_faillock.so\n```\n\n*Example Script:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n arr=('Name: Notify of failed login attempts and reset count upon success' 'Default: yes' 'Priority: 1024' 'Auth-Type: Primary' 'Auth:' ' requisite pam_faillock.so preauth' 'Account-Type: Primary' 'Account:' ' required pam_faillock.so')\n printf '%s\\n' \"${arr[@]}\" > /usr/share/pam-configs/faillock_notify\n}\n```\n\nRun the following command to update the `common-auth` and `common-account` PAM files with the new profiles:\n\n```\n# pam-auth-update --enable \n```\n\n*Example:*\n\n```\n# pam-auth-update --enable faillock\n# pam-auth-update --enable faillock_notify\n```\n\n**Note:**\n\n- The name used for the file must be used in the `pam-auth-update --enable` command\n\n- The `Name:` line should be easily recognizable and understood\n\n- The `Priority:` Line is important as it effects the order of the lines in the `/etc/pam.d/` files\n\n- If a site specific custom profile is being used in your environment to configure PAM that includes the configuration for the `pam_faillock` module, enable that module instead" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled", + "title": "5.3.2.3 Ensure pam_pwquality module is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled_smt", + "name": "statement", + "prose": "The `pam_pwquality.so` module performs password quality checking. This module can be plugged into the password stack of a given service to provide strength-checking for passwords. The code was originally based on pam_cracklib module and the module is backwards compatible with its options.\n\nThe action of this module is to prompt the user for a password and check its strength against a system dictionary and a set of rules for identifying poor choices.\n\nThe first action is to prompt for a single password, check its strength and then, if it is considered strong, prompt for the password a second time (to verify that it was typed correctly on the first occasion). All being well, the password is passed on to subsequent modules to be installed as the new authentication token." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled_rationale", + "name": "rationale", + "prose": "Use of a unique, complex passwords helps to increase the time and resources required to compromise the password." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure pam_pwquality module is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled_obj" + } + ], + "prose": "Run the following command to verify that pam_pwhistory is enabled:\n\n```\n# grep -P -- '\\bpam_pwquality\\.so\\b' /etc/pam.d/common-password\n```\n\nOutput should be similar to:\n\n```\npassword requisite pam_pwquality.so retry=3\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to verify the `pam_pwquality.so` line exists in a `pam-auth-update` profile:\n\n```\n# grep -P -- '\\bpam_pwquality\\.so\\b' /usr/share/pam-configs/*\n```\n\nOutput should be similar to:\n\n```\n/usr/share/pam-configs/pwquality: requisite pam_pwquality.so retry=3\n/usr/share/pam-configs/pwquality: requisite pam_pwquality.so retry=3\n```\n\n**- IF -** similar output is returned:\n\nRun the following command to update `/etc/pam.d/common-password` with the returned profile:\n\n```\n# pam-auth-update --enable {PROFILE_NAME}\n```\n\n*Example:*\n\n```\n# pam-auth-update pwquality\n```\n\n**- IF -** similar output is **NOT** returned:\n\nCreate a pam-auth-update profile in `/usr/share/pam-configs/` with the following lines:\n\n```\nName: Pwquality password strength checking\nDefault: yes\nPriority: 1024\nConflicts: cracklib\nPassword-Type: Primary\nPassword:\n requisite pam_pwquality.so retry=3\n```\n\n*Example:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n arr=('Name: Pwquality password strength checking' 'Default: yes' 'Priority: 1024' 'Conflicts: cracklib' 'Password-Type: Primary' 'Password:' ' requisite pam_pwquality.so retry=3')\n printf '%s\\n' \"${arr[@]}\" > /usr/share/pam-configs/pwquality\n}\n```\n\nRun the following command to update `/etc/pam.d/common-password` with the `pwquality` profile:\n\n```\n# pam-auth-update --enable pwquality\n```\n\n**Note:**\n\n- The name used for the file must be used in the `pam-auth-update --enable` command\n\n- The `Name:` line should be easily recognizable and understood\n\n- The `Priority:` Line is important as it effects the order of the lines in the `/etc/pam.d/` files\n\n- If a site specific custom profile is being used in your environment to configure PAM that includes the configuration for the `pam_pwquality` module, enable that module instead" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled", + "title": "5.3.2.4 Ensure pam_pwhistory module is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled_smt", + "name": "statement", + "prose": "The `pam_pwhistory.so` module saves the last passwords for each user in order to force password change history and keep the user from alternating between the same password too frequently.\n\nThis module does not work together with kerberos. In general, it does not make much sense to use this module in conjunction with `NIS` or `LDAP`, since the old passwords are stored on the local machine and are not available on another machine for password history checking." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled_rationale", + "name": "rationale", + "prose": "Use of a unique, complex passwords helps to increase the time and resources required to compromise the password." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure pam_pwhistory module is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled_obj" + } + ], + "prose": "Run the following command to verify that pam_pwhistory is enabled:\n\n```\n# grep -P -- '\\bpam_pwhistory\\.so\\b' /etc/pam.d/common-password\n```\n\nOutput should be similar to:\n\n```\npassword requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to verify the `pam_pwquality.so` line exists in a `pam-auth-update` profile:\n\n```\n# grep -P -- '\\bpam_pwhistory\\.so\\b' /usr/share/pam-configs/*\n```\n\nOutput should be similar to:\n\n```\n/usr/share/pam-configs/pwhistory: requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok\n```\n\n**- IF -** similar output is returned:\n\nRun the following command to update `/etc/pam.d/common-password` with the returned profile:\n\n```\n# pam-auth-update --enable {PROFILE_NAME}\n```\n\n*Example:*\n\n```\n# pam-auth-update pwhistory\n```\n\n**- IF -** similar output is **NOT** returned:\n\nCreate a `pwhistory` profile in `/usr/share/pam-configs/` with the following lines:\n\n```\nName: pwhistory password history checking\nDefault: yes\nPriority: 1024\nPassword-Type: Primary\nPassword: requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok\n```\n\n*Example Script:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n arr=('Name: pwhistory password history checking' 'Default: yes' 'Priority: 1024' 'Password-Type: Primary' 'Password:' ' requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok')\n printf '%s\\n' \"${arr[@]}\" > /usr/share/pam-configs/pwhistory\n}\n```\n\nRun the following command to update `/etc/pam.d/common-password` with the `pwhistory` profile:\n\n```\n# pam-auth-update --enable pwhistory\n```\n\n**Note:**\n\n- The name used for the file must be used in the `pam-auth-update --enable` command\n\n- The `Name:` line should be easily recognizable and understood\n\n- The `Priority:` Line is important as it effects the order of the lines in the `/etc/pam.d/` files\n\n- If a site specific custom profile is being used in your environment to configure PAM that includes the configuration for the `pam_pwhistory` module, enable that module instead" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.3.3_Configure_PAM_Arguments", + "title": "Configure PAM Arguments", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.3.3.1_Configure_pam_faillock_module", + "title": "Configure pam_faillock module", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured", + "title": "5.3.3.1.1 Ensure password failed attempts lockout is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/6/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured_smt", + "name": "statement", + "prose": "The `deny=` option will deny access if the number of consecutive authentication failures for this user during the recent interval exceeds **." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured_rationale", + "name": "rationale", + "prose": "Locking out user IDs after *n* unsuccessful consecutive login attempts mitigates brute force password attacks against your systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure password failed attempts lockout is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured_obj" + } + ], + "prose": "Run the following command to verify that Number of failed logon attempts before the account is locked is no greater than `5` and meets local site policy:\n\n```\n# grep -Pi -- '^\\h*deny\\h*=\\h*[1-5]\\b' /etc/security/faillock.conf\n\ndeny = 5\n```\n\nRun the following command to verify that the `deny` argument has not been set, or `5` or less and meets local site policy:\n\n```\n# grep -Pi -- '^\\h*auth\\h+(requisite|required|sufficient)\\h+pam_faillock\\.so\\h+([^#\\n\\r]+\\h+)?deny\\h*=\\h*(0|[6-9]|[1-9][0-9]+)\\b' /etc/pam.d/common-auth\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Create or edit the following line in `/etc/security/faillock.conf` setting the `deny` option to `5` or less:\n\n```\ndeny = 5\n```\n\nRun the following command:\n\n```\n# grep -Pl -- '\\bpam_faillock\\.so\\h+([^#\\n\\r]+\\h+)?deny\\b' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `deny=` arguments from the `pam_faillock.so` line(s):" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured", + "title": "5.3.3.1.2 Ensure password unlock time is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/6/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured_smt", + "name": "statement", + "prose": "`unlock_time=` - The access will be re-enabled after ** seconds after the lock out. The value `0` has the same meaning as value never - the access will not be re-enabled without resetting the faillock entries by the faillock(8) command.\n\n**Note:**\n\n- The default directory that pam_faillock uses is usually cleared on system boot so the access will be also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the dir option.\n\n- It is usually undesirable to permanently lock out users as they can become easily a target of denial of service attack unless the usernames are random and kept secret to potential attackers.\n\n- The maximum configurable value for `unlock_time` is `604800`" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured_rationale", + "name": "rationale", + "prose": "Locking out user IDs after *n* unsuccessful consecutive login attempts mitigates brute force password attacks against your systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure password unlock time is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured_obj" + } + ], + "prose": "Run the following command to verify that the time in seconds before the account is unlocked is either `0` (never) or `900` (15 minutes) or more and meets local site policy:\n\n```\n# grep -Pi -- '^\\h*unlock_time\\h*=\\h*(0|9[0-9][0-9]|[1-9][0-9]{3,})\\b' /etc/security/faillock.conf\n\nunlock_time = 900\n```\n\nRun the following command to verify that the `unlock_time` argument has not been set, or is either `0` (never) or `900` (15 minutes) or more and meets local site policy:\n\n```\n# grep -Pi -- '^\\h*auth\\h+(requisite|required|sufficient)\\h+pam_faillock\\.so\\h+([^#\\n\\r]+\\h+)?unlock_time\\h*=\\h*([1-9]|[1-9][0-9]|[1-8][0-9][0-9])\\b' /etc/pam.d/common-auth\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set password unlock time to conform to site policy. `unlock_time` should be `0` (never), or `900` seconds or greater.\n\nEdit `/etc/security/faillock.conf` and update or add the following line:\n\n```\nunlock_time = 900\n```\n\nRun the following command: remove the `unlock_time` argument from the `pam_faillock.so` module in the PAM files:\n\n```\n# grep -Pl -- '\\bpam_faillock\\.so\\h+([^#\\n\\r]+\\h+)?unlock_time\\b' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `unlock_time=` argument from the `pam_faillock.so` line(s):\n\nImpact:\n\nUse of `unlock_time=0` may allow an attacker to cause denial of service to legitimate users. This will also require a systems administrator with elevated privileges to unlock the account." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.3_Ensure_password_failed_attempts_lockout_includes_root_account", + "title": "5.3.3.1.3 Ensure password failed attempts lockout includes root account", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/6/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.3_Ensure_password_failed_attempts_lockout_includes_root_account_smt", + "name": "statement", + "prose": "`even_deny_root` - Root account can become locked as well as regular accounts\n\n`root_unlock_time=n` - This option implies even_deny_root option. Allow access after n seconds to root account after the account is locked. In case the option is not specified the value is the same as of the unlock_time option." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.3_Ensure_password_failed_attempts_lockout_includes_root_account_rationale", + "name": "rationale", + "prose": "Locking out user IDs after n unsuccessful consecutive login attempts mitigates brute force password attacks against your systems." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.3_Ensure_password_failed_attempts_lockout_includes_root_account_obj", + "name": "assessment-objective", + "prose": "Ensure password failed attempts lockout includes root account" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.3_Ensure_password_failed_attempts_lockout_includes_root_account_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.3_Ensure_password_failed_attempts_lockout_includes_root_account_obj" + } + ], + "prose": "Run the following command to verify that `even_deny_root` and/or `root_unlock_time` is enabled:\n\n```\n# grep -Pi -- '^\\h*(even_deny_root|root_unlock_time\\h*=\\h*\\d+)\\b' /etc/security/faillock.conf\n```\n\n*Example output:*\n\n```\neven_deny_root\n\n--AND/OR--\n\nroot_unlock_time = 60\n```\n\nRun the following command to verify that **- IF -** `root_unlock_time` is set, it is set to `60` (One minute) or more:\n\n```\n# grep -Pi -- '^\\h*root_unlock_time\\h*=\\h*([1-9]|[1-5][0-9])\\b' /etc/security/faillock.conf\n```\n\nNothing should be returned\n\nRun the following command to check the `pam_faillock.so` module for the `root_unlock_time` argument. Verify **-IF-** `root_unlock_time` is set, it is set to `60` (One minute) or more:\n\n```\n# grep -Pi -- '^\\h*auth\\h+([^#\\n\\r]+\\h+)pam_faillock\\.so\\h+([^#\\n\\r]+\\h+)?root_unlock_time\\h*=\\h*([1-9]|[1-5][0-9])\\b' /etc/pam.d/common-auth\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.3_Ensure_password_failed_attempts_lockout_includes_root_account_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/security/faillock.conf`:\n\n- Remove or update any line containing `root_unlock_time`, **- OR -** set it to a value of `60` or more\n\n- Update or add the following line:\n\n```\neven_deny_root\n```\n\nRun the following command:\n\n```\n# grep -Pl -- '\\bpam_faillock\\.so\\h+([^#\\n\\r]+\\h+)?(even_deny_root|root_unlock_time)' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `even_deny_root` and `root_unlock_time` arguments from the `pam_faillock.so` line(s):\n\nImpact:\n\nUse of `unlock_time=0` or `root_unlock_time=0` may allow an attacker to cause denial of service to legitimate users." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.3.3.2_Configure_pam_pwquality_module", + "title": "Configure pam_pwquality module", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured", + "title": "5.3.3.2.1 Ensure password number of changed characters is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured_smt", + "name": "statement", + "prose": "The `pwquality` `difok` option sets the number of characters in a password that must not be present in the old password." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured_rationale", + "name": "rationale", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure password number of changed characters is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured_obj" + } + ], + "prose": "Run the following command to verify that the `difok` option is set to `2` or more and follows local site policy:\n\n```\n# grep -Psi -- '^\\h*difok\\h*=\\h*([2-9]|[1-9][0-9]+)\\b' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```\n\n*Example output:*\n\n```\n/etc/security/pwquality.conf.d/50-pwdifok.conf:difok = 2\n```\n\nVerify returned value(s) are `2` or more and meet local site policy\n\nRun the following command to verify that `difok` is not set, is `2` or more, and conforms to local site policy:\n\n```\n# grep -Psi -- '^\\h*password\\h+(requisite|required|sufficient)\\h+pam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?difok\\h*=\\h*([0-1])\\b' /etc/pam.d/common-password\n```\n\nNothing should be returned\n\n**Note:**\n\n- settings should be configured in only **one** location for clarity\n\n- Settings observe an order of precedence:\n\n- module arguments override the settings in the `/etc/security/pwquality.conf` configuration file\n\n- settings in the `/etc/security/pwquality.conf` configuration file override settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory\n\n- settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory are read in canonical order, with last read file containing the setting taking precedence\n\n- It is recommended that settings be configured in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory for clarity, convenience, and durability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Create or modify a file ending in `.conf` in the `/etc/security/pwquality.conf.d/` directory or the file `/etc/security/pwquality.conf` and add or modify the following line to set `difok` to `2` or more. Ensure setting conforms to local site policy:\n\n*Example:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*difok\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"difok = 2\" > /etc/security/pwquality.conf.d/50-pwdifok.conf\n}\n```\n\nRun the following command:\n\n```\n# grep -Pl -- '\\bpam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?difok\\b' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `difok` argument from the `pam_pwquality.so` line(s):" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured", + "title": "5.3.3.2.2 Ensure minimum password length is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured_smt", + "name": "statement", + "prose": "The minimum password length setting determines the lowers number of characters that make up a password for a user account. There are many different theories about how to determine the best password length for an organization, but perhaps \"passphrase\" is a better term than \"password\".\n\nThe `minlen` option sets the minimum acceptable size for the new password (plus one if credits are not disabled which is the default). Cannot be set to lower value than 6." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured_rationale", + "name": "rationale", + "prose": "Strong passwords help protect systems from password attacks. Types of password attacks include dictionary attacks, which attempt to use common words and phrases, and brute force attacks, which try every possible combination of characters. Also attackers may try to obtain the account database so they can use tools to discover the accounts and passwords." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure minimum password length is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured_obj" + } + ], + "prose": "Run the following command to verify that password length is `14` or more characters, and conforms to local site policy:\n\n```\n# grep -Psi -- '^\\h*minlen\\h*=\\h*(1[4-9]|[2-9][0-9]|[1-9][0-9]{2,})\\b' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```\n\n*Example output:*\n\n```\n/etc/security/pwquality.conf.d/50-pwlength.conf:minlen = 14\n```\n\nVerify returned value(s) are no less than `14` characters and meet local site policy\n\nRun the following command to verify that `minlen` is not set, or is `14` or more characters, and conforms to local site policy:\n\n```\n# grep -Psi -- '^\\h*password\\h+(requisite|required|sufficient)\\h+pam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?minlen\\h*=\\h*([0-9]|1[0-3])\\b' /etc/pam.d/system-auth /etc/pam.d/common-password\n```\n\nNothing should be returned\n\n**Note:**\n\n- settings should be configured in only **one** location for clarity\n\n- Settings observe an order of precedence:\n\n- module arguments override the settings in the `/etc/security/pwquality.conf` configuration file\n\n- settings in the `/etc/security/pwquality.conf` configuration file override settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory\n\n- settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory are read in canonical order, with last read file containing the setting taking precedence\n\n- It is recommended that settings be configured in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory for clarity, convenience, and durability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Create or modify a file ending in `.conf` in the `/etc/security/pwquality.conf.d/` directory or the file `/etc/security/pwquality.conf` and add or modify the following line to set password length of `14` or more characters. Ensure that password length conforms to local site policy:\n\n*Example:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*minlen\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"minlen = 14\" > /etc/security/pwquality.conf.d/50-pwlength.conf\n}\n```\n\nRun the following command:\n\n```\n# grep -Pl -- '\\bpam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?minlen\\b' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `minlen` argument from the `pam_pwquality.so` line(s):\n\nImpact:\n\nIn general, it is true that longer passwords are better (harder to crack), but it is also true that forced password length requirements can cause user behavior that is predictable and undesirable. For example, requiring users to have a minimum 16-character password may cause them to choose repeating patterns like fourfourfourfour or passwordpassword that meet the requirement but aren’t hard to guess. Additionally, length requirements increase the chances that users will adopt other insecure practices, like writing them down, re-using them or storing them unencrypted in their documents.\n\nHaving a reasonable minimum length with no maximum character limit increases the resulting\naverage password length used (and therefore the strength).6" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured", + "title": "5.3.3.2.3 Ensure password complexity is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured_smt", + "name": "statement", + "prose": "Password complexity can be set through:\n\n- `minclass` - The minimum number of classes of characters required in a new password. (digits, uppercase, lowercase, others). e.g. `minclass = 4` requires digits, uppercase, lower case, and special characters.\n\n- `dcredit` - The maximum credit for having digits in the new password. If less than `0` it is the minimum number of digits in the new password. e.g. `dcredit = -1` requires at least one digit\n\n- `ucredit` - The maximum credit for having uppercase characters in the new password. If less than `0` it is the minimum number of uppercase characters in the new password. e.g. `ucredit = -1` requires at least one uppercase character\n\n- `ocredit` - The maximum credit for having other characters in the new password. If less than `0` it is the minimum number of other characters in the new password. e.g. `ocredit = -1` requires at least one special character\n\n- `lcredit` - The maximum credit for having lowercase characters in the new password. If less than `0` it is the minimum number of lowercase characters in the new password. e.g. `lcredit = -1` requires at least one lowercase character" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured_rationale", + "name": "rationale", + "prose": "Strong passwords protect systems from being hacked through brute force methods.\n\nRequiring at least one non-alphabetic character increases the search space beyond pure dictionary words, which makes the resulting password harder to crack.\n\nForcing users to choose an excessively complex password, e.g. some combination of upper-case, lower-case, numbers, and special characters, has a negative impact. It places an extra burden on users and many will use predictable patterns (for example, a capital letter in the first position, followed by lowercase letters, then one or two numbers, and a “special character” at the end). Attackers know this, so dictionary attacks will often contain these common patterns and use the most common substitutions like, $ for s, @ for a, 1 for l, 0 for o." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure password complexity is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured_obj" + }, + { + "rel": "script", + "href": "#0af82d1a-78bc-5eaf-b3d8-fec15d1acdd1" + } + ], + "prose": "Run the following command to verify:\n\n- `dcredit`, `ucredit`, `lcredit`, and `ocredit` are not set to a value greater than `0`\n\n- Complexity conforms to local site policy:\n\n```\n# grep -Psi -- '^\\h*(minclass|[dulo]credit)\\b' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```\n\n*Example output:*\n\n```\n/etc/security/pwquality.conf.d/50-pwcomplexity.conf:minclass = 3\n/etc/security/pwquality.conf.d/50-pwcomplexity.conf:ucredit = -2\n/etc/security/pwquality.conf.d/50-pwcomplexity.conf:lcredit = -2\n/etc/security/pwquality.conf.d/50-pwcomplexity.conf:dcredit = -1\n/etc/security/pwquality.conf.d/50-pwcomplexity.conf:ocredit = 0\n```\n\nThe example represents a requirement of three character classes, with passwords requiring two upper case, two lower case, and one numeric character.\n\nRun the following command to verify that module arguments in the configuration file(s) are not being overridden by arguments in `/etc/pam.d/common-password`:\n\n```\n# grep -Psi -- '^\\h*password\\h+(requisite|required|sufficient)\\h+pam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?(minclass=\\d*|[dulo]credit=-?\\d*)\\b' /etc/pam.d/common-password\n```\n\nNothing should be returned\n\n**Note:**\n\n- settings should be configured in only **one** location for clarity\n\n- Settings observe an order of precedence:\n\n- module arguments override the settings in the `/etc/security/pwquality.conf` configuration file\n\n- settings in the `/etc/security/pwquality.conf` configuration file override settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory\n\n- settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory are read in canonical order, with last read file containing the setting taking precedence\n\n- It is recommended that settings be configured in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory for clarity, convenience, and durability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command:\n\n```\n# grep -Pl -- '\\bpam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?(minclass|[dulo]credit)\\b' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `minclass`, `dcredit`, `ucredit`, `lcredit`, and `ocredit` arguments from the `pam_pwquality.so` line(s)\n\nCreate or modify a file ending in `.conf` in the `/etc/security/pwquality.conf.d/` directory or the file `/etc/security/pwquality.conf` and add or modify the following line(s) to set complexity according to local site policy:\n\n- `minclass = _N_`\n\n- `dcredit = _N_` # Value should be either `0` or a number proceeded by a minus (`-`) symbol\n\n- `ucredit = -1` # Value should be either `0` or a number proceeded by a minus (`-`) symbol\n\n- `ocredit = -1` # Value should be either `0` or a number proceeded by a minus (`-`) symbol\n\n- `lcredit = -1` # Value should be either `0` or a number proceeded by a minus (`-`) symbol\n\n*Example 1 - Set `minclass = 3`:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*minclass\\s*=/# &/' /etc/security/pwquality.conf\n sed -ri 's/^\\s*[dulo]credit\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"minclass = 3\" > /etc/security/pwquality.conf.d/50-pwcomplexity.conf\n}\n```\n\n*Example 2 - set `dcredit = -1`, `ucredit = -1`, and `lcredit = -1`:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*minclass\\s*=/# &/' /etc/security/pwquality.conf\n sed -ri 's/^\\s*[dulo]credit\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '%s\\n' \"dcredit = -1\" \"ucredit = -1\" \"lcredit = -1\" > /etc/security/pwquality.conf.d/50-pwcomplexity.conf\n}\n```\n\nImpact:\n\nPasswords that are too complex in nature make it harder for users to remember, leading to bad practices. In addition, composition requirements provide no defense against common attack types such as social engineering or insecure storage of passwords" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured", + "title": "5.3.3.2.4 Ensure password same consecutive characters is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured_smt", + "name": "statement", + "prose": "The `pwquality` `maxrepeat` option sets the maximum number of allowed same consecutive characters in a new password." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured_rationale", + "name": "rationale", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure password same consecutive characters is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured_obj" + } + ], + "prose": "Run the following command to verify that the `maxrepeat` option is set to `3` or less, not `0`, and follows local site policy:\n\n```\n# grep -Psi -- '^\\h*maxrepeat\\h*=\\h*[1-3]\\b' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```\n\n*Example output:*\n\n```\n/etc/security/pwquality.conf.d/50-pwrepeat.conf:maxrepeat = 3\n```\n\nVerify returned value(s) are `3` or less, not `0`, and meet local site policy\n\nRun the following command to verify that `maxrepeat` is not set, is `3` or less, not `0`, and conforms to local site policy:\n\n```\n# grep -Psi -- '^\\h*password\\h+(requisite|required|sufficient)\\h+pam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?maxrepeat\\h*=\\h*(0|[4-9]|[1-9][0-9]+)\\b' /etc/pam.d/common-password\n```\n\nNothing should be returned\n\n**Note:**\n\n- settings should be configured in only **one** location for clarity\n\n- Settings observe an order of precedence:\n\n- module arguments override the settings in the `/etc/security/pwquality.conf` configuration file\n\n- settings in the `/etc/security/pwquality.conf` configuration file override settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory\n\n- settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory are read in canonical order, with last read file containing the setting taking precedence\n\n- It is recommended that settings be configured in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory for clarity, convenience, and durability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Create or modify a file ending in `.conf` in the `/etc/security/pwquality.conf.d/` directory or the file `/etc/security/pwquality.conf` and add or modify the following line to set `maxrepeat` to `3` or less and not `0`. Ensure setting conforms to local site policy:\n\n*Example:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*maxrepeat\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"maxrepeat = 3\" > /etc/security/pwquality.conf.d/50-pwrepeat.conf\n}\n```\n\nRun the following command:\n\n```\n# grep -Pl -- '\\bpam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?maxrepeat\\b' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `maxrepeat` argument from the `pam_pwquality.so` line(s):" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured", + "title": "5.3.3.2.5 Ensure password maximum sequential characters is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured_smt", + "name": "statement", + "prose": "The `pwquality` `maxsequence` option sets the maximum length of monotonic character sequences in the new password. Examples of such sequence are `12345` or `fedcb`. The check is disabled if the value is `0`.\n\n**Note:** Most such passwords will not pass the simplicity check unless the sequence is only a minor part of the password." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured_rationale", + "name": "rationale", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure password maximum sequential characters is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured_obj" + } + ], + "prose": "Run the following command to verify that the `maxsequence` option is set to `3` or less, not `0`, and follows local site policy:\n\n```\n# grep -Psi -- '^\\h*maxsequence\\h*=\\h*[1-3]\\b' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```\n\n*Example output:*\n\n```\n/etc/security/pwquality.conf.d/50-pwmaxsequence.conf:maxsequence = 3\n```\n\nVerify returned value(s) are `3` or less, not `0`, and meet local site policy\n\nRun the following command to verify that `maxsequence` is not set, is `3` or less, not `0`, and conforms to local site policy:\n\n```\n# grep -Psi -- '^\\h*password\\h+(requisite|required|sufficient)\\h+pam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?maxsequence\\h*=\\h*(0|[4-9]|[1-9][0-9]+)\\b' /etc/pam.d/common-password\n```\n\nNothing should be returned\n\n**Note:**\n\n- settings should be configured in only **one** location for clarity\n\n- Settings observe an order of precedence:\n\n- module arguments override the settings in the `/etc/security/pwquality.conf` configuration file\n\n- settings in the `/etc/security/pwquality.conf` configuration file override settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory\n\n- settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory are read in canonical order, with last read file containing the setting taking precedence\n\n- It is recommended that settings be configured in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory for clarity, convenience, and durability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Create or modify a file ending in `.conf` in the `/etc/security/pwquality.conf.d/` directory or the file `/etc/security/pwquality.conf` and add or modify the following line to set `maxsequence` to `3` or less and not `0`. Ensure setting conforms to local site policy:\n\n*Example:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n sed -ri 's/^\\s*maxsequence\\s*=/# &/' /etc/security/pwquality.conf\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s' \"maxsequence = 3\" > /etc/security/pwquality.conf.d/50-pwmaxsequence.conf\n}\n```\n\nRun the following command:\n\n```\n# grep -Pl -- '\\bpam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?maxsequence\\b' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `maxsequence` argument from the `pam_pwquality.so` line(s):" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled", + "title": "5.3.3.2.6 Ensure password dictionary check is enabled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled_smt", + "name": "statement", + "prose": "The `pwquality` `dictcheck` option sets whether to check for the words from the `cracklib` dictionary." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled_rationale", + "name": "rationale", + "prose": "If the operating system allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity for successful guesses, and brute-force attacks." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure password dictionary check is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled_obj" + } + ], + "prose": "Run the following command to verify that the `dictcheck` option is not set to `0` (disabled) in a pwquality configuration file:\n\n```\n# grep -Psi -- '^\\h*dictcheck\\h*=\\h*0\\b' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```\n\nNothing should be returned\n\nRun the following command to verify that the `dictcheck` option is not set to `0` (disabled) as a module argument in a PAM file:\n\n```\n# grep -Psi -- '^\\h*password\\h+(requisite|required|sufficient)\\h+pam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?dictcheck\\h*=\\h*0\\b' /etc/pam.d/common-password\n```\n\nNothing should be returned\n\n**Note:**\n\n- Settings observe an order of precedence:\n\n- module arguments override the settings in the `/etc/security/pwquality.conf` configuration file\n\n- settings in the `/etc/security/pwquality.conf` configuration file override settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory\n\n- settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory are read in canonical order, with last read file containing the setting taking precedence\n\n- It is recommended that settings be configured in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory for clarity, convenience, and durability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit any file ending in `.conf` in the `/etc/security/pwquality.conf.d/` directory and/or the file `/etc/security/pwquality.conf` and comment out or remove any instance of `dictcheck = 0`:\n\n*Example:*\n\n```\n# sed -ri 's/^\\s*dictcheck\\s*=/# &/' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```\n\nRun the following command:\n\n```\n# grep -Pl -- '\\bpam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?dictcheck\\b' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `dictcheck` argument from the `pam_pwquality.so` line(s)" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced", + "title": "5.3.3.2.7 Ensure password quality checking is enforced", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced_smt", + "name": "statement", + "prose": "The `pam_pwquality` module can be configured to either reject a password if it fails the checks, or only print a warning.\n\nThis is configured by setting the `enforcing=` argument. If nonzero, a password will be rejected if it fails the checks, otherwise only a warning message will be provided.\n\nThis setting applies only to the pam_pwquality module and possibly other applications that explicitly change their behavior based on it. It does not affect pwmake(1) and pwscore(1)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced_rationale", + "name": "rationale", + "prose": "Strong passwords help protect systems from password attacks. Types of password attacks include dictionary attacks, which attempt to use common words and phrases, and brute force attacks, which try every possible combination of characters. Also attackers may try to obtain the account database so they can use tools to discover the accounts and passwords." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced_obj", + "name": "assessment-objective", + "prose": "Ensure password quality checking is enforced" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced_obj" + } + ], + "prose": "Run the following command to verify that `enforcing=0` has not been set in a `pwquality` configuration file:\n\n```\n# grep -PHsi -- '^\\h*enforcing\\h*=\\h*0\\b' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```\n\nNothing should be returned\n\nRun the following command to verify that the `enforcing=0` argument has not been set on the `pam_pwquality` module:\n\n```\n# grep -PHsi -- '^\\h*password\\h+[^#\\n\\r]+\\h+pam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?enforcing=0\\b' /etc/pam.d/common-password\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command:\n\n```\n# grep -Pl -- '\\bpam_pwquality\\.so\\h+([^#\\n\\r]+\\h+)?enforcing=0\\b' /usr/share/pam-configs/*\n```\n\nEdit any returned files and remove the `enforcing=0` argument from the `pam_pwquality.so` line(s)\n\nEdit `/etc/security/pwquality.conf` and all files ending in `.conf` in the `/etc/security/pwquality.conf.d/` directory and remove or comment out any line containing the `enforcing = 0` argument:\n\n*Example:*\n\n```\n# sed -ri 's/^\\s*enforcing\\s*=\\s*0/# &/' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user", + "title": "5.3.3.2.8 Ensure password quality is enforced for the root user", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user_smt", + "name": "statement", + "prose": "If the `pwquality` `enforce_for_root` option is enabled, the module will return error on failed check even if the user changing the password is root.\n\nThis option is off by default which means that just the message about the failed check is printed but root can change the password anyway.\n\n**Note:** The root is not asked for an old password so the checks that compare the old and new password are not performed." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user_rationale", + "name": "rationale", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.\n\nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user_obj", + "name": "assessment-objective", + "prose": "Ensure password quality is enforced for the root user" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user_obj" + } + ], + "prose": "Run the following command to verify that the `enforce_for_root` option is enabled in a pwquality configuration file:\n\n```\n# grep -Psi -- '^\\h*enforce_for_root\\b' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/*.conf\n```\n\n*Example output:*\n\n```\n/etc/security/pwquality.conf.d/50-pwroot.conf:enforce_for_root\n```\n\n**Note:**\n\n- Settings observe an order of precedence:\n\n- module arguments override the settings in the `/etc/security/pwquality.conf` configuration file\n\n- settings in the `/etc/security/pwquality.conf` configuration file override settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory\n\n- settings in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory are read in canonical order, with last read file containing the setting taking precedence\n\n- It is recommended that settings be configured in a `.conf` file in the `/etc/security/pwquality.conf.d/` directory for clarity, convenience, and durability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit or add the following line in a `*.conf` file in `/etc/security/pwquality.conf.d` or in `/etc/security/pwquality.conf`:\n\n*Example:*\n\n```\n#!/urs/bin/env bash\n\n{\n [ ! -d /etc/security/pwquality.conf.d/ ] && mkdir /etc/security/pwquality.conf.d/\n printf '\\n%s\\n' \"enforce_for_root\" > /etc/security/pwquality.conf.d/50-pwroot.conf\n}\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.3.3.3_Configure_pam_pwhistory_module", + "title": "Configure pam_pwhistory module", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured", + "title": "5.3.3.3.1 Ensure password history remember is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured_smt", + "name": "statement", + "prose": "The `/etc/security/opasswd` file stores the users' old passwords and can be checked to ensure that users are not recycling recent passwords. The number of passwords remembered is set via the remember argument value in set for the `pam_pwhistory` module.\n\n- remember= - `` is the number of old passwords to remember" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured_rationale", + "name": "rationale", + "prose": "Requiring users not to reuse their passwords make it less likely that an attacker will be able to guess the password or use a compromised password.\n\n**Note:** These change only apply to accounts configured on the local system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure password history remember is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured_obj" + } + ], + "prose": "Run the following command and verify:\n\n- The `pwhistory` line in `/etc/pam.d/common-password` includes `remember=`\n\n- The value of is `24` or more\n\n- The value meets local site policy\n\n```\n# grep -Psi -- '^\\h*password\\h+[^#\\n\\r]+\\h+pam_pwhistory\\.so\\h+([^#\\n\\r]+\\h+)?remember=\\d+\\b' /etc/pam.d/common-password\n```\n\nOutput should be similar to:\n\n```\npassword requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command:\n\n```\n# awk '/Password-Type:/{ f = 1;next } /-Type:/{ f = 0 } f {if (/pam_pwhistory\\.so/) print FILENAME}' /usr/share/pam-configs/*\n```\n\nEdit any returned files and edit or add the `remember=` argument, with a value of `24` or more, that meets local site policy to the `pam_pwhistory` line in the `Password` section:\n\n*Example File:*\n\n```\nName: pwhistory password history checking\nDefault: yes\nPriority: 1024\nPassword-Type: Primary\nPassword:\n requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok # <- **ensure line includes remember=**\n```\n\nRun the following command to update the files in the `/etc/pam.d/` directory:\n\n```\n# pam-auth-update --enable \n```\n\n*Example:*\n\n```\n# pam-auth-update --enable pwhistory\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user", + "title": "5.3.3.3.2 Ensure password history is enforced for the root user", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user_smt", + "name": "statement", + "prose": "If the `pwhistory` `enforce_for_root` option is enabled, the module will enforce password history for the root user as well" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user_rationale", + "name": "rationale", + "prose": "Requiring users not to reuse their passwords make it less likely that an attacker will be able to guess the password or use a compromised password\n\n**Note:** These change only apply to accounts configured on the local system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user_obj", + "name": "assessment-objective", + "prose": "Ensure password history is enforced for the root user" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user_obj" + } + ], + "prose": "Run the following command to verify that the `enforce_for_root` argument is exists on the `pwhistory` line in `/etc/pam.d/common-password`:\n\n```\n# grep -Psi -- '^\\h*password\\h+[^#\\n\\r]+\\h+pam_pwhistory\\.so\\h+([^#\\n\\r]+\\h+)?enforce_for_root\\b' /etc/pam.d/common-password\n```\n\nOutput should be similar to:\n\n```\npassword requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command:\n\n```\n# awk '/Password-Type:/{ f = 1;next } /-Type:/{ f = 0 } f {if (/pam_pwhistory\\.so/) print FILENAME}' /usr/share/pam-configs/*\n```\n\nEdit any returned files and add the `enforce_for_root` argument to the `pam_pwhistory` line in the `Password` section:\n\n*Example File:*\n\n```\nName: pwhistory password history checking\nDefault: yes\nPriority: 1024\nPassword-Type: Primary\nPassword:\n requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok # <- **ensure line includes enforce_for_root**\n```\n\nRun the following command to update the files in the `/etc/pam.d/` directory:\n\n```\n# pam-auth-update --enable \n```\n\n*Example:*\n\n```\n# pam-auth-update --enable pwhistory\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok", + "title": "5.3.3.3.3 Ensure pam_pwhistory includes use_authtok", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/11" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok_smt", + "name": "statement", + "prose": "`use_authtok` - When password changing enforce the module to set the new password to the one provided by a previously stacked password module" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok_rationale", + "name": "rationale", + "prose": "`use_authtok` allows multiple pam modules to confirm a new password before it is accepted." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok_obj", + "name": "assessment-objective", + "prose": "Ensure pam_pwhistory includes use_authtok" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok_obj" + } + ], + "prose": "Run the following command to verify that the `use_authtok` argument exists on the `pwhistory` line in `/etc/pam.d/common-password`:\n\n```\n# grep -Psi -- '^\\h*password\\h+[^#\\n\\r]+\\h+pam_pwhistory\\.so\\h+([^#\\n\\r]+\\h+)?use_authtok\\b' /etc/pam.d/common-password\n```\n\nOutput should be similar to:\n\n```\npassword requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command:\n\n```\n# awk '/Password-Type:/{ f = 1;next } /-Type:/{ f = 0 } f {if (/pam_pwhistory\\.so/) print FILENAME}' /usr/share/pam-configs/*\n```\n\nEdit any returned files and add the `use_authtok` argument to the `pam_pwhistory` line in the `Password` section:\n\n*Example File:*\n\n```\nName: pwhistory password history checking\nDefault: yes\nPriority: 1024\nPassword-Type: Primary\nPassword:\n requisite pam_pwhistory.so remember=24 enforce_for_root try_first_pass use_authtok # <- **ensure line includes use_authtok**\n```\n\nRun the following command to update the files in the `/etc/pam.d/` directory:\n\n```\n# pam-auth-update --enable \n```\n\n*Example:*\n\n```\n# pam-auth-update --enable pwhistory\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.3.3.4_Configure_pam_unix_module", + "title": "Configure pam_unix module", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok", + "title": "5.3.3.4.1 Ensure pam_unix does not include nullok", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok_smt", + "name": "statement", + "prose": "The `nullok` argument overrides the default action of `pam_unix.so` to not permit the user access to a service if their official password is blank." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok_rationale", + "name": "rationale", + "prose": "Using a strong password is essential to helping protect personal and sensitive information from unauthorized access" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok_obj", + "name": "assessment-objective", + "prose": "Ensure pam_unix does not include nullok" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok_obj" + } + ], + "prose": "Run the following command to verify that the `nullok` argument is not set on the `pam_unix.so` module:\n\n```\n# grep -PH -- '^\\h*^\\h*[^#\\n\\r]+\\h+pam_unix\\.so\\b' /etc/pam.d/common-{password,auth,account,session,session-noninteractive} | grep -Pv -- '\\bnullok\\b'\n```\n\nOutput should be similar to:\n\n```\n/etc/pam.d/common-password:password [success=1 default=ignore] pam_unix.so obscure use_authtok try_first_pass yescrypt\n/etc/pam.d/common-auth:auth [success=2 default=ignore] pam_unix.so try_first_pass\n/etc/pam.d/common-account:account [success=1 new_authtok_reqd=done default=ignore] pam_unix.so\n/etc/pam.d/common-session:session required pam_unix.so\n/etc/pam.d/common-session-noninteractive:session required pam_unix.so\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command:\n\n```\n# grep -PH -- '^\\h*([^#\\n\\r]+\\h+)?pam_unix\\.so\\h+([^#\\n\\r]+\\h+)?nullok\\b' /usr/share/pam-configs/*\n```\n\nEdit any files returned and remove the `nullok` argument for the `pam_unix` lines\n\n*Example File:*\n\n```\nName: Unix authentication\nDefault: yes\nPriority: 256\nAuth-Type: Primary\nAuth:\n [success=end default=ignore] pam_unix.so try_first_pass # <- **ensure line does not include nullok nullok**\nAuth-Initial:\n [success=end default=ignore] pam_unix.so # <- **ensure line does not include nullok nullok**\nAccount-Type: Primary\nAccount:\n [success=end new_authtok_reqd=done default=ignore] pam_unix.so\nAccount-Initial:\n [success=end new_authtok_reqd=done default=ignore] pam_unix.so\nSession-Type: Additional\nSession:\n required pam_unix.so\nSession-Initial:\n required pam_unix.so\nPassword-Type: Primary\nPassword:\n [success=end default=ignore] pam_unix.so obscure use_authtok try_first_pass yescrypt\nPassword-Initial:\n [success=end default=ignore] pam_unix.so obscure yescrypt\n```\n\nRun the following command to update the files in the `/etc/pam.d/` directory:\n\n```\n# pam-auth-update --enable \n```\n\n*Example:*\n\n```\n# pam-auth-update --enable unix\n```\n\n**Note:** If custom files are being used, the corresponding files in `/etc/pam.d/` would need to be edited directly, and the `pam-auth-update --enable ` command skipped" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember", + "title": "5.3.3.4.2 Ensure pam_unix does not include remember", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember_smt", + "name": "statement", + "prose": "The `remember=n` argument saves the last n passwords for each user in `/etc/security/opasswd` in order to force password change history and keep the user from alternating between the same password too frequently. The MD5 password hash algorithm is used for storing the old passwords. Instead of this option the `pam_pwhistory` module should be used. The `pam_pwhistory` module saves the last n passwords for each user in `/etc/security/opasswd` using the password hash algorithm set on the `pam_unix` module. This allows for the `yescrypt` or `sha512` hash algorithm to be used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember_rationale", + "name": "rationale", + "prose": "The `remember=n` argument should be removed to ensure a strong password hashing algorithm is being used. A stronger hash provides additional protection to the system by increasing the level of effort needed for an attacker to successfully determine local user's old passwords stored in `/etc/security/opasswd`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember_obj", + "name": "assessment-objective", + "prose": "Ensure pam_unix does not include remember" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember_obj" + } + ], + "prose": "Run the following command to verify that the `remember` argument is not set on the `pam_unix.so` module:\n\n```\n# grep -PH -- '^\\h*^\\h*[^#\\n\\r]+\\h+pam_unix\\.so\\b' /etc/pam.d/common-{password,auth,account,session,session-noninteractive} | grep -Pv -- '\\bremember=\\d+\\b'\n```\n\nOutput should be similar to:\n\n```\n/etc/pam.d/common-password:password [success=1 default=ignore] pam_unix.so obscure yescrypt\n/etc/pam.d/common-auth:auth [success=1 default=ignore] pam_unix.so\n/etc/pam.d/common-account:account [success=1 new_authtok_reqd=done default=ignore] pam_unix.so\n/etc/pam.d/common-session:session required pam_unix.so\n/etc/pam.d/common-session-noninteractive:session required pam_unix.so\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command:\n\n```\n# grep -PH -- '^\\h*([^#\\n\\r]+\\h+)?pam_unix\\.so\\h+([^#\\n\\r]+\\h+)?remember\\b' /usr/share/pam-configs/*\n```\n\nEdit any files returned and remove the `remember=__` argument for the `pam_unix` lines\n\n*Example output:*\n\n```\n[success=end default=ignore] pam_unix.so obscure use_authtok try_first_pass yescrypt remember=5 # **<- remove remember=**\n[success=end default=ignore] pam_unix.so obscure yescrypt remember=5 # **<- remove remember=**\n```\n\nRun the following command to update the files in the `/etc/pam.d/` directory:\n\n```\n# pam-auth-update --enable \n```\n\n*Example:*\n\n```\n# pam-auth-update --enable unix\n```\n\n**Note:** If custom files are being used, the corresponding files in `/etc/pam.d/` would need to be edited directly, and the `pam-auth-update --enable ` command skipped" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm", + "title": "5.3.3.4.3 Ensure pam_unix includes a strong password hashing algorithm", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/11" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm_smt", + "name": "statement", + "prose": "A cryptographic hash function converts an arbitrary-length input into a fixed length output. Password hashing performs a one-way transformation of a password, turning the password into another string, called the hashed password.\n\nThe `pam_unix` module can be configured to use one of the following hashing algorithms for user's passwords:\n\n- `md5` - When a user changes their password next, encrypt it with the `MD5` algorithm.\n\n- `bigcrypt` - When a user changes their password next, encrypt it with the `DEC C2` algorithm.\n\n- `sha256` - When a user changes their password next, encrypt it with the `SHA256` algorithm. The `SHA256` algorithm must be supported by the crypt(3) function.\n\n- `sha512` - When a user changes their password next, encrypt it with the `SHA512` algorithm. The `SHA512` algorithm must be supported by the crypt(3) function.\n\n- `blowfish` - When a user changes their password next, encrypt it with the `blowfish` algorithm. The `blowfish` algorithm must be supported by the crypt(3) function.\n\n- `gost_yescrypt` - When a user changes their password next, encrypt it with the `gost-yescrypt` algorithm. The `gost-yescrypt` algorithm must be supported by the crypt(3) function.\n\n- `yescrypt` - When a user changes their password next, encrypt it with the `yescrypt` algorithm. The `yescrypt` algorithm must be supported by the crypt(3) function." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm_rationale", + "name": "rationale", + "prose": "The `SHA-512` and `yescrypt` algorithms provide a stronger hash than other algorithms used by Linux for password hash generation. A stronger hash provides additional protection to the system by increasing the level of effort needed for an attacker to successfully determine local user passwords.\n\n**Note:** These changes only apply to the local system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm_obj", + "name": "assessment-objective", + "prose": "Ensure pam_unix includes a strong password hashing algorithm" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm_obj" + } + ], + "prose": "Run the following command to verify that a strong password hashing algorithm is set on the pam_unix.so module:\n\n```\n# grep -PH -- '^\\h*password\\h+([^#\\n\\r]+)\\h+pam_unix\\.so\\h+([^#\\n\\r]+\\h+)?(sha512|yescrypt)\\b' /etc/pam.d/common-password\n```\n\nOutput should be similar to:\n\n```\n/etc/pam.d/common-password:password [success=1 default=ignore] pam_unix.so obscure use_authtok try_first_pass yescrypt\n```\n\nVerify that the line(s) include either `sha512` **- OR -** `yescrypt`" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command:\n\n```\n# awk '/Password-Type:/{ f = 1;next } /-Type:/{ f = 0 } f {if (/pam_unix\\.so/) print FILENAME}' /usr/share/pam-configs/*\n```\n\nEdit any returned files and edit or add a strong hashing algorithm, either sha512 or yescrypt, that meets local site policy to the `pam_unix` lines in the `Password` section:\n\n*Example File:*\n\n```\nName: Unix authentication\nDefault: yes\nPriority: 256\nAuth-Type: Primary # <- Start of \"Auth\" section\nAuth:\n [success=end default=ignore] pam_unix.so try_first_pass\nAuth-Initial:\n [success=end default=ignore] pam_unix.so\nAccount-Type: Primary # <- Start of \"Account\" section\nAccount:\n [success=end new_authtok_reqd=done default=ignore] pam_unix.so\nAccount-Initial:\n [success=end new_authtok_reqd=done default=ignore] pam_unix.so\nSession-Type: Additional # <- Start of \"Session\" section\nSession:\n required pam_unix.so\nSession-Initial:\n required pam_unix.so\nPassword-Type: Primary # <- Start of \"Password\" section\nPassword:\n [success=end default=ignore] pam_unix.so obscure use_authtok try_first_pass yescrypt # <- **ensure hashing algorithm is either sha512 or yescrypt**\nPassword-Initial:\n [success=end default=ignore] pam_unix.so obscure yescrypt # <- **ensure hashing algorithm is either sha512 or yescrypt**\n```\n\nRun the following command to update the files in the `/etc/pam.d/` directory:\n\n```\n# pam-auth-update --enable \n```\n\n*Example:*\n\n```\n# pam-auth-update --enable unix\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok", + "title": "5.3.3.4.4 Ensure pam_unix includes use_authtok", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/11" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok_smt", + "name": "statement", + "prose": "`use_authtok` - When password changing enforce the module to set the new password to the one provided by a previously stacked password module" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok_rationale", + "name": "rationale", + "prose": "`use_authtok` allows multiple pam modules to confirm a new password before it is accepted." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok_obj", + "name": "assessment-objective", + "prose": "Ensure pam_unix includes use_authtok" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok_obj" + } + ], + "prose": "Run the following command to verify that `use_authtok` is set on the pam_unix.so module lines in the password stack:\n\n```\n# grep -PH -- '^\\h*password\\h+([^#\\n\\r]+)\\h+pam_unix\\.so\\h+([^#\\n\\r]+\\h+)?use_authtok\\b' /etc/pam.d/common-password\n```\n\nOutput should be similar to:\n\n```\n/etc/pam.d/common-password:password [success=1 default=ignore] pam_unix.so obscure use_authtok try_first_pass yescrypt\n```\n\nVerify that the line(s) include `use_authtok`" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command:\n\n```\n# awk '/Password-Type:/{ f = 1;next } /-Type:/{ f = 0 } f {if (/pam_unix\\.so/) print FILENAME}' /usr/share/pam-configs/*\n```\n\nEdit any returned files add `use_authtok` to the `pam_unix` line in the `Password` section under `Password:` subsection:\n\n**Note:** The if the file's `Password` section includes a `Password-Initial:` subsection, `use_authtok` should not be added to the `pam_unix` line in the `Password-Initial:` subsection\n\n*Example File:*\n\n```\nName: Unix authentication\nDefault: yes\nPriority: 256\nAuth-Type: Primary # <- Start of \"Auth\" section\nAuth:\n [success=end default=ignore] pam_unix.so try_first_pass\nAuth-Initial:\n [success=end default=ignore] pam_unix.so\nAccount-Type: Primary # <- Start of \"Account\" section\nAccount:\n [success=end new_authtok_reqd=done default=ignore] pam_unix.so\nAccount-Initial:\n [success=end new_authtok_reqd=done default=ignore] pam_unix.so\nSession-Type: Additional # <- Start of \"Session\" section\nSession:\n required pam_unix.so\nSession-Initial:\n required pam_unix.so\nPassword-Type: Primary # <- Start of \"Password\" section\nPassword:\n [success=end default=ignore] pam_unix.so obscure use_authtok try_first_pass yescrypt # <- **ensure line includes use_authtok**\nPassword-Initial:\n [success=end default=ignore] pam_unix.so obscure yescrypt # <- **Password-Initial: subsection does not include use_authtok\n```\n\nRun the following command to update the files in the `/etc/pam.d/` directory:\n\n```\n# pam-auth-update --enable \n```\n\n*Example:*\n\n```\n# pam-auth-update --enable unix\n```" + } + ] + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.4_User_Accounts_and_Environment", + "title": "User Accounts and Environment", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.4.1_Configure_shadow_password_suite_parameters", + "title": "Configure shadow password suite parameters", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured", + "title": "5.4.1.1 Ensure password expiration is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured_smt", + "name": "statement", + "prose": "The `PASS_MAX_DAYS` parameter in `/etc/login.defs` allows an administrator to force passwords to expire once they reach a defined age.\n\n`PASS_MAX_DAYS` ** - The maximum number of days a password may be used. If the password is older than this, a password change will be forced. If not specified, -1 will be assumed (which disables the restriction)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured_rationale", + "name": "rationale", + "prose": "The window of opportunity for an attacker to leverage compromised credentials or successfully compromise credentials via an online brute force attack is limited by the age of the password. Therefore, reducing the maximum age of a password also reduces an attacker's window of opportunity.\n\nWe recommend a yearly password change. This is primarily because for all their good intentions users will share credentials across accounts. Therefore, even if a breach is publicly identified, the user may not see this notification, or forget they have an account on that site. This could leave a shared credential vulnerable indefinitely. Having an organizational policy of a 1-year (annual) password expiration is a reasonable compromise to mitigate this with minimal user burden." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure password expiration is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured_obj" + }, + { + "rel": "script", + "href": "#7aeb383b-25b1-58f1-b622-fc0695d750f4" + } + ], + "prose": "Run the following command and verify `PASS_MAX_DAYS` is set to 365 days or less and conforms to local site policy:\n\n```\n# grep -Pi -- '^\\h*PASS_MAX_DAYS\\h+\\d+\\b' /etc/login.defs\n```\n\n*Example output:*\n\n```\nPASS_MAX_DAYS 365\n```\n\nRun the following command to verify all `/etc/shadow` passwords `PASS_MAX_DAYS`:\n\n- is greater than `0` days\n\n- is less than or equal to `365` days\n\n- conforms to local site policy\n\n```\n# awk -F: '($2~/^\\$.+\\$/) {if($5 > 365 || $5 < 1)print \"User: \" $1 \" PASS_MAX_DAYS: \" $5}' /etc/shadow\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the `PASS_MAX_DAYS` parameter to conform to site policy in `/etc/login.defs` :\n\n```\nPASS_MAX_DAYS 365\n```\n\nModify user parameters for all users with a password set to match:\n\n```\n# chage --maxdays 365 \n```\n\nEdit `/etc/login.defs` and set `PASS_MAX_DAYS` to a value greater than `0` that follows local site policy:\n\n*Example:*\n\n```\nPASS_MAX_DAYS 365\n```\n\nRun the following command to modify user parameters for all users with a password set to a maximum age no greater than `365` or less than `1` that follows local site policy:\n\n```\n# chage --maxdays \n```\n\n*Example:*\n\n```\n# awk -F: '($2~/^\\$.+\\$/) {if($5 > 365 || $5 < 1)system (\"chage --maxdays 365 \" $1)}' /etc/shadow\n```\n\n**Warning:** If a password has been set at system install or kickstart, the `last change date` field is not set, In this case, setting `PASS_MAX_DAYS` will immediately expire the password. One possible solution is to populate the `last change date` field through a command like: `chage -d \"$(date +%Y-%m-%d)\" root`\n\nImpact:\n\nThe password expiration must be greater than the minimum days between password changes or users will be unable to change their password.\n\nExcessive password expiration requirements do more harm than good, because these requirements make users select predictable passwords, composed of sequential words and numbers that are closely related to each other. In these cases, the next password can be predicted based on the previous one (incrementing a number used in the password for\nexample). Also, password expiration requirements offer no containment benefits because attackers will often use credentials as soon as they compromise them. Instead, immediate password changes should be based on key events including, but not limited to:\n\n- Indication of compromise\n\n- Change of user roles\n\n- When a user leaves the organization.\n\nNot only does changing passwords every few weeks or months frustrate the user, but it’s also been suggested that it does more harm than good, because it could lead to bad practices by the user such as adding a character to the end of their existing password." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured", + "title": "5.4.1.2 Ensure minimum password days is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_shadow_field_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "pass_min_days:<:1" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured_smt", + "name": "statement", + "prose": "`PASS_MIN_DAYS` <*N*> - The minimum number of days allowed between password changes. Any password changes attempted sooner than this will be rejected. If not specified, 0 will be assumed (which disables the restriction)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured_rationale", + "name": "rationale", + "prose": "Users may have favorite passwords that they like to use because they are easy to remember and they believe that their password choice is secure from compromise. Unfortunately, passwords are compromised and if an attacker is targeting a specific individual user account, with foreknowledge of data about that user, reuse of old, potentially compromised passwords, may cause a security breach.\n\nBy restricting the frequency of password changes, an administrator can prevent users from repeatedly changing their password in an attempt to circumvent password reuse controls" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure minimum password days is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured_obj" + }, + { + "rel": "script", + "href": "#7aeb383b-25b1-58f1-b622-fc0695d750f4" + } + ], + "prose": "Run the following command to verify that `PASS_MIN_DAYS` is set to a value greater than `0`and follows local site policy:\n\n```\n# grep -Pi -- '^\\h*PASS_MIN_DAYS\\h+\\d+\\b' /etc/login.defs\n```\n\n*Example output:*\n\n```\nPASS_MIN_DAYS 1\n```\n\nRun the following command to verify all passwords have a `PASS_MIN_DAYS` greater than `0`:\n\n```\n# awk -F: '($2~/^\\$.+\\$/) {if($4 < 1)print \"User: \" $1 \" PASS_MIN_DAYS: \" $4}' /etc/shadow\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/login.defs` and set `PASS_MIN_DAYS` to a value greater than `0` that follows local site policy:\n\n*Example:*\n\n```\nPASS_MIN_DAYS 1\n```\n\nRun the following command to modify user parameters for all users with a password set to a minimum days greater than zero that follows local site policy:\n\n```\n# chage --mindays \n```\n\n*Example:*\n\n```\n# awk -F: '($2~/^\\$.+\\$/) {if($4 < 1)system (\"chage --mindays 1 \" $1)}' /etc/shadow\n```\n\nImpact:\n\nIf a users password is set by other personnel as a procedure in dealing with a lost or expired password, the user should be forced to update this \"set\" password with their own password. e.g. force \"change at next logon\".\n\nIf it is not possible to have a user set their own password immediately, and this recommendation or local site procedure may cause a user to continue using a third party generated password, `PASS_MIN_DAYS` for the effected user should be temporally changed to `0`, to allow a user to change their password immediately.\n\nFor applications where the user is not using the password at console, the ability to \"change at next logon\" may be limited. This may cause a user to continue to use a password created by other personnel." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured", + "title": "5.4.1.3 Ensure password expiration warning days is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_shadow_field_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "pass_warn_age:<:7" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/1" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured_smt", + "name": "statement", + "prose": "The `PASS_WARN_AGE` parameter in `/etc/login.defs` allows an administrator to notify users that their password will expire in a defined number of days.\n\n`PASS_WARN_AGE` ** - The number of days warning given before a password expires. A zero means warning is given only upon the day of expiration, a negative value means no warning is given. If not specified, no warning will be provided." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured_rationale", + "name": "rationale", + "prose": "Providing an advance warning that a password will be expiring gives users time to think of a secure password. Users caught unaware may choose a simple password or write it down where it may be discovered." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure password expiration warning days is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured_obj" + }, + { + "rel": "script", + "href": "#7aeb383b-25b1-58f1-b622-fc0695d750f4" + } + ], + "prose": "Run the following command and verify `PASS_WARN_AGE` is `7` or more and follows local site policy:\n\n```\n# grep -Pi -- '^\\h*PASS_WARN_AGE\\h+\\d+\\b' /etc/login.defs\n```\n\n*Example output:*\n\n```\nPASS_WARN_AGE 7\n```\n\nRun the following command to verify all passwords have a `PASS_WARN_AGE` of `7` or more:\n\n```\n# awk -F: '($2~/^\\$.+\\$/) {if($6 < 7)print \"User: \" $1 \" PASS_WARN_AGE: \" $6}' /etc/shadow\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/login.defs` and set `PASS_WARN_AGE` to a value of `7` or more that follows local site policy:\n\n*Example:*\n\n```\nPASS_WARN_AGE 7\n```\n\nRun the following command to modify user parameters for all users with a password set to a minimum warning to `7` or more days that follows local site policy:\n\n```\n# chage --warndays \n```\n\n*Example:*\n\n```\n# awk -F: '($2~/^\\$.+\\$/) {if($6 < 7)system (\"chage --warndays 7 \" $1)}' /etc/shadow\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured", + "title": "5.4.1.4 Ensure strong password hashing algorithm is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/11" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured_smt", + "name": "statement", + "prose": "A cryptographic hash function converts an arbitrary-length input into a fixed length output. Password hashing performs a one-way transformation of a password, turning the password into another string, called the hashed password.\n\n`ENCRYPT_METHOD` (string) - This defines the system default encryption algorithm for encrypting passwords (if no algorithm are specified on the command line). It can take one of these values:\n\n- `MD5` - MD5-based algorithm will be used for encrypting password\n\n- `SHA256` - SHA256-based algorithm will be used for encrypting password\n\n- `SHA512` - SHA512-based algorithm will be used for encrypting password\n\n- `BCRYPT` - BCRYPT-based algorithm will be used for encrypting password\n\n- `YESCRYPT` - YESCRYPT-based algorithm will be used for encrypting password\n\n- `DES` - DES-based algorithm will be used for encrypting password (default)\n\n**Note:**\n\n- This parameter overrides the deprecated `MD5_CRYPT_ENAB` variable.\n\n- This parameter will only affect the generation of group passwords.\n\n- The generation of user passwords is done by PAM and subject to the PAM configuration.\n\n- It is recommended to set this variable consistently with the PAM configuration." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured_rationale", + "name": "rationale", + "prose": "The `SHA-512` and `yescrypt` algorithms provide a stronger hash than other algorithms used by Linux for password hash generation. A stronger hash provides additional protection to the system by increasing the level of effort needed for an attacker to successfully determine local group passwords." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure strong password hashing algorithm is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured_obj" + } + ], + "prose": "Run the following command to verify the hashing algorithm is `sha512` or `yescrypt` in `/etc/login.defs`:\n\n```\n# grep -Pi -- '^\\h*ENCRYPT_METHOD\\h+(SHA512|yescrypt)\\b' /etc/login.defs\n```\n\n*Example output:*\n\n```\nENCRYPT_METHOD SHA512\n - OR -\nENCRYPT_METHOD YESCRYPT\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/login.defs` and set the `ENCRYPT_METHOD` to `SHA512` or `YESCRYPT`:\n\n```\nENCRYPT_METHOD \n```\n\n*Example:*\n\n```\nENCRYPT_METHOD YESCRYPT\n```\n\n**Note:**\n\n- This only effects local groups' passwords created after updating the file to use `sha512` or `yescrypt`.\n\n- If it is determined that the password algorithm being used is not `sha512` or `yescrypt`, once it is changed, it is recommended that all group passwords be updated to use the stronger hashing algorithm.\n\n- It is recommended that the chosen hashing algorithm is consistent across `/etc/login.defs` and the PAM configuration" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured", + "title": "5.4.1.5 Ensure inactive password lock is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured_smt", + "name": "statement", + "prose": "User accounts that have been inactive for over a given period of time can be automatically disabled.\n\n`INACTIVE` - Defines the number of days after the password exceeded its maximum age where the user is expected to replace this password.\n\nThe value is stored in the shadow password file. An input of `0` will disable an expired password with no delay. An input of `-1` will blank the respective field in the shadow password file." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured_rationale", + "name": "rationale", + "prose": "Inactive accounts pose a threat to system security since the users are not logging in to notice failed login attempts or other anomalies." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure inactive password lock is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured_obj" + }, + { + "rel": "script", + "href": "#7aeb383b-25b1-58f1-b622-fc0695d750f4" + } + ], + "prose": "Run the following command and verify `INACTIVE` conforms to site policy (no more than 45 days):\n\n```\n# useradd -D | grep INACTIVE\n\nINACTIVE=45\n```\n\nVerify all users with a password have Password inactive no more than 45 days after password expires\n\nVerify all users with a password have Password inactive no more than 45 days after password expires: Run the following command and Review list of users and `INACTIVE` to verify that all users `INACTIVE` conforms to site policy (no more than 45 days):\n\n```\n# awk -F: '($2~/^\\$.+\\$/) {if($7 > 45 || $7 < 0)print \"User: \" $1 \" INACTIVE: \" $7}' /etc/shadow\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to set the default password inactivity period to 45 days or less that meets local site policy:\n\n```\n# useradd -D -f \n```\n\n*Example:*\n\n```\n# useradd -D -f 45\n```\n\nRun the following command to modify user parameters for all users with a password set to a inactive age of `45` days or less that follows local site policy:\n\n```\n# chage --inactive \n```\n\n*Example:*\n\n```\n# awk -F: '($2~/^\\$.+\\$/) {if($7 > 45 || $7 < 0)system (\"chage --inactive 45 \" $1)}' /etc/shadow\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past", + "title": "5.4.1.6 Ensure all users last password change date is in the past", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past_smt", + "name": "statement", + "prose": "All users should have a password change date in the past." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past_rationale", + "name": "rationale", + "prose": "If a user's recorded password change date is in the future, then they could bypass any set password expiration." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past_obj", + "name": "assessment-objective", + "prose": "Ensure all users last password change date is in the past" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past_obj" + }, + { + "rel": "script", + "href": "#d6ab71b8-9471-5e6b-a844-7f057de465b4" + } + ], + "prose": "Run the following command and verify nothing is returned\n\n```\n{\n while IFS= read -r l_user; do\n l_change=$(date -d \"$(chage --list $l_user | grep '^Last password change' | cut -d: -f2 | grep -v 'never$')\" +%s)\n if [[ \"$l_change\" -gt \"$(date +%s)\" ]]; then\n echo \"User: \\\"$l_user\\\" last password change was \\\"$(chage --list $l_user | grep '^Last password change' | cut -d: -f2)\\\"\"\n fi\n done < <(awk -F: '$2~/^\\$.+\\$/{print $1}' /etc/shadow)\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Investigate any users with a password change date in the future and correct them. Locking the account, expiring the password, or resetting the password manually may be appropriate." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.4.2_Configure_root_and_system_accounts_and_environment", + "title": "Configure root and system accounts and environment", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account", + "title": "5.4.2.1 Ensure root is the only UID 0 account", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_user_uid_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "root:0" + ] + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account_smt", + "name": "statement", + "prose": "Any account with UID 0 has superuser privileges on the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account_rationale", + "name": "rationale", + "prose": "This access must be limited to only the default `root` account and only from the system console. Administrative access must be through an unprivileged account using an approved mechanism as noted in Item 5.6 Ensure access to the su command is restricted." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account_obj", + "name": "assessment-objective", + "prose": "Ensure root is the only UID 0 account" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account_obj" + }, + { + "rel": "script", + "href": "#ad96b673-9ce1-5232-9721-d4e785bb6854" + } + ], + "prose": "Run the following command and verify that only \"root\" is returned:\n\n```\n# awk -F: '($3 == 0) { print $1 }' /etc/passwd\n\nroot\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to change the `root` account UID to `0`:\n\n```\n# usermod -u 0 root\n```\n\nModify any users other than `root` with UID `0` and assign them a new UID." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account", + "title": "5.4.2.2 Ensure root is the only GID 0 account", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_user_gid_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "root:0" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account_smt", + "name": "statement", + "prose": "The `usermod` command can be used to specify which group the `root` account belongs to. This affects permissions of files that are created by the `root` account." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account_rationale", + "name": "rationale", + "prose": "Using GID 0 for the `root` account helps prevent `root` -owned files from accidentally becoming accessible to non-privileged users." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account_obj", + "name": "assessment-objective", + "prose": "Ensure root is the only GID 0 account" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account_obj" + }, + { + "rel": "script", + "href": "#78a10f33-f6dd-54e5-9e39-fe063dae6252" + } + ], + "prose": "Run the following command to verify the `root` user's primary GID is `0`, and no other user's have GID `0` as their primary GID:\n\n```\n# awk -F: '($1 !~ /^(sync|shutdown|halt|operator)/ && $4==\"0\") {print $1\":\"$4}' /etc/passwd\n\nroot:0\n```\n\n**Note:** User's: sync, shutdown, halt, and operator are excluded from the check for other user's with GID `0`" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to set the `root` user's GID to `0`:\n\n```\n# usermod -g 0 root\n```\n\nRun the following command to set the `root` group's GID to `0`:\n\n```\n# groupmod -g 0 root\n```\n\nRemove any users other than the `root` user with GID 0 or assign them a new GID if appropriate." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group", + "title": "5.4.2.3 Ensure group root is the only GID 0 group", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_group_gid_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "root:0" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group_smt", + "name": "statement", + "prose": "The `groupmod` command can be used to specify which group the `root` group belongs to. This affects permissions of files that are group owned by the `root` group." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group_rationale", + "name": "rationale", + "prose": "Using GID 0 for the `root` group helps prevent `root` group owned files from accidentally becoming accessible to non-privileged users." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group_obj", + "name": "assessment-objective", + "prose": "Ensure group root is the only GID 0 group" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group_obj" + }, + { + "rel": "script", + "href": "#0577d57c-79e0-5876-9d54-1307cfeee2a4" + } + ], + "prose": "Run the following command to verify no group other than `root` is assigned GID `0`:\n\n```\n# awk -F: '$3==\"0\"{print $1\":\"$3}' /etc/group\n\nroot:0\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to set the `root` group's GID to `0`:\n\n```\n# groupmod -g 0 root\n```\n\nRemove any groups other than the `root` group with GID 0 or assign them a new GID if appropriate." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled", + "title": "5.4.2.4 Ensure root account access is controlled", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled_smt", + "name": "statement", + "prose": "There are a number of methods to access the root account directly. Without a password set any user would be able to gain access and thus control over the entire system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled_rationale", + "name": "rationale", + "prose": "Access to `root` should be secured at all times." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled_obj", + "name": "assessment-objective", + "prose": "Ensure root account access is controlled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled_obj" + }, + { + "rel": "script", + "href": "#2a3327a1-9dec-5d87-b73d-266fdce4eb40" + } + ], + "prose": "Run the following command to verify that either the root user's password is set or the root user's account is locked:\n\n```\n# passwd -S root | awk '$2 ~ /^(P|L)/ {print \"User: \\\"\" $1 \"\\\" Password is status: \" $2}'\n```\n\nVerify the output is either:\n\n```\nUser: \"root\" Password is status: P\n- OR -\nUser: \"root\" Password is status: L\n```\n\n**Note:**\n\n- `P` - Password is set\n\n- `L` - Password is locked" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to set a password for the `root` user:\n\n```\n# passwd root\n```\n\n**- OR -**\n\nRun the following command to lock the `root` user account:\n\n```\n# usermod -L root\n```\n\nImpact:\n\nIf there are any automated processes that relies on access to the root account without authentication, they will fail after remediation." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity", + "title": "5.4.2.5 Ensure root path integrity", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity_smt", + "name": "statement", + "prose": "The `root` user can execute any command on the system and could be fooled into executing programs unintentionally if the `PATH` is not set correctly." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity_rationale", + "name": "rationale", + "prose": "Including the current working directory (.) or other writable directory in `root`'s executable path makes it likely that an attacker can gain superuser access by forcing an administrator operating as `root` to execute a Trojan horse program." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity_obj", + "name": "assessment-objective", + "prose": "Ensure root path integrity" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity_obj" + }, + { + "rel": "script", + "href": "#55b1a5f2-02bd-5547-b88c-25d7f515aeaa" + } + ], + "prose": "Run the following script to verify root's path does not include:\n\n- Locations that are not directories\n\n- An empty directory (`::`)\n\n- A trailing (`:`)\n\n- Current working directory (`.`)\n\n- Non `root` owned directories\n\n- Directories that less restrictive than mode `0755`\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output2=\"\"\n l_pmask=\"0022\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_pmask )) )\"\n l_root_path=\"$(sudo -Hiu root env | grep '^PATH' | cut -d= -f2)\"\n unset a_path_loc && IFS=\":\" read -ra a_path_loc <<< \"$l_root_path\"\n grep -q \"::\" <<< \"$l_root_path\" && l_output2=\"$l_output2\\n - root's path contains a empty directory (::)\"\n grep -Pq \":\\h*$\" <<< \"$l_root_path\" && l_output2=\"$l_output2\\n - root's path contains a trailing (:)\"\n grep -Pq '(\\h+|:)\\.(:|\\h*$)' <<< \"$l_root_path\" && l_output2=\"$l_output2\\n - root's path contains current working directory (.)\"\n while read -r l_path; do\n if [ -d \"$l_path\" ]; then\n while read -r l_fmode l_fown; do\n [ \"$l_fown\" != \"root\" ] && l_output2=\"$l_output2\\n - Directory: \\\"$l_path\\\" is owned by: \\\"$l_fown\\\" should be owned by \\\"root\\\"\"\n [ $(( $l_fmode & $l_pmask )) -gt 0 ] && l_output2=\"$l_output2\\n - Directory: \\\"$l_path\\\" is mode: \\\"$l_fmode\\\" and should be mode: \\\"$l_maxperm\\\" or more restrictive\"\n done <<< \"$(stat -Lc '%#a %U' \"$l_path\")\"\n else\n l_output2=\"$l_output2\\n - \\\"$l_path\\\" is not a directory\"\n fi\n done <<< \"$(printf \"%s\\n\" \"${a_path_loc[@]}\")\"\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n *** PASS ***\\n - Root's path is correctly configured\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\\n\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Correct or justify any:\n\n- Locations that are not directories\n\n- Empty directories (`::`)\n\n- Trailing (`:`)\n\n- Current working directory (`.`)\n\n- Non `root` owned directories\n\n- Directories that less restrictive than mode `0755`" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured", + "title": "5.4.2.6 Ensure root user umask is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured_smt", + "name": "statement", + "prose": "The user file-creation mode mask (`umask`) is used to determine the file permission for newly created directories and files. In Linux, the default permissions for any newly created directory is 0777 (`rwxrwxrwx`), and for any newly created file it is 0666 (`rw-rw-rw-`). The `umask` modifies the default Linux permissions by restricting (masking) these permissions. The `umask` is not simply subtracted, but is processed bitwise. Bits set in the `umask` are cleared in the resulting file mode.\n\n`umask` can be set with either `Octal` or `Symbolic` values:\n\n- `Octal` (Numeric) Value - Represented by either three or four digits. ie `umask 0027` or `umask 027`. If a four digit umask is used, the first digit is ignored. The remaining three digits effect the resulting permissions for user, group, and world/other respectively.\n\n- `Symbolic` Value - Represented by a comma separated list for User `u`, group `g`, and world/other `o`. The permissions listed are not masked by `umask`. ie a `umask` set by `umask u=rwx,g=rx,o=` is the `Symbolic` equivalent of the `Octal` `umask 027`. This `umask` would set a newly created directory with file mode `drwxr-x---` and a newly created file with file mode `rw-r-----`.\n\n**root user Shell Configuration Files:**\n\n- `/root/.bash_profile` - Is executed to configure the root users' shell before the initial command prompt. **Is only read by login shells.**\n\n- `/root/.bashrc` - Is executed for interactive shells. **only read by a shell that's both interactive and non-login**\n\n`umask` is set by order of precedence. If `umask` is set in multiple locations, this order of precedence will determine the system's default `umask`.\n\n**Order of precedence:**\n\n- `/root/.bash_profile`\n\n- `/root/.bashrc`\n\n- The system default umask" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured_rationale", + "name": "rationale", + "prose": "Setting a secure value for `umask` ensures that users make a conscious choice about their file permissions. A permissive `umask` value could result in directories or files with excessive permissions that can be read and/or written to by unauthorized users." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure root user umask is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured_obj" + } + ], + "prose": "Run the following to verify the root user `umask` is set to enforce a newly created directories' permissions to be `750 (drwxr-x---)`, and a newly created file's permissions be `640 (rw-r-----)`, or more restrictive:\n\n```\n# grep -Psi -- '^\\h*umask\\h+(([0-7][0-7][01][0-7]\\b|[0-7][0-7][0-7][0-6]\\b)|([0-7][01][0-7]\\b|[0-7][0-7][0-6]\\b)|(u=[rwx]{1,3},)?(((g=[rx]?[rx]?w[rx]?[rx]?\\b)(,o=[rwx]{1,3})?)|((g=[wrx]{1,3},)?o=[wrx]{1,3}\\b)))' /root/.bash_profile /root/.bashrc\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/root/.bash_profile` and `/root/.bashrc` and remove, comment out, or update any line with `umask` to be `0027` or more restrictive." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell", + "title": "5.4.2.7 Ensure system accounts do not have a valid login shell", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell_smt", + "name": "statement", + "prose": "There are a number of accounts provided with most distributions that are used to manage applications and are not intended to provide an interactive shell. Furthermore, a user may add special accounts that are not intended to provide an interactive shell." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell_rationale", + "name": "rationale", + "prose": "It is important to make sure that accounts that are not being used by regular users are prevented from being used to provide an interactive shell. By default, most distributions set the password field for these accounts to an invalid string, but it is also recommended that the shell field in the password file be set to the `nologin` shell. This prevents the account from potentially being used to run any commands." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell_obj", + "name": "assessment-objective", + "prose": "Ensure system accounts do not have a valid login shell" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell_obj" + }, + { + "rel": "script", + "href": "#a2f74d47-2fe4-56c2-8476-6f1c77202f65" + } + ], + "prose": "Run the following command to verify system accounts, except for `root`, `halt`, `sync`, `shutdown` or `nfsnobody`, do not have a valid login shell:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_valid_shells=\"^($(awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n awk -v pat=\"$l_valid_shells\" -F: '($1!~/^(root|halt|sync|shutdown|nfsnobody)$/ && ($3<'\"$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\"' || $3 == 65534) && $(NF) ~ pat) {print \"Service account: \\\"\" $1 \"\\\" has a valid shell: \" $7}' /etc/passwd\n}\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to set the shell for any service accounts returned by the audit to `nologin`:\n\n```\n# usermod -s $(command -v nologin) \n```\n\n*Example script:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n awk -v pat=\"$l_valid_shells\" -F: '($1!~/^(root|halt|sync|shutdown|nfsnobody)$/ && ($3<'\"$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\"' || $3 == 65534) && $(NF) ~ pat) {system (\"usermod -s '\"$(command -v nologin)\"' \" $1)}' /etc/passwd\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked", + "title": "5.4.2.8 Ensure accounts without a valid login shell are locked", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked_smt", + "name": "statement", + "prose": "There are a number of accounts provided with most distributions that are used to manage applications and are not intended to provide an interactive shell. Furthermore, a user may add special accounts that are not intended to provide an interactive shell." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked_rationale", + "name": "rationale", + "prose": "It is important to make sure that accounts that are not being used by regular users are prevented from being used to provide an interactive shell. By default, most distributions set the password field for these accounts to an invalid string, but it is also recommended that the shell field in the password file be set to the `nologin` shell. This prevents the account from potentially being used to run any commands." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked_obj", + "name": "assessment-objective", + "prose": "Ensure accounts without a valid login shell are locked" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked_obj" + }, + { + "rel": "script", + "href": "#90495ec8-deec-51cc-866a-f5f99be62940" + } + ], + "prose": "Run the following script to verify all non-root accounts without a valid login shell are locked.\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_valid_shells=\"^($(awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n while IFS= read -r l_user; do\n passwd -S \"$l_user\" | awk '$2 !~ /^L/ {print \"Account: \\\"\" $1 \"\\\" does not have a valid login shell and is not locked\"}'\n done < <(awk -v pat=\"$l_valid_shells\" -F: '($1 != \"root\" && $(NF) !~ pat) {print $1}' /etc/passwd)\n}\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to lock any non-root accounts without a valid login shell returned by the audit:\n\n```\n# usermod -L \n```\n\n*Example script:*:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_valid_shells=\"^($(awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n while IFS= read -r l_user; do\n passwd -S \"$l_user\" | awk '$2 !~ /^L/ {system (\"usermod -L \" $1)}'\n done < <(awk -v pat=\"$l_valid_shells\" -F: '($1 != \"root\" && $(NF) !~ pat) {print $1}' /etc/passwd)\n}\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_5.4.3_Configure_user_default_environment", + "title": "Configure user default environment", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells", + "title": "5.4.3.1 Ensure nologin is not listed in /etc/shells", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells_smt", + "name": "statement", + "prose": "`/etc/shells` is a text file which contains the full pathnames of valid login shells. This file is consulted by `chsh` and available to be queried by other programs.\n\nBe aware that there are programs which consult this file to find out if a user is a normal user; for example, FTP daemons traditionally disallow access to users with shells not included in this file." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells_rationale", + "name": "rationale", + "prose": "A user can use `chsh` to change their configured shell.\n\nIf a user has a shell configured that isn't in in `/etc/shells`, then the system assumes that they're somehow restricted. In the case of `chsh` it means that the user cannot change that value.\n\nOther programs might query that list and apply similar restrictions.\n\nBy putting `nologin` in `/etc/shells`, any user that has `nologin` as its shell is considered a full, unrestricted user. This is not the expected behavior for `nologin`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells_obj", + "name": "assessment-objective", + "prose": "Ensure nologin is not listed in /etc/shells" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells_obj" + } + ], + "prose": "Run the following command to verify that `nologin` is not listed in the `/etc/shells` file:\n\n```\n# grep -Ps '^\\h*([^#\\n\\r]+)?\\/nologin\\b' /etc/shells\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/shells` and remove any lines that include `nologin`" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured", + "title": "5.4.3.2 Ensure default user shell timeout is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured_smt", + "name": "statement", + "prose": "`TMOUT` is an environmental setting that determines the timeout of a shell in seconds.\n\n- TMOUT=*n* - Sets the shell timeout to *n* seconds. A setting of `TMOUT=0` disables timeout.\n\n- readonly TMOUT- Sets the TMOUT environmental variable as readonly, preventing unwanted modification during run-time.\n\n- export TMOUT - exports the TMOUT variable\n\n**System Wide Shell Configuration Files:**\n\n- `/etc/profile` - used to set system wide environmental variables on users shells. The variables are sometimes the same ones that are in the `.bash_profile`, however this file is used to set an initial PATH or PS1 for all shell users of the system. **is only executed for interactive *login* shells, or shells executed with the --login parameter.**\n\n- `/etc/profile.d` - `/etc/profile` will execute the scripts within `/etc/profile.d/*.sh`. It is recommended to place your configuration in a shell script within `/etc/profile.d` to set your own system wide environmental variables.\n\n- `/etc/bashrc` - System wide version of `.bashrc`. In Fedora derived distributions, `/etc/bashrc` also invokes /etc/profile.d/*.sh if *non-login* shell, but redirects output to `/dev/null` if *non-interactive.* **Is only executed for *interactive* shells or if `BASH_ENV` is set to `/etc/bashrc`.**" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured_rationale", + "name": "rationale", + "prose": "Setting a timeout value reduces the window of opportunity for unauthorized user access to another user's shell session that has been left unattended. It also ends the inactive session and releases the resources associated with that session." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure default user shell timeout is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured_obj" + }, + { + "rel": "script", + "href": "#248436ec-a0a3-52db-b28c-f5a6027b1ea1" + } + ], + "prose": "Run the following script to verify that `TMOUT` is configured to: include a timeout of no more than `900` seconds, to be `readonly`, to be `exported`, and is not being changed to a longer timeout.\n\n```bash\n#!/usr/bin/env bash\n\n{\n output1=\"\" output2=\"\"\n [ -f /etc/bashrc ] && BRC=\"/etc/bashrc\"\n for f in \"$BRC\" /etc/profile /etc/profile.d/*.sh ; do\n grep -Pq '^\\s*([^#]+\\s+)?TMOUT=(900|[1-8][0-9][0-9]|[1-9][0-9]|[1-9])\\b' \"$f\" && grep -Pq '^\\s*([^#]+;\\s*)?readonly\\s+TMOUT(\\s+|\\s*;|\\s*$|=(900|[1-8][0-9][0-9]|[1-9][0-9]|[1-9]))\\b' \"$f\" && grep -Pq '^\\s*([^#]+;\\s*)?export\\s+TMOUT(\\s+|\\s*;|\\s*$|=(900|[1-8][0-9][0-9]|[1-9][0-9]|[1-9]))\\b' \"$f\" &&\n output1=\"$f\"\n done\n grep -Pq '^\\s*([^#]+\\s+)?TMOUT=(9[0-9][1-9]|9[1-9][0-9]|0+|[1-9]\\d{3,})\\b' /etc/profile /etc/profile.d/*.sh \"$BRC\" && output2=$(grep -Ps '^\\s*([^#]+\\s+)?TMOUT=(9[0-9][1-9]|9[1-9][0-9]|0+|[1-9]\\d{3,})\\b' /etc/profile /etc/profile.d/*.sh $BRC)\n if [ -n \"$output1\" ] && [ -z \"$output2\" ]; then\n echo -e \"\\nPASSED\\n\\nTMOUT is configured in: \\\"$output1\\\"\\n\"\n else\n [ -z \"$output1\" ] && echo -e \"\\nFAILED\\n\\nTMOUT is not configured\\n\"\n [ -n \"$output2\" ] && echo -e \"\\nFAILED\\n\\nTMOUT is incorrectly configured in: \\\"$output2\\\"\\n\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Review `/etc/bashrc`, `/etc/profile`, and all files ending in `*.sh` in the `/etc/profile.d/` directory and remove or edit all `TMOUT=_n_` entries to follow local site policy. `TMOUT` should not exceed 900 or be equal to `0`.\n\nConfigure `TMOUT` in **one** of the following files:\n\n- A file in the `/etc/profile.d/` directory ending in `.sh`\n\n- `/etc/profile`\n\n- `/etc/bashrc`\n\n*`TMOUT` configuration examples:*\n\n- As multiple lines:\n\n```\nTMOUT=900\nreadonly TMOUT\nexport TMOUT\n```\n\n- As a single line:\n\n```\nreadonly TMOUT=900 ; export TMOUT\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured", + "title": "5.4.3.3 Ensure default user umask is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured_smt", + "name": "statement", + "prose": "The user file-creation mode mask (`umask`) is used to determine the file permission for newly created directories and files. In Linux, the default permissions for any newly created directory is 0777 (`rwxrwxrwx`), and for any newly created file it is 0666 (`rw-rw-rw-`). The `umask` modifies the default Linux permissions by restricting (masking) these permissions. The `umask` is not simply subtracted, but is processed bitwise. Bits set in the `umask` are cleared in the resulting file mode.\n\n`umask` can be set with either `Octal` or `Symbolic` values:\n\n- `Octal` (Numeric) Value - Represented by either three or four digits. ie `umask 0027` or `umask 027`. If a four digit umask is used, the first digit is ignored. The remaining three digits effect the resulting permissions for user, group, and world/other respectively.\n\n- `Symbolic` Value - Represented by a comma separated list for User `u`, group `g`, and world/other `o`. The permissions listed are not masked by `umask`. ie a `umask` set by `umask u=rwx,g=rx,o=` is the `Symbolic` equivalent of the `Octal` `umask 027`. This `umask` would set a newly created directory with file mode `drwxr-x---` and a newly created file with file mode `rw-r-----`.\n\nThe default `umask` can be set to use the `pam_umask` module or in a `System Wide Shell Configuration File`. The user creating the directories or files has the discretion of changing the permissions via the chmod command, or choosing a different default `umask` by adding the `umask` command into a `User Shell Configuration File`, ( `.bash_profile` or `.bashrc`), in their home directory.\n\n**Setting the default umask:**\n\n- pam_umask module:\n\n- will set the umask according to the system default in `/etc/login.defs` and user settings, solving the problem of different `umask` settings with different shells, display managers, remote sessions etc.\n\n- `umask=` value in the `/etc/login.defs` file is interpreted as Octal\n\n- Setting `USERGROUPS_ENAB` to yes in `/etc/login.defs` (default):\n\n- will enable setting of the `umask` group bits to be the same as owner bits. (examples: 022 -> 002, 077 -> 007) for non-root users, if the `uid` is the same as `gid`, and `username` is the same as the ``\n\n- userdel will remove the user's group if it contains no more members, and useradd will create by default a group with the name of the user\n\n- `System Wide Shell Configuration File`:\n\n- `/etc/profile` - used to set system wide environmental variables on users shells. The variables are sometimes the same ones that are in the `.bash_profile`, however this file is used to set an initial PATH or PS1 for all shell users of the system. **is only executed for interactive *login* shells, or shells executed with the --login parameter.**\n\n- `/etc/profile.d` - `/etc/profile` will execute the scripts within `/etc/profile.d/*.sh`. It is recommended to place your configuration in a shell script within `/etc/profile.d` to set your own system wide environmental variables.\n\n- `/etc/bashrc` - System wide version of `.bashrc`. In Fedora derived distributions, `etc/bashrc` also invokes /etc/profile.d/*.sh if *non-login* shell, but redirects output to `/dev/null` if *non-interactive.* **Is only executed for *interactive* shells or if `BASH_ENV` is set to `/etc/bashrc`.**\n\n**User Shell Configuration Files:**\n\n- `~/.bash_profile` - Is executed to configure your shell before the initial command prompt. **Is only read by login shells.**\n\n- `~/.bashrc` - Is executed for interactive shells. **only read by a shell that's both interactive and non-login**\n\n`umask` is set by order of precedence. If `umask` is set in multiple locations, this order of precedence will determine the system's default `umask`.\n\n**Order of precedence:**\n\n- A file in `/etc/profile.d/` ending in `.sh` - This will override any other system-wide `umask` setting\n\n- In the file `/etc/profile`\n\n- On the `pam_umask.so` module in `/etc/pam.d/postlogin`\n\n- In the file `/etc/login.defs`\n\n- In the file `/etc/default/login`" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured_rationale", + "name": "rationale", + "prose": "Setting a secure default value for `umask` ensures that users make a conscious choice about their file permissions. A permissive `umask` value could result in directories or files with excessive permissions that can be read and/or written to by unauthorized users." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure default user umask is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured_obj" + }, + { + "rel": "script", + "href": "#11ed45fb-b2a8-572b-97d5-a5ce474bd8b6" + } + ], + "prose": "Run the following to verify the default user `umask` is set to `027`(octal) or `u=rwx,g=rx,o=` (Symbolic) to enforce newly created directories' permissions to be `750 (drwxr-x---)`, and newly created file's permissions be `640 (rw-r-----)`, or more restrictive:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n file_umask_chk()\n {\n if grep -Psiq -- '^\\h*umask\\h+(0?[0-7][2-7]7|u(=[rwx]{0,3}),g=([rx]{0,2}),o=)(\\h*#.*)?$' \"$l_file\"; then\n l_output=\"$l_output\\n - umask is set correctly in \\\"$l_file\\\"\"\n elif grep -Psiq -- '^\\h*umask\\h+(([0-7][0-7][01][0-7]\\b|[0-7][0-7][0-7][0-6]\\b)|([0-7][01][0-7]\\b|[0-7][0-7][0-6]\\b)|(u=[rwx]{1,3},)?(((g=[rx]?[rx]?w[rx]?[rx]?\\b)(,o=[rwx]{1,3})?)|((g=[wrx]{1,3},)?o=[wrx]{1,3}\\b)))' \"$l_file\"; then\n l_output2=\"$l_output2\\n - umask is incorrectly set in \\\"$l_file\\\"\"\n fi\n }\n while IFS= read -r -d $'\\0' l_file; do\n file_umask_chk\n done < <(find /etc/profile.d/ -type f -name '*.sh' -print0)\n [ -z \"$l_output\" ] && l_file=\"/etc/profile\" && file_umask_chk\n [ -z \"$l_output\" ] && l_file=\"/etc/bashrc\" && file_umask_chk\n [ -z \"$l_output\" ] && l_file=\"/etc/bash.bashrc\" && file_umask_chk\n [ -z \"$l_output\" ] && l_file=\"/etc/pam.d/postlogin\"\n if [ -z \"$l_output\" ]; then\n if grep -Psiq -- '^\\h*session\\h+[^#\\n\\r]+\\h+pam_umask\\.so\\h+([^#\\n\\r]+\\h+)?umask=(0?[0-7][2-7]7)\\b' \"$l_file\"; then\n l_output1=\"$l_output1\\n - umask is set correctly in \\\"$l_file\\\"\"\n elif grep -Psiq '^\\h*session\\h+[^#\\n\\r]+\\h+pam_umask\\.so\\h+([^#\\n\\r]+\\h+)?umask=(([0-7][0-7][01][0-7]\\b|[0-7][0-7][0-7][0-6]\\b)|([0-7][01][0-7]\\b))' \"$l_file\"; then\n l_output2=\"$l_output2\\n - umask is incorrectly set in \\\"$l_file\\\"\"\n fi\n fi\n [ -z \"$l_output\" ] && l_file=\"/etc/login.defs\" && file_umask_chk\n [ -z \"$l_output\" ] && l_file=\"/etc/default/login\" && file_umask_chk\n [[ -z \"$l_output\" && -z \"$l_output2\" ]] && l_output2=\"$l_output2\\n - umask is not set\"\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\"\n [ -n \"$l_output\" ] && echo -e \"\\n- * Correctly configured * :\\n$l_output\\n\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script and perform the instructions in the output to set the default umask to `027` or more restrictive:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" l_out=\"\"\n file_umask_chk()\n {\n if grep -Psiq -- '^\\h*umask\\h+(0?[0-7][2-7]7|u(=[rwx]{0,3}),g=([rx]{0,2}),o=)(\\h*#.*)?$' \"$l_file\"; then\n l_out=\"$l_out\\n - umask is set correctly in \\\"$l_file\\\"\"\n elif grep -Psiq -- '^\\h*umask\\h+(([0-7][0-7][01][0-7]\\b|[0-7][0-7][0-7][0-6]\\b)|([0-7][01][0-7]\\b|[0-7][0-7][0-6]\\b)|(u=[rwx]{1,3},)?(((g=[rx]?[rx]?w[rx]?[rx]?\\b)(,o=[rwx]{1,3})?)|((g=[wrx]{1,3},)?o=[wrx]{1,3}\\b)))' \"$l_file\"; then\n l_output2=\"$l_output2\\n - \\\"$l_file\\\"\"\n fi\n }\n while IFS= read -r -d $'\\0' l_file; do\n file_umask_chk\n done < <(find /etc/profile.d/ -type f -name '*.sh' -print0)\n [ -n \"$l_out\" ] && l_output=\"$l_out\"\n l_file=\"/etc/profile\" && file_umask_chk\n l_file=\"/etc/bashrc\" && file_umask_chk\n l_file=\"/etc/bash.bashrc\" && file_umask_chk\n l_file=\"/etc/pam.d/postlogin\"\n if grep -Psiq '^\\h*session\\h+[^#\\n\\r]+\\h+pam_umask\\.so\\h+([^#\\n\\r]+\\h+)?umask=(([0-7][0-7][01][0-7]\\b|[0-7][0-7][0-7][0-6]\\b)|([0-7][01][0-7]\\b))' \"$l_file\"; then\n l_output2=\"$l_output2\\n - \\\"$l_file\\\"\"\n fi\n l_file=\"/etc/login.defs\" && file_umask_chk\n l_file=\"/etc/default/login\" && file_umask_chk\n if [ -z \"$l_output2\" ]; then\n echo -e \" - No files contain a UMASK that is not restrictive enough\\n No UMASK updates required to existing files\"\n else\n echo -e \"\\n - UMASK is not restrictive enough in the following file(s):$l_output2\\n\\n- Remediation Procedure:\\n - Update these files and comment out the UMASK line\\n or update umask to be \\\"0027\\\" or more restrictive\"\n fi\n if [ -n \"$l_output\" ]; then\n echo -e \"$l_output\"\n else\n echo -e \" - Configure UMASK in a file in the \\\"/etc/profile.d/\\\" directory ending in \\\".sh\\\"\\n\\n Example Command (Hash to represent being run at a root prompt):\\n\\n# printf '%s\\\\\\n' \\\"umask 027\\\" > /etc/profile.d/50-systemwide_umask.sh\\n\"\n fi\n}\n```\n\n**Notes:**\n\n- This method only applies to bash and shell. If other shells are supported on the system, it is recommended that their configuration files also are checked\n\n- If the `pam_umask.so` module is going to be used to set `umask`, ensure that it's not being overridden by another setting. Refer to the PAM_UMASK(8) man page for more information" + } + ] + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6_Logging_and_Auditing", + "title": "Logging and Auditing", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.1_System_Logging", + "title": "System Logging", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.1.1_Configure_systemd-journald_service", + "title": "Configure systemd-journald service", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active", + "title": "6.1.1.1 Ensure journald service is enabled and active", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active_smt", + "name": "statement", + "prose": "Ensure that the `systemd-journald` service is enabled to allow capturing of logging events." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active_rationale", + "name": "rationale", + "prose": "If the `systemd-journald` service is not enabled to start on boot, the system will not capture logging events." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active_obj", + "name": "assessment-objective", + "prose": "Ensure journald service is enabled and active" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active_obj" + } + ], + "prose": "Run the following command to verify `systemd-journald` is enabled:\n\n```\n# systemctl is-enabled systemd-journald.service\n\nstatic\n```\n\n**Note:** By default the `systemd-journald` service does not have an `[Install]` section and thus cannot be enabled / disabled. It is meant to be referenced as `Requires` or `Wants` by other unit files. As such, if the status of `systemd-journald` is not `static`, investigate why\n\nRun the following command to verify `systemd-journald` is active:\n\n```\n# systemctl is-active systemd-journald.service\n\nactive\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to unmask and start `systemd-journald.service`\n\n```\n# systemctl unmask systemd-journald.service\n# systemctl start systemd-journald.service\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured", + "title": "6.1.1.2 Ensure journald log file access is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured_smt", + "name": "statement", + "prose": "Journald will create logfiles that do not already exist on the system. This setting controls what permissions will be applied to these newly created files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured_rationale", + "name": "rationale", + "prose": "It is important to ensure that log files have the correct permissions to ensure that sensitive data is archived and protected." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure journald log file access is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured_obj" + } + ], + "prose": "Run the following script to verify:\n\n- systemd-journald logfiles are mode `0640` or more restrictive\n\n- Directories /run/ and /var/lib/systemd/ are mode `0755` or more restrictive\n\n- All other configured directories are mode `2755`, `0750`, or more restrictive\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=()\n l_systemd_config_file=\"/etc/tmpfiles.d/systemd.conf\" l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\"\n f_file_chk()\n {\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n if [ $(( $l_mode & $l_perm_mask )) -le 0 ] || [[ \"$l_type\" = \"Directory\" && \"$l_mode\" =~ 275(0|5) ]]; then\n a_out+=(\" - $l_type \\\"$l_logfile\\\" access is:\" \\\n \" mode: \\\"$l_mode\\\", owned by: \\\"$l_user\\\", and group owned by: \\\"$l_group\\\"\")\n else\n a_out2+=(\" - $l_type \\\"$l_logfile\\\" access is:\" \\\n \" mode: \\\"$l_mode\\\", owned by: \\\"$l_user\\\", and group owned by: \\\"$l_group\\\"\" \\\n \" should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n fi\n }\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\" a_out=() a_out2=()\n l_logfile_perms_line=\"$(awk '($1~/^(f|d)$/ && $2~/\\/\\S+/ && $3~/[0-9]{3,}/){print $2 \":\" $3 \":\" $4 \":\" $5}' \"$l_file\")\"\n while IFS=: read -r l_logfile l_mode l_user l_group; do\n if [ -d \"$l_logfile\" ]; then\n l_perm_mask=\"0027\" l_type=\"Directory\"\n grep -Psq '^(\\/run|\\/var\\/lib\\/systemd)\\b' <<< \"$l_logfile\" && l_perm_mask=\"0022\"\n else\n l_perm_mask=\"0137\" l_type=\"File\"\n fi\n grep -Psq '^(\\/run|\\/var\\/lib\\/systemd)\\b' <<< \"$l_logfile\" && l_perm_mask=\"0022\"\n f_file_chk\n done <<< \"$l_logfile_perms_line\"\n [ \"${#a_out[@]}\" -gt \"0\" ] && a_output+=(\" - File: \\\"$l_file\\\" sets:\" \"${a_out[@]}\")\n [ \"${#a_out2[@]}\" -gt \"0\" ] && a_output2+=(\" - File: \\\"$l_file\\\" sets:\" \"${a_out2[@]}\")\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** REVIEW **\" \\\n \" - Review file access to ensure they are set IAW site policy:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```\n\nReview the output" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "If the default configuration is not appropriate for the site specific requirements, copy `/usr/lib/tmpfiles.d/systemd.conf` to `/etc/tmpfiles.d/systemd.conf` and modify as required. Recommended mode for logfiles is `0640` or more restrictive." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured", + "title": "6.1.1.3 Ensure journald log file rotation is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured_smt", + "name": "statement", + "prose": "Journald includes the capability of rotating log files regularly to avoid filling up the system with logs or making the logs unmanageably large. The file `/etc/systemd/journald.conf` is the configuration file used to specify how logs generated by Journald should be rotated." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured_rationale", + "name": "rationale", + "prose": "By keeping the log files smaller and more manageable, a system administrator can easily archive these files to another system and spend less time looking through inordinately large log files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure journald log file rotation is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured_obj" + } + ], + "prose": "Review the `systemd-journald` configuration. Verify logs are rotated according to site policy. The specific parameters for log rotation are:\n\nRun the following script and review the output to ensure logs are rotated according to site policy:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"SystemMaxUse=^.+$\" \"SystemKeepFree=^.+$\" \"RuntimeMaxUse=^.+$\" \"RuntimeKeepFree=^.+$\" \"MaxFileSec=^.+$\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: ***\" \" \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/systemd/journald.conf` or a file ending in `.conf` the `/etc/systemd/journald.conf.d/` directory. Set the following parameters in the `[Journal]` section to ensure logs are rotated according to site policy. The settings should be carefully understood as there are specific edge cases and prioritization of parameters.\n\n*Example Configuration*:\n\n```\n[Journal]\nSystemMaxUse=1G\nSystemKeepFree=500M\nRuntimeMaxUse=200M\nRuntimeKeepFree=50M\nMaxFileSec=1month\n```\n\n*Example script to create systemd drop-in configuration file:*\n\n```\n{\n a_settings=(\"SystemMaxUse=1G\" \"SystemKeepFree=500M\" \"RuntimeMaxUse=200M\" \"RuntimeKeepFree=50M\" \"MaxFileSec=1month\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n```\n\n**Note:**\n\n- If these settings appear in a canonically later file, or later in the same file, the setting will be overwritten\n\n- Logfile size and configuration to move logfiles to a remote log server should be accounted for when configuring these settings\n\nRun to following command to update the parameters in the service:\n\n```\n# systemctl reload-or-restart systemd-journald\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use", + "title": "6.1.1.4 Ensure only one logging system is in use", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use_smt", + "name": "statement", + "prose": "Best practices recommend that a single centralized logging system be used for log management, choose a single service either `rsyslog` **- OR -** `journald` to be used as a single centralized logging system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use_rationale", + "name": "rationale", + "prose": "Configuring only one logging service either `rsyslog` **- OR -** `journald` avoids redundancy, optimizes resources, simplifies configuration and management, and ensures consistency." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure only one logging system is in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use_obj" + }, + { + "rel": "script", + "href": "#d6aa2e15-2064-5c18-b653-a8a03f13d1d8" + } + ], + "prose": "Run the following script to ensure only one logging system is in use:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" # Check the status of rsyslog and journald\n if systemctl is-active --quiet rsyslog; then\n l_output=\"$l_output\\n - rsyslog is in use\\n- follow the recommendations in Configure rsyslog subsection only\"\n elif systemctl is-active --quiet systemd-journald; then\n l_output=\"$l_output\\n - journald is in use\\n- follow the recommendations in Configure journald subsection only\"\n else\n echo -e “unable to determine system logging”\n l_output2=\"$l_output2\\n - unable to determine system logging\\n- Configure only ONE system logging: rsyslog OR journald\"\n fi\n if [ -z \"$l_output2\" ]; then # Provide audit results\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Reason(s) for audit failure:\\n$l_output2\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "- Determine whether to use `journald` **- OR -** `rsyslog` depending on site needs\n\n- Configure `systemd-jounald.service`\n\n- Configure only **ONE** either `journald` **- OR -** `rsyslog` and complete the recommendations in that subsection\n\n- Return to this recommendation to ensure only one logging system is in use\n\nImpact:\n\nTransitioning from one logging service to another can be complex and time consuming, it involves reconfiguration and may result in data loss if not managed and reconfigured correctly." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.1.2_Configure_journald", + "title": "Configure journald", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.1.2_Configure_journald_recommendations", + "title": "Configure journald (the section's own recommendations)", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled", + "title": "6.1.2.2 Ensure journald ForwardToSyslog is disabled", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_systemd_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "ForwardToSyslog=no:systemd/journald.conf" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled_smt", + "name": "statement", + "prose": "Data from `journald` should be kept in the confines of the service and not forwarded to other services." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled_rationale", + "name": "rationale", + "prose": "**- IF -** `journald` is the method for capturing logs, all logs of the system should be handled by `journald` and not forwarded to other logging mechanisms.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled_obj", + "name": "assessment-objective", + "prose": "Ensure journald ForwardToSyslog is disabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled_obj" + }, + { + "rel": "script", + "href": "#b3f0988f-8e03-56a7-94fe-2a8b0c83dd45" + } + ], + "prose": "**- IF -** `journald` is the method for capturing logs\n\nRun the following script to verify `ForwardToSyslog` is set to `no`:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"ForwardToSyslog=no\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** `rsyslog` is the preferred method for capturing logs, this section and Recommendation should be skipped and the \"Configure rsyslog\" section followed.\n\n**- IF -** `journald` is the preferred method for capturing logs:\n\nSet the following parameter in the `[Journal]` section in `/etc/systemd/journald.conf` or a file in /etc/systemd/journald.conf.d/ ending in `.conf`:\n\n```\nForwardToSyslog=no\n```\n\n*Example script to create systemd drop-in configuration file:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_settings=(\"ForwardToSyslog=no\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n```\n\n**Note:** If this setting appears in a canonically later file, or later in the same file, the setting will be overwritten\n\nRun to following command to update the parameters in the service:\n\n```\n# systemctl reload-or-restart systemd-journald\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured", + "title": "6.1.2.3 Ensure journald Compress is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_systemd_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "Compress=yes:systemd/journald.conf" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/3" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured_smt", + "name": "statement", + "prose": "The journald system includes the capability of compressing overly large files to avoid filling up the system with logs or making the logs unmanageably large." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured_rationale", + "name": "rationale", + "prose": "Uncompressed large files may unexpectedly fill a filesystem leading to resource unavailability. Compressing logs prior to write can prevent sudden, unexpected filesystem impacts.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure journald Compress is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured_obj" + }, + { + "rel": "script", + "href": "#b3f0988f-8e03-56a7-94fe-2a8b0c83dd45" + } + ], + "prose": "**- IF -** `journald` is the method for capturing logs\n\nRun the following script to verify `Compress` is set to `yes`:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"Compress=yes\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** `rsyslog` is the preferred method for capturing logs, this section and Recommendation should be skipped and the \"Configure rsyslog\" section followed.\n\n**- IF -** `journald` is the preferred method for capturing logs:\n\nSet the following parameter in the `[Journal]` section in `/etc/systemd/journald.conf` or a file in `/etc/systemd/journald.conf.d/` ending in `.conf`:\n\n```\nCompress=yes\n```\n\n*Example script to create systemd drop-in configuration file:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_settings=(\"Compress=yes\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n```\n\n**Note:** If this setting appears in a canonically later file, or later in the same file, the setting will be overwritten\n\nRun to following command to update the parameters in the service:\n\n```\n# systemctl reload-or-restart systemd-journald\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured", + "title": "6.1.2.4 Ensure journald Storage is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_systemd_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "Storage=persistent:systemd/journald.conf" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured_smt", + "name": "statement", + "prose": "Data from journald may be stored in volatile memory or persisted locally on the server. Logs in memory will be lost upon a system reboot. By persisting logs to local disk on the server they are protected from loss due to a reboot." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured_rationale", + "name": "rationale", + "prose": "Writing log data to disk will provide the ability to forensically reconstruct events which may have impacted the operations or security of a system even after a system crash or reboot.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure journald Storage is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured_obj" + }, + { + "rel": "script", + "href": "#b3f0988f-8e03-56a7-94fe-2a8b0c83dd45" + } + ], + "prose": "**- IF -** `journald` is the method for capturing logs\n\nRun the following script to verify `Storage` is set to `persistent`:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"Storage=persistent\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** `rsyslog` is the preferred method for capturing logs, this section and Recommendation should be skipped and the \"Configure rsyslog\" section followed.\n\n**- IF -** `journald` is the preferred method for capturing logs:\n\nSet the following parameter in the `[Journal]` section in `/etc/systemd/journald.conf` or a file in /etc/systemd/journald.conf.d/ ending in `.conf`:\n\n```\nStorage=persistent\n```\n\n*Example script to create systemd drop-in configuration file:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_settings=(\"Storage=persistent\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n```\n\n**Note:** If this setting appears in a canonically later file, or later in the same file, the setting will be overwritten\n\nRun to following command to update the parameters in the service:\n\n```\n# systemctl reload-or-restart systemd-journald\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.1.2.1_Configure_systemd-journal-remote", + "title": "Configure systemd-journal-remote", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed", + "title": "6.1.2.1.1 Ensure systemd-journal-remote is installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed_smt", + "name": "statement", + "prose": "Journald `systemd-journal-remote` supports the ability to send log events it gathers to a remote log host or to receive messages from remote hosts, thus enabling centralized log management." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed_rationale", + "name": "rationale", + "prose": "Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local system.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure systemd-journal-remote is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed_obj" + } + ], + "prose": "**- IF -** `journald` will be used for logging on the system:\n\nRun the following command to verify `systemd-journal-remote` is installed.\n\n```\n# dpkg-query -s systemd-journal-remote &>/dev/null && echo \"systemd-journal-remote is installed\"\n```\n\nVerify the output matches:\n\n```\nsystemd-journal-remote is installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to install `systemd-journal-remote`:\n\n```\n# apt install systemd-journal-remote\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured", + "title": "6.1.2.1.2 Ensure systemd-journal-upload authentication is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured_smt", + "name": "statement", + "prose": "Journald `systemd-journal-upload` supports the ability to send log events it gathers to a remote log host." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured_rationale", + "name": "rationale", + "prose": "Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local system.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure systemd-journal-upload authentication is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured_obj" + } + ], + "prose": "Run the following script to verify `systemd-journal-upload` authentication is configured:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journal-upload.conf\"\n a_parameters=(\"URL=^.+$\" \"ServerKeyFile=^.+$\" \"ServerCertificateFile=^.+$\" \"TrustedCertificateFile=^.+$\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: ***\" \" \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```\n\nReview the output to ensure it matches your environments' certificate locations and the URL of the log server:\n\n*Example output:*\n\n```\n- Audit Result:\n ** PASS **\n - Parameter: \"URL\"\n set to: \"192.168.50.42\"\n in the file: \"/etc/systemd/journal-upload.conf.d/60-journald_upload.conf\"\n - Parameter: \"ServerKeyFile\"\n set to: \"/etc/ssl/private/journal-upload.pem\"\n in the file: \"/etc/systemd/journal-upload.conf.d/60-journald_upload.conf\"\n - Parameter: \"ServerCertificateFile\"\n set to: \"/etc/ssl/certs/journal-upload.pem\"\n in the file: \"/etc/systemd/journal-upload.conf.d/60-journald_upload.conf\"\n - Parameter: \"TrustedCertificateFile\"\n set to: \"/etc/ssl/ca/trusted.pem\"\n in the file: \"/etc/systemd/journal-upload.conf.d/60-journald_upload.conf\"\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `/etc/systemd/journal-upload.conf` file or a file in `/etc/systemd/journal-upload.conf.d` ending in `.conf` and ensure the following lines are set in the `[Upload]` section per your environment:\n\n*Example settings:*\n\n```\n[Upload]\nURL=192.168.50.42\nServerKeyFile=/etc/ssl/private/journal-upload.pem\nServerCertificateFile=/etc/ssl/certs/journal-upload.pem\nTrustedCertificateFile=/etc/ssl/ca/trusted.pem\n```\n\n*Example script to create systemd drop-in configuration file:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_settings=(\"URL=192.168.50.42\" \"ServerKeyFile=/etc/ssl/private/journal-upload.pem\" \\\n \"ServerCertificateFile=/etc/ssl/certs/journal-upload.pem\" \"TrustedCertificateFile=/etc/ssl/ca/trusted.pem\")\n [ ! -d /etc/systemd/journal-upload.conf.d/ ] && mkdir /etc/systemd/journal-upload.conf.d/\n if grep -Psq -- '^\\h*\\[Upload\\]' /etc/systemd/journal-upload.conf.d/60-journald_upload.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journal-upload.conf.d/60-journald_upload.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journal-upload.conf.d/60-journald_upload.conf\n fi\n}\n```\n\nRun the following command to update the parameters in the service:\n\n```\n# systemctl reload-or-restart systemd-journal-upload\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active", + "title": "6.1.2.1.3 Ensure systemd-journal-upload is enabled and active", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active_smt", + "name": "statement", + "prose": "Journald `systemd-journal-upload` supports the ability to send log events it gathers to a remote log host." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active_rationale", + "name": "rationale", + "prose": "Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local system.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active_obj", + "name": "assessment-objective", + "prose": "Ensure systemd-journal-upload is enabled and active" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active_obj" + } + ], + "prose": "Run the following command to verify `systemd-journal-upload` is enabled.\n\n```\n# systemctl is-enabled systemd-journal-upload.service\n\nenabled\n```\n\nRun the following command to verify `systemd-journal-upload` is active:\n\n```\n# systemctl is-active systemd-journal-upload.service\n\nactive\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to unmask, enable and start `systemd-journal-upload`:\n\n```\n# systemctl unmask systemd-journal-upload.service\n# systemctl --now enable systemd-journal-upload.service\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use", + "title": "6.1.2.1.4 Ensure systemd-journal-remote service is not in use", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use_smt", + "name": "statement", + "prose": "Journald `systemd-journal-remote` supports the ability to receive messages from remote hosts, thus acting as a log server. Clients should not receive data from other hosts.\n\n**Note:**\n\n- The same package, `systemd-journal-remote`, is used for both sending logs to remote hosts and receiving incoming logs.\n\n- With regards to receiving logs, there are two services; `systemd-journal-remote.socket` and `systemd-journal-remote.service`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use_rationale", + "name": "rationale", + "prose": "If a client is configured to also receive data, thus turning it into a server, the client system is acting outside it's operational boundary.\n\n**Note:** This recommendation **only applies if `journald` is the chosen method for client side logging**. Do not apply this recommendation if `rsyslog` is used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use_obj", + "name": "assessment-objective", + "prose": "Ensure systemd-journal-remote service is not in use" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use_obj" + } + ], + "prose": "Run the following command to verify `systemd-journal-remote.socket` and `systemd-journal-remote.service` are not enabled:\n\n```\n# systemctl is-enabled systemd-journal-remote.socket systemd-journal-remote.service | grep -P -- '^enabled'\n```\n\nNothing should be returned\n\nRun the following command to verify `systemd-journal-remote.socket` and `systemd-journal-remote.service` are not active:\n\n```\n# systemctl is-active systemd-journal-remote.socket systemd-journal-remote.service | grep -P -- '^active'\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to stop and mask `systemd-journal-remote.socket` and systemd-journal-remote.service:\n\n```\n# systemctl stop systemd-journal-remote.socket systemd-journal-remote.service\n# systemctl mask systemd-journal-remote.socket systemd-journal-remote.service\n```" + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.1.3_Configure_rsyslog", + "title": "Configure rsyslog", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed", + "title": "6.1.3.1 Ensure rsyslog is installed", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_systemd_parameter_not_match_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "ForwardToSyslog=yes:/etc/systemd/journald.conf" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed_smt", + "name": "statement", + "prose": "The `rsyslog` software is recommended in environments where `journald` does not meet operation requirements." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed_rationale", + "name": "rationale", + "prose": "The security enhancements of `rsyslog` such as connection-oriented (i.e. TCP) transmission of logs, the option to log to database formats, and the encryption of log data en route to a central logging server) justify installing and configuring the package." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure rsyslog is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed_obj" + }, + { + "rel": "script", + "href": "#c462a465-0f39-52c6-86d2-23251f051b85" + } + ], + "prose": "**- IF -** `rsyslog` is being used for logging on the system:\n\nRun the following command to verify `rsyslog` is installed:\n\n```\n# dpkg-query -s rsyslog &>/dev/null && echo \"rsyslog is installed\"\n```\n\nVerify the output matches:\n\n```\nrsyslog is installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to install `rsyslog`:\n\n```\n# apt install rsyslog\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active", + "title": "6.1.3.2 Ensure rsyslog service is enabled and active", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_systemd_parameter_not_match_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "ForwardToSyslog=yes:/etc/systemd/journald.conf" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active_smt", + "name": "statement", + "prose": "Once the `rsyslog` package is installed, ensure that the service is enabled." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active_rationale", + "name": "rationale", + "prose": "If the `rsyslog` service is not enabled to start on boot, the system will not capture logging events." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active_obj", + "name": "assessment-objective", + "prose": "Ensure rsyslog service is enabled and active" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active_obj" + }, + { + "rel": "script", + "href": "#c462a465-0f39-52c6-86d2-23251f051b85" + } + ], + "prose": "**- IF -** `rsyslog` is being used for logging on the system:\n\nRun the following command to verify `rsyslog.service` is enabled:\n\n```\n# systemctl is-enabled rsyslog\n\nenabled\n```\n\nRun the following command to verify `rsyslog.service` is active:\n\n```\n# systemctl is-active rsyslog.service\n\nactive\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** `rsyslog` is being used for logging on the system:\n\nRun the following commands to unmask, enable, and start `rsyslog.service`:\n\n```\n# systemctl unmask rsyslog.service\n# systemctl enable rsyslog.service\n# systemctl start rsyslog.service\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog", + "title": "6.1.3.3 Ensure journald is configured to send logs to rsyslog", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_systemd_parameter_chk_v3.sh as XCCDF_VALUE_REGEX", + "values": [ + "ForwardToSyslog=yes:systemd/journald.conf" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/9" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog_smt", + "name": "statement", + "prose": "Data from `systemd-journald` may be stored in volatile memory or persisted locally on the server. Utilities exist to accept remote export of `systemd-journald` logs, however, use of the `rsyslog` service provides a consistent means of log collection and export." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog_rationale", + "name": "rationale", + "prose": "**- IF -** `rsyslog` is the preferred method for capturing logs, all logs of the system should be sent to it for further processing.\n\n**Note:** This recommendation **only applies if `rsyslog` is the chosen method for client side logging**. Do not apply this recommendation if `systemd-journald` is used." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog_obj", + "name": "assessment-objective", + "prose": "Ensure journald is configured to send logs to rsyslog" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog_obj" + }, + { + "rel": "script", + "href": "#b3f0988f-8e03-56a7-94fe-2a8b0c83dd45" + } + ], + "prose": "**- IF -** `rsyslog` is the preferred method for capturing logs\n\nRun the following script to verify that logs are forwarded to `rsyslog` by setting `ForwardToSyslog` to `yes` in the systemd-journald configuration:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_systemd_config_file=\"systemd/journald.conf\"\n a_parameters=(\"ForwardToSyslog=yes\")\n f_config_file_parameter_chk()\n {\n l_used_parameter_setting=\"\"\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"$l_systemd_config_file\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -n \"$l_used_parameter_setting\" ]; then\n while IFS=: read -r l_file_name l_file_parameter; do\n while IFS=\"=\" read -r l_file_parameter_name l_file_parameter_value; do\n if grep -Pq -- \"$l_parameter_value\" <<< \"$l_file_parameter_value\"; then\n a_output+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" correctly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\")\n else\n a_output2+=(\" - Parameter: \\\"${l_file_parameter_name// /}\\\"\" \\\n \" incorrectly set to: \\\"${l_file_parameter_value// /}\\\"\" \\\n \" in the file: \\\"$l_file_name\\\"\" \\\n \" Should be set to: \\\"$l_value_out\\\"\")\n fi\n done <<< \"$l_file_parameter\"\n done <<< \"$l_used_parameter_setting\"\n else\n a_output2+=(\" - Parameter: \\\"$l_parameter_name\\\" is not set in an included file\" \\\n \" *** Note: \\\"$l_parameter_name\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n }\n for l_input_parameter in \"${a_parameters[@]}\"; do\n while IFS=\"=\" read -r l_parameter_name l_parameter_value; do # Assess and check parameters\n l_parameter_name=\"${l_parameter_name// /}\"; l_parameter_value=\"${l_parameter_value// /}\"\n l_value_out=\"${l_parameter_value//-/ through }\"; l_value_out=\"${l_value_out//|/ or }\"\n l_value_out=\"$(tr -d '(){}' <<< \"$l_value_out\")\"\n f_config_file_parameter_chk\n done <<< \"$l_input_parameter\"\n done\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```\n\nRun the following command to verify `systemd-journald.service` and `rsyslog.service` are loaded and active:\n\n```\n# systemctl list-units --type service | grep -P -- '(journald|rsyslog)'\n```\n\nOutput should be similar to:\n\n```\nrsyslog.service loaded active running System Logging Service\nsystemd-journald.service loaded active running Journal Service\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**- IF -** `Journald` is the preferred method for capturing logs, this section and Recommendation should be skipped and the \"Configure Journald\" section followed.\n\n**- IF -** `rsyslog` is the preferred method for capturing logs:\n\nSet the following parameter in the `[Journal]` section in `/etc/systemd/journald.conf` or a file in `/etc/systemd/journald.conf.d/` ending in `.conf`:\n\n```\nForwardToSyslog=yes\n```\n\n*Example script to create systemd drop-in configuration file:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_settings=(\"ForwardToSyslog=yes\")\n [ ! -d /etc/systemd/journald.conf.d/ ] && mkdir /etc/systemd/journald.conf.d/\n if grep -Psq -- '^\\h*\\[Journal\\]' /etc/systemd/journald.conf.d/60-journald.conf; then\n printf '%s\\n' \"\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n else\n printf '%s\\n' \"\" \"[Journal]\" \"${a_settings[@]}\" >> /etc/systemd/journald.conf.d/60-journald.conf\n fi\n}\n```\n\n**Note:** If this setting appears in a canonically later file, or later in the same file, the setting will be overwritten\n\nRun to following command to update the parameters in the service:\n\nRestart `systemd-journald.service`:\n\n```\n# systemctl reload-or-restart systemd-journald.service\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured", + "title": "6.1.3.4 Ensure rsyslog log file creation mode is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_rsyslog_filecreatemode_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "0137" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured_smt", + "name": "statement", + "prose": "`rsyslog` will create logfiles that do not already exist on the system.\n\nThe `global()` configuration object `umask`, available in rsyslog 8.26.0+, sets the rsyslogd process’ umask. If not specified, the system-provided default is used. The value given must always be a 4-digit octal number, with the initial digit being zero.\n\nThe legacy `$umask` parameter sets the `rsyslogd` process' umask. If not specified, the system-provided default is used. The value given must always be a 4-digit octal number, with the initial digit being zero.\n\nThe legacy `$FileCreateMode` parameter allows the setting of the mode with which `rsyslogd` creates new files. If not specified, the value `0644` is used. The value given must always be a 4-digit octal number, with the initial digit being zero. Please note that the actual permission depend on `rsyslogd` process `umask`. If in doubt, use `$umask 0000` right at the beginning of the configuration file to remove any restrictions.\n\nThe legacy `$FileCreateMode` may be specified multiple times. If so, it specifies the creation mode for all selector lines that follow until the next `$FileCreateMode` parameter. Order of lines is vitally important." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured_rationale", + "name": "rationale", + "prose": "It is important to ensure that log files have the correct permissions to ensure that sensitive data is archived and protected." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure rsyslog log file creation mode is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured_obj" + }, + { + "rel": "script", + "href": "#a264fe5d-1388-5bc2-b887-44c0d6a5304f" + } + ], + "prose": "Run the following command\n\nRun the following script to verify `$FileCreateMode` to set to mode `0640` or more restrictive:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\"\n l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\") l_parameter_name='\\$FileCreateMode'\n f_parameter_chk()\n {\n l_perm_mask=\"0137\"; l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n l_mode=\"$(awk '{print $2}' <<< \"$l_used_parameter_setting\" | xargs)\"\n if [ $(( $l_mode & $l_perm_mask )) -gt 0 ]; then\n a_output2+=(\" - Parameter: \\\"${l_parameter_name//\\\\/}\\\" is incorrectly set to mode: \\\"$l_file_mode\\\"\" \\\n \" in the file: \\\"$l_file\\\"\" \" Should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n else\n a_output+=(\" - Parameter: \\\"${l_parameter_name//\\\\/}\\\" is correctly set to mode: \\\"$l_file_mode\\\"\" \\\n \" in the file: \\\"$l_file\\\"\" \" Should be mode: \\\"$l_maxperm\\\" or more restrictive\")\n fi\n }\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[*]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n while IFS= read -r l_file; do\n l_file=\"$(tr -d '# ' <<< \"$l_file\")\"\n l_used_parameter_setting=\"$(grep -PHs -- '^\\h*'\"$l_parameter_name\"'\\b' \"$l_file\" | tail -n 1)\"\n [ -n \"$l_used_parameter_setting\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n\n if [ -n \"$l_used_parameter_setting\" ]; then\n f_parameter_chk\n else\n a_output2+=(\" - Parameter: \\\"${l_parameter_name//\\\\/}\\\" is not set in a configuration file\" \\\n \" *** Note: \\\"${l_parameter_name//\\\\/}\\\" May be set in a file that's ignored by load procedure ***\")\n fi\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit either `/etc/rsyslog.conf` or a dedicated `.conf` file in `/etc/rsyslog.d/` and set `$FileCreateMode` to `0640` or more restrictive:\n\n```\n$FileCreateMode 0640\n```\n\n*Example script to create a drop-in configuration file in the default include location:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n [ ! -d \"/etc/rsyslog.d/\" ] && mkdir /etc/rsyslog.d/\n printf '%s\\n' \"\" \"\\$FileCreateMode 0640\" >> /etc/rsyslog.d/60-rsyslog.conf\n}\n```\n\nReload the service:\n\n```\n# systemctl reload-or-restart rsyslog\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured", + "title": "6.1.3.5 Ensure rsyslog logging is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured_smt", + "name": "statement", + "prose": "The `rsyslog` and configuration files specifies rules for logging and which files are to be used to log certain classes of messages." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured_rationale", + "name": "rationale", + "prose": "A great deal of important security-related information is sent via `rsyslog` (e.g., successful and failed su attempts, failed login attempts, root login attempts, etc.)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure rsyslog logging is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured_obj" + } + ], + "prose": "Review the contents of `/etc/rsyslog.conf` and `/etc/rsyslog.d/*.conf` files to ensure appropriate logging is set. In addition, run the following command and verify that the log files are logging information as expected:\n\nRun the following script and review the output from the `rsyslog` configuration to ensure appropriate logging is set an in accordance with local site policy.\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\")\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n for l_logfile in \"${a_config_files[@]}\"; do\n grep -PHs -- '^\\h*[^#\\n\\r\\/:]+\\/var\\/log\\/.*$' \"$l_logfile\"\n done\n}\n```\n\n*Example output:*\n\n```\n/etc/rsyslog.d/60-rsyslog.conf:auth,authpriv.* /var/log/secure\n/etc/rsyslog.d/60-rsyslog.conf:mail.* -/var/log/mail\n/etc/rsyslog.d/60-rsyslog.conf:mail.info -/var/log/mail.info\n/etc/rsyslog.d/60-rsyslog.conf:mail.warning -/var/log/mail.warn\n/etc/rsyslog.d/60-rsyslog.conf:mail.err /var/log/mail.err\n/etc/rsyslog.d/60-rsyslog.conf:cron.* /var/log/cron\n/etc/rsyslog.d/60-rsyslog.conf:*.=warning;*.=err -/var/log/warn\n/etc/rsyslog.d/60-rsyslog.conf:*.crit /var/log/warn\n/etc/rsyslog.d/60-rsyslog.conf:*.*;mail.none;news.none -/var/log/messages\n/etc/rsyslog.d/60-rsyslog.conf:local0,local1.* -/var/log/localmessages\n/etc/rsyslog.d/60-rsyslog.conf:local2,local3.* -/var/log/localmessages\n/etc/rsyslog.d/60-rsyslog.conf:local4,local5.* -/var/log/localmessages\n/etc/rsyslog.d/60-rsyslog.conf:local6,local7.* -/var/log/localmessages\n/etc/rsyslog.d/50-default.conf:auth,authpriv.* /var/log/auth.log #<- Will be ignored\n/etc/rsyslog.d/50-default.conf:*.*;auth,authpriv.none -/var/log/syslog\n/etc/rsyslog.d/50-default.conf:kern.* -/var/log/kern.log\n/etc/rsyslog.d/50-default.conf:mail.* -/var/log/mail.log #<- Will be ignored\n/etc/rsyslog.d/50-default.conf:mail.err /var/log/mail.err #<- Will be ignored\n```\n\n**Note:**\n\n- Output is generated as :\n\n- Files are listed in order of precedence. If the same parameter is listed multiple times, only the first occurrence will be used be the `rsyslog` daemon" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the following lines in the configuration file(s) returned by the audit as appropriate for your environment.\n\n**Note:** The below configuration is shown for example purposes only. Due care should be given to how the organization wishes to store log data.\n\n```\n*.emerg :omusrmsg:*\nauth,authpriv.* /var/log/secure\nmail.* -/var/log/mail\nmail.info -/var/log/mail.info\nmail.warning -/var/log/mail.warn\nmail.err /var/log/mail.err\ncron.* /var/log/cron\n*.=warning;*.=err -/var/log/warn\n*.crit /var/log/warn\n*.*;mail.none;news.none -/var/log/messages\nlocal0,local1.* -/var/log/localmessages\nlocal2,local3.* -/var/log/localmessages\nlocal4,local5.* -/var/log/localmessages\nlocal6,local7.* -/var/log/localmessages\n```\n\nRun the following command to reload the `rsyslogd` configuration:\n\n```\n# systemctl reload-or-restart rsyslog\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host", + "title": "6.1.3.6 Ensure rsyslog is configured to send logs to a remote log host", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host_smt", + "name": "statement", + "prose": "`rsyslog` supports the ability to send log events it gathers to a remote log host or to receive messages from remote hosts, thus enabling centralized log management." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host_rationale", + "name": "rationale", + "prose": "Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host_obj", + "name": "assessment-objective", + "prose": "Ensure rsyslog is configured to send logs to a remote log host" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host_obj" + } + ], + "prose": "Run the following script and review the output of `rsyslog` configuration. Verify that logs are sent to a central host used by your organization:\n\n**basic format**\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\")\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n for l_logfile in \"${a_config_files[@]}\"; do\n grep -Hs -- \"^*.*[^I][^I]*@\" \"$l_logfile\"\n done\n}\n```\n\nOutput should include `@@`:\n\n*Example output:*\n\n```\n/etc/rsyslog.d/60-rsyslog.conf:*.* @@loghost.example.com\n```\n\n**- OR -**\nRun the following script and review the output of `rsyslog` configuration. Verify that logs are sent to a central host used by your organization:\n\n**advanced format**\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\")\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n for l_logfile in \"${a_config_files[@]}\"; do\n grep -PHsi -- '^\\s*([^#]+\\s+)?action\\(([^#]+\\s+)?\\btarget=\\\"?[^#\"]+\\\"?\\b' \"$l_logfile\"\n done\n}\n```\n\nOutput should include `target=`:\n\n*Example output:*\n\n```\n/etc/rsyslog.d/60-rsyslog.conf:*.* action(type=\"omfwd\" target=\"loghost.example.com\" port=\"514\" protocol=\"tcp\"\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the `rsyslog` configuration and add the following line (where `loghost.example.com` is the name of your central log host). The `target` directive may either be a fully qualified domain name or an IP address.\n\n*Example script to create a drop-in configuration file:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_parameters=('*.* action(type=\"omfwd\" target=\"loghost.example.com\" port=\"514\" protocol=\"tcp\"' \\\n ' action.resumeRetryCount=\"100\"' ' queue.type=\"LinkedList\" queue.size=\"1000\")')\n [ ! -d \"/etc/rsyslog.d/\" ] && mkdir /etc/rsyslod.d/\n printf '%s\\n' \"\" \"${a_parameters[@]}\" >> /etc/rsyslog.d/60-rsyslog.conf\n}\n```\n\nRun the following command to reload `rsyslog.service`:\n\n```\n# systemctl reload-or-restart rsyslog.service\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client", + "title": "6.1.3.7 Ensure rsyslog is not configured to receive logs from a remote client", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/4/subcontrol/8" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client_smt", + "name": "statement", + "prose": "`rsyslog` supports the ability to receive messages from remote hosts, thus acting as a log server. Clients should not receive data from other hosts." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client_rationale", + "name": "rationale", + "prose": "If a client is configured to also receive data, thus turning it into a server, the client system is acting outside its operational boundary." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client_obj", + "name": "assessment-objective", + "prose": "Ensure rsyslog is not configured to receive logs from a remote client" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client_obj" + }, + { + "rel": "script", + "href": "#6434d985-ed98-5289-a298-40e5bc3908c5" + } + ], + "prose": "Unless the system's primary function is to serve as a logfile server, run the following script to review the `rsyslog` configuration and verify that the system is not configured to accept incoming logs.\n\n**advanced format**\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=()\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_include='\\$IncludeConfig' a_config_files=(\"rsyslog.conf\")\n while IFS= read -r l_file; do\n l_conf_loc=\"$(awk '$1~/^\\s*'\"$l_include\"'$/ {print $2}' \"$(tr -d '# ' <<< \"$l_file\")\" | tail -n 1)\"\n [ -n \"$l_conf_loc\" ] && break\n done < <($l_analyze_cmd cat-config \"${a_config_files[@]}\" | tac | grep -Pio '^\\h*#\\h*\\/[^#\\n\\r\\h]+\\.conf\\b')\n if [ -d \"$l_conf_loc\" ]; then\n l_dir=\"$l_conf_loc\" l_ext=\"*\"\n elif grep -Psq '\\/\\*\\.([^#/\\n\\r]+)?\\h*$' <<< \"$l_conf_loc\" || [ -f \"$(readlink -f \"$l_conf_loc\")\" ]; then\n l_dir=\"$(dirname \"$l_conf_loc\")\" l_ext=\"$(basename \"$l_conf_loc\")\"\n fi\n while read -r -d $'\\0' l_file_name; do\n [ -f \"$(readlink -f \"$l_file_name\")\" ] && a_config_files+=(\"$(readlink -f \"$l_file_name\")\")\n done < <(find -L \"$l_dir\" -type f -name \"$l_ext\" -print0 2>/dev/null)\n for l_logfile in \"${a_config_files[@]}\"; do\n l_fail=\"$(grep -Psi -- '^\\h*module\\(load=\\\"?imtcp\\\"?\\)' \"$l_logfile\")\"\n [ -n \"$l_fail\" ] && a_output2+=(\"- Advanced format entry to accept incoming logs: \\\"$l_fail\\\"\" \"found in: \\\"$l_logfile\\\"\")\n l_fail=\"$(grep -Psi -- '^\\h*input\\(type=\\\"?imtcp\\\"?\\b' \"$l_logfile\")\"\n [ -n \"$l_fail\" ] && a_output2+=(\"- Advanced format entry to accept incoming logs: \\\"$l_fail\\\"\" \"found in: \\\"$l_logfile\\\"\")\n l_fail=\"$(grep -Psi -- '^\\h*module\\(load=\\\"?imtcp\\\"?\\)' \"$l_logfile\")\"\n [ -n \"$l_fail\" ] && a_output2+=(\"- Obsolete format entry to accept incoming logs: \\\"$l_fail\\\"\" \"found in: \\\"$l_logfile\\\"\")\n l_fail=\"$(grep -Psi -- '^\\h*input\\(type=\\\"?imtcp\\\"?\\b' \"$l_logfile\")\"\n [ -n \"$l_fail\" ] && a_output2+=(\"- Obsolete format entry to accept incoming logs: \\\"$l_fail\\\"\" \"found in: \\\"$l_logfile\\\"\")\n done\n if [ \"${#a_output2[@]}\" -le \"0\" ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \" - No entries to accept incoming logs found\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Unless the system's primary function is to serve as a logfile server , modify the files returned by the Audit Procedure and remove the specific lines highlighted by the audit. Verify none of the following entries are present in the `rsyslog` configuration.\n\n**advanced format**\n\n```\nmodule(load=\"imtcp\")\ninput(type=\"imtcp\" port=\"514\")\n```\n\n**deprecated legacy format**\n\n```\n$ModLoad imtcp\n$InputTCPServerRun\n```\n\nReload the service:\n\n```\n# systemctl reload-or-restart rsyslog\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured", + "title": "6.1.3.8 Ensure logrotate is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured_smt", + "name": "statement", + "prose": "The system includes the capability of rotating log files regularly to avoid filling up the system with logs or making the logs unmanageably large. The file `/etc/logrotate.d/rsyslog` is the configuration file used to rotate log files created by `rsyslog`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured_rationale", + "name": "rationale", + "prose": "By keeping the log files smaller and more manageable, a system administrator can easily archive these files to another system and spend less time looking through inordinately large log files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure logrotate is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured_obj" + } + ], + "prose": "Run the following script to analyze the `logrotate` configuration:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_analyze_cmd=\"$(readlink -f /bin/systemd-analyze)\" l_config_file=\"/etc/logrotate.conf\"\n l_include=\"$(awk '$1~/^\\s*include$/{print$2}' \"$l_config_file\" 2>/dev/null)\"\n [ -d \"$l_include\" ] && l_include=\"$l_include/*\"\n $l_analyze_cmd cat-config \"$l_config_file\" $l_include\n}\n```\n\n**Note:** The last occurrence of a argument is the one used for the `logrotate` configuration" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/logrotate.conf`, or the appropriate configuration file provided by the script in the Audit Procedure, as necessary to ensure logs are rotated according to site policy." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.1.4_Configure_Logfiles", + "title": "Configure Logfiles", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured", + "title": "6.1.4.1 Ensure access to all logfiles has been configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured_smt", + "name": "statement", + "prose": "Log files contain information from many services on the the local system, or in the event of a centralized log server, others systems logs as well.\n\nIn general log files are found in `/var/log/`, although application can be configured to store logs elsewhere. Should your application store logs in another, ensure to run the same test on that location." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured_rationale", + "name": "rationale", + "prose": "It is important that log files have the correct permissions to ensure that sensitive data is protected and that only the appropriate users / groups have access to them." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured_obj", + "name": "assessment-objective", + "prose": "Ensure access to all logfiles has been configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured_obj" + }, + { + "rel": "script", + "href": "#6e3721be-ede6-5c6c-8816-981a95705b19" + } + ], + "prose": "Run the following script to verify that files in `/var/log/` have appropriate permissions and ownership:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=(); a_output2=()\n f_file_test_chk()\n {\n a_out2=()\n maxperm=\"$( printf '%o' $(( 0777 & ~$perm_mask)) )\"\n [ $(( $l_mode & $perm_mask )) -gt 0 ] && \\\n a_out2+=(\" o Mode: \\\"$l_mode\\\" should be \\\"$maxperm\\\" or more restrictive\")\n [[ ! \"$l_user\" =~ $l_auser ]] && \\\n a_out2+=(\" o Owned by: \\\"$l_user\\\" and should be owned by \\\"${l_auser//|/ or }\\\"\")\n [[ ! \"$l_group\" =~ $l_agroup ]] && \\\n a_out2+=(\" o Group owned by: \\\"$l_group\\\" and should be group owned by \\\"${l_agroup//|/ or }\\\"\")\n [ \"${#a_out2[@]}\" -gt 0 ] && a_output2+=(\" - File: \\\"$l_fname\\\" is:\" \"${a_out2[@]}\")\n }\n while IFS= read -r -d $'\\0' l_file; do\n while IFS=: read -r l_fname l_mode l_user l_group; do\n if grep -Pq -- '\\/(apt)\\h*$' <<< \"$(dirname \"$l_fname\")\"; then\n perm_mask='0133' l_auser=\"root\" l_agroup=\"(root|adm)\"; f_file_test_chk\n else\n case \"$(basename \"$l_fname\")\" in\n lastlog | lastlog.* | wtmp | wtmp.* | wtmp-* | btmp | btmp.* | btmp-* | README)\n perm_mask='0113' l_auser=\"root\" l_agroup=\"(root|utmp)\"\n f_file_test_chk ;;\n cloud-init.log* | localmessages* | waagent.log*)\n perm_mask='0133' l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n file_test_chk ;;\n secure{,*.*,.*,-*} | auth.log | syslog | messages)\n perm_mask='0137' l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n f_file_test_chk ;;\n SSSD | sssd)\n perm_mask='0117' l_auser=\"(root|SSSD)\" l_agroup=\"(root|SSSD)\"\n f_file_test_chk ;;\n gdm | gdm3)\n perm_mask='0117' l_auser=\"root\" l_agroup=\"(root|gdm|gdm3)\"\n f_file_test_chk ;;\n *.journal | *.journal~)\n perm_mask='0137' l_auser=\"root\" l_agroup=\"(root|systemd-journal)\"\n f_file_test_chk ;;\n *)\n perm_mask='0137' l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n if [ \"$l_user\" = \"root\" ] || ! grep -Pq -- \"^\\h*$(awk -F: '$1==\"'\"$l_user\"'\" {print $7}' /etc/passwd)\\b\" /etc/shells; then\n ! grep -Pq -- \"$l_auser\" <<< \"$l_user\" && l_auser=\"(root|syslog|$l_user)\"\n ! grep -Pq -- \"$l_agroup\" <<< \"$l_group\" && l_agroup=\"(root|adm|$l_group)\"\n fi\n f_file_test_chk ;;\n esac\n fi\n done < <(stat -Lc '%n:%#a:%U:%G' \"$l_file\")\n done < <(find -L /var/log -type f \\( -perm /0137 -o ! -user root -o ! -group root \\) -print0)\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n a_output+=(\" - All files in \\\"/var/log/\\\" have appropriate permissions and ownership\")\n printf '\\n%s' \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '\\n%s' \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\" \"\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following script to update permissions and ownership on files in `/var/log`.\n\nAlthough the script is not destructive, ensure that the output of the audit procedure is captured in the event that the remediation causes issues.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=()\n f_file_test_fix()\n {\n a_out2=()\n maxperm=\"$( printf '%o' $(( 0777 & ~$perm_mask)) )\"\n if [ $(( $l_mode & $perm_mask )) -gt 0 ]; then\n a_out2+=(\" o Mode: \\\"$l_mode\\\" should be \\\"$maxperm\\\" or more restrictive\" \" x Removing excess permissions\")\n chmod \"$l_rperms\" \"$l_fname\"\n fi\n if [[ ! \"$l_user\" =~ $l_auser ]]; then\n a_out2+=(\" o Owned by: \\\"$l_user\\\" and should be owned by \\\"${l_auser//|/ or }\\\"\" \" x Changing ownership to: \\\"$l_fix_account\\\"\")\n chown \"$l_fix_account\" \"$l_fname\"\n fi\n if [[ ! \"$l_group\" =~ $l_agroup ]]; then\n a_out2+=(\" o Group owned by: \\\"$l_group\\\" and should be group owned by \\\"${l_agroup//|/ or }\\\"\" \" x Changing group ownership to: \\\"$l_fix_account\\\"\")\n chgrp \"$l_fix_account\" \"$l_fname\"\n fi\n [ \"${#a_out2[@]}\" -gt 0 ] && a_output2+=(\" - File: \\\"$l_fname\\\" is:\" \"${a_out2[@]}\")\n }\n l_fix_account='root'\n while IFS= read -r -d $'\\0' l_file; do\n while IFS=: read -r l_fname l_mode l_user l_group; do\n if grep -Pq -- '\\/(apt)\\h*$' <<< \"$(dirname \"$l_fname\")\"; then\n perm_mask='0133' l_rperms=\"u-x,go-wx\" l_auser=\"root\" l_agroup=\"(root|adm)\"; f_file_test_fix\n else\n case \"$(basename \"$l_fname\")\" in\n lastlog | lastlog.* | wtmp | wtmp.* | wtmp-* | btmp | btmp.* | btmp-* | README)\n perm_mask='0113' l_rperms=\"ug-x,o-wx\" l_auser=\"root\" l_agroup=\"(root|utmp)\"\n f_file_test_fix ;;\n cloud-init.log* | localmessages* | waagent.log*)\n perm_mask='0133' l_rperms=\"u-x,go-wx\" l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n file_test_fix ;;\n secure | auth.log | syslog | messages)\n perm_mask='0137' l_rperms=\"u-x,g-wx,o-rwx\" l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n f_file_test_fix ;;\n SSSD | sssd)\n perm_mask='0117' l_rperms=\"ug-x,o-rwx\" l_auser=\"(root|SSSD)\" l_agroup=\"(root|SSSD)\"\n f_file_test_fix ;;\n gdm | gdm3)\n perm_mask='0117' l_rperms=\"ug-x,o-rwx\" l_auser=\"root\" l_agroup=\"(root|gdm|gdm3)\"\n f_file_test_fix ;;\n *.journal | *.journal~)\n perm_mask='0137' l_rperms=\"u-x,g-wx,o-rwx\" l_auser=\"root\" l_agroup=\"(root|systemd-journal)\"\n f_file_test_fix ;;\n *)\n perm_mask='0137' l_rperms=\"u-x,g-wx,o-rwx\" l_auser=\"(root|syslog)\" l_agroup=\"(root|adm)\"\n if [ \"$l_user\" = \"root\" ] || ! grep -Pq -- \"^\\h*$(awk -F: '$1==\"'\"$l_user\"'\" {print $7}' /etc/passwd)\\b\" /etc/shells; then\n ! grep -Pq -- \"$l_auser\" <<< \"$l_user\" && l_auser=\"(root|syslog|$l_user)\"\n ! grep -Pq -- \"$l_agroup\" <<< \"$l_group\" && l_agroup=\"(root|adm|$l_group)\"\n fi\n f_file_test_fix ;;\n esac\n fi\n done < <(stat -Lc '%n:%#a:%U:%G' \"$l_file\")\n done < <(find -L /var/log -type f \\( -perm /0137 -o ! -user root -o ! -group root \\) -print0)\n if [ \"${#a_output2[@]}\" -le 0 ]; then # If all files passed, then we report no changes\n a_output+=(\" - All files in \\\"/var/log/\\\" have appropriate permissions and ownership\")\n printf '\\n%s' \"- All files in \\\"/var/log/\\\" have appropriate permissions and ownership\" \" o No changes required\" \"\"\n else\n printf '\\n%s' \"${a_output2[@]}\" \"\"\n fi\n}\n```\n\n**Note:** You may also need to change the configuration for your logging software or services for any logs that had incorrect permissions.\n\nIf there are services that log to other locations, ensure that those log files have the appropriate permissions." + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.2_System_Auditing", + "title": "System Auditing", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.2.1_Configure_auditd_Service", + "title": "Configure auditd Service", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed", + "title": "6.2.1.1 Ensure auditd packages are installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed_smt", + "name": "statement", + "prose": "auditd is the userspace component to the Linux Auditing System. It's responsible for writing audit records to the disk" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed_rationale", + "name": "rationale", + "prose": "The capturing of system events provides system administrators with information to allow them to determine if unauthorized access to their system is occurring." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed_obj", + "name": "assessment-objective", + "prose": "Ensure auditd packages are installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed_obj" + } + ], + "prose": "Run the following command and verify `auditd` is installed:\n\n```\n# dpkg-query -s auditd &>/dev/null && echo auditd is installed\n\nauditd is installed\n```\n\nRun the following command to verify `audispd-plugins` is installed:\n\n```\n# dpkg-query -s audispd-plugins &>/dev/null && echo audispd-plugins is installed\n\naudispd-plugins is installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to Install `auditd` and `audispd-plugins`\n\n```\n# apt install auditd audispd-plugins\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active", + "title": "6.2.1.2 Ensure auditd service is enabled and active", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active_smt", + "name": "statement", + "prose": "Turn on the `auditd` daemon to record system events." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active_rationale", + "name": "rationale", + "prose": "The capturing of system events provides system administrators with information to allow them to determine if unauthorized access to their system is occurring." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active_obj", + "name": "assessment-objective", + "prose": "Ensure auditd service is enabled and active" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active_obj" + } + ], + "prose": "Run the following command to verify `auditd` is enabled:\n\n```\n# systemctl is-enabled auditd | grep '^enabled'\n\nenabled\n```\n\nVerify result is \"enabled\".\n\nRun the following command to verify `auditd` is active:\n\n```\n# systemctl is-active auditd | grep '^active'\n\nactive\n```\n\nVerify result is active" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to unmask, enable and start `auditd`:\n\n```\n# systemctl unmask auditd\n# systemctl enable auditd\n# systemctl start auditd\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled", + "title": "6.2.1.3 Ensure auditing for processes that start prior to auditd is enabled", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_grub_option_exist_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "audit=1" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled_smt", + "name": "statement", + "prose": "Configure `grub2` so that processes that are capable of being audited can be audited even if they start up prior to `auditd` startup." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled_rationale", + "name": "rationale", + "prose": "Audit events need to be captured on processes that start up prior to `auditd` , so that potential malicious activity cannot go undetected." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled_obj", + "name": "assessment-objective", + "prose": "Ensure auditing for processes that start prior to auditd is enabled" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled_obj" + }, + { + "rel": "script", + "href": "#98739ca0-ad70-55aa-8506-980b20cec38c" + } + ], + "prose": "Run the following command:\n\n```\n# find /boot -type f -name 'grub.cfg' -exec grep -Ph -- '^\\h*linux' {} + | grep -v 'audit=1'\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/default/grub` and add `audit=1` to `GRUB_CMDLINE_LINUX`:\n\nExample:\n\n```\nGRUB_CMDLINE_LINUX=\"audit=1\"\n```\n\nRun the following command to update the `grub2` configuration:\n\n```\n# update-grub\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient", + "title": "6.2.1.4 Ensure audit_backlog_limit is sufficient", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_grub_option_exist_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "audit_backlog_limit=\\d+" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient_smt", + "name": "statement", + "prose": "In the kernel-level audit subsystem, a socket buffer queue is used to hold audit events. Whenever a new audit event is received, it is logged and prepared to be added to this queue.\n\nThe kernel boot parameter `audit_backlog_limit=N`, with `N` representing the amount of messages, will ensure that a queue cannot grow beyond a certain size. If an audit event is logged which would grow the queue beyond this limit, then a failure occurs and is handled according to the system configuration" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient_rationale", + "name": "rationale", + "prose": "If an audit event is logged which would grow the queue beyond the `audit_backlog_limit`, then a failure occurs, auditd records will be lost, and potential malicious activity could go undetected." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient_obj", + "name": "assessment-objective", + "prose": "Ensure audit_backlog_limit is sufficient" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient_obj" + }, + { + "rel": "script", + "href": "#98739ca0-ad70-55aa-8506-980b20cec38c" + } + ], + "prose": "Run the following command and verify the `audit_backlog_limit=` parameter is set:\n\n```\n# find /boot -type f -name 'grub.cfg' -exec grep -Ph -- '^\\h*linux' {} + | grep -Pv 'audit_backlog_limit=\\d+\\b'\n```\n\nNothing should be returned." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit `/etc/default/grub` and add `audit_backlog_limit=N` to GRUB_CMDLINE_LINUX. The recommended size for `N` is `8192` or larger.\n\nExample:\n\n```\nGRUB_CMDLINE_LINUX=\"audit_backlog_limit=8192\"\n```\n\nRun the following command to update the `grub2` configuration:\n\n```\n# update-grub\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.2.2_Configure_Data_Retention", + "title": "Configure Data Retention", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured", + "title": "6.2.2.1 Ensure audit log storage size is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured_smt", + "name": "statement", + "prose": "Configure the maximum size of the audit log file. Once the log reaches the maximum size, it will be rotated and a new log file will be started." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured_rationale", + "name": "rationale", + "prose": "It is important that an appropriate size is determined for log files so that they do not impact the system and audit data is not lost." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit log storage size is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured_obj" + } + ], + "prose": "Run the following command and ensure output is in compliance with site policy:\n\n```\n# grep -Po -- '^\\h*max_log_file\\h*=\\h*\\d+\\b' /etc/audit/auditd.conf\n\nmax_log_file = \n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameter in `/etc/audit/auditd.conf` in accordance with site policy:\n\n```\nmax_log_file = \n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted", + "title": "6.2.2.2 Ensure audit logs are not automatically deleted", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted_smt", + "name": "statement", + "prose": "The `max_log_file_action` setting determines how to handle the audit log file reaching the max file size. A value of `keep_logs` will rotate the logs but never delete old logs." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted_rationale", + "name": "rationale", + "prose": "In high security contexts, the benefits of maintaining a long audit history exceed the cost of storing the audit history." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted_obj", + "name": "assessment-objective", + "prose": "Ensure audit logs are not automatically deleted" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted_obj" + } + ], + "prose": "Run the following command and verify output matches:\n\n```\n# grep max_log_file_action /etc/audit/auditd.conf\n\nmax_log_file_action = keep_logs\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the following parameter in `/etc/audit/auditd.conf:`\n\n```\nmax_log_file_action = keep_logs\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full", + "title": "6.2.2.3 Ensure system is disabled when audit logs are full", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full_smt", + "name": "statement", + "prose": "The `auditd` daemon can be configured to halt the system or put the system in single user mode, if no free space is available or an error is detected on the partition that holds the audit log files.\n\nThe `disk_full_action` parameter tells the system what action to take when no free space is available on the partition that holds the audit log files. Valid values are `ignore`, `syslog`, `rotate`, `exec`, `suspend`, `single`, and `halt`.\n\n- `ignore`, the audit daemon will issue a syslog message but no other action is taken\n\n- `syslog`, the audit daemon will issue a warning to syslog\n\n- `rotate`, the audit daemon will rotate logs, losing the oldest to free up space\n\n- `exec`, /path-to-script will execute the script. You cannot pass parameters to the script. The script is also responsible for telling the auditd daemon to resume logging once its completed its action\n\n- `suspend`, the audit daemon will stop writing records to the disk\n\n- `single`, the audit daemon will put the computer system in single user mode\n\n- `halt`, the audit daemon will shut down the system\n\nThe `disk_error_action` parameter tells the system what action to take when an error is detected on the partition that holds the audit log files. Valid values are `ignore`, `syslog`, `exec`, `suspend`, `single`, and `halt`.\n\n- `ignore`, the audit daemon will not take any action\n\n- `syslog`, the audit daemon will issue no more than 5 consecutive warnings to syslog\n\n- `exec`, /path-to-script will execute the script. You cannot pass parameters to the script\n\n- `suspend`, the audit daemon will stop writing records to the disk\n\n- `single`, the audit daemon will put the computer system in single user mode\n\n- `halt`, the audit daemon will shut down the system" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full_rationale", + "name": "rationale", + "prose": "In high security contexts, the risk of detecting unauthorized access or nonrepudiation exceeds the benefit of the system's availability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full_obj", + "name": "assessment-objective", + "prose": "Ensure system is disabled when audit logs are full" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full_obj" + } + ], + "prose": "Run the following command and verify the `disk_full_action` is set to either `halt` or `single`:\n\n```\n# grep -Pi -- '^\\h*disk_full_action\\h*=\\h*(halt|single)\\b' /etc/audit/auditd.conf\n\ndisk_full_action = \n```\n\nRun the following command and verify the `disk_error_action` is set to `syslog`, `single`, or `halt`:\n\n```\n# grep -Pi -- '^\\h*disk_error_action\\h*=\\h*(syslog|single|halt)\\b' /etc/audit/auditd.conf\n\ndisk_error_action = \n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set one of the following parameters in `/etc/audit/auditd.conf` depending on your local security policies.\n\n```\ndisk_full_action = \ndisk_error_action = \n```\n\n*Example:*\n\n```\ndisk_full_action = halt\ndisk_error_action = halt\n```\n\nImpact:\n\n`disk_full_action` parameter:\n\n- Set to `halt` - the `auditd` daemon will shutdown the system when the disk partition containing the audit logs becomes full.\n\n- Set to `single` - the `auditd` daemon will put the computer system in single user mode when the disk partition containing the audit logs becomes full.\n\n`disk_error_action` parameter:\n\n- Set to `halt` - the `auditd` daemon will shutdown the system when an error is detected on the partition that holds the audit log files.\n\n- Set to `single` - the `auditd` daemon will put the computer system in single user mode when an error is detected on the partition that holds the audit log files.\n\n- Set to `syslog` - the `auditd` daemon will issue no more than 5 consecutive warnings to syslog when an error is detected on the partition that holds the audit log files." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space", + "title": "6.2.2.4 Ensure system warns when audit logs are low on space", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space_smt", + "name": "statement", + "prose": "The `auditd` daemon can be configured to halt the system, put the system in single user mode or send a warning message, if the partition that holds the audit log files is low on space.\n\nThe `space_left_action` parameter tells the system what action to take when the system has detected that it is starting to get low on disk space. Valid values are `ignore`, `syslog`, `rotate`, `email`, `exec`, `suspend`, `single`, and `halt`.\n\n- `ignore`, the audit daemon does nothing\n\n- `syslog`, the audit daemon will issue a warning to syslog\n\n- `rotate`, the audit daemon will rotate logs, losing the oldest to free up space\n\n- `email`, the audit daemon will send a warning to the email account specified in `action_mail_acct` as well as sending the message to syslog\n\n- `exec`, /path-to-script will execute the script. You cannot pass parameters to the script. The script is also responsible for telling the auditd daemon to resume logging once its completed its action\n\n- `suspend`, the audit daemon will stop writing records to the disk\n\n- `single`, the audit daemon will put the computer system in single user mode\n\n- `halt`, the audit daemon will shut down the system\n\nThe `admin_space_left_action` parameter tells the system what action to take when the system has detected that it is low on disk space. Valid values are `ignore`, `syslog`, `rotate`, `email`, `exec`, `suspend`, `single`, and `halt`.\n\n- `ignore`, the audit daemon does nothing\n\n- `syslog`, the audit daemon will issue a warning to syslog\n\n- `rotate`, the audit daemon will rotate logs, losing the oldest to free up space\n\n- `email`, the audit daemon will send a warning to the email account specified in `action_mail_acct` as well as sending the message to syslog\n\n- `exec`, /path-to-script will execute the script. You cannot pass parameters to the script. The script is also responsible for telling the auditd daemon to resume logging once its completed its action\n\n- `suspend`, the audit daemon will stop writing records to the disk\n\n- `single`, the audit daemon will put the computer system in single user mode\n\n- `halt`, the audit daemon will shut down the system" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space_rationale", + "name": "rationale", + "prose": "In high security contexts, the risk of detecting unauthorized access or nonrepudiation exceeds the benefit of the system's availability." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space_obj", + "name": "assessment-objective", + "prose": "Ensure system warns when audit logs are low on space" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space_obj" + } + ], + "prose": "Run the following command and verify the `space_left_action` is set to `email`, `exec`, `single`, or `halt`:\n\n```\n# grep -P -- '^\\h*space_left_action\\h*=\\h*(email|exec|single|halt)\\b' /etc/audit/auditd.conf\n```\n\nVerify the output is `email`, `exec`, `single`, or `halt`\n\n*Example output*\n\n```\nspace_left_action = email\n```\n\nRun the following command and verify the `admin_space_left_action` is set to `single` **- OR -** `halt`:\n\n```\n# grep -P -- '^\\h*admin_space_left_action\\h*=\\h*(single|halt)\\b' /etc/audit/auditd.conf\n```\n\nVerify the output is `single` or `halt`\n\n*Example output:*\n\n```\nadmin_space_left_action = single\n```\n\n**Note:** A Mail Transfer Agent (MTA) must be installed and configured properly to set `space_left_action = email`" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Set the `space_left_action` parameter in `/etc/audit/auditd.conf` to `email`, `exec`, `single`, or `halt`:\n\n*Example:*\n\n```\nspace_left_action = email\n```\n\nSet the `admin_space_left_action` parameter in `/etc/audit/auditd.conf` to `single` or `halt`:\n\n*Example:*\n\n```\nadmin_space_left_action = single\n```\n\n**Note:** A Mail Transfer Agent (MTA) must be installed and configured properly to set `space_left_action = email`\n\nImpact:\n\nIf the `admin_space_left_action` is set to `single` the audit daemon will put the computer system in single user mode." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.2.3_Configure_auditd_Rules", + "title": "Configure auditd Rules", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected", + "title": "6.2.3.1 Ensure changes to system administration scope (sudoers) is collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected_smt", + "name": "statement", + "prose": "Monitor scope changes for system administrators. If the system has been properly configured to force system administrators to log in as themselves first and then use the `sudo` command to execute privileged commands, it is possible to monitor changes in scope. The file `/etc/sudoers`, or files in `/etc/sudoers.d`, will be written to when the file(s) or related attributes have changed. The audit records will be tagged with the identifier \"scope\"." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected_rationale", + "name": "rationale", + "prose": "Changes in the `/etc/sudoers` and `/etc/sudoers.d` files can indicate that an unauthorized change has been made to the scope of system administrator activity." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected_obj", + "name": "assessment-objective", + "prose": "Ensure changes to system administration scope (sudoers) is collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# awk '/^ *-w/ \\\n&&/\\/etc\\/sudoers/ \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n```\n\nVerify the output matches:\n\n```\n-w /etc/sudoers -p wa -k scope\n-w /etc/sudoers.d -p wa -k scope\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# auditctl -l | awk '/^ *-w/ \\\n&&/\\/etc\\/sudoers/ \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n```\n\nVerify the output matches:\n\n```\n-w /etc/sudoers -p wa -k scope\n-w /etc/sudoers.d -p wa -k scope\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor scope changes for system administrators.\n\n*Example:*\n\n```\n# printf \"\n-w /etc/sudoers -p wa -k scope\n-w /etc/sudoers.d -p wa -k scope\n\" >> /etc/audit/rules.d/50-scope.rules\n```\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged", + "title": "6.2.3.2 Ensure actions as another user are always logged", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged_smt", + "name": "statement", + "prose": "`sudo` provides users with temporary elevated privileges to perform operations, either as the superuser or another user." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged_rationale", + "name": "rationale", + "prose": "Creating an audit log of users with temporary elevated privileges and the operation(s) they performed is essential to reporting. Administrators will want to correlate the events written to the audit trail with the records written to `sudo`'s logfile to verify if unauthorized commands have been executed." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged_obj", + "name": "assessment-objective", + "prose": "Ensure actions as another user are always logged" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# awk '/^ *-a *always,exit/ \\\n&&/ -F *arch=b(32|64)/ \\\n&&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n&&(/ -C *euid!=uid/||/ -C *uid!=euid/) \\\n&&/ -S *execve/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -C euid!=uid -F auid!=unset -S execve -k user_emulation\n-a always,exit -F arch=b32 -C euid!=uid -F auid!=unset -S execve -k user_emulation\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# auditctl -l | awk '/^ *-a *always,exit/ \\\n&&/ -F *arch=b(32|64)/ \\\n&&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n&&(/ -C *euid!=uid/||/ -C *uid!=euid/) \\\n&&/ -S *execve/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -S execve -C uid!=euid -F auid!=-1 -F key=user_emulation\n-a always,exit -F arch=b32 -S execve -C uid!=euid -F auid!=-1 -F key=user_emulation\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor elevated privileges.\n\n*Example:*\n\n```\n# printf \"\n-a always,exit -F arch=b64 -C euid!=uid -F auid!=unset -S execve -k user_emulation\n-a always,exit -F arch=b32 -C euid!=uid -F auid!=unset -S execve -k user_emulation\n\" >> /etc/audit/rules.d/50-user_emulation.rules\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected", + "title": "6.2.3.3 Ensure events that modify the sudo log file are collected", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_rule_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "SUDOLOGFILE::-p wa" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected_smt", + "name": "statement", + "prose": "Monitor the `sudo` log file. If the system has been properly configured to disable the use of the `su` command and force all administrators to have to log in first and then use `sudo` to execute privileged commands, then all administrator commands will be logged to `/var/log/sudo.log` . Any time a command is executed, an audit event will be triggered as the `/var/log/sudo.log` file will be opened for write and the executed administration command will be written to the log." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected_rationale", + "name": "rationale", + "prose": "Changes in `/var/log/sudo.log` indicate that an administrator has executed a command or the log file itself has been tampered with. Administrators will want to correlate the events written to the audit trail with the records written to `/var/log/sudo.log` to verify if unauthorized commands have been executed." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure events that modify the sudo log file are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**Note:** This recommendation requires that the sudo logfile is configured. See guidance provided in the recommendation \"Ensure sudo log file exists\"\n\n**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n SUDO_LOG_FILE=$(grep -r logfile /etc/sudoers* | sed -e 's/.*logfile=//;s/,? .*//' -e 's/\"//g' -e 's|/|\\\\/|g')\n [ -n \"${SUDO_LOG_FILE}\" ] && awk \"/^ *-w/ \\\n &&/\"${SUDO_LOG_FILE}\"/ \\\n &&/ +-p *wa/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'SUDO_LOG_FILE' is unset.\\n\"\n}\n```\n\nVerify output of matches:\n\n```\n-w /var/log/sudo.log -p wa -k sudo_log_file\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n SUDO_LOG_FILE=$(grep -r logfile /etc/sudoers* | sed -e 's/.*logfile=//;s/,? .*//' -e 's/\"//g' -e 's|/|\\\\/|g')\n [ -n \"${SUDO_LOG_FILE}\" ] && auditctl -l | awk \"/^ *-w/ \\\n &&/\"${SUDO_LOG_FILE}\"/ \\\n &&/ +-p *wa/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'SUDO_LOG_FILE' is unset.\\n\"\n}\n```\n\nVerify output matches:\n\n```\n-w /var/log/sudo.log -p wa -k sudo_log_file\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Note:** This recommendation requires that the sudo logfile is configured. See guidance provided in the recommendation \"Ensure sudo log file exists\"\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor events that modify the sudo log file.\n\n*Example:*\n\n```\n# {\nSUDO_LOG_FILE=$(grep -r logfile /etc/sudoers* | sed -e 's/.*logfile=//;s/,? .*//' -e 's/\"//g')\n[ -n \"${SUDO_LOG_FILE}\" ] && printf \"\n-w ${SUDO_LOG_FILE} -p wa -k sudo_log_file\n\" >> /etc/audit/rules.d/50-sudo.rules || printf \"ERROR: Variable 'SUDO_LOG_FILE' is unset.\\n\"\n}\n```\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected", + "title": "6.2.3.4 Ensure events that modify date and time information are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected_smt", + "name": "statement", + "prose": "Capture events where the system date and/or time has been modified. The parameters in this section are set to determine if the;\n\n- `adjtimex` - tune kernel clock\n\n- `settimeofday` - set time using `timeval` and `timezone` structures\n\n- `stime` - using seconds since 1/1/1970\n\n- `clock_settime` - allows for the setting of several internal clocks and timers\n\nsystem calls have been executed. Further, ensure to write an audit record to the configured audit log file upon exit, tagging the records with a unique identifier such as \"time-change\"." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected_rationale", + "name": "rationale", + "prose": "Unexpected changes in system date and/or time could be a sign of malicious activity on the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure events that modify date and time information are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n awk '/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&/ -S/ \\\n &&(/adjtimex/ \\\n ||/settimeofday/ \\\n ||/clock_settime/ ) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n\n awk '/^ *-w/ \\\n &&/\\/etc\\/localtime/ \\\n &&/ +-p *wa/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n}\n```\n\nVerify output of matches:\n\n```\n-a always,exit -F arch=b64 -S adjtimex,settimeofday -k time-change\n-a always,exit -F arch=b32 -S adjtimex,settimeofday -k time-change\n-a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -k time-change\n-a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -k time-change\n-w /etc/localtime -p wa -k time-change\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n auditctl -l | awk '/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&/ -S/ \\\n &&(/adjtimex/ \\\n ||/settimeofday/ \\\n ||/clock_settime/ ) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n\n auditctl -l | awk '/^ *-w/ \\\n &&/\\/etc\\/localtime/ \\\n &&/ +-p *wa/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n}\n```\n\nVerify the output includes:\n\n```\n-a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=time-change\n-a always,exit -F arch=b32 -S settimeofday,adjtimex -F key=time-change\n-a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=time-change\n-a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F key=time-change\n-w /etc/localtime -p wa -k time-change\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor events that modify date and time information.\n\nExample:\n\n```\n# printf \"\n-a always,exit -F arch=b64 -S adjtimex,settimeofday -k time-change\n-a always,exit -F arch=b32 -S adjtimex,settimeofday -k time-change\n-a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -k time-change\n-a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -k time-change\n-w /etc/localtime -p wa -k time-change\n\" >> /etc/audit/rules.d/50-time-change.rules\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected", + "title": "6.2.3.5 Ensure events that modify the system's network environment are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected_smt", + "name": "statement", + "prose": "Record changes to network environment files or system calls. The below parameters monitors the following system calls, and write an audit event on system call exit:\n\n- `sethostname` - set the systems host name\n\n- `setdomainname` - set the systems domain name\n\nThe files being monitored are:\n\n- `/etc/issue` and `/etc/issue.net` - messages displayed pre-login\n\n- `/etc/hosts` - file containing host names and associated IP addresses\n\n- `/etc/networks` - symbolic names for networks\n\n- `/etc/network/` - directory containing network interface scripts and configurations files\n\n- `/etc/netplan/` - central location for YAML networking configurations files" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected_rationale", + "name": "rationale", + "prose": "Monitoring system events that change network environments, such as `sethostname` and `setdomainname`, helps identify unauthorized alterations to host and domain names, which could compromise security settings reliant on these names. Changes to `/etc/hosts` can signal unauthorized attempts to alter machine associations with IP addresses, potentially redirecting users and processes to unintended destinations. Surveillance of `/etc/issue` and `/etc/issue.net` is crucial to detect intruders inserting false information to deceive users. Monitoring `/etc/network/` reveals modifications to network interfaces or scripts that may jeopardize system availability or security. Additionally, tracking changes in the `/etc/netplan/` directory ensures swift detection of unauthorized adjustments to network configurations. All audit records should be appropriately tagged for relevance" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure events that modify the system's network environment are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following commands to check the on disk rules:\n\n```\n# awk '/^ *-a *always,exit/ \\\n&&/ -F *arch=b(32|64)/ \\\n&&/ -S/ \\\n&&(/sethostname/ \\\n ||/setdomainname/) \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n\n# awk '/^ *-w/ \\\n&&(/\\/etc\\/issue/ \\\n ||/\\/etc\\/issue.net/ \\\n ||/\\/etc\\/hosts/ \\\n ||/\\/etc\\/network/ \\\n ||/\\/etc\\/netplan/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -S sethostname,setdomainname -k system-locale\n-a always,exit -F arch=b32 -S sethostname,setdomainname -k system-locale\n-w /etc/issue -p wa -k system-locale\n-w /etc/issue.net -p wa -k system-locale\n-w /etc/hosts -p wa -k system-locale\n-w /etc/networks -p wa -k system-locale\n-w /etc/network -p wa -k system-locale\n-w /etc/netplan -p wa -k system-locale\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# auditctl -l | awk '/^ *-a *always,exit/ \\\n&&/ -F *arch=b(32|64)/ \\\n&&/ -S/ \\\n&&(/sethostname/ \\\n ||/setdomainname/) \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n\n# auditctl -l | awk '/^ *-w/ \\\n&&(/\\/etc\\/issue/ \\\n ||/\\/etc\\/issue.net/ \\\n ||/\\/etc\\/hosts/ \\\n ||/\\/etc\\/network/ \\\n ||/\\/etc\\/netplan/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n```\n\nVerify the output includes:\n\n```\n-a always,exit -F arch=b64 -S sethostname,setdomainname -F key=system-locale\n-a always,exit -F arch=b32 -S sethostname,setdomainname -F key=system-locale\n-w /etc/issue -p wa -k system-locale\n-w /etc/issue.net -p wa -k system-locale\n-w /etc/hosts -p wa -k system-locale\n-w /etc/networks -p wa -k system-locale\n-w /etc/network -p wa -k system-locale\n-w /etc/netplan -p wa -k system-locale\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor events that modify the system's network environment.\n\n*Example:*\n\n```\n# printf \"\n-a always,exit -F arch=b64 -S sethostname,setdomainname -k system-locale\n-a always,exit -F arch=b32 -S sethostname,setdomainname -k system-locale\n-w /etc/issue -p wa -k system-locale\n-w /etc/issue.net -p wa -k system-locale\n-w /etc/hosts -p wa -k system-locale\n-w /etc/networks -p wa -k system-locale\n-w /etc/network/ -p wa -k system-locale\n-w /etc/netplan/ -p wa -k system-locale\n\" >> /etc/audit/rules.d/50-system_locale.rules\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected", + "title": "6.2.3.6 Ensure use of privileged commands are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected_smt", + "name": "statement", + "prose": "Monitor privileged programs, those that have the `setuid` and/or `setgid` bit set on execution, to determine if unprivileged users are running these commands." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected_rationale", + "name": "rationale", + "prose": "Execution of privileged commands by non-privileged users could be an indication of someone trying to gain unauthorized access to the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure use of privileged commands are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected_obj" + }, + { + "rel": "script", + "href": "#0b888c8c-32bf-512b-8421-fa32e83e3eb0" + } + ], + "prose": "**On disk configuration**\n\nRun the following script to check on disk rules:\n\n```bash\n#!/usr/bin/env bash\n\n{\n for PARTITION in $(findmnt -n -l -k -it $(awk '/nodev/ { print $2 }' /proc/filesystems | paste -sd,) | grep -Pv \"noexec|nosuid\" | awk '{print $1}'); do\n for PRIVILEGED in $(find \"${PARTITION}\" -xdev -perm /6000 -type f); do\n grep -qr \"${PRIVILEGED}\" /etc/audit/rules.d && printf \"OK: '${PRIVILEGED}' found in auditing rules.\\n\" || printf \"Warning: '${PRIVILEGED}' not found in on disk configuration.\\n\"\n done\n done\n}\n```\n\nVerify that all output is `OK`.\n\n**Running configuration**\n\nRun the following script to check loaded rules:\n\n```bash\n#!/usr/bin/env bash\n\n{\n RUNNING=$(auditctl -l)\n [ -n \"${RUNNING}\" ] && for PARTITION in $(findmnt -n -l -k -it $(awk '/nodev/ { print $2 }' /proc/filesystems | paste -sd,) | grep -Pv \"noexec|nosuid\" | awk '{print $1}'); do\n for PRIVILEGED in $(find \"${PARTITION}\" -xdev -perm /6000 -type f); do\n printf -- \"${RUNNING}\" | grep -q \"${PRIVILEGED}\" && printf \"OK: '${PRIVILEGED}' found in auditing rules.\\n\" || printf \"Warning: '${PRIVILEGED}' not found in running configuration.\\n\"\n done\n done \\\n || printf \"ERROR: Variable 'RUNNING' is unset.\\n\"\n}\n```\n\nVerify that all output is `OK`.\n\n**Special mount points**\n\nIf there are any special mount points that are not visible by default from `findmnt` as per the above audit, said file systems would have to be manually audited." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor the use of privileged commands.\n\n*Example script:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n AUDIT_RULE_FILE=\"/etc/audit/rules.d/50-privileged.rules\"\n NEW_DATA=()\n for PARTITION in $(findmnt -n -l -k -it $(awk '/nodev/ { print $2 }' /proc/filesystems | paste -sd,) | grep -Pv \"noexec|nosuid\" | awk '{print $1}'); do\n readarray -t DATA < <(find \"${PARTITION}\" -xdev -perm /6000 -type f | awk -v UID_MIN=${UID_MIN} '{print \"-a always,exit -F path=\" $1 \" -F perm=x -F auid>=\"UID_MIN\" -F auid!=unset -k privileged\" }')\n for ENTRY in \"${DATA[@]}\"; do\n NEW_DATA+=(\"${ENTRY}\")\n done\n done\n readarray &> /dev/null -t OLD_DATA < \"${AUDIT_RULE_FILE}\"\n COMBINED_DATA=( \"${OLD_DATA[@]}\" \"${NEW_DATA[@]}\" )\n printf '%s\\n' \"${COMBINED_DATA[@]}\" | sort -u > \"${AUDIT_RULE_FILE}\"\n}\n```\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```\n\n**Special mount points**\n\nIf there are any special mount points that are not visible by default from just scanning `/`, change the `PARTITION` variable to the appropriate partition and re-run the remediation.\n\nImpact:\n\nBoth the audit and remediation section of this recommendation will traverse all mounted file systems that is not mounted with either `noexec` or `nosuid` mount options. If there are large file systems without these mount options, **such traversal will be significantly detrimental to the performance of the system.**\n\nBefore running either the audit or remediation section, inspect the output of the following command to determine exactly which file systems will be traversed:\n\n```\n# findmnt -n -l -k -it $(awk '/nodev/ { print $2 }' /proc/filesystems | paste -sd,) | grep -Pv \"noexec|nosuid\"\n```\n\nTo exclude a particular file system due to adverse performance impacts, update the audit and remediation sections by adding a sufficiently unique string to the `grep` statement. The above command can be used to test the modified exclusions." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected", + "title": "6.2.3.7 Ensure unsuccessful file access attempts are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected_smt", + "name": "statement", + "prose": "Monitor for unsuccessful attempts to access files. The following parameters are associated with system calls that control files:\n\n- creation - `creat`\n\n- opening - `open` , `openat`\n\n- truncation - `truncate` , `ftruncate`\n\nAn audit log record will only be written if all of the following criteria is met for the user when trying to access a file:\n\n- a non-privileged user (auid>=UID_MIN)\n\n- is not a Daemon event (auid=4294967295/unset/-1)\n\n- if the system call returned EACCES (permission denied) or EPERM (some other permanent error associated with the specific system call)" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected_rationale", + "name": "rationale", + "prose": "Failed attempts to open, create or truncate files could be an indication that an individual or process is trying to gain unauthorized access to the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure unsuccessful file access attempts are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&(/ -F *exit=-EACCES/||/ -F *exit=-EPERM/) \\\n &&/ -S/ \\\n &&/creat/ \\\n &&/open/ \\\n &&/truncate/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output includes:\n\n```\n-a always,exit -F arch=b64 -S creat,open,openat,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access\n-a always,exit -F arch=b64 -S creat,open,openat,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access\n-a always,exit -F arch=b32 -S creat,open,openat,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k access\n-a always,exit -F arch=b32 -S creat,open,openat,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k access\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&(/ -F *exit=-EACCES/||/ -F *exit=-EPERM/) \\\n &&/ -S/ \\\n &&/creat/ \\\n &&/open/ \\\n &&/truncate/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output includes:\n\n```\n-a always,exit -F arch=b64 -S open,truncate,ftruncate,creat,openat -F exit=-EACCES -F auid>=1000 -F auid!=-1 -F key=access\n-a always,exit -F arch=b64 -S open,truncate,ftruncate,creat,openat -F exit=-EPERM -F auid>=1000 -F auid!=-1 -F key=access\n-a always,exit -F arch=b32 -S open,truncate,ftruncate,creat,openat -F exit=-EACCES -F auid>=1000 -F auid!=-1 -F key=access\n-a always,exit -F arch=b32 -S open,truncate,ftruncate,creat,openat -F exit=-EPERM -F auid>=1000 -F auid!=-1 -F key=access\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor unsuccessful file access attempts.\n\n*Example:*\n\n```\n# {\nUID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n[ -n \"${UID_MIN}\" ] && printf \"\n-a always,exit -F arch=b64 -S creat,open,openat,truncate,ftruncate -F exit=-EACCES -F auid>=${UID_MIN} -F auid!=unset -k access\n-a always,exit -F arch=b64 -S creat,open,openat,truncate,ftruncate -F exit=-EPERM -F auid>=${UID_MIN} -F auid!=unset -k access\n-a always,exit -F arch=b32 -S creat,open,openat,truncate,ftruncate -F exit=-EACCES -F auid>=${UID_MIN} -F auid!=unset -k access\n-a always,exit -F arch=b32 -S creat,open,openat,truncate,ftruncate -F exit=-EPERM -F auid>=${UID_MIN} -F auid!=unset -k access\n\" >> /etc/audit/rules.d/50-access.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected", + "title": "6.2.3.8 Ensure events that modify user/group information are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected_smt", + "name": "statement", + "prose": "Record events affecting the modification of user or group information, including that of passwords and old passwords if in use.\n\n- `/etc/group` - system groups\n\n- `/etc/passwd` - system users\n\n- `/etc/gshadow` - encrypted password for each group\n\n- `/etc/shadow` - system user passwords\n\n- `/etc/security/opasswd` - storage of old passwords if the relevant PAM module is in use\n\n- `/etc/nsswitch.conf` - file configures how the system uses various databases and name resolution mechanisms\n\n- `/etc/pam.conf` - file determines the authentication services to be used, and the order in which the services are used.\n\n- `/etc/pam.d` - directory contains the PAM configuration files for each PAM-aware application.\n\nThe parameters in this section will watch the files to see if they have been opened for write or have had attribute changes (e.g. permissions) and tag them with the identifier \"identity\" in the audit log file." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected_rationale", + "name": "rationale", + "prose": "Unexpected changes to these files could be an indication that the system has been compromised and that an unauthorized user is attempting to hide their activities or compromise additional accounts." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure events that modify user/group information are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# awk '/^ *-w/ \\\n&&(/\\/etc\\/group/ \\\n ||/\\/etc\\/passwd/ \\\n ||/\\/etc\\/gshadow/ \\\n ||/\\/etc\\/shadow/ \\\n ||/\\/etc\\/security\\/opasswd/ \\\n ||/\\/etc\\/nsswitch.conf/ \\\n ||/\\/etc\\/pam.conf/ \\\n ||/\\/etc\\/pam.d/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n```\n\nVerify the output matches:\n\n```\n-w /etc/group -p wa -k identity\n-w /etc/passwd -p wa -k identity\n-w /etc/gshadow -p wa -k identity\n-w /etc/shadow -p wa -k identity\n-w /etc/security/opasswd -p wa -k identity\n-w /etc/nsswitch.conf -p wa -k identity\n-w /etc/pam.conf -p wa -k identity\n-w /etc/pam.d -p wa -k identity\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# auditctl -l | awk '/^ *-w/ \\\n&&(/\\/etc\\/group/ \\\n ||/\\/etc\\/passwd/ \\\n ||/\\/etc\\/gshadow/ \\\n ||/\\/etc\\/shadow/ \\\n ||/\\/etc\\/security\\/opasswd/ \\\n ||/\\/etc\\/nsswitch.conf/ \\\n ||/\\/etc\\/pam.conf/ \\\n ||/\\/etc\\/pam.d/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n```\n\nVerify the output matches:\n\n```\n-w /etc/group -p wa -k identity\n-w /etc/passwd -p wa -k identity\n-w /etc/gshadow -p wa -k identity\n-w /etc/shadow -p wa -k identity\n-w /etc/security/opasswd -p wa -k identity\n-w /etc/nsswitch.conf -p wa -k identity\n-w /etc/pam.conf -p wa -k identity\n-w /etc/pam.d -p wa -k identity\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor events that modify user/group information.\n\n*Example:*\n\n```\n# printf \"\n-w /etc/group -p wa -k identity\n-w /etc/passwd -p wa -k identity\n-w /etc/gshadow -p wa -k identity\n-w /etc/shadow -p wa -k identity\n-w /etc/security/opasswd -p wa -k identity\n-w /etc/nsswitch.conf -p wa -k identity\n-w /etc/pam.conf -p wa -k identity\n-w /etc/pam.d -p wa -k identity\n\" >> /etc/audit/rules.d/50-identity.rules\n```\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected", + "title": "6.2.3.9 Ensure discretionary access control permission modification events are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected_smt", + "name": "statement", + "prose": "Monitor changes to file permissions, attributes, ownership and group. The parameters in this section track changes for system calls that affect file permissions and attributes. The following commands and system calls effect the permissions, ownership and various attributes of files.\n\n- `chmod`\n\n- `fchmod`\n\n- `fchmodat`\n\n- `chown`\n\n- `fchown`\n\n- `fchownat`\n\n- `lchown`\n\n- `setxattr`\n\n- `lsetxattr`\n\n- `fsetxattr`\n\n- `removexattr`\n\n- `lremovexattr`\n\n- `fremovexattr`\n\nIn all cases, an audit record will only be written for non-system user ids and will ignore Daemon events. All audit records will be tagged with the identifier \"perm_mod.\"" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected_rationale", + "name": "rationale", + "prose": "Monitoring for changes in file attributes could alert a system administrator to activity that could indicate intruder activity or policy violation." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure discretionary access control permission modification events are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**Note:** Output showing all audited syscalls, e.g. (-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat,chmod,fchmod,fchmodat,setxattr,lsetxattr,fsetxattr,removexattr,lremovexattr,fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod) is also acceptable. These have been separated by function on the displayed output for clarity.\n\n**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -S/ \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&(/chmod/||/fchmod/||/fchmodat/ \\\n ||/chown/||/fchown/||/fchownat/||/lchown/ \\\n ||/setxattr/||/lsetxattr/||/fsetxattr/ \\\n ||/removexattr/||/lremovexattr/||/fremovexattr/) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b64 -S chown,fchown,lchown,fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b32 -S lchown,fchown,chown,fchownat -F auid>=1000 -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b64 -S setxattr,lsetxattr,fsetxattr,removexattr,lremovexattr,fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b32 -S setxattr,lsetxattr,fsetxattr,removexattr,lremovexattr,fremovexattr -F auid>=1000 -F auid!=unset -F key=perm_mod\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -S/ \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&(/chmod/||/fchmod/||/fchmodat/ \\\n ||/chown/||/fchown/||/fchownat/||/lchown/ \\\n ||/setxattr/||/lsetxattr/||/fsetxattr/ \\\n ||/removexattr/||/lremovexattr/||/fremovexattr/) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -F key=perm_mod\n-a always,exit -F arch=b64 -S chown,fchown,lchown,fchownat -F auid>=1000 -F auid!=-1 -F key=perm_mod\n-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -F key=perm_mod\n-a always,exit -F arch=b32 -S lchown,fchown,chown,fchownat -F auid>=1000 -F auid!=-1 -F key=perm_mod\n-a always,exit -F arch=b64 -S setxattr,lsetxattr,fsetxattr,removexattr,lremovexattr,fremovexattr -F auid>=1000 -F auid!=-1 -F key=perm_mod\n-a always,exit -F arch=b32 -S setxattr,lsetxattr,fsetxattr,removexattr,lremovexattr,fremovexattr -F auid>=1000 -F auid!=-1 -F key=perm_mod\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor discretionary access control permission modification events.\n\n*Example:*\n\n```\n# {\nUID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n[ -n \"${UID_MIN}\" ] && printf \"\n-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=${UID_MIN} -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b64 -S chown,fchown,lchown,fchownat -F auid>=${UID_MIN} -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=${UID_MIN} -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b32 -S lchown,fchown,chown,fchownat -F auid>=${UID_MIN} -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b64 -S setxattr,lsetxattr,fsetxattr,removexattr,lremovexattr,fremovexattr -F auid>=${UID_MIN} -F auid!=unset -F key=perm_mod\n-a always,exit -F arch=b32 -S setxattr,lsetxattr,fsetxattr,removexattr,lremovexattr,fremovexattr -F auid>=${UID_MIN} -F auid!=unset -F key=perm_mod\n\" >> /etc/audit/rules.d/50-perm_mod.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected", + "title": "6.2.3.10 Ensure successful file system mounts are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected_smt", + "name": "statement", + "prose": "Monitor the use of the `mount` system call. The `mount` (and `umount` ) system call controls the mounting and unmounting of file systems. The parameters below configure the system to create an audit record when the mount system call is used by a non-privileged user" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected_rationale", + "name": "rationale", + "prose": "It is highly unusual for a non privileged user to `mount` file systems to the system. While tracking `mount` commands gives the system administrator evidence that external media may have been mounted (based on a review of the source of the mount and confirming it's an external media type), it does not conclusively indicate that data was exported to the media. System administrators who wish to determine if data were exported, would also have to track successful `open`, `creat` and `truncate` system calls requiring write access to a file under the mount point of the external media file system. This could give a fair indication that a write occurred. The only way to truly prove it, would be to track successful writes to the external media. Tracking write system calls could quickly fill up the audit log and is not recommended. Recommendations on configuration options to track data export to media is beyond the scope of this document." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure successful file system mounts are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -S/ \\\n &&/mount/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=unset -k mounts\n-a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -S/ \\\n &&/mount/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=-1 -F key=mounts\n-a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=-1 -F key=mounts\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor successful file system mounts.\n\n*Example:*\n\n```\n# {\nUID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n[ -n \"${UID_MIN}\" ] && printf \"\n-a always,exit -F arch=b32 -S mount -F auid>=$UID_MIN -F auid!=unset -k mounts\n-a always,exit -F arch=b64 -S mount -F auid>=$UID_MIN -F auid!=unset -k mounts\n\" >> /etc/audit/rules.d/50-mounts.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected", + "title": "6.2.3.11 Ensure session initiation information is collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected_smt", + "name": "statement", + "prose": "Monitor session initiation events. The parameters in this section track changes to the files associated with session events.\n\n- `/var/run/utmp` - tracks all currently logged in users.\n\n- `/var/log/wtmp` - file tracks logins, logouts, shutdown, and reboot events.\n\n- `/var/log/btmp` - keeps track of failed login attempts and can be read by entering the command `/usr/bin/last -f /var/log/btmp`.\n\nAll audit records will be tagged with the identifier \"session.\"" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected_rationale", + "name": "rationale", + "prose": "Monitoring these files for changes could alert a system administrator to logins occurring at unusual hours, which could indicate intruder activity (i.e. a user logging in at a time when they do not normally log in)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected_obj", + "name": "assessment-objective", + "prose": "Ensure session initiation information is collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# awk '/^ *-w/ \\\n&&(/\\/var\\/run\\/utmp/ \\\n ||/\\/var\\/log\\/wtmp/ \\\n ||/\\/var\\/log\\/btmp/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n```\n\nVerify the output matches:\n\n```\n-w /var/run/utmp -p wa -k session\n-w /var/log/wtmp -p wa -k session\n-w /var/log/btmp -p wa -k session\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# auditctl -l | awk '/^ *-w/ \\\n&&(/\\/var\\/run\\/utmp/ \\\n ||/\\/var\\/log\\/wtmp/ \\\n ||/\\/var\\/log\\/btmp/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n```\n\nVerify the output matches:\n\n```\n-w /var/run/utmp -p wa -k session\n-w /var/log/wtmp -p wa -k session\n-w /var/log/btmp -p wa -k session\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor session initiation information.\n\n*Example:*\n\n```\n# printf \"\n-w /var/run/utmp -p wa -k session\n-w /var/log/wtmp -p wa -k session\n-w /var/log/btmp -p wa -k session\n\" >> /etc/audit/rules.d/50-session.rules\n```\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected", + "title": "6.2.3.12 Ensure login and logout events are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected_smt", + "name": "statement", + "prose": "Monitor login and logout events. The parameters below track changes to files associated with login/logout events.\n\n- `/var/log/lastlog` - maintain records of the last time a user successfully logged in.\n\n- `/var/run/faillock` - directory maintains records of login failures via the `pam_faillock` module." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected_rationale", + "name": "rationale", + "prose": "Monitoring login/logout events could provide a system administrator with information associated with brute force attacks against user logins." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure login and logout events are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# awk '/^ *-w/ \\\n&&(/\\/var\\/log\\/lastlog/ \\\n ||/\\/var\\/run\\/faillock/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n```\n\nVerify the output matches:\n\n```\n-w /var/log/lastlog -p wa -k logins\n-w /var/run/faillock -p wa -k logins\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# auditctl -l | awk '/^ *-w/ \\\n&&(/\\/var\\/log\\/lastlog/ \\\n ||/\\/var\\/run\\/faillock/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n```\n\nVerify the output matches:\n\n```\n-w /var/log/lastlog -p wa -k logins\n-w /var/run/faillock -p wa -k logins\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor login and logout events.\n\n*Example:*\n\n```\n# printf \"\n-w /var/log/lastlog -p wa -k logins\n-w /var/run/faillock -p wa -k logins\n\" >> /etc/audit/rules.d/50-login.rules\n```\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected", + "title": "6.2.3.13 Ensure file deletion events by users are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected_smt", + "name": "statement", + "prose": "Monitor the use of system calls associated with the deletion or renaming of files and file attributes. This configuration statement sets up monitoring for:\n\n- `unlink` - remove a file\n\n- `unlinkat` - remove a file attribute\n\n- `rename` - rename a file\n\n- `renameat` rename a file attribute\nsystem calls and tags them with the identifier \"delete\"." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected_rationale", + "name": "rationale", + "prose": "Monitoring these calls from non-privileged users could provide a system administrator with evidence that inappropriate removal of files and file attributes associated with protected files is occurring. While this audit option will look at all events, system administrators will want to look for specific privileged files that are being deleted or altered." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure file deletion events by users are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -S/ \\\n &&(/unlink/||/rename/||/unlinkat/||/renameat/) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat -F auid>=1000 -F auid!=unset -k delete\n-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat -F auid>=1000 -F auid!=unset -k delete\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -S/ \\\n &&(/unlink/||/rename/||/unlinkat/||/renameat/) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -S rename,unlink,unlinkat,renameat -F auid>=1000 -F auid!=-1 -F key=delete\n-a always,exit -F arch=b32 -S unlink,rename,unlinkat,renameat -F auid>=1000 -F auid!=-1 -F key=delete\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor file deletion events by users.\n\n*Example:*\n\n```\n# {\nUID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n[ -n \"${UID_MIN}\" ] && printf \"\n-a always,exit -F arch=b64 -S rename,unlink,unlinkat,renameat -F auid>=${UID_MIN} -F auid!=unset -F key=delete\n-a always,exit -F arch=b32 -S rename,unlink,unlinkat,renameat -F auid>=${UID_MIN} -F auid!=unset -F key=delete\n\" >> /etc/audit/rules.d/50-delete.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected", + "title": "6.2.3.14 Ensure events that modify the system's Mandatory Access Controls are collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected_smt", + "name": "statement", + "prose": "Monitor AppArmor, an implementation of mandatory access controls. The parameters below monitor any write access (potential additional, deletion or modification of files in the directory) or attribute changes to the `/etc/apparmor/` and `/etc/apparmor.d/` directories.\n\n**Note:** If a different Mandatory Access Control method is used, changes to the corresponding directories should be audited." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected_rationale", + "name": "rationale", + "prose": "Changes to files in the `/etc/apparmor/` and `/etc/apparmor.d/` directories could indicate that an unauthorized user is attempting to modify access controls and change security contexts, leading to a compromise of the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure events that modify the system's Mandatory Access Controls are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# awk '/^ *-w/ \\\n&&(/\\/etc\\/apparmor/ \\\n ||/\\/etc\\/apparmor.d/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n```\n\nVerify the output matches:\n\n```\n-w /etc/apparmor/ -p wa -k MAC-policy\n-w /etc/apparmor.d/ -p wa -k MAC-policy\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# auditctl -l | awk '/^ *-w/ \\\n&&(/\\/etc\\/apparmor/ \\\n ||/\\/etc\\/apparmor.d/) \\\n&&/ +-p *wa/ \\\n&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n```\n\nVerify the output matches:\n\n```\n-w /etc/apparmor/ -p wa -k MAC-policy\n-w /etc/apparmor.d/ -p wa -k MAC-policy\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor events that modify the system's Mandatory Access Controls.\n\n*Example:*\n\n```\n# printf \"\n-w /etc/apparmor/ -p wa -k MAC-policy\n-w /etc/apparmor.d/ -p wa -k MAC-policy\n\" >> /etc/audit/rules.d/50-MAC-policy.rules\n```\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected", + "title": "6.2.3.15 Ensure successful and unsuccessful attempts to use the chcon command are collected", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_rule_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "-F path=/usr/bin/chcon::-a (always,exit|exit,always):-F perm=x:-F auid>=1000:-F auid!=(unset|-1|4294967295)" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected_smt", + "name": "statement", + "prose": "The operating system must generate audit records for successful/unsuccessful uses of the `chcon` command." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected_rationale", + "name": "rationale", + "prose": "The `chcon` command is used to change file security context. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure successful and unsuccessful attempts to use the chcon command are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/chcon/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/chcon/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -S all -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=-1 -F key=perm_chng\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor successful and unsuccessful attempts to use the `chcon` command.\n\n*Example:*\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && printf \"\n-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=${UID_MIN} -F auid!=unset -k perm_chng\n\" >> /etc/audit/rules.d/50-perm_chng.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected", + "title": "6.2.3.16 Ensure successful and unsuccessful attempts to use the setfacl command are collected", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_rule_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "-F path=/usr/bin/setfacl::-a (always,exit|exit,always):-F perm=x:-F auid>=1000:-F auid!=(unset|-1|4294967295)" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected_smt", + "name": "statement", + "prose": "The operating system must generate audit records for successful/unsuccessful uses of the `setfacl` command" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected_rationale", + "name": "rationale", + "prose": "This utility sets Access Control Lists (ACLs) of files and directories. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure successful and unsuccessful attempts to use the setfacl command are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/setfacl/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/setfacl/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -S all -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=-1 -F key=perm_chng\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor successful and unsuccessful attempts to use the `setfacl` command.\n\n*Example:*\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && printf \"\n-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=${UID_MIN} -F auid!=unset -k perm_chng\n\" >> /etc/audit/rules.d/50-perm_chng.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected", + "title": "6.2.3.17 Ensure successful and unsuccessful attempts to use the chacl command are collected", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_rule_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "-F path=/usr/bin/chacl::-a (always,exit|exit,always):-F perm=x:-F auid>=1000:-F auid!=(unset|-1|4294967295)" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected_smt", + "name": "statement", + "prose": "The operating system must generate audit records for successful/unsuccessful uses of the `chacl` command.\n\n`chacl` is an IRIX-compatibility command, and is maintained for those users who are familiar with its use from either XFS or IRIX." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected_rationale", + "name": "rationale", + "prose": "`chacl` changes the ACL(s) for a file or directory. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure successful and unsuccessful attempts to use the chacl command are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/chacl/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/chacl/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -S all -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=-1 -F key=perm_chng\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor successful and unsuccessful attempts to use the `chacl` command.\n\n*Example:*\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && printf \"\n-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=${UID_MIN} -F auid!=unset -k perm_chng\n\" >> /etc/audit/rules.d/50-perm_chng.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected", + "title": "6.2.3.18 Ensure successful and unsuccessful attempts to use the usermod command are collected", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_rule_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "-F path=/usr/sbin/usermod::-a (always,exit|exit,always):-F perm=x:-F auid>=1000:-F auid!=(unset|-1|4294967295)" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected_smt", + "name": "statement", + "prose": "The operating system must generate audit records for successful/unsuccessful uses of the `usermod` command." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected_rationale", + "name": "rationale", + "prose": "The `usermod` command modifies the system account files to reflect the changes that are specified on the command line. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected_obj", + "name": "assessment-objective", + "prose": "Ensure successful and unsuccessful attempts to use the usermod command are collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following command to check the on disk rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/sbin\\/usermod/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k usermod\n```\n\n**Running configuration**\n\nRun the following command to check loaded rules:\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/sbin\\/usermod/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -S all -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=-1 -F key=usermod\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor successful and unsuccessful attempts to use the `usermod` command.\n\n*Example:*\n\n```\n# {\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && printf \"\n-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=${UID_MIN} -F auid!=unset -k usermod\n\" >> /etc/audit/rules.d/50-usermod.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected", + "title": "6.2.3.19 Ensure kernel module loading unloading and modification is collected", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected_smt", + "name": "statement", + "prose": "Monitor the loading and unloading of kernel modules. All the loading / listing / dependency checking of modules is done by `kmod` via symbolic links.\n\nThe following system calls control loading and unloading of modules:\n\n- `init_module` - load a module\n\n- `finit_module` - load a module (used when the overhead of using cryptographically signed modules to determine the authenticity of a module can be avoided)\n\n- `delete_module` - delete a module\n\n- `create_module` - create a loadable module entry\n\n- `query_module` - query the kernel for various bits pertaining to modules\n\nAny execution of the loading and unloading module programs and system calls will trigger an audit record with an identifier of `modules`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected_rationale", + "name": "rationale", + "prose": "Monitoring the use of all the various ways to manipulate kernel modules could provide system administrators with evidence that an unauthorized change was made to a kernel module, possibly compromising the security of the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected_obj", + "name": "assessment-objective", + "prose": "Ensure kernel module loading unloading and modification is collected" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "**On disk configuration**\n\nRun the following script to check the on disk rules:\n\n```bash\n#!/usr/bin/env bash\n\n{\n awk '/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F auid!=unset/||/ -F auid!=-1/||/ -F auid!=4294967295/) \\\n &&/ -S/ \\\n &&(/init_module/ \\\n ||/finit_module/ \\\n ||/delete_module/ \\\n ||/create_module/ \\\n ||/query_module/) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules\n\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/kmod/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" /etc/audit/rules.d/*.rules \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output matches:\n\n```\n-a always,exit -F arch=b64 -S init_module,finit_module,delete_module,create_module,query_module -F auid>=1000 -F auid!=unset -k kernel_modules\n-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=unset -k kernel_modules\n```\n\n**Running configuration**\n\nRun the following script to check loaded rules:\n\n```bash\n#!/usr/bin/env bash\n\n{\n auditctl -l | awk '/^ *-a *always,exit/ \\\n &&/ -F *arch=b(32|64)/ \\\n &&(/ -F auid!=unset/||/ -F auid!=-1/||/ -F auid!=4294967295/) \\\n &&/ -S/ \\\n &&(/init_module/ \\\n ||/finit_module/ \\\n ||/delete_module/ \\\n ||/create_module/ \\\n ||/query_module/) \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'\n\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && auditctl -l | awk \"/^ *-a *always,exit/ \\\n &&(/ -F *auid!=unset/||/ -F *auid!=-1/||/ -F *auid!=4294967295/) \\\n &&/ -F *auid>=${UID_MIN}/ \\\n &&/ -F *perm=x/ \\\n &&/ -F *path=\\/usr\\/bin\\/kmod/ \\\n &&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)\" \\\n || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\nVerify the output includes:\n\n```\n-a always,exit -F arch=b64 -S create_module,init_module,delete_module,query_module,finit_module -F auid>=1000 -F auid!=-1 -F key=kernel_modules\n-a always,exit -S all -F path=/usr/bin/kmod -F perm=x -F auid>=1000 -F auid!=-1 -F key=kernel_modules\n```\n\n**Symlink audit**\n\nRun the following script to audit if the symlinks `kmod` accepts are indeed pointing at it:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_files=(\"/usr/sbin/lsmod\" \"/usr/sbin/rmmod\" \"/usr/sbin/insmod\" \"/usr/sbin/modinfo\" \"/usr/sbin/modprobe\" \"/usr/sbin/depmod\")\n for l_file in \"${a_files[@]}\"; do\n if [ \"$(readlink -f \"$l_file\")\" = \"$(readlink -f /bin/kmod)\" ]; then\n printf \"OK: \\\"$l_file\\\"\\n\"\n else\n printf \"Issue with symlink for file: \\\"$l_file\\\"\\n\"\n fi\n done\n}\n```\n\nVerify the output states `OK`. If there is a symlink pointing to a different location it should be investigated" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "**Create audit rules**\n\nEdit or create a file in the `/etc/audit/rules.d/` directory, ending in `.rules` extension, with the relevant rules to monitor kernel module modification.\n\n*Example:*\n\n```bash\n#!/usr/bin/env bash\n\n{\n UID_MIN=$(awk '/^\\s*UID_MIN/{print $2}' /etc/login.defs)\n [ -n \"${UID_MIN}\" ] && printf \"\n -a always,exit -F arch=b64 -S init_module,finit_module,delete_module,create_module,query_module -F auid>=${UID_MIN} -F auid!=unset -k kernel_modules\n -a always,exit -F path=/usr/bin/kmod -F perm=x -F auid>=${UID_MIN} -F auid!=unset -k kernel_modules\n \" >> /etc/audit/rules.d/50-kernel_modules.rules || printf \"ERROR: Variable 'UID_MIN' is unset.\\n\"\n}\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable", + "title": "6.2.3.20 Ensure the audit configuration is immutable", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_rule_chk_v2.sh as XCCDF_VALUE_REGEX", + "values": [ + "-e 2::" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable_smt", + "name": "statement", + "prose": "Set system audit so that audit rules cannot be modified with `auditctl` . Setting the flag \"-e 2\" forces audit to be put in immutable mode. Audit changes can only be made on system reboot.\n\n**Note:** This setting will require the system to be rebooted to update the active `auditd` configuration settings." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable_rationale", + "name": "rationale", + "prose": "In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. Users would most likely notice a system reboot and that could alert administrators of an attempt to make unauthorized audit changes." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable_obj", + "name": "assessment-objective", + "prose": "Ensure the audit configuration is immutable" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable_obj" + }, + { + "rel": "script", + "href": "#c20ab9e6-5e79-56ec-af8d-020f2984fab5" + } + ], + "prose": "Run the following command and verify output matches:\n\n```\n# grep -Ph -- '^\\h*-e\\h+2\\b' /etc/audit/rules.d/*.rules | tail -1\n\n-e 2\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit or create the file `/etc/audit/rules.d/99-finalize.rules` and add the line `-e 2` at the end of the file:\n\n*Example:*\n\n```\n# printf '\\n%s' \"-e 2\" >> /etc/audit/rules.d/99-finalize.rules\n```\n\n**Load audit rules**\n\nMerge and load the rules into active configuration:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\n# if [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then printf \"Reboot required to load rules\\n\"; fi\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same", + "title": "6.2.3.21 Ensure the running and on disk configuration is the same", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same_smt", + "name": "statement", + "prose": "The Audit system have both on disk and running configuration. It is possible for these configuration settings to differ.\n\n**Note:** Due to the limitations of `augenrules` and `auditctl`, it is not absolutely guaranteed that loading the rule sets via `augenrules --load` will result in all rules being loaded or even that the user will be informed if there was a problem loading the rules." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same_rationale", + "name": "rationale", + "prose": "Configuration differences between what is currently running and what is on disk could cause unexpected problems or may give a false impression of compliance requirements." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same_obj", + "name": "assessment-objective", + "prose": "Ensure the running and on disk configuration is the same" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same_obj" + } + ], + "prose": "**Merged rule sets**\n\nEnsure that all rules in `/etc/audit/rules.d` have been merged into `/etc/audit/audit.rules`:\n\n```\n# augenrules --check\n\n/usr/sbin/augenrules: No change\n```\n\nShould there be any drift, run `augenrules --load` to merge and load all rules." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "If the rules are not aligned across all three () areas, run the following command to merge and load all rules:\n\n```\n# augenrules --load\n```\n\nCheck if reboot is required.\n\n```\nif [[ $(auditctl -s | grep \"enabled\") =~ \"2\" ]]; then echo \"Reboot required to load rules\"; fi\n```" + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.2.4_Configure_auditd_File_Access", + "title": "Configure auditd File Access", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured", + "title": "6.2.4.1 Ensure audit log files mode is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_logfile_mode_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "0137" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured_smt", + "name": "statement", + "prose": "Audit log files contain information about the system and system activity." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured_rationale", + "name": "rationale", + "prose": "Access to audit records can reveal system and configuration data to attackers, potentially compromising its confidentiality." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit log files mode is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured_obj" + }, + { + "rel": "script", + "href": "#3d302179-a881-5040-8157-4bbffde66318" + } + ], + "prose": "Run the following script to verify audit log files are mode `0640` or more restrictive:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_perm_mask=\"0137\"\n if [ -e \"/etc/audit/auditd.conf\" ]; then\n l_audit_log_directory=\"$(dirname \"$(awk -F= '/^\\s*log_file\\s*/{print $2}' /etc/audit/auditd.conf | xargs)\")\"\n if [ -d \"$l_audit_log_directory\" ]; then\n l_maxperm=\"$(printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n a_files=()\n while IFS= read -r -d $'\\0' l_file; do\n [ -e \"$l_file\" ] && a_files+=(\"$l_file\")\n done < <(find \"$l_audit_log_directory\" -maxdepth 1 -type f -perm /\"$l_perm_mask\" -print0)\n\t\t if (( \"${#a_files[@]}\" > 0 )); then\n for l_file in \"${a_files[@]}\"; do\n l_file_mode=\"$(stat -Lc '%#a' \"$l_file\")\"\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - File: \\\"$l_file\\\" is mode: \\\"$l_file_mode\\\"\\n (should be mode: \\\"$l_maxperm\\\" or more restrictive)\\n\"\n done\n else\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - All files in \\\"$l_audit_log_directory\\\" are mode: \\\"$l_maxperm\\\" or more restrictive\"\n fi\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Log file directory not set in \\\"/etc/audit/auditd.conf\\\" please set log file directory\"\n fi\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - File: \\\"/etc/audit/auditd.conf\\\" not found.\\n - ** Verify auditd is installed **\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to remove more permissive mode than `0640` from audit log files:\n\n```\n# [ -f /etc/audit/auditd.conf ] && find \"$(dirname $(awk -F \"=\" '/^\\s*log_file/ {print $2}' /etc/audit/auditd.conf | xargs))\" -type f -perm /0137 -exec chmod u-x,g-wx,o-rwx {} +\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured", + "title": "6.2.4.2 Ensure audit log files owner is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_log_files_owner_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "root" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured_smt", + "name": "statement", + "prose": "Audit log files contain information about the system and system activity." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured_rationale", + "name": "rationale", + "prose": "Access to audit records can reveal system and configuration data to attackers, potentially compromising its confidentiality." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit log files owner is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured_obj" + }, + { + "rel": "script", + "href": "#7b50ef7c-abce-5ed1-9c53-a35eb45d7553" + } + ], + "prose": "Run the following script to verify audit log files are owned by the `root` user:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n if [ -e \"/etc/audit/auditd.conf\" ]; then\n l_audit_log_directory=\"$(dirname \"$(awk -F= '/^\\s*log_file\\s*/{print $2}' /etc/audit/auditd.conf | xargs)\")\"\n if [ -d \"$l_audit_log_directory\" ]; then\n while IFS= read -r -d $'\\0' l_file; do\n l_output2=\"$l_output2\\n - File: \\\"$l_file\\\" is owned by user: \\\"$(stat -Lc '%U' \"$l_file\")\\\"\\n (should be owned by user: \\\"root\\\")\\n\"\n done < <(find \"$l_audit_log_directory\" -maxdepth 1 -type f ! -user root -print0)\n else\n l_output2=\"$l_output2\\n - Log file directory not set in \\\"/etc/audit/auditd.conf\\\" please set log file directory\"\n fi\n else\n l_output2=\"$l_output2\\n - File: \\\"/etc/audit/auditd.conf\\\" not found.\\n - ** Verify auditd is installed **\"\n fi\n if [ -z \"$l_output2\" ]; then\n l_output=\"$l_output\\n - All files in \\\"$l_audit_log_directory\\\" are owned by user: \\\"root\\\"\\n\"\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :$l_output\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :$l_output2\\n\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to configure the audit log files to be owned by the `root` user:\n\n```\n# [ -f /etc/audit/auditd.conf ] && find \"$(dirname $(awk -F \"=\" '/^\\s*log_file/ {print $2}' /etc/audit/auditd.conf | xargs))\" -type f ! -user root -exec chown root {} +\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured", + "title": "6.2.4.3 Ensure audit log files group owner is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_log_files_group_owner_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "(root|adm)" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured_smt", + "name": "statement", + "prose": "Audit log files contain information about the system and system activity." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured_rationale", + "name": "rationale", + "prose": "Access to audit records can reveal system and configuration data to attackers, potentially compromising its confidentiality." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit log files group owner is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured_obj" + }, + { + "rel": "script", + "href": "#41d0c09d-38c6-53a2-bdf1-2e9034272129" + } + ], + "prose": "Run the following command to verify `log_group` parameter is set to either `adm` or `root` in `/etc/audit/auditd.conf`:\n\n```\n# grep -Piws -- '^\\h*log_group\\h*=\\h*\\H+\\b' /etc/audit/auditd.conf | grep -Pvi -- '(adm)'\n```\n\nNothing should be returned\n\nUsing the path of the directory containing the audit logs, verify audit log files are owned by the \"root\" or \"adm\" group by running the following script:\n\n```bash\n#!/usr/bin/env bash\n\n{\n if [ -e /etc/audit/auditd.conf ]; then\n l_fpath=\"$(dirname \"$(awk -F \"=\" '/^\\s*log_file/ {print $2}' /etc/audit/auditd.conf | xargs)\")\"\n find -L \"$l_fpath\" -not -path \"$l_fpath\"/lost+found -type f \\( ! -group root -a ! -group adm \\) -exec ls -l {} +\n fi\n}\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to configure the audit log files to be group owned by `adm`:\n\n```\n# find $(dirname $(awk -F\"=\" '/^\\s*log_file/ {print $2}' /etc/audit/auditd.conf | xargs)) -type f \\( ! -group adm -a ! -group root \\) -exec chgrp adm {} +\n```\n\nRun the following command to set the `log_group` parameter in the audit configuration file to `log_group = adm`:\n\n```\n# sed -ri 's/^\\s*#?\\s*log_group\\s*=\\s*\\S+(\\s*#.*)?.*$/log_group = adm\\1/' /etc/audit/auditd.conf\n```\n\nRun the following command to restart the audit daemon to reload the configuration file:\n\n```\n# systemctl restart auditd\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured", + "title": "6.2.4.4 Ensure the audit log file directory mode is configured", + "params": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured_xccdf-value-regex", + "class": "XCCDF_VALUE_REGEX", + "label": "Value exported to nix_auditd_logfile_directory_mode_chk.sh as XCCDF_VALUE_REGEX", + "values": [ + "0027" + ] + } + ], + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured_smt", + "name": "statement", + "prose": "The audit log directory contains audit log files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured_rationale", + "name": "rationale", + "prose": "Audit information includes all information including: audit records, audit settings and audit reports. This information is needed to successfully audit system activity. This information must be protected from unauthorized modification or deletion. If this information were to be compromised, forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure the audit log file directory mode is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured_obj" + }, + { + "rel": "script", + "href": "#57daba1f-ec1a-58c6-81ad-3d406fbd0e08" + } + ], + "prose": "Run the following script to verify the audit log directory is mode 0750 or more restrictive:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_perm_mask=\"0027\"\n if [ -e \"/etc/audit/auditd.conf\" ]; then\n l_audit_log_directory=\"$(dirname \"$(awk -F= '/^\\s*log_file\\s*/{print $2}' /etc/audit/auditd.conf | xargs)\")\"\n if [ -d \"$l_audit_log_directory\" ]; then\n l_maxperm=\"$(printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n l_directory_mode=\"$(stat -Lc '%#a' \"$l_audit_log_directory\")\"\n if [ $(( $l_directory_mode & $l_perm_mask )) -gt 0 ]; then\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Directory: \\\"$l_audit_log_directory\\\" is mode: \\\"$l_directory_mode\\\"\\n (should be mode: \\\"$l_maxperm\\\" or more restrictive)\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - Directory: \\\"$l_audit_log_directory\\\" is mode: \\\"$l_directory_mode\\\"\\n (should be mode: \\\"$l_maxperm\\\" or more restrictive)\\n\"\n fi\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - Log file directory not set in \\\"/etc/audit/auditd.conf\\\" please set log file directory\"\n fi\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - File: \\\"/etc/audit/auditd.conf\\\" not found\\n - ** Verify auditd is installed **\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to configure the audit log directory to have a mode of \"0750\" or less permissive:\n\n```\n# chmod g-w,o-rwx \"$(dirname \"$(awk -F= '/^\\s*log_file\\s*/{print $2}' /etc/audit/auditd.conf | xargs)\")\"\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured", + "title": "6.2.4.5 Ensure audit configuration files mode is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured_smt", + "name": "statement", + "prose": "Audit configuration files control auditd and what events are audited." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured_rationale", + "name": "rationale", + "prose": "Access to the audit configuration files could allow unauthorized personnel to prevent the auditing of critical events.\n\nMisconfigured audit configuration files may prevent the auditing of critical events or impact the system's performance by overwhelming the audit log. Misconfiguration of the audit configuration files may also make it more difficult to establish and investigate events relating to an incident." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit configuration files mode is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured_obj" + }, + { + "rel": "script", + "href": "#b33b3e27-0307-555d-85f8-633bc01ca592" + } + ], + "prose": "Run the following script to verify that the audit configuration files are mode `0640` or more restrictive:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" l_perm_mask=\"0137\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n while IFS= read -r -d $'\\0' l_fname; do\n l_mode=$(stat -Lc '%#a' \"$l_fname\")\n if [ $(( \"$l_mode\" & \"$l_perm_mask\" )) -gt 0 ]; then\n l_output2=\"$l_output2\\n - file: \\\"$l_fname\\\" is mode: \\\"$l_mode\\\" (should be mode: \\\"$l_maxperm\\\" or more restrictive)\"\n fi\n done < <(find /etc/audit/ -type f \\( -name \"*.conf\" -o -name '*.rules' \\) -print0)\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - All audit configuration files are mode: \\\"$l_maxperm\\\" or more restrictive\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n$l_output2\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to remove more permissive mode than `0640` from the audit configuration files:\n\n```\n# find /etc/audit/ -type f \\( -name '*.conf' -o -name '*.rules' \\) -exec chmod u-x,g-wx,o-rwx {} +\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured", + "title": "6.2.4.6 Ensure audit configuration files owner is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured_smt", + "name": "statement", + "prose": "Audit configuration files control auditd and what events are audited." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured_rationale", + "name": "rationale", + "prose": "Access to the audit configuration files could allow unauthorized personnel to prevent the auditing of critical events.\n\nMisconfigured audit configuration files may prevent the auditing of critical events or impact the system's performance by overwhelming the audit log. Misconfiguration of the audit configuration files may also make it more difficult to establish and investigate events relating to an incident." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit configuration files owner is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured_obj" + }, + { + "rel": "script", + "href": "#003b6f15-7428-5b5b-96c0-6a7b522244f9" + } + ], + "prose": "Run the following command to verify that the audit configuration files are owned by the root user:\n\n```\n# find /etc/audit/ -type f \\( -name '*.conf' -o -name '*.rules' \\) ! -user root\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to change ownership to `root` user:\n\n```\n# find /etc/audit/ -type f \\( -name '*.conf' -o -name '*.rules' \\) ! -user root -exec chown root {} +\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured", + "title": "6.2.4.7 Ensure audit configuration files group owner is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured_smt", + "name": "statement", + "prose": "Audit configuration files control auditd and what events are audited." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured_rationale", + "name": "rationale", + "prose": "Access to the audit configuration files could allow unauthorized personnel to prevent the auditing of critical events.\n\nMisconfigured audit configuration files may prevent the auditing of critical events or impact the system's performance by overwhelming the audit log. Misconfiguration of the audit configuration files may also make it more difficult to establish and investigate events relating to an incident." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit configuration files group owner is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured_obj" + }, + { + "rel": "script", + "href": "#c1a75251-7d45-5b0b-83b5-714fef3c3f89" + } + ], + "prose": "Run the following command to verify that the audit configuration files are owned by the group `root`:\n\n```\n# find /etc/audit/ -type f \\( -name '*.conf' -o -name '*.rules' \\) ! -group root\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to change group to `root`:\n\n```\n# find /etc/audit/ -type f \\( -name '*.conf' -o -name '*.rules' \\) ! -group root -exec chgrp root {} +\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured", + "title": "6.2.4.8 Ensure audit tools mode is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured_smt", + "name": "statement", + "prose": "Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured_rationale", + "name": "rationale", + "prose": "Protecting audit information includes identifying and protecting the tools used to view and manipulate log data. Protecting audit tools is necessary to prevent unauthorized operation on audit information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit tools mode is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured_obj" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + } + ], + "prose": "Run the following script to verify the audit tools are mode `0755` or more restrictive:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" l_perm_mask=\"0022\"\n l_maxperm=\"$( printf '%o' $(( 0777 & ~$l_perm_mask )) )\"\n a_audit_tools=(\"/sbin/auditctl\" \"/sbin/aureport\" \"/sbin/ausearch\" \"/sbin/autrace\" \"/sbin/auditd\" \"/sbin/augenrules\")\n for l_audit_tool in \"${a_audit_tools[@]}\"; do\n l_mode=\"$(stat -Lc '%#a' \"$l_audit_tool\")\"\n if [ $(( \"$l_mode\" & \"$l_perm_mask\" )) -gt 0 ]; then\n l_output2=\"$l_output2\\n - Audit tool \\\"$l_audit_tool\\\" is mode: \\\"$l_mode\\\" and should be mode: \\\"$l_maxperm\\\" or more restrictive\"\n else\n l_output=\"$l_output\\n - Audit tool \\\"$l_audit_tool\\\" is correctly configured to mode: \\\"$l_mode\\\"\"\n fi\n done\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :$l_output\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :$l_output2\\n\"\n [ -n \"$l_output\" ] && echo -e \"\\n - * Correctly configured * :\\n$l_output\\n\"\n fi\n unset a_audit_tools\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to remove more permissive mode from the audit tools:\n\n```\n# chmod go-w /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/augenrules\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured", + "title": "6.2.4.9 Ensure audit tools owner is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured_smt", + "name": "statement", + "prose": "Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured_rationale", + "name": "rationale", + "prose": "Protecting audit information includes identifying and protecting the tools used to view and manipulate log data. Protecting audit tools is necessary to prevent unauthorized operation on audit information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit tools owner is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured_obj" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify the audit tools are owned by the `root` user:\n\n```\n# stat -Lc \"%n %U\" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/augenrules | awk '$2 != \"root\" {print}'\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to change the owner of the audit tools to the `root` user:\n\n```\n# chown root /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/augenrules\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured", + "title": "6.2.4.10 Ensure audit tools group owner is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured_smt", + "name": "statement", + "prose": "Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured_rationale", + "name": "rationale", + "prose": "Protecting audit information includes identifying and protecting the tools used to view and manipulate log data. Protecting audit tools is necessary to prevent unauthorized operation on audit information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure audit tools group owner is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + } + ], + "prose": "Run the following command to verify the audit tools are owned by the group `root`\n\n```\n# stat -Lc \"%n %G\" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/augenrules | awk '$2 != \"root\" {print}'\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to change group ownership to the groop `root`:\n\n```\n# chgrp root /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/augenrules\n```" + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_6.3_Configure_Integrity_Checking", + "title": "Configure Integrity Checking", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed", + "title": "6.3.1 Ensure AIDE is installed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/14" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed_smt", + "name": "statement", + "prose": "AIDE takes a snapshot of filesystem state including modification times, permissions, and file hashes which can then be used to compare against the current state of the filesystem to detect modifications to the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed_rationale", + "name": "rationale", + "prose": "By monitoring the filesystem state compromised files can be detected to prevent or limit the exposure of accidental or malicious misconfigurations or modified binaries." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed_obj", + "name": "assessment-objective", + "prose": "Ensure AIDE is installed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed_obj" + } + ], + "prose": "Run the following command to verify `aide` is installed:\n\n```\n# dpkg-query -s aide &>/dev/null && echo \"aide is installed\"\n\naide is installed\n```\n\nRun the following command to verify `aide-common` is installed:\n\n```\n# dpkg-query -s aide-common &>/dev/null && echo \"aide-common is installed\"\n\naide-common is installed\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install AIDE using the appropriate package manager or manual installation:\n\n```\n# apt install aide aide-common\n```\n\nConfigure AIDE as appropriate for your environment. Consult the AIDE documentation for options.\n\nRun the following commands to initialize AIDE:\n\n```\n# aideinit\n# mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked", + "title": "6.3.2 Ensure filesystem integrity is regularly checked", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/8/subcontrol/5" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked_smt", + "name": "statement", + "prose": "Periodic checking of the filesystem integrity is needed to detect changes to the filesystem." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked_rationale", + "name": "rationale", + "prose": "Periodic file checking allows the system administrator to determine on a regular basis if critical files have been changed in an unauthorized fashion." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked_obj", + "name": "assessment-objective", + "prose": "Ensure filesystem integrity is regularly checked" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked_obj" + } + ], + "prose": "Run the following command:\n\n```\n# systemctl list-unit-files | awk '$1~/^dailyaidecheck\\.(timer|service)$/{print $1 \"\\t\" $2}'\n```\n\n*Example output:*\n\n```\ndailyaidecheck.service static\ndailyaidecheck.timer enabled\n```\n\nVerify `dailyaidecheck.timer` is `enabled` and `dailyaidecheck.service` is either `static` or `enabled`.\n\nRun the following command to verify `dailyaidecheck.timer` is `active`:\n\n```\n# systemctl is-active dailyaidecheck.timer\n\nactive\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to unmask `dailyaidecheck.timer` and `dailyaidecheck.service`:\n\n```\n# systemctl unmask dailyaidecheck.timer dailyaidecheck.service\n```\n\nRun the following command to enable and start `dailyaidecheck.timer`:\n\n```\n# systemctl --now enable dailyaidecheck.timer\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools", + "title": "6.3.3 Ensure cryptographic mechanisms are used to protect the integrity of audit tools", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools_smt", + "name": "statement", + "prose": "Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.\n\n`aide.conf` is case-sensitive. Leading and trailing white spaces are ignored. Each config lines must end with new line.\n\n`AIDE` uses the backslash character `\\` as escape character for '` `' (space), '@' and '' (backslash) (e.g. '\\ ' or '@'). To literally match a '' in a file path with a regular expression you have to escape the backslash twice (i.e. '\\\\').\n\nThere are three types of lines in `aide.conf`:\n\n- The configuration options which are used to set configuration parameters and define groups.\n\n- (restricted) rules that are used to indicate which files are added to the database.\n\n- Macro lines define or undefine variables within the config file.\n\n**Note:** Lines beginning with `#` are ignored as comments.\n\n`@@include` ** - Include **.\n\n- The content of the file is used as if it were inserted in this part of the config file.\n\n- The maximum depth of nested includes is 16.\n\n`@@include ** ** - [RULE_PREFIX] (added in AIDE v0.17)\n\n- Include all (regular) files found in matching regular expression (sub-directories are ignored).\n\n- The file are included in lexical sort order.\n\n- If `RULE_PREFIX` is set, all rules included by the statement are prefixed with given (added in AIDE v0.18). Prefixes from nested include statements are concatenated.\n\n- The content of the files is used as if it were inserted in this part of the config file.\n\n`@x_include`:\n\n- is identical to `@@include`, except that if a config file is executable is is run and the output is used as config.\n\n- If the executable file exits with status greater than zero or writes to stderr aide stops with an error.\n\n- For security reasons ** and each executable config file must be owned by the current user or root. They must not be group- or world-writable.\n\n- `@@x_include __` (added in AIDE v0.17):\n\n- `@@x_include ** ** [RULE_PREFIX] (added in AIDE v0.17)\n\n`@@x_include_setenv` ** ** (added in AIDE v0.17)\n\n- Adds the variable ** with the value ** to the environment used for config file execution.\n\n- Environment variable names are limited to alphanumeric characters (A-Za-z0-9) and the underscore '_' and must not begin with a digit." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools_rationale", + "name": "rationale", + "prose": "Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.\n\nAttackers may replace the audit tools or inject code into the existing tools with the purpose of providing the capability to hide or erase system activity from the audit logs.\n\nAudit tools should be cryptographically signed in order to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools_obj", + "name": "assessment-objective", + "prose": "Ensure cryptographic mechanisms are used to protect the integrity of audit tools" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools_obj" + }, + { + "rel": "script", + "href": "#698d979e-fb96-5253-8652-e5149d57c49b" + } + ], + "prose": "Verify that Advanced Intrusion Detection Environment (AIDE) is properly configured .\n\nRun the following script to verify:\n\n- AIDE is configured to use cryptographic mechanisms to protect the integrity of audit tools:\n\n- The following audit tool files include the options \"p, i, n, u, g, s, b, acl, xattrs and sha512\"\n\n- auditctl\n\n- auditd\n\n- ausearch\n\n- aureport\n\n- autrace\n\n- augenrules\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output=() a_output2=() l_tool_dir=\"$(readlink -f /sbin)\"\n a_items=(\"p\" \"i\" \"n\" \"u\" \"g\" \"s\" \"b\" \"acl\" \"xattrs\" \"sha512\")\n l_aide_cmd=\"$(whereis aide | awk '{print $2}')\"\n a_audit_files=(\"auditctl\" \"auditd\" \"ausearch\" \"aureport\" \"autrace\" \"augenrules\")\n if [ -f \"$l_aide_cmd\" ] && command -v \"$l_aide_cmd\" &>/dev/null; then\n a_aide_conf_files=(\"$(find -L /etc -type f -name 'aide.conf')\")\n f_file_par_chk()\n {\n a_out2=()\n for l_item in \"${a_items[@]}\"; do\n ! grep -Psiq -- '(\\h+|\\+)'\"$l_item\"'(\\h+|\\+)' <<< \"$l_out\" && \\\n a_out2+=(\" - Missing the \\\"$l_item\\\" option\")\n done\n if [ \"${#a_out2[@]}\" -gt \"0\" ]; then\n a_output2+=(\" - Audit tool file: \\\"$l_file\\\"\" \"${a_out2[@]}\")\n else\n a_output+=(\" - Audit tool file: \\\"$l_file\\\" includes:\" \" \\\"${a_items[*]}\\\"\")\n fi\n }\n for l_file in \"${a_audit_files[@]}\"; do\n if [ -f \"$l_tool_dir/$l_file\" ]; then\n l_out=\"$(\"$l_aide_cmd\" --config \"${a_aide_conf_files[@]}\" -p f:\"$l_tool_dir/$l_file\")\"\n f_file_par_chk\n else\n a_output+=(\" - Audit tool file \\\"$l_file\\\" doesn't exist\")\n fi\n done\n else\n a_output2+=(\" - The command \\\"aide\\\" was not found\" \" Please install AIDE\")\n fi\n if [ \"${#a_output2[@]}\" -le 0 ]; then\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** PASS **\" \"${a_output[@]}\" \"\"\n else\n printf '%s\\n' \"\" \"- Audit Result:\" \" ** FAIL **\" \" - Reason(s) for audit failure:\" \"${a_output2[@]}\"\n [ \"${#a_output[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"- Correctly set:\" \"${a_output[@]}\" \"\"\n fi\n}\n```\n\n**Note:** The script is written to read the \"winning\" configuration setting, to include any configuration settings in files included as part of the `@@x_include` setting." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to determine the absolute path to the non-symlinked version on the audit tools:\n\n```\n# readlink -f /sbin\n```\n\nThe output will be either `/usr/sbin` **- OR -** `/sbin`. Ensure the correct path is used.\n\nEdit `/etc/aide/aide.conf` and add or update the following selection lines replacing `` with the correct path returned in the command above:\n\n```\n# Audit Tools\n/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512\n/auditd p+i+n+u+g+s+b+acl+xattrs+sha512\n/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512\n/aureport p+i+n+u+g+s+b+acl+xattrs+sha512\n/autrace p+i+n+u+g+s+b+acl+xattrs+sha512\n/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512\n```\n\n*Example*\n\n```\n# printf '%s\\n' \"\" \"# Audit Tools\" \"$(readlink -f /sbin/auditctl) p+i+n+u+g+s+b+acl+xattrs+sha512\" \"$(readlink -f /sbin/auditd) p+i+n+u+g+s+b+acl+xattrs+sha512\" \"$(readlink -f /sbin/ausearch) p+i+n+u+g+s+b+acl+xattrs+sha512\" \"$(readlink -f /sbin/aureport) p+i+n+u+g+s+b+acl+xattrs+sha512\" \"$(readlink -f /sbin/autrace) p+i+n+u+g+s+b+acl+xattrs+sha512\" \"$(readlink -f /sbin/augenrules) p+i+n+u+g+s+b+acl+xattrs+sha512\" >> /etc/aide/aide.conf\n```\n\n**Note: - IF -** `/etc/aide/aide.conf` includes a `@@x_include` statement:\n\n- ** and each executable config file must be owned by the current user or root\n\n- They must not be group or world-writable\n\n*Example:*\n\n```\n@@x_include /etc/aide.conf.d ^[a-zA-Z0-9_-]+$\n```" + } + ] + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_7_System_Maintenance", + "title": "System Maintenance", + "groups": [ + { + "id": "xccdf_org.cisecurity.benchmarks_group_7.1_System_File_Permissions", + "title": "System File Permissions", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured", + "title": "7.1.1 Ensure permissions on /etc/passwd are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured_smt", + "name": "statement", + "prose": "The `/etc/passwd` file contains user account information that is used by many system utilities and therefore must be readable for these utilities to operate." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured_rationale", + "name": "rationale", + "prose": "It is critical to ensure that the `/etc/passwd` file is protected from unauthorized write access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/passwd are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify `/etc/passwd` is mode 644 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root`:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/passwd\n\nAccess: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to remove excess permissions, set owner, and set group on `/etc/passwd`:\n\n```\n# chmod u-x,go-wx /etc/passwd\n# chown root:root /etc/passwd\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured", + "title": "7.1.2 Ensure permissions on /etc/passwd- are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured_smt", + "name": "statement", + "prose": "The `/etc/passwd-` file contains backup user account information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured_rationale", + "name": "rationale", + "prose": "It is critical to ensure that the `/etc/passwd-` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/passwd- are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify `/etc/passwd-` is mode 644 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root`:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: { %g/ %G)' /etc/passwd-\n\nAccess: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: { 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to remove excess permissions, set owner, and set group on `/etc/passwd-`:\n\n```\n# chmod u-x,go-wx /etc/passwd-\n# chown root:root /etc/passwd-\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured", + "title": "7.1.3 Ensure permissions on /etc/group are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured_smt", + "name": "statement", + "prose": "The `/etc/group` file contains a list of all the valid groups defined in the system. The command below allows read/write access for root and read access for everyone else." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured_rationale", + "name": "rationale", + "prose": "The `/etc/group` file needs to be protected from unauthorized changes by non-privileged users, but needs to be readable as this information is used with many non-privileged programs." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/group are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify `/etc/group` is mode 644 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root`:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/group\n\nAccess: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to remove excess permissions, set owner, and set group on `/etc/group`:\n\n```\n# chmod u-x,go-wx /etc/group\n# chown root:root /etc/group\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured", + "title": "7.1.4 Ensure permissions on /etc/group- are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured_smt", + "name": "statement", + "prose": "The `/etc/group-` file contains a backup list of all the valid groups defined in the system." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured_rationale", + "name": "rationale", + "prose": "It is critical to ensure that the `/etc/group-` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/group- are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify `/etc/group-` is mode 644 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root`:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/group-\n\nAccess: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to remove excess permissions, set owner, and set group on `/etc/group-`:\n\n```\n# chmod u-x,go-wx /etc/group-\n# chown root:root /etc/group-\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured", + "title": "7.1.5 Ensure permissions on /etc/shadow are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured_smt", + "name": "statement", + "prose": "The `/etc/shadow` file is used to store the information about user accounts that is critical to the security of those accounts, such as the hashed password and other security information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured_rationale", + "name": "rationale", + "prose": "If attackers can gain read access to the `/etc/shadow` file, they can easily run a password cracking program against the hashed password to break it. Other security information that is stored in the `/etc/shadow` file (such as expiration) could also be useful to subvert the user accounts." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/shadow are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify `/etc/shadow` is mode 640 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root` or ({GID}/ shadow):\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/shadow\n```\n\n*Example:*\n\n```\nAccess: (0640/-rw-r-----) Uid: ( 0/ root) Gid: ( 42/ shadow)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run **one** of the following commands to set ownership of `/etc/shadow` to `root` and group to either `root` or `shadow`:\n\n```\n# chown root:shadow /etc/shadow\n -OR-\n# chown root:root /etc/shadow\n```\n\nRun the following command to remove excess permissions form `/etc/shadow`:\n\n```\n# chmod u-x,g-wx,o-rwx /etc/shadow\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured", + "title": "7.1.6 Ensure permissions on /etc/shadow- are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured_smt", + "name": "statement", + "prose": "The `/etc/shadow-` file is used to store backup information about user accounts that is critical to the security of those accounts, such as the hashed password and other security information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured_rationale", + "name": "rationale", + "prose": "It is critical to ensure that the `/etc/shadow-` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/shadow- are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify `/etc/shadow-` is mode 640 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root` or `{GID}/shadow`:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/shadow-\n```\n\n*Example:*\n\n```\nAccess: (0640/-rw-r-----) Uid: ( 0/ root) Gid: ( 42/ shadow)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run **one** of the following commands to set ownership of `/etc/shadow-` to `root` and group to either `root` or `shadow`:\n\n```\n# chown root:shadow /etc/shadow-\n -OR-\n# chown root:root /etc/shadow-\n```\n\nRun the following command to remove excess permissions form `/etc/shadow-`:\n\n```\n# chmod u-x,g-wx,o-rwx /etc/shadow-\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured", + "title": "7.1.7 Ensure permissions on /etc/gshadow are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured_smt", + "name": "statement", + "prose": "The `/etc/gshadow` file is used to store the information about groups that is critical to the security of those accounts, such as the hashed password and other security information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured_rationale", + "name": "rationale", + "prose": "If attackers can gain read access to the `/etc/gshadow` file, they can easily run a password cracking program against the hashed password to break it. Other security information that is stored in the `/etc/gshadow` file (such as group administrators) could also be useful to subvert the group." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/gshadow are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify `/etc/gshadow` is mode 640 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root` or `{GID}/shadow:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/gshadow\n```\n\n*Example:*\n\n```\nAccess: (0640/-rw-r-----) Uid: ( 0/ root) Gid: ( 42/ shadow)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run **one** of the following commands to set ownership of `/etc/gshadow` to `root` and group to either `root` or `shadow`:\n\n```\n# chown root:shadow /etc/gshadow\n -OR-\n# chown root:root /etc/gshadow\n```\n\nRun the following command to remove excess permissions form `/etc/gshadow`:\n\n```\n# chmod u-x,g-wx,o-rwx /etc/gshadow\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured", + "title": "7.1.8 Ensure permissions on /etc/gshadow- are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured_smt", + "name": "statement", + "prose": "The `/etc/gshadow-` file is used to store backup information about groups that is critical to the security of those accounts, such as the hashed password and other security information." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured_rationale", + "name": "rationale", + "prose": "It is critical to ensure that the `/etc/gshadow-` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/gshadow- are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify `/etc/gshadow-` is mode 640 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root` or `{GID}/shadow`:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/gshadow-\n```\n\n*Example:*\n\n```\nAccess: (0640/-rw-r-----) Uid: ( 0/ root) Gid: ( 42/ shadow)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run **one** of the following commands to set ownership of `/etc/gshadow-` to `root` and group to either `root` or `shadow`:\n\n```\n# chown root:shadow /etc/gshadow-\n -OR-\n# chown root:root /etc/gshadow-\n```\n\nRun the following command to remove excess permissions form `/etc/gshadow-`:\n\n```\n# chmod u-x,g-wx,o-rwx /etc/gshadow-\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured", + "title": "7.1.9 Ensure permissions on /etc/shells are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured_smt", + "name": "statement", + "prose": "`/etc/shells` is a text file which contains the full pathnames of valid login shells. This file is consulted by `chsh` and available to be queried by other programs." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured_rationale", + "name": "rationale", + "prose": "It is critical to ensure that the `/etc/shells` file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/shells are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following command to verify `/etc/shells` is mode 644 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root`:\n\n```\n# stat -Lc 'Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/shells\n\nAccess: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to remove excess permissions, set owner, and set group on `/etc/shells`:\n\n```\n# chmod u-x,go-wx /etc/shells\n# chown root:root /etc/shells\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured", + "title": "7.1.10 Ensure permissions on /etc/security/opasswd are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured_smt", + "name": "statement", + "prose": "`/etc/security/opasswd` and it's backup `/etc/security/opasswd.old` hold user's previous passwords if `pam_unix` or `pam_pwhistory` is in use on the system" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured_rationale", + "name": "rationale", + "prose": "It is critical to ensure that `/etc/security/opasswd` is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure permissions on /etc/security/opasswd are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured_obj" + }, + { + "rel": "script", + "href": "#bf7369ee-da68-5c46-bf41-d90974408be7" + }, + { + "rel": "script", + "href": "#8562a87f-938a-5f79-8e44-1d3a4068684e" + }, + { + "rel": "script", + "href": "#93db8f79-a8a0-5916-a892-1009381d7426" + } + ], + "prose": "Run the following commands to verify `/etc/security/opasswd` and `/etc/security/opasswd.old` are mode 600 or more restrictive, `Uid` is `0/root` and `Gid` is `0/root` if they exist:\n\n```\n# [ -e \"/etc/security/opasswd\" ] && stat -Lc '%n Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/security/opasswd\n\n/etc/security/opasswd Access: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ root)\n -OR-\nNothing is returned\n```\n\n```\n# [ -e \"/etc/security/opasswd.old\" ] && stat -Lc '%n Access: (%#a/%A) Uid: ( %u/ %U) Gid: ( %g/ %G)' /etc/security/opasswd.old\n\n/etc/security/opasswd.old Access: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ root)\n -OR-\nNothing is returned\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following commands to remove excess permissions, set owner, and set group on `/etc/security/opasswd` and `/etc/security/opasswd.old` is they exist:\n\n```\n# [ -e \"/etc/security/opasswd\" ] && chmod u-x,go-rwx /etc/security/opasswd\n# [ -e \"/etc/security/opasswd\" ] && chown root:root /etc/security/opasswd\n# [ -e \"/etc/security/opasswd.old\" ] && chmod u-x,go-rwx /etc/security/opasswd.old\n# [ -e \"/etc/security/opasswd.old\" ] && chown root:root /etc/security/opasswd.old\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured", + "title": "7.1.11 Ensure world writable files and directories are secured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured_smt", + "name": "statement", + "prose": "World writable files are the least secure. Data in world-writable files can be modified and compromised by any user on the system. World writable files may also indicate an incorrectly written script or program that could potentially be the cause of a larger compromise to the system's integrity. See the `chmod(2)` man page for more information.\n\nSetting the sticky bit on world writable directories prevents users from deleting or renaming files in that directory that are not owned by them." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured_rationale", + "name": "rationale", + "prose": "Data in world-writable files can be modified and compromised by any user on the system. World writable files may also indicate an incorrectly written script or program that could potentially be the cause of a larger compromise to the system's integrity.\n\nThis feature prevents the ability to delete or rename files in world writable directories (such as `/tmp` ) that are owned by another user." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured_obj", + "name": "assessment-objective", + "prose": "Ensure world writable files and directories are secured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured_obj" + }, + { + "rel": "script", + "href": "#fb1d60f7-025e-5da4-ab52-8089bb071f6f" + } + ], + "prose": "Run the following script to verify:\n\n- No world writable files exist\n\n- No world writable directories without the sticky bit exist\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n l_smask='01000'\n a_file=(); a_dir=() # Initialize arrays\n a_path=(! -path \"/run/user/*\" -a ! -path \"/proc/*\" -a ! -path \"*/containerd/*\" -a ! -path \"*/kubelet/pods/*\" -a ! -path \"*/kubelet/plugins/*\" -a ! -path \"/sys/*\" -a ! -path \"/snap/*\")\n while IFS= read -r l_mount; do\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n [ -f \"$l_file\" ] && a_file+=(\"$l_file\") # Add WR files\n if [ -d \"$l_file\" ]; then # Add directories w/o sticky bit\n l_mode=\"$(stat -Lc '%#a' \"$l_file\")\"\n [ ! $(( $l_mode & $l_smask )) -gt 0 ] && a_dir+=(\"$l_file\")\n fi\n fi\n done < <(find \"$l_mount\" -xdev \\( \"${a_path[@]}\" \\) \\( -type f -o -type d \\) -perm -0002 -print0 2> /dev/null)\n done < <(findmnt -Dkerno fstype,target | awk '($1 !~ /^\\s*(nfs|proc|smb|vfat|iso9660|efivarfs|selinuxfs)/ && $2 !~ /^(\\/run\\/user\\/|\\/tmp|\\/var\\/tmp)/){print $2}')\n if ! (( ${#a_file[@]} > 0 )); then\n l_output=\"$l_output\\n - No world writable files exist on the local filesystem.\"\n else\n l_output2=\"$l_output2\\n - There are \\\"$(printf '%s' \"${#a_file[@]}\")\\\" World writable files on the system.\\n - The following is a list of World writable files:\\n$(printf '%s\\n' \"${a_file[@]}\")\\n - end of list\\n\"\n fi\n if ! (( ${#a_dir[@]} > 0 )); then\n l_output=\"$l_output\\n - Sticky bit is set on world writable directories on the local filesystem.\"\n else\n l_output2=\"$l_output2\\n - There are \\\"$(printf '%s' \"${#a_dir[@]}\")\\\" World writable directories without the sticky bit on the system.\\n - The following is a list of World writable directories without the sticky bit:\\n$(printf '%s\\n' \"${a_dir[@]}\")\\n - end of list\\n\"\n fi\n unset a_path; unset a_arr; unset a_file; unset a_dir # Remove arrays\n # If l_output2 is empty, we pass\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\"\n [ -n \"$l_output\" ] && echo -e \"- * Correctly configured * :\\n$l_output\\n\"\n fi\n}\n```\n\n**Note:** On systems with a large number of files and/or directories, this audit may be a long running process" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "- World Writable Files:\n\n- It is recommended that write access is removed from `other` with the command ( `chmod o-w ` ), but always consult relevant vendor documentation to avoid breaking any application dependencies on a given file.\n\n- World Writable Directories:\n\n- Set the sticky bit on all world writable directories with the command ( `chmod a+t ` )\n\nRun the following script to:\n\n- Remove other write permission from any world writable files\n\n- Add the sticky bit to all world writable directories\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_smask='01000'\n a_file=(); a_dir=() # Initialize arrays\n a_path=(! -path \"/run/user/*\" -a ! -path \"/proc/*\" -a ! -path \"*/containerd/*\" -a ! -path \"*/kubelet/pods/*\" -a ! -path \"*/kubelet/plugins/*\" -a ! -path \"/sys/*\" -a ! -path \"/snap/*\")\n while IFS= read -r l_mount; do\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n l_mode=\"$(stat -Lc '%#a' \"$l_file\")\"\n if [ -f \"$l_file\" ]; then # Remove excess permissions from WW files\n echo -e \" - File: \\\"$l_file\\\" is mode: \\\"$l_mode\\\"\\n - removing write permission on \\\"$l_file\\\" from \\\"other\\\"\"\n chmod o-w \"$l_file\"\n fi\n if [ -d \"$l_file\" ]; then # Add sticky bit\n if [ ! $(( $l_mode & $l_smask )) -gt 0 ]; then\n echo -e \" - Directory: \\\"$l_file\\\" is mode: \\\"$l_mode\\\" and doesn't have the sticky bit set\\n - Adding the sticky bit\"\n chmod a+t \"$l_file\"\n fi\n fi\n fi\n done < <(find \"$l_mount\" -xdev \\( \"${a_path[@]}\" \\) \\( -type f -o -type d \\) -perm -0002 -print0 2> /dev/null)\n done < <(findmnt -Dkerno fstype,target | awk '($1 !~ /^\\s*(nfs|proc|smb|vfat|iso9660|efivarfs|selinuxfs)/ && $2 !~ /^(\\/run\\/user\\/|\\/tmp|\\/var\\/tmp)/){print $2}')\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist", + "title": "7.1.12 Ensure no files or directories without an owner and a group exist", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist_smt", + "name": "statement", + "prose": "Administrators may delete users or groups from the system and neglect to remove all files and/or directories owned by those users or groups." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist_rationale", + "name": "rationale", + "prose": "A new user or group who is assigned a deleted user's user ID or group ID may then end up \"owning\" a deleted user or group's files, and thus have more access on the system than was intended." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist_obj", + "name": "assessment-objective", + "prose": "Ensure no files or directories without an owner and a group exist" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist_obj" + }, + { + "rel": "script", + "href": "#8831a090-5cfc-56cc-a3cd-259d13d9d90d" + } + ], + "prose": "Run the following script to verify no unowned or ungrouped files or directories exist:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n a_nouser=(); a_nogroup=() # Initialize arrays\n a_path=(! -path \"/run/user/*\" -a ! -path \"/proc/*\" -a ! -path \"*/containerd/*\" -a ! -path \"*/kubelet/pods/*\" -a ! -path \"*/kubelet/plugins/*\" -a ! -path \"/sys/fs/cgroup/memory/*\" -a ! -path \"/var/*/private/*\")\n while IFS= read -r l_mount; do\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n while IFS=: read -r l_user l_group; do\n [ \"$l_user\" = \"UNKNOWN\" ] && a_nouser+=(\"$l_file\")\n [ \"$l_group\" = \"UNKNOWN\" ] && a_nogroup+=(\"$l_file\")\n done < <(stat -Lc '%U:%G' \"$l_file\")\n fi\n done < <(find \"$l_mount\" -xdev \\( \"${a_path[@]}\" \\) \\( -type f -o -type d \\) \\( -nouser -o -nogroup \\) -print0 2> /dev/null)\n done < <(findmnt -Dkerno fstype,target | awk '($1 !~ /^\\s*(nfs|proc|smb|vfat|iso9660|efivarfs|selinuxfs)/ && $2 !~ /^\\/run\\/user\\//){print $2}')\n if ! (( ${#a_nouser[@]} > 0 )); then\n l_output=\"$l_output\\n - No files or directories without a owner exist on the local filesystem.\"\n else\n l_output2=\"$l_output2\\n - There are \\\"$(printf '%s' \"${#a_nouser[@]}\")\\\" unowned files or directories on the system.\\n - The following is a list of unowned files and/or directories:\\n$(printf '%s\\n' \"${a_nouser[@]}\")\\n - end of list\"\n fi\n if ! (( ${#a_nogroup[@]} > 0 )); then\n l_output=\"$l_output\\n - No files or directories without a group exist on the local filesystem.\"\n else\n l_output2=\"$l_output2\\n - There are \\\"$(printf '%s' \"${#a_nogroup[@]}\")\\\" ungrouped files or directories on the system.\\n - The following is a list of ungrouped files and/or directories:\\n$(printf '%s\\n' \"${a_nogroup[@]}\")\\n - end of list\"\n fi\n unset a_path; unset a_arr ; unset a_nouser; unset a_nogroup # Remove arrays\n if [ -z \"$l_output2\" ]; then # If l_output2 is empty, we pass\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\"\n [ -n \"$l_output\" ] && echo -e \"\\n- * Correctly configured * :\\n$l_output\\n\"\n fi\n}\n```\n\n**Note:** On systems with a large number of files and/or directories, this audit may be a long running process" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Remove or set ownership and group ownership of these files and/or directories to an active user on the system as appropriate." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed", + "title": "7.1.13 Ensure SUID and SGID files are reviewed", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed_smt", + "name": "statement", + "prose": "The owner of a file can set the file's permissions to run with the owner's or group's permissions, even if the user running the program is not the owner or a member of the group. The most common reason for a SUID or SGID program is to enable users to perform functions (such as changing their password) that require root privileges." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed_rationale", + "name": "rationale", + "prose": "There are valid reasons for SUID and SGID programs, but it is important to identify and review such programs to ensure they are legitimate. Review the files returned by the action in the audit section and check to see if system binaries have a different checksum than what from the package. This is an indication that the binary may have been replaced." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed_obj", + "name": "assessment-objective", + "prose": "Ensure SUID and SGID files are reviewed" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "EXAMINE" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed_obj" + } + ], + "prose": "Run the following script to generate a list of SUID and SGID files:\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\"\n a_suid=(); a_sgid=() # initialize arrays\n while IFS= read -r l_mount; do\n while IFS= read -r -d $'\\0' l_file; do\n if [ -e \"$l_file\" ]; then\n l_mode=\"$(stat -Lc '%#a' \"$l_file\")\"\n [ $(( $l_mode & 04000 )) -gt 0 ] && a_suid+=(\"$l_file\")\n [ $(( $l_mode & 02000 )) -gt 0 ] && a_sgid+=(\"$l_file\")\n fi\n done < <(find \"$l_mount\" -xdev -type f \\( -perm -2000 -o -perm -4000 \\) -print0 2>/dev/null)\n done < <(findmnt -Dkerno fstype,target,options | awk '($1 !~ /^\\s*(nfs|proc|smb|vfat|iso9660|efivarfs|selinuxfs)/ && $2 !~ /^\\/run\\/user\\// && $3 !~/noexec/ && $3 !~/nosuid/) {print $2}')\n if ! (( ${#a_suid[@]} > 0 )); then\n l_output=\"$l_output\\n - No executable SUID files exist on the system\"\n else\n l_output2=\"$l_output2\\n - List of \\\"$(printf '%s' \"${#a_suid[@]}\")\\\" SUID executable files:\\n$(printf '%s\\n' \"${a_suid[@]}\")\\n - end of list -\\n\"\n fi\n if ! (( ${#a_sgid[@]} > 0 )); then\n l_output=\"$l_output\\n - No SGID files exist on the system\"\n else\n l_output2=\"$l_output2\\n - List of \\\"$(printf '%s' \"${#a_sgid[@]}\")\\\" SGID executable files:\\n$(printf '%s\\n' \"${a_sgid[@]}\")\\n - end of list -\\n\"\n fi\n [ -n \"$l_output2\" ] && l_output2=\"$l_output2\\n- Review the preceding list(s) of SUID and/or SGID files to\\n- ensure that no rogue programs have been introduced onto the system.\\n\"\n unset a_arr; unset a_suid; unset a_sgid # Remove arrays\n # If l_output2 is empty, Nothing to report\n if [ -z \"$l_output2\" ]; then\n echo -e \"\\n- Audit Result:\\n$l_output\\n\"\n else\n echo -e \"\\n- Audit Result:\\n$l_output2\\n\"\n [ -n \"$l_output\" ] && echo -e \"$l_output\\n\"\n fi\n}\n```\n\n**Note:** on systems with a large number of files, this may be a long running process" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Ensure that no rogue SUID or SGID programs have been introduced into the system. Review the files returned by the action in the Audit section and confirm the integrity of these binaries." + } + ] + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_group_7.2_Local_User_and_Group_Settings", + "title": "Local User and Group Settings", + "controls": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords", + "title": "7.2.1 Ensure accounts in /etc/passwd use shadowed passwords", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/11" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords_smt", + "name": "statement", + "prose": "Local accounts can uses shadowed passwords. With shadowed passwords, The passwords are saved in shadow password file, `/etc/shadow`, encrypted by a salted one-way hash. Accounts with a shadowed password have an `x` in the second field in `/etc/passwd`." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords_rationale", + "name": "rationale", + "prose": "The `/etc/passwd` file also contains information like user ID's and group ID's that are used by many system programs. Therefore, the `/etc/passwd` file must remain world readable. In spite of encoding the password with a randomly-generated one-way hash function, an attacker could still break the system if they got access to the `/etc/passwd` file. This can be mitigated by using shadowed passwords, thus moving the passwords in the `/etc/passwd` file to `/etc/shadow`. The `/etc/shadow` file is set so only root will be able to read and write. This helps mitigate the risk of an attacker gaining access to the encoded passwords with which to perform a dictionary attack.\n\n**Note:**\n\n- All accounts must have passwords or be locked to prevent the account from being used by an unauthorized user.\n\n- A user account with an empty second field in `/etc/passwd` allows the account to be logged into by providing only the username." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords_obj", + "name": "assessment-objective", + "prose": "Ensure accounts in /etc/passwd use shadowed passwords" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords_obj" + } + ], + "prose": "Run the following command and verify that no output is returned:\n\n```\n# awk -F: '($2 != \"x\" ) { print \"User: \\\"\" $1 \"\\\" is not set to shadowed passwords \"}' /etc/passwd\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to set accounts to use shadowed passwords and migrate passwords in `/etc/passwd` to `/etc/shadow`:\n\n```\n# pwconv\n```\n\nInvestigate to determine if the account is logged in and what it is being used for, to determine if it needs to be forced off." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty", + "title": "7.2.2 Ensure /etc/shadow password fields are not empty", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/5/subcontrol/2" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty_smt", + "name": "statement", + "prose": "An account with an empty password field means that anybody may log in as that user without providing a password." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty_rationale", + "name": "rationale", + "prose": "All accounts must have passwords or be locked to prevent the account from being used by an unauthorized user." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty_obj", + "name": "assessment-objective", + "prose": "Ensure /etc/shadow password fields are not empty" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty_obj" + }, + { + "rel": "script", + "href": "#68883ac0-8ede-5f78-b91a-1ae0f321d81f" + } + ], + "prose": "Run the following command and verify that no output is returned:\n\n```\n# awk -F: '($2 == \"\" ) { print $1 \" does not have a password \"}' /etc/shadow\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "If any accounts in the `/etc/shadow` file do not have a password, run the following command to lock the account until it can be determined why it does not have a password:\n\n```\n# passwd -l \n```\n\nAlso, check to see if the account is logged in and investigate what it is being used for to determine if it needs to be forced off." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup", + "title": "7.2.3 Ensure all groups in /etc/passwd exist in /etc/group", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + }, + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/14/subcontrol/6" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup_smt", + "name": "statement", + "prose": "Over time, system administration errors and changes can lead to groups being defined in `/etc/passwd` but not in `/etc/group` ." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup_rationale", + "name": "rationale", + "prose": "Groups defined in the `/etc/passwd` file but not in the `/etc/group` file pose a threat to system security since group permissions are not properly managed." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup_obj", + "name": "assessment-objective", + "prose": "Ensure all groups in /etc/passwd exist in /etc/group" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup_obj" + }, + { + "rel": "script", + "href": "#997edba2-e4f3-536a-aa35-6cf12f432c61" + } + ], + "prose": "Run the following script to verify all GIDs in `/etc/passwd` exist in `/etc/group`:\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_passwd_group_gid=(\"$(awk -F: '{print $4}' /etc/passwd | sort -u)\")\n a_group_gid=(\"$(awk -F: '{print $3}' /etc/group | sort -u)\")\n a_passwd_group_diff=(\"$(printf '%s\\n' \"${a_group_gid[@]}\" \"${a_passwd_group_gid[@]}\" | sort | uniq -u)\")\n while IFS= read -r l_gid; do\n awk -F: '($4 == '\"$l_gid\"') {print \" - User: \\\"\" $1 \"\\\" has GID: \\\"\" $4 \"\\\" which does not exist in /etc/group\" }' /etc/passwd\n done < <(printf '%s\\n' \"${a_passwd_group_gid[@]}\" \"${a_passwd_group_diff[@]}\" | sort | uniq -D | uniq)\n unset a_passwd_group_gid; unset a_group_gid; unset a_passwd_group_diff\n}\n```\n\nNothing should be returned" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Analyze the output of the Audit step above and perform the appropriate action to correct any discrepancies found." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty", + "title": "7.2.4 Ensure shadow group is empty", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty_smt", + "name": "statement", + "prose": "The shadow group allows system programs which require access the ability to read the /etc/shadow file. No users should be assigned to the shadow group." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty_rationale", + "name": "rationale", + "prose": "Any users assigned to the shadow group would be granted read access to the /etc/shadow file. If attackers can gain read access to the `/etc/shadow` file, they can easily run a password cracking program against the hashed passwords to break them. Other security information that is stored in the `/etc/shadow` file (such as expiration) could also be useful to subvert additional user accounts." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty_obj", + "name": "assessment-objective", + "prose": "Ensure shadow group is empty" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty_obj" + }, + { + "rel": "script", + "href": "#c9eefbb7-8bd3-56c5-809b-2cfaf19f2d91" + } + ], + "prose": "Run the following commands and verify no results are returned:\n\n```\n# awk -F: '($1==\"shadow\") {print $NF}' /etc/group\n# awk -F: '($4 == '\"$(getent group shadow | awk -F: '{print $3}' | xargs)\"') {print \" - user: \\\"\" $1 \"\\\" primary group is the shadow group\"}' /etc/passwd\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Run the following command to remove all users from the shadow group\n\n```\n# sed -ri 's/(^shadow:[^:]*:[^:]*:)([^:]+$)/\\1/' /etc/group\n```\n\nChange the primary group of any users with shadow as their primary group.\n\n```\n# usermod -g \n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist", + "title": "7.2.5 Ensure no duplicate UIDs exist", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist_smt", + "name": "statement", + "prose": "Although the `useradd` program will not let you create a duplicate User ID (UID), it is possible for an administrator to manually edit the `/etc/passwd` file and change the UID field." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist_rationale", + "name": "rationale", + "prose": "Users must be assigned unique UIDs for accountability and to ensure appropriate access protections." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist_obj", + "name": "assessment-objective", + "prose": "Ensure no duplicate UIDs exist" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist_obj" + }, + { + "rel": "script", + "href": "#86fad0e7-86b5-57a5-893d-8bb824a3e371" + } + ], + "prose": "Run the following script and verify no results are returned:\n\n```bash\n#!/usr/bin/env bash\n\n{\n while read -r l_count l_uid; do\n if [ \"$l_count\" -gt 1 ]; then\n echo -e \"Duplicate UID: \\\"$l_uid\\\" Users: \\\"$(awk -F: '($3 == n) { print $1 }' n=$l_uid /etc/passwd | xargs)\\\"\"\n fi\n done < <(cut -f3 -d\":\" /etc/passwd | sort -n | uniq -c)\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Based on the results of the audit script, establish unique UIDs and review all files owned by the shared UIDs to determine which UID they are supposed to belong to." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist", + "title": "7.2.6 Ensure no duplicate GIDs exist", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist_smt", + "name": "statement", + "prose": "Although the `groupadd` program will not let you create a duplicate Group ID (GID), it is possible for an administrator to manually edit the `/etc/group` file and change the GID field." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist_rationale", + "name": "rationale", + "prose": "User groups must be assigned unique GIDs for accountability and to ensure appropriate access protections." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist_obj", + "name": "assessment-objective", + "prose": "Ensure no duplicate GIDs exist" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist_obj" + }, + { + "rel": "script", + "href": "#c9ff0d40-4cd4-58a0-8ef9-bfbaaa07b52d" + } + ], + "prose": "Run the following script and verify no results are returned:\n\n```bash\n#!/usr/bin/env bash\n\n{\n while read -r l_count l_gid; do\n if [ \"$l_count\" -gt 1 ]; then\n echo -e \"Duplicate GID: \\\"$l_gid\\\" Groups: \\\"$(awk -F: '($3 == n) { print $1 }' n=$l_gid /etc/group | xargs)\\\"\"\n fi\n done < <(cut -f3 -d\":\" /etc/group | sort -n | uniq -c)\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Based on the results of the audit script, establish unique GIDs and review all files owned by the shared GID to determine which group they are supposed to belong to." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist", + "title": "7.2.7 Ensure no duplicate user names exist", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist_smt", + "name": "statement", + "prose": "Although the `useradd` program will not let you create a duplicate user name, it is possible for an administrator to manually edit the `/etc/passwd` file and change the user name." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist_rationale", + "name": "rationale", + "prose": "If a user is assigned a duplicate user name, it will create and have access to files with the first UID for that username in `/etc/passwd` . For example, if \"test4\" has a UID of 1000 and a subsequent \"test4\" entry has a UID of 2000, logging in as \"test4\" will use UID 1000. Effectively, the UID is shared, which is a security problem." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist_obj", + "name": "assessment-objective", + "prose": "Ensure no duplicate user names exist" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist_obj" + }, + { + "rel": "script", + "href": "#338088f7-4f5b-55b8-b668-0eb40c86ff37" + } + ], + "prose": "Run the following script and verify no results are returned:\n\n```bash\n#!/usr/bin/env bash\n\n{\n while read -r l_count l_user; do\n if [ \"$l_count\" -gt 1 ]; then\n echo -e \"Duplicate User: \\\"$l_user\\\" Users: \\\"$(awk -F: '($1 == n) { print $1 }' n=$l_user /etc/passwd | xargs)\\\"\"\n fi\n done < <(cut -f1 -d\":\" /etc/group | sort -n | uniq -c)\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Based on the results of the audit script, establish unique user names for the users. File ownerships will automatically reflect the change as long as the users have unique UIDs." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist", + "title": "7.2.8 Ensure no duplicate group names exist", + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist_smt", + "name": "statement", + "prose": "Although the `groupadd` program will not let you create a duplicate group name, it is possible for an administrator to manually edit the `/etc/group` file and change the group name." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist_rationale", + "name": "rationale", + "prose": "If a group is assigned a duplicate group name, it will create and have access to files with the first GID for that group in `/etc/group` . Effectively, the GID is shared, which is a security problem." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist_obj", + "name": "assessment-objective", + "prose": "Ensure no duplicate group names exist" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist_obj" + }, + { + "rel": "script", + "href": "#2eeb230a-482b-5b9c-a554-44ec61456b37" + } + ], + "prose": "Run the following script and verify no results are returned:\n\n```bash\n#!/usr/bin/env bash\n\n{\n while read -r l_count l_group; do\n if [ \"$l_count\" -gt 1 ]; then\n echo -e \"Duplicate Group: \\\"$l_group\\\" Groups: \\\"$(awk -F: '($1 == n) { print $1 }' n=$l_group /etc/group | xargs)\\\"\"\n fi\n done < <(cut -f1 -d\":\" /etc/group | sort -n | uniq -c)\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Based on the results of the audit script, establish unique names for the user groups. File group ownerships will automatically reflect the change as long as the groups have unique GIDs." + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured", + "title": "7.2.9 Ensure local interactive user home directories are configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured_smt", + "name": "statement", + "prose": "The user home directory is space defined for the particular user to set local environment variables and to store personal files. While the system administrator can establish secure permissions for users' home directories, the users can easily override these. Users can be defined in `/etc/passwd` without a home directory or with a home directory that does not actually exist." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured_rationale", + "name": "rationale", + "prose": "Since the user is accountable for files stored in the user home directory, the user must be the owner of the directory. Group or world-writable user home directories may enable malicious users to steal or modify other users' data or to gain another user's system privileges. If the user's home directory does not exist or is unassigned, the user will be placed in \"/\" and will not be able to write any files or have local environment variables set." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured_obj", + "name": "assessment-objective", + "prose": "Ensure local interactive user home directories are configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured_obj" + }, + { + "rel": "script", + "href": "#88636fa6-40ac-50db-82be-f7154d7a414e" + } + ], + "prose": "Run the following script to Ensure:\n\n- local interactive user home directories exist\n\n- Ensure local interactive users own their home directories\n\n- Ensure local interactive user home directories are mode 750 or more restrictive\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output=\"\" l_output2=\"\" l_heout2=\"\" l_hoout2=\"\" l_haout2=\"\"\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n unset a_uarr && a_uarr=() # Clear and initialize array\n while read -r l_epu l_eph; do # Populate array with users and user home location\n a_uarr+=(\"$l_epu $l_eph\")\n done <<< \"$(awk -v pat=\"$l_valid_shells\" -F: '$(NF) ~ pat { print $1 \" \" $(NF-1) }' /etc/passwd)\"\n l_asize=\"${#a_uarr[@]}\" # Here if we want to look at number of users before proceeding\n [ \"$l_asize \" -gt \"10000\" ] && echo -e \"\\n ** INFO **\\n - \\\"$l_asize\\\" Local interactive users found on the system\\n - This may be a long running check\\n\"\n while read -r l_user l_home; do\n if [ -d \"$l_home\" ]; then\n l_mask='0027'\n l_max=\"$( printf '%o' $(( 0777 & ~$l_mask)) )\"\n while read -r l_own l_mode; do\n [ \"$l_user\" != \"$l_own\" ] && l_hoout2=\"$l_hoout2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" is owned by: \\\"$l_own\\\"\"\n if [ $(( $l_mode & $l_mask )) -gt 0 ]; then\n l_haout2=\"$l_haout2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" is mode: \\\"$l_mode\\\" should be mode: \\\"$l_max\\\" or more restrictive\"\n fi\n done <<< \"$(stat -Lc '%U %#a' \"$l_home\")\"\n else\n l_heout2=\"$l_heout2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" Doesn't exist\"\n fi\n done <<< \"$(printf '%s\\n' \"${a_uarr[@]}\")\"\n [ -z \"$l_heout2\" ] && l_output=\"$l_output\\n - home directories exist\" || l_output2=\"$l_output2$l_heout2\"\n [ -z \"$l_hoout2\" ] && l_output=\"$l_output\\n - own their home directory\" || l_output2=\"$l_output2$l_hoout2\"\n [ -z \"$l_haout2\" ] && l_output=\"$l_output\\n - home directories are mode: \\\"$l_max\\\" or more restrictive\" || l_output2=\"$l_output2$l_haout2\"\n [ -n \"$l_output\" ] && l_output=\" - All local interactive users:$l_output\"\n if [ -z \"$l_output2\" ]; then # If l_output2 is empty, we pass\n echo -e \"\\n- Audit Result:\\n ** PASS **\\n - * Correctly configured * :\\n$l_output\"\n else\n echo -e \"\\n- Audit Result:\\n ** FAIL **\\n - * Reasons for audit failure * :\\n$l_output2\"\n [ -n \"$l_output\" ] && echo -e \"\\n- * Correctly configured * :\\n$l_output\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "If a local interactive users' home directory is undefined and/or doesn't exist, follow local site policy and perform one of the following:\n\n- Lock the user account\n\n- Remove the user from the system\n\n- create a directory for the user. If undefined, edit `/etc/passwd` and add the absolute path to the directory to the last field of the user.\n\nRun the following script to:\n\n- Remove excessive permissions from local interactive users home directories\n\n- Update the home directory's owner\n\n```bash\n#!/usr/bin/env bash\n\n{\n l_output2=\"\"\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n unset a_uarr && a_uarr=() # Clear and initialize array\n while read -r l_epu l_eph; do # Populate array with users and user home location\n a_uarr+=(\"$l_epu $l_eph\")\n done <<< \"$(awk -v pat=\"$l_valid_shells\" -F: '$(NF) ~ pat { print $1 \" \" $(NF-1) }' /etc/passwd)\"\n l_asize=\"${#a_uarr[@]}\" # Here if we want to look at number of users before proceeding\n [ \"$l_asize \" -gt \"10000\" ] && echo -e \"\\n ** INFO **\\n - \\\"$l_asize\\\" Local interactive users found on the system\\n - This may be a long running process\\n\"\n while read -r l_user l_home; do\n if [ -d \"$l_home\" ]; then\n l_mask='0027'\n l_max=\"$( printf '%o' $(( 0777 & ~$l_mask)) )\"\n while read -r l_own l_mode; do\n if [ \"$l_user\" != \"$l_own\" ]; then\n l_output2=\"$l_output2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" is owned by: \\\"$l_own\\\"\\n - changing ownership to: \\\"$l_user\\\"\\n\"\n chown \"$l_user\" \"$l_home\"\n fi\n if [ $(( $l_mode & $l_mask )) -gt 0 ]; then\n l_output2=\"$l_output2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" is mode: \\\"$l_mode\\\" should be mode: \\\"$l_max\\\" or more restrictive\\n - removing excess permissions\\n\"\n chmod g-w,o-rwx \"$l_home\"\n fi\n done <<< \"$(stat -Lc '%U %#a' \"$l_home\")\"\n else\n l_output2=\"$l_output2\\n - User: \\\"$l_user\\\" Home \\\"$l_home\\\" Doesn't exist\\n - Please create a home in accordance with local site policy\"\n fi\n done <<< \"$(printf '%s\\n' \"${a_uarr[@]}\")\"\n if [ -z \"$l_output2\" ]; then # If l_output2 is empty, we pass\n echo -e \" - No modification needed to local interactive users home directories\"\n else\n echo -e \"\\n$l_output2\"\n fi\n}\n```" + } + ] + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured", + "title": "7.2.10 Ensure local interactive user dot files access is configured", + "links": [ + { + "rel": "reference", + "href": "http://cisecurity.org/20-cc/v8.0/control/3/subcontrol/3" + } + ], + "parts": [ + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured_smt", + "name": "statement", + "prose": "While the system administrator can establish secure permissions for users' \"dot\" files, the users can easily override these.\n\n- `.forward` file specifies an email address to forward the user's mail to.\n\n- `.rhost` file provides the \"remote authentication\" database for the rcp, rlogin, and rsh commands and the rcmd() function. These files bypass the standard password-based user authentication mechanism. They specify remote hosts and users that are considered trusted (i.e. are allowed to access the local system without supplying a password)\n\n- `.netrc` file contains data for logging into a remote host or passing authentication to an API.\n\n- `.bash_history` file keeps track of the user’s commands." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured_rationale", + "name": "rationale", + "prose": "User configuration files with excessive or incorrect access may enable malicious users to steal or modify other users' data or to gain another user's system privileges." + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured_obj", + "name": "assessment-objective", + "prose": "Ensure local interactive user dot files access is configured" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured_asm", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "language", + "value": "bash", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "evaluation", + "value": "stdout-regex", + "ns": "https://example.org/ns/oscal-automation" + }, + { + "name": "pass-condition", + "value": "\\*\\* PASS \\*\\*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured_obj" + }, + { + "rel": "script", + "href": "#e1fb82e1-f5dc-562b-8dd3-59a741de85da" + } + ], + "prose": "Run the following script to verify local interactive user dot files:\n\n- Don't include `.forward`, `.rhost`, or `.netrc` files\n\n- Are mode 0644 or more restrictive\n\n- Are owned by the local interactive user\n\n- Are group owned by the user's primary group\n\n- `.bash_history` is mode 0600 or more restrictive\n\n**Note:** If a `.netrc` file is required, and follows local site policy, it should be mode `0600` or more restrictive.\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=(); a_output3=()\n l_maxsize=\"1000\" # Maximum number of local interactive users before warning (Default 1,000)\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n a_user_and_home=() # Create array with local users and their home directories\n while read -r l_local_user l_local_user_home; do # Populate array with users and user home location\n [[ -n \"$l_local_user\" && -n \"$l_local_user_home\" ]] && a_user_and_home+=(\"$l_local_user:$l_local_user_home\")\n done <<< \"$(awk -v pat=\"$l_valid_shells\" -F: '$(NF) ~ pat { print $1 \" \" $(NF-1) }' /etc/passwd)\"\n l_asize=\"${#a_user_and_home[@]}\" # Here if we want to look at number of users before proceeding\n [ \"${#a_user_and_home[@]}\" -gt \"$l_maxsize\" ] && printf '%s\\n' \"\" \" ** INFO **\" \\\n \" - \\\"$l_asize\\\" Local interactive users found on the system\" \\\n \" - This may be a long running check\" \"\"\n file_access_chk()\n {\n a_access_out=()\n l_max=\"$( printf '%o' $(( 0777 & ~$l_mask)) )\"\n if [ $(( $l_mode & $l_mask )) -gt 0 ]; then\n a_access_out+=(\" - File: \\\"$l_hdfile\\\" is mode: \\\"$l_mode\\\" and should be mode: \\\"$l_max\\\" or more restrictive\")\n fi\n if [[ ! \"$l_owner\" =~ ($l_user) ]]; then\n a_access_out+=(\" - File: \\\"$l_hdfile\\\" owned by: \\\"$l_owner\\\" and should be owned by \\\"${l_user//|/ or }\\\"\")\n fi\n if [[ ! \"$l_gowner\" =~ ($l_group) ]]; then\n a_access_out+=(\" - File: \\\"$l_hdfile\\\" group owned by: \\\"$l_gowner\\\" and should be group owned by \\\"${l_group//|/ or }\\\"\")\n fi\n }\n while IFS=: read -r l_user l_home; do\n a_dot_file=(); a_netrc=(); a_netrc_warn=(); a_bhout=(); a_hdirout=()\n if [ -d \"$l_home\" ]; then\n l_group=\"$(id -gn \"$l_user\" | xargs)\";l_group=\"${l_group// /|}\"\n while IFS= read -r -d $'\\0' l_hdfile; do\n while read -r l_mode l_owner l_gowner; do\n case \"$(basename \"$l_hdfile\")\" in\n .forward | .rhost )\n a_dot_file+=(\" - File: \\\"$l_hdfile\\\" exists\") ;;\n .netrc )\n l_mask='0177'; file_access_chk\n if [ \"${#a_access_out[@]}\" -gt 0 ]; then\n a_netrc+=(\"${a_access_out[@]}\")\n else\n a_netrc_warn+=(\" - File: \\\"$l_hdfile\\\" exists\")\n fi ;;\n .bash_history )\n l_mask='0177'; file_access_chk\n [ \"${#a_access_out[@]}\" -gt 0 ] && a_bhout+=(\"${a_access_out[@]}\") ;;\n * )\n l_mask='0133'; file_access_chk\n [ \"${#a_access_out[@]}\" -gt 0 ] && a_hdirout+=(\"${a_access_out[@]}\") ;;\n esac\n done < <(stat -Lc '%#a %U %G' \"$l_hdfile\")\n done < <(find \"$l_home\" -xdev -type f -name '.*' -print0)\n fi\n if [[ \"${#a_dot_file[@]}\" -gt 0 || \"${#a_netrc[@]}\" -gt 0 || \"${#a_bhout[@]}\" -gt 0 || \"${#a_hdirout[@]}\" -gt 0 ]]; then\n a_output2+=(\" - User: \\\"$l_user\\\" Home Directory: \\\"$l_home\\\"\" \"${a_dot_file[@]}\" \"${a_netrc[@]}\" \"${a_bhout[@]}\" \"${a_hdirout[@]}\")\n fi\n [ \"${#a_netrc_warn[@]}\" -gt 0 ] && a_output3+=(\" - User: \\\"$l_user\\\" Home Directory: \\\"$l_home\\\"\" \"${a_netrc_warn[@]}\")\n done <<< \"$(printf '%s\\n' \"${a_user_and_home[@]}\")\"\n if [ \"${#a_output2[@]}\" -le 0 ]; then # If l_output2 is empty, we pass\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \" ** WARNING **\" \"${a_output3[@]}\"\n printf '%s\\n' \"- Audit Result:\" \" ** PASS **\"\n else\n printf '%s\\n' \"- Audit Result:\" \" ** FAIL **\" \" - * Reasons for audit failure * :\" \"${a_output2[@]}\" \"\"\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \" ** WARNING **\" \"${a_output3[@]}\"\n fi\n}\n```" + }, + { + "id": "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured_rem", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user dot file permissions and determine the action to be taken in accordance with site policy.\n\nThe following script will:\n\n- remove excessive permissions on `dot` files within interactive users' home directories\n\n- change ownership of `dot` files within interactive users' home directories to the user\n\n- change group ownership of `dot` files within interactive users' home directories to the user's primary group\n\n- list `.forward` and `.rhost` files to be investigated and manually deleted\n\n```bash\n#!/usr/bin/env bash\n\n{\n a_output2=(); a_output3=()\n l_maxsize=\"1000\" # Maximum number of local interactive users before warning (Default 1,000)\n l_valid_shells=\"^($( awk -F\\/ '$NF != \"nologin\" {print}' /etc/shells | sed -rn '/^\\//{s,/,\\\\\\\\/,g;p}' | paste -s -d '|' - ))$\"\n a_user_and_home=() # Create array with local users and their home directories\n while read -r l_local_user l_local_user_home; do # Populate array with users and user home location\n [[ -n \"$l_local_user\" && -n \"$l_local_user_home\" ]] && a_user_and_home+=(\"$l_local_user:$l_local_user_home\")\n done <<< \"$(awk -v pat=\"$l_valid_shells\" -F: '$(NF) ~ pat { print $1 \" \" $(NF-1) }' /etc/passwd)\"\n l_asize=\"${#a_user_and_home[@]}\" # Here if we want to look at number of users before proceeding\n [ \"${#a_user_and_home[@]}\" -gt \"$l_maxsize\" ] && printf '%s\\n' \"\" \" ** INFO **\" \\\n \" - \\\"$l_asize\\\" Local interactive users found on the system\" \\\n \" - This may be a long running check\" \"\"\n file_access_fix()\n {\n a_access_out=()\n l_max=\"$( printf '%o' $(( 0777 & ~$l_mask)) )\"\n if [ $(( $l_mode & $l_mask )) -gt 0 ]; then\n printf '%s\\n' \"\" \" - File: \\\"$l_hdfile\\\" is mode: \\\"$l_mode\\\" and should be mode: \\\"$l_max\\\" or more restrictive\" \\\n \" Updating file: \\\"$l_hdfile\\\" to be mode: \\\"$l_max\\\" or more restrictive\"\n chmod \"$l_change\" \"$l_hdfile\"\n fi\n if [[ ! \"$l_owner\" =~ ($l_user) ]]; then\n printf '%s\\n' \"\" \" - File: \\\"$l_hdfile\\\" owned by: \\\"$l_owner\\\" and should be owned by \\\"${l_user//|/ or }\\\"\" \\\n \" Updating file: \\\"$l_hdfile\\\" to be owned by \\\"${l_user//|/ or }\\\"\"\n chown \"$l_user\" \"$l_hdfile\"\n fi\n if [[ ! \"$l_gowner\" =~ ($l_group) ]]; then\n printf '%s\\n' \"\" \" - File: \\\"$l_hdfile\\\" group owned by: \\\"$l_gowner\\\" and should be group owned by \\\"${l_group//|/ or }\\\"\" \\\n \" Updating file: \\\"$l_hdfile\\\" to be group owned by \\\"${l_group//|/ or }\\\"\"\n chgrp \"$l_group\" \"$l_hdfile\"\n fi\n }\n while IFS=: read -r l_user l_home; do\n a_dot_file=(); a_netrc=(); a_netrc_warn=(); a_bhout=(); a_hdirout=()\n if [ -d \"$l_home\" ]; then\n l_group=\"$(id -gn \"$l_user\" | xargs)\";l_group=\"${l_group// /|}\"\n while IFS= read -r -d $'\\0' l_hdfile; do\n while read -r l_mode l_owner l_gowner; do\n case \"$(basename \"$l_hdfile\")\" in\n .forward | .rhost )\n a_dot_file+=(\" - File: \\\"$l_hdfile\\\" exists\" \" Please review and manually delete this file\") ;;\n .netrc )\n l_mask='0177'; l_change=\"u-x,go-rwx\"; file_access_fix\n a_netrc_warn+=(\" - File: \\\"$l_hdfile\\\" exists\") ;;\n .bash_history )\n l_mask='0177'; l_change=\"u-x,go-rwx\"; file_access_fix ;;\n * )\n l_mask='0133'; l_change=\"u-x,go-wx\"; file_access_fix ;;\n esac\n done < <(stat -Lc '%#a %U %G' \"$l_hdfile\")\n done < <(find \"$l_home\" -xdev -type f -name '.*' -print0)\n fi\n [ \"${#a_dot_file[@]}\" -gt 0 ] && a_output2+=(\" - User: \\\"$l_user\\\" Home Directory: \\\"$l_home\\\"\" \"${a_dot_file[@]}\")\n [ \"${#a_netrc_warn[@]}\" -gt 0 ] && a_output3+=(\" - User: \\\"$l_user\\\" Home Directory: \\\"$l_home\\\"\" \"${a_netrc_warn[@]}\")\n done <<< \"$(printf '%s\\n' \"${a_user_and_home[@]}\")\"\n [ \"${#a_output3[@]}\" -gt 0 ] && printf '%s\\n' \"\" \" ** WARNING **\" \"${a_output3[@]}\" \"\"\n [ \"${#a_output2[@]}\" -gt 0 ] && printf '%s\\n' \"\" \"${a_output2[@]}\"\n}\n```" + } + ] + } + ] + } + ] + } + ], + "back-matter": { + "resources": [ + { + "uuid": "c54b4287-f421-5f90-a4d1-4b94f3d30a9a", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark (CIS-CAT benchmark file)", + "description": "The benchmark file every control, part and value in this catalog was taken from. Held on the basis the repository's source inventory records.", + "rlinks": [ + { + "href": "../../../sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.json", + "media-type": "application/json", + "hashes": [ + { + "algorithm": "SHA-256", + "value": "1a90fccb4442decd119382233ff8986caaaeede83dcf3c5ab22a87c747ab0c81" + } + ] + } + ] + }, + { + "uuid": "93b2e475-6325-556c-b6bd-49e0c2bd2b3d", + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark (published document)", + "rlinks": [ + { + "href": "../../../sources/cis/CIS_Ubuntu_Linux_24.04_LTS_Benchmark_v1.0.0.pdf", + "media-type": "application/pdf", + "hashes": [ + { + "algorithm": "SHA-256", + "value": "8ebe23d21c23e383c81620ad04655e3b1d8fdf0b6eb9ddfdb7a97d0a5b5e7ef1" + } + ] + } + ] + }, + { + "uuid": "80cb14a1-10b1-5f05-896a-d9de8c0264f6", + "title": "deb_no_iptables.sh", + "description": "Script Check Engine script, named by the check expression of 9 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "deb_no_iptables.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "f3cc5685-0c0f-5c1d-956a-62c6b9201ab2", + "title": "deb_no_nftables.sh", + "description": "Script Check Engine script, named by the check expression of 8 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "deb_no_nftables.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "ddfb5558-71c5-5ed4-9f77-3d23499e5934", + "title": "ip6tables_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "ip6tables_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "0f5a5341-15bb-5e72-afb4-f5f30d078f90", + "title": "iptables_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "iptables_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "5cf2a45e-b702-50b3-bac8-cd40feac3a2f", + "title": "iptables_input.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "iptables_input.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "a547fb1c-fae3-5b3a-9a83-e8cfddd2799f", + "title": "iptables_output.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "iptables_output.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "3017a433-7b16-5895-8da4-830e2c0e9700", + "title": "nft_loopback.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nft_loopback.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "a43ed1b1-a76a-5e9d-ae1f-22b31f714fc0", + "title": "nft_ruleset.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nft_ruleset.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "961d523c-1913-5b74-8444-fd2ecd8a1a27", + "title": "nft_ruleset_drop.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nft_ruleset_drop.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "4f790ecf-e162-54ca-8796-5676a1223901", + "title": "nft_tables.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nft_tables.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "90495ec8-deec-51cc-866a-f5f99be62940", + "title": "nix_account_no_login_shell_locked_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_account_no_login_shell_locked_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "b82274ce-0bb5-507b-b87e-750b2ca253ef", + "title": "nix_apparmor_profiles_chk.sh", + "description": "Script Check Engine script, named by the check expression of 2 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_apparmor_profiles_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "41d0c09d-38c6-53a2-bdf1-2e9034272129", + "title": "nix_auditd_log_files_group_owner_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_auditd_log_files_group_owner_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "7b50ef7c-abce-5ed1-9c53-a35eb45d7553", + "title": "nix_auditd_log_files_owner_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_auditd_log_files_owner_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "57daba1f-ec1a-58c6-81ad-3d406fbd0e08", + "title": "nix_auditd_logfile_directory_mode_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_auditd_logfile_directory_mode_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "3d302179-a881-5040-8157-4bbffde66318", + "title": "nix_auditd_logfile_mode_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_auditd_logfile_mode_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "0b888c8c-32bf-512b-8421-fa32e83e3eb0", + "title": "nix_auditd_privileged_commands_rule_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_auditd_privileged_commands_rule_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "c20ab9e6-5e79-56ec-af8d-020f2984fab5", + "title": "nix_auditd_rule_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 19 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_auditd_rule_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "8cb0ff77-5776-5be3-b783-b088b579b951", + "title": "nix_chrony_timeserver_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_chrony_timeserver_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "cf2a8e9a-3c5c-53bf-ba7d-7c3228bec943", + "title": "nix_crontab_access_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_crontab_access_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "698d979e-fb96-5253-8652-e5149d57c49b", + "title": "nix_deb_audit_tool_aide_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_deb_audit_tool_aide_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "59138dc1-7e43-501a-ad77-9ed031fe40aa", + "title": "nix_deb_single_firewall_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_deb_single_firewall_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "2686ef59-353f-5c13-9942-df354bf7ec50", + "title": "nix_deb_timesync_daemon_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_deb_timesync_daemon_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "c9ff0d40-4cd4-58a0-8ef9-bfbaaa07b52d", + "title": "nix_duplicate_gid.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_duplicate_gid.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "2eeb230a-482b-5b9c-a554-44ec61456b37", + "title": "nix_duplicate_groupname.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_duplicate_groupname.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "86fad0e7-86b5-57a5-893d-8bb824a3e371", + "title": "nix_duplicate_uid.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_duplicate_uid.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "338088f7-4f5b-55b8-b668-0eb40c86ff37", + "title": "nix_duplicate_username.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_duplicate_username.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "d6aa2e15-2064-5c18-b653-a8a03f13d1d8", + "title": "nix_fed34_ensure_only_one_logging_system_in_use.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_fed34_ensure_only_one_logging_system_in_use.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "c1a75251-7d45-5b0b-83b5-714fef3c3f89", + "title": "nix_file_collection_group_owner_chk.sh", + "description": "Script Check Engine script, named by the check expression of 2 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_file_collection_group_owner_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "b33b3e27-0307-555d-85f8-633bc01ca592", + "title": "nix_file_collection_mode_chk.sh", + "description": "Script Check Engine script, named by the check expression of 2 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_file_collection_mode_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "003b6f15-7428-5b5b-96c0-6a7b522244f9", + "title": "nix_file_collection_owner_chk.sh", + "description": "Script Check Engine script, named by the check expression of 2 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_file_collection_owner_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "e0939ee2-6da4-5eb2-9964-47e83340beff", + "title": "nix_gdm_automount_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_gdm_automount_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "ae5daade-80d9-5815-ad3d-1392a03d779d", + "title": "nix_gdm_autorun_never_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_gdm_autorun_never_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "10bf0fcd-7392-5205-a09f-65e2d016d1d0", + "title": "nix_gdm_autorun_never_override_chk3.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_gdm_autorun_never_override_chk3.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "1eaf90f5-94bd-526f-b160-5c0ba9494520", + "title": "nix_gdm_disable_user_list_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_gdm_disable_user_list_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "1175b087-5c60-5b14-8344-6f57ee739247", + "title": "nix_gdm_disabling_automatic_mounting_removable_media_notoverride_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_gdm_disabling_automatic_mounting_removable_media_notoverride_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "d08e5b09-61d3-5699-a968-17aecd7a5c7b", + "title": "nix_gdm_login_banner_configured_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_gdm_login_banner_configured_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "b0b32250-cdfe-514d-8426-62bcd570ee9f", + "title": "nix_gdm_screen_lock_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_gdm_screen_lock_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "b8bba142-3ae6-54d4-891f-19905e3768fc", + "title": "nix_gdm_screen_lock_override_chk_v3.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_gdm_screen_lock_override_chk_v3.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "bf7369ee-da68-5c46-bf41-d90974408be7", + "title": "nix_group_chk.sh", + "description": "Script Check Engine script, named by the check expression of 23 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_group_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "0577d57c-79e0-5876-9d54-1307cfeee2a4", + "title": "nix_group_gid_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_group_gid_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "997edba2-e4f3-536a-aa35-6cf12f432c61", + "title": "nix_group_in_passwd_not_in_group_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_group_in_passwd_not_in_group_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "98739ca0-ad70-55aa-8506-980b20cec38c", + "title": "nix_grub_option_exist_chk.sh", + "description": "Script Check Engine script, named by the check expression of 2 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_grub_option_exist_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "2aa5c2ae-c45b-5110-a8e4-5ff5055d0b44", + "title": "nix_ip6tables_loopback_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_ip6tables_loopback_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "dd79f8f2-4ddb-5def-a3b5-ee16e8fbd6f5", + "title": "nix_ip6tables_openports_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_ip6tables_openports_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "5a54c70b-4dab-5cb3-9ab7-e0ffad1a76bc", + "title": "nix_iptables_openports_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_iptables_openports_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "a1587053-8ee8-519f-a5fa-90a621907ce1", + "title": "nix_ipv6_disabled_chk.sh", + "description": "Script Check Engine script, named by the check expression of 5 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_ipv6_disabled_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "2e8cc4e6-e832-5237-8072-747bc9b921b0", + "title": "nix_kernel_parameter_chk_v3.sh", + "description": "Script Check Engine script, named by the check expression of 14 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_kernel_parameter_chk_v3.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "6e3721be-ede6-5c6c-8816-981a95705b19", + "title": "nix_logfile_access_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_logfile_access_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "8562a87f-938a-5f79-8e44-1d3a4068684e", + "title": "nix_mode_chk.sh", + "description": "Script Check Engine script, named by the check expression of 23 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_mode_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "57406427-e772-5765-9a71-89d9da9cd0b3", + "title": "nix_module_chk_v3.sh", + "description": "Script Check Engine script, named by the check expression of 13 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_module_chk_v3.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "42b4ed84-8173-56f8-a824-927d22ea68c0", + "title": "nix_mount_point_exists_chk.sh", + "description": "Script Check Engine script, named by the check expression of 7 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_mount_point_exists_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "504ee9c5-f07f-5edd-bb9a-22368a870987", + "title": "nix_mount_point_option_chk.sh", + "description": "Script Check Engine script, named by the check expression of 19 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_mount_point_option_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "f3b68e83-292c-5797-8dd6-c9cbb3509fbe", + "title": "nix_mta_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_mta_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "93db8f79-a8a0-5916-a892-1009381d7426", + "title": "nix_owner_chk.sh", + "description": "Script Check Engine script, named by the check expression of 23 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_owner_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "d6ab71b8-9471-5e6b-a844-7f057de465b4", + "title": "nix_password_change_past.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_password_change_past.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "0af82d1a-78bc-5eaf-b3d8-fec15d1acdd1", + "title": "nix_pwquality_complexity_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_pwquality_complexity_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "2a3327a1-9dec-5d87-b73d-266fdce4eb40", + "title": "nix_root_account_access_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_root_account_access_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "55b1a5f2-02bd-5547-b88c-25d7f515aeaa", + "title": "nix_root_path_integrity_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_root_path_integrity_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "a264fe5d-1388-5bc2-b887-44c0d6a5304f", + "title": "nix_rsyslog_filecreatemode_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_rsyslog_filecreatemode_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "6434d985-ed98-5289-a298-40e5bc3908c5", + "title": "nix_rsyslog_receive_logs_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_rsyslog_receive_logs_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "493dae7a-ddc4-5ca6-95da-e85f143fbb0f", + "title": "nix_service_owned_by_user_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_service_owned_by_user_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "7aeb383b-25b1-58f1-b622-fc0695d750f4", + "title": "nix_shadow_field_chk.sh", + "description": "Script Check Engine script, named by the check expression of 4 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_shadow_field_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "68883ac0-8ede-5f78-b91a-1ae0f321d81f", + "title": "nix_shadow_password_field_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_shadow_password_field_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "1dc0ec4f-7928-5d29-8db7-362548b598e4", + "title": "nix_ssh_private_key_perm_chk_v4.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_ssh_private_key_perm_chk_v4.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "57a1abd0-77da-5198-8396-c7cc0177fd96", + "title": "nix_ssh_public_key_access_chk_v4.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_ssh_public_key_access_chk_v4.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "8a22716d-41ec-59bb-92f7-dc0ea7be08c9", + "title": "nix_sshd_config_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 19 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_sshd_config_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "c20cb629-62df-5989-a424-ccc908ff76c9", + "title": "nix_sshd_config_match_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 11 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_sshd_config_match_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "a2f74d47-2fe4-56c2-8476-6f1c77202f65", + "title": "nix_system_account_no_login_shell_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_system_account_no_login_shell_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "b3f0988f-8e03-56a7-94fe-2a8b0c83dd45", + "title": "nix_systemd_parameter_chk_v3.sh", + "description": "Script Check Engine script, named by the check expression of 5 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_systemd_parameter_chk_v3.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "c462a465-0f39-52c6-86d2-23251f051b85", + "title": "nix_systemd_parameter_not_match_chk.sh", + "description": "Script Check Engine script, named by the check expression of 2 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_systemd_parameter_not_match_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "11ed45fb-b2a8-572b-97d5-a5ce474bd8b6", + "title": "nix_umask_chk_v2.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_umask_chk_v2.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "8831a090-5cfc-56cc-a3cd-259d13d9d90d", + "title": "nix_unowned_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_unowned_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "e1fb82e1-f5dc-562b-8dd3-59a741de85da", + "title": "nix_user_dot_files_access_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_user_dot_files_access_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "78a10f33-f6dd-54e5-9e39-fe063dae6252", + "title": "nix_user_gid_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_user_gid_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "88636fa6-40ac-50db-82be-f7154d7a414e", + "title": "nix_user_home_directory_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_user_home_directory_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "c9eefbb7-8bd3-56c5-809b-2cfaf19f2d91", + "title": "nix_user_shadow_primary_group_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_user_shadow_primary_group_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "ad96b673-9ce1-5232-9721-d4e785bb6854", + "title": "nix_user_uid_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_user_uid_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "1f5cef69-4a5c-5158-b8a9-1cb2e1b4b1e6", + "title": "nix_wireless_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_wireless_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "fb1d60f7-025e-5da4-ab52-8089bb071f6f", + "title": "nix_world_writable_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_world_writable_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "d83d68a0-3dc5-57a7-a576-b8e59aa271ab", + "title": "nix_xdcmp_enabled_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "nix_xdcmp_enabled_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "cbb382ff-7f3d-5d6d-baeb-e04e2e9a3d0f", + "title": "no_ufw.sh", + "description": "Script Check Engine script, named by the check expression of 6 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "no_ufw.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "248436ec-a0a3-52db-b28c-f5a6027b1ea1", + "title": "tmout_chk.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "tmout_chk.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "ac7bc4ba-ad76-51ad-a186-141ae169ea70", + "title": "ufw_disabled.sh", + "description": "Script Check Engine script, named by the check expression of 2 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "ufw_disabled.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "3cabd680-cf22-51ac-8f50-287b791fba0e", + "title": "ufw_enabled.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "ufw_enabled.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "231cebf0-c7e6-560c-8766-202efb1ad849", + "title": "ufw_open_ports.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "ufw_open_ports.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "d5717121-c357-535f-9766-d54b266aed20", + "title": "ufw_status.sh", + "description": "Script Check Engine script, named by the check expression of 2 recommendations. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "ufw_status.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "62cbc0bc-3992-5e32-9def-f6b4a58c417c", + "title": "wbissue.net.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "wbissue.net.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "3535fabd-c67e-59e2-a8a6-24f9ad1ff515", + "title": "wbissue.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "wbissue.sh", + "media-type": "application/x-sh" + } + ] + }, + { + "uuid": "81f9478a-4a96-5c9e-89a8-b7c88600513b", + "title": "wbmotd.sh", + "description": "Script Check Engine script, named by the check expression of 1 recommendation. It ships with CIS-CAT and is not held here, so this resource carries its name and no hash.", + "rlinks": [ + { + "href": "wbmotd.sh", + "media-type": "application/x-sh" + } + ] + } + ] + } + } +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-server-profile.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-server-profile.json new file mode 100644 index 0000000..2800c12 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-server-profile.json @@ -0,0 +1,278 @@ +{ + "profile": { + "uuid": "257cb52d-72d3-54e2-b2c5-40a0caffae39", + "metadata": { + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 1 - Server", + "published": "2026-09-09T00:00:00Z", + "last-modified": "2026-09-09T00:00:00Z", + "version": "1.0.0", + "oscal-version": "1.2.1", + "remarks": "The benchmark's own profile of that name, as the selection of controls it makes. Items in this profile intend to:\n\n- be practical and prudent;\n\n- provide a clear security benefit; and\n\n- not inhibit the utility of the technology beyond acceptable means.\n\nThis profile is intended for servers." + }, + "imports": [ + { + "href": "cis-ubuntu-24-04-lts-benchmark-catalog.json", + "include-controls": [ + { + "with-ids": [ + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode", + "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set", + "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted", + "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted", + "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle", + "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled", + "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode", + "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface", + "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver", + "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users", + "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users", + "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified", + "xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored", + "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored", + "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged", + "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw", + "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables", + "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables", + "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists", + "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist", + "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty", + "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists", + "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally", + "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly", + "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked", + "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed", + "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords", + "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty", + "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup", + "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty", + "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured" + ] + } + ] + } + ], + "merge": { + "as-is": true + } + } +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-workstation-profile.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-workstation-profile.json new file mode 100644 index 0000000..bab8631 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-1-workstation-profile.json @@ -0,0 +1,272 @@ +{ + "profile": { + "uuid": "756b93ff-765d-5413-9cd5-f3ea7d2e5280", + "metadata": { + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 1 - Workstation", + "published": "2026-09-09T00:00:00Z", + "last-modified": "2026-09-09T00:00:00Z", + "version": "1.0.0", + "oscal-version": "1.2.1", + "remarks": "The benchmark's own profile of that name, as the selection of controls it makes. Items in this profile intend to:\n\n- be practical and prudent;\n\n- provide a clear security benefit; and\n\n- not inhibit the utility of the technology beyond acceptable means.\n\nThis profile is intended for workstations." + }, + "imports": [ + { + "href": "cis-ubuntu-24-04-lts-benchmark-catalog.json", + "include-controls": [ + { + "with-ids": [ + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode", + "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set", + "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted", + "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted", + "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle", + "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled", + "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode", + "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface", + "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver", + "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users", + "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users", + "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified", + "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored", + "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored", + "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged", + "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw", + "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables", + "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables", + "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists", + "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist", + "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty", + "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists", + "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally", + "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly", + "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked", + "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed", + "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords", + "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty", + "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup", + "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty", + "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured" + ] + } + ] + } + ], + "merge": { + "as-is": true + } + } +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-server-profile.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-server-profile.json new file mode 100644 index 0000000..34e8db9 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-server-profile.json @@ -0,0 +1,339 @@ +{ + "profile": { + "uuid": "515ef1b4-e5d7-5c90-9d3d-096b318d0339", + "metadata": { + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 2 - Server", + "published": "2026-09-09T00:00:00Z", + "last-modified": "2026-09-09T00:00:00Z", + "version": "1.0.0", + "oscal-version": "1.2.1", + "remarks": "The benchmark's own profile of that name, as the selection of controls it makes. This profile extends the \"Level 1 - Server\" profile. Items in this profile exhibit one or more of the following characteristics:\n\n- are intended for environments or use cases where security is paramount.\n\n- acts as defense in depth measure.\n\n- may negatively inhibit the utility or performance of the technology.\n\nThis profile is intended for servers." + }, + "imports": [ + { + "href": "cis-ubuntu-24-04-lts-benchmark-catalog.json", + "include-controls": [ + { + "with-ids": [ + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing", + "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set", + "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted", + "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted", + "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.7.1_Ensure_GDM_is_removed", + "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle", + "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled", + "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.20_Ensure_X_window_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode", + "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface", + "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver", + "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users", + "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users", + "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified", + "xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored", + "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored", + "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged", + "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw", + "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables", + "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables", + "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists", + "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist", + "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty", + "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists", + "xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation", + "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally", + "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly", + "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.3_Ensure_password_failed_attempts_lockout_includes_root_account", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient", + "xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted", + "xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full", + "xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked", + "xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools", + "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed", + "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords", + "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty", + "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup", + "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty", + "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured" + ] + } + ] + } + ], + "merge": { + "as-is": true + } + } +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-workstation-profile.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-workstation-profile.json new file mode 100644 index 0000000..569e373 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-level-2-workstation-profile.json @@ -0,0 +1,336 @@ +{ + "profile": { + "uuid": "f050d8b7-d0f8-5fd7-9b6c-67f05dbe1e68", + "metadata": { + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0, Level 2 - Workstation", + "published": "2026-09-09T00:00:00Z", + "last-modified": "2026-09-09T00:00:00Z", + "version": "1.0.0", + "oscal-version": "1.2.1", + "remarks": "The benchmark's own profile of that name, as the selection of controls it makes. This profile extends the \"Level 1 - Workstation\" profile. Items in this profile exhibit one or more of the following characteristics:\n\n- are intended for environments or use cases where security is paramount.\n\n- acts as defense in depth measure.\n\n- may negatively inhibit the utility or performance of the technology.\n\nThis profile is intended for workstations." + }, + "imports": [ + { + "href": "cis-ubuntu-24-04-lts-benchmark-catalog.json", + "include-controls": [ + { + "with-ids": [ + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.1.10_Ensure_unused_filesystems_kernel_modules_are_not_available", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition", + "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode", + "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing", + "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set", + "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted", + "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted", + "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_1.5.5_Ensure_Automatic_Error_Reporting_is_not_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly", + "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.4_Ensure_GDM_screen_locks_when_the_user_is_idle", + "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden", + "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled", + "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode", + "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface", + "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed", + "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver", + "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony", + "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users", + "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users", + "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified", + "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available", + "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored", + "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored", + "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged", + "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted", + "xccdf_org.cisecurity.benchmarks_rule_4.1.1_Ensure_a_single_firewall_configuration_utility_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw", + "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables", + "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables", + "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists", + "xccdf_org.cisecurity.benchmarks_rule_4.3.5_Ensure_nftables_base_chains_exist", + "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables", + "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports", + "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty", + "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists", + "xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation", + "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally", + "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly", + "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.1_Ensure_latest_version_of_pam_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.2_Ensure_libpam-modules_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.1.3_Ensure_libpam-pwquality_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.2_Ensure_pam_faillock_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.3_Ensure_pam_pwquality_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.2.4_Ensure_pam_pwhistory_module_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.1_Ensure_password_failed_attempts_lockout_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.2_Ensure_password_unlock_time_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.1.3_Ensure_password_failed_attempts_lockout_includes_root_account", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.1_Ensure_pam_unix_does_not_include_nullok", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.2_Ensure_pam_unix_does_not_include_remember", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm", + "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_password_days_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.5_Ensure_inactive_password_lock_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.1.6_Ensure_all_users_last_password_change_date_is_in_the_past", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.4_Ensure_root_account_access_is_controlled", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell", + "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.2_Ensure_default_user_shell_timeout_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.1.4_Ensure_only_one_logging_system_is_in_use", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client", + "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active", + "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled", + "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient", + "xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted", + "xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full", + "xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.3_Ensure_events_that_modify_the_sudo_log_file_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable", + "xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured", + "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed", + "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked", + "xccdf_org.cisecurity.benchmarks_rule_6.3.3_Ensure_cryptographic_mechanisms_are_used_to_protect_the_integrity_of_audit_tools", + "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured", + "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed", + "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords", + "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty", + "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup", + "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty", + "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist", + "xccdf_org.cisecurity.benchmarks_rule_7.2.9_Ensure_local_interactive_user_home_directories_are_configured", + "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured" + ] + } + ] + } + ], + "merge": { + "as-is": true + } + } +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json new file mode 100644 index 0000000..ae5a479 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/cis-ubuntu-24-04-lts-to-nist-sp-800-53-rev5-mapping.json @@ -0,0 +1,5934 @@ +{ + "mapping-collection": { + "uuid": "81247db0-821d-53a0-9620-8a142f69944f", + "metadata": { + "title": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0 mapped to NIST SP 800-53 Revision 5", + "published": "2026-09-09T00:00:00Z", + "last-modified": "2026-09-09T00:00:00Z", + "version": "1.0.0", + "oscal-version": "1.2.1", + "remarks": "Generated by tools/executable_first_corpus.py from the SP 800-53 references the benchmark carries in its own identifiers. The references are CIS's; the mapping model around them is the generator's." + }, + "provenance": { + "method": "hybrid", + "matching-rationale": "semantic", + "status": "draft", + "mapping-description": "Each map carries the SP 800-53 Revision 5 controls the benchmark names in the recommendation's own identifiers. CIS made the mapping; the generator transcribed it into the mapping model, which is why the method is hybrid. Every recommendation is narrower than the control it names, so every map is a subset relationship." + }, + "mappings": [ + { + "uuid": "59d857a2-4c37-53cf-bcfc-89a8a0cfa3a9", + "source-resource": { + "type": "catalog", + "href": "cis-ubuntu-24-04-lts-benchmark-catalog.json" + }, + "target-resource": { + "type": "catalog", + "href": "https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json" + }, + "maps": [ + { + "uuid": "15411d58-ef50-5bd9-9ac0-f4d53602cc2c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_cramfs_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "34ee70db-8498-5123-a375-61a157cf68a7", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_freevxfs_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "303be919-7da1-5004-8e0b-f49825b207e6", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_hfs_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "bd6ce2fa-1a54-5583-8466-05da35c87c2c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_hfsplus_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "abab4a27-871c-5709-b6a4-7d2aa9391fef", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_jffs2_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "c6053993-67a0-59e1-af09-706ba1374867", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_overlayfs_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "6099dacb-8169-5ede-a9b4-d4de35b8793e", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_squashfs_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "065410c0-86f9-5d4a-b8c8-1122de60ece0", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_udf_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "0ae1d25b-0fb4-5840-a418-19ac35bec88c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.1.9_Ensure_usb-storage_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-3" + } + ] + }, + { + "uuid": "9f0c47e9-2b00-5c4e-ab4f-ef010369abc5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.1_Ensure_tmp_is_a_separate_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "21fd8690-e25d-5862-bbd0-facdaaeef089", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.2_Ensure_nodev_option_set_on_tmp_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "7818fa81-303a-581c-8373-34bef8640223", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.3_Ensure_nosuid_option_set_on_tmp_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "6dfa94c9-2be7-5dd8-8d88-9c4861f9302b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.1.4_Ensure_noexec_option_set_on_tmp_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "6d8513f9-9790-519a-937e-7feb2833bc6a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.1_Ensure_devshm_is_a_separate_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "e431f7ef-5a6e-5cd3-9ec3-0361d935a088", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.2_Ensure_nodev_option_set_on_devshm_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "c1eae5e6-1822-519e-acfc-d6a433bcb883", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.3_Ensure_nosuid_option_set_on_devshm_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "ef2d2888-cb76-51a8-8a70-4f12267c2f5d", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.2.4_Ensure_noexec_option_set_on_devshm_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "338f0c88-e970-5a40-8561-b30b2ce189c9", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.1_Ensure_separate_partition_exists_for_home" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "6d1ab107-73c6-519c-921e-f07ad4c96acb", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.2_Ensure_nodev_option_set_on_home_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "adf8425e-57a0-5049-91ae-305bde137b58", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.3.3_Ensure_nosuid_option_set_on_home_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "4a2aa1f9-422d-5e83-8e88-0140dc3d123f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.1_Ensure_separate_partition_exists_for_var" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "a74f28ca-5079-52b6-bb4f-6ddd95d4afc6", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.2_Ensure_nodev_option_set_on_var_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "725ac888-6e6c-5bc4-80ea-f2382780655d", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.4.3_Ensure_nosuid_option_set_on_var_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "cba83cda-7db2-5d59-a412-dabce552107f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.1_Ensure_separate_partition_exists_for_vartmp" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "edce820d-d6ea-59eb-991a-347b3ca06c9f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.2_Ensure_nodev_option_set_on_vartmp_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "8baa8b36-6c5a-56c5-ae70-d0d03e6caf9a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.3_Ensure_nosuid_option_set_on_vartmp_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "2d1d1007-51e7-5905-9564-d2a3ea660eb4", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.5.4_Ensure_noexec_option_set_on_vartmp_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "2ec6ff66-590d-54e7-a44a-c3acb3fe13b7", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.1_Ensure_separate_partition_exists_for_varlog" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "e556c2ae-2f7b-518e-8757-a33d41149300", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.2_Ensure_nodev_option_set_on_varlog_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "9c9723e6-1e05-5854-b305-cb1f49bbc42f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.3_Ensure_nosuid_option_set_on_varlog_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "16fec273-30ff-575a-80e9-7c7146bb0734", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.6.4_Ensure_noexec_option_set_on_varlog_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "c62b7603-fe92-534d-80af-893a42d9cebf", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.1_Ensure_separate_partition_exists_for_varlogaudit" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "ce54d75b-98da-55c8-9778-f21828e7b7af", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.2_Ensure_nodev_option_set_on_varlogaudit_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "a36bff1d-91e1-5ed9-affd-2ede71a5492a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.3_Ensure_nosuid_option_set_on_varlogaudit_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "bc61248c-ac0e-5006-8ecd-8944ff9d7988", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.1.2.7.4_Ensure_noexec_option_set_on_varlogaudit_partition" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "4a41d06e-a829-52a5-81ef-f381a44d7d23", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.1_Ensure_GPG_keys_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-2" + } + ] + }, + { + "uuid": "47c2e219-c53f-5827-a9ea-4d67758a582f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.2.1.2_Ensure_package_manager_repositories_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-2" + } + ] + }, + { + "uuid": "c26cc453-9229-5bd9-89ae-82ccc5374c6a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.2.2.1_Ensure_updates_patches_and_additional_security_software_are_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-2" + } + ] + }, + { + "uuid": "d9ca082c-0787-562f-86b7-720999e859dc", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.1_Ensure_AppArmor_is_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + } + ] + }, + { + "uuid": "39cfced6-1f95-5b09-a885-363a9e3c466f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.2_Ensure_AppArmor_is_enabled_in_the_bootloader_configuration" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + } + ] + }, + { + "uuid": "4a20c9a4-7f85-5057-a944-20342934352a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.3_Ensure_all_AppArmor_Profiles_are_in_enforce_or_complain_mode" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + } + ] + }, + { + "uuid": "56a91bd0-95f6-59ff-a268-b4f3e346128d", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.3.1.4_Ensure_all_AppArmor_Profiles_are_enforcing" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + } + ] + }, + { + "uuid": "a12c8b70-7dae-5a04-9401-747737d95f64", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_bootloader_password_is_set" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + } + ] + }, + { + "uuid": "612a47f0-52e4-5f84-ab03-f9c173bd4b90", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_access_to_bootloader_config_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + } + ] + }, + { + "uuid": "cc114c69-5c65-5c07-8ab0-2f8a8023fbcc", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_address_space_layout_randomization_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "f5208b18-a7d9-5bf6-b417-a28ebc37a838", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_ptrace_scope_is_restricted" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "61cf6a90-e8c0-5f15-9889-f1e4edb9e696", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_core_dumps_are_restricted" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "11e05668-90eb-529f-8a8f-3d114a11f4d8", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_not_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-3" + } + ] + }, + { + "uuid": "b8210eb0-757a-5a32-b444-eac9eef7c8ec", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.6.1_Ensure_message_of_the_day_is_configured_properly" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-3" + } + ] + }, + { + "uuid": "3de6eb1e-a425-5230-b66b-88df72bbb4db", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.6.2_Ensure_local_login_warning_banner_is_configured_properly" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-3" + } + ] + }, + { + "uuid": "c5b7ae74-ed48-5dbc-afb6-5652bef4ea86", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_remote_login_warning_banner_is_configured_properly" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-3" + } + ] + }, + { + "uuid": "a43c5e50-e318-5baa-a369-9a36981199c3", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.6.4_Ensure_access_to_etcmotd_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "b60d711d-1c46-5286-977f-2058de7f70c4", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.6.5_Ensure_access_to_etcissue_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "dfc69eda-26db-56e0-91e1-5ed3c97781c0", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.6.6_Ensure_access_to_etcissue.net_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "3cc68be1-e7bc-5045-88ec-eb32ea931209", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.7.1_Ensure_GDM_is_removed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-11" + } + ] + }, + { + "uuid": "dd684a69-dc63-5c3a-ba0f-b0c31b4fd054", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "9609273c-bf53-5af6-bd8e-bc8ba1f60fac", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.7.3_Ensure_GDM_disable-user-list_option_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "04573cce-cbc6-58c9-b146-4ba1928a7619", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.7.5_Ensure_GDM_screen_locks_cannot_be_overridden" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-11" + } + ] + }, + { + "uuid": "51c091e8-b011-5154-99e7-9dbd5dc5e7c8", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.7.6_Ensure_GDM_automatic_mounting_of_removable_media_is_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "45f18632-daae-5b92-bfcb-a472fbc882bd", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.7.7_Ensure_GDM_disabling_automatic_mounting_of_removable_media_is_not_overridden" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "9dff13e0-23d0-5cbf-bb7f-93acb0e08175", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.7.8_Ensure_GDM_autorun-never_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "3921e65c-8347-5a36-bd0f-8d0fcc72b778", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.7.9_Ensure_GDM_autorun-never_is_not_overridden" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "e0e3c53c-1cd4-549e-815e-c4166f3d1421", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_1.7.10_Ensure_XDMCP_is_not_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-4" + } + ] + }, + { + "uuid": "01291b72-4793-5318-8d8f-d8f2534c8326", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_autofs_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-3" + }, + { + "type": "control", + "id-ref": "mp-7" + } + ] + }, + { + "uuid": "516b1816-4c1c-57dc-b31c-1d114f43883c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_avahi_daemon_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-4" + } + ] + }, + { + "uuid": "5a20cfcb-624b-5554-9228-9299bb9577b3", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_dhcp_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "d3c3aa99-e02c-5406-a59d-2f68ceb515ab", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_dns_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "46a2af50-97a0-521d-b506-b074af1692f1", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_dnsmasq_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "c6f0b801-39f2-52c8-8f4b-4a698f8e926d", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_ftp_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "03131974-9ea8-562a-bf17-8a6f60c20610", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_ldap_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "08b1cc6d-a0ce-5265-ac78-4fa32b288427", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_message_access_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "ff44ac45-f981-5c20-aedd-ffddf644e0f5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_network_file_system_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "e6cb0d77-4c48-5294-8504-efafb70fe4b7", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_nis_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "479611f7-c66f-51fd-8956-330804a78e84", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.11_Ensure_print_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "1ab038db-5c0b-56d3-9b6b-fcd7e5c8ff79", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.12_Ensure_rpcbind_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "dcc9fa52-30ac-5e51-b257-1a32c2380869", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.13_Ensure_rsync_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "81f482ee-82e7-53ba-8981-7cd7e5db3a19", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.14_Ensure_samba_file_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "583392f0-fcbb-5579-99d8-7d4b74c644d3", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.15_Ensure_snmp_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "44d23957-d04e-5d16-8ae0-0abd2f9bea79", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.16_Ensure_tftp_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "addbde30-2a3f-5c76-8a00-7bb7a9e1bdda", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.17_Ensure_web_proxy_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "a9cb13eb-42ba-5aa3-bcf3-895f6da5ecec", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.18_Ensure_web_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "4e8ccadc-eafd-59c8-9cbb-6ff84c1dbd7f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.19_Ensure_xinetd_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "f3053913-f327-5644-a443-a11e97446e6a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.20_Ensure_X_window_server_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-11" + } + ] + }, + { + "uuid": "9e6a1612-cc55-56ed-963e-671c73a0b3a0", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.21_Ensure_mail_transfer_agent_is_configured_for_local-only_mode" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "bb7bb172-792e-59fa-bd55-a459738cd844", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.1.22_Ensure_only_approved_services_are_listening_on_a_network_interface" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "0ca4e948-8909-55bb-a9d1-9c6edb152efa", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.2.1_Ensure_NIS_Client_is_not_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "cm-11" + } + ] + }, + { + "uuid": "b60fac79-de32-56d3-977b-631688cbdbf2", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_rsh_client_is_not_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "ab0d6e17-1144-542b-96bd-6b17e6b1a90f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_talk_client_is_not_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "b72451b4-7117-50bc-af6e-233c336a4cac", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_telnet_client_is_not_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "cm-11" + } + ] + }, + { + "uuid": "e46a04f5-5eb8-5bbc-8723-7c74e7ca4600", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_ldap_client_is_not_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "6865907f-0af9-5b46-9df0-3de6a3431a97", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_ftp_client_is_not_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "cm-11" + } + ] + }, + { + "uuid": "79c793af-6ef0-5797-9a63-92ca133dede5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.3.1.1_Ensure_a_single_time_synchronization_daemon_is_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "e9f0b477-e274-5945-a679-3e8aa95cd86b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.1_Ensure_systemd-timesyncd_configured_with_authorized_timeserver" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-7" + }, + { + "type": "control", + "id-ref": "au-8" + } + ] + }, + { + "uuid": "ed51bf53-5330-50ad-911d-4282d8558c3c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.3.2.2_Ensure_systemd-timesyncd_is_enabled_and_running" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-7" + }, + { + "type": "control", + "id-ref": "au-8" + } + ] + }, + { + "uuid": "fab1802b-2329-5d86-aa9e-44b59b497a3d", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.1_Ensure_chrony_is_configured_with_authorized_timeserver" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "19522cb0-0807-58fe-80a2-4bb32f56c7b0", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.2_Ensure_chrony_is_running_as_user__chrony" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-8" + } + ] + }, + { + "uuid": "02d8d11a-bc02-5ed8-9f8c-1f0d0c838d41", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.3.3.3_Ensure_chrony_is_enabled_and_running" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-8" + } + ] + }, + { + "uuid": "65488f10-16f3-593a-8cad-66b097248ca3", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.1_Ensure_cron_daemon_is_enabled_and_active" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "079f6e2a-9a1f-5b82-8e3b-1e47e05a5bf0", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.2_Ensure_permissions_on_etccrontab_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "8bb14f5b-8896-523d-8416-d17604c40d10", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.3_Ensure_permissions_on_etccron.hourly_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "cec0cda3-730a-57c8-9379-b228ece34e37", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.4_Ensure_permissions_on_etccron.daily_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "f6d42456-5553-561f-b5e3-38d341c4b257", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.5_Ensure_permissions_on_etccron.weekly_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "cc3606be-7073-5d61-93f2-b48752d54d87", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.6_Ensure_permissions_on_etccron.monthly_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "31ac2f36-bc7e-56e9-aaf0-d5bd7f2fe3c5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.7_Ensure_permissions_on_etccron.d_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "5c17df23-fe4c-54d6-b340-3fcb521130ac", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.4.1.8_Ensure_crontab_is_restricted_to_authorized_users" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "d4fa8c9c-c39b-5bd0-a10a-77bccf85397e", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_2.4.2.1_Ensure_at_is_restricted_to_authorized_users" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "4ccc3048-f23a-5190-a094-1e985f704060", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IPv6_status_is_identified" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "5dd74316-d2d3-5327-842f-ae12d0af9329", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_wireless_interfaces_are_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "cc2c1dff-5a75-5b62-bd2c-2c8dcfa6ed8a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.1.3_Ensure_bluetooth_services_are_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "548b9c32-df6d-5c4e-a843-c387766e21d0", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_dccp_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-4" + }, + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "fb2a63e7-775e-55da-ad7b-ff4846ca22e5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_tipc_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-4" + }, + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "a717db65-225f-5239-92da-9acac46c5336", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_rds_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-4" + }, + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "6cb0ef30-fcaa-52ec-997e-4f891009c573", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_sctp_kernel_module_is_not_available" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "si-4" + }, + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "2633a4dc-1752-51b7-a875-8673440050f2", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_ip_forwarding_is_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "cd8e808f-8dfc-55d1-833b-c5a85cd1c95c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_packet_redirect_sending_is_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "fa54b545-ff3c-5fc6-810f-7644b2096419", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_bogus_icmp_responses_are_ignored" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "114de4f8-99f1-5e02-b098-05bc6c343343", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.4_Ensure_broadcast_icmp_requests_are_ignored" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "77540413-82bb-5b06-8a8f-8f7a2170c8e5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.5_Ensure_icmp_redirects_are_not_accepted" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "10ef982a-6432-5d1d-880c-b85fb17e0ad2", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.6_Ensure_secure_icmp_redirects_are_not_accepted" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "08cfb864-b970-5ca0-9e84-086f1580320a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.7_Ensure_reverse_path_filtering_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "ca24eea2-9788-59c1-9ec3-651e1c374326", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.8_Ensure_source_routed_packets_are_not_accepted" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "ea3e2cfa-e067-5860-bb9f-6d56d106c5f4", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.9_Ensure_suspicious_packets_are_logged" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "db8979d8-28cb-5883-9979-8605a850c14e", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.10_Ensure_tcp_syn_cookies_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "7721f044-eb58-56c5-8d21-9e4e7a35c5ae", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_3.3.11_Ensure_ipv6_router_advertisements_are_not_accepted" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "23ea71a9-4ece-532b-8cd4-eee6bf71e012", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.2.1_Ensure_ufw_is_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "7adde8bc-2cce-5f73-97b4-a75adcaf3f8a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.2.2_Ensure_iptables-persistent_is_not_installed_with_ufw" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "8a460a1e-88b6-5014-996c-c9f1795f5975", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_ufw_service_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "9e67b881-e38a-5e0b-bc55-5eb116d4bda5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_ufw_loopback_traffic_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "dbd30bc6-df9e-5125-8e55-e0f69cd4efea", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.2.5_Ensure_ufw_outbound_connections_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "1b479d0c-8d59-53af-912b-798008995a19", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.2.6_Ensure_ufw_firewall_rules_exist_for_all_open_ports" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "1fa359b8-3397-51b2-9f14-98ef7bec6b06", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.2.7_Ensure_ufw_default_deny_firewall_policy" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "c48a6707-e36c-54d2-a09b-612fda3bde19", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.3.1_Ensure_nftables_is_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + } + ] + }, + { + "uuid": "caa1c6a3-6bfa-5af9-a669-b1561944d86a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.3.2_Ensure_ufw_is_uninstalled_or_disabled_with_nftables" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "17d74509-0ebb-5dee-96fe-e339afc27eb5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.3.3_Ensure_iptables_are_flushed_with_nftables" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "c8b76563-f870-5550-b0d8-8115850d404f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.3.4_Ensure_a_nftables_table_exists" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "f42f8b51-eb8f-5ab7-b921-a0a9bdaa64e5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.3.6_Ensure_nftables_loopback_traffic_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "85d0dfd8-e238-577e-873a-7935f11481e5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.3.7_Ensure_nftables_outbound_and_established_connections_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "ca46d2f2-a4ad-5637-8b01-f67cb003df90", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.3.8_Ensure_nftables_default_deny_firewall_policy" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "11b1c27b-be8d-5e01-8c51-9a7103c5e8de", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.3.9_Ensure_nftables_service_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "cc9e83d8-929f-5add-abc3-b4a606ce1223", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.3.10_Ensure_nftables_rules_are_permanent" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "2bd76771-d4fc-5ce6-920a-1d585e955311", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.1_Ensure_iptables_packages_are_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "b9a58d49-a3ca-53e4-95c9-3c9a1fa2b62e", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.2_Ensure_nftables_is_not_in_use_with_iptables" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "06e6f1de-8c41-5da9-b694-08d4547e9a5c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.1.3_Ensure_ufw_is_not_in_use_with_iptables" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "1c7d4974-b5b4-5337-bf8d-9372e3538625", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.1_Ensure_iptables_default_deny_firewall_policy" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "1812426f-680b-51f4-a09e-b3e7ff016d46", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.2_Ensure_iptables_loopback_traffic_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "31604617-61ed-5ea5-bc1d-b3f58f7888c7", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.3_Ensure_iptables_outbound_and_established_connections_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "7e4b4eb8-9fdf-50c8-872d-020e3d646834", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.2.4_Ensure_iptables_firewall_rules_exist_for_all_open_ports" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "012f8cda-0b79-569f-a1e6-b83de4280aba", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.1_Ensure_ip6tables_default_deny_firewall_policy" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "c9b71042-5b8e-514e-bb49-5a746f55b492", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.2_Ensure_ip6tables_loopback_traffic_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "45117d87-e24d-5aff-8488-38b37af6872b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.3_Ensure_ip6tables_outbound_and_established_connections_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "3d9c7358-72d5-5ade-a653-3baa551edab8", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_4.4.3.4_Ensure_ip6tables_firewall_rules_exist_for_all_open_ports" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ca-9" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "0086b4a5-3840-5002-b347-a1ab589e88a3", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_permissions_on_etcsshsshd_config_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "97d7ff7e-b4db-50a6-99c9-6b129a658ef0", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_SSH_private_host_key_files_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "3dc98714-9080-5007-882c-0d2f0f15cf81", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_SSH_public_host_key_files_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "88073f0b-0d8c-5ea1-8fcb-edf4c494919c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_sshd_access_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "8ddfd5ce-53f4-542f-bfab-2a8577ee6650", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_sshd_Banner_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "cedffb4f-8410-5202-b88b-a0279f0a02db", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_sshd_Ciphers_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-8" + } + ] + }, + { + "uuid": "28acae68-f79d-5e02-802d-7626f54b49df", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_sshd_ClientAliveInterval_and_ClientAliveCountMax_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "774b995c-94a2-5b5f-9847-dc182521633b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_sshd_DisableForwarding_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-7" + } + ] + }, + { + "uuid": "2946f39d-d53c-5086-9295-3f4ec115c84f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.9_Ensure_sshd_GSSAPIAuthentication_is_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "aadff0f0-207f-5bb4-b2f9-252750a81055", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.10_Ensure_sshd_HostbasedAuthentication_is_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "e26ea6f4-64f4-5cb4-985c-9440f5af6a5a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.11_Ensure_sshd_IgnoreRhosts_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "accd7f3b-f166-5d17-bd29-4f1373b6066a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.12_Ensure_sshd_KexAlgorithms_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "sc-8" + } + ] + }, + { + "uuid": "6fcce0c3-e229-5e3a-b611-d8a4cb6d1f57", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.13_Ensure_sshd_LoginGraceTime_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "73a35052-ddb1-5610-b6cc-4a1b6c0808e7", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.14_Ensure_sshd_LogLevel_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "48d48029-719a-5fa4-9015-7f8c10a54963", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.15_Ensure_sshd_MACs_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "28bc0708-a7a3-5c88-87f4-71303dc6d1d4", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.16_Ensure_sshd_MaxAuthTries_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "0a2bb261-9961-5a57-831b-714ed0d5dbff", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.17_Ensure_sshd_MaxSessions_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "5a012627-af00-5e0d-8a34-ee50a26518c1", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.18_Ensure_sshd_MaxStartups_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "aeead994-ffcb-547e-bf11-b4ecce1f908c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.19_Ensure_sshd_PermitEmptyPasswords_is_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "e7fa3347-b5d9-561a-a55e-598b93ecb586", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.20_Ensure_sshd_PermitRootLogin_is_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-6" + } + ] + }, + { + "uuid": "518d273a-81d5-5dad-8fe6-a8037647bfe7", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.21_Ensure_sshd_PermitUserEnvironment_is_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "22d0c1d5-55d8-5718-a89a-82409906c9e3", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.1.22_Ensure_sshd_UsePAM_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "4fca4b3a-634b-5e2b-bae1-41279005dda5", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_sudo_is_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-6" + } + ] + }, + { + "uuid": "d48c0e26-498b-5f5b-bee3-c7474da19f61", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_sudo_commands_use_pty" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-6" + } + ] + }, + { + "uuid": "da3d4a7c-1aff-549c-8929-63e79a95a3ee", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_sudo_log_file_exists" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "4b3ee271-068b-5336-b192-3d8fd998ec44", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_users_must_provide_password_for_privilege_escalation" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-6" + } + ] + }, + { + "uuid": "c62b6242-ac82-5b81-8fca-0a9a3696436a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_re-authentication_for_privilege_escalation_is_not_disabled_globally" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-6" + } + ] + }, + { + "uuid": "a7453c4f-2040-534d-8ca0-9ec8bc442f5e", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_sudo_authentication_timeout_is_configured_correctly" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-6" + } + ] + }, + { + "uuid": "a0a04252-ceea-56f8-bbcc-f29df49ab43e", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_access_to_the_su_command_is_restricted" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "634d9e07-2db7-5e0a-b4f4-e67e3397e174", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.2.1_Ensure_pam_unix_module_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5.1" + } + ] + }, + { + "uuid": "aa6ee22c-1327-5f15-a206-a287d5f58ecf", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.1_Ensure_password_number_of_changed_characters_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "5490be6c-49b6-560d-97ed-ce3bd0b12ac6", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.2_Ensure_minimum_password_length_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5.1" + } + ] + }, + { + "uuid": "77fbefca-f527-5d4f-931c-d5e55acd3066", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.3_Ensure_password_complexity_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "ffd0ee69-1f5d-5bc7-8d6c-ab2eca37af05", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.4_Ensure_password_same_consecutive_characters_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "805242c9-6bfa-52ae-9be4-704e23f6b04a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.5_Ensure_password_maximum_sequential_characters_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "5f7389d2-7047-5043-8984-68771ce1c744", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.6_Ensure_password_dictionary_check_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "98f6541e-7c10-5dc8-9536-152f29dbe1c6", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.7_Ensure_password_quality_checking_is_enforced" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "2ac3b8c6-f7d2-5f47-ad68-7d5c1bd310a2", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.2.8_Ensure_password_quality_is_enforced_for_the_root_user" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "031683e9-7bb5-568f-8880-0cd0466e1aa0", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.1_Ensure_password_history_remember_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5.1" + } + ] + }, + { + "uuid": "1c9a07a5-e2e8-55b2-b757-731613aebdfd", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.2_Ensure_password_history_is_enforced_for_the_root_user" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "fa4251c3-0627-5657-ad3c-cd6b681ce4b8", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.3.3_Ensure_pam_pwhistory_includes_use_authtok" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "8bbb4c41-0d8f-5837-b55b-707226faeafa", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.3_Ensure_pam_unix_includes_a_strong_password_hashing_algorithm" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "62bc92bb-dc31-5ae8-a6cf-421367e9ce4b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.3.3.4.4_Ensure_pam_unix_includes_use_authtok" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "844716d5-b05b-5bf9-b2af-231d8b8700e1", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "baad5035-7fc3-5ab7-b0db-75f808185d9c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_strong_password_hashing_algorithm_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "e1601bc9-e858-56b6-847b-93c2abf47525", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.1_Ensure_root_is_the_only_UID_0_account" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "5044ed0e-cfa5-5c4d-808e-158401925b83", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.2_Ensure_root_is_the_only_GID_0_account" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "c8c4787b-3bd7-5c30-8d57-70110b1b742f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.3_Ensure_group_root_is_the_only_GID_0_group" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "f628819b-9183-5d68-9b01-97a2fa1ae66a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.5_Ensure_root_path_integrity" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "80f1ba52-1a8a-5767-b996-ecedaf6635ae", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.6_Ensure_root_user_umask_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "931cb930-95e7-54e4-b232-41ce7f4df231", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.7_Ensure_system_accounts_do_not_have_a_valid_login_shell" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-2.5" + }, + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "ac-11" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "0cd1104d-5a38-54a9-8ed3-268edd8693d1", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.2.8_Ensure_accounts_without_a_valid_login_shell_are_locked" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-2.5" + }, + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "ac-11" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "bd515148-f21d-50b2-b55b-1f4a6d894554", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.1_Ensure_nologin_is_not_listed_in_etcshells" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "412afa46-f00c-5f4d-a5fb-18548e1c4d37", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_5.4.3.3_Ensure_default_user_umask_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "7510f1d7-56b9-5018-9dd4-a4657028dabb", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.1_Ensure_journald_service_is_enabled_and_active" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-7" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "d95de0fc-6b68-5442-809e-9dd84b66e1a1", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.2_Ensure_journald_log_file_access_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "mp-2" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "5dd4b3f1-871b-5753-bc67-f9d630372db6", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.1.3_Ensure_journald_log_file_rotation_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-7" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "822a8ef8-face-5f33-aafe-e528e8324249", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.2_Ensure_journald_ForwardToSyslog_is_disabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-6" + }, + { + "type": "control", + "id-ref": "au-7" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "c07be92d-94e1-5aff-933c-426f08c2c1ee", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.3_Ensure_journald_Compress_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-4" + } + ] + }, + { + "uuid": "836ebcc4-5871-57fe-9fc7-ab9fa21a0b7a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.4_Ensure_journald_Storage_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "6a993ad6-1983-5b8f-aeab-11b8ab65db45", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.1_Ensure_systemd-journal-remote_is_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-7" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "f3ee2c02-5e1c-5ccc-a709-3a4a53131955", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.2_Ensure_systemd-journal-upload_authentication_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "5fc1400a-a91c-57d5-8fa5-587d208010bb", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.3_Ensure_systemd-journal-upload_is_enabled_and_active" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "0c5e0127-65ba-5c90-aaa2-582b2537e74d", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.2.1.4_Ensure_systemd-journal-remote_service_is_not_in_use" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-7" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "e3fa32cd-4bc5-563f-9ee7-2f1fded21122", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.1_Ensure_rsyslog_is_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "61684a46-34e7-5a16-89f7-82621a09c860", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.2_Ensure_rsyslog_service_is_enabled_and_active" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "ee632fb3-e3cd-5e95-9b89-9625c529499d", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.3_Ensure_journald_is_configured_to_send_logs_to_rsyslog" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-4" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "5908cb6b-ce86-5984-b734-cf9c992efc93", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.4_Ensure_rsyslog_log_file_creation_mode_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "ac-6" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "a9fa035e-1f8a-5e4f-9c99-53044149d906", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.5_Ensure_rsyslog_logging_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-7" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "097a7e0c-528a-584e-b2fd-a8ab7a217d08", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.6_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-6" + } + ] + }, + { + "uuid": "09949052-62c4-5771-9cc4-62536651e43c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.7_Ensure_rsyslog_is_not_configured_to_receive_logs_from_a_remote_client" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-7" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "391dd611-49b8-51f4-b094-318020cca10f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.3.8_Ensure_logrotate_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-8" + } + ] + }, + { + "uuid": "e7922423-0da8-5ebb-8d26-6ad8cf40581f", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.1.4.1_Ensure_access_to_all_logfiles_has_been_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "ee598455-d133-5821-9909-d71eece559b3", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.1_Ensure_auditd_packages_are_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "eba53f22-9807-54ad-8473-eaded4a90a83", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.2_Ensure_auditd_service_is_enabled_and_active" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "5f0ca13e-c584-5786-a9d7-3fe569ed5c8b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "280d82c0-7692-54b2-aa0d-cc9bba488f72", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.1.4_Ensure_audit_backlog_limit_is_sufficient" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + } + ] + }, + { + "uuid": "dbf219aa-1ba4-5b06-8dee-c7f6ac84d00b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.1_Ensure_audit_log_storage_size_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-8" + } + ] + }, + { + "uuid": "17fae923-48b2-55ba-b0cb-220ca9a4901c", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.2_Ensure_audit_logs_are_not_automatically_deleted" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-8" + } + ] + }, + { + "uuid": "73c64e98-084e-560b-bbf3-c23eb5b2a602", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.3_Ensure_system_is_disabled_when_audit_logs_are_full" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-8" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "abdda97b-b3e2-5c95-8964-bba352e0ac49", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.2.4_Ensure_system_warns_when_audit_logs_are_low_on_space" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-8" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "6409f09c-7433-565d-abf5-ef4964e4a9e4", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.1_Ensure_changes_to_system_administration_scope_sudoers_is_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "37c1ae5e-79a2-5119-8ceb-9ddd5c2f4ad6", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.2_Ensure_actions_as_another_user_are_always_logged" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "12f36d4c-c176-5403-be41-81b8513ab05d", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.4_Ensure_events_that_modify_date_and_time_information_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "ed63bdbc-cbf8-5611-a014-13c43adc3dfe", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.5_Ensure_events_that_modify_the_systems_network_environment_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "3fda8310-9637-59fb-9804-18778108a7c6", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.6_Ensure_use_of_privileged_commands_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-3.1" + } + ] + }, + { + "uuid": "79206578-e3b4-5342-8b6f-d2d6f3e3f3ff", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.7_Ensure_unsuccessful_file_access_attempts_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "02f49f2d-b643-5c88-a20b-7e16676871b0", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.8_Ensure_events_that_modify_usergroup_information_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "67c05df5-96da-5fb0-bf9e-64d8f1412b12", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.9_Ensure_discretionary_access_control_permission_modification_events_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "9e7b0199-207f-5079-be13-b5238d78abed", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.10_Ensure_successful_file_system_mounts_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "3a89a91d-b140-58c8-8995-bfc15d899483", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.11_Ensure_session_initiation_information_is_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "fe3306e0-21ab-59d4-ab56-e105dc82d0a4", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.12_Ensure_login_and_logout_events_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "7e6fa6d3-1144-5136-983d-c092a5c33eea", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.13_Ensure_file_deletion_events_by_users_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "sc-7" + } + ] + }, + { + "uuid": "ee651818-54e4-50cd-b90e-a86496b8ba4e", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.14_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "5e555667-8dff-581e-a6b5-158dea498189", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.15_Ensure_successful_and_unsuccessful_attempts_to_use_the_chcon_command_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "d7ed36d2-01d8-5e24-9d99-c514175a5832", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.16_Ensure_successful_and_unsuccessful_attempts_to_use_the_setfacl_command_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "ba71f494-f54c-50f3-b286-931640f2c638", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.17_Ensure_successful_and_unsuccessful_attempts_to_use_the_chacl_command_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "1509e98f-27cf-53f7-85f1-efb7f723228a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.18_Ensure_successful_and_unsuccessful_attempts_to_use_the_usermod_command_are_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "si-5" + } + ] + }, + { + "uuid": "05d193fe-0605-5e0d-ad59-c4681cbd6468", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.19_Ensure_kernel_module_loading_unloading_and_modification_is_collected" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "cm-6" + } + ] + }, + { + "uuid": "adae8295-edb9-553e-86b8-4fb9d8b5d993", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.20_Ensure_the_audit_configuration_is_immutable" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "au-3" + }, + { + "type": "control", + "id-ref": "au-12" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "1b45a599-a029-53a7-a7e4-a000db805f02", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.3.21_Ensure_the_running_and_on_disk_configuration_is_the_same" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "3d9ba1b6-5be2-53ce-8c26-e3044ae65f00", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.1_Ensure_audit_log_files_mode_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "f3281b2f-75db-57bd-920e-323a44cb84f3", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.2_Ensure_audit_log_files_owner_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "9a3bf274-4875-5b50-acda-3ca88c713501", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.3_Ensure_audit_log_files_group_owner_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "109bd405-e2c7-567b-a458-914ad197e1a9", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.4_Ensure_the_audit_log_file_directory_mode_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "73629b37-bec8-5036-ae26-066dd6af6e4b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.5_Ensure_audit_configuration_files_mode_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "3657b13a-8e34-54f7-9295-34483f6f5bc9", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.6_Ensure_audit_configuration_files_owner_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "4d8389b0-b48d-5500-a666-e461b1258bcd", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.7_Ensure_audit_configuration_files_group_owner_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "0b9d9956-3ce4-59d7-927a-1d377bd90880", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.8_Ensure_audit_tools_mode_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "f3565f7b-25c4-54e1-a616-2dd02a67c91b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.9_Ensure_audit_tools_owner_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "c3268476-ef66-5bfe-8d80-eba35f051717", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.2.4.10_Ensure_audit_tools_group_owner_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-3" + } + ] + }, + { + "uuid": "2ba22cd7-f3d8-51bd-8d00-7f6846427b9b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.3.1_Ensure_AIDE_is_installed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + } + ] + }, + { + "uuid": "269fb3ee-844d-567c-af31-f02b479a43ff", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_6.3.2_Ensure_filesystem_integrity_is_regularly_checked" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "au-2" + } + ] + }, + { + "uuid": "ee4e82fa-6386-5780-8a12-3a0c74de760b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.1_Ensure_permissions_on_etcpasswd_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "b21014fc-d1a5-5d36-996f-9bcca39b3038", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.2_Ensure_permissions_on_etcpasswd-_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "3a7c20a9-b3a9-59a0-b83b-2ff3959cad25", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.3_Ensure_permissions_on_etcgroup_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "dd9e8863-53b0-5ca7-ba69-b3266bab7648", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.4_Ensure_permissions_on_etcgroup-_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "4cc32f0e-06f4-5d41-b2f1-58f0d85afc81", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.5_Ensure_permissions_on_etcshadow_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "9abfb35f-b78d-5cd9-8e06-89d6a39a604e", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.6_Ensure_permissions_on_etcshadow-_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "6d82ac95-468a-59a8-a9c8-11a1453ec88a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.7_Ensure_permissions_on_etcgshadow_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "6db653fb-461c-508b-a19d-3c5f56255485", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.8_Ensure_permissions_on_etcgshadow-_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "12c568ef-7200-5788-b7e1-f4aad0b65a87", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.9_Ensure_permissions_on_etcshells_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "10c88c18-c514-5c36-a6f3-a2d1cffcd242", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.10_Ensure_permissions_on_etcsecurityopasswd_are_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "4c7ccc56-b23a-5d6f-8001-e1253a08157d", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.11_Ensure_world_writable_files_and_directories_are_secured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "687ddbe0-3784-50e7-91be-ae70d7656e92", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.12_Ensure_no_files_or_directories_without_an_owner_and_a_group_exist" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "9d9209cf-07c2-568b-9a7c-529348f730df", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.1.13_Ensure_SUID_and_SGID_files_are_reviewed" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + }, + { + "type": "control", + "id-ref": "ac-3" + }, + { + "type": "control", + "id-ref": "mp-2" + } + ] + }, + { + "uuid": "28493968-9352-5c61-805e-309d8c910fa4", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.2.1_Ensure_accounts_in_etcpasswd_use_shadowed_passwords" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "9aa241df-3a2c-507e-8a54-d7244eb23536", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.2.2_Ensure_etcshadow_password_fields_are_not_empty" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "ac731a83-a434-548b-a7f3-c65f8e85362a", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.2.3_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "06952f5d-2839-57a2-86e1-58a0cc12d6b8", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.2.4_Ensure_shadow_group_is_empty" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "ecddaca8-3119-55bd-8783-0b792e71613b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.2.5_Ensure_no_duplicate_UIDs_exist" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "b321cc7b-9c49-516a-bcb4-29e7d1e9d95b", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.2.6_Ensure_no_duplicate_GIDs_exist" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "95fc739c-0864-5d32-839e-3bb5010a6969", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.2.7_Ensure_no_duplicate_user_names_exist" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "81b847f0-f1ac-5928-a8eb-8f58a000d150", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.2.8_Ensure_no_duplicate_group_names_exist" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + }, + { + "uuid": "76484cd8-fedd-5847-aa71-2568df3e0166", + "relationship": "subset-of", + "sources": [ + { + "type": "control", + "id-ref": "xccdf_org.cisecurity.benchmarks_rule_7.2.10_Ensure_local_interactive_user_dot_files_access_is_configured" + } + ], + "targets": [ + { + "type": "control", + "id-ref": "cm-1" + }, + { + "type": "control", + "id-ref": "cm-2" + }, + { + "type": "control", + "id-ref": "cm-6" + }, + { + "type": "control", + "id-ref": "cm-7" + }, + { + "type": "control", + "id-ref": "ia-5" + } + ] + } + ] + } + ] + } +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json new file mode 100644 index 0000000..e35e937 --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/examples/executable-first/oscal/nist-sp-800-53-rev5-with-ubuntu-24-04-lts-stig-profile.json @@ -0,0 +1,14782 @@ +{ + "profile": { + "uuid": "d3f38b40-1034-5634-86be-8b98137a3b1d", + "metadata": { + "title": "NIST SP 800-53 Revision 5, with the Canonical Ubuntu 24.04 LTS Security Technical Implementation Guide V1R5 as executable assessment methods", + "published": "2026-02-06T00:00:00Z", + "last-modified": "2026-09-09T00:00:00Z", + "version": "V1R5", + "oscal-version": "1.2.1", + "links": [ + { + "rel": "source", + "href": "#7e7104a2-af0d-5803-a260-7280e8006ecf" + }, + { + "rel": "source", + "href": "#e483dc41-2538-5a53-a9a1-07a1a5a38eb1" + }, + { + "rel": "source", + "href": "#aec779f8-11e6-54ac-a60d-c1f8193d0623" + } + ], + "remarks": "Generated by tools/executable_first_corpus.py from the STIG named in back-matter (Release: 5 Benchmark Date: 01 Apr 2026, status accepted). Every rule becomes an assessment objective on the SP 800-53 control its CCIs map to, with DISA's check text as the body of an assessment method beside it and DISA's fix text in a remediation part. The STIG publishes the check as text, so the method names no engine and no evaluation rule. The platform is the CPE the CIS Benchmark publishes for the same operating system, because the STIG carries none. The mapping from CCIs to controls is the one the STIG's published OSCAL conversion derived from DISA's CCI list." + }, + "imports": [ + { + "href": "https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json", + "include-controls": [ + { + "with-ids": [ + "ac-10", + "ac-11", + "ac-11.1", + "ac-12", + "ac-17.1", + "ac-17.2", + "ac-2.2", + "ac-2.3", + "ac-2.4", + "ac-3", + "ac-3.4", + "ac-6.10", + "ac-6.8", + "ac-6.9", + "ac-7", + "ac-8", + "au-12", + "au-12.3", + "au-14.1", + "au-3", + "au-3.1", + "au-4", + "au-4.1", + "au-5", + "au-5.1", + "au-6.4", + "au-7", + "au-7.1", + "au-8", + "au-9", + "au-9.3", + "cm-14", + "cm-3.5", + "cm-5.1", + "cm-5.6", + "cm-6", + "cm-7", + "cm-7.2", + "cm-7.5", + "cm-7.9", + "ia-11", + "ia-2", + "ia-2.1", + "ia-2.12", + "ia-2.2", + "ia-2.5", + "ia-2.6", + "ia-3", + "ia-5.1", + "ia-5.13", + "ia-5.2", + "ia-7", + "ia-8", + "ma-3.5", + "ma-4", + "ma-4.1", + "ma-4.6", + "sc-10", + "sc-11", + "sc-13", + "sc-17", + "sc-23.5", + "sc-24", + "sc-28", + "sc-28.1", + "sc-28.3", + "sc-3", + "sc-4", + "sc-45", + "sc-45.1", + "sc-5", + "sc-5.2", + "sc-8", + "sc-8.1", + "sc-8.2", + "si-11", + "si-16", + "si-2.6", + "si-6" + ] + } + ] + } + ], + "merge": { + "as-is": true + }, + "modify": { + "alters": [ + { + "control-id": "ac-10", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-10_obj-ubtu-24-200000", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270677", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270677r1101774_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200000", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000054", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must limit the number of concurrent sessions to 10 for all accounts and/or account types.", + "parts": [ + { + "id": "ac-10_dsc-ubtu-24-200000", + "name": "guidance", + "prose": "Ubuntu 24.04 LTS management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to denial-of-service (DoS) attacks. \n \nThis requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions must be defined based upon mission needs and the operational environment for each system." + } + ] + }, + { + "id": "ac-10_asm-ubtu-24-200000", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-10_obj-ubtu-24-200000" + } + ], + "prose": "Verify Ubuntu 24.04 LTS limits the number of concurrent sessions to 10 for all accounts and/or account types with the following command: \n \n$ grep -r maxlogins /etc/security/limits.conf /etc/security/limits.d/*.conf\n/etc/security/limits.d/maxlogins.conf:* hard maxlogins 10\n \nIf the \"maxlogins\" item does not have a value of \"10\" or less, is commented out, or is missing, this is a finding." + }, + { + "id": "ac-10_rem-ubtu-24-200000", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to limit the number of concurrent sessions to 10 for all accounts and/or account types. \n \nAdd the following line to the top of the /etc/security/limits.conf or in a \".conf\" file defined in /etc/security/limits.d/: \n \n* hard maxlogins 10" + } + ] + } + ] + }, + { + "control-id": "ac-11", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-11.1_obj-ubtu-24-101000" + } + ], + "parts": [ + { + "id": "ac-11_obj-ubtu-24-200020", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270678", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270678r1101791_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200020", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000057", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must initiate a graphical session lock after 10 minutes of inactivity.", + "parts": [ + { + "id": "ac-11_dsc-ubtu-24-200020", + "name": "guidance", + "prose": "A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence. \n \nThe session lock is implemented at the point where session activity can be determined. \n \nRegardless of where the session lock is determined and implemented, once invoked, a session lock of Ubuntu 24.04 LTS must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system." + } + ] + }, + { + "id": "ac-11_asm-ubtu-24-200020", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-11_obj-ubtu-24-200020" + } + ], + "prose": "Note: If Ubuntu 24.04 LTS does not have a graphical user interface installed, this requirement is not applicable. \n\nVerify the Ubuntu operation system has a graphical user interface session lock configured to activate after 10 minutes of inactivity with the following commands: \n \nSet the following settings to verify the graphical user interface session is configured to lock the graphical user session after 10 minutes of inactivity: \n \n**$ gsettings get org.gnome.desktop.screensaver lock-enabled\ntrue\n\n$ gsettings get org.gnome.desktop.screensaver lock-delay\nuint32 0\n\n$ gsettings get org.gnome.desktop.session idle-delay\nuint32 600\n\nNote: If \"lock-enabled\" is not set to \"true\", this is a finding.\n\nIf \"lock-delay\" is set to a value greater than \"0\", or if \"idle-delay\" is set to a value greater than \"600\", or either settings are missing, this is a finding." + }, + { + "id": "ac-11_rem-ubtu-24-200020", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to lock the current graphical user interface session after 10 minutes of inactivity. \n \nCreate or edit a file named /etc/dconf/db/local.d/00-screensaver with the following contents:\n\n[org/gnome/desktop/session]\nidle-delay=uint32 900\n\n[org/gnome/desktop/screensaver]\nlock-enabled=true\nlock-delay=uint32 600\n\nUpdate the dconf settings:\n\n$ sudo dconf update" + }, + { + "id": "ac-11_obj-ubtu-24-200040", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270679", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270679r1107295_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200040", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000056", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must prevent a user from overriding the disabling of the graphical user interface automount function.", + "parts": [ + { + "id": "ac-11_dsc-ubtu-24-200040", + "name": "guidance", + "prose": "A nonprivileged account is any operating system account with authorizations of a nonprivileged user.\n\nSatisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227" + } + ] + }, + { + "id": "ac-11_asm-ubtu-24-200040", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-11_obj-ubtu-24-200040" + } + ], + "prose": "Note: This requirement assumes the use of the Ubuntu 24.04 LTS default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable.\n\nVerify Ubuntu 24.04 LTS disables the ability of the user to override the graphical user interface automount setting.\n\nDetermine which profile the system database is using with the following command:\n\n$ sudo grep system-db /etc/dconf/profile/user\n\nsystem-db:local\n\nCheck that the automount setting is locked from nonprivileged user modification with the following command:\n\nNote: The example below is using the database \"local\" for the system, so the path is \"/etc/dconf/db/local.d\". This path must be modified if a database other than \"local\" is being used.\n\n$ grep 'automount-open' /etc/dconf/db/local.d/locks/* \n\n/org/gnome/desktop/media-handling/automount-open\n\nIf the command does not return at least the example result, this is a finding." + }, + { + "id": "ac-11_rem-ubtu-24-200040", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS so the GNOME desktop does not allow a user to change the setting that disables automated mounting of removable media.\n\nAdd the following line to \"/etc/dconf/db/local.d/locks/00-security-settings-lock\" to prevent user modification:\n\n/org/gnome/desktop/media-handling/automount-open\n\nUpdate the dconf system databases:\n\n$ sudo dconf update" + }, + { + "id": "ac-11_obj-ubtu-24-200042", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-274873", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-274873r1107300_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200042", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000056", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000057", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000058", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must prevent a user from overriding the disabling of the graphical user smart card removal action.", + "parts": [ + { + "id": "ac-11_dsc-ubtu-24-200042", + "name": "guidance", + "prose": "A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.\n\nThe session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, Ubuntu 24.04 LTS must provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.\n\nSatisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011" + } + ] + }, + { + "id": "ac-11_asm-ubtu-24-200042", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-11_obj-ubtu-24-200042" + } + ], + "prose": "Note: This requirement assumes the use of the Ubuntu 24.04 LTS default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable.\n\nVerify Ubuntu 24.04 LTS disables the ability of the user to override the smart card removal action setting.\n\n$ gsettings writable org.gnome.settings-daemon.peripherals.smartcard removal-action\n \nfalse\n \nIf \"removal-action\" is writable and the result is \"true\", this is a finding." + }, + { + "id": "ac-11_rem-ubtu-24-200042", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to prevent a user from overriding the disabling of the graphical user smart card removal action.\n\nAdd the following line to \"/etc/dconf/db/local.d/locks/00-security-settings-lock\":\n\n/org/gnome/settings-daemon/peripherals/smartcard/removal-action\n\nUpdate the dconf system databases:\n\n$ sudo dconf update" + } + ] + } + ] + }, + { + "control-id": "ac-11.1", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-11.1_obj-ubtu-24-101000", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270674", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270674r1067167_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-101000", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000060", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000057", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must allow users to directly initiate a session lock for all connection types.", + "parts": [ + { + "id": "ac-11.1_dsc-ubtu-24-101000", + "name": "guidance", + "prose": "A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence. \n \nThe session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, Ubuntu 24.04 LTSs need to provide users with the ability to manually invoke a session lock so users may secure their session if they need to temporarily vacate the immediate physical vicinity.\n\nSatisfies: SRG-OS-000031-GPOS-00012, SRG-OS-000030-GPOS-00011" + } + ] + }, + { + "id": "ac-11.1_asm-ubtu-24-101000", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-11.1_obj-ubtu-24-101000" + } + ], + "prose": "Verify Ubuntu 24.04 LTS has the \"vlock\" package installed with the following command: \n \n$ dpkg -l | grep vlock \nii vlock 2.2.2-10 amd64 Virtual Console locking program\n \nIf \"vlock\" is not installed, this is a finding." + }, + { + "id": "ac-11.1_rem-ubtu-24-101000", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install the \"vlock\" package (if it is not already installed) by running the following command: \n \n$ sudo apt install -y vlock" + }, + { + "id": "ac-11.1_obj-ubtu-24-200043", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-274871", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-274871r1107302_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200043", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000060", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must conceal, via the session lock, information previously visible on the display with a publicly viewable image.", + "parts": [ + { + "id": "ac-11.1_dsc-ubtu-24-200043", + "name": "guidance", + "prose": "Setting the screensaver mode to blank-only conceals the contents of the display from passersby." + } + ] + }, + { + "id": "ac-11.1_asm-ubtu-24-200043", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-11.1_obj-ubtu-24-200043" + } + ], + "prose": "Note: This requirement assumes the use of the Ubuntu 24.04 LTS default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable.\n\nTo verify the screensaver is configured to be blank, run the following command:\n\n$ gsettings writable org.gnome.desktop.screensaver picture-uri\n \nfalse\n \nIf \"picture-uri\" is writable and the result is \"true\", this is a finding." + }, + { + "id": "ac-11.1_rem-ubtu-24-200043", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to prevent a user from overriding the picture-uri setting for graphical user interfaces.\n\nIn the file \"/etc/dconf/db/local.d/00-security-settings\", add or update the following lines:\n\n[org/gnome/desktop/screensaver]\npicture-uri=''\n\nPrevent user modification by adding the following line to \"/etc/dconf/db/local.d/locks/00-security-settings-lock\":\n\n/org/gnome/desktop/screensaver/picture-uri\n\nUpdate the dconf system databases:\n\n$ sudo dconf update" + } + ] + } + ] + }, + { + "control-id": "ac-12", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-12_obj-ubtu-24-200060", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270680", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270680r1066529_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200060", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002361", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must automatically terminate a user session after inactivity timeouts have expired.", + "parts": [ + { + "id": "ac-12_dsc-ubtu-24-200060", + "name": "guidance", + "prose": "Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. \n \nSession termination terminates all processes associated with a user's logical session except those processes specifically created by the user (i.e., session owner) to continue after the session is terminated. \n \nConditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. \n \nThis capability is typically reserved for specific operating system functionality where the system owner, data owner, or organization requires additional assurance." + } + ] + }, + { + "id": "ac-12_asm-ubtu-24-200060", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-12_obj-ubtu-24-200060" + } + ], + "prose": "Verify Ubuntu 24.04 LTS automatically terminates a user session after inactivity timeouts have expired with the following command:\n \n$ sudo grep -E \"\\bTMOUT=[0-9]+\" /etc/bash.bashrc /etc/profile.d/*\n/etc/profile.d/99-terminal_tmout.sh:TMOUT=600 \n\nIf \"TMOUT\" is not set, or if the value is \"0\" or is commented out, this is a finding." + }, + { + "id": "ac-12_rem-ubtu-24-200060", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to automatically terminate a user session after inactivity timeouts have expired or at shutdown. \n \nCreate the file \"/etc/profile.d/99-terminal_tmout.sh\" file if it does not exist. \n \nModify or append the following line in the \"/etc/profile.d/99-terminal_tmout.sh \" file: \n \nTMOUT=600 \n \nThis will set a timeout value of 10 minutes for all future sessions. \n \nTo set the timeout for the current sessions, execute the following command over the terminal session: \n \n$ export TMOUT=600" + } + ] + } + ] + }, + { + "control-id": "ac-17.1", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-17.1_obj-ubtu-24-100300", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270654", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270654r1067143_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100300", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have an application firewall installed in order to control remote access methods.", + "parts": [ + { + "id": "ac-17.1_dsc-ubtu-24-100300", + "name": "guidance", + "prose": "Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk, and make remote user access management difficult at best. \n \nRemote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nUbuntu 24.04 LTS functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets)." + } + ] + }, + { + "id": "ac-17.1_asm-ubtu-24-100300", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.1_obj-ubtu-24-100300" + } + ], + "prose": "Verify that the Uncomplicated Firewall (ufw) is installed with the following command: \n \n$ dpkg -l | grep ufw\nii ufw 0.36.2-6 all program for managing a Netfilter firewall\n \nIf the \"ufw\" package is not installed, ask the system administrator if another application firewall is installed. \n \nIf no application firewall is installed, this is a finding." + }, + { + "id": "ac-17.1_rem-ubtu-24-100300", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install the ufw by using the following command: \n \n$ sudo apt install -y ufw" + }, + { + "id": "ac-17.1_obj-ubtu-24-100310", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270655", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270655r1067145_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100310", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enable and run the Uncomplicated Firewall (ufw).", + "parts": [ + { + "id": "ac-17.1_dsc-ubtu-24-100310", + "name": "guidance", + "prose": "Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk, and make remote user access management difficult at best. \n \nRemote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nUbuntu 24.04 LTS functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).\n\nSatisfies: SRG-OS-000297-GPOS-00115, SRG-OS-000480-GPOS-00232" + } + ] + }, + { + "id": "ac-17.1_asm-ubtu-24-100310", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.1_obj-ubtu-24-100310" + } + ], + "prose": "Verify the ufw is enabled on the system with the following command: \n \n$ sudo ufw status\nStatus: active\n \nIf the above command returns the status as \"inactive\" or any type of error, this is a finding. \n\nIf the ufw is not installed, ask the system administrator if another application firewall is installed. If a different firewall is active on the system, this is not a finding." + }, + { + "id": "ac-17.1_rem-ubtu-24-100310", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Enable the ufw by using the following command: \n \n$ sudo ufw enable\n\nNote: Enabling the firewall will potentially disrupt ssh sessions." + }, + { + "id": "ac-17.1_obj-ubtu-24-200090", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270681", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270681r1134806_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200090", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000067", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must monitor remote access methods.", + "parts": [ + { + "id": "ac-17.1_dsc-ubtu-24-200090", + "name": "guidance", + "prose": "Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk, and make remote user access management difficult at best. \n \nRemote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nAutomated monitoring of remote access sessions allows organizations to detect cyberattacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets)." + } + ] + }, + { + "id": "ac-17.1_asm-ubtu-24-200090", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.1_obj-ubtu-24-200090" + } + ], + "prose": "Verify that Ubuntu 24.04 LTS monitors all remote access methods with the following command: \n \n$ grep -E -r '^(auth,authpriv\\.\\*|daemon\\.\\*)' /etc/rsyslog.* \n/etc/rsyslog.d/50-default.conf:auth,authpriv.* /var/log/auth.log\n \nIf \"auth.*\", \"authpriv.*\", or \"daemon.*\" are not configured to be logged in at least one of the config files, this is a finding." + }, + { + "id": "ac-17.1_rem-ubtu-24-200090", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to monitor all remote access methods by adding the following lines to the \"/etc/rsyslog.d/50-default.conf\" file: \n \nauth.*,authpriv.* /var/log/secure \ndaemon.* /var/log/messages \n \nFor the changes to take effect, restart the \"rsyslog\" service with the following command: \n \n$ sudo systemctl restart rsyslog.service" + } + ] + } + ] + }, + { + "control-id": "ac-17.2", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-17.2_obj-ubtu-24-100820", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270667", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270667r1067107_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100820", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000068", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-003123", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002421", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the SSH daemon to use FIPS 140-3 approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission.", + "parts": [ + { + "id": "ac-17.2_dsc-ubtu-24-100820", + "name": "guidance", + "prose": "Without cryptographic integrity protections, information can be altered by unauthorized users without detection. \n \nRemote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nNonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. \n \nLocal maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. \n \nEncrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions that have common application in digital signatures, checksums, and message authentication codes.\n\nSatisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000394-GPOS-00174, SRG-OS-000424-GPOS-00188" + } + ] + }, + { + "id": "ac-17.2_asm-ubtu-24-100820", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.2_obj-ubtu-24-100820" + } + ], + "prose": "Verify that the SSH daemon is configured to implement only FIPS-approved algorithms with the following command:\n\n$ sudo grep -r 'Ciphers' /etc/ssh/sshd_config*\nCiphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\n \nIf any ciphers other than \"Ciphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\" are listed, the \"Ciphers\" keyword is missing, or the returned line is commented out, or if multiple conflicting ciphers are returned, this is a finding." + }, + { + "id": "ac-17.2_rem-ubtu-24-100820", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to allow the SSH daemon to only implement FIPS-approved algorithms. \n \nAdd the following line (or modify the line to have the required value) to the \"/etc/ssh/sshd_config\" file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): \n \nCiphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\n \nRestart the \"sshd\" service for changes to take effect: \n \n$ sudo systemctl restart sshd" + }, + { + "id": "ac-17.2_obj-ubtu-24-100830", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270668", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270668r1067110_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100830", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001453", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002890", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002421", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the SSH daemon to use Message Authentication Codes (MACs) employing FIPS 140-3 approved cryptographic hashes to prevent the unauthorized disclosure of information and/or detect changes to information during transmission.", + "parts": [ + { + "id": "ac-17.2_dsc-ubtu-24-100830", + "name": "guidance", + "prose": "Without cryptographic integrity protections, information can be altered by unauthorized users without detection. \n \nRemote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. \n \nLocal maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. \n \nEncrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions that have common application in digital signatures, checksums, and message authentication codes.\n\nSatisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000424-GPOS-00188" + } + ] + }, + { + "id": "ac-17.2_asm-ubtu-24-100830", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.2_obj-ubtu-24-100830" + } + ], + "prose": "Verify the SSH daemon is configured to only use MACs that employ FIPS 140-3 approved ciphers with the following command:\n\n$ grep -irs macs /etc/ssh/sshd_config*\nMACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\n\nIf any algorithms other than \"hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\" are listed, the returned line is commented out, or if conflicting results are returned, this is a finding." + }, + { + "id": "ac-17.2_rem-ubtu-24-100830", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to allow the SSH daemon to only use MACs that employ FIPS 140-3 approved ciphers. \n \nAdd the following line (or modify the line to have the required value) to the \"/etc/ssh/sshd_config\" file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): \n \nMACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\n \nRestart the \"sshd\" service for changes to take effect:\n\n$ sudo systemctl restart sshd" + }, + { + "id": "ac-17.2_obj-ubtu-24-100840", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270669", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270669r1134804_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100840", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000068", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS SSH server must be configured to use only FIPS 140-3 validated key exchange algorithms.", + "parts": [ + { + "id": "ac-17.2_dsc-ubtu-24-100840", + "name": "guidance", + "prose": "Without cryptographic integrity protections provided by FIPS-validated cryptographic algorithms, information can be viewed and altered by unauthorized users without detection.\n\nThe system will attempt to use the first algorithm presented by the client that matches the server list." + } + ] + }, + { + "id": "ac-17.2_asm-ubtu-24-100840", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.2_obj-ubtu-24-100840" + } + ], + "prose": "Verify that the SSH daemon is configured to use only FIPS-validated key exchange algorithms with the following command:\n\n$ sudo grep -ir kexalgorithms /etc/ssh/sshd_config*\nKexAlgorithms ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256\n \nIf \"KexAlgorithms\" does not contain only the algorithms \"ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256\", is commented out, or is missing, this is a finding." + }, + { + "id": "ac-17.2_rem-ubtu-24-100840", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the SSH daemon to use only FIPS-validated key exchange algorithms by adding or modifying the following line in \"/etc/ssh/sshd_config\":\n\nKexAlgorithms ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256\n\nRestart the \"sshd\" service for changes to take effect:\n\n$ sudo systemctl restart sshd" + }, + { + "id": "ac-17.2_obj-ubtu-24-100850", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270670", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270670r1067115_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100850", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001453", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the SSH client to use FIPS 140-3 approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission.", + "parts": [ + { + "id": "ac-17.2_dsc-ubtu-24-100850", + "name": "guidance", + "prose": "Without cryptographic integrity protections, information can be altered by unauthorized users without detection. \n \nRemote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nNonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. \n \nLocal maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. \n \nEncrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions that have common application in digital signatures, checksums, and message authentication codes. \n \nBy specifying a cipher list with the order of ciphers being in a \"strongest to weakest\" orientation, the system will automatically attempt to use the strongest cipher for securing SSH connections." + } + ] + }, + { + "id": "ac-17.2_asm-ubtu-24-100850", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.2_obj-ubtu-24-100850" + } + ], + "prose": "Verify the SSH client is configured to use only ciphers employing FIPS 140-3 approved algorithms with the following command:\n\n$ sudo grep -r 'Ciphers' /etc/ssh/ssh_config*\nCiphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\n \nIf any ciphers other than \"Ciphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\" are listed, the \"Ciphers\" keyword is missing, or the returned line is commented out, or if multiple conflicting ciphers are returned, this is a finding." + }, + { + "id": "ac-17.2_rem-ubtu-24-100850", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the Ubuntu 24.04 LTS SSH client to use only ciphers employing FIPS 140-3 approved algorithms by updating the \"/etc/ssh/ssh_config\" file with the following line:\n\nCiphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\n\nRestart the \"ssh\" service for changes to take effect:\n\n$ sudo systemctl restart ssh" + }, + { + "id": "ac-17.2_obj-ubtu-24-100860", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270671", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270671r1155244_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100860", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001453", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS SSH client must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms.", + "parts": [ + { + "id": "ac-17.2_dsc-ubtu-24-100860", + "name": "guidance", + "prose": "Without cryptographic integrity protections, information can be altered by unauthorized users without detection. \n \nRemote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. \n \nLocal maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. \n \nEncrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions that have common application in digital signatures, checksums, and message authentication codes." + } + ] + }, + { + "id": "ac-17.2_asm-ubtu-24-100860", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.2_obj-ubtu-24-100860" + } + ], + "prose": "Verify the SSH client is configured to only use MACs employing FIPS 140-3 approved algorithms with the following command:\n\n$ sudo grep -ir macs /etc/ssh/ssh_config*\nMACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\n\nIf any MACs other than \"hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\" are listed, or the returned line is commented out, this is a finding." + }, + { + "id": "ac-17.2_rem-ubtu-24-100860", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the Ubuntu 24.04 LTS SSH client to use only MACs employing FIPS 140-3 approved algorithms by updating the \"/etc/ssh/ssh_config\" file with the following line:\n\nMACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\n\nRestart the \"ssh\" service for changes to take effect:\n\n$ sudo systemctl restart ssh" + } + ] + } + ] + }, + { + "control-id": "ac-2.2", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-2.2_obj-ubtu-24-200250", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270682", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270682r1066535_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200250", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000016", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001682", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must automatically remove or disable emergency accounts after 72 hours.", + "parts": [ + { + "id": "ac-2.2_dsc-ubtu-24-200250", + "name": "guidance", + "prose": "Temporary accounts are privileged or nonprivileged accounts established during pressing circumstances, such as new software or hardware configuration or an incident response, where the need for prompt account activation requires bypassing normal account authorization procedures. If any inactive temporary accounts are left enabled on the system and are not either manually removed or automatically expired within 72 hours, the security posture of the system will be degraded and exposed to exploitation by unauthorized users or insider threat actors.\n\nTemporary accounts are different from emergency accounts. Emergency accounts, also known as \"last resort\" or \"break glass\" accounts, are local logon accounts enabled on the system for emergency use by authorized system administrators to manage a system when standard logon methods are failing or not available. Emergency accounts are not subject to manual removal or scheduled expiration requirements.\n\nThe automatic expiration of temporary accounts may be extended as needed by the circumstances but it must not be extended indefinitely. A documented permanent account must be established for privileged users who need long-term maintenance accounts.\n\nSatisfies: SRG-OS-000002-GPOS-00002, SRG-OS-000123-GPOS-00064" + } + ] + }, + { + "id": "ac-2.2_asm-ubtu-24-200250", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-2.2_obj-ubtu-24-200250" + } + ], + "prose": "Verify temporary accounts have been provisioned with an expiration date of 72 hours with the following command:\n\n$ sudo chage -l | grep -i \"account expires\"\n\nVerify each of these accounts has an expiration date set within 72 hours.\n\nIf any temporary accounts have no expiration date set or do not expire within 72 hours, this is a finding." + }, + { + "id": "ac-2.2_rem-ubtu-24-200250", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to expire temporary accounts after 72 hours with the following command:\n\n$ sudo chage -E $(date -d +3days +%Y-%m-%d) " + } + ] + } + ] + }, + { + "control-id": "ac-2.3", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-2.3_obj-ubtu-24-200260", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270683", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270683r1066538_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200260", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-003627", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-003628", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.", + "parts": [ + { + "id": "ac-2.3_dsc-ubtu-24-200260", + "name": "guidance", + "prose": "Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. \n \nOperating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.\n\nSatisfies: SRG-OS-000118-GPOS-00060, SRG-OS-000590-GPOS-00110" + } + ] + }, + { + "id": "ac-2.3_asm-ubtu-24-200260", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-2.3_obj-ubtu-24-200260" + } + ], + "prose": "Verify the account identifiers (individuals, groups, roles, and devices) are disabled after 35 days of inactivity with the following command: \n \nCheck the account inactivity value by performing the following command: \n \n$ grep INACTIVE /etc/default/useradd\nINACTIVE=35 \n \nIf \"INACTIVE\" is not set to a value 0<[VALUE]<=35, is commented out, or is missing, this is a finding." + }, + { + "id": "ac-2.3_rem-ubtu-24-200260", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to disable account identifiers after 35 days of inactivity after the password expiration. \n \nRun the following command to change the configuration for adduser: \n \n$ sudo useradd -D -f 35 \n \nNote: DOD recommendation is 35 days, but a lower value is acceptable. The value \"0\" will disable the account immediately after the password expires." + } + ] + } + ] + }, + { + "control-id": "ac-2.4", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-2.4_obj-ubtu-24-200280", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270684", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270684r1066541_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200280", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000018", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001403", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001404", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001405", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.", + "parts": [ + { + "id": "ac-2.4_dsc-ubtu-24-200280", + "name": "guidance", + "prose": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221" + } + ] + }, + { + "id": "ac-2.4_asm-ubtu-24-200280", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200280" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/passwd\" with the following command: \n \n$ sudo auditctl -l | grep passwd \n-w /etc/passwd -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "ac-2.4_rem-ubtu-24-200280", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/passwd\". \n \nAdd or update the following rule to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/passwd -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "ac-2.4_obj-ubtu-24-200290", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270685", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270685r1066544_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200290", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000018", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001403", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001404", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001405", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.", + "parts": [ + { + "id": "ac-2.4_dsc-ubtu-24-200290", + "name": "guidance", + "prose": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221" + } + ] + }, + { + "id": "ac-2.4_asm-ubtu-24-200290", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200290" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/group\" with the following command: \n \n$ sudo auditctl -l | grep group \n-w /etc/group -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "ac-2.4_rem-ubtu-24-200290", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/group\". \n \nAdd or update the following rule to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/group -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "ac-2.4_obj-ubtu-24-200300", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270686", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270686r1066547_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200300", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000018", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001403", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001404", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001405", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.", + "parts": [ + { + "id": "ac-2.4_dsc-ubtu-24-200300", + "name": "guidance", + "prose": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221" + } + ] + }, + { + "id": "ac-2.4_asm-ubtu-24-200300", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200300" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/shadow\" with the following command: \n \n$ sudo auditctl -l | grep shadow \n-w /etc/shadow -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "ac-2.4_rem-ubtu-24-200300", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/shadow\". \n \nAdd or update the following rule to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/shadow -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "ac-2.4_obj-ubtu-24-200310", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270687", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270687r1066550_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200310", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000018", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001403", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001404", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001405", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.", + "parts": [ + { + "id": "ac-2.4_dsc-ubtu-24-200310", + "name": "guidance", + "prose": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221" + } + ] + }, + { + "id": "ac-2.4_asm-ubtu-24-200310", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200310" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/gshadow\" with the following command: \n \n$ sudo auditctl -l | grep gshadow\n-w /etc/gshadow -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "ac-2.4_rem-ubtu-24-200310", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/gshadow\". \n \nAdd or update the following rule to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/gshadow -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "ac-2.4_obj-ubtu-24-200320", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270688", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270688r1066553_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200320", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000018", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001403", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001404", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001405", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.", + "parts": [ + { + "id": "ac-2.4_dsc-ubtu-24-200320", + "name": "guidance", + "prose": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. \n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221" + } + ] + }, + { + "id": "ac-2.4_asm-ubtu-24-200320", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200320" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/security/opasswd\" with the following command: \n \n$ sudo auditctl -l | grep opasswd \n-w /etc/security/opasswd -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "ac-2.4_rem-ubtu-24-200320", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/security/opasswd\". \n \nAdd or update the following rule to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/security/opasswd -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + } + ] + } + ] + }, + { + "control-id": "ac-3", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-3_obj-ubtu-24-102000", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270675", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270675r1137691_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-102000", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000213", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS when booted must require authentication upon booting into single-user and maintenance modes.", + "parts": [ + { + "id": "ac-3_dsc-ubtu-24-102000", + "name": "guidance", + "prose": "To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. \n \nSuccessful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. \n \nAccess control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system." + } + ] + }, + { + "id": "ac-3_asm-ubtu-24-102000", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-3_obj-ubtu-24-102000" + } + ], + "prose": "Verify Ubuntu 24.04 LTS requires a password for authentication upon booting into single-user and maintenance modes with the following command: \n \n$ sudo grep -i password /boot/grub/grub.cfg \npassword_pbkdf2 root grub.pbkdf2.sha512.10000.MFU48934NJA87HF8NSD34493GDHF84NG \n \nIf the root password entry does not begin with \"password_pbkdf2\", this is a finding." + }, + { + "id": "ac-3_rem-ubtu-24-102000", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system to require a password for authentication upon booting into single-user and maintenance modes. \n \nGenerate an encrypted (grub) password for root with the following command: \n \n$ grub-mkpasswd-pbkdf2 \nEnter Password: \nReenter Password: \nPBKDF2 hash of your password is grub.pbkdf2.sha512.10000.MFU48934NJD84NF8NSD39993JDHF84NG \n \nUsing the hash from the output, modify the \"/etc/grub.d/40_custom\" file with the following command to add a boot password: \n \n$ sudo sed -i '$i set superusers=\\\"root\\\"\\npassword_pbkdf2 root ' /etc/grub.d/40_custom \n \nwhere is the hash generated by grub-mkpasswd-pbkdf2 command. \n \nGenerate an updated \"grub.conf\" file with the new password by using the following command: \n \n$ sudo update-grub" + } + ] + } + ] + }, + { + "control-id": "ac-3.4", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-3.4_obj-ubtu-24-100500", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270659", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270659r1066466_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100500", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002165", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001764", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001774", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have AppArmor installed.", + "parts": [ + { + "id": "ac-3.4_dsc-ubtu-24-100500", + "name": "guidance", + "prose": "Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at Ubuntu 24.04 LTS-level. \n \nSome of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline. \n \nMethods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).\n\nSatisfies: SRG-OS-000312-GPOS-00124, SRG-OS-000368-GPOS-00154, SRG-OS-000370-GPOS-00155" + } + ] + }, + { + "id": "ac-3.4_asm-ubtu-24-100500", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-3.4_obj-ubtu-24-100500" + } + ], + "prose": "Verify Ubuntu 24.04 LTS has AppArmor installed with the following command:\n \n$ dpkg -l | grep apparmor\nii apparmor 4.0.1really4.0.1-0ubuntu0.24.04.3 amd64 user-space parser utility for AppArmor\nii libapparmor1:amd64 4.0.1really4.0.1-0ubuntu0.24.04.3 amd64 changehat AppArmor library\n \nIf the AppArmor package is not installed, this is a finding." + }, + { + "id": "ac-3.4_rem-ubtu-24-100500", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install \"AppArmor\" with the following command: \n \n$ sudo apt install apparmor \n \nNote: AppArmor must have properly configured profiles for applications and home directories. All configurations will be based on the actual system setup and organization and normally are on a per role basis. Refer to the AppArmor documentation for more information on configuring profiles." + } + ] + } + ] + }, + { + "control-id": "ac-6.10", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-7.2_obj-ubtu-24-100510" + } + ] + } + ] + }, + { + "control-id": "ac-6.8", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-6.8_obj-ubtu-24-200580", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270689", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270689r1066556_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200580", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002233", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002234", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004188", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must prevent all software from executing at higher privilege levels than users executing the software and the audit system must be configured to audit the execution of privileged functions.", + "parts": [ + { + "id": "ac-6.8_dsc-ubtu-24-200580", + "name": "guidance", + "prose": "In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations. \n \nSome programs and processes are required to operate at a higher privilege level and therefore, must be excluded from the organization-defined software list after review.\n\nSatisfies: SRG-OS-000326-GPOS-00126, SRG-OS-000327-GPOS-00127, SRG-OS-000755-GPOS-00220" + } + ] + }, + { + "id": "ac-6.8_asm-ubtu-24-200580", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-6.8_obj-ubtu-24-200580" + } + ], + "prose": "Verify Ubuntu 24.04 LTS audits the execution of privilege functions by auditing the \"execve\" system call with the following command: \n \n$ sudo auditctl -l | grep execve\n-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -F key=execpriv\n-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -F key=execpriv\n-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -F key=execpriv\n-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -F key=execpriv\n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "ac-6.8_rem-ubtu-24-200580", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to audit the execution of all privileged functions. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -F key=execpriv\n-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -F key=execpriv\n-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -F key=execpriv\n-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -F key=execpriv\n \nNotes: For 32-bit architectures, only the 32-bit specific entries are required. \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + } + ] + } + ] + }, + { + "control-id": "ac-6.9", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-6.8_obj-ubtu-24-200580" + } + ] + } + ] + }, + { + "control-id": "ac-7", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-7_obj-ubtu-24-200610", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270690", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270690r1067126_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200610", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000044", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002238", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts have been made.", + "parts": [ + { + "id": "ac-7_dsc-ubtu-24-200610", + "name": "guidance", + "prose": "By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account.\n\nSatisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128" + } + ] + }, + { + "id": "ac-7_asm-ubtu-24-200610", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-7_obj-ubtu-24-200610" + } + ], + "prose": "Verify that Ubuntu 24.04 LTS utilizes the \"pam_faillock\" module with the following command:\n\n$ grep faillock /etc/pam.d/common-auth \nauth [default=die] pam_faillock.so authfail\nauth sufficient pam_faillock.so authsucc\n\nIf the pam_faillock.so module is not present in the \"/etc/pam.d/common-auth\" file, this is a finding.\n\nVerify the pam_faillock module is configured to use the following options:\n\n$ sudo egrep 'silent|audit|deny|fail_interval| unlock_time' /etc/security/faillock.conf\naudit\nsilent\ndeny = 3\nfail_interval = 900\nunlock_time = 0\n\nIf the \"silent\" keyword is missing or commented out, this is a finding.\nIf the \"audit\" keyword is missing or commented out, this is a finding.\nIf the \"deny\" keyword is missing, commented out, or set to a value greater than \"3\", this is a finding.\nIf the \"fail_interval\" keyword is missing, commented out, or set to a value greater than \"900\", this is a finding.\nIf the \"unlock_time\" keyword is missing, commented out, or not set to \"0\", this is a finding." + }, + { + "id": "ac-7_rem-ubtu-24-200610", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to utilize the \"pam_faillock\" module. \n\nEdit the /etc/pam.d/common-auth file to add the following lines below the \"auth\" definition for pam_unix.so:\nauth [default=die] pam_faillock.so authfail\nauth sufficient pam_faillock.so authsucc\n\nConfigure the \"pam_faillock\" module to use the following options:\n\nEdit the /etc/security/faillock.conf file and add/update the following keywords and values:\naudit\nsilent\ndeny = 3\nfail_interval = 900\nunlock_time = 0" + } + ] + } + ] + }, + { + "control-id": "ac-8", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ac-8_obj-ubtu-24-200640", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270691", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270691r1066562_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200640", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000048", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001384", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001385", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001386", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001387", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001388", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must display the Standard Mandatory DOD Notice and Consent Banner before granting access to via an SSH logon.", + "parts": [ + { + "id": "ac-8_dsc-ubtu-24-200640", + "name": "guidance", + "prose": "Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. \n \nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. \n \nThe banner must be formatted in accordance with applicable DOD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: \n \n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \n \nBy using this IS (which includes any device attached to this IS), you consent to the following conditions: \n \n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. \n \n-At any time, the USG may inspect and seize data stored on this IS. \n \n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. \n \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\" \n \nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: \n \n\"I've read (literal ampersand) consent to terms in IS user agreem't.\"\n\nSatisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088" + } + ] + }, + { + "id": "ac-8_asm-ubtu-24-200640", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-8_obj-ubtu-24-200640" + } + ], + "prose": "Verify Ubuntu 24.04 LTS displays the Standard Mandatory DOD Notice and Consent Banner before granting access via an SSH logon with the following command: \n \n$ sudo grep -ir banner /etc/ssh/sshd_config* \n/etc/ssh/sshd_config:Banner /etc/issue.net\n \nThe command will return the banner option along with the name of the file that contains the SSH banner. If the line is commented out, missing, or conflicting results are returned, this is a finding.\n \nVerify the specified banner file matches the Standard Mandatory DOD Notice and Consent Banner exactly: \n \n$ cat /etc/issue.net \n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \n \nBy using this IS (which includes any device attached to this IS), you consent to the following conditions: \n \n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. \n \n-At any time, the USG may inspect and seize data stored on this IS. \n \n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. \n \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\" \n \nIf the banner text does not match the Standard Mandatory DOD Notice and Consent Banner exactly, this is a finding." + }, + { + "id": "ac-8_rem-ubtu-24-200640", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to display the Standard Mandatory DOD Notice and Consent Banner before granting access via an SSH logon.\n\nSet the parameter Banner in \"/etc/ssh/sshd_config\" to point to the \"/etc/issue.net\" file: \n \n$ sudo sed -i '/^Banner/d' /etc/ssh/sshd_config \n$ sudo sed -i '$aBanner /etc/issue.net' /etc/ssh/sshd_config \n \nEither create the file containing the banner or replace the text in the file with the Standard Mandatory DOD Notice and Consent Banner. The DOD required text is: \n \n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \n \nBy using this IS (which includes any device attached to this IS), you consent to the following conditions: \n \n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. \n \n-At any time, the USG may inspect and seize data stored on this IS. \n \n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. \n \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\" \n \nRestart the SSH daemon for the changes to take effect and then signal the SSH server to reload the configuration file: \n \n$ sudo systemctl -s SIGHUP kill sshd" + }, + { + "id": "ac-8_obj-ubtu-24-200650", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270692", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270692r1066565_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200650", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000048", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enable the graphical user logon banner to display the Standard Mandatory DOD Notice and Consent Banner before granting local access to the system via a graphical user logon.", + "parts": [ + { + "id": "ac-8_dsc-ubtu-24-200650", + "name": "guidance", + "prose": "Display of a standardized and approved use notification before granting access to Ubuntu 24.04 LTS ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. \n \nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. \n \nThe banner must be formatted in accordance with applicable DOD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: \n \n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \n \nBy using this IS (which includes any device attached to this IS), you consent to the following conditions: \n \n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. \n \n-At any time, the USG may inspect and seize data stored on this IS. \n \n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. \n \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\" \n \nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: \n \n\"I've read (literal ampersand) consent to terms in IS user agreem't.\"" + } + ] + }, + { + "id": "ac-8_asm-ubtu-24-200650", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-8_obj-ubtu-24-200650" + } + ], + "prose": "Note: If the system does not have a graphical user interface installed, this requirement is not applicable. \n\nVerify Ubuntu 24.04 LTS is configured to display the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 24.04 LTS via a graphical user logon with the following command: \n \n$ grep ^banner-message-enable /etc/gdm3/greeter.dconf-defaults\nbanner-message-enable=true\n \nIf the value for \"banner-message-enable\" is set to \"false\", the line is commented out, or no value is returned, this is a finding." + }, + { + "id": "ac-8_rem-ubtu-24-200650", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to display the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 24.04 LTS via a graphical user logon.\n\nEdit the \"/etc/gdm3/greeter.dconf-defaults\" file. \n \nLook for the \"banner-message-enable\" parameter under the \"[org/gnome/login-screen]\" section and uncomment it (remove the leading \"#\" characters): \n[org/gnome/login-screen] \nbanner-message-enable=true \n \nUpdate the GDM with the new configuration: \n \n$ sudo dconf update \n$ sudo systemctl restart gdm3" + }, + { + "id": "ac-8_obj-ubtu-24-200660", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270693", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270693r1066568_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200660", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000048", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must display the Standard Mandatory DOD Notice and Consent Banner before granting local access to the system via a graphical user logon.", + "parts": [ + { + "id": "ac-8_dsc-ubtu-24-200660", + "name": "guidance", + "prose": "Display of a standardized and approved use notification before granting access to Ubuntu 24.04 LTS ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. \n \nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. \n \nThe banner must be formatted in accordance with applicable DOD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: \n \n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \n \nBy using this IS (which includes any device attached to this IS), you consent to the following conditions: \n \n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. \n \n-At any time, the USG may inspect and seize data stored on this IS. \n \n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. \n \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\" \n \nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: \n \n\"I've read (literal ampersand) consent to terms in IS user agreem't.\"" + } + ] + }, + { + "id": "ac-8_asm-ubtu-24-200660", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-8_obj-ubtu-24-200660" + } + ], + "prose": "Note: If the system does not have a graphical user interface installed, this requirement is not applicable. \n\nVerify Ubuntu 24.04 LTS displays the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 24.04 LTS via a graphical user logon with the command: \n \n$ grep ^banner-message-text /etc/gdm3/greeter.dconf-defaults \nbanner-message-text=\"You are accessing a U.S. Government \\(USG\\) Information System \\(IS\\) that is provided for USG-authorized use only.\\s+By using this IS \\(which includes any device attached to this IS\\), you consent to the following conditions:\\s+-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct \\(PM\\), law enforcement \\(LE\\), and counterintelligence \\(CI\\) investigations.\\s+-At any time, the USG may inspect and seize data stored on this IS.\\s+-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\\s+-This IS includes security measures \\(e.g., authentication and access controls\\) to protect USG interests--not for your personal benefit or privacy.\\s+-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\" \n \nIf the banner-message-text is missing, commented out, or does not match the Standard Mandatory DOD Notice and Consent Banner exactly, this is a finding." + }, + { + "id": "ac-8_rem-ubtu-24-200660", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS displays the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 24.04 LTS via a graphical user logon.\n\nEdit the \"/etc/gdm3/greeter.dconf-defaults\" file. \n \nSet the \"banner-message-text\" line to contain the appropriate banner message text as shown below: \n \nbanner-message-text='You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\\n\\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\\n\\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\\n\\n-At any time, the USG may inspect and seize data stored on this IS.\\n\\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\\n\\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\\n\\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.' \n \nUpdate the GDM with the new configuration: \n \n$ sudo dconf update \n$ sudo systemctl restart gdm3" + }, + { + "id": "ac-8_obj-ubtu-24-200680", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270694", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270694r1066571_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200680", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000050", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured to enforce the acknowledgement of the Standard Mandatory DOD Notice and Consent Banner for all SSH connections.", + "parts": [ + { + "id": "ac-8_dsc-ubtu-24-200680", + "name": "guidance", + "prose": "The banner must be acknowledged by the user prior to allowing the user access to Ubuntu 24.04 LTS. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DOD will not be in compliance with system use notifications required by law. \n \nUbuntu 24.04 LTS must prevent further activity until the user executes a positive action to manifest agreement." + } + ] + }, + { + "id": "ac-8_asm-ubtu-24-200680", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-8_obj-ubtu-24-200680" + } + ], + "prose": "Verify Ubuntu 24.04 LTS is configured to prompt a user to acknowledge the Standard Mandatory DOD Notice and Consent Banner before granting access with the following command:\n\n$ less /etc/profile.d/ssh_confirm.sh\n#!/bin/bash\n\nif [ -n \"$SSH_CLIENT\" ] || [ -n \"$SSH_TTY\" ]; then\n while true; do\n read -p \" \n\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\n\nDo you agree? [y/N] \" yn\n case $yn in\n [Yy]* ) break ;;\n [Nn]* ) exit 1 ;;\n esac\n done\nfi\n\nIf the output does not match the text above, this is a finding." + }, + { + "id": "ac-8_rem-ubtu-24-200680", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to prompt a user to acknowledge the Standard Mandatory DOD Notice and Consent Banner before granting access:\n\n$ sudo vi /etc/profile.d/ssh_confirm.sh\n#!/bin/bash\n\nif [ -n \"$SSH_CLIENT\" ] || [ -n \"$SSH_TTY\" ]; then\n while true; do\n read -p \" \n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\n\nDo you agree? [y/N] \" yn\n case $yn in\n [Yy]* ) break ;;\n [Nn]* ) exit 1 ;;\n esac\n done\nfi\n\nNote: The \"ssh_confirm.sh\" script is provided as a supplemental file to this document." + } + ] + } + ] + }, + { + "control-id": "au-12", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100400" + }, + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100410" + }, + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200280" + }, + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200290" + }, + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200300" + }, + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200310" + }, + { + "rel": "assessment-objective", + "href": "#ac-2.4_obj-ubtu-24-200320" + }, + { + "rel": "assessment-objective", + "href": "#ma-4.1_obj-ubtu-24-500010" + } + ], + "parts": [ + { + "id": "au-12_obj-ubtu-24-900040", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270775", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270775r1068369_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900040", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000171", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that audit configuration files are not write-accessible by unauthorized users.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900040", + "name": "guidance", + "prose": "Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. \n \nMisconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900040", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900040" + } + ], + "prose": "Verify /etc/audit/audit.rules, /etc/audit/rules.d/*, and /etc/audit/auditd.conf files have a mode of \"0640\" or less permissive with the following command: \n \n$ sudo ls -al /etc/audit/ /etc/audit/rules.d/\n/etc/audit/: \n \n-rw-r----- 1 root root 804 Nov 25 11:01 auditd.conf \n -rw-r----- 1 root root 9128 Dec 27 09:56 audit.rules \n-rw-r----- 1 root root 127 Feb 7 2018 audit-stop.rules \n \ndrwxr-x--- 2 root root 4096 Dec 27 09:56 rules.d \n \n/etc/audit/rules.d/: \n\n -rw-r----- 1 root root 244 Dec 27 09:56 audit.rules \n-rw-r----- 1 root root 10357 Dec 27 09:56 stig.rules \n \nIf /etc/audit/audit.rule, /etc/audit/rules.d/*, or /etc/audit/auditd.conf files have a mode more permissive than \"0640\", this is a finding." + }, + { + "id": "au-12_rem-ubtu-24-900040", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure /etc/audit/audit.rules, /etc/audit/rules.d/*, and /etc/audit/auditd.conf files to have a mode of \"0640\" by using the following command: \n \n$ sudo chmod -R 0640 /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/*" + }, + { + "id": "au-12_obj-ubtu-24-900050", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270776", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270776r1066817_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900050", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000171", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must permit only authorized accounts to own the audit configuration files.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900050", + "name": "guidance", + "prose": "Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. \n \nMisconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900050", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900050" + } + ], + "prose": "Verify /etc/audit/audit.rules, /etc/audit/rules.d/*, and /etc/audit/auditd.conf files are owned by \"root\" account with the following command: \n \n$ sudo ls -al /etc/audit/ /etc/audit/rules.d/ \n/etc/audit/: \n \n-rw-r----- 1 root root 804 Nov 25 11:01 auditd.conf \n -rw-r----- 1 root root 9128 Dec 27 09:56 audit.rules \n-rw-r----- 1 root root 127 Feb 7 2018 audit-stop.rules \n \ndrwxr-x--- 2 root root 4096 Dec 27 09:56 rules.d \n \n/etc/audit/rules.d/: \n\n -rw-r----- 1 root root 244 Dec 27 09:56 audit.rules \n-rw-r----- 1 root root 10357 Dec 27 09:56 stig.rules \n \nIf the /etc/audit/audit.rules, /etc/audit/rules.d/*, or /etc/audit/auditd.conf file is owned by a user other than \"root\", this is a finding." + }, + { + "id": "au-12_rem-ubtu-24-900050", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure /etc/audit/audit.rules, /etc/audit/rules.d/*, and /etc/audit/auditd.conf files to be owned by \"root\" user by using the following command: \n \n$ sudo chown root /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/*" + }, + { + "id": "au-12_obj-ubtu-24-900060", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270777", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270777r1066820_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900060", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000171", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must permit only authorized groups to own the audit configuration files.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900060", + "name": "guidance", + "prose": "Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. \n \nMisconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900060", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900060" + } + ], + "prose": "Verify /etc/audit/audit.rules, /etc/audit/rules.d/*, and /etc/audit/auditd.conf files are owned by \"root\" group with the following command: \n \n$ sudo ls -al /etc/audit/ /etc/audit/rules.d/\n/etc/audit/: \n \n-rw-r----- 1 root root 804 Nov 25 11:01 auditd.conf \n -rw-r----- 1 root root 9128 Dec 27 09:56 audit.rules \n-rw-r----- 1 root root 127 Feb 7 2018 audit-stop.rules \n \ndrwxr-x--- 2 root root 4096 Dec 27 09:56 rules.d \n \n/etc/audit/rules.d/: \n\n -rw-r----- 1 root root 244 Dec 27 09:56 audit.rules \n-rw-r----- 1 root root 10357 Dec 27 09:56 stig.rules \n \nIf the \"/etc/audit/audit.rules\", \"/etc/audit/rules.d/*\", or \"/etc/audit/auditd.conf\" file is owned by a group other than \"root\", this is a finding." + }, + { + "id": "au-12_rem-ubtu-24-900060", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure /etc/audit/audit.rules, /etc/audit/rules.d/*, and /etc/audit/auditd.conf files to be owned by \"root\" group by using the following command: \n \n$ sudo chown :root /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/*" + }, + { + "id": "au-12_obj-ubtu-24-900070", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270778", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270778r1066823_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900070", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the su command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900070", + "name": "guidance", + "prose": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900070", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900070" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records upon successful/unsuccessful attempts to use the \"su\" command with the following command: \n \n$ sudo auditctl -l | grep /bin/su \n-a always,exit -F path=/bin/su -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-priv_change \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900070", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to generate audit records when successful/unsuccessful attempts to use the \"su\" command occur. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/bin/su -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-priv_change \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900080", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270779", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270779r1066826_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900080", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the chfn command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900080", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900080", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900080" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records upon successful/unsuccessful attempts to use the \"chfn\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/chfn \n-a always,exit -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-chfn \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900080", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"chfn\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-chfn \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900090", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270780", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270780r1066829_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900090", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the mount command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900090", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900090", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900090" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records upon successful/unsuccessful attempts to use the \"mount\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/mount \n-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-mount \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900090", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"mount\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-mount \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900100", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270781", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270781r1066832_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900100", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the umount command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900100", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900100", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900100" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records upon successful/unsuccessful attempts to use the \"umount\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/umount\n-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-umount \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900100", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"umount\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-umount \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900110", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270782", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270782r1066835_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900110", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the ssh-agent command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900110", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900110", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900110" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"ssh-agent\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/ssh-agent\n-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-ssh \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900110", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"ssh-agent\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-ssh \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900120", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270783", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270783r1066838_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900120", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the ssh-keysign command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900120", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900120", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900120" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"ssh-keysign\" command with the following command:\n \n$ sudo auditctl -l | grep ssh-keysign\n-a always,exit -F path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-ssh \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900120", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"ssh-keysign\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-ssh \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900130", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270784", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270784r1068371_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for any use of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900130", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n\nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206" + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900130", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900130" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"setxattr\", \"fsetxattr\", \"lsetxattr\", \"removexattr\", \"fremovexattr\", and \"lremovexattr\" system calls with the following command: \n \n$ sudo auditctl -l | grep xattr\n-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -k perm_mod \n-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod \n-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -k perm_mod \n-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod \n \nIf the command does not return audit rules for the \"setxattr\", \"fsetxattr\", \"lsetxattr\", \"removexattr\", \"fremovexattr\" and \"lremovexattr\" syscalls or the lines are commented out, this is a finding. \n \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900130", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"setxattr\", \"fsetxattr\", \"lsetxattr\", \"removexattr\", \"fremovexattr\", and \"lremovexattr\" system calls. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -k perm_mod \n-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod \n-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -k perm_mod \n-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required.\n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900140", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270785", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270785r1068373_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900140", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the chown, fchown, fchownat, and lchown system calls.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900140", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206" + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900140", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900140" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chown\", \"fchown\", \"fchownat\", and \"lchown\" system calls with the following command:\n \n$ sudo auditctl -l | grep chown\n-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k perm_chng \n-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k perm_chng \n \nIf the command does not return audit rules for the \"chown\", \"fchown\", \"fchownat\", and \"lchown\" syscalls or the lines are commented out, this is a finding. \n \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900140", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chown\", \"fchown\", \"fchownat\", and \"lchown\" system calls. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\": \n \n-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k perm_chng \n-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k perm_chng \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required. \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900150", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270786", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270786r1068375_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900150", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the chmod, fchmod, and fchmodat system calls.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900150", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206" + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900150", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900150" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chmod\", \"fchmod\", and \"fchmodat\" system calls with the following command: \n \n$ sudo auditctl -l | grep chmod\n-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k perm_chng \n-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k perm_chng \n \nIf the command does not return audit rules for the \"chmod\", \"fchmod\" and \"fchmodat\" syscalls or the lines are commented out, this is a finding. \n \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900150", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chmod\", \"fchmod\", and \"fchmodat\" system calls. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\": \n \n-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k perm_chng \n-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k perm_chng \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required. \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900160", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270787", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270787r1068378_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900160", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the creat, open, openat, open_by_handle_at, truncate, and ftruncate system calls.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900160", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000474-GPOS-00219" + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900160", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900160" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon unsuccessful attempts to use the \"creat\", \"open\", \"openat\", \"open_by_handle_at\", \"truncate\", and \"ftruncate\" system calls with the following command: \n \n$ sudo auditctl -l | grep 'open\\|truncate\\|creat'\n-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -k perm_access \n-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -k perm_access \n-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -k perm_access \n-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -k perm_access \n \nIf the command does not return audit rules for the \"creat\", \"open\", \"openat\", \"open_by_handle_at\", \"truncate\", and \"ftruncate\" syscalls or the lines are commented out, this is a finding. \n \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900160", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any unsuccessful use of the \"creat\", \"open\", \"openat\", \"open_by_handle_at\", \"truncate\", and \"ftruncate\" system calls. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -k perm_access \n-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -k perm_access \n-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -k perm_access \n-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -k perm_access \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required. \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900170", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270788", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270788r1066853_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900170", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the sudo command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900170", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900170", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900170" + } + ], + "prose": "Verify an audit event is generated for any successful/unsuccessful use of the \"sudo\" command with the following command:\n \n$ sudo auditctl -l | grep /usr/bin/sudo\n-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900170", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"sudo\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900180", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270789", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270789r1066856_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900180", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the sudoedit command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900180", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900180", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900180" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"sudoedit\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/sudoedit\n-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900180", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"sudoedit\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\": \n \n-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900190", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270790", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270790r1068380_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900190", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the chsh command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900190", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900190", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900190" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chsh\" command with the following command: \n \n$ sudo auditctl -l | grep chsh\n-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900190", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chsh\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900200", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270791", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270791r1066862_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900200", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the newgrp command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900200", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900200", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900200" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"newgrp\" command with the following command: \n \n$ sudo auditctl -l | grep newgrp\n-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900200", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"newgrp\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900210", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270792", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270792r1066865_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900210", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the chcon command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900210", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900210", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900210" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chcon\" command with the following command: \n \n$ sudo auditctl -l | grep chcon\n-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900210", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chcon\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900220", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270793", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270793r1066868_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900220", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the apparmor_parser command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900220", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900220", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900220" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"apparmor_parser\" command with the following command: \n \n$ sudo auditctl -l | grep apparmor_parser\n-a always,exit -F path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900220", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"apparmor_parser\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900230", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270794", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270794r1066871_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900230", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the setfacl command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900230", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900230", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900230" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"setfacl\" command with the following command: \n \n$ sudo auditctl -l | grep setfacl\n-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900230", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"setfacl\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900240", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270795", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270795r1066874_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900240", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the chacl command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900240", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900240", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900240" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chacl\" command with the following command: \n\n$ sudo audtctl -l | grep chacl\n-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900240", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chacl\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=-1 -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900250", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270796", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270796r1066877_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900250", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for the use and modification of faillog file.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900250", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218" + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900250", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900250" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record upon successful/unsuccessful modifications to the \"faillog\" file with the following command:\n \n$ sudo auditctl -l | grep faillog\n-w /var/log/faillog -p wa -k logins \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900250", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the \"faillog\" file. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/faillog -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900260", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270797", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270797r1066880_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900260", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for the use and modification of the lastlog file.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900260", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218" + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900260", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900260" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record when successful/unsuccessful modifications to the \"lastlog\" file occur with the following command: \n \n$ sudo auditctl -l | grep lastlog\n-w /var/log/lastlog -p wa -k logins \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900260", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the \"lastlog\" file. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/lastlog -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900270", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270798", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270798r1068382_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900270", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the passwd command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900270", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900270", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900270" + } + ], + "prose": "Verify that an audit event is generated for any successful/unsuccessful use of the \"passwd\" command with the following command: \n \n$ sudo auditctl -l | grep -w passwd\n-a always,exit -S all -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-passwd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900270", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"passwd\" command. \n \nAdd or update the following rule in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-passwd \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900280", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270799", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270799r1066886_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900280", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the unix_update command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900280", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900280", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900280" + } + ], + "prose": "Verify that an audit event is generated for any successful/unsuccessful use of the \"unix_update\" command with the following command: \n \n$ sudo auditctl -l | grep -w unix_update\n-a always,exit -F path=/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-unix-update \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900280", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"unix_update\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-unix-update \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900290", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270800", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270800r1066889_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900290", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the gpasswd command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900290", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900290", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900290" + } + ], + "prose": "Verify that an audit event is generated for any successful/unsuccessful use of the \"gpasswd\" command with the following command:\n \n$ sudo auditctl -l | grep -w gpasswd\n-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-gpasswd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900290", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"gpasswd\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-gpasswd \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900300", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270801", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270801r1066892_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900300", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the chage command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900300", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900300", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900300" + } + ], + "prose": "Verify that an audit event is generated for any successful/unsuccessful use of the \"chage\" command with the following command: \n \n$ sudo auditctl -l | grep -w chage\n-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-chage \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900300", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"chage\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-chage \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900310", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270802", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270802r1066895_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900310", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the usermod command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900310", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900310", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900310" + } + ], + "prose": "Verify an audit event is generated for any successful/unsuccessful use of the \"usermod\" command with the following command: \n \n$ sudo auditctl -l | grep -w usermod\n-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-usermod \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900310", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"usermod\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-usermod \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900320", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270803", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270803r1066898_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900320", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the crontab command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900320", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900320", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900320" + } + ], + "prose": "Verify an audit event is generated for any successful/unsuccessful use of the \"crontab\" command with the following command: \n \n$ sudo auditctl -l | grep -w crontab\n-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-crontab \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900320", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"crontab\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-crontab \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900330", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270804", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270804r1066901_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900330", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the pam_timestamp_check command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900330", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900330", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900330" + } + ], + "prose": "Verify an audit event is generated for any successful/unsuccessful use of the \"pam_timestamp_check\" command with the following command: \n \n$ sudo auditctl -l | grep -w pam_timestamp_check\n-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-pam_timestamp_check \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900330", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"pam_timestamp_check\" command. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=-1 -k privileged-pam_timestamp_check \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900340", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270805", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270805r1068384_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900340", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the init_module and finit_module syscalls.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900340", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000471-GPOS-00216" + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900340", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900340" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record for any successful/unsuccessful attempts to use the \"init_module\" and \"finit_module\" syscalls with the following command: \n \n$ sudo auditctl -l | grep init_module\n-a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -k module_chng \n-a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -k module_chng \n \nIf the command does not return audit rules for the \"init_module\" and \"finit_module\" syscalls or the lines are commented out, this is a finding.\n \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900340", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"init_module\" and \"finit_module\" syscalls. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -k module_chng \n-a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -k module_chng \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required. \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900350", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270806", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270806r1068386_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900350", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the delete_module syscall.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900350", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n\nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000477-GPOS-00222" + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900350", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900350" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates an audit record for any successful/unsuccessful attempts to use the \"delete_module\" syscall with the following command: \n \n$ sudo auditctl -l | grep -w delete_module\n-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=-1 -k module_chng \n-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=-1 -k module_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900350", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"delete_module\" syscall. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=-1 -k module_chng \n-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=-1 -k module_chng \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required. \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900510", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270807", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270807r1066910_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900510", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records when successful/unsuccessful attempts to modify the /etc/sudoers file occur.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900510", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900510", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900510" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records for all modifications that affect \"/etc/sudoers\" with the following command: \n \n$ sudo auditctl -l | grep sudoers\n-w /etc/sudoers -p wa -k privilege_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900510", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to generate audit records for all modifications that affect \"/etc/sudoers\". \n\nAdd or update the following rule to \"/etc/audit/rules.d/stig.rules\": \n\n-w /etc/sudoers -p wa -k privilege_modification \n\nTo reload the rules file, issue the following command: \n\n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900520", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270808", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270808r1067100_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900520", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records when successful/unsuccessful attempts to modify the /etc/sudoers.d directory occur.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900520", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.\n\nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900520", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900520" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records for all modifications that affect \"/etc/sudoers.d\" directory with the following command: \n \n$ sudo auditctl -l | grep sudoers.d\n-w /etc/sudoers.d -p wa -k privilege_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900520", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to generate audit records for all modifications that affect \"/etc/sudoers.d\" directory. \n\nAdd or update the following rule to \"/etc/audit/rules.d/stig.rules\": \n\n-w /etc/sudoers.d -p wa -k privilege_modification \n\nTo reload the rules file, issue the following command: \n\n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900540", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270809", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270809r1068388_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900540", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for any successful/unsuccessful use of unlink, unlinkat, rename, renameat, and rmdir system calls.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900540", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900540", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900540" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records for any successful/unsuccessful use of \"unlink\", \"unlinkat\", \"rename\", \"renameat\", and \"rmdir\" system calls with the following command:\n \n$ sudo auditctl -l | grep 'unlink\\|rename\\|rmdir'\n-a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -F key=delete \n-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -F key=delete \n \nIf the command does not return audit rules for the \"unlink\", \"unlinkat\", \"rename\", \"renameat\", and \"rmdir\" syscalls or the lines are commented out, this is a finding. \n \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900540", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate audit events for any successful/unsuccessful use of \"unlink\", \"unlinkat\", \"rename\", \"renameat\", and \"rmdir\" system calls. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file:\n \n-a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -k delete \n-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -k delete \n\nNote: For 32-bit architectures, only the 32-bit specific entries are required. \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900590", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270810", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270810r1066919_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900590", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for the /var/log/wtmp file.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900590", + "name": "guidance", + "prose": "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900590", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900590" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records showing start and stop times for user access to the system via the \"/var/log/wtmp\" file with the following command: \n \n$ sudo auditctl -l | grep '/var/log/wtmp'\n-w /var/log/wtmp -p wa -k logins \n \nIf the command does not return a line matching the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900590", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate audit events showing start and stop times for user access via the \"/var/log/wtmp\" file. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/wtmp -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900600", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270811", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270811r1066922_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900600", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for the /var/run/utmp file.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900600", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900600", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900600" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records showing start and stop times for user access to the system via the \"/var/run/utmp\" file with the following command:\n \n$ sudo auditctl -l | grep '/var/run/utmp'\n-w /var/run/utmp -p wa -k logins \n \nIf the command does not return a line matching the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900600", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate audit events showing start and stop times for user access via the \"/var/run/utmp\" file. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/run/utmp -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900610", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270812", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270812r1066925_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900610", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for the /var/log/btmp file.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900610", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900610", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900610" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records showing start and stop times for user access to the system via the \"/var/log/btmp\" file with the following command: \n \n$ sudo auditctl -l | grep '/var/log/btmp'\n-w /var/log/btmp -p wa -k logins \n \nIf the command does not return a line matching the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900610", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to generate audit events showing start and stop times for user access via the \"/var/log/btmp file\". \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/btmp -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900730", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270813", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270813r1066928_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900730", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records when successful/unsuccessful attempts to use modprobe command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900730", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900730", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900730" + } + ], + "prose": "Verify if Ubuntu 24.04 LTS is configured to audit the execution of the module management program \"modprobe\" with the following command: \n \n$ sudo auditctl -l | grep '/sbin/modprobe'\n-w /sbin/modprobe -p x -k modules \n \nIf the command does not return a line, or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900730", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to audit the execution of the module management program \"modprobe\". \n \nAdd or update the following rule in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /sbin/modprobe -p x -k modules \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900740", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270814", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270814r1066931_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900740", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records when successful/unsuccessful attempts to use the kmod command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900740", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900740", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900740" + } + ], + "prose": "Verify Ubuntu 24.04 LTS is configured to audit the execution of the module management program \"kmod\" with the following command: \n \n$ sudo auditctl -l | grep kmod\n-w /bin/kmod -p x -k module \n \nIf the command does not return a line, or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900740", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to audit the execution of the module management program \"kmod\". \n \nAdd or update the following rule in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /bin/kmod -p x -k modules \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-900750", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270815", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270815r1066934_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900750", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records when successful/unsuccessful attempts to use the fdisk command.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-900750", + "name": "guidance", + "prose": "Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter)." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-900750", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-900750" + } + ], + "prose": "Verify Ubuntu 24.04 LTS is configured to audit the execution of the partition management program \"fdisk\" with the following command: \n \n$ sudo auditctl -l | grep fdisk\n-w /usr/sbin/fdisk -p x -k fdisk \n \nIf the command does not return a line, or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "au-12_rem-ubtu-24-900750", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to audit the execution of the partition management program \"fdisk\". \n \nAdd or update the following rule in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /usr/sbin/fdisk -p x -k fdisk \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "au-12_obj-ubtu-24-200270", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-274870", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-274870r1155243_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200270", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must audit any script or executable called by cron as root or by any privileged user.", + "parts": [ + { + "id": "au-12_dsc-ubtu-24-200270", + "name": "guidance", + "prose": "Any script or executable called by cron as root or by any privileged user must be owned by that user, must have the permissions 755 or more restrictive, and should have no extended rights that allow any nonprivileged user to modify the script or executable." + } + ] + }, + { + "id": "au-12_asm-ubtu-24-200270", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-12_obj-ubtu-24-200270" + } + ], + "prose": "Verify Ubuntu 24.04 LTS is configured to audit the execution of any system call made by cron as root or as any privileged user.\n\n$ sudo auditctl -l | grep /etc/cron.d\n-w /etc/cron.d -p wa -k cronjobs\n\n$ sudo auditctl -l | grep /var/spool/cron\n-w /var/spool/cron -p wa -k cronjobs\n\nIf either of these commands does not return the expected output, or the lines are commented out, this is a finding." + }, + { + "id": "au-12_rem-ubtu-24-200270", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to audit the execution of any system call made by cron as root or as any privileged user.\n\nAdd or update the following file system rules to \"/etc/audit/rules.d/audit.rules\":\n-w /etc/cron.d/ -p wa -k cronjobs\n-w /var/spool/cron/ -p wa -k cronjobs\n\nTo load the rules to the kernel immediately, use the following command:\n\n$ sudo augenrules --load" + } + ] + } + ] + }, + { + "control-id": "au-12.3", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100400" + }, + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100410" + } + ] + } + ] + }, + { + "control-id": "au-14.1", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "au-14.1_obj-ubtu-24-102010", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270676", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270676r1155245_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-102010", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001464", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must initiate session audits at system startup.", + "parts": [ + { + "id": "au-14.1_dsc-ubtu-24-102010", + "name": "guidance", + "prose": "If auditing is enabled late in the startup process, the actions of some startup processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created." + } + ] + }, + { + "id": "au-14.1_asm-ubtu-24-102010", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-14.1_obj-ubtu-24-102010" + } + ], + "prose": "Verify Ubuntu 24.04 LTS enables auditing at system startup in GRUB. \n\nCheck the main GRUB defaults to ensure that auditing is enabled:\n$ sudo grep -ir GRUB_CMDLINE_LINUX /etc/default/grub\n/etc/default/grub:GRUB_CMDLINE_LINUX_DEFAULT=\"audit=1\"\n/etc/default/grub:GRUB_CMDLINE_LINUX=\"audit=1\"\n \nIf any linux lines do not contain \"audit=1\", this is a finding.\n\nCheck the generated GRUB configuration to ensure that the setting is propagated to the bootloader:\n$ sudo grep \"^\\s*linux\" /boot/grub/grub.cfg \nlinux /vmlinuz-6.8.0-31-generic root=UUID=c92a542f-aee4-4af9-94b2-203624ccb8e3 ro audit=1 quiet splash $vt_handoff\nlinux /vmlinuz-6.8.0-31-generic root=UUID=c92a542f-aee4-4af9-94b2-203624ccb8e3 ro recovery nomodeset dis_ucode_ldr audit=1\n \nIf any linux lines do not contain \"audit=1\", this is a finding.\n\nNote: Output details may vary by system." + }, + { + "id": "au-14.1_rem-ubtu-24-102010", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to produce audit records at system startup. \n \nEdit the \"/etc/default/grub\" file and add \"audit=1\" to the \"GRUB_CMDLINE_LINUX\" option and to the \"GRUB_CMDLINE_LINUX_DEFAULT\" option. \n\nGRUB_CMDLINE_LINUX_DEFAULT=\"audit=1\"\nGRUB_CMDLINE_LINUX=\"audit=1\"\n \nTo update the grub config file, run: \n \n$ sudo update-grub" + } + ] + } + ] + }, + { + "control-id": "au-3", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100400" + }, + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100410" + } + ] + } + ] + }, + { + "control-id": "au-3.1", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100400" + }, + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100410" + } + ] + } + ] + }, + { + "control-id": "au-4", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "au-4_obj-ubtu-24-900920", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270816", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270816r1066937_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900920", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001849", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must allocate audit record storage capacity to store at least one week's worth of audit records, when audit records are not immediately sent to a central audit record storage facility.", + "parts": [ + { + "id": "au-4_dsc-ubtu-24-900920", + "name": "guidance", + "prose": "To ensure operating systems have a sufficient storage capacity in which to write the audit logs, operating systems must be able to allocate audit record storage capacity. \n \nThe task of allocating audit record storage capacity is usually performed during initial installation of Ubuntu 24.04 LTS." + } + ] + }, + { + "id": "au-4_asm-ubtu-24-900920", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-4_obj-ubtu-24-900920" + } + ], + "prose": "Verify Ubuntu 24.04 LTS allocates audit record storage capacity to store at least one week's worth of audit records when audit records are not immediately sent to a central audit record storage facility. \n \nDetermine which partition the audit records are being written to with the following command: \n \n$ sudo grep ^log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log \n \nCheck the size of the partition that audit records are written to (with the example being \"/var/log/audit/\") with the following command: \n \n$ sudo df -h /var/log/audit/\n/dev/sda2 24G 10.4G 13.6G 43% /var/log/audit \n \nIf the audit records are not written to a partition made specifically for audit records (\"/var/log/audit\" is a separate partition), determine the amount of space being used by other files in the partition with the following command: \n \n$ sudo du -sh [audit_partition]\n1.8G /var/log/audit \n \nNote: The partition size needed to capture a week's worth of audit records is based on the activity level of the system and the total storage capacity available. \n \nIf the audit record partition is not allocated for sufficient storage capacity, this is a finding." + }, + { + "id": "au-4_rem-ubtu-24-900920", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Allocate enough storage capacity for at least one week's worth of audit records when audit records are not immediately sent to a central audit record storage facility. \n \nIf audit records are stored on a partition made specifically for audit records, use the \"parted\" program to resize the partition with sufficient space to contain one week's worth of audit records. \n \nIf audit records are not stored on a partition made specifically for audit records, a new partition with sufficient amount of space will need be to be created. \n \nSet the auditd server to point to the mount point where the audit records must be located: \n \n$ sudo sed -i -E 's@^(log_file\\s*=\\s*).*@\\1 /audit.log@' /etc/audit/auditd.conf \n \nwhere is the aforementioned mount point." + } + ] + } + ] + }, + { + "control-id": "au-4.1", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "au-4.1_obj-ubtu-24-100450", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270658", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270658r1067151_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100450", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001851", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS audit event multiplexor must be configured to offload audit logs onto a different system or storage media from the system being audited.", + "parts": [ + { + "id": "au-4.1_dsc-ubtu-24-100450", + "name": "guidance", + "prose": "Information stored in one location is vulnerable to accidental or incidental deletion or alteration. \n \nOffloading is a common process in information systems with limited audit storage capacity.\n\nSatisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224" + } + ] + }, + { + "id": "au-4.1_asm-ubtu-24-100450", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-4.1_obj-ubtu-24-100450" + } + ], + "prose": "Verify the audit event multiplexor is configured to offload audit records to a different system or storage media from the system being audited. \n \nCheck that audisp-remote plugin is installed:\n\n$ dpkg -l | grep audispd-plugins\nii audispd-plugins 1:3.1.2-2.1build1.1 amd64 Plugins for the audit event dispatcher \n\nIf the packet is \"not installed\", this is a finding. \n \nCheck that the records are being offloaded to a remote server with the following command: \n \n$ sudo grep -i active /etc/audit/plugins.d/au-remote.conf\nactive = yes \n \nIf \"active\" is not set to \"yes\", or the line is commented out, or is missing, this is a finding. \n \nCheck that audisp-remote plugin is configured to send audit logs to a different system: \n \n$ sudo grep -i ^remote_server /etc/audit/audisp-remote.conf\nremote_server = 192.168.122.126 \n \nIf the \"remote_server\" parameter is not set, is set with a local address, or is set with an invalid address, this is a finding." + }, + { + "id": "au-4.1_rem-ubtu-24-100450", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit event multiplexor to offload audit records to a different system or storage media from the system being audited. \n \nInstall the audisp-remote plugin: \n \n$ sudo apt install -y audispd-plugins\n \nSet the audisp-remote plugin as active by editing the \"/etc/audit/plugins.d/au-remote.conf\" file: \n \n$ sudo sed -i -E 's/active\\s*=\\s*no/active = yes/' /etc/audit/plugins.d/au-remote.conf \n \nSet the address of the remote machine by editing the \"/etc/audit/audisp-remote.conf\" file: \n \n$ sudo sed -i -E 's/(remote_server\\s*=).*/\\1 /' /etc/audit/audisp-remote.conf \n \nwhere must be substituted by the address of the remote server receiving the audit log. \n \nMake the audit service reload its configuration files: \n \n$ sudo systemctl restart auditd.service" + }, + { + "id": "au-4.1_obj-ubtu-24-900950", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270817", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270817r1066940_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900950", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001851", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have a crontab script running weekly to offload audit events of standalone systems.", + "parts": [ + { + "id": "au-4.1_dsc-ubtu-24-900950", + "name": "guidance", + "prose": "Information stored in one location is vulnerable to accidental or incidental deletion or alteration. \n \nOffloading is a common process in information systems with limited audit storage capacity." + } + ] + }, + { + "id": "au-4.1_asm-ubtu-24-900950", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-4.1_obj-ubtu-24-900950" + } + ], + "prose": "Note: If this is an interconnected system, this is not applicable.\n \nVerify there is a script that offloads audit data and that script runs weekly with the following command:\n\n$ ls /etc/cron.weekly \naudit-offload \n \nCheck if the script inside the file offloads audit logs to external media. \n \nIf the script file does not exist or does not offload audit logs, this is a finding." + }, + { + "id": "au-4.1_rem-ubtu-24-900950", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Create a script that offloads audit logs to external media and runs weekly. \n \nThe script must be located in the \"/etc/cron.weekly\" directory." + } + ] + } + ] + }, + { + "control-id": "au-5", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "au-5_obj-ubtu-24-900980", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270819", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270819r1068390_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900980", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000139", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must alert the system administrator (SA) and information system security officer (ISSO) (at a minimum) in the event of an audit processing failure.", + "parts": [ + { + "id": "au-5_dsc-ubtu-24-900980", + "name": "guidance", + "prose": "It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. \n \nAudit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. \n \nThis requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both." + } + ] + }, + { + "id": "au-5_asm-ubtu-24-900980", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-5_obj-ubtu-24-900980" + } + ], + "prose": "Verify that the SA and ISSO (at a minimum) are notified in the event of an audit processing failure with the following command: \n \n$ sudo grep '^action_mail_acct' /etc/audit/auditd.conf\naction_mail_acct = \n \nIf the value of the \"action_mail_acct\" keyword is not set to an account for security personnel, the returned line is commented out, or the keyword is missing, this is a finding." + }, + { + "id": "au-5_rem-ubtu-24-900980", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure \"auditd\" service to notify the SA and ISSO in the event of an audit processing failure. \n \nEdit the following line in \"/etc/audit/auditd.conf\" to ensure administrators are notified via email for those situations: \n \naction_mail_acct = \n \nNote: Change \"administrator_account\" to an account for security personnel. \n \nRestart the \"auditd\" service so the changes take effect: \n \n$ sudo systemctl restart auditd.service" + } + ] + } + ] + }, + { + "control-id": "au-5.1", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "au-5.1_obj-ubtu-24-900960", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270818", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270818r1066943_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-900960", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001855", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must immediately notify the system administrator (SA) and information system security officer (ISSO) (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.", + "parts": [ + { + "id": "au-5.1_dsc-ubtu-24-900960", + "name": "guidance", + "prose": "If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion." + } + ] + }, + { + "id": "au-5.1_asm-ubtu-24-900960", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-5.1_obj-ubtu-24-900960" + } + ], + "prose": "Verify Ubuntu 24.04 LTS notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity with the following command: \n \nNote: If the space_left_action is set to \"email\", an email package must be available.\n\n$ sudo grep ^space_left_action /etc/audit/auditd.conf\nspace_left_action email \n \n$ sudo grep ^space_left /etc/audit/auditd.conf\nspace_left 250000 \n \nIf the \"space_left\" parameter is set to \"syslog\", is missing, set to blanks, or set to a value less than 25 percent of the space free in the allocated audit record storage, this is a finding. \n \nIf the \"space_left_action\" parameter is missing or set to blanks, this is a finding. \n\nIf the \"space_left_action\" is set to \"email\", check the value of the \"action_mail_acct\" parameter with the following command: \n \n$ sudo grep ^action_mail_acct /etc/audit/auditd.conf\naction_mail_acct root@localhost \n \nThe \"action_mail_acct\" parameter, if missing, defaults to \"root\". If the \"action_mail_acct parameter\" is not set to the email address of the SA(s) and/or ISSO, this is a finding. \n \nIf the \"space_left_action\" is set to \"exec\", the system executes a designated script. If this script informs the SA of the event, this is not a finding." + }, + { + "id": "au-5.1_rem-ubtu-24-900960", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit \"/etc/audit/auditd.conf\" and set the \"space_left_action\" parameter to \"exec\" or \"email\". \n \nIf the \"space_left_action\" parameter is set to \"email\", set the \"action_mail_acct\" parameter to an email address for the SA and ISSO. \n \nIf the \"space_left_action\" parameter is set to \"exec\", ensure the command being executed notifies the SA and ISSO. \n \nEdit \"/etc/audit/auditd.conf\" and set the \"space_left\" parameter to be at least 25 percent of the repository maximum audit record storage capacity." + } + ] + } + ] + }, + { + "control-id": "au-6.4", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100400" + }, + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100410" + } + ] + } + ] + }, + { + "control-id": "au-7", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100400" + }, + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100410" + } + ] + } + ] + }, + { + "control-id": "au-7.1", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100400" + }, + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100410" + } + ] + } + ] + }, + { + "control-id": "au-8", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "au-8_obj-ubtu-24-901220", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270820", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270820r1066949_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901220", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001890", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).", + "parts": [ + { + "id": "au-8_dsc-ubtu-24-901220", + "name": "guidance", + "prose": "If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. \n \nTime stamps generated by Ubuntu 24.04 LTS include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC." + } + ] + }, + { + "id": "au-8_asm-ubtu-24-901220", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-8_obj-ubtu-24-901220" + } + ], + "prose": "Verify the time zone is configured to use UTC or GMT with the following command: \n \n$ timedatectl status | grep -i \"time zone\"\nTime zone: UTC (UTC, +0000) \n \nIf \"Timezone\" is not set to UTC or GMT, this is a finding." + }, + { + "id": "au-8_rem-ubtu-24-901220", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "To configure the system time zone to use UTC or GMT, run the following command, replacing [ZONE] with UTC or GMT: \n \n$ sudo timedatectl set-timezone [ZONE]" + } + ] + } + ] + }, + { + "control-id": "au-9", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "au-9_obj-ubtu-24-901230", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270821", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270821r1134818_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901230", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001494", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001493", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure audit tools with a mode of \"0755\" or less permissive.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901230", + "name": "guidance", + "prose": "Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. \n \nOperating systems providing tools to interface with audit information will leverage user permissions, roles identifying the user accessing the tools, and the corresponding user rights to make decisions regarding access to audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.\n\nSatisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000256-GPOS-00097" + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901230", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901230" + } + ], + "prose": "Verify Ubuntu 24.04 LTS configures the audit tools to have a file permission of \"0755\" or less to prevent unauthorized access with the following command: \n \n$ stat -c \"%n %a\" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd* /sbin/augenrules\n/sbin/auditctl 755 \n/sbin/aureport 755 \n/sbin/ausearch 755 \n/sbin/autrace 755 \n/sbin/auditd 755 \n/sbin/augenrules 755 \n \nIf any of the audit tools have a mode more permissive than \"0755\", this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901230", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit tools on Ubuntu 24.04 LTS to be protected from unauthorized access by setting the correct permissive mode using the following command: \n \n$ sudo chmod 0755 [audit_tool] \n \nReplace \"[audit_tool]\" with the audit tool that does not have the correct permissions." + }, + { + "id": "au-9_obj-ubtu-24-901240", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270822", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270822r1134821_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901240", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001494", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001493", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure audit tools to be owned by root.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901240", + "name": "guidance", + "prose": "Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. \n \nOperating systems providing tools to interface with audit information will leverage user permissions, roles identifying the user accessing the tools, and the corresponding user rights to make decisions regarding access to audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.\n\nSatisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000256-GPOS-00097" + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901240", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901240" + } + ], + "prose": "Verify Ubuntu 24.04 LTS configures the audit tools to be owned by root to prevent any unauthorized access with the following command: \n \n$ stat -c \"%n %U\" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd* /sbin/augenrules\n/sbin/auditctl root \n/sbin/aureport root \n/sbin/ausearch root \n/sbin/autrace root \n/sbin/auditd root \n/sbin/augenrules root \n \nIf any of the audit tools are not owned by root, this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901240", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit tools on Ubuntu 24.04 LTS to be protected from unauthorized access by setting the file owner as root using the following command: \n \n$ sudo chown root [audit_tool] \n \nReplace \"[audit_tool]\" with each audit tool not owned by root." + }, + { + "id": "au-9_obj-ubtu-24-901250", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270823", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270823r1134824_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901250", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001494", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001493", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the audit tools to be group owned by root.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901250", + "name": "guidance", + "prose": "Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. \n \nOperating systems providing tools to interface with audit information will leverage user permissions, roles identifying the user accessing the tools, and the corresponding user rights to make decisions regarding access to audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.\n\nSatisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000256-GPOS-00097" + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901250", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901250" + } + ], + "prose": "Verify Ubuntu 24.04 LTS configures the audit tools to be group owned by root to prevent any unauthorized access with the following command: \n \n$ stat -c \"%n %G\" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd* /sbin/augenrules\n/sbin/auditctl root \n/sbin/aureport root \n/sbin/ausearch root \n/sbin/autrace root \n/sbin/auditd root \n/sbin/augenrules root \n \nIf any of the audit tools are not group owned by root, this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901250", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit tools on Ubuntu 24.04 LTS to be protected from unauthorized access by setting the file group as root using the following command: \n \n$ sudo chown :root [audit_tool] \n \nReplace \"[audit_tool]\" with each audit tool not group owned by root." + }, + { + "id": "au-9_obj-ubtu-24-901260", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270824", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270824r1066961_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901260", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001495", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have directories that contain system commands set to a mode of \"0755\" or less permissive.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901260", + "name": "guidance", + "prose": "Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. \n \nOperating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user has to make access decisions regarding the deletion of audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators." + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901260", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901260" + } + ], + "prose": "Verify the system commands directories have mode \"0755\" or less permissive with the following command: \n \n$ find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec stat -c \"%n %a\" '{}' \\; \n \nIf any directories are found to be group-writable or world-writable, this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901260", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system commands directories to be protected from unauthorized access. Run the following command: \n \n$ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec chmod -R 755 '{}' \\;" + }, + { + "id": "au-9_obj-ubtu-24-901270", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270825", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270825r1066964_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901270", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001495", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have directories that contain system commands owned by root.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901270", + "name": "guidance", + "prose": "Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. \n \nOperating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user has to make access decisions regarding the deletion of audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators." + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901270", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901270" + } + ], + "prose": "Verify the system commands directories are owned by root with the following command: \n \n$ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec stat -c \"%n %U\" '{}' \\; \n \nIf any system commands directories are returned, this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901270", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system commands directories to be protected from unauthorized access. Run the following command: \n \n$ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec chown root '{}' \\;" + }, + { + "id": "au-9_obj-ubtu-24-901280", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270826", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270826r1066967_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901280", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001495", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have directories that contain system commands group-owned by root.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901280", + "name": "guidance", + "prose": "Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. \n \nOperating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user has to make access decisions regarding the deletion of audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators." + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901280", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901280" + } + ], + "prose": "Verify the system commands directories are group-owned by root with the following command: \n \n$ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec stat -c \"%n %G\" '{}' \\; \n \nIf any system commands directories are returned that are not Set Group ID up on execution (SGID) files and owned by a privileged account, this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901280", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system commands directories to be protected from unauthorized access. Run the following command: \n \n$ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec chgrp root '{}' \\;" + }, + { + "id": "au-9_obj-ubtu-24-901300", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270827", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270827r1066970_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901300", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000162", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000163", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that audit log files are not read or write-accessible by unauthorized users.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901300", + "name": "guidance", + "prose": "Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. \n \nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028" + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901300", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901300" + } + ], + "prose": "Verify that the audit log files have a mode of \"0600\" or less permissive. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, determine if the audit log files have a mode of \"0600\" or less with the following command: \n \n$ sudo stat -c \"%n %a\" /var/log/audit/*\n/var/log/audit/audit.log 600 \n \nIf the audit log files have a mode more permissive than \"0600\", this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901300", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit log files to have a mode of \"0600\" or less permissive. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw log_file /etc/audit/auditd.conf \n\nlog_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, configure the audit log files to have a mode of \"0600\" or less permissive by using the following command: \n \n$ sudo chmod 0600 /var/log/audit/*" + }, + { + "id": "au-9_obj-ubtu-24-901310", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270828", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270828r1066973_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901310", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000162", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000163", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000164", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured to permit only authorized users ownership of the audit log files.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901310", + "name": "guidance", + "prose": "Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. \n \nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029" + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901310", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901310" + } + ], + "prose": "Verify the audit log files are owned by \"root\" account. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, determine if the audit log files are owned by the \"root\" user with the following command: \n \n$ sudo stat -c \"%n %U\" /var/log/audit/*\n/var/log/audit/audit.log root \n \nIf the audit log files are owned by a user other than \"root\", this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901310", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit log directory and its underlying files to be owned by \"root\" user. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw log_file /etc/audit/auditd.conf \n\nlog_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, configure the audit log files to be owned by \"root\" user by using the following command: \n \n$ sudo chown root /var/log/audit/*" + }, + { + "id": "au-9_obj-ubtu-24-901350", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270829", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270829r1066976_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901350", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000162", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000163", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000164", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must permit only authorized groups ownership of the audit log files.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901350", + "name": "guidance", + "prose": "Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. \n \nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029" + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901350", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901350" + } + ], + "prose": "Verify the group owner is set to own newly created audit logs in the audit configuration file with the following command: \n\n$ sudo grep -iw log_group /etc/audit/auditd.conf\nlog_group = root \n\nIf the value of the \"log_group\" parameter is other than \"root\", this is a finding.\n\nDetermine where the audit logs are stored with the following command: \n\n$ sudo grep -iw log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log \n\nUsing the path of the directory containing the audit logs, determine if the audit log files are owned by the \"root\" group with the following command: \n\n$ sudo stat -c \"%n %G\" /var/log/audit/*\n/var/log/audit/audit.log root \n\nIf the audit log files are owned by a group other than \"root\", this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901350", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit log directory and its underlying files to be owned by \"root\" group.\n\nSet the \"log_group\" parameter of the audit configuration file to the \"root\" value so when a new log file is created, its group owner is properly set:\n\n$ sudo sed -i '/^log_group/D' /etc/audit/auditd.conf\n$ sudo sed -i /^log_file/a'log_group = root' /etc/audit/auditd.conf\n\nSignal the audit daemon to reload the configuration file to update the group owners of existing files:\n\n$ sudo systemctl kill auditd -s SIGHUP" + }, + { + "id": "au-9_obj-ubtu-24-901380", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270830", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270830r1068397_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-901380", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000164", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that the audit log directory is not write-accessible by unauthorized users.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-901380", + "name": "guidance", + "prose": "If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. \n \nTo ensure the veracity of audit information, Ubuntu 24.04 LTS must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. \n \nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity." + } + ] + }, + { + "id": "au-9_asm-ubtu-24-901380", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-901380" + } + ], + "prose": "Verify that the audit log directory has a mode of \"0750\" or less permissive. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw ^log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, determine if the directory has a mode of \"0750\" or less with the following command: \n \n$ sudo stat -c \"%n %a\" /var/log/audit\n/var/log/audit 750 \n \nIf the audit log directory has a mode more permissive than \"0750\", this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-901380", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit log directory to have a mode of \"0750\" or less permissive. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw ^log_file /etc/audit/auditd.conf \n\nlog_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, configure the audit log directory to have a mode of \"0750\" or less permissive by using the following command: \n \n$ sudo chmod -R 750 /var/log/audit" + }, + { + "id": "au-9_obj-ubtu-24-909000", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270832", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270832r1068399_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-909000", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000163", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS audit system must protect auditing rules from unauthorized change.", + "parts": [ + { + "id": "au-9_dsc-ubtu-24-909000", + "name": "guidance", + "prose": "Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit Ubuntu 24.04 LTS system activity. In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. A system reboot would be noticeable, and a system administrator could then investigate the unauthorized changes." + } + ] + }, + { + "id": "au-9_asm-ubtu-24-909000", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9_obj-ubtu-24-909000" + } + ], + "prose": "Verify the audit system prevents unauthorized changes to the rules with the following command:\n\n$ grep -E '^-e 2' /etc/audit/audit.rules\n-e 2\n\nIf the audit system is not set to be immutable by adding the \"-e 2\" option to the end of \"/etc/audit/audit.rules\", this is a finding." + }, + { + "id": "au-9_rem-ubtu-24-909000", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit system to set the audit rules to be immutable by adding the following line to the end of \"/etc/audit/rules.d/audit.rules\":\n\n-e 2" + } + ] + } + ] + }, + { + "control-id": "au-9.3", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "au-9.3_obj-ubtu-24-909890", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270831", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270831r1135002_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-909890", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001496", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must use cryptographic mechanisms to protect the integrity of audit tools.", + "parts": [ + { + "id": "au-9.3_dsc-ubtu-24-909890", + "name": "guidance", + "prose": "Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. \n \nIt is not uncommon for attackers to replace the audit tools or inject code into the existing tools with the purpose of providing the capability to hide or erase system activity from the audit logs. \n \nTo address this risk, audit tools must be cryptographically signed to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files." + } + ] + }, + { + "id": "au-9.3_asm-ubtu-24-909890", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#au-9.3_obj-ubtu-24-909890" + } + ], + "prose": "Verify that Advanced Intrusion Detection Environment (AIDE) is properly configured to use cryptographic mechanisms to protect the integrity of audit tools with the following command: \n \n$ egrep '(\\/sbin\\/(audit|au))' /etc/aide/aide.conf\n/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512 \n \nIf any of the seven audit tools do not have appropriate selection lines, this is a finding." + }, + { + "id": "au-9.3_rem-ubtu-24-909890", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Add or update the following selection lines for \"/etc/aide/aide.conf\" to protect the integrity of the audit tools: \n \n# Audit Tools \n/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512" + } + ] + } + ] + }, + { + "control-id": "cm-14", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "cm-14_obj-ubtu-24-300001", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270695", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270695r1066574_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300001", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-003992", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS Advance Package Tool (APT) must be configured to prevent the installation of patches, service packs, device drivers, or Ubuntu 24.04 LTS components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.", + "parts": [ + { + "id": "cm-14_dsc-ubtu-24-300001", + "name": "guidance", + "prose": "Changes to any software components can have significant effects on the overall security of Ubuntu 24.04 LTS. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor. \n \nAccordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization. \n \nVerifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. Ubuntu 24.04 LTS will not have to verify the software again. This requirement does not mandate DOD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA." + } + ] + }, + { + "id": "cm-14_asm-ubtu-24-300001", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-14_obj-ubtu-24-300001" + } + ], + "prose": "Verify that APT is configured to prevent the installation of patches, service packs, device drivers, or Ubuntu 24.04 LTS components without verification they have been digitally signed using a certificate recognized and approved by the organization with the following command: \n \n$ grep AllowUnauthenticated /etc/apt/apt.conf.d/* \n \nIf any files are returned from the command with \"AllowUnauthenticated\" are set to \"true\", this is a finding." + }, + { + "id": "cm-14_rem-ubtu-24-300001", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure APT to prevent the installation of patches, service packs, device drivers, or Ubuntu 24.04 LTS components without verification they have been digitally signed using a certificate recognized and approved by the organization. \n \nRemove/update any APT configuration files that contain the variable \"AllowUnauthenticated\" to \"false\" or remove \"AllowUnauthenticated\" entirely from each file. Below is an example of setting the \"AllowUnauthenticated\" variable to \"false\": \n \nAPT::Get::AllowUnauthenticated \"false\";" + } + ] + } + ] + }, + { + "control-id": "cm-3.5", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#si-6_obj-ubtu-24-100130" + } + ] + } + ] + }, + { + "control-id": "cm-5.1", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "cm-5.1_obj-ubtu-24-100400", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270656", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270656r1067148_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100400", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-003938", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001914", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000169", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000135", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000131", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000132", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000133", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000134", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000154", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000158", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001876", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001875", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001877", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001878", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001879", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001880", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001881", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001882", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have the \"auditd\" package installed.", + "parts": [ + { + "id": "cm-5.1_dsc-ubtu-24-100400", + "name": "guidance", + "prose": "Without establishing the when, where, type, source, and outcome of events that occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. \n \nWithout the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. \n \nReconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. \n \nSuccessful incident response and auditing relies on timely, accurate system information and analysis to allow the organization to identify and respond to potential incidents in a proficient manner. If Ubuntu 24.04 LTS does not provide the ability to centrally review Ubuntu 24.04 LTS logs, forensic analysis is negatively impacted. \n \nAssociating event types with detected events in Ubuntu 24.04 LTS audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.\n\nSatisfies: SRG-OS-000365-GPOS-00152, SRG-OS-000337-GPOS-00129, SRG-OS-000062-GPOS-00031, SRG-OS-000475-GPOS-00220, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000122-GPOS-00063, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142" + } + ] + }, + { + "id": "cm-5.1_asm-ubtu-24-100400", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100400" + } + ], + "prose": "Verify the audit service is configured to produce audit records with the following command: \n \n$ dpkg -l | grep auditd \nii auditd 1:3.0.7-1build1 amd64 User space tools for security auditing\n\nIf the \"auditd\" package is not installed, this is a finding." + }, + { + "id": "cm-5.1_rem-ubtu-24-100400", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit service to produce audit records containing the information needed to establish when (date and time) an event occurred. \n \nInstall the audit service (if the audit service is not already installed) with the following command: \n \n$ sudo apt install -y auditd" + }, + { + "id": "cm-5.1_obj-ubtu-24-100410", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270657", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270657r1066460_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100410", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-003938", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001914", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000169", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000135", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000131", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000132", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000133", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000134", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000154", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000158", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001876", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001875", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001877", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001878", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001879", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001880", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001881", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001882", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must produce audit records and reports containing information to establish when, where, what type, the source, and the outcome for all DOD-defined auditable events and actions in near real time.", + "parts": [ + { + "id": "cm-5.1_dsc-ubtu-24-100410", + "name": "guidance", + "prose": "Without establishing the when, where, type, source, and outcome of events that occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. \n \nWithout the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. \n \nReconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. \n \nSuccessful incident response and auditing relies on timely, accurate system information and analysis to allow the organization to identify and respond to potential incidents in a proficient manner. If Ubuntu 24.04 LTS does not provide the ability to centrally review Ubuntu 24.04 LTS logs, forensic analysis is negatively impacted. \n \nAssociating event types with detected events in Ubuntu 24.04 LTS audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.\n\nSatisfies: SRG-OS-000365-GPOS-00152, SRG-OS-000337-GPOS-00129, SRG-OS-000062-GPOS-00031, SRG-OS-000475-GPOS-00220, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000122-GPOS-00063, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142" + } + ] + }, + { + "id": "cm-5.1_asm-ubtu-24-100410", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.1_obj-ubtu-24-100410" + } + ], + "prose": "Verify the audit service is enabled with the following command: \n \n$ systemctl is-enabled auditd.service \nenabled\n\nIf the command above returns \"disabled\", this is a finding. \n \nVerify the audit service is properly running and active on the system with the following command: \n \n$ systemctl is-active auditd.service \nactive \n \nIf the command above returns \"inactive\", this is a finding." + }, + { + "id": "cm-5.1_rem-ubtu-24-100410", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the audit service to produce audit records containing the information needed to establish when (date and time) an event occurred. \n \nEnable the audit service with the following command: \n \n$ sudo systemctl enable auditd.service \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + } + ] + } + ] + }, + { + "control-id": "cm-5.6", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "cm-5.6_obj-ubtu-24-300006", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270696", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270696r1107306_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300006", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001499", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS library files must have mode 0755 or less permissive.", + "parts": [ + { + "id": "cm-5.6_dsc-ubtu-24-300006", + "name": "guidance", + "prose": "If Ubuntu 24.04 LTS were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications." + } + ] + }, + { + "id": "cm-5.6_asm-ubtu-24-300006", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.6_obj-ubtu-24-300006" + } + ], + "prose": "Verify the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" have mode 0755 or less permissive.\n\nCheck that the systemwide shared library files have mode 0755 or less permissive with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' -perm /022 -exec stat -c \"%n %a\" {} +\n\nIf any output is returned, this is a finding." + }, + { + "id": "cm-5.6_rem-ubtu-24-300006", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" to have mode 0755 or less permissive with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' -perm /022 -exec chmod go-w {} +" + }, + { + "id": "cm-5.6_obj-ubtu-24-300007", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270697", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270697r1107308_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300007", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001499", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS library files must be owned by root.", + "parts": [ + { + "id": "cm-5.6_dsc-ubtu-24-300007", + "name": "guidance", + "prose": "If Ubuntu 24.04 LTS were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications." + } + ] + }, + { + "id": "cm-5.6_asm-ubtu-24-300007", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.6_obj-ubtu-24-300007" + } + ], + "prose": "Verify the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" are owned by root with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' ! -user root -exec stat -c \"%n %U\" {} +\n\nIf any output is returned, this is a finding." + }, + { + "id": "cm-5.6_rem-ubtu-24-300007", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" to be owned by root with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' ! -user root -exec chown root {} +" + }, + { + "id": "cm-5.6_obj-ubtu-24-300008", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270698", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270698r1101751_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300008", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001499", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS library directories must be owned by root.", + "parts": [ + { + "id": "cm-5.6_dsc-ubtu-24-300008", + "name": "guidance", + "prose": "If Ubuntu 24.04 LTS were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications." + } + ] + }, + { + "id": "cm-5.6_asm-ubtu-24-300008", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.6_obj-ubtu-24-300008" + } + ], + "prose": "Verify the systemwide shared library directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" are owned by root with the following command: \n \n$ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec stat -c \"%n %U\" '{}' \\; \n \nIf any systemwide library directory is returned, this is a finding." + }, + { + "id": "cm-5.6_rem-ubtu-24-300008", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the library files and their respective parent directories to be protected from unauthorized access. Run the following command: \n \n$ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec chown root '{}' \\;" + }, + { + "id": "cm-5.6_obj-ubtu-24-300009", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270699", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270699r1107310_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300009", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001499", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS library files must be group-owned by root or a system account.", + "parts": [ + { + "id": "cm-5.6_dsc-ubtu-24-300009", + "name": "guidance", + "prose": "If Ubuntu 24.04 LTS were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications." + } + ] + }, + { + "id": "cm-5.6_asm-ubtu-24-300009", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.6_obj-ubtu-24-300009" + } + ], + "prose": "Verify the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" are group owned by root with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' ! -group root -exec stat -c \"%n %G\" {} +\n\nIf any output is returned, this is a finding." + }, + { + "id": "cm-5.6_rem-ubtu-24-300009", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" to be group owned by root with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' ! -group root -exec chown :root {} +" + }, + { + "id": "cm-5.6_obj-ubtu-24-300010", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270700", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270700r1066589_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300010", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001499", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS library directories must be group-owned by root.", + "parts": [ + { + "id": "cm-5.6_dsc-ubtu-24-300010", + "name": "guidance", + "prose": "If Ubuntu 24.04 LTS were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications." + } + ] + }, + { + "id": "cm-5.6_asm-ubtu-24-300010", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.6_obj-ubtu-24-300010" + } + ], + "prose": "Verify the systemwide library directories \"/lib\", \"/lib64\", and \"/usr/lib\" are group-owned by root with the following command: \n \n$ sudo find /lib /usr/lib /lib64 ! -group root -type d -exec stat -c \"%n %G\" '{}' \\; \n \nIf any systemwide shared library directory is returned, this is a finding." + }, + { + "id": "cm-5.6_rem-ubtu-24-300010", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system library directories to be protected from unauthorized access. Run the following command: \n \n$ sudo find /lib /usr/lib /lib64 ! -group root -type d -exec chgrp root '{}' \\;" + }, + { + "id": "cm-5.6_obj-ubtu-24-300011", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270701", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270701r1066592_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300011", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001499", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have system commands set to a mode of 0755 or less permissive.", + "parts": [ + { + "id": "cm-5.6_dsc-ubtu-24-300011", + "name": "guidance", + "prose": "If Ubuntu 24.04 LTS were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to Ubuntu 24.04 LTS with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications." + } + ] + }, + { + "id": "cm-5.6_asm-ubtu-24-300011", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.6_obj-ubtu-24-300011" + } + ], + "prose": "Verify the system commands contained in the following directories have mode 0755 or less permissive with the following command: \n \n$ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec stat -c \"%n %a\" '{}' \\; \n \nIf any files are found to be group-writable or world-writable, this is a finding." + }, + { + "id": "cm-5.6_rem-ubtu-24-300011", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system commands to be protected from unauthorized access. Run the following command: \n \n$ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec chmod 755 '{}' \\;" + }, + { + "id": "cm-5.6_obj-ubtu-24-300012", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270702", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270702r1066595_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300012", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001499", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have system commands owned by root or a system account.", + "parts": [ + { + "id": "cm-5.6_dsc-ubtu-24-300012", + "name": "guidance", + "prose": "If Ubuntu 24.04 LTS were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to Ubuntu 24.04 LTS with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications." + } + ] + }, + { + "id": "cm-5.6_asm-ubtu-24-300012", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.6_obj-ubtu-24-300012" + } + ], + "prose": "Verify the system commands contained in the following directories are owned by root, or a required system account, with the following command: \n \n$ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type f -exec stat -c \"%n %U\" '{}' \\; \n \nIf any system commands are returned and not owned by a required system account, this is a finding." + }, + { + "id": "cm-5.6_rem-ubtu-24-300012", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system commands and their respective parent directories to be protected from unauthorized access. Run the following command, replacing \"[FILE]\" with any system command file not owned by \"root\" or a required system account: \n \n$ sudo chown root [FILE]" + }, + { + "id": "cm-5.6_obj-ubtu-24-300013", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270703", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270703r1066598_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300013", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001499", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have system commands group-owned by root or a system account.", + "parts": [ + { + "id": "cm-5.6_dsc-ubtu-24-300013", + "name": "guidance", + "prose": "If Ubuntu 24.04 LTS were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to Ubuntu 24.04 LTS with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications." + } + ] + }, + { + "id": "cm-5.6_asm-ubtu-24-300013", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-5.6_obj-ubtu-24-300013" + } + ], + "prose": "Verify the system commands contained in the following directories are group-owned by root or a required system account with the following command: \n \n$ find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin \\-type f -perm -u=x -exec stat --format=\"%n %G\" {} + | \\awk '$2 != \"root\" && $2 != \"daemon\" && $2 != \"adm\" && $2 != \"shadow\" && $2 != \"mail\" && $2 != \"crontab\" && $2 != \"_ssh\"'\n\nNote: The above command uses awk to filter out common system accounts. If your system uses other required system accounts, add them to the awk condition to filter them out of the results.\n\nIf any system commands are returned that are not group-owned by a required system account, this is a finding." + }, + { + "id": "cm-5.6_rem-ubtu-24-300013", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system commands to be protected from unauthorized access. Run the following command, replacing \"[FILE]\" with any system command file not group-owned by \"root\" or a required system account: \n \n$ sudo chgrp [SYSTEMACCOUNT] [FILE]" + } + ] + } + ] + }, + { + "control-id": "cm-6", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "cm-6_obj-ubtu-24-100010", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270645", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270645r1068357_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100010", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must not have the \"systemd-timesyncd\" package installed.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-100010", + "name": "guidance", + "prose": "Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate. \n\nOrganizations must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints)." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-100010", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-100010" + } + ], + "prose": "Verify the \"systemd-timesyncd\" package is not installed with the following command:\n\n$ dpkg -l | grep systemd-timesyncd\n\nIf the \"systemd-timesyncd\" package is installed, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-100010", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "The \"systemd-timesyncd\" package will be uninstalled as part of the \"chrony\" package install. Purge the remaining configuration files for \"systemd-timesyncd\" from Ubuntu 24.04 LTS:\n\n$ sudo apt-get purge systemd-timesyncd" + }, + { + "id": "cm-6_obj-ubtu-24-100020", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270646", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270646r1068358_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100020", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must not have the \"ntp\" package installed.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-100020", + "name": "guidance", + "prose": "Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate. \n\nOrganizations must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints)." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-100020", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-100020" + } + ], + "prose": "Verify the \"ntp\" package is not installed with the following command:\n\n$ dpkg -l | grep ntp\n\nIf the \"ntp\" package is installed, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-100020", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Uninstall the \"ntp\" package using the following command:\n\n$ sudo apt remove ntp\n\nIf there are additional configuration files on the system that must be removed, the following command can be used instead:\n\n$ sudo apt-get purge ntp" + }, + { + "id": "cm-6_obj-ubtu-24-100600", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270661", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270661r1067175_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100600", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have the \"libpam-pwquality\" package installed.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-100600", + "name": "guidance", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \"pwquality\" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-100600", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-100600" + } + ], + "prose": "Verify Ubuntu 24.04 LTS has the \"libpam-pwquality\" package installed with the following command: \n \n$ dpkg -l | grep libpam-pwquality\nii libpam-pwquality:amd64 1.4.5-3build1 amd64 PAM module to check password strength \n \nIf \"libpam-pwquality\" is not installed, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-100600", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install the \"pam_pwquality\" package by using the following command: \n \n$ sudo apt install -y libpam-pwquality" + }, + { + "id": "cm-6_obj-ubtu-24-100700", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270664", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270664r1068359_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100700", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have the \"chrony\" package installed.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-100700", + "name": "guidance", + "prose": "Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate. \n\nOrganizations must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints)." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-100700", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-100700" + } + ], + "prose": "Verify the \"chrony\" package is installed using the following command:\n \n$ dpkg -l | grep chrony\nii chrony 4.5-1ubuntu4.1 amd64 Versatile implementation of the Network Time Protocol\n\nIf the \"chrony\" package is not installed, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-100700", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install the \"chrony\" network time protocol package using the following command:\n\n$ sudo apt install -y chrony" + }, + { + "id": "cm-6_obj-ubtu-24-300016", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270705", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270705r1066604_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300016", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that when passwords are changed or new passwords are established, pwquality must be used.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300016", + "name": "guidance", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \"pwquality\" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300016", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300016" + } + ], + "prose": "Verify that Ubuntu 24.04 LTS uses \"pwquality\" to enforce the password complexity rules. \n \nVerify the pwquality module is being enforced by Ubuntu 24.04 LTS with the following command: \n \n$ grep -i enforcing /etc/security/pwquality.conf\nenforcing = 1 \n \nIf the value of \"enforcing\" is not \"1\", or the line is commented out, this is a finding. \n \nCheck for the use of \"pwquality\" with the following command: \n \n$ cat /etc/pam.d/common-password | grep requisite | grep pam_pwquality\npassword requisite pam_pwquality.so retry=3 \n \nIf the value of \"retry\" is set to \"0\" or is greater than \"3\", or if a line is not returned, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300016", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to use \"pwquality\" to enforce password complexity rules. \n \nAdd the following line to \"/etc/security/pwquality.conf\" (or modify the line to have the required value): \n \nenforcing = 1 \n \nAdd the following line to \"/etc/pam.d/common-password\" (or modify the line to have the required value): \n \npassword requisite pam_pwquality.so retry=3 \n \nNote: Ensure the value of \"retry\" is between \"1\" and \"3\"." + }, + { + "id": "cm-6_obj-ubtu-24-300017", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270706", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270706r1068361_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300017", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300017", + "name": "guidance", + "prose": "Limiting the number of logon attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an account.\n\nThe delay option is set in microseconds." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300017", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300017" + } + ], + "prose": "Verify Ubuntu 24.04 LTS enforces a delay of at least four seconds between logon prompts following a failed logon attempt with the following command: \n \n$ grep pam_faildelay /etc/pam.d/common-auth\nauth required pam_faildelay.so delay=4000000\n \nIf the value for \"delay\" is not set to \"4000000\" or greater, the line is commented out, or is missing, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300017", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to enforce a delay of at least four seconds between logon prompts following a failed logon attempt. \n \nEdit the file \"/etc/pam.d/common-auth\" and set the parameter \"pam_faildelay\" to a value of \"4000000\" or greater: \n \nauth required pam_faildelay.so delay=4000000" + }, + { + "id": "cm-6_obj-ubtu-24-300021", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270707", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270707r1101786_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300021", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must require users to reauthenticate for privilege escalation or when changing roles.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300021", + "name": "guidance", + "prose": "Without reauthentication, users may access resources or perform tasks for which they do not have authorization.\n \nWhen operating systems provide the capability to escalate a functional capability, it is critical the user reauthenticate." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300021", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300021" + } + ], + "prose": "Verify the \"/etc/sudoers\" file has no occurrences of \"!authenticate\" with the following command: \n \n$ sudo egrep -iR '!authenticate' /etc/sudoers /etc/sudoers.d/\n \nIf any occurrences of \"!authenticate\" return from the command, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300021", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Remove any occurrence of \"!authenticate\" found in \"/etc/sudoers\" file or files in the \"/etc/sudoers.d\" directory." + }, + { + "id": "cm-6_obj-ubtu-24-300022", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270708", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270708r1066613_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300022", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300022", + "name": "guidance", + "prose": "The security risk of using X11 forwarding is that the client's X11 display server may be exposed to attack when the SSH client requests forwarding. A system administrator (SA) must protect clients that may expose themselves to attack by unwittingly requesting X11 forwarding, which can warrant a ''no'' setting. \n \nX11 forwarding must be enabled with caution. Users with the ability to bypass file permissions on the remote host (for the user's X11 authorization database) can access the local X11 display through the forwarded connection. An attacker may then be able to perform activities such as keystroke monitoring if the ForwardX11Trusted option is also enabled. \n \nIf X11 services are not required for the system's intended function, they must be disabled or restricted as appropriate to the system's needs." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300022", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300022" + } + ], + "prose": "Verify that X11Forwarding is disabled with the following command: \n \n$ sudo grep -ir x11forwarding /etc/ssh/sshd_config* | grep -v \"^#\"\nX11Forwarding no \n \nIf the \"X11Forwarding\" keyword is set to \"yes\" and is not documented with the information system security officer (ISSO) as an operational requirement, is missing, or multiple conflicting results are returned, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300022", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the \"X11Forwarding\" keyword and set its value to \"no\" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): \n \nX11Forwarding no \n \nRestart the SSH daemon for the changes to take effect: \n \n$ sudo systemctl restart sshd.service" + }, + { + "id": "cm-6_obj-ubtu-24-300023", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270709", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270709r1066616_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300023", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS SSH daemon must prevent remote hosts from connecting to the proxy display.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300023", + "name": "guidance", + "prose": "When X11 forwarding is enabled, there may be additional exposure to the server and client displays if the sshd proxy display is configured to listen on the wildcard address. By default, sshd binds the forwarding server to the loopback address and sets the hostname part of the DISPLAY environment variable to localhost. This prevents remote hosts from connecting to the proxy display." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300023", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300023" + } + ], + "prose": "Verify the SSH daemon prevents remote hosts from connecting to the proxy display with the following command:\n\n$ sudo grep -ir x11uselocalhost /etc/ssh/sshd_config*\nX11UseLocalhost yes\n\nIf the \"X11UseLocalhost\" keyword is set to \"no\", is commented out, is missing, or multiple conflicting results are returned, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300023", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the SSH daemon to prevent remote hosts from connecting to the proxy display. \n \nEdit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the \"X11UseLocalhost\" keyword and set its value to \"yes\" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): \n \nX11UseLocalhost yes \n \nRestart the SSH daemon for the changes to take effect: \n \n$ sudo systemctl restart sshd.service" + }, + { + "id": "cm-6_obj-ubtu-24-300025", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270711", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270711r1184069_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300025", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must disable the x86 Ctrl-Alt-Delete key sequence if a graphical user interface is installed.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300025", + "name": "guidance", + "prose": "A locally logged-on user who presses Ctrl-Alt-Delete, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In the graphical environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300025", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300025" + } + ], + "prose": "Verify Ubuntu 24.04 LTS is not configured to reboot the system when Ctrl-Alt-Delete is pressed when using a graphical user interface with the following command:\n\n$ gsettings get org.gnome.settings-daemon.plugins.media-keys logout\n@as []\n\nIf the \"logout\" key is bound to an action, is commented out, or is missing, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300025", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to disable the Ctrl-Alt-Delete sequence when using a graphical user interface.\n\nCreate or edit a file named /etc/dconf/db/local.d/00-mediakeys with the following contents:\n\n[org/gnome/settings-daemon/plugins/media-keys]\nlogout=@as []\n\nUpdate the dconf settings:\n\n$ sudo dconf update" + }, + { + "id": "cm-6_obj-ubtu-24-300026", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270712", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270712r1068363_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300026", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must disable the x86 Ctrl-Alt-Delete key sequence.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300026", + "name": "guidance", + "prose": "A locally logged-on user who presses Ctrl-Alt-Delete, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300026", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300026" + } + ], + "prose": "Verify Ubuntu 24.04 LTS is not configured to reboot the system when Ctrl-Alt-Delete is pressed with the following command:\n\n$ systemctl status ctrl-alt-del.target\no ctrl-alt-del.target\n Loaded: masked (Reason: Unit ctrl-alt-del.target is masked.)\n Active: inactive (dead)\n\nIf the \"ctrl-alt-del.target\" is not masked, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300026", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system to disable the Ctrl-Alt-Delete sequence for the command line with the following commands:\n\n$ sudo systemctl disable ctrl-alt-del.target\n[...]\n\n$ sudo systemctl mask ctrl-alt-del.target\nCreated symlink /etc/systemd/system/ctrl-alt-del.target ? /dev/null.\n\nReload the daemon to take effect: \n\n$ sudo systemctl daemon-reload" + }, + { + "id": "cm-6_obj-ubtu-24-300027", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270713", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270713r1066628_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300027", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must not have accounts configured with blank or null passwords.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300027", + "name": "guidance", + "prose": "If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords must never be used in operational environments." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300027", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300027" + } + ], + "prose": "Check the \"/etc/shadow\" file for blank passwords with the following command:\n\n$ sudo awk -F: '!$2 {print $1}' /etc/shadow\n\nIf the command returns any results, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300027", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure all accounts on the system to have a password or lock the account with the following commands:\n\nPerform a password reset:\n$ sudo passwd [username]\n\nLock an account:\n$ sudo passwd -l [username]" + }, + { + "id": "cm-6_obj-ubtu-24-300028", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270714", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270714r1134808_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300028", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must not allow accounts configured in Pluggable Authentication Modules (PAM) with blank or null passwords.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300028", + "name": "guidance", + "prose": "If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords must never be used in operational environments." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300028", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300028" + } + ], + "prose": "To verify null passwords cannot be used, run the following command: \n\n$ grep nullok /etc/pam.d/common-password /etc/pam.d/common-auth\n\nIf this produces any output, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300028", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "If an account is configured for password authentication but does not have an assigned password, it is possible to log on to the account without authenticating.\n\nRemove any instances of the \"nullok\" option in \"/etc/pam.d/common-password\" to prevent logons with empty passwords." + }, + { + "id": "cm-6_obj-ubtu-24-300029", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270715", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270715r1066634_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300029", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for all events that affect the systemd journal files.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300029", + "name": "guidance", + "prose": "Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to modify system level binaries and their operation. Auditing the systemd journal files provides logging that can be used for forensic purposes.\n \nTo address access requirements, many operating systems may be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300029", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300029" + } + ], + "prose": "Verify Ubuntu 24.04 LTS generates audit records for all events that affect \"/var/log/journal\" with the following command: \n \n$ sudo auditctl -l | grep journal\n-w /var/log/journal -p wa -k systemd_journal \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "cm-6_rem-ubtu-24-300029", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to generate audit records for events that affect \"/var/log/journal\". \n \nAdd or update the following rule to \"/etc/audit/rules.d/stig.rules\": \n \n-w /var/log/journal -p wa -k systemd_journal \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + }, + { + "id": "cm-6_obj-ubtu-24-300030", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270716", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270716r1066637_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300030", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS default filesystem permissions must be defined in such a way that all authenticated users can read and modify only their own files.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300030", + "name": "guidance", + "prose": "Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300030", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300030" + } + ], + "prose": "Verify Ubuntu 24.04 LTS defines default permissions for all authenticated users in such a way that the user can read and modify only their own files with the following command:\n \n$ grep -i '^\\s*umask' /etc/login.defs\nUMASK 077 \n \nIf the \"UMASK\" variable is set to \"000\", this is a finding with the severity raised to a CAT I. \n \nIf the value of \"UMASK\" is not set to \"077\", is commented out, or is missing, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300030", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system to define the default permissions for all authenticated users in such a way that the user can read and modify only their own files. \n \nEdit the \"UMASK\" parameter in the \"/etc/login.defs\" file to match the example below: \n \nUMASK 077" + }, + { + "id": "cm-6_obj-ubtu-24-300031", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270717", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270717r1067177_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300031", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must not allow unattended or automatic login via SSH.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300031", + "name": "guidance", + "prose": "Failure to restrict system access to authenticated users negatively impacts Ubuntu 24.04 LTS security." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300031", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300031" + } + ], + "prose": "Verify unattended or automatic login via SSH is disabled with the following command:\n\n$ egrep -r '(Permit(.*?)(Passwords|Environment))' /etc/ssh/sshd_config\nPermitEmptyPasswords no\nPermitUserEnvironment no\n\nIf the \"PermitEmptyPasswords\" or \"PermitUserEnvironment\" keywords are set to a value other than \"no\", are commented out, are both missing, or conflicting results are returned, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300031", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to allow the SSH daemon to not allow unattended or automatic login to the system. \n \nAdd or edit the following lines in the \"/etc/ssh/sshd_config\" file: \n \nPermitEmptyPasswords no \nPermitUserEnvironment no \n \nRestart the SSH daemon for the changes to take effect: \n \n$ sudo systemctl restart sshd.service" + }, + { + "id": "cm-6_obj-ubtu-24-300020", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-274868", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-274868r1107313_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300020", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must require users to provide a password for privilege escalation.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-300020", + "name": "guidance", + "prose": "Without reauthentication, users may access resources or perform tasks for which they do not have authorization.\n\nWhen operating systems provide the capability to escalate a functional capability, it is critical that the user reauthenticate.\n\nSatisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158" + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-300020", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-300020" + } + ], + "prose": "Verify that \"/etc/sudoers\" has no occurrences of \"NOPASSWD\" with the following command:\n\n$ sudo egrep -iR 'NOPASSWD' /etc/sudoers /etc/sudoers.d/\n\nIf any occurrences of \"NOPASSWD\" are returned from the command and have not been documented with the information system security officer (ISSO) as an organizationally defined administrative group using multifactor authentication (MFA), this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-300020", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the operating system to not allow users to execute privileged actions without authenticating with a password.\n\nRemove any occurrence of \"NOPASSWD\" found in \"/etc/sudoers\" file or files in the \"/etc/sudoers.d\" directory.\n\n$ sudo find /etc/sudoers /etc/sudoers.d -type f -exec sed -i '/NOPASSWD/ s/^/# /g' {} \\;" + }, + { + "id": "cm-6_obj-ubtu-24-700400", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-278917", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-278917r1155246_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700400", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000366", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be a vendor-supported release.", + "parts": [ + { + "id": "cm-6_dsc-ubtu-24-700400", + "name": "guidance", + "prose": "An operating system release is considered \"supported\" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security issues discovered in the system software.\n\nThe support status of the OS depends on its subscription status. \n\nEnd Of Life dates for Ubuntu 24.04 releases are as follows:\nStandard Support: April 2029\nExtended Security Maintenance (ESM): April 2036\n\nESM is available via an Ubuntu Pro subscription." + } + ] + }, + { + "id": "cm-6_asm-ubtu-24-700400", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-6_obj-ubtu-24-700400" + } + ], + "prose": "Verify the version of Ubuntu 24.04 LTS is vendor supported with the following command:\n\n$ grep DISTRIB_DESCRIPTION /etc/lsb-release\nDISTRIB_DESCRIPTION=\"Ubuntu 24.04.3 LTS\"\n\nCheck the subscription status of the system with the following command:\n$ pro status\n\nIf the installed version of Ubuntu 24.04 LTS is not supported, this is a finding." + }, + { + "id": "cm-6_rem-ubtu-24-700400", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Upgrade to a supported version of Ubuntu 24.04 LTS." + } + ] + } + ] + }, + { + "control-id": "cm-7", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "cm-7_obj-ubtu-24-100040", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270648", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270648r1066433_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100040", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000381", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must not have the rsh-server package installed.", + "parts": [ + { + "id": "cm-7_dsc-ubtu-24-100040", + "name": "guidance", + "prose": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore, may remain unsecured. They increase the risk to the platform by providing additional attack vectors. \n \nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n \nExamples of nonessential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled." + } + ] + }, + { + "id": "cm-7_asm-ubtu-24-100040", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-7_obj-ubtu-24-100040" + } + ], + "prose": "Verify the rsh-server package is installed with the following command: \n \n$ dpkg -l | grep rsh-server \n \nIf the rsh-server package is installed, this is a finding." + }, + { + "id": "cm-7_rem-ubtu-24-100040", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to disable nonessential capabilities by removing the rsh-server package from the system with the following command: \n \n$ sudo apt remove rsh-server" + }, + { + "id": "cm-7_obj-ubtu-24-300041", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270719", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270719r1067172_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300041", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000382", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management Category Assurance List (PPSM CAL) and vulnerability assessments.", + "parts": [ + { + "id": "cm-7_dsc-ubtu-24-300041", + "name": "guidance", + "prose": "To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems. \n \nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. \n \nTo support the requirements and principles of least functionality, Ubuntu 24.04 LTS must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues." + } + ] + }, + { + "id": "cm-7_asm-ubtu-24-300041", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-7_obj-ubtu-24-300041" + } + ], + "prose": "Check the firewall configuration for any unnecessary or prohibited functions, ports, protocols, and/or services with the following command:\n \n$ sudo ufw show raw \nChain OUTPUT (policy ACCEPT) \ntarget prot opt sources destination \nChain INPUT (policy ACCEPT 1 packets, 40 bytes) \n pkts bytes target prot opt in out source destination \n \nChain FORWARD (policy ACCEPT 0 packets, 0 bytes) \n pkts bytes target prot opt in out source destination \n \nChain OUTPUT (policy ACCEPT 0 packets, 0 bytes) \n pkts bytes target prot opt in out source destination \n \nAsk the system administrator for the site or program PPSM Components Local Services Assessment (CLSA). Verify the services allowed by the firewall match the PPSM CLSA. \n \nIf there are any additional ports, protocols, or services that are not included in the PPSM CLSA, this is a finding. \n \nIf there are any ports, protocols, or services that are prohibited by the PPSM CAL, this is a finding." + }, + { + "id": "cm-7_rem-ubtu-24-300041", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Add all ports, protocols, or services allowed by the PPSM CLSA by using the following command: \n \n$ sudo ufw allow \n \nWhere the direction is \"in\" or \"out\" and the port is the one corresponding to the protocol or service allowed. \n \nTo deny access to ports, protocols, or services, use: \n \n$ sudo ufw deny " + }, + { + "id": "cm-7_obj-ubtu-24-100050", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-279938", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-279938r1156367_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100050", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000381", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must not have the nfs-kernel-server package installed.", + "parts": [ + { + "id": "cm-7_dsc-ubtu-24-100050", + "name": "guidance", + "prose": "It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. \n \nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n \nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled." + } + ] + }, + { + "id": "cm-7_asm-ubtu-24-100050", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-7_obj-ubtu-24-100050" + } + ], + "prose": "Verify Ubuntu 24.04 LTS does not have nfs packages installed.\n\nCheck if packages are installed:\n$sudo dpkg -l | grep -E 'nfs-common | nfs-kernel-server'\n\nIf the nfs-common or nfs-kernel-server packages are installed, this is a finding" + }, + { + "id": "cm-7_rem-ubtu-24-100050", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to disable non-essential capabilities by removing the nfs-common and nfs-kernel-server packages from the system with the following commands:\n\nRemove packages if present:\n$ sudo apt purge --yes nfs-common nfs-kernel-server\n\nRemove any unneeded dependencies\n$ sudo apt autoremove --yes\n\nVerify NFS services are gone:\n$ sudo systemctl list-units --type=service | grep nfs" + } + ] + } + ] + }, + { + "control-id": "cm-7.2", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-3.4_obj-ubtu-24-100500" + } + ], + "parts": [ + { + "id": "cm-7.2_obj-ubtu-24-100510", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270660", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270660r1066469_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100510", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001764", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002235", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001774", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured to use AppArmor.", + "parts": [ + { + "id": "cm-7.2_dsc-ubtu-24-100510", + "name": "guidance", + "prose": "Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at Ubuntu 24.04 LTS-level. \n \nSome of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline. \n \nMethods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).\n\nSatisfies: SRG-OS-000368-GPOS-00154, SRG-OS-000324-GPOS-00125, SRG-OS-000370-GPOS-00155" + } + ] + }, + { + "id": "cm-7.2_asm-ubtu-24-100510", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-7.2_obj-ubtu-24-100510" + } + ], + "prose": "Verify Ubuntu 24.04 LTS AppArmor active with the following commands: \n \n$ systemctl is-active apparmor.service\nactive \n \nIf \"active\" is not returned, this is a finding. \n \n$ systemctl is-enabled apparmor.service \nenabled \n \nIf \"enabled\" is not returned, this is a finding." + }, + { + "id": "cm-7.2_rem-ubtu-24-100510", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Enable \"apparmor\" with the following command:\n \n$ sudo systemctl enable apparmor.service \n \nStart \"apparmor\" with the following command: \n \n$ sudo systemctl start apparmor.service \n \nNote: AppArmor must have properly configured profiles for applications and home directories. All configurations will be based on the actual system setup and organization and normally are on a per role basis. Refer to the AppArmor documentation for more information on configuring profiles." + } + ] + } + ] + }, + { + "control-id": "cm-7.5", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-3.4_obj-ubtu-24-100500" + }, + { + "rel": "assessment-objective", + "href": "#cm-7.2_obj-ubtu-24-100510" + } + ] + } + ] + }, + { + "control-id": "cm-7.9", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "cm-7.9_obj-ubtu-24-300039", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270718", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270718r1134811_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300039", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-003959", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001958", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must disable automatic mounting of Universal Serial Bus (USB) mass storage driver.", + "parts": [ + { + "id": "cm-7.9_dsc-ubtu-24-300039", + "name": "guidance", + "prose": "Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.\n\nPeripherals include, but are not limited to, devices such as flash drives, external storage, and printers.\n\nSatisfies: SRG-OS-000690-GPOS-00140, SRG-OS-000378-GPOS-00163" + } + ] + }, + { + "id": "cm-7.9_asm-ubtu-24-300039", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-7.9_obj-ubtu-24-300039" + } + ], + "prose": "Verify that Ubuntu 24.04 LTS disables the ability to load the USB storage kernel module with the following command:\n\n$ sudo grep usb-storage /etc/modprobe.d/* | grep \"/bin/false\" \n/etc/modprobe.d/DISASTIG.conf:install usb-storage /bin/false\n\nIf the command does not return any output, or the line is commented out, this is a finding.\n\nVerify Ubuntu 24.04 LTS disables the ability to use USB mass storage devices.\n\n$ sudo grep usb-storage /etc/modprobe.d/* | grep -i \"blacklist\"\n/etc/modprobe.d/DISASTIG.conf:blacklist usb-storage\n\nIf the command does not return any output, or the line is commented out, this is a finding." + }, + { + "id": "cm-7.9_rem-ubtu-24-300039", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to disable using the USB storage kernel module with the following command: \n\n$ sudo su -c \"echo install usb-storage /bin/false >> /etc/modprobe.d/DISASTIG.conf\"\n\nConfigure Ubuntu 24.04 LTS to disable the ability to use USB mass storage devices with the following command:\n\n$ sudo su -c \"echo blacklist usb-storage >> /etc/modprobe.d/DISASTIG.conf\"" + } + ] + } + ] + }, + { + "control-id": "ia-11", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ia-11_obj-ubtu-24-300019", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-274869", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-274869r1107312_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300019", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002038", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004895", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must restrict privilege elevation to authorized personnel.", + "parts": [ + { + "id": "ia-11_dsc-ubtu-24-300019", + "name": "guidance", + "prose": "If the \"sudoers\" file is not configured correctly, any user defined on the system can initiate privileged actions on the target system." + } + ] + }, + { + "id": "ia-11_asm-ubtu-24-300019", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-11_obj-ubtu-24-300019" + } + ], + "prose": "Verify the operating system restricts privilege elevation to authorized personnel with the following command:\n\n$ sudo grep -iwR 'ALL' /etc/sudoers /etc/sudoers.d/ | grep -v '#'\n\nIf either of the following entries are returned, this is a finding:\nALL ALL=(ALL) ALL\nALL ALL=(ALL:ALL) ALL" + }, + { + "id": "ia-11_rem-ubtu-24-300019", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the operating system to restrict privilege elevation to authorized personnel.\n\nRemove the following entries from the /etc/sudoers file or any configuration file under /etc/sudoers.d/:\n\nALL ALL=(ALL) ALL\nALL ALL=(ALL:ALL) ALL" + } + ] + } + ] + }, + { + "control-id": "ia-2", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ia-2_obj-ubtu-24-400000", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270720", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270720r1066649_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400000", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000764", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000804", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must uniquely identify interactive users.", + "parts": [ + { + "id": "ia-2_dsc-ubtu-24-400000", + "name": "guidance", + "prose": "To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. \n \nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n \n1) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and \n \n2) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.\n\nSatisfies: SRG-OS-000104-GPOS-00051, SRG-OS-000121-GPOS-00062" + } + ] + }, + { + "id": "ia-2_asm-ubtu-24-400000", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2_obj-ubtu-24-400000" + } + ], + "prose": "Verify Ubuntu 24.04 LTS contains no duplicate User IDs (UIDs) for interactive users with the following command: \n \n$ awk -F \":\" 'list[$3]++{print $1, $3}' /etc/passwd \n \nIf output is produced and the accounts listed are interactive user accounts, this is a finding." + }, + { + "id": "ia-2_rem-ubtu-24-400000", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Edit the file \"/etc/passwd\" and provide each interactive user account that has a duplicate UID with a unique UID." + } + ] + } + ] + }, + { + "control-id": "ia-2.1", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.6_obj-ubtu-24-100650" + }, + { + "rel": "assessment-objective", + "href": "#ia-2.6_obj-ubtu-24-100660" + } + ], + "parts": [ + { + "id": "ia-2.1_obj-ubtu-24-400020", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270721", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270721r1066652_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400020", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000765", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000766", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must implement smart card logins for multifactor authentication for local and network access to privileged and nonprivileged accounts.", + "parts": [ + { + "id": "ia-2.1_dsc-ubtu-24-400020", + "name": "guidance", + "prose": "Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. \n \nMultifactor authentication requires using two or more factors to achieve authentication. \n \nFactors include: \n1) Something a user knows (e.g., password/PIN); \n2) Something a user has (e.g., cryptographic identification device, token); and \n3) Something a user is (e.g., biometric). \n \nA privileged account is defined as an information system account with authorizations of a privileged user. \n \nNetwork access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). \n \nThe DOD common access card (CAC) with DOD-approved PKI is an example of multifactor authentication.\n\nSatisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000107-GPOS-00054, SRG-OS-000106-GPOS-00053, SRG-OS-000108-GPOS-00055" + } + ] + }, + { + "id": "ia-2.1_asm-ubtu-24-400020", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.1_obj-ubtu-24-400020" + } + ], + "prose": "Verify that the \"pam_pkcs11.so\" module is configured with the following command:\n\n$ grep -r pam_pkcs11.so /etc/pam.d/common-auth\nauth [success=2 default=ignore] pam_pkcs11.so\n\nIf the module is not configured, is missing, or commented out, this is a finding." + }, + { + "id": "ia-2.1_rem-ubtu-24-400020", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to use multifactor authentication for access to accounts. \n \nAdd or update \"pam_pkcs11.so\" in \"/etc/pam.d/common-auth\" to match the following line: \n \nauth [success=2 default=ignore] pam_pkcs11.so" + }, + { + "id": "ia-2.1_obj-ubtu-24-400030", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270722", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270722r1067130_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400030", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000765", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000766", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must implement smart card logins for multifactor authentication for local and network access to privileged and nonprivileged accounts over SSH.", + "parts": [ + { + "id": "ia-2.1_dsc-ubtu-24-400030", + "name": "guidance", + "prose": "Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. \n \nMultifactor authentication requires using two or more factors to achieve authentication. \n \nFactors include: \n1) Something a user knows (e.g., password/PIN); \n2) Something a user has (e.g., cryptographic identification device, token); and \n3) Something a user is (e.g., biometric). \n \nA privileged account is defined as an information system account with authorizations of a privileged user. \n \nNetwork access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). \n \nThe DOD common access card (CAC) with DOD-approved PKI is an example of multifactor authentication.\n\nSatisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000107-GPOS-00054, SRG-OS-000106-GPOS-00053, SRG-OS-000108-GPOS-00055" + } + ] + }, + { + "id": "ia-2.1_asm-ubtu-24-400030", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.1_obj-ubtu-24-400030" + } + ], + "prose": "Verify the sshd daemon allows public key authentication with the following command:\n \n$ sudo grep -r ^PubkeyAuthentication /etc/ssh/sshd_config*\n/etc/ssh/sshd_config:PubkeyAuthentication yes\n\nIf \"PubkeyAuthentication\" is not set to \"yes\", is commented out, is missing, or conflicting results are returned, this is a finding." + }, + { + "id": "ia-2.1_rem-ubtu-24-400030", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to use multifactor authentication for access to accounts. \n \nSet the sshd option \"PubkeyAuthentication\" to \"yes\" in the \"/etc/ssh/sshd_config\" file.\n\nPubkeyAuthentication yes" + } + ] + } + ] + }, + { + "control-id": "ia-2.12", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ia-2.12_obj-ubtu-24-100900", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270672", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270672r1067161_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100900", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001953", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must accept Personal Identity Verification (PIV) credentials.", + "parts": [ + { + "id": "ia-2.12_dsc-ubtu-24-100900", + "name": "guidance", + "prose": "The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. \n \nDOD has mandated the use of the common access card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems." + } + ] + }, + { + "id": "ia-2.12_asm-ubtu-24-100900", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.12_obj-ubtu-24-100900" + } + ], + "prose": "Verify the \"opensc-pcks11\" package is installed on the system with the following command: \n \n$ dpkg -l | grep opensc-pkcs11 \nii opensc-pkcs11:amd64 0.25.0~rc1-1build2 amd64 Smart card utilities with support for PKCS#15 compatible cards \n \nIf the \"opensc-pcks11\" package is not installed, this is a finding." + }, + { + "id": "ia-2.12_rem-ubtu-24-100900", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to accept PIV credentials. \n \nInstall the \"opensc-pkcs11\" package using the following command: \n \n$ sudo apt install -y opensc-pkcs11" + }, + { + "id": "ia-2.12_obj-ubtu-24-100910", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270673", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270673r1067164_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100910", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001953", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must accept Personal Identity Verification (PIV) credentials managed through the Privileged Access Management (PAM)  framework.", + "parts": [ + { + "id": "ia-2.12_dsc-ubtu-24-100910", + "name": "guidance", + "prose": "The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. \n \nDOD has mandated the use of the common access card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems." + } + ] + }, + { + "id": "ia-2.12_asm-ubtu-24-100910", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.12_obj-ubtu-24-100910" + } + ], + "prose": "Verify the \"libpam-pcks11\" package is installed on the system with the following command: \n \n$ dpkg -l | grep libpam-pkcs11 \nii libpam-pkcs11 0.6.12-2build3 amd64 Fully featured PAM module for using PKCS#11 smart cards\n \nIf the \"libpam-pcks11\" package is not installed, this is a finding." + }, + { + "id": "ia-2.12_rem-ubtu-24-100910", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to accept PIV credentials that are managed through the PAM framework. \n \nInstall the \"libpam-pkcs11\" package using the following command: \n \n$ sudo apt install -y libpam-pkcs11" + }, + { + "id": "ia-2.12_obj-ubtu-24-400060", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270723", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270723r1066658_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400060", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001954", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must electronically verify Personal Identity Verification (PIV) credentials.", + "parts": [ + { + "id": "ia-2.12_dsc-ubtu-24-400060", + "name": "guidance", + "prose": "The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. \n \nDOD has mandated the use of the common access card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems." + } + ] + }, + { + "id": "ia-2.12_asm-ubtu-24-400060", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.12_obj-ubtu-24-400060" + } + ], + "prose": "Verify Ubuntu 24.04 LTS electronically verifies PIV credentials via certificate status checking with the following command: \n \n$ sudo grep use_pkcs11_module /etc/pam_pkcs11/pam_pkcs11.conf | awk '/pkcs11_module opensc {/,/}/' /etc/pam_pkcs11/pam_pkcs11.conf | grep cert_policy | grep ocsp_on \n \ncert_policy = ca,signature,ocsp_on; \n \nIf every returned \"cert_policy\" line is not set to \"ocsp_on\", or the line is commented out, this is a finding." + }, + { + "id": "ia-2.12_rem-ubtu-24-400060", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to do certificate status checking for multifactor authentication. \n \nModify all of the \"cert_policy\" lines in \"/etc/pam_pkcs11/pam_pkcs11.conf\" to include \"ocsp_on\"." + } + ] + } + ] + }, + { + "control-id": "ia-2.2", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.6_obj-ubtu-24-100650" + }, + { + "rel": "assessment-objective", + "href": "#ia-2.6_obj-ubtu-24-100660" + }, + { + "rel": "assessment-objective", + "href": "#ia-2.1_obj-ubtu-24-400020" + }, + { + "rel": "assessment-objective", + "href": "#ia-2.1_obj-ubtu-24-400030" + } + ] + } + ] + }, + { + "control-id": "ia-2.5", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ia-2.5_obj-ubtu-24-400110", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270724", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270724r1066661_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400110", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004045", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must prevent direct login to the root account.", + "parts": [ + { + "id": "ia-2.5_dsc-ubtu-24-400110", + "name": "guidance", + "prose": "To ensure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated. \n \nA group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. Examples of the group authenticator are the Unix OS \"root\" user account, the Windows \"Administrator\" account, the \"sa\" account, or a \"helpdesk\" account. \n \nFor example, the Unix and Windows operating systems offer a \"switch user\" capability allowing users to authenticate with their individual credentials and, when needed, switch to the administrator role. This method provides for unique individual authentication prior to using a group authenticator. \n \nUsers (and any processes acting on behalf of users) need to be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization, which outlines specific user actions that can be performed on Ubuntu 24.04 LTS without identification or authentication. \n \nRequiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as adding an additional level of protection of the actions that can be taken with group account knowledge." + } + ] + }, + { + "id": "ia-2.5_asm-ubtu-24-400110", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.5_obj-ubtu-24-400110" + } + ], + "prose": "Verify Ubuntu 24.04 LTS prevents direct logins to the root account with the following command: \n \n$ sudo passwd -S root\nroot L 04/08/2024 0 99999 7 -1 \n \nIf the output does not contain \"L\" in the second field to indicate the account is locked, this is a finding." + }, + { + "id": "ia-2.5_rem-ubtu-24-400110", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to prevent direct logins to the root account by performing the following operations: \n \n$ sudo passwd -l root" + } + ] + } + ] + }, + { + "control-id": "ia-2.6", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ia-2.6_obj-ubtu-24-100650", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270662", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270662r1067156_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100650", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004046", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004047", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000765", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000766", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have the \"SSSD\" package installed.", + "parts": [ + { + "id": "ia-2.6_dsc-ubtu-24-100650", + "name": "guidance", + "prose": "Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. \n \nMultifactor authentication requires using two or more factors to achieve authentication. \n \nFactors include: \n1) Something a user knows (e.g., password/PIN); \n2) Something a user has (e.g., cryptographic identification device, token); and \n3) Something a user is (e.g., biometric). \n \nA privileged account is defined as an information system account with authorizations of a privileged user. \n \nNetwork access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). \n \nThe DOD common access card (CAC) with DOD-approved PKI is an example of multifactor authentication.\n\nSatisfies: SRG-OS-000705-GPOS-00150, SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160" + } + ] + }, + { + "id": "ia-2.6_asm-ubtu-24-100650", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.6_obj-ubtu-24-100650" + } + ], + "prose": "Verify Ubuntu 24.04 LTS has the packages required for multifactor authentication installed with the following command:\n\n$ dpkg -l | grep sssd\nii sssd 2.9.4-1.1ubuntu6.1 amd64 System Security Services Daemon -- metapackage\nii sssd-ad 2.9.4-1.1ubuntu6.1 amd64 System Security Services Daemon -- Active Directory back end\nii sssd-ad-common 2.9.4-1.1ubuntu6.1 amd64 System Security Services Daemon -- PAC responder\nii sssd-common 2.9.4-1.1ubuntu6.1 amd64 System Security Services Daemon -- common files\nii sssd-ipa 2.9.4-1.1ubuntu6.1 amd64 System Security Services Daemon -- IPA back end\nii sssd-krb5 2.9.4-1.1ubuntu6.1 amd64 System Security Services Daemon -- Kerberos back end\nii sssd-krb5-common 2.9.4-1.1ubuntu6.1 amd64 System Security Services Daemon -- Kerberos helpers\nii sssd-ldap 2.9.4-1.1ubuntu6.1 amd64 System Security Services Daemon -- LDAP back end\nii sssd-proxy 2.9.4-1.1ubuntu6.1 amd64 System Security Services Daemon -- proxy back end\n\nIf the \"sssd\" package is not installed, this is a finding. The additional sssd components listed by the command may differ from configuration to configuration. \n\nEnsure that \"libpam-sss\" (the PAM integration module for SSSD) is installed with the following command:\n\n$ dpkg -l | grep libpam-sss\ni libpam-sss:amd64 2.9.4-1.1ubuntu6.1 amd64 Pam module for the System Security Services Daemon\n\nEnsure that \"libnss-sss\" (the NSS module for retrieving user and group information) is installed with the following command:\n\n$ dpkg -l | grep libnss-sss\nii libnss-sss:amd64 2.9.4-1.1ubuntu6.1 amd64 Nss library for the System Security Services Daemon" + }, + { + "id": "ia-2.6_rem-ubtu-24-100650", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install the sssd.service and the required pam packages with the following commands: \n \n$ sudo apt install -y sssd\n\n$ sudo apt install -y libpam-sss\n\n$ sudo apt install -y libnss-sss" + }, + { + "id": "ia-2.6_obj-ubtu-24-100660", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270663", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270663r1066478_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100660", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004046", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004047", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000765", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000766", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must use the \"SSSD\" package for multifactor authentication services.", + "parts": [ + { + "id": "ia-2.6_dsc-ubtu-24-100660", + "name": "guidance", + "prose": "Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. \n \nMultifactor authentication requires using two or more factors to achieve authentication. \n \nFactors include: \n1) Something a user knows (e.g., password/PIN); \n2) Something a user has (e.g., cryptographic identification device, token); and \n3) Something a user is (e.g., biometric). \n \nA privileged account is defined as an information system account with authorizations of a privileged user. \n \nNetwork access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). \n \nThe DOD common access card (CAC) with DOD-approved PKI is an example of multifactor authentication.\n\nSatisfies: SRG-OS-000705-GPOS-00150, SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160" + } + ] + }, + { + "id": "ia-2.6_asm-ubtu-24-100660", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2.6_obj-ubtu-24-100660" + } + ], + "prose": "Verify the \"sssd.service\" is enabled and active with the following commands: \n \n$ sudo systemctl is-enabled sssd\nenabled\n\n$ sudo systemctl is-active sssd\nactive\n\nIf \"sssd.service\" is not active or enabled, this is a finding." + }, + { + "id": "ia-2.6_rem-ubtu-24-100660", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Enable the \"sssd.service to start automatically on reboot with the following command: \n \n$ sudo systemctl enable sssd.service \n \nensure the \"sssd\" service is running \n \n$ sudo systemctl start sssd.service" + } + ] + } + ] + }, + { + "control-id": "ia-3", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#cm-7.9_obj-ubtu-24-300039" + } + ], + "parts": [ + { + "id": "ia-3_obj-ubtu-24-200041", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-274872", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-274872r1107297_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-200041", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000778", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001958", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must prevent a user from overriding the disabling of the graphical user interface autorun function.", + "parts": [ + { + "id": "ia-3_dsc-ubtu-24-200041", + "name": "guidance", + "prose": "Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.\n\nSatisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227" + } + ] + }, + { + "id": "ia-3_asm-ubtu-24-200041", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-3_obj-ubtu-24-200041" + } + ], + "prose": "Note: This requirement assumes the use of the Ubuntu 24.04 LTS default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable.\n\nVerify Ubuntu 24.04 LTS disables ability of the user to override the graphical user interface autorun setting.\n\nDetermine which profile the system database is using with the following command:\n\n$ gsettings writable org.gnome.desktop.media-handling autorun-never\n \nfalse\n \nIf \"autorun-never\" is writable, the result is \"true\". If this is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding." + }, + { + "id": "ia-3_rem-ubtu-24-200041", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the Ubuntu 24.04 LTS GNOME desktop to not allow a user to change the setting that disables autorun on removable media.\n\nAdd the following line to \"/etc/dconf/db/local.d/locks/00-security-settings-lock\" to prevent user modification:\n\n/org/gnome/desktop/media-handling/autorun-never\n\nUpdate the dconf system databases:\n\n$ sudo dconf update" + } + ] + } + ] + }, + { + "control-id": "ia-5.1", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ia-5.1_obj-ubtu-24-100030", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270647", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270647r1066430_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100030", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000197", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must not have the telnet package installed.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-100030", + "name": "guidance", + "prose": "Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best. \n \nRemote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nUbuntu 24.04 LTS functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets)." + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-100030", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-100030" + } + ], + "prose": "Verify the telnet package is not installed on Ubuntu 24.04 LTS with the following command: \n \n$ dpkg -l | grep telnetd \n\nIf the telnetd package is installed, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-100030", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Remove the telnet package from Ubuntu 24.04 LTS with the following command: \n \n$ sudo apt remove telnetd" + }, + { + "id": "ia-5.1_obj-ubtu-24-300014", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270704", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270704r1066601_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-300014", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004061", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must prevent the use of dictionary words for passwords.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-300014", + "name": "guidance", + "prose": "Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof." + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-300014", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-300014" + } + ], + "prose": "Verify Ubuntu 24.04 LTS uses the \"cracklib\" library to prevent the use of dictionary words with the following command: \n \n$ grep dictcheck /etc/security/pwquality.conf\ndictcheck=1 \n \nIf the \"dictcheck\" parameter is not set to \"1\" or is commented out, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-300014", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to prevent the use of dictionary words for passwords. \n \nAdd or update the following line in the \"/etc/security/pwquality.conf\" file to include the \"dictcheck=1\" parameter: \n \ndictcheck=1" + }, + { + "id": "ia-5.1_obj-ubtu-24-400220", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270725", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270725r1101789_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400220", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004062", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must store only encrypted representations of passwords.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-400220", + "name": "guidance", + "prose": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements." + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-400220", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-400220" + } + ], + "prose": "Verify the Ubuntu operating system stores only encrypted representations of passwords with the following command:\n\n$ grep pam_unix.so /etc/pam.d/common-password\npassword [success=1 default=ignore] pam_unix.so obscure sha512 shadow rounds=100000\n\nIf \"sha512\" is missing from the \"pam_unix.so\" line, or if the \"rounds\" is set to less than 100000, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-400220", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to store encrypted representations of passwords.\n\nAdd or modify the \"sha512\" parameter value to the following line in \"/etc/pam.d/common-password\" file:\n\npassword [success=1 default=ignore] pam_unix.so obscure sha512 shadow rounds=100000" + }, + { + "id": "ia-5.1_obj-ubtu-24-400260", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270726", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270726r1066667_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400260", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004065", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004066", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enforce password complexity by requiring that at least one uppercase character be used.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-400260", + "name": "guidance", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \n \nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.\n\nSatisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000730-GPOS-00190" + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-400260", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-400260" + } + ], + "prose": "Verify Ubuntu 24.04 LTS enforces password complexity by requiring that at least one uppercase character be used with the following command: \n \n$ grep -i \"ucredit\" /etc/security/pwquality.conf\nucredit=-1 \n \nIf the \"ucredit\" parameter is greater than \"-1\", is commented out, or is missing, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-400260", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to enforce password complexity by requiring that at least one uppercase character be used. \n\nAdd or update the \"/etc/security/pwquality.conf\" file to contain the \"ucredit\" parameter: \n \nucredit=-1" + }, + { + "id": "ia-5.1_obj-ubtu-24-400270", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270727", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270727r1066670_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400270", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004065", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004066", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enforce password complexity by requiring that at least one lowercase character be used.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-400270", + "name": "guidance", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \n \nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.\n\nSatisfies: SRG-OS-000070-GPOS-00038, SRG-OS-000730-GPOS-00190" + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-400270", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-400270" + } + ], + "prose": "Verify Ubuntu 24.04 LTS enforces password complexity by requiring that at least one lowercase character be used with the following command: \n \n$ grep -i \"lcredit\" /etc/security/pwquality.conf\nlcredit=-1 \n \nIf the \"lcredit\" parameter is greater than \"-1\", is commented out, or is missing, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-400270", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to enforce password complexity by requiring that at least one lowercase character be used. \n\nAdd or update the \"/etc/security/pwquality.conf\" file to contain the \"lcredit\" parameter: \n \nlcredit=-1" + }, + { + "id": "ia-5.1_obj-ubtu-24-400280", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270728", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270728r1066673_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400280", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004065", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004066", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enforce password complexity by requiring that at least one numeric character be used.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-400280", + "name": "guidance", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \n \nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.\n\nSatisfies: SRG-OS-000071-GPOS-00039, SRG-OS-000730-GPOS-00190" + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-400280", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-400280" + } + ], + "prose": "Verify Ubuntu 24.04 LTS enforces password complexity by requiring that at least one numeric character be used. \n \nDetermine if the field \"dcredit\" is set in the \"/etc/security/pwquality.conf\" file with the following command: \n \n$ grep -i \"dcredit\" /etc/security/pwquality.conf\ndcredit=-1 \n \nIf the \"dcredit\" parameter is greater than \"-1\", is commented out, or is missing, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-400280", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to enforce password complexity by requiring that at least one numeric character be used. \n \nAdd or update the \"/etc/security/pwquality.conf\" file to contain the \"dcredit\" parameter: \n \ndcredit=-1" + }, + { + "id": "ia-5.1_obj-ubtu-24-400290", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270729", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270729r1066676_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400290", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004065", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004066", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must require the change of at least eight characters when passwords are changed.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-400290", + "name": "guidance", + "prose": "If Ubuntu 24.04 LTS allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks. \n \nThe number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different. \n \nIf the password length is an odd number, then number of changed characters must be rounded up. For example, a password length of 15 characters must require the change of at least eight characters.\n\nSatisfies: SRG-OS-000072-GPOS-00040, SRG-OS-000730-GPOS-00190" + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-400290", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-400290" + } + ], + "prose": "Verify Ubuntu 24.04 LTS requires the change of at least eight characters when passwords are changed with the following command:\n \n$ grep -i \"difok\" /etc/security/pwquality.conf\ndifok=8 \n \nIf the \"difok\" parameter is less than \"8\" or is commented out, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-400290", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to require the change of at least eight characters when passwords are changed. \n \nAdd or update the \"/etc/security/pwquality.conf\" file to include the \"difok=8\" parameter: \n \ndifok=8" + }, + { + "id": "ia-5.1_obj-ubtu-24-400300", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270730", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270730r1066679_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400300", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004065", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004066", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enforce 24 hours/1 day as the minimum password lifetime. Passwords for new users must have a 24 hours/1 day minimum password lifetime restriction.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-400300", + "name": "guidance", + "prose": "Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.\n\nSatisfies: SRG-OS-000075-GPOS-00043, SRG-OS-000730-GPOS-00190" + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-400300", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-400300" + } + ], + "prose": "Verify Ubuntu 24.04 LTS enforces a 24 hours/1 day minimum password lifetime for new user accounts with the following command: \n \n$ grep -i ^PASS_MIN_DAYS /etc/login.defs \nPASS_MIN_DAYS 1 \n \nIf the \"PASS_MIN_DAYS\" parameter value is less than \"1\" or is commented out, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-400300", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to enforce a 24 hours/1 day minimum password lifetime. \n \nAdd or modify the following line in the \"/etc/login.defs\" file: \n \nPASS_MIN_DAYS 1" + }, + { + "id": "ia-5.1_obj-ubtu-24-400310", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270731", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270731r1066682_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400310", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004065", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004066", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enforce a 60-day maximum password lifetime restriction. Passwords for new users must have a 60-day maximum password lifetime restriction.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-400310", + "name": "guidance", + "prose": "Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If Ubuntu 24.04 LTS does not limit the lifetime of passwords and force users to change their passwords, there is the risk that Ubuntu 24.04 LTS passwords could be compromised.\n\nSatisfies: SRG-OS-000076-GPOS-00044, SRG-OS-000730-GPOS-00190" + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-400310", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-400310" + } + ], + "prose": "Verify Ubuntu 24.04 LTS enforces a 60-day maximum password lifetime for new user accounts with the following command:\n \n$ grep -i ^PASS_MAX_DAYS /etc/login.defs\nPASS_MAX_DAYS 60 \n \nIf the \"PASS_MAX_DAYS\" parameter value is less than \"60\" or is commented out, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-400310", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to enforce a 60-day maximum password lifetime. \n \nAdd or modify the following line in the \"/etc/login.defs\" file: \n \nPASS_MAX_DAYS 60" + }, + { + "id": "ia-5.1_obj-ubtu-24-400320", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270732", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270732r1066685_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400320", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004065", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004066", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enforce a minimum 15-character password length.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-400320", + "name": "guidance", + "prose": "The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. \n \nPassword complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.\n\nSatisfies: SRG-OS-000078-GPOS-00046, SRG-OS-000730-GPOS-00190" + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-400320", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-400320" + } + ], + "prose": "Verify the pwquality configuration file enforces a minimum 15-character password length with the following command:\n\n$ grep -i minlen /etc/security/pwquality.conf\nminlen=15\n\nIf \"minlen\" parameter value is not \"15\" or higher, is commented out, or is missing, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-400320", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to enforce a minimum 15-character password length. \n \nAdd or modify the \"minlen\" parameter value to the \"/etc/security/pwquality.conf\" file: \n \nminlen=15" + }, + { + "id": "ia-5.1_obj-ubtu-24-400330", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270733", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270733r1066688_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400330", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004065", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004066", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must enforce password complexity by requiring that at least one special character be used.", + "parts": [ + { + "id": "ia-5.1_dsc-ubtu-24-400330", + "name": "guidance", + "prose": "Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity or strength is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \n \nPassword complexity is one factor in determining how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. \n \nSpecial characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.\n\nSatisfies: SRG-OS-000266-GPOS-00101, SRG-OS-000730-GPOS-00190" + } + ] + }, + { + "id": "ia-5.1_asm-ubtu-24-400330", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.1_obj-ubtu-24-400330" + } + ], + "prose": "Determine if the field \"ocredit\" is set in the \"/etc/security/pwquality.conf\" file with the following command: \n \n$ grep -i \"ocredit\" /etc/security/pwquality.conf\nocredit=-1 \n \nIf the \"ocredit\" parameter is greater than \"-1\", is commented out, or is missing, this is a finding." + }, + { + "id": "ia-5.1_rem-ubtu-24-400330", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to enforce password complexity by requiring that at least one special character be used. \n \nAdd or update the following line in the \"/etc/security/pwquality.conf\" file to include the \"ocredit=-1\" parameter: \n \nocredit=-1" + } + ] + } + ] + }, + { + "control-id": "ia-5.13", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ia-5.13_obj-ubtu-24-400340", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270734", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270734r1155240_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400340", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002007", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured such that Pluggable Authentication Module (PAM) prohibits the use of cached authentications after one day.", + "parts": [ + { + "id": "ia-5.13_dsc-ubtu-24-400340", + "name": "guidance", + "prose": "If cached authentication information is out-of-date, the validity of the authentication information may be questionable." + } + ] + }, + { + "id": "ia-5.13_asm-ubtu-24-400340", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.13_obj-ubtu-24-400340" + } + ], + "prose": "Note: If smart card authentication is not being used on the system, this requirement is not applicable. \n\nVerify PAM prohibits the use of cached authentications after one day with the following command:\n \n$ sudo grep offline_credentials_expiration /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf \noffline_credentials_expiration = 1 \n \nIf \"offline_credentials_expiration\" in \"/etc/sssd/sssd.conf\" or in a file with a name ending in .conf in the \"/etc/sssd/conf.d/\" directory, is not set to \"1\", is commented out, is missing, or conflicting results are returned, this is a finding." + }, + { + "id": "ia-5.13_rem-ubtu-24-400340", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure PAM to prohibit the use of cached authentications after one day. Add or change the following line in \"/etc/sssd/sssd.conf\" just below the line \"[pam]\": \n \noffline_credentials_expiration = 1 \n \nNote: It is valid for this configuration to be in a file with a name that ends with \".conf\" and does not begin with a \".\" in the \"/etc/sssd/conf.d/\" directory instead of the \"/etc/sssd/sssd.conf\" file." + } + ] + } + ] + }, + { + "control-id": "ia-5.2", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ia-5.2_obj-ubtu-24-400360", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270735", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270735r1066694_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400360", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000185", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004909", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS, for PKI-based authentication, SSSD must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.", + "parts": [ + { + "id": "ia-5.2_dsc-ubtu-24-400360", + "name": "guidance", + "prose": "Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. \n \nA trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. \n \nWhen there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a certification authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. \n \nThis requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.\n\nSatisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000775-GPOS-00230" + } + ] + }, + { + "id": "ia-5.2_asm-ubtu-24-400360", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.2_obj-ubtu-24-400360" + } + ], + "prose": "Verify Ubuntu 24.04 LTS, for PKI-based authentication, has valid certificates by constructing a certification path to an accepted trust anchor. \n\nEnsure the pam service is listed under [sssd] with the following command:\n\n$ sudo grep -A 1 '^\\[sssd\\]' /etc/sssd/sssd.conf\n[sssd]\nservices = nss,pam,ssh\n\nIf \"pam\" is not listed in services, this is a finding.\n\nAdditionally, ensure the pam service is set to use pam for smart card authentication in the [pam] section of /etc/sssd/sssd.conf with the following command:\n\n$ sudo grep -A 1 '^\\[pam]' /etc/sssd/sssd.conf\n[pam]\npam_cert_auth = True\n\nIf \"pam_cert_auth = True\" is not returned, this is a finding.\n\nEnsure \"ca\" is enabled in \"certificate_verification\" with the following command: \n \n$ sudo grep certificate_verification /etc/sssd/sssd.conf\ncertificate_verification = ca_cert,ocsp\n \nIf \"certificate_verification\" is not set to \"ca\" or the line is commented out, this is a finding." + }, + { + "id": "ia-5.2_rem-ubtu-24-400360", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS, for PKI-based authentication, to validate certificates by constructing a certification path to an accepted trust anchor. \n \nAdd or update the /etc/sssd/sssd.conf so that the following entries are in the correct sections of the file: \n \n$ sudo vi /etc/sssd/sssd.conf\n\n[sssd]\nservices = nss,pam,ssh\nconfig_file_version = 2\n\n[pam]\npam_cert_auth = True\n\n[domain/example.com]\nldap_user_certificate = usercertificate;binary\ncertificate_verification = ca_cert,ocsp\nca_cert = /etc/ssl/certs/ca-certificates.crt" + }, + { + "id": "ia-5.2_obj-ubtu-24-400370", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270736", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270736r1066697_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400370", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000187", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must map the authenticated identity to the user or group account for PKI-based authentication.", + "parts": [ + { + "id": "ia-5.2_dsc-ubtu-24-400370", + "name": "guidance", + "prose": "Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis." + } + ] + }, + { + "id": "ia-5.2_asm-ubtu-24-400370", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.2_obj-ubtu-24-400370" + } + ], + "prose": "Verify that authenticated certificates are mapped to the appropriate user group in the \"/etc/sssd/sssd.conf\" file with the following command: \n \n$ grep -i ldap_user_certificate /etc/sssd/sssd.conf\nldap_user_certificate=userCertificate;binary" + }, + { + "id": "ia-5.2_rem-ubtu-24-400370", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure sssd to map authenticated certificates to the appropriate user group by adding the following line to the \"/etc/sssd/sssd.conf\" file:\n\nldap_user_certificate=userCertificate;binary" + }, + { + "id": "ia-5.2_obj-ubtu-24-400375", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270737", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270737r1067178_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400375", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000185", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004909", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS, for PKI-based authentication, Privileged Access Management (PAM) must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.", + "parts": [ + { + "id": "ia-5.2_dsc-ubtu-24-400375", + "name": "guidance", + "prose": "Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. \n \nA trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. \n \nWhen there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a certification authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. \n \nThis requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.\n\nSatisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000775-GPOS-00230" + } + ] + }, + { + "id": "ia-5.2_asm-ubtu-24-400375", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.2_obj-ubtu-24-400375" + } + ], + "prose": "Verify Ubuntu 24.04 LTS, for PKI-based authentication, has valid certificates by constructing a certification path to an accepted trust anchor. \n \nDetermine which pkcs11 module is being used via the \"use_pkcs11_module\" in \"/etc/pam_pkcs11/pam_pkcs11.conf\" and then ensure \"ca\" is enabled in \"cert_policy\" with the following command: \n \n$ sudo grep use_pkcs11_module /etc/pam_pkcs11/pam_pkcs11.conf | awk '/pkcs11_module opensc {/,/}/' /etc/pam_pkcs11/pam_pkcs11.conf | grep cert_policy | grep ca \n \ncert_policy = ca,signature,ocsp_on; \n \nIf \"cert_policy\" is not set to \"ca\" or the line is commented out, this is a finding." + }, + { + "id": "ia-5.2_rem-ubtu-24-400375", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS, for PKI-based authentication, to validate certificates by constructing a certification path to an accepted trust anchor. \n \nDetermine which pkcs11 module is being used via the \"use_pkcs11_module\" in \"/etc/pam_pkcs11/pam_pkcs11.conf\" and ensure \"ca\" is enabled in \"cert_policy\". \n \nAdd or update the \"cert_policy\" to ensure \"ca\" is enabled: \n \ncert_policy = ca,signature,ocsp_on; \n \nIf the system is missing an \"/etc/pam_pkcs11/\" directory and an \"/etc/pam_pkcs11/pam_pkcs11.conf\", find an example to copy into place and modify accordingly at \"https://manpages.ubuntu.com/manpages/xenial/man8/pam_pkcs11.8.html\"." + }, + { + "id": "ia-5.2_obj-ubtu-24-400380", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270738", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270738r1066703_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400380", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004068", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS for PKI-based authentication, must implement a local cache of revocation data in case of the inability to access revocation information via the network.", + "parts": [ + { + "id": "ia-5.2_dsc-ubtu-24-400380", + "name": "guidance", + "prose": "Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates)." + } + ] + }, + { + "id": "ia-5.2_asm-ubtu-24-400380", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.2_obj-ubtu-24-400380" + } + ], + "prose": "Note: If smart card authentication is not being used on the system, this is not applicable. \n \nVerify Ubuntu 24.04 LTS, for PKI-based authentication, uses local revocation data when unable to access it from the network with the following command:\n\n$ grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep -E -- 'crl_auto|crl_offline' \ncert_policy = ca,signature,ocsp_on,crl_auto; \n \nIf \"cert_policy\" is not set to include \"crl_auto\" or \"crl_offline\", this is a finding." + }, + { + "id": "ia-5.2_rem-ubtu-24-400380", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS, for PKI-based authentication, to use local revocation data when unable to access the network to obtain it remotely. \n \nAdd or update the \"cert_policy\" option in \"/etc/pam_pkcs11/pam_pkcs11.conf\" to include \"crl_auto\" or \"crl_offline\". \n \ncert_policy = ca,signature,ocsp_on, crl_auto; \n \nIf the system is missing an \"/etc/pam_pkcs11/\" directory and an \"/etc/pam_pkcs11/pam_pkcs11.conf\", find an example to copy into place and modify accordingly at \"/usr/share/doc/libpam-pkcs11/examples/pam_pkcs11.conf.example.gz\"." + } + ] + } + ] + }, + { + "control-id": "ia-7", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ia-7_obj-ubtu-24-400400", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270739", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270739r1067124_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-400400", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000803", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must encrypt all stored passwords with a FIPS 140-3 approved cryptographic hashing algorithm.", + "parts": [ + { + "id": "ia-7_dsc-ubtu-24-400400", + "name": "guidance", + "prose": "Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised." + } + ] + }, + { + "id": "ia-7_asm-ubtu-24-400400", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-7_obj-ubtu-24-400400" + } + ], + "prose": "Verify the shadow password suite configuration is set to encrypt passwords with a FIPS 140-3 approved cryptographic hashing algorithm with the following command: \n \n$ grep -i ENCRYPT_METHOD /etc/login.defs \nENCRYPT_METHOD SHA512 \n \nIf \"ENCRYPT_METHOD\" does not equal SHA512 or greater, this is a finding." + }, + { + "id": "ia-7_rem-ubtu-24-400400", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to encrypt all stored passwords. \n \nEdit/modify the following line in the \"/etc/login.defs\" file and set \"ENCRYPT_METHOD\" to SHA512: \n \nENCRYPT_METHOD SHA512" + } + ] + } + ] + }, + { + "control-id": "ia-8", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-2_obj-ubtu-24-400000" + } + ] + } + ] + }, + { + "control-id": "ma-3.5", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-6.8_obj-ubtu-24-200580" + } + ] + } + ] + }, + { + "control-id": "ma-4", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ma-4_obj-ubtu-24-500050", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270741", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270741r1066712_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-500050", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000877", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must use strong authenticators in establishing nonlocal maintenance and diagnostic sessions.", + "parts": [ + { + "id": "ma-4_dsc-ubtu-24-500050", + "name": "guidance", + "prose": "Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric." + } + ] + }, + { + "id": "ma-4_asm-ubtu-24-500050", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ma-4_obj-ubtu-24-500050" + } + ], + "prose": "Verify Ubuntu 24.04 LTS is configured to use strong authenticators in the establishment of nonlocal maintenance and diagnostic maintenance with the following command:\n\n$ sudo grep -r ^UsePAM /etc/ssh/sshd_config*\n/etc/ssh/sshd_config:UsePAM yes\n\nIf \"UsePAM\" is not set to \"yes\", conflicting results are returned, the line is commented out, or is missing, this is a finding." + }, + { + "id": "ma-4_rem-ubtu-24-500050", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to use strong authentication when establishing nonlocal maintenance and diagnostic sessions. \n \nAdd or modify the following line to /etc/ssh/sshd_config: \n \nUsePAM yes" + } + ] + } + ] + }, + { + "control-id": "ma-4.1", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "ma-4.1_obj-ubtu-24-500010", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270740", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270740r1066709_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-500010", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002884", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-000172", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate audit records for privileged activities, nonlocal maintenance, diagnostic sessions, and other system-level access.", + "parts": [ + { + "id": "ma-4.1_dsc-ubtu-24-500010", + "name": "guidance", + "prose": "If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available. \n \nThis requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems. \n \nNonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. \n \nThis requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing \"ping,\" \"ls,\" \"ipconfig,\" or the hardware and software implementing the monitoring port of an Ethernet switch.\n\nSatisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215" + } + ] + }, + { + "id": "ma-4.1_asm-ubtu-24-500010", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#ma-4.1_obj-ubtu-24-500010" + } + ], + "prose": "Verify Ubuntu 24.04 LTS audits activities performed during nonlocal maintenance and diagnostic sessions with the following command: \n \n$ sudo auditctl -l | grep sudo.log \n-w /var/log/sudo.log -p wa -k maintenance \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above." + }, + { + "id": "ma-4.1_rem-ubtu-24-500010", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to audit activities performed during nonlocal maintenance and diagnostic sessions. \n \nAdd or update the following rules in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/sudo.log -p wa -k maintenance \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load" + } + ] + } + ] + }, + { + "control-id": "ma-4.6", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.2_obj-ubtu-24-100820" + }, + { + "rel": "assessment-objective", + "href": "#ac-17.2_obj-ubtu-24-100830" + } + ] + } + ] + }, + { + "control-id": "sc-10", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-10_obj-ubtu-24-600000", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270742", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270742r1066715_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600000", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001133", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must immediately terminate all network connections associated with SSH traffic after a period of inactivity.", + "parts": [ + { + "id": "sc-10_dsc-ubtu-24-600000", + "name": "guidance", + "prose": "Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. \n \nSession termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. \n \nConditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. \n \nThis capability is typically reserved for specific Ubuntu 24.04 LTS functionality where the system owner, data owner, or organization requires additional assurance." + } + ] + }, + { + "id": "sc-10_asm-ubtu-24-600000", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-10_obj-ubtu-24-600000" + } + ], + "prose": "Verify that all network connections associated with SSH traffic automatically terminate after a period of inactivity with the following command: \n\n$ sudo grep -ir ClientAliveCountMax /etc/ssh/sshd_config*\n/etc/ssh/sshd_config:ClientAliveCountMax 1\n\nIf \"ClientAliveCountMax\" is not to \"1\", if conflicting results are returned, is commented out, or is missing, this is a finding." + }, + { + "id": "sc-10_rem-ubtu-24-600000", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to automatically terminate inactive SSH sessions after a period of inactivity. \n \nModify or append the following line in the \"/etc/ssh/sshd_config\" file, replacing \"[Count]\" with a value of 1: \n \nClientAliveCountMax 1 \n \nRestart the SSH daemon for the changes to take effect: \n \n$ sudo systemctl restart ssh.service" + }, + { + "id": "sc-10_obj-ubtu-24-600010", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270743", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270743r1066718_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600010", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001133", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must immediately terminate all network connections associated with SSH traffic at the end of the session or after 10 minutes of inactivity.", + "parts": [ + { + "id": "sc-10_dsc-ubtu-24-600010", + "name": "guidance", + "prose": "Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. \n \nTerminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at Ubuntu 24.04 LTS level, and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that Ubuntu 24.04 LTS terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session." + } + ] + }, + { + "id": "sc-10_asm-ubtu-24-600010", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-10_obj-ubtu-24-600010" + } + ], + "prose": "Verify that all network connections associated with SSH traffic are automatically terminated at the end of the session or after 10 minutes of inactivity with the following command:\n\n$ grep -ir ClientAliveInterval /etc/ssh/sshd_config*\n/etc/ssh/sshd_config:ClientAliveInterval 600\n\nIf \"ClientAliveInterval\" does not exist, is not set to a value of \"600\" or less in \"/etc/ssh/sshd_config\", if conflicting results are returned, is commented out, or is missing, this is a finding." + }, + { + "id": "sc-10_rem-ubtu-24-600010", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to automatically terminate all network connections associated with SSH traffic at the end of a session or after a 10-minute period of inactivity.\n\nIn the file /etc/ssh/sshd_config set ClientAliveInterval to a value of \"600\" or less: \n\nClientAliveInterval 600\n\nRestart the SSH daemon for the changes to take effect:\n\n$ sudo systemctl restart sshd.service" + } + ] + } + ] + }, + { + "control-id": "sc-11", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-11_obj-ubtu-24-300019" + } + ] + } + ] + }, + { + "control-id": "sc-13", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-13_obj-ubtu-24-600030", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270744", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270744r1137699_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600030", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002450", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.", + "parts": [ + { + "id": "sc-13_dsc-ubtu-24-600030", + "name": "guidance", + "prose": "Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. Ubuntu 24.04 LTS must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.\n\nSatisfies: SRG-OS-000478-GPOS-00223, SRG-OS-000396-GPOS-00176" + } + ] + }, + { + "id": "sc-13_asm-ubtu-24-600030", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-13_obj-ubtu-24-600030" + } + ], + "prose": "Verify the system is configured to run in FIPS mode with the following command: \n \n$ grep -i 1 /proc/sys/crypto/fips_enabled\n1 \n \nIf a value of \"1\" is not returned, this is a finding." + }, + { + "id": "sc-13_rem-ubtu-24-600030", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system to run in FIPS mode. Add \"fips=1\" to the kernel parameter during Ubuntu 24.04 LTSs install. \n \nEnabling a FIPS mode on a pre-existing system involves a number of modifications to Ubuntu 24.04 LTS. Refer to the Ubuntu Pro security certification documentation for instructions. \n \nA subscription to the \"Ubuntu Pro\" plan is required to obtain the FIPS Kernel cryptographic modules and enable FIPS.\n\nNote: Ubuntu Pro security certification instructions can be found at: https://ubuntu.com/security/certifications/docs/fips-enablement\n\nThe basic steps use the following commands:\n\n$ sudo pro attach \n$ sudo pro enable fips-updates" + } + ] + } + ] + }, + { + "control-id": "sc-17", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ia-5.2_obj-ubtu-24-400360" + }, + { + "rel": "assessment-objective", + "href": "#ia-5.2_obj-ubtu-24-400375" + } + ] + } + ] + }, + { + "control-id": "sc-23.5", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-23.5_obj-ubtu-24-600060", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270745", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270745r1066724_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600060", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002470", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must use DOD PKI-established certificate authorities (CAs) for verification of the establishment of protected sessions.", + "parts": [ + { + "id": "sc-23.5_dsc-ubtu-24-600060", + "name": "guidance", + "prose": "Untrusted CAs can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DOD-approved CA, trust of this CA has not been established. \n \nThe DOD will only accept PKI-certificates obtained from a DOD-approved internal or external certificate authority. Reliance on CAs for the establishment of secure sessions includes, for example, the use of SSL/TLS certificates." + } + ] + }, + { + "id": "sc-23.5_asm-ubtu-24-600060", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-23.5_obj-ubtu-24-600060" + } + ], + "prose": "Verify the directory containing the root certificates for Ubuntu 24.04 LTS contains certificate files for DOD PKI-established CAs by iterating over all files in the \"/etc/ssl/certs\" directory and checking if, at least one, has the subject matching \"DOD ROOT CA\".\n\n$ grep -ir DOD /etc/ssl/certs\nDOD_PKE_CA_chain.pem\n\nIf no root certificate is found, this is a finding." + }, + { + "id": "sc-23.5_rem-ubtu-24-600060", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to use of DOD PKI-established CAs for verification of the establishment of protected sessions. \n \nEdit the \"/etc/ca-certificates.conf\" file, adding the character \"!\" to the beginning of all uncommented lines that do not start with the \"!\" character with the following command: \n \n$ sudo sed -i -E 's/^([^!#]+)/!\\1/' /etc/ca-certificates.conf \n \nAdd at least one CA to the \"/usr/local/share/ca-certificates\" directory in the PEM format. \n \nUpdate the \"/etc/ssl/certs\" directory with the following command: \n \n$ sudo update-ca-certificates" + } + ] + } + ] + }, + { + "control-id": "sc-24", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-24_obj-ubtu-24-100200", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270653", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270653r1067141_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100200", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001665", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured to preserve log records from failure events.", + "parts": [ + { + "id": "sc-24_dsc-ubtu-24-100200", + "name": "guidance", + "prose": "Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. \n \nPreserving operating system state information helps to facilitate operating system restart and return to the operational mode of the organization with least disruption to mission/business processes." + } + ] + }, + { + "id": "sc-24_asm-ubtu-24-100200", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-24_obj-ubtu-24-100200" + } + ], + "prose": "Verify the log service is installed properly with the following command: \n \n$ dpkg -l | grep rsyslog \nii rsyslog 8.2312.0-3ubuntu9 amd64 reliable system and kernel logging daemon \n \nIf the \"rsyslog\" package is not installed, this is a finding. \n \nCheck that the log service is enabled with the following command: \n \n$ systemctl is-enabled rsyslog\nenabled \n \nIf the command above returns \"disabled\", this is a finding. \n \nCheck that the log service is properly running and active on the system with the following command: \n \n$ systemctl is-active rsyslog\nactive \n \nIf the command above returns \"inactive\", this is a finding." + }, + { + "id": "sc-24_rem-ubtu-24-100200", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the log service to collect failure events. \n \nInstall the log service (if the log service is not already installed) with the following command: \n \n$ sudo apt install -y rsyslog \n \nEnable the log service with the following command: \n \n$ sudo systemctl enable --now rsyslog" + }, + { + "id": "sc-24_obj-ubtu-24-600070", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270746", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270746r1155242_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600070", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001190", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must disable kernel core dumps.", + "parts": [ + { + "id": "sc-24_dsc-ubtu-24-600070", + "name": "guidance", + "prose": "Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may consume a considerable amount of disk space and may result in denial of service by exhausting the available space on the target file system partition." + } + ] + }, + { + "id": "sc-24_asm-ubtu-24-600070", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-24_obj-ubtu-24-600070" + } + ], + "prose": "Verify kernel core dumps are disabled unless needed with the following command: \n \n$ systemctl status kdump-tools.service\no kdump-tools.service\n Loaded: masked (Reason: Unit kdump-tools.service is masked.)\n Active: inactive (dead)\n\nIf kdump-tools is not installed the output will be:\nUnit kdump-tools.service could not be found.\n\nIf \"kdump-tools.service\" is not masked and inactive, ask the system administrator (SA) if the use of the service is required and documented with the information system security officer (ISSO).\n\nIf the service is active and is not documented, this is a finding." + }, + { + "id": "sc-24_rem-ubtu-24-600070", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "If kernel core dumps are not required, disable the \"kdump-tools\" service with the following command: \n \n$ sudo systemctl disable kdump-tools.service\n \nIf kernel core dumps are required, document the need with the ISSO." + } + ] + } + ] + }, + { + "control-id": "sc-28", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-28_obj-ubtu-24-600090", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270747", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270747r1066730_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600090", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001199", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002475", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002476", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004910", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "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.", + "parts": [ + { + "id": "sc-28_dsc-ubtu-24-600090", + "name": "guidance", + "prose": "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-00184, SRG-OS-000780-GPOS-00240" + } + ] + }, + { + "id": "sc-28_asm-ubtu-24-600090", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-28_obj-ubtu-24-600090" + } + ], + "prose": "Note: 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$ 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 bytes \nDisklabel type: gpt \nDisk identifier: 83298450-B4E3-4B19-A9E4-7DF147A5FEFB \n \nDevice Start End Sectors Size Type \n/dev/vda1 2048 4095 2048 1M BIOS boot \n/dev/vda2 4096 2101247 2097152 1G Linux filesystem \n/dev/vda3 2101248 31455231 29353984 14G Linux filesystem \n(...) \n \nVerify the system partitions are all encrypted with the following command: \n \n$ more /etc/crypttab\n \nEvery persistent disk partition present must have an entry in the file. \n \nIf any partitions other than the boot partition or pseudo file systems (such as /proc or /sys) are not listed, this is a finding." + }, + { + "id": "sc-28_rem-ubtu-24-600090", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "To 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." + } + ] + } + ] + }, + { + "control-id": "sc-28.1", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-28_obj-ubtu-24-600090" + } + ] + } + ] + }, + { + "control-id": "sc-28.3", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-28_obj-ubtu-24-600090" + } + ] + } + ] + }, + { + "control-id": "sc-3", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-3_obj-ubtu-24-600130", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270748", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270748r1066733_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001084", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group.", + "parts": [ + { + "id": "sc-3_dsc-ubtu-24-600130", + "name": "guidance", + "prose": "An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. \n \nSecurity functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For nonkernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code. \n \nDevelopers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. \n \nUbuntu 24.04 LTS restricts access to security functions through the use of access control mechanisms and by implementing least privilege capabilities." + } + ] + }, + { + "id": "sc-3_asm-ubtu-24-600130", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-3_obj-ubtu-24-600130" + } + ], + "prose": "Verify the sudo group has only members who require access to security functions with the following command: \n \n$ grep sudo /etc/group\nsudo:x:27:foo \n \nIf the sudo group contains users not needing access to security functions, this is a finding." + }, + { + "id": "sc-3_rem-ubtu-24-600130", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the sudo group with only members requiring access to security functions. \n \nTo remove a user from the sudo group, run: \n \n$ sudo gpasswd -d sudo" + } + ] + } + ] + }, + { + "control-id": "sc-4", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-4_obj-ubtu-24-600140", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270749", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270749r1137695_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600140", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001090", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must restrict access to the kernel message buffer.", + "parts": [ + { + "id": "sc-4_dsc-ubtu-24-600140", + "name": "guidance", + "prose": "Restricting access to the kernel message buffer limits access only to root. This prevents attackers from gaining additional system information as a nonprivileged user." + } + ] + }, + { + "id": "sc-4_asm-ubtu-24-600140", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-4_obj-ubtu-24-600140" + } + ], + "prose": "Verify Ubuntu 24.04 LTS is configured to restrict access to the kernel message buffer with the following command:\n\n$ sysctl kernel.dmesg_restrict\nkernel.dmesg_restrict = 1\n\nIf \"kernel.dmesg_restrict\" is not set to \"1\" or is missing, this is a finding.\n\nVerify there are no configurations that enable the kernel dmesg function:\n\n$ sudo grep -r kernel.dmesg_restrict /run/sysctl.d/* /etc/sysctl.d/* /usr/local/lib/sysctl.d/* /usr/lib/sysctl.d/* /lib/sysctl.d/* /etc/sysctl.conf 2> /dev/null\n/etc/sysctl.d/10-kernel-hardening.conf:kernel.dmesg_restrict = 1\n\nIf any instance of \"kernel.dmesg_restrict\" is uncommented and set to \"0\", or if conflicting results are returned, this is a finding." + }, + { + "id": "sc-4_rem-ubtu-24-600140", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to restrict access to the kernel message buffer.\n\nSet the system to the required kernel parameter by adding or modifying the following line in /etc/sysctl.conf or a config file in the /etc/sysctl.d/ directory:\n\n kernel.dmesg_restrict = 1\n\nRemove any configurations that conflict with the above from the following locations: \n /run/sysctl.d/\n /etc/sysctl.d/\n /usr/local/lib/sysctl.d/\n /usr/lib/sysctl.d/\n /lib/sysctl.d/\n /etc/sysctl.conf\n\nReload settings from all system configuration files with the following command:\n\n $ sudo sysctl --system" + }, + { + "id": "sc-4_obj-ubtu-24-600150", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270750", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270750r1137695_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600150", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001090", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must set a sticky bit on all public directories to prevent unauthorized and unintended information transferred via shared system resources.", + "parts": [ + { + "id": "sc-4_dsc-ubtu-24-600150", + "name": "guidance", + "prose": "Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. \n \nThis requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DOD or other government agencies. \n \nThere may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components." + } + ] + }, + { + "id": "sc-4_asm-ubtu-24-600150", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-4_obj-ubtu-24-600150" + } + ], + "prose": "Verify all public (world-writeable) directories have the public sticky bit set with the following command: \n \n$ sudo find / -type d -perm -002 ! -perm -1000 \n \nIf any world-writable directories are found missing the sticky bit, this is a finding." + }, + { + "id": "sc-4_rem-ubtu-24-600150", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure all public directories to have the sticky bit set to prevent unauthorized and unintended information transferred via shared system resources. \n \nSet the sticky bit on all public directories using the following command, replacing \"[Public Directory]\" with any directory path missing the sticky bit: \n \n$ sudo chmod +t [Public Directory]" + } + ] + } + ] + }, + { + "control-id": "sc-45", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-45_obj-ubtu-24-600160", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270751", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270751r1066742_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600160", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004922", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004923", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must compare internal information system clocks at least every 24 hours with an authoritative time server.", + "parts": [ + { + "id": "sc-45_dsc-ubtu-24-600160", + "name": "guidance", + "prose": "Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate. \n \nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. \n \nOrganizations must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).\n\nSatisfies: SRG-OS-000785-GPOS-00250, SRG-OS-000355-GPOS-00143" + } + ] + }, + { + "id": "sc-45_asm-ubtu-24-600160", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-45_obj-ubtu-24-600160" + } + ], + "prose": "Note: If the system is not networked, this requirement is not applicable.\n\nVerify Ubuntu 24.04 LTS is configured to compare the system clock at least every 24 hours to an authoritative time source with the following command:\n\n$ sudo grep -ir maxpoll /etc/chrony*\nserver [source] iburst maxpoll 16\n\nIf the parameter \"server\" is not set, is not set to an authoritative DOD time source, or is commented out, this is a finding.\n\nIf the \"maxpoll\" option is set to a number greater than 16, the line is commented out, or is missing, this is a finding." + }, + { + "id": "sc-45_rem-ubtu-24-600160", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "To configure the system clock to compare to the authoritative time source at least every 24 hours, edit the \"/etc/chrony/chrony.conf\" file. Add or correct the following lines, by replacing \"[source]\" in the following line with an authoritative time source: \n\nserver [source] iburst maxpoll 16 \n\nIf the \"chrony\" service was running and the value of \"maxpoll\" or \"server\" was updated, the service must be restarted using the following command: \n\n$ sudo systemctl restart chrony.service" + } + ] + } + ] + }, + { + "control-id": "sc-45.1", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-45_obj-ubtu-24-600160" + } + ], + "parts": [ + { + "id": "sc-45.1_obj-ubtu-24-600180", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270752", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270752r1068365_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600180", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "low", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-004926", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.", + "parts": [ + { + "id": "sc-45.1_dsc-ubtu-24-600180", + "name": "guidance", + "prose": "Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. \n \nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations must consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems). \n \nOrganizations must also consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). This requirement is related to the comparison done every 24 hours in SRG-OS-000355 because a comparison must be done to determine the time difference." + } + ] + }, + { + "id": "sc-45.1_asm-ubtu-24-600180", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-45.1_obj-ubtu-24-600180" + } + ], + "prose": "Verify Ubuntu 24.04 LTS synchronizes internal system clocks to the authoritative time source when the time difference is greater than one second. \n \nCheck the value of \"makestep\" with the following command: \n \n$ grep makestep /etc/chrony/chrony.conf\nmakestep 1 -1 \n \nIf the makestep option is not set to \"1 -1\", is commented out, or is missing, this is a finding." + }, + { + "id": "sc-45.1_rem-ubtu-24-600180", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure chrony to synchronize the internal system clocks to the authoritative source when the time difference is greater than one second by doing the following: \n \nEdit the \"/etc/chrony/chrony.conf\" file and add: \n \nmakestep 1 -1 \n \nRestart the chrony service: \n \n$ sudo systemctl restart chrony.service" + } + ] + } + ] + }, + { + "control-id": "sc-5", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-5_obj-ubtu-24-600200", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270754", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270754r1066751_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600200", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002385", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the uncomplicated firewall to rate-limit impacted network interfaces.", + "parts": [ + { + "id": "sc-5_dsc-ubtu-24-600200", + "name": "guidance", + "prose": "Denial of service (DoS) occurs when a resource is not available for legitimate users, resulting in the organization not being able to accomplish its mission or causing it to operate at degraded capacity.\n \nThis requirement addresses the configuration of Ubuntu 24.04 LTS to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks." + } + ] + }, + { + "id": "sc-5_asm-ubtu-24-600200", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-5_obj-ubtu-24-600200" + } + ], + "prose": "Verify an application firewall is configured to rate limit any connection to the system. \n \nCheck all the services listening to the ports with the following command: \n \n$ ss -l46ut \nNetid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process \ntcp LISTEN 0 511 *:http *:* \ntcp LISTEN 0 128 [::]:ssh [::]:*\ntcp LISTEN 0 128 [::]:ipp [::]:* \ntcp LISTEN 0 128 [::]:smtp [::]:*\n\n \nFor each entry, verify the Uncomplicated Firewall (ufw) is configured to rate limit the service ports with the following command: \n \n$ sudo ufw status \nStatus: active \n \nTo Action From \n-- ------ ---- \n80/tcp LIMIT Anywhere\n25/tcp LIMIT Anywhere\nAnywhere DENY 177.60.7.4\n443 LIMIT Anywhere \n22/tcp LIMIT Anywhere \n80/tcp (v6) LIMIT Anywhere\n25/tcp (v6) LIMIT Anywhere \n22/tcp (v6) LIMIT Anywhere (v6) \n\n25 DENY OUT Anywhere\n25 (v6) DENY OUT Anywhere (v6)\n\nIf any port with a state of \"LISTEN\" that does not have an action of \"DENY\", is not marked with the \"LIMIT\" action, this is a finding. If the Status is set to anything other than \"active\" this is a finding." + }, + { + "id": "sc-5_rem-ubtu-24-600200", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the application firewall to protect against or limit the effects of DoS attacks by ensuring Ubuntu 24.04 LTS is implementing rate-limiting measures on impacted network interfaces. \n \nTo change the Status of ufw to \"active\" use the following command:\n$ sudo ufw enable\n\nCheck all the services listening to the ports with the following command: \n \n$ sudo ss -l46ut \nNetid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process \ntcp LISTEN 0 128 [::]:ssh [::]:* \n \nFor each service with a port listening to connections, run the following command, replacing \"[service]\" with the service that needs to be rate limited. \n \n$ sudo ufw limit [service] \n \nRate-limiting can also be done on an interface. An example of adding a rate-limit on the eth0 interface follows: \n \n$ sudo ufw limit in on eth0" + } + ] + } + ] + }, + { + "control-id": "sc-5.2", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-5.2_obj-ubtu-24-600190", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270753", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270753r1066748_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600190", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001095", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured to use TCP syncookies.", + "parts": [ + { + "id": "sc-5.2_dsc-ubtu-24-600190", + "name": "guidance", + "prose": "Denial of service (DoS) occurs when a resource is not available for legitimate users, resulting in the organization not being able to accomplish its mission or causing it to operate at degraded capacity. \n \nManaging excess capacity ensures sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning." + } + ] + }, + { + "id": "sc-5.2_asm-ubtu-24-600190", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-5.2_obj-ubtu-24-600190" + } + ], + "prose": "Verify Ubuntu 24.04 LTS is configured to use TCP syncookies with the following command:\n \n$ sysctl net.ipv4.tcp_syncookies \nnet.ipv4.tcp_syncookies = 1 \n \nIf the value is not \"1\", this is a finding. \n \nCheck the saved value of TCP syncookies with the following command: \n \n$ sudo grep -ir net.ipv4.tcp_syncookies /etc/sysctl.d/*.conf /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf 2> /dev/null \n/etc/sysctl.d/99-sysctl.conf:net.ipv4.tcp_syncookies=1\n/etc/sysctl.conf:net.ipv4.tcp_syncookies=1\n\nIf the \"net.ipv4.tcp_syncookies\" option is not set to \"1\", is commented out, or is missing, this is a finding." + }, + { + "id": "sc-5.2_rem-ubtu-24-600190", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to use TCP syncookies with the following command: \n \n$ sudo sysctl -w net.ipv4.tcp_syncookies=1 \n \nIf \"1\" is not the system's default value, add or update the following line in \"/etc/sysctl.conf\": \n \nnet.ipv4.tcp_syncookies = 1" + } + ] + } + ] + }, + { + "control-id": "sc-8", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "sc-8_obj-ubtu-24-100800", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270665", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270665r1067133_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100800", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002418", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002420", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002422", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must have SSH installed.", + "parts": [ + { + "id": "sc-8_dsc-ubtu-24-100800", + "name": "guidance", + "prose": "Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. \n \nThis requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. \n \nProtecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190" + } + ] + }, + { + "id": "sc-8_asm-ubtu-24-100800", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-8_obj-ubtu-24-100800" + } + ], + "prose": "Verify the SSH package is installed with the following command: \n \n$ dpkg -l | grep openssh \nii openssh-client 1:9.6p1-3ubuntu13.5 amd64 secure shell (SSH) client, for secure access to remote machines\nii openssh-server 1:9.6p1-3ubuntu13.5 amd64 secure shell (SSH) server, for secure access from remote machines\nii openssh-sftp-server 1:9.6p1-3ubuntu13.5 amd64 secure shell (SSH) sftp server module, for SFTP access from remote machines\n \nIf the \"openssh\" server package is not installed, this is a finding." + }, + { + "id": "sc-8_rem-ubtu-24-100800", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install the \"ssh\" meta-package on the system with the following command: \n \n$ sudo apt install -y ssh" + }, + { + "id": "sc-8_obj-ubtu-24-100810", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270666", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270666r1066487_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100810", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "high", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002418", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002420", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002422", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must use SSH to protect the confidentiality and integrity of transmitted information.", + "parts": [ + { + "id": "sc-8_dsc-ubtu-24-100810", + "name": "guidance", + "prose": "Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. \n \nThis requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. \n \nProtecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190" + } + ] + }, + { + "id": "sc-8_asm-ubtu-24-100810", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-8_obj-ubtu-24-100810" + } + ], + "prose": "Verify the \"sshd.service\" is enabled and active with the following commands: \n \n$ sudo systemctl is-enabled ssh\nenabled\n\n$ sudo systemctl is-active ssh\nactive\n\nIf \"ssh.service\" is not active or loaded, this is a finding." + }, + { + "id": "sc-8_rem-ubtu-24-100810", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Enable the \"ssh\" service to start automatically on reboot with the following command: \n \n$ sudo systemctl enable ssh.service \n \nensure the \"ssh\" service is running \n \n$ sudo systemctl start ssh.service" + }, + { + "id": "sc-8_obj-ubtu-24-600230", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270755", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270755r1066754_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-600230", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002418", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must disable all wireless network adapters.", + "parts": [ + { + "id": "sc-8_dsc-ubtu-24-600230", + "name": "guidance", + "prose": "Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise Ubuntu 24.04 LTS. \n \nThis requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with an operating system. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR Keyboards, Mice, and Pointing Devices and Near Field Communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DOD requirements for wireless data transmission and be approved for use by the approving authority (AO). Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that need to be protected, modification of communications with these wireless peripherals may be used to compromise Ubuntu 24.04 LTS. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. \n \nProtecting the confidentiality and integrity of communications with wireless peripherals can be accomplished by physical means (e.g., employing physical barriers to wireless radio frequencies) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. If the wireless peripheral is only passing telemetry data, encryption of the data may not be required." + } + ] + }, + { + "id": "sc-8_asm-ubtu-24-600230", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-8_obj-ubtu-24-600230" + } + ], + "prose": "Note: This requirement is not applicable for systems that do not have physical wireless network radios.\n\nVerify there are no wireless interfaces configured on the system with the following command: \n \n$ ls -L -d /sys/class/net/*/wireless | xargs dirname | xargs basename \n \nIf a wireless interface is configured and has not been documented and approved by the information system security officer (ISSO), this is a finding." + }, + { + "id": "sc-8_rem-ubtu-24-600230", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "List all the wireless interfaces with the following command: \n \n$ ls -L -d /sys/class/net/*/wireless | xargs dirname | xargs basename \n \nFor each interface, configure the system to disable wireless network interfaces with the following command: \n \n$ sudo ifdown \n \nFor each interface listed, find their respective module with the following command: \n \n$ basename $(readlink -f /sys/class/net//device/driver) \n \nwhere must be substituted by the actual interface name. \n \nCreate a file in the \"/etc/modprobe.d\" directory and for each module, add the following line: \n \ninstall /bin/true \n \nFor each module from the system, execute the following command to remove it: \n \n$ sudo modprobe -r " + } + ] + } + ] + }, + { + "control-id": "sc-8.1", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#ac-17.2_obj-ubtu-24-100820" + }, + { + "rel": "assessment-objective", + "href": "#ac-17.2_obj-ubtu-24-100830" + } + ] + } + ] + }, + { + "control-id": "sc-8.2", + "adds": [ + { + "position": "ending", + "links": [ + { + "rel": "assessment-objective", + "href": "#sc-8_obj-ubtu-24-100800" + }, + { + "rel": "assessment-objective", + "href": "#sc-8_obj-ubtu-24-100810" + } + ] + } + ] + }, + { + "control-id": "si-11", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "si-11_obj-ubtu-24-700010", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270756", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270756r1134814_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700010", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001312", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700010", + "name": "guidance", + "prose": "Any operating system providing too much information in error messages risks compromising the data and security of the structure, and organizations must carefully consider the content and structure of error messages. \n \nThe extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, Social Security numbers, and credit card numbers.\n\nThe /var/log/btmp, /var/log/wtmp, and /var/log/lastlog files have group write and global read permissions to allow for the lastlog function to perform. Limiting the permissions beyond this configuration will result in the failure of functions that rely on the lastlog database. Additionally, Canonical recommends excluding the history.log and eipp.log.xz from consideration in this check." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700010", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700010" + } + ], + "prose": "Verify Ubuntu 24.04 LTS has all system log files under the /var/log directory with a permission set to \"640\" or less permissive with the following command:\n\nNote: The btmp, wtmp, lastlog, history, and eipp.log.xz files are excluded from this check. Refer to the Discussion for details.\n\n$ sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec stat -c \"%n %a\" {} \\;\n\nIf the command displays any output, this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700010", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to set permissions of all log files under the /var/log directory to \"640\" or more restricted by using the following command:\n\nNote: The btmp, wtmp, lastlog, history, and eipp.log.xz files are excluded. Refer to the Discussion for details.\n\n$ sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec chmod 640 '{}' \\;" + }, + { + "id": "si-11_obj-ubtu-24-700020", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270757", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270757r1184072_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700020", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001312", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must generate system journal entries without revealing information that could be exploited by adversaries.", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700020", + "name": "guidance", + "prose": "Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages must be carefully considered by the organization. \n \nOrganizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700020", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700020" + } + ], + "prose": "Verify the /run/log/journal and /var/log/journal directories have permissions set to \"640\" or less permissive with the following command:\n\n$ sudo find /run/log/journal /var/log/journal -type d -exec stat -c \"%n %a\" {} \\;\n/run/log/journal 640\n/var/log/journal 640\n/var/log/journal/6a52424faa6e480ea5fc7346b9345792 640\n\nIf any output returned has a permission set greater than 640, this is a finding.\n\nVerify all files in the /run/log/journal and /var/log/journal directories have permissions set to \"640\" or less permissive with the following command:\n\n$ sudo find /run/log/journal /var/log/journal -type f -exec stat -c \"%n %a\" {} \\;\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system.journal 640\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000@0005f97cd4a8c9b5a.journal~ 640\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cd2a1e0a7-d58b848af46813a4.journal~ 640\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cb900e501-55ea053b7f75ae1c.journal~ 640\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000.journal 640\n\nIf any output returned has a permission set greater than \"640\", this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700020", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system to set the appropriate permissions to the files and directories used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nz /run/log/journal 0640 root systemd-journal - -\nZ /run/log/journal/%m ~0640 root systemd-journal - -\nz /var/log/journal 0640 root systemd-journal - -\nz /var/log/journal/%m 0640 root systemd-journal - -\nz /var/log/journal/%m/system.journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect." + }, + { + "id": "si-11_obj-ubtu-24-700030", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270758", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270758r1066763_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700030", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001312", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that the \"journalctl\" command is not accessible by unauthorized users.", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700030", + "name": "guidance", + "prose": "Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages must be carefully considered by the organization. \n \nOrganizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700030", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700030" + } + ], + "prose": "Verify the journalctl command has a permission set of \"740\" with the following command:\n\n$ sudo find /usr/bin/journalctl -exec stat -c \"%n %a\" {} \\;\n/usr/bin/journalctl 740\n\nIf journalctl is not set to \"740\", this is a finding" + }, + { + "id": "si-11_rem-ubtu-24-700030", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure journalctl to have a permission set of \"740\":\n\n$ sudo chmod 740 /usr/bin/journalctl" + }, + { + "id": "si-11_obj-ubtu-24-700040", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270759", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270759r1068367_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700040", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that the \"journalctl\" command is owned by \"root\".", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700040", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700040", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700040" + } + ], + "prose": "Verify the journalctl command is owned by \"root\" with the following command:\n\n$ sudo find /usr/bin/journalctl -exec stat -c \"%n %U\" {} \\;\n/usr/bin/journalctl root\n\nIf journalctl is not owned by \"root\", this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700040", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure journalctl to be owned by \"root\":\n\n$ sudo chown root /usr/bin/journalctl" + }, + { + "id": "si-11_obj-ubtu-24-700050", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270760", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270760r1066769_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700050", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that the \"journalctl\" command is group-owned by \"root\".", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700050", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700050", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700050" + } + ], + "prose": "Verify the journalctl command is group-owned by \"root\" with the following command:\n\n$ sudo find /usr/bin/journalctl -exec stat -c \"%n %G\" {} \\;\n/usr/bin/journalctl root\n\nIf journalctl is not group-owned by \"root\", this is a finding" + }, + { + "id": "si-11_rem-ubtu-24-700050", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure journalctl to be group-owned by \"root\":\n\n$ sudo chown :root /usr/bin/journalctl" + }, + { + "id": "si-11_obj-ubtu-24-700060", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270761", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270761r1184074_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700060", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the directories used by the system journal to be group-owned by \"systemd-journal\".", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700060", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700060", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700060" + } + ], + "prose": "Verify the /run/log/journal and /var/log/journal directories are group-owned by \"systemd-journal\" with the following command:\n\n$ sudo find /run/log/journal /var/log/journal -type d -exec stat -c \"%n %G\" {} \\;\n/run/log/journal systemd-journal\n/var/log/journal systemd-journal\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e systemd-journal\n\nIf any output returned is not group-owned by \"systemd-journal\", this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700060", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system to set the appropriate group-ownership to the directories used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nz /run/log/journal 0640 root systemd-journal - -\nz /var/log/journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect." + }, + { + "id": "si-11_obj-ubtu-24-700070", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270762", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270762r1184076_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700070", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the files used by the system journal to be group-owned by \"systemd-journal\".", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700070", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700070", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700070" + } + ], + "prose": "Verify the /run/log/journal and /var/log/journal files are group-owned by \"systemd-journal\" with the following command:\n\n$ sudo find /run/log/journal /var/log/journal -type f -exec stat -c \"%n %G\" {} \\; \n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system.journal systemd-journal\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000@0005f97cd4a8c9b5-f088232c3718485a.journal~ systemd-journal\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cd2a1e0a7-d58b848af46813a4.journal~ systemd-journal\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cb900e501-55ea053b7f75ae1c.journal~ systemd-journal\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000.journal systemd-journal\n\nIf any output returned is not group-owned by \"systemd-journal\", this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700070", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system to set the appropriate group-ownership to the files used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nZ /run/log/journal/%m ~0640 root systemd-journal - -\nz /var/log/journal/%m 0640 root systemd-journal - -\nz /var/log/journal/%m/system.journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect." + }, + { + "id": "si-11_obj-ubtu-24-700080", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270763", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270763r1184078_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700080", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the directories used by the system journal to be owned by \"root\".", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700080", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700080", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700080" + } + ], + "prose": "Verify the /run/log/journal and /var/log/journal directories are owned by \"root\" with the following command:\n\n$ sudo find /run/log/journal /var/log/journal -type d -exec stat -c \"%n %U\" {} \\;\n/run/log/journal root\n/var/log/journal root\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e root\n\nIf any output returned is not owned by \"root\", this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700080", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system to set the appropriate ownership to the directories used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nz /run/log/journal 0640 root systemd-journal - -\nz /var/log/journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect." + }, + { + "id": "si-11_obj-ubtu-24-700090", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270764", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270764r1184080_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700090", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the files used by the system journal to be owned by \"root\"", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700090", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700090", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700090" + } + ], + "prose": "Verify the /run/log/journal and /var/log/journal files are owned by \"root\" with the following command:\n\n$ sudo find /run/log/journal /var/log/journal -type f -exec stat -c \"%n %U\" {} \\; \n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system.journal root\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000@0005f97cd4a8c9b5-f088232c3718485a.journal~ root\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cd2a1e0a7-d58b848af46813a4.journal~ root\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cb900e501-55ea053b7f75ae1c.journal~ root\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000.journal root\n\nIf any output returned is not owned by \"root\", this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700090", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure the system to set the appropriate ownership to the files used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nZ /run/log/journal/%m ~0640 root systemd-journal - -\nz /var/log/journal/%m 0640 root systemd-journal - -\nz /var/log/journal/%m/system.journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect." + }, + { + "id": "si-11_obj-ubtu-24-700100", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270765", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270765r1066784_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700100", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the /var/log directory to be group-owned by syslog.", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700100", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700100", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700100" + } + ], + "prose": "Verify that Ubuntu 24.04 LTS configures the /var/log directory to be group-owned by \"syslog\" with the following command: \n \n$ stat -c \"%n %G\" /var/log\n/var/log syslog \n \nIf the \"/var/log\" directory is not group-owned by syslog, this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700100", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to have syslog group-own the /var/log directory with the following command: \n \n$ sudo chgrp syslog /var/log" + }, + { + "id": "si-11_obj-ubtu-24-700110", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270766", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270766r1066787_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700110", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the /var/log directory to be owned by root.", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700110", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700110", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700110" + } + ], + "prose": "Verify Ubuntu 24.04 LTS configures the /var/log directory to be owned by \"root\" with the following command: \n \n$ stat -c \"%n %U\" /var/log\n/var/log root \n \nIf the \"/var/log\" directory is not owned by root, this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700110", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to have root own the /var/log directory by running the following command: \n \n$ sudo chown root /var/log" + }, + { + "id": "si-11_obj-ubtu-24-700120", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270767", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270767r1066790_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700120", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the /var/log directory to have mode \"0755\" or less permissive.", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700120", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700120", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700120" + } + ], + "prose": "Note: If rsyslog is active and enabled on Ubuntu 24.04 LTS, this requirement is not applicable.\n\nVerify Ubuntu 24.04 LTS configures the /var/log directory with a mode of \"755\" or less permissive with the following command:\n\n$ stat -c \"%n %a\" /var/log\n/var/log 755\n\nIf a value of \"755\" or less permissive is not returned, this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700120", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to have permissions of \"0755\" for the /var/log directory by running the following command: \n \n$ sudo chmod 0755 /var/log" + }, + { + "id": "si-11_obj-ubtu-24-700130", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270768", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270768r1066793_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure the /var/log/syslog file to be group-owned by adm.", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700130", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700130", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700130" + } + ], + "prose": "Verify that Ubuntu 24.04 LTS configures the /var/log/syslog file to be group-owned by \"adm\" with the following command: \n \n$ stat -c \"%n %G\" /var/log/syslog \n/var/log/syslog adm \n \nIf the /var/log/syslog file is not group-owned by \"adm\", this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700130", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to have adm group-own the /var/log/syslog file by running the following command: \n \n$ sudo chgrp adm /var/log/syslog" + }, + { + "id": "si-11_obj-ubtu-24-700140", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270769", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270769r1066796_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700140", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure /var/log/syslog file to be owned by syslog.", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700140", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700140", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700140" + } + ], + "prose": "Verify that Ubuntu 24.04 LTS configures the /var/log/syslog file to be owned by \"syslog\" with the following command: \n \n$ stat -c \"%n %U\" /var/log/syslog \n/var/log/syslog syslog \n \nIf the \"/var/log/syslog\" file is not owned by syslog, this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700140", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to have syslog own the /var/log/syslog file by running the following command: \n \n$ sudo chown syslog /var/log/syslog" + }, + { + "id": "si-11_obj-ubtu-24-700150", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270770", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270770r1066799_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700150", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001314", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure /var/log/syslog file with mode \"0640\" or less permissive.", + "parts": [ + { + "id": "si-11_dsc-ubtu-24-700150", + "name": "guidance", + "prose": "Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements." + } + ] + }, + { + "id": "si-11_asm-ubtu-24-700150", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-11_obj-ubtu-24-700150" + } + ], + "prose": "Verify that Ubuntu 24.04 LTS configures the /var/log/syslog file with mode \"0640\" or less permissive with the following command: \n \n$ stat -c \"%n %a\" /var/log/syslog\n/var/log/syslog 640 \n \nIf a value of \"640\" or less permissive is not returned, this is a finding." + }, + { + "id": "si-11_rem-ubtu-24-700150", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to have permissions of \"0640\" for the /var/log/syslog file by running the following command: \n \n$ sudo chmod 0640 /var/log/syslog" + } + ] + } + ] + }, + { + "control-id": "si-16", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "si-16_obj-ubtu-24-700300", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270771", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270771r1066802_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700300", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002824", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must implement nonexecutable data to protect its memory from unauthorized code execution.", + "parts": [ + { + "id": "si-16_dsc-ubtu-24-700300", + "name": "guidance", + "prose": "Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. \n \nExamples of attacks are buffer overflow attacks." + } + ] + }, + { + "id": "si-16_asm-ubtu-24-700300", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-16_obj-ubtu-24-700300" + } + ], + "prose": "Verify the NX (no-execution) bit flag is set on the system with the following command: \n \n$ sudo dmesg | grep -i \"execute disable\" \n[ 0.000000] NX (Execute Disable) protection: active \n \nIf \"dmesg\" does not show \"NX (Execute Disable) protection: active\", check the cpuinfo settings with the following command: \n \n$ grep flags /proc/cpuinfo | grep -w nx | sort -u \nflags : fpu vme de pse tsc ms nx rdtscp lm constant_tsc \n \nIf \"flags\" does not contain the \"nx\" flag, this is a finding." + }, + { + "id": "si-16_rem-ubtu-24-700300", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to enable NX. \n \nIf \"nx\" is not showing up in \"/proc/cpuinfo\", and the system's BIOS setup configuration permits toggling the No Execution bit, set it to \"enable\"." + }, + { + "id": "si-16_obj-ubtu-24-700310", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270772", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270772r1066805_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700310", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002824", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must implement address space layout randomization to protect its memory from unauthorized code execution.", + "parts": [ + { + "id": "si-16_dsc-ubtu-24-700310", + "name": "guidance", + "prose": "Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. \n \nExamples of attacks are buffer overflow attacks." + } + ] + }, + { + "id": "si-16_asm-ubtu-24-700310", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-16_obj-ubtu-24-700310" + } + ], + "prose": "Verify Ubuntu 24.04 LTS implements address space layout randomization (ASLR) with the following command: \n \n$ sysctl kernel.randomize_va_space\nkernel.randomize_va_space = 2 \n \nIf nothing is returned, verify the kernel parameter \"randomize_va_space\" is set to \"2\" with the following command: \n \n$ cat /proc/sys/kernel/randomize_va_space\n2 \n \nIf \"kernel.randomize_va_space\" is not set to \"2\", this is a finding. \n \nVerify that a saved value of the \"kernel.randomize_va_space\" variable is not defined. \n \n$ sudo egrep -R \"^kernel.randomize_va_space=[^2]\" /etc/sysctl.conf /etc/sysctl.d \n \nIf this returns a result, this is a finding." + }, + { + "id": "si-16_rem-ubtu-24-700310", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Remove the \"kernel.randomize_va_space\" entry found in the \"/etc/sysctl.conf\" file or any file located in the \"/etc/sysctl.d/\" directory. \n \nAfter the line has been removed, the kernel settings from all system configuration files must be reloaded before any of the changes will take effect. Run the following command to reload all of the kernel system configuration files: \n \n$ sudo sysctl --system" + } + ] + } + ] + }, + { + "control-id": "si-2.6", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "si-2.6_obj-ubtu-24-700320", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270773", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270773r1066808_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-700320", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002617", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that Advance Package Tool (APT) removes all software components after updated versions have been installed.", + "parts": [ + { + "id": "si-2.6_dsc-ubtu-24-700320", + "name": "guidance", + "prose": "Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system." + } + ] + }, + { + "id": "si-2.6_asm-ubtu-24-700320", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-2.6_obj-ubtu-24-700320" + } + ], + "prose": "Verify APT is configured to remove all software components after updated versions have been installed with the following command: \n \n$ grep -i remove-unused /etc/apt/apt.conf.d/50unattended-upgrades \nUnattended-Upgrade::Remove-Unused-Dependencies \"true\"; \nUnattended-Upgrade::Remove-Unused-Kernel-Packages \"true\"; \n \nIf the \"::Remove-Unused-Dependencies\" and \"::Remove-Unused-Kernel-Packages\" parameters are not set to \"true\", are commented out, or are missing, this is a finding." + }, + { + "id": "si-2.6_rem-ubtu-24-700320", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure APT to remove all software components after updated versions have been installed. \n \nAdd or update the following options to the \"/etc/apt/apt.conf.d/50unattended-upgrades\" file: \n \nUnattended-Upgrade::Remove-Unused-Dependencies \"true\"; \nUnattended-Upgrade::Remove-Unused-Kernel-Packages \"true\";" + } + ] + } + ] + }, + { + "control-id": "si-6", + "adds": [ + { + "position": "ending", + "parts": [ + { + "id": "si-6_obj-ubtu-24-100100", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270649", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270649r1067136_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100100", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002696", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must use a file integrity tool to verify correct operation of all security functions.", + "parts": [ + { + "id": "si-6_dsc-ubtu-24-100100", + "name": "guidance", + "prose": "Without verification, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. \n \nThis requirement applies to Ubuntu 24.04 LTS performing security function verification/testing and/or systems and environments that require this functionality." + } + ] + }, + { + "id": "si-6_asm-ubtu-24-100100", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-6_obj-ubtu-24-100100" + } + ], + "prose": "Verify that Advanced Intrusion Detection Environment (AIDE) is installed and verifies the correct operation of all security functions with the following command:\n\n$ dpkg -l | grep aide\nii aide 0.18.6-2build2 amd64 Advanced Intrusion Detection Environment - dynamic binary\nii aide-common 0.18.6-2build2 all Advanced Intrusion Detection Environment - Common files\n\nIf AIDE is not installed, ask the system administrator how file integrity checks are performed on the system. \n\nIf there is no application installed to perform integrity checks, this is a finding." + }, + { + "id": "si-6_rem-ubtu-24-100100", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Install the \"AIDE\" file integrity package:\n\n$ sudo apt install -y aide" + }, + { + "id": "si-6_obj-ubtu-24-100110", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270650", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270650r1155241_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100110", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002696", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must configure AIDE to perform file integrity checking on the file system if installed.", + "parts": [ + { + "id": "si-6_dsc-ubtu-24-100110", + "name": "guidance", + "prose": "Without verification, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. \n \nThis requirement applies to Ubuntu 24.04 LTS performing security function verification/testing and/or systems and environments that require this functionality." + } + ] + }, + { + "id": "si-6_asm-ubtu-24-100110", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-6_obj-ubtu-24-100110" + } + ], + "prose": "Note: If a file integrity tool other than Advanced Intrusion Detection Environment (AIDE) is employed, this requirement is not applicable.\n\nVerify AIDE is configured on the system by performing a manual check:\n\n$ sudo aide -c /etc/aide/aide.conf --check\n\nExample output:\n...\nStart timestamp: 2024-10-30 14:22:38 -0400 (AIDE 0.18.6)\nAIDE found differences between database and filesystem!!\n...\n\nIf AIDE is being used for system file integrity checking and the command fails, this is a finding." + }, + { + "id": "si-6_rem-ubtu-24-100110", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Initialize the AIDE package (this may take a few minutes):\n$ sudo aideinit\nRunning aide --init...\n\nThe new database will need to be renamed to be read by AIDE:\n$ sudo cp -p /var/lib/aide/aide.db.new /var/lib/aide/aide.db\n\nPerform a manual check:\n$ sudo aide -c /etc/aide/aide.conf --check\n\nExample output:\n...\nStart timestamp: 2024-10-30 14:22:38 -0400 (AIDE 0.18.6)\nAIDE found differences between database and filesystem!!\n...\n\nDone." + }, + { + "id": "si-6_obj-ubtu-24-100120", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270651", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270651r1068395_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100120", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002699", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must be configured so that the script which runs each 30 days or less to check file integrity is the default one.", + "parts": [ + { + "id": "si-6_dsc-ubtu-24-100120", + "name": "guidance", + "prose": "Without verification, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. \n \nNotifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications, such as lights. \n \nThis requirement applies to Ubuntu 24.04 LTS performing security function verification/testing and/or systems and environments that require this functionality." + } + ] + }, + { + "id": "si-6_asm-ubtu-24-100120", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-6_obj-ubtu-24-100120" + } + ], + "prose": "Note: If AIDE is not installed, this finding is not applicable.\n\nCheck the AIDE configuration file integrity installed on the system (the default configuration file is located at /etc/aide/aide.conf or in /etc/aide/aide.conf.d/) with the following command:\n$ sudo sha256sum /etc/aide/aide.conf\nf3bbea2552f2c5b475627850d8a5fba1659df6466986d5a18948d9821ecbe491 /etc/aide/aide.conf\n\nDownload the original aide-common package in the /tmp directory: \n$ cd /tmp; apt download aide-common \n\nGenerate the checksum from the aide.conf file in the downloaded .deb package:\n$ sudo dpkg-deb --fsys-tarfile /tmp/aide-common_0.18.6-2build2_all.deb | tar -xO ./usr/share/aide/config/aide/aide.conf | sha256sum\nf3bbea2552f2c5b475627850d8a5fba1659df6466986d5a18948d9821ecbe491 -\n\nIf the checksums of the system file (/etc/aide/aide.conf) and the extracted file do not match, this is a finding.\n\nTo verify the frequency of the file integrity checks, inspect the contents of the scheduled jobs as follows:\n\nChecking scheduled cron jobs:\n$ grep -r aide /etc/cron* /etc/crontab\n/etc/cron.daily/dailyaidecheck:SCRIPT=\"/usr/share/aide/bin/dailyaidecheck\"\n\nChecking the systemd timer (this will show when the next scheduled run occurs and the last time the AIDE check was triggered):\n$ sudo systemctl list-timers | grep aide\nThu 2024-10-31 02:01:58 EDT 10h Wed 2024-10-30 13:47:41 EDT - dailyaidecheck.timer dailyaidecheck.service\n\nThe contents of these files can be inspected with the following commands:\n$ sudo systemctl cat dailyaidecheck.timer\n$ sudo systemctl cat dailyaidecheck.service\n\nIf there is no AIDE script file in the cron directories or in the systemd timer, this is a finding." + }, + { + "id": "si-6_rem-ubtu-24-100120", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "The cron file for AIDE is fairly complex as it creates the report. This file is installed with the \"aide-common\" package, and the default can be restored by copying it from the package: \n \nDownload the original package to the /tmp dir: \n \n$ cd /tmp; apt download aide-common \n \nExtract the aide script to its original place: \n\n$ dpkg-deb --fsys-tarfile /tmp/aide-common_*.deb | sudo tar -x --wildcards ./usr/share/aide/config/cron.daily/dailyaidecheck* -C /\n \nCopy it to the cron.daily directory: \n \n$ sudo cp -f /usr/share/aide/config/cron.daily/aide /etc/cron.daily/dailyaidecheck*" + }, + { + "id": "si-6_obj-ubtu-24-100130", + "name": "assessment-objective", + "props": [ + { + "name": "stig-group-id", + "value": "V-270652", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-rule-id", + "value": "SV-270652r1067138_rule", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "stig-id", + "value": "UBTU-24-100130", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "severity", + "value": "medium", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-002702", + "ns": "https://public.cyber.mil/stigs/ns" + }, + { + "name": "cci", + "value": "CCI-001744", + "ns": "https://public.cyber.mil/stigs/ns" + } + ], + "prose": "Ubuntu 24.04 LTS must notify designated personnel if baseline configurations are changed in an unauthorized manner. The file integrity tool must notify the system administrator (SA) when changes to the baseline configuration or anomalies in the operation of any security functions are discovered.", + "parts": [ + { + "id": "si-6_dsc-ubtu-24-100130", + "name": "guidance", + "prose": "Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to Ubuntu 24.04 LTS. Changes to Ubuntu 24.04 LTS configurations can have unintended side effects, some of which may be relevant to security. \n \nDetecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of Ubuntu 24.04 LTS. Ubuntu 24.04 LTS' IMO/information system security officer (ISSO) and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.\n\nSatisfies: SRG-OS-000447-GPOS-00201, SRG-OS-000363-GPOS-00150" + } + ] + }, + { + "id": "si-6_asm-ubtu-24-100130", + "name": "assessment-method", + "props": [ + { + "name": "method", + "value": "TEST" + }, + { + "name": "platform", + "value": "cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*", + "ns": "https://example.org/ns/oscal-automation" + } + ], + "links": [ + { + "rel": "assessment-objective", + "href": "#si-6_obj-ubtu-24-100130" + } + ], + "prose": "Verify that Advanced Intrusion Detection Environment (AIDE) notifies the SA when anomalies in the operation of any security functions are discovered with the following command: \n \n$ grep SILENTREPORTS /etc/default/aide\nSILENTREPORTS=no\n \nIf \"SILENTREPORTS\" is set to \"yes\", is commented out, or is missing, this is a finding." + }, + { + "id": "si-6_rem-ubtu-24-100130", + "name": "remediation", + "ns": "https://example.org/ns/oscal-automation", + "prose": "Configure Ubuntu 24.04 LTS to notify designated personnel if baseline configurations are changed in an unauthorized manner. \n \nModify the \"SILENTREPORTS\" parameter in the \"/etc/default/aide\" file with a value of \"no\" if it does not already exist as follows:\n\nSILENTREPORTS=no" + } + ] + } + ] + } + ] + }, + "back-matter": { + "resources": [ + { + "uuid": "7e7104a2-af0d-5803-a260-7280e8006ecf", + "title": "Canonical Ubuntu 24.04 LTS Security Technical Implementation Guide, V1R5", + "rlinks": [ + { + "href": "../../../sources/disa/U_CAN_Ubuntu_24-04_LTS_STIG_V1R5_Manual-xccdf.xml", + "media-type": "application/xml", + "hashes": [ + { + "algorithm": "SHA-256", + "value": "4c527cf0ed912947bb0c51be15f1a6bbc5a4bf05469ae083d94a01471edea77c" + } + ] + } + ] + }, + { + "uuid": "e483dc41-2538-5a53-a9a1-07a1a5a38eb1", + "title": "The STIG's published OSCAL conversion, source of the CCI to control mapping", + "rlinks": [ + { + "href": "../../assessment-first/DISA/STIG_XCCDF%20to%20OSCAL%20Assessment%20Plans/ubuntu24.json", + "media-type": "application/oscal.assessment-plan+json", + "hashes": [ + { + "algorithm": "SHA-256", + "value": "aebb58537acdacaba6667d6076c2f6147baac9d436641789266cb857c126fd3e" + } + ] + } + ] + }, + { + "uuid": "aec779f8-11e6-54ac-a60d-c1f8193d0623", + "title": "NIST SP 800-53 Revision 5 catalog", + "rlinks": [ + { + "href": "https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json", + "media-type": "application/oscal.catalog+json" + } + ] + } + ] + } + } +} diff --git a/docs/analysis/2026-08-automating-technical-hardening-guidance/executable-first.html b/docs/analysis/2026-08-automating-technical-hardening-guidance/executable-first.html new file mode 100644 index 0000000..02ea23f --- /dev/null +++ b/docs/analysis/2026-08-automating-technical-hardening-guidance/executable-first.html @@ -0,0 +1,190 @@ + + + + + +Executable-first | Automating Technical Hardening Guidance with OSCAL + + + + + + + + + + + + + + + + + + + + + +
    + +

    Executable-first

    +

    The rule is an assessment objective part on a control and the check an executable assessment method beside it, carrying a script. The catalog adds both when its author supplies the check, a profile otherwise; a typed assembly on a component is the other construct.

    + +
    +

    1. Stakeholder roles and OSCAL models

    +
    +

    Executable-first treats a hardening rule as a requirement, as catalog-first does, in the Control layer. 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. The table shows the models each party uses.

    +

    Seven parties publish, implement or assess hardening guidance. The table maps each party to OSCAL models and groups guidance authors separately from automation providers and operators.

    +
    +
    + + + + + + + + + + + + +
    PartyOSCAL model
    Regulatory control providersNIST and other bodies publishing regulatory controls, such as SP 800-53catalog
    Mapping providersOrganisations linking guidance to frameworks through DISA's CCI list, NIST's OLIR programme or the Secure Controls FrameworkprofileEdits the profile that puts the objective and the method on the framework control. Placing the part is the tie.
    Hardening guidance authorsBenchmark publishers and technology providers author guidance in the same OSCAL model for each approach.
    Technical hardening guidance providersCIS, DISA and other benchmark publisherscatalogShips the guide as a catalog whose controls carry their own executable methods.
    Technology providersVendors publishing configuration guidance for hardware, software and services, independently or with benchmark publishers such as CIScatalog
    Automation providers and operatorsProviders build policy engines. System owners and auditors run checks to produce implementation responses or assessment results.
    Policy engine providersProviders of assessment and checking tools such as OPA, Kyverno, ScubaGear and OpenSCAPprofilePublishes a profile that imports a catalog untouched and adds executable methods for its engine.
    System ownersOrganisations implementing and documenting controls on a systemprofilesystem-security-planThe selection and the plan of record. Running the checks writes findings, not responses, so an owner who runs them is assessing.
    Independent auditorsAssessors running checks and reviewing results independently of system ownersruns 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 policy engine reads OSCAL, executes checks and writes OSCAL. Providers publish the checks; each flow identifies the party executing the checks.

    + +
    +

    2. Strengths and risks

    +
    +

    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 rule

      +

      A profile adds parts 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 script as environment variables, so one script serves many controls with each organisation's own value.

      +
    4. +
    5. + +

      Findings need no new field

      +

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

      +
    6. +
    7. + +

      The plan of record stays put

      +

      Methods sit on controls the assessment plan reads, so hundreds of checks add no control to the plan of record.

      +
    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, operated by the profile author.

      +
    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 runs nothing.

      +
    4. +
    5. + +

      The subject is a convention

      +

      The platform prop is a CPE that no SSP component carries, so which host runs a check is decided outside the schema.

      +
    6. +
    7. + +

      Claim and result never meet

      +

      The finding targets the objective and the response the control, so the plan of record cannot name the checks behind its claim.

      +
    8. +
    +
    +
    +
    +
    +

    3. Tracing rules and checks from implementation to assessment

    +
    +

    The chain connects a rule to checks, implementation claims and assessment results. Each step identifies the relationships a consumer must resolve and the fields used to resolve those relationships.

    +
      +
    1. Rule definition. 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 is outside OSCAL.
    8. +
    9. Runtime to Claim. The run writes no response, and the plan of record is untouched, 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 chain uses rule 1, data at rest, from the six questions page. Each step shows the fields and values a consumer follows. The relationship type indicates whether resolution uses schema-defined references, containment or publisher conventions.
    +
    +
    + + + + +
    + +
    + + + + + + + + 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 da48850..22a66b6 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 - + - + - +