> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/risk-assessment-and-prioritization/global-risk-management/cloud-security.md).

# Cloud Security

The **Cloud Security Risk Summary** page provides a consolidated view of security findings across the cloud services for a selected account. It helps users quickly assess risk distribution and identify services requiring immediate attention.

## To Access Cloud Security

Navigate to **Global Risk** > **Cloud Security**.

The top panel displays the metadata related to the executed scan:

<figure><img src="https://content.gitbook.com/content/xDmLTMQiowMHZ4CQPCvT/blobs/GlXFaX3DTZLcObl0Ztg4/cloud%20security%201.png" alt=""><figcaption></figcaption></figure>

* **Account -** Indicate the cloud account on which the scan is performed.
* **Trigger Type -** Indicates how the scan was initiated (e.g., AWS integration).
* **Triggered By -** Indicates whether the user or system that initiated the scan.
* **Scan Date -** Indicates the timestamp of when the scan was executed.&#x20;

The column below displays the details of the cloud services evaluated during the scan.

<figure><img src="https://content.gitbook.com/content/xDmLTMQiowMHZ4CQPCvT/blobs/OM3iorZDZCh9wvIP54HL/cloud%20security%20.png" alt=""><figcaption></figcaption></figure>

* **Services** - Displays the name of the cloud service evaluated during the scan.&#x20;
* **Resources** - Displays the number of resources evaluated during the scan.&#x20;
* **Rules** - Displays the number of security or compliance rules applied to evaluate the resources within each service.
* **Summary** - Displays the number of security alerts identified during the scan.&#x20;

## To Access Remediation in Cloud Security

Delivery Shield integrates CSPM (Cloud Security Posture Management) remediation, letting teams detect cloud security misconfigurations and generate automated fixes for them — directly from the findings, without switching to external cloud consoles or separate remediation tools.&#x20;

* Navigate to Global Risk > Cloud Security.
* Select the cloud service for which you want to apply remediation and click on it.

<img src="https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2Ffq4ErNJE8E0A0UcapIYB%2Funknown.png?alt=media&amp;token=fd351a60-d87f-4793-bf86-a23cdcbddde8" alt="" height="199" width="602">

* The Findings page is displayed.
* Expand the Affected Resources section.
* Expand the affected resource for which you want to apply remediation.
* Click Remediation.

<img src="https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2Fyw9KaMN0JaNe9GILyvZn%2Funknown.png?alt=media&amp;token=2eb65b96-0832-4f8f-a82f-f9472e1daaa4" alt="" height="260" width="602">

* A detailed analysis is provided, covering:
* Overview — summary of the vulnerability and affected component.
* Fix Plan — recommended remediation approach.
* Remediation — the actionable fix, ready to apply.

<img src="https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2FTaDbE5tR3SDWLJ7fFi1S%2Funknown.png?alt=media&amp;token=2179e582-8aaa-49ef-a8d3-da97616ca881" alt="" height="334.6232090928799" width="602">

\ <br>
