I suspect the mentality is "we are a research organisation we don't have to play by the rules" and it permeates from the top clear down to the maintenance staff.
Maybe their funding should be stopped until they get a passing grade!?!?
clearly NASA is 'over the moon' about information security -- lol
Yeah, well, similar attitude I saw when I worked with engineers and developers at a major multi-national. They all thought as they were "technical" people that a) they should get admin access to their systems and b) they were creative people and security just got in their way of doing their job.
When I work with clients in other industries, I see the same thing. In medical field, security "gets in the way" of doing whatever job they are doing, being creative, etc. Or security is "IT's responsibility", not theirs...
@emb021 wrote:Yeah, well, similar attitude I saw when I worked with engineers and developers at a major multi-national. They all thought as they were "technical" people that a) they should get admin access to their systems and b) they were creative people and security just got in their way of doing their job.
When I work with clients in other industries, I see the same thing. In medical field, security "gets in the way" of doing whatever job they are doing, being creative, etc. Or security is "IT's responsibility", not theirs...
My current customer is a DoD research group and same thing applies. Thankfully they were commanded to make IA happen so now they are dragging their feet and kicking pebbles trying to obstruct but at least it is moving forward.
@emb021 wrote:When I work with clients in other industries, I see the same thing. In medical field, security "gets in the way" of doing whatever job they are doing, being creative, etc. Or security is "IT's responsibility", not theirs...
Yes, very much a prevalent hurdle we security folks face. I've come to the conclusion/approach that more than anything this indicates how security/quality was not integrated from the beginning. It can help deflect the issue from "the problem is you" to "Hey, I need your help in fixing something that has been screwed up from the start." Organizationally, we should be integrating quality (I look at security as a function of quality) from the beginning in any process or role. Instead, we often sacrifice quality in order to capture market share. That's the tendency today - nearly every business model demands a certain scale to succeed. We no longer have the "start small, do it right, and build from there" model. The early days of NASA were all about working the problem (and even then we had some notable failures) but today, too many engineers, of any sort have been raised on the attitude of "we'll fix that with 2.0" Ask Boeing how that's going ....