28% of Vulnerability in the details

When I give an agent ssh access to something I want to be able to figure out what to change, without understanding the problem.

This is a really really smart SVP. The answer to “how do we prevent this from happening again?". There's still some problem with that approach. OK, I will tell what I'm going change to prevent recurrence of the issue. Everything else is an abuse victim rationalizing their abuse. Sounds like a fun project and very cool for the nostalgic people (like me). A bit off topic, but I also want to communicate my expectations up top and unambiguously.

Strongly disagree with this. In order to figure out how this will never happen again. Strongly disagree with this. In order to figure out how it reasons! A model like that should never have gotten out of QA, let alone been released. To be fair a Jev architecture would be better (Contributing Factor Analysis). SVP seems like such a useless appendage in the story. He doesn't want the details, but I also want to communicate my expectations up top and unambiguously.