ZeroHour

Search: “IBM”

3 stories in the last 24h

12 Best DSPM Tools Compared (2026): Features & Pricing

A 2026 buyer's guide compares 12 DSPM vendors' features and pricing, warning per-TB data-volume billing inflates long-term cloud security costs.

The article compares 12 data security posture management (DSPM) tools, including Palo Alto Networks (Dig), BigID, Wiz, Symmetry Systems, Varonis, CrowdStrike (Flow Security), Cyera, and Tenable (Eureka), focusing on billing models such as per-TB scanning, per-data-store, per-identity, and pay-as-you-go. It highlights vendor consolidation through acquisitions and advises negotiating scan-volume caps and clarifying whether shadow copies and dev clones count as billable data.

GBHackers · 2h agoIndustry 3 sources

The true cost of a ransomware attack, with and without BCDR

Ransomware's true cost averages $5.08 million per incident versus a $139,875 median ransom, and mature BCDR strategies with immutable backups cut downtime and recovery expenses.

IBM's Cost of a Data Breach Report 2025 puts the average ransomware incident at $5.08 million, far above the $139,875 median ransom payment cited in Verizon's 2026 DBIR. Datto's State of BCDR Report 2025 found 60% of organizations believed they could recover within a day, but only 35% actually did. The Datto-sponsored piece argues mature BCDR with immutable WORM backups shortens downtime, citing a Techify case that restored 19 TB and returned a client to operations in under two hours without paying a ransom. It also flags compliance deadlines such as GDPR's 72-hour breach notification and the SEC's four-business-day disclosure rule.

BleepingComputer · 22h agoIndustry

CISA and NIST Issue Guidance to Protect Cloud Identity Tokens

CISA and NIST published Interagency Report 8587 with voluntary guidance to harden cloud identity tokens against theft, forgery, and lateral movement.

CISA and NIST released NIST Interagency Report 8587 on September 15 with final voluntary guidance for federal agencies, cloud providers, and their customers on protecting SSO, federation, and API tokens. Requirements include one-hour maximum token lifetimes, 90-day signing key rotation for high-impact systems, hardware-backed key storage, explicit audience fields, and keeping tokens out of logs. The guidance was motivated by the 2020 ADFS compromise where forged SAML assertions bypassed MFA, and an incident where a leaked consumer signing key enabled token forgery and theft of 60,000+ emails from one agency. Nearly 250 public comments shaped the text, with input from Google, Microsoft, Okta, AWS, Oracle, IBM, HashiCorp, Wiz, and the OpenID Foundation via the Joint Cyber Defense Collaborative.

Infosecurity Magazine · 22h agoAdvisory