Azure AD Privileged Identity management (Part 1): Zero Trust Model

By Ashwin Venugopal -

 



To read part 2 please click here

Zero Trust Model

Sometime back security was focused on a strong perimeter defense to keep malicious hackers out. Anything outside the was treated as hostile, whereas inside the wall, an organization's systems were trusted, but today's security posture is to assume breach and use the zero trust model. Nowadays security professionals no longer focus on perimeter defense and modern organizations have to support access to data and services evenly from both inside and outside the corporate firewall.

What does Zero Trust mean?

The Zero Trust Model states that you should never assume trust but instead continually validate trust. Instead of assuming everything behind the corporate firewall is safe, the zero trust model assumes breach and verifies each request as though it originates from an open network. It relies on verifiable user and device trust claims to grant access to organizational resources.

The trust determination components are:
  • Identity Provider that establishes a user's identity and related information.
  • Device Directory which validates a device and the device integrity.
  • Policy evaluation service determines whether the user and device confirm to security policies.

  • Access Proxy determines which organizational resources can be accessed. 

Implementing a Zero Trust Security Model

A zero trust model requires signals to inform decisions, policies to make access decisions, and enforcement capabilities to implement those decisions effectively. Here it is explained thoroughly: 

Signal- To make an informed decision.

Decision- Based on organizational policy.

Enforcement- Of the policy across resources

Zero Trust consider many signal sources- from identity systems to device management and security tools- to create context-rich insights that help make informed decisions.

The access request and signal are analyzed to deliver a decision based on finely-tuned access policies, delivering granular, organization-centric access control.

Decisions are then enforced across the entire digital estate- such as read-only access to SaaS app or remediating compromised passwords with a self-service password reset.

 If you can't determine who the user is, you can't establish a trust relationship for other transactions.

Guiding principles of Zero Trust

  1. Verify Explicitly- Always authenticate and authorize based on all available data points, including user identity, location, device health, service or workload, data classification, and anomalies.
  2. Use least privileged access- Limit user access with Just In Time and Just Enough Access (JIT/JEA), risk based adaptive policies, and data protection to protect both data and productivity.
  3. Assume Breach- Minimize blast radius for breaches and prevent lateral movement by segmenting access by network, user, devices, and application awareness. Verify that all sessions are encrypted end to end. Use analytics to get visibility, drive threat detection, and improve defenses.

Microsoft's Zero Trust Architecture

This system works with intune, pushing device configuration requirements to the managed devices. The device then generates the statement of health, which is stored in Azure AD. When the device user requests access to a resource, the device health state is verified as part of the authentication exchange with Azure AD. Below is a simplified reference architecture for our approach to implementing zero trust:


The National Institute of Standards and Technology has a Zero Trust Architecture, NIST 800-207, publication.




To read part 2 please click here










Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more