PLM and Engineering Data Security Guide: Protecting CAD, Design Vaults and Supplier Collaboration

Product lifecycle management (PLM) systems hold the most valuable and most widely shared data a manufacturer owns, and most of it leaves the vault the moment an engineer needs to work on it. CAD models, drawings, bills of materials, process sheets and test data are copied to workstations, exported as neutral formats, sent to suppliers and pasted into new tools. This guide covers how to secure the PLM platform itself, control access to design data by project, classification and nationality, protect files once they leave the vault, and run supplier collaboration without losing track of who holds what. It is written for security architects, PLM administrators and engineering IT teams in manufacturing, aerospace, defence, automotive and medical device organisations.

Key takeaways

• The vault is not the boundary. Most engineering data loss happens after a legitimate check-out or export, so file-level protection and export tracking matter as much as PLM permissions.
• Classify by obligation, not by sensitivity alone. Export control (ITAR, EAR), defence contract terms (DFARS 252.204-7012), customer NDAs and trade secrets each impose different rules on who may see a part, and the PLM access model has to express all of them.
• PLM servers are internet-facing targets. CISA added a PTC Windchill and FlexPLM remote code execution flaw to the Known Exploited Vulnerabilities catalogue in June 2026 with known ransomware use, so patch and exposure discipline belongs with the rest of your perimeter.
• Supplier access is the biggest exposure. Time-bound, project-scoped supplier accounts with automatic expiry beat shared portal logins and ad hoc email of drawings.
• Integration accounts hold everything. ERP, MES, CAD and visualisation connectors usually run as powerful service accounts that bypass the access rules people are subject to.

What PLM holds and why attackers want it

A PLM system (for example Siemens Teamcenter, PTC Windchill or Dassault Systèmes ENOVIA) is the system of record for a product's definition across its life: requirements, CAD models and drawings, the engineering bill of materials, change orders, manufacturing process plans, supplier part data, test results and compliance evidence. A file vault stores the CAD and document files; a database stores metadata, structure and history; and integrations push released data to ERP, manufacturing execution systems and supplier portals.

The Five Eyes Secure Innovation guidance, published by the security agencies of Australia, Canada, New Zealand, the United Kingdom and the United States, lists the routes by which state actors, competitors and criminals obtain technology: insiders, cyber intrusions, physical theft, targeting during travel, investment used to gain access, foreign legal regimes that compel access, and compromised suppliers. Every one of those routes ends at the design data in PLM or at a copy of it.

Classifying engineering data by obligation

Engineering data needs more than a single "confidential" label, because the rules for who may see it come from different sources and they often apply at once to the same part.

• ITAR technical data: 22 CFR 120.33 defines technical data as information required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance or modification of defence articles, and names blueprints, drawings, photographs, plans, instructions and documentation as forms it takes. Release to a foreign person is an export, so the PLM access model must know nationality, not just department. See the Encryption Export Controls Guide.
• EAR technology and cloud storage: 15 CFR 734.18(a)(5) says sending, taking or storing unclassified technology is not an export if it is secured with end-to-end encryption using FIPS 140-2 (or successor) validated modules or equally effective means, and is not intentionally stored in a Country Group D:5 country. That makes key ownership and storage location real design decisions for cloud PLM.
• Defence contract data: DFARS 252.204-7012 lists research and engineering data, engineering drawings, specifications, process sheets, technical reports and source code as examples of controlled technical information, requires NIST SP 800-171 on contractor systems, and requires cyber incidents to be reported within 72 hours of discovery. See the CUI Guide and the CMMC Scoping Guide.
• Automotive prototypes: TISAX, governed by the ENX Association against the VDA ISA catalogue, includes prototype protection objectives alongside information security and data protection. See the TISAX Guide.
• Trade secrets and customer NDAs: protection depends on showing reasonable steps were taken, which in practice means documented access restriction and evidence of who received what.

Record each obligation as structured metadata on the item or document (for example export jurisdiction, classification number, contract or NDA reference, owning programme), set by the engineering owner at creation and checked at release. Free-text title blocks on drawings are not enough: access rules cannot evaluate them. See the Data Classification Guide.

Access control inside the PLM platform

Mature PLM platforms combine several access layers. Siemens' own ITAR white paper for Teamcenter describes Authorized Data Access as an umbrella for export control, NDAs and supplier contracts: authorising documents such as export licences, technical assistance agreements and NDAs list the users and groups they cover, carry an expiry date, and access is revoked automatically when they expire. Users and groups can be classified by nationality or location, and ACLs then grant, deny or leave privileges unset. Other platforms use different names (Windchill uses access control policies, contexts and security labels) but the same building blocks apply.

