Commentary

George Hulme
 

Fannie Mae Logic Bomb Makes Case For Strong IDM

The indictment of an IT contractor working at Fannie Mae, who schemed to destroy the data on 4,000 servers, confirms what we know: bad economic times and layoffs are perilous, and identity and access management has never been more important.

The indictment of an IT contractor working at Fannie Mae, who schemed to destroy the data on 4,000 servers, confirms what we know: bad economic times and layoffs are perilous, and identity and access management has never been more important.Take a look at Tom Claburn's news story, "Fannie Mae Contractor Indicted For Logic Bomb," and you'll read about a logic bomb (a malcode designed to do something bad when triggered) that was designed to wipe 4,000 of the mortgage company's servers. Claburn writes:

[The logic bomb] was allegedly placed by Rajendrasinh Makwana, an IT contractor who worked in Fannie Mae's Urbana, Md., facility. It was set to execute on Jan. 31. Had it done so, Fannie Mae engineers expect it would have caused millions of dollars in damage and possibly shut down the government-sponsored mortgage lender for a week.

More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Makwana was indicted for unauthorized computer access Tuesday in federal Court.

According to the story, an eagle-eyed Unix engineer, only identified as SK, found the script "by accident." Kudos for being observant.

But the story shows the importance of de-provisioning users, quickly:

The discovery occurred on Oct. 29. Makwana had been terminated as a Fannie Mae contractor on Oct. 24, around 1 or 1:30 p.m., the affidavit says, but his network access was not terminated until late that evening. Makwana was fired for allegedly creating a computer script earlier that month that changed server settings without the permission of his supervisor.

Makwana was not required to turn in his badge or Fannie Mae-supplied laptop until the end of the day on Oct. 24. According to Nye's affidavit, it was during that afternoon that Makwana is alleged to have planted the malicious script.

There are two layers of defenses, that I can think of, offhand, that can be proactively taken to protect your organization from such an event. First: thorough background checks. While this won't screen everyone who could potentially be a bad character, it will screen those who have no business having admin privileges to critical IT systems.

The second layer of defense is having an identity and access control management system in place so that terminated employees -- especially those with network admin privileges -- can have their network access shut down immediately.

There is no reason why network access should have been possible after the talk with HR. None.

Perhaps Makwana is innocent, and someone else planted the logic bomb. That will be argued out in court. I'm certain that when network access is cut, a terminated admin can't plant logic bombs.

Fannie Mae is fortunate that SK was sharp enough to spot this script before it was set to trigger.


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