4 ms·
"Under GDPR, IP addresses can be considered PII, so it makes sense to set up an anonymizer for nginx ip address logs." One thing I wonder about is what you wou
by pmoriarty 7y ago
"Under GDPR, IP addresses can be considered PII, so it makes sense to set up an anonymizer for nginx ip address logs."
One thing I wonder about is what you would do if, say, you have an abuser on your site that you need to ban due to behavior detected after the fact through a log file.
If one needs their IP in order to ban them, but their IP is anonymized, what do you do?
- DiabloD3 7y agoOne way hash of the IP.
- jacquesm 7y agoThe search space is so small you can simply create a table with all of the hashes and use that to reverse the hash.
- thaumasiotes 7y agoMandatory IPv6 could finally be here! ;D
- GhettoMaestro 7y agoYou could always salt it.
- thaumasiotes 7y agoHow would that address the problem? Salts don't make hashes any less reversible.
- majewsky 7y agoSalts are only useful when you already know which hash to check e.g. because the user supplied the username that picks which password hash to check. When matching an IP against a list of salted hashes, you need to hash the input with every possible salt to compare against all hashes in the list. So for performance reasons, it's probably not feasible to use more than one salt (or a small number of salts). Then it's again very possible to reverse the list of salted hashes because the search space is number of all IP addresses times number of salts used, which is way less than the number of all hashes.
- EdwardDiego 7y agoYeah, we're GDPR bound and henceforth compliant, and nope, a one-way hash isn't sufficient. We just drop the last octet and accept it. I mean, we can still say 'this impression was from a user in Strasbourg', but we enrich the record with that enroute through our pipeline, about the same time as we drop the last octet of the IP.
- brightball 7y agoGDPR is supposed to allow retention of certain data for security purposes.
- bostik 7y agoThere is also the fact that GDPR cannot overrule industry specific regulations that mandate long-term retention. I work in gambling industry, and we are required by the regulations to keep ALL user information, including the KYC documents they submit, on file for a minimum of 5 years after their last activity. If you are looking for toxic data stores, this is among the worst ones there is. Limiting access to that data is crucial, and making sure it's not misused is mandatory. It could be worse. There are domains with more demanding data retention requirements: insurance and consumer finance in particular.
- jumpingmice 7y agoThere's nothing wrong with retaining full IP address information for the defined purpose of operating your site. Combining such information with other data to perform, say, ad targeting would be more problematic.
- bchanudet 7y agoIP alone is not considered personal data. If this is the only thing you store about a user on your website (for example for a static website), don't bother and keep it as it is. If you store anything else about the user (their firstname/lastname) and can make a relation between this and the IP (e.g. you can see that this IP went to the page myprofile.php?id=438098 at 23:10 yesterday), then you should already have somewhere where the user can see why you store their firstname/lastname. Just add "IP" to the list of data stored, for the purpose of maintaining your systems safe and accessible, warn that you'll store it for 30 days, because after the logs are purged, and then you're fine.
- Silhouette 7y agoOur current policy is to retain basic access logs, including IP addresses, potentially indefinitely. In GDPR terms, we have obvious legitimate interests in being able to identify repeat offenders trying to abuse our system in some way, in being able to identify recurring problems with how our systems are operating, and in tracking long term usage patterns. These interests combined with the very low risk of any adverse consequences should any of the relevant logs leak make our policy of indefinite retention in this specific instance compatible with GDPR in our view. Incidentally, we have in fact identified repeat abusers returning to our site several years later based on their access patterns and IP addresses as recorded in logs, so there is even an objectively demonstrable long-term threat should anyone ever want to question this policy.
- solidasparagus 7y agoI think you block the IP without correlating it to a given user. Pseudonymity seems like one of the most realistic ways of becoming GDPR compliant without losing the value of data.
- PeterStuer 7y agoIf you are a B2C site then banning based on IP in today's multi NAT layered internet with non-fixed IP's and mobile devices is probably going to be wildly ineffective and cause far more collateral damage than you think.