Anti-spam is often seen as a convenience: keeping adverts out of the inbox. In fact it is the first layer of cyber defence. Email is what brings phishing messages, malicious attachments and “invoices from suppliers” into a company — the kind after which money disappears from the account.
According to the review by Ukraine’s National Cybersecurity Coordination Center (NCCC), in 2025 various forms of phishing became the main initial access vector in cyberattacks in Ukraine. According to CERT-UA, the team handled 1,727 phishing cases in 2025 — twice as many as in 2024 (843). Below: how attacks came in by email, what anti-spam checks, why it is not enough on its own, what to set up and how FortiMail closes these gaps.
How attacks came in by email in 2025
According to the NCCC review, attacks on organisations aimed at stealing money most often used mass phishing emails imitating correspondence with counterparties: invoices, contracts, payment instructions. The goal was access to remote banking systems and unauthorised payments.
| Technique | What happened |
|---|---|
| Emails from hacked mailboxes | The mailings usually came from previously compromised addresses of private companies and government bodies — from a sender the recipient trusts |
| Bypassing filters | Password-protected archives, disk images (IMG, ISO), links to Dropbox, Google Drive, OneDrive and other legitimate services |
| Archiver vulnerabilities | Phishing emails with archives that exploited WinRAR vulnerabilities; early in the year one group used a zero-day vulnerability in 7-Zip to bypass antivirus |
| Old Office vulnerabilities | Financially motivated groups spread malware en masse through Microsoft Office vulnerabilities known since 2017 |
| Attacks on mail servers | Using specially crafted emails, attackers exploited vulnerabilities in Roundcube and Zimbra webmail to intercept login tokens and steal correspondence |
| Personalisation | Texts written with AI in high-quality Ukrainian; in the second half of the year one group began adding the targeted organisation’s name to the subject line |
| Through a supplier | To send malware to heating and utility companies, attackers hacked the mailboxes of a supplier of their equipment |
Another threat is mass hoax bomb threats sent from anonymous mailboxes. According to the review, about 70% of these threats come from Russia or the temporarily occupied territories.
Links in emails lead to phishing sites. According to cyber police data cited in the review, 72,803 phishing domains were detected and blocked in 2025.
What anti-spam checks
Modern email filtering is not just about weeding out adverts. Depending on the solution, it checks:
- the sender: the reputation of the server and domain, and the results of SPF, DKIM and DMARC checks;
- the content: signs of spam and phishing, impersonation of a manager or partner, lookalike domains;
- attachments: the file type and whether it contains malicious code;
- links: whether they lead to known malicious or phishing sites.
The UK’s NCSC recommends filtering or blocking spam, phishing and malware before an email reaches the user — ideally on the server rather than in the email client. Cloud filtering should be switched on for all users.
Why anti-spam alone is not enough
Attackers know how filters work and get around them:
- A password-protected archive cannot be unpacked and checked by an ordinary filter.
- A link to a legitimate file-sharing service does not look suspicious: the malicious file sits in Google Drive or OneDrive.
- An email from a real partner’s hacked mailbox passes SPF, DKIM and DMARC. The DMARC standard says explicitly that a successful check only means the domain was used with its owner’s authorisation, not that the message is safe.
That is why the NCSC proposes four layers of defence: make it difficult for attackers to reach users, help people identify and report phishing, limit the impact of an email that does get through, and respond quickly to incidents. Anti-spam is the first layer, but not the only one.
The solution: FortiMail
FortiMail is Fortinet’s email security gateway. It inspects inbound and outbound email before it reaches the mail server or the mailbox, and complements the built-in protection of Microsoft 365 or Exchange. Here is how its features map to the techniques attackers used in 2025:
| Attacker technique | FortiMail feature |
|---|---|
| Mass mailings and known malware | FortiGuard antispam and antivirus: sender and domain reputation, signatures, heuristics, outbreak protection against new waves of mailings |
| Password-protected archives and documents | Automatic decryption of archives, PDF and Office documents using built-in and custom password lists and words from the email body — so the content can be checked |
| Documents with macros and Office exploits | Content disarm and reconstruction (CDR): removing macros and active content from Office and PDF documents; analysis in a cloud sandbox |
| Links to file-sharing services and phishing sites | URL filtering by FortiGuard categories, including newly registered domains; click protection: links are rewritten and rescanned at the moment of the click |
| Impersonating a manager or partner, lookalike domains | Business email compromise (BEC) protection: detection of address impersonation and lookalike (cousin) domains |
| Spoofing your domain | SPF, DKIM and DMARC checks for inbound email |
| An email found to be malicious after delivery | API integration with Microsoft 365 and Google: finding and removing that email from mailboxes |
| A mailing from an employee’s hacked mailbox | Outbound email is inspected just like inbound |
How it is deployed. As a gateway in front of the mail server — changing the domain’s MX record is enough; in transparent mode — without changing the MX record or the mail server settings; via the Microsoft 365 and Google APIs — also without an MX change. FortiMail comes as a hardware appliance, a virtual machine (VMware, Hyper-V, KVM, AWS, Azure, Google Cloud) or the FortiMail Cloud service.
What to watch in licensing. Content disarm and reconstruction, click protection, impersonation analysis and cloud sandboxing come in the Enterprise ATP bundle, not the base one. Scanning Microsoft 365 and Google mailboxes and removing emails after delivery require the Enterprise ATP bundle with Cloud Email API support.
Integrations. FortiMail sends logs to FortiAnalyzer and FortiSIEM, so email events can be analysed together with network and endpoint events.
No filter is a guarantee: an email from a real partner’s hacked mailbox can look entirely legitimate. That is why the other layers — multi-factor authentication, endpoint protection, training and monitoring — are still needed.
SPF, DKIM and DMARC: protecting your domain
These three DNS records stop attackers from sending email in your company’s name — to your customers, partners and your own staff:
- SPF — a list of servers allowed to send email on behalf of the domain.
- DKIM — a digital signature that lets the recipient check the email was sent from your domain and not altered in transit.
- DMARC — a policy: what to do with emails that fail the check (none — only collect reports, quarantine — treat as suspicious, usually the spam folder, reject — refuse them) and where to send reports.
The standard itself describes how to roll out DMARC: first set up SPF and DKIM, then publish a none policy with reporting. The reports will show every service that sends email in your name — CRM, newsletters, accounting software. Fix the ones that fail the check, and only then move to quarantine and reject.
This also affects delivery of your own emails. Since February 2024, Google has required all senders to Gmail to set up SPF or DKIM, and those sending more than 5,000 emails a day to set up SPF, DKIM and DMARC. Emails that fail the checks may be marked as spam or rejected.
What a company should do
- Configure filtering rather than relying on the defaults. Spam, phishing and malware filtering should cover every mailbox — in the email service’s built-in protection or on a separate gateway such as FortiMail.
- Block attachments you do not need for work: disk images, scripts, shortcuts, documents with macros from the internet. Quarantine password-protected archives for checking.
- Honour senders’ DMARC policies: emails that fail the check for domains with a quarantine or reject policy should not reach the inbox. The NCSC recommends honouring these policies.
- Set up SPF, DKIM and DMARC for your own domains, including those that do not send email.
- Update mail servers and the programs that open attachments: Exchange, Roundcube, Zimbra, Microsoft Office, archivers. How to build this process: “Vulnerability management: where to start”.
- Protect email accounts with phishing-resistant multi-factor authentication and watch for suspicious sign-ins and new forwarding rules.
- Give people a simple way to report a suspicious email — a button in the email client or a dedicated address. The NCSC stresses: do not punish people for clicking, or they will stop reporting mistakes.
- Verify changes to bank details and urgent payments through another channel — by calling a known number, not by replying to the same email.
How to recognise a phishing email: “Phishing: what it is and how to protect a company”. Where an email that gets through every layer can end up: “Ransomware: how to protect your business”.
If a malicious email has already got through
- Find the same emails in every mailbox and delete or quarantine them — a mailing is rarely a one-off.
- Block the sender, the domain and the links from the email.
- Find out who opened the attachment or followed the link. Disconnect those devices from the network and change passwords from a clean device.
- Check mailboxes for new forwarding rules and emails sent in employees’ names.
- Report to CERT-UA, and if money was lost — to the bank and the cyber police.
First steps are described in detail on the “Security incident” page, and how to prepare in advance in “Incident response: the plan and playbooks”.
Checklist
- Spam, phishing and malware filtering covers every mailbox
- Unneeded attachment types are blocked, password-protected archives are checked
- Incoming emails are checked against the sender’s SPF, DKIM and DMARC
- SPF, DKIM and DMARC are set up for your own domains, and DMARC reports are analysed
- Mail servers, Office and archivers are kept up to date
- Email is protected with multi-factor authentication
- Suspicious sign-ins and new forwarding rules are monitored
- Staff know how to report a suspicious email
- Changes to bank details are verified through another channel
- There is a procedure for when a malicious email has already got through
How Bereg-IT can help
In a consultation or audit we check your email filtering, SPF, DKIM and DMARC settings and processes. We deploy and configure FortiMail for your email and help you choose the licence; as part of IT infrastructure we work with Microsoft Exchange and Office 365. The next layers, if an email does get through, are endpoint protection and NGFW. We test staff resilience with training phishing campaigns as part of a pentest. SOC as a Service connects email and office services as an event source and notifies you of suspicious sign-ins and activity.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- National Cybersecurity Coordination Center at the NSDC of Ukraine, Review of the National Cybersecurity System of Ukraine 2025 (in Ukrainian) — phishing as the main access vector, phishing mailing techniques, attacks on mail servers, cyber police data: https://www.rnbo.gov.ua/files/2026/NATIONAL_CYBER_SCC/kiber_2025.pdf
- SSSCIP, “CERT-UA handled almost 6,000 cyber incidents in 2025: the number of enemy attacks rose by 37%” (07.01.2026, in Ukrainian): https://cip.gov.ua/ua/news/cert-ua-u-2025-roci-opracyuvala-maizhe-6000-kiberincidentiv-kilkist-vorozhikh-atak-zrosla-na-37
- NCSC (UK), Phishing attacks: defending your organisation — four layers of defence, email filtering, DMARC: https://www.ncsc.gov.uk/guidance/phishing
- RFC 9989, Domain-Based Message Authentication, Reporting, and Conformance (DMARC) (May 2026) — how to roll out DMARC: https://www.rfc-editor.org/rfc/rfc9989
- RFC 7208, Sender Policy Framework (SPF): https://www.rfc-editor.org/rfc/rfc7208; RFC 6376, DomainKeys Identified Mail (DKIM) Signatures: https://www.rfc-editor.org/rfc/rfc6376
- Google, Email sender guidelines — requirements for senders to Gmail from 1 February 2024: https://support.google.com/a/answer/81126
- Fortinet, FortiMail Data Sheet (January 2026) — features, deployment modes, licence bundles: https://www.fortinet.com/content/dam/fortinet/assets/data-sheets/FortiMail.pdf