• Separate view from download: many engineers, buyers and quality staff only need to see a lightweight visualisation (for example JT or a PDF drawing), not the native CAD model. Grant download of native formats as a distinct privilege.
• Bulk operations are a privilege: exporting a whole product structure, generating a full data package or running a bulk report is how a leaver or intruder takes a whole product line. Restrict it to roles that need it and alert on it.
• Attribute sources: nationality and employer attributes drive export decisions, so they must come from an authoritative feed (HR, the supplier onboarding record) and changes must flow through within a day. See the Joiner-Mover-Leaver Guide.
• Reviews: programme owners recertify membership quarterly and on programme close. See the Access Reviews Guide.

Securing the PLM platform and its integrations

PLM is a multi-tier application: web and application servers, a file server or object storage vault (often with remote cache servers at other sites), a database, a visualisation service and a set of integrations. Treat it as a tier-one business system.

• Patch and exposure: the CISA Known Exploited Vulnerabilities catalogue lists CVE-2026-12569, an improper input validation flaw in PTC Windchill and FlexPLM that lets an unauthenticated remote attacker execute code, added on 25 June 2026 and marked as known to be used in ransomware campaigns. Keep PLM web tiers behind a reverse proxy or VPN, not directly on the internet, and subscribe to the vendor's security advisories. See the Vulnerability Management Guide.
• Viewer and translator file parsing: CAD viewers and translators parse complex formats from outside the organisation. CISA advisory ICSA-24-011-06 described four flaws in Siemens JT2Go and Teamcenter Visualization triggered by specially crafted CGM files, three of which could allow code execution, and advised not opening CGM files from untrusted sources. Run translation of supplier files in an isolated conversion service, not on engineers' desktops.
• Integration service accounts: connectors to ERP, MES, CAD authoring tools and supplier portals typically run as service accounts with broad read access across every programme. Give each integration its own account scoped to the data it moves, store its credentials in a vault, and block interactive logon. See the Service Account Security Guide.
• Vault and cache servers: the file vault holds native files outside the database's access logic. Restrict operating system and share access to the PLM service identity, encrypt at rest, and make sure remote cache servers at plants and supplier sites get the same hardening as the main vault.
• Database and backups: a DBA or backup operator can read every design without passing through PLM rules. Treat database and backup access as privileged and log it. See the DBA Privileged Access guide.
• Single sign-on and MFA: federate PLM authentication to the corporate identity provider so leaver processing and MFA apply, and retire local PLM accounts other than a sealed break-glass administrator.

Where identity fits

In most PLM estates the hardest identities to govern are not engineers. They are supplier users created by a buyer for a single project and never removed, integration accounts that were granted "read all" during an upgrade, and the PLM application's own database and vault accounts with passwords in configuration files. A quarterly inventory of all three, with an owner and an expiry for each, closes most of the gap. See the Third-Party Access Guide and the Service Account Inventory Template.

Protecting engineering data outside the vault

Siemens' own Teamcenter blog on rights management makes the point plainly: once downloaded, files end up on local drives, personal devices, email and file-sharing services, and authorised employees can copy specifications to unmanaged devices. Choose controls by how the data is used.

• Engineering workstations: local CAD caches and working directories hold full models. Encrypt disks, block unmanaged removable media and clear caches on reassignment. See the Engineering Workstation Security Guide and the Information Rights Management and Persistent File Protection Guide.
• Generative AI tools: engineers paste code, specifications and test data into public assistants to save time. The Samsung ChatGPT source code leak shows how fast engineering material reaches a public tool when no approved alternative exists. Approve a tool with enterprise data terms and block the rest for engineering networks.

Supplier and partner collaboration

Suppliers need drawings to quote and build, and joint development partners need live models. The Secure Innovation guidance advises vetting partners, sharing only the data they need, and backing NDAs with real controls because an NDA alone does not stop theft.

1. Define the data package per relationship: which parts, which formats (native, STEP, JT, PDF), which revision, for how long. Record it against the contract or NDA reference.
2. Use a controlled exchange channel: a supplier portal or managed file transfer service with per-supplier accounts, download logging and link expiry, not personal email or consumer file sharing. See the Managed File Transfer (MFT) Security Guide.
3. Named, federated supplier accounts: one account per person, MFA enforced, expiry tied to the contract end date, sponsor named on the internal side.
4. Flow down obligations: where DFARS 252.204-7012 applies, the clause must be included in subcontracts involving covered defence information, and subcontractors report incidents up the chain. Check that the supplier's own environment meets the same standard before sending controlled data.
5. Retrieve and certify at the end: at contract end, revoke accounts, request written certification of deletion and keep it with the contract record. See the Vendor Offboarding and Termination Guide.

Implementation roadmap

