Cloud Security FAQs for DevOps Interviews: 52 Terms (2027)

52 cloud security FAQs for DevOps interviews: shared responsibility, IAM, KMS, zero trust, CSPM, secrets and compliance, with AWS, Azure and GCP names.

Sep 18, 2025 - 14:04
Nov 9, 2026 - 15:16
 0  57
Cloud Security FAQs for DevOps Interviews: 52 Terms (2027)

Cloud security FAQs in DevOps interviews are short definition questions: shared responsibility, least privilege, encryption keys, zero trust, posture management, secrets, compliance. This page gives 52 plain-language answers in eight groups, with the AWS, Azure and Google Cloud service names to use, checked against each provider's documentation and NIST in November 2026.

Interviewers often open with a quick-fire round of definitions before going deep. If you stumble there, the harder rounds go badly. This glossary-style page is for that round. For longer answers and hands-on work, move on to our 90+ cloud security interview questions, the scenario-based set and the advanced set.

Key takeaways

  • Know the shared responsibility split: the provider secures the cloud infrastructure, and you secure what you put in it. How much that covers depends on the service model.
  • Answer definitions in two sentences: what it is, then why a team uses it.
  • Each provider has an equivalent for the main controls: IAM, key management, audit logs, posture management and secrets storage. Learn one set well and the names of the others.
  • Zero trust, as NIST SP 800-207 describes it, grants no implicit trust based on network location or asset ownership.
  • Prefer short-lived identity (roles, managed identities, workload identity) over long-lived keys.

Service names across the three clouds

ControlAWSAzureGoogle Cloud
Identity and accessIAM, IAM Identity CenterMicrosoft Entra ID, Azure RBACCloud IAM
Key managementAWS KMSAzure Key VaultCloud KMS
Secrets storageSecrets ManagerAzure Key VaultSecret Manager
Audit loggingCloudTrailAzure Activity logCloud Audit Logs
Posture managementAWS Security Hub, AWS ConfigMicrosoft Defender for CloudSecurity Command Center
Policy guardrailsService control policiesAzure PolicyOrganization Policy
Workload identityIAM rolesManaged identitiesService accounts with workload identity

For deeper provider comparisons, see most asked cloud security questions.

Foundations

1. What is cloud security?

The policies, controls and practices that protect cloud data, applications and infrastructure from unauthorised access, loss and misuse. Teams apply it through identity, encryption, network design, monitoring and automation.

2. What is the shared responsibility model?

AWS describes it as security "of" the cloud (the provider protects hardware, software, networking and facilities) and security "in" the cloud (the customer). For a virtual machine you manage the guest operating system, patches and firewall rules. For a service like Amazon S3, AWS runs the infrastructure and platform, and you manage your data, encryption settings and permissions.

3. What are inherited, shared and customer-specific controls?

Inherited controls come entirely from the provider, such as physical data centre security. Shared controls need both sides, such as patch management where the provider patches infrastructure and you patch your guest OS and applications. Customer-specific controls are yours alone, such as how you route and zone your data.

4. What is the CIA triad?

Confidentiality (only authorised people see data), integrity (data is not altered improperly) and availability (systems work when needed). Most security controls protect one or more of these.

5. What is defense in depth?

Layering controls so one failure does not expose everything: identity, network, host, application and data layers each have their own protections.

6. What is least privilege?

Granting only the permissions needed to do a task, for only as long as needed. In practice that means narrow roles, time-limited access and regular review of unused permissions.

7. What is a threat, a vulnerability and a risk?

A vulnerability is a weakness, a threat is something that can exploit it, and risk is the likelihood and impact of that happening. Teams rank risk to decide what to fix first.

8. What is attack surface?

The sum of the ways someone could reach or affect your systems: exposed endpoints, open ports, public storage, permissive roles and third-party integrations. Reducing it means removing what you do not need.

Identity and access

9. What is IAM?

Identity and access management decides who or what can do which actions on which resources. Every major cloud has an IAM service, and identity is usually the first security boundary.

10. What is the difference between authentication and authorisation?

Authentication proves who you are. Authorisation decides what you may do after that.

11. What is MFA, and why is it required for admins?

Multi-factor authentication needs two or more proofs of identity, such as a password and a hardware key or authenticator code. It limits damage when a password leaks, so administrators and root accounts should always have it.

12. What is RBAC?

Role-based access control assigns permissions to roles and roles to people or workloads. It is easier to review than permissions attached to individuals. Azure RBAC and Google Cloud IAM roles follow this model.

