Skip to content
Home ยป Security at Prixl

Security at Prixl

You are putting Prixl software on the server that holds your firm’s client files, so you should know exactly what it does and how we look after the data it sends us. This page sets that out. The detailed list of data is in our Privacy Policy, and the outside companies we use are on the sub-processors page.

Where your data lives

Everything the Warden agent and Guard send from your servers is stored in India, on Amazon Web Services in the Mumbai region (ap-south-1): the service the agent talks to, the event database, the monthly archive and uploaded diagnostic logs. Event history is deleted automatically about 35 days after it reaches us. Alert and summary emails are sent through Zoho ZeptoMail’s Indian service.

There is no Prixl cloud dashboard. The Warden dashboard runs on your server itself, so your settings and the dashboard you look at stay on your own machine.

What the Warden agent can and cannot do

Warden installs to C:\Program Files\Prixl\Warden\ and runs as two Windows services, “Prixl Warden Activity Monitor” and “Prixl Warden Updater”, under the LocalSystem account. It needs those rights to read the Windows Security log and to change firewall rules when you ask it to.

It reads:

  • The Windows Security and System event logs: sign-ins, account and group changes, new services and scheduled tasks, policy and firewall changes.
  • The Windows Firewall log of blocked connections, to count attacks on each port.
  • The Windows settings its 29-check security audit looks at, such as Remote Desktop, firewall, password and lockout policy, SMBv1, Defender and update age.

It changes things only when your administrator asks: a one-click fix from the Hardening tab (each one can be reverted), a manual IP block, automatic blocking of attacking IPs (off until you switch it on), a block requested through the link in an alert email, the Guard set-up, and locking Remote Desktop to Guard. Every change made from the dashboard is emailed to your administrators with the Windows user name of the person who made it.

It never reads the contents of your files, documents, Tally data, email or browsing, and it does not record keystrokes or the screen. It never collects passwords.

What the Prixl cloud can ask the agent to do. There is no remote command line: the cloud never sends the agent a command to run, and the one exception is described under “Installers and automatic updates” below. The cloud sends the agent its signed licence and monitoring rules (which Windows events to watch and how to judge them), keeps the Guard list of invited people in step, and can restore your own dashboard settings if the server’s local copy is lost. Beyond that, it can only:

  • pass on an IP block that your administrator requested from an alert email;
  • ask for a copy of Warden’s own recent log files when we are diagnosing a fault;
  • re-open Remote Desktop if your administrator is locked out after locking it to Guard and asks us to help (it stays open until they lock it again);
  • offer a Warden update (see below).

Network: outbound HTTPS only

  • Warden connects out over HTTPS (port 443) to api.warden.prixl.io and, for updates, downloads.prixl.io. You do not open any inbound port for monitoring.
  • The dashboard listens only on the server itself (127.0.0.1, port 9843), so other computers on your network cannot reach it. Opening it needs a Windows administrator (a UAC prompt) and an access token stored in a file that only administrators can read.
  • If you use Guard, Warden adds an inbound firewall rule for WireGuard on UDP port 51820, and one that lets staff connected through Guard ping the server. WireGuard does not answer packets that are not from an invited device, so port scanners see nothing there.

Encryption and authentication

  • In transit: everything between your server and Prixl uses HTTPS.
  • At rest: the database and storage in AWS are encrypted. On your server, Warden’s settings and credentials under C:\ProgramData\Prixl\warden\ are stored encrypted.
  • Each server proves who it is: when Warden enrols it receives its own device secret, and it uses that secret to authenticate every request. One server cannot send data as another.
  • Your licence and settings from us are signed: the agent checks a digital signature, made with a key held in AWS Key Management Service, before it accepts its licence and monitoring rules.

Installers and automatic updates

  • Download Warden only from the link in your welcome email, which points to downloads.prixl.io over HTTPS. The installer is not yet signed with a Windows code-signing certificate, so Windows SmartScreen may show a warning when you run it. We are working on getting one.
  • The “Prixl Warden Updater” service checks for a new version every few minutes. Before installing one it checks the file’s SHA-256 fingerprint against the value the Prixl cloud gives it, together with a code tied to your server’s own device secret. A file that fails either check is not installed.
  • You can turn off automatic installs in the dashboard under Settings, Software Updates, “Install updates automatically”. Updates marked as mandatory security fixes still install at their deadline.
  • The updater is able to run a PowerShell script that is part of an update package, before or after the files are replaced, under the same LocalSystem account. Each script’s own fingerprint is checked against the package’s list before it runs. Our publishing tool does not add one today. Packages are published only by Prixl, so this is the one way new code can reach your server, which is why the fingerprint and device-secret checks above matter.

Who at Prixl can see your data

Only the few Prixl staff who run the service can reach production systems. They look at a customer’s data only to give support the customer asked for, to fix a fault, to investigate a security problem, or when the law requires it, and access is logged. We do not sell data and we do not use it for advertising.

Guard Secure Access: we cannot see inside the tunnel

  • Guard uses WireGuard. Each staff member’s Guard app creates its own key pair on their computer; only the public key is sent to Prixl. The office server’s private key stays on the server.
  • The Remote Desktop session travels inside the encrypted tunnel between the staff computer and your server. Prixl’s cloud only helps the two ends find each other; it never holds the keys and cannot read the traffic.
  • When a direct connection is impossible (for example on some mobile and CGNAT networks), the encrypted packets go through a Cloudflare relay. Cloudflare carries only encrypted WireGuard packets and takes no part in the key exchange.
  • Your administrator invites each person with a one-time code that expires after 24 hours, and can revoke anyone from the Secure Access tab.

More on how Guard works is on the Guard page.

If something goes wrong

We report cyber security incidents to CERT-In within 6 hours of noticing them, as the CERT-In Directions of 28 April 2022 require, and we tell affected customers without undue delay, with what we know and what they should do. The Privacy Policy explains our duties under the DPDP Act, which start in mid-May 2027.

Reporting a security problem

If you think you have found a vulnerability in Warden, Guard, our cloud service or this website, use the contact form and mark it “Security report”. Please include what you found, how to reproduce it, and how to reach you. We will acknowledge your report, keep you informed while we fix it, and credit you if you want. Please give us reasonable time to fix the problem before you make it public, and do not access or change other people’s data while testing. Our contact details are also published in security.txt.

Want to see Warden on your own server first? Start your 30-day free trial.