SecPod

Learn Search

Search across all Learn content

← Back to Security Research
The First Step Towards Endpoint Security Brilliance

The First Step Towards Endpoint Security Brilliance

This year has forced us into a lot of new challenges in the digital world. During the first half of 2020, Microsoft has seen a 150% increase in vulnerabilities than the entirety of 2019. Security breaches and ransomware attacks are being reported at an alarming rate this year. Cybercriminals now hav...

Nov 1, 2020By Pranav Krishnan2 min read

This year has forced us into a lot of new challenges in the digital world. During the first half of 2020, Microsoft has seen a 150% increase in vulnerabilities than the entirety of 2019. Security breaches and ransomware attacks are being reported at an alarming rate this year. Cybercriminals now have the icing on the cake as remote work norms have taken a permanent spot.

As the cybersecurity expert, you are left with the massive responsibility of securing enterprise endpoints wherever they are. 

Here’s the problem…

The leading cause of security breaches in 2019 was a result of unapplied security patches. Traditional vulnerability assessment tools and practices are not effective anymore with the evolving sophistication and frequency of cyber-attacks. You are probably left with siloed vulnerability assessment and patching tools that force you into manual patching methods, long patching cycles, and inefficient scanning methods. 

The first step: integrated vulnerability and patch management

Vulnerability and patch management are two sides of the same coin. They have to work together to run a tight ship and reduce your attack surface effectively. An integrated approach makes your endpoint security proactive in detecting and mitigating vulnerabilities and is the first step towards endpoint security brilliance.

Download our eBook“Integrated Vulnerability and Patch Management: Your First Step Towards Endpoint Security Brilliance”.We’ve expanded on the problems of siloed tools and the advantages of an integrated approach to vulnerability and patch management.

You can also watch the recording of our webinar about “Reducing risks through Integrated Vulnerability and Patch Management”.

Featured Posts

Open WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels
WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

CVE Research

WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

Oct 1, 2026

Open OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure
OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

CVE Research

OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

Two critical vulnerabilities added to CISA KEV on September 24, 2026 reveal sharply different exploitation timelines. CVE-2026-71362 saw publicly documented exploitation roughly one day after Adobe's patch release, while CVE-2026-5430 had a 133-day vendor-remediation-to-observed-exploitation interval.

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026
Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

CVE Research

Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

Three Linux kernel vulnerabilities entered CISA’s KEV catalog on September 18, 2026, although their Linux 6.12 fixes were available 91–386 days earlier. This analysis separates patch availability, CVE publication, and known-exploitation status without treating KEV dates as first-attack dates.

Sep 28, 2026