@frgx Totally agree. Have you ever done a big program scale “go delete surface area” stuff? I’ve only done it adhoc typically as the result of a point audit or cluster of vulns
Golden opportunity to convert this vulnpocalypse hype into properly funding vuln mgmt (the least exciting, often most lacking part of a security program)
This is our chance as an industry!
@frgx A flight with no internet + this pleasant nerdsnipe = this long answer: https://t.co/FNCOMvceYc
I'm organizationally sheltered but in a big company the above is what I think ideal looks like
@ZackKorman@IceSolst Enjoyable writeup. I feel the same way about the paperwork theater of compliance stuff. I felt slightly better when I accepted that security != compliance and just think of it as a different thing https://t.co/qVEb7GDWtT
@intoverflow Extremely cool. I've long harbored a dream of a coffee table hacking tales book with the benefit of full knowledge + hindsight of 10 interesting breaches or events or something. If this project is that, I want to read it even more!
The differences between performing privacy and security work in a big company for my fellow computer security people.
https://t.co/xdQRy9ExwB
I'm still newer to privacy work so this is my "most likely to be wrong" writeup, feedback welcome
@philvenables Agree with you.
A thing I haven't sorted yet, what is the optimal amount of compliance effort to spend, your post made me finish a post about that: https://t.co/qVEb7GDWtT
@jeffvanderstoep Good writeup. Agree that vuln prevention > discovery > response.
Curious about
1. How is "old" vs "new" code designated?
2. How is a specific vuln connected to only old or new code? Or am I misunderstanding
3. No counterfactual here right? ex to find/fix vulns in the old code
@dinodaizovi I like this so much.
This fundamental uncomfortable truth then has weird side effects
1. Buy more snake oil products, because it can't hurt!
2. Use this compliance framework, to at least CYA
3. Build cool stuff, because its fun and pseudo-justifiable.