Zero Trust
CIA-Zero Trust
CIA Triad (Very Important)
The goal of Defense in Depth is to protect the CIA Triad.
!image.png
Here's the CIA Triad in a clean table format for easy SC-900 revision.
| CIA | Meaning | Example | Technologies | Easy Memory |
|---|---|---|---|---|
| Confidentiality (C) π | Only authorized people can access or view the data. | Only the HR department can view employee salaries. | Encryption, Multi-Factor Authentication (MFA), Access Control | Confidential = Secret |
| Integrity (I) β | Data should not be changed without authorization. | A student's exam marks should not be modified by another student. | Hashing, Digital Signatures, Audit Logs | Integrity = Correct Data |
| Availability (A) π’ | Data and systems should be available whenever authorized users need them. | Microsoft Teams should be accessible during office hours. | Backup, Load Balancer, Disaster Recovery, DDoS Protection | Availability = Always Available |
| Letter | Remember |
|---|---|
| C | Confidentiality = Keep Data Secret π |
| I | Integrity = Keep Data Correct β |
| A | Availability = Keep Data Accessible π’ |
Quick Exam Tip:
- Data stolen β Confidentiality
- Data modified β Integrity
- Service unavailable β Availability
AAA
!Screenshot 2026-07-28 101054.png
!Screenshot 2026-07-28 101234.png
!Screenshot 2026-07-28 103507.png
Q1. Why use Defense in Depth?
β Because multiple layers of security provide better protection than relying on a single security control.
Q2. Which layer is the most important?
β Data Layer, because the main goal is to protect the organization's data.
Q3. What protects user identity?
β Identity Layer (MFA, RBAC, passwords).
Q4. What protects against internet attacks?
β Perimeter Layer (Firewall, DDoS Protection).
Q5. What protects the operating system?
β Compute Layer.
β SC-900 One-Page Revision
| Layer | Purpose | Example |
|---|---|---|
| Physical | Protect building | CCTV, Guards |
| Identity | Verify users | MFA, RBAC |
| Perimeter | Stop internet attacks | Firewall, DDoS |
| Network | Control traffic | NSG, VNet |
| Compute | Protect servers | Patch OS, Antivirus |
| Application | Secure apps | Input Validation |
| Data | Protect information | Encryption, Backups |
π― SC-900 Memory Shortcut
- Defense in Depth = Many security layers (if one fails, another protects).
- PIP N CAD = Physical β Identity β Perimeter β Network β Compute β Application β Data.
- CIA = Confidentiality (Secret), Integrity (Correct), Availability (Always Accessible).
Zero Trust Model
What is Zero Trust?
!Screenshot 2026-06-30 091634.png
Definition
Zero Trust = Never Trust, Always Verify
Don't trust anyone automatically, even if they are inside the company network.
Every time someone tries to access data, Microsoft checks:
- β Who are you?
- β Which device are you using?
- β Where are you logging in from?
- β What are you trying to access?
Only after verification is access granted.
Easy Example
Imagine you're entering an airport.
Even if you're already inside the airport:
- Passport β
- Boarding Pass β
- Security Check β
- Face Verification β
You are checked multiple times.
Zero Trust works exactly like this.
Traditional Security vs Zero Trust
| Traditional Security | Zero Trust |
|---|---|
| Trust users inside the network | Trust nobody by default |
| Login once | Verify continuously |
| Network is trusted | Every request is verified |
Three Principles of Zero Trust
These are very important for SC-900.
Zero Trust β 3 Guiding Principles (SC-900)
| Principle | Meaning | What is Checked? | Example | Easy Memory |
|---|---|---|---|---|
| 1. Verify Explicitly β | Always verify every access request before granting access. Never trust by default. | β Identityβ Deviceβ Locationβ Applicationβ Risk | Rahul logs in to Microsoft 365. Microsoft verifies his password, MFA, device compliance, and login location before allowing access. | Verify everything before giving access. |
| 2. Use Least Privilege π | Give users only the minimum permissions they need to perform their job. | Only required roles and permissions are assigned. | HR can access salary data, Developers can access source code, Accountants can access financial records. A developer cannot view salary information. | Minimum Access = Maximum Security |
| 3. Assume Breach π¨ | Always assume an attacker may already be inside the network and limit the damage. | Detect suspicious activity, require MFA, monitor users, segment networks, and block risky access. | A hacker steals an employee's password. Microsoft detects an unusual login, requests MFA, blocks access, and alerts the security team. | Always assume attackers are already inside. |
π― SC-900 Memory Trick
| Principle | Remember |
|---|---|
| β Verify Explicitly | Verify every login |
| π Least Privilege | Give minimum access |
| π¨ Assume Breach | Assume hackers are already inside |
Seven Pillars of Zero Trust
Microsoft protects 7 areas.
About the author
- Cloud Security & DevSecOps Engineer with 4+ years of experience in securing and managing cloud infrastructure across AWS, Azure, GCP, and Alibaba Cloud. Currently working as an External Cloud Security Consultant with Deloitte, supporting SAP in CSPM and multi-cloud security initiatives. Skilled in cloud security, compliance, vulnerability management, IAM, security automation, and governance. Hands-on experience with AWS Security Hub, GuardDuty, AWS Config, KMS, WAF, Inspector, Terraform, Checkov, TFSec, GitHub Actions, Argo CD, Trivy, and Semgrep. Experienced in Kubernetes, Amazon EKS, Docker, Helm, CI/CD security, Infrastructure as Code, and Security as Code. Familiar with CIS Benchmarks, NIST, PCI DSS, and AWS security best practices. AWS Certified Solutions Architect β Associate and HashiCorp Certified Terraform Associate, with a strong focus on building secure, scalable, and automated cloud platforms.
Comments
Join the discussionNo comments yet. Be the first to comment.