Security

Security

SyncTide watches water, energy and industrial installations, so its security is part of our customers' operations. This page says how the platform is protected and how to report a vulnerability.

The platform

How SyncTide is protected

Accounts and access

  • Passwords are stored as salted PBKDF2-SHA256 hashes with 260,000 iterations.
  • Two-factor authentication (TOTP) with any authenticator app, offline too; it can be required per role.
  • Roles — viewer, operator, administrator — and access limited to chosen equipment.
  • Login attempts are limited per address and per account; sessions end after 12 hours by default, and after the period of inactivity you set.
  • An audit log of logins, changes and administrative actions.

The web interface

  • Every script, font and style is served by SyncTide itself; the only outside request is the map tiles, when a page shows the map.
  • A Content-Security-Policy allows only the platform's own scripts. It is enforced in our cloud; on your server it starts in report mode and is switched on with one setting.
  • Headers stop other sites from framing the interface and stop uploads from being run as scripts.
  • HTTPS: in our cloud with certificates renewed automatically; on your server with one command, using a built-in certificate authority — no domain or internet connection needed.

Updates and licences

  • Updates are signed (Ed25519) and checked against a key built into SyncTide before anything runs; every file is checked against its SHA-256 hash.
  • An installer downloaded from the interface runs only when its signature and its SHA-256 match.
  • The key that signs updates is separate from the key that signs licences.
  • Licence files are signed; the tag limit and the licensed modules are enforced by the software.

Data and networks

  • On your server the data stays on your network: SyncTide sends nothing to us.
  • Photos from field visits are stored without location or camera data. New in 1.14.8 — coming soon
  • Industrial protocols such as Modbus TCP and IEC 104 have no encryption of their own: keep the PLCs on a separate network and reach remote sites through a VPN.
  • For encryption at rest, use the operating system's own: BitLocker on Windows.

Our cloud

  • Servers in Germany (EU); each customer has its own application containers and database.
  • A firewall with only the ports needed; administrative access by SSH key only.
  • Daily backups of the database and the files, with an integrity check, kept for 30 days.
  • Dataloggers can send by SFTP or FTPS. Plain FTP is offered for loggers that support nothing else, and it is not encrypted.

Where SyncTide runs

Your server or our cloud: what each option covers, backups and updates.