300-745 practice question 11 of 15

A product manager is focused on maintaining the security integrity of a microservice-based application as new features are developed and integrated…

Full set: 58 questions
A product manager is focused on maintaining the security integrity of a microservice-based application as new features are developed and integrated. To ensure that known software vulnerabilities are not introduced into the product, it is crucial to implement a robust application security technique. The technique must be applied during the build phase of the software development lifecycle, which allows the team to proactively identify and address vulnerability risks before deployment. Which application security technique must be applied to accomplish the goal?
Answer options
A: secret detection
B: container scanning Correct answer
C: infrastructure as code scanning
D: Open API specification analysis
Correct Answer:
B. container scanning
Explanation

The scenario describes securing a microservice-based application by identifying known software vulnerabilities during the build phase. Microservices are commonly packaged and deployed as containers. Container scanning is the specific security technique designed to analyze container images for known vulnerabilities (CVEs) within the base operating system, application dependencies, and third-party libraries. This scan is integrated into the CI/CD pipeline after an image is built but before it is pushed to a registry or deployed, perfectly aligning with the requirement to proactively address vulnerabilities during the build phase of the software development lifecycle.

Why Incorrect

A. secret detection: This technique scans for hardcoded credentials (e.g., passwords, API keys), not known software vulnerabilities in application components or dependencies.
C. infrastructure as code scanning: This analyzes configuration files (e.g., Terraform, CloudFormation) for security misconfigurations in the cloud environment, not the application code itself.
D. Open API specification analysis: This reviews the design and structure of an API for security flaws but does not scan the underlying software components for known vulnerabilities. ---

References

1. Cisco Secure Application At-a-Glance. (2023). Cisco. In the "Key capabilities" section, it describes "Container Image Security" as a feature that "Scans container images for vulnerabilities and provides remediation guidance." This directly supports the use of container scanning to find known vulnerabilities.

2. National Institute of Standards and Technology (NIST). (September 2017). NIST Special Publication 800-190, Application Container Security Guide. Page 13, Section 3.3.1, "Static Analysis of Images." The document states, "Vulnerability scanning tools can be used to check for known vulnerabilities in the software included in an image... This should be done after an image is built but before it is pushed to a registry." This confirms the technique and its placement in the build phase.

3. Cisco. (2024). Implementing and Operating Cisco Security Core Technologies (SCOR 350-701) Official Cert Guide. Chapter 23, "Cloud Security," discusses the DevSecOps pipeline and notes that container scanning is a critical step to "scan the container image for vulnerabilities" before it is stored in a repository. This aligns the practice with the build phase of the SDLC.

Scroll to Top