Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› Mailbox Rule Creation
Threats, Abuse & Incident Response

Mailbox Rule Creation

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Threats, Abuse & Incident Response

Mailbox rule creation is the act of adding an automated rule to an email mailbox. In security work, such rules can move, forward, delete, or mark messages based on sender, subject, or other conditions, and attackers often abuse them to hide alerts or redirect mail after account compromise.

How Mailbox Rules Work

Mailbox rules are mailbox-side automation, usually evaluated when a message arrives, that can sort, redirect, delete, or flag mail without a human opening each item. They are legitimate productivity features, but they also sit close to the trust boundary between inbound email and the user’s inbox, which makes their behaviour important to understand.

Rules can be simple, such as moving newsletters into folders, or more powerful, such as forwarding messages to another address or applying actions to messages from a particular sender. The more automatic the action, the more carefully organisations need to distinguish normal user convenience from post-compromise abuse.

Why Mailbox Rules Are Abused by Attackers

Mailbox rule abuse is a common post-compromise technique because it helps an intruder control what the victim sees next. A malicious rule can hide security alerts, bury replies from colleagues, or forward mail to an external account so the attacker can watch account recovery steps and business conversations.

This matters most after credential theft or session compromise, when the attacker already has mailbox access and wants to stay invisible. The rule becomes a persistence aid inside the mailbox itself, reducing the chance that the victim notices unusual activity quickly.

For a technique-focused view of this pattern, the ATT&CK mapping and defensive patterns are covered in T1114 Email Collection Defensive Guide.

What to Look For in Email and Audit Data

Mailbox rules are easiest to spot when organisations know which mailboxes exist, which ones can create rules, and which rules should never exist. Exposure review usually starts with tenant inventory, mailbox settings, audit logging, and any allowance for external forwarding or delegated access.

Detection is strongest when changes to inbox rules, forwarding destinations, and suspicious sender or subject conditions are reviewed together. A single benign-looking rule may not be meaningful, but a rule that suppresses alerts, deletes specific mail, or forwards matching messages to an unfamiliar destination deserves immediate attention.

The broader defensive checks that help surface this behaviour are summarised in Email Platform Health Check, while M1047 Audit is useful when you want to tie rule review to recurring control validation.

Remediation and Hardening When Rules Exist

Once a suspicious rule is found, the priority is to remove the rule, recover mailbox visibility, and check whether the attacker created other persistence paths such as forwarding settings, delegates, or malicious sign-in persistence. If compromise is suspected, the mailbox should be treated as part of a wider account incident, not as an isolated email problem.

Hardening usually means limiting who can create or change forwarding behaviour, blocking or tightly governing external auto-forwarding, and making mailbox audit coverage reliable enough to catch rule creation quickly. The practical security value is not the rule itself, but the fact that it can silently reroute or suppress business-critical mail after compromise.

Where rule behaviour is being checked as part of a structured detection or response programme, D3-FCA File Creation Analysis is a useful companion for thinking about event-driven detection logic, even though the mailbox setting itself is the main subject here.

Risk and Threat Considerations

Mailbox rule creation is risky because it can convert a one-time mailbox compromise into a stealthier, longer-lived access path. The attacker does not need to keep logging in if the mailbox itself starts filtering evidence, forwarding sensitive messages, or hiding recovery notices from the user.

Failure mechanism: The rule exploits mailbox automation and user trust, then redirects, suppresses, or deletes mail that would otherwise expose compromise.

Impact: Organisations can lose alert visibility, users can miss recovery prompts or approval requests, and attackers can monitor correspondence or maintain persistence after the initial intrusion.

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.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1114 — Email CollectionMailbox rule abuse is a recognized email collection and redirection technique.
M1047 — AuditRegular audit activity is central to finding mailbox rule creation and related persistence.
Recommendation — Map mailbox rule abuse to T1114 and hunt for hidden forwarding, deletion, and suppression rules. Apply audit reviews to mailbox rule changes, forwarding settings, and related mailbox policy drift.
NIST SP 800-53 Rev 5AU-2 — Event LoggingMailbox rule creation depends on logging to expose suspicious mailbox changes.
AU-6 — Audit Record Review, Analysis, and ReportingReview of mailbox audit events is needed to detect rule abuse and account compromise signs.
AC-2 — Account ManagementMailbox rules are governed through account and mailbox management controls.
Recommendation — Log mailbox rule creation and forwarding changes so security teams can review them promptly. Review mailbox audit records for suspicious rule creation, forwarding, and deletion behaviour. Restrict mailbox rule and forwarding changes to approved account management processes.
CIS Controls v8CIS-5 — Account ManagementMailbox rule abuse is controlled through account and mailbox administration discipline.
CIS-8 — Audit Log ManagementMailbox rule investigation depends on audit logging and review.
Recommendation — Use account management controls to limit who can create or alter mailbox automation. Centralise and review audit logs for mailbox rule creation and forwarding changes.

Practitioner Guidance

What to watch for: Treat new mailbox rules as a security event when they are created outside a normal change pattern, especially if they involve forwarding, deletion, or sender-based conditions. The highest-value review is not just “was a rule added?”, but “does this rule change who can see, receive, or respond to important mail?”

Governance implication: Mailbox rules should be owned as part of email security and account protection, not left as an informal user convenience feature. Clear policy around forwarding, auditing, and incident review makes it much easier to separate legitimate automation from abuse.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org