BRCO Global EN

Controlled IoT Access

The private network connects. Remote access determines who gets in.

Limited access for technicians, integrators, or manufacturers to defined assets.

The private APN provides the route to the devices. This layer governs human access: identity, destination, service, validity period, and event logging according to the contracted scope.

Operations and supportIT and cybersecurityIntegratorsAuthorized manufacturers
What an access-control layer changes

It does not replace private connectivity. It adds governance over access.

The private route makes the assets reachable. The access-control layer applies a common policy before enabling a human session.

01

Consistent access

Users connect through a defined access path instead of creating a different method for every device.

02

Limited permissions

Each authorization is limited to the asset, service, and period required for the task.

03

Third-party control

Integrators and manufacturers can receive separate permissions, managed according to agreed responsibilities.

04

Support traceability

Session events and status may be retained for support and operational review, according to the contracted scope.

Outcome: a consistent path for internal users and third parties, without turning every asset into a separate entry point.

Where access is controlled

Managed environment or customer infrastructure.

Private connectivity can remain unchanged. What changes is who operates user access, policies, and logs.

Managed environment

Managed access

For organizations that need to enable access for technicians or third parties without operating their own remote-access infrastructure.

Best fit: teams without specialized infrastructure or those that prefer to delegate access operations.

●

User access termination

●

Policies by user, project, or group

●

Logging and support according to contracted scope

Customer infrastructure

Customer-operated access

For organizations that already have a firewall, VPN, or cloud infrastructure and want to retain control of users and policies.

Best fit: IT teams able to operate authentication, permissions, changes, and event review.

●

Users and authentication operated by the customer

●

Policies applied on the customer firewall or access platform

●

Additional component only when required by the design

This decision does not replace the architecture of the Private APN. The private connection between the mobile network and the authorized environment is defined separately.

Access policy

Five decisions before enabling a session.

Access is limited to what the task requires, without granting broad reach across the private network.

Five decisions before enabling a session.

Core access functions.

Controls that govern user entry to private assets.

Access termination

Defined point for authenticating and receiving remote sessions.

Segmentation and rules

Separation by user, project, asset, range, or application.

Access lifecycle

Provisioning, changes, expiration, and revocation according to agreed responsibilities.

Event logging

Information available for support and operational review, according to the contracted scope.

Optional operations and resilience.

Additional capabilities included according to criticality, compatibility, and contract.

Access-layer monitoring

Monitoring the status and availability of the access component.

Retention and export

Retention or forwarding of events when supported by the platform and scope.

High availability

HA or failover design when justified by continuity requirements.

Access redundancy

A second endpoint or tunnel, subject to the architecture and environment compatibility.

Responsible scope. The access layer provides authentication, authorization, control, and logging. By itself, it is not a NOC, a device-monitoring service, or comprehensive asset management. Final capabilities depend on the contract and technical environment.

Access governance

Define, validate, and operate every permission.

Implementation focuses on users, assets, services, and responsibilities. Private connectivity is treated as a prerequisite and is not redesigned on this page.

  • Users, assets, services, schedules, validity periods, and approval owners.
  • Authentication, isolation, permissions, revocation, and event logging.
  • Provisioning, deprovisioning, changes, support, and periodic review according to the contract.

I agree to the processing of my personal data according to the privacy policy.