IC IS: Moving Forward
This is not an insignificant development (PDF):
A groundbreaking new policy from the Office of the Director of National Intelligence changes how the intelligence community and, by influence, the entire federal government will build, validate and approve information technology systems. The policy requires common security controls and risk-management procedures – a unified approach to enhance collaboration.
Intelligence Community Directive 503 covers a lot of ground, but two key details stand out: There will be a single certification and accreditation process, which means all systems must follow the same authorized security requirements. Systems managers, the policy adds, should accept security risks when necessary to yield a decision advantage from timely and accurate intelligence.
Those measures will make it easier for the IC to adopt cutting-edge technology. They also foster reciprocity as well as information sharing. If one IC element certifies a system or major application, then others in the community can trust that it is secure without spending more time and money to duplicate tests.
There is, in effect, a uniform standard for background checks and security clearances. Has been for some time. Yet every agency still imposes additional burdens and caveats that make one’s clearance largely un-transferable without forcing someone to jump through additional, often flaming, hoops.
Now before you get on my case about this being “a contractor problem,” I would note that this impacts feds going from one agency to another as well. The pain is universal, expensive, and detrimental to mission accomplishment.
So here is the thing to watch for: If you still read stories in GCN or FCW a year from now about differing standards or accreditation issues you’ll know ICD 503 is never going to live up to the promise and that we’ve squandered another practical reform effort for the sake of parochialism.
Hoping for the best …
