4 ms·
How will this even work? Will he tell his company's developers to develop software that will protect against all the vulnerabilities he learned about while bein
by mtgx 11y ago
How will this even work? Will he tell his company's developers to develop software that will protect against all the vulnerabilities he learned about while being the head of NSA and hacking into everyone's networks? That seems...wrong somehow?
- lotharbot 11y agohe'll probably spend a lot of time having the devs write software based on DoD standards. It's surprising how much of security is "make sure you've configured everything correctly".
- qb45 11y agoIt's surprising how much of security is "make sure you've configured everything correctly". Or "don't accept ' or 1=1 -- as a password", for that matter. Internet-facing web system with several thousand users, just a year ago or so. Made me feel like I'm back in the '90s.
- bqe 11y agoThere's nothing inherently wrong with that password as long as your code isn't vulnerable to SQL injection, which is trivial to do nowadays.
- qb45 11y agoSure SQL injection is trivial to do nowadays; it's always been. I mean, of course I meant this was an SQL injection.
- dragonwriter 11y agoI'm pretty sure GP was saying making sure your code isn't vulnerable to SQL injection is trivial to do nowadays, not that SQL injection is trivial to do.
- rylee 11y agoIt's trivial to not be vulnerable to SQL injection.
- thephyber 11y agoThat's not what "trivial" means. Trivial means the simplest possible example, which in almost every web framework involves passing input as received to the DB driver without knowing its contents and without escaping/sanitizing it. Only by using frameworks and DB drivers correctly (RTFM) is one able to accurately avoid SQLi. I would argue that "using software correctly" is by no means trivial and rarely happens in most systems that have less than NASA quality safeguards. I would agree that most modern frameworks which are adopted by at least a few hundred developers tend to use best practices and a "security by default" mindset, but that's far from saying that "avoiding SQLi is trivial".
- pyre 11y agoThis: > "don't accept ' or 1=1 -- as a password" (the way that it's stated) implies that one should be checking input for possible SQL injection attacks and dropping the request, rather than sanitizing input so that the attack doesn't work, but the password is valid.
- nickpsecurity 11y agoI'm guessing he'll just apply stuff they developed in NSA for NIDS, patch deployments, etc. Just a good HIPS (esp whitelisting) and patching knocks out 75% of so-called APT's per Australia's DSD. Good monitoring catches many of the rest eventually. Those by themselves, combined with NSA's improvements, would dramatically improve security for organizations that had little of it but lots of money. Probably sells them on an image and liability benefit, too: "bank shouldn't be liable because we even went so far as putting former director of NSA in charge of our security. What more could we have done!?" Trying to counter liability in courts or with lobbying is main security model for big business. So, something like this is undoubtedly a benefit.
- jka 11y agoPrediction: They'll build tools/services which are broadly similar to existing security technologies (IDS / log analysis / etc) and then their sales team will mention - at opportune moments - that they have an ex-NSA founder who oversees the technology. If pressed there probably won't be a huge amount of details on what extra security / insight that might provide vs their competitors, but there'll be implicit suggestions that it's because what he knows is classified and nation-state level and that it actually filters down to the way they design and implement the services. Is there real magic technology previously unknown to security that they'll be able to add? And would it be wise to expose it via a small startup if so? Personally doubt both, but probably doubt the former more so. Meanwhile a basic product will develop, sales will flow, it's probably a safe-ish bet for the early investors/founders, the sun will continue to rise in the east and set in the west, etc.
- uptown 11y ago"Will he tell his company's developers to develop software that will protect against all the vulnerabilities he learned about while being the head of NSA" Not only what he learned while he was there; it seems his original plan was to continue to receive a steady stream of intelligence info even after he'd left: https://fcw.com/articles/2014/10/22/nsa-cto-moonlight-gig-ends.aspx https://fcw.com/articles/2014/10/22/nsa-cto-moonlight-gig-en...
- samstave 11y agoWhen this info first came out - I was under the impression that he was going to have fairly exclusive access to license some tech that the NSA had made - and a bunch of people balked at this as NSA is technically a public entity and as such, should not preclude anyone else from gaining access to the same IP -- further, it was argued that as a public entity they should not be charging fees to access the IP.
- Bedon292 11y agoI am going to bet that he doesn't actually know the details of any of those vulnerabilities. He was the head of the entire agency, not a technical guy. He probably know that something was done, but not how it was implemented on a technical and usable level.