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

6/18/2020
10:00 AM
Chris Triolo
Chris Triolo
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

CISO Dialogue: How to Optimize Your Security Budget

CISOs are never going to have all the finances they want. Hard choices must be made. The CISO of Amazon Prime Video discusses his approaches to a slimmed-down budget.

It's unavoidable: New projects require budgets. To justify the expense, any budget spent on new technology needs to be designed to lower the risk profile. Or the problem might be an inefficiency in the program that can be better addressed with new technology. So, how can CISOs understand how best to optimize their limited pool of security budget? I sat down with Brett Wahlin, the CISO of Amazon Prime Video, to discuss the topic.

"There are many different approaches to managing a security budget, and CISOs organize and prioritize uniquely based on the company, industry, and threats. Three consistent areas of spending are identity and access management (IAM), global risk and compliance (GRC), and security operations," Wahlin told me, noting:

  • IAM is always a mess because no one wants to deal with access management, passwords, access sprawl, and so on.  
  • GRC is difficult because there are always new regulations to remain compliant with; privacy, in particular, is an ongoing challenge.
  • With security operations, levels of effectiveness vary. Wahlin posed several questions for consideration. "Is it in-house? Are you outsourcing to an MSSP? How are you measuring effectiveness? It's an area where I often have to retool from a people, process, and technology standpoint."

Budget allocation should shift to address these problems. Wahlin's trick to shift budgets to new priorities? Find money in existing budgets through optimization — such as replacing humans with software, moving operating expenditures to capital expenditures. "If I can automate an activity with software and repurpose human resources, that's a powerful money-saving step," he said.   

ROI? No So Fast
ROI is a legitimate business concern, but Wahlin generally discourages the idea of ROI as a gauge of cybersecurity success. Referencing ROSI, return on security investment, Wahlin said ROI alone is a vendor-driven metric. "It makes the assumption that you can place a value on an asset that is out of your control and that you can measure a loss and a probability of occurrence."

Still, CISOs want to save wherever they can. Security operations and monitoring is an opportunity for replacing head count with software, which Wahlin has done. "If you automate your Tier 1 security analysts, you can free up head count and save budget," he said. "Plus, the analysts who remain will have a much better job experience. They won't be staring at events on a screen but doing more meaningful, satisfying work."

SOAR and SIEM: Worth It?
Some organizations wonder if security orchestration and response (SOAR) tools are worth the engineering upkeep. "I think it's promising. When I look at getting efficiencies out of a SOC, I have to look at events, correlate, and then determine what needs to be done," Wahlin said. "Your SOAR is only as fast as the individual making a decision. Automate the decision and the SOAR will operate better." 

Wahlin continued, "As for [security information and event management (SIEM)], I used to feel that it was necessary to build a SOC because teams had to collect alerts from a diverse number of sensors and reduce them to meaningful incidents to investigate. I now find my opinion changing." A next-generation SIEM can take all the alerts from the sensors directly and make decisions on those alerts, and then you don't have to store them in the SIEM.

Top Tips for New CISOs
Wahlin concluded with a breakdown of the most important things he would recommend a new CISO look at, both budgetary and beyond:

  • Look at the three most problematic areas: IAM, GRC, and SecOps. You can always find things to fix, and it will give you some quick wins.
  • Know your industry and how your security program can help the company grow.
  • You need to be able to constantly communicate the value you're bringing to the table — it's how you'll get budget and, more importantly, it's how you keep it.
  • "Partnering with the business" is not just a catch phrase batted around at security conferences. Learn what it means for your company and be a good partner.
  • Think like an architect: As you build a program, how do the different functions interact with each other? How do you plan to grow based on shared communication? 
  • Don't be afraid to pull something out if it's not raising the security bar for your company.     

CISOs are never going to have all the finances they want. Hard choices need to be made — choices that will determine your entire organization's security posture. Diagnose what needs immediate attention and work from there. Your priorities will help you see where you can save money by making changes in other areas, such as using automation to reduce head count. These best practices will help you build a solid security foundation that optimizes your budget.  

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's featured story: "What's Anonymous Up to Now?"

Chris Triolo's security expertise includes building world-class professional services organizations as VP of Professional Services at ForeScout and global VP of Professional Services and Support for HP Software Enterprise Security Products (ESP). Chris' depth in Security ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/17/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25789
PUBLISHED: 2020-09-19
An issue was discovered in Tiny Tiny RSS (aka tt-rss) before 2020-09-16. The cached_url feature mishandles JavaScript inside an SVG document.
CVE-2020-25790
PUBLISHED: 2020-09-19
** DISPUTED ** Typesetter CMS 5.x through 5.1 allows admins to upload and execute arbitrary PHP code via a .php file inside a ZIP archive. NOTE: the vendor disputes the significance of this report because "admins are considered trustworthy"; however, the behavior "contradicts our secu...
CVE-2020-25791
PUBLISHED: 2020-09-19
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with unit().
CVE-2020-25792
PUBLISHED: 2020-09-19
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with pair().
CVE-2020-25793
PUBLISHED: 2020-09-19
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with From<InlineArray<A, T>>.