# Security > Review security findings, track compliance, and suppress accepted risks across your connected clouds --- Site [llms.txt](/llms.txt) --- The Security section brings your cloud security and compliance posture into the CloudBolt Platform. Each configured cloud provider (AWS and Azure) gets its own Security & Compliance page with two tabs: **Findings** (the default) and **Compliance**. A shared **Suppressions** page covers both clouds. The Security section lets you: - **Review findings:** Browse, filter, and export security findings across your connected accounts and subscriptions, with severity and type breakdowns at a glance. - **Track compliance:** See per-framework compliance scores, a 30-day trend, and the controls that are failing. - **Suppress findings:** Mute individual findings that are accepted risks or false positives, and manage all active suppressions in one place. AWS findings come from AWS Security Hub, which aggregates compliance findings from your standards subscriptions, vulnerability findings from Amazon Inspector, and exposure findings from Security Hub Exposure Detection. Azure findings come from Microsoft Defender for Cloud recommendations. Data appears within 24 hours of the first successful scan. Viewing security data requires no special role. Creating or removing suppressions requires the Administrator or Operations role. ## Access the Security section 1. Log in to the CloudBolt Platform. 1. In the sidebar, select **Security** to expand it, then choose **AWS**, **Azure**, or **Suppressions**. 1. On a cloud's Security & Compliance page, switch between the **Findings** and **Compliance** tabs. ## Findings The **Findings** tab summarizes your open findings and lists them in a filterable table. Summary tiles show **Total findings**, **Affected resources**, and **Affected accounts** (AWS) or **Affected subscriptions** (Azure). "By severity" tiles break the total down into **Critical**, **High**, **Medium**, **Low**, and **Info**. On Azure, selecting a severity tile filters the table. AWS adds "By finding type" tiles for **Compliance**, **Vulnerability**, and **Exposure** findings. If the latest scan had failures, an amber banner appears above the tiles: "Last scan: {time}. {failed} of {configured} accounts/subscriptions failed during this scan." You can dismiss the banner; it reappears with the next day's snapshot. | Element | Description | | --- | --- | | Findings table (AWS) | Shows Type, Severity, Status, Control, Framework, Resource, Account, Region, Source, CVE / CVSS, and Recommendation, plus an **Open in AWS Security Hub console** deep link and a Suppress button on each row. | | Findings table (Azure) | Shows Severity, Recommendation, Resource, Subscription, and Categories. Expand a row for the full detail panel (Description, Remediation, Threats, Implementation effort, User impact, and Region) with **Open in Azure portal** and **Suppress finding** buttons. A search box lets you search by recommendation or resource. | | Filters | Filter chips above the table narrow the result set. When the table is capped, it shows "Showing first {n} of {total} findings — refine filters to narrow the set." | | Export | The export menu downloads the loaded rows as CSV or JSON. | ## Compliance The **Compliance** tab shows a card for each framework with its compliance percentage (passing controls ÷ total controls), a progress bar, and "{failing} failing of {total} controls". Frameworks with nothing assessed show **Not assessed**. On Azure, cards are grouped by framework family with version chips. Each framework also has a **Compliance trend (last 30 days)** line chart; on Azure, the chart shows "Trends will be available after 7 days of tracking" until 7 days of history exist. Select a framework card to drill into its control list. AWS shows Title, Status, Max severity, Failing resources, and Recommendation for each control; Azure shows Title, Status, Failing resources, and Total resources. On Azure, selecting a failing count jumps to the Findings tab pre-filtered to that control. On Azure, some regulatory frameworks (NIST 800-53, CIS, HIPAA, and PCI) can appear marked **Projected** ("Projected from your enabled policies") even if you never formally assigned them in Defender. CloudBolt maps the Azure policies you already have enabled onto the framework's controls, and a coverage note ("{N} of {M} framework controls assessed") shows how much of the framework those policies actually cover. ## Manage suppressions Suppressing hides a finding from the tables, KPI counts, and compliance calculations without deleting any scan data. Suppressions apply to individual findings and are excluded in near-real time; you can remove a suppression later to bring the finding back. ### Suppress a finding 1. On the **Findings** tab, select the Suppress button on the finding (the bell icon in the row on AWS, or **Suppress finding** in the expanded detail panel on Azure). The **Suppress finding** modal opens. 1. Enter a **Reason** (required). 1. Optionally set a **Suppress until** date. Leave it blank to suppress indefinitely. 1. Select **Suppress**. ### Remove a suppression The **Suppressions** page (**Security** > **Suppressions**) lists active suppressions across both clouds. To remove one: 1. In the sidebar, select **Security**, then **Suppressions**. 1. Select the trash icon on the suppression's row. The finding reappears on the next data refresh. Suppressions cannot be edited. To change one, remove it and suppress the finding again. | Column | Description | | --- | --- | | Cloud | The cloud provider the finding belongs to (AWS or Azure). | | Finding ID | The identifier of the suppressed finding. | | Account / Subscription | The AWS account or Azure subscription the finding was reported in. | | Reason | The reason entered when the finding was suppressed. | | Suppressed until | The date the suppression expires. Blank means the suppression is permanent. | | Suppressed at | When the suppression was created. | | Actions | The trash icon removes the suppression (unsuppress). |