Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Building the Hybrid Cloud
- Connected Government: How to Build and Procure Network Services for the Future
- Continuing Diagnostics and Mitigation: Discussion of Progress and Next Steps
- Federal Executive Forum
- Federal Tech Talk
- The Intersection: Where Technology Meets Transformation
- Maximizing ROI Through Data Center Consolidation
- Moving to the Cloud. What's the best approach for me
- Navigating Tough Choices in Government Cloud Computing
- The New Generation of Database
- Satellite Communications: Acquiring SATCOM in Tight Times
- Targeting Advanced Threats: Proven Methods from Detection through Remediation
- Transformative Technology: Desktop Virtualization in Government
- The Truth About IT Opex and Software Defined Networking
- Value of Health IT
Shows & Panels
NIST recommends new approach to cybersecurity
Thursday - 7/22/2010, 4:57pm EDT
Federal News Radio
Agencies have invested considerable resources on security at the systems level in response to escalating cyber threats.
An upcoming publication from the National Institute of Standards and Technology will recommend changing that by shifting to a three-tiered risk management strategy, according to Ron Ross, a senior computer scientist at NIST.
Ross spoke with Federal News Radio's Jason Miller at the Government IT Leadership Forum.
The document, 800-39, will integrate security and risk management from the strategic level at the top of the organization down all the way to the lowest level systems. It is currently in draft form and Ross expects it to be released in about two months.
According to Ross, most NIST publications have focused on security at the systems level but 800-39 will be, "the first serious discussion about what it means to have the three tiers: the governance layer where you talk about culture and about trust models and the risk management paradigm being implemented across the organization. And then tier two being an aggressive use of enterprise architecture and building security at that level."
Ross says that while agencies will continue to battle "endless vulnerabilities at the back end," effective use of enterprise architecture will help secure most system weaknesses and give agencies, "a hope of reducing some of those at the back end."
Aggressive use of enterprise architecture will focus on integrating security and privacy requirements into the architecture process. Ross says, "the approach is aggressive in the sense of making sure we get the right requirements early in the process instead of waiting until the system is already deployed and then we have to retro fit things. It never works as well, it's more costly and we don't get as much effectiveness out of it."
There are several multi-agency studies of the role of enterprise architecture in security. Ross says the Federal Enterprise Architecture Process is good but needs to be used more aggressively and hopes some of the NIST recommendations will be added to it.
The Office of Management and Budget recently upgraded the Federal Enterprise Architecture Security and Privacy Profile, a handbook on how to implement security and privacy at the enterprise architecture level. Ross expects the new profile to be released within the next month.
"We tried to craft a document that would be understandable to both security folks and enterprise architects and the privacy community. So when you start to develop a new information system coming out of your enterprise architecture these things will already be built into the process. You can't go forward and procure a new system unless those security and privacy requirements have already been defined and are part of the overall package going forward."
Ross also says the idea of agile defense will be described in 800-39, as well as in addendums to the ongoing document 800-37.
Agile defense assesses each threat's taxonomy; its capabilities, intentions, resources and targeting aspects, and creates a cyber security capability equivalent for each threat.
According to Ross, the new NIST documents do not specifically address upgrades in continuous monitoring because it has always been a part of the risk management framework; however, he expects continuous monitoring to move toward automation.
"It's not a replacement for anything," he says. "It's actually driving us forward to get better information in a more timely fashion."
(Copyright 2010 by Federal News Radio. All Rights Reserved.)