Agriculture
15 columns
64 rows
8 formats

IoT Sensor Network Security Logs

This dataset contains detailed security incident logs from an IoT-enabled agriculture sensor network, capturing intrusion attempts, device breaches, anomaly detections, and automated security responses. Each record includes device identifiers, event types, severity levels, geolocation, network details, and compliance indicators, enabling comprehensive monitoring and analysis of field-deployed IoT security. The dataset is ideal for operational oversight, incident response optimization, and regulatory compliance in smart agriculture environments.

last updated 10 Jan 2026
by GoMask

The brief that made it

Real-time monitoring and analysis of IoT security incidents in agricultural environments

Sample rows

preview · 8 of 64 rows · all 15 columns

log_idstring	event_severitystring	compliance_flagboolean	response_actionstring	timestampdatetime	device_idstring	device_typestring	device_location_latitudefloat	device_location_longitudefloat	event_typestring	source_ipstring	destination_ipstring	response_statusstring	operator_idstring	incident_descriptionstring
SECLOG-001	medium	false	alert_sent	2024-04-01T07:15:44Z	DEV-AG01	soil_sensor	39.9872	-104.6732	intrusion_attempt	192.168.1.82	10.0.0.22	success	op_tech_01	Intrusion attempt from external IP detected and alert sent to operator.
SECLOG-002	high	true	device_isolated	2024-04-01T08:03:12Z	DEV-AG02	weather_station	40.0048	-104.6587	device_breach	172.16.0.5	10.0.0.45	success	sys_auto_03	Device breach detected, device isolated to prevent further damage.
SECLOG-003	low	false	blank	2024-04-01T09:21:33Z	DEV-AG03	irrigation_controller	39.9856	-104.6699	anomaly_detected	blank	blank	blank	op_tech_01	Unusual sensor readings detected but no action taken.
SECLOG-004	medium	false	reboot_initiated	2024-04-01T09:55:00Z	DEV-AG04	soil_sensor	39.9962	-104.672	response_triggered	192.168.1.23	10.0.0.19	success	sys_auto_01	Automated response triggered to reboot device after anomaly detection.
SECLOG-005	critical	true	device_isolated	2024-04-01T10:14:25Z	DEV-AG05	weather_station	40.012	-104.6614	malware_detected	203.0.113.77	10.0.0.47	success	op_tech_02	Critical malware detected on weather station. Device isolated and incident reported.
SECLOG-006	high	false	access_blocked	2024-04-01T10:50:11Z	DEV-AG06	irrigation_controller	39.9928	-104.6792	unauthorized_access	198.51.100.11	10.0.0.31	success	sys_auto_05	Unauthorized access attempt blocked by system firewall.
SECLOG-007	medium	false	alert_sent	2024-04-01T11:02:04Z	DEV-AG07	soil_sensor	39.995	-104.6707	intrusion_attempt	192.168.1.90	10.0.0.23	success	op_tech_01	Suspicious network traffic detected, alert sent to security team.
SECLOG-008	critical	true	alert_sent	2024-04-01T11:31:59Z	DEV-AG08	weather_station	40.0163	-104.6681	device_breach	203.0.113.20	10.0.0.48	success	op_tech_02	Device breach detected. Alert sent and incident escalated for compliance review.
SECLOG-009	medium	false	firmware_updated	2024-04-01T12:06:18Z	DEV-AG09	irrigation_controller	39.9839	-104.6815	response_triggered	blank	blank	success	sys_auto_02	Firmware update triggered as automated response to detected vulnerability.
SECLOG-010	low	false	blank	2024-04-01T12:37:43Z	DEV-AG10	soil_sensor	39.9937	-104.6742	anomaly_detected	blank	blank	blank	op_tech_01	Minor anomaly detected in soil moisture readings.
SECLOG-011	high	false	alert_sent	2024-04-01T13:10:09Z	DEV-AG11	weather_station	40.0227	-104.6633	malware_detected	203.0.113.44	10.0.0.49	success	op_tech_02	Malware signature detected on weather station, alert sent for review.
SECLOG-012	medium	false	no_action	2024-04-01T13:49:23Z	DEV-AG12	irrigation_controller	39.987	-104.6772	intrusion_attempt	192.168.1.99	10.0.0.32	pending	op_tech_03	Intrusion attempt flagged but pending further analysis.
SECLOG-013	high	true	access_blocked	2024-04-01T14:05:16Z	DEV-AG13	soil_sensor	39.9897	-104.6738	device_breach	172.16.0.28	10.0.0.26	failure	sys_auto_05	Device breach detected and access blocking failed.
SECLOG-014	medium	false	firmware_updated	2024-04-01T14:44:38Z	DEV-AG14	weather_station	40.0116	-104.6668	response_triggered	blank	blank	success	sys_auto_03	Automated firmware update response after anomaly detection.
SECLOG-015	critical	true	device_isolated	2024-04-01T15:12:14Z	DEV-AG15	irrigation_controller	39.9905	-104.682	malware_detected	203.0.113.121	10.0.0.34	success	op_tech_01	Critical malware detected, device isolated and incident escalated for compliance.
SECLOG-016	medium	false	access_blocked	2024-04-01T15:47:02Z	DEV-AG16	soil_sensor	39.9918	-104.6713	unauthorized_access	198.51.100.27	10.0.0.24	success	sys_auto_05	Unauthorized access attempt successfully blocked.
SECLOG-017	high	false	alert_sent	2024-04-01T16:25:51Z	DEV-AG17	weather_station	40.0192	-104.6651	intrusion_attempt	192.168.1.37	10.0.0.51	success	op_tech_03	Multiple intrusion attempts detected, alert escalated to operator.
SECLOG-018	critical	true	device_isolated	2024-04-01T16:54:19Z	DEV-AG18	irrigation_controller	39.9884	-104.6783	device_breach	172.16.0.32	10.0.0.38	success	op_tech_02	Critical device breach detected and device isolated.
SECLOG-019	low	false	blank	2024-04-01T17:21:40Z	DEV-AG19	soil_sensor	39.9946	-104.6701	anomaly_detected	blank	blank	blank	op_tech_01	Sensor anomaly detected, no action required.
SECLOG-020	high	false	alert_sent	2024-04-01T17:56:27Z	DEV-AG20	weather_station	40.0261	-104.6644	malware_detected	203.0.113.66	10.0.0.53	success	op_tech_03	Malware detected, alert sent for immediate review.

