Skip to main content
  • 710 Accesses

Abstract

Incident response is a critical component of security operations. When events are escalated to incident status, the team needs to act as quickly as possible without jeopardizing the quality of the response. The details of building and maintaining a program are detailed in Cybersecurity Incident Response so an in-depth discussion will not take place here. What this chapter focuses on are the processes the security operations team or program should conduct to understand the incident and prepare for engaging forensic specialists if necessary. The starting point is going to vary based on how the event is detected. If an endpoint is acting suspicious, then the analysis starts there. If an alert is generated by an IDS or some other network monitoring tool, then the analysis starts with network artifacts. What the security operations team wants to understand is what endpoints are affected and what the characteristics of the infection are. It also wants to understand where the suspect malware came from. This necessitates investigation logs and packets from the network, logs from the endpoint, assessing network connections and running services on the endpoint, and if the endpoint is still powered on, collecting the memory. The ability to pull memory from a suspect endpoint and saving it for analysis later is an intermediate skill that can be learned with practice. Some argue that capturing memory can corrupt some of the data because the process itself causes some of the memory to be lost. In the end, having this data for later analysis outweighs this risk as it holds the details of the infection. Sophisticated infections are easier to understand with these artifacts, and law enforcement or forensic experts will appreciate the availability of this evidence. Analyzing and investigating endpoints may not fall into the traditional role of a SOC, but most healthcare organizations again have small staffs. If a separate SOC is not practical, unless outsourced to a managed service provider, a separate incident response team also will not exist. Having the capabilities outlined in this chapter speeds up investigation and leaves experts to conducting deeper and more complex investigative processes vs. rudimentary collection.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    Eric Thompson, Cybersecurity Incident Response (Apress, 2018); www.apress.com/us/book/9781484238691

  2. 2.

    Eric Thompson, Cybersecurity Incident Response (Apress, 2018); www.apress.com/us/book/9781484238691

  3. 3.

    https://ja3er.com/form

  4. 4.

    https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247362855967

  5. 5.

    www.fortinet.com/blog/threat-research/deep-dive-into-emotet-malware.html

  6. 6.

    www.virustotal.com

  7. 7.

    https://github.com/screetsec/TheFatRat

  8. 8.

    https://github.com/Screetsec/TheFatRat

  9. 9.

    www.opinionatedgeek.com/codecs/base64decoder

  10. 10.

    www.offensive-security.com/metasploit-unleashed/backdooring-exe-files/

  11. 11.

    https://accessdata.com/products-services/forensic-toolkit-ftk

  12. 12.

    https://github.com/volatilityfoundation/volatility

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2020 Eric C. Thompson

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Thompson, E.C. (2020). Incident Response. In: Designing a HIPAA-Compliant Security Operations Center. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-5608-4_6

Download citation

Publish with us

Policies and ethics