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(5)

developer security architecture and design  | conceptually simple design

assessment objective:

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

sa-17(5)(a)

design and structure the security-relevant hardware, software, and firmware to use a complete, conceptually simple protection mechanism with precisely defined semantics; and

sa-17(5)(b)

internally structure the security-relevant hardware, software, and firmware with specific regard for this mechanism.

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; information system design documentation; information system security architecture documentation; information system configuration settings and associated documentation; developer documentation describing design and structure of security-relevant hardware, software, and firmware components; other relevant documents or records].

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