Back to News
Market Impact: 0.5

Cloud CISO Perspectives : New Threat Horizons report highlights current cloud threats

AAPLDELL
Cybersecurity & Data PrivacyArtificial IntelligenceTechnology & InnovationGeopolitics & WarRegulation & LegislationCrypto & Digital AssetsTrade Policy & Supply ChainInfrastructure & Defense
Cloud CISO Perspectives : New Threat Horizons report highlights current cloud threats

Third-party software exploits became the primary initial access vector in H2 2025, accounting for 44.5% of incidents versus 27.2% for weak credentials (software exploitation was under 3% at the start of 2025). GTIG tracked 90 zero-days in 2025 (48% targeting enterprise tech), and examples include React2Shell exploitation deploying crypto miners within ~48 hours and supply-chain/CI-CD compromises achieving full cloud admin rights in under 72 hours. Google recommends accelerated automation (WAFs, identity-based controls) and tamper-resistant logging to blunt faster, AI-assisted attacks and anti-forensic tactics.

Analysis

The market is entering a sustained reallocation of security spend from perimeter credentials to cloud-native runtime and supply-chain controls; expect enterprise budgets to shift meaningfully within the next 6–18 months toward immutable logging, edge WAFs, and CI/CD attestation tooling. That shift favors vendors that can sell integrated telemetry + enforcement rather than point EDR products—buyers will prize solutions that convert high-volume noisy telemetry into tamper-resistant, legally admissible records. A second-order supply-chain dynamic: appliance and backup vendors face outsized reputational and contracting risk because customers will demand verifiable recovery guarantees and cryptographic proof of immutability for backups. Conversely, companies that provide zero-trust build blocks (OIDC trust management, fine‑grained pipeline credentials, SBOM verification) will see recurring revenue expansion and higher gross retention as customers bake those controls into procurement contracts. Key catalysts run on three timelines: exploit velocity and headline incidents can compress market reactions to days, procurement cycles and proof-of-concept deployments play out over quarters, and regulatory or insurance requirements for tamper-resistant logging will drive multi-year structural revenue growth for compliant vendors. The primary reversal risk is rapid adoption of curated, signed package registries and mandatory artifact attestation in major clouds—if that becomes the de facto standard, marginal demand for some stopgap runtime controls could decelerate. My base-case: winners are platform-native security and observability firms with API-first enforcement and immutable storage; losers are legacy hardware/backups and small niche tools lacking enterprise audit-grade logging. Market pricing today likely underestimates downstream recurring revenue from compliance-driven logging, but overestimates the ease of converting SMB cloud customers to higher-priced run-time protection in the next 12 months.