conv.

All stories
SecurityQuiet 13d · day 13

ICE agents allegedly exposed searching crowd-sourced agent database

A viral post claims immigration enforcement officers searched their own names in a crowd-sourced list, potentially revealing their identities.

What to know

  • A Mastodon post alleges ICE agents used work computers to search themselves in a crowd-sourced database of immigration enforcement officers.
  • The incident illustrates a basic operational security failure: interactive databases log user queries, exposing those who search them.
  • Security experts in the thread note the broader risk of entering PII into databases, even ones designed to check for compromises.

The dispute Whether the incident is primarily a failure of individual agents to understand basic security, or symptomatic of a broader design risk in interactive databases that collect user data. · positions read across 5 posts and comments

many voices

This reflects a basic lack of cybersecurity knowledge among law enforcement.

  • “What having zero understanding of one's tools does to someone. It's an interactive service. That's an obvious risk.”

    lispi314@udongein.xyz · Mastodon ↗
some voices

The real problem is that interactive databases inherently collect data about who searches them, creating a trap for users.

  • “This is why I never type my PII into a "have you been pawned" website. "Here, has your social security number been stolen? TYPE YOUR FULL NAME AND SOCIAL SECURITY NUMBER IN THIS FORM"”

    ai6yr@m.ai6yr.org · Mastodon ↗

ICE (Immigration and Customs Enforcement) Agency implicated in security incident

ICE agents allegedly exposed searching crowd-sourced agent database
social.vivaldi.net

How it unfolded 3 developments, newest first · click a bar or a number to jump posts

