Tenable Blog

In recent years, the increased availability of IoT and OT devices has enabled the electric grid to operate more efficiently. But, these devices also expand the cyber threat landscape, creating prime targets for cybercriminals.

Connected devices – and the infrastructure that supports them – open the grid to hackers. And, the potential consequences are serious. For example, a major disruption to the grid could inconvenience millions of users, threaten the safety of hospital patients or throw global markets into chaos.

The company is top-ranked in strategy and current offering.

Tenable was among 13 select companies invited by Forrester to participate in its October 17, 2019, Forrester Wave™ evaluation, Vulnerability Risk Management, Q4 2019. In this evaluation, Tenable was cited as a Leader in Vulnerability Risk Management (VRM).

As vulnerability management evolves, organizations are seeing increased need for prioritization, benchmarking and flexible reporting. Here are five things to keep in mind when choosing a VM solution.

Vulnerability management is once again rising to the top of the security agenda — driven by the risks from new technologies, speed of new threats and greater board attention on cybersecurity. As a result, many organizations are now modernizing their VM programs.

What’s out: CVSS-based prioritization, blind spots, inflexible reporting.

Administrators rejoice: only nine of the 59 vulnerabilities in Microsoft's October 2019 Security Update are rated critical.

Microsoft’s October 2019 Patch Tuesday contains updates for 59 CVEs, nine of which are rated critical. Administrators may rejoice this month with a smaller than usual Patch Tuesday. The following is a breakdown of the most important CVEs from this month’s release.

The new Solutions view page in Tenable.sc 5.12 helps you unlock the power of Predictive Prioritization and the Vulnerability Priority Rating. Here’s how.

The National Vulnerability Database has analyzed nearly 13,000 vulnerabilities so far in 2019. Patching each of those vulnerabilities requires time, effort and resources. But where does one start? How do you identify those vulnerabilities with the highest likelihood of causing a business-disrupting event in your unique environment? Which do you fix first?