SECURITY / PROGNODESecurity at PROGNODE.
PROGNODE monitors industrial processes, so we treat security reports with priority. This page explains how to report a vulnerability and what you can expect from us.
01 / REPORTReport a vulnerability.
Email security@prognode.io. Please do not report suspected vulnerabilities in public forums or issue trackers.
- Product and version (PROGNODE Monitor shows it in the sidebar)
- What you found and its impact
- Steps to reproduce or a proof of concept, if available
- Whether you know of active exploitation
- How to reach you and whether you would like to be credited
Do not include real process data, customer data or credentials in a report.
02 / RESPONSEWhat happens next.
- Acknowledgement within 2 business days
- Initial assessment and severity (CVSS v4.0) within 5 business days
- Fix or mitigation: Critical within 14 days, High within 30 days, Medium and Low in the next planned release (at most 90 days)
- Public advisory when a fix is available, coordinated with you
Actively exploited vulnerabilities and severe incidents are reported to the competent authorities as required by law, including the EU Cyber Resilience Act and the Turkish Cyber Security Law.
03 / SUPPORTSupported versions.
PROGNODE Monitor receives security updates for at least five years after the first release of each major version. The PROGNODE Client for Windows and the mobile app are supported in their latest version; PROGNODE Cloud is updated centrally.
PROGNODE Monitor and the Windows Client check for new versions and install them after confirmation. Every installer is verified with its published SHA-256 checksum before it runs.
04 / DESIGNSecurity by design.
- Read-only industrial connectors — PROGNODE never writes to PLCs or field devices
- Process data stays on the PROGNODE Monitor PC; Remote Access relays alarm metadata only
- Web interface on localhost only; phones and Windows PCs connect over pinned HTTPS with a check code at pairing
- Licenses, activation and offline sign-in verified locally with Ed25519 signatures; passwords stored as Argon2id verifiers
- Encrypted backups (AES-256-GCM)
- A software bill of materials (CycloneDX) for every build; dependencies scanned for known vulnerabilities
05 / RESEARCHGood-faith research.
We will not pursue legal action against research done in good faith within this policy: test only your own installation or a test environment, avoid privacy violations and service disruption, do not access other customers' data and never test against industrial equipment you are not authorised to operate.