Download
eda consortium anti piracy committee update n.
Skip this Video
Loading SlideShow in 5 Seconds..
EDA Consortium Anti-Piracy Committee Update PowerPoint Presentation
Download Presentation
EDA Consortium Anti-Piracy Committee Update

EDA Consortium Anti-Piracy Committee Update

140 Views Download Presentation
Download Presentation

EDA Consortium Anti-Piracy Committee Update

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. EDA ConsortiumAnti-Piracy Committee Update Dave Graubart EDAC Anti-Piracy Committee Chair Director, Software Engineering, Synopsys September 8, 2010

  2. Agenda Why EDA Piracy is important State of EDA Piracy today Piracy threats EDAC updates

  3. Why EDA Piracy Is Important

  4. How It Should Work (materials courtesy of AWR Corp) EDA 1 EDA 2 Product X Engineer cost $1.00 EDA cost $0.10 Product X++ Engineer cost $2.00 EDA cost $0.20 Function X++ $2.20 Function X $1.10 EDA customer selects “Best” (price for performance)

  5. How It Actually Works EDA 1 Pirate Product X Engineer cost $1.00 EDA cost $0.10 Product X Engineer cost $1.00 EDA cost $0.00 Same Function Function X $1.00 Function X $1.10 Pirate does not need to differentiate their technology because they know they can win on price! EDA customer selects “Best” (price wins)

  6. The Cycle for EDA Vendor Pirate EDA 1 EDA customer picks cheapest Having won sale, increases headcount Having lost sale, reduces headcount Diminishing returns Decreases EDA investment No EDA investment

  7. The Cycle for EDA Customer Competitor using pirated EDA SW Honest Customer Consumer picks cheapest Having won sale, increases headcount Having lost sale, reduces headcount Diminishing returns Decreases EDA spending No EDA spending

  8. Prediction for EDA If EDA industry doesn’t secure a level playing field for our customers, our industries will suffer greatly

  9. Required Changes EDA industry and EDA customers must not tolerate piracy • Ignoring it is not an option • Tolerating it is not an option • Succumbing to it is not an option

  10. State of EDA Piracy Today

  11. State of Piracy Today Data is scarce and varies Estimates range from <20% to >40% of EDA software use is illegal Cracked versions of almost everything are available Unknown revenue impact, but most agree it’s significant to both EDA suppliers and its honest customers

  12. Stages of Piracy Acknowledgement Denial • Everyone thinks it’s the other guys problem Anger • I can’t believe they are doing that Frustration • Everything we try to do to harden our software fails Acceptance • Implement systems to turn users of pirated software into customers

  13. Piracy Threats

  14. How is EDA software pirated? Counterfeit licenses and key generator Binary tampering to bypass or modify license code Cloning hostid to reuse legit software and license file many times While any are left unaddressed, piracy continues

  15. The Weakest Link will be Exploited

  16. Counterfeit Licenses Modern licenses use strong encryption such as FNP’s TRL Most EDA companies use this today Software that doesn’t require TRL is vulnerable Slow impact as users of counterfeit licenses stay on old unprotected versions Improvements have no impact on honest customers

  17. Binary Tampering Our biggest known problem today Military-strength hardening is now available to commercial market Some deployment and plans for deployment of hardening is occurring Slow impact as users of cracked software stay on old unprotected versions Improvements have no impact on honest customers Tamper detection is also possible

  18. Cloning Hostids MAC Address and Solaris hostid are weak Several possible approaches under study, little changed from a year ago Fast impact as the old licenses expire Improvements do have impact on honest customers

  19. Cloning Hostids Consistency requirements understood • We can’t expect customers to use a different hostid per vendor Up-time/DR requirements understood • Otherwise, easy to change to strong unclonable hostid Lead time requirements understood • Both vendors and customers will need time

  20. EDAC Updates

  21. EDAC Updates Technical committee identified options to combat binary tampering and hostid cloning But – connection to business priorities needed to be stronger Recent and active business committee involvement to complement technical committee

  22. EDAC Updates Validating Anti-tamper approaches Hostid action delayed from what predicted last year • Technology moving quickly • Time to get major EDA companies talking to each other • Evolving compute environments; i.e. VMs, Cloud • Involvement by new business committee • Expecting decisions late this year

  23. Summary Piracy is a big problem hurting EDA vendors and customers alike Several threats are known and all need to be addressed EDAC sees stability in addressing 2 of 3 threats with plans for last threat emerging soon

  24. Thank you Send any thoughts to graubart@synopsys.com