Frequently asked questions

Six weeks: discovery in week 0, installation in week 1, four weeks live with weekly reviews, and a readout in week 6 covering the incidents detected, faults localised and a baseline report. Choose one to three sites, including the one that complains most. About the pilot.

See Pricing.

They complement each other. Sensors give a constant, device-independent view of each location, 24/7. The laptop agent shows what one user's own machine is doing, but only while it is switched on. With both, you can tell a device problem from a network one: sensors fine but laptops slow points at the device.

CNA collects metrics, not logs or traces, so it sits alongside your logging and application performance monitoring tools rather than replacing them.

ModelB tests the service path (applications, DNS and the network path) over wired Ethernet or Wi-Fi. ModelC adds a Wi-Fi 7 adapter for sites with Wi-Fi 7 access points. ModelA is a small wireless-only Wi-Fi 6 probe that measures Wi-Fi where people sit. Most floors use a mix: see Sensors.

No. Sensors join your Wi-Fi or Ethernet like any user device. All connections are outbound: data travels over TLS, and management sessions are encrypted and started by the device, so no inbound firewall rules are needed. Details: Network requirements.

WPA2 and WPA3 Personal, WPA2-Enterprise with username and password (PEAP), and certificate-based EAP-TLS. Static IP addressing is supported as well as DHCP. Your administrator sets this in a network profile.

Yes. Switch that circuit's probe from ping to trace in the site settings.

We plan for these during discovery, together with static IP addressing, ping-blocked circuits and certificate-based Wi-Fi. Tell us about them early. If you use Zscaler, the laptop agent shows the Zscaler client connection details.

Where people sit, spread across each floor and including the worst spots, not directly under access points. See where to place sensors.

Yes. The defaults are 12 sites, 12 applications, 25 network profiles and 6 email groups, and each can be raised on request.

Monitoring data is kept for 90 days by default; longer retention is available at extra cost. Wi-Fi scans of nearby networks are kept for 24 hours, because of the volume of data they produce. The configuration audit trail is kept for a year.

Each client has a dedicated Cloud Unit, with its own portal and databases: no data is shared with other clients. It is hosted in the United Kingdom, or in your own private environment if you prefer.

Its storage is encrypted and unlocks only on the network, so a sensor taken off-site can't be read. Tell us if a sensor goes missing.

Yes. CNA holds IASME IoT Cyber Assurance Level 1, covering the devices, hub, apps and associated cloud services, and is reviewed independently every year. See Security.

It answers questions from your own monitoring data in the portal. Nothing is sent until someone asks it a question, it sees only what that person is allowed to see, and your data is not used to train AI models. Questions are processed in the EU: see the service privacy notice. A private AI option, for organisations whose policy keeps operational data away from public AI services, is coming next.

No. It helps people interpret what CNA measures and suggests what to check. Alerts are still the thresholds you set.

Yes, with your identity provider, such as Okta or Entra ID. Access to the portal can also be restricted to your own network or VPN.

A sustained problem typically raises an alert in about 10–15 minutes, day or night. That is an estimate from the default alert settings: rules are checked every two minutes and must stay in breach for ten. It can be tuned for you.

Email groups are standard. Teams, Slack, ITSM and on-call tools can be set up on request.

Each sensor tests up to 12 applications every two minutes, with DNS lookup time. Wi-Fi signal, quality, rate and access point are measured every 15 seconds, and nearby networks are scanned every 15–20 minutes (the 24 strongest access points).

Only the administrators you nominate. Views are role-based, and every change is recorded with who made it, when, and the old and new values. See IoT administration.

Yes. View (kiosk) mode hides the menus for a NOC wall. You can also share a view by link or snapshot. See working with dashboards.

If you sign in through your organisation's identity provider, your password is managed there, not in CNA.

History is kept when an application is replaced, so for a time range that spans the change you'll see both the old and the new one.