Preventing IP theft with the MSC8144EC DSP
By Dahan O. Author, Levenglick D.
July 30, 2007 -- dspdesignline.com
System and software companies spend billions of dollars developing confidential software IP to give their solution a unique edge. Unfortunately, a deployed system leaves this IP out in the open, accessible to any hacker and ripe for the malicious picking. Code can be stolen or the entire system cloned, either by eavesdropping on communication lines used to download IP to the site, or by going to a deployment site and downloading code directly from a system's storage. This can, and has in the past, lead to lawsuits and loss of income.
There are two main methods for protecting against IP theft. One can safeguard the code by physically locking the storage or one can virtually lock the code by encryption. The encryption solution is preferable, as encryption locks are harder to pick than physical ones. In order to allow encrypted code to run a standard machine, yet keep the code encrypted when it is vulnerable to attack (i.e., in form accessible to a hacker), the hardware has to allow the decryption of code before its execution as well as protect the cleartext code in storage. This problem has resulted in hardware solutions in various products for various markets. In the DSP market, the MSC8144EC, through an innovative combination of hardware and embedded software, is the first high end DSP to provide a software security solution. This article describes this hardware and software support for software security, and maps the security threats that this solution addresses.
July 30, 2007 -- dspdesignline.com
System and software companies spend billions of dollars developing confidential software IP to give their solution a unique edge. Unfortunately, a deployed system leaves this IP out in the open, accessible to any hacker and ripe for the malicious picking. Code can be stolen or the entire system cloned, either by eavesdropping on communication lines used to download IP to the site, or by going to a deployment site and downloading code directly from a system's storage. This can, and has in the past, lead to lawsuits and loss of income.
There are two main methods for protecting against IP theft. One can safeguard the code by physically locking the storage or one can virtually lock the code by encryption. The encryption solution is preferable, as encryption locks are harder to pick than physical ones. In order to allow encrypted code to run a standard machine, yet keep the code encrypted when it is vulnerable to attack (i.e., in form accessible to a hacker), the hardware has to allow the decryption of code before its execution as well as protect the cleartext code in storage. This problem has resulted in hardware solutions in various products for various markets. In the DSP market, the MSC8144EC, through an innovative combination of hardware and embedded software, is the first high end DSP to provide a software security solution. This article describes this hardware and software support for software security, and maps the security threats that this solution addresses.
To read the full article, click here
Related Semiconductor IP
- Verification IP for C-PHY
- Band-Gap Voltage Reference with dual 2µA Current Source - X-FAB XT018
- 250nA-88μA Current Reference - X-FAB XT018-0.18μm BCD-on-SOI CMOS
- UCIe D2D Adapter & PHY Integrated IP
- Low Dropout (LDO) Regulator
Related Articles
- PCIe IP With Enhanced Security For The Automotive Market
- VLSI Physical Design Methodology for ASIC Development with a Flavor of IP Hardening
- Increasing bandwidth to 128 GB/s with a tailored PCIe 6.0 IP Controller
- Calibrate and Configure your Power Management IC with NVM IP
Latest Articles
- SCENIC: Stream Computation-Enhanced SmartNIC
- Agentic AI-based Coverage Closure for Formal Verification
- Microarchitectural Co-Optimization for Sustained Throughput of RISC-V Multi-Lane Chaining Vector Processors
- RISC-V Functional Safety for Autonomous Automotive Systems: An Analytical Framework and Research Roadmap for ML-Assisted Certification
- Emulation-based System-on-Chip Security Verification: Challenges and Opportunities