Commentary

George Hulme
 

SnooperGate: Two Fired Over Illegal Obama Passport Snooping

It's the second time in a week where workers improperly accessed electronic records of the rich, powerful, or famous.

It's the second time in a week where workers improperly accessed electronic records of the rich, powerful, or famous.Late Thursday evening, news broke that contractors working for the U.S. State Department had fired two workers and scolded another for a series of incidents of improper snooping at Sen. Barack Obama's passport files.

During a conference call Thursday night with reporters, State Department spokesman Sean McCormack labeled the incident a case of "imprudent curiosity."


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Actually, it was a case of three separate acts of "imprudent curiosity," which occurred on Jan. 9, Feb. 21, and March 14.

The department's inspector general will look into whether the snoops were politically motivated.

Like many corporations, the State Department has policies and controls in place to help keep these things from happening. And each time such Passport records are accessed, workers are warned that access without "need-to-know" is a violation of the Privacy Act of 1974.

I guess this set of curiosity seekers felt they "needed to know."

This incident is a mirror image of the events earlier this year that affected the medical privacy of Britney Spears. Just as is the case with the Obama snoopers, the workers at UCLA Medical Center had access privileges to the systems that held the private information.

When answering a reporter's question last night, Patrick F. Kennedy, under secretary for management at the State Department, summed up the department's conundrum, as well as that of many organization's facing similar challenges:

In order to deal with 18 million passports a year, we require lots of people to have access because it's compartmentalized in the sense that different people perform different functions, including recording if someone advises that their passport has been lost or stolen, so that requires you go to in and make notifications.

In other words, broad access rights, based on job functions, need to be granted to workers so they can do their job. There's no way to predict which workers will go bad.

In both of these cases, with Spears and Obama, the monitoring mechanisms were in place to identify the breach or privacy. And people are getting fired for their misdeeds. Let's hope prosecutions are forthcoming.

These types of incidents, no matter how tightly managed an organization's identity management system is, or the database security measures they have in place, are going to occur.

Both of these incidents make a great argument for database auditing and monitoring applications, backed up by strict law enforcement. The paradox going forward will be, as both database monitoring solutions get better, and more companies deploy them, the more cases of SnooperGate we're going to hear about.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links