1. Inventory (weeks 1 to 4): list PLM instances, vault and cache servers, integrations and their service accounts, supplier portals, and every external user. Identify which programmes carry export control, defence contract or NDA obligations.
2. Close the exposure (weeks 2 to 6): remove direct internet exposure of PLM web tiers, apply outstanding vendor security patches, enforce SSO and MFA, and disable stale supplier accounts.
3. Classification metadata (months 2 to 4): add mandatory export, contract and classification attributes to item and document types, backfill for active programmes first, and pilot the access rules in a test environment with copies of real rules.
4. Tighten privileges (months 3 to 6): split view from download, restrict bulk export, scope integration accounts. Roll out programme by programme with a named rollback: keep the previous rule tree exported so it can be restored if engineers are blocked.
5. Protect data in motion (months 4 to 9): move supplier exchange to the controlled channel, apply rights management to outgoing packages, deploy endpoint DLP in monitor mode on engineering workstations before blocking.
6. Monitor and review (ongoing): feed PLM audit logs to the SIEM, run quarterly programme membership reviews, and test the controls with a tabletop on a departing engineer scenario.

Smaller manufacturers often run PLM-lite or product data management inside the CAD vendor's cloud. Focus on SSO, MFA, per-supplier accounts, export logging and viewer-only sharing; defer rights management until supplier volume justifies it. Large and defence organisations need the full attribute-based model, separate enclaves for controlled programmes, and evidence suitable for CMMC or customer audits.

Detection and measurement

Enable the PLM platform's audit logging for logins, downloads, exports, data package generation, access rule changes and licence object changes, and forward it to the SIEM. Data theft from information repositories maps to MITRE ATT&CK T1213 Data from Information Repositories, with copying from network shares (T1039) and upload to cloud storage (T1567.002) as the usual next steps.

• Bulk download: a user downloading more native files in a day than their 90-day baseline, especially across programmes.
• Leaver window: download or export activity by users with a resignation or contract end date in the next 30 days. See the Insider Data Theft Guide.
• Restricted access attempts: denied access to export-controlled items, which can indicate a misclassified user or probing.
• Rule changes: any change to ACLs, rule trees or licence objects outside an approved change ticket.
• Service account use: integration accounts used interactively or from new hosts.

Framework mapping

Common failure patterns

• Classification lives in the title block: export markings are printed on drawings but not stored as attributes, so the PLM cannot enforce them and a foreign national can open the model.
• Supplier accounts outlive the contract: a buyer creates accounts for a quote, the supplier is not selected, and the accounts stay active for years with access to a whole assembly.
• Integration account reads everything: a connector granted broad rights during an upgrade becomes the easiest path to every programme, and its password sits in a configuration file on the integration server.
• PLM web tier on the internet: remote access for plants and partners is provided by publishing the PLM web server directly, leaving it exposed when the next critical vendor flaw appears.
• Native files emailed to suppliers: the controlled portal is slow, so engineers attach STEP files to email, and nobody can say later which supplier holds which revision.
• Leaver downloads unnoticed: no baseline for download volume, so a departing engineer's bulk export in the final weeks is found only when a competitor's product appears.

Practitioner checklist

• Inventory every PLM instance, vault and cache server, integration and external user, with an owner for each.
• Remove direct internet exposure of PLM web tiers and apply all vendor security advisories, prioritising any KEV-listed flaw.
• Store export jurisdiction, classification, contract and NDA references as mandatory item attributes.
• Source nationality, location and employer attributes from HR and supplier onboarding records.
• Separate viewing from native file download and restrict bulk export and data package generation.
• Give each integration its own scoped service account with credentials in a vault and no interactive logon.
• Exchange supplier data through a controlled channel with per-person accounts, logging and expiry.
• Run supplier file translation in an isolated service, not on engineering desktops.
• Alert on bulk downloads, leaver-window activity and access rule changes.
• Recertify programme membership quarterly and collect deletion certificates at contract end.

Standards and references

• eCFR: 22 CFR 120.33 Technical data (ITAR)
• eCFR: 15 CFR 734.18 Activities that are not exports, reexports, or transfers (EAR)
• Acquisition.gov: DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting
• NIST: SP 800-171 Rev. 3 Protecting Controlled Unclassified Information
• US National Counterintelligence and Security Center: Secure Innovation (Five Eyes guidance)
• CISA: Known Exploited Vulnerabilities Catalog
• CISA: ICSA-24-011-06 Siemens Teamcenter Visualization and JT2Go
• MITRE ATT&CK: Data from Information Repositories

Related NHI Mgmt Group resources: Engineering Workstation Security Guide · CUI Guide · Information Rights Management and Persistent File Protection Guide · Insider Data Theft Guide · Third-Party Access Guide