AWS, Azure & GCP · Cloud across providers
What are the core cloud security practices?
Short answer
Secure identity first, then network boundaries, data encryption, patching and detection. Use the shared responsibility model, least privilege, private networking by default and centralised audit logs.
Cloud security starts with identity because almost every action is an API call. After identity, reduce network exposure, encrypt data, keep software patched, and detect abnormal behaviour. The provider secures the underlying infrastructure; you secure what you configure on top.
Layers to cover
- Identity: strong authentication, federation, least privilege and short-lived credentials
- Network: private subnets by default, restricted ingress, private endpoints and egress control
- Data: encryption at rest and in transit, key management and backup protection
- Compute and supply chain: patching, image scanning and signed artifacts
- Detection: centralised audit logs, guardrails, anomaly alerts and incident response
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Deny",
"Action": "organizations:LeaveOrganization",
"Resource": "*"
}
]
}Defence in depth means no single control is trusted alone. A private subnet plus a security group plus authenticated application access is stronger than any one of them. Guardrails at the organisation level prevent whole classes of misconfiguration before a team ships.
Follow-ups you should expect
Interviewers use these to check whether the first answer was understanding or memorisation.
- 1What does the shared responsibility model cover?
- 2How do organisation guardrails differ from team policies?
- 3Which controls would you put in a new account baseline?
- 4How do you detect a compromised credential?
Say it in the interview
I start with identity because every cloud action is an API call, then reduce network exposure, encrypt data and keep software patched. I use the shared responsibility model to be explicit about what the provider covers and what I own. Defence in depth and organisation guardrails prevent whole classes of misconfiguration, which is the most common cause of cloud incidents.
Use this as a model, not a script. Saying it in your own words is what makes it survive follow-up pressure.
Related questions
Reading is step one
Now say it out loud.
Understanding an answer and delivering it under pressure are different skills. Rehearse this topic in a live AWS, Azure & GCP mock interview and get scored feedback on depth, clarity and confidence.