AI Risk Wire

Risks

Unlawful surveillance and biometric use

AI is used for biometric identification, emotion recognition, social scoring or tracking that the law forbids or restricts.

NIST AI 600-1 · Data PrivacyEU AI Act Art. 5

incidents (primary) · 1 more as secondary
0read for controls · 0 not yet
0fixes reported
0repeats after a fix

Incidents per day

0 on 1 Nov 2026; average of the 7 days before: 0.

4 Oct 2026: 05 Oct 2026: 06 Oct 2026: 07 Oct 2026: 08 Oct 2026: 09 Oct 2026: 010 Oct 2026: 011 Oct 2026: 012 Oct 2026: 013 Oct 2026: 014 Oct 2026: 015 Oct 2026: 016 Oct 2026: 017 Oct 2026: 018 Oct 2026: 019 Oct 2026: 020 Oct 2026: 021 Oct 2026: 022 Oct 2026: 023 Oct 2026: 024 Oct 2026: 025 Oct 2026: 026 Oct 2026: 027 Oct 2026: 028 Oct 2026: 029 Oct 2026: 030 Oct 2026: 031 Oct 2026: 01 Nov 2026: 02 Nov 2026: 0 6 Oct9 Oct12 Oct15 Oct18 Oct21 Oct24 Oct27 Oct30 Oct2 Novto date

Developers

Developer not named in the sources.

Where the chain broke

Part of the systemIncidents where the control was not effective or did not existIncidents where the control was effectiveIncidents where sources don't mention the controlIncidents not yet checked for controls
L1 Model
Model provider
L2 Harness
Agent framework vendor
L3 Application
Deployer
L4 Infrastructure / target
Organisation hit

Controls for this risk, by layer

ControlIncidents where the control was not effective or did not existIncidents where the control was effectiveIncidents where sources don't mention the controlMost common reason it was not effective
A person confirms biometric matches
L3 Application
Data minimisation
L3 Application
Legal check against prohibited uses
L3 Application
Risk assessment per deployment
L3 Application
Bias testing
L3 Application

5 of 5 controls for this risk not yet recorded as effective.

Fixes reported and what followed

No remediation reported for incidents of this risk.

Incidents

EffectiveNot effectiveNot effective (bypassed)Did not existNot stated in sourcesNot yet checkedAttacker's ownOrder: model · harness · application · target

DateIncidentRiskWhere it failedControls mentioned in sources
No incidents match.

Also under this risk as a secondary risk: LR-2026-0559