The Zero Trust Model

By Ashwin Venugopal -

 





Zero Trust Concept

As the name suggests zero trust always assumes breach and verifies every request as though it originates from an open network, instead of assuming that everything behind the corporate firewall is completely safe. Zero trust always teaches us to "never trust, always verify". while every access request is fully authenticated, authorized, and encrypted before granting access, the rich intelligence and analytics are used to detect as well as respond to the anomalies on real time.

Zero Trust Principles

  • Verify explicitly- You must always authenticate as well as authorize according to the available data points, along with the user identity, location, device health, service or workload, data classification, and anomalies.

  • Use least privileged access- User access must be limited with the help of Just-in-Time and Just-Enough-Access (JIT/JEA), risk-based adaptive policies, and data protection to protect both the data as well as productivity.

  • Assume breach- The blast radius must be minimized for breaches and lateral movement should be prevented by segmenting access by network, user, devices, and app awareness with the help of analytics to get visibility, drive threat detection, and improve defenses.

Zero Trust Components

The six primary components are:

  1. Identities- Each identity must be verified and secured with strong authentication across your entire digital environment.

  1. Devices- Gain visibility into the devices accessing the network after ensuring their health status and compliance before granting access.

  1. Applications- Discover shadow IT, ensure appropriate in-app permissions, gate access based on real-time analytics while also monitoring and control user actions.

  1. Data- Prefer data-driven protection instead of perimeter-based data protection, use intelligence to classify and label data, encrypt and restrict access based organizational policies.

  1. Infrastructure- You can readily use telemetry to detect attacks as well as anomalies, automatically block as well as flag risky behavior, and employ least privilege access principles.

  1. Network- You should not blindly trust the devices and users simply because they are on an internal network. You must encrypt all internal communications, limit access by policy, employ microsegmentation, and real-time threat detection. 

Plan for a Zero Trust Model

A successful zero trust strategy contains seamless as well as flexible access to systems, applications, and data while also ensuring the security of both the users and the resources required to complete their jobs. The steps to securing your identity infrastructure includes:

  • Strengthen your credentials- If users in your identity system uses weak passwords without strengthening them with MFA, you will be compromised more often.

  • Reduce your attack surface area- You must avoid using older, less secure protocols, limit access entry points, and exercise more significant control of administrative access to resources to make it harder for the hackers to even think of an attack.

  • Automate threat response- You can easily reduce costs and risks by simply reducing the time criminals have to embed themselves into your environment.   

  • Increase your awareness- The regular auditing as well as logging of security-related events and alerts, will help you to identify the pattern that may indicate an internal attack or attempted or successful external penetration of your network.

  • Enable user self-help- You can reduce friction by simply empowering your users to stay productive, even as you remain vigilant.

Zero Trust using Azure AD Conditional Access

Azure AD offers the much needed strong, adaptive, standard-based identity verification required in zero trust framework. It provides intrinsically strong authentication (including automatic adaptive protection against many attacks) along with the permission for admins to express their access requirements in simple terms. A framework of controls like additional authentication factors, terms of use, limited access, and the other session semantics are available to guarantee that "we are secure at access" in our zero trust approach.

Zero Trust Networking

All the organizations contains their particular network security characterized by the following:
  • Few network security perimeters and open, flat networks.
  • Minimal threat protection and static traffic filtering.
  • Unencrypted internal traffic. 

If you want to implement an end-to-end zero trust framework for securing networks, you should firstly focus on the following initial deployment objectives:

I. Networking segmentation- Many ingress/egress cloud micro-perimeters with some micro-segmentation.
II. Threat protection- Cloud native filtering and protection for known threats.
III. Encryption- User-to-app internal traffic is encrypted. 

After successfully completing all these steps, you can also focus on the following additional deployment objectives:

IV. Network segmentation- Fully distributed ingress/egress cloud micro-perimeters and deeper micro-perimeters and deeper micro-segmentation.
V. Threat protection- Machine learning-based threat protection and filtering with context-based signals.
VI. Encryption- All traffic is encrypted.














Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more