Cloud

3/23/2016
12:40 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

What The Feds Said At RSA

A look at some of the insights top US government officials from the White House, DoD, NSA, FBI, and other agencies shared at the RSA Conference in San Francisco last month.
Previous
1 of 9
Next

Source: iStock
Source: iStock

US government officials were all over the RSA Conference this year--many as guest speakers and panelists—including White House cybersecurity coordinator Michael Daniel, Secretary of Defense Ash Carter, and various officials from the Department of Homeland Security, the FBI, NSA, and the US Secret Service.

If there was one theme that their talks and comments had in common, it was that they were all keen on demonstrating a more open government that really gets that it must partner with the cybersecurity industry. That means declassifying and sharing more of its own threat intelligence, working more closely with organizations hit by cyberattacks (and before they’re in full incident response mode), and closer ties to the researcher community.

As Defense Secretary Ash Carter put it when announcing the department's unprecedented bug bounty pilot at the RSA Conference, DoD technologists need to “think outside the five-sided box.”

Here’s a look at what some of the federal government officials said at RSA that shows they may well be thinking outside the Nation’s Capital in their cybersecurity policies and efforts.

 

 

Interop 2016 Las VegasFind out more about security threats at Interop 2016, May 2-6, at the Mandalay Bay Convention Center, Las Vegas. Click here for pricing information and to register.

 

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Previous
1 of 9
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/27/2016 | 11:33:37 AM
New Dept?
I wonder if Daniel's (et al.) comments suggest a paving of the way for a Department of Cybersecurity or something of the like (which, at this point, I'm not sure is a bad idea; DoD and Homeland could certainly stand to have some help).
Microsoft President: Governments Must Cooperate on Cybersecurity
Kelly Sheridan, Staff Editor, Dark Reading,  11/8/2018
To Click or Not to Click: The Answer Is Easy
Kowsik Guruswamy, Chief Technology Officer at Menlo Security,  11/14/2018
Veterans Find New Roles in Enterprise Cybersecurity
Kelly Sheridan, Staff Editor, Dark Reading,  11/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Online Malware and Threats: A Profile of Today's Security Posture
Online Malware and Threats: A Profile of Today's Security Posture
This report offers insight on how security professionals plan to invest in cybersecurity, and how they are prioritizing their resources. Find out what your peers have planned today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19279
PUBLISHED: 2018-11-14
PRIMX ZoneCentral before 6.1.2236 on Windows sometimes leaks the plaintext of NTFS files. On non-SSD devices, this is limited to a 5-second window and file sizes less than 600 bytes. The effect on SSD devices may be greater.
CVE-2018-19280
PUBLISHED: 2018-11-14
Centreon 3.4.x has XSS via the resource name or macro expression of a poller macro.
CVE-2018-19281
PUBLISHED: 2018-11-14
Centreon 3.4.x allows SNMP trap SQL Injection.
CVE-2018-17960
PUBLISHED: 2018-11-14
CKEditor 4.x before 4.11.0 allows user-assisted XSS involving a source-mode paste.
CVE-2018-19278
PUBLISHED: 2018-11-14
Buffer overflow in DNS SRV and NAPTR lookups in Digium Asterisk 15.x before 15.6.2 and 16.x before 16.0.1 allows remote attackers to crash Asterisk via a specially crafted DNS SRV or NAPTR response, because a buffer size is supposed to match an expanded length but actually matches a compressed lengt...