4 ms·
Learning new skills in InfoSec without getting overwhelmed
- solipsism 8y agoThis article isn't about infosec at all. Instead it gives some general advice for avoiding analysis paralysis and choosing from among many options.
- debatem1 8y agoSecurity is about doubting what you're told, productively. Anyone who tells you otherwise should be doubted-- productively. If you build security tools, verify that they actually work. If you write exploits, doubt every correctness claim until proven. If you make policy, assume ill intent until proven otherwise. These are the iron rules. Knowing where to look or to care comes with experience. In the meantime, ask questions.
- lobotryas 8y ago> assume ill intent until proven otherwise What does this even mean? This sounds more like being a roadblock to everyone else because you can say “but what about the security” and everyone has to dance to your tune.
- jodrellblank 8y agoAssume the user's search term or form data is going to contain SQL injection attempts. Design to handle that. Assume the person calling up to reset a password is trying to access someone else's account, so make them prove their identity before resetting a password. Assume employees will go poking around internal fileshares where they shouldn't have access, and design ACLs to keep them out. and everyone has to dance to your tune. Good. Developers who don't dance to that tune are responsible for headline after headline after headline of valuable user data being accessed, stolen, or leaked, and should risk having their professional software development licenses revoked and companies being fined by watchdogs.
- thrower123 8y agoThis sort of thing is exhausting if you have to keep it up unsupported. Being the negative nancy that keeps pointing out the holes in other peoples' grand plans earns you no kudos.
- pixl97 8y agoDepends who you are leaking the holes to. Negative Nancy probably makes a living selling said flaws to foriegn governments these days because no one will listen to them.
- debatem1 8y agoA team I used to work with closely had a process where if a development team didn't think an issue was important enough to fix and release the security team was encouraged to find other buyers for the vuln. It was actually a pretty great way to both keep people on the same page and keep your security folks tethered to reality.
- closeparen 8y agoWhich is why security should be primarily a software development team offering high-quality, safe-by-default libraries and services. Instead of "you idiots failed to consider authorization" it becomes "here are the onboarding instructions for our authorization system, and here's your language's client."
- debatem1 8y agoIf you're unsupported it's both exhausting and pointless. If you're lightly supported, IMO it's generally better to fight the long fight for stronger support than to spend political capital on specific bugs or design flaws.
- crispyambulance 8y ago> [devs who don't heed to security primacy] should risk having their professional software development licenses revoked and companies being fined by watchdogs. But there is no such thing as a "software development license". Is that just naive wishful thinking? I mean, do you think that the way to secure systems is layer after layer of pain-in-the-ass red-tape and heavily silo-ed organizational structure? Instead of just forcing people to "dance to your tune" perhaps a more cooperative approach is better?
- debatem1 8y agoI'll get to what I meant in a moment, but first... I'm not sure what you think a security team should do, honestly. Security teams exist because your management has a cross-cutting concern and needs people to represent that concern on the ground. If they don't do that they aren't doing their job. So if they have a security concern they should say "but what about the security". If everyone then has to dance that tune, it should suggest to you that your management thinks they have a point. In terms of what I meant, security policy is rife with areas where you have to decide "is this borderline behavior acceptable". Your default answer to that should be "no", basically because otherwise your policy will grow too complicated to reason about quickly.
- zcw100 8y agoYes, you’re a pretty little snowflake. Unique among the wold. No other profession or field has to suffer the hardships you have to suffer. Get over yourself. Everyone has has this problem. Many people don’t even have a name for what they do. You have conferences, educational curricula including at the university level, professional organizations, etc