An enterprise security team wants to enforce security policies for container images before deployment. They need a solution that allows developers to scan images locally, ensures compliance with organ

Question

Options

• AInline Scanning in CI/CD Pipelines
• BBehavior-Based Malware Analysis After Deployment
• CManual Security Audits of Container Images
• DCloud-Based Signature-Based Scanning

• A
  85% (35)
• B
  2% (1)
• C
  5% (2)
• D
  7% (3)

Explanation

Option A: Inline scanning during the CI/CD pipeline ensures that container images are assessed before they are pushed to production. This method helps developers catch vulnerabilities early, enforce security policies automatically, and integrate with DevSecOps workflows to prevent deployment of insecure images. Option B: This method involves monitoring container behavior after deployment, which does not prevent vulnerable images from entering production. The goal of pre-runtime protection is to stop threats before they reach the runtime stage. Option C: Manual audits are time-consuming, error-prone, and not scalable for enterprise environments. Automated scanning within the CI/CD pipeline provides a more effective and consistent approach to image assessment. Option D: While cloud-based signature scanning can identify known threats, it often lacks integration with CI/CD pipelines and does not provide real-time feedback to developers. It is more reactive than proactive.

No community discussion yet for this question.