- Cybersecurity:Attack and Defense Strategies
- Yuri Diogenes Erdal Ozkaya
- 355字
- 2021-06-30 19:15:50
Lessons learned
After reading this scenario, you can see examples of many areas that were covered throughout this chapter and that will come together during an incident. But an incident is not finished when the issue is resolved. In fact, this is just the beginning of a whole different level of work that needs to be done for every single incident—document the lessons learned.
One of the most valuable pieces of information that you have in the post-incident activity phase is the lessons learned. This will help you to keep refining the process through the identification of gaps in the process and areas of improvement. When an incident is fully closed, it will be documented, and this documentation must be very detailed, with the full timeline of the incident, the steps that were taken to resolve the problem, what happened during each step, and how the issue was finally resolved outlined in depth.
This documentation will be used as a base to answer the following questions:
- Who identified the security issue? A user or the detection system?
- Was the incident opened with the right priority?
- Did the security operations team perform the initial assessment correctly?
- Is there anything that could be improved at this point?
- Was the data analysis done correctly?
- Was the containment done correctly?
- Is there anything that could be improved at this point?
- How long did it take to resolve this incident?
The answers to these questions will help refine the incident response process and also enrich the incident database. The incident management system should have all incidents fully documented and searchable. The goal is to create a knowledge base that can be used for future incidents. Oftentimes, an incident can be resolved using the same steps that were used in the previous incident.
Another important point to cover is evidence retention. All the artifacts that were captured during the incident should be stored according to the company's retention policy, unless there are specific guidelines evidence retention. Keep in mind that if the attacker needs to be prosecuted, the evidence must be kept intact until legal actions are completely settled.
- 操作系統實用教程(Linux版)
- 從零開始寫Linux內核:一書學透核心原理與實現
- 大學計算機應用基礎實踐教程(Windows 7+Office 2013)
- Extending Puppet
- Windows Server 2012 Hyper-V Cookbook
- 玩到極致 iPhone 4S完全攻略
- 混沌工程實戰:手把手教你實現系統穩定性
- Linux自動化運維:Shell與Ansible(微課版)
- Dreamweaver CS5.5 Mobile and Web Development with HTML5,CSS3,and jQuery
- Kali Linux 2018:Windows Penetration Testing
- Linux網絡操作系統項目教程(RHEL 7.4/CentOS 7.4)(第3版)(微課版)
- Linux系統管理初學者指南:基于CentOS 7.6
- 鴻蒙HarmonyOS應用開發入門
- 樹莓派+傳感器:創建智能交互項目的實用方法、工具及最佳實踐
- Gradle Effective Implementations Guide(Second Edition)