3 ms·
The government is a particularly painful place to do defense, but even in the commercial world, defense is pain and generally doesn't attract people who are as
by rdl 13y ago
The government is a particularly painful place to do defense, but even in the commercial world, defense is pain and generally doesn't attract people who are as "awesome" as offense. It tends to be more a conventional IT function, just implementing standards on existing stuff, mainly policy, etc. (NSA/DOD uses totally conventional computers for almost all of its work, so it's really "how to secure large Windows networks")
It's different when you're designing/implementing security for a new system which is very limited in scope (e.g. I would have loved to have been on the PAL design team for nuclear weapons) and very important/high profile. If you're doing anything else, it's much more a conventional IT job.
In the commercial world, it's kind of like how bitcoin (being disruptive, even if relatively undeveloped and toylike) is super popular, and is exciting, while no one is really super-enthusiastic about implementing x9.9898908098, ACH, etc.
I actually had no idea about there being different contractors on the offense side, since my contact has been really with the defense/customer side (which is shared with most of DOD). It's somewhat reassuring, as I wouldn't actually trust the "defense" people I've met with the level of information and access NSA obviously has.