The threat we design against
Industrial and infrastructure operators have learned to treat every connected device as a possible entry point. That caution is justified. A sensor that is poorly secured can expose operational data, can be used to move deeper into a network and can be made to report false information.
AFFERENT's design goal is that adding a NODE to a facility should improve the operator's understanding of their equipment without widening their exposure. The principles below follow from that goal.
Design principles
Observe, do not control
NODE is a sensing device. It is designed to observe an asset, not to operate it. Keeping the device out of the control path removes an entire category of risk: a monitoring device that cannot command a machine cannot be used to command it.
Device identity
Every device should be individually identifiable and able to prove its identity. A platform that cannot tell a genuine device from an imitation cannot trust the data it receives.
Encryption in transit and at rest
Data moving between a device and AFFERENT Cloud is designed to be encrypted in transit, and stored data is designed to be encrypted at rest. Communication is intended to be initiated by the device, so that a facility does not need to open inbound access to its network.
Least privilege
Devices, services and people should have the access their role requires and nothing more. Access to customer data is designed to be role-based, limited and recorded.
Secure updates
Devices in the field must be updatable, because vulnerabilities are discovered over time. Updates must also be trustworthy. Software delivered to a device is designed to be verified before it is installed, with a safe path back if an update fails.
Data minimization
Processing at the edge limits what leaves a site. Transmitting findings and supporting evidence, in place of continuous raw streams, reduces both the volume and the sensitivity of data in motion.
Customer ownership of data
Operational data belongs to the customer who generated it. How that data is used, retained and deleted will be governed by written agreements, not assumptions.
What we do not claim
AFFERENT does not currently display any security certification, because we will display a certification only after it has been earned and can be verified. This page describes design principles and intended architecture. It is not an attestation, an audit report or a statement of compliance with any standard.
Customers evaluating AFFERENT for sensitive environments should expect to review current security documentation directly with us. Contact the team to begin that conversation.
Reporting a vulnerability
If you believe you have found a security issue in an AFFERENT product or service, please read our responsible disclosure policy. We welcome reports from security researchers.
