add security aou - #147
Merged
Merged
Conversation
RolandJentschETAS
requested review from
PandaeDo,
aschemmel-tech,
masc2023 and
pahmann
as code owners
August 20, 2026 14:18
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
masc2023
reviewed
Aug 20, 2026
masc2023
requested changes
Aug 20, 2026
masc2023
approved these changes
Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces templates and documentation updates to better support security-related Assumptions of Use (AoU) requirements for both features and components. It adds new template files for documenting security AoU requirements, updates the documentation structure to reference these templates, and improves clarity and traceability by updating references to requirement artifacts.
Documentation and Template Additions:
security_analysis/aou_requirements.rst, including guidance on how to fill it out for a specific feature.score/component_example/docs/security_analysis/aou_requirements.rst, with instructions and example requirement snippets.Documentation Structure Updates:
security_analysis/aou_requirements.rstfiles, ensuring these AoU requirements are part of the documentation structure. [1] [2]Reference and Traceability Improvements:
docs/template/index.rstto consistently use Sphinx Needs references (e.g.,:need:) for all requirement artifacts, improving traceability and clarity throughout the documentation. [1] [2]