SC-500 — Microsoft Certified: Cloud and AI Security Engineer Associate Cheat Sheet

Identity Decision Table

Common Identity Traps

Authentication, authorization, and privilege

A large share of Microsoft security questions test whether you know which identity layer controls which decision.

Azure RBAC versus Microsoft Entra roles

Conditional Access quick rules

Conditional Access is often the right answer when a scenario includes who, where, device state, risk, application, or session control.

Trap: Conditional Access grants access only after authentication signals are evaluated. It does not replace Azure RBAC, app permissions, network controls, or data permissions.

Managed identity versus service principal

Candidate mistake: Seeing “service-to-service access” and immediately choosing a client secret. In modern Azure designs, managed identity or federation is usually safer.

Resource Governance Matrix

AI Workload Network Controls

Secure AI Application Pattern

RAG and Vector Search Security

AI Content Safety and Guardrails

AI security review

SC-500’s AI security angle is likely to test whether you can secure AI workloads as cloud applications with additional AI-specific risks.

AI security responsibility model

Azure OpenAI and Azure AI workload hardening

Prompt injection and RAG traps

Decision rule: AI security is not only “turn on content filtering.” You also need identity, least privilege, network isolation, data governance, logging, and safe tool design.

Secure AI application workflow

    flowchart TD
	    A[AI workload requirement] --> B{Uses enterprise data?}
	    B -- No --> C[Secure model endpoint, identity, network, logging]
	    B -- Yes --> D[Classify data and confirm access boundaries]
	    D --> E[Enforce source permissions and retrieval filters]
	    E --> F{Can model call tools or actions?}
	    F -- No --> G[Apply prompt/output controls and monitor]
	    F -- Yes --> H[Limit tool permissions and require validation]
	    H --> G
	    G --> I[Centralize logs and test with adversarial prompts]

Key Vault and managed HSM

Trap: Storing a secret in Key Vault is not enough. The application identity still needs least-privilege access, network restrictions may be required, and logs should be monitored.

Storage security quick review

Candidate mistake: Choosing a broad account SAS when the scenario requires least privilege, short duration, and user delegation.

Data classification and governance

Microsoft Purview-related concepts may appear in scenarios involving data discovery, classification, sensitivity, retention, DLP, and audit.

Defender for Cloud Concepts

Sentinel Concepts

Microsoft Defender for Cloud review

Microsoft Defender for Cloud is a key security posture and workload protection service for Azure and multicloud environments.

Common Defender for Cloud traps

• A recommendation may require manual remediation, policy assignment, configuration change, or deployment of an agent/extension.
• Secure score is useful for prioritization but is not an official certification of compliance.
• Defender for Cloud posture management is different from Microsoft Defender XDR incident correlation.
• Enabling a Defender plan may add detection capabilities, but you still need correct identity, network, and data controls.
• Multicloud visibility depends on connectors, permissions, and supported configurations.

Azure Administrative Changes

AzureActivity
| where TimeGenerated > ago(24h)
| where CategoryValue == "Administrative"
| project TimeGenerated, OperationNameValue, ActivityStatusValue, Caller, ResourceGroup, ResourceId
| order by TimeGenerated desc

Key Vault Secret Access Review

AzureDiagnostics
| where ResourceProvider == "MICROSOFT.KEYVAULT"
| where OperationName has "Secret"
| project TimeGenerated, OperationName, identity_claim_appid_g, CallerIPAddress, ResultType
| order by TimeGenerated desc

Suspicious Multiple IP Sign-ins

SigninLogs
| where TimeGenerated > ago(1d)
| summarize IPCount=dcount(IPAddress), IPs=make_set(IPAddress) by UserPrincipalName
| where IPCount > 3
| order by IPCount desc

Common KQL Operators

CI/CD Security Checklist

• Use least-privilege deployment identities.
• Prefer federated credentials over stored secrets.
• Scope credentials per environment.
• Require peer review for production changes.
• Run code, dependency, secret, and IaC scanning before merge.
• Protect pipeline variables and logs.
• Do not print tokens, prompts, connection strings, or API keys.
• Require approvals for high-risk production deployments.
• Monitor deployment activity in Azure Activity Log and SIEM.

Fast Response Decisions

Secure Azure Landing Zone Controls

Fast final review checklist

Use this checklist before topic drills or a mock exam.

Identity

• Can you distinguish Microsoft Entra roles, Azure RBAC, app permissions, and data-plane permissions?
• Do you know when to use Conditional Access, PIM, access reviews, and managed identities?
• Can you identify risky service principal secrets and replace them with safer patterns?

Azure platform

• Can you choose between NSG, Azure Firewall, WAF, Private Endpoint, Bastion, and DDoS Protection?
• Can you explain Azure Policy versus Defender for Cloud versus Azure RBAC?
• Can you identify the right control for public exposure, insecure configuration, and missing monitoring?

Data and secrets

• Can you secure Key Vault access with identity, RBAC/access policy, network restrictions, and logging?
• Can you choose between Microsoft-managed keys and customer-managed keys when a scenario requires key control?
• Can you reduce risk from shared keys, broad SAS tokens, and exposed secrets?

AI security

• Can you secure model endpoints, AI app identities, RAG data sources, prompts, outputs, and logs?
• Can you recognize direct and indirect prompt injection?
• Can you prevent AI oversharing by enforcing source permissions and retrieval boundaries?

Detection and response

• Can you distinguish Defender for Cloud, Defender XDR, Sentinel, Log Analytics, workbooks, and playbooks?
• Can you recognize alert versus incident versus connector versus analytics rule?
• Can you read simple KQL intent even if syntax is not the main focus?

Network security decision table

Private Endpoint trap: Private Endpoint requires DNS planning. A workload can still fail if the private DNS zone, records, or resolver path are wrong.

Azure Policy versus RBAC versus Defender for Cloud

Decision rule:

• If the scenario says “prevent noncompliant resources from being created,” think Azure Policy.
• If it says “allow a user to manage a resource,” think Azure RBAC.
• If it says “find, prioritize, and remediate security risks,” think Defender for Cloud.

AKS and container review

Trap: Kubernetes has its own RBAC and runtime model. Azure RBAC alone does not automatically solve pod permissions, container image risk, network policy, or secret handling.

Incident and alert vocabulary

KQL concepts to recognize

You do not need to memorize every KQL function, but you should understand common operations.

Trap: A workbook visualizes data. It does not ingest logs by itself. A connector or diagnostic setting usually supplies the data.

“What should be done first?”

When several answers are plausible, look for the first control that removes the largest risk with least operational complexity.