Skip to content
Cloud Security Breaches

Exposed network services and request paths: 8 incidents in the ledger

An exposed network service is a reachable service or request path, such as an open management port, an unpatched internet-facing application or a request forged to reach a metadata endpoint, that gave a caller a way into a workload and into the credentials or data attached to it.

Open the ledger ยท All eight paths

How it works

Every cloud virtual machine can reach a local metadata service that hands out temporary credentials. AWS documentation says the service has two versions, that by default an instance can use either, and that an instance can be set to accept only the session-based version. A request path in an application that fetches a URL on a caller's behalf can be steered at that local address, and the credentials in the reply belong to the instance's role.

Open ports follow the same logic. Network rules at each provider allow or deny traffic by source, port and protocol, and Microsoft's documentation describes a default deny rule for inbound traffic that explicit rules override. A rule that opens a management port to the whole internet makes the service behind it the first step of an incident. Sources in the ledger name the service or request path when the company or provider does.

The incidents

DisclosedOrganizationCloudHow access was gained
2026-01-08People Central Pte. Ltd.AWSThe decision says the company, a cloud-based HR software provider, had Remote Desktop Protocol access open to the internet without two-factor authentication on its AWS cloud servers, settings allowed inbound traffic from all IP addresses in the cloud environment, and SQL injection vulnerabilities were present with no web application firewall.
2025-03-20People Central Pte. Ltd. (Singapore, cloud-based HR software provider)Amazon Web ServicesThe decision lists contributing lapses: SQL injection vulnerabilities in the web application with no web application firewall, RDP access open to the internet without two-factor authentication, settings that allowed inbound traffic from all IP addresses in the cloud environment, and vulnerability scanning only every two years.
2024-12-08BeyondTrustAmazon Web ServicesThe company stated a zero-day vulnerability of a third-party application was used to gain access to an online asset in a BeyondTrust AWS account, which allowed the threat actor to obtain an infrastructure API key that was then used against a separate AWS account that operated Remote Support infrastructure.
2024-08-30Verkada Inc.Verkada (cloud-based security camera provider)The FTC press release says the complaint alleges the company failed to provide appropriate security measures, including failing to require unique and complex passwords, adequately encrypt customer data and implement secure network controls. The Justice Department release says the complaint alleges failures in appropriate access management and data protection controls. Neither source states how the hacker obtained the access.
2024-04-22Payroll2U Pte. Ltd.AWSThe decision says a single compromised user account was used for Remote Desktop Protocol access to five servers in the company's AWS environment, and that investigators could not determine how the credentials were obtained. It lists no MFA for administrator accounts or accounts with access to personal data.
2022-07-14Crawfort Pte. Ltd.AWSThe decision says the company opened an S3 server port in its AWS environment for one week during a data migration, and that the S3 bucket holding the data was publicly accessible due to a misconfiguration. It states the threat actor gained access to the public bucket in that period.
2019-08-27ImpervaAWSThe company's follow-up post says an unauthorized use of an administrative API key in one of its production AWS accounts led to exposure of a database snapshot. It lists the steps as a snapshot created for testing, an internal compute instance accessible from the outside world that contained an AWS API key, compromise of that instance and theft of the key, and use of the key to access the snapshot.
2019-07-29Capital OneAWSThe company stated that a highly sophisticated individual was able to exploit a specific configuration vulnerability in its infrastructure and that the issue was not specific to the cloud. The OCC consent order finds the bank failed to establish appropriate risk management for its cloud operating environment, including network security controls.

The kind of control that addresses it

require session-based metadata access on every instance, close management ports to the internet, and limit the role attached to each workload

Sources

  1. Amazon EC2 User Guide: the Instance Metadata Service, read 16 Nov 2026
  2. Microsoft Learn: network security groups overview, read 16 Nov 2026
  3. Google Cloud: VPC firewall rules, read 16 Nov 2026

Last reviewed 16 Nov 2026.