Security pillar principles in Azure - Commands & Configuration

Introduction

Security pillar principles help protect your cloud resources from threats. They guide you to keep data safe, control access, and monitor your environment.

When you want to protect sensitive customer data in your cloud applications

When you need to control who can access your cloud resources and what they can do

When you want to detect and respond to security threats quickly

When you need to comply with laws and regulations about data protection

When you want to build trust with users by keeping their information secure

Commands

This command enables automatic provisioning of security services in your Azure subscription to help protect resources.

Terminal

az security auto-provisioning-setting create --name default --auto-provision On

Expected Output

{

  "autoProvision": "On",

  "id": "/subscriptions/00000000-0000-0000-0000-000000000000/providers/Microsoft.Security/autoProvisioningSettings/default",

  "name": "default",

  "type": "Microsoft.Security/autoProvisioningSettings"

}

→

--name - Sets the name of the auto-provisioning setting

→

--auto-provision - Turns auto-provisioning On or Off

This command assigns the Reader role to a user or service, giving them read-only access to resources in a specific resource group.

Terminal

az role assignment create --assignee 11111111-1111-1111-1111-111111111111 --role Reader --scope /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/myResourceGroup

Expected Output

{

  "canDelegate": null,

  "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/myResourceGroup/providers/Microsoft.Authorization/roleAssignments/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",

  "name": "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",

  "principalId": "11111111-1111-1111-1111-111111111111",

  "principalType": "User",

  "roleDefinitionId": "/subscriptions/00000000-0000-0000-0000-000000000000/providers/Microsoft.Authorization/roleDefinitions/acdd72a7-3385-48ef-bd42-f606fba81ae7",

  "scope": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/myResourceGroup",

  "type": "Microsoft.Authorization/roleAssignments"

}

→

--assignee - Specifies the user or service principal to assign the role

→

--role - Specifies the role to assign

→

--scope - Limits the role assignment to a specific resource or group

This command lists security alerts in the specified resource group to help you monitor potential threats.

Terminal

az security alert list --resource-group myResourceGroup

Expected Output

[

  {

    "alertDisplayName": "Suspicious login",

    "alertType": "SuspiciousLogin",

    "severity": "High",

    "status": "Active",

    "timeGenerated": "2024-06-01T12:00:00Z"

  }

]

→

--resource-group - Filters alerts to a specific resource group

Key Concept

If you remember nothing else from this pattern, remember: controlling access, protecting data, and monitoring threats are the core of cloud security.

Common Mistakes

Assigning overly broad permissions to users or services

This can lead to accidental or malicious changes that harm your resources or data.

Use the principle of least privilege by assigning only the permissions needed for the task.

Not enabling automatic security service provisioning

Without automatic provisioning, some security features may not be active, leaving gaps in protection.

Enable auto-provisioning to ensure security services are always running.

Ignoring security alerts or not monitoring them regularly

Threats can go unnoticed and cause damage if alerts are not reviewed and acted upon.

Regularly check security alerts and respond promptly to any issues.

Summary

Enable automatic security service provisioning to protect resources continuously.

Assign roles carefully to control who can access and change your cloud resources.

Monitor security alerts regularly to detect and respond to threats quickly.

Practice

1. Which of the following best describes the main goal of the Security pillar in cloud architecture?

easy

A. Optimize cloud costs and resource usage

B. Protect cloud resources from threats and unauthorized access

C. Improve application performance and scalability

D. Automate deployment and infrastructure management

Solution

1. Step 1: Understand the purpose of the Security pillar

   The Security pillar focuses on protecting cloud resources from threats and unauthorized access.

2. Step 2: Compare with other cloud pillars

   Other pillars like Cost Optimization or Performance Efficiency focus on costs and performance, not security.

3. Final Answer:

   Protect cloud resources from threats and unauthorized access -> Option B

4. Quick Check:

   Security pillar = Protect resources [OK]

Hint: Security pillar means protecting resources from threats [OK]

Common Mistakes:

• Confusing security with cost or performance
• Thinking security is only about firewalls
• Ignoring access control as part of security

2. Which Azure service is primarily used to manage user identities and control access to resources securely?

easy

A. Azure Active Directory

B. Azure Monitor

C. Azure Blob Storage

D. Azure DevOps

Solution

