TL;DR: Novel phishing, impersonation, and BEC can slip past perimeter-based email security when rules and signatures are all it has, with IRONSCALES arguing that API-native controls are built for that gap. Email security then has to work inside the tenant, where mailbox behaviour and cross-tenant remediation matter more than rerouting mail.
Editorial analysis by NHI Mgmt Group, based on content published by IRONSCALES: “Ready to Move On: How to Evaluate, Select, and Deploy Modern Email Security”.
Key questions
Q: How should security teams evaluate API-native email security instead of a gateway model?
A: Evaluate whether the control inspects mailbox context, learns behaviour inside the tenant, and remediates delivered threats without forcing MX changes.
Q: What are the signs that an email security platform is still behaving like a SEG?
A: If the vendor relies on rules, signatures, policy updates, or mail rerouting, it is still operating on a perimeter model.
Q: What breaks when an email security gateway relies on rules and signatures?
A: Rules and signatures fail when the message is novel, socially engineered, or delivered through a trusted account.
Practitioner guidance
- Define the architectural outcome before comparing vendors Decide whether you are trying to modernise a perimeter gateway or replace it with a control that works inside Microsoft 365 and Google Workspace.
- Test behaviour-based detection against real inbox conditions Run a pilot that includes impersonation, vendor fraud, and account takeover scenarios, then measure whether the platform flags messages that signatures miss.
- Validate tenant-wide remediation workflows Confirm that one detected threat can be removed across all affected mailboxes without manual cross-checking between tenants.
Bottom line: Legacy email gateways struggle when attacks depend on impersonation, behavioural deception, or delivered messages that do not match known signatures.
Glossary terms: AI-native email security, Behavior Baseline, Business email compromise, Perimeter email gateway
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Perimeter email filtering is now a structural lagging control. Static rules and signatures still matter, but they are increasingly backward-looking in a threat environment where intent, sender behaviour, and account compromise matter more than file inspection. That means email security governance should be evaluated as an identity-adjacent control problem, not just a messaging hygiene problem. Practitioners should treat the perimeter model as a containment layer, not the primary decision engine.
A question worth separating out:
Q: Should MSPs prioritise deployment simplicity or remediation depth in email security?
A: Deployment simplicity matters, but only if it does not weaken response depth. MSPs should prioritise platforms that connect directly to tenant mailboxes, preserve delivery flow, and can remove the same threat across affected environments without creating additional manual work.
👉 Read our full editorial: Legacy SEG limitations are driving API-native email security migration