It is however, important to note that there are many recorded cases of websites generally considered to be a low security risk that have been compromised. 14.3.8.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1602] Agencies permitting TLS through their gateways SHOULD implement: a solution that decrypts and inspects the TLS traffic as per content filtering requirements; or a whitelist specifying the addresses (uniform resource locators) to which encrypted connections are permitted, with all other addresses blocked. 14.3.9. Legal advice on the Inspection of TLS traffic 14.3.9.R.01. Rationale Encrypted TLS traffic may contain personally identifiable information. Agencies should seek legal advice on whether inspecting such traffic is in breach of the Privacy Act or other legislation. User policies should incorporate an explanation of the security drivers and acknowledgement from users on the policy contents and requirements. Refer to Chapter 9 – Personnel Security and Chapter 15 – Email Security. 14.3.9.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1605] Agencies SHOULD seek legal advice regarding the inspection of encrypted TLS traffic by their gateways. 14.3.10. Whitelisting / Blacklisting websites 14.3.10.R.01. Rationale Defining a whitelist of permitted websites and blocking all unlisted websites limits one of the most common data delivery and exfiltration techniques used by malicious code. However, if agency personnel have a legitimate requirement to access a numerous and rapidly changing list of websites, agencies will need to consider the practicality and costs of such an implementation. In such cases black listing is a limited but none-the-less effective measure. 14.3.10.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1609] Agencies SHOULD implement whitelisting for all HTTP traffic being communicated through their gateways. 14.3.10.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1608] Agencies using a whitelist on their gateways to specify the external addresses, to which encrypted connections are permitted, SHOULD specify whitelist addresses by domain name or IP address. 14.3.10.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1610] If agencies do not whitelist websites they SHOULD blacklist websites to prevent access to known malicious websites. 14.3.10.C.04. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1611] Agencies blacklisting websites SHOULD update the blacklist on a frequent basis to ensure that it remains effective. 14.3.11. Client-side active content 14.3.11.R.01. Rationale Software that runs on agency systems SHOULD be controlled by the agency. Active content delivered though websites should be constrained so that it cannot arbitrarily access system users’ files or deliver malicious code. Unfortunately the implementations of Web browsers regularly contain flaws that permit such activity. 14.3.11.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1614] Agencies SHOULD block client-side active content, such as Java and ActiveX, which are assessed as having a limited business impact. 14.3.11.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1615] Agencies SHOULD: use client-side controls that allow JavaScript on a per website basis; and add JavaScript functions used only for malicious purposes to the agency Web content filter or IDS/IPS. 14.3.12. Web content filter 14.3.12.R.01. Rationale Using a Web proxy provides agencies with an opportunity to filter potentially harmful information to system users and their workstations. 14.3.12.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1618] Agencies SHOULD use the Web proxy to filter content that is potentially harmful to system users and their workstations. 14.3.13. Website Passwords 14.3.13.R.01. Rationale Some websites require the use of a userID and password as the authentication mechanism. The management of passwords on these websites is often insecure and there are numerous examples of compromises where tens of thousands, and sometimes millions of passwords are compromised in a single incident. Where the same password is used on multiple websites, an incident can potentially compromise the user’s account on every website using that password. It is important to treat these websites as insecure and manage passwords appropriately. 14.3.13.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST NOT [CID:1621] Users MUST NOT use agency userID and login passwords as credentials for external websites. 193 Version_3.5__January-2022

Select target paragraph3

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