Unknown credential remains active inside a live coding session.
An unowned key is still in use, and it is already adjacent to auth-service work.
Evidence: sk-ant-...C001 · active session · auth-service touch
Open API key storySecurity Global Overview
One live trust break needs containment, two concentration hotspots widen company consequence, and two blind spots are slowing confident response.
Operator Brief
Needs review
2 urgent concerns · 3 hotspots · 3 unknown entities · 2 exposure paths
Hotspots
3 hotspots
Credential reuse, sensitive auth code touch, and a plain HTTP edge are carrying most of the consequence.
Unknown Entities
3 entities
One key, one endpoint, and one owner chain are not confidently identified yet.
Touchpoints
5 surfaces
A small set of repos, files, and execution surfaces explain why the story matters.
Exposure Paths
2 paths
Two paths show how concern may leave, spread, or cross a boundary.
Fastest Next Click
Resolve the unknown credential first. It’s the fastest containment decision and the cleanest pivot into the rest of the story.
Critical Concerns
An unowned key is still in use, and it is already adjacent to auth-service work.
Evidence: sk-ant-...C001 · active session · auth-service touch
Open API key storyA session touched auth-related code and then crossed into an unencrypted destination.
Evidence: /src/auth.ts · 10.0.2.15:8080 · http · same window
Open exposure pathsHotspots
Open in inventoryOne unknown key appears across multiple high-consequence surfaces.
Resolve the key and ownership chain first to collapse the blast radius.
Open hotspotsA small set of auth-related files and repos carry most of the consequence.
See the exact touchpoints before deciding whether to contain.
Open touchpointsA session crossed into a plain HTTP destination after sensitive work.
Classify the destination intent and decide whether this is expected traffic.
Open exposure pathsWhat Changed
A previously unseen API key appeared in a live coding session.
The key surfaced minutes ago and is not yet tied to an approved owner record.
A session crossed from auth-related file access into a plain HTTP destination.
Volume stayed low, but consequence rose because the boundary changed after sensitive touch.
A shared automation identity now spans more sensitive surfaces than before.
It may be legitimate growth, but concentration widened enough to deserve review.