Cloud Security
Cloud Infra Systems Maker Oxide Hits $6B Value After $445M Eclipse-Led Series D
Oxide Computer secures $445M in Series D funding from Eclipse, bringing total capital raised to approximately $835M for its cloud infrastructure systems.
Cloud Security coverage from Firewall Pulse holds 12 articles, 11 of them reference guides. The newest was published on October 10, 2026. New stories are added as soon as they are confirmed, from more than 50 sources checked as often as every 45 seconds. Each story lists its sources. Primary sources we follow for this section include Kubernetes: Security Concepts and NIST Cybersecurity Framework.
Oxide Computer secures $445M in Series D funding from Eclipse, bringing total capital raised to approximately $835M for its cloud infrastructure systems.
Attackers target the build pipeline because it holds the keys to the kingdom, allowing them to plant malware before your security tools ever see the code.
Compliance fails when teams treat it as a periodic audit rather than a continuous state enforced by automated policy checks at the infrastructure level.
Cloud backup relies on immutable storage objects and client-side encryption to prevent ransomware, but network latency and API rate limits dictate your actual recovery speed.
Workload identity replaces long-lived secrets with short-lived tokens, shifting the security boundary from credential storage to identity verification at runtime.
Excess permissions often hide in long-standing service accounts, creating a silent path for attackers to move laterally without triggering immediate alerts.
Most container supply chain compromises occur long before deployment, exploiting trust in automated build pipelines and unsigned image layers.
Identity is the new perimeter, and poorly written access policies allow attackers to move laterally without triggering any network alerts or alarms.
Stolen tokens bypass multi-factor authentication because the system treats them as a verified session, not a new login attempt.
An unauthenticated dashboard exposes the API server directly, granting an attacker immediate control over every workload and secret within the cluster without needing to exploit application code.
Without enforced tenant isolation, a single misconfiguration can allow one customer to read or alter the data of another, bypassing application logic entirely.
API insecurity often hides in successful responses rather than errors, making traffic volume and payload structure more reliable indicators than failure codes.