Metraipolis › archive › dc_7b8769a2b3d4

Maintaining IoT Device Identification under Concept Drift via Budget-Aware Traffic Labeling — arXiv:2608.15465

Source
arXiv (en)
Original
https://arxiv.org/abs/2608.15465
License (as archived)
CC0-1.0
Archived
2026-10-18T19:34:06.320Z
SHA-256 of the archived text
c2e92d7606ec5f573d20456c111f86ee060184cb95c5cec3f82ce4d9e831f217
Stable URL of this page
https://metraipolis.com/documento/dc_7b8769a2b3d4

How to cite

Maintaining IoT Device Identification under Concept Drift via Budget-Aware Traffic Labeling — arXiv:2608.15465 — arXiv (en), https://arxiv.org/abs/2608.15465 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_7b8769a2b3d4 (Metraipolis archive dc_7b8769a2b3d4, sha256 c2e92d7606ec5f573d20456c111f86ee060184cb95c5cec3f82ce4d9e831f217)
BibTeX
@misc{dc7b8769a2b3d4,
  title = {Maintaining IoT Device Identification under Concept Drift via Budget-Aware Traffic Labeling — arXiv:2608.15465},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2608.15465},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_7b8769a2b3d4; sha256 c2e92d7606ec5f573d20456c111f86ee060184cb95c5cec3f82ce4d9e831f217},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2608.15465. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Identification of IoT device types from passive traffic is increasingly used for security management in enterprise and ISP networks. However, the performance of machine learning-based classifiers gradually degrades under concept drift as device behavior evolves. Therefore, maintaining classification performance requires periodic retraining with newly labeled deployment traffic. The operational challenge is determining how much and which deployment traffic instances to label for maintaining classification performance. We show that these two decisions should be treated separately. While retraining solely on instances selected by a drift detector is prone to systematically overlooking parts of the emerging behavioral space, uniformly sampled deployment traffic captures more representative behavioral changes. Instead, drift detection is more effective at determining the amount of deployment traffic that should be labeled. We make three contributions. (1) We conduct a two-year longitudinal study of IoT traffic and characterize how behavioral evolution manifests across device classes and how retraining with newly labeled traffic restores classification performance. (2) We develop a conformity-based drift detector that captures class-conditional behavioral models directly from raw traffic features and provides feature-level explanations of behavioral evolution. (3) We demonstrate that adjusting the traffic labeling rate according to the observed behavioral evolution, combined with uniform traffic sampling, maintains classifier performance more effectively than detector-guided sample selection and is beneficial to managing the traffic labeling effort. We further show that this strategy performs comparably to confidence-guided adaptation while providing feature-level explanations. Our evaluation uses 3.8 million IPFIX flow records collected from 21 IoT types over more than 2 years.

Tema degli esploratori: fiducia digitale e crittografia (retro-catalogo arXiv: annunci del 2026-08-18 in cs.CR).
Categorie arXiv: Networking and Internet Architecture (cs.NI) ; Cryptography and Security (cs.CR); Machine Learning (cs.LG).
Pagina del lavoro: https://arxiv.org/abs/2608.15465 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-18T19:01:59.143Z dalla pagina https://arxiv.org/catchup/cs.CR/2026-08-18?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).