Study guide

2.4 Encryption, Hashing, and Data States

Azure SC-900 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map

1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map

2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC

2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation

3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication

3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities

4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection

4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk

5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault

5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets

6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score

6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans

7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks

7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks

8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence

8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence

9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score

9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager

10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit

10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management

11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps

11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop

12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path

12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900

2.4 Encryption, Hashing, and Data States

Key Takeaways Explain This Topic AI

Encryption makes data unreadable to unauthorized viewers and is reversible with the correct key; SC-900 tests it as a data-protection concept, not deep cryptography.

Symmetric encryption uses one shared key for both encrypt and decrypt (fast, good for bulk data, e.g. AES); asymmetric encryption uses a public/private key pair (e.g. RSA) and underpins key exchange and digital signatures.

Data exists in three states — at rest (stored), in transit (moving across a network), and in use (being processed in memory) — and each can be protected with encryption.

Hashing is one-way: it produces a fixed-length digest that cannot be reversed, so it is used for integrity checks and password storage (with salting), not for confidentiality.

Exam clue is in the verb: 'make unreadable but recoverable by authorized users' -> encryption; 'detect change or avoid storing plain passwords' -> hashing.

Last updated: June 2026

Encryption: reversible protection with a key

Encryption is the process of making data unreadable and unusable to unauthorized viewers. To read encrypted data, it must be decrypted using the required key. If an attacker steals encrypted data but not the key, the data should stay unreadable — which is why encryption protects the confidentiality goal of the CIA triad. SC-900 tests encryption as a foundational concept, not as a mathematics exam, so focus on what each type is for and when to choose it.

Microsoft Learn describes two primary types:

Type Keys used Strengths Typical use Example algorithms

Symmetric One shared secret key for both encrypt and decrypt Fast; efficient for large volumes of data Bulk data encryption, storage and disk encryption AES, 3DES

Asymmetric A related public/private key pair Solves key distribution; enables digital signatures Key exchange, TLS handshakes, signing, certificates RSA, ECC

Symmetric encryption uses the same key to encrypt and decrypt. It is fast, but the challenge is securely sharing that single key between parties. Asymmetric encryption uses a mathematically related public key and private key . Data encrypted with the public key can be decrypted only with the matching private key (confidentiality), and data signed with the private key can be verified with the public key (authenticity and integrity via digital signatures). In practice, systems often combine both — asymmetric encryption to exchange a symmetric session key, then fast symmetric encryption for the bulk data.

The three data states

Protection goals differ depending on where data is, so SC-900 expects you to know the three states and that encryption can protect each:

Data at rest — data stored on a device, disk, database, or storage account. Protected by storage/disk encryption (for example, encrypting an Azure Storage account or a database).

Data in transit — data moving across a network, between services, or over the internet. Protected by transport encryption such as TLS/HTTPS.

Data in use — data actively being processed in memory or by compute. This is the hardest to protect; technologies like confidential computing aim to protect it while in use.

A common distractor invents a fourth state such as 'data in retirement' — there are only three. Expect a scenario like 'data is moving between two microservices' (in transit) or 'records are saved in a database' (at rest), and match the state to the right encryption point.

Key management matters

Encryption is only as strong as the protection of its keys. If keys are exposed, the encryption is defeated. Whenever a scenario asks 'how does encrypted data stay secure,' the answer involves protecting, storing, and rotating keys (in Azure, services like Azure Key Vault manage keys and secrets) and controlling who can access them. 'Bring your own key' and 'customer-managed keys' are options where the customer controls the key material.

Hashing: one-way fingerprints

Hashing is fundamentally different from encryption. A hash function converts any input into a fixed-length value called a digest (or hash). Three properties define it:

One-way — you cannot reverse a hash to recover the original input. There is no 'decryption key' for a hash.

Deterministic — the same input with the same algorithm always produces the same digest.

Avalanche effect — changing even one character of the input produces a completely different digest.

These properties make hashing ideal for integrity verification: if a downloaded file's computed hash differs from the published hash, the file changed in transit. Hashing is also used in password storage . Rather than storing a plaintext password, a system stores its hash; at sign-in, the entered password is hashed and compared to the stored value. Salting adds a unique random value before hashing so that two users with the same password get different stored hashes, defeating precomputed (rainbow-table) attacks.

Encryption vs. hashing — choosing correctly

If the scenario says... Choose Because

Data must be unreadable now but recoverable later by authorized users Encryption Encryption is reversible with the correct key

  • Verify whether a file or message was altered Hashing A changed input yields a different digest
  • Avoid storing plaintext passwords Hashing (with salt) Hashes are not reversible to the original password

Two parties must exchange a secret over an open network Asymmetric encryption A public/private key pair solves key distribution

The exam often hides the answer in the verb . 'Make unreadable but later recover' signals reversible encryption . 'Detect change' or 'don't store the plain password' signals one-way hashing . A frequent trap is claiming hashing keeps data secret — it does not provide confidentiality; it provides a tamper-evident fingerprint.

Digital signatures tie it together

A digital signature combines hashing and asymmetric encryption, and it is a favorite exam connection point. The sender hashes the message to create a digest, then encrypts that digest with their private key to form the signature. The recipient decrypts it with the sender's public key , re-hashes the received message, and compares the digests. A match gives two assurances: integrity (the message was not altered) and authenticity/non-repudiation (only the private-key holder could have signed it). A digital signature does not hide the message — it proves who sent it and that it was unchanged, not that it is secret.

One-paragraph cheat sheet

Encryption protects confidentiality and is reversible with a key (symmetric = one shared key, fast, bulk data; asymmetric = public/private pair, key exchange and signatures). Hashing protects integrity , is one-way , and is used for tamper detection and salted password storage. Data lives in three states — at rest, in transit, in use — and encryption can protect each.