News for hackers. Stuff that matters.
Re:An incident impacting 5M accounts and private information... by tick_tock_tick on Tuesday August 09, 2022 @02:27PM (#32401859)
No that's not valid at all! You must remove any trace of your ability to backwards engineering the IPs. Hashing isn't sufficient since it's so easy to run over the whole IPv4 space. This is one of the trade offs.
Re:An incident impacting 5M accounts and private information... by 0x0 on Tuesday August 09, 2022 @03:55PM (#32403379)
You could probably make the argument that you need to store http logs with cleartext IP addresses for more than 30 days for operational security and fraud detection reasons. I would certainly consider 180+ days of cleartext IP addresses quite necessary to be able to react to any security or abuse incidents.
Re:An incident impacting 5M accounts and private information... by zaarn on Tuesday August 09, 2022 @02:38PM (#32402064)
You can if the hash collides within the IPv4 address space; ie it's a hash of less than about 16 bits. Enough to let your roughly see if something fishy is going on but you can't reverse engineer to any specific IP, only a set of 64 thousand.
Re:An incident impacting 5M accounts and private information... by tick_tock_tick on Tuesday August 09, 2022 @05:30PM (#32404583)
That isn't good enough. By taking that hash and old request data combined with your current request logs it's enough to de-anonymization a significant portion of those logs making you not in compliance.
Re:An incident impacting 5M accounts and private information... by zaarn on Wednesday August 17, 2022 @04:36AM (#32493830)
Data from the past few days we do have a legitimate interest in; protecting our network. If someone is spamming us we need to be able to find out who did it and the only way to do that is deanonymized logs to begin with. Atleast in my workplace we have worked with the DPA to ensure that we are in compliance and there is no issue in keeping around 7 days of IP logs without further anonymization. All or long term logs are hashed below the bit minimum, and that can't be paired with old request data as easily since we strip all but major version identifiers from User Agents, for example.
Re:An incident impacting 5M accounts and private information... by heurisko on Tuesday August 09, 2022 @02:51PM (#32402251)
Wouldn't salting mitigate this?
Re:An incident impacting 5M accounts and private information... by 0x457 on Tuesday August 09, 2022 @04:09PM (#32403551)
If something uniquely identifies someone, it's considered a PII and a salted (but still useful) hash of the IP address is that. At least under GDPR. That means you will need to throw away the salt and have different salt for every instance. At that point, you might as well replace with a random string, and that isn't very useful.

"In the context of the European GDPR the Article 29 Working Party has stated that while the technique of salting and then hashing data “reduce[s] the likelihood of deriving the input value,” because “calculating the original attribute value hidden behind the result of a salted hash function may still be feasible within reasonable means,” the salted-hashed output should be considered pseudonymized data that remains subject to the GDPR."

Under CCPA, I think that is enough, HOWEVER, business must implement business processes that specifically prohibit reidentification. So again, not useful at all in this case.

The question should be is IP address a PII or not. Under CCPA and GDPR it is, but only if it “identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household.”