Part IX: Radar, Lidar, Depth, Thermal, Event, and RF Sensing
Chapter 47: RF and Wireless Sensing

Privacy implications of ubiquitous RF sensing

"A camera has a lens you can cover and a red light you can watch for. The router in your hallway has neither, sees through the wall, and was already in the house. I am told this is a feature."

A Reluctant AI Agent

Prerequisites

This section closes Chapter 47, so it assumes the sensing capabilities the earlier sections built: presence and activity from channel state information (Section 47.2), pose and vital-sign reconstruction from Wi-Fi (Section 47.3), through-wall and multi-person sensing (Section 47.4), and the sensing amendment IEEE 802.11bf (Section 47.5). It connects to the biometric-privacy thread introduced for wearables in Chapter 34 and to the technical privacy machinery of Chapter 64. No new signal-processing background is needed; the work here is threat modeling and mitigation.

Why a communication link became a surveillance device

Every capability in this chapter shares one uncomfortable property: it needs no cooperation from the person being sensed and no dedicated hardware. The transmitter and receiver are already installed, already powered, and already legal, because they were sold as a router and a phone. Once IEEE 802.11bf turns opportunistic CSI sensing into a standardized, on-by-default service (Section 47.5), the number of rooms that can be monitored jumps from a handful of research testbeds to essentially every space with Wi-Fi. That is the privacy story in one sentence: a modality that reconstructs breathing rate, gait, keystrokes, and coarse pose is about to become ambient infrastructure. Unlike a camera, it has no obvious aperture to cover, it penetrates drywall, and it produces no image a person can point to and say "that is me." This section builds the threat model, quantifies what leaks, and shows the defenses that actually move the needle, because "the data was only a channel estimate" is not a privacy argument.

What actually leaks, and how sensitive it is

What an RF sensing adversary recovers is not one thing but a ladder of increasingly personal inferences, each built from the same CSI stream. At the bottom sits occupancy: is anyone home, and roughly how many people. One rung up is activity and gait, which is quasi-biometric because walking style identifies individuals across sessions with useful accuracy. Higher still are vital signs, the sub-millimeter chest displacement of breathing and heartbeat that Section 47.3 extracted, which are health data in every regulatory sense. Near the top are fine motor signals: several published attacks recover typed keystrokes and even PINs from the multipath perturbations of finger motion. Why this ordering matters is that mitigation cost and legal exposure both climb the ladder, and a system provisioned only to detect a fall may leak vital signs it never intended to collect.

How to reason about the leak quantitatively is to treat each inference as a channel with a bit rate. A useful lens is mutual information between the private attribute \(A\) (identity, health state, keystroke) and the observable feature \(X\) (a window of CSI),

$$I(A; X) = H(A) - H(A \mid X),$$

where a privacy defense succeeds insofar as it drives \(I(A; X)\) toward zero while preserving \(I(T; X)\) for the intended task \(T\). This framing, developed with the estimation vocabulary of Chapter 4, is what separates a real defense from cosmetic obfuscation: adding noise that any classifier learns to ignore lowers neither term and buys nothing. When the distinction bites hardest is under function creep, where a link deployed for a benign task is later repurposed. Because the raw CSI already contains the whole ladder, the constraint has to live in the pipeline, not in the operator's good intentions.

RF sensing breaks the assumptions consent frameworks rely on

Most privacy law and UX design assume the sensed party can perceive the sensor, is within its line of sight, and can withhold consent by leaving or covering it. Ubiquitous RF sensing violates all three. It works through walls, so the sensed person may be in a different room or a neighboring apartment; it leaves no visible trace, so there is no red light to notice; and it rides on infrastructure the person cannot switch off without losing connectivity. A visitor, a child, a delivery courier, and the neighbor next door never agreed to anything and cannot opt out. This is why RF sensing is not "just another camera problem." The camera's social contract (you can see it, so you know to behave as if watched) simply does not transfer, and any governance model that assumes it will fail silently.

The adversary and attack surface

