🏛️ Issues and Advocacy Training™
Courses › Large Organization Security Programs, Governance and Compliance™

Lesson 2 of 14 · about 55 minutes · Updated November 15, 2026

Budgets, Staffing and the Business Case

You'll be able to

  • Describe what organizations spend on security using named surveys and forecasts, and explain why benchmarks mislead when used as targets.
  • Identify the main cost components of a large security program and where they often sit in other departments' budgets.
  • Explain what 23 NYCRR Part 500, the FTC Safeguards Rule, the HIPAA Security Rule and SEC Item 106 say about security resources.
  • Build a business case that states risk in dollars with ranges, using FAIR and the Gordon-Loeb ceiling, and use breach-cost studies with their caveats.
  • Compare build, buy, managed and co-sourced options and plan a tool consolidation review.
  • Explain how public sector security is funded, including the State and Local Cybersecurity Grant Program's history and status through 2026, and plan staffing, hiring and retention.

Start here: the short version

  • Large organizations typically spend around a tenth of their IT budget on security. In the 2025 IANS Research and Artico Search benchmark of 587 chief information security officers, security averaged 10.9 percent of IT spending and 0.69 percent of revenue, and budgets grew only 4 percent, the slowest in five years.1 Treat any benchmark as a conversation starter, not a target.
  • The world market keeps growing anyway. Gartner forecast worldwide end-user security spending of $213 billion in 2025 and about $240 billion in 2026, with security software the largest and fastest-growing piece.2
  • People are the biggest line. Staff and compensation took 39 percent of the average security budget in the IANS data, software 29 percent and outsourced services 12 percent.1 The ISC2 2025 workforce study found 59 percent of security teams reporting critical or significant skills shortfalls, and almost half of professionals saying they feel exhausted.3
  • A good business case is about risk in dollars, not fear. Estimate how often a loss could happen and how much it would cost, show how the proposed spending changes those two numbers, and compare the change with the price. Industry breach-cost averages (IBM's 2025 study put the U.S. average at $10.22 million) are a starting point with real limits, not a forecast for your organization.4
  • Several regulators make resources a governance duty. New York's 23 NYCRR Part 500 tells the board to confirm that management has allocated sufficient resources, and the FTC Safeguards Rule requires qualified security personnel sufficient to manage the risk.56
  • Public agencies face a different calendar and a shrinking federal cushion. The $1 billion State and Local Cybersecurity Grant Program from the 2021 infrastructure law made its last scheduled award in 2025 ($91.75 million with a 40 percent local match), and its authority has lapsed and been extended several times since.7

Rules, standards and data described: 23 NYCRR Part 500 as amended effective Nov. 1, 2023; FTC Standards for Safeguarding Customer Information, 16 CFR 314.4 (amended 2021 and 2023); HIPAA Security Rule, 45 CFR 164.306 (current eCFR); SEC Regulation S-K Item 106 (17 CFR 229.106, adopted 2023); NIST SP 800-181 Rev. 1, the NICE Workforce Framework for Cybersecurity (November 2020); the State and Local Cybersecurity Grant Program at 6 U.S.C. 665g as created by the Infrastructure Investment and Jobs Act (Pub. L. 117-58, Nov. 15, 2021), its FY2025 funding notice (July 28, 2025) and reported extensions through 2026; the FAIR Standard Version 3.0 (FAIR Institute, Jan. 15, 2025); IANS and Artico Search benchmarks (2025), Gartner forecasts (July 2025 and September 2026), ISC2 workforce studies (2024 and 2025) and the IBM and Ponemon Institute Cost of a Data Breach reports (2025 and 2026). All read Nov. 15, 2026. Rules, appropriations and survey results change every year; check the current text and the newest edition before relying on any figure.

Before you change anything. Plan changes to production systems, test them first, keep a way back, and follow your change management process. For clinical, plant-floor or other safety systems, involve the vendor, your safety lead and qualified engineers (see modules 109 and 111).

The budget meeting usually happens in the fall. The chief financial officer has a spreadsheet with every department's request, and the total is higher than what the organization can afford. The chief information security officer is asking for a 14 percent increase: two more security analysts, a replacement for an end-of-life firewall cluster, a new tool to watch cloud accounts, a bigger budget for outside penetration testing, and the insurance broker's warning that next year's cyber premium will depend on proving the backups cannot be deleted by an intruder. The chief financial officer asks the question every CISO should be ready for: "If I give you this, what do we get, and what happens if I give you half?"

This lesson is about answering that question honestly. It covers what organizations actually spend and where the money goes, what the law says about resources, how many people the field has and what they cost, how to build a business case that a finance team will respect, when to build, buy or hire a service, how public agencies fund security through appropriations and grants, and how to hire and keep people without burning them out. It ends with a sample budget request.

It builds on Risk Management in Plain Terms, which teaches the risk register, heat maps and the FAIR quantitative method, and on Running the Program in the small business module. The program structure that this budget pays for is in lesson 1; the metrics that show whether the money worked are in lesson 3; insurance, one of the larger outside costs, is in lesson 9.

What organizations spend

Three kinds of numbers get quoted in budget meetings: the size of the world security market, the share of an organization's IT budget or revenue that goes to security, and the cost per employee. Each answers a different question, and each comes from a survey or a forecast with its own methods. Name the source and year every time you use one.

The world market

Gartner, the research firm, publishes forecasts of worldwide "end-user spending on information security," meaning what buyers pay for security software, services and network security equipment. Its July 29, 2025 release put 2024 spending at about $193.4 billion, 2025 at about $213 billion and 2026 at about $239.8 billion, a projected 12.5 percent increase. Security software was the largest segment at a forecast $121.2 billion in 2026, security services next at $92.8 billion, and network security equipment at $25.8 billion. Gartner's analyst attributed the growth to "higher defense budgets, rising threats, increasing regulatory pressure and better cybersecurity awareness," with cloud security and artificial intelligence as the main drivers.2

Gartner revises these forecasts each quarter. A summary of its third-quarter 2026 forecast (published Sept. 24, 2026), written by an independent analyst blog because the full Gartner document is behind a paywall, reported 2025 actual spending of about $217.7 billion and a 2026 forecast of about $247.5 billion, up 13.6 percent in current dollars, with spending reaching about $373 billion by 2030.8 The direction is the same in every edition: steady double-digit growth, led by software sold as a subscription.

The market number is useful for one thing in a budget meeting: it shows that vendors' prices and the number of products are both rising, so a flat security budget is a shrinking one in real terms. It says nothing about what your organization should spend.

Share of the IT budget and of revenue

The most widely quoted benchmark for large private organizations is the annual Security Budget Benchmark from IANS Research and Artico Search, a research firm and an executive search firm. The 2025 edition surveyed 587 CISOs in the United States and Canada from April to August 2025. It found:1

  • Average budget growth of 4 percent in 2025, down from 8 percent in 2024, the lowest in the five years the survey has tracked.
  • 47 percent of CISOs received an increase, down from 62 percent in 2024 and 78 percent in 2022; 39 percent had flat budgets.
  • Security averaged 10.9 percent of total IT spending, down from 11.9 percent in 2024 but well above 8.6 percent in 2020.
  • Security spending averaged 0.69 percent of company revenue, roughly flat.
  • Staff and compensation were 39 percent of the security budget, software 29 percent and outsourcing 12 percent.

The IANS sample leans toward larger companies with a dedicated CISO who chose to answer, so it describes organizations that already take security seriously. Industry matters a great deal: financial services and technology companies spend more of their revenue on security than manufacturers or retailers with thin margins, and a hospital's share is shaped by how much of its IT is run by its electronic health record vendor. IANS publishes industry cuts of the same data for its clients.

Public sector spending

State governments spend a much smaller share. The 2024 Deloitte and NASCIO Cybersecurity Study, a survey of the chief information security officers of all 50 states and the District of Columbia released Sept. 30, 2024, found that more than a third of state CISOs had no dedicated cybersecurity budget line at all, and that four of the 51 said their state put less than 1 percent of its IT budget toward security. NASCIO noted that federal agencies generally earmark more than 10 percent. Staffing had improved: the share of state CISOs with fewer than five dedicated security staff fell from 16 percent in 2020 to 4 percent.9

Federal civilian agencies report their cyber spending to the Office of Management and Budget, which publishes the totals each year in the "Management" chapter of the President's budget, the Analytical Perspectives volume. The fiscal 2027 edition (April 2026) includes a table of estimated civilian cybersecurity spending by agency and another that sorts the CFO Act agencies' cyber funding by NIST Cybersecurity Framework function.10 In July 2025 reporting on the fiscal 2026 request, the administration proposed cutting civilian cyber spending by about $1.23 billion, roughly 10 percent below 2024 levels, including about $500 million from the Cybersecurity and Infrastructure Security Agency (CISA); the House Homeland Security appropriations bill advanced that June instead provided CISA $2.74 billion, about $146 million below 2025.11 The final fiscal 2026 numbers depend on appropriations acts enacted after that reporting; read the current Analytical Perspectives tables before quoting a total.

Why benchmarks mislead

A CFO who hears "peers spend 10.9 percent of IT on security" may conclude that an organization at 9 percent is underfunded, or that one at 12 percent is overspending. Neither follows. Four problems recur:

  • Definitions differ. One company counts identity management, backup, logging storage and the help desk's password resets as security; another counts them as IT. Moving a tool between budgets changes the ratio without changing protection.
  • The denominator moves. If IT spending falls because the company moved to cloud services, the security share rises with no new security. If a company grows revenue fast, its security share of revenue falls.
  • Spending is not outcome. The number says what was bought, not whether it was configured, monitored and used. Many of the breaches in the common mistakes section below happened at organizations with large security budgets.
  • Survivorship and self-selection. Surveys hear from CISOs who answer surveys. Organizations with no CISO, which are often the least funded, are underrepresented.

Use benchmarks to start a conversation ("we are below the middle of our industry; here is why that may be a risk") and then move to the organization's own risks and gaps, which is where the rest of this lesson goes.

What the money buys: the cost components

A security budget in a large organization has six main parts. Each has its own driver, and each is often split between budgets owned by different executives. A CISO who can show where every dollar sits, including the dollars in other departments' budgets, has a far easier conversation with finance.

ComponentWhat is in itWhat drives the costWhere it often hides
PeopleSalaries, benefits, bonuses, contractors, recruiting fees, certifications and training for the security staffHeadcount, local labor market, on-call and 24-hour coverage, specialty skills (cloud, OT, application security)Security engineers who sit in IT, privacy staff in the general counsel's office, application security staff in engineering
Tools and platformsEndpoint detection and response, identity and multifactor authentication, email security, security information and event management (SIEM), vulnerability scanning, cloud security, data loss prevention, backup protectionNumber of users, devices, cloud workloads and data volume; most tools are priced per user, per device or per gigabyteLicenses bundled in the IT productivity suite; log storage paid by the cloud team
ServicesManaged detection and response, penetration testing, incident response retainers, consulting, virtual CISOHours of coverage, scope of testing, retainer sizeRetainers bought by the general counsel's office or through the insurer's panel
InsuranceCyber insurance premium, deductible reserves, broker feesRevenue, industry, claims history and the controls underwriters ask about (lesson 9)Risk management or treasury budget
Audits and assuranceSOC 2 reports, ISO 27001 certification, PCI DSS assessments, FedRAMP or CMMC assessments, internal audit's IT auditsNumber of frameworks, scope, how many products or business units are in scopeCompliance, finance or internal audit budgets; product teams paying for their own SOC 2
Training and awarenessPhishing simulations, role-based training, tabletop exercises, executive briefingsNumber of employees, regulatory training requirementsHuman resources or the compliance office

People

People are the largest share in every survey and the hardest cost to cut quickly. A 24-hour security operations center needs about five to six full-time people for each seat that must be filled around the clock, once vacations, training, sick days and turnover are counted, which is why many large organizations buy overnight and weekend monitoring from a managed service even if they staff the day shift themselves. That staffing multiple is a common planning rule of thumb rather than a published standard; check it against your own schedule and leave policy. Recruiting a senior specialist can take months and a recruiting fee, and losing one costs the knowledge of how the organization's systems actually fit together.

Pay for the top job has risen faster than budgets. IANS and Artico reported on Nov. 13, 2025, from a survey of 566 CISOs in the United States and Canada (April to October 2025), that CISO compensation rose an average of 6.7 percent in 2025; average total compensation was $844,000 in the technology sector and $744,000 in financial services, and the top 1 percent earned more than $3.2 million.12 Those are figures for large companies, mostly including equity; a county, a school district or a regional hospital pays a small fraction of that and competes for the same people.

Tools and platforms

Tools are where budgets grow quietly. Most security products are now sold as annual subscriptions priced per user, per device, per cloud workload or per gigabyte of data. That means a merger, a hiring wave or a move of systems to the cloud raises the security bill automatically. The biggest single surprise in many budgets is log data: a SIEM that charges by the volume of data it takes in can double in cost when the organization turns on cloud logging that regulators or insurers asked for. Ask every vendor what the price will be at 150 and 200 percent of today's volume before signing a three-year contract.

Services, insurance, audits and training

Outsourced services were 12 percent of the average budget in the IANS data.1 They include managed detection and response, testing, and the incident response retainer that lets the organization call a forensic firm at 2 a.m. without negotiating a contract first. Insurance premiums, audits and certifications are often paid from other budgets, which is one reason the security share of IT can look low. A company that holds a SOC 2 report, an ISO 27001 certificate and a PCI DSS assessment pays for three separate audit engagements plus the internal staff time to gather evidence for them; lesson 4 covers mapping one control to many rules so the evidence is gathered once, and lessons 5 and 6 cover the reports themselves.

The budget split in one picture

Where the average security budget went, 2025 587 CISOs, United States and Canada, IANS and Artico Search benchmark Staff 39% pay, benefits, contractors Software 29% subscriptions, licenses Services 12% Other 20% not broken down "Other" usually holds hardware, insurance and audit fees paid by security, training and travel. Many costs sit outside the security budget: identity and backup in IT, retainers in legal, premiums in risk management, certifications in compliance. Count them before comparing. Shares are survey averages, not a recommended mix.
The average split of a large organization's security budget in 2025. Original graphic for this module; data from the IANS Research and Artico Search 2025 Security Budget Benchmark (published Aug. 5, 2025). The "other" share is the remainder after the three categories IANS published and is not broken down in the public summary.

What the law says about resources

No U.S. law tells a private organization to spend a set percentage on security. Several rules do make adequate resources part of the duty, which changes how a budget cut should be documented.

  • New York DFS, 23 NYCRR 500.4. For covered banks, insurers and other licensees, the senior governing body must oversee the cybersecurity program and "confirm that the covered entity's management has allocated sufficient resources to implement and maintain a cybersecurity program." Section 500.10 requires qualified cybersecurity personnel, the entity's own or a vendor's, sufficient to manage its risks.5 A board that approves a cut in the security budget without a record that it asked whether resources remain sufficient has a hard time showing it met this duty.
  • FTC Safeguards Rule, 16 CFR 314.4. Non-bank financial institutions (mortgage brokers, auto dealers that finance, tax preparers, payment processors and many others) must name a Qualified Individual to run the program, use qualified information security personnel "sufficient to manage your information security risks," keep them current through training, and have the Qualified Individual report in writing to the board at least once a year.6
  • HIPAA Security Rule, 45 CFR 164.306(b). Covered entities and business associates may choose security measures by considering their size and complexity, their technical capabilities, "the costs of security measures," and the probability and criticality of risks.13 Cost is a legitimate factor, but only after a risk analysis; HHS enforcement has repeatedly treated the absence of a risk analysis as a violation regardless of budget (see the risk analysis lesson in module 109).
  • SEC Regulation S-K Item 106. Public companies must describe in the 10-K how they assess and manage material cyber risks and how management and the board oversee them, including the relevant expertise of the people responsible.14 Item 106 does not require a budget figure, but a company that describes a mature program in its 10-K while starving it in practice invites the kind of disclosure claims covered in Governance, Boards, Officers and Disclosure.

Bank regulators take the same line in examinations: the Office of the Comptroller of the Currency's $80 million penalty against Capital One in August 2020 cited the bank's "failure to establish effective risk assessment processes" before moving significant operations to the public cloud and its failure to correct the problems in time, not any specific tool it lacked.15 The lesson for budget owners is that a regulator judges whether resources matched the risk the organization took on, and a business decision that expands risk (a cloud migration, an acquisition, a new product) should carry its own security cost.

A Seattle City Light worker at an accounting machine in 1954
A Seattle City Light worker at an office machine in 1954, described on Commons as an IBM accounting machine. Budgets have always been built on records of what things cost. Photo: Seattle Municipal Archives. Wikimedia Commons, CC BY 2.0.

The workforce numbers

The claim that there is a huge shortage of cybersecurity workers appears in nearly every budget request. The numbers behind it are real but need careful reading, because they measure different things.

ISC2 workforce studies

ISC2, the nonprofit that issues the CISSP certification, runs the largest annual survey of security professionals. Its 2024 study, based on 15,852 respondents surveyed in 2024, estimated a worldwide "workforce gap" of 4.8 million, up 19 percent from the year before, and a U.S. gap of 504,307, up from 482,985 in 2023. It estimated the active North American workforce at about 1.45 million. The gap is ISC2's estimate of how many more people organizations say they would need to be fully staffed, so it rises when budgets are tight as well as when demand grows.16

The 2025 study (16,029 respondents, surveyed July and August 2025, released in December 2025) changed emphasis. It did not publish a headline gap figure and instead focused on skills. Its findings:3

  • 95 percent of respondents had at least one skills need on their team, and 59 percent reported critical or significant skills needs, up from 44 percent in 2024.
  • Only 34 percent said their organization had the right level of staffing.
  • 36 percent reported budget cuts in the past year, 24 percent layoffs and 39 percent hiring freezes; 31 percent expected more cutbacks in the next 12 months.
  • 48 percent said they feel exhausted from trying to keep up with threats and new technology, and 47 percent said they often feel overwhelmed by their workload.
  • 28 percent had integrated AI security tools and another 41 percent were testing or evaluating them; 73 percent expected AI to create more specialized security roles.

Read together, the two studies describe a market in which organizations want more skilled people but are not always funding the positions, and in which the shortage is sharpest for experienced specialists (cloud security, identity, operational technology, incident response, AI security) rather than for entry-level applicants, many of whom report trouble getting a first job.

CyberSeek job postings

CyberSeek, an online tool built by CompTIA and Lightcast with support from the NIST-led National Initiative for Cybersecurity Education (NICE), counts actual job postings. At its June 2, 2025 update, CyberSeek reported 514,359 cybersecurity job listings in the United States over the prior 12 months, about 12 percent more than the year before.17 Postings are not the same as unfilled jobs: one opening can be posted several times, and some postings are for roles that are mostly IT with security duties. CyberSeek's map lets a user see postings and the employed workforce by state and metropolitan area, which is the most useful number for an Idaho employer comparing the Boise market with Salt Lake City or Spokane.

The White House's National Cyber Workforce and Education Strategy, released July 31, 2023, cited an industry estimate of 411,000 unmet U.S. cyber jobs in 2022 and called for "hiring by demonstrated skills," noting that skills-based hiring "is more predictive of job performance than hiring by education or work experience."18

Building the business case

A business case is a short written argument that a specific expense will produce a specific result worth more than it costs. Finance teams see dozens a year. The security ones that succeed share four habits: they begin with a named risk the business already cares about, they put the risk in dollars with an honest range, they show the alternatives considered (including doing nothing and doing half), and they say how the organization will know next year whether the money worked.

Start with the risk, not the tool

"We need an extended detection and response platform" is a tool request. "Our ransomware exposure is the largest risk on the enterprise risk register; today an intruder who gets an administrator's password can delete our backups; this proposal makes the backups undeletable and cuts our expected loss by about two-thirds" is a business case. Pull the risk from the risk register described in 108 lesson 2 and tie it to an outcome leaders recognize: days of downtime at the plants, patient diversions at the hospital, missed payroll, a regulator's order, a lost contract that requires a SOC 2 report or a CMMC certificate.

FAIR in plain terms

The most common method for putting cyber risk in dollars is FAIR, Factor Analysis of Information Risk. It began as an industry model, became an Open Group standard (the Open FAIR Risk Taxonomy, O-RT, and Risk Analysis, O-RA), and is now also maintained by the nonprofit FAIR Institute, which published FAIR Standard Version 3.0 on Jan. 15, 2025.1920 In plain terms:

  • Risk is "the probable frequency and probable magnitude of future loss."19
  • Loss event frequency is how often you expect a loss to happen in a year. It depends on how often threats act against you and how likely they are to succeed given your controls.
  • Loss magnitude is how much each event costs: primary loss (response, replacement, lost productivity) plus secondary loss (fines, lawsuits, lost customers, reputation), which happen only some of the time.
  • FAIR names six forms of loss: productivity, response, replacement, fines and judgments, competitive advantage and reputation.19

The analyst estimates each factor as a range (a minimum, a most likely value and a maximum) rather than a single number, then runs thousands of simulated years (a Monte Carlo simulation) to produce a range of annual loss. The result is a statement such as "there is a 10 percent chance that ransomware costs us more than $25 million in a given year," which a finance team can compare with other business risks. FAIR does not make the uncertainty go away; it makes the uncertainty visible, which is more honest than a red square on a heat map.

A worked example

The following example is fictional and illustrative. It uses round numbers to show the arithmetic, not real estimates for any organization.

A regional health system with $1.5 billion in revenue estimates, from its own history, peer incidents and its insurer's data, that it has about a 10 percent chance each year of a ransomware attack that disrupts clinical systems. If one happens, the most likely total cost (response, downtime, diverted patients, notification, legal claims) is about $12 million. The expected annual loss is 0.10 times $12 million, or $1.2 million. The CISO proposes $400,000 a year for undeletable (immutable) backups, multifactor authentication on the remaining administrator and remote access accounts, and 24-hour managed detection. The security team estimates, with a range, that these cut the annual chance to about 6 percent (attackers still get in sometimes, but are caught sooner) and the cost of an event to about $7 million (recovery takes days instead of weeks). The new expected loss is 0.06 times $7 million, or $420,000.

Worked example: ransomware controls at a fictional health system Illustrative numbers only $1,200,000 Before 10% x $12 million $420,000 After 6% x $7 million Expected annual loss Reduction: $780,000 a year Cost of proposal: $400,000 a year Net benefit: $380,000 a year About $1.95 back per $1 spent Gordon-Loeb ceiling for this one risk: about 37% of $1.2 million, or about $441,000. The $400,000 proposal is under it. Real analyses use ranges and simulation, not single points.
A cost-benefit comparison in expected annual loss. Original graphic for this module; the method follows the FAIR Standard Version 3.0 (FAIR Institute, Jan. 15, 2025) and the Gordon-Loeb model (2002, extended 2016); all numbers are fictional.

The reduction in expected loss is $780,000 a year against a cost of $400,000, a net benefit of $380,000 and roughly $1.95 back for each dollar. The CISO should also show the range: if the controls cut the chance only to 8 percent and the cost only to $10 million, the new expected loss is $800,000, the reduction is $400,000, and the proposal merely breaks even. Showing that downside makes the case more credible, not less. The CISO should also show half the proposal (immutable backups alone, for example) so the CFO can see which piece carries most of the benefit.

When the change touches production systems, as a backup redesign or a new authentication requirement does, the plan should include testing and a way to roll back, and the budget should include the staff time to do that.

The Gordon-Loeb ceiling

Two University of Maryland economists, Lawrence Gordon and Martin Loeb, published a model in 2002 showing that, under broad assumptions, the best amount to spend protecting a given set of information is never more than about 37 percent (1 divided by e, the base of natural logarithms) of the expected loss from a breach of that information.21 They and a co-author confirmed the result for two broad classes of breach probability functions in 2016.22 The intuition is that each added dollar of protection buys less risk reduction than the one before, so at some point the next dollar is worth less than a dollar. The model is a check on overspending against one risk, not a formula for the whole budget, and it depends on a sound estimate of expected loss; in the worked example, the $441,000 ceiling (37 percent of $1.2 million) is above the $400,000 proposal, which is consistent.

Using breach-cost studies carefully

The most quoted number in security budget requests comes from the Cost of a Data Breach Report, conducted each year by the Ponemon Institute and sponsored and analyzed by IBM. Its 2025 edition, released July 30, 2025, studied 600 organizations with breaches between March 2024 and February 2025 and reported:4

  • a global average cost of $4.44 million, the first decline in five years, and a U.S. average of $10.22 million, a record;
  • health care as the costliest industry at $7.42 million;
  • an average of 241 days to identify and contain a breach;
  • average savings of $1.9 million, and 80 fewer days, at organizations that used AI and automation extensively in security operations;
  • $670,000 more in cost at organizations with high levels of "shadow AI," meaning AI tools used without approval;
  • only 49 percent of breached organizations planning to increase security spending afterward, down from 63 percent in 2024.

The 2026 edition, released July 29, 2026, covering 602 organizations with breaches from March 2025 to February 2026, put the global average at $4.99 million, a record, reported that 39 percent of the breaches involved ransomware, and said organizations using AI and automation in security operations cut costs by almost $2 million on average.23 A law firm summary of the full report gives the 2026 U.S. average as $11.5 million and the average time to identify and contain as 247 days.24

These numbers are useful, but a finance team will ask about the method, and the CISO should know the answers:

  • It is a sample of breached organizations that agreed to be interviewed, not a random sample of all organizations or all breaches.
  • Costs are estimated by interviews and activity-based costing, including indirect costs such as lost business and staff time, rather than taken from accounting records.
  • Very large breaches are studied separately, so the average describes mid-sized incidents.
  • The sponsor sells security products and services, and the report's "cost amplifiers" and "cost savers" are correlations, not proof that a given tool caused the savings.

Other researchers have found very different numbers. When Verizon's 2015 Data Breach Investigations Report analyzed nearly 200 cyber insurance claims, it calculated an average of $0.58 per breached record, against Ponemon's $201; Verizon said both per-record averages "create very poor estimators," and Larry Ponemon said his institute stood by its results while acknowledging possible errors.25 A 2016 RAND study by Sasha Romanosky of 12,000 incidents in an insurance industry dataset found a typical cost of about $200,000 and that most incidents cost companies less than 0.4 percent of annual revenue.26 Insurance claims understate losses because of deductibles, limits and exclusions; interview-based studies may overstate them. The honest use of any of these numbers is as one input to a range, with your own data, your insurer's loss data and peer incidents weighted more heavily.

What real incidents cost

Public company filings give hard numbers that are often more persuasive to a board than survey averages:

  • MGM Resorts. In a Form 8-K filed Oct. 5, 2023, MGM estimated that a September 2023 cyberattack would reduce that month's Adjusted Property EBITDAR by about $100 million and that it had incurred less than $10 million in one-time expenses for consultants, legal fees and other advisors in the quarter. It said it expected its cyber insurance to cover the financial impact.27
  • UnitedHealth Group and Change Healthcare. The February 2024 ransomware attack on its Change Healthcare unit cost UnitedHealth about $3.1 billion in 2024 in direct response and business disruption costs, according to its fourth-quarter results reported Jan. 16, 2025. Its first estimate, in April 2024, had been about $1.6 billion.28
  • Suffolk County, New York. A September 2022 ransomware attack on the county cost more than $25 million in remediation and other expenses by September 2024, according to a county legislative committee report; the county had no CISO, no incident response plan and no cyber insurance at the time, and its main website was down for five months.29

Two cautions: a large company's losses do not scale down neatly to a smaller one, and an incident that happened to a peer is evidence of a threat, not a forecast. Use them to show leaders what "high impact" means in their own industry.

Compliance-driven spending

Some spending is not optional and does not need a return-on-investment argument: the Safeguards Rule's required elements for a finance company, the encryption and access controls a HIPAA risk analysis calls for, the PCI DSS assessment the card brands require, the CMMC Level 2 assessment a defense contractor needs to keep bidding. The business case for these is the cost of not complying: lost contracts, penalties, or the loss of a license. Separate mandatory items from discretionary ones in the request so leaders see the true decision space. Then look for overlap: a control built once and mapped to several frameworks (lesson 4) is cheaper than four teams gathering the same evidence for four auditors.

Presenting to the CFO and the board

  1. Open with the top three risks in business terms and the current expected loss range for each.
  2. State the mandatory spending (laws, contracts, insurer requirements) separately from discretionary spending.
  3. For each discretionary item, show cost, risk reduction with a range, and what happens at zero, half and full funding.
  4. Show what you stopped paying for this year (retired tools, consolidated contracts). Finance teams trust requests from people who also cut.
  5. Show how progress will be measured next year, using the metrics in lesson 3.
  6. Write down the decision. If leaders accept a risk by funding less, record who accepted it, for how long and at what expected loss. That record protects the organization in an examination and the CISO in a dispute.

Tool sprawl and consolidation

Large organizations accumulate security products the way houses accumulate keys. Each incident, audit finding and new regulation tends to add a tool; few tools are ever removed. The result is overlapping licenses, products nobody has time to tune, alerts nobody reads, and integration work that eats the staff time the tools were supposed to save. In a Gartner survey published Sept. 12, 2022, 75 percent of organizations said they were pursuing security vendor consolidation.30 Vendors have since pushed "platforms" that bundle endpoint, identity, email, cloud and SIEM functions under one contract.

Consolidation can save money and, more important, staff time. It also concentrates risk: one vendor's outage or flawed update can affect every function at once, as the July 19, 2024 CrowdStrike update failure showed on millions of Windows computers (covered in lesson 12 and lesson 9). A sound consolidation review asks:

  1. Inventory. List every security product, its owner, its annual cost, its renewal date, what it is supposed to detect or prevent, and whether anyone looked at its output in the last 30 days.
  2. Map to controls. Match each tool to the controls it supports in the framework the organization uses (for example, NIST CSF 2.0 categories). Two tools covering the same control are candidates to combine; a control with no tool is a gap.
  3. Measure use. A tool that is licensed for 20,000 devices but deployed on 12,000 is a coverage problem before it is a cost problem.
  4. Price the switch. Include migration labor, retraining, parallel running, detection rules that must be rebuilt, and early termination fees. Consolidation savings often arrive in year two or three.
  5. Plan the change. Replacing an endpoint agent or an identity provider is a production change: schedule it, test it on a pilot group, and keep a way back until the new tool is proven.
  6. Keep exit options. Negotiate data export rights and avoid contract terms that make leaving a platform impractical; regulators increasingly ask about concentration and exit plans.
Folded U.S. twenty dollar banknotes
Folded twenty dollar bills. Every security request competes with every other use of the same money. Photo: United States Department of the Treasury. Wikimedia Commons, Public domain.

Build, buy or managed services

For each security capability, a large organization decides whether to build it with its own staff and tools, buy a product and run it in-house, or contract a managed service to run it. Many end up with a mix: a managed security service provider (MSSP) or managed detection and response (MDR) firm watches alerts overnight, an in-house team handles investigation and response during the day, and specialists are hired by the engagement for penetration tests and forensics. Lesson 1 covers these as operating models; this section covers the money.

ChoiceStrengthsWeaknessesFits best when
Build in-house (own staff, own tools)Deep knowledge of the business; full control; skills stay in the organizationHighest fixed cost; hard to staff around the clock; vulnerable to turnoverThe capability is central to the business or regulated closely (a bank's fraud and identity controls, a utility's OT monitoring)
Buy a product, run it in-houseFaster than building; vendor handles research and updatesLicenses grow with size; tools need tuning staff; sprawl riskThe organization has staff to run it during the hours it matters
Managed service (MSSP, MDR, virtual CISO)24-hour coverage without a 24-hour team; predictable monthly cost; access to specialistsLess business context; quality varies; contract and data access terms matter; the organization still owns the risk and the decisionsAround-the-clock monitoring, specialized testing, or organizations that cannot recruit locally
Co-sourced (shared)Combines in-house knowledge with outside scaleHandoffs between teams can drop alerts; needs clear runbooksLarge organizations covering nights, weekends or surges
A security capability is needed 1. Central to the business or closely regulated? yes Build or run in-house outside help for surges no 2. Must it run 24 hours a day? yes Managed or co-sourced for nights, weekends no 3. People to tune and use the tool? yes Buy the product, run it in-house no Use a managed service Whatever the choice, the organization still owns the risk and the decisions. Contracts need data access, incident notice, right to audit and an exit plan.
A simple way to sort build, buy and managed-service choices. Original graphic for this module; a planning aid, not a rule from any standard.

When pricing a managed service, compare it with the full cost of the in-house alternative: salaries and benefits for enough people to cover every hour, recruiting, training, turnover, the tools the team needs and the management time to run it. Then read the contract closely. The vendor contract lessons in 108 lesson 8 apply in full: who can see your data, how fast the provider must tell you about its own incidents, whether you can audit it or rely on its SOC 2 report (lesson 5), what happens to your logs if you leave, and who decides to isolate a production server at 3 a.m. A managed service can watch; it cannot accept risk on your behalf.

The public sector budget process

Government security budgets move on a different clock. A private company can approve a mid-year purchase after an incident; a state agency usually needs an appropriation from the legislature, often a year or more ahead, and a county needs its commissioners to adopt a budget at a public hearing. That makes the business case public, which is useful for reporters and advocates and sometimes awkward for security staff who do not want to publish their weaknesses.

State IT budgets and chargeback

Most states run security through a central IT agency that charges other agencies for services (a "chargeback" or rate model) plus direct appropriations for statewide projects. Rates hide security costs inside the price of email, network and hosting; a direct appropriation shows them. The Deloitte and NASCIO finding that more than a third of state CISOs had no dedicated security budget line reflects this: security is real money in those states, but it is not visible as its own line, which makes it harder to defend in a lean year.9

Federal CIO and CISO budget lines

Each federal agency's chief information officer submits IT and cybersecurity spending to OMB as part of the budget process, and OMB publishes agency totals and a breakdown by NIST framework function in the Analytical Perspectives volume each year.10 Agency CISOs work within the CIO's budget at most departments, and inspectors general review the results each year under the Federal Information Security Modernization Act. CISA's budget is separate and pays for services that agencies and, in many cases, state and local governments use for free, such as vulnerability scanning and the Known Exploited Vulnerabilities catalog. Cuts to CISA proposed for fiscal 2026 matter to local governments for that reason: some services a county now gets for free could become a line in its own budget.11

The State and Local Cybersecurity Grant Program

The Infrastructure Investment and Jobs Act, signed Nov. 15, 2021, created the State and Local Cybersecurity Grant Program (SLCGP) at 6 U.S.C. 665g and gave it $1 billion over four federal fiscal years, run jointly by CISA and FEMA.31 Its design matters for anyone reading a state's security budget:

  • Declining appropriations and rising match. The law provided $200 million for fiscal 2022, $400 million for 2023, $300 million for 2024 and $100 million for 2025, and required states to pay a growing share of project costs: 10 percent in the first year, rising by 10 points a year to 40 percent in the fourth.31
  • Money for local governments. States must pass at least 80 percent of the funds through to local governments (or spend it on their behalf with their consent), and at least 25 percent must benefit rural areas.31
  • Planning first. Each state must form a cybersecurity planning committee and have a statewide cybersecurity plan approved before it can spend most of the money.31

The program moved slowly. According to an April 2025 Government Accountability Office report (GAO-25-107313), DHS had awarded about $172 million of the $1 billion to 33 states and territories as of Aug. 1, 2024, funding 839 projects.32 FEMA announced the fourth and last scheduled round on July 28, 2025: $91.75 million for states, with a 40 percent minimum cost share (30 percent for multi-entity projects), no cost-share waivers except for four insular territories, no extensions of the period of performance, and a Jan. 30, 2026 deadline for states to confirm or revise their cybersecurity plans. The 2025 notice also dropped the requirement, in place for 2022 through 2024, that recipients complete the Nationwide Cybersecurity Review.7 CISA paired it with a $12.1 million round of the Tribal Cybersecurity Grant Program.33

The program's legal authority then ran out on Sept. 30, 2025. The spending deal that ended the 43-day federal shutdown, passed Nov. 12, 2025, revived it temporarily.32 The House passed the PILLAR Act (H.R. 5078) by voice vote on Nov. 17, 2025; it would reauthorize the program through 2033, set the federal share at 60 percent for single applicants and 70 percent for multi-entity groups (five points more for states that fully implement multifactor authentication by Oct. 1, 2027), and leave funding to annual appropriations.34 Senators Maggie Hassan and John Cornyn introduced a one-year Senate reauthorization, S. 3251, on Dec. 1, 2025.3435 A fiscal 2026 appropriations law signed Feb. 3, 2026 (Pub. L. 119-75, Division I, section 5009) then moved the program's termination date to Sept. 30, 2026, as reporters had expected when the package was released in January.3136 At a May 2026 House hearing the subcommittee chair said, "Unless Congress acts, that program expires this September," and Tennessee's CIO testified that the state's $21 million in grants had secured nearly 90,000 endpoints and trained more than 21,000 local government employees.37 In June 2026 the PILLAR Act still had not reached a Senate floor vote, and state and local associations were asking the Senate to restore funding.38 A policy brief dated Oct. 5, 2026 from the Foundation for Defense of Democracies was titled as describing the program's third lapse, which suggests the authority ran out again on Sept. 30, 2026; this lesson could not read that brief or confirm any later action by Congress, so check congress.gov and CISA's SLCGP page for the current status.

State and Local Cybersecurity Grant Program, 2021 to 2026 Nov. 15, 2021 law creates $1 billion FY2022 $200M 10% match FY2023 $400M 20% match FY2024 $300M 30% match FY2025 $100M 40% match July 28, 2025: $91.75M offered Sept. 30, 2025: authority lapses Nov. 2025: revived; House passes PILLAR Act Feb. 3, 2026: law extension to Sept. 30, 2026 Sept. 30, 2026: expires again; renewal unconfirmed Bar heights show each year's appropriation; match is the minimum non-federal share.
The rise and lapse of the federal cyber grant program for states and local governments. Original graphic for this module; data from 6 U.S.C. 665g, FEMA's FY2025 key changes fact sheet (July 28, 2025), Pub. L. 119-75 (Feb. 3, 2026), NACo (Nov. 2025) and Route Fifty (May 26, 2026).

For budget owners the lesson is the one every grant teaches: grant money built capability that now has a running cost. Licenses bought with fiscal 2023 grant funds renew every year, and local governments that relied on the grant must either budget for them, find another source or turn them off. A county's cyber budget request in 2026 and 2027 should list which services came from the grant and what it will cost to keep each.

Idaho

Idaho chose to use much of its grant money for statewide services rather than small cash awards. The Idaho Office of Emergency Management, which runs the program for local governments, says the State and Local Cybersecurity Planning Committee concluded that "small, short-term cash grants would not sufficiently address" local gaps, and instead offered services with estimated statewide costs of $900,000 for risk assessment and gap management, $450,000 for governance and planning and $330,440 for training, with no local match required. Eligible counties, cities, school districts, special districts and tribal organizations signed a consent agreement to take part, and IOEM's cybersecurity area field officers support them by region.39 That page describes the fiscal 2022 round; how Idaho used the later rounds should be checked with IOEM.

At the state agency level, the Office of Information Technology Services (ITS) described its fiscal 2026 budget request in February 2025 as including a $10 million Cybersecurity and Information Technology Resilience fund for IT line items and replacements, ITS ownership of agency networking equipment and further centralization of infrastructure, with the rates ITS bills to customer agencies rising a net 1.6 percent.40 The final amounts are in the Legislature's appropriation bills and the Legislative Services Office budget documents; the governance side, including the Idaho Technology Authority, is in lesson 1.

Job seekers at a Hiring Our Heroes job fair at Fort Jackson
Soldiers, veterans and family members at a Hiring Our Heroes job fair at Fort Jackson, South Carolina, in March 2012. Veterans are one of the hiring pools organizations use to fill security jobs. Photo: Sgt. 1st Class Joel Quebec. Wikimedia Commons, Public domain.

Hiring, retention and burnout

Because people are the largest cost, the staffing plan is the heart of the budget. It should say how many people the program needs, with which skills, which roles will be filled by employees and which by services, how the organization will find them, and how it will keep them.

Defining the roles

The common vocabulary for security jobs is the NICE Workforce Framework for Cybersecurity, published as NIST Special Publication 800-181 Revision 1 in November 2020. It describes work roles (for example, defensive cybersecurity, vulnerability analysis, systems security management) in terms of tasks, knowledge and skills, and NIST updates the detailed components separately from the publication.41 Using NICE role names in job descriptions and the staffing plan makes it easier to compare with peers, to write apprenticeship standards and to show an examiner that every function has an owner. Lesson 1 maps NICE roles onto a security organization chart.

Hiring for skills

The federal workforce strategy and many large employers have moved toward skills-based hiring: removing degree requirements that are not needed for the work, using practical tests, and counting experience from the military, IT support or other fields. The 2023 strategy noted that 46 percent of federal cybersecurity jobs were open to applicants without a bachelor's degree, compared with 20 percent in the private sector, in the study it cited.18 Practical steps for a large organization:

  • Write job descriptions from the NICE tasks the role actually performs, and drop requirements nobody on the current team meets.
  • Grow analysts from the IT help desk, network operations and audit staff, who already know the organization's systems.
  • Budget for training and certification time as part of the job, not as a perk to be cut first.
  • Use paid internships and apprenticeships to build a pipeline (below).
  • Check that background checks and clearance requirements are tied to the role's real access, so they do not screen out good candidates for no reason.

Pay and the market

Security pay is set by a national market but paid from local budgets. A specialist in Boise can now work remotely for a bank in New York. Public employers and smaller private ones answer with what they can offer: stable employment, pensions, mission, flexible schedules, training, and in government, student loan programs. Large private organizations use retention bonuses and equity. Whatever the approach, the budget should show market data for each role (from salary surveys, the state's labor department or the organization's compensation team) and the cost of losing a person in that role: recruiting, the months the job sits empty, and the knowledge that leaves.

Retention and burnout

Security work has an unusual mix of stress: constant alerts, on-call duty, blame after incidents and long stretches in which success means nothing happened. Gartner predicted in February 2023 that by 2025 nearly half of cybersecurity leaders would change jobs, 25 percent of them for different roles entirely because of work-related stress.42 That was a prediction, not a measurement, but the ISC2 2025 survey found 48 percent of professionals feeling exhausted and 47 percent often overwhelmed by their workload.3 Burnout is a budget issue because turnover is expensive and because tired people miss things.

Measures that cost money and should be in the budget:

  • Enough people for a humane on-call rotation, or a managed service that takes the overnight pager.
  • Alert tuning time. A detection tool that produces thousands of false alarms a day burns people out; staff time to tune it is a direct retention investment.
  • Automation of repetitive work (enriching alerts, resetting accounts, collecting audit evidence), which the IBM studies associate with lower breach costs and which also removes the dullest work.4
  • Post-incident recovery time for the team after a major event, planned in advance.
  • Training and career paths, so people can grow without leaving.

Measures that cost little: blameless reviews after incidents, leaders who defend the team when a risk they warned about comes true, and a CISO who is not the only person who knows how things work.

Apprenticeships and the federal workforce strategy

Registered apprenticeships combine paid work with structured training under a standard approved by the U.S. Department of Labor or a state apprenticeship agency. The White House and the Labor Department ran a 120-day Cybersecurity Apprenticeship Sprint that ended Nov. 15, 2022; the administration reported 194 new cybersecurity registered apprenticeship programs approved or in development and more than 7,000 apprentices hired, more than 1,000 of them in the private sector.43 These are the government's own reported figures.

The National Cyber Workforce and Education Strategy, released July 31, 2023, organized federal efforts under four pillars: equip every American with foundational cyber skills, transform cyber education, expand and enhance the national cyber workforce, and strengthen the federal cyber workforce.18 Federal priorities have shifted since 2025, and some programs described in the strategy may have changed or ended; check the Office of the National Cyber Director's current materials before relying on a particular program. For a large employer, the practical uses are an apprenticeship standard to adapt rather than write from scratch, partnerships with community colleges and universities (in Idaho, the state's public colleges and universities run cybersecurity programs), and federal scholarship-for-service graduates who owe government service.

