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
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2027
Published: 2015-03-31
eGroupware before 1.8.006.20140217 allows remote attackers to conduct PHP object injection attacks, delete arbitrary files, and possibly execute arbitrary code via the (1) addr_fields or (2) trans parameter to addressbook/csv_import.php, (3) cal_fields or (4) trans parameter to calendar/csv_import.p...

CVE-2014-2830
Published: 2015-03-31
Stack-based buffer overflow in cifskey.c or cifscreds.c in cifs-utils before 6.4, as used in pam_cifscreds, allows remote attackers to have unspecified impact via unknown vectors.

CVE-2014-7876
Published: 2015-03-31
Unspecified vulnerability in HP Integrated Lights-Out (iLO) firmware 2 before 2.27 and 4 before 2.03 and iLO Chassis Management (CM) firmware before 1.30 allows remote attackers to gain privileges, execute arbitrary code, or cause a denial of service via unknown vectors.

CVE-2014-9462
Published: 2015-03-31
The _validaterepo function in sshpeer in Mercurial before 3.2.4 allows remote attackers to execute arbitrary commands via a crafted repository name in a clone command.

CVE-2014-9706
Published: 2015-03-31
The build_index_from_tree function in index.py in Dulwich before 0.9.9 allows remote attackers to execute arbitrary code via a commit with a directory path starting with .git/, which is not properly handled when checking out a working tree.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.