Owning It

Probably everyone by now has heard of Target's unfortunate lapse in security which led to the compromise of upwards of 70 million accounts.  Today, Target is taking steps toward damage control, not just for themselves but for the customers who face possible targeting down the road.  Pun intended.  Their email states that they are "offering one year of free credit monitoring to all Target guests who shopped in U.S. stores".  This is refreshing.  Not only has the retailer solved the problem from their end, they are offering mitigation for end users. 

Where did the problem arise?  It wasn't a hack from outside that just downloaded the information, it was malware that was actually running on their registers.  Granted, this resulted from a hacker intrusion, but it goes to the point of the malware itself.  Follow the money.  In some form or fashion, this variety of software exists to bilk people.  It is propagated to earn. 

Malware isn't my point, though.  Ownership is.  Responsibility.  Taking charge and making reparations, making it right.  I do that even for mistakes that aren't mine, which breeds sensitivity on the subject.  For example, a client needed full backup of the computers in their business in case of failure.  There was failure, not only of the system but of the verified backup as well!  I had recommended and installed the software to provide the failsafe, but it did not work.  Now what?

I worked all weekend to get the system back up and running, upgrading their operating system in the process without charging them overtime or for the upgrade.  Why?  Because it was the right thing to do.  It wasn't my fault the backup failed, but it was on my recommendation the customer used it.  It certainly wasn't their fault.  In my book, owning it is the only right thing to do, making it right, and that is what I did.  There have been a lot of orphaned, high profile failures in that area lately.  Seeing Target own their issue made my day.