Agri IoT Sensor Security Audit Log

This dataset provides detailed security audit logs from distributed agriculture IoT sensor networks, including authentication attempts, anomaly detections, compliance checks, and remediation actions. It enables AgTech startups and IoT security teams to benchmark device security, detect vulnerabilities, and ensure regulatory compliance across smart farming deployments. Rich contextual fields support advanced analytics for threat detection and compliance reporting.

  • last updated 26 Dec 2025
  • by GoMask
The brief that made it

Benchmarking IoT device security and compliance in smart farming environments

Sample rows

preview · 8 of 120 rows · all 18 columns
log_idstringevent_severitystringremediation_actionstringtimestampdatetimedevice_idstringdevice_typestringdevice_location_latitudefloatdevice_location_longitudefloatevent_typestringevent_statusstringuser_idstringsource_ipstringdestination_ipstringanomaly_typestringcompliance_check_typestringcompliance_standardstringremediation_statusstringevent_descriptionstring
cf2d32b1-9e24-4a3b-ab84-ac7e1cdbinfoblank2024-04-21T08:34:22Zsoil-moisture-1002soil-moisture34.2321-118.4914authenticationsuccesssvc_ops_1110.12.18.31192.168.1.15blankblankblankblankRoutine authentication succeeded for soil-moisture sensor at Los Angeles field site.
7eafc9bcae994f0ccriticaldevice_isolated2024-04-23T16:12:11Zweather-station-2123weather-station50.85034.3517anomalydetectedsvc_monitor203.0.113.4510.34.44.2firmware_tamperingblankblankpendingFirmware tampering detected on weather-station-2123 in Brussels. Immediate action recommended.
f9c4a5e6-2b1d-4bfc-bb28-7e6ad3c3warningblank2024-04-24T09:41:08Zirrigation-controller-3067irrigation-controller37.7749-122.4194compliance_checkcompliantaud_stevens8.8.8.810.0.0.5blankpassword_policyISO27001blankPassword policy compliance verified for irrigation-controller-3067 at San Francisco location.
12e3f4a9fa32d1c0infoblank2024-04-22T11:22:55Zenv-sensor-5580env-sensor48.85662.3522configuration_changesuccessauto_maint10.0.15.4192.168.0.22blankblankblankblankConfiguration updated for env-sensor-5580 in Paris. New calibration applied.
ab7e3c9f-4cb2-4f8e-8fd2-1c6a3b68warningblank2024-04-22T18:50:36Zsoil-moisture-1046soil-moisture00authenticationfailureop_ben203.0.113.2210.14.3.9blankblankblankblankFailed authentication attempt for soil-moisture-1046 from external IP.
fbca32d4-3e4a-4f6a-bb77-3e9ad12fwarningdevice_rebooted2024-04-21T15:30:42Zirrigation-controller-3091irrigation-controller41.40362.1744anomalydetectedsvc_analytics1.1.1.1192.168.1.22unusual_trafficblankblankcompletedUnusual traffic detected on irrigation-controller-3091 in Barcelona. Possible DDoS activity.
e4f6acb7-3ef8-4a1d-8b9c-2d4ab3e2criticalfirmware_updated2024-04-23T06:14:19Zenv-sensor-5612env-sensor66.5135compliance_checknon-compliantaud_validator8.8.4.410.43.2.1blankfirmware_updateGDPRpendingFirmware update compliance failed for env-sensor-5612 at high latitude. Immediate remediation required.
bcf123e2d4a9f7c8infoblank2024-04-21T23:01:12Zweather-station-2188weather-station51.5074-0.1278authenticationsuccesssvc_ops_1310.0.8.13192.168.1.44blankblankblankblankRoutine authentication succeeded for weather-station-2188 in London.

What the 120 rows show

from the 120-row sample
  • 3anomaly types
  • 3compliance check types
  • 3compliance standards
  • 3remediation statuses
  • 4event types
  • 6event statuses
