Cloud Governance
IAM least-privilege, storage exposure, secrets management, network controls, audit logging, CSPM coverage, and cost anomaly detection — across AWS, GCP, Azure, OCI, and Cloudflare.
Before you start — what to have ready for Cloud Governance
Gather these first. Every one of them is something the assessment will ask for, and finding them mid-way is where an assessment stalls.
Decide your scope first
Every control in this framework is assessed, so there is no scope step to complete first. Have these decided before you begin so your answers describe one consistent thing.
- Which systems, services and locations are in scope — write this down before you answer anything.
- Who owns each area, so an answer about it is somebody’s to give.
- The period the evidence should cover, where the framework opines on a period rather than a moment.
Gather these documents
What Cloud Governance is assessed against. Find them before you start — the assessment reads what you upload, not what you tell it.
- Cloud governance / cloud security policy
- Cloud account and identity configuration (IAM roles, MFA)
- Storage and network security configuration (public-access controls)
- Logging and monitoring configuration
- Encryption and key management policy
- Backup and recovery configuration
Have the right people
Who needs to be involved, and what changes if it is only you.
- Someone who can find the documents — usually whoever owns the control day to day.
- A second person to review what was uploaded, if you want reviewed coverage. They must not be the person who submitted or attached that evidence: no one reviews their own work.
- One person can complete the whole assessment. Reviewed coverage will read zero, and that is accurate rather than a fault.
- A reviewer’s acceptance is what raises a control from partial to proven, and every workspace has that during the open beta. It becomes something a plan includes once there is anything to buy.
Prepare the files
Upload only what the assessment needs. You are responsible for removing or masking personal and sensitive data that a control does not require — do it before you upload. Cloud configuration exports contain account ids, resource names and sometimes secrets. Redact account identifiers and any keys or tokens before uploading — the policy and the configuration standards are what is assessed.
- Upload digital documents only — a Word file, a spreadsheet, or a PDF with real text. A photograph or a scanned paper has no readable text, so it cannot be assessed or prove a control.
- A scan or a photograph has no text to read, so it cannot prove a control. Export the original instead.
- The same file cannot be uploaded twice to one library — it is recognised by its contents, not its name.
- Upload the document itself, not a summary of it. A summary is your description of the evidence, not the evidence.
- A document that is not about this framework will be accepted and matched against nothing. It still counts against your library, so it is worth checking before you send it.
Know what you will get
So the result is what you expected when you started.
- You get a readiness position derived from the evidence you upload, and a list of where the gaps are.
- You do not get an audit, an opinion, or a certification. Only a licensed auditor, an accredited certification body, or the relevant regulator can give you those.
- Controls you upload nothing for are reported as UNEXAMINED — not as failed. That distinction is deliberate.
- A document can support a control without proving it. Supporting evidence raises a control to partial; reaching proven takes evidence a second person independently reviewed and accepted.
Your assessment journey
From your cloud estate to an evidence-backed governance position, with an optional configuration check.
Which providers you run on, what is internet-facing, and what sensitive data the estate holds.
Open →Eighteen controls across identity, data security, network, logging, misconfiguration and cost governance. Anything left unanswered counts as zero.
Open →Your position by domain with the gaps ordered by weight, each raisable as a corrective action you can track.
Open →Each control names what would prove it - an IAM policy export, a public-access-block configuration, a flow log retention setting. Upload them and the score rests on configuration rather than recollection.
Open →Inspect security-group/NSG exports and AWS root-credential summary flags in your browser. Raw exports stay local; selected findings can become workspace actions. No readiness score changes.
Open →