How many people?

There is no authoritative ratio of security staff to employees or to IT staff. Surveys report averages that vary widely by industry and by what the organization outsources. A better method is to build the number from the work: list each function the program must perform (from the organization chart in lesson 1 and the controls in the framework the organization uses), the hours each needs, which hours must be covered around the clock, and which a service will perform. Then compare the result with peer data as a sanity check. A staffing plan built this way also shows leaders exactly what stops happening if a position is cut.

Sample: Security Budget Request template

Sample only. Adapt it to your organization's risks, systems and laws, have qualified people review it, and do not treat it as a substitute for a risk assessment.

Follows: NIST Cybersecurity Framework 2.0, Govern function (Feb. 26, 2024); the FAIR Standard Version 3.0 (FAIR Institute, Jan. 15, 2025) for loss estimates; 23 NYCRR 500.4 and 500.10 (as amended Nov. 1, 2023); 16 CFR 314.4(e) and (i); 45 CFR 164.306(b); NIST SP 800-181 Rev. 1 (NICE Framework) for role names.

1. Summary

Fiscal year: [FY]. Prepared by: [CISO name and title]. Reviewed by: [CIO, CFO or budget office, risk officer]. Total request: $[amount], a [percent] change from the current year's $[amount]. Of this, $[amount] is mandatory (law, regulation, contract or insurance requirement) and $[amount] is discretionary. Security spending in other departments' budgets that supports this program: $[amount], listed in section 7.

