Manage Insider Risk in Microsoft 365 (part 2)

By Ashwin Venugopal -

 


To read part 1 please click here


Assign Permissions

A global administrator will always need to assign you and other compliance officers to the Insider Risk Management or Insider Risk Management Admin role group by using the Permissions module in the Microsoft 365 compliance center and once assigned to one of these roles, you will have the ability to assign additional users to the specific role groups to manage different sets of insider risk management features.

You have the ability to choose from the following role group options when configuring insider risk management:

  • Insider Risk Management- You can use this role group to manage risk management for your organization in a single group. It contains all the insider risk management permission roles and is the easiest way to quickly get started with insider risk management as well as a good fit for organizations that do not need separate permissions defined for separate groups of the users.

  • Insider Risk Management Admin- You can use this role group initially configure insider risk management and later to segregate insider risk administrators into a defined group. The users in this role group can create, read, update, and delete insider risk management alerts, cases, as well as notice templates but cannot access the insider risk content explorer. 

  • Insider Risk Management Analysts- You can use this group to assign permissions to the users that will act as the insider risk data investigators. The users in this role group can access all the insider risk management alerts, cases, notices templates, and the Content Explorer for all the cases.  

Potential Dependencies

Two of the insider risk management templates have dependencies that must be configured for policy indicators to generate relevant activity alerts which might be optional depending on the policy you plan to configure for your organization. 

Departing employee data theft template

If you want to configure a policy using the Department employee data theft template, you'll need to configure a Microsoft 365 Human Resources (HR) data connector so that you can import user and log data from third party risk management as well as human resources platforms which helps you to alert drive alert indicators in insider risk management policies and is an important part of configuring full risk management coverage in your organization. The following requirements must be met before you can set up an HR connector:

  • A global administrator will need to consent to allow the Office 365 Import service to access data in your organization.
  • The user who creates the HR connector will need to be assigned the Mailbox Import Export role in Exchange Online. 
  • You have to have a system in place for retrieving and exporting the data from your organization's HR system as well as add it to a CSV file.   

Once all the requirements have been met, you can easily set up your HR connector.

Data leaks template

Insider Risk Management supports the DLP policies to help identify the intentional or accidental exposure of the sensitive information to the unwanted parties which help to drive the alert indicators for the sensitive information and is an important part of configuring full risk management coverage in your organization. 
Note- To reduce noise, alerts will only fire when a high volume DLP policy qualifying event is triggered. For example, an alert will fire if the policy detects 10 or more credit card numbers in an email or document, but not less. 

Creating a new insider risk policy

To create a new insider risk management policy, you can use the policy wizard in the Insider Risk Management solution present in the Microsoft 365 compliance center. You can also create a new policy briefly by stepping through the policy wizard and policy settings to configure the following items:

  • Policy template
  • Users or groups- the policy will apply to (optionally, assign higher risk scores to detected activity based on where the related content located, what sensitive info is included, and what sensitivity labels are applied). 
  • Alert indicators (Indicators need to be enabled under the Policy Settings before they can be selected when creating a policy).
  • Duration (time frame) for monitoring  



To read part 1 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 groups of computers, re
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 of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more