Cloud Governance and Security Best Practices
Guardrails, policy as code, identity and network baselines, data protection, posture management and the shared responsibility model across AWS, Azure and Google Cloud.
Shared responsibility model
The provider secures the cloud (facilities, hardware, hypervisor, managed service internals); the customer secures what they put in the cloud (identities, configurations, data, applications). The split shifts with the service model: more customer responsibility for VMs, less for SaaS.
Guardrails: preventive, detective, corrective
| Type | Examples |
|---|---|
| Preventive | SCPs/Azure Policy deny/Org Policy constraints: allowed regions, no public storage, encryption required, no IAM user keys |
| Detective | AWS Config, Security Hub, Defender for Cloud, Security Command Center findings; CSPM tools |
| Corrective | Auto-remediation (e.g. close a public bucket, quarantine an instance) |
Policy as code example (Azure Policy: deny public blob access)
{
"if": {
"allOf": [
{ "field": "type", "equals": "Microsoft.Storage/storageAccounts" },
{ "field": "Microsoft.Storage/storageAccounts/allowBlobPublicAccess", "notEquals": false }
]
},
"then": { "effect": "deny" }
}Security baseline checklist
- Central SSO with MFA; no shared or long-lived credentials; break-glass procedures.
- Least privilege roles; regular access reviews; just-in-time admin.
- Org-wide audit logging to an immutable archive; central SIEM.
- Encryption at rest by default; customer-managed keys for sensitive data.
- Private networking for data services; controlled egress.
- Vulnerability and image scanning; patching SLAs.
- Secrets in managed vaults; rotation.
- Backups with immutability; tested restores.
- Infrastructure as code with policy checks in CI.
- Incident response runbooks for cloud-specific scenarios (key compromise, ransomware, public exposure).
Architect-level considerations
[!EA] Governance should be automated and paved-road: give teams templates that are compliant by default and use policy to block only the truly dangerous.
Interview questions and answers
How do you stop teams creating public S3 buckets?
Account-level and organization-level S3 Block Public Access, SCPs preventing changes to it, detective controls with Config/Security Hub, and approved patterns (CloudFront with origin access control) for legitimate public content.
What is CSPM?
Cloud Security Posture Management: continuous assessment of cloud configurations against benchmarks (CIS, NIST, PCI) to detect misconfigurations, with prioritization and remediation workflows.