Commentary

Bob Evans
Senior VP, Global CIO  

From Layoffs To Ripoffs: Wicked New Threats From Ex-Employees

Most companies are "ill-prepared for an onslaught which could prove calamitous" and face "the greatest security threat of our times" from laid-off workers who are "extremely dangerous," say members of a global security-response team. In these dark days, stealing data's old hat; the new threats include tampering with billing systems, changing customer orders, and altering design documents.

Most companies are "ill-prepared for an onslaught which could prove calamitous" and face "the greatest security threat of our times" from laid-off workers who are "extremely dangerous," say members of a global security-response team. In these dark days, stealing data's old hat; the new threats include tampering with billing systems, changing customer orders, and altering design documents.For you CIOs out there, are you aware of this? If so, have you taken all necessary precautions? If not, what explanation do you plan to use if you get hit and your CEO calls you in and asks how in the name of heaven this could have happened?

Trying to highlight the enormous risk enterprises are facing as hundreds of thousands of white-collar workers lose their jobs, the Forum of Incident Response and Security Teams (FIRST) has issued a "Scared Straight"-style press release in advance of a global meeting in Japan next month, writes my colleague Tim Wilson at our excellent Dark Reading security site.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

What struck me about the tone of the comments from FIRST members and other security experts interviewed by Wilson was the consistency in their levels of concern that most organizations are simply doing nothing to prevent what could be some disastrous disruptions and/or corruptions of their operations. And again, they said next to nothing about the threats from organized-crime rings and other external malicious hackers - instead, the entire focus of this latest round of alarms was the huge swath of office workers who've been laid off or fear they are about to be, and don't want to go quietly into unemployment. Writes Wilson:

"One of the greatest security threats of our times is from insiders, as organizations lay off tens of thousands of workers," said Scott McIntyre, a FIRST steering committee member and representative of the Netherlands-based KPN Computer Emergency Response Team (CERT). "People know the axe is coming, and the longer employers prolong the swing of that axe, the more danger they expose themselves to, either from sabotage or data theft. An employee who thinks he or she is [going to be laid off] can start fouling up systems which are critical to the organization, or decide to take an unauthorized pay-off by stealing a mass of data."

But as bad as data theft can be, it gets worse. This new wave of insider threat is also expected to include code-level attempts to sabotage billing systems, product-design systems, customer-ordering systems, and more. Outlining the concerns of FIRST steering committee chair Derrick Scholl, Wilson offers this:

"Sure, an insider is capable of stealing corporate secrets, or customer lists, or destroying computers, but their potential for harm is far worse," [Scholl] states. "Imagine a software company where an insider has the ability to change code in the product without being detected. What if the insider altered design documents or tampered with customer orders? Or ripped out hard drives and corrupted systems just as a big corporation was about to issue its quarterly bills to hundreds of thousands of customers? It's a totally different order of threat, and it requires a different way of thinking."

Wilson's article offers a range of suggestions of how companies can make plans to mitigate these insider threats, and in spite of the global economic downturn that has gutted IT budgets, CIOs are going to have to find ways to devote the necessary people, dollars, and intensity to be as fully prepared as possible.


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