
Device connects
An engineer connects a laptop to the network at a regional utility office.
Industries|Energy & Utilities
Secure branch and field site connectivity with web filtering

An engineer connects a laptop to the network at a regional utility office.

The solution checks whether the device is registered and meets configured posture requirements, such as patch level, antivirus status and disk encryption.

Compliant devices are allowed according to policy, while unregistered or non-compliant devices are denied or quarantined.
Why it matters

Apply a common device-admission policy across field offices and regional locations without requiring a switch or VLAN redesign at every site.

Restrict non-compliant laptops before they can become an entry point to shared business systems.

Require contractor and vendor laptops to be registered before they are admitted to the network.

Help a small central IT team manage device admission across locations with limited local IT support.
Use cases
01
An engineer returns to a field office with a laptop that has been offline for weeks and has missed important security updates.
ZT-NAC checks the laptop against configured posture requirements and quarantines it through its host firewall if it fails.
The laptop remains restricted until it meets the utility's security requirements, reducing its exposure to shared systems.
02
A contractor connects an unregistered laptop to an available network port while working on a utility project.
ZT-NAC denies the device by default until utility IT registers it and it meets the required posture.
An unknown contractor device does not receive unrestricted access to the utility's office network.
03
Central IT manages many utility offices spread across a large service area, with limited technical staff at individual locations.
ZT-NAC applies the same agent-based, host-firewall enforcement wherever the supported agent is deployed.
The utility can maintain consistent admission controls without relying on local IT staff to configure each site's network.
See how device compliance works
Check every laptop, workstation, and branch device against the bank’s security policy before it connects, using ZT-NAC.
Read the full solution →See how COSGrid provides solutions for Retail
Let’s see how COSGrid enables secure remote access and network visibility across stores, warehouses, and head office.
Explore the Industry →See how audit visibility works
Keep a clear, searchable record of network activity so the bank can show auditors and regulators exactly what happened and when, with NetShield NDR.
Read the full solution →
The security team needs to investigate which devices communicated with a billing system hosted in the head-office data centre.

NetShield NDR analyses available network traffic and flow metadata to identify communications between devices and systems.

The utility correlates available network records with access logs and other security evidence to investigate the activity.
Why it matters

Gain additional context about communication between regional offices, endpoints and data-centre systems.

Use available TLS handshake and flow metadata without decrypting traffic at this detection layer.

Review the communication patterns of a potentially compromised device to help determine which systems it contacted.

Network-level visibility can include devices that do not run an endpoint agent, subject to the available traffic visibility and sensor deployment.
Use cases
01
An internal audit team needs to investigate communications with customer billing and data systems hosted in the utility's data centre.
NetShield NDR is designed to provide network-level evidence of device communications, which can be reviewed alongside available access records.
The audit team has additional evidence for investigating network activity instead of relying exclusively on authentication records.
02
A laptop at a remote division office is found to be compromised, and the security team needs to establish which internal systems it contacted.
NetShield NDR analyses available network flows associated with the device, including encrypted connections through metadata.
The team can use observed communication patterns to scope the incident and guide its investigation.
03
A regional office operates printers and older servers that cannot run the utility's endpoint security agent.
NetShield NDR is designed to provide visibility into network traffic involving those devices when the relevant traffic is visible to its sensors.
The utility can investigate communications involving more than just agent-managed endpoints.
See how audit visibility works
Keep a clear, searchable record of network activity so the bank can show auditors and regulators exactly what happened and when, with NetShield NDR.
Read the full solution →See how COSGrid provides solutions for Retail
Let’s see how COSGrid enables secure remote access and network visibility across stores, warehouses, and head office.
Explore the Industry →See how In Country Security Control
Keep security functions, access logs, and traffic data inside the bank’s own environment and national borders, with deployment records ready for auditors.
Read the full solution →
The utility identifies the applications employees and external vendors need, along with its requirements for access infrastructure and logs.

SwiftZAccess provides browser-based access for authorised vendors, while MicroZAccess provides per-application access for supported managed devices.

The utility manages access policies and reviews available access records within the chosen deployment model.
Why it matters

Give external service providers access to specific authorised web applications without placing their devices on the utility's network.

Restrict managed-device users to the internal applications approved for their roles.

Self-host SwiftZAccess in the utility's own environment where required, subject to the deployment architecture.

Use deployment records and available access logs to help answer questions about where access infrastructure runs and where records are maintained.
Use cases
01
An outsourced billing-support provider needs to use one internal web application from devices that the utility does not manage.
SwiftZAccess can be self-hosted in the utility's environment and configured to provide the vendor with browser access to the approved application only.
The vendor can perform its assigned work without receiving broad network access or installing an agent on its device.
02
Engineers at regional offices and field locations need to reach approved utility applications from managed laptops.
MicroZAccess applies per-application access policies to authorised devices through its peer-routed mesh architecture.
Engineers can reach the applications required for their work without being granted unrestricted network-level access.
03
A utility's risk committee asks where its access infrastructure operates and where access records are maintained.
The utility reviews its deployment configuration and available records for the self-hosted SwiftZAccess components and its MicroZAccess deployment.
The utility can document the actual deployment and data-handling arrangements. Regulatory compliance must be assessed against the applicable requirements and the complete deployment architecture.
See how In Country Security Control works
Keep security functions, access logs, and traffic data inside the bank’s own environment and national borders, with deployment records ready for auditors.
Read the full solution →See how COSGrid provides solutions for Retail
Let’s see how COSGrid enables secure remote access and network visibility across stores, warehouses, and head office.
Explore the Industry →See how device compliance works
Check every laptop, workstation, and branch device against the bank’s security policy before it connects, using ZT-NAC.
Read the full solution →Necessary Cookies
Performance Cookies
Targetting Cookies
Functional Cookies