Gartner’s Top Strategic Technology Trends for 2027
Case Study
How The University of Kansas Health System Automated Vulnerability Management with Remedio
An academic medical center based in Kansas City, and one of the nation’s leading providers of cancer research and cancer care. The health system serves as a destination for complex, high-acuity patient care.
Like most large healthcare organizations, the University of Kansas Health System was up against a problem the entire industry has struggled with for two decades: as software becomes more pervasive, the number of vulnerabilities in that software increases exponentially. Every newly discovered vulnerability, whether a critical zero-day or routine Patch Tuesday update, generated another remediation ticket for an already-stretched IT team.
The Challenge: A Backlog That Never Stops Growing
Like most large enterprise healthcare organizations, the University of Kansas Health System faced a growing backlog of security flaws that far exceeded manual team bandwidth. Every newly discovered vulnerability, whether a critical zero-day or routine Patch Tuesday update, generated another remediation ticket for an already-stretched IT team.
By shifting away from traditional detection-only models and implementing vulnerability remediation automation, the IT team gained the ability to execute, validate, and roll back changes safely across thousands of endpoints without risking clinical downtime.
“The volume of the remediation that needs to be implemented simply outpaces the capacity that they have to implement them.”
Michael Meis
Associate Chief Information Security Officer
The root of the problem, in his view, was structural. Vulnerability management as a discipline has always focused on detection and prioritization; finding the vulnerability, scoring its severity, and handing it off.
"Then you create a ticket and send it over to the remediation team, and they get to it whenever they can," he says. "Because of that, the remediation of those vulnerabilities is always manual. Traditional vulnerability management approaches have never provided an automated way to scale your vulnerability remediation."
The cost of that 99% doesn't disappear just because it's deprioritized. Every unremediated weakness stays open as a way in, and for a health system, one breach can mean exposed patient data, regulatory penalties, and ransomware that takes clinical systems offline.
The backlog also turns compliance into manual labor. Each unfixed finding has to be tracked, justified, and explained again at the next audit. Teams spend hours pulling scan reports and building spreadsheets to show auditors what's been fixed, and when configurations drift, a control that passed last year can quietly fail this year. Skilled staff end up proving the organization's security posture instead of improving it.
“We don’t need to know that there is more blood on the floor. We don’t need to know which tile we should go scrub first. We need people to come in, grab a mop and help us start cleaning up.”
The Solution: Why Remedio Earned Their Trust
Before Remedio, UKHS was reluctant to embrace autonomous remediation. The idea that something could make changes to their environment with a simple click worried decision makers. The last thing they wanted was a solution that would be more disruptive than the problem its solving.
That hesitation is prudent for a healthcare delivery organization that provides lifesaving care running on the back of their technology. Outages are more than inconveniences; they're measured in mortality rates.
“It was important for us to have confidence in the tools that we were implementing and the impact that it would have on those technologies.”
Fortunately, Meis and his team didn't start from zero. The University of Kansas Health System already relied on Remedio as its core configuration hardening solution, using it to enforce secure baselines and eliminate misconfigurations across the environment. That track record of safe, reliable changes in a clinical setting gave the team a foundation of trust. When it came time to extend Remedio into autonomous vulnerability remediation, they were expanding a partnership that had already proven itself.
Even so, the bar was high. Two capabilities in particular gave Meis and his team the confidence to move forward:
Pre-remediation visibility.
Before any change was made, the team could understand exactly what would be affected – "the ability to understand what the impact is going to be in your environment when that last particular service was used or when it wasn't used, and what it was going to break, essentially, when you clicked the remediate button."
The ability to roll back.
If a remediation had an unexpected impact, it could be reversed quickly. "That gave us the confidence that even if we did make a mistake, that we would be able to recover from that mistake very quickly – again, to ensure that we're not negatively impacting our patients."
The Results: 3000 Hours Back, Zero Downtime, and a Broader View of Risk
For a team that had been stuck in an endless remediation backlog, the operational gains were immediate and measurable:
- 1 3000 hours saved on remediation work that would otherwise have been done by hand
- 2 2 FTEs of productivity added, allowing the team to go further and deeper with their work
- 3 Zero downtime ,including one major outage prevented before it could reach clinical systems
In a hospital, that last number matters most. It’s exactly the risk Meis worried about before adopting Remedio. Because Remedio maps dependencies and blast radius before any change is made, the team caught a remediation that would have caused a major outage and stopped it before it went out. Thousands of fixes went live without disrupting a single clinical system.
Audit preparation changed too. Every remediation Remedio performs is logged, controlled, and reversible, and continuous validation against secure baselines confirms each fix is still in place. Instead of reconstructing their posture from scan reports and spreadsheets before every audit, the team can show auditors a running record of what was fixed, when, and that it stayed fixed.
The hours saved did more than shrink the backlog. They changed how the health system thinks about vulnerabilities. Historically, "vulnerabilities" meant a narrow slice of the attack surface: CVEs with published scores and available patches. With remediation capacity no longer the bottleneck, that definition has broadened considerably.
The Human Impact: Fix Fearlessly, and Have It Stay Fixed
Beyond the technical and operational gains, Meis points to a cultural shift on his team, rooted in a problem familiar to every security professional: the endless remediation loop. "You set a configuration baseline, you clean up against it, and then a year later you're back doing it again."
Remedio breaks that cycle by continuously validating the environment against its secure baselines, so drift is caught and corrected before it can build back into a backlog. And because every change is checked for dependencies and blast radius before it's made, with instant rollback if needed, the team can trust that a fix won't create a new problem somewhere else.
Using Remedio has allowed the team to have confidence that when they fix something, it stays fixed. That may sound like a small thing, but for most organizations, it's a source of continued frustration.
“The ability to be able to say that we fixed this and we know it will stay fixed has been a huge morale improvement for my team.”
For a team that once faced a backlog with no visible end, that confidence changes the work itself: every remediation is progress that holds, not ground that will have to be retaken next year.
Looking Ahead
The University of Kansas Health System isn't stopping at vulnerability remediation. Meis and his team are now turning their attention to AI governance across the organization – both commercial generative AI tools and the local agents being deployed on endpoints – with the goal of enabling safe adoption without stifling innovation. Alongside that effort, the team is building out visibility into non-human identities, working to understand how those identities are used, what they can access, and how their actions are tracked across the enterprise.
As Meis frames it, AI is reshaping the security landscape on both sides of the fight: it's accelerating attackers, compressing the time between vulnerability discovery and exploitation, while also introducing new risks around ungoverned use inside the organization.
"The risk of shadow AI, or ungoverned AI adoption, presents even more risk than software as a service, because not only are you putting data into these tools, but they can also take actions on behalf of your users."
“The risk of shadow AI, or ungoverned AI adoption, presents even more risk than software as a service, because not only are you putting data into these tools, but they can also take actions on behalf of your users.”
Michael Meis
Associate Chief Information Security Officer
Having brought discipline and scale to vulnerability remediation, the health system is now applying the same rigor to the next frontier.
Remedio is meeting that need with AI Govern, a continuous AI exposure management platform that discovers, governs, and automates remediation of AI risk across agents, copilots, IDEs, browser extensions, MCP connectors, and local AI tooling – giving security teams the same visibility, automatic correction, and instant rollback that earned KU Health System's trust in vulnerability remediation, now applied to shadow AI and non-human identities.