[Email Security] Learning path

src/content/docs/cloudflare-one/implementation-guides/secure-o365-email.mdx

@@ -0,0 +1,7 @@
+---
+pcx_content_type: navigation
+title: Secure Microsoft 365 email with Email Security
+external_link: /learning-paths/secure-o365-email/
+sidebar:
+  order: 4
+---

src/content/docs/learning-paths/secure-o365-email/concepts/index.mdx

@@ -0,0 +1,16 @@
+---
+title: Concepts
+pcx_content_type: overview
+sidebar:
+  order: 1
+---
+
+Review the concepts behind Cloudflare's Email Security.
+
+## Objectives
+
+By the end of this module, you will be able to:
+
+* Explain how Cloudflare works.
+* Describe what Email Security is. 
+* Understand how Cloudflare prevents email-based phishing attacks.

src/content/docs/learning-paths/secure-o365-email/concepts/prevent-phishing-attack.mdx

@@ -0,0 +1,20 @@
+---
+title: How Cloudflare prevents email-based phishing attacks
+pcx_content_type: overview
+sidebar:
+  order: 5
+---
+
+Cloudflare Email Security uses a variety of factors to determine whether a given email message attachment, URL, or specific network traffic is part of a phishing campaign.
+
+These small pattern assessments are dynamic in nature. Cloudflare's automated systems use a combination of factors to clearly distinguish between a valid phishing campaign and benign traffic.
+
+Cloudflare's vast global network detects emergent campaign infrastructure and aggregates data for Cloudflare's proprietary analytics engine SPARSE.
+
+SPARSE uses AI and ML models to make effective detections for all types of malicious emails, including Business Email Compromise (BEC). 
+
+In a BEC attack, the attacker falsifies an email message to trick the victim into performing some action - most often transferring money to an account or location the attacker controls. 
+
+To detect these low volume, malicious emails that do not contain malware, malicious links or email attachments, Cloudflare analyzes the email thread, content, sentiment and context via message lexical analysis, subject analysis and sender analysis. Display names are also compared with known executive names for similarity using several matching models. 
+
+Refer to [How we detect phish](/email-security/reference/how-we-detect-phish/#sample-attack-types-and-detections) to learn more about additional attack types and detections. 

src/content/docs/learning-paths/secure-o365-email/concepts/protect-from-phishing-attacks.mdx

@@ -0,0 +1,16 @@
+---
+title: Protect your organization from phishing attacks
+pcx_content_type: overview
+sidebar:
+  order: 6
+---
+
+In the early 2000s, Secure Email Gateways (SEGs) were introduced to deal with a growing need around the routing and filtering of email. While SEGs were successful at their mission for many years, their fundamental design has made it impossible for them to keep pace as phishing threats rapidly grow in scope and sophistication. 
+
+Continuously updating manual rulesets and policies that were originally built for on-prem servers only inflates the amount of time and effort involved in maintaining a SEG. This has resulted in an increase in cost and complexity while still falling short of catching the most dangerous threats, such as business email compromise (BEC) attacks.
+
+As organizations continue to adopt Microsoft 365 to enhance communication and collaboration for their hybrid workforce, it is crucial to take advantage of Microsoft's native security features while integrating complementary, machine learning-based solutions to automatically block and isolate the most dangerous threats. This strategy not only significantly reduces phishing risk, but also simplifies workflows, minimizing the time and effort needed for ongoing security management.
+
+Analysts agree that consolidating capabilities to minimize overlapping functionality is helping organizations reduce cost and complexity. However, they also advise organizations to carefully assess native features to ensure they satisfy all use cases. As Microsoft continues to build out its essential email security features, the growing overlap with SEGs has given organizations an opportunity to streamline security operations by leveraging capabilities already included in their E3 or E5 license. 
+
+This shift enables organizations to eliminate complex and costly SEG deployments, redirecting a fraction of that budget to integrate lightweight solutions that effectively address the most dangerous phishing threats. Cloudflare Email Security provides an integrated, low-touch solution that augments Microsoft 365 using machine learning threat analysis to automate the detection of BEC and multi-channel attacks.

src/content/docs/learning-paths/secure-o365-email/concepts/what-is-cloudflare.mdx

@@ -0,0 +1,10 @@
+---
+title: What is Cloudflare?
+pcx_content_type: overview
+sidebar:
+  order: 2
+---
+
+import { Render } from "~/components"
+
+<Render file="what-is-cloudflare" product="fundamentals" />

src/content/docs/learning-paths/secure-o365-email/concepts/what-is-email-security.mdx

@@ -0,0 +1,10 @@
+---
+title: What is Email Security?
+pcx_content_type: overview
+sidebar:
+  order: 4
+---
+
+Despite email's importance as a communication method, security and privacy were not built into the [The Simple Mail Transfer Protocol (SMTP) protocol](https://www.cloudflare.com/learning/email-security/what-is-smtp/). As a result, email is a major attack vector. 
+
+Email security is the process of preventing [email-based](https://www.cloudflare.com/learning/email-security/what-is-email/) cyber attacks and unwanted communications. It spans protecting inboxes from takeover, protecting domains from [spoofing](https://www.cloudflare.com/learning/ssl/what-is-domain-spoofing/), stopping [phishing attacks](https://www.cloudflare.com/learning/access-management/phishing-attack/), preventing fraud, blocking [malware](https://www.cloudflare.com/learning/ddos/glossary/malware/) delivery, and filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/). 

src/content/docs/learning-paths/secure-o365-email/concepts/what-is-phishing-attack.mdx

@@ -0,0 +1,12 @@
+---
+title: What is a phishing attack?
+pcx_content_type: overview
+sidebar:
+  order: 3
+---
+
+[Phishing](https://www.cloudflare.com/en-gb/learning/access-management/phishing-attack/) is an attempt to steal sensitive data, typically in the form of usernames, passwords, or other important account information. The phisher either uses the stolen information themselves (for instance, to take over the user's accounts with their password), or sells the stolen information.
+
+Phishing attackers disguise themselves as a reputable source. With an enticing or seemingly urgent request, an attacker lures the victim into providing information, just as a person uses bait while fishing.
+
+Phishing often takes place over email. Phishers either try to trick people into emailing information directly, or link to a webpage they control that is designed to look legitimate (for instance, a fake login page where the victim enters their password).

src/content/docs/learning-paths/secure-o365-email/configure-email-security/active-directory-sync.mdx

@@ -0,0 +1,38 @@
+---
+title: Manage your active directory
+pcx_content_type: how-to
+sidebar:
+  order: 2
+---
+
+Directories are folders to store user data. Email Security allows you to manage directories from the Cloudflare dashboard.
+
+To manage a Microsoft directory:
+
+1. Log in to [Zero Trust ](https://one.dash.cloudflare.com/).
+2. Select **Email security**.
+3. Select **Directories**.
+4. Under **Directory name**, select **MS directory**.
+5. From here, you can manage **Groups** or **Users** directories.
+
+Email Security allows you to view and manage your groups directory and their [impersonation registry](/cloudflare-one/email-security/detection-settings/impersonation-registry/). 
+When a group is added to the registry, all members are registered by default.
+
+To manage your group directory, on the **MS directory** page, select **Groups**.
+
+To add a single group to the registry:
+
+1. Select the group name you want to add.
+2. Select the three dots > **Add to registry**.
+
+To add multiple groups to the registry at once:
+
+1. Select the group names you want to add to the registry.
+2. Select the **Action** dropdown list.
+3. Select **Add to registry**.
+
+In addition, Email Security allows you to:
+
+- [Remove groups from the registry](/cloudflare-one/email-security/directories/manage-ms-directories/manage-groups-directory/#remove-groups-from-registry).
+- [Filter the impersonation registry](/cloudflare-one/email-security/directories/manage-ms-directories/manage-groups-directory/#filter-impersonation-registry).
+- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-ms-directories/manage-users-directory/).

src/content/docs/learning-paths/secure-o365-email/configure-email-security/audit-logs.mdx

@@ -0,0 +1,21 @@
+---
+title: Enable audit logs
+pcx_content_type: how-to
+sidebar:
+  order: 6
+---
+
+With Email Security, you can enable logs to review actions performed on your account.
+
+To enable audit logs:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
+2. Select **Analytics & Logs** > **Logpush**.
+3. Select **Audit logs**.
+4. Under **Configure logpush job**:
+  - **Job name**: Enter the job name.
+  - **If logs match**: Select Filtered logs:
+      - **Field**: Choose `ResourceType`.
+      - **Operator**: Choose `starts with`.
+      - **Value**: Enter `email_security`.
+5. Select **Submit**.

src/content/docs/learning-paths/secure-o365-email/configure-email-security/create-allow-policies.mdx

@@ -0,0 +1,39 @@
+---
+title: Create allow policies
+pcx_content_type: how-to
+sidebar:
+  order: 3
+---
+
+Email Security allows you to configure allow policies. An allow policy exempts messages that match certain patterns from normal detection scanning. 
+
+You can choose how Email Security will handle messages that match your criteria:
+
+- **Trusted Sender**: Messages will bypass all [detections](/cloudflare-one/email-security/reference/dispositions-and-attributes/) and link following. Typically, it only applies to phishing simulations from vendors such as KnowBe4. Many emails contain links in them. Some of these could be links to surveys, phishing simulations and other trackable links. By marking a message as a Trusted Sender, Email Security will not scan any attachments from the sender and will not attempt to open the links in the emails. 
+- **Exempt Recipient**: Messages will be exempt from all Email Security [detections](/cloudflare-one/email-security/reference/dispositions-and-attributes/) intended for recipients matching this pattern (email address or regular expression only). Typically, this only applies to submission mailboxes for user reporting to security.
+- **Accept Sender**: Messages will exempt messages from the `SPAM`, `SPOOF`, and `BULK` [dispositions](/cloudflare-one/email-security/reference/dispositions-and-attributes/) (but not `MALICIOUS` or `SUSPICIOUS`). Commonly used for external domains and sources that send mail on behalf of your organization, such as marketing emails or internal tools.
+
+## Configure allow policies
+
+To configure allow policies:
+
+1. Log in to [Zero Trust](https://one.dash.cloudflare.com/).
+2. Select **Email Security**.
+3. Select **Settings**, then go to **Detection settings** > **Allow policies**.
+4. On the **Detection settings** page, select **Add a policy**.
+5. On the **Add an allow policy** page, enter the policy information:
+    - **Input method**: Choose between **Manual input**, and **Uploading an allow policy**:
+        - **Manual input**:
+            - **Action**: Select one of the following to choose how Email Security will handle messages that match your criteria:
+                - **Trust sender**: Messages will bypass all detections and link following.
+                - **Exempt recipient**: Message to this recipient will bypass all detections.
+                - **Accept sender**: Messages from this sender will be exempted from Spam, Spoof, and Bulk dispositions.
+        - **Rule type**: Specify the scope of your policy. Choose one of the following:
+            - **Email addresses**: Must be a valid email.
+            - **IP addresses**: Can only be IPv4. IPv6 and CIDR are invalid entries.
+            - **Domains**: Must be a valid domain.
+            - **Regular expressions**: Must be valid Java expressions. Regular expressions are matched with fields related to the sender email address (envelope from, header from, reply-to), the originating IP address, and the server name for the email.
+        - **(Recommended) Sender verification**: This option enforces DMARC, SPF, or DKIM authentication. If you choose to enable this option, Email Security will only honor policies that pass authentication.
+            - **Notes**: Provide additional information about your allow policy.
+    - **Uploading an allow policy**: Upload a file no larger than 150 KB. The file can only contain `Pattern`, `Notes`, `Verify Email`, `Trusted Sender`, `Exempt Recipient`, and `Acceptable Sender` fields. The first row must be a header row.
+6. Select **Save**.

src/content/docs/learning-paths/secure-o365-email/configure-email-security/impersonation-registry.mdx

@@ -0,0 +1,30 @@
+---
+title: Add user to the impersonation registry
+pcx_content_type: how-to
+sidebar:
+  order: 3
+---
+
+Attackers often try to impersonate executives within an organization when sending malicious emails (with requests about banking information, trade secrets, and more), which is known as a [Business Email Compromise (BEC)](https://www.cloudflare.com/en-gb/learning/email-security/business-email-compromise-bec/) attack.
+
+The impersonation registry protects against these attacks by looking for spoofs of known key users in an organization. Information about key users you either synced with your directory or entered manually in the dashboard is used by Email Security to run enhanced scan techniques and find these spoofed emails.
+
+To add a user to the impersonation registry:
+
+1. Log in to [Zero Trust](https://one.dash.cloudflare.com/).
+2. Select **Email Security**.
+3. Select **Settings** > **Impersonation registry**.
+4. Select **Add a user**.
+5. Select **Input method**: Choose between **Manual input**, **Upload manual list**, and **Select from existing directories**:
+    - **Manual input**: Enter the following information:
+        - **User info**: enter a valid **Display name**.
+        - **User email**: Enter one of the following:
+            - **Email address**: Enter all known email addresses, separated by a comma.
+            - **Regular expressions**: Must be valid Java expressions.
+    - **Upload manual list**: You can upload a file no larger than 150 KB containing all variables of potential emails. The file must contain `Display_Name` and `Email`, and the first row must be the header row.
+    - **Select from existing directories**:
+        - **Select directory**: Select your directory.
+        - **Add users or groups**: Choose the users or groups you want to register.
+6. Select **Save**.
+
+For more information on how to edit and remove users, refer to [Impersonation Registry](/cloudflare-one/email-security/detection-settings/impersonation-registry/#edit-users). 

src/content/docs/learning-paths/secure-o365-email/configure-email-security/index.mdx

@@ -0,0 +1,10 @@
+---
+title: Configure Email Security
+pcx_content_type: overview
+sidebar:
+  order: 3
+---
+
+With Email Security, there is limited manual configuration and tuning. The Active Directory sync, allow policies, and additional detections are important to consider when you set up Email Security. 
+
+In this module, you will configure your email environment.

src/content/docs/learning-paths/secure-o365-email/configure-email-security/report-phish.mdx

@@ -0,0 +1,21 @@
+---
+title: Report phish
+pcx_content_type: how-to
+sidebar:
+  order: 5
+---
+
+Before deploying Email Security to production, you will have to consider reporting any phishing attacks, evaluating which disposition to assign a specific message, and using different screen criteria to search through your inbox.
+
+PhishNet is an add-in button that helps users to submit phish samples missed by Email Security detection. 
+
+To set up PhishNet O365:
+
+1. Log in to the Microsoft admin panel. Go to **Microsoft 365 admin center** > **Settings** > **Integrated Apps**.
+2. Select **Upload custom apps**.
+3. Choose **Provide link to manifest file** and paste the the following URL:
+
+```txt
+https://phishnet-o365.area1cloudflare-webapps.workers.dev?clientId=ODcxNDA0MjMyNDM3NTA4NjQwNDk1Mzc3MDIxNzE0OTcxNTg0Njk5NDEyOTE2NDU5ODQyNjU5NzYzNjYyNDQ3NjEwMzIxODEyMDk1NQ
+```
+4. Verify and complete the wizard.

src/content/docs/learning-paths/secure-o365-email/configure-email-security/set-additional-detections.mdx

@@ -0,0 +1,61 @@
+---
+title: Set additional detections
+pcx_content_type: how-to
+sidebar:
+  order: 4
+---
+
+Email Security allows you to configure the following additional detections:
+
+- [Domain age](/cloudflare-one/email-security/detection-settings/additional-detections/#configure-domain-age)
+- [Blank email detection](/cloudflare-one/email-security/detection-settings/additional-detections/#configure-blank-email-detection)
+- [Automated Clearing House (ACH)](/cloudflare-one/email-security/detection-settings/additional-detections/#configure-ach-change-from-free-email-detection) change from free email detection.
+- [HTML attachment email detection](/cloudflare-one/email-security/detection-settings/additional-detections/#configure-html-attachment-email-detection)
+
+To configure additional detections:
+
+1. Log in to [Zero Trust](https://one.dash.cloudflare.com/).
+2. Select **Email Security**.
+3. Select **Settings**.
+4. On the Settings page, go to **Detection settings** > **Additional detections**, and select **Edit**.
+
+## Configure domain age
+
+The domain age is the time since the domain has been registered.
+
+To configure a domain age:
+
+1. On the **Edit additional detections** page:
+    - Select **Malicious domain age**: Controls the threshold for a malicious disposition. Maximum of 100 days.
+    - Select **Suspicious domain age**: Controls the threshold for a suspicious disposition. Maximum of 100 days.
+2. Select **Save**.
+
+## Configure blank email detection
+
+Blank email detection detects emails with blank bodies and assigns a default disposition. You can choose between **Malicious** and **Suspicious** as dispositions.
+
+To enable blank email detection:
+
+1. On the **Edit additional detections** page, enable **Blank email detection**.
+2. Choose between **Malicious** and **Suspicious**.
+3. Select **Save**.
+
+## Configure ACH change from free email detection
+
+[Automated Clearing House (ACH)](https://en.wikipedia.org/wiki/Automated_clearing_house) is a banking term related to direct deposits. ACH change from free email detection detects payroll inquiries or change requests from free email domains and assigns a default disposition. You can choose between **Malicious** and **Suspicious** as dispositions.
+
+To enable ACH change from free email detection:
+
+1. On the **Edit additional detections** page, enable **ACH change from free email detection**.
+2. Choose between **Malicious** and **Suspicious**.
+3. Select **Save**.
+
+## Configure HTML Attachment Email Detection
+
+HTML attachment email detection detects HTM and HTML attachments in emails and assigns a default disposition.
+
+To enable HTML attachment email detection:
+
+1. On the **Edit additional detections** page, enable **HTML attachment email detection**.
+2. Choose between **Malicious** and **Suspicious**.
+3. Select **Save**.

src/content/docs/learning-paths/secure-o365-email/enable-auto-moves/configure-auto-moves.mdx

@@ -0,0 +1,24 @@
+---
+title: Configure auto-moves
+pcx_content_type: how-to
+sidebar:
+  order: 3
+---
+
+To configure auto-move events:
+
+1. Log in to [Zero Trust](https://one.dash.cloudflare.com/).
+2. Select **Email security**.
+3. Select **Settings**.
+4. Select **Moves**.
+5. Under **Auto-moves**, select **Configure**.
+6. Assign actions based on malicious, spoof, suspicious, spam, and bulk dispositions. Select among:
+    - **Soft delete - user recoverable**: Moves the message to the user's **Recoverable Items - Deleted** folder. Messages can be recovered by the user.
+    - **Hard delete - admin recoverable**: Completely deletes messages from a user's inbox.
+    - **Move to trash**: Moves messages to the trash or deleted items email folder.
+    - **Move to junk**: Moves the message to the junk or spam folder.
+    - **No action**: Messages stay in the origin folder.
+7. Select **Post-delivery** moves:
+    - **(Recommended) Post-delivery response**: Enabling this option allows Email Security to rescan delivered emails at multiple time intervals for previously unknown phishing sites or campaigns.
+    - **(Recommended) Phish submission response**: Enabling this option allows Email Security to move emails that your users reported as phishing and Email Security determined to be malicious.
+8. Select **Save**.