2. Top risks this budget addresses

For each of the top [three to five] risks on the enterprise risk register: the risk in business terms; current estimated annual loss as a range ($[low] to $[high], most likely $[amount]) and the method used; the board-approved risk appetite for it; and whether current spending keeps it within appetite.

3. Current spending by component

People ($[amount], [number] full-time positions, [number] vacant), tools and platforms ($[amount], [number] products), services ($[amount]), insurance ($[amount], paid by [department]), audits and certifications ($[amount]), training and awareness ($[amount]). Attach the tool inventory with owner, cost, renewal date and last review.

4. Mandatory items

For each: the requirement and its citation or contract clause, the deadline, the cost, and the consequence of not funding it (penalty, lost contract, loss of coverage, audit finding).

5. Discretionary items

For each item: what it is; the risk it reduces; the estimated change in annual loss (range); one-time and recurring cost for [three] years; the alternatives considered (do nothing, partial funding, managed service, consolidation); dependencies on other teams; the plan to test changes to production systems and roll them back if needed; and how success will be measured next year.

6. Savings and retirements

Tools retired, contracts consolidated, services brought in-house or moved out, with annual savings of $[amount] and any one-time switching costs.

7. Security costs in other budgets

Identity and backup (IT), incident response retainer (general counsel's office), cyber insurance (risk management), certifications (compliance), awareness training (human resources), product security (engineering): amount and owner for each.

8. Staffing plan

Positions by NICE work role, filled and vacant; coverage hours; on-call rotation; positions proposed; market pay data and source; turnover in the past [two] years; training budget per person; apprenticeship or internship plans.

9. Funding scenarios

At [100] percent: [outcomes]. At [75] percent: [what is deferred and the resulting risk]. At [50] percent: [what is deferred and the resulting risk]. At flat funding: [what is cut, given price increases of about [percent] on existing contracts].

10. Grants and outside funding (public entities)

Grant-funded services and licenses, their end dates, the annual cost to continue each, and the plan if the grant is not renewed.

11. Decision record

Approved amount: $[amount]. Items not funded: [list]. Resulting risks accepted, by whom, for what period, and the date for review: [entries]. Signature of the approving official: [name, title, date]. For regulated entities: date the board or committee was informed that resources were reviewed for sufficiency: [date].

Pictures, Numbers and Infographics

The numbers below are the ones most often quoted in security budget discussions. Each comes from a named survey, forecast, filing or law with its date; none is a target for any one organization.

MeasureFigureSource and date
Worldwide end-user security spending$213 billion (2025); about $240 billion forecast (2026)Gartner, July 29, 20252
Revised 2026 worldwide forecastAbout $247.5 billion, up 13.6 percentGartner 3Q26 forecast as summarized Oct. 20268
Security share of IT budget, large organizations10.9 percent (2025), 11.9 percent (2024), 8.6 percent (2020)IANS and Artico, 587 CISOs, 20251
Security spending as share of revenue0.69 percentIANS and Artico, 20251
Average security budget growth4 percent (2025), 8 percent (2024)IANS and Artico, 20251
Budget splitStaff 39 percent, software 29 percent, outsourcing 12 percentIANS and Artico, 20251
CISO pay increase; top earners6.7 percent (2025); top 1 percent above $3.2 millionIANS and Artico, 566 CISOs, Nov. 13, 202512
State CISOs with no dedicated security budget lineMore than one-thirdDeloitte and NASCIO, Sept. 30, 20249
Proposed cut to federal civilian cyber spending, FY2026 requestAbout $1.23 billion (about 10 percent below 2024)CSO Online report on White House budget data, July 9, 202511
Worldwide security workforce gap (ISC2 estimate)4.8 million (2024); U.S. 504,307ISC2 2024 study, 15,852 respondents16
Teams with critical or significant skills needs59 percent (2025), up from 44 percent (2024)ISC2 2025 study, 16,029 respondents3
U.S. cybersecurity job listings, prior 12 months514,359CyberSeek via NIST, June 2, 202517
Average cost of a data breach$4.44 million global, $10.22 million U.S. (2025); $4.99 million global (2026)IBM and Ponemon, July 30, 2025 and July 29, 2026423
Savings with extensive security AI and automation$1.9 million per breach (2025)IBM and Ponemon, July 30, 20254
Typical cost of a cyber incident in insurance dataAbout $200,000; most under 0.4 percent of revenueRAND (Romanosky), Sept. 20, 201626
Gordon-Loeb spending ceilingAbout 37 percent (1/e) of expected lossGordon and Loeb, 2002; Gordon, Loeb and Zhou, 20162122
Change Healthcare attack cost to UnitedHealthAbout $3.1 billion in 2024Reported with fourth-quarter results, Jan. 16, 202528
MGM Resorts September 2023 attackAbout $100 million EBITDAR impact; under $10 million one-time costsForm 8-K, Oct. 5, 202327
Suffolk County, N.Y. ransomware costsMore than $25 millionCounty legislative committee report, Sept. 202429
Capital One OCC penalty$80 millionOCC, Aug. 6, 202015
State and Local Cybersecurity Grant Program$1 billion over FY2022 to FY2025; last round $91.75 million at 40 percent match6 U.S.C. 665g; FEMA, July 28, 2025317
SLCGP authority end dateSept. 30, 2026 (extended from Sept. 30, 2025)6 U.S.C. 665g(s) as amended Feb. 3, 202631
Idaho grant-funded local services (FY2022 round)$900,000 risk assessment; $450,000 governance and planning; $330,440 trainingIdaho Office of Emergency Management39
Cybersecurity apprenticeship sprint, 2022194 new programs; more than 7,000 apprentices hiredWhite House fact sheet, Nov. 15, 202243
The security workforce in 2025 Percent of 16,029 respondents, ISC2 Cybersecurity Workforce Study 2025 Critical or significant skills needs 59% Feel exhausted keeping up 48% Often overwhelmed by workload 47% Hiring freezes 39% Budget cuts 36% Staffing at the right level 34% Layoffs 24% Bar length is proportional to percent (600 px = 100 percent).
Skills, stress and cutbacks in the 2025 security workforce. Original graphic for this module; data from ISC2, 2025 Cybersecurity Workforce Study (released December 2025).

Common mistakes

Buying tools without the people to watch them

Suffolk County, New York, had security monitoring in place before its September 2022 ransomware attack. The county legislature's special committee report found that alerts of suspicious activity from a Palo Alto Networks platform appeared in the months before the attack and that an FBI agent had called the county in June 2022 about suspicious traffic, and that neither led to action. The county had several separate IT teams and no CISO to pull them together.29 A tool budget without a staffing budget buys alerts, not protection.

Running on equipment that no longer gets security updates

The same report found that numerous Suffolk County firewalls had reached end of life and were no longer receiving security updates, and that a pass-through connection let traffic bypass firewalls into the County Clerk's systems. Recovery cost more than $25 million, the county had no cyber insurance, and its main website was down for five months.29 Replacement cycles for security equipment belong in the capital plan, not in an emergency request.

Expanding risk without budgeting for it

The OCC's $80 million penalty against Capital One in August 2020 cited the bank's failure to establish effective risk assessment processes before migrating significant IT operations to the public cloud, and its failure to correct the deficiencies in a timely manner.15 Any project that changes the organization's risk (a cloud migration, an acquisition, a new customer-facing app) should carry its own security assessment and budget, approved with the project.

Hiding security inside other lines

When more than a third of state CISOs report no dedicated security budget line, the security program is funded by rates and other agencies' choices and is hard to defend or measure.9 Even where costs are shared, the CISO should publish one consolidated view each year (section 7 of the sample request).

Building on grants without a plan to sustain them

The federal grant program's appropriations fell from $400 million in fiscal 2023 to $100 million in fiscal 2025 while the required match rose to 40 percent, the 2025 round allowed no extensions, and the program's authority lapsed and was extended more than once.317 Local governments that bought subscriptions with grant money and did not budget the renewals face a cliff.

Quoting a survey average as a forecast

Telling a board that "a breach will cost us $10 million" because that is a survey's U.S. average invites the question of why the Verizon analysis of insurance claims, or RAND's study of 12,000 incidents, found far smaller typical costs.2526 Present a range built from several sources and the organization's own data, and say which assumptions drive it.

Cutting without a record of the accepted risk

New York's Part 500 makes the board confirm that management has allocated sufficient resources.5 A budget cut decided in a hallway, with no written statement of what will not be done and who accepted the risk, leaves the board unable to show it met that duty and leaves the CISO exposed after an incident. The decision record in section 11 of the sample request is cheap insurance.

Questions people ask

What percentage of our IT budget should go to security?

There is no correct number. Large private organizations in the 2025 IANS survey averaged 10.9 percent of IT and 0.69 percent of revenue, and federal agencies generally earmark more than 10 percent of IT, while many states spend far less.19 Use the averages to check whether you are far outside your industry, then build the number from your risks, legal requirements and gaps.

Is the cybersecurity worker shortage real?

For experienced specialists, yes: 59 percent of teams in the 2025 ISC2 survey reported critical or significant skills needs, and CyberSeek counted 514,359 U.S. job listings in the 12 months before June 2025.317 But the same ISC2 survey found budget cuts, layoffs and hiring freezes at a third or more of organizations, and many newcomers struggle to find a first job. The gap is partly a gap in funded, trained positions, not only in people.

Can we outsource security entirely?

You can outsource work, not accountability. The FTC Safeguards Rule lets a financial institution use an affiliate's or a service provider's personnel, but it still must name a Qualified Individual, oversee the provider and report to its board.6 New York's Part 500 allows a CISO employed by an affiliate or third party with similar conditions.5 Someone inside the organization must make risk decisions, manage the contracts and lead during an incident.

Does cyber insurance replace security spending?

No. Insurance pays for some losses after an incident; it does not prevent the incident, cover every loss, or restore lost trust. Insurers also price and sometimes deny coverage based on the controls the security budget pays for, such as multifactor authentication and protected backups. Lesson 9 covers what insurers ask and what policies exclude. MGM expected insurance to cover its 2023 losses; Suffolk County had none.2729

How do we justify spending when nothing bad has happened?

By showing what the spending prevented or limited and what the risk would be without it: attacks blocked, vulnerabilities fixed before they were exploited, recovery tests that worked, audit findings closed, insurance terms improved, contracts won because the organization could show a SOC 2 report or a CMMC certificate. Pair those measures (lesson 3) with the expected loss estimate. A quiet year is evidence the program works only if the program can show what it did.

If we must cut, what should go first?

Start with unused or duplicate tools found in a consolidation review, then low-value activities (reports nobody reads, audits that duplicate others). Protect the things that limit the worst outcomes: identity and multifactor authentication, protected backups and tested recovery, monitoring with someone watching, patching of internet-facing systems and the incident response retainer. Record what was cut and the risk accepted.

What happens to local governments when the federal grant ends?

They must fund the services from their own budgets, find state help, or stop. In Idaho, much of the grant money paid for statewide services delivered through the Office of Emergency Management rather than cash to each county, so the question is whether the state continues those services.39 County commissioners can ask their IT director for a list of grant-funded services and their renewal costs.

Hard questions

Should regulators set minimum security spending?

For: Organizations underinvest because breach costs fall partly on customers, patients and the public, not only on the organization; a floor would force attention, and some countries' rules for critical infrastructure come close to one. Against: A spending floor measures inputs, not results; organizations could meet it by buying shelfware, and the right amount varies enormously by size and risk. What the evidence shows: U.S. rules instead require a risk-based program, qualified people and board confirmation that resources are sufficient (New York, the FTC, HIPAA), which ties resources to risk without a number.5613 The benchmark data show wide variation even among organizations with mature programs, which is the strongest argument against a single floor.1

Is the skills gap a shortage of people or of employers willing to train and pay?

Shortage of people: Demand grows faster than schools and certifications produce experienced practitioners, and the most needed skills (cloud, OT, incident response, AI security) take years to learn. Shortage of employer investment: Many postings require years of experience for entry roles, degree requirements screen out capable people, and in 2025 more than a third of organizations reported budget cuts and hiring freezes.3 What the evidence shows: Both are true. The federal strategy's emphasis on skills-based hiring and apprenticeships, and the sprint's reported 7,000 apprentices, suggest that employers who train can fill roles; the persistent shortage of senior specialists suggests the pipeline takes years to mature.1843

Should Washington keep paying for local government cybersecurity?

For continued federal funding: Local governments run 911, water, elections and schools; attacks on them affect national security and interstate commerce; small counties cannot afford specialists; and the grant program's rising match was designed to build local commitment. Tennessee testified that its grants secured nearly 90,000 endpoints.37 For local responsibility: Local systems are local functions; federal grants are temporary and create cliffs; the program spent slowly ($172 million of $1 billion by Aug. 1, 2024); and the federal budget is under pressure.32 What the evidence shows: Congress has repeatedly extended the program's authority but has not provided new multi-year money, and the House-passed reauthorization leaves funding to annual appropriations.34 Whether the investment improved local security is still being measured; the 2025 notice added target ranges for performance measures, which should produce better evidence.7

Does consolidating onto one vendor's platform make us safer or more fragile?

Safer: Fewer tools mean fewer gaps between them, less integration work, better-tuned detections and more staff time for real threats. More fragile: One vendor's outage, flawed update or breach affects everything at once, and lock-in weakens the buyer's negotiating position. What the evidence shows: Most organizations are consolidating, but large outages such as the July 2024 CrowdStrike update failure show the concentration risk is real.30 The prudent middle is to consolidate where it reduces real complexity, keep separate controls for the most critical safeguards (for example, backups that a compromised management console cannot delete), and keep tested exit and recovery plans.

Is putting cyber risk in dollars honest, or false precision?

Honest: Dollars are the language of budget decisions; methods like FAIR force analysts to state assumptions and ranges that a heat map hides, and the result can be compared with other business risks. False precision: The inputs are often guesses, rare catastrophic events are hard to estimate, and a precise-looking number may persuade leaders more than it should. What the evidence shows: The wide disagreement among breach-cost studies (about $200,000 typical in RAND's insurance data versus multimillion-dollar averages in interview-based studies) shows how much the answer depends on method.2526 Quantification is most useful when it reports ranges, shows its assumptions and is compared over time, and least useful when a single number is presented as fact.

For reporters and advocates

What public records exist.

  • SEC filings on EDGAR. Form 8-K Item 1.05 and later 8-K, 10-Q and 10-K filings often state incident costs, insurance recoveries and remediation spending; 10-K Item 1C describes how the company manages cyber risk and who oversees it. EDGAR full-text search finds filings by phrase and date.44 Compare what a company says about its program with what it later discloses about costs.
  • Government budgets. The federal Analytical Perspectives volume lists civilian cyber spending by agency.10 State budget requests, appropriation bills and legislative budget committee minutes show IT and security lines; in Idaho, look at the Office of Information Technology Services budget request and the Joint Finance-Appropriations Committee's records.40 County and city budgets are adopted at public hearings.
  • Grant records. Federal grant awards, including the State and Local Cybersecurity Grant Program, are searchable on USAspending.gov.45 States must have approved cybersecurity plans and planning committees; ask for the plan, the committee's membership and minutes, and the list of local subawards or services.31
  • Audits and enforcement. GAO and inspector general reports, state legislative auditors' reports, bank regulators' enforcement actions (such as the OCC's Capital One order) and FTC orders often describe resource failures in plain terms.15
  • Idaho public records. The Idaho Public Records Act, Idaho Code Title 74, Chapter 1, gives access to agency budgets, contracts and grant documents; agencies may withhold specific security details whose release would create a risk, so ask for spending, contracts and plans rather than system vulnerabilities.46
  • Free federal services. CISA lists the free services available to state and local governments and critical infrastructure; ask whether a local agency uses them.47

Questions to ask.

  • What share of the IT budget goes to security, how is it counted, and how has it changed over three years?
  • Is there a CISO or named security lead, and how many dedicated security staff are there? How many positions are vacant, and for how long?
  • What security services or licenses were paid for with federal grant money, when do they end, and what will it cost to keep them?
  • Has the board, commission or council been told what risks were accepted when security requests were not funded? Is there a written record?
  • Does the organization carry cyber insurance, and what controls did the insurer require?
  • When did the organization last test restoring its systems from backup, and did it work?
  • For a public company after an incident: what has it disclosed about costs and insurance recoveries, and how does that compare with its 10-K description of its program?

The Idaho angle. Idaho used its early federal cyber grant funds mainly for statewide services to local governments through the Office of Emergency Management, and the state's IT agency requested a $10 million cybersecurity and IT resilience fund for fiscal 2026.3940 Reporters covering county budgets can ask what happens to those services after the federal program's authority was set to end on Sept. 30, 2026, and legislators can ask ITS how the resilience fund was spent and what it bought.

Where to go next

  • CyberSeek: Free interactive map of U.S. cybersecurity job postings and workforce by state and metro area, supported by NIST's NICE program. For hiring managers and budget writers: use it to compare the local market (for example Boise) with others before setting pay and recruiting plans.
  • NICE Workforce Framework for Cybersecurity: Free. The standard vocabulary of security work roles, tasks, knowledge and skills. Use it to write job descriptions, staffing plans and apprenticeship standards.
  • CISA Free Cybersecurity Services and Tools: Free catalog of government and vetted no-cost services. Public agencies and small critical infrastructure operators should check it before budgeting for a paid equivalent.
  • CISA State and Local Cybersecurity Grant Program page: Free. Program rules, planning committee and plan requirements, and status updates. For state and local budget officers and reporters tracking whether the program is renewed.
  • FAIR Institute standards and resources: The FAIR Standard and introductory material are free to read; training and certification cost money. For risk managers and CISOs building dollar-based business cases.
  • Apprenticeship.gov: Free U.S. Department of Labor site for finding and registering apprenticeship programs, including cybersecurity occupations. For HR and security leaders building a talent pipeline.
  • OMB Analytical Perspectives (federal budget): Free. Each year's Management chapter lists civilian federal cyber spending by agency. For reporters, analysts and federal budget staff.
Still being checked (9 items)

These points could not be fully confirmed against a primary source when this lesson was written and fact checked in November 2026. The text above states each one as uncertain.

  • Gartner's third-quarter 2026 forecast figures ($217.7 billion for 2025, $247.5 billion for 2026) come from an independent blog's summary; the Gartner document is paywalled and was not read.
  • The 2026 U.S. average breach cost ($11.5 million) and 247-day figure come from a law firm summary; the full IBM 2026 report requires registration and was not read.
  • The Gartner Sept. 12, 2022 consolidation press release page could not be loaded; the 75 percent figure is from its title and press coverage.
  • Final enacted FY2026 federal civilian cyber spending and CISA's final FY2026 appropriation were not confirmed; the lesson cites the request and a House committee bill. OMB's FY2027 Analytical Perspectives table values were not read.
  • Whether Congress renewed or funded the State and Local Cybersecurity Grant Program after its authority was set to end Sept. 30, 2026 could not be confirmed as of Nov. 15, 2026. A Foundation for Defense of Democracies brief dated Oct. 5, 2026 is titled as describing a third lapse, but its page could not be loaded (rechecked Nov. 16, 2026); StateScoop reported Sept. 1, 2026 that NASCIO was still asking Congress to reauthorize it.
  • How Idaho used the FY2023 to FY2025 SLCGP rounds, and the final enacted amount of Idaho ITS's FY2026 Cybersecurity and IT Resilience fund, were not confirmed.
  • The rule of thumb of five to six full-time people per around-the-clock seat is a common planning figure, not a published standard.
  • Whether IANS and Artico published a 2026 Security Budget Benchmark was not confirmed; the 2025 edition is the latest read.
  • The ISC2 2025 study's release date (December 2025) is taken from the page metadata.

Last verified November 15, 2026. General education, not legal, compliance, audit or other professional advice; rule versions and dates are stated in the text, and the sources used are listed in the Notes and Sources below. Check the regulator's current text before relying on any point.

Notes

  1. IANS Research and Artico Search, 2025 Security Budget Benchmark Report, summary page (587 CISOs in the U.S. and Canada, data gathered April to August 2025; average budget growth 4 percent, down from 8 percent in 2024; 47 percent received increases, 39 percent flat; security 10.9 percent of IT spending, down from 11.9 percent in 2024 and up from 8.6 percent in 2020; 0.69 percent of revenue; staff 39 percent, software 29 percent, outsourcing 12 percent). Summary report dated Aug. 5, 2025 (read Nov. 15, 2026). Read it online. ↩
  2. Gartner, press release, "Gartner Forecasts Worldwide End-User Spending on Information Security to Total $213 Billion in 2025," July 29, 2025 (2024: $193,408 million; 2025: $213,025 million; 2026: $239,759 million, up 12.5 percent; 2026 segments: security software $121,154 million, security services $92,780 million, network security $25,825 million; quotation from Ruggero Contu) (read Nov. 15, 2026). Read it online. ↩
  3. ISC2, "Cybersecurity Professionals Navigate Evolving Workplaces While Seizing New Opportunities," release of the 2025 ISC2 Cybersecurity Workforce Study, December 2025 (16,029 respondents surveyed July and August 2025; 95 percent with at least one skills need; 59 percent critical or significant needs, up from 44 percent; 34 percent right staffing; 36 percent budget cuts, 24 percent layoffs, 39 percent hiring freezes; 31 percent expect more cutbacks; 48 percent exhausted; 47 percent often overwhelmed; 28 percent integrated AI security tools, 19 percent testing, 22 percent evaluating; 73 percent expect more specialized skills) (read Nov. 15, 2026). Read it online. ↩
  4. IBM Newsroom, "IBM Report: 13% Of Organizations Reported Breaches Of AI Models Or Applications, 97% Of Which Reported Lacking Proper AI Access Controls," July 30, 2025, announcing the Cost of a Data Breach Report 2025, conducted by the Ponemon Institute and analyzed by IBM (600 organizations; breaches March 2024 to February 2025; global average $4.44 million; U.S. $10.22 million; health care $7.42 million; 241 days; $1.9 million and 80 days saved with extensive security AI and automation; $670,000 added by high shadow AI; 49 percent planning to invest in security after a breach, down from 63 percent) (read Nov. 15, 2026). Read it online. ↩
  5. New York Department of Financial Services, 23 NYCRR Part 500, Cybersecurity Requirements for Financial Services Companies, as amended by the Second Amendment effective Nov. 1, 2023, sections 500.4 (CISO, which may be employed by an affiliate or third-party service provider; board oversight, including confirming that management has allocated sufficient resources) and 500.10 (qualified cybersecurity personnel sufficient to manage risks) (read Nov. 15, 2026). Read it online. ↩
  6. 16 CFR 314.4(a), (e) and (i), FTC Standards for Safeguarding Customer Information (Qualified Individual; qualified information security personnel "sufficient to manage your information security risks"; written report to the board at least annually), eCFR current text; amended rule published Dec. 9, 2021 (read Nov. 15, 2026). Read it online. ↩
  7. FEMA, "Fiscal Year 2025 State and Local Cybersecurity Grant Program Key Changes," fact sheet, July 28, 2025 ($91.75 million; 40 percent minimum cost share, 30 percent for multi-entity projects; waivers only for American Samoa, Guam, the U.S. Virgin Islands and the Northern Mariana Islands; Cybersecurity Plan confirmation or revision due Jan. 30, 2026; Nationwide Cybersecurity Review no longer required; no period of performance extensions; performance measure target ranges added) (read Nov. 15, 2026). Read it online. ↩
  8. Software Strategies Blog, "Gartner 3Q26 Information Security Forecast" (Oct. 5, 2026), summarizing Gartner, Forecast: Information Security, Worldwide, 2024-2030, 3Q26 (G00862059, Sept. 24, 2026): 2025 $217.7 billion; 2026 $247.5 billion, up 13.6 percent; 2030 about $373 billion. Secondary summary of a paid Gartner document; figures not checked against the original (read Nov. 15, 2026). Read it online. ↩
  9. NASCIO, "2024 Deloitte-NASCIO Survey Finds States Face Growing Cybersecurity Threats, Tight Budgets," Sept. 30, 2024 (CISOs of 50 states and D.C.; more than one-third without a dedicated cybersecurity budget; four of 51 allocate less than 1 percent of IT budget; federal agencies generally more than 10 percent; CISOs with fewer than five staff fell from 16 percent in 2020 to 4 percent) (read Nov. 15, 2026). Read it online. ↩
  10. Office of Management and Budget, Analytical Perspectives, Budget of the U.S. Government, Fiscal Year 2027, chapter 5, "Management" (April 2026), including Table 05-5, Estimated Civilian Federal Cybersecurity Spending by Agency, and Table 05-6, NIST Framework Function Civilian CFO Act Agency Funding Totals. The table values were not read for this lesson (read Nov. 15, 2026). Read it online. ↩
  11. Cynthia Brumfield, "Trump seeks unprecedented $1.23 billion cut to federal cyber budget," CSO Online, July 9, 2025 (based on White House FY2026 crosscut data; about 10 percent below 2024; about $500 million cut requested for CISA; House Homeland Security bill advanced June 3, 2025 with $2.74 billion for CISA, $146 million below 2025). Press report (read Nov. 15, 2026). Read it online. ↩
  12. IANS Research and Artico Search, press release, "New Report from IANS and Artico Search Shows 6.7% Rise in CISO Compensation in 2025 Amid Economic Uncertainty and Evolving Digital Risk," Nov. 13, 2025 (566 CISOs in the U.S. and Canada, April to October 2025; tech average $844,000, financial services $744,000; top 1 percent above $3.2 million) (read Nov. 15, 2026). Read it online. ↩
  13. 45 CFR 164.306(b), HIPAA Security Rule, flexibility of approach (factors include size, complexity and capabilities, technical infrastructure, "the costs of security measures," and the probability and criticality of potential risks), eCFR current text (read Nov. 15, 2026). Read it online. ↩
  14. 17 CFR 229.106 (Regulation S-K Item 106, Cybersecurity), adopted by SEC Release No. 33-11216 (July 26, 2023), eCFR current text (read Nov. 15, 2026). Read it online. ↩
  15. Office of the Comptroller of the Currency, News Release 2020-101, "OCC Assesses $80 Million Civil Money Penalty Against Capital One," Aug. 6, 2020 (read Nov. 15, 2026). Read it online. ↩
  16. ISC2, "Employers Must Act: Cybersecurity Workforce Growth Stalls as Skills Gaps Widen," September 2024, first look at the 2024 ISC2 Cybersecurity Workforce Study (15,852 respondents; global gap 4.8 million, up 19 percent; U.S. gap 504,307, up from 482,985; North American workforce 1,454,868) (read Nov. 15, 2026). Read it online. ↩
  17. NIST, news release on CyberSeek updates, June 2, 2025, updated Aug. 22, 2025 ("Employers deployed 514,359 job listings over the past 12 months," about 12 percent more than the prior period) (read Nov. 15, 2026). Read it online. ↩
  18. The White House, Office of the National Cyber Director, National Cyber Workforce and Education Strategy, July 31, 2023 (four pillars; skills-based hiring; 411,000 unmet demand estimate for 2022; 46 percent of federal versus 20 percent of private cyber jobs open without a bachelor's degree, citing an outside study) (read Nov. 15, 2026). Read it online. ↩
  19. FAIR Institute, Factor Analysis of Information Risk (FAIR) Model, Standard Artifact, Version 3.0, Jan. 15, 2025 (risk as "the probable frequency and probable magnitude of future loss"; loss event frequency, loss magnitude and their factors; six forms of loss) (read Nov. 15, 2026). Read it online. ↩
  20. The Open Group, Risk Taxonomy (O-RT), The Open Group Standard (Open FAIR), online edition (read Nov. 15, 2026). Read it online. ↩
  21. Lawrence A. Gordon and Martin P. Loeb, "The Economics of Information Security Investment," ACM Transactions on Information and System Security 5(4): 438 to 457 (2002) (read Nov. 15, 2026). Read it online. ↩
  22. Lawrence A. Gordon, Martin P. Loeb and Lei Zhou, "Investing in Cybersecurity: Insights from the Gordon-Loeb Model," Journal of Information Security 7(2): 49 to 59 (March 2016) (optimal investment does not exceed about 37 percent, 1/e, of expected loss for two broad classes of breach probability functions) (read Nov. 15, 2026). Read it online. ↩
  23. IBM Newsroom, "IBM Study: One in Four Malicious Breaches are AI-Enabled, Costing Companies $6 Million on Average," July 29, 2026, on the Cost of a Data Breach Report 2026 by the Ponemon Institute, sponsored and analyzed by IBM (602 organizations; breaches March 2025 to February 2026; global average $4.99 million; ransomware in 39 percent, up from 34 percent; almost $2 million lower costs with AI and automation in security operations) (read Nov. 15, 2026). Read it online. ↩
  24. Baker Donelson, "Ten Takeaways From IBM's 2026 Cost of a Data Breach Report" (2026) (U.S. average $11.5 million; 247 days to identify and contain; health care $6.64 million). Secondary summary of the full IBM report, which requires registration and was not read (read Nov. 15, 2026). Read it online. ↩
  25. Fortune, "Data breach cost estimate dispute" (April 24, 2015), on Verizon's 2015 Data Breach Investigations Report ($0.58 per record from nearly 200 insurance claims) and the Ponemon Institute's $201 per record estimate, with comments from Verizon and Larry Ponemon. Press report (read Nov. 15, 2026). Read it online. ↩
  26. RAND Corporation, news release, "Cost of Cyber Incidents Not Large Compared with Other Business Losses; May Influence Responses by Businesses," Sept. 20, 2016, on Sasha Romanosky, "Examining the Costs and Causes of Cyber Incidents," Journal of Cybersecurity (2016) (12,000 incidents in an Advisen dataset; typical cost about $200,000; most less than 0.4 percent of annual revenue) (read Nov. 15, 2026). Read it online. ↩
  27. MGM Resorts International, Form 8-K, Oct. 5, 2023 (approximately $100 million negative impact on September Adjusted Property EBITDAR; less than $10 million in one-time expenses in the third quarter; expectation that cyber insurance will be sufficient), SEC EDGAR (read Nov. 15, 2026). Read it online. ↩
  28. Healthcare Dive, report on UnitedHealth Group's fourth-quarter and full-year 2024 results, Jan. 16, 2025 (Change Healthcare cyberattack costs of about $3.1 billion in 2024; earlier estimates $1.6 billion in April and $2.9 billion in October 2024). Press report on the company's earnings release (read Nov. 15, 2026). Read it online. ↩
  29. David Jones, "Suffolk County ignored threat warnings before ransomware attack," Cybersecurity Dive, Sept. 18, 2024, on the report of the Suffolk County Legislature's special committee on the September 2022 attack (FBI call in June 2022; unheeded platform alerts; no CISO; end-of-life firewalls; more than $25 million in costs; no insurance; website down five months). Press report on the committee's findings (read Nov. 15, 2026). Read it online. ↩
  30. Gartner, press release, "Gartner Survey Shows 75% of Organizations Are Pursuing Security Vendor Consolidation in 2022," Sept. 12, 2022. The press release page could not be loaded; figure confirmed from the release title and press coverage (read Nov. 15, 2026). Read it online. ↩
  31. 6 U.S.C. 665g, State and Local Cybersecurity Grant Program, enacted by the Infrastructure Investment and Jobs Act, Pub. L. 117-58 (Nov. 15, 2021): subsection (g) planning committee; (m) federal share limits by year (90, 80, 70 and 60 percent for single entities); (n)(2) at least 80 percent to local governments and 25 percent to rural areas; (r) authorization of $200 million, $400 million, $300 million and $100 million for FY2022 to FY2025; (s) termination Sept. 30, 2026, as amended by Pub. L. 119-75, Div. I, sec. 5009 (Feb. 3, 2026), Legal Information Institute text (read Nov. 15, 2026). Read it online. ↩
  32. Route Fifty, "Government funding deal reups cyber grant program," Nov. 13, 2025 (deal passed Nov. 12, 2025 after a 43-day shutdown; program had expired in September 2025). Press report. The $172 million and 839-project figures are from U.S. Government Accountability Office report GAO-25-107313, April 29, 2025 (about $172 million awarded to 33 states and territories for 839 projects as of Aug. 1, 2024; https://www.gao.gov/products/gao-25-107313) (read Nov. 15, 2026). Read it online. ↩
  33. CISA, "DHS Launches Over $100 Million in Funding to Strengthen Communities' Cyber Defenses" (FY2025 SLCGP $91.7 million; Tribal Cybersecurity Grant Program $12.1 million) (read Nov. 15, 2026). Read it online. ↩
  34. National Association of Counties, "Congress Considers Bills to Reauthorize State and Local Cybersecurity Grant Program" (House passage of the PILLAR Act, H.R. 5078, by voice vote Nov. 17, 2025; reauthorization through 2033; 60 and 70 percent federal shares, plus five points for full MFA by Oct. 1, 2027; Senate bill by Sens. Hassan and Cornyn introduced Dec. 1, 2025; program then set to expire Jan. 30, 2026) (read Nov. 15, 2026). Read it online. ↩
  35. Route Fifty, "New Senate bill would reauthorize cyber grant program," Dec. 3, 2025 (S. 3251, one-year reauthorization for FY2026). Press report (read Nov. 15, 2026). Read it online. ↩
  36. Nextgov/FCW, "Funding bill extends TMF and cyber measures through September," Jan. 20, 2026 (conferenced FY2026 package extending CISA 2015 and the SLCGP through Sept. 30, 2026). Press report (read Nov. 15, 2026). Read it online. ↩
  37. Route Fifty, "State leaders renew call for cyber grant program's renewal," May 26, 2026 (quotations of Rep. Andy Ogles and Tennessee CIO Kristin Darby; Tennessee's $21 million, nearly 90,000 endpoints, more than 21,000 employees trained). Press report (read Nov. 15, 2026). Read it online. ↩
  38. Information Technology and Innovation Foundation, "Congress Can Strengthen State and Local Cybersecurity in One Bill," June 26, 2026 (PILLAR Act cleared the House in November 2025 and had not reached a Senate floor vote); see also Foundation for Defense of Democracies, policy brief, Oct. 5, 2026, titled on its listing as describing the grant program's "third lapse" (https://www.fdd.org/analysis/2026/10/05/federal-grant-programs-third-lapse-endangers-state-cybersecurity/); the brief itself could not be loaded (read Nov. 15, 2026). Read it online. ↩
  39. Idaho Office of Emergency Management, State and Local Cybersecurity Grant Program page for local governments (FY2022 round: services instead of cash; risk assessment and gap management $900,000, governance and planning $450,000, training $330,440; no local match; consent agreement; cybersecurity area field officers) (read Nov. 15, 2026). Read it online. ↩
  40. Idaho Office of Information Technology Services, "ITS FY 2026 Budget," Feb. 20, 2025 ($10 million Cybersecurity and Information Technology Resilience fund in the Governor's recommendation; service billing fund up a net 1.6 percent) (read Nov. 15, 2026). Read it online. ↩
  41. NIST Special Publication 800-181 Revision 1, Workforce Framework for Cybersecurity (NICE Framework), November 2020; NICE Framework components are updated separately on the NICE website (read Nov. 15, 2026). Read it online. ↩
  42. Gartner, press release, "Gartner Predicts Nearly Half of Cybersecurity Leaders Will Change Jobs by 2025," Feb. 22, 2023 (25 percent to move to different roles because of work-related stress) (read Nov. 15, 2026). Read it online. ↩
  43. The White House, "Fact Sheet: Biden-Harris Administration Accomplishes Cybersecurity Apprenticeship Sprint," Nov. 15, 2022 (194 new cybersecurity registered apprenticeship programs approved or in development; more than 7,000 apprentices hired, more than 1,000 in the private sector). Archived; government-reported figures (read Nov. 15, 2026). Read it online. ↩
  44. U.S. Securities and Exchange Commission, EDGAR full text search (read Nov. 15, 2026). Read it online. ↩
  45. USAspending.gov, official source of federal spending and award data (read Nov. 15, 2026). Read it online. ↩
  46. Idaho Code Title 74, Chapter 1, Public Records Act, Idaho Legislature (read Nov. 15, 2026). Read it online. ↩
  47. CISA, "Free Cybersecurity Services and Tools" catalog (read Nov. 15, 2026). Read it online. ↩

Check yourself

1. In the 2025 IANS Research and Artico Search Security Budget Benchmark, what was the average security share of total IT spending?

2. Which category was the largest share of the average security budget in the 2025 IANS data?

3. Under 23 NYCRR 500.4 as amended in 2023, what must the senior governing body confirm about resources?

4. What does the HIPAA Security Rule, 45 CFR 164.306(b), say about cost?

5. In FAIR, risk is described as:

6. The Gordon-Loeb model suggests that the best investment to protect a given set of information is no more than about what share of the expected loss?

7. Which statement about the IBM and Ponemon Cost of a Data Breach Report is accurate?

8. What was the minimum non-federal cost share for single-entity projects in the FY2025 State and Local Cybersecurity Grant Program?

9. Why did the OCC assess an $80 million penalty against Capital One in August 2020?

10. According to the Idaho Office of Emergency Management, how did Idaho's planning committee choose to use its early SLCGP funds for local governments?

Terms in this lesson

Security budget benchmark
A survey average of what peer organizations spend on security, usually as a share of IT spending or revenue; useful for comparison, not as a target.
End-user security spending
Gartner's measure of what buyers worldwide pay for security software, services and network security equipment.
Expected annual loss
The probability of a loss event in a year times its likely cost; in FAIR, a range produced from estimates of loss event frequency and loss magnitude.
Loss event frequency
In FAIR, how often a loss is expected to occur in a period, based on how often threats act and how likely they are to succeed.
Loss magnitude
In FAIR, how much a loss event costs, made up of primary loss and, sometimes, secondary loss such as fines, lawsuits and lost customers.
Monte Carlo simulation
Running thousands of simulated years with inputs drawn from estimated ranges to produce a distribution of possible annual losses.
Gordon-Loeb model
An economic model (2002) showing that, under broad assumptions, optimal spending to protect a set of information does not exceed about 37 percent of the expected loss.
Tool sprawl
An accumulation of overlapping security products that raises cost and staff workload without matching gains in protection.
Managed detection and response (MDR)
A service in which an outside provider monitors an organization's systems, investigates alerts and helps respond, often around the clock.
Co-sourcing
Sharing a security function between in-house staff and a service provider, for example a provider covering nights and weekends.
Chargeback
A government or corporate funding model in which a central IT agency bills other units for services, often with security costs included in the rates.
State and Local Cybersecurity Grant Program (SLCGP)
A federal grant program created by the 2021 infrastructure law (6 U.S.C. 665g) that provided $1 billion over FY2022 to FY2025 to states for state, local and rural cybersecurity, with a rising local match.
Cost share (match)
The portion of a grant-funded project's cost that the recipient must pay from non-federal funds; 40 percent for single entities in the FY2025 SLCGP round.
Skills-based hiring
Hiring based on demonstrated ability, through practical tests and relevant experience, rather than degrees or years of experience alone.
Registered apprenticeship
A paid job with structured training under a standard approved by the U.S. Department of Labor or a state apprenticeship agency.
Risk acceptance record
A written decision naming who accepted a risk, for what period and at what estimated cost, typically made when a security request is not funded.

Full glossary

Sources