I’m trying to bring awareness around the need for authentication with encryption by using software to alert and report on failed MAC verification attempts, and sharing the results with middle management.
I’m not a cryptographer, but I see the value in a proper implementation. Ideally I’d like to create a report that says X attacks were prevented.
Is this a valid idea, or is it overly simplistic? If not, where should I start in implementing it? (Low level AES, PGP, etc?)
Here is a C# MAC code sample that could be modified to alert or log when authentication fails. This is an incomplete sample that shouldn’t be used AS-IS since many other details need to be considered before implementing
Authenticate-then-Encrypt (AtE)orEncrypt-then-Authenticate (EtA)It would be nice to know what performance counter, log file, or DLL
exceptionrelates to this error. I’ll be investigating BouncyCastle to see where the corresponding exception is.