Meaning-Layer Inventory
Reframed around the questions above the raw lists: who is unresolved, what sensitive context matters most, where activity can leave the company, and which shared lanes amplify impact.
Operator Brief
Inventory needs review
3 trust anchors unresolved, 2 exposure paths matter now, and 1 shared execution lane is widening scope.
Unresolved trust
3 entities
1 key, 1 endpoint, and 1 identity chain are changing attribution confidence.
Sensitive context
5 touchpoints
A small set of repos, files, credentials, and capabilities carry most of the company consequence.
External boundaries
2 paths
One plain HTTP edge and one unlabeled destination deserve review.
Shared blast radius
1 lane
A shared automation path is beginning to span more endpoints and sensitive paths.
Where inventory matters most
These lanes explain why an entity type matters before the user opens its focused meaning page.
One unknown API key is now a company-wide question, not just a row in inventory.
Why it matters
Shared credentials can span users, endpoints, and downstream systems. Security needs to know quickly whether this is approved activity or a real unknown.
Scope
1 unknown key, shared AI credential lane, active session against auth-related code.
Open the raw API key list, verify owner, then decide whether to suspend immediately.
Open API key storyThe environment cannot be secured confidently if active hosts are not bound to owners.
Why it matters
When endpoint inventory is incomplete, every live session on that host becomes harder to verify, contain, or dismiss.
Scope
1 unresolved endpoint, 1 live session, unclear team ownership.
Bind the unresolved host to a person, team, or environment.
Open endpoint storyFiles and repos matter most when they reveal which services, configs, or secrets could widen exposure.
Why it matters
Security should spot the small set of sensitive paths that carry most consequence without paging through every row.
Scope
auth-service, customer-web, auth.ts, .env, deploy configs, and related sessions.
Open repo inventory first, then confirm which files sit nearest highest-consequence codebases.
Open repo storySecondary calls and external tool paths show where AI activity can leave the company.
Why it matters
The dangerous moment is the connection between company context and a destination outside the expected trust boundary.
Scope
1 HTTP destination, 1 unlabeled host, one session window crossing from file access to network.
Classify the destination and verify whether the path is expected internal traffic.
Open boundary storySurfaced patterns
A familiar developer from an uninventoried endpoint.
A first-seen credential against company-critical code.
Session touched important code then called an unfamiliar host.
One automation identity across more endpoints and sensitive paths.
Active endpoint without person or team attached.
Session reaches .env and auth-related code.
Filesystem or outbound capabilities in unexpected sessions.
Shared key touches auth-service and customer-web.
Single live session ties key, host, files, and destination.
New MCP server, business function unknown.
Higher-cost traffic clustering around important code.
CI-like pattern from a developer endpoint, or vice versa.
Nothing individually unknown, but never together before.
Inventory relationship spotlight
Shared Execution Lane
One shared automation path touches auth code, deploy config, and an outbound destination through the same lane.
Shared trust anchor
1 automation identity
Company reach
3 sensitive paths + 2 envs
Boundary edge
1 unlabeled destination
Fastest drill
owners + credentials + dests
Entities determining attribution.
Assets carrying consequence.
Where context meets outbound reach.
Interpretation above raw entities.
Entity catalog by security meaning
Identity and ownership inventory determines whether security can attribute activity confidently.
Users
Known users distinguish approved work from unattributed sessions.
Signal: 1 identity chain still unresolved.
Open user storyEndpoints
Endpoints anchor host ownership, environment type, containment.
Signal: 1 host lacks owner binding.
Open endpoint storyAPI Keys
Credentials define real blast radius more than session rows.
Signal: 1 key unknown or not yet synced.
Open API key storyConsequence comes from sensitive content and the tools that can reach or transform it.
Files
Which files are sensitive, shared, or active right now.
Signal: 3 sensitive files account for most concern.
Open file storyRepos
Repos explain which service turns sensitive file into company impact.
Signal: auth-service and customer-web anchor most work.
Open repo storyCapabilities
What agent could do once reaching sensitive context.
Signal: Filesystem read and outbound paths highest-consequence.
Open capability storySessions
Join actors, credentials, files, destinations into evidence chain.
Signal: 1 live session driving top trust concern.
Open session storyBoundary-crossing inventory shows where many stories become real risk.
Secondary Calls
Where company context might flow after agent acts.
Signal: 1 plain HTTP destination needs classification.
Open boundary storyMCP Servers
Expand reach by exposing new tools and remote context.
Signal: 1 server path lacks business-purpose labeling.
Open MCP server storyModels
Matter when sensitive prompts or premium paths concentrate.
Signal: Premium usage stable, shared execution lane growing.
Open model storyShared infrastructure means one mistaken trust assumption spreads farther.
Agents
Automation lanes determine how behavior spreads.
Signal: 1 shared automation path spans more endpoints.
Open agent storySessions by Lane
Concurrency changes how fast security needs to move.
Signal: Most important concern still live, not historical.
Open session storyExecution Mix
Shared lanes reveal if one credential carrying too much.
Signal: Automation concentrating into one shared path.
Open agent storyInventory gaps blocking trust
The most important current host still lacks team and environment labeling.
Unblocks: Attribution, host isolation, and whether current AI usage is legitimate company activity.
An unknown key could be real drift or delayed sync, and the page should show that distinction clearly.
Unblocks: Faster revoke-or-verify decisions for the shared credential lane.
Some secondary calls still lack business-purpose classification.
Unblocks: Clearer separation between expected internal services and possible exfiltration paths.
Stable inventory coverage
Known-good identity coverage
34 / 36 sessionsMost activity still maps cleanly to known users, endpoints, and expected credentials.
Expected outbound traffic
7 / 8 pathsNearly all destinations remain encrypted and familiar to the organization.
Contained execution footprint
3 agent lanesThe software footprint is still narrow enough for security to reason about quickly.