Phishing Attacks NCSC, UK https://www.gov.uk/content/files/phishing_guidan ce_final.pdf Domain-based Message NCSC, UK https://www.gov.uk/government/publications/em Authentication, Reporting ail-security-standards/domain-based-message- and Conformance (DMARC) authentication-reporting-and-conformance-dmarc Binding Operational DHS https://cyber.dhs.gov/assets/report/bod-18- Directive BOD-18-01 Malicious Email Mitigation 01.pdf ACSC https://acsc.gov.au/publications/protect/maliciou Strategies Mitigating spoofed emails – s_email_mitigation.htm ACSC http://www.asd.gov.au/publications/csocprote Sender Policy Framework ct/Spoof_Email_Sender_Policy_Framework.pdf explained Rationale & Controls 15.2.22. Domain-based Message Authentication, Reporting and Conformance (DMARC) 15.2.22.R.01. Rationale Phishing and malware distribution attacks are common internet security threats. To limit the possibility of agency domains being used fraudulently (e.g. for spam or spear-phishing), agencies should implement: A Sender Policy Framework (SPF); DomainKeys Identified Mail (DKIM); and Domain-based Message Authentication, Reporting & Conformance (DMARC) records. 15.2.22.R.02. Rationale It is important to note that DMARC depends on the proper implementation of both SPF and DKIM. DMARC records are published in the DNS and provide guidance to the email receiver on actions to take when emails received do not conform to the published record. 15.2.22.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:6019] Before implementing DMARC agencies SHOULD: Create a DMARC policy; List all domains, in particular those used for the sending and/or receiving of email; Review the configuration of SPF and DKIM for all active domains and all published domains; and Establish one or more monitored inboxes to receive DMARC reports. 15.2.22.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:6020] Agencies SHOULD enable DMARC for all email originating from or received by their domain(s), including: sending domain owners SHOULD publish a DMARC record with a related DNS entry advising mail receivers of the characteristics of messages purporting to originate from the sender’s domain; received DMARC messages SHOULD be managed in accordance with the agency’s published DMARC policy; and agencies SHOULD produce failure reports and aggregate reports according to the agency’s DMARC policies. 15.2.22.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:6021] Agencies SHOULD review DMARC reports on a regular basis and address any identified anomalies or security issues. 15.2.23. Filtering suspicious emails and attachments 15.2.23.R.01. Rationale The intent of blocking specific types of emails is to reduce the likelihood of phishing emails and emails or attachments containing malicious code entering the agency’s networks. 15.2.23.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1745] Agencies SHOULD configure the following gateway filters: inbound and outbound email, including any attachments, that contain: malicious code; content in conflict with the agency’s email policy; content that cannot be identified; blacklisted or unauthorised filetypes; and encrypted content, when that content cannot be inspected for malicious code or authenticated as originating from a trusted source; emails addressed to internal email aliases with source addresses located from outside the domain; and all emails arriving via an external connection where the source address uses an internal agency domain name. 15.2.24. Active web addresses (URL) embedded in emails 15.2.24.R.01. Rationale Spoofed emails often contain an active (embedded) email address directing users to a malicious website in order to infect the workstation or 202 Version_3.5__January-2022

Select target paragraph3

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