[Email Security] Learning path

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,36 @@
+---
+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.
+
+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 [here](/cloudflare-one/email-security/reference/how-es-detects-phish/).

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,9 @@
+---
+title: What is a 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/get-started/create-email-security-account.mdx

@@ -0,0 +1,17 @@
+---
+title: Create an Email Security account
+pcx_content_type: overview
+sidebar:
+  order: 3
+---
+
+To create your Email Security account, you will need the alphanumeric string on the URL when logged in to the Cloudflare dashboard.
+
+If you do not have a Cloudflare account, you can create one for free, [here](https://dash.cloudflare.com/sign-up).
+
+From there, your account team will create an Email Security account for you. To establish your tenant, you will need the following information:
+
+- *Average Monthly Inbound Message Volume*
+- *Number of Active Email Users*
+- *Domain(s)*
+- *Admin Email Address *

src/content/docs/learning-paths/secure-o365-email/get-started/deployment-models.mdx

@@ -0,0 +1,11 @@
+---
+title: Deployment models
+pcx_content_type: overview
+sidebar:
+  order: 5
+---
+
+While there are multiple deployment methods, the easiest way to get started with Email Security is via the API deployment method.
+
+When you choose the [API deployment](/cloudflare-one/email-security/setup/post-delivery-deployment/api/), Email Security can both scan and take actions on emails after they have reached a user's inbox. 
+With a [Journaling setup](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/office365-journaling/) alone without API integration, Email Security can only scan emails after it has reached a user's inbox.

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

@@ -0,0 +1,12 @@
+---
+title: Get started with Email Security
+pcx_content_type: overview
+sidebar:
+  order: 1
+---
+
+In this learning path, you will learn how to protect your organization from phishing attacks with Email Security. 
+Your users will experience a reduction in spam and phishing emails and have simple ways to report any suspicious activity. 
+Administrators will be able to review detections and phishing trends that target their organization without having to tune Email Security. 
+
+[Microsoft O365 API deployment diagram](/assets/images/email-security/deployment/api-setup/ms365-api-deployment.png)

src/content/docs/learning-paths/secure-o365-email/get-started/initial-login.mdx

@@ -0,0 +1,8 @@
+---
+title: Initial login
+pcx_content_type: overview
+sidebar:
+  order: 4
+---
+
+{/* DOUBLE CHECK INFO ON LEARNING PATH DRAFT */}

src/content/docs/learning-paths/secure-o365-email/get-started/prerequisites.mdx

@@ -0,0 +1,8 @@
+---
+title: Prerequisites
+pcx_content_type: overview
+sidebar:
+  order: 2
+---
+
+To make the most of this learning path, make sure that you have access to Microsoft 365. 

src/content/docs/learning-paths/secure-o365-email/get-started/recommended-deployment-model.mdx

@@ -0,0 +1,16 @@
+---
+title: Recommended deployment models
+pcx_content_type: overview
+sidebar:
+  order: 6
+---
+
+An API deployment model with Email Security has multiple benefits for Microsoft 365 Customers. 
+
+The API deployment with Email Security offers: 
+
+- Easy protection for complex email architectures, without requiring any change to mail flow operations.
+- Agentless deployment for Microsoft O365.
+- Office 365 directory integration  to retrieve user and group information and prevent user impersonation.
+
+[Api and journaling deployment diagram](/assets/images/email-security/deployment/api-setup/api-and-journaling-deployment.png)

src/content/learning-paths/secure-o365-email.json

@@ -0,0 +1,8 @@
+{
+	"title": "Secure Your Microsoft 365 Email Environment with Email Security",
+	"path": "/learning-paths/secure-o365-email/",
+	"priority": 2,
+	"description": "Use Cloudflare's Email Security to protect your Microsoft 365 email inbox.",
+	"products": ["Email Security"],
+	"product_group": "Cloudflare One"
+}