Fortinet FortiMail: Anti-Phishing Policies

In FortiMail policy design, phishing defense fails when organizations expect one control to identify every malicious message. Attackers can spoof domains, abuse legitimate cloud services, compromise real accounts, register look-alike domains, manipulate display names, send weaponized attachments, or write convincing social-engineering text without any obviously malicious URL. FortiMail’s anti-phishing value comes from combining multiple signals and applying policy based on the organization’s mail flow.

That layered approach fits the broader lesson from social engineering: attackers exploit trust, not just technical vulnerabilities. Email security must therefore evaluate identity, domain authentication, sender history, content, URLs, attachments, impersonation patterns, and user context together.

FortiMail contributes to Fortinet security operations when policies produce clear actions and escalation paths. The goal is to stop high-confidence malicious mail while preserving business communication and producing enough evidence for analysts to understand ambiguous cases.

Separate sender identity from display-name appearance

Users often judge a message by the name shown in the mail client. Attackers exploit this by using a trusted executive, supplier, or support-team display name while sending from an unrelated address. FortiMail impersonation analysis can use manual mappings and dynamically learned relationships between display names and internal email addresses.

Dynamic learning is useful because organizations have too many legitimate correspondents to model manually, but learning systems need guardrails. A new executive assistant, rebranded vendor, acquisition, or mail-routing change can alter normal patterns. Review important impersonation mappings and protect high-value identities explicitly.

Do not treat a display-name match as proof of fraud. Use it as one signal combined with domain, address, authentication results, message history, and content. The stronger the business impact of the requested action, the more evidence the policy should require.

Protect executive and supplier identities with a curated list of high-impact names and addresses, but avoid making the list so broad that common names create constant warnings. The strongest value comes from identities whose impersonation could authorize payments, credentials, sensitive data release, or account changes.

Dynamic mapping should be monitored for poisoning. If a malicious sender repeatedly uses a display name before the system has learned the legitimate pattern, automation could normalize the wrong relationship. Critical identities still deserve explicit configuration.

Domain authentication narrows spoofing but does not solve compromise

SPF, DKIM, and DMARC can make unauthorized use of a domain much harder when configured and enforced correctly. They are foundational for distinguishing legitimate sending infrastructure from obvious spoofing. However, a compromised mailbox can send fully authenticated phishing messages.

Email policy should therefore use authentication results without treating pass as synonymous with trusted. A message can pass domain controls and still contain malicious instructions, fraudulent payment requests, or dangerous attachments. Conversely, legitimate forwarding and third-party senders can create complex authentication outcomes.

Monitor domain-authentication failure patterns and align enforcement with the organization’s sending ecosystem. Policy changes should be staged so a stricter DMARC posture does not unexpectedly reject legitimate business systems.

DMARC enforcement should be coordinated with subdomains and third-party senders. Marketing, ticketing, HR, CRM, and transactional systems often send on behalf of the organization. Inventory them before moving to stricter policy so failures are fixed rather than simply bypassed.

Watch for cousin-domain and reply-to abuse that passes the victim organization’s DMARC checks because the attacker uses a different domain entirely. Domain authentication is strongest against spoofing of domains you control, not every form of brand impersonation.

Content and URL controls need context

Malicious URLs may be newly registered, compromised, shortened, redirected, or hosted on reputable platforms. URL reputation and rewriting can help, but the system should also evaluate the surrounding message. A credential-harvest link in an unsolicited payroll message is different from the same domain in a legitimate vendor bulletin.

Attachment analysis should consider file type, archive structure, macros, embedded URLs, and the sender relationship. High-risk attachment types can be quarantined or sent for sandbox analysis, while lower-risk content may be delivered with warnings depending on policy.

Layering reduces dependence on any single detector. Even phishing-resistant authentication does not eliminate the business-email-compromise problem when attackers persuade authorized users to approve payments, disclose data, or change account details.

URL analysis should follow redirects and account for time-of-click changes when supported by the broader security stack. Attackers frequently deliver a benign page during initial scanning and weaponize it later. Message-time reputation is only one observation point.

Password-protected archives and documents deserve defined handling. Encryption can hide content from automated inspection, but legitimate business workflows may use it routinely. Policy should reflect the organization’s actual communication patterns.

Policy actions should match confidence and business cost

Rejecting, discarding, quarantining, tagging, delivering with a warning, or holding for review all have different operational consequences. High-confidence malware may justify rejection or quarantine. Ambiguous impersonation may be better routed to review if the sender could plausibly be a new business partner.

