> 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-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/ibm-cloud-cloud-onboarding/ibm-cloud-security-capabilities-and-deployment-planning.md).

# IBM Cloud security capabilities and deployment planning

Plan IBM Cloud onboarding by reviewing Cortex XDR security capabilities, supported regions, and deployment requirements.

Plan your deployment by reviewing the scope, scan mode, security capabilities, and regions that Cortex XDR supports for IBM Cloud. The onboarding process deploys everything with a single Terraform authentication template.

## Onboarding scope and scan mode

IBM Cloud onboarding has a fixed scope and scan mode. You don't select either one in the onboarding wizard.

* **Scope:** Account. Each cloud instance in Cortex XDR represents one IBM Cloud account. If you manage several accounts, for example in an IBM Cloud enterprise, onboard each account separately.
* **Scan mode:** Cloud scan. Cortex XDR reads your account configuration from the Cortex XDR environment. Outposts aren't supported for IBM Cloud.
* **Provisioning method:** Terraform. Cortex XDR generates a Terraform authentication template that you run with your own IBM Cloud credentials.

## Security capabilities

IBM Cloud onboarding supports the Discovery capability. This capability is mandatory and Cortex XDR deploys it automatically when you onboard an IBM Cloud account.

| Capability | Service ID created                                  | Purpose                                                                                                                                                                                |
| ---------- | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Discovery  | Read-only service ID (`cortex-<suffix>-service-id`) | Read-only discovery and inventory of IBM Cloud resources and their configuration, including Key Protect, Secrets Manager, Cloud Object Storage, Activity Tracker, and resource groups. |

The following capabilities aren't currently supported for IBM Cloud:

* Agentless disk scanning
* Data security posture management (DSPM)
* Audit logs and flow logs
* Registry scanning
* Serverless scanning
* Automation

## Supported regions

Cortex XDR discovers resources in the following IBM Cloud regions. When you onboard an account, you can include or exclude specific regions with the scope modification settings in the onboarding wizard.

| Region name   | Region ID  |
| ------------- | ---------- |
| Dallas        | `us-south` |
| Washington DC | `us-east`  |
| Toronto       | `ca-tor`   |
| Montreal      | `ca-mon`   |
| Sao Paulo     | `br-sao`   |
| London        | `eu-gb`    |
| Frankfurt     | `eu-de`    |
| Madrid        | `eu-es`    |
| Tokyo         | `jp-tok`   |
| Osaka         | `jp-osa`   |
| Sydney        | `au-syd`   |
| Chennai       | `in-che`   |
| Mumbai        | `in-mum`   |

Account-level resources are global in IBM Cloud. Region scope modifications don't affect them.

## Deployment planning checklist

Before you start, decide the following:

* **Who runs the template:** A user with administrator access in the IBM Cloud account runs the Terraform template with an IBM Cloud API key. For the required access, see [Prerequisites for onboarding IBM Cloud](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/ibm-cloud-cloud-onboarding/prerequisites-for-onboarding-ibm-cloud.md).
* **Where you store the Terraform files:** Keep the Terraform files and the Terraform state file in a dedicated, secure directory for each IBM Cloud account. You need them later to rotate the API key or to offboard the account. The state file contains the API key, so treat it as sensitive.
* **Which regions to monitor:** Decide whether to monitor all supported regions, or to include or exclude specific regions.
* **Which tags to add:** Decide which tags Cortex XDR adds to the service ID it creates in your account, in addition to the mandatory `managed_by:paloaltonetworks` tag.


---

# 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-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/ibm-cloud-cloud-onboarding/ibm-cloud-security-capabilities-and-deployment-planning.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.
