Blog · compliance

Cloud PCB design security: five myths, and the handoff the platform answer stops at

Is cloud PCB design secure enough for a controlled project, and what happens to the design package after you press send?

ChinaPCB Editorial 1620 words · 8 min read

The switching signals in this article

  1. 01 File leaves the workspace An ODB++ or Gerber package can be exported in minutes; the platform log records the export, not what the receiving site does with it.
  2. 02 External recipients A contract manufacturer, CAM partner or test house is outside your identity provider, so workspace permissions stop at the shared link.
  3. 03 Multi-site supplier A group certificate or a parent-company audit can sit at a different address from the floor that builds your boards.
  4. 04 No scope in the record A security certificate listed without a site address or certificate number is a question to ask, not a control you can rely on.
  5. 05 Subcontracted CAM Engineering files often travel to a second site before tooling; that hop is invisible in the platform's events log.

A widely republished article answers five cloud-security myths for PCB design teams: that cloud storage is less secure than an on-premises server, that cloud workflows cannot meet strict security requirements, that they cannot satisfy ITAR and EAR, that file access cannot be tracked, and that sharing files means losing control of permissions. The answers are largely correct. Modern platforms offer single sign-on, SAML 2.0, IP allowlists, role-based permissions, workspace isolation, multi-factor authentication and independent SOC 2 Type II attestation. For a distributed engineering team, those controls can be stronger than a shared drive behind a VPN.

All five answers share one boundary condition: they describe what happens inside the platform. The moment a manufacturing package is exported and sent to a supplier, the platform’s guarantees stop travelling with the file. This article takes the five claims as given and follows the file past that boundary, using the public records of 131 PCB factories as the receiving-side evidence.

The five myths, answered inside the platform

MythPlatform answerWhat it does not cover
Cloud storage is less secure than on-premisesDedicated security teams, encrypted transport and sharing links that replace email attachments and USB drives.The supplier's mailbox, file server and CAM workstation after export.
Cloud cannot meet strict requirementsIP allowlisting, RBAC, SSO, SAML 2.0, workspace isolation, MFA and SOC 2 Type II.Whether the receiving factory can show an equally scoped control set.
Cloud cannot comply with ITAR and EARA physically separate US region operated by US persons, with a WAF blocking non-US IPs by default.Access by foreign-national engineers at a supplier, which an IP filter cannot see.
Nobody can see who opened a fileEvent logs with user identity, timestamp and action type, exportable to a SIEM.Downloads, forwards and re-imports that happen outside the workspace.
Sharing files loses permission controlWorkspace- and project-level permissions tied to enterprise identity.Permissions on a package that has already left as a downloadable file.

The distinction is not a criticism of the platform. It is a scope statement. SOC 2 Type II attests to controls at a service organisation over an audit period; it says nothing about the shop floor that receives your Gerbers. A SOC 2 report also has a system boundary and a complement of user entities. If your supplier is not inside that boundary, the report does not describe them.

The same logic applies to export control. Restricting a workspace to US IP ranges reduces one class of risk. It does not answer whether an engineer at a contract manufacturer has opened the package from a permitted network, or whether the technical data has been placed on a server in another jurisdiction. WAF geoblocking is a network control; nationality checks are people controls. One does not stand in for the other.

What actually leaves when you press send

A fabrication package is not a single file. It is a set of artefacts that together describe the product: Gerber or ODB++ layers, drill files, the stackup, copper weights, impedance requirements, the netlist, the bill of materials, panel drawings and often the assembly drawings too. For a multilayer or HDI board, that package can describe more of the product than the schematics alone. The basic build inputs for a quote are already a substantial disclosure.

The export itself is usually logged. What happens next is normally a mix of email, a supplier portal, a shared drive and a CAM engineer’s local machine. At least four perimeters appear after the export:

  1. The transfer channel. A download link with a default expiry is different from a named account on a supplier portal. One creates a file that can be forwarded; the other creates an identity that can be revoked.
  2. The receiving legal entity. The name on a website may be a brand, a sales company or a parent group. The entity that signs the NDA and holds the design files should be the entity named on the business licence and, where relevant, the UL file.
  3. The receiving site. A group can hold a certificate at one address while the order runs at another. Certificate scope is a site question before it is a company question.
  4. The CAM step. Engineering files are frequently passed to a CAM engineer, and on complex work that step can be subcontracted. The platform’s events log has no visibility of that hop.

None of these perimeters is addressed by switching from an on-premises ECAD server to a cloud workspace. Moving the design system changes who administers the first perimeter; it does not create controls at the other three.

What 131 supplier records show about the receiving side

The directory currently publishes 131 factory profiles. Every one carries the same evidence level: public-sources-reviewed. Zero are independently reviewed. That label matters here, because a directory can report what a supplier publishes without claiming to have audited their file-handling practices.

Against that background, four counts are worth carrying into a security review:

  • 17 of 131 profiles list ISO/IEC 27001 in their certification records. Ten of those 17 entries carry a caveat in the record itself: scope not described, an older revision still shown, no certificate number, or certificate images only.
  • 12 of 131 list AS9100. Among the 18 factories tagged for aerospace and defence work, only nine have AS9100 on record.
  • Zero list SOC 2, ITAR or CMMC controls in their certification records.
  • Zero capability lines across the profiles describe an encrypted file-transfer channel, VPN, controlled data room or restricted engineering-file access.

These are gaps in the public record. They are not findings about a factory’s internal controls, and they do not establish that a supplier mishandles design data. They do establish that a buyer cannot substitute a directory listing for a direct question. A security questionnaire answered in writing is stronger evidence than a logo gallery either way.

The caveats are specific enough to be useful. ATS in Shanghai lists ISO/IEC 27001:2022, with the information-security scope not described. Delton’s Huangshi record shows the 2013 revision still on its website while an ESG report places the current system across Guangzhou, Huangshi and Dongguan. JLC lists ISO/IEC 27001:2022 for information security. Kaifa lists ISO 27001 together with ISO 22301 for business continuity. WUS lists both ISO 22301 and ISO/IEC 27001. In each case the useful follow-up is the same: ask for the certificate number, the named site, the scope statement and the current surveillance date.

This is the same brand-versus-entity distinction the industries cross-table exposes for sector certificates: a group-level claim does not automatically travel to the floor that builds your order.

Carrying an audit trail across the boundary

A workspace log that ends at export is still useful. It becomes one third of a trail rather than the whole trail. The other two parts are cheap to produce and rarely requested together:

  • A transfer manifest for each release: package name, version, file hash, date, recipient entity and the person who authorised the send. A hash matters because two packages called rev_bGerber.zip can contain different layers, and a filename is not a version.
  • A receiving acknowledgement from the named entity: who stored the files, at which site, whether CAM is in-house, and how superseded revisions and sample boards are handled. One page signed by both sides is enough.

Ask for these alongside the RFQ checklist rather than after the deposit. The factory verification guide covers the business-licence and UL-file checks that identify the receiving entity. Put the two reviews in the same document and you get a single record that joins identity, site and file custody.

For an export-controlled programme, add one more line: the nationality and role of every person who can open the package, including at suppliers. A WAF cannot answer that, and a supplier outside your identity provider will not appear in your SSO logs.

When GovCloud-class controls earn their cost

A purpose-built sovereign region makes sense when the data classification warrants it: controlled technical data, a requirement that operations and support be performed only by US persons, or external collaborators who should never see the workspace at all. In those cases the geographic and personnel restrictions are the product, not an extra.

For a commercial board with ordinary confidentiality requirements, the higher-yield work is usually at the handoff: name the receiving entity, verify the site behind the certificate, restrict the transfer channel, and keep a manifest for every release. A restricted cloud region plus an uncontrolled email thread is a weaker combination than a standard commercial workspace plus a disciplined transfer process.

The decision should be made from the file’s classification, not from the platform’s feature list. Write down what the package contains, who may open it, which sites may store it and how long copies survive. Then check which of those four statements the platform enforces and which need a contract. The answer will usually split across both.

A five-line check for the next design release

Before releasing the next package, run these five lines:

  1. Workspace export logged with user, time and action.
  2. Manifest recorded with version, hash, recipient entity and date.
  3. Receiving legal entity matches the business licence and any UL file.
  4. Certificate scope checked at the site that will build the boards.
  5. CAM location disclosed, including any subcontracted engineering step.

If line 1 is the only one you can answer today, the five-myth article has done its job: the workspace is secure on its own terms. The remaining four lines are where cloud PCB design security becomes a supply-chain question. The PCB design topic and technical articles explain the design-side decisions; the fabrication topic follows the same package onto the production floor.

Questions this article answers

Does a SOC 2 Type II cloud EDA platform make my PCB design secure end to end?

It secures the workspace the platform operates. It does not cover the engineering package once it is exported to a fabrication partner, and it does not verify the receiving site's own information-security controls. Treat the platform attestation and the factory-side evidence as two separate checks.

Can cloud PCB design tools be used for ITAR or EAR controlled technical data?

Purpose-built regions exist for export-controlled workloads, with US-only infrastructure and access restrictions. They reduce infrastructure risk but do not transfer the compliance duty to the vendor. Access is still governed by who can open the file, including engineers at suppliers and other companies.

How many Chinese PCB factories in this directory list SOC 2, ITAR or CMMC controls?

None of the 131 published profiles lists SOC 2, ITAR or CMMC in its certification records. Seventeen list ISO/IEC 27001, but ten of those entries carry a caveat about scope, revision or certificate number. That is a description of public records, not a finding about any factory's internal controls.

What should an audit trail include after a design file is sent to a factory?

Three things that join up: the platform's events log with user, time and action; a transfer manifest recording package version, file hash, recipient and timestamp; and a written acknowledgement from the named legal entity at the receiving site stating where the files are stored and which site does CAM.

Is a WAF that blocks non-US IP addresses the same as US-person-only access?

No. An IP filter is a network control. It cannot establish the nationality of a user who authenticates through an allowed network, and it has no reach into a supplier's workspace. For export-controlled projects, geoblocking is one control among several, not a substitute for identity checks.