[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 your Microsoft 365 email environment 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,38 @@
+---
+title: How Cloudflare prevents email-based phishing attacks
+pcx_content_type: overview
+sidebar:
+  order: 4
+---
+
+Email-based phishing attacks can be divided into two main categories: Those with and without a malicious URL or attachment.
+
+Email Security uses a variety of factors to determine whether a given email message, a web domain or URL, or specific network traffic is part of a phishing campaign (marked with a `Malicious` [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#dispositions)) or other common campaigns (for example, `Spam`).
+
+These small pattern assessments are dynamic in nature and — in many cases — no single one in and of itself will determine the final verdict. Instead, our automated systems use a combination of factors and non-factors to clearly distinguish between a valid phishing campaign and benign traffic.
+
+Emails without a Malicious URL or attachment typically fall into the Business Email Compromise (BEC) category. BEC is a type of social engineering attack. 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 uses machine learning analysis, analyzing email threads, content, sentiment and context via message lexical analysis, subject analysis, word count assessment and sender analysis. Display names are also compared with known executive names for similarity using several matching modeling including the [Levenshtein Algorithm](https://en.wikipedia.org/wiki/Levenshtein_distance), and if matched, lagged when a sender is organization from an unknown domain.
+
+## Type of malicious attacks
+
+When malicious payloads or URLs are included or attached to an email, additional steps are taken to protect your users. For example:
+
+- **Attack type**:  Malicious payload attached to the message.
+- **Example**: Classic campaign technique which utilizes a variety of active attachment types (EXE, DOC, XLS, PPT, OLE, PDF, and more) as the malicious payload for ransomware attacks, Trojans, viruses, and malware.
+- **Detections applied**: Machine learning (ML) models on binary bitmaps of the payload as well as higher-level attributes of the payload, with specific focus on signatureless detections for maximum coverage. Additionally, for relevant active payloads, the engine invokes a real-time sandbox to assess behavior and determine maliciousness.
+
+- **Attack type**: Encrypted malicious payload attached to the message, with password in message body as text.
+- **Example**: Campaigns that induce the user to apply a password within the message body to the attachment.
+- **Detections applied**: Real-time lexical parsing of message body for password extraction and ML models on binary bitmaps of the payload, signatureless detections for maximum coverage.
+
+- **Attack type**: Malicious URLs within message body.
+- **Example**: Typical phish campaigns with a socially engineered call to action URL that will implant malware (for example, watering hole attacks, malvertising, or scripting attacks).
+- **Detections applied**: Continuous web crawling, followed by real-time link crawling for a select group of suspicious urls, followed by machine learning applied to URL patterns in combination with other pattern rules and topic-based machine learning models for exhaustive coverage of link-based attacks.
+
+- **Attack type**: Malicious payload linked through a Malicious payload linked through a URL in a messageURL in a message.
+- **Example**: Campaigns where the URL links through to a remote malicious attachment (for example, in a .doc or .pdf file).
+- **Detections applied**: Remote document and/or attachment extraction followed by ML detection tree on the payload, instant crawl of links.
+
+Additional attack types and detections can be found in the [Email Security Detection Methods](/cloudflare-one/email-security/reference/how-es-detects-phish/) documentation.

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

@@ -0,0 +1,10 @@
+---
+title: Protect your organization from phishing attacks
+pcx_content_type: overview
+sidebar:
+  order: 5
+---
+
+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 organization's 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,12 @@
+---
+title: What is Email Security?
+pcx_content_type: overview
+sidebar:
+  order: 3
+---
+
+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, stopping phishing attacks, preventing fraud, blocking malware delivery, filtering spam, and using encryption to protect the contents of emails from unauthorized persons.
+
+Security and privacy were not built into email when it was first invented, and despite email's importance as a communication method, these are still not built into email by default. As a result, email is a major attack vector for large and small organizations, and for individuals well.

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

@@ -0,0 +1,10 @@
+---
+title: What is a phishing attack?
+pcx_content_type: overview
+sidebar:
+  order: 2
+---
+
+Email security is the process of preventing [email](https://www.cloudflare.com/learning/email-security/what-is-email/)-based 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, filtering [spam](https://www.cloudflare.com/learning/email-security/how-to-stop-spam-emails/), and using [encryption](https://www.cloudflare.com/learning/ssl/what-is-encryption/) to protect the contents of emails from unauthorized persons.*
+
+Security and [privacy](https://www.cloudflare.com/learning/privacy/what-is-data-privacy/) were not built into email when it was first invented, and despite email's importance as a communication method, these are still not built into email by default. As a result, email is a major [attack vector](https://www.cloudflare.com/learning/security/glossary/attack-vector/) for large and small organizations, and for individuals well.*

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

@@ -0,0 +1,38 @@
+---
+title: Active directory sync
+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](https://developers.cloudflare.com/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/email-security-configuration/create-allow-policies.mdx

@@ -0,0 +1,39 @@
+---
+title: Create allow policies
+pcx_content_type: how-to
+sidebar:
+  order: 4
+---
+
+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 by Email Security. Typically, it only applies to phishing simulations from vendors such as KnowBe4.
+- **Exempt Recipient**: Will exempt messages 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.
+- **Acceptable Sender**: 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/email-security-configuration/impersonation-registry.mdx

@@ -0,0 +1,30 @@
+---
+title: 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) attack .
+
+This feature 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/email-security-configuration/index.mdx

@@ -0,0 +1,8 @@
+---
+title: Initial Email Security Configuration
+pcx_content_type: overview
+sidebar:
+  order: 1
+---
+
+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 the tool. 

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

@@ -0,0 +1,61 @@
+---
+title: Set additional detections
+pcx_content_type: how-to
+sidebar:
+  order: 5
+---
+
+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**.