The Defendermate blog
Research, industry perspectives, technical deep dives and product updates from the Defendermate team.
Latest · Technical deep dive
Verify the Exploit, Validate the Path
An attack path fires only if the CVE is exploitable where it sits and every step beyond holds. Verify the exploit everywhere, validate the path where it counts.
-
Patching Is Not the Only Move
Patching is the end state, but often not the answer yet. Where else to act on a vulnerability: upstream, on the resource or downstream, until it's safe.
-
You Shouldn't Have to Break Production to Know What's Broken
Pentests and BAS fire exploits at live systems. Non-intrusive verification proves exploitability by reading state, continuously, on every finding.
-
What Is Autonomous Exposure Remediation (AER)?
Gartner's new AER category uses AI agents to deploy remediation. Why verifying exploitability first decides whether it clears the backlog or adds noise.
-
PHP2Shell (CVE-2026-109618, CVE-2026-109619): What Actually Decides Whether You're Exposed
Exploited four days before disclosure. PHP's workarounds don't make you safe, and version numbers mislead. What decides PHP2Shell exposure, build by build.
-
MA-S2: The Disqualifying Deficiencies Most Security Programs Carry Today
Palantir's MA-S2 standard lists disqualifying deficiencies for AI-era security programs: CVSS-only triage and manual MTTR fail. Check yours.
-
Filter Harder. Remediate Smarter. Only Math That Works in the AI Era.
Exploitability = code x configuration x deployment x network x runtime state. No tool checks all five. 80-90% of your cve are false positives.
-
When Every CVE Has an Exploit, KEV Stops Meaning Anything
AI makes exploit generation cheap and universal. When every CVE has an exploit, KEV loses its signal. Condition verification is the only filter left.
-
Is It Exploitable? A Triage Framework
CVSS, EPSS, and KEV don't tell you if a CVE is exploitable in your environment. This three-step framework shows how to check.
-
Why Does Your Cloud Workload Have So Many CVEs?
347 CVEs in a small container app. 12,000 across the fleet. Seven structural forces explain why most findings aren't exploitable.