SecurityCertified

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, March 19, 2010

Time and Cost to Defend the Town

Posted on 6:19 PM by Unknown

Recently I guest-blogged on the importance of learning how another person thinks. This week I had a chance to apply this lesson with a new decision maker. I learned that I need to develop a way for this executive to think about our security program. I discussed the situation with my wife and she suggested focusing on cost. I thought about this a little more and realized that was the right way to approach the problem.

Consider the following scenario. You're the mayor of a town. You need to decide how much of your budget to allocate to the fire department. To apply the most simplistic analysis to the problem, consider this scene. As mayor you give the fire chief a simple goal: "protect us from fires!" The fire chief asks you: "Mayor, on average, how fast do you want the fire department to respond to a fire?"

I am not an expert on fighting real fires, but let's think about a range of some possible answers.

  • Option 1. Instantly. Literally as soon as a fire is detected, fire fighters are on site. Assume this level of response produces the maximum level of containment and preservation of property value, on average.

  • Option 2. Within 15 minutes. Assume this level of response produces 75% containment and preservation of property value, on average.

  • Option 3. Within 30 minutes. 50% containment and preservation of property value, on average.

  • Option 4. Within 45 minutes. 25% containment and preservation of property value, on average.

  • Option 5. Within 60 minutes. It's too late. With this timing, the property value is destroyed.


As mayor you're likely to first reach for option 1. After all, you want to preserve property value. However, the fire chief says "maybe you should consider the following data."

  • Option 1 costs $64 million. Fire fighters are deployed at 16 locations.

  • Option 2 costs $32 million. Fire fighters are deployed at 8 locations.

  • Option 3 costs $16 million. Fire fighters are deployed at 4 locations.

  • Option 4 costs $8 million. Fire fighters are deployed at 2 locations.

  • Option 5 costs $4 million. Fire fighters are deployed at 1 location.


At this point you're starting to sweat. There has to be a way out of this situation! You decide that you can't afford option 1, or 2, or probably even 3. The recession is hitting your town hard. You ask the fire chief if there's a way to reduce the number of fires expected to occur, so that a smaller fire fighting force can react more quickly to fewer fires.

The fire chief switches from his fire fighter role to that of fire marshall. He says that is certainly possible, if the mayor wants to pick from one or more of the following options.

  • Rebuild dwellings using fire-resistant materials.

  • Inspect and rewire electrical systems, including aggressive, persistent monitoring for faults.

  • Deploy advanced fire, smoke, and related alarms everywhere.

  • Remove flammable materials from dwellings.

  • Educate citizens on fire hazards.

  • Ensure all citizens know how to contact the fire department, and have the means to do so efficiently and effectively.

  • Plus a dozen more options...


You are probably getting the hang of this scenario. At this point the mayor needs to know the cost of each of the fire resistant methods outlined above. Let's not forget one other element: the fire chief asks the police chief to inform the mayor of the arsonist threat, and describes how dedicating counter-threat activities can deter and detain adversaries who set dwellings ablaze.

At the end of the day, the fire chief is presenting options to the mayor, and it's up to the mayor to decide how fast do we want to be able to respond to the fires that will happen, for how much cost.

(I underline the "fires that will happen" because that is the reality of life. Disasters happen, so you have to plan for them.)

For me, this is the best way to approach this executive. The fire chief doesn't get to decide how much money to spend on the problem. That's the mayor's decision. The mayor needs to make a budget choice, preferably with the fire chief's input, and then let the fire chief make the best resource allocation to meet the time goals requested by the mayor.

For me, time and cost are the best levers we can move in digital security. I can measure detection and response time for the incidents we handle. I can track how much money I am spending to meet those time requirements. If the mayor wants faster response time, the mayor can try to reduce the number of fires via fire marshall programs and/or apply more resources to the fire fighters.

Beyond measuring incident detection and response for real intrusions, you can use red teaming/adversary simulation to create metrics. You can say "for the money currently spent on our security resistance program, it takes a Red Team X number of minutes to accomplish Goal X. Is that acceptable?" If X minutes is unacceptable, you can again present cost-benefit analysis in order to derive a decision.

