Learn about Time to Patch, including how to measure it, and leverage it in dashboards and visualizations with Metabase.
Time to patch is a metric that determines the average amount of time it takes to fix an unknown vulnerability. This is an important visualization to have, as it covers both team efficiency and the degree of risk level associated with your security. The longer it takes for your team to identify and fix a problem, the more vulnerable you are to security breaches.
Get Started
Time to patch covers the entire process of discovering and patching a vulnerability. In a given timeframe, you’ll need to know the number of bugs discovered, and the amount of time it took to patch each vulnerability. Time spent patching / Number of patches created in a given timeframe = Time to patch To create an example, if your total number of minutes spent on discovering and deploying a patch in a 6-month period was 280 minutes and you had 3 bugs, that would mean your time to patch would be a rounded 93.4 minutes. The downside of using this metric is the lack of context. This calculation doesn’t specify the severity of a vulnerability or how labor-intensive it was to patch. Still, time to patch can give you a little insight into how efficient your team is in attacking vulnerabilities as they happen.
Get everyone on the same page by collecting your most important metrics into a single view.
Take your data wherever it needs to go by embedding it in your internal wikis, websites, and content.
Empower your team to measure their own progress and explore new paths to achieve their goals.
That's right, no sales calls necessary—just sign up, and get running in under 5 minutes.
We connect to the most popular production databases and data warehouses.
Invite your team and start building dashboards—no SQL required.
