I don't work on security, but I have worked with security. The [lack of] operational maturity of security software and skills required to administrate it, part

I don't work on security, but I have worked with security. The [lack of] operational maturity of security software and skills required to administrate it, particularly at scale, and particularly administration of the data stores are almost certainly one of security's larger pain points. Security often keeps itself separate-ish from production itself, so "who administrates the data stores for security systems, the data store expert overloaded with dealing with making the website function, or the security expert who knows a lot about security and not very much about data stores or operations?" Another major pain point is controlling the signal to noise ratio and therefore determining the risk to toil (sisyphusian manual labor) ratio. > the systems themselves decide to mitigate issues, propagate patches (or even vaccines for zero-days) and also share incidents that look suspicious, so the surrounding nodes can start to quarantine themselves off Are we talking production machines or employee machines? If you are referring to the former, I will yell at you. I have gotten people fired for doing that type of thing cowboy style. It's one thing to flag a machine as requiring administration by the people who understand it, it's another to administrate someone else's machines, particularly when they are on call for it. What does mitigate, patch, or propagate mean in terms of actual example of administrative action? For that matter what does peer to peer mean?