In Pentagon’s belated march to the cloud, DoD CIO looks to spark ‘national dialogue’ on cloud security

Pentagon CIO sees renewed vigor in DoD's cloud migration path as an opportunity to raise the bar for the nation's overall cybersecurity, telling vendors he want...

The Pentagon’s top technology official told vendors Thursday that DoD wants a much closer partnership with commercial cloud providers, and that the department is destined to put much more of its data into privately-hosted computing environments.

The cybersecurity worries that have made the military a reluctant adopter of cloud computing are far from resolved, so far. But Terry Halvorsen, DoD’s acting chief information officer, said his department is determined to overcome them. For starters, the department’s public-facing websites should be turned over to cloud providers post-haste, he said, and the military’s email services ought to be managed by IT firms who do that sort of thing for a living.

Terry Halvorsen, acting chief information officer, DoD
In the first of what he vowed would be many more industry engagements surrounding DoD’s use of commercial IT services, Halvorsen outlined the broad strokes of an agenda that would attempt not only to bring the department up to speed with cloud computing, but also seek to influence the way all cloud services — both public and private — are secured in the future.

As its own new starting point, DoD released a new security requirements guide two weeks ago which more clearly delineates its security demands from cloud service providers, and recognizes that not all data is created equal.

“What’s really the right level of security for things like financial data or personnel data? If we get those answers right, that’s way beyond just what we can use in DoD,” Halvorsen said. “All of you want your data to be secure too, and you in industry ought to be asking where your data is, because a lot if it is not very secure. If we can raise that national bar together, we can do it much more effectively and much more efficiently.”

DoD formally revised its approach to cloud security in a newly-published security requirements guide earlier this month, simplifying some of the demands the department imposes on cloud providers, streamlining some of its processes and aligning its procedures more closely with existing standards for cloud security. Cloud providers who have already met the governmentwide FedRAMP standards are eligible to handle DoD’s less sensitive “level 2” data without any additional security requirements.

For now, the department is requiring a DoD-only “FedRAMP Plus” certification process that adds more checks when vendors are dealing with more sensitive data. But Halvorsen said there’s no good reason it has to be that way forever.

“If we get FedRAMP Plus right, that ought to become no longer just our own ‘plus’ requirement, we could have a national standard that is not just for the government, but that applies to everybody,” he said. “It would say, ‘Okay, if you’ve got this type of medical data, this is the level of protection it needs.’ Commercial, government, academic, anyplace, we ought to have that that level of protection so that it’s not overprotected and it’s not overpriced. I think we can get a national dialogue started, and I think this group of people here can actually do that.”

The Defense Department has only a handful of companies in its catalog of approved cloud computing service providers so far. While it hopes the revised procedures will expand the crop, Halvorsen is also thinking a few steps ahead.

DoD’s path forward will require a shift in risk acceptance. In certain cases — like military installations’ mess hall menus and budget data from 1942 — the department is probably applying more security protections than the cost justifies, Halvorsen said. On the other hand, some providers will be taking care of genuinely relevant national security information, and that might require some innovative partnerships. Like letting companies build their data centers on military bases.

“I have still not taken off the table that at one point we might have a data distribution center that is mostly contracted, but inside a government installation where we provide the physical security,” he said. “We have some advantages there: most physical security people can’t roll tanks up to your building to help out. We can do that. Government does some things really well. How do we do that partnership? It takes some different thinking, it takes some different acquisition approaches.”

Speaking to reporters on the sidelines of the industry day, Halvorsen said that the private-data-center-on-government-facility approach is still just a notion. But he also sees it as one way to lower the overall cost of cloud computing while also increasing security.

“We’ve actually done some of that already, but not to the level I want,” he said. “In the department of the Navy, Hewlett Packard operates some of their own data centers inside federal space. The arrangement is good, but I’d like to push it bigger. For example, HP doesn’t store anybody’s data in there except ours. My model would say, ‘Why couldn’t HP do that, but make money by storing other companies’ data?’ If you’re a defense contractor, you really have to play by my rule sets. Maybe one of those contractors would like to put their data into one of those facilities that’s already in a very secure place. The other group I see that would want to do that is financial institutions.

We are not there yet, but that’s what we’re looking to push the model forward on.”

Before pulling off anything that bold, DoD needs to start with the basics, like putting policies in place that let it migrate meaningful quantities of data and processing capacity into commercial cloud environments. The security guide it published this month eased that process for data that’s already publicly releasable, and Halvorsen says that’s where DoD components need to start.

“This ought to be a no-brainer,” he said. “For all of us in the government, if we have data that we want to get to the public — our marketing and information exchange with the public — why wouldn’t we put that in a public cloud? The public might actually be able to see it then. One of our problems sometimes is we have public-facing data sitting in our own networks, but, small problem, the public can’t get to it. If you put that in a public cloud, not only do you get a cost advantage, you get some mission effectiveness right away.”

More mission effectiveness, officials say, because DoD’s owned-and-operated systems would be relieved from having to host and handle data that doesn’t need to be protected to the military’s high security standards.

“Pushing anything that’s public facing out to commercial industry really helps me out,” said Maj. Gen. Alan Lynn, the vice director of the Defense Information Systems Agency. “Because I really want to have a highly-secure platform for DoD, and the more I’m touching the outer surface of the Web with my networks, the more risk I take. So anything we can push out to the commercial space is a boon for our business.”

Beyond public websites, Halvorsen said DoD plans to start pushing a host of other less-sensitive computing responsibilities into commercial computing environments, including all of the department’s unclassified email.

DoD started consolidating many of its unclassified email systems into a single “enterprise email” system several years ago, but for now, it’s hosted and operated by DISA. Halvorsen has told the agency that the next version — Defense Enterprise Email 2.0 — needs to be an entirely commercial endeavor.

“I think that the commercial industry has certainly shown that they could do an unclassified email system at a lower price, and that shouldn’t surprise anybody,” he said. “Email is commoditized. So any time you can share in a commoditized environment, you’re going to drive down the price, and I think they’re at the point where they’ll be able to meet our security requirements. Again, I see the national cyber bar coming up, and I think that we’re such a big market that they’ll willing to adapt their security to meet our needs. I’m hoping this comes out to be 25 to 30 percent more efficient when we’re done.”

But Defense IT officials say they’re not standing still when it comes to incorporating cloud into hosting and processing needs for sensitive data. Under what the new security guide categorizes as levels 4, 5 and 6 information, cloud providers will have to interact with DoD-operated “cloud access points” that apply Pentagon security protections to data that moves back and forth between the cloud. Those access points don’t exist yet, aside from two pilot programs being run by DISA and the Navy. But Halvorsen says they’re coming soon.

“When I get that right, I actually further reduce my security problem,” he said. “Some of it is just about physical footprint. If I have fewer points where I connect to the broad commercial network, it’s easier to secure. DISA is moving very quickly — this is actually one place where I’m happy with the movement. We can’t tell industry the exact solution yet, we really have to make sure we’ve done the right threat analysis. But I suspect that within the next 90 days we’ll be able to start standing up the cloud access points.”

RELATED STORIES:

DoD rewrites cloud security rules in move toward risk acceptance

FedRAMP developing a FISMA high baseline in 2015

Army’s move to enterprise email kicked culture transformation into gear

Copyright © 2024 Federal News Network. All rights reserved. This website is not intended for users located within the European Economic Area.

    Pentagon Austin

    Pentagon finishes review of Austin’s failure to tell Biden and other leaders about his cancer

    Read more
    Congress Defense

    Big pay raise for troops in defense bill sent to Biden. Conservatives stymied on cultural issues

    Read more