Allowing and blocking access to domain names Defining an organisation-approved list of domain names, and blocking all others, removes one of the most common data exfiltration paths used by an adversary. In doing so, even a relatively permissive list of allowed domain names, such as the entire Australian subdomain (‘*.au’) or the top 1,000 websites from the Alexa website ranking, offers better security than relying solely on a list of malicious domain names. Furthermore, in cases where an organisation chooses to implement a relatively permissive list of allowed domain names, or list of website categories, security risks can be further mitigated by blocking dynamic domain names, or domain names that can be registered anonymously for free, as these are often used by an adversary due to their lack of attribution. Finally, as users rarely have a requirement to access websites via their IP addresses instead of their domain names, the presence of such activities could indicate malicious code attempting to communicate with an adversary’s command and control infrastructure and should be blocked. Security Control: ISM-0958; Revision: 8; Updated: Mar-22; Applicability: All; Essential Eight: N/A An organisation-approved list of domain names, or list of website categories, is implemented for all Hypertext Transfer Protocol and Hypertext Transfer Protocol Secure traffic communicated through gateways. Security Control: ISM-1236; Revision: 2; Updated: Mar-22; Applicability: All; Essential Eight: N/A Malicious domain names, dynamic domain names and domain names that can be registered anonymously for free are blocked by web content filters. Security Control: ISM-1171; Revision: 2; Updated: Mar-22; Applicability: All; Essential Eight: N/A Attempts to access websites through their IP addresses instead of their domain names are blocked by web content filters. Further information Further information on content filtering techniques can be found in the content filtering section of these guidelines. Further information and examples of client-side JavaScript controls are available from the NoScript project. Content filtering Content filtering techniques The following content filtering techniques should be considered as part of an organisation’s content filtering implementation for gateways and CDSs:  Antivirus scans: Scans files for viruses and other malicious code.  Automated dynamic analysis: Analyses executable files run in a sandbox to detect suspicious behaviour.  File extension checks: Checks file extensions to determine purported file types.  File format checks: Checks files conform to defined file format specifications.  File type checks: Checks file headers to determine actual file types.  Keyword checks: Checks files for keywords that could indicate undesirable content.  Metadata checks: Checks files for metadata that should be removed.  Protective marking checks: Checks files for protective markings that may indicate undesirable content.  Manual inspections: Involves the manual inspection of files for suspicious or undesirable content that an automated system may miss, which is particularly important for multimedia and content rich files. 146

Select target paragraph3

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