Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Incident Response in the Age of Cloud

You're reading from   Incident Response in the Age of Cloud Techniques and best practices to effectively respond to cybersecurity incidents

Arrow left icon
Product type Paperback
Published in Feb 2021
Publisher Packt
ISBN-13 9781800569218
Length 622 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Dr. Erdal Ozkaya Dr. Erdal Ozkaya
Author Profile Icon Dr. Erdal Ozkaya
Dr. Erdal Ozkaya
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Getting Started with Incident Response 2. Incident Response – Evolution and Current Challenges FREE CHAPTER 3. How to Organize an Incident Response Team 4. Key Metrics for Incident Response 5. Methods and Tools of Incident Response Processes 6. Incident Handling 7. Incident Investigation 8. Incident Reporting 9. Incident Response on Multiple Platforms 10. Cyber Threat Intelligence Sharing 11. Incident Response in the Cloud 12. Building a Culture of Incident Readiness 13. Incident Response Best Practices 14. Incident Case Studies 15. Ask the Experts 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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime