ShutterGap Exposes Millions of AWS Cloud Resources Between Security Scans
A critical blind spot in cloud security tooling, dubbed “ShutterGap,” in which millions of AWS resources are briefly and publicly exposed, only to disappear before traditional monitoring tools can detect them.

Continue reading

Shipping and Maritime: A Cyber Incident Is Now a Hazardous Condition
As of July 2025, the US Coast Guard treats a cyber incident as a hazardous condition, in the same regime as a fire or a grounding. In shipping, that is not a compliance footnote. It recognizes what an attack actually takes away: not records, but the ability to operate.

Healthcare: The Most Expensive Sector to Get Wrong
Healthcare faces the highest data breach costs of any industry, averaging $6.64 million per incident in 2026. As cloud adoption accelerates, misconfigurations threaten patient data, HIPAA compliance, and critical clinical operations. Discover why detection alone isn't enough and how preventive cloud security stops risky configurations before deployment-without disrupting patient care.

Exploiting Cloud Misconfigurations, Part 2: How Attackers Discover Cloud Resources
The first thing an attacker needs is a target, so an attack naturally begins with resource discovery. During discovery, the attacker builds and expands a database of resource identifiers. These resources are then checked periodically for exploitable conditions. A resource may be discovered long before an opportunity to exploit it arises.

Ten Years Is a Long Time to Be Wrong
For nearly a decade, a cloud misconfiguration at Toyota left sensitive vehicle data belonging to approximately 2.15 million customers accessible from the internet. What began as a single configuration mistake in 2013 went undetected until 2023, exposing a fundamental weakness in traditional cloud security: detecting misconfigurations only works when someone is looking. And when Toyota finally investigated, it uncovered additional exposures. The incident raises a critical question for every organization operating in the cloud: Why wait to discover a security risk when you could prevent it from existing in the first place?
.avif)
The Key That Should Not Have Worked
A leaked cloud credential is usually treated as a detection problem. Find it, revoke it, rotate it, and move on. But the Volkswagen and Cariad data exposure raises a more important question: why was there a long-lived credential worth stealing in the first place? When a single reusable key can unlock sensitive cloud data, the leak is only part of the problem - the configuration that allowed that key to exist is the other.
.avif)
The Role That Should Never Have Existed
On 29 July 2019, Capital One disclosed that an attacker had taken data relating to roughly 106 million people across the United States and Canada. The attacker was Paige Thompson, a former Amazon Web Services engineer, who was arrested the same day and convicted on computer fraud charges in June 2022. The company's settlements reached around $190 million.