ÁùºÏ²ÊÖ±²¥¿ª½±

In the beginning of electronic data management, data was relatively secure. After all, you owned all the hardware. The data servers were on premise. The person sitting in front of the computer was your trusted employee. And of course, you hired only good people. You vetted them directly, and you paid them well. They had no reason to act in bad faith.

Today, the world of data has changed. Security breaches that were once unthinkable are happening all the time, and it is important to secure not only the software but the hardware, too. Our data landscape has evolved to be vast, connected, and interdependent. People you don¡¯t know¡ªwell beyond your corporate walls¡ªhave an impact on your security.

With cloud computing, your job is just one of a great number of jobs running on massive servers in hyperscale data centers, likely located far away from your core operations. These data centers have an abundance of virtual machines running jobs from an untold number of different clients, all using different devices. Within the data center, you are allocated a specific amount of memory and number of processor cores so you can accomplish your jobs and tasks.

Because you don¡¯t directly control these operations, you don¡¯t know if someone inside the data center is rolling up to a server with an oscilloscope and logic analyzer to probe ¡°your¡± server¡¯s internal signals. You don¡¯t know that a data center employee doesn¡¯t also work for a foreign government. You don¡¯t know if they¡¯ve been tasked to snoop around your hardware and the virtual machines.

This is why you need hardware encryption inside virtual servers¡ªthe ability to communicate between virtual machine and hardware using a secure encryption key exchange where a third party, even one who owns, manages, and runs the data center day-to-day, doesn¡¯t have access to the encryption itself.

is a new framework and architecture to secure I/O virtualization, which was introduced by way of an ECN that makes it part of the most recent PCI Express? (PCIe?) 6.0 specification. Even though the PCIe 6.0 specification introduced the new 64GT/s signaling speed, TDISP can be utilized at any speed. The standardized interface framework defines how to secure the interconnect between the virtual machine host and the device, regardless of where your data center resides or who has access to the servers inside of it.

Standardized Software Framework to Achieve Secure Interfaces

Here¡¯s the important point: Each of your devices needs to perform functions and to have encryption to exchange keys with your virtual machines in the data center. But this process can be complex and problematic. For instance, Company A might be a CPU vendor and the virtual machine hardware in the data center already knows the CPU. In this case, there¡¯s no need for an interface framework for security because the virtual machine already knows the hardware encryption for that CPU. But when the virtual server is shared, as is prevalent in today¡¯s cloud computing environment, the devices plug in not only Company A, but also a variety of devices from Companies B and C, and perhaps others. In these cases, you would need to teach the software about each device to ensure the proper encryption.

If you wanted to ensure encryption in the past, it had to be done in a proprietary manner. Most often, organizations did not do this well. Because of these inefficiencies, it begs the question: instead of having unique interfaces for each of your devices, how can you standardize the ability to protect interfaces from attack?

TDISP Enables Secure Key Exchange

Key management is the primary role of TDISP. It has the ability to turn on and off the encryption, performing like a control panel, so you can refresh keys for the next hour, or the next 10 minutes, or any other timeframe. The TDISP framework standardizes the process and manages the entire key exchange, eliminating the need to build unique interfaces for each different device.

On the hardware side, once the connection is negotiated and the link secured, if there is register manipulation outside of TDISP, you can identify the connection as no longer secure. With TDISP you can detect the attempt to intercept your communications, enabling you to flag the software, letting it know that something is wrong so that it resecures the link before the breach ever occurs.

TDISP is a state-of-the-art framework, a part of your overarching security strategy that will standardize your approach to IO interconnect security, mitigating attacks before they happen. You may think this kind of security is for the NSA-level targets and not applicable for everyday use cases. Perhaps you aren¡¯t operating in the national security space and your product isn¡¯t particularly security sensitive. However, the fact is, any breach getting between you and your end user is a threat with potential full-circ