CYBERSECURITYTRACKER
Permanent story citation

Stopping Vulnerable Driver Attacks

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 5172

As cited

Copy frozen at (site build).

Stopping Vulnerable Driver Attacks

No summary had been written when this copy was frozen.

First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Stopping Vulnerable Driver Attacks

Ransomware actors increasingly exploit vulnerable drivers to disable endpoint security products before encryption attacks. Elastic Security released 65 YARA rules for detecting vulnerable driver abuse and deployed inline blocklisting in Endpoint version 8.3 and later. The firm recommends organizations combine blocklisting, allowlisting, behavior controls, and anomaly detection to defend against kernel mode attacks.

Why it matters: Organizations using vulnerable drivers or third-party drivers face kernel-level compromise that security tools cannot detect or prevent; implement blocklisting immediately and evaluate allowlisting strategies for your driver inventory.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Stopping Vulnerable Driver Attacks

Ransomware actors increasingly exploit vulnerable drivers to disable endpoint security products before encryption attacks. Elastic Security released 65 YARA rules for detecting vulnerable driver abuse and deployed inline blocklisting in Endpoint version 8.3 and later. The firm recommends organizations combine blocklisting, allowlisting, behavior controls, and anomaly detection to defend against kernel mode attacks.

Why it matters: Organizations using vulnerable drivers or third-party drivers face kernel-level compromise that security tools cannot detect or prevent; implement blocklisting immediately and evaluate allowlisting strategies for your driver inventory.

VendorsMicrosoft
Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary