LB 525 - Agricultural Data Zero Trust Manifesto
PREPARED BY AGRASOFT
Through our work in agricultural data security and privacy, we have come to value:
Verified Identity and Access over unlimited data availability.
Data Minimization and Purpose Specification over unrestricted collection.
Continuous Monitoring and Assessment over periodic reviews.
Risk-Based Controls over universal permissions.
Individual Privacy Rights over operational convenience.
That is, while we value the items on the right, we value the items on the left more.
Principles:
Our highest priority is to protect sensitive agricultural data through continuous verification and validation of every access attempt, regardless of source or location.
Agricultural data should be collected, used, and shared only for specified, permissionsed, controlled and legitimate purposes, with demonstrable identity and access controls at every step.
We embrace awareness of the ag data threat landscapes and security requirements. Zero trust processes must be harnessed for secure, permissioned, monitored ag data exchange, from seedtime to harvest.
Farm operators, agronomists, and technologists must work together cooperatively to implement and maintain zero trust principles across all agricultural systems.
Build data handling processes around privacy and ownership aligned stakeholders. Give them the environment and support they need to protect data privacy, and trust them to get the job done within verified boundaries.
The most efficient and effective method of sharing ag data between supply chain parties and stakeholders is by explicit consent data exchanges using, secure encrypted communication channels.
Secure agricultural data is the primary measure of progress. Privacy-preserving techniques must be demonstrable and measurable.
Zero trust processes promote sustainable development. The stakeholders should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances data security.
Simplicity--the art of maximizing the amount of work not done while maintaining security--is essential.
The best architectures, requirements, and designs emerge from self-organizing teams that understand both agriculture and security.
At regular intervals, the team reflects on how to become more effective at protecting agricultural data, then tunes and adjusts its behavior accordingly.
Supporting Practices:
Implement the principle of least privilege
Verify explicitly before granting access
Use encryption in transit and at rest
Monitor and log all data access and movements
Maintain detailed data inventories and flows
Conduct regular privacy impact assessments
Enforce data classification and handling procedures
Practice security-first incident response
Train all stakeholders in privacy and security practices
Establish clear data governance structures