Applicable

(Y)es / (N)o

(C)onfidentiality

(I)ntegrity

(A)vailability

RPN

(C+I+A)

(S)atisfactory

L1

M2

H3

L1

M2

H3

L1

M2

H3

(O)ther than satisfactory +##

sa-17(2)

developer security architecture and design  | security-relevant components

assessment objective:

Determine if the organization requires the developer of the information system, system component, or information system service to:

sa-17(2)(a)

sa-17(2)(a)[1]

define security-relevant hardware;

sa-17(2)(a)[2]

define security-relevant software;

sa-17(2)(a)[3]

define security-relevant firmware; and

sa-17(2)(b)

provide a rationale that the definition for security-relevant hardware, software, and firmware components is complete.

potential assessment methods and objects:

Examine: [select from: System and services acquisition policy; enterprise architecture policy; procedures addressing developer security architecture and design specification for the information system; solicitation documentation; acquisition documentation; service-level agreements; acquisition contracts for the information system, system component, or information system service; list of security-relevant hardware, software, and firmware components;  documented rationale of completeness regarding definitions provided for security-relevant hardware, software, and firmware; other relevant documents or records].

Interview: [select from: Organizational personnel with system and services acquisition responsibilities; organizational personnel with information security responsibilities; system developers; organizational personnel with security architecture and design responsibilities].