If you think you've heard this line of reasoning before (outside this blog), please check whether the other advocates have emphasized outcomes as I do here and elsewhere. I'm not saying "spend $10 million to achieve 95% patch compliance." That's an input metric. I'm talking about output metrics against real intrusion activity and adversary simulations.
Email ThisBlogThis!Share to XShare to Facebook
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Happy 7th Birthday TaoSecurity Blog
    Today, 8 January 2010, is the 7th birthday of TaoSecurity Blog . I wrote my first post on 8 January 2003 while working as an incident resp...
  • Report on Instances of US Forces Abroad
    Thanks to Steven Aftergood's post Instances of US Forces Abroad I learned of a new Congressional Research Service report of the same na...
  • Security Conference Recommendations
    After my post Bejtlich Teaching at USENIX Security in San Francisco 8-9 Aug a reader asked the following: Richard, I was curious if you cou...
  • I Want to Detect and Respond to Intruders But I Don't Know Where to Start!
    "I want to detect and respond to intruders but I don't know where to start!" This is a common question. Maybe you have a new...
  • Security Onion + (ELSA or Snorby) + CapMe = Awesome
    Happy New Year everyone, and with some new open source software, what a year it will be. Monday Doug Burks released Security Onion 12.04 . P...
  • With "Cyber" Attacks, Effects Matter More Than Means
    I enjoyed reading Stuxnet Poses Interesting International Cyber Law Issues by Rick Aldrich in IAnewsletter Vol 14 No 2 (pdf). I've kno...
  • "Protect the Data" from the Evil Maid
    I recently posted "Protect the Data" from Whom? . I wrote: [P]rivate citizens (and most organizations who are not nation-state ac...
  • Review of Digital Triage Forensics Posted
    Amazon.com just published my two star review of Digital Triage Forensics: Processing the Digital Crime Scene by Stephen Pearson and Richard...
  • Unrealistic "Security Advice"
    I just read a blog post (no need to direct traffic there with a link) that included the following content: This week, I had the opportunity ...
  • Does This Sound Familiar?
    Now that over a week has passed since this Economist article was published, I wanted to cite it and ask if the problem it describes sounds ...

Categories

  • afcert
  • Air Force
  • analysis
  • announcement
  • apt
  • attribution
  • bestbook
  • blackhat
  • books
  • breakers
  • bro
  • bruins
  • certification
  • china
  • cisco
  • cissp
  • cloud
  • clowns
  • commodore
  • conferences
  • controls
  • correlation
  • counterintelligence
  • cybercommand
  • cyberwar
  • dfm
  • education
  • engineering
  • feds
  • fisma
  • freebsd
  • GE
  • ge-cirt
  • hakin9
  • history
  • impressions
  • information warfare
  • ipv6
  • law
  • leadership
  • malware
  • mandiant
  • microsoft
  • mssp
  • nsm
  • offense
  • oisf
  • packetstash
  • philosophy
  • pirates
  • powerpoint
  • press
  • psirt
  • reading
  • redteam
  • reviews
  • russia
  • sans
  • sec
  • sguil
  • snorby
  • spying
  • threat model
  • threats
  • Traffic Talk
  • training
  • tufte
  • tv
  • ubuntu
  • usenix
  • verizon
  • vulnerabilities
  • wisdom
  • writing

Blog Archive

  • ►  2013 (16)
    • ►  September (1)
    • ►  August (1)
    • ►  June (2)
    • ►  April (2)
    • ►  March (1)
    • ►  February (3)
    • ►  January (6)
  • ►  2012 (60)
    • ►  December (4)
    • ►  November (5)
    • ►  October (3)
    • ►  September (10)
    • ►  August (2)
    • ►  July (6)
    • ►  June (6)
    • ►  May (4)
    • ►  April (2)
    • ►  March (9)
    • ►  February (6)
    • ►  January (3)
  • ►  2011 (108)
    • ►  December (3)
    • ►  November (7)
    • ►  October (11)
    • ►  September (9)
    • ►  August (18)
    • ►  July (10)
    • ►  June (5)
    • ►  May (4)
    • ►  April (13)
    • ►  March (17)
    • ►  February (2)
    • ►  January (9)
  • ▼  2010 (193)
    • ►  December (14)
    • ►  November (11)
    • ►  October (6)
    • ►  September (16)
    • ►  August (15)
    • ►  July (26)
    • ►  June (15)
    • ►  May (15)
    • ►  April (15)
    • ▼  March (16)
      • GE-CIRT Joins FIRST
      • Bejtlich in April Wired Magazine
      • Bejtlich Returns to PaulDotCom Podcast
      • Ways to Justify Security Programs: 13 Cs
      • Forget ROI and Risk. Consider Competitive Advantage
      • Time and Cost to Defend the Town
      • Guest Post on SecureThinking about Cyber Shockwave
      • Verizon Incident Sharing Framework
      • Bejtlich Keynote at VizSec 2010
      • Bejtlich OWASP Podcast Posted
      • Traffic Talk 10 Posted
      • Einstein 3 Coming to a Private Network Near You?
      • Making a Point with Pressure Points
      • Keeping FreeBSD Applications Up-to-Date in BSD Mag...
      • Bejtlich Teaching at Black Hat EU and USA 2010
      • Bejtlich to Speak at FIRST 2010
    • ►  February (19)
    • ►  January (25)
  • ►  2009 (123)
    • ►  December (10)
    • ►  November (17)
    • ►  October (21)
    • ►  September (13)
    • ►  August (20)
    • ►  July (21)
    • ►  June (21)
Powered by Blogger.

About Me

Unknown
View my complete profile