Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Incident Response in the Age of Cloud
  • Table Of Contents Toc
  • Feedback & Rating feedback
Incident Response in the Age of Cloud

Incident Response in the Age of Cloud

By : Dr. Erdal Ozkaya
4.6 (16)
close
close
Incident Response in the Age of Cloud

Incident Response in the Age of Cloud

4.6 (16)
By: Dr. Erdal Ozkaya

Overview of this book

Cybercriminals are always in search of new methods to infiltrate systems. Quickly responding to an incident will help organizations minimize losses, decrease vulnerabilities, and rebuild services and processes. In the wake of the COVID-19 pandemic, with most organizations gravitating towards remote working and cloud computing, this book uses frameworks such as MITRE ATT&CK® and the SANS IR model to assess security risks. The book begins by introducing you to the cybersecurity landscape and explaining why IR matters. You will understand the evolution of IR, current challenges, key metrics, and the composition of an IR team, along with an array of methods and tools used in an effective IR process. You will then learn how to apply these strategies, with discussions on incident alerting, handling, investigation, recovery, and reporting. Further, you will cover governing IR on multiple platforms and sharing cyber threat intelligence and the procedures involved in IR in the cloud. Finally, the book concludes with an “Ask the Experts” chapter wherein industry experts have provided their perspective on diverse topics in the IR sphere. By the end of this book, you should become proficient at building and applying IR strategies pre-emptively and confidently.
Table of Contents (18 chapters)
close
close
16
Other Books You May Enjoy
17
Index

Reporting to third parties

There are many third parties interested in the affairs of an organization, particularly cybersecurity incidents. Such parties include government agencies, regulatory bodies, and organizations within a supply chain. Regulatory bodies are mostly focused on compliance while partner organizations are concerned about the impacts of an incident on normal business processes. Therefore, when reporting to third parties, there could be diverse focus areas depending on the party intended to receive the report. However, at the bare minimum, an incident report to third parties should include the following elements.

Description of the incident

This should be a succinct explanation of the events that occurred before, during, and after the incident. The details could be put in simple terms for a non-technical audience but technical jargon can be used for some entities, like regulatory bodies.

Cause of the incident

It is important to highlight the cause...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY