Security
Where your data stays
PureView runs on your own server, so your network data stays on your network. The appliance tells us which version it runs and which licence it holds, and the request it uses is refused by its format if it carries anything more. If you choose PureView mail for alarm email, the appliance also sends us a short notice for each alarm, as described below.
What stays on your network
What stays on your network, and the one connection the appliance makes to us.
- Your credentials stay with you
- The device and server passwords the appliance uses are held on the appliance, on your hardware. We hold no copy, and our systems have no way to receive one.
- The update request carries no operational data
- When the appliance checks for updates, it tells us which version it runs and which licence it holds, because we cannot say whether an update applies without knowing both. Device counts, hostnames, addresses, topology, syslog and configuration are refused by the format of that request itself.
- PureView mail carries a notice, not the alarm
- PureView mail is optional, for a site with no mail server of its own. For each alarm, the appliance sends us who to tell, the alarm's priority, whether it has opened, is still open or has cleared, the time, the sender name you set and a link to your console. It never sends what failed or where. Device names, ports, rooms and IP and MAC addresses are refused by the format of that request, and a console reached by an IP address gets no link. We keep only whether each notice was delivered. Notices are sent through our mail provider, which handles the recipient's address and the notice to deliver it.
- Activation and updates need one outbound connection
- The appliance needs outbound HTTPS to Zenaclove to activate its licence and to check for updates. It needs no inbound access from the internet.
- Signatures are checked on your appliance
- Zenaclove signs every licence and every release. The appliance checks those signatures itself, against keys built into PureView, before it accepts a licence or installs an update.
What we hold
We hold commercial records only: your organisation, your subscription, your licences and your support history. This is how we protect them.
- Records are separated by organisation
- Every record we hold belongs to one organisation. Our database enforces that separation itself, as a second check behind the application's own.
- Access is decided on the server
- What you can see and do in your client account is checked on our server for every request, by the same check whatever page the request comes from.
- Sensitive actions ask again
- Issuing a licence, publishing a release, changing what someone is allowed to do, or authorising support access each needs a two step verification code confirmed within the last 15 minutes.
- The audit trail is tamper-evident
- Each audit entry is linked to the one before it. If an entry is altered or removed, the break in the chain shows it. This shows tampering after the fact; it is not a guarantee that tampering is impossible.
- Signing keys are held apart
- The private key that signs licences is kept outside the web application and its database. Only the public key, which is all that checking a signature needs, is stored there.
What your team looks after
Because the appliance runs on your server, some of its security is in your hands.
- The credentials you give the appliance
- The appliance holds passwords for your devices and servers. Limiting those accounts to what PureView needs, and changing their passwords, is for your team. We never receive them, so we cannot change them for you.
- Who can sign in to the console
- Your organisation creates and removes the accounts on your installation. We do not create, approve or remove them.
- The server it runs on
- Patching and securing the server PureView runs on is for your team, as it would be for any server you run.
Report a security problem
If you have found a security problem in PureView or in this site, tell us and say in the first line that it is a security report. We route those reports straight to the engineers.
Include enough detail to reproduce it. Please do not send live credentials, customer data or anything from a production appliance.
Security questions
If they have questions this page does not answer, send them to us and an engineer will reply.