ASD ISM 1502 Block inbound external email spoofing internal domains
What it says
Emails arriving via an external connection where the email source address uses an internal domain, or internal subdomain, are blocked at the email gateway.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Block, at the email gateway, any email that comes in from outside but carries a sender address in an internal domain or internal subdomain.
Emails arriving via an external connection, meaning from outside the organisation's own email systems, must be blocked at the email gateway when their source address, the sender's email address, is in an internal domain or internal subdomain. Internal domains are the organisation's own domain names, and an internal subdomain is any name under one of them. Blocked means stopped at the gateway and not delivered, so a warning banner or junk folder does not meet it. The rule applies even if the email passes sender authentication checks.
Free. Save your status, tasks and notes.
Why it matters
Phishing that appears to come from a colleague or internal team is more readily trusted. Blocking external mail that claims an internal sender removes that disguise at the gateway, before staff see it, though lookalike domains need other checks.
How to implement
List every internal domain and subdomain.
Start from the domains the email system accepts mail for, then check DNS zones and domain registrations for older or secondary domains. Write the rule to match each domain and anything under it, not exact names only, so an invented subdomain is caught too.
Move legitimate outside senders off internal addresses first.
Services such as a ticketing or survey platform that email staff as an internal address should instead use their own domain or an authenticated account on the organisation's email system. Join the organisation's own cloud and on-premises email by an authenticated connector. Never exempt by sender address, which a spoofer can copy.
Create the block rule on every email gateway, backup ones included (ISM-0570).
Match mail from outside whose envelope sender or visible From address is in an internal domain or subdomain, and reject it, not just tag or junk it. On a cloud email service, where rejecting can notify unverified senders (ISM-1024), quarantine it for administrators, but reject DMARC failures (ISM-1799).
Test from outside through every gateway.
Send test emails from an external mail server to each gateway, using an internal domain and then an internal subdomain as the sender, once in the envelope sender alone and once in the From field alone. Confirm in the gateway log that each was blocked and none reached a mailbox.
Keep it running
Add each new domain to the rule when the organisation registers or acquires it. Retest after gateway, routing or email platform changes, and check that any new outside service emailing staff uses its own domain or an authenticated account on the organisation's email system.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The list of internal domains in the gateway rule, with the email system's accepted domains and the organisation's domain registrations.
Look at
Whether every internal domain is covered, and whether the rule matches any subdomain or only exact names.
Good evidence
Every domain the organisation holds, including secondary and older ones, is in the rule, and the rule matches any subdomain of each.
- Check 2 of 3What an auditor asks for
Ask for
A test, from a mail server outside the organisation, of emails sent to each gateway including backup gateways, using an internal domain and then an internal subdomain as the sender, once in the envelope sender alone and once in the From field alone.
Look at
Whether each email is blocked at the gateway, and what the gateway log records.
Good evidence
Every test email is blocked at the gateway, on primary and backup gateways alike, and none reaches a mailbox, junk folder or quarantine that users can release.
- Check 3 of 3What an auditor asks for
Ask for
The rule's exceptions and the gateway's allow lists, with the list of outside services that email staff.
Look at
Whether any sender, domain or connection is exempt from the block, and on what basis.
Good evidence
No exception, whether by sender address, domain or IP address, lets through mail arriving over an external connection with an internal sender address, and each outside service that emails staff uses its own domain or an authenticated account on the organisation's email system.
Mappings
Closest match in ISO/IEC 27001: A.5.14, Information transfer, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.5.14.
ISM-1502 requires the email gateway to block emails arriving via an external connection that use an internal domain or subdomain as the source address, preventing spoofed messages from impersonating internal senders. This is a specific technical safeguard for the security of information transfer by electronic messaging, which Annex A 5.14 requires the organisation to govern through transfer rules and procedures. Annex A 5.14 covers all transfer facilities and parties, whereas ISM-1502 addresses only inbound email sender spoofing at the gateway.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




