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.
This is an interesting comment because I would have thought that defense and offense would be fairly symmetrical. Is the asymmetry due to lack of interest in defense? Is it because it's easier to break things then to keep them from breaking? E.g. it's much easier to teach someone to shoot well than it is to teach someone to heal a bullet wound.