13. What is a managed identity in Azure?

An identity assigned to an Azure compute resource so an application can obtain Microsoft Entra tokens without handling credentials. Microsoft documents two types: system-assigned, which shares the lifecycle of the resource, and user-assigned, which is a standalone resource that several resources can share.

14. Why use roles instead of long-lived access keys?

Roles give temporary credentials that expire, and nothing needs to be stored in code or config. Long-lived keys leak into repositories and logs and stay valid until someone rotates them.

15. What is federation and single sign-on?

Federation lets users sign in with an existing identity provider (for example your company directory) and receive temporary cloud access. Single sign-on lets one login work across many applications.

16. What is a service control policy or organization policy?

A guardrail set at the organization level that limits what accounts or projects can do, regardless of local permissions. In AWS, service control policies set maximum permissions but do not grant any themselves.

Data protection

17. What is encryption at rest and in transit?

At rest means protecting stored data (disks, buckets, databases). In transit means protecting data moving over a network, normally with TLS. Do both.

18. What is a KMS key?

A logical key in a key management service that is the top of a key hierarchy. In AWS KMS, there are customer managed keys (you control the lifecycle and key policy), AWS managed keys (AWS controls them in your account) and AWS owned keys (internal to AWS, with no visibility to you).

19. What is envelope encryption?

Data is encrypted with a data key, and the data key is itself protected by a key in the key management service. KMS can return a data key as plaintext and as an encrypted copy, so you encrypt locally and store only the encrypted key with the data.

20. What is an encryption context?

Extra key-value information bound to an encryption operation in AWS KMS. If you use one, you must supply the same context to decrypt, and it appears in CloudTrail logs, which helps audit why a key was used.

21. What is a secret, and where should it live?

A credential such as a password, API key or certificate. Keep secrets in a secrets service (Secrets Manager, Key Vault, Secret Manager) and fetch them at runtime, never in source code or images.

22. What is data classification?

Labelling data by sensitivity (for example public, internal, confidential, regulated) so protections, retention and access follow the label.

23. What is data loss prevention?

Controls that detect and block sensitive data leaving where it should stay, using patterns and policy. Cloud services such as Amazon Macie scan storage for sensitive data.

24. What is tokenisation versus encryption?

Encryption transforms data with a key and can be reversed with that key. Tokenisation replaces the value with a token and keeps the mapping in a separate protected vault.

Network security

25. What is a VPC or virtual network?

A logically isolated network in a cloud account where you define subnets, routing and filtering. Place databases and internal services in private subnets with no direct internet route.

26. Security groups versus network ACLs?

Security groups attach to instances and are stateful with allow rules only. Network ACLs apply to subnets, are stateless and support allow and deny rules.

27. What is a WAF?

A web application firewall filters HTTP traffic using rules to block common web attacks before they reach the application. Pair it with secure code, not instead of it.

28. What is DDoS protection?

Services that absorb or filter floods of traffic aimed at making a system unavailable. Providers offer baseline protection, with extra tiers for critical applications.

29. What are private endpoints?

Private network addresses for reaching a cloud service so traffic does not cross the public internet. Examples are AWS PrivateLink, Azure Private Link and Google Private Service Connect.

30. What is VPC Service Controls?

A Google Cloud feature that creates perimeters around managed services such as Cloud Storage and BigQuery to reduce data exfiltration risk. Communication across the perimeter is blocked by default, and it complements IAM instead of replacing it.

31. What is zero trust?

NIST SP 800-207 describes it as a set of paradigms that move defenses from static network perimeters to users, assets and resources, with no implicit trust based on network location or ownership of the device. In practice: authenticate and authorise every request, and verify device and user before granting access to each resource. See our zero trust tools.

Posture, monitoring and detection

32. What is CSPM?

Cloud security posture management continuously assesses cloud configuration against standards and reports misconfigurations. Microsoft Defender for Cloud describes CSPM as continuous visibility with actionable guidance across Azure, AWS and GCP, with a free foundational plan and a paid Defender CSPM plan.

33. What is Google Security Command Center?

Google's platform for finding vulnerabilities and misconfigurations, detecting threats, enforcing postures and exporting findings. It has Standard, Premium and Enterprise tiers, and Google documents that organizations on Enterprise will move to Premium on or after 21 May 2027.

34. What are audit logs, and why do they matter?

