Trusted Computing: The COTS Perspective Series
When examining security and Trusted Computing, system-level protection is not simply the sum of its parts. While the individual modules, operating system, and boot software all are important, system security is also not an additive process; it can’t simply be bolted-on to make the system secure.
A systems designer must look at all system elements individually and understand how they work together. If a single discrete element of the system is insecure, it is not possible for the designer to claim confidently that the entire system is secure. You need to know how each system element integrates with the rest, what interfaces are available to those elements, and how each element communicates with the other parts of the system.
The systems designer must make every effort to eliminate any risk of inadvertently providing an insecure port of entry into the system that makes it vulnerable to malicious attack.
Login and download the white paper to learn more.
Steve Edwards
Director and Technical Fellow
Steve has over 25 years of experience in the embedded system industry. He leads Curtiss-Wright Defense Solutions’ efforts in addressing physical and cyber security on their COTS products and represents the company in defense related security conferences. Steve has worked collaboratively in several standard bodies, including a time chairing the VITA 65 OpenVPX, and as lead for the Sensor Open Systems Architecture (SOSA) Security Subcommittee. Steve lead the design of Curtiss-Wright’s first rugged multiprocessor and FPGA products and was involved in the architecture, management, and evangelization of the industry’s first VPX products. He has a Bachelor of Science in Electrical Engineering from Rutgers University.
