To celebrate our 10th episode of the Strive podcast, I released an extended episode covering a real-life cyberattack, which brings to life some of the topics I\u2019ve covered in previous episodes.<\/p>\n\n\n\n
I investigated this attack personally during my time working in forensics and attack modeling, before my time at Commvault. Company names have been kept anonymous here for obvious reasons, but this illustration will bring you a little closer to how a breach unfolds in the real world.<\/p>\n\n\n\n
This breach began when the IT team noticed unusual activity on the network. It started with a few alerts from an intrusion detection system signaling potential anomalies on the network. At first, it seemed like a false alarm. But as the alerts grew more frequent, the team realized they were facing something a little bit more substantial.<\/p>\n\n\n\n
The alerts seen by the IT team were an example of too little too late in this case. The activity was network traffic stimulated by criminals already communicating with their malware through command and control, sometimes referred to as C2.<\/p>\n\n\n\n
The attackers actually started their campaign against this organization about three months previously, with phishing emails crafted to appear as legitimate internal communications.<\/p>\n\n\n\n
And that\u2019s of course all it took \u2013 just for one employee to click on the embedded malicious link. A remote access Trojan, a RAT, enabled the attackers to establish a foothold in the corporate network, and the weaponization phase of the attack was complete.<\/p>\n\n\n\n
Next, using a tool called Mimikatz, the criminals extracted credentials from system memory, gaining admin access to the corporate network. They could now move laterally across the network, exploiting further vulnerabilities in unpatched systems to gain a further foothold in the network.<\/p>\n\n\n\n
Then, they started to remotely execute various commands on various machines and servers across the IT estate, in order to further prepare for a ransomware attack.<\/p>\n\n\n\n
Once they had full control and had gathered all the information about the targeted organization as was needed, which was about three months\u2019 worth of reconnaissance in this case, the attackers deployed ransomware known as Ryuk, notorious for its ability to encrypt entire networks very quickly.<\/p>\n\n\n\n
The impact of the attack was immediate and devastating. Critical business applications came to a halt within minutes. The organization could no longer access critical data like essential systems, customer information, financial records, and internal documents.<\/p>\n\n\n\n
The attackers then left a ransom note, demanding a substantial payment of Bitcoin to decrypt the data. In response to all of this, the organization activated their incident response plan. They started to isolate affected systems to prevent further spread of the Ryuk ransomware, and they engaged cyber security experts to conduct a thorough investigation.<\/p>\n\n\n\n
The targeted company decided NOT to pay the ransom and instead rely on system backups and disaster recovery techniques. The recovery process was complex and time-consuming. The organization had to rebuild much of its IT infrastructure almost from the hardware up.<\/p>\n\n\n\n
The first step the organization took was containment, isolating infected systems to prevent the ransomware from spreading any further. Next came eradication, the business of removing the malicious software and cleaning up the network as much as possible using advanced anti-malware tools.<\/p>\n\n\n\n
After several days of working on containment and eradication, the restoration process could finally start. Unfortunately, some critical backups were compromised by the ransomware. And the restoration process here was painstakingly slow.<\/p>\n\n\n\n
It took eight days to ascertain where the last clean recovery points were for most of the critical business applications. A lot of recent data was lost, and the business was pretty close to breaking point by the time critical systems could be fully recovered.<\/p>\n\n\n\n
Once critical systems were back up and running, the process of rigorous monitoring began. Here, implementing enhanced monitoring solutions was necessary to try and attack any signs of residual malicious activity.<\/p>\n\n\n\n
All of this was reliant on thorough communication with internal and external stakeholders on the breach itself and the steps being taken to mitigate the impacts of it.<\/p>\n\n\n\n
This incident underscores several critical lessons for organizations of all sizes:<\/p>\n\n\n\n
Firstly, regular cyber security training for employees is essential. Skepticism toward email and likely phishing attempts potentially could have thwarted the initial breach three months before the indicator of compromise.<\/p>\n\n\n\n
Having up-to-date backups stored offline, immutable, that cannot be compromised, is completely vital. And of course, the regular testing of those backups would have ensured in this case that they could be relied upon in this emergency. Regular testing of restoration into a clean room would have saved this organization a great deal of recovery time.<\/p>\n\n\n\n
Implementing multi-factor authentication would have significantly reduced the risks associated with that credential theft that we saw.<\/p>\n\n\n\n
Employing advanced threat detection techniques and anomaly detection techniques could have helped to identify early and mitigate threats in close to real time.<\/p>\n\n\n\n
The organization\u2019s full recovery here took several months, during which they operated at a significant reduced capacity. The financial cost here was immense, not only in terms of recovery expenses, but also in lost business and reputational damage.<\/p>\n\n\n\n