Define which users and message classes deserve stricter controls. Finance, executives, HR, legal, and administrators are common targets, but broad restrictions can interfere with external communication. Use role and message context rather than one global action for every suspected phishing signal.

Quarantine processes also need service levels. A safe message held for six hours can disrupt business even if the security control technically worked. Measure release time and false-positive causes.

Quarantine should expose enough reason codes for help-desk and security teams to make consistent release decisions. If reviewers see only a generic ‘spam’ label, they cannot distinguish weak reputation from strong impersonation evidence.

Create separate actions for user-facing banners and analyst-only evidence. Over-warning users causes habituation; a banner should indicate a meaningful residual risk, not simply that a message was external.

Integrate sandbox evidence without assuming every file must detonate

FortiMail can work with FortiSandbox and other analysis services so suspicious files and URLs receive deeper inspection. That integration is most useful when policy determines which messages need dynamic analysis rather than indiscriminately sending everything.

Static detection, reputation, file-type controls, and sender context can resolve many messages quickly. Dynamic analysis is valuable for uncertain files that may reveal behavior only when executed. The security design should account for scan latency and define how mail is handled while analysis is pending.

Keep the final disposition explainable. Analysts should know whether a message was blocked because of impersonation, authentication failure, malicious attachment behavior, URL reputation, content pattern, or a combination.

Sandbox submissions can be prioritized by attachment novelty, sender trust, file type, macro presence, embedded URLs, and campaign prevalence. This reduces latency for the objects most likely to benefit from behavioral analysis.

Define what happens when the sandbox is unavailable. A security control should not silently switch from hold-for-analysis to unconditional delivery unless that fail-open behavior is explicitly accepted.

User reports are a sensor, not a substitute for controls

Employees will always see messages that automated systems rate incorrectly. Provide a simple reporting mechanism and feed high-quality reports into investigation. A cluster of similar reports may indicate a campaign that bypassed existing controls.

At the same time, do not make the workforce the primary detection engine. Users cannot consistently evaluate sophisticated sender infrastructure or attachment behavior. Security awareness should focus on recognizing high-risk requests and using a reliable reporting path. When a campaign is confirmed, coordinate response with incident-response teams: search for related messages, identify recipients, revoke malicious sessions or credentials, block infrastructure where appropriate, and preserve evidence.

User-reporting metrics should distinguish true malicious reports from bulk spam and benign uncertainty. High reporting volume is useful only if the workflow can triage it and feed confirmed campaign patterns back into controls.

After account compromise, search for messages sent from the legitimate mailbox as well as messages that spoofed it. Authentication systems and mail controls need to work together because compromised identity can bypass many sender-authentication checks.

Measure prevention, false positives, and campaign response

Useful metrics include blocked high-confidence phishing, impersonation detections, false-positive release rate, average quarantine-review time, malicious messages reported after delivery, repeat sender infrastructure, time to campaign-wide search, and number of users who interacted before containment.

Review policy results inside the wider Fortinet ecosystem rather than in isolation. FortiAnalyzer, FortiSandbox, FortiGate, identity systems, and endpoint telemetry can add context when an email event becomes a broader incident.

The strongest anti-phishing program does not chase a perfect detection percentage. It layers controls so one attacker technique must defeat several independent signals, and it gives analysts a fast path to contain the messages that still get through.

Run controlled phishing simulations carefully. They can test reporting and workflow, but unrealistic campaigns teach the wrong lessons. Use scenarios that exercise the same identity, urgency, and business-process weaknesses attackers target without humiliating users.

Policy review should include business stakeholders. Finance and executive assistants often know which external sender changes are legitimate and can help tune controls more precisely than a security-only review.

Track policy changes with before-and-after false-positive and malicious-catch rates. If a new control sharply increases quarantines without increasing confirmed threats, it may be too broad. If malicious reports rise after relaxation, the organization has evidence to restore stronger enforcement.

Email security also depends on operational hygiene outside FortiMail: rapid disabling of compromised accounts, secure vendor-change procedures, payment verification, and protected administrative identities. Technical filtering and business-process controls should reinforce each other.

Leave a Reply

How It Works

img
Step 1. Choose Exam
on ExamLabs
Download IT Exams Questions & Answers
img
Step 2. Open Exam with
Avanset Exam Simulator
Press here to download VCE Exam Simulator that simulates real exam environment
img
Step 3. Study
& Pass
IT Exams Anywhere, Anytime!