EDA in the Cloud: OneSpin says your design is secure
Several companies have tried to move EDA into the cloud, and for very good reasons. EDA tools are expensive and smaller companies may feel that they do not get enough utilization from a tool to make the buy price worth it. They require small amounts of tool usage during certain parts of their flow and the rest of the time, it sits there idle even though they continue to pay maintenance on it. Larger companies also have problems although somewhat different. At peak times they may like to have many more licenses available, but cannot justify it based on average utilization rates. The cloud promises to make any number of copies of an EDA tool available on an as-needed basis. The demand is there, but there has always been that large bogey – the security of the design. Companies do not like that they have to upload their design onto a server, that is who-knows-where, and unclear how well the security is set up. We hear almost daily about data being stolen from one company or another, and many of these are large companies, who presumably take their security somewhat seriously. There are probable many more cases of data theft that go unreported or even undetected.
To read the full article, click here
Related Semiconductor IP
- SHA-256 Secure Hash Algorithm IP Core
- EdDSA Curve25519 signature generation engine
- DeWarp IP
- 6-bit, 12 GSPS Flash ADC - GlobalFoundries 22nm
- LunaNet AFS LDPC Encoder and Decoder IP Core
Related Blogs
- What does Amazon's multiday cloud outage mean for EDA cloud services?
- Amazon's cloud service crash permanently lost data. Think this has implications for EDA?
- Scaling EDA in the Cloud
- Arm's Cloud EDA Success: Two Paths to Greater Value
Latest Blogs
- Area, Pipelining, Integration: A Comparison of SHA-2 and SHA-3 for embedded Systems.
- Why Your Next Smartphone Needs Micro-Cooling
- Teaching AI Agents to Speak Hardware
- SOCAMM: Modernizing Data Center Memory with LPDDR6/5X
- Bridging the Gap: Why eFPGA Integration is a Managed Reality, Not a Schedule Risk