Named security endpoints
Give security infrastructure clear public identity and rDNS naming.
Security Gateway
Security Gateway
Public network identity for security gateways and controlled access points.
Security gateways, firewalls, SASE edges, monitoring systems, access controls, and administrative endpoints may need public-address evidence for customer, supplier, and internal reviews. LARUS One can provide named Identity Addresses and documentation; each reviewer decides whether to accept it, and acceptance is not guaranteed.
Identity capacity
One Identity Unit. Up to 254 globally unique Identity Addresses
Each LARUS One Identity Unit can activate up to 254 globally unique Identity Addresses at one deployed location, for the devices, endpoints, computers, servers, gateways, applications, APIs, and trusted access points that need stable public network identity.
The Identity Location is the selected home, office, family office, hotel, enterprise site, API edge, or private network where the Identity Unit is deployed through the LARUS One delivery network.
Actual usable count may depend on delivery design, security policy, and local network configuration.
Value
Support security review with documented network identity
Use Identity Addresses for firewalls, SASE gateways, Zero Trust access points, monitoring gateways, SOC systems, residence security systems, and administrative endpoints.
Identity Address examples
Assign public network identity to the systems that need recognition
- Firewall gateway
- SASE edge
- Security monitoring endpoint
- Access control gateway
- SOC connector
- Admin workstation
- Residence security gateway
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network
Policy alignment
Submit Identity Passport and Allowlist Pack evidence for independent customer security review; approval is not guaranteed.
Delivery changes
A provider, location, or architecture change requires a fresh technical and delivery assessment. Keeping the same address is not guaranteed.
FAQ
Answers to common questions
Does public identity change security policy?
Public identity works with the customer security architecture. Firewalls, SASE, routing, segmentation, and access policies continue to control what is reachable.
Can security devices have distinct Identity Addresses?
Yes. Identity Addresses can be assigned to gateways, access points, monitoring systems, and security workflows.
Related use cases
Explore related ways to use network identity
Deploy
Deploy one Identity Unit to one selected location
Deploy one Identity Unit to one selected location and activate up to 254 globally unique Identity Addresses for the systems that need stable public network identity.
LARUS maintains the Identity Unit, Identity Addresses, Identity Passport, Allowlist Pack, and continuity record. The selected provider delivers the local network service.