What a threat model needs is a clear picture of who can do the sensing. There are three distinct adversaries, and they call for different defenses. The first-party adversary owns the access point: a landlord, an employer, or a smart-home vendor who legitimately controls the radio and can quietly enable sensing. The second-party adversary is a co-tenant or houseguest who runs sensing on the shared network against another occupant. The third-party adversary owns nothing on the link and instead eavesdrops, placing a passive receiver nearby to read the CSI perturbations of a victim's traffic, or in the through-wall case sensing a target who is not even using the attacker's network. Why the third-party case is the most alarming is that it needs no account, no credential, and no cooperation; the victim's own devices radiate the signal, and physics does the rest, which connects this to the spoofing-and-adversary mindset of Chapter 68.

The apartment wall that was never a boundary

Consider a mid-rise apartment where tenant A installs a commodity mesh Wi-Fi kit. A security researcher in the adjacent unit, tenant B, runs a passive CSI logger tuned to A's channel. Because 5 GHz Wi-Fi passes through a single interior drywall partition with only moderate attenuation, B recovers a coarse presence-and-motion trace of A's living room: when A is home, when A paces, and, over quiet nights, a low-frequency oscillation consistent with breathing during sleep. B never touched A's network, never saw A, and broke no lock. The only "sensor" involved was A's own router radiating through a wall that stops sound and light but not 5 GHz RF. This is the through-wall privacy scenario of Section 47.4 reframed as an attack, and it is why perimeter-based intuitions about privacy do not hold for RF.

Defenses that actually reduce the leak

What works is a layered stack, because no single control covers all three adversaries. At the physical layer, geofencing the sensing region and reducing transmit power or nulling energy toward exterior walls shrinks the through-wall surface, and the 802.11bf design includes signaling so a station can decline to participate in sensing measurements. At the signal layer, deliberate obfuscation injects structured perturbations, randomized artificial motion or crafted interference, that raise \(H(A \mid X)\) for sensitive attributes while a whitelisted task model, trained on the same perturbation, still reads \(I(T; X)\). At the learning layer, the private attribute is scrubbed by adversarial representation learning: train an encoder whose features predict the intended task but on which an adversary head cannot recover identity or vitals, a min-max objective in the spirit of the fair-representation and federated methods of Chapter 64. At the governance layer, process the CSI on-device and emit only the minimal task label, so no reconstructable stream ever leaves the room; this data-minimization posture is the same one the regulation survey of Chapter 70 recommends across sensing modalities.

How to check whether a defense is real, rather than security theater, is to run the adversary yourself and measure the residual leak. The snippet below sketches the audit: fit a simple attribute classifier on protected features and report how far above chance it lands. Why this belongs in every RF sensing project is that leakage is empirical; a defense that looks principled can still leave a linearly decodable identity signal, and the only way to know is to try to decode it. The result also feeds the leakage-safe evaluation thread, because splitting by person and environment (never by random window) is what keeps the audit honest.

import numpy as np
from sklearn.linear_model import LogisticRegression
from sklearn.model_selection import GroupKFold
from sklearn.metrics import accuracy_score

def privacy_leakage(features, secret_labels, person_ids):
    """Estimate how recoverable a 'secret' attribute is from protected features.
    Leakage = adversary accuracy minus a majority-class baseline. ~0 is good."""
    gkf = GroupKFold(n_splits=5)
    accs, base = [], []
    for tr, te in gkf.split(features, secret_labels, groups=person_ids):
        clf = LogisticRegression(max_iter=1000).fit(features[tr], secret_labels[tr])
        accs.append(accuracy_score(secret_labels[te], clf.predict(features[te])))
        vals, counts = np.unique(secret_labels[tr], return_counts=True)
        base.append(np.mean(secret_labels[te] == vals[counts.argmax()]))
    return float(np.mean(accs) - np.mean(base))   # residual leakage above chance

# leak near 0  -> attribute is well protected; leak >> 0 -> the defense failed
A minimal privacy-leakage audit: an adversary classifier tries to recover a sensitive attribute (identity, health state) from the features a system exports, scored above a majority baseline with person-grouped splits so leakage is not confused with memorized windows.

Adversarial scrubbing without hand-rolling the min-max loop

Building the adversarial-representation defense from scratch means writing a gradient-reversal layer, two optimizers, and a fragile min-max schedule, easily 120 or more lines before it trains stably. Libraries such as IBM's adversarial-robustness-toolbox and the fairness toolkit fairlearn provide the scrubbing objective and the leakage metrics as configured components, cutting the defense-plus-audit harness to roughly 15 lines. The library owns the gradient reversal, the alternating updates, and the metric plumbing; you supply the encoder, the task head, and the attribute you want made unrecoverable.

