EvidenceSheet

SA-20 Customized Development of Critical Components. Reimplement or custom develop the following critical system components: [organization-defined]

Customized Development of Critical Components. Reimplement or custom develop the following critical system components: [organization-defined].

5
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Development records for those components under the organisation's secure development life cycle · Source control / CI pipeline
  • Evidence of why the commercially available component was unacceptable, linking to a supply chain risk finding · Document repository
  • Assurance evidence for the custom component, such as design review and testing results · Document repository

governing documentDocuments that govern the control

  • The defined list of critical system components to be reimplemented or custom developed, with the criticality rationale · Document repository
  • Ongoing maintenance ownership for the custom component · Document repository

First move

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

SA-17 Developer Security and Privacy Architecture and Design. Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that: Is consistent with the organization's · SA-21 Developer Screening. Require that the developer of [organization-defined]: Has appropriate access authorizations as determined by assigned [organization-defined] ; and Satisfies the following additional personnel screening criteria: [organization-defined]