azureblog.co.uk
← SC-500 study plan
SC-500 · Secure storage, databases, and networkingAlso in SC-500

Secure storage accounts and databases

Storage account security settings, firewall rules, Defender for Storage, access policies, Azure SQL platform security, database auditing and Defender for Databases.

  • 20 min
  • 7 concepts
  • Try it yourself
  • 4-question check

Learn

Storage accounts and databases hold the data attackers want. The pattern is the same for both: identity-based access, no public network exposure, encryption, logging, and threat detection.

  1. 1

    Implement and configure security for storage accounts

    Turn off shared key access where possible (forces Entra ID auth), turn off anonymous blob access, require secure transfer and TLS 1.2 minimum, use infrastructure encryption or customer-managed keys if required, and enable soft delete and versioning. Use Azure Policy to enforce these.

    Remember: Disable shared key access to force Entra ID authentication.

  2. 2

    Configure Azure Storage firewall rules

    Set public network access to disabled and use private endpoints, or enabled from selected virtual networks and IP addresses. Add resource instance rules for specific Azure services and allow trusted Microsoft services where needed. Network rules don't stop access via private endpoints.

    Remember: Best: public access disabled, private endpoints only.

  3. 3

    Implement Defender for Storage threat protection configurations

    Defender for Storage detects suspicious activity (unusual access, data exfiltration patterns, access from Tor), malware scanning on upload (near real time, with results as blob index tags or events to quarantine), and sensitive data threat detection to prioritise alerts on sensitive data. Enable at subscription level with per-account overrides and a monthly scanning cap.

    Remember: Malware scanning on upload with automatic quarantine via events.

  4. 4

    Manage access to storage, including access policies

    Prefer Entra ID with data roles (Storage Blob Data Reader/Contributor). If SAS is needed, use user delegation SAS, short expiry and HTTPS only. Use stored access policies on containers so service SAS tokens can be revoked by changing or deleting the policy. Configure a SAS expiration policy and rotate account keys.

    Remember: Revocable SAS: stored access policy.

  5. 5

    Implement platform-level security configurations in Azure SQL

    Use Microsoft Entra-only authentication, disable public network access with private endpoints, keep TDE on (with customer-managed keys if required), use Always Encrypted for sensitive columns, dynamic data masking and row-level security, set minimum TLS and enable ledger for tamper evidence.

    Remember: Entra-only authentication removes SQL logins.

  6. 6

    Configure database auditing for Azure SQL Database and Azure SQL Managed Instance

    Auditing tracks database events to a storage account, Log Analytics or Event Hubs. Server-level auditing applies to all databases. Audit Microsoft support operations too. Query audit logs in Log Analytics or with the audit logs viewer.

    Remember: Server-level auditing covers every database on the server.

  7. 7

    Configure Defender for Databases protection across Azure database services

    Defender for Databases covers Azure SQL, SQL servers on machines, open-source relational databases (PostgreSQL, MySQL, MariaDB) and Cosmos DB: vulnerability assessment (express configuration for SQL), and threat detection for SQL injection, anomalous access and brute force.

    Remember: SQL injection alerts: Defender for SQL.

Same principles, two services

PrincipleStorageAzure SQL
IdentityDisable shared key; Entra data rolesEntra-only authentication
NetworkPrivate endpoint, public access offPrivate endpoint, public access off
EncryptionSSE, CMK, infrastructure encryptionTDE, CMK, Always Encrypted
LoggingDiagnostic settingsAuditing
ThreatsDefender for StorageDefender for SQL

Try it

Build a SAS and see how each choice affects risk and revocation.

This interactive part needs JavaScript.

In the portal

  • Storage configurationAzure portal: Storage accounts > your account > Settings > Configuration
  • Storage networkingAzure portal: Storage accounts > your account > Security + networking > Networking
  • SQL auditingAzure portal: SQL servers > your server > Security > Auditing
  • Entra-only authAzure portal: SQL servers > your server > Settings > Microsoft Entra ID

Key terms

Click a card to see the definition.

Check your understanding

4 questions. Score 80% or more and these skills are marked as confident in your SC-500 and SC-500 study plan.

  1. How do you force Entra ID authentication on a storage account?

  2. How can a service SAS be revoked without rotating keys?

  3. Which removes SQL authentication from Azure SQL?

  4. What scans uploaded blobs for malware?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.