implementation of access controls on relevant objects to limit system users and programs to the minimum access required; installation of antivirus and anti-malware software; installation of software-based firewalls limiting inbound and outbound network connections; configuration of either remote logging or the transfer of local event logs to a central server; and protection of audit and other logs through the use of a one way pipe to reduce likelihood of compromise key transaction records. 14.1.9. Maintaining hardened SOEs 14.1.9.R.01. Rationale Whilst a SOE can be sufficiently hardened when it is deployed, its security will progressively degrade over time. Agencies can address the degradation of the security of a SOE by ensuring that patches are continually applied, system users are not able to disable or bypass security functionality and antivirus and other security software is appropriately maintained with the latest signatures and updates. 14.1.9.R.02. Rationale End Point Agents monitor traffic and apply security policies on applications, storage interfaces and data in real-time. Administrators actively block or monitor and log policy breaches. The End Point Agent can also create forensic monitoring to facilitate incident investigation. 14.1.9.R.03. Rationale End Point Agents can monitor user activity, such as the cut, copy, paste, print, print screen operations and copying data to external drives and other devices. The Agent can then apply policies to limit such activity. 14.1.9.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:1158] Agencies MUST ensure that for all servers and workstations: a technical specification is agreed for each platform with specified controls; a standard configuration created and updated for each operating system type and version; system users do not have the ability to install or disable software without approval; and installed software and operating system patching is up to date. 14.1.9.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1159] Agencies SHOULD ensure that for all servers and workstations: malware detection heuristics are set to a high level; malware pattern signatures are checked for updates on at least a daily basis; malware pattern signatures are updated as soon as possible after vendors make them available; all disks and systems are regularly scanned for malicious code; and the use of End Point Agents is considered. 14.1.10. Default passwords and accounts 14.1.10.R.01. Rationale Default passwords and accounts for operating systems are often exploited by attackers as they are well documented in product manuals and can be easily checked in an automated manner with little effort required. 14.1.10.C.01. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST [CID:1162] Agencies MUST reduce potential vulnerabilities in their SOEs by: removing unused accounts; renaming or deleting default accounts; and replacing default passwords before or during the installation process. 14.1.10.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1163] Agencies SHOULD reduce potential vulnerabilities in their SOEs by: removing unused accounts; renaming or deleting default accounts; and replacing default passwords, before or during the installation process. 14.1.11. Server separation 14.1.11.R.01. Rationale Servers with a high security risk can include Web, email, file, Internet Protocol Telephony (IPT) servers, Mobile Device Manager (MDM) servers and gateway components. It is important to clearly identify all services and connections to design a complete and secure server separation architecture. Refer also to Chapter 19 – Gateway Security. 14.1.11.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1169] Where servers with a high security risk have connectivity to unsecure public networks, agencies SHOULD: use appropriately designed and configured gateways; consider the use of cross-domain solutions; segment networks; maintain effective functional segregation between servers allowing them to operate independently; minimise communications between servers at both the network and file system level as appropriate; and 188 Version_3.5__January-2022

Select target paragraph3

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