The file security gap is the difference between how well an organization believes it protects files and what its visibility, tools, and processes demonstrate. A wide gap leaves analysts triaging files that leadership assumes are already handled, and it hides risk until a breach exposes it. |
|---|
Key Takeaways
- IT and security teams already spend 42.5% of their time on file-related security work
- Only 16.9% of respondents report full visibility into the file lifecycle
- 94.5% of organizations rate their file security maturity higher than evidence supports
- File-related incidents cost affected organizations an average of $2.2 million over two years
The queue is already long when the analyst sits down. Most of it is files from outside: a supplier’s attachment, a vendor-portal download, a partner transfer. Nothing has fired an alert, and nothing has a verdict. Two floors up, the CISO is rewriting a slide for Thursday’s board meeting. The self-assessment says file security is mature, and the CISO would like a way to check. Both assume the incoming files have been dealt with. An Osterman Research survey published in October 2026 tested that assumption.
What Does the Osterman 2026 File Security Report Say?
Osterman Research’s 2026 Enterprise File Security Report, commissioned by OPSWAT, surveyed US organizations across industries in July 2026. Four findings matter most to SOC analysts and CISOs, and the table below ties three of them to the opening scene.
Opening Scene Backed by Research Data
SOC Daily Reality | Osterman Research Finding |
A queue of files without verdicts | 42.5% of IT and security time goes to file-related security |
A slide that says “mature” | 94.5% rate themselves above what their own answers support |
No way to check | 16.9% report full file lifecycle visibility |
Where Does the Analyst’s Week Go?
A large share of it goes to files. According to Osterman Research, IT and security teams already spend 42.5% of their time on file-related security activities, and most respondents expect that share to grow as AI-driven threats add to the load.
The report does not say how those hours are spent, but the second number explains why they are hard to cut. Only 16.9% of respondents report full visibility into the file lifecycle, so analysts work on files they cannot fully trace, and a file without a verdict becomes a ticket.
The Reason CISOs Overestimate File Security Maturity
The CISO sees the same problem from the other side because a team that cannot see every file also cannot measure how well it protects them. Self-assessment runs ahead of evidence. Osterman Research found that 94.5% of respondents rate their file security higher than their own survey answers support. The report leaves the cause open, noting that confidence may rest on vendor claims or on incident data.
For a CISO, the gap shows up first in the board report and then in the bill. Organizations that suffered a file-related breach or security incident averaged $2.2 million in total cost over two years, and a board told file security is mature will ask why. The report defines incidents broadly, including employee negligence and AI agents, so the figure is not the cost of malware alone.
Malicious Files Can Come from Trusted Sources
The report also shows where that exposure starts. Files from outside the organization carry the most risk, regardless of whether the sender is trusted. Respondents rated three ways files enter an organization as the riskiest: downloads from unknown sources, email and links, and managed file transfer.
Recent news shows the pattern. A tampered build of Anthropic’s Claude Code extension planted an SSH backdoor on developer machines, and Cursor said it was live in its marketplace for about 11 hours on October 29, 2026. Anthropic said its own systems were not compromised and that an attacker used access to Cursor’s marketplace to publish the tampered copy.
The incident involved a package, not a document, but the pattern is the same. A trusted channel delivered content nobody inspected. A European healthcare provider met it with a supplier’s file, finding a zero-day exploit that had bypassed its single-antivirus defenses. Nobody looked inside because nobody had a reason to, and that is the visibility problem behind the 16.9%.
What Is Prevention-First File Security?
That leaves a choice between hunting for each bad file and stopping it before it reaches anyone. Prevention-first file security aims to stop file-borne threats from reaching users without relying on detecting each one first, and CDR (content disarm and reconstruction) is a key technology.
Osterman Research found that organizations taking this approach report higher extreme confidence in most of the situations it tested, especially where files cross organizational boundaries. Some files cannot be sanitized, such as executables and installers, and those still need a verdict.
Four Industries, One File Security Gap
The same problem plays out in every industry. Each receives files from outside parties it does not control, and only 16.9% of respondents can see the full file lifecycle. The remedy the Osterman data points to is to inspect and sanitize files before users open them and give analysts a verdict instead of raw evidence.
Government and Defense
Files cross network and classification boundaries, often into air-gapped environments. With only 16.9% of respondents reporting full lifecycle visibility, a government CISO answers auditors for a posture that cannot be fully evidenced, while analysts judge each third-party transfer without the full picture.
Finance
Customer documents and transaction files flow all day. For the CISO, a $2.2 million average incident cost puts a price on the maturity problem, and a board told file security is mature will want to know why. For analysts, falsified AI-generated files are a rising priority, so a forged invoice no longer looks forged.
Energy
Continuous operations leave small SOC teams carrying the 42.5% file security load, hours taken from OT monitoring. A customer story describes a North American energy provider whose SOC faced alert floods and intelligence without verdicts.
Manufacturing
Suppliers send drawings, firmware, and orders from outside. A plant that assumes its supplier channel is safe is making the assumption the survey tested, and 94.5% of respondents rated their maturity above what the evidence supported. For the analyst, every download is a judgment call, and for the CISO the supplier channel is a risk nobody has yet measured.
A Verdict Instead of a Queue
A SOC analyst needs one defensible verdict per file, and a CISO needs it visible in reporting. MetaDefender Aether™ is OPSWAT’s AI-driven unified five-layer zero-day detection solution designed to turn multi-layer evidence into a single confidence-based verdict on suspicious files. It works alongside prevention layers, covers the files sanitization cannot, and gives analysts the behaviors and indicators of compromise behind each verdict.
In the energy provider’s case, the published story lists less alert noise, faster SOC workflows, and reduced burnout. The analyst opens the queue and sees verdicts. The CISO rewrites Thursday’s slide with evidence underneath it.
See What Else the Research Holds for You, as Explained by Its Author
The blog covers four findings from the Osterman Research report. Our webinar titled “Files in the AI Era: What’s Changing, What’s Coming, and What It Breaks” covers the rest, with the analyst who wrote the study.
Michael Sampson of Osterman Research walks through five findings, including where attacker attention has moved, why the industry is split between detection and prevention, and why the biggest barriers are leadership support and knowledge, not budget.
George Prichici, OPSWAT’s VP of Products, then explains what those findings mean in practice. The session is independent research, not a product demo, so it works whether you are a SOC analyst looking for a way to cut triage time or a CISO building the next board slide.
FAQ
What is the file security gap?
The file security gap is the distance between how mature organizations believe their file security is and what their practices support. Osterman Research found 94.5% of respondents rate themselves above the evidence.
How much time do security teams spend on file security?
IT and security teams spend an average of 42.5% of their time on file-related security activities, and most respondents expect that to grow.
What is prevention-first file security?
Prevention-first file security aims to stop file-borne threats from reaching users without relying on detecting each one first. Prevention-first organizations report higher extreme confidence in most of the situations Osterman Research tested.
Does the Osterman report cover every industry?
The survey covered US organizations across industries and does not report results by sector.
