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-3407
Published: 2014-11-27
The SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 9.3(.2) and earlier does not properly allocate memory blocks during HTTP packet handling, which allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCuq68888.

CVE-2014-4829
Published: 2014-11-27
Cross-site request forgery (CSRF) vulnerability in IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allows remote attackers to hijack the authentication of arbitrary users for requests tha...

CVE-2014-4831
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to hijack sessions via unspecified vectors.

CVE-2014-4832
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to obtain sensitive cookie information by sniffing the network during an HTTP session.

CVE-2014-4883
Published: 2014-11-27
resolv.c in the DNS resolver in uIP, and dns.c in the DNS resolver in lwIP 1.4.1 and earlier, does not use random values for ID fields and source ports of DNS query packets, which makes it easier for man-in-the-middle attackers to conduct cache-poisoning attacks via spoofed reply packets.

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?