Email Security/Exchange Online - Ensure That an Anti-Phishing Policy Has Been Created

By Ashwin Venugopal -

 






Summary

Office 365 generally includes all the built-in features that can help in protecting the users from phishing attacks, by default. However, Anti-Phishing Policies can also be set up in order to increase the protection level, for example, by refining settings to better detect as well as prevent impersonation and spoofing attacks. The default policy will apply to all users within an organization, and is a single view where you can fine-tune anti-phishing protection. Custom policies can be created and configured for specific users, groups or domains within the organization and will take precedence over the default policy for the scoped users.

Reason

This policy can protect the users from phishing attacks (like impersonation and spoofing), while also using safety tips simultaneously, to warn the users about the potentiality of harmful messages.

What If?

Turning on Anti-Phishing policy, does not cause any impact, the messages can be displayed when applicable.

How to?

To set the Anti-Phishing policy, use the Microsoft 365 Admin Center:
  1. Select Security in order to open the Microsoft 365 Defender portal. 
  2. Under E-mail & Collaboration navigate to Policies & rules > Threat policies.
  3. Now, pick Anti-phishing.
  4. Click Create to make an anti-phishing policy.

To create an Anti-Phishing policy, use the Exchange Online PowerShell Module:
  1. Connect to Exchange Online using Connect-ExchangeOnline.
  2. Now, run the following Exchange Online PowerShell command: 

    3. New-AntiPhishPolicy -Name "Office365 AntiPhish Policy"

Monitor:

To review the Anti-Phishing policy, use the Microsoft 365 Admin Center:
  1. Select Security in order to open the Security portal.
  2. Under E-mail & Collaboration navigate to Policies & rules > Threat policies.
  3. Now, pick Anti-phishing.
  4. After that, verify the Office365 AntiPhish Default (Default) policy exists.

To verify Anti-Phishing policy, use the Exchange Online PowerShell Module:
  1. Connect to Exchange Online using Connect-ExchangeOnline.
  2. Now, run the following Exchange Online PowerShell command: 

    3. Get-AntiPhishPolicy | ft Name.

      3. Verify Office365 AntiPhish Default  policy exists.




























































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