15.1.18. Awareness of email usage policies 15.1.18.R.01. Rationale In order to protect information and systems, system users will need to be familiar with email usage policies. 15.1.18.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:1726] Agencies MUST make their system users aware of the agency’s email usage policies. 15.1.19. Monitoring email usage 15.1.19.R.01. Rationale Agencies may choose to monitor compliance with aspects of email usage policies such as attempts to send prohibited file types or executables, attempts to send excessive sized attachments or attempts to send classified information without appropriate protective markings. 15.1.19.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1729] Agencies SHOULD implement measures to monitor their personnel’s compliance with email usage policies. 15.1.19.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1730] Agencies SHOULD enforce the use of approved government email systems such as SEEMAIL. 15.1.20. Public Web-based email services 15.1.20.R.01. Rationale Using public Web-based email services may allow personnel to bypass security measures that agencies will have put in place to protect against malicious code or phishing attempts distributed via email. Web based email services may also by-pass agency context filtering mechanisms. 15.1.20.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT [CID:1733] Agencies SHOULD NOT allow personnel to use public Web-based email services, for processing, receiving or sending emails or attachments for official business. 15.2. Email Infrastructure Objective 15.2.1. Email infrastructure is hardened, email is secured and protective marking of email messages is enforced. Context Scope 15.2.2. This section covers information on email infrastructure security. Information on using email applications can be found inSection 15.1 - Email Applications and Section 9.3 - Using the Internet. Anti-Spoofing Controls 15.2.3. Phishing and malware distribution attacks are common internet security threats. To avoid agency domains being used fraudulently (e.g. for spam or spear-phishing), the following should be implemented: Sender Policy Framework (SPF) DomainKeys Identified Mail (DKIM) Domain-based Message Authentication, Reporting & Conformance (DMARC) records 15.2.4. Correct configuration of these features will help other mail servers authenticate the email they receive from your domains. It is important to note that DMARC is designed to protect against direct domain spoofing only. DMARC does not eliminate the need for additional forms of protection and analysis. It does, however, provide a way for participating senders and receivers to coordinate protective activities and streamline security processes. 15.2.5. It is also important to note that not all mail service providers enable DMARC, substituting the registration of a free email account as a validation of the user’s email account instead. In this case the benefits and reporting associated with DMARC are not available. Domain-based Message Authentication, Reporting and Conformance (DMARC) Vocabulary 15.2.6. The terms “none”, “reject” and “quarantine” are used to describe DMARC actions based on policy modes. In this usage: “none” means no action on the transmission or receipt of the email but continue to collect data and send reports; By default, email under a “reject” policy setting is not delivered. “Reject” either: refuses to accept non-compliant email, or initially accepts the non-compliant email but prevents an email reaching the user. The acceptance process can generate a Delivery Status Notification (block/“bounce”) or simply delete/drop the email (block/delete); “quarantine” prevents an email from reaching the user but safely storing it so it can be accessed if required (a potentially suspicious email and/or attachment subject to additional scrutiny). Quarantined items can be released following a review and release process. What is DMARC 15.2.7. Domain-based Message Authentication, Reporting and Conformance (DMARC) is an email authentication policy and reporting protocol that: complements and unifies the existing validation checks performed by SPF and DKIM; checks the stated origin of inbound emails using a combination ofSender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM); establishes a recipient email response for emails that fail the check; 199 Version_3.5__January-2022

Select target paragraph3

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