Skip to content

Add requirement traceability validation#2

Open
solomonsjoseph wants to merge 2 commits into
mainfrom
hardening/requirement-traceability-check
Open

Add requirement traceability validation#2
solomonsjoseph wants to merge 2 commits into
mainfrom
hardening/requirement-traceability-check

Conversation

@solomonsjoseph
Copy link
Copy Markdown
Owner

Summary

  • Add scripts/check-requirement-traceability.sh to validate spec security requirement IDs against context/06-security-requirements.md.
  • Run the traceability check from methodology verification and CI.
  • Document the automated methodology checks in the README.

Validation

  • chmod +x scripts/check-requirement-traceability.sh
  • scripts/check-security-methodology.sh passed.
  • scripts/verify-methodology.sh passed.
  • scripts/check-requirement-traceability.sh passed.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dff6fa84e3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +28 to +29
for requirement_id in id_pattern.findall(line):
if requirement_id not in valid_ids:
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Reject malformed security IDs in specs

The traceability check only validates tokens that already match \b[A-Z][A-Z0-9]+-\d{3}\b, so malformed references in ## Security Requirements (for example AUTHN-01 or lowercase IDs) are silently ignored and the check still passes. This defeats the purpose of enforcing spec-to-requirement traceability, because a typo can remove a requirement from validation without triggering CI.

Useful? React with 👍 / 👎.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant