← CRA Compliance Checklists
AgricultureDeadline: 11 December 2027

CRA Compliance Checklist: Smart Greenhouse Automation

Default class for most products, including climate, irrigation and lighting controllers. Important Class I for a gateway whose core functionality is an internet router or modem (Annex III, point 12)

Smart greenhouse automation systems, including climate control, automated irrigation, LED lighting control, CO2 enrichment systems, and integrated greenhouse management platforms, are products with digital elements in scope for the CRA. They control critical agricultural production environments and their compromise could affect crop yields, food supply, and energy consumption. Annex III lists no agricultural or automation category, so most systems are default class (Article 7(1)). Installation size and food supply impact do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment must address. A gateway whose core functionality is an internet router or modem is Important Class I (Annex III, point 12).

14
checklist items
10
high priority
11 December 2027
deadline
Agriculture
sector
CRA Classification:Default class for most products, including climate, irrigation and lighting controllers. Important Class I for a gateway whose core functionality is an internet router or modem (Annex III, point 12)

Last updated 26 October 2026

1. Scope & Classification

Confirm all networked greenhouse automation controllers and management platforms are in CRA scope

highArticle 3(1)

Climate controllers, irrigation controllers, LED drivers with network connectivity, and greenhouse management software are products with digital elements. Map all networked components.

Classify each product by its core functionality, whatever the size of the installation

mediumArticle 7(1), Annex III, point 12

Climate, irrigation and lighting controllers match no Annex III point and are default class, also in large controlled environment agriculture (CEA) facilities. Food supply impact raises the risk that the Article 13(2) risk assessment must address. A gateway whose core functionality is a router or a modem for connection to the internet is Important Class I (Annex III, point 12).

Assess intersection with EU Machinery Regulation for automated handling, harvesting, or spraying systems within the greenhouse

mediumArticle 6, CRA / Machinery Regulation (EU) 2023/1230

Automated greenhouse machinery (transplanting robots, harvesting machines) are subject to the Machinery Regulation as well as CRA.

Compile SBOM for greenhouse management software, controller firmware, sensor firmware, and all connectivity components

high

Greenhouse automation platforms integrate multiple controller types (climate, irrigation, lighting) often from different vendors. Compile SBOMs for each.

2. Product Security (Annex I Part I)

Implement authentication for all greenhouse controller management interfaces - eliminate default or shared credentials

highAnnex I, Part I(2)

Unauthorised access to greenhouse climate controllers could manipulate temperature, humidity, or CO2 levels, destroying crops. Require authentication with unique per-installation credentials.

Validate all control setpoints received from management systems - reject values outside agronomically safe ranges

high

A malicious setpoint pushing greenhouse temperature to crop-damaging extremes could destroy an entire crop. Implement hard limits for all critical control parameters.

Encrypt all communications between greenhouse controllers, sensors, and management platforms

high

Greenhouse management commands and crop data should be encrypted. Use TLS for all IP communications and appropriate security for industrial protocols (Modbus TCP, BACnet/IP).

Implement signed firmware updates and verify before application to production greenhouse control systems

high

Greenhouse controllers managing active crops cannot be taken offline carelessly. Provide signed updates with staged rollout and rollback capability.

3. CVD Policy & Vulnerability Handling

Publish a CVD policy with a security contact for greenhouse automation system vulnerabilities

highArticle 13(1)

Greenhouse automation systems are an emerging security research area. A CVD policy enables responsible disclosure before vulnerabilities are exploited.

Define security support lifecycle appropriate to greenhouse automation investment - minimum 7 years

high

Greenhouse automation infrastructure is a capital investment with a long operational life. Commit to a 7-year minimum support period and publish per-product end dates.

4. Article 14 Incident Reporting

Define Article 14 triggers - focus on exploitation enabling setpoint manipulation or denial-of-service affecting climate control in active production facilities

mediumArticle 14(1)

An exploited vulnerability that disables climate control in a large greenhouse during winter could destroy the entire crop. Define your Article 14 criteria.

Prepare and test Article 14 notification procedure - assign owners for each reporting milestone

mediumArticle 14(2)

Use the CVD Portal Article 14 timeline tool to plan your notification process and test it before an incident.

5. CE Marking & Technical Documentation

Prepare CRA technical file covering controller security architecture, setpoint validation logic, SBOM, and update mechanism

highArticle 31, Annex VII

Technical documentation should demonstrate that setpoint validation prevents out-of-range command injection and that all communications are protected.

Issue EU Declaration of Conformity referencing the CRA for all in-scope greenhouse automation products

highArticle 20, Article 28

DoC must reference the CRA. For wireless sensors and controllers, also reference the Radio Equipment Directive.

Track your Smart Greenhouse Automation compliance progress in CVD Portal.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Our greenhouse automation system uses BACnet - is this protocol compatible with CRA encryption requirements?+

BACnet/SC (Secure Connect) supports TLS encryption and certificate-based authentication, and is the recommended CRA-compliant variant. Legacy BACnet/IP does not include native security and must be protected by network-layer controls (VPN, firewall, VLAN isolation) as a compensating measure. New greenhouse automation installations should implement BACnet/SC where possible.

Our greenhouse management platform is offered as SaaS - does CRA apply?+

Purely cloud-based SaaS is generally outside CRA scope. However, if you supply on-premises controller hardware, locally installed software, or gateway devices alongside the SaaS platform, those local components are in scope. The greenhouse controllers themselves (hardware + firmware) are always in scope regardless of whether management is cloud-based.

We integrate third-party climate sensors into our greenhouse management platform - are we responsible for their CRA compliance?+

Each sensor manufacturer is responsible for their own CRA compliance. You, as the platform integrator, are responsible for the security of your platform and how it handles data from those sensors. If you sell a complete integrated system (including third-party sensors rebranded or bundled under your brand), you take on manufacturer responsibility for the system. If you merely provide integration support for third-party sensors, the sensor manufacturer retains their own CRA obligations.

This checklist is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Need a CVD policy for Smart Greenhouse Automation?

Download a free CRA-compliant disclosure policy template and deploy it in minutes.

Browse templates →