Choose the initial email-security operating layers
Fortra’s published Email Security Core tier combines Cloud Email Protection, awareness or human-risk learning and Suspicious Email Analysis. It is relevant when the requirement joins technical protection with user reporting and review. Verify current product names, licence metrics and entitlements because packaging can evolve after a catalogue page is written.
Map mail platforms, domains, user groups and the people who investigate suspicious messages. The bundle selection should explain how an employee report reaches analysis and how the resulting decision is handled. Purchasing several layers does not by itself connect their owners or operating procedures.
Pilot legitimate mail and the reporting loop
Use approved messages to test normal business delivery, reporting and the intended review path. Include shared mailboxes and application senders where supported. Awareness activities need audience, language and privacy decisions; they should not be treated as automatically configured by an email-platform integration.
For UAE teams across shifts, establish who handles time-sensitive reports and legitimate-message release. Handover should preserve mail-flow assumptions, user-reporting instructions, escalation and learning ownership. MMC can scope licensing and the selected rollout. Domain-authentication work or external-domain monitoring should be compared with the current higher-tier offer rather than assumed included in Core.
Evidence to request for this scope
- Confirm the current Core components, mail-platform support and licence quantities.
- Validate legitimate mail plus an approved user-report-to-analysis scenario.
- Assign learning administration, message-review authority and service coverage explicitly.