
A well-defended core, serious exposures in the estate around it
Authorized external red team, OSINT-led, delivered as a leadership-level findings report. Anonymized.
Who we worked with.
A philanthropic organization's internet-facing estate: a public website behind a cloud edge service, a staging environment, a federated single-sign-on identity layer, and perimeter network appliances.
Anonymized. No client names, people, domains, addresses or locations are published.
The question we were asked.
The public website was reasonably well defended. The real question was what sat around it: the staging environment, the identity layer, and the network perimeter, where an external attacker with no credentials has room to operate.
Assessment modules used.
Authorized external red team, OSINT-led, delivered as a leadership-level findings report.
External red team
OSINT-led, external, unauthenticated, black-box testing of the internet-facing estate.
Web & cloud edge
The public website and its cloud edge protection.
Staging exposure
A public staging server.
Identity layer
The federated single-sign-on identity layer.
Network perimeter
Perimeter network appliances.
Severity, validated.
- HighThe website's administrator control panel was reachable from the open internet through an inconsistency in the edge protection, on an end-of-life platform with no login lockout or rate-limiting.
- HighA public staging server exposed an unauthenticated search database holding a full copy of the site index (tens of thousands of records), readable and write-capable with no credential.
- HighThe federated identity layer retained a legacy authentication endpoint outside account-lockout and throttling.
- HighTwo perimeter appliances answered DNS for the whole internet and amplified responses to roughly 22 times the request size.
What changed.
Midway through the assessment the organization tightened the control on the administrator path. The engagement then identified a second route that reached the same administrator login despite the new rule, and reported it. Remaining fixes were supplied in order.
Organization tightened the control on the administrator path.
A second route to the administrator login was found despite the fix, and reported.
Fix order for the staging host, legacy identity endpoint, and open resolvers.

What the client received.
- Leadership-level findings report
- Each finding: what was observed, why it matters, live proof
- Second-route finding reported after the mid-assessment fix
- Prioritized fix order: staging host, legacy identity endpoint, open resolvers
- Authorization-gated step documented, not run
Prepared by TitanDef offensive security team

Find out what an adversary already sees.
Focused engagements run 5 to 7 business days, with a 72-hour first-findings commitment. Powered by frontier AI models; every finding validated by a senior human.
