Government and information security–it really means two different things, and I’m going to break it down for you “Big Bird Stylie” as something I call the InfoSec Equities Issue.
If you’re like me, you have to be wondering the same things over and over again:
- Why is is that DHS has perpetually scored low on their FISMA report card and yet they are supposed to be leading the way for cybersecurity for the nation as a whole? (FYI, they got a B+ for FY 2007)
- How is it that the Government as a whole can have these gianormous data breaches ala the Veterans Administration and yet still claim to know how to help us secure our systems?
- Does the FTC really expect me to keep a straight face when I read OnGuardOnline?
Well fear not, dear readers, for this is the secret to understanding these conundrums: they’re actually different issues with a different funding trail. This budget difference, although a topic we security people shun whenever we can, is insanely critical.
For securing their own internal systems, the Government faces exactly the same problems that most companies have only amplified because of scale–security is a cost center, and cost centers get reduced wherever possible. Fudiciary responsibility to the taxpayers requires that the agency CISO’s staff do more with less, and that’s not a happy thought if you end up on the wrong side of the security budget equation.
Minimal Security photo by °Florian.
When it comes to security of external systems (and some national-level internal programs), the Government runs these as a program and offered as a service to the nation. Some typical programs include the following:
- Almost all of the National Cyber Security Division
- Department of Justice’s Computer Crime and Intellectual Property Section
- The National Infrastructure Protection Plan
- DHS’s Science and Technology Directorate
- And yes, even NIST’s FISMA Project
It’s one of Washington’s best-kept secrets: being a program manager in the Government means that you get a mission and a bag of money, and your job is to decide where to spend it all. This is the sweetest job and the one that you want whether it’s in security or any other discipline that you could image is a Government service–health care, law enforcement, or even the infamous “Gub’mint cheese”.
However, all is not peachy for programs. They can get cancelled based on political will and trends, so if your program ends up non-favorably in the Washington Post, you might end with your bag of money pilfered for other programs.
Heightened Security photo by robmcm.
This concept of divergent funding is all nice and neat except, dear readers, when the issues are not separate–ie, when an internal IT system protected by the internal budget supports a particular program. For example, consider the following scenarios:
- Security of vulnerability data at US-CERT (external) that resides on a Government IT system (internal).
- A financial system (internal) that tracks distributions to welfare recipients (external).
- A government website (internal) that supports awareness and training on security issues affecting individual citizens such as identity theft (external).
Now this is the concept behind the way Government is supposed to be running security programs: the internal funds pay for the centralized security and the funded programs pay for any level of security for IT systems that they sponsor.
But several catches:
- The system owner has to understand how to budget for or ensure that security for their program is budgetted for. Somewhere in there is an understanding of security risk.
- The system owner (who in theory has better funding and therefore better security) is dependent upon the centrally-managed security (which in theory has less funding and therefore worse security).
- Program-specific security comes out of the program, which means that higher security costs means that the program manager can’t spend money on the services they provide, which is where they really want to be spending it.
- A ton of negotiation is required to figure out responsibilities between the program manager and the CIO/CISO.
- If the agency takes too much money out of the program budget for security, we run into the same fudiciary responsibility problems in that we’re not managing our money properly.