Session Name: Incident Retrospectives as Code
The incident is not done when it is remediated, it is done when the retrospective ("post-mortem") is done. Blameless retrospectives are now table stakes for any organization. But what about consistency? What about long-term research?
How do you make sure the timeline is consistent? That all action items have tickets? Use the same tools you use everywhere else: source control and continuous integration!
Moving incident retrospectives to code is as important as moving your infrastructure to code: a whole world of automation and analysis opens up.
Speaker Bio:
Moshe has been using open source software since 1995 and has been using Python as his main development language since 1998. He has been a contributor to CPython, is a founding member of the Python Software Foundation, and a founding member of the Twisted project.
.png?width=610&name=J1_ModernCybersecurityBook_Promo%201200x628%20v2@2x%20(1).png)
