Enabling Standards in Your Cloud
Activating a security framework in Policy Manager tells Pulse what to measure you against. It does not change anything in your cloud. This page covers the other half: enabling the matching standard in AWS, Azure or Google Cloud, so that there is compliance data for Pulse to report on.
Table of contents
What Activating a Framework Does
Policy Manager lists the security frameworks available to your organisation and lets you activate or deactivate them. Activating one adds it to your organisation’s active posture assessment in Pulse - the set of standards Pulse scores you against, reports on, and raises violations for.
It applies within Pulse only. Your cloud environment is not modified. No policy is created, no setting is changed, and nothing you deploy is blocked or altered as a result.
That matters because the two sides have to agree. Your cloud runs the evaluations and produces the findings; Pulse reads them, explains them, and turns them into violations you can plan work against.
Pulse lists every framework and every policy inside it regardless of what your cloud evaluates, so a framework is never missing and never looks empty. Violations are what depend on the cloud side. Activate a framework whose standard your cloud does not evaluate and you get the full policy list with nothing reported against it - and its Status in Policy Manager reads Awaiting Cloud, which is the page telling you that this half is done and the other one is not.
When you activate a framework, Pulse asks you to confirm that it should apply across the entire scope of the service, and then tells you:
Request will be implemented in the next business day.
Activating a framework is also what unlocks the rest of Policy Manager. Until one is activated, the per-policy settings - Exempt, Audit, Remediate and the prevention preferences - stay disabled.
Before You Start
- Cloud Compliance is a Pulse Premium feature. See Pulse Ecosystem for what each tier includes.
- Activating and deactivating frameworks requires the Manager company role. Pulse describes this in Policy Manager as Compliance Manager permissions. With any other role the page is read-only.
- The cloud-side steps below are performed in your cloud, by your own administrators, and need privileged access there. The roles required differ per cloud and are listed in each section.
What Onboarding Already Enabled
Cloud onboarding offers to enable a baseline standard for you. If you took that option, one standard is already running and the sections below apply only to additional standards you want on top of it.
| Cloud | Baseline offered during onboarding | Where it is described |
|---|---|---|
| Amazon Web Services | Security Hub CSPM with AWS Foundational Security Best Practices v1.0.0 | AWS Onboarding |
| Microsoft Azure | The Microsoft Cloud Security Benchmark policy initiative, assigned in DoNotEnforce mode | Azure Onboarding |
| Google Cloud | Security Health Analytics | Google Onboarding |
If you skipped it, or onboarded before it was offered, start with the onboarding page for your cloud rather than with this one.
Amazon Web Services
Compliance findings reach Pulse through AWS Security Hub CSPM. A standard has to be enabled there before its controls are evaluated and its findings exist.
What you need
- Security Hub CSPM enabled, with a delegated administrator designated for your organisation
- AWS Config recording in every account and region you want findings from - Security Hub evaluates from the Config configuration recorder
- Security Hub administration permission in your Security account
Enabling a standard
- Sign in to your designated Security account - the Security Hub CSPM delegated administrator.
- Go to Security Hub CSPM → Security standards.
- Find the standard you want and enable it.
- Go to Settings → General and turn Consolidated control findings on, so that controls shared between standards are grouped and deduplicated rather than reported once per standard.
Enabling a standard enables all of the controls within it. Scope follows your Security Hub setup: standards apply per account and per region, so a standard enabled in one region produces findings for that region only. With a delegated administrator and cross-region aggregation in place, you do this once in the Security account rather than account by account.
Automatic enablement in new accounts
Under local configuration, Security Hub can switch default standards on automatically when an account joins your organisation, and enable all of their controls with them. If you would rather decide standard by standard, turn automatic enablement off before you start.
Timing
Allow up to 24 hours for the security score to be calculated in full after enabling a standard.
Microsoft Azure
Compliance findings reach Pulse from Microsoft Defender for Cloud. Its regulatory standards and benchmarks are Azure Policy initiatives, so enabling a standard means assigning its initiative at the scope you want measured.
What you need
Resource Policy Contributorat the scope you are assigning to- These resource providers registered on the target subscriptions:
Microsoft.ResourceGraph,Microsoft.PolicyInsights,Microsoft.Authorization
Checking resource providers
In the Azure portal, go to Subscriptions → [your subscription] → Settings → Resource providers, search for each of the three, and register any that are not already Registered. They are usually registered by default.
Choosing a scope
An initiative can be assigned at a management group, a subscription or a resource group. A management group is the usual choice: it covers the subscriptions beneath it, including ones added later.
Enabling a standard
- In the Azure portal, go to Policy → Definitions.
- Find the initiative for the standard you want. Both built-in and custom initiatives can be used.
- Click Assign.
- Set the Scope to your target management group or subscription.
- Click Review + Create.
Timing
Compliance data depends on Azure Policy evaluating the newly assigned initiative, which happens on Azure’s own schedule. If a subscription shows no compliance results for the new assignment, you can ask Azure to evaluate it now - see the standard is assigned, but a subscription has no compliance results.
Google Cloud
Compliance findings reach Pulse from Security Command Center. Two services are involved: Security Health Analytics detects the misconfigurations, and Compliance Manager maps those findings to regulatory frameworks.
What you need
- Security Command Center active for your organisation
- Security Health Analytics enabled and Compliance Manager switched on, as described below
- Access in Security Command Center to enable services and to assign frameworks to resources. The exact Google Cloud roles are set by Google, so check them against Google’s documentation for your organisation
Enabling the services
- In the Google Cloud console, go to Security → Overview to open Security Command Center.
- In the left-hand menu, click Settings, then open the Services tab.
- Confirm Security Health Analytics is Enabled.
- Go to Security → Compliance. If a welcome banner appears, click Enable compliance.
You can verify the second step from Settings → Services as well, where Compliance Manager should be ON.
Once the services are on, a number of compliance standards are already evaluated and visible for review on the original Monitor tab.
Enabling a standard
Compliance Manager measures your cloud against frameworks. A framework is a set of cloud controls, and it can be built in or custom. You choose which part of your hierarchy a framework applies to by assigning resources to it, so you decide which standards apply where rather than reading whatever is on by default.
- Go to Security → Compliance and open the Configure tab.
- Under Frameworks, find the framework for the standard you want and click its name to open Framework details. The list shows each framework’s platform, categories and Tier, and the Assigned column shows whether it is already assigned.
- Click Actions, then Manage resource assignments. A Monitor panel opens on the right.
- Under Select resources to monitor, click Browse in the Resource field and choose the organization, folder or project the framework should apply to.
- Under Define framework parameters, enter a value for any cloud control that asks for one. Many frameworks have none, in which case the panel says so.
- Click Monitor. Google Cloud confirms with Framework Deployment initiated successfully.
If Security Health Analytics is active on the resource you choose, the panel warns that its detectors may produce duplicate findings and suggests disabling it before the deployment. Leave Security Health Analytics enabled unless Devoteam advises otherwise: Pulse reports violations from the findings it produces.
The framework then appears in the Frameworks table on the Monitor tab marked New, where Assigned to shows the resource and Controls passing shows the share of controls that pass.
Choose Monitor, not Enforce: monitoring gives Pulse the findings it reports on, and does not enforce compliance or remediate violations in your cloud.
If no built-in framework matches what you need, click Create custom framework on the Configure → Frameworks tab and build it from the Cloud controls tab’s controls. Assign a custom framework to resources in the same way.
Timing
Google Cloud notes that the monitoring information on the Monitor tab may have a lag of up to 30 hours. This is longer than the general allowance under After You Enable a Standard.
After You Enable a Standard
- Activate the matching framework in Policy Manager, if you have not already. The cloud produces the findings; activating is what puts them in scope for Pulse.
- Allow time for the data to arrive. Findings appear in Pulse after your cloud has evaluated the new standard and Pulse has collected the results - allow up to 24 hours for data to load into Pulse, on top of your cloud’s own evaluation schedule.
- Watch the Status in Policy Manager. It moves from Awaiting Cloud to Active once data starts arriving, which is the clearest confirmation that both halves are now in place.
- Check Compliance State. The framework should start reporting metrics rather than sitting empty.
Having Devoteam Do This For You
Every step on this page is a change inside your own cloud, which is why it is yours to make. If you would rather not make it yourself, that is what the Managed Cloud Compliance service is for.
With Managed Cloud Compliance enabled, Devoteam implements the cloud-side work on your behalf - enabling and maintaining standards, implementing approved exemptions, carrying out remediation, and deploying preventive controls - as an operated service rather than a set of instructions.
This depends on the permissions you grant. Which scopes Devoteam may act in, and what may be changed there, is agreed with you during onboarding and nothing is done outside it.
Read more: Cloud Managed Services.
Q&A
I activated a framework in Pulse. Why are there no violations?
Check its Status in Policy Manager. Awaiting Cloud means exactly this: activated in Pulse, but your cloud is not evaluating that standard, so there is nothing to report. Work through the section above for your cloud.
If the standard is already enabled there, give it time: your cloud evaluates on its own schedule, and Pulse collects the results afterwards. The Status changes to Active once data arrives.
Azure: the standard is assigned, but a subscription has no compliance results
Azure Policy evaluates a newly assigned initiative on its own schedule, and does not always reach every subscription promptly. A subscription can go several days with no compliance results for a new assignment, including the Microsoft Cloud Security Benchmark assigned during onboarding. Until Azure has evaluated it there is nothing for Pulse to collect, so the subscription has no data in Compliance State.
You can ask Azure to evaluate a subscription straight away. In Azure Cloud Shell, run:
az policy state trigger-scan --subscription <subscription-id>
- It needs
Resource Policy Contributoron the subscription - the same role as assigning the initiative. - The evaluation runs in Azure and takes a while to finish. Check its progress in Policy → Compliance, scoped to the subscription.
- Once Azure shows results there, allow up to 24 hours for them to appear in Pulse.
Azure: a subscription added to the management group later has no compliance results
An initiative assigned at a management group also applies to subscriptions added under it later, including the Microsoft Cloud Security Benchmark assigned during onboarding. Azure evaluates a new subscription on its own schedule, which can take days, so it can have no compliance results in the meantime.
To start an evaluation straight away, in Azure Cloud Shell:
az policy state trigger-scan --subscription <subscription-id>
If the command fails, check that the Microsoft.PolicyInsights resource provider is registered on the subscription, under Subscriptions → [your subscription] → Settings → Resource providers. If it shows anything other than Registered, register it and run the command again.
- Starting an evaluation needs
Resource Policy Contributor. Registering a resource provider needsContributororOwner. - Once Azure shows results in Policy → Compliance, allow up to 24 hours for them to appear in Pulse.
Does activating a framework block anything we deploy?
No. Activating a framework in Pulse changes nothing in your cloud, so it cannot block or alter a deployment. Preventive controls are a separate decision, configured per policy, and they take effect through your cloud rather than through the activation.
Can I deactivate a framework?
Yes, from the same place in Policy Manager - with one exception. Each cloud provider has one default framework, and that framework cannot be deactivated while it holds the role. Set a different default for that provider from the framework list first.
Deactivating removes the framework from the service scope in Pulse. It does not disable the standard in your cloud, which continues to evaluate and produce findings until you disable it there as well.
We already have a standard enabled that Pulse does not show
A standard your cloud evaluates is only reported by Pulse once the matching framework is activated in Policy Manager. Until then its Status reads Ready to Activate - the data is there, waiting for you to bring it into scope.
Who can activate frameworks?
Users with the Manager company role. Other roles see Policy Manager as read-only, and the per-policy settings stay disabled for them.