An auto-forwarding rule is a mailbox setting that sends incoming email to another address automatically. Attackers value this control because it can quietly redirect sensitive messages out of the organisation after a compromise. Security teams monitor forwarding rules closely since they are a common persistence and exfiltration path.
What an auto-forwarding rule does
An auto-forwarding rule is a mailbox setting that silently reroutes incoming mail to another address. It can be legitimate for migration or delegation, but it also creates a direct path for message theft when an attacker controls the mailbox or adds forwarding after compromise.
Because the rule operates inside the email service, it can be harder to spot than obvious phishing or password changes. The forwarding destination may look normal in the user interface while sensitive messages, password resets, and approval flows continue to leave the organisation.
Why auto-forwarding rules matter in account compromise
Auto-forwarding is dangerous because email often carries the most useful compromise material, such as password resets, security alerts, payroll changes, and business approvals. Once a rule exists, the attacker may not need to stay active in the inbox, which makes the abuse useful for persistence as well as exfiltration.
The main security impact is loss of message confidentiality and continued attacker visibility into new communications. In practice, that can extend a compromise even after the initial phishing page, stolen password, or session token has been addressed.
How organisations find risky forwarding behaviour
Forwarding rules should be checked against mailbox inventory, admin policy, and user-reported symptoms such as missing emails or unexpected replies. Security teams usually look for newly added inbox rules, external destinations, and forwarding changes that appear after a login from an unusual location or device.
Detection is strongest when mailbox audit data, message trace, and identity logs are reviewed together. That makes it easier to separate ordinary auto-forwarding from malicious persistence, especially when the attacker also deleted local copies or used a hidden rule name.
Useful detection and response guidance is covered in T1114 Email Collection Defensive Guide, Microsoft 365 Unified Audit Log Guide for Detection, and Email Gateway and Message Trace Detection Guide.
Controls that reduce forwarding-rule abuse
The safest posture is to block or tightly restrict external auto-forwarding, especially for high-risk accounts and mailboxes that handle finance, legal, or security correspondence. Organisations should also make rule creation visible to administrators, because a forwarding rule is only useful to defenders when they can see it and investigate it quickly.
Broader email hardening helps as well: strong authentication, session review, mailbox auditing, and limits on application access reduce the chance that an attacker can create or hide a forwarding path. If a compromise is already suspected, the forwarding destination, active sessions, recovery details, and any connected mail access should be reviewed together.
For a practical hardening baseline, see Exchange Online Security Guide, and for incident handling after mailbox compromise, use Hacked Social Media or Email Account Recovery Guide and Business Email Compromise Response Playbook.
What to do after a malicious forwarding rule is found
Once an abusive rule is discovered, the priority is to remove the rule, revoke active sessions, and confirm the mailbox is no longer forwarding mail externally. The investigation should then look for related persistence, such as consent grants, hidden inbox rules, or other mailbox changes made around the same time.
It is also important to review whether any sensitive messages already left the organisation. That can change the response from a simple mailbox cleanup into a broader fraud, privacy, or follow-up scam response, depending on what the attacker may have seen.
For incident context and attacker tradecraft, see Business Email Compromise Response Playbook and Microsoft 365 Unified Audit Log Guide for Detection.
Risk and Threat Considerations
Auto-forwarding rules are attractive to attackers because they create low-noise persistence and a reliable exfiltration channel. Even if the mailbox owner regains access, the attacker may continue receiving sensitive mail until the rule is found and removed.
Failure mechanism: The attacker adds or modifies a mailbox rule that forwards messages to an external address, then uses the rule to collect future mail without repeatedly logging in.
Impact: Confidential mail, password resets, fraud approvals, and investigation threads can leave the organisation, extending the compromise and increasing the chance of secondary fraud.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1114 — Email Collection | Forwarding rules are a documented email collection and exfiltration path. |
| Recommendation — Map mailbox forwarding abuse to T1114 and alert on new external forwarding rules. | ||
| NIST SP 800-53 Rev 5 | AU-6 — Audit Record Review, Analysis, and Reporting | Mailbox and audit logs are needed to detect unauthorized forwarding changes. |
| AC-2 — Account Management | Mailbox forwarding is governed through account policy and administrative oversight. | |
| IA-5 — Authenticator Management | Forwarding abuse often follows compromised credentials or sessions. | |
| Recommendation — Review mailbox and sign-in audit records for rule creation and forwarding changes. Restrict who can create forwarding rules and review mailbox settings regularly. Rotate and protect authenticators after mailbox compromise to prevent renewed access. | ||
| CIS Controls v8 | CIS-5 — Account Management | Mailboxes and forwarding permissions are account-management concerns. |
| Recommendation — Inventory and control mailbox accounts, permissions, and forwarding changes. | ||
Practitioner Guidance
Why practitioners should care: Auto-forwarding should be treated as a mailbox control, not just a user convenience setting. In most environments, the question is whether the business truly needs external forwarding at all, and if so, which mailboxes may use it under policy.
What to watch for: Newly created forwarding rules, forwarding to personal mail providers, and rule changes that appear alongside sign-in anomalies or recovery-detail changes deserve immediate review. The strongest signal is when forwarding begins after suspicious access, not when it is part of a known onboarding or migration process.
Related resources from NHI Mgmt Group
- Who is accountable when a departing employee leaves a forwarding rule in place?
- How should auto dealerships implement MFA to meet the FTC Safeguards Rule without disrupting daily operations?
- When should organisations treat external email auto-forwarding as an unacceptable risk rather than a convenience feature?
- How do security teams know whether a mail forwarding rule is materially risky?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org