An architect is integrating Prisma Cloud with a CI/CD pipeline (such as GitHub Actions or Jenkins) to perform Infrastructure as Code (IaC) scanning. Which TWO scanning targets or mechanisms are supported by Prisma Cloud for IaC security? (Choose two)
Prisma Cloud's IaC scanning natively parses Terraform and AWS CloudFormation templates, detecting misconfigurations before deployment. The IaC CLI and GitHub Actions integration let architects embed this check directly into CI/CD pipelines, satisfying the shift-left requirement in the stem.
Why this answer
Option A is correct because Prisma Cloud's IaC scanning explicitly supports Terraform and AWS CloudFormation templates, and it can be invoked through the Prisma Cloud IaC CLI (twistcli / checkov-based scanning) or via native CI/CD integrations such as the GitHub Actions integration, making it a supported scanning target and mechanism for pipeline use. Option B is correct because Prisma Cloud also scans Kubernetes YAML manifests and Helm charts stored in git repositories to detect misconfigurations, which is a core IaC security capability for container-orchestration configuration. Option C is not correct because Prisma Cloud IaC scanning analyzes declarative infrastructure code, not live TCP packet sniffing on a network switch interface.
Option D is not correct because SNMPv1 is a network-management protocol and has nothing to do with querying the Jenkins REST API for IaC scanning. Option E is not correct because Prisma Cloud Defenders run as containers or hosts in cloud/Kubernetes environments, not inside a laptop BIOS, which is not a supported IaC scanning mechanism.