Table of contents exchange of letters with the minister executive summary



Download 5.91 Mb.
View original pdf
Page317/329
Date27.11.2023
Size5.91 Mb.
#62728
1   ...   313   314   315   316   317   318   319   320   ...   329
Report of the COI into the Cyber Attack on SingHealth 10 Jan 2019

COI Report – Part VII
Page 404 of 425

49.3 The incident response plan must include wide-ranging examples
of security incidents, and the corresponding indicators of attack
1173. There are many different ways to tell if a system has been or is being compromised, but unless employees are able to detect, alert, and respond to these indicators in real-time, the ability to stop a cyber-attack in its tracks will be very limited.
1174. Incident response plans should therefore include a wide variety of examples of possible security incidents. There are many types of security incidents that may require reporting. These incidents should be described broadly, and accompanied by detailed descriptions of corresponding indicators of attacks of that type. Some examples of the types of security incidents to be highlighted to employees include a) Breach of personal information b) Denial of service/Distributed denial of service c) Unauthorised port scanning d) Firewall breach e) Virus outbreak f) Computer accounts) accessed by an unauthorised person g) Compromise of credentials resulting from malware infection, phishing attack, or improper disclosure of passwords) to an unauthorised person h) Devices) infected with ransomware and



COI Report – Part VII
Page 405 of 425

(i) Unauthorised modification of content or data (unexplained or unauthorised code changes, compromised/defaced website, etc.)
1175. It is important that the IR plan emphasises that context is crucial to understanding whether a cyber attack is taking place. For example, a single ping a utility used to determine whether a specific Internet Protocol (“IP”) address, or host, exists or is accessible) on the network initiated from an external source may require minimal, if any, response. No mitigating actions maybe necessary since no harmful effects were caused by the incident. However, a suspicious pattern of pings on the communications network initiated from an external source or a specific malicious security incident would require a more detailed response, mitigation steps, and more detailed documentation of the incident and outcome. Again, it must be highlighted that employees must look at the indicators
cumulatively, and not in isolation, to determine if an attack is in progress.
1176. There should be a particular focus on familiarising staff with APTs, as the signature feature of an APT attack is its propensity to remain under the radar, exploiting weaknesses in the ability of employees to detect and respond to subtle signs of attack. The Committee was informed that IHiS is adding a playbook for APT. IHiS should consider automating the playbook as an online knowledge retention tool for the purpose of guiding frontline responders. The plan should also familiarise staff with indicators of attack. Some suggested indicators are in the following sections.
49.3.1
Suspicious Privileged Account Activity
1177. As was seen from the Cyber Attack, should an attacker gain access to a user account on the network, the attacker will often seek to elevate the account’s privileges, or use it to gain access to a different account with higher privileges. Staff need to be told to watch out for out-of-hours account usage, and account activity which is out of character for that particular user, etc.




Download 5.91 Mb.

Share with your friends:
1   ...   313   314   315   316   317   318   319   320   ...   329




The database is protected by copyright ©ininet.org 2024
send message

    Main page