> 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/runtime-security/agentless-scanning/configure-accounts.md).
# Configure Agentless Scanning
Agentless scanning provides visibility into vulnerabilities and compliance risks on cloud workloads by scanning the root volumes of snapshots. The agentless scanning architecture lets you inspect a host and the container images in that host without having to install an agent or affecting its execution.
To learn more about the architecture and scan results, see [How agentless scanning works?](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/runtime-security/agentless-scanning/agentless-scanning.md)
To configure agentless scanning for your cloud accounts, you must onboard the accounts to Prisma Cloud.
Ensure you can connect to the Prisma Cloud Console over HTTPS from your cloud account. Ideally, your security group denies all incoming traffic and allows one egress port. Review the egress port configuration needed to [enable access to the Prisma Cloud console](/content-collections/get-started/console-prerequisites.md).
Complete the steps in the following pages to enable agentless scanning as you onboard accounts from the supported cloud providers.
* [Amazon Web Services](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/connect/connect-cloud-accounts/onboard-aws/onboard-aws.md)
* [Microsoft Azure](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/connect/connect-cloud-accounts/onboard-your-azure-account/onboard-your-azure-account.md)
* [Google Cloud Platform](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/connect/connect-cloud-accounts/onboard-gcp/onboard-gcp.md)
* [Oracle Cloud Infrastructure](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/connect/connect-cloud-accounts/onboard-your-oci-account/onboard-your-oci-account.md)
When you onboard the account on Prisma Cloud, you can grant the needed permissions for all accounts in your organization. The onboarded accounts show up in **Runtime Security > Manage > Cloud accounts** after up to 24 hours.
You can change the configuration after onboarding your cloud accounts in **Runtime Security > Manage > Cloud accounts**.
## Disable Accounts
When you disable an account in Prisma Cloud, the account remains available under **Runtime Security > Manage > Cloud accounts** for up to 24 hours. After that time, the disabled account is removed from **Runtime Security > Manage > Cloud accounts**. Until the account is removed, errors occur when you run discovery, agentless, or serverless scans. Any updates to the disabled account are ignored.
The disabled account is marked as deleted in **Runtime Security > Manage > Cloud accounts** with a garbage bin icon next to it, and you can delete it safely. If you had deleted the account in **Runtime Security > Manage > Cloud accounts** but then disabled it, the account will show up again in **Runtime Security > Manage > Cloud accounts** with a garbage bin icon next to it, and you can delete it safely.
## Bulk Actions
Prisma Cloud supports performing agentless configuration at scale. Different cloud providers and authentication subtypes require different configuration fields, which also limits your ability to change accounts in bulk. The Prisma Cloud Console displays all the configuration fields that can be changed across all the selected accounts, and hides those that differ to prevent accidental misconfiguration.
Only change the configuration of multiple accounts from the same cloud provider and of the same authentication subtype. If you select accounts from different providers, you can’t change agentless configuration fields.
The following procedure shows the steps needed to configure agentless scanning for multiple accounts at the same time.
1. Go to **Runtime Security > Manage > Cloud accounts**
2. Select multiple accounts.
Only select accounts from the same cloud provider and of the same authentication subtype. If you select accounts from different providers, you can’t change agentless configuration fields.
3. Click the **Bulk actions** dropdown.
4. Select the **Agentless configuration** button.
5. Change the configuration values for the selected accounts.
* Select **Save** to save the configuration for the selected accounts.
---
# 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/runtime-security/agentless-scanning/configure-accounts.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.