Auditing - Ensure Microsoft 365 Audit Log Search Is Enabled

By Ashwin Venugopal -

 








Summary

Enabling the audit log search in Microsoft Purview compliance will allow the recording of the user and admin activity of an organization, that can be retained for 90 days. However, if an organization is using a third-party Security Information and Event Management (SIEM) application to access the auditing data, then, a global admin can turn off audit log search in Microsoft 365.

Reason

This setting can help Office 365  back office teams to investigate activities for regular security operational or forensic purposes.

How to?

To enable Microsoft 365 audit log search, use the Microsoft 365 Admin Center:
  1. Log in as an administrator.
  2. Navigate to the Microsoft Purview compliance portal by going to https://compliance.office.com
  3. Under solutions, select Audit.
  4. Now, click on Start recording user and admin activity next to information warning at the top.
  5. Click Yes on the dialog box to confirm.

To enable Microsoft 365 audit log search via Exchange Online PowerShell:
  1. Connect to Exchange Online using Connect-ExchangeOnline.
  2. Now, run the following Exchange Online PowerShell command: 

    Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true

Monitor:

To verify audit log search is enabled, use the Microsoft 365 Admin Center:
  1. Log in as an administrator.
  2. Navigate to the Microsoft Purview compliance portal by going to https://compliance.office.com
  3. Under solutions, select Audit and then pick an applicable time frame
  4. Now, verify that you are able to do searches (e.g. try searching for Activities as Access file and results should be displayed).

To verify audit log search is enabled, use the Exchange Online PowerShell Module:
  1. Connect to Exchange Online using Connect-ExchangeOnline.
  2. Now, run the following Exchange Online PowerShell command: 

    Get-AdminAuditLogConfig | FL UnifiedAuditLogIngestionEnabled 
      3. Verify the resulting value is UnifiedAuditLogIngestionEnabled : True.

































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