Named security endpoints
Give security infrastructure clear public identity and rDNS naming.
Security Gateway
Public network identity for security gateways and trusted access points.
Security gateways, firewalls, SASE edges, monitoring systems, access controls, and trusted admin endpoints often need stable recognition across customers, suppliers, and internal teams. LARUS One gives those systems named Identity Addresses and continuity evidence.
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 policy with recognizable 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 gatewaySASE edgeSecurity monitoring endpointAccess control gatewaySOC connectorAdmin workstationResidence security gateway
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network.
Policy alignment
Use Identity Passport and Allowlist Pack with customer security reviews.
Continuity
Keep the security identity stable across provider and architecture changes.
FAQ
Customer-facing answers for this use case.
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
Continue through the identity workflows connected to this page.
Office egress identity
Public network identity for office egress and trusted business workflows.
Give office networks stable public identity for employees, finance systems, supplier access, security reviews, applications, and trusted workflows.
View related use caseAPI application identity
Public network identity for APIs, applications, and callbacks.
Use LARUS One Identity Addresses for API allowlists, webhooks, application callbacks, AI tool access, production services, and customer integrations.
View related use casePrivate residence network identity
Public network identity for private residences and secure home infrastructure.
Bring stable public network identity to private residences, secure homes, executive networks, family office systems, and managed IT workflows.
View related use caseCustomer allowlist identity
Public network identity for customer allowlists and security reviews.
Give customers stable Identity Addresses for allowlists, security review, API access, supplier systems, and trusted enterprise connectivity.
View related use caseDeploy
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.