Peak 2 pieces in 3h at Oct 29, 3 PM; 5 pieces over 13 days (5 posts) Oct 29, 3 PM — 2 pieces · 2 posts — Mastodon 2Oct 29, 6 PM — 2 pieces · 2 posts — Mastodon 2Oct 29, 9 PM — quietOct 30, 12 AM — 1 piece · 1 post — Mastodon 1Oct 30, 3 AM — quietOct 30, 6 AM — quietOct 30, 9 AM — quietOct 30, 12 PM — quietOct 30, 3 PM — quietOct 30, 6 PM — quietOct 30, 9 PM — quietOct 31, 12 AM — quietOct 31, 3 AM — quietOct 31, 6 AM — quietOct 31, 9 AM — quietOct 31, 12 PM — quietOct 31, 3 PM — quietOct 31, 6 PM — quietOct 31, 9 PM — quietNov 1, 12 AM — quietNov 1, 2 AM — quietNov 1, 5 AM — quietNov 1, 8 AM — quietNov 1, 11 AM — quietNov 1, 2 PM — quietNov 1, 5 PM — quietNov 1, 8 PM — quietNov 1, 11 PM — quietNov 2, 2 AM — quietNov 2, 5 AM — quietNov 2, 8 AM — quietNov 2, 11 AM — quietNov 2, 2 PM — quietNov 2, 5 PM — quietNov 2, 8 PM — quietNov 2, 11 PM — quietNov 3, 2 AM — quietNov 3, 5 AM — quietNov 3, 8 AM — quietNov 3, 11 AM — quietNov 3, 2 PM — quietNov 3, 5 PM — quietNov 3, 8 PM — quietNov 3, 11 PM — quietNov 4, 2 AM — quietNov 4, 5 AM — quietNov 4, 8 AM — quietNov 4, 11 AM — quietNov 4, 2 PM — quietNov 4, 5 PM — quietNov 4, 8 PM — quietNov 4, 11 PM — quietNov 5, 2 AM — quietNov 5, 5 AM — quietNov 5, 8 AM — quietNov 5, 11 AM — quietNov 5, 2 PM — quietNov 5, 5 PM — quietNov 5, 8 PM — quietNov 5, 11 PM — quietNov 6, 2 AM — quietNov 6, 5 AM — quietNov 6, 8 AM — quietNov 6, 11 AM — quietNov 6, 2 PM — quietNov 6, 5 PM — quietNov 6, 8 PM — quietNov 6, 11 PM — quietNov 7, 2 AM — quietNov 7, 5 AM — quietNov 7, 8 AM — quietNov 7, 11 AM — quietNov 7, 2 PM — quietNov 7, 5 PM — quietNov 7, 8 PM — quietNov 7, 11 PM — quietNov 8, 2 AM — quietNov 8, 5 AM — quietNov 8, 8 AM — quietNov 8, 11 AM — quietNov 8, 2 PM — quietNov 8, 5 PM — quietNov 8, 8 PM — quietNov 8, 11 PM — quietNov 9, 2 AM — quietNov 9, 5 AM — quietNov 9, 8 AM — quietNov 9, 11 AM — quietNov 9, 2 PM — quietNov 9, 5 PM — quietNov 9, 8 PM — quietNov 9, 11 PM — quietYesterday, 2 AM — quietYesterday, 5 AM — quietYesterday, 8 AM — quietYesterday, 11 AM — quietYesterday, 2 PM — quietYesterday, 5 PM — quietYesterday, 8 PM — quietYesterday, 11 PM — quietToday, 2 AM — quietToday, 5 AM — quietToday, 8 AM — quietToday, 11 AM — quietToday, 2 PM — quietToday, 5 PM — quiet 1–3
Oct 30Oct 31Nov 1Nov 2Nov 3Nov 4Nov 5Nov 6Nov 7Nov 8Nov 9yesterdaynow · 8:59 PM ET
  1. background

    Critics compare incident to lack of operational security awareness — Commentary characterizes the incident as reflecting poor understanding of cybersecurity tools and operational security practices.

  2. 3

    Observers note interactive services inherently log queries

    An analysis points out that the fundamental design of interactive databases—logging user searches—creates an obvious security risk that should be understood by trained agents.

    “What having zero understanding of one's tools does to someone. It's an interactive service. That's an obvious risk.”
    — lispi314@udongein.xyz
    • What having zero understanding of one's tools does to someone. It's an interactive service. That's an obvious risk. source: https://social.vivaldi.net/@xtaldave/117526018053115068 @ xtaldave

      lispi314@udongein.xyzMastodon12d agoview on Mastodon ↗
  3. 2

    Security concerns raised about data collection risks

    A commenter highlights the broader cybersecurity risk of entering personally identifiable information into interactive databases, noting the irony of being asked to provide sensitive data to check if it was compromised.

    “This is why I never type my PII into a "have you been pawned" website. "Here, has your social security number been stolen? TYPE YOUR FULL NAME AND SOCIAL SECURITY NUMBER IN THIS FORM"”
    — ai6yr@m.ai6yr.org
    • ai6yr@m.ai6yr.org

      This is why I never type my PII into a "have you been pawned" website. "Here, has your social security number been stolen? TYPE YOUR FULL NAME AND SOCIAL SECURITY NUMBER IN THIS FORM" https:// social.vivaldi.net/@xtaldave/1 17526018053115068 # cybersecurity

      ai6yr@m.ai6yr.orgMastodon13d ago77▲view on Mastodon ↗
    2 more of the top 3 · 3 posts in this stretch
    • SrRochardBunson

      RE: https:// social.vivaldi.net/@xtaldave/1 17526018053115068 😅 :success:

      SrRochardBunsonMastodon13d ago17▲view on Mastodon ↗
    • vruz@mstdn.social

      This is roughly equivalent to the Johnny English class of American cops. https:// social.vivaldi.net/@xtaldave/1 17526018053115068

      vruz@mstdn.socialMastodon13d agoview on Mastodon ↗
    all of them →
  4. 1

    Claim surfacesICE agents search crowd-sourced agent list from work computers

    A post on Mastodon claims that ICE agents searched a crowd-sourced database of ICE agent names using their work computers, apparently to check if they were listed.

    “ICE agents: search a crowd sourced ICE agent list for their own names from their work computers.”
    — xtaldave@vivaldi.net
    • ICE agents: search a crowd sourced ICE agent list for their own names from their work computers. Crowd sourced ICE agents website: _yoink_

      xtaldave@vivaldi.netMastodon13d ago129▲view on Mastodon ↗

What people are saying 0 voices from 0 sites · best of 5 · verbatim