Compliance Analysis
Compliance State tells you the estate is 74% compliant. Compliance Analysis tells you which policies are failing, on which assets, and what is already being done about them.
Table of contents
What the Page Is For
It is the investigative view: violations grouped by the policy that raised them, and each policy opened up to the individual resources breaching it.
- The question here is what is wrong with us - which controls we are failing, how badly, and how widely.
- The question in Remediation Planner is what will we do about this asset - it is a live planning tool, worked violation by violation.
This is the view to bring to a review meeting or an auditor.

Who Sees What
Like Remediation Planner, this page is scoped by asset ownership - so two people can open the same framework and see different estates.
| Role | What the page shows |
|---|---|
| Manager | The whole estate, and the Policy Action column |
| Analyst | The whole estate, read-only |
| User | Only the assets in the Asset Groups they are delegated to. The Policy Action column is not shown |
A User is delegated to one or more Asset Groups on the Asset Ownership page, and Pulse then limits every page to the assets in those groups without that person filtering anything. On this page that means the non-compliant assets listed under a policy are their own resources rather than the company’s.
Set up Asset Ownership first
Ownership is a prerequisite for this page, not an optional extra. A User who is not delegated to an Asset Group owns no assets, so selecting a policy shows them nothing to investigate - and that is indistinguishable from being compliant.
Configuring it is the Ownership Manager’s job and is done on the Assets page, not here:
- Allocate assets to an Asset Group - usually by pointing Pulse at the cloud tag key your teams already use for ownership.
- Delegate the asset owners to that group. Each of them needs at least the Company User role.
- Allow for the next processing cycle, up to 24 hours, before tag-based allocation shows up.
Asset Ownership covers the whole setup; Before You Start lists what has to be in place first.
Managers and Analysts see every Asset Group without being delegated to any, so the full picture is available to them whether ownership has been configured or not. It is the asset owners who depend on it.
Choosing a Framework
Everything on the page is scoped to one security framework, chosen from the selector beside the page title.

- Only activated frameworks appear - activating them is done in Policy Manager.
- The framework you open on is your organisation’s default framework, the same one for everyone.
- Changing the selection resets the filters on both tables, because a filter that made sense for one framework rarely means anything in another.
Step 1 - Select Policy
The upper table lists every evaluated policy in the framework, with its status and how many violations it has raised.
Every column in the policy table
| Column | What it holds | Values |
|---|---|---|
| Policy Name | The policy - click it to open the full analysis | The provider’s own policy name |
| Compliance Status | Whether the estate currently meets it | Compliant · Non-Compliant |
| Violations | How many assets are breaching it | A count |
| Severity | The assessed risk of the policy | Low · Medium · High · Critical |
| Policy Category | The security domain the policy belongs to | One of fourteen - see below |
| Policy Action | What your organisation decided should happen, and a link to change it | Pending to Assess · Under Investigation · Audit · Remediate · Exempt · Exemption Due Soon · Exempt Expired |
| Prevention Preference | Whether non-compliant deployments should be blocked | Permit · Prevent |
| Remediation Complexity | How much work a fix typically takes | Simple · Moderate · Complex · Redeployment · Guideline |
| Policy Release Date | When the provider published the policy | A date |
Prevention Preference, Remediation Complexity and Policy Release Date are not shown by default - add them from the column control in the table toolbar.
Show Only Selected collapses the list to the policy you picked, which frees the screen for the assets below once you have found it.
The fourteen Policy Categories
Every policy belongs to exactly one security domain:
- Identity & Access Management (IAM)
- Network Security & Perimeter
- Data Protection (At Rest & In Transit)
- Key & Secret Management
- Logging & Observability
- Compute & Runtime Security
- Container & Orchestration (Kubernetes)
- Configuration Management (CSPM)
- Infrastructure as Code (IaC) Security
- Vulnerability Management
- Storage Governance
- Resilience & Disaster Recovery
- Resource Organization & Tagging
- Cloud Service Enablement
Filtering by category is how you review one control area at a time - all your logging controls, or everything touching keys and secrets.
Filter by Compliance Status to see only what is failing. Sorting by Violations descending puts the widest failures first, which is usually not the same order as severity: a Low severity policy breached on two hundred assets may matter more than a High one breached on one.
Opening a policy
Click the policy name for the full analysis.

