Email Security/Exchange Online - Ensure That DKIM Is Enabled For All Exchange Online Domains

By Ashwin Venugopal -

 







Summary

DKIM should be used along with SPF and DMARC to prevent spoofers from sending messages that look like they are coming from your domain.

Reason

If DKIM is enabled with Office 365, then, the messages that are sent from Exchange Online will be cryptographically signed. This will allow the receiving email system to validate that the messages are generated by a server authorized by the organization and not being spoofed.

What If?

Although, setting up DKIM will not affect anything, but, the organizations must ensure appropriate setup to ensure continuous mail-flow.

How to?

To setup DKIM records, first add the records to the DNS system, for each domain in Exchange Online that you plan to use to send email with:
  1. After creating the DNS records, enable DKIM signing in the Office 365 Admin Portal.
  2. Launch the Security Admin Center.
  3. Under E-mail & Collaboration navigate to Policies & rules > Threat policies.
  4. Now, under Rules pick DKIM.
  5. After that, click on each domain and click Enable next to Sign messages for this domain with DKIM signature.

To verify DKIM 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: 

    3. Get-DkimSigningConfig

       3. Verify Enabled is set to True.

Monitor:

To review if DKIM is enabled, 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, under Rules pick DKIM.
  4. After that, click on each domain and confirm that Sign messages for this domain with DKIM signature is Enabled.

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...
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