Internet exposure
Identify services reachable from the internet and show the rules and routes that make the path possible.
← Exposure ManagementAvailableNSPM · Built on Skyreach Orion
Model effective reachability across clouds, clusters and sites.
NSPM brings networks, subnets, routes, firewalls, load balancers, peerings and private connectivity into one topology. Orion distinguishes adjacency, policy and effective routing so a diagram does not imply a path that the evidence cannot support.
Evidence in
What Orion connects
The exact coverage depends on the integrations and authorised evidence available in your environment. Every record retains where it came from.
Example sources
- Azure VNets, NSGs, routes and firewalls
- AWS VPCs, security groups, ACLs and transit
- Google Cloud VPCs, firewall policies and routes
- Kubernetes services, ingress and NetworkPolicy
- VPN, peering and hybrid connectivity
- Supported firewall, DNS and network platforms
What the ontology models
- Networks, subnets and address spaces
- Interfaces, endpoints and public IPs
- Firewall rules and security policies
- Routes, peerings, gateways and tunnels
- Load balancers and backend relationships
- Observed and derived reachability evidence
Intelligence out
What visibility and insight you gain
The module uses the shared Orion model, so its findings can be understood through evidence collected by other security disciplines.
Segmentation
Reveal unexpected development-to-production, cross-cloud and east-west connectivity.
Rule analysis
Surface broad, redundant, shadowed or ineffective rules with the assets they affect.
Attack-path context
Combine reachable services with vulnerabilities, identities and target importance.
Connected analysis
An example of the exposure Orion can reveal
This is an illustrative relationship chain, not a claim that every path represents a confirmed compromise. Orion preserves evidence and confidence so teams can validate what is effective.
Internet→Ingress policy→Reachable workload→Internal target
Risks made visible
What the module is looking for
- Management ports and sensitive services exposed publicly
- Unexpected routes across peering, transit or VPN connections
- Broad firewall rules that bypass intended segmentation
- Unrestricted egress from important workloads
- Missing flow logging or protective network controls
- Multi-hop lateral movement to critical assets
Questions it helps answer
Move from findings to decisions
- Can the internet reach this database through any path?
- Can development reach production across shared transit?
- Which firewall rule creates this exposure?
- What becomes unreachable if we change this policy?
Why Orion matters
This discipline does not operate in isolation
Network Security Posture Management contributes its evidence to the same ontology used by the rest of Exposure Management. That allows a finding to inherit network reachability, identity privilege, data sensitivity, software, application and business context where those facts exist.
See the complete Exposure Management productNSPM evidence+Shared ontology+Cross-domain context=Prioritised exposure
See what this means in your environment
Tell us which sources you use and the questions your teams struggle to answer today.