Dev security
How we build, test and release the software you run. These practices come from years of delivering production IoT solutions on our own platform.
-
Code review and protected branches
Every change is reviewed before merge, and branch protection keeps unreviewed code out. -
Separate environments
Development, test and production run separately, and production data is never used in tests. -
Code analysis (SAST)
Snyk Code scans LTS branches every week. -
Dependency scanning
Snyk Open Source checks third-party dependencies every week. -
Container scanning
Docker Scout and Snyk Container scan our container images. -
Change management
Changes are requested, assessed and approved and tracked in Jira; minor changes follow a shortened path. -
Independent penetration testing
An external tester checks the platform every year, following OWASP, OSSTMM and NIST SP 800-115. The latest test, by DataArt, ran in February 2026, with a retest in March 2026. -
Security fixes and CVEs
Security fixes ship in maintenance and patch releases, which need no upgrade script. Fixed CVE IDs are listed in the Security section of the release notes. -
Release support
LTS releases are supported for 18 months, standard releases for 6 months.
Read next
Can’t find what you need?
Our security team answers questions, shares documents under NDA and handles vulnerability reports.
-
Contact our security team
Questions, questionnaires and data requests.
-
Get documents
Certificates and policies; request the NDA ones from the library.
-
Report a vulnerability
Tell us privately. We reply within three business days.