The New Stack Podcast

How to Respond to Any Crisis (IT or Otherwise) in an Organized Way

Episode Summary

For this week's episode, we speak with Rich Adams, a senior engineer of security and incident response at PagerDuty. A few weeks back, PagerDuty released as open source the documentation for how organizations can set up a process for responding to incidents, including the establishment of a command center and the designation of an incident response leader. The guidelines are based on the company's own standard operating procedures for handling a crisis. In the second half of the show, we spoke to Kong co-founder Marco Palladino, about the end of what calls "software tribalism," as open source moves the industry to a hybrid world driven by developers, not software stack vendors.

Episode Notes

For this week's episode, we speak with Rich Adams, a senior engineer of security and incident response at PagerDuty. A few weeks back, PagerDuty released as open source the documentation for how organizations can set up a process for responding to incidents, including the establishment of a command center and the designation of an incident response leader. The guidelines are based on the company's own standard operating procedures for handling a crisis.

In the second half of the show, we spoke to Kong co-founder Marco Palladino, about the end of what calls "software tribalism," as open source moves the industry to a hybrid world driven by developers, not software stack vendors.