Chapter 5 - Theory

3. Steps to Handle Cyberattacks

Immediate Detection and Identification

The first step in handling a cyberattack is detecting the incident. Early detection is essential to mitigate damage and protect critical systems. Automated tools like IDS, SIEM systems, and endpoint detection and response (EDR) solutions can help identify suspicious activities in real time (Sikos, 2020; Sowmya & Mary Anita, 2023). Once an anomaly is detected, it is crucial to verify whether it is indeed a cyber attack or a false positive.

Containment

Once an attack has been confirmed, containment measures should be taken to limit the attack's scope. This could involve isolating affected systems, disabling network ports, or disconnecting systems from the internet. Quick containment reduces the impact on operations and prevents the spread of the attack across other critical systems or the entire network (National Institute of Standards and Technology, 2015).

Eradication

After containment, the next step is to eradicate the threat. This involves removing any malware or unauthorized access from the affected systems. The recovery team should ensure that all traces of the attack are completely eliminated, such as deleting malicious files, reversing unauthorized system changes, and closing any backdoors that may have been created by the attackers (Stallings & Brown, 2018).

Recovery

Once the attack has been eradicated, the recovery phase begins. This includes restoring affected systems from clean backups, reconfiguring firewalls, and patching vulnerabilities to prevent future attacks. Systems should be carefully monitored during this phase to ensure that the recovery process does not inadvertently reintroduce the threat (Whitman & Mattord, 2019). Depending on the severity of the attack, full system restoration may take hours, days, or even weeks.

Post-Incident Review and Reporting

After the incident has been handled, a detailed post-incident review is conducted to assess the response's effectiveness. This review should focus on identifying what went well, what could have been improved, and what gaps in the plan need to be addressed. The organization should also provide a formal incident report, documenting the timeline of events, actions taken, and the impact of the attack. These reports are often shared with regulatory bodies and stakeholders as part of the compliance process (IMO, 2017).