Commentary

You Can Fool Some Employees All Of The Time ...

TO: Richard Spires, CIO, Internal Revenue Service FROM: John Soat SUBJECT: Social Engineering

TO: Richard Spires, CIO, Internal Revenue Service FROM: John Soat SUBJECT: Social EngineeringDear Richard:

I know you were just recently promoted to Deputy Commissioner for Operations Support for the IRS, effective next month (congrats, BTW). But I wanted to bring to your attention a report issued last month by the Treasury Department concerning a potential security problem, which, with all the hubbub over your new position, you might have missed. I have some context to bring to bear on that report, based on research data my organization recently generated, that you -- or your replacement -- might find illuminating.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The report is entitled "Employees Continue To Be Susceptible To Social Engineering Attempts That Could Be Used By Hackers." The report details a security test, conducted by the Treasury Department's Inspector General For Tax Administration, which involved 102 IRS employees who were contacted by phone by persons identifying themselves as computer help desk representatives. In order to help resolve a computer problem, each IRS employee was asked his or her name and then asked to change his or her computer password to one recommended by the caller.

Guess how many complied? Sixty percent. And that's not all. Only eight out of the 102 employees contacted a manager to report the call or check to see if it was legit.

Don't feel bad -- you're in the same boat as a lot of U.S. companies. According to InformationWeek Research's 10th annual Global Information Security Survey, a research study conducted earlier this year with more than 3,000 IT and security professionals, a third of U.S. respondents say enforcing security policies is the biggest security challenge they face this year, and 28% cite the need to make users more aware of security concerns.

According to the Inspector General's report, the IRS has nearly 100,000 employees and contractors who have access to tax return information processed on approximately 240 computer systems that contain over 1,500 databases. That's a lot of people -- and data -- to keep track of.

Unfortunately, when it comes to trying to keep employees on their toes, security-wise, it's not a pretty picture. Of 804 respondents who admitted they'd had security breaches in the past year, 21% say they were caused by social engineering -- the type of mind games and verbal razzamatazz that fooled your employees. And there doesn't seem to be a lot that can be done about it. Less than 20% of survey respondents feel that increased training on security technology and procedures will have a significant impact in reducing employee-based security breaches.

That may be something of a self-fulfilling prophecy. Only 40% of our survey takers report having any sort of regular security training (monthly, quarterly, annually) for their employees, while most train them on an ad hoc basis, and 13% never do.

However, the ones who do drill their employees on security issues feel they should get their money's worth: Two-fifths agree that employees should be fined in some way for making mistakes after they've received training.

But I guess that's not an option for you, right? Unless I want to pay more taxes, that is. So, let's think about that for a little while. My tax forms aren't all that interesting anyway.


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