Federal authorities arrested a 58-year-old Colorado Springs man after unravelling the origin of a "Declaration Of War" that threatened harm or death to Elon Musk, owners of his Tesla vehicles, and members of President Donald Trump's Cabinet.
Sure he’s dumb but his failure gives an interesting insight into how wide the US dragnet on its citizens is. A mail address used to apply for unemployment has been indexed somewhere « just in case ». Nice.
Storage and indexing is cheap. From a usability perspective indexing makes sense: call centre staff can tell someone why their unemployment application has been denied/delayed etc.
From a security perspective, Google, Proton, and friends want to track failed login IPs so they can assign (internal) reputation scores to incoming requests.
It’s the sharing & cross enrichment that would bother me. That your unemployment office keeps a CRM with the info makes sense. That LEA has it all and more together with the gods know what else is what I would object to.
Same for how service providers store that info; there’s a fine line between storing enough and too much. Or too long. And not everything needs to be tied forever to the customer ; sometimes a hash or whatever does wonder for the legitimate purpose. Storing more is often « just in case I can market the data later » which I’m personally not agreeing with.
Sure he’s dumb but his failure gives an interesting insight into how wide the US dragnet on its citizens is. A mail address used to apply for unemployment has been indexed somewhere « just in case ». Nice.
Storage and indexing is cheap. From a usability perspective indexing makes sense: call centre staff can tell someone why their unemployment application has been denied/delayed etc.
From a security perspective, Google, Proton, and friends want to track failed login IPs so they can assign (internal) reputation scores to incoming requests.
It’s the sharing & cross enrichment that would bother me. That your unemployment office keeps a CRM with the info makes sense. That LEA has it all and more together with the gods know what else is what I would object to. Same for how service providers store that info; there’s a fine line between storing enough and too much. Or too long. And not everything needs to be tied forever to the customer ; sometimes a hash or whatever does wonder for the legitimate purpose. Storing more is often « just in case I can market the data later » which I’m personally not agreeing with.