← SSDF

SSDF

Source and Review

Source control is where proposed software changes become an accountable record. Review practices should make the change’s purpose, author, approval and relevant security considerations visible before code enters a trusted branch.

How the work is approached

  1. Define repository access and branch protection rules
  2. Review changes and detect secrets or unsafe patterns
  3. Link approvals, checks and exceptions to the change record

A reviewer can follow a software change from its request through approval and testing. The team can distinguish reviewed work from emergency exceptions and unauthorized modifications. The review should retain repository governance and access decisions so the team can explain the decisions later.

Useful starting information

  • Repository structure and contributor roles
  • Change and approval records
  • Secret handling and review rules

Outputs to agree and review

  • Repository governance and access decisions
  • Review and exception records
  • Change-to-test traceability

A practical example

A pull request changes authentication behavior. The review identifies the affected trust boundary, requires focused tests and records the approval before merging into the release branch.

What to watch for

A second reviewer adds value only when the review has clear expectations and the reviewer can assess the change.

Scope, ownership and acceptance criteria should be agreed for the actual environment. The example describes a planning approach, not a promised result or a determination of compliance.

Planning worksheet

Use this short worksheet to record your starting information, action owners and evidence locations before a detailed review.

Download the Source and Review worksheet (CSV)

Continue within this service

Framework reference

NIST SSDF publication. Use the baseline and direction applicable to your environment and engagement.

Ready to discuss your scope?

Get in touch