Now Available:

line

Featured Resources:

line

Newsletter

Email Address:


line

Ask the Expert

Have a question for our resident expert? Email your questions to Rebecca.

« A Twist Within a New State Breach Notice Law: Maryland's Also Requires Information Security Safeguards | Main | Outsourced Company's Unsecure Application Makes U.K. Passport Applicant PII Available to Everyone On the Internet »

Insider Threat Example: Leaked Clinton Memo Provides At Least 5 Good Security Lessons

Mid-last week it was widely reported, probably more so in the national news than here in Iowa, that one of Hillary Clinton's top campaign folks had written a memo to her urging her to skip Iowa and focus on other states. This leaked memo was the grist of much discussion on the political talk shows over the weekend.

Clinton has been here in Iowa so many times that she's almost a resident. This leaked memo did not make much difference to the folks here in the heartland; her actions speak much louder than her aide's words. Plus, I think Clinton handled the leak very well (read about it in the article).

However, if she had not been here much, this could have been very damaging to her campaign in Iowa.

But, it brings up the question...how did this private memo get leaked to the press in the first place?

Can you imagine all the business memos you have in your organization, between your business leaders that reveal their candid thoughts and often not-too-good ideas? What if these memos got into the hands of the press, or even more likely in today's YouTube generation, got posted to a website?

This is another good example of the insider threat.

The article did not report how the memo was leaked. So, let's consider some of the possibilities, given information is commonly shared electronically, and that there are many campaign offices throughout Iowa, along with all the other locations throughout the U.S.

1. Someone may have sent the memo as an email attachment to another campaign member. That person may have forwarded the message, along with the memo, so someone outside the campaign, who in turn may have sent it to the Des Moines Register reporter.
LESSON: When you send information via email you have no control over it once you hit the button. Do not send confidential information within clear text email messages or clear text attachments.

2. Someone may have thrown away a hard copy printout of the memo, and someone digging through the trash, perhaps even a reporter, may have found it.
LESSON: Do not throw papers containing confidential information into the trash without shredding.

3. Someone may have had access to the storage location on the server who should not have had access.
LESSON: Give access only on a need-to-know basis. In other words, prohibit all access by default, and give access as necessary for job responsilities.

4. The memo writer himself may have leaked the memo on purpose. He could have been in cahoots with someone in another campaign camp, or he may be disgruntled.
LESSON: Use logging to know who is doing what with your information. Provide ongoing training. Apply sanctions consistently. Do appropriate background checks prior to hiring employees who will have access to sensitive information or mission critical assets.

5. Someone who had access to the memo may not have known that they shouldn't give the information to anyone outside the organization.
LESSON: Have strong information security policies; communicate them effectively and on an ongoing basis, meaning you need to put forth effort to have a comprehensive training and awareness program.

These are just 5 possibilities; there are of course many, many more...feel free to offer some of your speculations!

There is also a good incident response lesson here; don't wait until an incident happens to convince the public that you should be forgiven for allowing it to happen.

Visibly practice exemplary information security and privacy habits, and promote your dedication to the safeguards to your customers and the public. Then, if an incident does occur, they will know that you were being proactive to keep bad things from happening.

TrackBack

TrackBack URL for this entry:
http://www.realtime-itcompliance.com/type/mt-tb.cgi/421

Comments

Chances are that the leak was the result of an insider breach, as implied above, and I will not speculate on intentional leaks in politics. Other ways this memo could have entered the public domain include being saved on a thumb drive which got lost, via unsecured wireless connection, or by social engineering.

Looks like they should have had an ILP product, such as the one my bank uses. We've prevented a number of potential disasters by using the GTB Inspector. Take a look at www.gttb.com

Post a comment

(All comments are approved by site leader before appearing here. Thanks for commenting!)

line

Rebecca Herold's Bio:

Rebecca Herold,CISSP, CIPP, CISM, CISA, FLMI, has been providing information security, privacy and regulatory assistance and services to organizations from a wide range of industries for over 18 years. Rebecca was instrumental in building the information security and privacy program while at Principal Financial Group, which was awarded the CSI Information Security Program of the Year Award in 1998. IT Security ranked Rebecca as one of the top 59 IT security influencers, and Computerworld put Rebecca their list of the 25 top privacy experts and on their list of the 9 best privacy consulting firms. Rebecca has been CPO for two consulting organizations, and has had her own information privacy, security and compliance business since 2004. Rebecca has written chapters for several books, dozens of articles, and has been writing a monthly privacy column for the CSI Alert newsletter since the beginning of 2001, and is working on her 11th book. Some of her other books include The Privacy Papers, Managing an Information Security and Privacy Awareness and Training Program, The Definitive Guide to Security Inside the Perimeter (Realtime Publishers), The Shortcut Guide to Improving IT Service Support through ITIL (Realtime Publishers), and The Practical Guide to HIPAA Privacy and Security Compliance. In addition, Rebecca is the leader of The Realtime IT Compliance Community where she posts to her IT Compliance weblog. You can contact Rebecca at: rebecca_herold@realtimepublishers.net.