Guidelines for email
26 controls in 2 sections in this part of the ASD ISM. Each control links to plain-English guidance, audit tips and cross-framework mappings.
26 controls
No controls on this page match.
Email gateways and servers
17 controls- ISM-0567Restrict email relay to specific domainsEmail servers may relay only email addressed to their own domains and subdomains, or genuinely sent by the organisation's own users or systems, so outsiders cannot use them as an open relay.NCOSPSTS
- ISM-0569Centralise email routing via gatewaysRoute all email entering or leaving the organisation through its centralised email gateways, with no server, application or device exchanging email around them.NCOSPSTS
- ISM-0570Maintain backup email gateways to primary standardsKeep every backup or alternative email gateway at the same standard as the primary, such as its patch level, content filtering and security settings.NCOSPSTS
- ISM-0571Ensure secure email transmission via gatewaysWhenever users send or receive email, an authenticated and encrypted connection must carry it through their organisation's centralised email gateways.NCOSPSTS
- ISM-0572Enable opportunistic TLS for email server encryptionTurn on opportunistic TLS on each email server that sends or receives email over public networks such as the internet, encrypting every connection the other server supports.NCOSPSTS
- ISM-0574Use SPF to authorise email serversPublish an SPF record for every organisation domain and subdomain that lists the email servers allowed to send for it, or states that none are where it sends no email.NCOSPSTS
- ISM-0861Enable DKIM signing for organisational emailsDKIM-sign all email sent from the organisation's domains and subdomains, including mail outside services send in its name, so receivers can check it is genuine and unaltered.NCOSPSTS
- ISM-1024Verify senders for email failure notificationsSend a notice that an email could not be delivered only to a sender verified by SPF or another trusted means, never to an unverified one.NCOSPSTS
- ISM-1026Verification of DKIM signatures on incoming emailsVerify the DKIM signature on every incoming email that carries one, checking it against the public key the signing domain publishes in DNS.NCOSPSTS
- ISM-1027Configure email distribution lists to preserve DKIM signaturesConfigure distribution list software that external senders post to so it passes messages on without changes that would break the original sender's DKIM signature.NCOSPSTS
- ISM-1151Verify email authenticity using SPFCheck SPF on all incoming email, testing whether the server delivering each message is authorised to send for the sender's domain.NCOSPSTS
- ISM-1183Implement hard fail SPF records for email securityEnd every SPF record for the organisation's domains and subdomains with hard fail ('-all'), so any server the record does not list gets an SPF result of fail.NCOSPSTS
- ISM-1234Protect email systems with content filteringUse email content filtering on both message bodies and attachments to remove or block content that could be harmful.NCOSPSTS
- ISM-1502Block inbound external email spoofing internal domainsBlock, at the email gateway, any email that comes in from outside but carries a sender address in an internal domain or internal subdomain.NCOSPSTS
- ISM-1540Configuring DMARC for email securityConfigure DMARC records with a reject policy for every organisation domain and subdomain, telling receivers to reject email that fails DMARC checks; quarantine or none does not meet it.NCOSPSTS
- ISM-1589Enable MTA-STS for secure email transportEnable MTA-STS in both directions, publishing an enforce-mode policy for each domain that receives email and having sending servers honour other domains' policies, so mail is not sent unencrypted.NCOSPSTS
- ISM-1799Enforce email rejection for failed DMARC checksReject incoming email that fails DMARC checks, rather than quarantining it or marking it as spam, even when the sending domain's own policy asks for less.NCOSPSTS
Email usage
9 controls- ISM-0264Develop and maintain an email usage policyWrite an email usage policy setting the rules for how the organisation's email is used, put those rules into effect, and keep the policy current.NCOSPSTS
- ISM-0267Blocking access to unapproved webmail servicesBlock access to every webmail service the organisation has not approved, so people cannot send or receive email around its email controls.NCOSPSTS
- ISM-0269Confirm all list members' nationality before emailing AUSTEO, AGAO or REL dataOn SECRET and TOP SECRET systems, do not send emails holding AUSTEO, AGAO or REL data to a distribution list unless every member's nationality can be confirmed.STS
- ISM-0270Apply protective markings to emails based on sensitivityMark every email with a protective marking that matches the most sensitive part of its subject line, body and attachments.NCOSPSTS
- ISM-0271Prevent protective marking tools from automatically marking emailsProtective marking tools must never put a marking into an email on their own: the user selects the protective marking for each email they send.NCOSPSTS
- ISM-0272Restrict protective marking tools to authorised system markingsProtective marking tools must offer only the markings the system's authorisation covers, so no user can select a marking the system may not handle.NCOSPSTS
- ISM-0565Email security for protective markingsConfigure email servers to block any email with an inappropriate protective marking, such as one above what the receiving system may handle, and to log and report it.NCOSPSTS
- ISM-1023Notify parties of blocked emailsWhen an email is blocked for its protective marking, notify its intended recipient if it was coming in, or its sender if it was going out.NCOSPSTS
- ISM-1089Block downgrading protective markings on email replies and forwardsOn replies and forwards, protective marking tools must not let users choose a lower marking than the email already carried.NCOSPSTS
Back to the full Australian Government Information Security Manual control list, or browse the complete control library.




