limit system users and programs to the minimum access needed to perform their duties.
14.1.12. Characterisation
14.1.12.R.01. Rationale
There are known techniques for defeating basic characterisations, therefore other methods of intrusion detection are also needed, particularly
in situations where it is impractical to use a trusted environment for the generation of the characterisation data. Characterisation is very useful
in post-intrusion forensic investigations where an infected disk can be compared to stored characterisation data in order to determine what files
have been changed or introduced.
14.1.12.R.02. Rationale
Characterisation is also directly related to business continuity and disaster recovery and is influenced by Business Impact Analyses and Risk
Assessments. Grouping elements by business applications and setting priority and criticality of the elements to the business may assist in
determining the most appropriate and useful characterisations.
14.1.12.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1185]
Agencies SHOULD:
characterise all servers whose functions are critical to the agency, and those identified as being at a high security risk of compromise;
store the characterisation information securely off the server in a manner that maintains integrity;
update the characterisation information after every legitimate change to a system as part of the change control process;
as part of the agency’s ongoing audit schedule, compare the stored characterisation information against current characterisation
information to determine whether a compromise, or a legitimate but incorrectly completed system modification, has occurred;
perform the characterisation from a trusted environment rather than the standard operating system wherever possible; and
resolve any detected changes in accordance with the agency’s information security incident management procedures.
14.1.12.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1189]
Agencies SHOULD use an Approved Cryptographic Algorithm to perform cryptographic checksums for characterisation purposes.
14.1.12.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1190]
Agencies SHOULD consider characterisations in the context of a BCP or DRP and any related Business Impact Analyses and Risk Assessments.
14.1.13. Automated outbound connections by software
14.1.13.R.01. Rationale
Applications that include beaconing functionality include those that initiate a connection to the vendor site over the Internet and inbound
remote management.
14.1.13.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1193]
Agencies SHOULD review all software applications to determine whether they attempt to establish any unauthorised or unplanned external
connections.
14.1.13.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1194]
If automated outbound connection functionality is included, agencies SHOULD make a business decision to determine whether to permit or
deny these connections, including an assessment of the security risks involved in doing so.
14.1.13.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1195]
If automated outbound connection functionality is included, agencies SHOULD consider the implementation of Data Loss Prevention (DLP)
technologies.
14.1.14. Knowledge of software used on systems
14.1.14.R.01. Rationale
Information about installed software, that could be disclosed outside the agency, can include:
user agent on Web requests disclosing the Web browser type;
network and email client information in email headers; and
email server software headers.
This information could provide a malicious entity with knowledge of how to tailor attacks to exploit vulnerabilities in the agency’s systems.
14.1.14.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1198]
Agencies SHOULD limit information that could be disclosed outside the agency about what software, and software versions are installed on their
systems.
14.2. Application Whitelisting
Objective
14.2.1. Only approved applications are used on agency controlled systems.
Context
Scope
14.2.2. This section covers information on the use of technical controls to restrict the specific applications that can be accessed by a user or group of users.
189
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents