Threat Modeling and Attack Surface Analysis of IoT-Enabled Controlled Environment Agriculture Systems

TL;DR

This paper develops the first comprehensive threat model for IoT-enabled Controlled Environment Agriculture systems, identifying numerous vulnerabilities and proposing security countermeasures.

Contribution

It introduces a novel threat model for CEA, applies multiple analysis techniques, and highlights unique AI-driven attack classes and security gaps in the industry.

Findings

123 unique threats identified across 25 data-flow elements

10 communication protocols operate without authentication or encryption

Only one CVE issued among surveyed vendors, with no IEC 62443 certifications

Abstract

The United States designates Food and Agriculture as one of sixteen critical infrastructure sectors, yet no mandatory cybersecurity requirements exist for agricultural operations and no formal threat model has been published for Controlled Environment Agriculture (CEA) systems. This paper presents the first comprehensive threat model for IoT-enabled CEA, applying STRIDE analysis, MITRE ATT&CK for ICS mapping, and IEC 62443 zone-and-conduit decomposition to a production platform deployed across 30+ commercial facilities in 8 U.S. climate zones. We enumerate 123 unique threats across 25 data-flow-diagram elements spanning 15 communication protocols, 10 of which operate with zero authentication or encryption by design. We identify five novel attack classes unique to AI-driven CEA: stealth destabilization of neural-network-tuned PID controllers, baseline drift poisoning of anomaly detectors, cross-facility propagation via federated transfer learning, adversarial agronomic schedules that exploit crop biology rather than computational models, and reward poisoning of reinforcement-learning energy optimizers. Physical impact analysis quantifies crop loss timelines from minutes (aeroponics) to days, including worker safety hazards from CO2 injection manipulation. A survey of 10 commercial CEA vendors reveals only one CVE ever issued, zero bug bounty programs, and zero IEC 62443 certifications. We propose a defense-in-depth countermeasure framework and recommend Security Level 2 as a minimum baseline.