| ▲ | How to Break into Security, Ptacek Edition (2012)(krebsonsecurity.com) | |||||||||||||
| 57 points by ronfriedhaber 2 hours ago | 14 comments | ||||||||||||||
| ▲ | liquid_oil an hour ago | parent | next [-] | |||||||||||||
Reading a post from 2012 like this it's shocking how quickly the ladder has been pulled up in all computer careers, but I suppose it's not as bad as the ladder pull from the dotcom bubble to 2012 where you could previously land a career "knowing HTML". | ||||||||||||||
| ||||||||||||||
| ▲ | sorentwo an hour ago | parent | prev | next [-] | |||||||||||||
Marking this as 2012 would help. It’s a fun read in a nostalgic, pre-ai kind of way, where emphasizing that developers should use bcrypt wasn’t standard practice. | ||||||||||||||
| ▲ | david_shaw 13 minutes ago | parent | prev | next [-] | |||||||||||||
I'm often asked how to turn a security-related interest or hobby into a job. For the longest time, I'd say pretty much the same thing written here: get a book, do some research, build some projects, talk to people in industry. I've been going to DEF CON for about 25 years now, and I've had this conversation countless times. But in 2026, tptacek says it best in the comments here: At this point, who knows? Are we still telling kids to learn programming languages to become software developers? Perhaps system design is a more reasonable skill set. That said, because this is the time to say it: security is still important, and it's not -- and shouldn't be -- fully automated. The toolchain is changing just like it always has. I remember when interpreted languages replaced compiled ones, and people said that interpreters solved security. Then people went from writing their own codebases to implementing frameworks, and people said it solved security. Barracuda Networks posters at every airport stated "Security Solved." As long as people take risks, security is important. Now we just need to focus on designing resilient systems instead of finding bugs and vulns on the code-level. LLMs can do that part for us. | ||||||||||||||
| ▲ | j-scott 2 hours ago | parent | prev | next [-] | |||||||||||||
(2012)? | ||||||||||||||
| ||||||||||||||
| ▲ | bryant an hour ago | parent | prev | next [-] | |||||||||||||
tptacek may disagree, but this needs an update considering how much has changed both with AI and the economies of scale AI brings to the discipline. I'm anticipating "the fundamentals are crucial," and as much as I want to agree, I think practical realities show us otherwise. We're at a point where all someone needs to know is how to AI-program-manage and how to glean enough about the discipline (or any discipline at this point) from AI to be dangerous enough in the field. To be a builder, breaker, or defender wearing any color hat of their choosing... that's it, really. | ||||||||||||||
| ||||||||||||||
| ▲ | smashandgrab 33 minutes ago | parent | prev | next [-] | |||||||||||||
I hire for incident response roles. Honestly, despite how much has changed this is still the way to do it for us. You need to be versed in many things and more importantly, interested enough to not feel entirely stressed out when things hit the fan. As for AI it’s been great for things like log review but those were already pretty low skill requirements. We haven’t had much luck past that. | ||||||||||||||
| ▲ | dzonga an hour ago | parent | prev | next [-] | |||||||||||||
it would be interesting to know what tptacek's thoughts are in the age of 'agents' violating vulnerabilities willy-nilly ? if his thoughts of getting into application security still apply. what the incentives are since hacking seems to be no longer a crime given how many hacking incidents have gone unpunished. | ||||||||||||||
| ||||||||||||||
| ▲ | tptacek an hour ago | parent | prev [-] | |||||||||||||
At this point, who knows? | ||||||||||||||
| ||||||||||||||