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.
Vulnerability disclosure
Reporting a vulnerability
Last updated: 2026-09-30 · Version 1.0
This is our coordinated vulnerability disclosure policy and our statement of support under the EU Cyber Resilience Act (Regulation (EU) 2024/2847).
1. Reporting a vulnerability
Email [email protected]. Please do not report security issues in public channels. Include, if you can:
- the affected component and version (shown in the product under Configuration → Runtime);
- a description, the impact you see, and steps or a proof of concept to reproduce it;
- whether you believe it is being exploited — say so in the subject line.
Machine-readable contact details are in /.well-known/security.txt.
2. What happens next
- Acknowledgement within 3 business days.
- Assessment and severity (CVSS) within 10 business days.
- For high and critical issues, a fix or mitigation as soon as practicable, with a target of 30 days.
- Public disclosure after a fix is available, agreed with you. We credit reporters who wish to be named.
Actively exploited vulnerabilities and severe incidents are reported to the Portuguese national CSIRT (CERT.PT) and to ENISA within the deadlines of Article 14 of the Cyber Resilience Act.
3. Support period
Security updates for SyncTide 1.x are provided until at least 31 December 2031, for the latest release of the 1.x line. Updates are delivered as signed packages; customers should stay on the latest release. The end of the support period will be announced at least 12 months in advance.
4. Advisories and SBOM
Security fixes are described in the release notes of the version that contains them, with the affected versions and the recommended action. A software bill of materials (CycloneDX) accompanies each release and is available to customers on request.
5. Scope
In scope: the SyncTide backend and API, web interface, data-collection and protocol workers, updater, Windows installer, Docker images, and the hosted service at *.synctide.app. Out of scope: denial of service by volume, social engineering, physical access, issues in third-party components with no impact on SyncTide, and installations configured against the documented hardening guidance. Do not access or modify customer data beyond what is needed to demonstrate an issue; for the hosted service, use only an instance you are entitled to use.
6. Safe harbour
We will not pursue legal action against researchers who act in good faith, follow this policy, avoid privacy violations and service disruption, and give us reasonable time to fix an issue before disclosing it.