Software trade secret expert witnesses for misappropriation, reasonable measures, access, and independent development. Source code review and testimony.
We help courts and counsel prove or disprove misappropriation in software trade secret disputes. Cyberonix analyzes how alleged secrets are defined, protected, accessed, and used—linking allegations to code‑level behavior and engineering facts. We support matters under state law and the Defend Trade Secrets Act (DTSA).
Notable Result
Summary: $105 million jury verdict (E.D. of Mich., Southern Division, Oct. 26, 2022)
- Cyberonix was retained by Versata Software to assess whether Ford misappropriated its trade secrets. The jury concluded that Ford misappropriated Versata’s trade secrets and awarded approximately $105 million in damages.
Common Software Trade Secret Scenarios
Trade secret disputes often arise in predictable engineering fact patterns, including:
- Departing employees or teams moving to competitors and disputes about reuse of code, designs, or know-how
- Contractor/vendor development relationships and disagreements about ownership, reuse, and confidentiality
- Partnership or joint-development breakups involving shared repositories, shared infrastructure, or shared roadmaps
- Competing products with similar architecture, UX flows, APIs, data models, or backend pipelines
- Alleged reuse of internal tools (build systems, CI/CD workflows, testing harnesses, or deployment automation)
- Disputes involving ML/AI pipelines (feature engineering, training workflows, evaluation harnesses, model-serving systems) where the “secret” is embedded in implementation details
Why Cyberonix for Trade Secret Litigation
- Software‑only focus: We specialize in software and software‑intensive systems, e.g., mobile, web, cloud, databases, AI, and software security
- Code‑level proof: Source code review, build artifacts, logs, and version history to test access, use, and independent development
- Courtroom‑ready experts: Our expert bench combines academic credentials and federal court experience
- Protective‑order discipline: Secure workflows aligned to typical POs for code and confidential materials
What We Do
- Identify alleged trade secrets and separate them from general skills/knowledge and public domain material
- Reasonable measures analysis (NDA/PO practice, repository controls, CI/CD access, logging)
- Access and opportunity assessment (who could see what, when, and how)
- Use/disclosure/derivation analysis mapped to source code and build artifacts.
- Independent development and reverse engineering activity analyses
- Public knowledge/prior‑art sweeps, targeted at claims of secrecy
- Artifact analysis (commits, diffs, logs, emails, Slack exports; reproducible environments)
- Deliverables: technical memoranda, claim/element charts, demonstratives, expert reports, deposition, and trial testimony
Trade Secret Issues We Address
Defining the Alleged Trade Secrets with Engineering Specificity
We help counsel and fact-finders distinguish alleged secrets from general skills/knowledge, common engineering patterns, and public-domain implementations, so the case focuses on the specific technical information at issue.
Reasonable Measures in Modern Software Organizations
We evaluate “reasonable measures” from a practical software perspective, including access controls, repository permissions, identity management, logging/auditing, offboarding practices, and confidentiality controls around sensitive technical materials.
Access and Opportunity
We reconstruct who could access what, when, and through which systems, connecting policy to real-world access paths (e.g., repo permissions, build systems, shared drives, cloud accounts, and audit trails).
Use, Disclosure, and Derivation
We analyze whether and how alleged trade secret information was used or disclosed, mapping allegations to code-level behavior, build artifacts, design decisions, and product functionality.
Independent Development and Clean-Room Workflows
We test whether similar outcomes can be explained by independent development, including timeline analysis, provenance review, and evidence of parallel engineering workstreams.
Reverse Engineering and Public Knowledge
Where relevant, we assess whether claimed “secret” functionality could have been derived through legitimate reverse engineering, public documentation, standards, or commonly available implementations.
Technical Support for Damages Theories
When needed, we provide technical input on topics such as head-start timeframes, engineering effort, and what functionality is attributable to the alleged secrets (often in coordination with damages experts, as appropriate).
Evidence We Commonly Analyze
Depending on the posture of the matter and what is available in discovery, our analyses may involve:
- Version control history (commits, diffs, merges, tags, branches) and related metadata (authorship, timestamps, code review notes)
- Repository and system access records (permissions, access logs, audit trails, credential events)
- Build and release artifacts (build configs, dependency manifests, CI/CD logs, release binaries, container images)
- Technical documentation (design docs, specs, ADRs, architecture diagrams, internal wikis, runbooks)
- Runtime evidence (logs, telemetry, network traces, reproducible test runs) where behavior matters
- Development workflow artifacts (issue trackers, test plans/results, incident reports, onboarding/offboarding records)
- Communications and file-transfer artifacts relevant to access and disclosure (as applicable)
Repository Forensics and Code Lineage Analysis
In software trade secret disputes, the technical record often lives in repository history and build pipelines, not just the final code snapshot. When appropriate, we:
- Reconstruct a defensible technical timeline using version history, development artifacts, and system logs
- Identify where similarity is meaningful versus where common patterns, frameworks, or requirements explain overlap
- Analyze provenance signals: file histories, refactors, module boundaries, naming patterns, unique constants, and architectural decisions
- Evaluate “derivation” theories by comparing what was allegedly known, when it was known, and what changed in the accused codebase over time
- Test independent development narratives by validating parallel work evidence (design docs, tickets, commits, tests, releases) and identifying inconsistencies
When to Bring Us In
- Pre-suit and early case assessment
- TRO / preliminary injunction support and expedited discovery
- Trade secret identification and “reasonable measures” evaluation
- Fact discovery: access, opportunity, and technical timeline reconstruction
- Expert discovery: reports, rebuttal, deposition preparation
- Pre-trial and trial: demonstratives, tutorials, and testimony support
Engagement Process
- Scope call + conflict check
- Protective order planning and secure evidence intake
- Early assessment: alleged secrets, pleadings, key systems, and available artifacts
- Deep analysis: repositories, builds, documents, and behavior testing (as appropriate)
- Synthesis: timelines, access maps, derivation narratives, and demonstratives
- Expert deliverables: declarations, reports, and rebuttal analysis
- Deposition and trial preparation + testimony
- Post-hearing/trial support: follow-on analysis and technical consulting
Selected Trade Secret Cases
Re: FormsNet LLC v. Glide Labs Inc.
- Retaining party: Glide Labs Inc.
- Venue: Superior Court of the State of California, County of San Francisco
- Case No.: CGC-21-588988
- Counsel: Keker, Van Nest & Peters LLP
- Nature of suit: Intellectual Property – Trade Secret
Financial Information Technologies Inc. v. IControl Systems, USA, LLC
- Retaining party: IControl Systems
- Venue: Middle District of Florida, Tampa Division
- Case No.: 8:17-cv-190-T-23MAP
- Counsel: Rocke McLean Sbar
- Nature of suit: Intellectual Property – Trade Secret
Ford Motor Company v. Versata Software, Inc., F/K/A Trilogy Software, Inc.
- Retaining party: Versata Software, Inc., F/K/A Trilogy Software, Inc.
- Venue: Eastern District of Michigan, Southern Division
- Case No.: 15-10628-MFL-EAS (consolidated with 15-11624-MFL-EAS)
- Counsel: Winston and Strawn LLP; Ahmad, Zavitsanos, Anaipakos, Alavi, and Mensing P.C.
- Nature of suit: Intellectual Property – Patent and Trade Secret
Financial Information Technologies Inc. v. IControl Systems, USA, LLC
- Retaining party: IControl Systems
- Venue: Middle District of Florida, Tampa Division
- Case No.: 8:17-cv-190-T-23MAP
- Counsel: Rocke McLean Sbar
- Nature of suit: Intellectual Property – Trade Secret
Related Expertise
Trade secret matters often overlap with:
- Source Code Review
- Software Security
- Cloud Computing
- Software Engineering
- Database and Storage
- Artificial Intelligence
- Internet and Web
- Mobile Software
See, also, Copyright and Breach of Contract practice areas.
We Are Cyberonix
At Cyberonix, our software expert witnesses offer academically grounded, industry-tested insights in complex software disputes. We support litigation involving patents, trade secrets, copyright, breach of contract, and class actions through source code analysis, technical reporting, and expert testimony.