Where the field is right now

As of 2026 the sharpest open problems sit at the collision of standardization and defense. IEEE 802.11bf makes sensing a first-class, negotiable service, so the frontier question is whether privacy controls (opt-out signaling, sensing-region attestation, measurement-scope limits) can be baked into the protocol rather than bolted on. On the attack side, recent work shows that generative reconstruction (mapping CSI to full-body pose and to inferred vital-sign waveforms) keeps improving, which means the leak ceiling is rising, not falling. The countervailing frontier is certified obfuscation: perturbation schemes with provable bounds on \(I(A; X)\) under a defined adversary class, borrowing differential-privacy machinery from Chapter 64. No deployed system yet offers such a certificate, and that gap is the most consequential unsolved problem in the modality.

Exercise

Take a Widar3.0 subset (the same data as this chapter's lab). Train two heads on a shared CSI encoder: a gesture classifier (the intended task) and a person-identity classifier (the adversary). First measure identity accuracy with a plain encoder. Then add a gradient-reversal branch on identity and retrain. Report the trade-off curve: gesture accuracy versus residual identity leakage as you scale the adversarial weight. At what point does protecting identity start to cost task performance you cannot afford?

Self-check

  1. Name the three adversary classes for RF sensing and state which one needs no access to the victim's network.
  2. Why does the standard camera privacy model (visible sensor, line of sight, coverable) fail to transfer to Wi-Fi sensing?
  3. In terms of \(I(A; X)\) and \(I(T; X)\), what does a good privacy defense do to each quantity, and why is injecting random noise usually insufficient?

Lab 47

build a Wi-Fi CSI activity-recognition model (Widar3.0) and test cross-environment generalization.

What's Next

In Chapter 48, we leave single-modality sensing behind and open Part X on sensor fusion, where RF, radar, lidar, and vision stop being rivals and start being complementary evidence about one world. The privacy tension does not vanish there; it compounds, because fusing weak modalities can reconstruct what each alone would have hidden. Carry the leakage-audit reflex forward.

Bibliography

Sensing capability and reconstruction (the leak surface)

Zhang, Y. et al. (2019). Widar3.0: Zero-Effort Cross-Domain Gesture Recognition with Wi-Fi. MobiSys / IEEE TPAMI.

The cross-domain gesture dataset and BVP method behind the lab; its very robustness is what makes RF sensing a durable privacy concern, not a lab curiosity.

Geng, J., Huang, D., De la Torre, F. (2023). DensePose From WiFi. arXiv:2301.00250.

Reconstructs dense human body pose from ordinary Wi-Fi signals, a vivid demonstration of how much personal detail a communication link exposes.

Wang, W. et al. (2015). Understanding and Modeling of WiFi Signal Based Human Activity Recognition (CARM). MobiCom.

The CSI-speed model that made activity recognition from Wi-Fi rigorous; foundational for reasoning about what activities are recoverable.

Attacks: keystrokes, identity, and eavesdropping

Ali, K. et al. (2015). Keystroke Recognition Using WiFi Signals (WiKey). MobiCom.

Recovers typed keys from CSI perturbations of finger motion; the canonical evidence that RF sensing reaches fine-grained, high-sensitivity inference.

Zeng, Y., Pathak, P., Mohapatra, P. (2016). WiWho: WiFi-Based Person Identification in Smart Spaces. IPSN.

Identifies individuals by gait from Wi-Fi alone, establishing that RF activity data is quasi-biometric rather than anonymous.

Standardization and defenses

Restuccia, F. (2021). IEEE 802.11bf: Toward Ubiquitous Wi-Fi Sensing. arXiv:2103.14918.

The reference overview of the sensing amendment that turns opportunistic CSI sensing into standardized infrastructure, the trigger for the ubiquity concern.

Qiao, Y. et al. (2020). PhyCloak: Obfuscating Sensing from Communication Signals. NSDI.

A physical-layer obfuscation defense that perturbs sensing while preserving communication, an early template for the signal-layer mitigation stack.

Goodfellow, I., Shlens, J., Szegedy, C. (2015). Explaining and Harnessing Adversarial Examples. ICLR.

The adversarial-perturbation foundation underlying both the reconstruction attacks and the adversarial-representation defenses discussed here.