XPN is a feature of the Intertrust Platform that provides end-to-end, persistent and consistent trust and security for IoT devices and the data they transmit.

Intertrust XPN allows you to conveniently and safely make data resources available for internal and external use, assuring that your explicitly defined usage policies are enforced in various environments. It is an effective way of demonstrating compliance with data usage requirements. 

XPN provides end-to-end trust from the device to the cloud. 

• The XPN device SDK is available on multiple chipsets, and as a C library for easy portability
• The XPN service in the cloud provides a simple interface to access data collected and transmitted from devices

Instead of patching together multiple tools, XPN provides businesses a single pane of glass solution for trust and protection of their IoT devices, the data they transmit, and their data operations. With XPN, businesses and their customers and partners can rest assured that they operate in a “full-trust” environment with a complete chain of trust for their data and a secure data platform for mission critical data-driven applications.

XPN’s edge-to-cloud security also provides businesses an auditable chain of trust for IoT data. This is especially useful for businesses that need to demonstrate the provenance and veracity of their IoT data for business transactions or regulatory requirements.

XPN extends Intertrust Platform’s features to provide end-to-end trust and protection that covers IoT devices, including older legacy devices, and the data from the device as it travels to the cloud and back to the device again. It does this by authenticating devices, asserting their secure status, persistently protecting the data as it travels from the device to the cloud and back to the device, and providing additional data points for audits.

See the XPN use cases below. 

a) Persistent data protection: XPN ensures that sensitive processing in IoT devices only occurs in secure environments. Data packages are digitally signed and optionally encrypted before being transmitted. When received on the server side of Intertrust Platform, the data is verified to assure its integrity and, upon confirmation, routed to its final destination, or processed in the Platform’s protected processing environment. IoT data is also easily combined with other data and metadata sources.

b) Enhanced auditing: Intertrust Platform includes extensive auditing features as part of its data governance capabilities. XPN expands this by introducing the ability to add information on IoT data used in transactions to the audit. This information can include timestamps and contextual metadata to prove provenance of data and protect against deep fakes. It also offers attestations on device and data integrity to provide further assurance of data trustworthiness. 

Organizations can use these enhanced audits for business, operational and regulatory purposes.

c) Commands: Commands with authorization control actuators so you can manage machines at the edge, for example, to change temperature on a thermostat or turn off an air conditioner.

a) A company that sells connected electric water heaters contracts with an electric utility to use its network of heaters to shed loads in demand / response when required. The company authenticates the water heaters using XPN, ensuring the security of the device. When the company’s cloud application connects to a water heater, it attests that it is secure and is allowed to join the network. Data from the water heaters is encrypted and protected by XPN all the way through to the cloud application and back to the water heater. The company can also use metadata from the IoT data for any transactional audits the utility might require.

b) A factory is required by the investors in the company that owns it to prove it met the carbon emission reduction standards set by the company. The company decides to do this by using data from sensors on the devices in the factory which are a combination of older legacy devices and more modern devices. XPN ensures that the data from all of the devices only comes from known secure devices and is protected all the way to the cloud based analytics program used by the company. The factory management produces a report detailing carbon emissions reductions of the factor and is able to demonstrate the provenance of the data.

a) A utility transmits unencrypted data from sensors on wind turbines over a secure IPSec tunnel to a gateway device which then encrypts the data and transmits it to the utility’s cloud data repository. However, an attacker has placed malware on the gateway that “poisons” the data so that the machine learning algorithms using the wind farm data to monitor its operational health determine that the wind farm is on the verge of a catastrophic breakdown. The wind farm is then shut down, leading to power instability for the region. XPN would mitigate this threat by allowing the utility’s cloud service to authenticate the data it receives and if it can’t, flagging it as untrustworthy. The data will no longer be used operationally until the issue is resolved.

b) A building developer uses a cloud application to improve the energy efficiency of one of its buildings. One of the inputs the application uses is temperature data from a legacy SCADA device in the building. Since the SCADA device isn’t equipped with recent hardware security protection and isn’t behind a firewall, an attacker initiates a malformed connection to the device and places malware on the device. XPN maintains digital twins for legacy devices and the legacy device can only connect to the digital twin. Any other connection to the legacy device must go to the digital twin through a firewall maintained by Intertrust Platform. The attacker’s malformed connection is detected and refused by the firewall.

A VPN protects data as it is being transmitted over the Internet, often by creating an encrypted “tunnel” for the network link the data is traversing. Once the data leaves the VPN connection, it is no longer protected by the VPN and dependent on whatever security features are implemented in its new environment. XPN Persistent Data Protection feature consistently protects the data regardless of the network or device it is located in. Further complicating things, VPN requires detailed configuration whereas XPN packets always know their routing destination.. Additionally, VPN technology offers neither the persistent data protection nor the simple routing of XPN.

Encryption turns data into an unreadable blob that can only be read if the reader holds a secret key. This protects the data from an unauthorized party reading it but does little else. XPN’s Persistent Data Protection and Entity Attestation Tokens add metadata to the data to help establish the provenance and secure state of the device that transmitted the data as well as authenticate that the data has not been altered after it was transmitted by the device.

The XPN metadata attached to data, even if it is encrypted, can be used to establish an edge-to-cloud auditable chain of trust for data transmitted from IoT devices. This can be useful to demonstrate data provenance for business or regulatory purposes.

Most modern IoT devices or gateways can be used with the XPN SDK. Legacy devices that do not include the hardware security features needed to support the XPN SDK can be protected through the XPN Digital Twins feature.

One example of an important security standard gaining traction in industry is the NIST 8259A IoT Device Baseline standard. NIST 8259A requires IoT devices to support a number of core security capabilities. 

XPN can help IoT device manufacturers and deployers meet a number of these including: a) Device Identification: XPN Entity Attestation Tokens and metadata includes device identity information, b) Device Configuration: XPN Entity Attestation Tokens  can show that the software on the device has not been changed in an unauthorized manner, c) Data Protection: XPN secret keys can be used to encrypt data and XPN metadata can be used to establish that data has not been tampered with after it was transmitted from the device, d) Logical Access to Interfaces: XPN Digital Twins doesn’t allow network connections to vulnerable legacy devices, e) Software Update: XPN digital signatures protect the software and ensures that it works on top of the hardware security needed to protect the software during an update, d) Cybersecurity State Awareness: XPN Entity Attestation Tokens and Digital Twins features provide information to applications and networks that the attached devices are secure.

On the device side, XPN is implemented via the XPN SDK (software development kit). On the server side, XPN uses the XPN Server Client which is integrated with Intertrust Platform.

On the device side, XPN requires at minimum a 32-bit microcontroller equipped with a secure processing environment. Most modern embedded operating systems such as FreeRTOS and various versions of embedded Linux are supported.

A device manufacturer or deployer can incorporate XPN into a device by using the XPN SDK. XPN is a feature of Intertrust Platform and can be incorporated into any end-to-end application which uses Intertrust Platform.

Yes, both the XPN SDK and Intertrust Platform can be implemented on premises.

Yes, Intertrust has a number of system integrator partners who can help integrate XPN into IoT networks. Please see the Intertrust Platform partners page.

Yes, support is available through Intertrust’s customer support team and Intertrust Platform partners.

XPN is available through an XPN toolkit from Intertrust. Each XPN toolkit includes device and application SDKs, import tools, and identity management services.

These sets of tools and services allow you to define, configure, operate, and monitor XPN. Contact the Intertrust sales team or a system integrator partner to get started.