> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-commands-guide/scanner-commands.md).

# Scanner Commands

* [enableScanners](#enablescanners)

### enableScanners

***

Enables or disables source-code scanners and updates their scan configuration for one or more repositories.

#### Arguments

<details>

<summary>Arguments</summary>

| Argument Name         | Description                                                                                                                                   | Required |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| repository\_ids       | A comma-separated list of repository asset IDs to configure scanners for.                                                                     | Required |
| enable\_scanners      | A comma-separated list of scanners to enable. Possible values are: SECRETS, IAC, SCA.                                                         | Optional |
| disable\_scanners     | A comma-separated list of scanners to disable. Possible values are: SECRETS, IAC, SCA.                                                        | Optional |
| secret\_validation    | Whether to enable live validation of discovered secrets. Relevant only when the SECRETS scanner is enabled. Possible values are: true, false. | Optional |
| pr\_scanning          | Whether to enable scanning on pull requests. Possible values are: true, false.                                                                | Optional |
| block\_on\_error      | Whether to block deployment when a scanner errors. Possible values are: true, false.                                                          | Optional |
| tag\_resource\_blocks | Whether to enable tagging of resource blocks. Possible values are: true, false.                                                               | Optional |
| tag\_module\_blocks   | Whether to enable tagging of module blocks. Possible values are: true, false.                                                                 | Optional |
| exclude\_paths        | A comma-separated list of file paths to exclude from scanning.                                                                                | Optional |

</details>

#### Outputs

<details>

<summary>Outputs</summary>

**Core.ScannerConfiguration.RepositoryID** *string*

The repository asset ID.

**Core.ScannerConfiguration.Status** *string*

The configuration update result: "updated" or "failed".

**Core.ScannerConfiguration.Error** *string*

The error message when the update failed.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-commands-guide/scanner-commands.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.