Skip to content

Conversation

@SecurityCRob
Copy link
Contributor

adding mappings for BSI

adding mappings for BSI

Signed-off-by: CRob <69357996+SecurityCRob@users.noreply.github.com>
@SecurityCRob
Copy link
Contributor Author

SecurityCRob commented Jan 13, 2026

depends on:
#459
#460

related to:
#461
#462
#463
#464
#465
#466
#467

Comment on lines +76 to +78
- reference-id: BSI-TR-03185-2
entries:
- reference-id: GV.01
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BSI GV.01 states:

Information on how to contribute to the project MUST be documented.
Information about the expected quality of contributions SHOULD be
given.

This documentation requirement does not appear to be relevant to OSPS-AC-01, which pertains to mandatory enforcement of multi-factor authentication.

- reference-id: Claim 2.2.2
- reference-id: BSI-TR-03185-2
entries:
- reference-id: QA.06
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BSI QA-06 states:

All changes to the source code SHOULD be peer-reviewed.

This seems more similar to OSPS-QA-07.01: "When a commit is made to the primary branch, the project's version control system MUST require at least one non-author human approval of the changes before merging."

I can see a loose mapping to branch protection, but it's pretty weak compared to QA-07. Do we want to keep multiple outgoing mappings?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants