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-3653
Published: 2015-07-06
Cross-site scripting (XSS) vulnerability in the template preview function in Foreman before 1.6.1 allows remote attackers to inject arbitrary web script or HTML via a crafted provisioning template.

CVE-2014-5406
Published: 2015-07-06
The Hospira LifeCare PCA Infusion System before 7.0 does not validate network traffic associated with sending a (1) drug library, (2) software update, or (3) configuration change, which allows remote attackers to modify settings or medication data via packets on the (a) TELNET, (b) HTTP, (c) HTTPS, ...

CVE-2014-9737
Published: 2015-07-06
Open redirect vulnerability in the Language Switcher Dropdown module 7.x-1.x before 7.x-1.4 for Drupal allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in a block.

CVE-2014-9738
Published: 2015-07-06
Multiple cross-site scripting (XSS) vulnerabilities in the Tournament module 7.x-1.x before 7.x-1.2 for Drupal allow remote authenticated users with certain permissions to inject arbitrary web script or HTML via an (1) account username, a (2) node title, or a (3) team entity title.

CVE-2014-9739
Published: 2015-07-06
Cross-site scripting (XSS) vulnerability in the Node Field module 7.x-2.x before 7.x-2.45 for Drupal allows remote authenticated users with certain permissions to inject arbitrary web script or HTML via unspecified vectors involving internal fields.

Dark Reading Radio
Archived Dark Reading Radio
Marc Spitler, co-author of the Verizon DBIR will share some of the lesser-known but most intriguing tidbits from the massive report