Records of who did what and when in the control plane (CloudTrail, Azure Activity log, Cloud Audit Logs). They are the main evidence in an investigation, so protect them from tampering and keep them in a separate account.

35. What is a SIEM?

A security information and event management system that collects and correlates logs from many sources to detect and investigate threats. Microsoft Sentinel is an example.

36. What is threat detection in the cloud?

Services that analyse logs and network data for suspicious behaviour. Amazon GuardDuty is the AWS example.

37. What is configuration drift?

When a live resource differs from its intended configuration, often through manual console changes. Infrastructure as code with drift checks and policy rules catch it. See configuration drift tools.

38. What is policy as code?

Writing guardrails as machine-checked rules (for example Open Policy Agent policies or cloud policy services) that run in pipelines and block insecure changes before deployment. See tools to automate cloud security policies.

Containers, Kubernetes and CI/CD

39. What is container image scanning?

Checking images for known vulnerabilities and bad configuration before they are deployed, usually in the build pipeline and again in the registry.

40. How do you secure a Kubernetes cluster at a high level?

Use RBAC with least privilege, restrict network traffic with network policies, avoid privileged containers, store secrets outside plain manifests, keep the control plane and nodes updated, and enable audit logging.

41. What is a software bill of materials (SBOM)?

A list of the components inside software, used to check whether a newly disclosed vulnerability affects you.

42. What is DevSecOps?

Building security checks into every stage of delivery, so problems are found while they are cheap to fix. Our cloud native security practices by phase lists them.

43. Why use short-lived credentials in CI/CD?

A leaked long-lived key gives an attacker lasting access. OIDC federation lets a pipeline get temporary cloud credentials for each run, restricted to a repository or branch.

Compliance and governance

44. What is compliance in the cloud?

Meeting the requirements of laws, standards and contracts that apply to your data and industry, and being able to prove it with evidence.

45. Name common frameworks and what they cover.

ISO/IEC 27001 covers information security management systems. SOC 2 is an attestation report on controls, from the AICPA. PCI DSS covers payment card data. HIPAA covers health information in the United States. GDPR covers personal data of people in the European Union. India's Digital Personal Data Protection Act, 2023 covers digital personal data. Which ones apply depends on your business.

46. Does using a compliant cloud make my application compliant?

No. The provider's certifications cover the parts it runs. Your own configuration, access control and data handling still need to meet the requirements under the shared responsibility model.

47. What is data residency?

The requirement that data is stored or processed in a specific country or region. You enforce it by choosing regions and blocking others with guardrail policies.

Incident response and good habits

48. What are the stages of incident response?

Preparation, detection and analysis, containment, eradication and recovery, and lessons learned. Practise with tabletop exercises before an incident.

49. A key is exposed in a public repository. What is the first action?

Revoke or disable the key immediately, then rotate it, review audit logs for use of the key, and remove it from history. Never just delete the commit.

50. What is a blast radius?

How much damage one compromised identity, account or component can cause. Separate accounts, narrow roles and network segmentation reduce it.

51. What is immutable infrastructure from a security view?

Replacing servers with freshly built images instead of patching them in place, so configuration is predictable and drift is rare.

52. How do I answer if I do not know a term?

Say so, then reason from what you know and name where you would look. Interviewers value honesty and a clear method more than a guess.

To practise these with labs, see the DevSecOps course in Pune, offered in the Kharadi classroom and live online across India. Other related guides: cloud security engineer questions, questions by certification and Akamai CDN and cloud security questions.

FAQs

What is the single most important cloud security concept for interviews?

The shared responsibility model, because it explains who is accountable for each control and shows up in almost every follow-up question.

Which cloud should I learn for security interviews?

Learn the one your target employers use, then learn the equivalent service names on the other two using a table like the one above.

How are FAQs different from full interview questions?

FAQs test definitions and quick reasoning. Full questions test applying them to a design or an incident.

Do I need a security certification?

Not for most DevOps roles. A certification can help, but projects that show secure pipelines and least-privilege access are stronger evidence.

What is the difference between CSPM and a SIEM?

CSPM looks at configuration and risk posture. A SIEM collects and correlates logs and events to detect threats.

Is zero trust a product?

No. NIST describes it as a set of principles and an architecture, which products help implement.

How should I store secrets in a pipeline?

Prefer short-lived credentials through OIDC and read other secrets from a secrets service at runtime, instead of placing long-lived keys in pipeline variables.

Official references

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.