
North.cloud Closes $60M Series B to Expand Cloud Spend Oversight
The cloud cost management platform raised $60 million in Series B funding, led by PeakSpan Capital, bringing its total capital to $67 million.
Cloud Security coverage from NetSec Observer holds 18 articles, 17 of them reference guides. The newest was published on October 16, 2026. New stories are added as soon as they are confirmed, from more than 150 sources checked as often as every 45 seconds. Each story lists its sources. Primary sources we follow for this section include Cloud Security Alliance and CIS Benchmarks.

The cloud cost management platform raised $60 million in Series B funding, led by PeakSpan Capital, bringing its total capital to $67 million.

Scanning infrastructure-as-code reveals misconfigurations that allow attackers to bypass network controls and access sensitive data before deployment.

Abandoned cloud assets create invisible attack surfaces that drain budgets and expose data long after the original project ends.

Version control history retains deleted secrets forever, and environment variables often fail to protect credentials from memory dumps or process listings.

Network firewalls fail to stop insider threats or stolen credentials, making identity the only reliable boundary for modern cloud environments.

Multi-region failover moves traffic across physical borders to survive total data center outages, not just server crashes.

Moving security checks earlier in the development cycle catches logic errors that automated scanning tools miss entirely.

Single sign on in Active Directory relies on encrypted tickets rather than repeated password checks, which shifts the security burden from user memory to server-side key protection.

Cloud ransomware rarely encrypts your data directly; it hijacks your permissions to lock you out of the systems you built.

Access reviews often create false security theater by forcing users to re-approve permissions they do not understand, while missing the actual risk of privilege escalation.

Your cloud provider can encrypt your data, but if they hold the keys, they can also read it without your permission.

Single sign-on shifts risk from password guessing to token theft, making session management the primary defense against account takeover.

Misconfigured access policies and unrotated keys expose your data even when encryption algorithms remain unbroken.

Containers are not virtual machines, and running a container as root does not automatically grant you host control without specific privilege escalation paths.

Automated scanners often miss secrets hidden in build artifacts, making manual review of commit history the only reliable defense against accidental data exposure.

Hardcoded credentials in public repositories remain active until you rotate them, creating a persistent backdoor that bypasses perimeter defenses.

Most cloud breaches start with service accounts that hold permanent, broad permissions instead of temporary, narrow ones tied to specific tasks.

Attackers do not steal your data in denial-of-wallet attacks; they exhaust your budget by forcing your infrastructure to perform expensive operations.