The 2026 Thales Data Threat Report - Manufacturing Edition, paints a concerning picture of the security posture in the manufacturing sector. Based on a survey of 417 executives, the report finds that manufacturers are grappling with new threats from Artificial Intelligence (AI), with 61% already experiencing deepfake attacks. Simultaneously, the sector is struggling with fundamental cloud security practices. A significant majority of organizations lack complete visibility into where their data is stored, and the encryption of sensitive data in the cloud is dangerously low, creating a fertile ground for attackers targeting cloud infrastructure.
The report highlights a dual threat facing manufacturers: emerging AI-driven attacks and persistent weaknesses in cloud security.
The threats described in the report map to several common attack techniques.
The convergence of these threats creates significant risk for manufacturers:
No specific Indicators of Compromise (IOCs) were provided in the source articles.
To counter these threats, security teams in manufacturing should hunt for the following:
sts:AssumeRoleD3-SCA - System Configuration Analysis.D3-SFA - System File Analysis.Directly addresses the report's finding of low encryption rates for sensitive data in the cloud.
Mitigates the risk of credential theft attacks against cloud environments, which 57% of manufacturers reported.
Essential for building resilience against AI-driven social engineering attacks like deepfakes.
The Thales report's finding that only 8% of manufacturers extensively encrypt their sensitive cloud data is a critical failure. Implementing File Encryption (or more broadly, data-at-rest encryption) is a fundamental control. For manufacturers, this means enabling default encryption on all cloud storage services (e.g., AWS S3, Azure Blob Storage). For highly sensitive intellectual property, such as CAD designs or chemical formulas, organizations should use client-side encryption or a Customer-Managed Encryption Key (CMEK) service from their cloud provider. This ensures that even if an attacker compromises the cloud platform or steals access credentials, the underlying data remains unreadable without the separate encryption key. This D3FEND technique changes a potential catastrophic data breach into a non-event, as the exfiltrated data is useless.
With 57% of manufacturers reporting an increase in cloud credential theft, enforcing Multi-factor Authentication is no longer optional. MFA should be mandated for all users accessing cloud resources, especially administrators and developers with privileged access to cloud management infrastructure and SaaS applications. In the manufacturing context, this applies to engineers accessing cloud-based SCADA management portals or supply chain managers using SaaS logistics platforms. Organizations should prioritize phishing-resistant MFA methods like FIDO2 security keys over less secure methods like SMS. This D3FEND technique provides a critical layer of defense that can stop an attacker even after they have successfully stolen a user's password, directly mitigating the most common vector for cloud account takeover.
To combat both sophisticated AI-driven social engineering and cloud account takeovers, User Behavior Analytics (UBA) is an essential detection capability. UBA platforms ingest logs from various sources (cloud, identity providers, endpoints) to build a baseline of normal behavior for each user. For a manufacturing firm, this could mean flagging when an engineer's account, which normally only accesses design files from the corporate network during business hours, suddenly starts downloading large quantities of data from a different country at 3 AM. This anomalous activity would trigger an alert. In the context of deepfake attacks, UBA can help by flagging the unusual follow-on actions after a social engineering attempt, such as a finance employee attempting to bypass a payment verification control they have never touched before. This provides a chance to detect and intervene in a complex attack chain.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.