PCF is compliant with this requirement. Pivotal regularly publishes security updates for Pivotal Cloud Foundry on Pivotal Network. Operators may subscribe to update notifications from Pivotal Network and use BOSH and Ops Manager to keep their deployments up-to-date.
When an operator applies a patch, PCF systematically rolls the update out to all VMs in a deployment, avoiding the need to patch individual VMs.
Pivotal provides the following incident response support resources:
RSS feed of Pivotal vulnerability reports: https://pivotal.io/security/rss
Pivotal Product Vulnerability Reports, archived on the Pivotal Application Security Team website
See Security Processes and Stemcells in the PCF documentation for more information.
The PCF deployer is responsible for performing scans for both configuration and vulnerabilities. PCF supports the use of third-party scanners, either through remote access scanning, or through local installation of third-party agents on the BOSH stemcells.
PCF deployers performing configuration scans against a PCF deployment should adjust their scanning benchmark to perform a cloud-native assessment, as opposed to employing a scanning benchmark intended for standalone Linux server deployments.
PCF deployers requiring assistance with scanning a deployment can contact the Pivotal Security team at email@example.com.
Organizations identify information systems affected by announced software flaws including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security responsibilities. Security-relevant software updates include, for example, patches, service packs, hot fixes, and anti-virus signatures. Organizations also address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations take advantage of available resources such as the Common Weakness Enumeration (CWE) or Common Vulnerabilities and Exposures (CVE) databases in remediating flaws discovered in organizational information systems. By incorporating flaw remediation into ongoing configuration management processes, required/anticipated remediation actions can be tracked and verified. Flaw remediation actions that can be tracked and verified include, for example, determining whether organizations follow US-CERT guidance and Information Assurance Vulnerability Alerts. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types. Organizations determine the degree and type of testing needed for the specific type of flaw remediation activity under consideration and also the types of changes that are to be configuration-managed. In some situations, organizations may determine that the testing of software and/or firmware updates is not necessary or practical, for example, when implementing simple anti-virus signature updates. Organizations may also consider in testing decisions, whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures.