Manage Device Access (part 1)

By Ashwin Venugopal -

 


To read part 2, please click here





Plan for Device Compliance

Device Compliance policies can define the rules and settings required to be configured on a device so that it can be considered compliant allowing you to monitor device compliance status as well as individual devices that are configured in an expected way. However, the device must be enrolled to Intune before applying for compliance policy which will help the device to be automatically added to a device group so that its compliance status can be automatically reported to Intune and shown in the portal.

Some of the commonly used device compliance settings are:

  1. Required password to access devices
  2. Local data encryption 
  3. Whether the device is jail-broken or rooted
  4. Minimum OS version required 
  5. Maximum OS version allowed
  6. Required the device to be at, or under the Mobile Threat Defense level

If you want to implement device compliance policies, you must satisfy the following prerequisites:

  • It must be licensed for Azure AD Premium P1 or Azure AD Premium P2 and Intune. Both of them are part of Microsoft 365 or Enterprise Mobility + Security, but they can also be obtained separately.

  • Its devices must run one of the given supported platforms- Android, Android Enterprise, iOS, macOS, Windows Phone 8.1, Windows 8.1 and later, Windows 10.

  • Its devices must be enrolled in Intune to be eligible for compliance management.  

Following are the two types of non-compliant actions:

  • Notify end users through email-  Everything in an email notification can be customized like recipients, subject, message body along with the company logo as well as contact information  before sending it to the end user. Intune includes details about the noncompliant device in the email notification. 

  • Mark device noncompliant- You can either specify the number of days immediately after which the device can be flagged as noncompliant or you can simply grant the user a grace period in which he or she can update the device to make it compliant. However, if the device is still not compliant after the specified number of days, then, it will be marked as noncompliant.  

Device compliance policies can be used as follows:

  • With conditional access- The devices that comply with the policy rules, can be allowed access to the email and other company resources, but if it doesn't, then they aren't allowed any access to the company resources. 

  • Without conditional access- The device compliance policies can also be used without any conditional access providing restrictions free access to the company resources. 

If compliance policies are used independently, then, the targeted devices are evaluated and reported with their compliance status. However, the compliance status can also be reported regardless of any primary user or enrollment by device enrollment manager.

Configure Conditional Users & Groups

A built-in Mobile Device Management (MDM) agent automatically begins to sync the device details to Intune after the device's successful enrollment to it which includes information like:
  1. Name of device
  2. Operating system
  3. Total and free storage space
  4. Enrolled date
  5. Encrypted
  6. Compliance

The information can be easily viewed on the Intune blade in the Azure portal or while generating reports. 

The user and device groups can be created with the help of static as well as dynamic membership in Azure AD. A group can be created in azure AD with dynamic membership by specifying a rule to determine membership based on user or device properties. If all the attributes of a user or device changes, Azure AD evaluates all dynamic groups in a directory to check if the change would trigger any group adds or removes. If a user or device satisfies a rule on a group, then, they are added as the member of that group and vice versa. 

A group membership rule can automatically populate a group with users or devices which is a binary expression resulting in a true or false outcome. The three parts of a simple group membership rule are as follows:

  • Specifies the object attribute; for example, you can use user.department to reference the Department attribute of a user object, or device.displayName to reference the displayName attribute of a device object. 

  • Can be one of many supported operators, like as Equals (-eq), Starts With (-startsWith), Contains (-contains), or Match (-match). 

  • The value against which you want to evaluate the property by using the operator. 











To read part 2, 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