Technology giant Google has reportedly announced to have rolled out an important update to its Cloud Build Continuous Integration/Continuous Delivery (CI/CD) software development platform. Reports cite, the update also includes automated container registry vulnerability scanning service that can scan all container images which are built using the cloud service.
The vulnerability scanning feature is designed to ensure that the containers deployed by various businesses, which are adopting the modern DevOps practices, do not contain any known vulnerabilities.
Google reportedly emphasized that the only way to make sure that the security protocols are always adhered to is by making the process automated. This is exactly why the vulnerability scanning process is automated as it will automatically scan all Cloud Build images that are created and stored in the Container Registry using the service.
According to a report by the Silicon Angle, the new vulnerability scanner essentially scans for known security threats or vulnerabilities during the initial stages of the CI/CD process to prevent any potentially corrupted images from being deployed.
For the record, the CI/CD process is a software development practice where developers maintain a common repository in which all the updated code is integrated and stored and programmers enter newly written code into the repository frequently. This method helps eliminate redundancies while allowing automated and quick roll out of software bug fixes and deployment of software updates.
The Cloud Build service currently utilizes the standard security databases to look for new issues, cite reports. The latest update reportedly allows the service to discern package vulnerabilities in Alpine, Debian and Ubuntu systems with support for RHEL and CentOS to be announced soon.
Once the service discovers an issue, it will immediately notify the user about it, however, the service can be configured using Cloud Functions and Pub/Sub notifications to take automatic actions. Users would also receive detailed reports about the severity of the shortcoming, the affected packages and the solutions available that could resolve the issue.