The Risks of Being Caught Naked Post: 302448665

Sponsored Content

Special Forums News, Links, Events and Announcements Complex Event Processing RSS News The Risks of Being Caught Naked Post 302448665 by Linux Bot on Thursday 26th of August 2010 02:45:03 PM

08-26-2010

Registered User

The Risks of Being Caught Naked

John Bates
08-26-2010 02:42 PM
According to the FT, the Financial Industry Regulatory Association is undertaking a �sweep� of broker-dealers that offer direct market access to high-frequency traders to find out if they have pre-trade risk management controls in place for their algorithmic customers. (Read the full story here: http://tinyurl.com/28rg287). Here at Progress Software we have been advocating the use of pre-trade risk management tools for some time. The prospect of High Frequency Trading (HFT) firms running trades directly through broker algorithms (naked access) to exchanges/ECNs without adequate supervision has always concerned us. Brokerage firms simply give their clients an exchange ID number, which the clients then enter into their algorithms so that they can trade directly with the exchange.

Regulators are right to be concerned. Unfiltered access to trading destinations can end up causing trading errors or worse. Anything can happen with naked access; from fat fingered errors, trading limits being breached, even fraud - all of which can cost brokers, traders and regulators big money.

Although the SEC proposed banning naked access in January, and the Committee of European Securities Regulators (CESR) is likely to follow in its footsteps, there has been considerable pushback from brokers and trading firms. They say that adding a pre-trade risk management step would cause a "latency hop" in the trading process, claiming it would make them uncompetitive. A layer of risk management often adds a third party into the mix, and - consequently - a delay.

But if everyone is required to add real-time, pre-trade risk management, then the competitive disadvantage is moot. The benefits of being able to pro-actively monitor trades before they hit an exchange or ECN far outweigh any microscopic latency hops in any event. The naked access playing field is hardly level. There are trading systems out there that claim to throughput a trade in 16 microseconds from outside an exchange's firewall, while exchange and ECN systems range anywhere from 250 to 700 microseconds (according to measurements by latency management firm Corvil).

Latency is clearly an important issue and complex event processing offers a solution. Brokers can achieve ultra-low-latency pre-trade risk management without compromising speed of access. An option is a low latency "risk firewall" utilizing complex event processing as its core, which can be benchmarked in the low microseconds. With a real-time risk solution in place, a message can enter through an order management system, be run through the risk hurdles and checks, and leave for the exchange a few microseconds later.

It is the ideal solution to a tricky question - how do I manage risk before my trade hits the exchange without compromising speed? The benefits are clear - a latency hop of a few microseconds not only saves money, it can also prepare your firm for the regulatory future.

Source...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

chmod 777 security risks?

Hello all, I did a considerable search of the forum and didn't find an answer so I'll ask it here. For clarity's sake I'll state that I know just enough about Unix to be Dangerous (I'm an old Clipper, VO, ASM programmer from the 80's.) I would like to install PHP driven CMS program to my...

2. AIX

process caught signal 5

Hello, We are using AIX 5.2 ML 7. One of the process in its log file said the following and stopped running. Caught signal=5, exiting. What would cause the signal 5 to be generated on an AIX box. Please advise. Thx Jerardfjay

3. UNIX for Dummies Questions & Answers

Naked x11

X :0 & export DISPLAY=:0 xterm & Can I do this with multiple displays, :1, :2, etc.?

4. Shell Programming and Scripting

My error is not being caught or handled

Hi, I my ksh script I have the following: ##--Checking the spool file for errors NumberOfErrors=`cat $CurrSpoolFile | grep " ORA-" | wc -l`my logfile shows this: PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. BEGIN...

5. Solaris

Exiting (caught signal 11)

I created a new Virtual machine and was trying to install Solaris but keep getting this error.:confused: EXITING (caught signal 11) Type "install-solaris to restart" Can't find anything on Google. This is the iso image I am using "sol-10-u11-ga-x86-dvd" Followed all the instructions on...

6. Shell Programming and Scripting

Continue Processing after a signal is caught

Is it possible to continue after signal is caught and control goes to function specified in the trap statement?

LEARN ABOUT DEBIAN

nwdiag

NWDIAG(1)						      General Commands Manual							 NWDIAG(1)

NAME

       nwdiag - generate network-diagram image file from spec-text file.

SYNOPSIS

       nwdiag [options] files

DESCRIPTION

       This manual page documents briefly the nwdiag commands.

       nwdiag is generate sequence-diagram image file from spec-text file.

OPTIONS

       These  programs	follow	the  usual  GNU  command  line	syntax, with long options starting with two dashes (`-').  A summary of options is
       included below.	For a complete description, see the Info files.

       -h, --help
	      show this help message and exit.

       --version
	      show program's version number and exit.

       -a, --antialias
	      Pass diagram image to anti-alias filter.

       -c FILE, --config=FILE
	      read configurations from FILE.

       -o FILE
	      write diagram to FILE.

       -f FONT, --font=FONT
	      use FONT to draw diagram.

       -T TYPE
	      Output diagram as TYPE format.

SEE ALSO

       The programs are documented fully by
       http://blockdiag.com/en/nwdiag/

AUTHOR

       nwdiag was written by Takeshi Komiya <i.tkomiya@gmail.com>

       This manual page was written by Kouhei Maeda <mkouhei@palmtb.net>, for the Debian project (and may be used by others).

								   June 11, 2011							 NWDIAG(1)