security-rules.md: Reporting section predates the newer complianceCategory-tagged rules
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Read the Reporting section in docs/security-rules.md and compare its wording with docs/security-compliance-categories.md. Update the sentence so it makes clear that multiple rules carry complianceCategory and points to the category list as the source of truth. Done when the section no longer implies that only two rules are tagged and the categories document remains authoritative.
Written by the indexing model from the issue text.
Description
Summary
The ## Reporting section of docs/security-rules.md opens with:
Both rules are tagged with a
complianceCategory(business-continuityandaccess-controlrespectively...)
This sentence predates the newer compliance-tagged rules and now reads as if only CDS-SEC-080/081 carry categories, when CDS-SEC-090/091 (and others) also carry complianceCategory (system-hardening) and participate in --group-by-category and --report nis2.
(The intro sentence above the rules table was reworded in #895 to cover 090/091; this section was not.)
Proposed change
Reword to enumerate the tagged rules or link to docs/security-compliance-categories.md as the authoritative category list, e.g.:
Rules tagged with a
complianceCategory(e.g.business-continuity,access-control,system-hardening; see security-compliance-categories.md) participate incds security --group-by-categoryandcds security --report nis2mode...
Acceptance criteria
- The section no longer implies only two rules are tagged;
docs/security-compliance-categories.mdremains the single source for the category list.
Found by a full-repo audit of main @ 275b6d9.
- Dominant language
- Python
- Stars
- 8
- Forks
- 12
- Avg merge
- 20h 2m
- Merged PRs (30d)
- 140
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RonaldHensbergen/composable-data-stack
-
area:cli priority:low refactor size:small
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
RonaldHensbergen/composable-data-stack#915 ·
Maintainers usually reply within 1 day
-
area:cli priority:low refactor size:small
Difficulty 1/5 Under an hour Newbie friendliness 88/100
RonaldHensbergen/composable-data-stack#906 ·
Maintainers usually reply within 1 day
-
area:docs documentation hacktoberfest priority:low size:small
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
RonaldHensbergen/composable-data-stack#865 ·
Maintainers usually reply within 1 day
-
area:cli area:configuration bug priority:medium size:medium
Difficulty 4/5 3-5 days Newbie friendliness 53/100
RonaldHensbergen/composable-data-stack#1010 ·
Maintainers usually reply within 1 day
-
area:cli enhancement priority:low python size:small
Difficulty 4/5 1-2 days Newbie friendliness 48/100
RonaldHensbergen/composable-data-stack#1008 ·
Maintainers usually reply within 1 day
All issues in RonaldHensbergen/composable-data-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/agent-lightning#661 ·
Maintainers usually reply within 2 days
-
area/profiles comp/cli P3 type/feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NousResearch/hermes-agent#146372 ·
Maintainers usually reply within 1 day
-
[BUG] OpenAI-compatible embedding model alias breaks embedder constructionPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Document obs-aw-automerge contract and fix automerge doc inconsistenciesPossibly taken @github-actions claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
GeoSeries scale and skew tests fail with pytest 9.2.0Possibly taken @jiayuasu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day