1. Step 1: Identify the service for identity and access management

   Azure Active Directory (Azure AD) manages user identities and access control.

2. Step 2: Eliminate unrelated services

   Azure Monitor is for monitoring, Blob Storage is for data storage, DevOps is for development pipelines.

3. Final Answer:

   Azure Active Directory -> Option A

4. Quick Check:

   Identity management = Azure AD [OK]

Hint: Azure AD controls user access and identities [OK]

Common Mistakes:

• Choosing monitoring or storage services for access control
• Confusing Azure AD with Azure DevOps
• Ignoring identity management as part of security

3. Consider this Azure policy snippet that denies public IP assignment to virtual machines:

{
  "if": {
    "field": "Microsoft.Network/publicIPAddresses/ipAddress",
    "exists": true
  },
  "then": {
    "effect": "deny"
  }
}

What is the expected behavior when a user tries to assign a public IP to a VM?

medium

A. The assignment is denied and blocked by the policy

B. The assignment is allowed without restrictions

C. The assignment is allowed but logged for review

D. The assignment triggers an alert but proceeds

Solution

1. Step 1: Analyze the policy condition

   The policy checks if a public IP address exists on the resource.

2. Step 2: Understand the policy effect

   The effect is set to "deny", which blocks the action if the condition is true.

3. Final Answer:

   The assignment is denied and blocked by the policy -> Option A

4. Quick Check:

   Policy effect 'deny' blocks public IP assignment [OK]

Hint: Policy with 'deny' effect blocks matching actions [OK]

Common Mistakes:

• Confusing 'deny' with 'audit' or 'allow'
• Assuming the assignment is allowed but logged
• Ignoring the policy effect field

4. You wrote this Azure Role-Based Access Control (RBAC) assignment JSON:

{
  "roleDefinitionId": "/subscriptions/12345/providers/Microsoft.Authorization/roleDefinitions/",
  "principalId": "12345678-1234-5678-9abc-def012345678",
  "scope": "/subscriptions/12345/resourceGroups/myRG"
}

Why does this assignment fail to grant access?

medium

A. The principalId is empty, so no user or group is assigned

B. The scope is invalid because resource group names cannot be used

C. The roleDefinitionId is missing the role GUID

D. The JSON format is incorrect and missing commas

Solution

1. Step 1: Check the roleDefinitionId completeness

   The roleDefinitionId must include the full GUID of the role after /roleDefinitions/.

2. Step 2: Verify other fields

   The principalId and scope are properly formatted; the issue is the incomplete roleDefinitionId.

3. Final Answer:

   The roleDefinitionId is missing the role GUID -> Option C

4. Quick Check:

   RoleDefinitionId needs full GUID [OK]

Hint: RoleDefinitionId must include full role GUID [OK]

Common Mistakes:

• Ignoring missing role GUID in roleDefinitionId
• Blaming the principalId instead of roleDefinitionId
• Thinking resource group names are invalid scopes

5. You want to design a secure Azure environment that automatically detects threats, controls access, encrypts data, and prepares for incidents. Which combination of Azure services best supports the Security pillar principles?

hard

A. Azure Virtual Machines, Azure Load Balancer, Azure Traffic Manager, Azure CDN

B. Azure DevOps, Azure Blob Storage, Azure Functions, Azure Monitor

C. Azure Logic Apps, Azure Cosmos DB, Azure App Service, Azure Automation

D. Azure Security Center, Azure Active Directory, Azure Key Vault, Azure Sentinel

Solution

1. Step 1: Identify services for threat detection and monitoring

   Azure Security Center and Azure Sentinel provide threat detection and security monitoring.

2. Step 2: Identify services for access control and data encryption

   Azure Active Directory manages access; Azure Key Vault secures encryption keys and secrets.

3. Step 3: Confirm the combination supports incident preparation

   Azure Sentinel helps with incident response and investigation.

4. Final Answer:

   Azure Security Center, Azure Active Directory, Azure Key Vault, Azure Sentinel -> Option D

5. Quick Check:

   Security services combo = Azure Security Center, Azure Active Directory, Azure Key Vault, Azure Sentinel [OK]

Hint: Combine security monitoring, access, encryption, and incident tools [OK]

Common Mistakes:

• Choosing unrelated services like DevOps or CDN
• Ignoring encryption or access control services
• Confusing monitoring with deployment tools