Phying News
P非影 中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

How Paddle Strengthened Its Security Posture with ProjectDiscovery

projectdiscovery.io | vulnerability | #bug-bounty | #attack-surface | #compliance | #red-team | #case-study | #pci-dss | #soc2 | #projectdiscovery | #paddle

Summary

Paddle consolidated scattered Nuclei and Subfinder scans onto ProjectDiscovery, centralizing attack surface visibility, cutting discovery from days to hours, and supporting PCI DSS and SOC 2 audits.
Published
Collected

original ↗

Related coverage

vulnerability · projectdiscovery.io
Nuclei Templates - April 2026
Nuclei Templates v10.4.2 and v10.4.3 ship 226 new templates covering 123 CVEs—about 10 actively exploited KEV entries—and push deeper into AI/LLM attack surface with 27 first-time contributors joining.
vulnerability · projectdiscovery.io
Securing the distributed perimeter: How Elastic scaled proactive detection with ProjectDiscovery Cloud
Elastic ran ~50,000 servers across AWS, Azure, and GCP and adopted ProjectDiscovery Cloud, scanning 14,500 external assets in under five minutes after outgrowing legacy scanners like BitSight.
vulnerability · projectdiscovery.io
How ConnectWise streamlined vulnerability detection with ProjectDiscovery
ConnectWise moved vulnerability scanning for 20,000+ AWS instances from Tenable Cloud to ProjectDiscovery, cutting scan time for 10,000 assets from two days to 15 minutes and retiring custom scripts.
vulnerability · projectdiscovery.io
Open by design, trusted by enterprises: how we keep Nuclei templates reliable at scale
Community-driven Nuclei templates stay enterprise-grade: each YAML template is lab-reproduced, checklist-hardened, and double-reviewed, proving exploitability instead of guessing from versions.
vulnerability · projectdiscovery.io
From Detection to Validation: Fixing Broken Vulnerability Workflows
Version scanning lies by omission: only ~6% of CVEs are exploited. Nuclei validates exploitability at runtime with matchers, extractors, and multi-step flows, as the 2025 CrushFTP cases illustrate.
vulnerability · projectdiscovery.io
The Coverage Lie: Why Current Vulnerability Scanners Fail to Stop Breaches
Legacy scanners fail from untrusted version-based guesses, not coverage gaps: only ~6% of CVEs are exploited, yet weaponization is fast. Runtime validation plus KEV focus yields actionable results.
back