diff --git a/src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/area-1.mdx b/src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/area-1.mdx index 0e614b07018cd2..eb75cfc7bd200f 100644 --- a/src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/area-1.mdx +++ b/src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/area-1.mdx @@ -7,6 +7,10 @@ sidebar: --- +import { Render } from "~/components"; + + + [Cloudflare Area 1](https://www.cloudflare.com/products/zero-trust/email-security/) is an email security platform that protects your organization's inbox from phishing, spam, and other malicious messages. This guide covers how to configure Area 1 as a SAML application in Cloudflare Zero Trust. ## Prerequisites diff --git a/src/content/docs/email-security/account-setup/escalation-contacts.mdx b/src/content/docs/email-security/account-setup/escalation-contacts.mdx index 8bb19969f89644..9f7ffb5a66bd5d 100644 --- a/src/content/docs/email-security/account-setup/escalation-contacts.mdx +++ b/src/content/docs/email-security/account-setup/escalation-contacts.mdx @@ -8,11 +8,9 @@ sidebar: import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + Whenever Email Security (formerly Area 1) finds an exceptional phishing threat or Email Service irregularity behavior (compromised email servers at a partner or vendor, wire fraud tactics, and more), we try to reach out to our customers. diff --git a/src/content/docs/email-security/account-setup/manage-account-members.mdx b/src/content/docs/email-security/account-setup/manage-account-members.mdx index 4bafc0baed1809..e50e43a774e236 100644 --- a/src/content/docs/email-security/account-setup/manage-account-members.mdx +++ b/src/content/docs/email-security/account-setup/manage-account-members.mdx @@ -7,11 +7,9 @@ sidebar: import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + If your account is a **Super Admin**, you have the ability to add, edit, and delete users and - if those users lose their two-factor authentication (2FA) device - reset their 2FA. diff --git a/src/content/docs/email-security/account-setup/manage-parent-permissions.mdx b/src/content/docs/email-security/account-setup/manage-parent-permissions.mdx index 968727c87cb691..d0d71cd1a43363 100644 --- a/src/content/docs/email-security/account-setup/manage-parent-permissions.mdx +++ b/src/content/docs/email-security/account-setup/manage-parent-permissions.mdx @@ -7,11 +7,9 @@ sidebar: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + When you set up Email Security through a [partner](/email-security/partners/), that partner's account is the **parent** account to your **child** account. diff --git a/src/content/docs/email-security/account-setup/permissions.mdx b/src/content/docs/email-security/account-setup/permissions.mdx index 76a395bfb444bb..2f7bad6a2036dd 100644 --- a/src/content/docs/email-security/account-setup/permissions.mdx +++ b/src/content/docs/email-security/account-setup/permissions.mdx @@ -7,11 +7,9 @@ sidebar: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + When you [create a user](/email-security/account-setup/manage-account-members/#add-user), the available options for permissions depend on whether your account is a **parent** account or a **child** account. diff --git a/src/content/docs/email-security/account-setup/sso/index.mdx b/src/content/docs/email-security/account-setup/sso/index.mdx index 5c733aa3558359..77e5b3c1ef2d60 100644 --- a/src/content/docs/email-security/account-setup/sso/index.mdx +++ b/src/content/docs/email-security/account-setup/sso/index.mdx @@ -7,11 +7,9 @@ sidebar: import { DirectoryListing, GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + For added security and convenience, Email Security (formerly Area 1) offers support for Security Assertion Markup Language based (SAML-based) single sign-on (SSO) logins. Organizations are able to choose between having users access Email Security (formerly Area 1) with a username and password plus a two-factor authentication (2FA) code, or using an SSO provider, such as OneLogin or Okta. diff --git a/src/content/docs/email-security/api/index.mdx b/src/content/docs/email-security/api/index.mdx index 1bb13de5103569..082a9f49e0d867 100644 --- a/src/content/docs/email-security/api/index.mdx +++ b/src/content/docs/email-security/api/index.mdx @@ -7,11 +7,9 @@ sidebar: import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + Email Security offers Application Programming Interfaces (APIs) to expose our phishing campaign rulesets. These APIs both aid research and provide a set of indicators to block using network security edge devices. diff --git a/src/content/docs/email-security/deployment/api/index.mdx b/src/content/docs/email-security/deployment/api/index.mdx index ce8b55919a7c63..eefcd43cc25c3d 100644 --- a/src/content/docs/email-security/deployment/api/index.mdx +++ b/src/content/docs/email-security/deployment/api/index.mdx @@ -10,11 +10,9 @@ head: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + diff --git a/src/content/docs/email-security/deployment/api/setup/exchange-bcc-setup.mdx b/src/content/docs/email-security/deployment/api/setup/exchange-bcc-setup.mdx index 31f25d220493bd..b5b76da496d110 100644 --- a/src/content/docs/email-security/deployment/api/setup/exchange-bcc-setup.mdx +++ b/src/content/docs/email-security/deployment/api/setup/exchange-bcc-setup.mdx @@ -12,12 +12,8 @@ head: import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - For customers using Microsoft Exchange, setting up Email Security via BCC is quick and easy. You need to configure an inbound rule to send emails to Email Security via BCC for processing and detection of potential phishing attacks. The following email flow shows how this works: ![Email flow when setting up a phishing assessment risk for Microsoft Exchange with Email Security.](~/assets/images/email-security/deployment/api-setup/exchange/bcc-exchange-flow.png) diff --git a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/add-domain.mdx b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/add-domain.mdx index ff75fdeb0e3adc..a8f8e08b700169 100644 --- a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/add-domain.mdx +++ b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/add-domain.mdx @@ -7,10 +7,8 @@ sidebar: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] -::: To set up Email Security (formerly Area 1) for Gmail: diff --git a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/index.mdx b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/index.mdx index b226beab1ebbc8..2f7b411ff23075 100644 --- a/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/index.mdx +++ b/src/content/docs/email-security/deployment/api/setup/gsuite-bcc-setup/index.mdx @@ -11,12 +11,8 @@ head: import { Render, Details } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - For customers using Gmail, setting up Email Security via BCC is quick and easy. All you need to do is create a content compliance filter to send emails to Email Security through BCC. The following email flow shows how this works: ![Email flow when setting up a phishing assessment risk for Gmail with Email Security.](~/assets/images/email-security/deployment/api-setup/gmail/gmail-bcc-flow.png) diff --git a/src/content/docs/email-security/deployment/api/setup/index.mdx b/src/content/docs/email-security/deployment/api/setup/index.mdx index 53ef404b7c6d30..399630436c7049 100644 --- a/src/content/docs/email-security/deployment/api/setup/index.mdx +++ b/src/content/docs/email-security/deployment/api/setup/index.mdx @@ -10,12 +10,8 @@ head: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - When you first get started with Email Security (formerly Area 1), you will need to set up a way to connect your current mail environment with Email Security. ## BCC setup diff --git a/src/content/docs/email-security/deployment/api/setup/office365-graph-api.mdx b/src/content/docs/email-security/deployment/api/setup/office365-graph-api.mdx index d75e8aeb418e1f..fd768898c44fe3 100644 --- a/src/content/docs/email-security/deployment/api/setup/office365-graph-api.mdx +++ b/src/content/docs/email-security/deployment/api/setup/office365-graph-api.mdx @@ -9,12 +9,8 @@ description: Learn how to scan and protect Office 365 emails with Email Security import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - For customers using Microsoft Office 365, setting up Email Security via Microsoft Graph API is quick and easy. The following email flow shows how this works: ![Email flow when setting up Email Security with the Microsoft Graph API](~/assets/images/email-security/deployment/api-setup/ms-graph/ms-graph.png) diff --git a/src/content/docs/email-security/deployment/api/setup/office365-journaling.mdx b/src/content/docs/email-security/deployment/api/setup/office365-journaling.mdx index 72def3580af9f6..f244d8c1b496cb 100644 --- a/src/content/docs/email-security/deployment/api/setup/office365-journaling.mdx +++ b/src/content/docs/email-security/deployment/api/setup/office365-journaling.mdx @@ -12,12 +12,8 @@ head: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - For customers using Microsoft Office 365, setting up Email Security via journaling is quick and easy. The following email flow shows how this works: ![Email flow when setting up a phishing assessment risk for Office 365 with Email Security.](~/assets/images/email-security/deployment/api-setup/journaling/office365-journaling-flow.png) diff --git a/src/content/docs/email-security/deployment/index.mdx b/src/content/docs/email-security/deployment/index.mdx index 0caae2ea4663a8..5c9f55139dab9b 100644 --- a/src/content/docs/email-security/deployment/index.mdx +++ b/src/content/docs/email-security/deployment/index.mdx @@ -7,6 +7,8 @@ sidebar: import { DirectoryListing, Render } from "~/components"; + + Select a deployment method to get started. diff --git a/src/content/docs/email-security/deployment/inline/index.mdx b/src/content/docs/email-security/deployment/inline/index.mdx index bdf7c5472818a9..8d17d70b352f37 100644 --- a/src/content/docs/email-security/deployment/inline/index.mdx +++ b/src/content/docs/email-security/deployment/inline/index.mdx @@ -10,11 +10,9 @@ head: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + diff --git a/src/content/docs/email-security/deployment/inline/setup/cisco-area1-mx.mdx b/src/content/docs/email-security/deployment/inline/setup/cisco-area1-mx.mdx index 40e72de04504bb..80e49ae5d99fbc 100644 --- a/src/content/docs/email-security/deployment/inline/setup/cisco-area1-mx.mdx +++ b/src/content/docs/email-security/deployment/inline/setup/cisco-area1-mx.mdx @@ -13,12 +13,8 @@ head: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - ![A schematic showing where Email Security security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/cisco-area1-mx/cisco-area1-mx.png) In this tutorial, you will learn how to configure Cisco IronPort with Email Security as MX record. This tutorial is broken down into several steps. diff --git a/src/content/docs/email-security/deployment/inline/setup/cisco-cisco-mx.mdx b/src/content/docs/email-security/deployment/inline/setup/cisco-cisco-mx.mdx index 1fd24188eae5c0..bd02dbff23a790 100644 --- a/src/content/docs/email-security/deployment/inline/setup/cisco-cisco-mx.mdx +++ b/src/content/docs/email-security/deployment/inline/setup/cisco-cisco-mx.mdx @@ -13,12 +13,8 @@ head: import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - ![A schematic showing where Email Security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/cisco-cisco-mx/cisco-mx.png) In this tutorial, you will learn how to configure Email Security with Cisco as MX record. This tutorial is broken down into several steps. diff --git a/src/content/docs/email-security/deployment/inline/setup/gsuite-area1-mx.mdx b/src/content/docs/email-security/deployment/inline/setup/gsuite-area1-mx.mdx index fb79cb8c47cc6a..d16bf2efb55815 100644 --- a/src/content/docs/email-security/deployment/inline/setup/gsuite-area1-mx.mdx +++ b/src/content/docs/email-security/deployment/inline/setup/gsuite-area1-mx.mdx @@ -12,12 +12,8 @@ head: import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - ![A schematic showing where Email Security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/gsuite-area1-mx/gsuite-area1-mx.png) In this tutorial, you will learn how to configure Google Workspace with Email Security as MX record. This tutorial is broken down into several steps. diff --git a/src/content/docs/email-security/deployment/inline/setup/office-365-area1-mx/index.mdx b/src/content/docs/email-security/deployment/inline/setup/office-365-area1-mx/index.mdx index b650b52731b5ab..1a8c55229f2b8f 100644 --- a/src/content/docs/email-security/deployment/inline/setup/office-365-area1-mx/index.mdx +++ b/src/content/docs/email-security/deployment/inline/setup/office-365-area1-mx/index.mdx @@ -13,12 +13,8 @@ head: import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - ![A schematic showing where Email Security is in the life cycle of an email received](~/assets/images/email-security/deployment/inline-setup/o365-area1-mx/office365-mx.png) In this tutorial, you will learn how to configure Microsoft Office 365 with Email Security as its MX record. This tutorial is broken down into several steps. If at any steps during this tutorial you receive a message saying that you need to run the `Enable-OrganizationCustomization` cmdlet, [refer to section 6](#6-execute-enable-organizationcustomization-if-required). diff --git a/src/content/docs/email-security/email-configuration/email-policies/index.mdx b/src/content/docs/email-security/email-configuration/email-policies/index.mdx index 77f087b8d56a16..8afb89ce471466 100644 --- a/src/content/docs/email-security/email-configuration/email-policies/index.mdx +++ b/src/content/docs/email-security/email-configuration/email-policies/index.mdx @@ -6,7 +6,9 @@ sidebar: --- -import { DirectoryListing } from "~/components" +import { DirectoryListing, Render } from "~/components" + + When you use an [inline setup](/email-security/deployment/inline/), you can modify incoming, non-blocked messages with a few added layers of protection: diff --git a/src/content/docs/email-security/email-configuration/index.mdx b/src/content/docs/email-security/email-configuration/index.mdx index c7e57ee6248754..d0bc6344222f39 100644 --- a/src/content/docs/email-security/email-configuration/index.mdx +++ b/src/content/docs/email-security/email-configuration/index.mdx @@ -7,11 +7,9 @@ sidebar: import { DirectoryListing, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + Once you have [set up Email Security](/email-security/deployment/), you have several options to customize and fine-tune email behavior. diff --git a/src/content/docs/email-security/email-configuration/phish-submissions/index.mdx b/src/content/docs/email-security/email-configuration/phish-submissions/index.mdx index e7c25c2a861822..0577337fecab1c 100644 --- a/src/content/docs/email-security/email-configuration/phish-submissions/index.mdx +++ b/src/content/docs/email-security/email-configuration/phish-submissions/index.mdx @@ -6,7 +6,9 @@ sidebar: --- -import { DirectoryListing, GlossaryTooltip } from "~/components" +import { DirectoryListing, GlossaryTooltip, Render } from "~/components" + + As part of your continuous email security posture, administrators and security analysts need to submit missed phish samples to [Email Security (formerly Area 1) Service Addresses](https://horizon.area1security.com/support/service-addresses/) so Cloudflare can process them and take necessary action. diff --git a/src/content/docs/email-security/index.mdx b/src/content/docs/email-security/index.mdx index 653e086c14c33e..c223a5aa6d16b1 100644 --- a/src/content/docs/email-security/index.mdx +++ b/src/content/docs/email-security/index.mdx @@ -24,12 +24,14 @@ Stop phishing attacks with Em -:::caution[Area 1 has been renamed] +:::note[Area 1 has been renamed] Area 1 is now **Email Security (formerly Area 1)**. Customers who purchased the new Email Security can access the documentation by going to Cloudflare Zero Trust > [Email Security](/cloudflare-one/email-security/). ::: + + --- diff --git a/src/content/docs/email-security/migrate-to-email-security.mdx b/src/content/docs/email-security/migrate-to-email-security.mdx index 2a6d830a014ba8..99465e8383123c 100644 --- a/src/content/docs/email-security/migrate-to-email-security.mdx +++ b/src/content/docs/email-security/migrate-to-email-security.mdx @@ -5,12 +5,37 @@ sidebar: order: 9 --- +import { Render } from "~/components"; + This page aims at showing you how to perform Area 1 actions in [Zero Trust Email Security](/cloudflare-one/email-security/), and new terminology introduced in Email Security. :::note Your Area 1 data and configuration settings are available in Email Security. ::: + + +## Contact support + +:::note +Starting from October 1, 2025, access and support for Email Security will only be available through the Cloudflare dashboard. Your Email Security protection will not change, but you will no longer be able to access the Area 1 dashboard or send support requests to `@area1security.com` email addresses. For help accessing the Cloudflare dashboard, reach out to successteam@cloudflare.com. +::: + +In Area 1, you can reach out to support via the following email addresses: + +- support@area1security.com +- phishguard@area1security.com (for PhishGuard customers only) + +In Email Security, you can: + +- Go to the [Cloudflare Help Center](https://www.support.cloudflare.com/s/?language=en_US) +- [Contact Cloudflare Support](/support/contacting-cloudflare-support/) +- [Raise a ticket](/support/contacting-cloudflare-support/#getting-help-with-an-issue) and enter the correct answer to the following questions: + - What type of question do you have? **Technical - Other Products** + - In what area can we help you? **Email Security** + +Alternatively, if you are a PhishGuard customer, you can [contact support](https://dash.cloudflare.com/?to=/:account/support) in the Cloudflare dashboard. + ## Invite users In Area 1, you [invite users](/email-security/account-setup/manage-account-members/#add-user) by logging in to the Area 1 portal and inviting members. @@ -34,7 +59,7 @@ Once you have added new account members, you will have to assign each member an ## Create webhooks :::note -Starting from October 2025, Area 1 webhooks will be visible in Zero Trust Email Security, but non-configurable. Use [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-user-action-logs) to create new webhooks or configure webhooks. +Starting from October 1, 2025, Area 1 webhooks will be visible in Zero Trust Email Security, but non-configurable. Use [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-user-action-logs) to create new webhooks or configure webhooks. ::: In Area 1, you can [create alert webhooks](/email-security/email-configuration/domains-and-routing/alert-webhooks/#create-an-alert-webhook). @@ -62,7 +87,7 @@ You can also check the status of APIs through the [Cloudflare Status API](https: ## Email reports :::note -Starting from October 2025, weekly and daily email reports will no longer be available. Go to [Monitoring](/cloudflare-one/email-security/email-monitoring/) in Email Security to monitor your inbox. +Starting from October 1, 2025, weekly and daily email reports will no longer be available. Go to [Monitoring](/cloudflare-one/email-security/email-monitoring/) in Email Security to monitor your inbox. ::: In Area 1, you receive daily or weekly updates of the number of emails dispositioned. @@ -72,35 +97,13 @@ In Email Security, you can view [email monitoring](/cloudflare-one/email-securit ## Email alerts for detections :::note -Starting from October 2025, emails alerts for detections will no longer be available. As an alternative, use [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-detection-logs). +Starting from October 1, 2025, emails alerts for detections will no longer be available. As an alternative, use [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-detection-logs). ::: In Area 1, you receive an email when an email is assigned a disposition. In Email Security, you enable [Logpush](/cloudflare-one/insights/logs/enable-logs/#enable-detection-logs) to enable detection logs. -## Contact support - -:::note -Starting from October 2025, we will no longer receive support requests via email to any `@area1security.com` address. We will transition to receiving support requests from the Cloudflare dashboard. -::: - -In Area 1, you can reach out to support via the following email addresses: - -- support@area1security.com -- phishguard@area1security.com (for PhishGuard customers only) - -In Email Security, you can: - -- Go to the [Cloudflare Help Center](https://www.support.cloudflare.com/s/?language=en_US) -- [Contact Cloudflare Support](/support/contacting-cloudflare-support/) -- [Raise a ticket](/support/contacting-cloudflare-support/#getting-help-with-an-issue) and enter the correct answer to the following questions: - - What type of question do you have? **Technical - Other Products** - - In what area can we help you? **Email Security** -- Email phishguard@area1security.com (for PhishGuard customers only). - -If you are PhishGuard customer, you will be informed when you can start raising PhishGuard tickets in the Cloudflare dashboard. - ## Search emails In Area 1, you can perform two types of search: [Fielded Search](/email-security/reporting/search/#fielded-search) and [Freeform Search](/email-security/reporting/search/#freeform-search). diff --git a/src/content/docs/email-security/partners.mdx b/src/content/docs/email-security/partners.mdx index fca98b4a0da07b..e4fc12bc20ff85 100644 --- a/src/content/docs/email-security/partners.mdx +++ b/src/content/docs/email-security/partners.mdx @@ -7,11 +7,9 @@ sidebar: import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + Email Security Channel and Alliance partners have the option to set up accounts for themselves and their customers. diff --git a/src/content/docs/email-security/reference/cloudflare-sso.mdx b/src/content/docs/email-security/reference/cloudflare-sso.mdx index 5641bca8626717..8b525a7f8f89b5 100644 --- a/src/content/docs/email-security/reference/cloudflare-sso.mdx +++ b/src/content/docs/email-security/reference/cloudflare-sso.mdx @@ -10,11 +10,9 @@ description: You can use your Cloudflare account as the single sign-on (SSO) import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + You can use your Cloudflare account as the single sign-on (SSO) authentication scheme to log in to the Email Security dashboard: diff --git a/src/content/docs/email-security/reference/dispositions-and-attributes.mdx b/src/content/docs/email-security/reference/dispositions-and-attributes.mdx index a85b7f7144926c..b7330d547179ce 100644 --- a/src/content/docs/email-security/reference/dispositions-and-attributes.mdx +++ b/src/content/docs/email-security/reference/dispositions-and-attributes.mdx @@ -7,11 +7,9 @@ sidebar: import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + Email Security uses a variety of factors to determine whether a given email message, domain, URL, or packet is part of a phishing campaign. These small pattern assessments are dynamic in nature and — in many cases — no single pattern will determine the final verdict. diff --git a/src/content/docs/email-security/reference/how-we-detect-phish.mdx b/src/content/docs/email-security/reference/how-we-detect-phish.mdx index d57986365acc73..731df09d0aaad3 100644 --- a/src/content/docs/email-security/reference/how-we-detect-phish.mdx +++ b/src/content/docs/email-security/reference/how-we-detect-phish.mdx @@ -7,10 +7,8 @@ sidebar: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + diff --git a/src/content/docs/email-security/reference/language-support.mdx b/src/content/docs/email-security/reference/language-support.mdx index 0e0996a12b8b43..79b9665bbeb0c9 100644 --- a/src/content/docs/email-security/reference/language-support.mdx +++ b/src/content/docs/email-security/reference/language-support.mdx @@ -7,12 +7,9 @@ sidebar: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] -::: - ## Email evaluation The scanning service and verdict engines used by Email Security are language agnostic. We provide support for Double Byte Character sets (DBCS) and UTF-8, UTF-16, and UTF-32 encoding. diff --git a/src/content/docs/email-security/reference/office365-gcc.mdx b/src/content/docs/email-security/reference/office365-gcc.mdx index 1cceffb988d506..79ea0e7dcc68fd 100644 --- a/src/content/docs/email-security/reference/office365-gcc.mdx +++ b/src/content/docs/email-security/reference/office365-gcc.mdx @@ -10,12 +10,8 @@ head: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - Microsoft 365 Government Community Cloud (GCC) is designed to meet the requirements of the US government. GCC Low and GCC High are two tiers of GCC, each with different security and compliance requirements. GCC Low is intended for use by US government organizations that handle sensitive but unclassified data, and have less stringent compliance requirements. diff --git a/src/content/docs/email-security/reference/timestamps.mdx b/src/content/docs/email-security/reference/timestamps.mdx index bdaca6cba0c779..809e3e6a8b5b3f 100644 --- a/src/content/docs/email-security/reference/timestamps.mdx +++ b/src/content/docs/email-security/reference/timestamps.mdx @@ -7,12 +7,8 @@ sidebar: import { Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: -
diff --git a/src/content/docs/email-security/reporting/index.mdx b/src/content/docs/email-security/reporting/index.mdx index 001d8a8924eb16..6b33ae0e3c7b2e 100644 --- a/src/content/docs/email-security/reporting/index.mdx +++ b/src/content/docs/email-security/reporting/index.mdx @@ -7,11 +7,9 @@ sidebar: import { DirectoryListing, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: + Email Security offers a variety of ways for you to better examine and understand your message traffic: diff --git a/src/content/docs/email-security/reporting/phish-reports.mdx b/src/content/docs/email-security/reporting/phish-reports.mdx index 3c900798f42fe7..17d23985e0992e 100644 --- a/src/content/docs/email-security/reporting/phish-reports.mdx +++ b/src/content/docs/email-security/reporting/phish-reports.mdx @@ -8,7 +8,9 @@ description: Access Phish reports through the dashboard or an email digest. --- -import { GlossaryTooltip } from "~/components" +import { GlossaryTooltip, Render } from "~/components" + + Email Security automatically generates phish reports to provide an overview of your email traffic. The report only includes malicious emails. Spam and bulk emails are not included. diff --git a/src/content/docs/email-security/reporting/search/index.mdx b/src/content/docs/email-security/reporting/search/index.mdx index 34bef7dff8e5c8..6a4fe71ba69571 100644 --- a/src/content/docs/email-security/reporting/search/index.mdx +++ b/src/content/docs/email-security/reporting/search/index.mdx @@ -10,12 +10,8 @@ description: Search for messages with a detection disposition or that have been import { GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - You can search for emails that have been processed by Email Security (formerly Area 1), whether they are marked with a detection disposition or not. There are two ways for searching emails: diff --git a/src/content/docs/email-security/reporting/siem-integration/index.mdx b/src/content/docs/email-security/reporting/siem-integration/index.mdx index c0aa4f8b6de5c0..e4e5d9e736984c 100644 --- a/src/content/docs/email-security/reporting/siem-integration/index.mdx +++ b/src/content/docs/email-security/reporting/siem-integration/index.mdx @@ -11,12 +11,8 @@ description: SIEM integrations allow you to view message-level information import { DirectoryListing, GlossaryTooltip, Render } from "~/components"; -:::caution[Area 1 has been renamed] - -::: - With a bit of configuration, you can also bring Email Security (formerly Area 1) data into your Security Information and Event Management (SIEM) tools to view message-level information outside of the dashboard and create your own custom reports. ## Connect a SIEM tool diff --git a/src/content/partials/email-security/contact-support.mdx b/src/content/partials/email-security/contact-support.mdx new file mode 100644 index 00000000000000..5378b3ab6111c2 --- /dev/null +++ b/src/content/partials/email-security/contact-support.mdx @@ -0,0 +1,8 @@ +--- +{} + +--- + +:::caution[Access to Area 1] +Beginning October 1, 2025, access and support for Email Security (formerly Area 1) will only be available through the Cloudflare dashboard. Your Email Security protection will not change, but you will no longer be able to access the Area 1 dashboard or send support requests to `@area1security.com` email addresses. For help accessing the Cloudflare dashboard, reach out to successteam@cloudflare.com. +::: \ No newline at end of file diff --git a/src/content/partials/email-security/rename-area1-to-ces.mdx b/src/content/partials/email-security/rename-area1-to-ces.mdx index c98396cd735c84..4e5b20b1df6b4e 100644 --- a/src/content/partials/email-security/rename-area1-to-ces.mdx +++ b/src/content/partials/email-security/rename-area1-to-ces.mdx @@ -3,4 +3,6 @@ --- +:::note[Area 1 has been renamed] Area 1 is now **Email Security (formerly Area 1)**. +:::