ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode

Search: “validation”

10,016 items

Searchkeywordsmart Sortlatesthotimportancerelevance
DomainAllCyberAIWindow24h3d7d30dAllIn the wildImportant onlyShow duplicates
CategoryAllVulnerability 3039Exploit / PoC 1126Malware 1083Ransomware 962Industry 873Data breach 771Policy & legal 618Phishing & fraud 615Threat actor 532Research 179Advisory 113Tools 105
SeverityAllcritical 4271high 2328medium 1825low 1380info 212

AWS Certificate Manager sets 2027 end date for email-validated certificate renewals

AWS Certificate Manager will phase out email validation for public certificates during 2027, requiring migration to DNS validation before September 30, 2027.

AWS Certificate Manager will stop offering email validation in new Regions on January 1, 2027, discontinue it for new certificate requests on March 31, 2027, and stop renewing email-validated certificates on September 30, 2027. This precedes the CA/Browser Forum's March 15, 2028 deadline ending email-based domain validation for publicly trusted certificates. AWS is updating the UpdateCertificateOptions API so customers can switch to DNS validation in place while retaining the certificate ARN, with Route 53 support for creating required CNAME records.

Help Net Security · Aug 14, 2026Advisory

AI Changed the Exposure Problem. Validation Needs to Change With It.

Picus Security argues vulnerability validation must combine exploitability, control validation, and agentic pentesting as AI accelerates disclosure volume.

Picus Security reports 35,853 CVEs were published in H1 2026, roughly 49% more than the prior year, while only 495 were catalogued as exploited in the wild and 116 were attacked on disclosure day. The vendor argues CVSS-based triage is inadequate and promotes combining exploitability validation, security control validation, and agentic pentesting into one program. The post also cites Anthropic data showing Mythos-class models surfaced 26,153 open-source vulnerability candidates with only 421 patched upstream, and promotes Picus's Validation Summit '26 on October 14-15.

The Hacker News · 2d agoIndustry

1.1.1.1 now supports post-quantum DNSSEC, all 2,420 bytes of it

Cloudflare's 1.1.1.1 resolver now validates post-quantum DNSSEC signatures using ML-DSA-44, a 2,420-byte NIST algorithm, preparing DNS for post-quantum migration by 2029.

Cloudflare enabled 1.1.1.1 to validate DNSSEC signatures using ML-DSA-44 (algorithm 18), a NIST-standardized post-quantum signature with 1,312-byte public keys and 2,420-byte signatures, roughly 38x larger than ECDSA P-256. The large signatures exceed common DNS-over-UDP limits, forcing fallback to TCP and creating downgrade risks while conventional algorithms must be published alongside. Cloudflare cites the risk of a quantum computer breaking RSA/ECDSA signatures by 2030 and plans full post-quantum security by 2029.

Cloudflare Blog · 6d agoTools1

Your Critical Vulnerabilities Might Not Be Your Biggest Risk

Autonomous penetration testing advocates prioritize exploitable attack paths over raw vulnerability severity for continuous security validation.

The article argues that scanner severity scores lack context: a critical flaw behind strong segmentation may be low priority, while a medium flaw on internet-facing systems can provide a foothold chained toward sensitive data. It positions autonomous penetration testing and attack path validation as the execution layer for continuous security validation, replacing point-in-time assessments. The piece is vendor-authored thought leadership rather than incident or vulnerability news.

The Hacker News · 5d agoIndustry1

The inconvenient truth about AI pentesting: someone has to check all the work

Survey of 158 practitioners shows AI pentesting floods teams with findings, creating 'validation debt' most teams cannot process.

The article argues AI pentesting creates 'validation debt': discovery scales far faster than teams' ability to verify AI-generated findings. In a survey of 158 practitioners, only 20.3% had workflows to triage more than 500 AI-generated candidates per engagement, while 29.7% called such volume unmanageable. One respondent spent two days validating 300 AI findings, of which 250 were duplicates, non-exploitable, or nonexistent. The author recommends capacity planning, ruthless deduplication, and risk-based prioritization before adopting AI pentesting tools.

Security Affairs · Aug 11, 2026Industry

Tuskira Vector brings autonomous red teaming to attack surface validation

Tuskira launched Vector, an autonomous red teaming agent that validates exploitable external attack surface against deployed controls using a Security Data Fabric digital twin.

Tuskira announced Vector, an agentic autonomous red teaming capability that simulates attacker behavior from outside an organization to identify its exploitable attack surface. Findings are validated against deployed compensating controls, internal risk data, and application/infrastructure topology via Tuskira's Security Data Fabric, which normalizes third-party tool signals into a live digital twin. The release extends Kairo (introduced May 2026), adding red team sensors and an agentic defense loop spanning agents Kairo, Lattice, Quell, and Iris. Tuskira claims Kairo has deprioritized up to 99% of scanner findings as unreachable and recomputes breach-path maps in minutes.

Help Net Security · 4h agoTools