7.3.8.
Containing data spills
7.3.8.R.01.
Rationale
The spillage of classified information onto a system not accredited to handle the information is considered aserious information security
incident. It may be a critical information security incident if PII or particularly sensitive information is spilled. Refer to Section 7.2 – Reporting
Information Security Incidents.
7.3.8.R.02.
Rationale
Isolation may include disconnection from other systems and any external connections. In some cases system isolation may not be possible for
architectural or operational reasons.
7.3.8.R.03.
Rationale
Segregation may be achieved by isolation, enforcing separation of key elements of a virtual system, removing network connectivity to the
relevant device or applying access controls to prevent or limit access.
7.3.8.R.04.
Rationale
It is important to note that powering off a system can destroy information that may be useful in forensics analysis or other investigative work.
In large, inter-connected systems, powering off a system may not be feasible.
7.3.8.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1283]
When classified information is introduced onto a system not accredited to handle the information, the following actions MUST be followed:
1. Immediately seek the advice of an ITSM;
2. Segregate or isolate the affected system and/or data spill;
3. Personnel MUST NOT delete the higher classified information unless specifically authorised by an ITSM.
7.3.8.C.02.
ControlSystem Classification(s): All Classifications; Compliance: MUST NOT
[CID:1284]
When classified information is introduced onto a system not accredited to handle the information, personnel MUST NOT copy, view, print or
email the information.
7.3.8.C.03.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1285]
When a data spill involving classified information or contaminating classified systems occurs and systems cannot be segregated or isolated
agencies SHOULD immediately contact the NCSC for further advice.
7.3.9.
Handling malicious code infection
7.3.9.R.01.
Rationale
The guidance for handling malicious code infections is provided to assist in preventing the spread of the infection and to prevent reinfection.
Important details include:
the infection date/time of the machine;
any observed effects and source details;
the possibility that system records and logs could be compromised; and
the period of infection.
7.3.9.R.02.
Rationale
A complete operating system reinstallation, or an extensive comparison of checksums or other characterisation information, is often the only
reliable way to ensure that malicious code is eradicated.
7.3.9.R.03.
Rationale
Agencies SHOULD be aware that some malicious code infections may be categorised as Advanced Persistent Threats (APTs) which may have
been present for some time before detection. Specialist assistance may be required to deal with APTs.
7.3.9.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1290]
Agencies SHOULD follow the steps described below when malicious code is detected:
isolate the infected system;
decide whether to request assistance from NCSC;
if such assistance is requested and agreed to, delay any further action until advised by NCSC;
scan all previously connected systems and any media used within a set period leading up to the information security incident, for malicious
code;
isolate all infected systems and media to prevent reinfection;
change all passwords and key material stored or potentially accessed from compromised systems, including any websites with password
controlled access;
advise system users of any relevant aspects of the compromise, including a recommendation to change all passwords on compromised
systems;
use up-to-date anti-malware software to remove the malware from the systems or media;
monitor network traffic for malicious activity;
report the information security incident and perform any other activities specified in the IRP; and
in the worst case scenario, rebuild and reinitialise the system.
7.3.10.
76
Allowing continued attacks
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents