Identity Governance (part 2 of 6)

By Ashwin Venugopal -

 



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
To read part 6, please click here





Conditional Access Explained

Nowadays, users can easily access your organization's resources with the help of various devices and apps from anywhere making it insufficient to simply focus on who can access your resource. Hence, Azure AD Conditional Access allows you to master the balance between productivity and productivity as well as the factor how a resource is accessed into an access control decision. It also helps you to implement automated access control decisions for accessing your cloud apps that are based on various conditions.

Common Scenarios

Conditional access policies allows you to apply right access controls under the required conditions while also providing you with extra security when needed and vice versa. It can easily help you with the following:

  • Sign-in risk- Azure AD Identity Protection detects sign-in risks. How do you restrict access if a detected sign-in risk indicates a bad actor? What if you would like to get stronger evidence that sign-in was performed by the legitimate user? What if your doubts are strong enough to even block specific users from accessing an app?

  • Network location- Azure AD can be accessed from anywhere. What if an access attempt is performed from a location that's not controlled by your IT department? A combination of username and password may be enough as a proof of identity for access attempts from your corporate network, but what if you want a stronger proof of identity for access attempts that are initiated from other unexpected countries or regions of the world or if you want to block them from certain locations?

  • Device management- In Azure AD, users can easily access cloud apps from a broad range of devices including mobile as well as personal devices. What if you want the access attempts should only be performed by the devices that are managed by your IT department or you want to block certain types of devices from accessing your cloud apps in your environment?

  • Client application- Nowadays, you can easily access multiple cloud apps with the help of different app types like web-based apps, mobile apps, or desktop apps. What if an access attempt is performed using a client app type that causes known issues? What if you require a device that is managed by your IT department for certain app types?

Conditional Access Policies

It is a definition of an access scenario using the following pattern:

When this happens

Then do this

 

Then do this represents the response of your policy. Conditional Access policy allows you to control how authorized users can access cloud apps under specific conditions while you can respond by enforcing additional requirements like multi-factor authentication, a managed device, and others; these requirements are known as access controls. 

When this happens determines the reason for triggering your policy which can be characterized by a group of conditions that have been satisfied. However, the following two mandatory assignment conditions play a special role in Azure AD Conditional Access:

  1. Users- The users performing an access attempt (Who).
  2. Cloud apps- The targets of an access attempt (What).

You can also include additional conditions that can describe how the access attempt is performed. The main objective of a conditional access policy is to enforce additional access controls on an access attempt to a cloud app based on how an access attempt is performed. 

A policy-based approach to protect access to your cloud apps enables you to start drafting the policy requirements for your environment with the help of the given structure without worrying about the technical implementation. 











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
To read part 6, please click here










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

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

Threat Hunting in Microsoft Sentinel (part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Introducing the Microsoft Sentinel Hunting Page Threat hunting is a series activities performed while investigating and as there are no guidelines to perform it, the available tools on the Microsoft Sentinel can be introduced to perform better in your investigations. Firstly, you have to choose the Hunting link in the Microsoft Sentinel navigation menu to get to the Hunting page which is divided into the following sections: The header bar- It is located at the top of the page as usual and contains Refresh as well as timespan drop down menu. The New Query button can help you with creating a new query and the Run all queries button can run all the hunting queries in the background while also updating the hunting query list section with the number of results found.  The summary bar- Here, you can view the total number of queries available to run, the total number of bookmarks, the number of results from running live
Read more