Sponsored Content
Full Discussion: Catching the Insiders
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Catching the Insiders Post 302474226 by Linux Bot on Tuesday 23rd of November 2010 05:00:03 PM
Old 11-23-2010
Catching the Insiders

John Bates
11-23-2010 05:26 PM
The FBI has raided some heavy hitters this week (http://tinyurl.com/238hrph), with three well-known hedge funds getting their doors rammed in, figuratively speaking. This could be the tip of the iceberg in all-encompassing insider trading investigation involving research firms, investment bankers, hedge funds and mutual funds. The gist of the investigation is that some trading firms might have been using sensitive market information provided to them by research firms before the market got it.

 

Traders have long sought out information that can give them an edge over a deal. But there is a fine line between giving trading tips and offering up non-public information to trading firms. One is legal, the other - of course - isn't. Whether these cases prove to be valid or not, there must have been clear evidence that insider information was used. Trading patterns can provide clues to insider activity, particularly if more than one firm acts in the same manner at the same time on the same information - prior to the market reacting. If the FBI can see these trading patterns it can then go after the participants to confirm suspicions. Traditionally this means recording of phone calls, emails and messaging conversations.

 

An example of a pattern that might indicate insider activity is if a firm trades an unusually large amount of a particular instrument that they haven't traded before, just seconds prior to a major news article that moves the market in that instrument. Maybe such a circumstance might just be good fortune or a result of good intuition, but a series of such occurrences from the same firm might be worth looking into. Upon further investigation you could find that several firms are doing this at the same time. Furthermore, perhaps the extent of the purchases is hidden across multiple liquidity pools. A whole pattern of evidence might be out there - under your very nose.

 

The problem with finding such a pattern of evidence is that many of the current methods of detection and investigation can only address the problem weeks, months or even years after they occur - if they can see it at all. Trying to sniff out insider trading without modern monitoring technology is like swimming after a shark. The shark ducks and dives and goes a thousand times faster than you can, eventually turning around and eating you.

 

To truly address the problem of insider trading, real time market surveillance technology must be adopted to monitor and detect patterns that indicate potential market abuse. The detection of abusive patterns must happen in real-time - so the authorities can respond while the iron is hot. Trading occurs at lightning speed these days, thanks to electronic and algorithmic trading. What has not kept pace in many cases is the use of monitoring technology necessary to stay on top of possible market abuses. As well as the use of technology by the authorities to help detect insider rings, exchanges, ECNs, brokers, traders and regulators all should take an intelligent approach to monitoring and surveillance in order to prevent other abuse and problems in their own domains - such as rogue trades - and fat finger errors.

 

Technology can't solve all of the problems, but it can offer more market transparency where issues can be identified much more quickly and potentially even prevented.

 



Source...
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

catching interrupts

hey i have been facing a problem,can you tell me if we can catch ctrl d in unix i have tried and sucessfully catched and disabled ctrl-c and ctrl -z but am not sure if we can do the same for CTRL-D, so got any clue mail on he forum or ...i mean c programming in Unix thats what i am working on (1 Reply)
Discussion started by: toughguy2handle
1 Replies

2. UNIX for Dummies Questions & Answers

Awk- catching the last two chars

Can anyone explain to me how to get the last two chars' from each row of Column (each row being variable in length) using awk, some of the lines will be blank, I'll be running a paste after awking. So I need to keep the blanks where they are..so I can paste back all columns in the correct order ... (9 Replies)
Discussion started by: Gerry405
9 Replies

3. Shell Programming and Scripting

Catching all Exit Codes

I have a Unix Script that has several exit in the middle. each returning seperate exit codes. I have to catch all the exit's and perform an operation say "Mail the status code" before the actual code completes. How can i do this in KSH ? (3 Replies)
Discussion started by: Sivaswami J
3 Replies

4. Shell Programming and Scripting

catching some errors

I need to find a way to keep a running tally of how many times events or actions occur. Say if a user is prompted to make inputs of 1 or 2, I want it to keep track of how many times 1 was entered, and how many times 2 was entered. Thanks for your help (5 Replies)
Discussion started by: bebop1111116
5 Replies

5. UNIX for Dummies Questions & Answers

Catching print jobs.

Hi, I am wondering how to catch print jobs to process them before been served to the printer. I was told that the challenge is to catch raw text that an old legacy application sends to the printer (invoices, quotes, etc) and save them as text files to allow a new application to process them... (5 Replies)
Discussion started by: miguel77mex
5 Replies

6. Programming

Signal catching

Hi! I want to catch all signals that my program receives print their name and then execute the default handler. Can you help me on that? I've tried the following code: #include <stdio.h> #include <unistd.h> #include <signal.h> void (*hnd)(int i); char signals = { "SIGHUP",... (7 Replies)
Discussion started by: dark_knight
7 Replies

7. Shell Programming and Scripting

Catching errors

Hi, I'm writing a scheduling script which will co-ordinate the launching of scripts. This script is scheduling based on an input file, and launches the appropriate scripts at the right times. The only issue I'm having is: - if a script dies, or even has a syntax error, I want to catch... (1 Reply)
Discussion started by: GoldenEye4ever
1 Replies

8. Shell Programming and Scripting

Catching error in sftp

Hi All Experts, I have a script which logs to the server via sftp connection with below code :- user_name@sftp_server.com and the connection is going smooth. My requirement is to place file in sftp_server in some path. and if path doesn't exist or the file is not put successfully I... (3 Replies)
Discussion started by: punitsoneji
3 Replies

9. Solaris

BSM not catching creat64

Solaris 9 system: I'm trying to get BSM to record to the point where additional files being put into /etc/opt/csw/sudoers.d will be recorded but thus far all I'm able to get are when files are deleted (via unlink). I've even tried auditing based on the "all" audit flag temporarily (thinking I... (2 Replies)
Discussion started by: thmnetwork
2 Replies
SENSORS-DETECT(8)					      System Manager's Manual						 SENSORS-DETECT(8)

NAME
sensors-detect - detect hardware monitoring chips SYNOPSIS
sensors-detect DESCRIPTION
sensors-detect is an interactive program that will walk you through the process of scanning your system for various hardware monitoring chips, or sensors, supported by libsensors(3), or more generally by the lm_sensors tool suite. sensors-detect will look for the following devices, in order: o Sensors embedded in CPUs, south bridges and memory controllers. o Sensors embedded in Super I/O chips. o Hardware monitoring chips accessed through ISA I/O ports. o Hardware monitoring chips reachable over the SMBus or more generally any I2C bus on your system. As the last two detection steps can cause trouble on some systems, they are normally not attempted if the second detection step led to the discovery of a Super I/O chip with complete hardware monitoring features. However, the user is always free to ask for all detection steps if so is his/her wish. This can be useful if a given system has more than one hardware monitoring chip. Some vendors are known to do this, most notably Asus and Tyan. WARNING
sensors-detect needs to access the hardware for most of the chip detections. By definition, it doesn't know which chips are there before it manages to identify them. This means that it can access chips in a way these chips do not like, causing problems ranging from SMBus lockup to permanent hardware damage (a rare case, thankfully.) The authors made their best to make the detection as safe as possible, and it turns out to work just fine in most cases, however it is impossible to guarantee that sensors-detect will not lock or kill a specific system. So, as a rule of thumb, you should not run sensors- detect on production servers, and you should not run sensors-detect if can't afford replacing a random part of your system. Also, it is recommended to not force a detection step which would have been skipped by default, unless you know what you are doing. SEE ALSO
sensors(1), libsensors(3) AUTHOR
Frodo Looijaard and Jean Delvare lm-sensors 3 December 2008 SENSORS-DETECT(8)
All times are GMT -4. The time now is 08:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy