Managing cyber security incidents Cyber security incident register Recording cyber security incidents in a register can assist with ensuring that appropriate remediation activities are undertaken. In addition, the types and frequency of cyber security incidents, along with the costs of any remediation activities, can be used as an input to future risk assessment activities. Security Control: ISM-0125; Revision: 5; Updated: Jun-21; Applicability: All; Essential Eight: N/A A cyber security incident register is maintained that covers the following:  the date the cyber security incident occurred  the date the cyber security incident was discovered  a description of the cyber security incident  any actions taken in response to the cyber security incident  to whom the cyber security incident was reported. Handling and containing data spills When a data spill occurs, an organisation should inform data owners and restrict access to the data. In doing so, affected systems can be powered off, have their network connectivity removed or have additional access controls applied to the data. It should be noted though that powering off systems could destroy data that would be useful for forensic investigations. Furthermore, users should be made aware of appropriate actions to take in the event of a data spill, such as not deleting, copying, printing or emailing the data. Security Control: ISM-0133; Revision: 2; Updated: Jun-21; Applicability: All; Essential Eight: N/A When a data spill occurs, data owners are advised and access to the data is restricted. Handling and containing malicious code infections Taking immediate remediation steps after the discovery of malicious code can minimise the time and cost spent eradicating and recovering from the infection. As a priority, all infected systems and media should be isolated to prevent the infection from spreading. Once isolated, infected systems and media can be scanned by antivirus software to potentially remove the infection or recover data. It is important to note though, a complete system restoration from a known good backup or rebuild may be the only reliable way to ensure that malicious code can be truly eradicated or data recovered. Security Control: ISM-0917; Revision: 7; Updated: Oct-19; Applicability: All; Essential Eight: N/A When malicious code is detected, the following steps are taken to handle the infection:  the infected systems are isolated  all previously connected media used in the period leading up to the infection are scanned for signs of infection and isolated if necessary  antivirus software is used to remove the infection from infected systems and media  if the infection cannot be reliably removed, systems are restored from a known good backup or rebuilt. Handling and containing intrusions When an intrusion is detected on a system, an organisation may wish to allow the intrusion to continue for a short period of time in order to fully understand the extent of the compromise and to assist with planning intrusion remediation activities. However, an organisation allowing an intrusion to continue in order to collect data or evidence 13

Select target paragraph3

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