A Faster Horse
Today, those in vulnerability management often create development environments (aka sandboxes) to test whether or not new patches will cause disruptions on their networks…just like they’ve been doing for 3 decades. Which leads to only one conclusion: ARPA-H is funding an effort to build a faster horse.
Why Patches Fail
The psychological source of this particular patch failure, of course, is the omnipresent fear that applying patches will result in a service disruption that will, at a minimum, make for a miserable few hours for IT practitioners, and could result in more serious repercussions. trackd was founded to counter exactly this rational, but largely anachronistic, fear.
How to Patch Vulnerabilities: A Comprehensive Guide
Leaving vulnerabilities unpatched can expose organizations to significant risks. Attackers actively search for known vulnerabilities to exploit, and exploiting unpatched vulnerabilities is a common technique. Such attacks can result in data breaches, financial losses, reputational damage, and legal liabilities.
Why Patches Fail
In this blog series, we’ll look at some of the more mundane – albeit common and operationally-significant – reasons patches fail.
MSP Patch Management: The Delicate Balance Between Operational Risk & Security Risk
The only thing better than learning from your own mistakes is learning from the mistakes of others. At trackd, we have come up with a radically simple but elegant solution to help organizations differentiate between the 98% of patches that are necessary and safe, and the 2% that will have your clients calling you on the weekends.
Providing Cybersecurity to the Underserved, and Building a Business by Doing So
At trackd, our free users are essential to our business plan; we literally can’t deliver the unique solution we’ve designed without them.
Weighing down cyber risk options: how to make objective cybersecurity decisions without negatively impacting the organization’s IT teams?
It’s often paid lip service to (or worse, intentionally neglected), and rarely appreciated, but there’s an operational cost to be paid for security. Security controls create inefficiencies, and those security measures can also introduce operational risk.
The Never-Ending Battle: Routine Patching vs. Operational Stability
It’s time for vulnerability management technology innovators to spend less time identifying and reporting on vulnerabilities, and more time building tools to help IT teams fix them more efficiently…and without their fingers constantly crossed.
Is the cybersecurity community’s obsession with compliance counter-productive?
Show me a large enterprise that was breached and I’ll show you a large enterprise adhering to multiple compliance standards.
Why Vulnerability Remediation Teams Wish They Were All Zero Days
IT professionals endure a lot more criticism for causing downtime when patching than they do for patching too slowly, so their default state is to be exceptionally cautious while absorbing the cyber risk of exposed vulnerabilities.
