4 ms·
Yeah it is odd. You decided to hit my server, I should be able to record the occurance. How am I suppposed to deflect DoS attacts if I can't maintain a list of
by ehnto 8y ago
Yeah it is odd. You decided to hit my server, I should be able to record the occurance. How am I suppposed to deflect DoS attacts if I can't maintain a list of nefarious IPs. I know that's a fairly low tech attack, but they still happen constantly. Is Fail2Ban no longer compliant?
I wouldn't be surprised if some policies pertaining to record keeping in some sectors contradict that requirement as well.
- IanCal 8y agoNot sure about this law but that sounds completely fine under GDPR. You need to keep your log files secure and not longer than necessary for what youre doing though. https://termsfeed.com/blog/gdpr-recitals/#Recital_49_8211_Ensuring_Network_Security_as_a_Legitimate_Interest https://termsfeed.com/blog/gdpr-recitals/#Recital_49_8211_En...
- Angostura 8y agoYou can do all those things under GDPR as they are required for the running of the service
- bryanrasmussen 8y agoTo deflect a DoS attack you should not need the records for an extended amount of time. There is no reason why you cannot specify you are keeping records for security purposes and getting rid of them when no longer pertinent.
- deleted 8y ago[deleted]
- elliekelly 8y agoYou absolutely can still maintain that list under CCPA. What you can't do is sell your list of nefarious IP addresses. You could sell (or buy) the service of checking various IP addresses against a proprietary list of nefarious IP addresses.