Finance firms found attack paths after expanding NodeZero testing
Original title: Audit-Ready Isn’t Attack-Ready.
Horizon3 case studies say a Dev environment reached production Domain Admin and one credential exposed about 300,000 files.
Horizon3 describes three unnamed financial and insurance customers using NodeZero for repeated exposure testing. A large US insurer found its development environment was not isolated: an unpatched ActiveMQ service and a privileged service account provided a path into production. A global payments provider and a third firm reported weak credentials, broad file access, and AWS attack paths that annual or limited pentests had missed. The vendor says customers then changed passwords, privileged access, and remediation workflows.
Unconfirmed: Outcomes, file counts, and a reported $500,000 insurance saving are vendor or customer claims; the organizations are unnamed.
- The insurer's Dev test found 266 cracked passwords, including 146 sharing one password.
- NodeZero used unpatched ActiveMQ and a service account to reach production Domain Admin.
- One weak credential reportedly reached nearly 300,000 files in about two hours.
- Weekly testing found 39 attack paths from one AWS read-only credential.
- That firm said full AWS account compromise took under 10 minutes.
- Vendors
- Horizon3.ai
- Products
- NodeZero
- Countries
- United States
From the original article
5 min read at horizon3.ai
Passing an audit doesn't guarantee attack readiness. Explore how three financial and insurance organizations use NodeZero to challenge security assumptions, expand penetration testing coverage, uncover exploitable attack paths, and verify remediation through continuous exposure management.
By Stephen Gates · horizon3.ai
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.