Our position
Security claims are easy to make and difficult to verify. Our policy is to describe what we design for, to say plainly which claims have been independently verified, and to display a certification mark only when the certification has been granted and is current.
At present AFFERENT does not hold and does not display any third-party security certification. When that changes, this page will say so, with the scope and date.
Data encryption
Our design standard is that data is encrypted whenever it moves between a device and our services, and whenever it is stored. This website is served only over encrypted connections.
Edge security
A device in the field can be physically reached by people who should not have it. The NODE design therefore treats the device itself as part of the security boundary: each device is intended to have its own identity, to run only software it can verify and to keep the minimum of sensitive data. NODE is designed to observe equipment, not to control it.
Secure communications
Communication between devices and AFFERENT Cloud is designed to be authenticated in both directions and initiated from the device, so that a customer does not need to permit inbound connections into an operational network.
Access controls
Access to customer data is designed to follow the principle of least privilege: limited to the people and services that need it, tied to individual identities and recorded. The administrative system behind this website applies the same approach, with role-based permissions and an audit log of administrative actions.
Vulnerability management
Software has defects, and some defects are security vulnerabilities. Our commitment is to make reporting easy, to assess reports promptly, to fix confirmed issues and to be able to deliver fixes to devices already in the field.
Responsible disclosure
We welcome reports from security researchers. Our responsible disclosure policy explains how to report an issue and what you can expect from us.
For customers
Organizations evaluating AFFERENT for sensitive environments can request current security documentation directly. Contact the team. For the engineering detail behind this page, see Security architecture.
Last updated October 7, 2026
