Add cloud-mail investigation without guessing tenant scope
Fortra Cloud Email Protection is the cloud-mail layer in the email portfolio. Evaluate it for threats and suspicious messages that require context inside the supported mail environment. The selection should identify the tenant, protected users and the response actions the organisation is willing to permit.
Document existing gateway and native mail controls before connecting another system. Overlapping quarantine, reporting or remediation can confuse both analysts and users if ownership is unclear. Shared mailboxes, application accounts and delegated administrators need to be represented in the design rather than treated as ordinary named employees.
Approve permissions and demonstrate the recovery workflow
Confirm supported platforms, current integration permissions and the proposed licence scope. Have the tenant owner approve access before a production connection is created. Agree how content and event data are handled, including retention and the roles allowed to review message evidence.
Pilot a representative user group with legitimate correspondence and authorised test cases. Trace a detection into the review process and demonstrate the permitted remediation and restoration path. A mistaken action should have a recoverable route and a named support owner. Acceptance should also show source health and the effect of removing the integration. Deployment is separate from a staffed review service, so any ongoing analyst coverage should be stated in the quotation.
Evidence to request for this scope
- Confirm tenant, mailbox and integration support against the current offer.
- Validate detection context and the approved message restoration process.
- Record administrative permissions, evidence access and the responsibilities of mail and security teams.