IoT-Enabled Remote Access Logs

This dataset provides detailed synthetic logs of remote property access events managed through IoT devices, including event timestamps, user roles, device types, access results, and property locations. Designed for security analysis, operational monitoring, and usage trend discovery, it enables organizations to optimize workflows and enhance unattended property management. The comprehensive structure supports both high-level analytics and granular event investigation.

  • last updated 1 Jan 2026
  • by GoMask
The brief that made it

Security incident investigation and audit trail analysis

Sample rows

preview · 8 of 80 rows · all 20 columns
log_idstringdevice_typestringaccess_duration_secondsintegerfailure_reasonstringevent_timestampdatetimeproperty_idstringproperty_street_addressstringproperty_citystringproperty_statestringproperty_postal_codestringproperty_countrystringdevice_idstringuser_idstringuser_rolestringaccess_methodstringaccess_resultstringremote_ipstringgeo_latitudefloatgeo_longitudefloatnotesstring
a9b2c3d4-e1f2-4467smart_lock220blank2024-06-01T08:23:15ZPROP1001150 Oakridge AveAustinTX78745USADEV-LOCK-001USR-TCH-001technicianmobile_appsuccess192.168.1.10130.2301-97.7685Routine maintenance access
f8e7d5c6-b2a1-5523camerablankinvalid credentials2024-06-01T09:05:41ZPROP100223 Maple StDenverCO80205USADEV-CAM-101USR-GST-002guestweb_portalfailure10.0.0.2239.7402-104.9929Guest unable to view camera feed
h6j5k4l3-m2n1-7743sensor1800blank2024-06-01T09:33:20ZPROP100388 Broomfield RdPortlandOR97229USADEV-SNS-209USR-CLN-003cleanerscheduledsuccess172.16.0.145.5483-122.8787Scheduled cleaning session
m5n6o7p8-q3r4-8265smart_lockblanknetwork timeout2024-06-01T10:17:04ZPROP1001150 Oakridge AveAustinTX78745USADEV-LOCK-001USR-TCH-001technicianapitimeout192.168.1.10530.2301-97.7685API call did not complete
p9q8r7s6-t5u4-9841gateway540blank2024-06-01T11:12:09ZPROP1004420 Lincoln AveMadisonWI53703USADEV-GWY-333USR-MGR-004managerweb_portalsuccess192.168.10.1043.0731-89.4012Manager accessed system dashboard
s1t2u3v4-w5x6-1052camera360blank2024-06-01T11:47:36ZPROP100223 Maple StDenverCO80205USADEV-CAM-102USR-MGR-002managermobile_appsuccess10.0.0.2339.7402-104.9929Manager verified camera status
v5w6x7y8-z9a1-2064sensor1200blank2024-06-01T12:25:19ZPROP1005301 Pine LaneSeattleWA98101USADEV-SNS-210USR-CLN-005cleanerscheduledsuccess10.1.1.2047.6097-122.3331Sensor triggered for cleaning
y9z8a7b6-c5d4-3076gatewayblankuser not authorized2024-06-01T13:08:27ZPROP1004420 Lincoln AveMadisonWI53703USADEV-GWY-334USR-GST-004guestmanual_overridedenied10.0.0.2443.0731-89.4012Guest denied access override

What the 80 rows show

from the 80-row sample

Sensor (device type) stands out: mean access_duration_seconds is 920.1, against 251.2 for the rest.

  • 291median access_duration_seconds
  • 4property countries
  • 4user roles
  • 4access results
  • 5access methods
Mean access_duration_seconds by device_type48 rows
05001,000241.7smart_lo…16 rows220.5camera12 rows920.1sensor16 rows381.3gateway4 rows
access_duration_seconds48 rows, in bands of 200
08161614821111401,0001,800access_duration_seconds →

Median 291, from 54 to 1,800.

failure_reason32 rows with a value · 48 left blank
  1. invalid credentials11
  2. device offline9
  3. network timeout3
  4. user not authorized3
  5. no access rights2
  6. access revoked2
  7. device not responding1
  8. connection timed out1
20 columns by typefrom the column list below
  • string 16
  • integer 1
  • float 2
  • datetime 1

Columns

20 columns in three groups
blueprint · 20 columns
columntypedescriptionexample
Text 16 columns
log_idstringUnique identifier for each remote access log eventuniquea9b2c3d4-e1f2-4467
property_idstringUnique identifier for the property being accessedPROP1001
property_street_addressstringStreet address of the propertyoptional150 Oakridge Ave
property_citystringCity where the property is locatedoptionalAustin
property_statestringState or region where the property is locatedoptionalTX
property_postal_codestringPostal or ZIP code of the propertyoptional78745
property_countrystringCountry where the property is located4 countries · optionalUSA
device_idstringUnique identifier for the IoT device managing the accessDEV-LOCK-001
device_typestringType of IoT device (e.g., smart lock, camera, sensor)smart_lock · camera · sensor · gateway · othersmart_lock
user_idstringUnique identifier for the user or workforce member initiating accessUSR-TCH-001
user_rolestringRole of the user (e.g., technician, cleaner, manager, guest)technician · cleaner · manager · guest · other · optionaltechnician
access_methodstringHow access was granted (e.g., mobile app, web portal, scheduled, manual override)6 valuesmobile_app
access_resultstringResult of the access attempt (e.g., success, failure, timeout, denied)success · failure · timeout · deniedsuccess
failure_reasonstringReason for failure if access_result is not 'success' (e.g., invalid credentials, device offline)8 reasons · optionalinvalid credentials
remote_ipstringIP address from which the access was initiatedoptional192.168.1.101
notesstringAdditional notes or comments about the access eventoptionalRoutine cleaning
Numbers 3 columns
access_duration_secondsintegerDuration of the access session in seconds (if applicable)0 or more · optional220
geo_latitudefloatLatitude of the IoT device or access point (if available)-90 to 90 · optional30.2301
geo_longitudefloatLongitude of the IoT device or access point (if available)-180 to 180 · optional-97.7685
Dates and times 1 column
event_timestampdatetimeDate and time when the remote access event occurred (in UTC)2024-06-01T08:23:15Z

Use it for

  • median access …29148 rowsmean access duration …241.7smar…220.5came…920.1sens…381.3gate…

    A technology dashboard

    Access_duration_seconds by device_type and a breakdown of failure_reason. Excel, Power BI or Tableau.

  • Why do the 16 sensor rows have a mean access_duration_seconds of 920.1?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable logs with event_timestamp, property_id and property_street_address to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 20 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 dataset80 rows20 columns
Yours1,000 rows20 columnsproperty_street_address: UK only

blueprint · iot-enabled-remote-access-logs

Behind this dataset

Same schema. As many rows as you need.

These 80 rows came out of a blueprint — 20 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 access event (entry or exit).
  • Event status must be 'authorized', 'denied', or 'error'.
  • Log includes access method (app, keycard, biometric, manual override).
  • Property type must be 'office', 'warehouse', or 'data center'.
  • Timestamps must reflect diverse hours, including off-peak.
  • User role is specified (employee, contractor, vendor, visitor).
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-enabled-remote-access-logs

What should your data show?

Preview 20 rows free
No signup. No card.