New answers tagged logging
SOX has a 7-year requirement. This PDF might not be authorative, but it highlights the matrix of best-practices between various requirements.
Snort certainly supports multiple, simultaneous log targets. I think in your desired use case the possibility may hinge on your rulesets and how you want them to log. I have never done it this way and don't have a need/desire to. Have a look at http://manual.snort.org/node21.html. This link details the Snort output options.
OAuth2 would be a nice protocol to use in this case. The consumer (e.g. accountant) will try to access data (some URL you provide) and the service provider (bank) will ask the consumer to provide an authorization token. You will provide the consumer with a token you obtained from the service provider. Upon seeing this, the service provider can then allow the ...
0x9fe513a40a2e169f9930d21b6b0a669d looks an awful lot like the output of MD5, but you can't be sure since the point of cryptography is to have random-looking output. Basically, the length and the characters look like the output of MD5, and MD5 is one of the more common algorithms, so that's why I'd guess that. MD5("udg47cj6"), however, does not output your ...
I appreciate where you're coming from, but this is actually very dangerous in a production system. While it might be kosher if 100% of all failed password attempts were in fact random evil people trying to break into your system, the fact is that a lot of bad passwords are actually going to be legitimate users making simple typos. And there's the rub: if ...
Top 50 recent answers are included