>Any time anything security relevant incident happens, you could make a private Slack channel named for the incident. This might be a good start, but it makes

>Any time anything security relevant incident happens, you could make a private Slack channel named for the incident. This might be a good start, but it makes me a little uncomfortable. In a true incident, there is a metric ton of stuff that I would not want to be discoverable. I like to set aside an area with locked-down access to keep the truly toxic material found during a serious incident. And for startups or other small companies reading this--the things mentioned here should not be a big deal or take enormous time to do. The earlier you do what is recommended in the post, the happier everyone will be. I'm reminded of my Dad's saying: Tires are like insurance: When you need it, it is too late. [edit typo]