3.13.2

SC.L2-3.13.2 · Level 2

Employ architectural designs, software development techniques, and systems engineering principles…

NIST SP 800-171 Rev 2 · §3.13.2

Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

Assessment objectives

From NIST SP 800-171A · 6 objectives must be met to satisfy this control

3.13.2[a] architectural designs that promote effective information security are identified.

Examine

[SELECT FROM: Security planning policy; procedures addressing security plan development and implementation; procedures addressing security plan reviews and updates; enterprise architecture documentation; security plan; records of security plan reviews and updates; other relevant documents or records].

Interview

[SELECT FROM: Personnel with security planning and plan implementation responsibilities; personnel with information security responsibilities].

Test

[SELECT FROM: Organizational processes for security plan development, review, update, and approval; mechanisms supporting the system security plan].

3.13.2[b] software development techniques that promote effective information security are identified.

Examine

[SELECT FROM: Security planning policy; procedures addressing security plan development and implementation; procedures addressing security plan reviews and updates; enterprise architecture documentation; security plan; records of security plan reviews and updates; other relevant documents or records].

Interview

[SELECT FROM: Personnel with security planning and plan implementation responsibilities; personnel with information security responsibilities].

Test

[SELECT FROM: Organizational processes for security plan development, review, update, and approval; mechanisms supporting the system security plan].

3.13.2[c] systems engineering principles that promote effective information security are identified.

Examine

[SELECT FROM: Security planning policy; procedures addressing security plan development and implementation; procedures addressing security plan reviews and updates; enterprise architecture documentation; security plan; records of security plan reviews and updates; other relevant documents or records].

Interview

[SELECT FROM: Personnel with security planning and plan implementation responsibilities; personnel with information security responsibilities].

Test

[SELECT FROM: Organizational processes for security plan development, review, update, and approval; mechanisms supporting the system security plan].

3.13.2[d] identified architectural designs that promote effective information security are employed.

Examine

[SELECT FROM: Security planning policy; procedures addressing security plan development and implementation; procedures addressing security plan reviews and updates; enterprise architecture documentation; security plan; records of security plan reviews and updates; other relevant documents or records].

Interview

[SELECT FROM: Personnel with security planning and plan implementation responsibilities; personnel with information security responsibilities].

Test

[SELECT FROM: Organizational processes for security plan development, review, update, and approval; mechanisms supporting the system security plan].

3.13.2[e] identified software development techniques that promote effective information security are employed.

Examine

[SELECT FROM: Security planning policy; procedures addressing security plan development and implementation; procedures addressing security plan reviews and updates; enterprise architecture documentation; security plan; records of security plan reviews and updates; other relevant documents or records].

Interview

[SELECT FROM: Personnel with security planning and plan implementation responsibilities; personnel with information security responsibilities].

Test

[SELECT FROM: Organizational processes for security plan development, review, update, and approval; mechanisms supporting the system security plan].

3.13.2[f] identified systems engineering principles that promote effective information security are employed.

Examine

[SELECT FROM: Security planning policy; procedures addressing security plan development and implementation; procedures addressing security plan reviews and updates; enterprise architecture documentation; security plan; records of security plan reviews and updates; other relevant documents or records].

Interview

[SELECT FROM: Personnel with security planning and plan implementation responsibilities; personnel with information security responsibilities].

Test

[SELECT FROM: Organizational processes for security plan development, review, update, and approval; mechanisms supporting the system security plan].

What we look for in practice

The following are placeholder notes that should be refined based on practice experience.

What assessors look for in practice. Documented evidence that this control is implemented across all CUI-handling systems within scope. Specific artifacts vary, but expect requests for written procedures, system configurations, and operational records demonstrating the control is active.

Common failure patterns. Typical issues include incomplete documentation, inconsistent implementation across systems, and missing periodic review records. Refine this section as your practice accumulates direct assessment experience.

Strong evidence looks like. Formal policy referencing this control, technical configurations demonstrating enforcement, periodic review logs with sign-off, and procedures for handling exceptions.

Scoring and POA&M context. 5-point control under the DoD Assessment Methodology. Highest scoring impact — treat as a foundational requirement. Not POA&M-eligible — must be implemented at assessment time.