Security
Built to be audited.
A platform that sits between client sites and a monitoring centre holds credentials, video and the record of who did what. These are the controls in place today, described as they are, with what each one covers.
How data moves
What crosses each hop, and what does not.
Four hops from a camera to an operator. At each one, only what the next step needs.
- 01
Source to platform
Events, snapshots and clips come from the camera vendor’s service with the credentials the customer supplied, or arrive from a Nexus appliance over its outbound link. Nothing is pulled from a site that was not connected on purpose.
- 02
Inside the platform
Every record carries its organisation, and the database enforces that boundary itself. Vendor credentials are encrypted before they are written; session tokens and API keys are stored as hashes.
- 03
Platform to monitoring centre
An alarm leaves with its clip and snapshot, to the monitoring platform the customer designated, in that platform’s own format. Operators open live video through the platform, never by reaching the site directly.
- 04
Platform to people
The dashboard is served through a global edge over TLS, with a WAF, behavioural blocking and rate limits in front. Clip links are signed and expire. Every sign-in, role change and alarm action is written to the audit trail.
Identity
Who can sign in, and how.
- Two-factor authenticationPlatform
- Authenticator-app codes with single-use recovery codes. Mandatory for administrators, owners and platform staff; enforceable per organisation for everyone.
- Single sign-onPlatform
- OpenID Connect per organisation with groups mapped to roles. Enforcement is optional, and an owner with a password is kept as break-glass so a broken identity provider cannot lock an organisation out.
- Password policyPlatform
- Twelve characters minimum, no reuse of recent passwords, nothing that contains the username or email, checked against a bundled list of common passwords and against the Have I Been Pwned range service. That check sends the first five characters of a hash, never the password, and a candidate is not rejected if the service cannot be reached.
- Brute-force protectionPlatform
- Per-identifier and per-address limits at the gateway with constant-time handling for unknown accounts, and a tighter ceiling on credential endpoints at the edge before a request reaches the gateway at all.
- SessionsPlatform
- Tokens are stored hashed. Absolute and idle limits apply, shorter for privileged roles. Every user can see their own sessions and end any of them, including all at once.
- InvitationsPlatform
- Email invitations carry a role and site grants set by the inviter. Links expire; an administrator can resend or revoke one before it is used.
Authorisation and tenancy
Who can see what.
- Four rolesPlatform
- Viewer, operator, admin and owner. Viewers and operators can be limited to named sites. The last administrator of an organisation cannot be removed or demoted.
- OrganisationsPlatform
- Every customer is an organisation. A monitoring centre is a partner organisation with client organisations beneath it; its administrators reach only that subtree.
- Support access by consentPlatform
- A client decides whether its monitoring centre may enter the client organisation: always, never, or only during a time-boxed window the client opens. Each entry is audited.
- Isolation at the databasePlatform
- Row-level security separates organisations inside the database, not only in application code. A 152-case isolation test runs on every change and blocks the release if any case fails.
- API keysPlatform
- Bound to one organisation, scoped to read, ingest or admin, with an expiry (90 days by default, one year at most), stored hashed and listed for review and revocation.
- Audit trailPlatform
- Sign-ins, role changes, alarm actions, support entries, API-key and configuration changes: append-only and hash-chained, mirrored to logs, with the chain verifiable per event from the reports view.
Data
How credentials, video and backups are handled.
- Credentials at restPlatform
- Camera-vendor and integration credentials, and the secret for the backup target, are encrypted with AES-256-GCM before they are stored, and are never returned to a browser or written to a log.
- TransportEdge
- TLS at the edge with HSTS preload. The platform is reachable only through an outbound tunnel from where it runs; it has no public origin address to attack.
- ClipsPlatform
- Delivered to the monitoring platform with the alarm, and served to operators through signed links bound to one event that expire on their own.
- BackupsPlatform
- Database backups are taken with the standard Postgres tool to a storage target the operator configures. Any backup can be validated by restoring it into a scratch database before it is trusted; a live restore is a separate, typed-confirmation, audited step.
- RetentionPlatform
- Storage retention for clips and snapshots is set per organisation and enforced by the platform.
- AppliancesAppliance
- Nexus NVR connects outbound only, needs no inbound port or firewall change, and keeps working locally without the cloud. Remote configuration and video export use an audited tunnel that opens for the job and closes after it.
- Third partiesPlatform
- The parties that may handle customer data are few and listed publicly, with what each one sees. The list is updated before any addition.
See the subprocessor list.
The edge
Before a request reaches the platform.
- Global edgeEdge
- Every host is served through a global edge network with volumetric DDoS protection; the origin has no public address.
- Web application firewallEdge
- Every request is inspected against virtual-patching rules for known exploits and blocked when it matches. If the inspector cannot answer, the request is refused rather than let through.
- Behavioural blockingEdge
- Addresses that probe, scan or brute-force are banned from observed behaviour, and a community blocklist of tens of thousands of known bad actors is applied on top.
- Rate limitsEdge
- A per-client ceiling on every host, and a tighter one on sign-in, second-factor, password and invitation endpoints.
- Security headersEdge
- HSTS with preload, no framing, no content sniffing, a strict referrer policy, and a restrictive permissions policy on every host.
- This websiteThis site
- Static files only, no server-side code, no cookies, no third-party script, no analytics that profile a visitor, and a content security policy that allows nothing from anywhere else.
Disclosure
If you find something.
We would rather hear about a problem from you than from anyone else.
- ReportingPlatform
- Email [email protected] with a description, the steps to reproduce it and the impact you believe it has. You will get an acknowledgement within two business days and a status update at least every seven days until the report is closed.
- ScopePlatform
- The service at app.nxconnect.io and the other nxconnect.io hosts, and the images we publish. Out of scope: denial-of-service testing, physical attacks, social engineering, the third-party services we integrate with, and findings that need a compromised operator device.
- Safe harbourPlatform
- Good-faith research that stays in scope, avoids privacy violations and service disruption, and gives us reasonable time to fix an issue before disclosure will not lead to legal action from us. If you are unsure whether something is in scope, ask first.
- FixesPlatform
- Reports are triaged by the security owner and tracked to closure. Fixes ship through the normal release pipeline; a critical fix may go out under the emergency change procedure. Only the currently deployed release receives security fixes.
Assurance
Where we are, and what we do not claim yet.
An ISO 27001 and SOC 2 programme is underway, built on the controls above. Reports will be available on request when issued. Security questions and vulnerability reports go to [email protected].
Not claimed on this page
- Encryption of the database volume at rest. Credentials and backup secrets inside it are encrypted; the volume is not yet.
- A recorded restore drill. Backups can be validated by restoring them; the first scheduled drill has not been logged yet.
- Any certification achieved. The programme is in progress.
- A public status page or a documentation portal.