Guest Blog // Selected Security Content Provided By Sophos
What's This?
06:08 PM
Dark Reading
Dark Reading
Security Insights

DoD's Bold Initiative: Secure The User, Not The Device

Joint Information Environment effort under way to improve its ability to share information between the services, industry partners, and other government agencies

Not all great ideas come out of the private sector. Occasionally some originate in the public sector. Or, as the following example shows, some are by-products based on partnerships between both.

The U.S. Department of Defense is planning the Joint Information Environment -- effectively a meaningful way to improve its ability to share information between the services, industry partners, and other government agencies. The Joint Information Environment will take all of those separate networks and collect them into a shared architecture.

As a Pentagon spokesman put it, information is meaningless unless it is delivered into the hands of those who need it. And because there are so many separate networks, information sharing isn't as efficient as it could be.

Sound familiar?

When it's complete, the Joint Information Environment will enable every user to get onto an approved device, from anywhere -- at home, at work, or on the move -- and get the information they need in a secure, reliable fashion.

The services will continue to support their own networks under the aegis of the Defense Information Systems Agency. The Joint Information Environment will eliminate redundancies in those networks, however. For example, instead of operating a parallel Army-only network for Army units that are stationed at a predominantly Air Force joint base, the Air Force will operate a single shared network for all personnel assigned to the base.

Developing the Joint Information Environment also involves moving toward DOD-wide services rather than every component buying, operating, and maintaining their own services, the Pentagon spokesman said.

"For example, rather than having every command operate their own email system, today the services have been combining those into a more efficient way of offering those things up at the service level," according to the DOD press release.

The enterprise email system, spearheaded by the Army, currently supports more than 550,000 users. The DOD intends to develop that system further by eventually providing every DOD user with an email address that is his regardless of command or location.

Ultimately, DOD users will have access to their email anywhere in the world, on any network operated by a DOD agency.

So let's regroup and figure out what this means for civilian information security professionals:

1. Enable every user to securely access data from any device, anywhere he is.
Hypothetically speaking, if you're working from home on your laptop and using your company's VPN to access your email, then switching over to your smartphone or BlackBerry to access your resources from the road, your ability to access information is seamless. In other words, it's no longer the device that becomes the first line of identity and authentication -- it's the user. Your policy and privileges follow you wherever you go regardless of the type of device used to access the network.

2. Authenticate users equally.
This is the ability for disparate divisions of the same company, even remote locations and offices of affiliates, agents, and partners, to be defined as a user in Active Directory and authenticated to the same shared network. I can't say conclusively whether the traditional VPN tunnels will be history given this type of environment (based on the Joint Base Air Force example of a shared network included in the press release, it seems likely), but, if so, it takes a lot of the upkeep and maintenance out of the equation.

3. Centralize users into a common directory.
As for security, sometimes centralization of users into a common directory like the kind suggested by the Joint Information Environment can actually be a positive development. Ultimately it requires fewer high-value IT staff of the DOD (in this case) to perform authentication checks and, as outlined in the press release itself, will allow the DOD to actually reduce the number of data centers over 10 years, from 1,500 to 250. It will also, of course, reduce infrastructure, such as computer systems, power supplies, and other equipment and applications required for their operation.

4. Achieve common ground.
Remaining data centers will share a common architecture and similar rate structure, again increasing the efficiency of the data center and, by default, how the data stored there is accessed, used, and accounted for.

5. Simplify services.
By reconfiguring how services are deployed (including email, natively developed DOD specific applications, etc.), including how they are operated, purchased, and maintained, the Joint Information Environment can help the DOD scale services based on an enterprise-wide model that's dependent on the number of users rather than the net number (or type) of devices.

Based on these outcomes alone, I think the implications presented by this technology are bold, even game-changing, both for the public as well as private sectors.

Brian Royer, a security subject matter expert, Sophos U.S., is partnering with SophosLabs to research and report on the latest trends in malware, web threats, endpoint and data protection, mobile security, cloud computing and data center virtualization.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Moderator
11/15/2012 | 2:27:22 PM
re: DoD's Bold Initiative: Secure The User, Not The Device
We have learned nothing from the anarchy of the last 5 years. Users/Machines compromised in the millions (especially consumers) and yet we still travel down this "BYOD" road towards fantasy land where the security of the endpoint doesn't matter. -áWe are either ignoring or pretending to have solved a problem that just keeps getting worse.
Register for Dark Reading Newsletters
White Papers
Current Issue
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-07-27
The kvm_apic_has_events function in arch/x86/kvm/lapic.h in the Linux kernel through 4.1.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by leveraging /dev/kvm access for an ioctl call.

Published: 2015-07-26
jquery_ujs.js in jquery-rails before 3.1.3 and 4.x before 4.0.4 and rails.js in jquery-ujs before 1.0.4, as used with Ruby on Rails 3.x and 4.x, allow remote attackers to bypass the Same Origin Policy, and trigger transmission of a CSRF token to a different-domain web server, via a leading space cha...

Published: 2015-07-26
The ff_mjpeg_decode_sof function in libavcodec/mjpegdec.c in FFmpeg before 2.5.4 does not validate the number of components in a JPEG-LS Start Of Frame segment, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via craft...

Published: 2015-07-26
Honeywell Tuxedo Touch before relies on client-side authentication involving JavaScript, which allows remote attackers to bypass intended access restrictions by removing USERACCT requests from the client-server data stream.

Published: 2015-07-26
Cross-site request forgery (CSRF) vulnerability in Honeywell Tuxedo Touch before allows remote attackers to hijack the authentication of arbitrary users for requests associated with home-automation commands, as demonstrated by a door-unlock command.

Dark Reading Radio
Archived Dark Reading Radio
What’s the future of the venerable firewall? We’ve invited two security industry leaders to make their case: Join us and bring your questions and opinions!