Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operations

3/11/2016
10:30 AM
Ben Johnson
Ben Johnson
Commentary
Connect Directly
Twitter
RSS
50%
50%

‘Must Haves’ & ‘Must Dos’ For The First Federal CISO

Offensive and defensive experience, public/private sector know-how, 'mini-NSA' mindset and vision are top traits we need in a chief information security officer.

So far this year, cybersecurity news is everywhere. And it includes some major announcements that are a welcome change from the dismal stories about huge data breaches that we read about far too often. President Obama requested a budget increase in cybersecurity spending. DHS revealed it will begin sharing threat intelligence with private companies. And, perhaps most significantly, the White House announced it would hire the first federal CISO. This is fantastic news!

So let’s look at what will be necessary for this significant new position to have the greatest chance of success (and not be yet another disappointment in the realm of federal information-security Initiatives).

Whoever the president chooses for this job is going to be a contentious pick. This person will be the first to serve in the role and will be highly visible during a time when major data breaches are an everyday occurrence. Breach fatigue has already largely set in (I already have four free credit monitoring services—how many do I need?). Expectations for the first federal CISO will be high. So what should the resume look like for anyone seeking the position? Here’s my thinking:

Hands-on offensive and defensive cyber-security experience: It’s hard to make well-informed decisions that impact millions of computer systems if you have never had to attack (as part of security testing) and defend systems yourself.

Intelligence community experience: Every cyber-defense team is like a mini-NSA for their organization—collecting information, processing it, “fusing” it together to make it actionable, etc.

Private and public sector experience: The federal government is a tough place to navigate if you have no experience dealing with it, so you’ll definitely need some of that. But private industry is always pushing the envelope, is innovating faster in cyber-defense tools and processes, and requires leaders who can handle dynamically changing environments.

Vision: The federal CISO will attempt to set policy and focus on huge gaps—both current and future—so he or she must be a visionary.

Let’s assume we find a great choice for federal CISO (and I expect we will). What should he or she focus on?  Two of the major themes from the federal initiative revolve around two of my most serious gripes with the state of information security: poor IT hygiene and an extreme shortage of qualified cyber defenders. If the new CISO did nothing but improve these two areas, we would have an order of magnitude improvement in the nation’s security. But we need more than that: The federal CISO needs to also focus on seven other key areas:

  1. Visibility: Keep cyber (and cyber successes) in the spotlight.
  2. IT hygiene: Identify outdated systems and reduce what must be defended. There are always systems that can be retired or that are exposed to the Internet but should not be.
  3. Fill our ranks: Identify common skill gaps across agencies and grow cyber leaders.
  4. Education: Implement a program to subsidize cybersecurity education for the general public and create career paths for them into federal roles (e.g., a Cyber GI Bill).
  5. Increase salaries: Attract the best and brightest to be cybersecurity experts in the public sector.
  6. Transparency: Require government agencies and departments to share what tools they’re using, what their incident response plans are, what attacks they are seeing, and their results from penetration tests, product evaluations, and more.
  7. Private industry partnerships: Create a private industry steering committee to reduce friction in the procurement process.

This is an exciting time to see the Obama administration pushing hard to improve our cyber defenses. The fact is, we are not winning the cyber war. Cybersecurity in the U.S. and the world is actually quite bleak. But by improving funding, hiring the right leadership, and putting the right amounts of transparency and agility at the top of the new CISO’s to-do list, we can turn the ship around.  

Related Content:

 

Interop 2016 Las VegasFind out more about security threats at Interop 2016, May 2-6, at the Mandalay Bay Convention Center, Las Vegas. Register today and receive an early bird discount of $200.

Ben Johnson is CTO and co-founder of Obsidian Security. Prior to founding Obsidian, he co-founded Carbon Black and most recently served as the company's chief security strategist. As the company's original CTO, he led efforts to create the powerful capabilities that helped ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
NSA Appoints Rob Joyce as Cyber Director
Dark Reading Staff 1/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Hunny, I looked every where for the dorritos. 
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8567
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver Vault Plugin prior to v0.0.6, Azure Plugin prior to v0.0.10, and GCP Plugin prior to v0.2.0 allow an attacker who can create specially-crafted SecretProviderClass objects to write to arbitrary file paths on the host filesystem, including /var/lib/kubelet/pods.
CVE-2020-8568
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver versions v0.0.15 and v0.0.16 allow an attacker who can modify a SecretProviderClassPodStatus/Status resource the ability to write content to the host filesystem and sync file contents to Kubernetes Secrets. This includes paths under var/lib/kubelet/pods that conta...
CVE-2020-8569
PUBLISHED: 2021-01-21
Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when: - The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass. - The snapshot-controller crashes, ...
CVE-2020-8570
PUBLISHED: 2021-01-21
Kubernetes Java client libraries in version 10.0.0 and versions prior to 9.0.1 allow writes to paths outside of the current directory when copying multiple files from a remote pod which sends a maliciously crafted archive. This can potentially overwrite any files on the system of the process executi...
CVE-2020-8554
PUBLISHED: 2021-01-21
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typicall...