Current service
The remediation changes are local. The production application, customer records and demo farms have not been changed by this work.
Customer review · 11 October 2026
Security &
service risk review.
What could affect your farm information, the accuracy of readings and the continuity of CropNexus — and how those risks are being addressed.
16
Current risksAll remain open at this review date
8
High priorityPrompt action required
7
Medium priorityPlanned reduction required
1
Low priorityAdditional protection
The review covers the existing application and data service, plus the new route that carries sensor readings into CropNexus. Several findings relate to existing controls; the new sensor connection adds availability, recovery and credential-management risks.
01 / Understand the priorities
Risk matrix
Read likelihood down the left and potential impact across the bottom. Select a cell to see its risks in the register.
Likelihood ↓16 current risks · future service excluded
LimitedMaterialMajor
Potential impact →
HighMediumLow
02 / The full register
Risks and planned responses
Each entry explains the potential customer effect, current protection, planned action and the evidence required to close it. Team owners are suggested responsibilities; timing labels are priorities, not agreed delivery dates.
| Reference | Risk & customer effect | Priority | Response status | Suggested owner |
|---|
No risks match these filters. Reset the filters to view the full register.
“Local improvements prepared” means source changes are ready for further release testing. It does not mean the live risk is resolved. Select a risk title to read its full response.
Separate release safeguard CNX-17
Customer access checks before a future data service is enabled
This service was not deployed in the reviewed cloud account and region. It must remain disabled until every caller can access only their approved farms and devices. It is rated High if enabled and is excluded from the 16 current risks and the matrix.
Read the safeguard03 / What this means for you
Users, features & demo farms
The remediation needs a controlled release with checks of normal customer workflows.
Farm access and demo setup
Authorised users should retain access to their farms and settings. The import page already requires a developer account; the fix strengthens the execution check. The existing admin/developer demo-farm reset action is retained.
Readings and weather
Scheduled jobs need their new permission setup before release. Missing setup would stop scheduled sensor and weather refreshes, including on demo farms. Normal sensor and simulator readings are expected to continue after a verified release.
Release checks
Rehearse sign-in, farm selection, configuration, demo reset, trunk and fruit charts, weather updates, imports and image uploads. Also test recovery, credential replacement and any required embedded presentation.
ReviewedEvidence recorded
Prepared locallyInitial checks passed
Release & verifyCustomer flows and failure tests
Close risksRecord live acceptance evidence
04 / Evidence still to confirm
Six further assurance checks
These are checks awaiting evidence. They are not six additional confirmed vulnerabilities.