> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/application-security/risk-management/monitor-and-manage-code-build/terraform-module-scan.md).
# Terraform Module Scanning
Prisma Cloud supports rendering and scanning both public, private, and locally cached Terraform modules (modules). This capability enables users to analyze misconfigurations that may result from the module definition and the variables defined in the module block.
## Public and Locally Cached Modules
Automated support for public modules is provided by the platform for all version control system (VCS) repositories that have been onboarded. For information on onboarding repositories refer to [Code Repositories](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/code-repositories/code-repositories.md).
### Public and Local Module Scanning through Checkov CLI
When using the Checkov CLI (CLI), make sure to include the `--download-external-modules true` flag to enable the automatic download of external modules.
Additionally, the CLI supports scanning the `.terraform` directory when modules have been downloaded locally.
Nested modules are not yet supported in scans performed in the `.terraform` directory.
## Private Module Support
Prisma Cloud supports the rendering and scanning of private modules through both CLI and VCS integrations. When using the CLI, refer to [Scanning Third-Party Terraform Modules with Checkov CLI](https://www.checkov.io/7.Scan%20Examples/Terraform.html) for instructions on including your API key, and optionally, the host.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.prismacloud.io/content-collections/application-security/risk-management/monitor-and-manage-code-build/terraform-module-scan.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.