Security Control: ISM-0570; Revision: 4; Updated: Sep-18; Applicability: All; Essential Eight: N/A Where backup or alternative email gateways are in place, they are maintained at the same standard as the primary email gateway. Open relay email servers An open relay email server (or open mail relay) is an email server that is configured to allow anyone on the internet to send emails through it. Such configurations are highly undesirable as spammers and worms can exploit them. Security Control: ISM-0567; Revision: 4; Updated: Mar-19; Applicability: All; Essential Eight: N/A Email servers only relay emails destined for or originating from their domains. Email server transport encryption Emails can be intercepted anywhere between originating email servers and destination email servers. Implementing opportunistic Transport Layer Security (TLS) encryption can mitigate this security risk while ensuring email servers remain compatible with each other. However, opportunistic TLS encryption is susceptible to downgrade attacks. To mitigate this security risk, Mail Transfer Agent Strict Transport Security (MTA-STS) allows domain owners to indicate that email transfers should only occur if satisfactory TLS encryption is negotiated beforehand. Implementing MTA-STS reduces the opportunity for downgrade attacks during email transfers, and provides visibility of when they are attempted. TLS reporting supports the implementation of MTA-STS by providing a mechanism for a domain owner to publish a location where reports can be submitted regarding the success or failure of attempts to initiate encrypted connections when sending emails to a specified domain. Security Control: ISM-0572; Revision: 4; Updated: Sep-21; Applicability: All; Essential Eight: N/A Opportunistic TLS encryption is enabled on email servers that make incoming or outgoing email connections over public network infrastructure. Security Control: ISM-1589; Revision: 1; Updated: Sep-21; Applicability: All; Essential Eight: N/A MTA-STS is enabled to prevent the transfer of unencrypted emails between complying servers. Sender Policy Framework SPF aids in the detection of spoofed emails by specifying a list of domains that are allowed to send emails. If an email server is not in the SPF record for a domain, SPF verification will fail. In specifying SPF records, domain owners should ensure that they delegate the minimum necessary set of hosts or Internet Protocol addresses necessary for sending emails. In addition, extra care should be taken when delegating to hosts or Internet Protocol addresses not under an organisation’s control. Security Control: ISM-0574; Revision: 5; Updated: Mar-22; Applicability: All; Essential Eight: N/A SPF is used to specify authorised email servers (or lack thereof) for all domains. Security Control: ISM-1183; Revision: 1; Updated: Sep-18; Applicability: All; Essential Eight: N/A A hard fail SPF record is used when specifying email servers. Security Control: ISM-1151; Revision: 3; Updated: Oct-19; Applicability: All; Essential Eight: N/A SPF is used to verify the authenticity of incoming emails. Security Control: ISM-1152; Revision: 3; Updated: Mar-19; Applicability: All; Essential Eight: N/A Incoming emails that fail SPF checks are blocked or marked in a manner that is visible to the recipients. DomainKeys Identified Mail DKIM enables the detection of spoofed email contents. This is achieved by DKIM records specifying the public key used to sign email contents. Specifically, if the signed digest in an email header does not match the signed contents of the email, verification will fail. 112

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents