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 Future of Government Data Centers
- The Future of IT: How CIOs Can Enable the Service-Oriented Enterprise
- The Intersection: Where Technology Meets Transformation
- Maximizing ROI Through Data Center Consolidation
- Mitigating Insider Threats in Virtual & Cloud Environments
- Modern Mission Critical Series
- 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
- Air Traffic Management Transformation Report
- Cloud First Report
- General Dynamics IT Enterprise Center
- Gov Cloud Minute
- Government in Technology Series
- Homeland Security Cybersecurity Market Report
- National Cybersecurity Awareness Month
- Technology Insights
- The Cyber Security Report
- The Next Generation Cyber Security Experts
Shows & Panels
Intel community's fight against terrorism moves beyond connecting the dots
Thursday - 6/5/2014, 4:16am EDT
The intelligence community is moving from "connect-the-dots" to sharing some or all of the picture created by connecting those dots.
As part of this effort, a working group is developing data standards to ease the burden of understanding the picture the dots create.
"What we are finding is each agency or department sort of has their own view of the data they own and/or manage and exploit. What we are trying to do [is figure out] how do you harmonize that knowledge from one agency to another effectively, and how do you do it quickly, particularly in a time-sensitive situation?" said Dirk Rankin, the chief technology officer for the National Counterterrorism Center and the co-chairman of the Data Aggregation Working Group (DAWG), in an exclusive interview with Federal News Radio.
Rankin said the DAWG actually may have "stumbled" onto something where standards do not exist but are especially needed.
Given the niche that the working group is in, the three-year-old committee is putting together a series of tools and architectures to address this big data problem.
"The driving use case, is how do you quickly discern whether or not agency A knows X information about person Y and sharing that basic very high level. Just a quick scan, do we have anything on that individual across other elements of the U.S. government?" Rankin said. "I think if we had an ability to do that rapidly through machine-to-machine interactions and cloud technologies and so forth, given the security concerns and everything else that needs to be baked into that, we would have a much better chance as a government to prevent future negative events from happening."
Clear need for the DAWG
Recent terrorist attacks against the United States demonstrate just how far the work has to go.
Rankin said while there has been a lot of work on data standards and data interoperability over the last decade, there still are challenges in correlating data.
He said the Christmas Day bomber helped launch the DAWG, and the Boston Marathon attack reinforced the need for systems to communicate with each other.
Paul Reynolds, the other co-chairman of the Data Aggregation Working Group, said without data standards and system interoperability, it's much more difficult for the disparate databases to talk.
"We wanted to know very quickly what was going on and who was involved. From our perspective, there were a high number of people spending a lot of time working across different databases within different parts of the organization that I work for, who were not necessarily working together to try and get this single picture," said Reynolds, who has received approval to speak only on behalf of the working group, as long as he didn't identify his agency. "It took a lot longer than it should have, and it really doesn't need to. That's the thing. If we do this right, it doesn't need to take that much effort. What we want to do is we want to get the people who are good at thinking about these things and really solving the problems and really asking the tough questions … and bring them to the point where they have a base knowledge of the information. Then we are in a good spot."
He added the product of his agency's work then could be sent over to another intelligence or law enforcement agency in a matter of seconds to help complete the picture. Or the information could be "staged" at the end of the agency's domain space, where other officials could query on an as-needed basis.
Two pilots and a tool kit
The Information Sharing Environment brought together the Data Aggregation Working Group when these events proved an opportunity existed to improve data standards.
In its annual report to Congress from September and its more recent Strategic Implementation Plan for the President's National Strategy for Information Sharing and Safeguarding, the ISE listed data tagging and developing a reference architecture as major priority areas.
Over the last three years, the DAWG has made progress in exploring and bringing together data aggregation best practices, especially from the health and finance sectors.
The working group currently is reviewing industry responses to a request for information issued in March.
The RFI will help the DAWG identify what is working or what has potential to go into a data aggregation reference architecture.
"We primarily are focusing on data aggregation systems, those systems that do the consolidation of information and correlation. By focusing on data aggregation systems, what we want to do is we want to build out an environment where these systems are available and ready to talk to each other in this format," Reynolds said. "The first step in doing that is understanding where we are today, and part of the reference architecture is helping people figure out where they are from a maturity perspective, as far as those systems in particular go. Then we also, in this reference architecture, are building out a vision of where we want to go. We know it will take a while to get there. We also want to help people for this to be a tool. We want them to have a clear understanding at the end of this of where their system is, and they'll have an idea of where they could take their system. And at least they'll do it in the right direction of where the whole of government is going."