SA-4 ACQUISITION PROCESS

Page last updated:

PCF Compliance

Compliance with the documentation requirements defined in this control is a deployer responsibility.

Pivotal provides reference architecture documentation for all supported IaaS environments.
These reference architecture artifacts describe the deployment environment in which a PCF deployment is intended to operate.

The PCF operator delegates Identity Management functions to the existing enterprise Identity Management system, via UAA.
The deployer is responsible for integrating any approved PIV into the enterprise IdM.


Control Description

The organization includes the following requirements, descriptions, and criteria, explicitly or by reference, in the acquisition contract for the information system, system component, or information system service in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, guidelines, and organizational mission/business needs:

  1. Security functional requirements;
  2. Security strength requirements;
  3. Security assurance requirements;
  4. Security-related documentation requirements;
  5. Requirements for protecting security-related documentation;
  6. Description of the information system development environment and environment in which the system is intended to operate; and
  7. Acceptance criteria.

Supplemental Guidance

Information system components are discrete, identifiable information technology assets (e.g., hardware, software, or firmware) that represent the building blocks of an information system. Information system components include commercial information technology products. Security functional requirements include security capabilities, security functions, and security mechanisms. Security strength requirements associated with such capabilities, functions, and mechanisms include degree of correctness, completeness, resistance to direct attack, and resistance to tampering or bypass. Security assurance requirements include: (i) development processes, procedures, practices, and methodologies; and (ii) evidence from development and assessment activities providing grounds for confidence that the required security functionality has been implemented and the required security strength has been achieved. Security documentation requirements address all phases of the system development life cycle. Security functionality, assurance, and documentation requirements are expressed in terms of security controls and control enhancements that have been selected through the tailoring process. The security control tailoring process includes, for example, the specification of parameter values through the use of assignment and selection statements and the specification of platform dependencies and implementation information. Security documentation provides user and administrator guidance regarding the implementation and operation of security controls. The level of detail required in security documentation is based on the security category or classification level of the information system and the degree to which organizations depend on the stated security capability, functions, or mechanisms to meet overall risk response expectations (as defined in the organizational risk management strategy). Security requirements can also include organizationally mandated configuration settings specifying allowed functions, ports, protocols, and services. Acceptance criteria for information systems, information system components, and information system services are defined in the same manner as such criteria for any organizational acquisition or procurement. The Federal Acquisition Regulation (FAR) Section 7.103 contains information security requirements from FISMA.