Going through the motions when we should be going through a checklist!

The risk of way too many error messages!
Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . .

For infotex, 2018 was the year of the “Aggressive Technology Plan.”

Something I’ve noticed, as we deploy too many new applications and such at once . . . even after testing . . . .

. . . if every time you log in,  you are greeted with one or two error messages, you stop reading those messages.  I realize that as a security professional I should not stop reading those messages, and I try to make myself slow down and ensure I’ve seen them before.  But I caught myself “blowing through them” this morning . . . I was in a hurry and a Client might have to wait on me if I read every error message . . .

. . . and thus this article.

Dan was wrong.  We need to read every error message and act accordingly.  We should never just click through them.  After all, they could be drive-by malware popups.

The risk of Error Message Fatigue should be reflected in our “new asset risk assessments.” And Error Message Fatigue Risk should be brought up in awareness training, especially if you think 2019 will be “The Year of the Aggressive Technology Plan!”

Original article by Dan Hadaway CRISC CISA CISM. Founder and Managing Partner, infotex

“Dan’s New Leaf” is a “fun blog to inspire thought in the area of IT Governance.”