Everything you own, external, internal, cloud and code, in one living context. Each exposure classified, evidenced and routed to its owner.
Assets12,480
Search assets…
Exposed · 37No hostname · 57New this week · 214
- grafana.ops.internalInternal by name, open to 0.0.0.0/0
- s3://acme-support-uploadsBucket policy allows public read
- 10.20.4.17No hostname · discovered this week
- checkout.acme.comInternet-facing · 4 services
Inventory
- Assets
- 12,480
- Domains & IPs
- 2,640
- Internal hosts
- 4,380
- Cloud resources
- 5,300
- Buckets
- 118
Assets
s3://acme-support-uploads · public10.20.4.17 · no hostnamecheckout.acme.comacme/checkout
grafana.ops.internalExposed
Ops dashboards for the payments stack, admin panel open to the internet without SSO.
AssetsChanges
Aug 27 → Sep 3
Newly exposed9
legacy-api.acme.comAPIRetired in the docs, still answers 200Tue 02:14
34.201.8.19:5432CloudSecurity group opened 5432 to 0.0.0.0/0Wed 11:40
s3://acme-support-uploadsBucketBucket policy allows anonymous readWed 16:02
grafana.ops.internalHostInternal by name, now reachable on :443Thu 08:51
New214
preview-482.acme.devHostPreview env for acme/web #482Mon 19:20
api.acme.com/v3/exportAPINew route, absent from the OpenAPI specTue 10:05
acme/billing-workerRepositoryNew repository in the connected GitHub orgWed 09:12
Changed37
checkout.acme.comHostTLS renewed, 2 routes addedThu 03:30
vpn.acme.comHostOpenVPN 2.5.8 → 2.6.12Thu 06:10
Retired31
old-cdn.acme.comHostDNS record removed, no longer resolvesMon 08:00
i-0b3f9a12 (staging)CloudInstance terminatedTue 22:45
Every route is probed for what it takes to get in: nothing, a session, or SSO. Public and privileged surfaces are ranked apart, and undocumented routes are probed the same way.
Responses are sampled for personal data, credentials and internal identifiers, so an open endpoint serving customer records outranks one serving a logo.
Each exposure is placed on the paths it sits on, from the edge through code to the data it reaches, so a hop into customer records outranks a stray dev box.
IssuesISSUE-2052
Subscribed···
SeverityHigh
StatusValidated
Targetlegacy-api.acme.com/v1/customers
http_exchange1GET /v1/customers?page=1 HTTP/22host: legacy-api.acme.com3// no cookie, token or SSO header45HTTP/2 200 OK6{ "customers": [{ "email": "j.doe@…", "phone": "+1 415…" },7 … 48,112 more ] }
ActivityEvidenceOwnership
Routed toMLMarco Lee@acme/platformAcceptedWhy
- CODEOWNERS in acme/api/services/legacy-api → @acme/platform
- acme-prod i-0b3f9a12tag team=platform
- ISSUE-1998 on the same hostfixed by Marco Lee, 3 weeks ago
Delivered
- PLT-418 Put legacy-api behind SSO or retire it
- #platform-sec
- Evidence pack
Trusted by security teams
We use tools on this site to collect and record your data (e.g., your searches), which we and our vendors may use to provide, improve, and personalize our offerings, make recommendations, and for analytics and marketing. Some of these tools identify visitors and link website activity to business contact and company information so we can better understand interest in our services and tailor our outreach. We may share your data with third parties, such as advertising vendors, social media companies, and research partners, which may be "targeted advertising," "selling," or "sharing" under applicable privacy laws. Continuing to browse our site means you accept these terms and our Privacy Policy. To opt out, click the Your Privacy Choices link in the footer.