What evidence do auditors commonly ask for on SC.L2-3.13.2 Security Engineering?

Documented security architecture and design principles; Secure development standards applied to in house software; Evidence principles are applied in design reviews.

What is the most common gap auditors find on SC.L2-3.13.2?

Principles documented but absent from actual design decisions

CMMC 2.0 · System and Communications Protection

`SC.L2-3.13.2` Security Engineering

Apply architectural design, software development techniques and systems engineering principles that promote effective information security.

Source: CMMC 2.0, SC.L2-3.13.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Evidence principles are applied in design reviews · Document repository

governing documentDocuments that govern the control

Documented security architecture and design principles · Policy repository / GRC workspace
Secure development standards applied to in house software · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Principles documented but absent from actual design decisions
Secure development standards not applied to acquired or outsourced code
No design review step in the development process

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

SC.L2-3.13.1 Boundary Protection · SC.L2-3.13.3 Role Separation