Cloud Compliance
Cloud Compliance brings the compliance engines of AWS, Azure and Google Cloud under one process. Five pages, each answering one question, in the order you meet them:
flowchart LR
A["1 - Compliance State<br/>How compliant are we?"]
B["2 - Policy Manager<br/>What are we measured<br/>against, and what should<br/>happen when we fail?"]
C["5 - Compliance Analysis<br/>Which policies are failing,<br/>and where?"]
D["3 - Remediation Planner<br/>What will we do<br/>about this asset?"]
E["4 - Exemptions<br/>What are we accepting<br/>instead of fixing?"]
A --> C
B --> C
C --> D
D --> E
E -.-> A
click A "/pulse-ecosystem/cloud-compliance/compliance-state/"
click B "/pulse-ecosystem/cloud-compliance/policy-manager/"
click C "/pulse-ecosystem/cloud-compliance/compliance-analysis/"
click D "/pulse-ecosystem/cloud-compliance/remediation-planner/"
click E "/pulse-ecosystem/cloud-compliance/exemptions/"
Read left to right, that is the working cycle:
- Choose what you are measured against. Activate security frameworks in Policy Manager, and decide what should happen when each policy inside them is broken.
- See where you stand. Compliance State scores every subscription against the framework and plots it over time.
- Find out what is behind the number. Compliance Analysis groups the violations by policy, down to the individual asset.
- Commit to doing something. Remediation Planner is where the owner of an asset says what will happen to it, and by when.
- Record what you accept instead. Exemptions is where an accepted risk is requested, approved or refused, with an expiry date.
The Pages
| Page | What you do there |
|---|---|
| Compliance State | Track compliance metrics over time and compare subscriptions |
| Policy Manager | Review security frameworks, activate them, and set what happens to each policy |
| Remediation Planner | Review violations assigned to you and plan what to do about them |
| Exemptions | Review, approve and reject exemption requests, with expiry and risk number |
| Compliance Analysis | Explore violation detail grouped by policy, down to the individual asset |
What You Get at Each Tier
- Cloud Essentials - compliance posture per subscription only, scored against a framework. Available without a Cloud Compliance subscription, and described with the rest of the free tier.
- Pulse Premium - all five pages. Choosing frameworks, setting policy actions, planning remediation and handling exemptions are the part that Premium adds.
- Managed Cloud Compliance - the same five pages, plus Devoteam operating them with you. The decisions you record in Pulse become work Devoteam carries out in your cloud, rather than a list your own team has to action.
That last difference is the one worth understanding before you start, because it changes what a decision in Pulse means. See Nothing in Pulse changes your cloud.
For how the tiers fit together across the whole platform, see Pulse Ecosystem.
Before the Data Arrives
Pulse reports on compliance data your cloud produces. Which standards your cloud evaluates is a setting in the cloud itself, not in Pulse:
- Every framework and every policy inside it is listed in Pulse, whatever your cloud evaluates.
-
Violations are what depend on the cloud side. A standard your cloud does not evaluate shows its policies with nothing reported against them.
- Enabling Standards in Your Cloud