SECURE COMPLIANCE PROTOCOLS

• US 20190312855A1
• Filed: 04/06/2018
• Published: 10/10/2019
• Est. Priority Date: 04/06/2018
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Sharma, Puneet, Raghuramu, Arun, Lee, David
• Granted Patent: US 11,223,631 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/1834 implemented based on peer-to-peer networks, e.g. gnutella p2p communication protocols H04L67/104
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 2009/45587 Isolation or security of virtual machine instances
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 2209/127 Trusted platform modules [TPM]
• CPC Class Codes: H04L 63/0485 Networking architectures for enhanced packet encryption processing, e.g. offloading of IPsec packet processing or efficient security association look-up
• CPC Class Codes: H04L 63/0492 by using a location-limited connection, e.g. near-field communication or limited proximity of entities
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/3297 involving time stamps, e.g. generation of time stamps
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees
• CPC Class Codes: H04W 12/106 Packet or message integrity
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/40 for vehicles, e.g. vehicle-to-pedestrians [V2P]
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

In some examples, a secure compliance protocol may include a virtual computing instance (VCI) deployed on a hypervisor and may be provisioned with hardware computing resources. In some examples the VCI may also include a cryptoprocessor to provide cryptoprocessing to securely communicate with a plurality of nodes, and a plurality of agents to generate a plurality of compliance proofs; the VCI may communicate with a server corresponding to a node of the plurality of nodes; and receive a time stamp corresponding to at least one compliance proof based on a metric of a connected device.

Claims

1. A secure compliance protocol system comprising:

a virtual computing instance (VCI) deployed on a hypervisor and provisioned with a plurality of hardware computing resources, the VCI comprising;

a cryptoprocessor to provide cryptoprocessing to securely communicate with a plurality of nodes; and

a plurality of agents to generate a plurality of compliance proofs; and

the VCI to;

communicate with a server corresponding to a node of the plurality of nodes; and

receive a time stamp corresponding to at least one compliance proof based on a metric of a connected device.

2. The secure compliance protocol system of claim 1, wherein the at least one compliance proof is at least one of a proof of safety, a proof of privacy, a proof of regulation, and a proof of local compliance laws or combinations thereof.

3. The secure compliance protocol system of claim 1, wherein the server is a Mobile Edge Computing (MEC) server and further comprises a peer-to-peer file system to store the at least one compliance proof.

4. The secure compliance protocol system of claim 3, wherein the MEC server executes a compliance audit utilizing a smart contract corresponding to two different nodes from the plurality of nodes.

5. The secure compliance protocol system of claim 1, wherein the VCI is deployed in a vehicle and wherein a vehicle is transitioning between a first geographical location related to a first node of the plurality of nodes and a second geographical location related to a second node of the plurality of nodes and wherein an agent of the plurality of agents generates a secure content proof in response to an event trigger based on the connected vehicle transitioning from the first geographical location to the second geographical location.

6. The secure compliance protocol system of claim 5, wherein a compliance state of the vehicle is requested by a third-party application.

7. The secure compliance protocol system of claim 5, wherein a compliance state of the vehicle is requested by stakeholders.

8. The secure compliance protocol system of claim 5, wherein a smart contract is executed by the MEC server corresponding to the first node and wherein the MEC server and the corresponding first node are included in a compliance blockchain.

9. The secure compliance protocol system of claim 1, wherein the plurality of agents interacts with the cryptoprocessor to produce the compliance proofs of the connected device and provide the compliance proof to the server corresponding to a particular node of the plurality of nodes to be stored as an immutable record.

10. The secure compliance protocol system of claim 1, wherein the server includes a blockchain application to provide an interface between a compliance blockchain and a third-party application.

14. The method of claim 10, wherein the particular server corresponding to the first node executes a smart contract that is also executable by a different server corresponding to a second node.

15. The method of claim 10, wherein the server further comprises a compliance monitor to regulate a compliance proof collection from the at least one compliance proof based on an event trigger.

11. A method for secure compliance protocols, comprising:

deploying, on a hypervisor, a virtual computing instance (VCI) provisioned with a plurality of hardware computing resources;

deploying, on the hypervisor, a cryptoprocessor to provide cryptoprocessing to a plurality of agents and securely communicate with a plurality of servers;

executing, by the plurality of agents, instructions to generate a plurality of compliance proofs; and

authenticating a particular compliance proof of the plurality of compliance proofs at a particular time, wherein a time stamp of the particular time is generated by a particular server of the plurality of servers corresponding to a first node.

12. The method of claim 11, wherein the server is a Mobile Edge Computing (MEC) server and further comprises a compliance blockchain to store a plurality of immutable compliance proof records.

13. The method of claim 12, wherein the MEC server further comprises a blockchain application to provide an interface between the compliance blockchain and an end user.

16. A system comprising:

a memory storing instructions corresponding to a plurality of agents;

a processor to execute the instructions stored by the memory, the instructions to authenticate a plurality of compliance proofs;

a cryptoprocessor to;

provide cryptoprocessing to securely communicate with a plurality of nodes;

securely communicate with a Mobile Edge Computing (MEC) server corresponding to each node of the plurality of nodes;

transmit at least one compliance proof based on a metric of a connected device to a first MEC server corresponding to a first node of the plurality of nodes, and

transmit the compliance proof based on the metric of the connected device to a second MEC server corresponding to a second node of the plurality of nodes, wherein the first node and the second node correspond to a respective first and second geographical position.

17. The system of claim 16, wherein a first smart contract corresponding to the first MEC server includes the at least one compliance proof.

18. The system of claim 16, wherein a second smart contract corresponding to the second MEC server includes the at least one compliance proof

19. The system of claim 16, wherein the plurality of agents execute instructions to provide an anti-replay mechanism.

20. The system of claim 16, wherein the plurality of agents execute instructions to generate a content proof to be stored as an immutable record by the first server.