Auditing - Ensure Mailbox Auditing For All Users Is Enabled

By Ashwin Venugopal -

 








Summary

Enabling mailbox auditing will help the Microsoft 365 back office teams in tracking logons to a mailbox as well as the actions taken while the user is logged on. When the mailbox audit logging is turned on for a mailbox, it will allow to search the audit log for mailbox activity, along with the additional actions performed by administrators, delegates, and owners logged by default.

Reason

By default, Microsoft has turned on mailbox audit logging since January, 2019, for all organizations, which means that certain actions performed by mailbox owners, delegates, and admins are automatically logged, and the corresponding mailbox audit records will be available for search in the mailbox audit log. Also after turning on this setting, the AuditEnabled property for affected mailboxes won't be changed from False to True; i.e., it ignores the AuditEnabled property on mailboxes. However, only certain mailbox types support default auditing On
  • User Mailboxes
  • Shared Mailboxes
  • Microsoft 365 Group Mailboxes

However, the remaining mailbox types require auditing be turned on at the mailbox level-
  • Resource Mailboxes
  • Public Folder Mailboxes
  • DiscoverySearch Mailboxes                                                                                                             
Whether it is for regulatory compliance or for tracking unauthorized configuration changes in Microsoft 365, enabling mailbox auditing allows for Microsoft 365 back office teams to run security operations, forensics or general investigations on mailbox activities.

Note- Without advanced auditing (E5 function) the logs are limited to 90 days.                                                                                                                                                       

 How to?

To enable mailbox auditing for all users, use the Exchange Online PowerShell Module:
  1. Run Microsoft Exchange Online PowerShell Module.
  2. Connect using Connect-ExchangeOnline.
  3. Run the following PowerShell commands-
$AuditAdmin = @ ("Copy", "Create", "FolderBind", "HardDelete", "MessageBind", "Move", "MoveToDeletedItems", "SendAs", "SendOnBehalf", "SoftDelete", "Update", "UpdateCalendarDelegation", "UpdateFolderPermissions", "UpdateInboxRules")

$AuditDelegate =
@ ("Create", "FolderBind", "HardDelete", "Move", "MoveToDeletedItems", "SendAs", "SendOnBehalf", "SoftDelete", "Update", " UpdateFolderPermissions", "UpdateInboxRules")

$AdminOwner =
@ ("Create", "HardDelete", "MailBoxLogin", "Move", "MoveToDeletedItems", "SoftDelete", "Update", "UpdateCalendarDelegation", "UpdateFolderPermissions", "UpdateInboxRules")

Get-Mailbox -ResultSize Unlimited | Set-Mailbox -AuditEnabled $true - AuditLogAgeLimit 180 -AuditAdmin $AuditAdmin -AuditDelegate $AuditDelegate -AuditOwner $AuditOwner

Monitor:

To verify mailbox auditing is enabled by default, use the Exchange Online PowerShell Module:
  1. Run Microsoft Exchange Online PowerShell Module.
  2. Connect using Connect-ExchangeOnline.
  3. Run the following PowerShell commands-

Get-OrganizationConfig | Format-List AuditDisabled

      4. Verify AuditDisabled is set to False.

To verify mailbox auditing is enabled for all mailboxes that do not support default auditing, use the Exchange Online PowerShell Module:
  1. Run Microsoft Exchange Online PowerShell Module.
  2. Connect using Connect-ExchangeOnline.
  3. Run the following PowerShell commands-

    Get-Mailbox -ResultSize Unlimited | Where-Object {$_.AuditEnabled -ne $true - and ($_.RecipientTypeDetails -ne "Usermailbox" -or $_.RecipientTypeDetails -ne "SharedMailbox")}
Alternatively, you can also run this command-

  Get-Mailbox | Where AuditEnabled -Match 'False' | select UserPrincipalName, auditenabled

      3. Verify AuditEnabled  is set to True for all mailboxes that are not a user, shared, or group mailbox.


































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