Risk
4/15/2010
02:07 PM
50%
50%

Senators Question Cyber Command Nominee

Gen. Keith Alexander told legislators he'll work closely with the president and Homeland Security to protect U.S. military networks against cyber attacks.

The Obama administration's candidate to lead the U.S. effort against cyber warfare assured lawmakers Thursday he can successfully balance the strategic military, technological, and cooperative aspects of the job he hopes to take on.

In his confirmation hearing Thursday before the Senate Armed Services Committee, Lt. Gen. Keith Alexander fielded questions about how he would perform in a position created only last year to perform a task some lawmakers themselves admittedly don't quite understand.

The Cyber Command, part of the U.S. Strategic Command, went into action in September specifically to protect Department of Defense networks and take charge of cyber warfare activities. It's based in Ft. Meade, Md., where the National Security Agency -- which Alexander currently leads -- is also headquartered.

The new command has raised concerns from lawmakers because it will act in the same territory as the NSA and the Department of Homeland Security, which are working as civilian agencies to protect U.S. networks against cyber attacks.

Senators have expressed concerns about the militarization of cybersecurity efforts, and some admitted Thursday during the hearing that they don't fully understand the scope of cyber warfare in the context of a military action.

In his opening comments Thursday, Alexander assured lawmakers that he won't overstep the boundaries of his role if confirmed to lead the Cyber Command.

"This is not about efforts to militarize cyberspace," he said. "Rather it's about safeguarding the integrity of our military system. My goal if confirmed will be to significantly improve the way we defend ourselves in this domain."

However, he said that his role would not merely be a defensive one, and that Cyber Command should mount offensive cyber attacks in the event of a cyber war.

Alexander said he would work alongside the DHS, in particular, to define the scope of his role and to develop strategies. The DHS is the government agency in charge of cybersecurity on U.S. soil.

Indeed, one of the trickiest issues lawmakers have been grappling with is the relationship between Cyber Command and the DHS. The DHS has been working with private companies that own most of that critical infrastructure to forge relationships and share intelligence, and ultimately is responsible for protecting networks at home.

However, Cyber Command would play a key role if there was a major attack from a foreign entity on critical networks, and Alexander was asked by the committee how he would juggle responsibilities.

"Our responsibility is to provide technical support to the DHS to help them build the technology they need to defend [critical] networks," he said. "I think that partnership continues to grow."

The committee posed to Alexander a hypothetical situation that described an attack coming from outside the country but routed through computers in the U.S., which would put it in the domain of the DHS and raise privacy concerns for U.S. citizens.

Alexander said in that case it would be necessary to coordinate efforts very closely with the DHS and the President himself, who would have the ultimate authority in that situation to act.

But this is one area he said that is not clearly defined by policy, which he said is still lacking to help the Cyber Command protect the DoD in the event of a cyber war. "That's one of the things the administration is trying to address," Alexander said.

Indeed, cybersecurity and cyber warfare policy has not evolved nearly as quickly as the threat the Cyber Command, DHS, and NSA are attempting to ward off. The House of Representatives only recently passed a cybersecurity bill while the Senate is currently considering one, but neither have gone into effect yet.

Alexander said the DoD network is hit with hundreds of thousands of probes a day that are attempting to detect vulnerabilities in the network, which is one of the reasons the Cyber Command was created in the first place.

"We have been alarmed by the increase, especially this year," he said. "It's growing rapidly."

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.