What the 64 rows show

from the 64-row sample

Critical (event severity) stands out: 12 of its 12 rows have compliance_flag = true, against 14 of 52 for the rest.

41%compliance_flag = true
3device types
3response statuses
6event types

Compliance flag rate by event_severitycompliance_flag = true

response_action55 rows with a value · 9 left blank

alert_sent14
access_blocked13
device_isolated10
reboot_initiated7
firmware_updated6
no_action5

15 columns by typefrom the column list below

string 11
float 2
datetime 1
boolean 1

Columns

15 columns in four groups

blueprint · 15 columns
column	type	description	example
Text 11 columns
`log_id`	string	Unique identifier for each security log entryunique	SECLOG-001
`device_id`	string	Unique identifier for the IoT device involved in the incident	DEV-AG01
`device_type`	string	Type or model of the IoT device (e.g., soil_sensor, weather_station, irrigation_controller)3 types	soil_sensor
`event_type`	string	Type of security event (e.g., intrusion_attempt, device_breach, anomaly_detected, response_triggered)6 values	intrusion_attempt
`event_severity`	string	Severity level of the event (e.g., low, medium, high, critical)low · medium · high · critical	medium
`source_ip`	string	IP address from which the event originated (if applicable)optional	192.168.1.82
`destination_ip`	string	IP address of the targeted device (if applicable)optional	10.0.0.22
`response_action`	string	Automated or manual action taken in response to the event (e.g., device_isolated, alert_sent, reboot_initiated, access_blocked)6 values · optional	alert_sent
`response_status`	string	Outcome of the response action (e.g., success, failure, pending)success · failure · pending · optional	success
`incident_description`	string	Detailed description of the security event and any relevant contextoptional	Intrusion attempt from ex…
`operator_id`	string	Identifier for the operator or automated system that handled the incident (if applicable)optional	op_tech_01
Numbers 2 columns
`device_location_latitude`	float	Latitude coordinate of the device's physical location-90 to 90 · optional	39.9872
`device_location_longitude`	float	Longitude coordinate of the device's physical location-180 to 180 · optional	-104.6732
Dates and times 1 column
`timestamp`	datetime	Date and time when the security event was recorded (UTC)	2024-04-01T07:15:44Z
True or false 1 column
`compliance_flag`	boolean	Indicates if the incident triggered a compliance requirement (true/false)optional	false

Use it for

An agriculture dashboard
The compliance_flag rate, compliance_flag by event_severity and a breakdown of response_action. Excel, Power BI or Tableau.
Why do 26 of 64 rows have compliance_flag = true?
A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
Logs64
SECLOG-001medium
SECLOG-002high
SECLOG-005critical
A software demo
Believable logs with timestamp, device_id and device_type to fill a screen in front of a buyer.

This dataset64 rows15 columns

Yours1,000 rows15 columnsdevice_location_latitude: UK only

blueprint · iot-sensor-network-security-logs

Behind this dataset

Same schema. As many rows as you need.

These 64 rows came out of a blueprint — 15 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 a unique security event detected by IoT sensors.
Include fields for device ID, event type, timestamp, severity, and automated response taken.
Events must be categorized as intrusion, unauthorized access, malware detection, or policy violation.
Severity levels must follow standardized risk scoring (e.g., Low, Medium, High).
Automated responses are limited to quarantine, alert, reboot, or log only.

Rows1,000 rows10,000 rows100,000 rows1,000,000 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: iot-sensor-network-security-logs

What should your data show?

No signup. No card.

Sample rows

What the 64 rows show

Columns

Use it for

An agriculture dashboard

A root-cause class exercise

A software demo

Make it yours.

Same schema. As many rows as you need.

More in Agriculture

What should your data show?