The analysis is organised into four sections. This is the same analysis you see from Policy Manager and Remediation Planner.
Every field in the policy analysis
Policy Review - what the policy is and why it matters
| Field | What it tells you |
|---|---|
| Name | The policy’s name |
| Severity | Low, Medium, High or Critical |
| Description | The provider’s own description of the control |
| Purpose | What the policy enforces, in one or two sentences |
| Benefits of Remediation | Three specific benefits of fixing it |
| Resource Type Affected | The resource types the policy applies to |
| Related Services Affected | Other services touched, and how |
| Possible Risk | What leaving it unaddressed may result in |
Change Impact - what happens to your estate if you remediate
| Field | What it tells you |
|---|---|
| Changes Made by Remediation | Exactly what property is changed, and whether it is in-place or destructive |
| Preparation for Remediation | The inputs to gather before starting |
| Service Reboot Required After Remediation | YES or NO, with the reason |
| Resource Redeployment Required for Remediation | YES or NO - YES means the resource must be recreated |
| Change Impact on Running Services | YES or NO, naming the workload disrupted |
Remediation Guides - how the fix is carried out
| Field | What it tells you |
|---|---|
| Manual Steps to Remediate | Numbered steps describing the target state |
| Remediation Complexity | How much work the fix takes - see the policy table above for the five values |
| Roll Back Steps | How to reverse the change if it goes wrong |
| Verification in JSON | What a compliant resource looks like, as a property and value |
More Info - how the policy maps to the wider world
| Field | What it tells you |
|---|---|
| Controls Covered | The equivalent control in ISO/IEC 27001:2022, CIS Controls v8.1, NIST SP 800-53 Rev. 5, PCI DSS v4.0.1 and SWIFT CSCF v2025 |
| Maturity | Where the policy sits in the provider’s lifecycle |
| Category | The security domain |
| Standard Names | The frameworks that include this policy |
The same analysis appears wherever a policy or a violation is opened, so it reads identically in Policy Manager and Remediation Planner.
Two parts earn their place in a review meeting. Possible Risk and Benefits of Remediation are written to be quoted directly to whoever approves the work. Controls Covered answers the auditor’s question - which ISO or NIST control this policy actually satisfies - without a mapping exercise.
And read Roll Back Steps before starting, not after. They exist so a change can go to a change board with an exit route already written down.
Step 2 - Review Non-Compliant Assets
Selecting a policy fills the lower table with the individual resources breaching it.

Every column in the assets table
| Column | What it holds | Values |
|---|---|---|
| Asset Name | The resource in breach | Your own resource names |
| Asset Category | What kind of resource it is | Comes from your cloud provider, so the set is open-ended - for example Storage, Integration |
| Subscription | The subscription, project or account it lives in | Your own names |
| Detection Date | When the violation was first found | A date |
| Remediation Status | What has been decided about this violation, and a link to change it | Pending to Assess · Internal Investigation · Planned to Remediate · Scheduled Remediation · Planned to Decommission · Exemption Requested |
Filter by Asset Name, Asset Category, Detection Date, Remediation Status or Subscription. Subscription is the one that matters most in practice: it narrows a policy’s breaches down to the assets one team owns, which is what turns a finding into an assignment. For a delegated User that narrowing has already happened - see Who Sees What.
Both tables export to CSV in full, not only the page on screen.
When the selected policy has no violations the table says No violations detected - the answer you want, rather than an error.
The Two Columns That Act
Policy Action and Remediation Status are not plain labels. Each one shows the current decision and links to the page where you can change it.
| Column | Shows | Links to |
|---|---|---|
| Policy Action, in the policy table | What your organisation decided should happen when this policy is broken | Policy Manager, in a new tab, on that exact framework and policy |
| Remediation Status, in the assets table | What has been decided about this specific violation | Remediation Planner, for that violation |
Read them as a to-do list. Either one showing Pending to Assess means nobody has decided yet - and the link is there so you can go and decide without hunting for the row on another page.
So the traversal through Cloud Compliance runs: a number on Compliance State, the policies behind it here, and then either the decision in Policy Manager or the work in Remediation Planner.
The Policy Action column is not shown to the User role - deciding what happens to a policy is a Manager’s call, while a User is here for their own assets. See Who Sees What.
Q&A
Nothing is listed in the lower table
Select a policy in the upper table first - the assets table shows the resources breaching whichever policy is selected. If one is selected and the table still says No violations detected, that policy is currently being met by every asset you can see.
That last qualification matters if you hold the User role: you see only the assets in the Asset Groups you are delegated to, so the policy may still be breached elsewhere in the company. Delegated to no group at all, every policy looks clean. Who Sees What explains the scoping, and Asset Ownership is where it is configured.
How is this different from Remediation Planner?
Remediation Planner is a live planning tool: violations listed as individual pieces of work, each given an owner, an action and a date. Compliance Analysis is for understanding rather than planning - it groups the same violations by policy to show which controls are failing and how widely.
The violation count here does not match Compliance State
They count different things and are not meant to agree:
- Here, violations are counted per policy - how many assets breach this one control.
- On Compliance State, they are counted per subscription, or across the whole tenant.
One asset can breach several policies, so no arithmetic connects the two figures.
Can I change a policy’s action from here?
Not on this page, but the Policy Action value is a link: it opens Policy Manager in a new tab, already filtered to that framework and policy. Changing it there requires the Manager role.
My colleague and I see different assets under the same policy
Expected, if you hold different roles. Manager and Analyst see the whole estate; a User sees only the assets in the Asset Groups they are delegated to. If a resource you are responsible for is missing, ask an Ownership Manager to allocate it to your group - see Asset Ownership.