Skip to content

[Email Security] Impersonation registry nuances #17519

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2024
Merged

[Email Security] Impersonation registry nuances #17519

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ...ocs/cloudflare-one/email-security/detection-settings/impersonation-registry.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ The impersonation registry contains combinations of emails of users who are like

The impersonation registry should contain a list of users who are likely to be impersonated. Email Security applies enhanced security to variations of registered email addresses for additional [Business Email Compromise (BEC)](https://www.cloudflare.com/en-gb/learning/email-security/business-email-compromise-bec/) protection.

For easier tracking, the Email Security team recommends syncing and structuring VIPs in groups, and avoid doing manual inputs of users.
:::

To add a user to the impersonation registry:
Expand Down
Loading