MX in the news: Testing Simulation. Stolen! Engineering IP Theft.

Testing and Simulation Review put a sharp spotlight on a problem that many engineering teams understand privately but still struggle to control in practice: engineering IP theft through ordinary file exchange. Sensitive design data is not always lost through spectacular breaches or sophisticated intrusion. More often, it leaks through routine process gaps, hurried decisions, weak handoff discipline, and too many tools doing the same job badly.

That is what makes the issue serious. Aerospace and automotive programmes depend on constant collaboration across suppliers, specialist vendors, test partners, and internal teams. Design files, calibration data, manufacturing evidence, and commercial documentation move quickly across organisations and regions. Once those exchanges rely on email attachments, public links, consumer-style sharing habits, or scattered inbox approvals, the margin for error widens fast.

My MX Data is built around a stricter model: secure file transfer for business through named user access, full audit trails, configurable expiry, and a quantum secure patented methodology designed to reduce exposure without turning collaboration into friction. The same control problem sits at the heart of Defending the Blueprint: Strategies to Thwart Engineering IP Theft, where the real weakness is rarely the file alone. It is the loose workflow around it.

Why engineering IP is so vulnerable during ordinary exchange

The most valuable engineering data rarely stays in one environment. It moves through design reviews, simulation cycles, external testing, supplier collaboration, procurement workflows, and quality investigations. That movement is necessary, but it also creates the exact conditions where control weakens. Files are copied, forwarded, downloaded, reuploaded, renamed, or left sitting in places that were convenient at the time but difficult to govern later.

The target list is obvious to anyone who has worked around product development or advanced manufacturing.

• Design artifacts: CAD assemblies, CAE outputs, simulation packs, wind tunnel results, battery strategies, ECU maps, and development notes.
• Manufacturing evidence: tooling parameters, PPAP submissions, defect imagery, supplier concessions, process validations, and production change records.
• Commercial files: RFQs, pricing models, contract drafts, programme schedules, sourcing decisions, and test reports.

Now add the real supply chain context. Your source material notes that the average company shares files with more than 800 online domains, that 9.2 percent of externally shared documents contain sensitive information, and that the average enterprise uses 57 file sharing services. Once file exchange is spread across that many destinations and tools, leaks often begin with something painfully ordinary: the wrong recipient, weak link control, stale access, or a file sent through the wrong channel because it felt faster at the time.

Why ordinary encryption is no longer the whole answer

Encryption still matters. Any serious file sharing model needs it. But long-life engineering data now sits inside a wider risk window. Designs created today may still have technical, commercial, or strategic value years from now. That means some engineering programmes are exposed not just to current theft, but to future decryption risk.

This is where the idea of the quantum windowDesigns created today may still be valuable years from now, when future attackers may have stronger decryption capabilities. becomes relevant. Adoption of quantum-resistant controls in the wild is still extremely early, with one source in your pack pointing to roughly 0.029 percent in some OpenSSH contexts. That matters because attackers do not need to exploit stolen data immediately to benefit from taking it.

So the question becomes broader than encryption alone. How is the file structured. How is access constrained. How much can a bad actor actually recover if they intercept a transfer. Can you prove who accessed what, when, and under which conditions. That is why MX’s response is architectural, not cosmetic.

The Anonymise, Shard, Restore model breaks content into separate shards stripped of identifying context, routes them independently, and restores them only for the authorised destination. Paired with named user access, full activity logging, and controlled collaboration, it creates a much less forgiving environment for theft and misuse. MX describes this as a quantum secure patented methodology intended to strengthen resilience while keeping daily engineering work usable. The longer threat horizon behind that model is the same one explored in Quantum-Proof Encryption and in the harvest-later risk discussed in MX in the News: The ‘Harvest Now, Decrypt Later’ Problem.

Where engineering teams usually lose control

IP theft is often discussed like a pure cyber problem, but in live programmes it is just as often an operating model problem. The most common weak points are familiar.

• Too many sharing tools: teams bounce between email, network folders, public links, personal cloud drives, and chat attachments depending on urgency.
• Weak share scope: recipients get more access than they need, or keep it longer than the project requires.
• Poor version control: suppliers or review teams work from stale files while the latest version sits somewhere else.
• Unclear approvals: decisions live in inboxes or chat threads instead of staying tied to the actual transfer.
• Workflow workarounds: when secure tools feel slow or rigid, users route around them.

That last point matters. Rigid tools do not eliminate risk. They often relocate it. If the approved process is frustrating enough, people will reach for whatever moves the file fastest. That is why speed and control need to coexist, which is exactly the operational problem addressed in Balancing Speed and Security.

Five moves that shrink your attack surface this quarter

These are practical steps programme teams can implement without redesigning the entire operating model.

What better control looks like in practice

Strong protection does not mean slowing programmes to a crawl. It means making secure behaviour the standard route instead of the painful route. A good system gives teams one place to send, review, update, revoke, and prove. It reduces the temptation to improvise because the governed workflow is already fast enough for live work.

That is also why context matters. File exchange is rarely just about the file. It includes approval, discussion, exceptions, timing, and evidence. When those elements live in separate places, traceability weakens. When they stay attached to the transfer, teams work with more confidence and less noise. That broader collaboration problem is exactly what sits underneath Data Sharing Services and Essentials for Secure Collaboration.

The real lesson from the interview

The Testing and Simulation Review conversation matters because it refuses to treat engineering IP theft as a distant or abstract threat. It places the problem where it actually lives, inside daily exchange habits. Valuable data leaves secure environments all the time. If that movement is not governed by named access, clear evidence, controlled sharing scope, and a more resilient architecture, the organisation is left hoping that ordinary habits will somehow produce secure outcomes.

Hope is not a control. A defined lane is. My MX Data is built to provide that lane, combining named users, auditability, version control, collaboration in context, and a security model intended to reduce present and future exposure without making engineering work heavier than it needs to be.