How to Securely Share a SolidWorks 3D Model

The belief that causes the problem

A prospect once told me: "we do not upload our 3D models to the cloud, we keep them on our servers instead, for better security."

I came to Sibe from cybersecurity, and I have met that belief many times. Data you can see feels safe. It is not the same thing as data that is safe, and plenty of people have learned the difference when their files turned up somewhere they should not have been.

The real tension is simpler than cloud versus on-premise. Data nobody can reach is perfectly secure and completely useless. Data that creates value has to be shared. The question is how to share it without multiplying the number of copies in existence.

Why you have to share at all

Very little product development happens inside one building. At some point you need to:

• Have a manufacturer assess a design for cost and feasibility
• Work with a partner on part design
• Hand modeling work to an outside contractor
• Show the product to marketing, or to a client, before it is finished

Each of those is a different risk, and each has a different right answer.

The four traditional routes, and how each one leaks

Email

The first thing everyone reaches for, and reasonable for something small and urgent. The exposure is that your mail system, or your partner's, becomes the weak point — and organizations with real security budgets still lose mailboxes.

Much of the damage needs no attacker at all. Someone forwards work mail to a personal address so they can reply from the road, and the attachment goes with it.

If you use it: control forwarding at the mail-system level, and put the effort into awareness — people who understand the consequences make fewer of these decisions.

File sharing services

Dropbox, Google Drive and the rest are genuinely convenient for large files and several recipients. That convenience is exactly what creates shadow IT: files shared outside anything IT can see, and therefore outside any retention or permission policy they can enforce.

If you use it: mandate one approved service so policy can actually be applied; set expiry dates, because a design draft does not need to sit on the web forever; and configure explicit access rather than "anyone with the link" — links travel further than the thread they started in.

Drop folders

Similar to file sharing, except the infrastructure is yours. The trade-off is that you are granting people outside your organization rights inside your environment.

If you use it: assign permissions per person, not per group, and re-check them on a schedule. If you grant write access anywhere, have malware and ransomware protection behind it — what you stand to lose is not only the models you meant to share.

Portable drives

Dated, but still in use. Drives and laptops are lost by the thousand every year, including by organizations whose entire job is security.

If you use it: encrypted drives with real keys, and a removable-media policy that disables ports for the roles that do not need them.

The problem all four share

Every one of them works by making a copy and handing it over.

Once the copy exists you have doubled the surface you are defending, and you are now defending the half you do not control. Every mitigation above is really an attempt to manage a copy you should not have created.

Start with what the reviewer actually needs

Before choosing how to share, decide what the other person has to do:

1. Look at the product. Managers, directors, marketing, clients. They need to see it and say what they think. They do not need geometry
2. Review the engineering. A contract engineer, a partner, another department. They need to inspect properly — measure, section, check clearances — but often not to edit
3. Quote or build it. A production facility needs manufacturable data, which usually does mean a real file, in a neutral format, under an NDA

Only the third genuinely requires handing over data. The first two are viewing problems that get solved as file-transfer problems out of habit.

Then weigh what a leak would actually cost

Does a competitor reproduce the product? Does someone file a patent first? Does the design appear online before launch? Does a customer see something unfinished and draw conclusions?

The answers differ per project, and they should decide how much friction is worth accepting.

And train the people

Most breaches come from someone not knowing, not from someone deciding. Technology alone does not fix that.

• Make sure people understand what the sensitive data is and why it matters
• Put NDAs in place along the supply chain, so anyone touching your designs knows where the liability sits

Share a view, not a file

This is the part that changes the arithmetic. A share link gives the reviewer the model in a browser — rotate, zoom, section, measure, comment — without the source file leaving your workspace.

• No copy is created. The reviewer sees the geometry; they do not receive it
• You decide who gets what. Some people need the source files. Most need to look and comment
• Access is revocable. Turn the link off and the view is gone — which is not true of an attachment
• Nothing to install. No CAD license, no account, so the security conversation never becomes a software rollout
• Every version is recorded, so you know which revision each person saw

On the engineering side, files stay under version control: engineers check them in and out directly in SolidWorks, and assembly references resolve without repair.

The short version

• Sharing a file and sharing a view are different acts with different risk
• Send files only to the people who must have them, in the format they need, under an NDA
• Everyone else gets a link, which can be withdrawn
• Whatever route you choose, the people using it decide whether it holds

No servers, no VPNs, no admin hassles.

Book a free 20-minute demo.