event_severity120 rows by value
0306054info45%36warning30%30critical25%
remediation_action46 rows with a value · 74 left blank
  1. device_isolated16
  2. device_rebooted12
  3. encryption_configured9
  4. password_reset5
  5. firmware_updated4
18 columns by typefrom the column list below
  • string 15
  • float 2
  • datetime 1

Columns

18 columns in three groups
blueprint · 18 columns
columntypedescriptionexample
Text 15 columns
log_idstringUnique identifier for each audit log entry.unique7eafc9bcae994f0c
device_idstringUnique identifier of the IoT sensor device involved in the event.soil-moisture-1002
device_typestringType or model of the IoT sensor device (e.g., soil-moisture, weather-station, irrigation-controller).8 typessoil-moisture
event_typestringType of security event (e.g., authentication, anomaly, compliance_check, configuration_change).4 valuesauthentication
event_severitystringSeverity level of the event (e.g., info, warning, critical).info · warning · criticalinfo
event_statusstringOutcome or status of the event (e.g., success, failure, detected, resolved, non-compliant, compliant).6 valuessuccess
user_idstringIdentifier of the user or service account initiating the event (if applicable).optionalsvc_ops_11
source_ipstringIP address from which the event originated.optional10.12.18.31
destination_ipstringIP address of the device or service targeted by the event.optional192.168.1.15
anomaly_typestringType of anomaly detected (e.g., unauthorized_access, firmware_tampering, unusual_traffic). Only populated for anomaly events.3 types · optionalfirmware_tampering
compliance_check_typestringType of compliance check performed (e.g., encryption_enabled, password_policy, firmware_update). Only populated for compliance_check events.3 types · optionalpassword_policy
compliance_standardstringRegulatory or industry standard referenced (e.g., ISO27001, NIST, GDPR).3 standards · optionalISO27001
event_descriptionstringDetailed description of the event, including relevant context or error messages.optionalRoutine authentication su…
remediation_actionstringAction taken to remediate the event (e.g., password_reset, device_isolated, firmware_updated).5 actions · optionaldevice_isolated
remediation_statusstringStatus of the remediation action (e.g., pending, completed, failed).pending · completed · failed · optionalpending
Numbers 2 columns
device_location_latitudefloatLatitude coordinate of the device's physical location.-90 to 90 · optional34.2321
device_location_longitudefloatLongitude coordinate of the device's physical location.-180 to 180 · optional-118.4914
Dates and times 1 column
timestampdatetimeDate and time when the event was logged (UTC).2024-04-21T08:34:22Z

Use it for

  • rows12018 columnsrows by event severity54info36warning30critic…

    An agriculture dashboard

    A breakdown of remediation_action. Excel, Power BI or Tableau.

  • What pattern can you find in 120 rows?

    A class exercise

    Hand out the rows and one question. Everyone works from the same 120 rows.

  • A software demo

    Believable logs with timestamp, device_id and device_type to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 18 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset120 rows18 columns
Yours1,000 rows18 columnsdevice_location_latitude: UK only

blueprint · agri-iot-sensor-security-audit-log

Behind this dataset

Same schema. As many rows as you need.

These 120 rows came out of a blueprint — 18 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each row represents an individual sensor event (login, config change, anomaly, etc.).
  • Device ID must be unique per event and tied to a valid sensor type (e.g., soil moisture, weather, drone).
  • Authentication failures and anomalies must be flagged and include a severity score.
  • Compliance checks must log pass/fail status based on industry security standards.
  • Timestamp must follow a consistent ISO 8601 format.
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
agri-iot-sensor-security-audit-log

More in Agriculture

Browse all
Also in AgricultureFarm Sensor Pest Detection LogsPrecision Farm Sensor ReadingsSmart Irrigation Sensor AnalyticsAll 1,966 datasets

What should your data show?

Preview 20 rows free
No signup. No card.