Skip to main content
Public network identity for security gateways and access points.

Security Gateway

Public network identity for security gateways and 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.

USD 6,998 per Identity Unit-yearChoose your local delivery partner after purchase.

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

The LARUS advantage

One identity, with LARUS behind you

01

Scale by active Location, not by address count

People, devices, rooms, network segments, and workflows do not change the subscription count. Count the Locations used at the same time.

02

LARUS and your provider, working together

LARUS anchors identity. The selected provider delivers the local network.

03

Put your network identity in your partners' hands

Share your Identity Passport and Allowlist Pack with business partners to introduce your network identity and support access requests.

04

Built to work with your security setup

Bring your LARUS network identity into the firewalls, SASE and access policies your team already manages.

From use case to paid pilot

Your first paid pilot

  1. 01

    Start one paid pilot

    Create an account and sign in to purchase one annual Identity Unit online.

  2. 02

    Add the first Location

    After purchase, add the office, property or other place where you will use the identity. Location profiles are free; one Unit serves one active Location at a time.

  3. 03

    Arrange delivery and activate

    Choose an available Certified Delivery Partner or submit your existing BYOIP-capable provider for review. LARUS coordinates delivery and activation with the selected provider.

  4. 04

    Share your identity. Grow your reach

    Share your Identity Passport and Allowlist Pack, put your first workflow to work, then add one Unit for each additional Location you use at the same time.

How LARUS One helps

LARUS anchors identity. The selected provider delivers the local network

01

Named security endpoints

Give security infrastructure clear public identity and rDNS naming.

02

Policy alignment

Share Identity Passport and Allowlist Pack evidence with your customers' security teams.

03

Delivery changes

Confirm any provider, location, or architecture change with LARUS before you switch.

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.

One paid pilot

Bring LARUS One to your first Location

Choose the connection that matters most. We coordinate delivery and activation, then grow with you as you add Locations.