Risk
1/4/2013
03:44 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

New Defense Budget Aims To Improve Cybersecurity

$633 billion package requires the Department of Defense to adopt next-generation cyber defenses and take new steps in secure software development.

Military Drones Present And Future: Visual Tour
Military Drones Present And Future: Visual Tour
(click image for larger view and for slideshow)
Cybersecurity and other information technologies play strong roles in the newly signed National Defense Authorization Act (NDAA) for fiscal year 2013, emphasizing the military's increasing reliance on IT.

The $633 billion package requires the Department of Defense to adopt next-generation cyber defenses and regularly report to Congress about its cyber efforts; includes guidelines on reporting cyber intrusions; and outlines steps that the military must take in software development and software licensing.

The NDAA does not take into account pending possible across-the-board cuts of DOD funds that will begin March 27 and reduce defense spending by hundreds of millions of dollars over the next 10 years if Congress fails to act by March 1.

[ To learn more about the government's cybersecurity efforts, read Congress Kills Cybersecurity Bill, White House Action Expected. ]

Key among the NDAA's tech guidelines are provisions dealing with cybersecurity and cyberwar. For example, the law instructs the DOD to "develop a strategy to acquire next-generation host-based cyber-security tools and capabilities" that go beyond current anti-malware and signature-based threat detection and instead can address "new or rapidly morphing threats."

These new technologies, the law says, must be installed in an open architecture that allows for multiple cybersecurity tools -- such as insider threat detection and continuous monitoring and configuration management -- to be added and integrated.

Other cyber provisions overhaul the software development process within the DOD, requiring the military to develop secure software development policy that does three things: Requires the use of static code analysis such as that performed by Veracode or a number of other code checking tools; prioritizes vulnerabilities based on risk; and ensures that secure software development is dealt with during the contracting phase of software development projects.

The DOD also must report to Congress quarterly on all the offensive and "significant" defensive military operations it carried out in cyberspace in the previous quarter. The NDAA notes that Congress expects to be briefed more widely on the activities of Cyber Command. Finally, under the law, contractors will be required to report successful penetrations to DOD.

Other broad IT requirements include DOD-wide IT initiatives. One such requirement could have a significant impact on how the DOD spends money on software by requiring an inventory of DOD software licenses and the development of a plan to assess how the military can "achieve the greatest possible economies of scale and cost savings in the procurement, use, and optimization of" those licenses.

The law requires the DOD to develop and submit to Congress a plan for a more consolidated IT infrastructure within the DOD known as the Joint Information Environment that will include milestones and metrics. It also requires the DOD CIO to study big data tools and submit a report on such tools to Congress.

The NDAA includes tech requirements for individual military services as well. For example, it requires the Army to review the Distributed Common Ground System (DCGS) -- a key operational IT system that deals largely with tactical and intelligence information -- and to issue plans for the system.

As for other services, the law will allow more open bidding on the Air Force's Network-Centric Solutions 2 (NETCENTS-2) acquisition vehicle. NETCENTS-2 was supposed to simplify big Air Force IT buys, but has been held up by vendor protests of contract awards.

Federal agencies must increase server utilization and energy efficiency as they squeeze more computer processing into fewer data centers. The new Data Center Optimization issue of InformationWeek Government explores how the Army, Homeland Security, Veterans Affairs and others are doing that. (Free registration required.)

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2004-2771
Published: 2014-12-24
The expand function in fio.c in Heirloom mailx 12.5 and earlier and BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an email address.

CVE-2014-3569
Published: 2014-12-24
The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 1.0.1j does not properly handle attempts to use unsupported protocols, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via an unexpected handshake, as demonstrated by an SSLv3 handshak...

CVE-2014-4322
Published: 2014-12-24
drivers/misc/qseecom.c in the QSEECOM driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate certain offset, length, and base values within an ioctl call, which allows attackers to gain privileges or c...

CVE-2014-6132
Published: 2014-12-24
Cross-site scripting (XSS) vulnerability in the Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3 through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 allows remote authenticated users to inject arbitrary web script or HTML vi...

CVE-2014-6153
Published: 2014-12-24
The Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3.x through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 does not set the secure flag for a cookie in an https session, which makes it easier for remote attackers to capture ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.