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
Comments
Threaded  |  Newest First  |  Oldest First
'Hidden Tunnels' Help Hackers Launch Financial Services Attacks
Kelly Sheridan, Staff Editor, Dark Reading,  6/20/2018
Inside a SamSam Ransomware Attack
Ajit Sancheti, CEO and Co-Founder, Preempt,  6/20/2018
Tesla Employee Steals, Sabotages Company Data
Jai Vijayan, Freelance writer,  6/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12697
PUBLISHED: 2018-06-23
A NULL pointer dereference (aka SEGV on unknown address 0x000000000000) was discovered in work_stuff_copy_to_from in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. This can occur during execution of objdump.
CVE-2018-12698
PUBLISHED: 2018-06-23
demangle_template in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30, allows attackers to trigger excessive memory consumption (aka OOM) during the "Create an array for saving the template argument values" XNEWVEC call. This can occur during execution of objdump.
CVE-2018-12699
PUBLISHED: 2018-06-23
finish_stab in stabs.c in GNU Binutils 2.30 allows attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact, as demonstrated by an out-of-bounds write of 8 bytes. This can occur during execution of objdump.
CVE-2018-12700
PUBLISHED: 2018-06-23
A Stack Exhaustion issue was discovered in debug_write_type in debug.c in GNU Binutils 2.30 because of DEBUG_KIND_INDIRECT infinite recursion.
CVE-2018-11560
PUBLISHED: 2018-06-23
The webService binary on Insteon HD IP Camera White 2864-222 devices has a stack-based Buffer Overflow leading to Control-Flow Hijacking via a crafted usr key, as demonstrated by a long remoteIp parameter to cgi-bin/CGIProxy.fcgi on port 34100.