14.3.1. Access to Web content is implemented in a secure and accountable manner. Context Scope 14.3.2. This section covers information on Web browsers, plug-ins and active content including the development and implementation of appropriate use policies. The requirements in this section apply equally to the Web accessed via the Internet as well as websites accessed on an agency intranet. References 14.3.3. A Web whitelisting software application that allows for the management of whitelists can be obtained from: Reference Title Dynamic Web Whitelisting for Publisher SourceForge Source http://whitetrash.sourceforge.net/ Squid 14.3.4. Examples of client-side JavaScript controls are available at: Reference Title NoScript Firefox extension Publisher Inform Action Source http://noscript.net Rationale & Controls 14.3.5. Web usage policy 14.3.5.R.01. Rationale If agencies allow system users to access the Web they will need to define the extent of Web access that is granted. This can be achieved through the development, and awareness raising amongst system users, of a Web usage policy. 14.3.5.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:1272] Agencies MUST develop and implement a policy governing appropriate Web usage. 14.3.6. Web proxy 14.3.6.R.01. Rationale Web proxies provide valuable information in determining if malicious code is performing regular interactions over Web traffic. Web proxies also provide usable information if system users are violating agency Web usage policies. 14.3.6.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1592] Agencies SHOULD use a Web proxy for all Web browsing activities. 14.3.6.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1593] An agency’s Web proxy SHOULD authenticate system users and provide logging that includes at least the following details about websites accessed: address (uniform resource locator); time/date; system user; internal IP address; and external IP address. 14.3.6.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD NOT [CID:1594] Agencies SHOULD NOT permit downloading of executable files from external websites unless there is a demonstrable and approved business requirement. 14.3.7. Applications and plug-ins 14.3.7.R.01. Rationale Web browsers can be configured to allow the automatic launching of downloaded files. This can occur with or without the system user’s knowledge thus making the workstation vulnerable to attack. 14.3.7.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1597] Agencies SHOULD disable the automatic launching of files downloaded from external websites. 14.3.8. Inspection of TLS 14.3.8.R.01. Rationale As TLS encrypted Web traffic travelling over HTTPS connections can deliver content without any filtering, agencies can reduce this security risk by using TLS inspection so that the Web traffic can be filtered. 14.3.8.R.02. Rationale An alternative of using a whitelist for HTTPS websites can allow websites that have a low security risk of delivering malicious code and have a high privacy requirement like Web banking, to continue to have end-to-end encryption. 14.3.8.R.03. 192 Rationale Version_3.5__January-2022

Select target paragraph3

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