Email Security/Exchange Online - Ensure Notifications For Internal Users Sending Malware Is Enabled

By Ashwin Venugopal -

 








Summary

Exchange Online Protection (EOP) is known as a cloud-based filtering service that protects an organization against spam, malware, and other email threats. It is present in all Microsoft 365 organizations with Exchange Online mailboxes.

EOP generally uses flexible anti-malware policies that can be easily set to notify Admins of malicious activity.

Reason

This setting can alert an administrator about an internal user sending contaminated messages indicating a compromised account or machine, that would require to be investigated.

Note- Audit and Remediation guidance may focus on the Default policy, but, if there is a custom policy in the organization's tenant, then, make sure that the setting is set as outlined in the highest priority policy list. 

What If?

Notification of account with potential issues should not cause an impact to the user.

How to?

To enable notifications for internal users sending malware, use the Microsoft 365 Admin Center:
  1. Click Security to open the Security portal.
  2. Under Email & Collaboration navigate to Policies & rules > Threat policies.
  3. Select Anti-malware.
  4. Pick Default policy.
  5. Now, click on Edit protection settings and change the settings for Notify an admin about undelivered messages from internal senders to On and enter the email address of the administrator who should be notified under Administrator email address.

To check the setting from PowerShell, use the Exchange Online PowerShell Module:
  1. Connect to Exchange Online using Connect-ExchangeOnline.
  2. Now, run the following Exchange Online PowerShell command: 

    Set-MalwareFilterPolicy -Identity ' (Identity Name) ' -
    EnableInternalSenderAdminNotifications $True -InternalSenderAdminAddress
    {admin@domainl.com}

Monitor:

To verify notifications for internal users sending malware is enabled, use the Microsoft 365 Admin Center:
  1. Click Security to open the Security portal.
  2. Under Email & Collaboration navigate to Policies & rules > Threat policies.
  3. Select Anti-malware.
  4. Click on Default policy.
  5. Now, ensure the setting for Notify an admin about undelivered messages from internal senders is set to On and that there is at least one email address under Administrator email address.

To check the setting from PowerShell, use the Exchange Online PowerShell Module:
  1. Connect to Exchange Online using Connect-ExchangeOnline.
  2. Now, run the following Exchange Online PowerShell command: 

    Get-MalwareFilterPolicy | fl Identity,
    EnableInternalSenderAdminNotifications, InternalSenderAdminAddress























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