A recent eWeek article “Cyber-security Hurts Federal Government Productivity, Survey Says” clearly demonstrates the significant security issues related to perception and communication. There seems to be a significant disconnect between what is thought to be needed to perform an agency’s mission and doing so without compromising computer systems.
“Surveyed federal executives believe that cyber-security policies and procedures should be modified to provide more emphasis on the importance of allowing federal managers to achieve their agency’s mission,” said Bryan Klopack, GBC’s director of research.
I get a two-for-one with this comment. First, it is apparent that federal managers don’t understand that a compromise of their agency’s computer systems will prevent them from delivering or performing their mission. Second, it seems as though policies and procedures are written in a vacuum without discussion with those the policy impacts.
There is no doubt that over-restrictive policies exist when it comes to web-site and e-mail access. Knee-jerk reaction usually leads to common sense being thrown out the window. That said, the threatscape has changed and there is real potential for systems to be compromised because of “choice failure” with e-mail and website use. Some system-wide protections simply need to be in place and inconvenience, by itself, is not a good enough reason to abandon good security practices.
In an editors note in SANS NewsBites, John Pescatore put it into perspective:
The blade guard on my power saw hampers my productivity in cutting wood, but chopping off my hand or even just a few fingers tends to also have an impact on my productivity.
The problem seems to stem from an over-reaction to a Presidential “mandate”.
President Obama signaled early in his administration that cyber-security in the federal government, especially in communications, and coordination, was a priority. “This status quo is no longer acceptable—not when there’s so much at stake. We can and we must do better,” he said.
Various agencies have responded to Obama’s mandate with their own rules.
Unilateral response to a “do better” mandate usually generates bad outcomes for everybody. This is what appears to have happened here. No communication. No requirements definition. Just a policy that is enforced through technology. Damn the torpedoes… full speed ahead!
What should be happening here?
First, business leaders (aka management) need to step up and gain some understanding that the threats they face could essentially grind productivity, and subsequently their mission, to a halt. It is no longer okay to say “this is the security group’s problem” and then walk away. Participation, horizontally and vertically throughout an organization, is required. Second, the security team needs to understand how people work, what they need to get their job done, and then work with them to find solutions.
It’s easier said than done but the status quo is indeed unacceptable. There is no such thing as 100% secure. There is, however, the potential to reduce risk while providing for business (or agency) needs. Without business, there is no need for security. Without security, business will fall victim to attack and fail. Contribution and collaboration is required to bridge this gap.
Based on this survey, I’m afraid we’re trying to cross Alaska’s Bridge to Nowhere.