What Atlas contains
- Entities — users, devices, accounts, policies, firewall rules, databases, load balancers, and any other object Panaptico reads or discovers
- Relationships — how entities connect: a user owns a device, a device sits on a network, a policy applies to a group
- Dependencies — what breaks if an entity moves or changes: a database behind an application, a certificate in front of a service
- Ghosts — unknown or unmanaged resources discovered through log analysis, network traffic, or probe responses
How Atlas stays current
Atlas updates in three ways:- Sensor reads populate known entities and their current attributes.
- Stream analysis correlates events and logs to infer relationships and discover unmanaged resources.
- Identity Links merge fragmented records into unified entities.
Example: Dependency impact
You plan to rotate a TLS certificate on a load balancer. Atlas shows the certificate is depended upon by three production services and two internal APIs. Before you rotate, Panaptico verifies that the new certificate is already deployed and trusted on all downstream paths. If any path is unobserved, the verification result is unknown, not assumed safe.When to use Atlas
Use Atlas when you need to understand what is really in your estate, how it connects, and what the blast radius of a change will be. Atlas feeds Initiatives, Routing decisions, and Work Items with ground-truth context.Identity Links
Resolve fragmented records into unified entities inside Atlas.
System Sensor
The always-on readers that keep Atlas current.
Cloud Migration
See how Atlas supports migration planning and dependency verification.