Define the phishing exposure and the action that follows
Fortra Phishing Protection is an external-threat and brand-protection enquiry. Distinguish it from filtering messages in employee inboxes: the concern may include fraudulent sites or campaigns targeting customers and trusted relationships outside the company's mail tenant. The project needs a defined asset and victim-exposure scope.
Start with verified brands, legitimate login or payment services and the evidence needed to identify an impersonating workflow. A suspicious link should be assessed without encouraging staff to enter real credentials or interact with a live scam. Use approved evidence-handling and review procedures.
Connect detection to authorised business response
Confirm the current service coverage and the interfaces used to deliver findings or intelligence. Define who reviews suspected phishing, who coordinates customer-facing decisions and who can approve external requests. A finding may involve security, brand and legal owners rather than the help desk alone.
Use an approved example to trace the decision process, including false-positive correction and the handling of incomplete evidence. Any disruption or takedown activity must remain within the contracted and authorised process. Handover should identify monitored assets, escalation priorities and reporting responsibilities. Where the organisation also needs employee mailbox protection, include that as a complementary scope rather than assuming one external service covers both requirements.
Evidence to request for this scope
- Identify legitimate customer-facing services and high-impact impersonation scenarios.
- Confirm selected detection, intelligence and response functions in writing.
- Rehearse evidence review and escalation without submitting real credentials to suspicious sites.
