Most business breaches are not exotic. They trace back to a short list of failures that are boring, documented, and fixable: unpatched systems, backups nobody has tested, applications that trust user input, and a security culture that got handed to the IT department and never picked back up by leadership. The four challenges below are the ones worth your attention because each one has a concrete, executable remedy, and each one fails the same way when nobody owns it.
Quick Take
The four challenges here are governance problems with technical remedies. The CEO sets the culture and the objectives, a named Security Program Manager runs the program, and the IT team executes. Backups, patching, vulnerability prioritization, and multi-factor authentication are table stakes: necessary, layered, and never sufficient on their own. No single control guarantees you avoid an incident, and any vendor promising otherwise is selling comfort, not security.
Challenge 1: Ransomware Encrypts Your Business and Demands Payment
Ransomware is malware designed to encrypt files on a device, rendering those files and the systems that depend on them unusable; the attacker then demands a ransom in exchange for decryption, as the U.S. Cybersecurity and Infrastructure Security Agency defines it on StopRansomware.gov. That definition explains the defense: if the core damage is encrypted, unusable data, then your recovery plan is the thing that decides whether an incident becomes a crisis.
The same CISA page lays out a short set of controls. None of them are novel. All of them are routinely skipped.
- Maintain offline, encrypted backups of your data, and test them regularly. An untested backup is a hope, not a control.
- Patch and update software and operating systems on a schedule. Not when someone remembers.
- Scan for vulnerabilities regularly, especially on internet-facing devices, to limit your attack surface.
- Report incidents. In the U.S., ransomware victims should report to federal law enforcement via IC3 or a Secret Service Field Office, and can request technical assistance or share information by contacting CISA.
Warning
Backups, patching, and scanning are layers, not substitutes. The CISA ransomware guidance is a floor for building a program, not a guarantee you will never have an incident, and no single control above will stop every attack on its own.
Challenge 2: Breach Costs Are Climbing, and AI Is Reshaping the Attack
The financial direction is unambiguous even if the headline number isn’t. IBM’s 2026 Cost of a Data Breach Report, produced with the Ponemon Institute, states that the global average cost of a data breach rose 12% over the prior year to a record high. IBM attributes the increase to higher detection, escalation, and lost-business costs, the slow, expensive tail of an incident rather than the initial hit.
The same report flags a shift in how attacks arrive: AI-driven attacks are growing, led by AI deepfake impersonations and AI-enabled malware, which drove the highest volume of those incidents. Read that as a warning about your verification habits. A convincing voice on a phone call or a polished video message is no longer evidence of identity.
Verizon’s 2026 Data Breach Investigations Report, which analyzes incidents from November 1, 2024 through October 31, 2025, adds a structural finding: software vulnerabilities now lead as the breach entry point, ahead of stolen passwords. Attackers are shifting focus from tricking people to exploiting systems. Ransomware remains involved in a meaningful share of breaches, though payouts are shrinking as more businesses decline to pay. Generative AI, per Verizon, is now bolstering multiple attack techniques across the kill chain.
| Trend | What the report states | What it means for your program |
|---|---|---|
| Breach cost direction | The IBM/Ponemon report states the global average cost rose 12% year over year to a record high | Budget for detection, escalation, and business disruption, not just prevention |
| AI-driven incidents | Deepfake impersonation and AI-enabled malware drove the highest volume of AI-driven incidents (IBM) | Strengthen identity verification and out-of-band confirmation for payments and access requests |
| Leading breach entry point | Software vulnerabilities now lead, ahead of stolen passwords (Verizon) | Shift patch and vulnerability management up your priority list |
| Ransomware prevalence | Ransomware involved in a share of breaches; payouts shrinking as businesses decline to pay (Verizon) | Assume recovery capability matters more than ransom negotiation |
Challenge 3: Exploitable Vulnerabilities — Injection Flaws and What’s Actually Being Attacked
Not every vulnerability deserves the same urgency, and treating them all as equal is how patch backlogs become permanent. Two things matter here: the classes of flaw that cause outsized damage, and a way to decide what to fix first.
SQL injection is the textbook example of a high-impact flaw. Per OWASP, a SQL injection attack inserts a SQL query through client input to the application. A successful exploit can read sensitive data, modify or delete database records, execute administrative operations such as shutting down the database management system, recover files from the server’s file system, and in some cases issue commands to the operating system. OWASP notes that SQL injection allows attackers to spoof identity, tamper with data, void transactions or change balances, fully disclose data, destroy it, or become administrators of the database server. It remains common in PHP and ASP applications, and OWASP generally considers it a high-impact severity issue, though the practical severity is limited by attacker skill and, to a lesser extent, defense-in-depth measures such as low-privilege database connections.
If you build or buy software, that last point is the actionable one: parameterized queries and least-privilege database accounts shrink the blast radius even when a flaw slips through. Teams reviewing application code can lean on code risk platforms like Apiiro to surface risky patterns earlier in the development cycle, though the underlying fix is still disciplined query construction and code review.
For everything else in your estate, stop trying to patch everything at once. CISA’s Known Exploited Vulnerabilities (KEV) catalog is the authoritative source of vulnerabilities that have actually been exploited in the wild, and CISA recommends using it as an input to your vulnerability management prioritization framework. Each entry carries a date added and a due date, which turns “we should patch more” into a dated work queue.
| Dimension | Patch everything, in order | KEV-prioritized |
|---|---|---|
| Prioritization logic | Severity score or vendor order | Whether the vulnerability is known to be exploited in the wild |
| Time to first fix | Slow, because the backlog competes with everything | Fast, because exploited items get a due date |
| Best fit for | Small estates with few systems and spare capacity | Any organization with more vulnerabilities than remediation hours |
| Main limitation | Critical exploited flaws can sit behind low-risk noise | Requires inventory and scanning to know what you have |
Challenge 4: Weak Security Culture and Governance
This is the challenge that decides whether the other three get solved. CISA’s cyber guidance for small businesses is blunt about the trap: most organizations assume the IT team alone is responsible for security, and that assumption increases the odds of a compromise. Culture cannot be delegated.
The CEO’s job, per CISA, is to establish a culture of security: talk about it to direct reports and the whole organization, fold security updates into regular communications, and set quarterly goals with leadership that include meaningful security objectives aligned to business goals. Security has to be an everyday activity. CISA’s example objectives are refreshingly concrete: adoption of multi-factor authentication (MFA), the percentage of systems fully patched, and the percentage of systems backed up.
The second structural move is naming a Security Program Manager. That person does not need to be a security expert or even an IT professional; their job is to ensure the organization implements the key elements of a strong program and to report progress and roadblocks to leadership. For a resource-constrained business, that framing is the difference between a program that exists and one that lives in someone’s spare time.
For a formal risk-management structure, NIST’s Cybersecurity Framework (CSF 2.0) is designed to help organizations understand and improve how they manage cybersecurity risk, with Profiles, Quick Start Guides, and Informative References to map your existing work onto a recognized structure. It is a management tool, not a compliance checkbox.
Info
CISA explicitly states that following its small-business advice is not a guarantee you will never have a security incident. It lays the groundwork for an effective program, nothing more.
Who owns what
- CEO: Owns the culture, sets security objectives aligned to business goals, and selects and supports the Security Program Manager.
- Security Program Manager: Owns implementation of the program’s key elements and reports progress and roadblocks to leadership. No security or IT background required.
- IT team: Owns execution: patching, scanning, backup operations, and access controls.
- Everyone else: Owns the everyday behavior the culture depends on, reinforced by leadership communication rather than a one-time training module.
If your organization is growing and the security conversation keeps getting deferred, the same pattern shows up in other operational areas. See our piece on the challenges companies face as they grow for the broader version of this problem.
Cross-Cutting: Encryption and Key Management Protect the Backups You Rely On
Encrypted backups are only as good as the keys that unlock them. Lose control of key material and your recovery plan evaporates at the worst possible moment. NIST SP 800-57 Part 1 Rev. 5, published in May 2020, provides general guidance and best practices for managing cryptographic keying material: the key types you may employ, the protection each type requires, and the functions involved in key management. If you run a formal public key infrastructure, that guidance is the reference to align your key lifecycle with. For smaller teams, the practical version is simpler: know where your keys live, who can access them, and how you would restore access if the person holding them left the company.
Build a Layered Security Program in Eight Steps
Work through these in order. Each step depends on the one before it, and the whole sequence is designed to be runnable by a small team without a dedicated security department.
- Inventory your systems and scan for vulnerabilities. You cannot prioritize what you have not catalogued. Include internet-facing devices first, since CISA specifically calls these out as the priority for scanning to limit your attack surface.
- Patch and update software and operating systems on a defined schedule. Set the cadence in writing and assign an owner. Ad hoc patching is the default failure mode.
- Check your findings against the CISA KEV catalog. Any vulnerability on the KEV list is known to be exploited in the wild and jumps the queue ahead of everything else.
- Remediate KEV-listed items by their due dates, then patch the remainder by risk. The catalog’s date-added and due-date fields give you a defensible work order.
- Stand up offline, encrypted backups. Offline matters: an attacker who reaches your backup server has removed your recovery option.
- Test restores on a regular schedule. A backup that has never been restored is an assumption. Test the restore, not just the backup job’s success message.
- Roll out multi-factor authentication. Make MFA adoption one of your quarterly security objectives, as CISA recommends, and track the percentage of accounts covered.
- Name a Security Program Manager and define your incident reporting path. The manager reports progress and roadblocks to the CEO. For ransomware, the reporting path runs to IC3 or a Secret Service Field Office, with CISA available for technical assistance.
Verify the result
- A full restore from backup completes successfully and the restored data is usable.
- Every KEV-listed vulnerability affecting your estate has been remediated by its due date or has a documented, owned exception.
- MFA coverage, patched-system percentage, and backed-up-system percentage are tracked as reported objectives.
- A named Security Program Manager is reporting progress and roadblocks to the CEO on a regular cadence.
The restore test fails or the restored data is incomplete
Treat this as a live incident rehearsal, not a routine failure. Check whether the backup job captured the systems you assumed it did, whether the encryption keys are available and current, and whether the restore target has enough capacity. Fix the gap before you need the backup for real, and if key access is the blocker, revisit your key management practices against NIST SP 800-57 guidance.
Patching causes conflicts or breaks a business-critical application
Do not respond by pausing patching across the estate. Isolate the affected application, document the conflict, and keep patching everything else on schedule. For KEV-listed vulnerabilities on the affected system, apply compensating controls such as network segmentation or restricting access until the conflict is resolved, and record the exception with an owner and a review date.
The Verdict: Own the Program, Layer the Controls, Expect No Guarantees
None of these four challenges require a security team the size of a bank. They require a CEO who treats security as a business objective, a named person accountable for the program, and an IT function that patches, scans, backs up, and tests on a schedule. The technical controls are well documented by CISA, NIST, and OWASP; the failure mode is almost always organizational.
Start with the step that exposes the most risk fastest: inventory and scan, then check what you find against KEV. From there, the backup restore test is the single exercise most likely to change how you think about your readiness. If your team is distributed and access control keeps slipping, our guide to simple tech solutions for scattered teams covers the practical side of locking down accounts across locations. When phishing and malicious attachments are the vector you keep seeing, a spam filtering solution belongs in the same layered stack as backups and patching, catching hostile mail before it reaches an inbox.
And keep the boundary honest: layered controls reduce risk, they do not eliminate it. CISA says so directly, and any plan that assumes otherwise is a plan built on comfort rather than evidence.
Key Takeaways
- Ransomware’s core damage is encrypted, unusable data, so tested, offline, encrypted backups are your recovery plan, not an optional extra.
- Breach costs are rising and AI-driven impersonation is reshaping how attacks arrive; verify identity out of band before acting on payment or access requests.
- Software vulnerabilities now lead as the breach entry point, and KEV turns an impossible patch backlog into a dated, defensible work queue.
- Security culture cannot be delegated to IT; the CEO sets the objectives and a named Security Program Manager runs the program.
- Encryption is only as strong as your key management: know where your keys live and who can restore access.
💬 Comments