Skip to main content
Use the Asset Map to find overlooked infrastructure, investigate individual services, and understand how an issue could affect the rest of your environment.

​
Find overlooked infrastructure

As your team grows, services can outlive the projects or people that created them. An internal tool may still be running long after anyone remembers deploying it. For example, connecting Railway can bring a forgotten deployment into your Asset Map. Your team can inspect the service, check whether it is publicly accessible, and decide whether it still needs to run.

​
Investigate a service

Select a service in the map and follow its relationships to understand where it runs, how it is exposed, and which resources and identities connect to it. Start with a question:
  • Is this service accessible from the public internet?
  • Which resources does it depend on?
  • Which identities have access to it?
Reviewing these relationships together helps you decide what to investigate or change.

​
Assess potential impact

When investigating a security issue, follow the affected asset’s relationships to see what else could be at risk. A service connected to a production database may warrant different attention from an isolated test deployment. The map helps you understand what an attacker could reach through an affected asset. During a run, agents use these relationships to investigate whether an attack path is exploitable.