Risk
1/31/2008
05:36 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

When Criminal Intent Lurks One Cube Away

The ongoing Société Général fraud story is a case study in insider threats. The costs, north of $7 billion for the French bank, are high and likely to go higher. For the rest of us, it leaves an uneasy question: Do we have a rogue in our organization? And if so, what do we do about it?

The ongoing Société Général fraud story is a case study in insider threats. The costs, north of $7 billion for the French bank, are high and likely to go higher. For the rest of us, it leaves an uneasy question: Do we have a rogue in our organization? And if so, what do we do about it?As was posted earlier this week, the fraud doesn't look like it required any "hacking" or significant technical skills to perpetrate. Rather, the accused allegedly used his inside knowledge on internal controls to bypass them and place roughly $73 billion in bogus trades that cost the bank more than $7 billion to unwind.

It's a stark reminder to security professionals what could be at stake if a knowledgeable insider ever turned bad in a fraudulent, criminal, even destructive way.

The Insider Threat Study: Illicit Cyber Activity in the Banking and Finance Sector, published by the U.S. Secret Service and the CERT Coordination Center, holds some interesting findings from its examination of 23 incidents conducted by 26 insiders. Including that, 70% of the time, insiders took advantage of failures in business rule checks and authorization mechanisms. Also, 78% of the time insiders were authorized and active computer users at the time, and a surprising 43% used their own username and passwords to commit their crime.

Those are scary statistics for anyone trying to protect their company's treasure, whether monetary or intellectual property. So how do you go about protecting against the insider threat? One place I'd start would be with background checks, upon hiring.

Unfortunately, the vast majority of people who commit these types of incidents don't have a record. This would screen some, but not enough. Another area would be strict identity management and access control enforcement, such as terminating orphaned accounts, limiting access rights, and regular and mandatory password changes among employees. Again, this would help, but not eliminate enough.

What about not only enforcing access control, but also monitoring employee's use of systems -- and letting all employees know -- their work actions are being logged. This would be the right thing to do, and would have to act as a deterrent, and even help with any forensic analysis that may be needed.

This would be a good start, but it's clearly not all inclusive.

What steps does your organization take to minimize the insider threat?

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5395
Published: 2014-11-21
Multiple cross-site request forgery (CSRF) vulnerabilities in Huawei HiLink E3276 and E3236 TCPU before V200R002B470D13SP00C00 and WebUI before V100R007B100D03SP01C03, E5180s-22 before 21.270.21.00.00, and E586Bs-2 before 21.322.10.00.889 allow remote attackers to hijack the authentication of users ...

CVE-2014-7137
Published: 2014-11-21
Multiple SQL injection vulnerabilities in Dolibarr ERP/CRM before 3.6.1 allow remote authenticated users to execute arbitrary SQL commands via the (1) contactid parameter in an addcontact action, (2) ligne parameter in a swapstatut action, or (3) project_ref parameter to projet/tasks/contact.php; (4...

CVE-2014-7871
Published: 2014-11-21
SQL injection vulnerability in Open-Xchange (OX) AppSuite before 7.4.2-rev36 and 7.6.x before 7.6.0-rev23 allows remote authenticated users to execute arbitrary SQL commands via a crafted jslob API call.

CVE-2014-8090
Published: 2014-11-21
The REXML parser in Ruby 1.9.x before 1.9.3 patchlevel 551, 2.0.x before 2.0.0 patchlevel 598, and 2.1.x before 2.1.5 allows remote attackers to cause a denial of service (CPU and memory consumption) a crafted XML document containing an empty string in an entity that is used in a large number of nes...

CVE-2014-8469
Published: 2014-11-21
Cross-site scripting (XSS) vulnerability in Guests/Boots in AdminCP in Moxi9 PHPFox before 4 Beta allows remote attackers to inject arbitrary web script or HTML via the User-Agent header.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?