Table of contents exchange of letters with the minister executive summary


Concluding investigations without further escalation – 22



Download 5.91 Mb.
View original pdf
Page98/329
Date27.11.2023
Size5.91 Mb.
#62728
1   ...   94   95   96   97   98   99   100   101   ...   329
Report of the COI into the Cyber Attack on SingHealth 10 Jan 2019
19.6 Concluding investigations without further escalation – 22
January 2018
321. Benjamin continued to monitor the network traffic until 22 January 2018. In this period, he found no further malicious outbound traffic from the PHI 1 Workstation. He then recorded his investigation process and findings into a deck of slides and sent the slides to Ernest on the afternoon of 22 January 2018.
322. That night, Ernest replied stating that it was an “informative report”, and
as we do not sic overall impact of this malware, I’m just wondering whether
to share this out ”. In saying this, Ernest had in mind sharing this with the Security team. The next morning, Benjamin replied agreeing that they did not know “the true impact of the malware”, and suggesting that the information be shared with IHiS security teams, “(j)ust to check if other institutions/clusters
have the same malware or printer misconfiguration”.
323. Ernest stated that this was, to his mind, not a reportable security incident as the malware on the PHI 1 Workstation had been contained. He also cited the
IR-SOP, which states that malware infections that have been detected, contained, and cleaned, without network propagation, need not be reported. He did not inform Wee “because suspected malware infection of a workstation is a very
common occurrence”. He also stated that they did not file an Incident Reporting Form (“IRF”) because they would not typically file an IRF for cases involving suspected malware infections.




COI Report – Part IV
Page 114 of 425

19.7 Assessment of IHiS’ incident response in January 2018
324. Based on the evidence presented, the Committee finds a number of deficiencies in the incident response by Ernest and Benjamin a) First, no steps were taken whatsoever by Ernest or Benjamin to investigate Workstation A, despite the evidence of communications between Workstation A and what was understood to be a suspicious IP address. The Committee finds this unsatisfactory, since such investigations would have been the next logical step following the containment of malicious activity on the PHI 1 Workstation, and was clearly not beyond their technical experience or expertise. b) Second, Ernest did not take steps to verify whether the malware found on the PHI 1 Workstation was propagated across the network.
Vivek has highlighted that this was a failure to implement the IR-
SOP which, as mentioned in paragraph 323 above, states that malware infections are not reportable if the malware is cleared and if there has been no network propagation. In this case, however, the callbacks from Workstation A were indicative of network propagation, and ought to have prompted further investigations.
325. These deficiencies arose from a failure by Ernest and Benjamin to appreciate the significance of the findings. Benjamin has explained that while he had previously dealt with malware infections, this was his first time dealing with malware which was communicating with C servers. Ernest has also explained that this was the first time he had dealt with a case where there were multiple attempts to communicate with a foreign IP address, from one or more workstations, and where one of those workstations was found with a suspicious file. As Ernest himself stated in his email to Benjamin on 22 January 2018, they did not know the “overall impact of this malware”.



Download 5.91 Mb.

Share with your friends:
1   ...   94   95   96   97   98   99   100   101   ...   329




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

    Main page