Use Asset Map to understand your environment as it exists today. It gives your team a current view of services, identities, deployments, and the relationships between them.
Asset Map can reveal infrastructure that your team no longer tracks. For example, a team with many Railway projects may discover an internal tool deployed by someone who has since left the company.Connecting Railway adds that deployment to the map. Your team can see that it is live on the public internet, has unprotected API routes, and can access a database.
Start with a service and inspect what connects to it. Asset Map helps you understand its public exposure, dependencies, identity relationships, and configuration alongside the rest of your environment.This gives your team the context to understand why a service matters before deciding what to investigate or change.
Use Asset Map to understand what a compromised asset could affect. Follow its connections to see the services, identities, and data paths that may be within its reach.This helps your team assess the impact of an issue without treating each asset as an isolated system.
