Threat Protection (part 2)

By Ashwin Venugopal -

 





To read part 1, please click here 




Zero-Hour Auto Purge (ZAP)

It's an email protection feature present in Microsoft 365 that can retroactively detect as well as neutralize malicious phishing, spam, or malware messages that have already been delivered to Exchange Online mailboxes. 

By default, ZAP is available with the default Exchange Online Protection (EOP) that's included with any Office 365 subscription containing Exchange Online mailboxes. It doesn't work in standalone EOP environments that protect on-premises Exchange mailboxes.

How ZAP works?

Although Microsoft Office 365 updates spam as well as malware signatures on daily basis, users can still receive malicious messages due to various reasons, including if content is weaponized after being delivered to users. ZAP  readily addresses this issue by regularly monitoring the updates to the Office 365 spam and malware signatures and finding as well as removing the messages that are already in a user's mailbox.

As ZAP's action is seamless for the user, they aren't notified if a message is detected and moved. Safe sender lists, mail flow rules (also called transport rules), Inbox rules, or additional filters take precedence over ZAP.

Malware ZAP

If you want to read or unread messages that are identified as containing malware after delivery, ZAP quarantines the message containing the malware attachments and only admins can view as well as manage malware messages from isolation. 

Malware ZAP is enabled by default in anti-malware policies. 

Phish ZAP

The ZAP outcome depends on the action that's configured for a Phishing email filtering verdict in the applicable anti-spam policy for the read or unread messages that are identified as phish after delivery. The available filtering verdict actions for phish and their possible ZAP outcomes are as follows:
  • Add X-Header, Prepend subject line with text- ZAP takes no action on the message.

  • Move message to Junk Email- ZAP moves the message to the Junk Email folder, as long as the junk email rule is enabled on the mailbox (it's enabled by default).

  • Redirect message to email address, Delete message, Quarantine message- ZAP quarantines the message and only admins can view as well as phish quarantined messages. 

By default, Phish ZAP is enabled in anti-spam policies, and the default action for the Phishing email filtering verdict is Quarantine message i.e. phish ZAP quarantines the message by default. 

Spam ZAP

The ZAP outcome always depends on the action that's configured for the Spam filtering verdict in the applicable anti-spam policy for the unread messages that are recognized as spam after delivery. The filtering verdict actions for spam and their possible ZAP outcomes are as follows:
  • Add X-Header, Prepend subject line with text- ZAP takes no action on the message.

  • Move message to Junk Email- ZAP moves the message to the Junk Email folder, as long as the junk email rule is enabled on the mailbox (it's enabled by default).

  • Redirect message to email address, Delete message, Quarantine message- ZAP quarantines the message and only end-users can view as well as manage their own spam quarantined messages. 

By default, spam ZAP is enabled in anti-spam policies, and the default action for Spam filtering verdict is Move message to Junk Email folder i.e. spam ZAP moves unread messages to Junk Email folder by default.  

How to see if ZAP moved a message?

If you want to know that whether ZAP moved your message or not, then, you can use either the Threat Protection Status report or Threat Explorer (and real-time detections). Note that as a system action, ZAP is not logged in the Exchange mailbox audit logs. 










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

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