Ir al contenido

Part 2: Security, Identity, and Cost Management in Azure

This module is fundamental. It covers how Azure protects its infrastructure and how you can (and should) protect yours.

0views

This module is fundamental. It covers how Azure protects your infrastructure and how you can (and should) protect your own.

  • Definition: (According to Parte_2, Página 48) It is a layered approach to securing computer systems. It provides multiple levels of protection so that if an attack bypasses one layer, it is isolated or stopped by the next.
  • Instructor Note (Castle Analogy):
    • Physical Layer: The moat and walls (Microsoft's data center).
    • Identity Layer: The guard asking for ID (Azure AD).
    • Perimeter Layer: The main gate (Azure Firewall, DDoS).
    • Network Layer: The guards inside the walls (NSGs).
    • Compute Layer: The room locks (VM security).
    • Data Layer: The safe (database encryption).
  • Definition: (According to Parte_2, Página 84) It is the evolution of the “Shared Responsibility Model” (from Part 1) applied to security. Security becomes a shared concern between the provider (Microsoft) and the customer (you).
  • Example: Microsoft is responsible for the security of the physical data center; you are responsible for the security in the cloud (e.g., configuring your NSG correctly).

Here we distinguish the tools that protect from the outside (North-South traffic) from those that protect from within (East-West traffic).

Azure DDoS (Distributed Denial of Service) Protection

Sección titulada «Protección de Denegación de Servicio (DDoS) de Azure»
  • Definition: (According to Parte_2, Página 44) Protects against attacks that attempt to saturate and exhaust your network resources (e.g., flooding your website with fake traffic).
  • Levels (Exam Trap!):
    1. Basic Level: It is enabled automatically and for free across the entire Azure platform. It protects Azure's global infrastructure.
    2. Standard Level: It is a paid service that adds specific and tailored mitigation capabilities for your resources (VMs, Load Balancers), providing telemetry and alerts.
  • Definition: (According to Parte_2, Página 18) It is a managed, stateful firewall-as-a-service (FaaS) (remember the connection context).
  • Function: Grants or denies access to the server based on source IP address, ports, and protocols. It protects against Internet threats.
  • Definition: (According to Parte_2, Página 59) They filter network traffic to and from Azure resources (such as VMs) in your virtual networks (VNet).
  • Function: They are a set of “Allow” or “Deny” rules (based on IP, port, and protocol) applied to a Subnet or a VM's network interface card (NIC).

The exam expects you to confuse Azure Firewall and NSGs. (Ref: Parte_2, Página 50).

  • Azure Firewall: It is the building's doorman. It is placed at your network perimeter (VNet) to protect you from external threats. It is intelligent and centralized.
  • NSG (Network Security Groups): They are the security guards on every floor. They filter traffic between your own VMs (e.g., ensuring the “Web” VM can only communicate with the “DB” VM via port 1433).

You use both for defense in depth.

These are your security “command centers.”

Azure Security Center (Now “Microsoft Defender for Cloud”)

Sección titulada «Azure Security Center (Ahora “Microsoft Defender for Cloud”)»
  • Definition: (According to Parte_2, Página 24) It is a monitoring service that offers threat protection and security recommendations for both Azure and on-premises data centers (hybrid).
  • Key Features (Ref: Parte_2, Páginas 34, 57):
    1. Secure Score: It gives you a score from 0 to 100 of your security “posture.”
    2. Recommendations: It tells you what to fix and how (e.g., “Enable disk encryption”).
    3. Policy Compliance: It measures your compliance against standards (e.g., ISO 27001, HIPAA).
    4. Threat Protection: It analyzes and identifies potential attacks.
  • Definition: (According to Parte_2, Página 26) It is a cloud-native SIEM (Security Information and Event Management) and SOAR (Security Orchestration, Automation and Response) solution.
  • Function: It is an “investigator.” It collects security logs from all your sources (Office 365, Firewalls, Azure AD, VMs) and uses AI to find threats, investigate incidents, and automate responses.

Security Center vs. Sentinel (The Second Big Trap!)

  • Security Center (Defender): Focuses on the Posture and Protection of your resources. It tells you “Your door is open”.
  • Sentinel (SIEM/SOAR): Focuses on threat Detection and Investigation. It checks the security cameras and tells you “Someone tried to open your door at 3:00 AM”.
  • Definition: (According to Parte_2, Página 20) Stores application “secrets” in a centralized cloud location.
  • Purpose: Prevents developers from putting passwords or API keys in the code.
  • Stores 3 things:
    1. Secrets: Connection strings, passwords, API keys.
    2. Keys: Encryption keys.
    3. Certificates: SSL/TLS certificates.
  • Definition: (According to Parte_2, Página 61) Provides physical servers that host only your virtual machines.
  • Purpose: For maximum hardware-level isolation (very strict regulatory compliance) or to control platform maintenance events.
  • Practice: Implement Azure Key Vault: The goal of this practice is to learn how to centralize application secrets, drastically improving security by not exposing passwords in configuration files or code.
  • Practice: Implement secure network traffic: The goal here is to learn how to use NSGs. This practice would involve creating rules to allow web traffic (Port 80/443) but deny direct access to the VM (RDP/SSH) from the Internet.

This section covers who can do what (Identity and Governance) and which rules and promises Azure adheres to (Privacy and Compliance).

This part focuses on Azure Active Directory (AAD) (now Microsoft Entra ID).

Differences between Authentication and Authorization

Sección titulada «Diferencias entre Autenticación y Autorización»
  • Definition: (According to Parte_2, Página 6) This is the most fundamental identity “trap”.
    1. Authentication (AuthN): Is the process of identifying who you are. It requests credentials to prove your identity (e.g., username + password).
    2. Authorization (AuthZ): Is the process of determining what you can do once your identity has been proven. It defines what data you can access.
  • Analogy: Authentication is showing your ID at the building entrance. Authorization is the key that only opens your apartment (and not your neighbor's).
  • Definition: (According to Parte_2, Página 8) Provides additional security by requiring two or more factors for complete authentication.
  • The 3 Factors:
    1. Something you know (e.g., a password, a PIN).
    2. Something you have (e.g., the phone that receives an SMS, an authentication app).
    3. Something you are (e.g., a fingerprint, facial recognition).
  • Definition: (According to Parte_2, Página 10) It is Microsoft's cloud-based identity and access management service.
  • Key Functions:
    • Authentication: Log in to access resources.
    • Single Sign-On (SSO): Log in once and access multiple applications (e.g., Office 365, Salesforce, Azure Portal) without re-entering your password.
    • Application management.
    • B2B (Business-to-Business): Invite “guest” users from other organizations to your AAD.
    • B2C (Business-to-Customer): Allow your customers to sign up and log in to your applications.
  • Definition: (According to Parte_2, Página 4) It is the “brain” or the “smart gatekeeper” of AAD.
  • Function: It gathers signals (who is the user?, where are they?, what device are they using?) to make decisions (Allow, Block) and apply policies (Require MFA).
  • Example: “If an Administrator logs in from an unknown country, Block access. If an employee logs in from outside the office, Allow but Require MFA.”

Governance is how you apply rules and control your resources.

  • Definition: (According to Parte_2, Página 82) Provides specific access administration.
  • Function: Grants users only the access they need to perform their jobs (Principle of Least Privilege).
  • How it works: You assign Roles (e.g., “Reader”, “Contributor”, “Owner”) to Users/Groups within a Scope (Management Group, Subscription, Resource Group).
  • Difference (AAD vs RBAC): AAD manages identity (authentication). RBAC manages access to Azure resources (authorization).
  • Definition: (According to Parte_2, Página 28) Protects your Azure resources from accidental deletion or modification.
  • Types (Exam Trap!):
    1. CanNotDelete: Users can read and modify the resource, but cannot delete it.
    2. ReadOnly: Users can only read. They cannot modify or delete. It is more restrictive.
  • Definition: (According to Parte_2, Página 52) They provide metadata (key-value pairs) for your Azure resources.
  • Function: They are used to logically organize resources.
  • Primary Use Case: Accumulate billing information (e.g., tagging all resources with “cost center: marketing” or “owner: joe”).
  • Definition: (According to Parte_2, Página 22) Helps enforce organizational standards and evaluate compliance at scale.
  • Function: It is the “audit and rules” service.
  • Example: You can create a policy to “Disallow the creation of VMs in regions outside of Europe” or “Audit all VMs that do not have disk encryption enabled”.
  • Definition: (According to Parte_2, Página 12) It allows teams to create and deploy new environments quickly that comply with regulations.
  • Function: It's a “package” or “template” that groups:
    • Role assignments (RBAC).
    • Policy assignments (Policy).
    • ARM templates (the resources to be created).
    • Resource groups.
  • Difference (Policy vs Blueprints): A Policy is a rule. A Blueprint is a set of rules, roles, and resources to deploy a complete and compliant environment from the start.
  • Definition: (According to Parte_2, Página 38) It is Microsoft's documented approach (recommended procedures, tools, and stories) to guide you on your cloud adoption journey.
  • Purpose: It is not a service; it is a strategy and planning guide.
  • Definition: (According to Parte_2, Página 86) These are Microsoft's commitments:
    • Security: Protect against cyber threats.
    • Privacy: Ensure data privacy through contractual agreements.
    • Compliance: Respect local laws and regulations.
  • Definition: (According to Parte_2, Página 92) Microsoft offers the most comprehensive set of compliance offerings (certifications and attestations) of any other provider.
  • Examples of Standards:
    • HIPAA: (USA) Health Insurance Portability and Accountability Act.
    • ISO/IEC 27018: Cloud privacy standard.
    • NIST: (USA) National Institute of Standards and Technology.
  • Definition: (According to Parte_2, Página 46) Explains what data Microsoft processes, how it processes it, and for what purpose it is used. Provides transparency.
  • Definitions: (According to Parte_2, Página 40)
    • OST: The legal terms and conditions you accept when purchasing services.
    • DPA: Establishes Microsoft's obligations regarding the processing and security of your data (Customer Data).
  • Definition: (According to Parte_2, Página 36) It is the public website where Microsoft provides detailed information about security, privacy, compliance, and policies.
  • Purpose: This is where you will find audit reports, certifications, and all compliance documentation.
  • Definition: Special Azure instances designed to meet strict data sovereignty and residency requirements.
  • Azure China 21Vianet: (According to Parte_2, Página 14)
    • It is a physically separate Azure instance.
    • It is managed by a Chinese partner (21Vianet).
    • All data stays within China to ensure compliance with the Chinese government.
  • Azure Government: (Not in your PDF, but relevant) Similar instances for the U.S. government.
  • Practice: Managing resource locks: The goal is to learn how to apply a lock (e.g., CanNotDelete) to a Resource Group or a critical resource (such as a database) to prevent accidental deletion.
  • Practice: Creating an Azure policy: The goal is to learn how to assign a built-in policy (e.g., “Allow only certain regions”) to a subscription to enforce company governance rules.

This is the final section of the syllabus. It covers how costs are calculated, how they are managed, and what service level agreements (SLAs) Azure offers, as well as how new features are released.

(According to Parte_2, Páginas 54-55) The exam expects you to know which factors influence the bill.

  1. Resource Type: Each service (VM, Storage, DB) has its own meter and price.
  2. Services: Support plans (Developer, Standard, ProDirect) and subscription types (Enterprise, Pay-as-you-go) can affect the price.
  3. Location (Region): Infrastructure is distributed globally and costs vary between regions (e.g., “US East” is often cheaper than “West Europe”).
  4. Bandwidth (Data Transfer):
    • Data Ingress: Generally free.
    • Data Egress: Generally paid. Pricing is based on billing “Zones”.
  5. Reserved Instances (Reservations): You commit to using a resource (such as a VM) for one or three years in exchange for a significant discount (up to 72%) on the pay-as-you-go price.
  6. Azure Hybrid Benefit: Allows customers with Software Assurance (SA) to use their on-premises licenses (e.g., Windows Server or SQL Server) in Azure at a reduced cost (essentially, you only pay for the base infrastructure).
  • Definition: (According to Parte_2, Página 30) A public tool (website) that helps you estimate the cost of the Azure products you plan to use.
  • When to use: BEFORE deployment, during the planning phase.
  • Configurations: You configure Region, Tier (e.g., Standard vs. Premium), Billing Options (Pay-as-you-go vs. Reservations), etc.
  • Definition: (According to Parte_2, Página 32) A tool to estimate the savings you can achieve when migrating from your on-premises infrastructure to Azure.
  • When to use: BEFORE migrating, to justify the move to the cloud.
  • Function: Compares your local costs (hardware, electricity, IT staff, cooling) with equivalent costs in Azure.

Exam Trap! (TCO vs. Pricing Calculator):

  • TCO Calculator: Compares Local vs. Azure. Helps you decide if you should migrate.
  • Pricing Calculator: Estimates costs within Azure. Helps you plan what to deploy.
  • Definition: (According to Parte_2, Página 16) It is the service within the Azure Portal that helps you understand, analyze, and optimize your current costs.
  • When to use: AFTER deployment, to monitor spending.
  • Key Functions:
    • Report creation: See where you are spending money.
    • Set Budgets: Establish a maximum limit (e.g., €500/month).
    • Alerts: Receive notifications if you approach your budget limit.
    • Recommendations: Provides tips (integrates with Azure Advisor).

Tactics you should know for the exam:

  1. Use Reservations: For stable workloads.
  2. Use Hybrid Benefit (HUB): If you have licenses with SA.
  3. Choose low-cost regions: If latency is not critical.
  4. Use Tags: To identify cost owners and see who is spending what.
  5. Monitor with Advisor: Implement cost recommendations.
  6. Use spending limits: Available in free trial subscriptions.
  • Definition: (According to Parte_2, Página 42) They describe Microsoft's commitments regarding uptime and connectivity.
  • Format: Expressed as a percentage, e.g., “99.9%” (three nines).
  • Important: SLAs are individual for each service. Services in Preview or free services typically do not offer SLAs.
  • Definition: (According to Parte_2, Página 90) Performance objectives range from 99% to 99.999%.
  • What happens if they fail? If a service does not meet the SLA guarantee, Microsoft credits (returns) you a percentage of the monthly fees for that service. They never return cash; it is a credit for future invoices.
  • Definition: (According to Parte_2, Página 2) You can compose SLAs.
  • Actions to INCREASE your SLA (Compound SLA):
    • Use Availability Zones: Deploying a VM in multiple zones gives you a 99.99% SLA. A single VM with a Premium disk only provides 99.9%.
    • Use Redundant Systems: Placing several VMs behind a load balancer.
  • Actions to REDUCE your SLA:
    • Add more chained services: If a website (99.9%) depends on a database (99.9%), the total SLA is 99,9% * 99,9% = 99,8%.
    • Choose free or non-SLA services: If a component of your app is “Free,” your app's total SLA is 0%.
  • Definition: (According to Parte_2, Página 80) Allows users to test features (beta) before the official release.
  • Types:
    1. Private Preview: Invitation only.
    2. Public Preview: All Azure customers can evaluate new features. Important: They have no SLA! They should not be used for production.
    3. General Availability (GA): The feature is finished, available to everyone, has an SLA, and is production-ready.
  • Definition: (According to Parte_2, Página 88) The “Azure Updates” portal is the official website where Microsoft provides information about new products, features, roadmaps, and availability.
  • Function: It is the best way to know what is new. You can subscribe via RSS.
  • Practice: Using the Pricing Calculator: The goal of this practice is to learn how to use the web tool (Pricing Calculator) to estimate a scenario. It involves adding a resource (e.g., a VM), configuring it (Region, OS, Size, usage hours), and adding options (e.g., a Support plan or a disk) to see how the estimated price changes in real time.

This document groups all the practical exercises from “Part 2: Security, Identity, and Cost Management,” detailing the learning objective of each one.

  • Topic Reference: Parte_2, Página 20.
  • Practice Objective: Learn to centralize the storage of “secrets” (such as passwords or API keys) so they are not exposed in application code or configuration files.
  • Key Practice Concepts:
    1. Create the Vault: Deploy an Azure Key Vault resource.
    2. Define Access Policies: Configure who (a user or an application) has permission to leer, escribir, or eliminar secrets.
    3. Add a Secret: Create a key-value entry (e.g., Nombre: "constr-db", Valor: "P@ssw0rd123").
    4. Integration (The most important step): Configure an application (such as an App Service) to use a Managed Identity (Managed Identity). This identity gives the application permission to read the Key Vault secret directly, without the developer needing to know the password.
  • Topic Reference: Parte_2, Página 59.
  • Practice Objective: Learn to use Network Security Groups (NSG) to filter network traffic and apply a basic security policy.
  • Key Practice Concepts:
    1. Create an NSG: Deploy the NSG resource.
    2. Create Inbound Rules: The typical scenario is a VM acting as a web server.
      • Create a high-priority rule (e.g., 100) to Allow traffic on ports 80 (HTTP) and 443 (HTTPS) from source Cualquiera (Any).
      • Create a lower-priority rule (e.g., 200) to Deny administrative access (port 22 for SSH or 3389 for RDP) from source Internet.
      • (Optional) Create a higher-priority rule (e.g., 110) to Allow RDP/SSH only from your office IP address (Mi IP).
    3. Associate the NSG: Apply this set of rules to the VM's Subnet (to protect all VMs in that subnet) or directly to the VM's Network Interface Card (NIC).
  • Topic Reference: Parte_2, Página 28.
  • Practice Objective: Learn to protect critical resources against accidental deletion or modification.
  • Key Practice Concepts:
    1. Navigate to Resource: Go to an important resource (such as a production Resource Group, a critical VM, or a Database).
    2. Go to “Locks”: In the resource menu, select the “Locks” option.
    3. Add a Lock:
      • Lock Type CanNotDelete (Cannot be deleted): This is the most common. It prevents any user (even the Owner) from deleting the resource, but allows it to continue functioning and being modified.
      • Lock Type ReadOnly (Read-only): This is much more restrictive. It prevents deleting AND modifying the resource. (Careful! Applying this to a production DB would stop it, as it would not be able to write new data).
  • Topic Reference: Parte_2, Página 22.
  • Practice Objective: Learn how to use Azure Policy to apply governance rules and audit compliance at scale.
  • Key Practice Concepts:
    1. Navigate to “Policy”: Go to the Azure Policy service.
    2. Assign a Policy: Select “Assignments” -> “Assign policy”.
    3. Select the Scope: Choose where the rule will be applied (e.g., to the entire Subscription or only to a development Resource Group).
    4. Select the Definition: Choose a built-in rule. Common examples for the exam:
      • “Allowed Locations (Regions)”: To force deployment only in Europe.
      • “Allowed VM SKUs”: To prevent the creation of huge and expensive VMs.
      • “Audit VMs that do not use managed disks”: To find non-compliant resources.
    5. Review Compliance: After a few minutes, the “Compliance” panel will show which existing resources are violating the new rule.
  • Topic Reference: Parte_2, Página 30.
  • Practice Objective: Learn how to use the public web tool Pricing Calculator to estimate the costs of a scenario before deploying it.
  • Key Practice Concepts:
    1. Add Resources: Search for and add products to the canvas (e.g., “Virtual Machines”, “Storage Accounts”).
    2. Configure Options: Change each resource's parameters to match your needs. You'll see the price change in real-time.
      • Region: (e.g., “West Europe” vs “US East”).
      • Size/Tier: (e.g., VM B2s vs D4s; Storage LRS vs GRS).
      • Usage Hours: (e.g., 730 hours/month for 24/7 vs 200 hours/month for development).
    3. Billing Options: Compare the price of Pay-as-you-go with a 1 or 3-year Reservation to see the savings.
    4. Add Support/Licenses: Include an Azure Support Plan or Azure Hybrid Benefit (AHB).
    5. Export: Save the estimate to share with the team.