3 ms·
I think you're missing the point. The author is advocating for a well defined set of policies and procedures and users that understand and follow them. The po
by dsfyu404ed 11y ago
I think you're missing the point. The author is advocating for a well defined set of policies and procedures and users that understand and follow them. The point of this is to create an environment where the security people get the info they need (from users) to do their jobs and the infrastructure (including users and policies) are set up in a way that lets them do their jobs.
Big companies have a more to lose and deeper pockets so they're more likely to give big paychecks to security people. Regardless, few organizations pay anyone in support roles well, security is no different.
The main point is that you need users who aren't afraid to say "hey WTF is this?" and a system that can back that up by evaluating $this and taking appropriate action across the entire network.
Speed is key but the waterfall/agile models are way too simple to apply at a high level. The workflow bears more resemblance to this:
http://franklinstreetwebserver.com/wp-content/uploads/2010/04/Afghanistan-powerpoint-graphic.jpeg http://franklinstreetwebserver.com/wp-content/uploads/2010/0...
because you've got a different path of actions taken for each event and making the decisions at each point as quickly as possible is key but there's often so many moving parts that a very rigid set of procedures is needed to ensure consistency.
If someone's workstation crypyo-walls a network share there's how many different moving parts involved in the cleanup?