You're deploying it wrong! TeamCity, Subversion & Web Deploy part 2: MSBuild and deployable packages
35 Actionable Password Statistics for Businesses in 2026 | Huntress
Huntress compiles 2026 password statistics showing 94% of 19 billion leaked passwords were reused and 37% of identity threats used stolen credentials.
Huntress published a compilation of password security statistics drawing on sources including Cybernews, Verizon's 2026 DBIR, IBM, and Bitwarden. Cybernews found 19 billion exposed passwords from roughly 200 incidents between April 2024 and April 2025, with only 6% unique and 94% reused across accounts. Huntress telemetry reports 37% of identity-based threats in 2026 involved stolen or suspicious credentials, while Verizon cites credential abuse in 39% of breaches. The piece argues weak and reused passwords remain a top entry point and recommends improved password hygiene.
The hidden work of modernizing Malwarebytes
Malwarebytes details its migration of Windows product managed components to .NET 10, citing security, supportability, diagnostics, and performance benefits.
Malwarebytes says it migrated the managed portions of Malwarebytes for Windows to .NET 10 while leaving native drivers and the detection engine untouched. The vendor cites a supported runtime, safer defaults, stronger cryptography, better diagnostics, and JIT/GC performance improvements as benefits. The migration also deprecated Windows 7 support, and the company applies staged rollouts and automated validation because its code runs with elevated privileges on millions of endpoints. No vulnerabilities or incidents are described.
How Developers Prevent Production Risk at the Source
Wiz argues shift-left code-stage security cuts remediation costs and ships Wiz Code, WizOS, and WizCLI to catch flaws pre-deployment.
A Wiz blog post argues that fixing vulnerabilities at the code stage costs a fraction of production remediation, citing the node:20-slim base image which ships 14 known CVEs, three of them critical. It claims AI agents can now analyze open-source commits and generate working exploits in minutes, shrinking the window between a public fix and automated attacks. The post promotes WizOS near-zero-CVE base images, WizCLI and MCP-server checks inside developer and AI agent sessions, and Wiz Code scanning across pull requests, repositories, and pipelines covering SAST, SCA, secrets, and IaC misconfigurations.
AI the Top Priority for New Spend as Cyber Budgets Flatline
IANS survey of 500 US CISOs finds AI is the top priority for net-new security budget even as overall cybersecurity budgets stay flat.
IANS's 2026 Security Budget Benchmark Report, based on interviews with 500 US security executives, found AI was the most popular focus for incremental budget, cited by 69% of respondents. Software now accounts for 35% of the security budget in 2026, up from 29% last year, nearly matching staff and compensation. Overall median budget growth remained flat, with 55% keeping budgets flat or making cuts, while 71% of VC-backed companies increased security budgets versus 52% of public companies. Most CISOs (69%) do not expect AI to cut headcount, and 81% anticipate it creating demand for new roles and skills.
Security Affairs newsletter Round 594 by Pierluigi Paganini – INTERNATIONAL EDITION
Weekly Security Affairs newsletter aggregates top stories including Cisco FMC exploitation, Qilin ransomware, Chrome zero-days, and Berlin leak.
Pierluigi Paganini's Security Affairs newsletter Round 594 (International Edition) rounds up the week's security headlines. Topics include attackers exploiting a critical Cisco FMC flaw to deploy Qilin ransomware, SonicWall mass exploitation linked to a UK council attack, multiple CISA KEV additions, Chrome zero-days used by four nation-state actors, a $320 million Liquid Network theft, and a Berlin ransomware data leak. It also covers AI security items such as agent sandbox failures and distillation campaigns by Chinese AI firms.
What your vendor says about PQC tells you if they are ready
Allot CTO outlines a telecom post-quantum migration playbook: inventory crypto, deploy hybrid ML-KEM on TLS first, and avoid missed interfaces.
Dr. Yaakov Stein, VP CTO of Allot, explains how mobile operators should triage post-quantum migration by data shelf life, protecting subscriber identity mappings, billing records, and call metadata that stay sensitive for years. He recommends starting with a comprehensive crypto inventory, then hybrid ML-KEM key exchange on TLS-protected 5G SBA and management interfaces, followed by IPsec backhaul and roaming links. Stein warns that migrations most often fail operationally through missed legacy interfaces such as SSH, RADIUS, or forgotten load balancers, and cites the early Kyber multi-packet TLS client hello issue as an example of middlebox incompatibility.