id: "SA-17(01)" title: "Formal Policy Model" family: "SA" family_name: "System and Services Acquisition" sort_id: "sa-17.01" priority: "P1" implementation_level: "organization" parent: "SA-17" enhancement: True
Statement
Require the developer of the system, system component, or system service to:
Produce, as an integral part of the development process, a formal policy model describing the {{ insert: param, sa-17.1_prm_1 }} to be enforced; and
Prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security and privacy policy when implemented.
Guidance
Formal models describe specific behaviors or security and privacy policies using formal languages, thus enabling the correctness of those behaviors and policies to be formally proven. Not all components of systems can be modeled. Generally, formal specifications are scoped to the behaviors or policies of interest, such as nondiscretionary access control policies. Organizations choose the formal modeling language and approach based on the nature of the behaviors and policies to be described and the available tools.
Assessment Objective: as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the {{ insert: param, sa-17.01_odp.01 }} to be enforced;
Assessment Objective: as an integral part of the development process, the developer of the system, system component, or system service is required to produce a formal policy model describing the {{ insert: param, sa-17.01_odp.02 }} to be enforced;
Assessment Objective: the developer of the system, system component, or system service is required to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational security policy when implemented;
Assessment Objective: the developer of the system, system component, or system service is required to prove that the formal policy model is internally consistent and sufficient to enforce the defined elements of the organizational privacy policy when implemented.
System and services acquisition policy
system and services acquisition procedures
enterprise architecture policy
enterprise architecture documentation
procedures addressing developer security and privacy architecture and design specifications for the system
solicitation documentation
acquisition documentation
service level agreements
acquisition contracts for the system, system component, or system service
system design documentation
system configuration settings and associated documentation
system security plan
privacy plan
other relevant documents or records
Organizational personnel with acquisition responsibilities
organizational personnel with information security and privacy responsibilities
system developer