IoT-deNAT: Outbound flow-based network traffic data of IoT and non-IoT devices behind a home NAT

Open data API in a single place

Provided by Zenodo

Get early access to IoT-deNAT: Outbound flow-based network traffic data of IoT and non-IoT devices behind a home NAT API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2020.07.23 00:00
Created
2020.07.01
Available languages
English
Keywords
Internet of Things (IoT), network traffic data, NetFlow, device identification, Network Address Translation (NAT), deNAT
Quality scoring

Dataset description

This dataset is comprised of NetFlow records, which capture the outbound network traffic of 8 commercial IoT devices and 5 non-IoT devices, collected during a period of 37 days in a lab at Ben-Gurion University of The Negev. The dataset was collected in order to develop a method for telecommunication providers to detect vulnerable IoT models behind home NATs. Each NetFlow record is labeled with the device model which produced it; for research reproducibilty, each NetFlow is also allocated to either the "training" or "test" set, in accordance with the partitioning described in: Y. Meidan, V. Sachidananda, H. Peng, R. Sagron, Y. Elovici, and A. Shabtai, A novel approach for detecting vulnerable IoT devices connected behind a home NAT, Computers & Security, Volume 97, 2020, 101968, ISSN 0167-4048, https://doi.org/10.1016/j.cose.2020.101968. (http://www.sciencedirect.com/science/article/pii/S0167404820302418)   Please note: The dataset itself is free to use, however users are requested to cite the above-mentioned paper, which describes in detail the research objectives as well as the data collection, preparation and analysis. Following is a brief description of the features used in this dataset.   # NetFlow features, used in the related paper for analysis 'FIRST_SWITCHED': System uptime at which the first packet of this flow was switched 'IN_BYTES': Incoming counter for the number of bytes associated with an IP Flow 'IN_PKTS': Incoming counter for the number of packets associated with an IP Flow 'IPV4_DST_ADDR': IPv4 destination address 'L4_DST_PORT': TCP/UDP destination port number 'L4_SRC_PORT': TCP/UDP source port number 'LAST_SWITCHED': System uptime at which the last packet of this flow was switched 'PROTOCOL': IP protocol byte (6: TCP, 17: UDP) 'SRC_TOS': Type of Service byte setting when there is an incoming interface 'TCP_FLAGS': Cumulative of all the TCP flags seen for this flow   # Features added by the authors 'IP': Prefix of the destination IP address, representing the network (without the host) 'DURATION': Time (seconds) between first/last packet switching   # Label 'device_model': <type>.<manufacturer>.<model number>   # Partition 'partition': Training or test   # Additional NetFlow features (mostly zero-variance) 'SRC_AS': Source BGP autonomous system number 'DST_AS': Destination BGP autonomous system number 'INPUT_SNMP': Input interface index 'OUTPUT_SNMP': Output interface index 'IPV4_SRC_ADDR': IPv4 source address 'MAC': MAC address of the source   # Additional data 'category': IoT or non-IoT 'type': IoT, access_point, smartphone, laptop 'date': Datepart of FIRST_SWITCHED 'inter_arrival_time': Time (seconds) between successive flows of the same device (identified by its MAC address)
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks