> 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/data-security-posture-management/how-to-articles/configure-the-scanning-settings-for-supported-services.md).

# Configure the scanning settings for supported services

This article describes how to do the following:

* Configure the scanning settings for services you want to scan and classify across multiple accounts. For example, prohibit the scanning or classification of an S3 bucket associated with a specific AWS account.
* Configure the scanning settings for a single account.
* Configure the scanning settings for multiple accounts.

### Configure the scanning settings for a single account

1. Navigate to the account you want to configure.
   1. In Prisma Cloud DSPM side menu, click **Preferences** to open the Settings window.
   2. In the Integrations tab, navigate to the required cloud platform thumbnail and click **Configure**.\
      ![](/files/88L6kk4fk8nLV47TgJJ4)
2. In the Connected Subscriptions area, select the name of the single account you want to configure, and then click the Settings icon.

   ![](/files/PgxhZBa0N1AG6pxrJ5oq)
3. In the Scanning options drawer, specify the scanning settings for each service associated with the account.\
   For example, turn on SQL Server to permit scanning the SQL Server of the selected account, or turn off MongoDB to prohibit scanning the MongoDB of the selected account.\
   ![](/files/BQw9iITycaoMXDLMOf9M)

### Configure the scanning settings for multiple accounts

Use bulk actions to configure the scanning settings for multiple accounts. For example prohibit the scanning of an RDS classification across all staging accounts.

1. Navigate to the account you want to configure.
   1. In the Prisma Cloud DSPM side menu, click Settings to open the Settings window.
   2. In the Integrations tab, navigate to the required cloud platform thumbnail and click Configure.

      ![](/files/88L6kk4fk8nLV47TgJJ4)
2. In the Connected Subscriptions area, select the names of the accounts you want to configure.
3. In the Options drop down, select Change Scanning Settings.\
   ![](/files/IrsZvTIBPL34h02ROiHW)
4. In the Scanings Settings drawer, click the Select drop down, and configure the scanning settings for each supported service:
   * Choose Enable to permit the scanning of the supported service.
   * Choose Disable to prohibit the scanning of the supported service.

     ![](/files/AxIErqxlS6bTSwhEzkxM)

### Monitoring an account

The **Monitoring** toggle button provides you with the options to enable or disable the monitoring of an account.

![](/files/OSBkZpdvzvTYZkmDTKS6)

**When the toggle button is turned from enabled to disabled, or vice-versa, the changes do not take effect immediately. Wait momentarily until the changes do take effect.**


---

# 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/data-security-posture-management/how-to-articles/configure-the-scanning-settings-for-supported-services.md?ask=<question>&goal=<endgoal>
```

`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.