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 week

No rise: 0 in the week of 26 Oct 2026, against an average of 0 over the 4 weeks before.

Week of 10 Aug 2026: 0Week of 17 Aug 2026: 0Week of 24 Aug 2026: 0Week of 31 Aug 2026: 0Week of 7 Sep 2026: 0Week of 14 Sep 2026: 0Week of 21 Sep 2026: 0Week of 28 Sep 2026: 0Week of 5 Oct 2026: 0Week of 12 Oct 2026: 0Week of 19 Oct 2026: 0Week of 26 Oct 2026: 0Week of 2 Nov 2026: 0 10 Aug17 Aug24 Aug31 Aug7 Sep14 Sep21 Sep28 Sep5 Oct12 Oct19 Oct26 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