Trusted device control messages

1. A method, comprising:

detecting an event within a first device integrated into a terminal device, wherein the event is associated with at least one operation processed within the first device and the first device is a peripheral of the terminal device, wherein detecting further includes detecting the event as being associated with security threat data detected on the first device with the at least one operation processed within the first device, and wherein the security threat data being detected as one of: a secure access request made from the first device as the at least one operation, a resource installation request made from the first device as the at least one operation, a resource deactivation request made from the first device as the at least one operation, a monitoring activity detected on the first device as the at least one operation, a storage exception occurring on the first device as the at least one operation, and an invalid operation request made from the first device as the at least one operation;

defining the event as a trusted control message by gathering data associated with the event and including data as data associated with the security threat data within an encrypted communication that represents the trusted control message, and wherein defining further includes using a secure protocol to assign a unique message number to the trusted control message, wherein the unique message number includes a unique session identifier for the secure session and a unique number representing the trusted control message relative to other messages passed during the secure session having other message numbers assigned by the secure protocol; and

communicating the trusted control message to a second device during the secure session between the first device and the second device for processing by the second device.

2. The method of claim 1 further comprising, storing the trusted control message in secure cache of the first device until the secure session is successfully established.

3. The method of claim 2 further comprising, collecting other trusted control messages for other detected events with the trusted control message in the secure cache until the secure session is successfully established.

4. The method of claim 1 , wherein defining further includes using the secure protocol to define the event in a normalized data format associated with the trusted control message.

5. The method of claim 4 , wherein defining using the secure protocol to assign an identifier to the trusted control message, wherein the identifier is associated with the first device.

6. The method of claim 5 , wherein defining further includes using the secure protocol to assign a message type to the trusted control message, wherein the message type distinguishes the trusted control message from other messages having other message types passed when the secure session is successfully established.

7. The method of claim 1 , wherein communicating further includes preventing the trusted control message from being communication from the first device when the secure session is terminated before the trusted control message could be sent to the second device.

8. The method of claim 1 , wherein communicating further includes identifying the trusted control message as a particular message that the second device is to forward to a third device during a second secure session between the second device and the third device.

9. The method of claim 8 , wherein identifying further includes recognizing the third device as a centralized server that manages: the first device, the terminal device, and the second device.

10. A method, comprising:

passing a trusted control message from a first device to a second device during a secure session between the first device and the second device, wherein passing further includes passing the trusted control message as an encrypted communication that includes at least some data that is relevant to security threat data and that is gathered upon detecting a particular event for at least one operation processed on the first device, wherein the first device is a peripheral device integrated into a terminal device, and wherein detecting further includes detecting the particular event as being associated with the security threat data detected on the first device with the at least one operation processed within the first device, and wherein the security threat data being detected as one of: a secure access request made from the first device as the at least one operation, a resource installation request made from the first device as the at least one operation, a resource deactivation request made from the first device as the at least one operation, a monitoring activity detected on the first device as the at least one operation, a storage exception occurring on the first device as the at least one operation, and an invalid operation request made from the first device as the at least one operation, and wherein passing further includes using a secure protocol to assign a unique message number to the trusted control message, wherein the unique message number includes a unique session identifier for the secure session and a unique number representing the trusted control message relative to other messages passed during the secure session having other message numbers assigned by the secure protocol;

validating, by the second device, the trusted control message; and

determining, by the second device, whether to process take an action associated with the trusted control message or whether to forward the trusted control message to a third device during a second secure session between the second device and the third device for the third device to process.

11. The method of claim 10 , wherein passing further includes using the secure protocol to pass the trusted control message during the secure session.

12. The method of claim 10 , wherein passing further includes passing the trusted control message as a command that is to be executed on the second device or the third device as the action.

13. The method of claim 10 , wherein passing further includes passing the trusted control message as an event that is to be propagated up through a network from a Secure Input/Output Module (SIOM) that is the first device to a centralized management server that is the second device.

14. The method of claim 10 , wherein validating further includes using the secure protocol associated with the first secure session and the second secure session to validate the trusted control message.

15. The method of claim 10 , wherein determining further includes decrypting the trusted control message to determine whether to take the action on the second device or whether to forward the trusted control message to the third device.

16. A system comprising:

a terminal device;

a Secure Input/Output Module (SIOM) integrated into the terminal device and configured and adapted to: i) establish a first secure session with a centralized management server, ii) establish a second secure session with a peripheral device, and iii) determine whether to: a) pass a trusted control message to one of: the centralized management server during the first secure session and the peripheral device during the second secure session and use a secure protocol to assign a unique message number to the trusted control message, wherein the unique message number includes a unique session identifier for both the first secure session and the second secure session and a unique number representing the trusted control message relative to other messages passed during the first secure session and the second secure session having other message numbers assigned by the secure protocol, and b) process an action on the SIOM defined by the trusted control message and received by the SIOM during one of: the first secure session and the second secure session, wherein the trusted control message is formulated as an encrypted communication having at least some data gathered for a particular event that is relevant to security threat data and that was detected as the particular event when a particular operation was processed by the peripheral device, and wherein detecting the particular event is detected as being associated with the security threat data gathered on the peripheral device with the particular operation processed within the peripheral device, and wherein the security threat data being detected as one of: a secure access request made from the peripheral device as the particular operation, a resource installation request made from the peripheral device as the particular operation, a resource deactivation request made from the peripheral device as the particular operation, a monitoring activity detected on the peripheral device as the particular operation, a storage exception occurring on the peripheral device as the particular operation, and an invalid operation request made from the peripheral device as the particular operation.

17. The system of claim 16 further comprising: the peripheral device integrated into the terminal device and configured and adapted to one or more of: i) pass the trusted control message to the SIOM during the second secure session and ii) receive the trusted control message from the SIOM during the second secure session.

18. The system of claim 16 further comprising: the centralized management server configured and adapted to one or more of: i) pass the trusted control message to the SIOM during the first secure session and ii) receive the trusted control message from the SIOM during the first secure session.