Slashdot Mirror


Brokerage Instant Messages Must Be Saved

DrEnter writes "According to an AP story on Yahoo!, the National Association of Securities Dealers (NASD) has told its members that they must keep a copy of all instant messages sent or received by employees for at least three years. This is similar to their requirements on keeping e-mail, although technically not nearly as easy. The NASD is a self-regulatory organization, and U.S. federal law requires almost all of the 5,300 U.S.-based securities firms and brokerages to be a member of it. There's a news release from the NASD concerning the requirement - it looks like the daunting technical issues have already resulted in some firms banning the use of IM completely."

265 comments

  1. daunting technical issues? by Surak · · Score: 4, Insightful

    What daunting technical issues? Nearly every instant messaging client has the ability to always log conversations. Simply standardize the clients that can be used, make sure that conversations are logged, and lock down the configs so that brokers can't change them. I see no daunting technical issues here.

    1. Re:daunting technical issues? by Craig+Maloney · · Score: 1

      Any time you see "daunting technical issue" when related to financial software, read "it'll cost us money to fix, and we'd rather implement some proprietary measure where we're guaranteed to make money rather than spend it for the perceived convenience of the customer".

    2. Re:daunting technical issues? by sosume · · Score: 1, Funny

      1) Start National Association of Securities Dealers (NASD)
      2) Oblige members to save instant messages
      3) ???
      4) Profit!!!

    3. Re:daunting technical issues? by Max+Romantschuk · · Score: 4, Interesting

      What daunting technical issues? Nearly every instant messaging client has the ability to always log conversations.

      Would you trust your IM to log messages? What if the logging fails? Will your boss listen to you, or would you rather not take the risk at all?

      --
      .: Max Romantschuk :: http://max.romantschuk.fi/
    4. Re:daunting technical issues? by Surak · · Score: 3, Interesting

      That's what IT staff are for. That's why you use standardized builds of client PCs. The IT staff does the integration work to ensure that things like logging occur. The standardized configs make sure that everything works and that users can't change it.

    5. Re:daunting technical issues? by Surak · · Score: 1

      How much money? Most companies due new builds of their standard clients every 18 months or so anyway. The time to integrate and test a locked-down IM config that ensures that logging happens is very small compared to the time it takes to install and integrate major apps, like, oh say, Microsoft Office or Lotus Notes, and it could happen has part of the standard build, meaning the actual costs are spread out so thin as to be almost non-existant. It would take an admin maybe -- what? -- an hour or two to implement this? If that?

    6. Re:daunting technical issues? by funkman · · Score: 3, Informative

      No its not. If they use AIM, then they can use the AOL gateway. The AOL gateway product can do also do their own authentication and force AIM clients (based on AIM handle) to use the gateway. The gateway can do all the needed logging. A strict IT policy to be followed by employees makes this task trivial.

    7. Re:daunting technical issues? by muffen · · Score: 4, Insightful

      As you said, they have the ability to log it on a client level. Imagine a company with 500 000 machines. Are you going to collect logs from each and every one every single day?? Even if you saved the logs on a network drive, do you want 500 000 different files per day?

      The difficulty is logging the traffic on a server level. The reasons are many. I think this article describes them fairly well.

      Basically, IM traffic tries to hide itself, generally as HTTP traffic. Yahoo for example prepends a HTTP header to all packets, thereby being disguised as a HTTP GET request. AOL/ICQ/MSN has the ability to use HTTP Proxy servers, and AOL provides www.proxy.aol.com for free (port 80, no pass). MSN will auto-configure itself to use a proxy server if direct access is blocked.

      Here's the result of logging IM traffic on a client level.

    8. Re:daunting technical issues? by jkrise · · Score: 1

      The daunting issues aren't with logging, rather with tapping. In a client-server setup (e-mail) it's pretty simple (apparently) to intercept and probe messages. Value added services (Spam, HTML, worms, viruses, etc.. ) can be provided as well. If the world shifted to encrypted peer-to-peer instant messages, many shady firms could go broke!

      Who should go broke first - brokers or firms?

      --
      If you keep throwing chairs, one day you'll break windows....
    9. Re:daunting technical issues? by viking099 · · Score: 1

      ICQ logs every message that comes down the pipe, and organises it chronologically by user ID number in a database.
      I've got ICQ conversations in my backup archives that go back to when I first got the application; approximately early-mid 1997.
      Backing it up is easy on any platform, as it stores it in a couple of files in a single directory. You can have a scheduled task download the directory on a weekly basis and put it in the backup directories.
      And since they're all text, you don't need the user password to read them (if someone leaves), and they're easily zipped up and encrypted.

    10. Re:daunting technical issues? by Surak · · Score: 1

      As you said, they have the ability to log it on a client level. Imagine a company with 500 000 machines. Are you going to collect logs from each and every one every single day?? Even if you saved the logs on a network drive, do you want 500 000 different files per day?

      Scripting. Simply produce a script that processes the logs and concatenates them into one big log. That's part of the process of integration that I mentioned. And not even General Motors as 500,000 machines (I used to work there, so I know), and most brokerages are fall smaller than General Motors.

    11. Re:daunting technical issues? by arkanes · · Score: 4, Insightful
      Missing the point - in this case, all the logging is done on client machines, outside the direct control of the support staff. That'd be a disaster if, say, someones hard drive failed and the log was lost, and then they were sued. Email is easy because you just mirror it on a server. You'd need some sort of complicated transparent proxy to log normal IMs, and that wouldn't work with encrypted conversations.

      In other words - yes, it can be done. No, it's not trivial.

    12. Re:daunting technical issues? by Anonymous Coward · · Score: 2, Interesting

      I work for a very large Chicago-based financial institution that has banned IM entirely for their brokerage staff and disallowed Internet-capable IM for the rest of the company and I can safely say that a combination of FUD and CYA prompted this decision.

      Basically, the bank's Infosec team was told to log everything and to ensure that no unauthorized external IM communication between the investment brokers and the outside world occurs, so instead of trying to overengineer a solution to ensure that only authorized IM occurs, they simply blocked outbound IM altogether and disallowed the brokers to have any IM client installed at all. Elegant? No. Effective? Yes.

      Perhaps at some time they'll go back and address the situation more granularly, but for now, it fits the requirements and protects the bank from being targeted by the SEC. Staying off their radar these days is a "Good Thing" [TM].

    13. Re:daunting technical issues? by shaitand · · Score: 3, Interesting

      umm ok, last I checked it takes less than 5mins to write a shell script that uploads these logs in the background to an ftp. Pop it in a cron job and bam, all set.

    14. Re:daunting technical issues? by Talez · · Score: 1

      Missing the point - in this case, all the logging is done on client machines, outside the direct control of the support staff

      Errr... Junction Points?

      Think symbolic links for network resources under Windows 2000 and upwards.

      Transparent, invisible logging to the server.

    15. Re:daunting technical issues? by Simon+(S2) · · Score: 1

      "The standardized configs make sure that everything works and that users can't change it."

      and then some user downloads any other IM, wich is not the one configured by the IT staff, and bypasses any logging.
      your solution is buggy.

      --
      I just don't trust anything that bleeds for five days and doesn't die.
    16. Re:daunting technical issues? by schnozzy · · Score: 1

      One of my company's clients is a broker/dealer who is crazy about compliance and has been logging all IM conversations for months now. They have an OpenBSD firewall running a little ruby+pf+ethereal+snort script to detect all IM activity and log it to sorted files, but you could probably do this sort of thing on any box. The only thing it can't log thus far is SSL'd jabber. (Which can log on it's own)

      Daunting, pushaw.

    17. Re:daunting technical issues? by shaitand · · Score: 1

      As someone else already noted, you cat the logs, then upload them to server using a scheduled script. This is not exactly difficult.

    18. Re:daunting technical issues? by Surak · · Score: 1, Insightful

      Now you're thinking. See what I mean? Put a smart IT staff to work, and the solutions just start pouring out. As I said, there are no daunting technical issues here.

    19. Re:daunting technical issues? by shaitand · · Score: 1

      This sounds like a concern for the firm... but how exactly is this a technical issues that makes it difficult to log IM's for 3yrs?

    20. Re:daunting technical issues? by bmongar · · Score: 4, Insightful
      Nearly every instant messaging client has the ability to always log conversations

      Client side logging is not sufficient. An employee can turn that off or delete the logs. The logging would have to be done server side. That would require a corporate IM solution which would log. I work for a company effected by this law. They don't allow any external or web based e-mail access for the same reason, they can't log it unless you go through their server.

      --
      As x approaches total apathy I couldn't care less.
    21. Re:daunting technical issues? by HighOrbit · · Score: 1

      Bingo ! You hit the nail on the head.

    22. Re:daunting technical issues? by blibbleblobble · · Score: 4, Funny

      "Imagine a company with 500 000 machines..."

      If you have 500,000 machines running Windows, this will be the least of your problems.

    23. Re:daunting technical issues? by bleh-of-the-huns · · Score: 3, Informative

      Its much eaiser to implement a corperate version of an IM server, that most IM networks now provide, then firewall off the other IM servers, forcing the clients to use the corperate version, or proxy all IM client request to std IM servers to the corperate one, provides central logging point, and peace of mind for the security personel.

      On the other hand.. IM is not secure by any means, anyone stupid enough to use it in a financial industry for anything other then talking to friends and bullshitting around, should be shot.

      --
      I came, I conquered, I coredumped
    24. Re:daunting technical issues? by Clover_Kicker · · Score: 1

      Yes, but since the logs originate on the desktop machines, they can't be trusted. I could edit the IM transcript before I log off for the day, to ensure that my evil comments don't make it into the archive.

      I usually use NET SEND for my smartass/obscene OOB communication, nobody logs/monitors that :)

    25. Re:daunting technical issues? by bleh-of-the-huns · · Score: 1

      500k machines.. easy. pick any federal orginasation that has satellite offices around the country... think FAA, think FBI, each of those easily has 500k machines (granted about half to may 2/3 are workstations, but you get the point)

      Scripting is not the answer in a large scale enviroment. It works great for small groups of machines where they interact alot, but for large scale applications, where say everyone is using said application, a server solution is the most cost effective and scalable solution.

      That, and like I said in an earlier response to you, the IM Providers actually have commercial versions of their servers for corperate customers, those solutions also include secure communications, unlike std IMing which is plain text for the most part, or very very week encryption (usually to make the non provider supplied clients incompatable with those supplied by the IM Provider themselves).

      --
      I came, I conquered, I coredumped
    26. Re:daunting technical issues? by AlecC · · Score: 2

      So you make it a disciplinary offence to install unapproved software on a PC used for financial work - which is what our finance department does. And occasionally sweem pachines for unauthorised executables.

      At a certain level, it doesn't make sense to insist that something marginally untrustworth cannot be done. It is not as if installing a new IM client would be a way to instant riches, so there isn't the motivation of theft to make someone do it. A financial services house should have a culture that says that IT should approve all software. If you want play-around machines, they should be separarte from the "trustworthy" machines and firewalled off.

      After all, employees could bypass the current email logging by installing hteir own email client, or by posting from a hotmail account or... But they don't.

      --
      Consciousness is an illusion caused by an excess of self consciousness.
    27. Re:daunting technical issues? by Clover_Kicker · · Score: 1

      >It would take an admin maybe -- what? -- an hour or two to implement
      >this? If that?

      Heh. They might want to test for more then 2 hours, just a thought :)

    28. re: daunting technical issues? by ed.han · · Score: 2, Informative

      having previously worked in a financial services company, i can tell you that most of them will already disallow installation of non-certified apps on the desktop. and of course, entire departments within IT exist to certify apps on the approved firm builds. indeed, at my previous employer, users are not admins on their own PCs and hence cannot install anything.

      i cannot imagine the CTO saying, "well, IM is an important communications medium for the employee staff with one another so let's put together a team to address the scripting issues. we need to include the resulting gigs of data in our backup processes as well."

      no, i think the liability issues will simply result in IM going away permanently within financial services firms.

      heck, when i was working there, i wasn't even able to post comments to slashdot. but then again, we were obliged to run netscape as our browser and e-mail client: outlook was verboten.

      [insert obligatory outlook joke here.]

      ed

    29. Re:daunting technical issues? by AlecC · · Score: 1

      I think that you are probably one level of paranoia too high here. It is not that they expect their users to be plotting over the IM to rob the company or plan evil deeds, it is keeping a record of what promises/lies/truths were said about a transaction when it goes sour some months later. If a client says "I only bought those securities because the dealer said they were a no-fail bet", you need to be able to recall what the dealer actually did say - whether s/he properly pointed out the risks in a transaction etc.

      Generally, I don't think they are protecting against fraud on the day the conversation happens - they are protecting against cover-ups after the fact - when the heavily boosted company goes bust or suchlike. I think that if they were into direct fraud, these dealers would have other ways of doing it.

      --
      Consciousness is an illusion caused by an excess of self consciousness.
    30. Re:daunting technical issues? by pboulang · · Score: 2, Informative
      not by any means? Ever used trillian? Ever read any news regarding AIM client with encryption?

      I would be wary of what you say, because all blanket statements are false.

      But, on the third hand, the number of people that use insecure methods of IM is disgustingly large, whereby entire industries could be made sniffing AIM coming out of market makers.

      --

      This comment is guaranteed*

      *not guaranteed

    31. Re:daunting technical issues? by Ulven · · Score: 2, Informative

      Isn't this where Jabber can help?

      The company can set up their own server, meaning that all messages stay inside the company network.

      IIRC it also encrypts the messages betweeen clients.

    32. Re:daunting technical issues? by Red_Harvest · · Score: 2, Informative
      Why not use IBM Sametime (PDF)?

      Organisation-wide IM client with authentication from internal LDAP/Domino Directory

      - no need to let AOL/MS listen in on your conversations, or open up your firewalls for that matter

      - every conversation is encrypted by default

      - server can be set up to log everything

      There ARE other options than MSN Messenger/AIM, you know...

    33. Re:daunting technical issues? by Anonymous Coward · · Score: 1, Insightful

      Missing the point - in this case, all the logging is done on client machines, outside the direct control of the support staff.

      Why not configure the IM software to log to a shared network location?

      You'd need some sort of complicated transparent proxy to log normal IMs, and that wouldn't work with encrypted conversations.

      No necessarily. With a standardized, locked-down machine configuration you could configure everything on the machine to use whatever proxy options you want. Nothing much would help log encrypted conversations, but, again, if you have control of the PC you can prevent them from using encryption.

    34. Re:daunting technical issues? by Anonymous Coward · · Score: 2, Informative

      last I checked it takes less than 5mins to write a shell script that uploads these logs in the background to an ftp.

      I bet you're a perl coder. Re-read the post you just replied to. See where it says "all the logging is done on client machines, outside the direct control of the support staff."

      Just because you have a theoretical shell script uploading stuff, you're still not in compliance with the mandate that says that all IMs be saved - in the example given, if the HD goes down before the shell script runs, then you still lose part of the log.

    35. Re:daunting technical issues? by sql*kitten · · Score: 2, Informative

      Email is easy because you just mirror it on a server. You'd need some sort of complicated transparent proxy to log normal IMs, and that wouldn't work with encrypted conversations.

      Brokers aren't going to be using just some random IM client they downloaded from the web, they'll be using something like this which looks and feels like a regular IM client (MSN in this case) but is designed for the need of the finance business, with logging to a server, encryption, directory services etc.

    36. Re:daunting technical issues? by parmenio · · Score: 1

      I am not sure it is especially complicated... Morgan Stanley does this already... everytime I get a an IM from my brother, even a simple 'hey', I get this attached: Notice: All instant messages sent to and from this contact name will be received or otherwise recorded by the Morgan Stanley IM Compliance system and are subject to archival, monitoring, or review and/or disclosure to someone other than the recipient. It is almost enough to scroll his orignal message off the screen ;)

    37. Re:daunting technical issues? by ClubStew · · Score: 1

      IM isn't always for bullshitting around. I use it to contact coworkers some distance off, or to setup lunch plans with some former coworkers elsewhere in the research park - but, hey, one has to eat!

    38. Re: daunting technical issues? by evil_roy · · Score: 1

      You are correct.

      This issue is dealt with by organisations every day, all arounf the world.

      Do not let unauthorised users install anything at all.

      Simple, effective, utterly uninteresting.

    39. Re:daunting technical issues? by mshiltonj · · Score: 1

      Mandate all you want. If I have write access to my IM logs, I have access to doctor,modify, or fabricate them. Since this is the case, these should not be legal documents.

    40. Re:daunting technical issues? by nelsonal · · Score: 1

      Finance is really just trafficing in information, and the brokerages have the most information, and are in a great position to profit from that information. They are regulated in several ways to prevent them from doing this. This archive is likely to be similar to the email that the NY Attorney General uncovered so many humorously frank opinions about the .com companies from the analysts who were touting them so highly externally. The NASD largely regulates retail customer brokerage firms, the big institutions are expected fend for themselves to a larger extent as they should have nearly the same access to information as the brokerage houses, unless something like fraud happens.

      --
      Degaussing scares the bad magnetism out of the monitor and fills it with good karma.
    41. Re:daunting technical issues? by arkanes · · Score: 1

      Thats fine, and all, but do you really want to bet your buisness on that? You need something more reliable than that when you're looking at legal issues like these.

    42. Re:daunting technical issues? by arkanes · · Score: 1

      A couple other posters have replied to me with other third party solutions, too. And I agree - that's exactly what you'd need. But setting up a system like that isn't neccesarily trivial, either (and setting up logging on 5000 workstations isn't either). All the people responding by saying that you should just use a network share or a cron job to archive the logs are (still) missing the point - thats fine for home use, or whatever, but when the absence of these logs (and, more imporantly, a verifiable chain of custody) can mean jail time for you and your employees, the loss of your trading license, and all kinds of other nasties, you want something more reliable than a network share or a cron job to an FTP server. You want a server will all the normal redundancies (RAID, offsite backup, etc) that logs all the traffic. And it's probably easier to just prohibit IM - at least while you spend the time to design a system or evaluate the third party ones.

    43. Re:daunting technical issues? by Smeagel · · Score: 1

      At where I'm working now for every employee that downloads/uses sametime our department is charged $6.95 a month from our IT department. This is very fishy to me since the company I was with last year had sametime installed on every computer by default. I'm in a highly regulated industry now though, so perhaps the charge is actually from our IT department for the work required to make sure it's logged. Our AIM, yahoo, etc is already firewalled out.

    44. Re:daunting technical issues? by Combuchan · · Score: 1

      While certain IM protocols use HTTP, the thing that differentiates IM from everything else is the port--HTTP is 80, Yahoo is 5050, AIM is 5190, and MSN messenger is 1863.

      And proxy.aol.com doesn't listen on anything other than :80, as far as I can tell.

      If I were a brokerage firm IT manager, I'd be using NAT, and block every outgoing port--including :80. Set up a local HTTP proxy on :8080 and configure the proxy server to disallow certain sites like proxy.aol.com.

      To comply with logging requirements, I'd tell employees to use an AIM client like gaim (there are win32 ports) that enable connection to a specific server and port, which would be the proxy server. I've seen perl port forwarders that could easily be extended to log conversations.

      There might be things I've overlooked in my hypothetical solution, but it's 07:02 MST and I really haven't slept all that much lately.

      The point is, things are not as difficult as they are made out to be.

      --
      "[T]he single essential element on which all discoveries will be dependent is human freedom." -- Barry Goldwater
    45. Re:daunting technical issues? by muffen · · Score: 1

      While certain IM protocols use HTTP, the thing that differentiates IM from everything else is the port--HTTP is 80, Yahoo is 5050, AIM is 5190, and MSN messenger is 1863.

      Not true, most of these can be configured to go out on port 80, you just said what the default ports are.
      Yahoo will do it automatically, MSN will auto configure itself to use a HTTP proxy on port 80, ICQ/AIM can be configured to connect to the server on port 80, or be configured to use a HTTP proxy server on port 80.
      I can add that most of them work on many more standard ports, including SMTP(25) and FTP(21).

      If I were a brokerage firm IT manager, I'd be using NAT, and block every outgoing port--including :80. Set up a local HTTP proxy on :8080 and configure the proxy server to disallow certain sites like proxy.aol.com.

      Good idea, if it wasnt for this.

      To comply with logging requirements, I'd tell employees to use an AIM client like gaim (there are win32 ports) that enable connection to a specific server and port, which would be the proxy server.

      You can just use the standard AIM client, it allows you to configure proxies and ports.

      You do have some interesting points though. I think if you modify the idea slightly, you should be able to produce a workable solution. I'm gonna think about it a little later, just have to work right now :(

    46. Re:daunting technical issues? by Glass+of+Water · · Score: 1

      The logs to which you refer. God, what a disaster.

      --
      There are no trolls. There are no trees out here.
    47. Re:daunting technical issues? by Scaba · · Score: 1

      I hadn't realized the FAA and FBI were NASD (National Association of Securties Dealers) members. In fact, I hadn't realized the FAA and FBI even traded in securities or did any kind of brokering at all. You learn something new (and most likely false) on Slashdot everyday.

    48. Re:daunting technical issues? by Anonymous Coward · · Score: 0

      Do you know what a shell script is? Most logging in systems these is done using shell scripts.

    49. Re:daunting technical issues? by Anonymous Coward · · Score: 0

      This is one of the worst stories I've ever seen. So they have to log their ICQ conversations. Who fucking cares? It's really easy to do and it does not infringe on these employees rights in any way. How does tripe like this make the front page while good stories are rejected or go on the sections?

    50. Re:daunting technical issues? by fermion · · Score: 1
      As has been said, the issue is not just logging, but secure, auditable logging. If a client claims a communication, and the trader denies, then the trader better make damn sure that the logging method he uses is not some half-ass consumer grade piece of crap that won't stand up in court.

      Beyond that, there is also an issue of destroying information. If it is logged, then it should be destroyed as soon as legally possible. This is not a hard thing to do is logging is centralized and the backups are at known centralized locations. It becomes a bit harder if everyone has a copy of the logs on their own machines as well as backups of those machines which may be misplaced in the file cabinets. In such a case, the federales are going to have a field day when they come to your office.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    51. Re:daunting technical issues? by Igmuth · · Score: 1

      XP/2K support shell scripts and cron jobs?

    52. Re:daunting technical issues? by Anonymous Coward · · Score: 0

      Okay. Take the source code to gaim and modify it
      to log all messages to a SQL database via ODBC. Do not allow the running of such client until the client can log into that database.

      The technical issues are becasue most of these copmanie have ignorant staff who could not write code to save their life. IF you do not like that
      option, write a proxy server that stores all the
      data to a database. Hell how hard can it be?

    53. Re:daunting technical issues? by Anonymous Coward · · Score: 0

      Wasn't it 'Jabber' that was really a sort of proxy to all those other services?

      Why not just force them to use the proxy, log there & let them go about their business?

    54. Re:daunting technical issues? by Erbo · · Score: 1
      Jabber can do more than that. If a company had its own Jabber server which was used by its employees, it could still interact with both Jabber and non-Jabber IM systems outside the company, but all communications would be forced through the corporate Jabber server, providing a convenient access point for keeping logs. (You'd have to firewall off port 5222, of course, keeping anyone inside the company from connecting to an external Jabber server, as well as the ports for all the other IM systems.)

      Jabber has optional support for end-to-end encryption as well, depending on the client.

      --
      Be who you are...and be it in style!
    55. Re: daunting technical issues? by aminorex · · Score: 1

      So those firms which incorporate flexible and
      interoperable instant messaging into their workflow
      will have an enormous competitive advantage.
      Looks like consolidation time in the financial
      services industry, then.

      --
      -I like my women like I like my tea: green-
    56. Re:daunting technical issues? by aminorex · · Score: 1

      Did they also cut all the phone lines?
      If not, there's unlogged digital instant
      messaging, and it's probably going over the
      Internet, unencrypted.

      --
      -I like my women like I like my tea: green-
    57. Re:daunting technical issues? by Simon+(S2) · · Score: 1

      " So you make it a disciplinary offence to install unapproved software on a PC used for financial work - which is what our finance department does. And occasionally sweem pachines for unauthorised executables."

      yeah yeah.... like this would be possible everywhere. i'm a programmer, and i'm admin on my box. and i install whatever i want. and it has to be that way. and there are a lot of other people which work that way, because it has to be like that.
      in this situation, the proposed solution is just plain stupid. maybe it would work under some circumstances, but for sure it's no general solution.

      --
      I just don't trust anything that bleeds for five days and doesn't die.
    58. Re:daunting technical issues? by Anonymous Coward · · Score: 0

      Most IT Billback schemes are just office politics.

    59. Re:daunting technical issues? by AlecC · · Score: 1

      E wouldn't expect it to be "possible everywhere". That would be stupid. This would only be necessary for places like the financial services industry, because they are playing with other peoples money. Money is just numbers. Do you want somebody like you - but less honest - installing whatever they like on your bank's computer? If so, watch your account empty. Of course, dealers computers aren't as sensitive as the bank's central database, but they are still making decisions about other people's money.

      The same person whould not be dealer and sysadm, even if they have the necessary skills. The banks go to a lot of effort to keep front offs (people who make the deals) and back office (people whe shuffle the paperwork to execute the deals) separate. When they don't, sooner otr later something goes wrong: that is how Barings went down the tubes.

      --
      Consciousness is an illusion caused by an excess of self consciousness.
    60. Re:daunting technical issues? by shaitand · · Score: 1

      First, how do you know they are going into an archive?

      Second, you have to have write access to your log, because without it, your im can't write to said log, but do you have any idea how little overhead is actually involved in making a master log and copy your personal log to it every 30 seconds... on the server level, this would be an issue, over the network this would be an issue... on a local workstation this wouldn't barely qualify as overhead.

    61. Re:daunting technical issues? by shaitand · · Score: 2

      umm and if the server goes down while the emails are being processed in memory, your technically not in compliance with the mandate that says ALL emails must be saved either. I don't have to log all IM's to be in compliance, I only have to implement reasonable measures to do so.

    62. Re:daunting technical issues? by shaitand · · Score: 1

      ummm why would I care about issues faced in win32 environments. If you do your trading on win32 systems (less and less common among serious traders, linux trading software is huge) then you sure as hell won't have me as an employee... or a customer.

      If your willing to trust win32 systems then there is no real reason to have the logs on your server anyway, after all it's really no less of a gamble than leaving them on the clients and placing a nice shortcut to it on the desktop for the employee.

    63. Re:daunting technical issues? by bobhagopian · · Score: 1

      You're absolutely right that most instant message clients have the ability to log conversations. However, there is at least one good reason that the problem is more difficult. Remember the Enron case, where the FBI and SEC went through the e-mails exchanged between certain employees? Suppose one of these companies was charged with similar crimes. The government could always subpoena e-mail evidence, which resides on central servers, but can't effectively do the same thing with IM logs with are stored on a client computer. If a corporate criminal had a computer with incriminating IM logs, the first thing the he/she would do is delete the files. In short, the purpose of maintaining such evidence is so that it can be recalled. Controlling access to your own logs makes the whole purpose of keeping such records pointless.

    64. Re:daunting technical issues? by RGNewJr · · Score: 1

      This rule is an add on to the email rule. It requires all emails and IM to be stored on WORM drives and stored for 3 years. We used Face-Time to capture the IM and forward them to an email box that is captured by our compliant email storage solution. A little expensive but quite easy.

    65. Re:daunting technical issues? by RGNewJr · · Score: 1

      This rule is an add on to the email rule. It requires all emails and IM to be stored on WORM drives and stored for 3 years. We used Face-Time to capture the IM and forward them to an email box that is captured by our compliant email storage solution. A little expensive but quite easy. Logging will not pass audits without the WORM storage and if you do not have an email solution by now, you are already going to get hit by auditors.

    66. Re:daunting technical issues? by Clover_Kicker · · Score: 1

      >First, how do you know they are going into an archive?

      Isn't that what we're talking about, archiving IM messages?

      >Second, you have to have write access to your log, because without it,
      >your im can't write to said log, but do you have any idea how little
      >overhead is actually involved in making a master log and copy your
      >personal log to it every 30 seconds... on the server level, this would
      >be an issue, over the network this would be an issue... on a local
      >workstation this wouldn't barely qualify as overhead.

      Since I have permissions to write to the log, I can just overwrite the central log with a doctored one at the end of the day.

      Trying to kludge logging into AIM or ICQ would be a harder and less reliable then rolling out an IM system with centralized loggin built in.

    67. Re:daunting technical issues? by shaitand · · Score: 1

      "Isn't that what we're talking about, archiving IM messages?"

      ok, this went over your head or I wasn't clear enough. By you, I meant you as an employee.

      "Since I have permissions to write to the log, I can just overwrite the central log with a doctored one at the end of the day."

      Apparently you didn't follow this either... you need write access to your personal log, there is no reason you need ANY access permissions to the central log... What would be the point of moving the data to a central log if you had access to it?

      If you overwrite your personal log at the end of the day it hardly matters since I've been moving the information in the logs every 30 seconds to a log which you don't have access to.

    68. Re:daunting technical issues? by Clover_Kicker · · Score: 1

      >there is no reason you need ANY access permissions to the central log

      How does my machine "upload them to server using a scheduled script" if I don't have any rights to the central log?

    69. Re:daunting technical issues? by shaitand · · Score: 1

      Are you trolling or just used to a home edition of M$ windows???

      First, in truth "Your machine" would be a terminal in my network. Anything over a 1ghz should be powerful enough to run 30 brokers since they have no need to use anything that requires something more intense than text manipulation (stock quotes, text data, charts, simple math and text data, email.. ummm I rest my case?). In which case it would be especially easy to handle this isues since everything would be on the terminal server to begin with.

      But since we are pretending the data is on your workstation, and I'm in a giving mood I'll bite.

      You have an IM log in your home directory. As a user rather than administrator, your home directory is your little world and the only thing your login has permission to access. You get a little notice that says "Access Denied" whenever you try to access a file outside of it or change outside that directory. Good ol cron is running as a memory resident program (one you don't have permission to stop any more than you can access those files outside your home directory).

      Every 30 seconds (this is an arbitrary time length), cron, executing as a user defined by me the administrator WHO DOES HAVE PERMISSION, reads that file in your home directory and appends everything in it to a central log file somewhere on the computer outside your home directory. Now we have a log file, that resides on your workstation that *gasp* you don't have access to!

      If your in a business environment, no matter who your are (unless it's the network admin), even the owner, the network admin would have to be an idiot to give you full access to even your own workstation. In a Stock Exchange, there are men with guns who help make sure you don't take advantage of the fact your physically sitting at that station.

    70. Re:daunting technical issues? by Clover_Kicker · · Score: 1

      Running AIM/ICQ/MSN messenger on the employee desktop doesn't fit with the locked-down situation you describe.

      The logging solution you describe is certainly possible, but silly. If the company has taken the time and $$$ to lock down and standardize the desktop, will they duct-tape a homebrew logging facility onto a consumer IM product, or purchase a corporate IM product that comes with the features they want?

  2. But why??? by jkrise · · Score: 3, Funny

    Can't they simply use Echelon instead??

    --
    If you keep throwing chairs, one day you'll break windows....
  3. Maybe it would be easier by Anonymous Coward · · Score: 0


    If they didn't have staff, seems like humans and their tendancies are more trouble than they are worth, fkuc people over profit

  4. What's the value? by monkey_tennis · · Score: 5, Insightful

    I struggle to see the value in this. If a broker wants to have an 'off the record' conversation they could still use their mobile phone or some other mechanism. Doesn't there come a point where you have to acknowledge that not all communication that takes place at a place of work is 'owned' (in a responsibility-for sense) by the employer?

    1. Re:What's the value? by darkov · · Score: 4, Informative

      You're looking at it from the wrong side. The biggest issue is brokers is having clients ring up or whatever give instructions and then take issue later (when the trades goes bad, presumably) or the client saying the the broker told them X and it caused them a loss.

    2. Re:What's the value? by monkey_tennis · · Score: 1

      I admit it's not an angle I'd considered, but surely in the case you suggest it's in the dealer's interest not to accept instruction without an audit trail - I'd be surprised that that any external body would need to enforce that.

    3. Re:What's the value? by the+uNF+cola · · Score: 2, Insightful

      The slightest word from a worker's mouth on the status of the stock market in terms of purchasing, can give a hint to a stock owner to buy or sell.

      This is insider trading, trading with information from the inside.

      The proxy'ing is simply a restrictive measure. It makes it easier to detect. Yes, you can't monitor all communications, but it makes it harder to do live communications, especially since the sound of typing doesn't say WHAT you are typing.

      After hours stuff you can't prevent, but then again, after hours information is stale and is less usefull... though could be useful none-the-less.

      --

      --
      "I'm not bright. Big words confuse me. But Wanda loves me and that should be enough for you." - Cosmo

    4. Re:What's the value? by pak-man · · Score: 2, Informative

      Mobile phones and other methods of personal communication are banned in trading areas.

    5. Re:What's the value? by Anonymous Coward · · Score: 1, Insightful

      "If a broker wants to have an 'off the record' conversation they could still use their mobile phone"

      Err, exactly how off-the-record did they want? Do you know anyone who works at a telephone company?

    6. Re:What's the value? by Anml4ixoye · · Score: 1

      And really, the issue being addressed here is one that the government has been dealing with. We have to block all IMing because we are under state and federal laws to record all electronic communications because it is considered public record. Not only to we have to record it, but we have to make it available to anyone making a public records request for the information.

      Several people have mentioned about installing IM servers, client logs, etc, but you have to remember when it comes down to it certain things are fine until they start costing the business money at which point they become an expense and a hassle.

    7. Re:What's the value? by Anonymous Coward · · Score: 0

      I think you misreading the issue. Main reson for this is not to look for bad guys. For many years brokers and dealers were taping conversations between their clients and traders. This was done to protect the both parties from making false claims like: "I told you to sell XYZ stok at $30.00 and not at $25.00 and 1000 shares and not 10000". E-mail and IM is just the next step. As long as you can recieve orders through this media, you have to have a way to resolve disputes.

    8. Re:What's the value? by sagneta · · Score: 4, Insightful

      It's not the employer that is making this requirement. The SEC has regulated such communication since its inception in 1934 in accordance with the Securities ACT of 1933 and the Securties and Exchange ACT of 1934. This is the law. Period.

      Insider trading and information dissemination is strictly regulated to prevent classic insider stock manipulation gambits. To get some idea of how that worked you can read "Reminiscence of a Stock Operator " first publised in 1924.

      Sam Waksel who was found guilty of violation of several securities laws and could have been hung up on obstruction of justice to boot is now spending 7 years in prison. He could have gotton 40.

      The laws have become stricter more recently. Just before the bubble burst Congress enacted more legislation that prevented companies from providing non-public information to traders, analysists and the like. They mean it. Siebel executives during a dinner recently that off the cuff mentioned some data to an analysist are now having to explain themselves to the SEC. SEC is in a bad mood these days.

      The point that is lost outside the industry is that the witch hunt is on. This happens after every debacle. It is not a technical issue. The IM infrastructure *must* meet SEC and NASD ( 1938 ACT ) rules and regulations otherwise the companies face prosecution and the individuals lose Series 7.

      I am actually astonished NASD waited this long. Brokerage firms are all ready rushing to comply in 2003 because it has been assumed this would happen.

      FYI

    9. Re:What's the value? by Uart · · Score: 1

      Mobile phones are also banned from the trading floor. A trader can get in trouble/fired for using one. All in-office communication MUST be recorded, its not for the entertainment of the employer, but rather for the protection of the consumer (insider trading).

      Remember in the movie Wall Street, Bud Fox used to make all of his calls on his cell phone?

      This is not a matter of the employer "owning the communication" its a matter of the employer taking reasonable steps to ensure that their employees aren't cheating. When the SEC comes along to investigate, they need to be able to produce this stuff.

      --

      Opinionated Law Student Strikes Again!
    10. Re:What's the value? by Anonymous Coward · · Score: 0, Funny

      Yup. This is just another case of loudmouth Slashdot geeks blindly spouting about a seeming "security" violation.

    11. Re:What's the value? by sql*kitten · · Score: 4, Informative

      I struggle to see the value in this.

      No offense, but you struggle because you're a slashbot and don't know what you're talking about. All communication in and out of a dealing room is recorded. This is so a customer can call up and do a trade on the phone, and then can't "DK" - deny later making the trade. Also, it means that traders can't pass on information they shouldn't to outside.

      Traders want everything to be recorded. Those tapes can keep you out of jail.

      they could still use their mobile phone or some other mechanism.

      Mobile phones are blocked inside dealing rooms. And even if they weren't, even being seen using one would get you in trouble. Sure you can pop down to Starbucks and make a call from there - in the 10 minutes it took you to walk down there, the market's moved, any information you might be sneaking out is probably obsolete.

      Doesn't there come a point where you have to acknowledge that not all communication that takes place at a place of work is 'owned' (in a responsibility-for sense) by the employer?

      Like I say, you don't know what you're talking about. Sure a dealer can make a personal phone call, if he gets time, the bank don't care, they just think he's schmoozing a customer. The only time the tapes are listened to is if something comes to court. This protects everyone involved, the customer, the dealer and the bank.

    12. Re:What's the value? by andy1307 · · Score: 1

      A simple IM message saying "Did you get my message on the results for company X" may not be critical when the message is actually being sent. It may assume importance later but you wont know it when you send it.

    13. Re:What's the value? by darkov · · Score: 1

      I guess the other side of it is where a broker is doing something shifty (front running, insider trading, etc) and the government and/or the compan want eveidence to stomp on them. Although for most employers/employees there is some basis for privacy, if you're a broker sitting at your desk you're out of luck. These folk handle multimillion and billion dollar transactions every day. Everything needs to be recorded.

    14. Re:What's the value? by TopShelf · · Score: 1

      When you consider that SEC violations can result in lawsuits and settlements with brokerage firms that result in awards totalling tens and hundreds of millions of dollars, it's worth both the SEC and the brokerages ensuring that these controls are in place.

      --
      Stop by my site where I write about ERP systems & more
    15. Re:What's the value? by SuiteSisterMary · · Score: 1

      When you think that it's the gov't who has to pay for the litegation and what not when somebody loses their shirt doing something stupid, it IS in their best interests to enforce it.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    16. Re:What's the value? by harmoniousness · · Score: 2, Informative

      Sql*kitten says: "Mobile phones are blocked inside dealing rooms."

      Well, some! I worked in a certain big dealing room in London, where they even installed mobile antenna repeaters to improve reception. Use of personal webmail accounts was rampant. It was understood - if you're making a deal, use a taped line!

      I agree with the first poster - someone has to acknowledge that not all communication is owned.

      But there are deeper reasons for this.

      To encourage logged IM is nice - it allows dealers to use IM for work, and improve their efficiency. However, once one dealer wants to make deals over IM, either all other dealers must follow, or risk entering into contracts on unlogged channels.

      So the NASD is really saying: IM is a good idea - but if we want to use it for our work, we've all got to start logging!

    17. Re:What's the value? by Anonymous Coward · · Score: 0

      Traders want everything to be recorded. Those tapes can keep you out of jail.

      If that's true, why aren't they saving these things already - why do they need to be told to do so?

  5. That should be easy by Daath · · Score: 3, Interesting

    Just build a custom Jabber server that saves everything serverside!

    Call it Corporate Jabber or something... Users should, however, be warned of the logging!

    Recently, here in Denmark, an employee of a company was dragged in court, because she was sending private mails from work (through an online dating site). The court ruled that it was ok, and that the company should stay out of the employees private life - even if she had some [private life] at work. Go Denmark ;)

    Anyway, there are lots of things to think about when logging...

    --
    Any technology distinguishable from magic, is insufficiently advanced.
    1. Re:That should be easy by arkanes · · Score: 1
      I believe that Jabber uses end-to-end encryption, so the server couldn't actually log like this - unless the Jabber protocol is trivially vulnerable to man in the middle attacks, or you add an extension to the protocol.

      On the other hand, using a Jabber server as a front end to the other IM networks would probably work.

    2. Re:That should be easy by interiot · · Score: 1

      Yeah, encryption and stuff doesn't really matter in this context... ssh uses encryption too, but court rulings still stand... corporations like this are required to set up an extra ssh server on the firewall edge that everyone on the inside connects to (and where things are decrypted and logged) and then from there makes one more ssh connection to the outside.

    3. Re:That should be easy by Phantasmo · · Score: 1

      Some Jabber clients are capable of end-to-end encryption, but aren't. However, client-to-server encryption through SSL is quite common.

      So, this would work very well in a corporate environment (except for your GNU/Linux users, happily chatting away using Tkabber and GnuPG), but don't trust plain-old Jabber for your personal, confidential communications! You could be snooped on by the admin!

      --

      The US Army: promoting democracy through unquestioned obedience
    4. Re:That should be easy by IamTheRealMike · · Score: 1
      Just build a custom Jabber server that saves everything serverside!

      Or use the premade ones from Tipic, Jabber Inc etc.

      I mean, this problem just screams "JABBER!!!" as a solution. Log it all server side. Transports for when employees need access to the proprietary networks. Server side logging is trivial. No worries :)

    5. Re:That should be easy by Sloppy · · Score: 1
      If we're talking about something that is acting on behalf of one of the parties interests, then it can have a copy of their key.

      Or just store the ciphertext, and the broker can decrypt it later when the customers says, "I never said buy SCO!"

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    6. Re:That should be easy by axxackall · · Score: 1
      The question is: if you log encrypted Jaber message, is it possible to decrypt it later, having proper keys? In other words, are those keys (used to encrypt) rapairable later?

      I guess, if you logg all encrypted mesages, you have to log the keys used to encrypt them. But if you log the key on the same server than for the server the message is not encrypted anymore.

      Or did I miss anything?

      --

      Less is more !
    7. Re:That should be easy by GoRK · · Score: 1

      That is what we do here. I work for an NASD member firm with logging requirements similar to those of the trading firms. I got a patch for jabber somewhere that spits out the messages, then I stuff it into a database and archive it out of there. As a side benefit to using Jabber, we can IM to AIM, MSN, etc. without losing the required logging. Highly recommended -- this saves us thousands of dollars in telephone charges monthly.

    8. Re:That should be easy by Anonymous Coward · · Score: 0

      Any technology distinguishable from magic, is insufficiently advanced.

      Remove the comma in your sig. It's grammatically incorrect, as it separates the subject, "technology", from the verb, "is".

    9. Re:That should be easy by Anonymous Coward · · Score: 0

      haha... so were you fired from LEK (or whatever they call themselves now) or just quit....

      ~GoAT~

  6. "Daunting technical issues"?? by The-Bus · · Score: 2, Insightful

    You mean, like the logs you can keep in ICQ? And if AIM/others doesn't support it, don't you think AOL will implement it pretty damn quickly so they don't lose market share in that industry?

    --

    Small potatoes make the steak look bigger.

    1. Re:"Daunting technical issues"?? by xpulsar87x · · Score: 1

      While resource hacking my copy of AIM at work here (we run win2k, deadaim doesn't work properly for some reason), I noticed several dialogs in the resource file already that seem to be dedicated towards logging. Someone also said that MacAIM supports it, so perhaps the Windows version has it as a planned expansion but just hasn't been completed yet?

  7. This is ridiculous... by brucmack · · Score: 2, Interesting

    What's next? Are they going to make it a requirement to keep audio tapes of all conversations, phone or otherwise, for 3 years? Surely they must stop sometime when the cost of implementation greatly outweigh any benefits.

    1. Re:This is ridiculous... by Anonymous Coward · · Score: 4, Informative

      Actually at my firm, we do log all calls made from our traders' phones for a 3 year period, it's more a protection against illegally/incorrect executed market orders, and liability mitigation and it is not an SEC requirement.

      If you think this is bad, we need to have full data backups for files, fax, and e-mail transmissions for a 7 year retention. That eats up a lot of tape...

    2. Re:This is ridiculous... by tgma · · Score: 3, Informative

      It may not be an SEC requirement, but isn't it an NASD requirement? I've been working at brokerages for the last ten years, and it would have been unthinkable for us not to have our conversations recorded.

      It wasn't just the traders and the salesmen, but the analysts as well. Maybe it wasn't a regulatory requirement, but it's definitely part of doing business in securities, because so much is done over the phone. It was actually surprising how little we used those recordings after they were made, but maybe we were just fortunate. Mostly it was to check trades, but the threat was always there that if you gave out inside information, you could be nailed.

      Interestingly we were allowed to use mobiles on the trading floor, but I can imagine that people are much more cautious in the US. Post-Spitzer, they are all running very scared. Most US investment bankers that I talk to now, virtually have to append a disclaimer to everything that they say. Must make for some interesting pillow talk.

    3. Re:This is ridiculous... by anjrober · · Score: 2, Interesting

      I use to work at a brokerage firm, a big one, and they do exactly that. Record each and every call that comes in. All of them. And the real kicker is they use the recorded calls all the time. They have to go back to the calls to find out exactly what was said and when.

  8. Foolish... by andreMA · · Score: 2, Insightful

    I can see drawing an analogy between email and postal mail and requiring the saving of that correspondence, but IM is better treated as telephone conversation -- which apparently isn't required to be saved.

    1. Re:Foolish... by Anonymous Coward · · Score: 0

      Actually, the NASD does require that phone conversations, e-mail and basicaly any communication between a licensed broker and anyone he/she gives market information to or might give market information to be stored for a minimum of 3 years and in some cases, 7 years. This is whats known as CYA (cover your a$$) in the business. It's really hard for the smaller firms to comply with some of this stuff tho. Even compressed, you hve any idea how much space an hours worth of phone conversations takes up? There is in existance, network based devices to record and index these conversations but they cost tens of thousands of dollars. IM logs, being text based would have to be many times smaller. Securities firms are already used to storing large amounts of documents and data files (or they had better be used to it). I don't see where having to store a few more megs would be that big of a deal.


      Megabyte
      Who is too lazy to register.

  9. Instant message : Sell SCO!! by jkrise · · Score: 1, Funny

    Hey brokers! Sell SCO! Sell SCO!! Sell SCO!!! Sell SCO!!!! Sell SCO!!!!! Sell SCO !!!!!!

    Got the message?

    Okay.. now log all you want.

    --
    If you keep throwing chairs, one day you'll break windows....
    1. Re:Instant message : Sell SCO!! by Prof.Phreak · · Score: 1

      Actually, this is precicely what they'd want you to do - "a large company going through a period of unpopularity" is usually a bargain stock wise. If everyone sells (and you buy) and assuming the company survives, a few years down the road you could've made a hefty profit (you bought really low - when everyone was selling).

      Or so me thinks...

      --

      "If anything can go wrong, it will." - Murphy

    2. Re:Instant message : Sell SCO!! by fliptout · · Score: 1

      Or you could short the stock as it goes down the tubes and then buy it when it hits rock bottom.

      --
      A witty saying proves you are wittier than the next guy.
  10. Boom Town by Deton8 · · Score: 3, Funny

    These new data retention laws are a boon to those of us in the data storage industry. If this keeps up I'm going to name my new yacht after the dude at the SEC (although "Cunt" is probably already taken).

  11. Have they looked at facetime? by alistair · · Score: 3, Informative

    From the facetime.com website;

    "Since 1999, FaceTime has been delivering instant messaging (IM) solutions for the security, management and control of IM in the enterprise.

    Our integrated enterprise IM management suite of products address the challenges of:

    * Network and Information Security
    * Regulatory and Corporate Compliance
    * Call Center Customer Service

    IM Auditor has been chosen by 32 of the largest 100 financial institutions and 7 of the 8 largest U.S. banks including Bank of America and Wachovia Securities to satisfy regulatory compliance requirements."

    The one thing that wouldn't be addressed is encrypted clients suched as the recently discussed Nullsoft "Waste" IM client. However, with businesses increasingly becoming addicted to IM clients and Blackberry devices, this would be a far more palatable solution than banning IM completely.

    1. Re:Have they looked at facetime? by Anonymous Coward · · Score: 1, Informative

      Yes. It what we're doing in my NASD-member company. There's two big problems with it:

      - Very expensive. Like, 6 figures expensive for a single node license (up to some number of users.) And then you pay another $10K+ or so for each extra IM client you want to support. (So we standardize on AIM and only need the AIM plugin.. that's about $65K for a standalone information)

      - You still need to save the logged data somewhere. It gets expensive, and more importantly, its safekeeping become a liability. So we outsource the storage offsite. Dedicated circuit is cheaper than having the NASD come in and say "Show us your logs!" and us running around to recover them on demand.

      You drop encyrpted AIM traffic, that's all there is to it. Just need to figure out how to cleanly redirect the AIM traffic through the FT proxy... ugh. Desktop support will not be fun. Glad I don't have to do that part.

      Or we could have used AIMsniffer and saved a bundle all around, but nooooo... and we even wrote an in-house version of AIMsniffer before it came out. Hint.. ethereal can decode normal AIM pretty easily.

    2. Re:Have they looked at facetime? by Jackson+Five · · Score: 1

      It's great that you decided to post an Ad for facetime, but seriously.... there are probably 20 small companies with IM's that are secure and log.

  12. This is understandable by Millbuddah · · Score: 4, Insightful

    Considering the recent media frenzy over Martha Stewart's case regarding insider trading, this really shouldn't come as much of a surprise. They're only trying to cover their own ass by having records for evidence if any insider trading information is being passed along with these instant messaging programs.

  13. Use Trillian by los+furtive · · Score: 1

    Trillian has excellent logging facilities on a per user/contact basis for all of the major IM services, and can be obtained for free.

    --

    I'm a writer, a poet, a genius, I know it. I don't buy software, I grow it.

    1. Re:Use Trillian by intermodal · · Score: 2, Informative

      and for any firms wanting to use linux, BSD, or OSX on the desktop, GAIM builds above .60 all have excellent logging and even have a good division-by-conversation format. Though your best bet for logging it all would be a custom jabber server that would save everything serverside (with warnings at conversation starts, of course)

      --
      In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
    2. Re:Use Trillian by Nick+Harkin · · Score: 1

      Actually, Gaim is now avaliable for win32 machines, although I'm not sure if it has logging, I would imagine it did.

    3. Re:Use Trillian by intermodal · · Score: 1

      yep...it's still a little buggy though. It has issues with the buddy list when MSN isn't running yet not connected (like down in the system tray)

      --
      In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
  14. Daunting? by kikta · · Score: 2, Interesting

    I don't see why they couldn't standardize on something like ICQ, Trillian, a Jabber client or anything else that logs everything. Then all they have to do is set the log to be saved on a network drive, rather than thier own. Is that really so daunting?

    Shit, I have logs for the last two years on this system. If you look at my laptop, it has logs from 1999 back to like 3 months after ICQ was first released. I was "daunted", but I overcame! ;-)

    1. Re:Daunting? by pointwood · · Score: 1

      erhm...as others have said - Use Jabber and let it log everything on the server.

    2. Re:Daunting? by Anonymous Coward · · Score: 0

      You'll find it's a wee bit more difficult to admin other people than it is to admin yourself--unless you have mental issues, in which case you already know what the average user is like. :)

    3. Re:Daunting? by Anonymous Coward · · Score: 0

      Since when is a serious comment with some sarcasm a Troll?

    4. Re:Daunting? by kikta · · Score: 1

      So administrating idiots in respect to IM is more daunting than usual? I don't buy that argument. Is it a pain in the ass, especially due to the legal requirements? Yes. Is there cause for that sector to freak out & consider banning IM (in the generic sense)? No.

    5. Re:Daunting? by Anonymous Coward · · Score: 0

      If you look at my laptop, it has logs from 1999 back to like 3 months after ICQ was first released.

      I only just managed a 7-digit ICQ number when I joined in March 1998, so it's been out longer than you think.

      I managed to keep all my logs from back then too, but gave up last year when I switched to using Trillian (which is *far* better too).

    6. Re:Daunting? by kikta · · Score: 1

      I joined sometime in the spring of 1997. ICQ was launched in December 1996 and I have a 6-digit number, 198150.

      I remember telling my roomate that the idea was going to be huge and he basically told me that it would be a flash in the pan. So I said, "Wanna be... hey, that asshole owes me money!

    7. Re:Daunting? by Anonymous Coward · · Score: 0

      Alright, now multiply your situation by 50,000 employees. Suddenly things are non-trivial again.

      Raise your head, open your eyes, and look past your own little island. See that? That's the rest of the world.

    8. Re:Daunting? by kikta · · Score: 1

      Ok, Troll, how is that any different that any other application that needs a standard configuration? Huh? Tell me, because I'd like to know how it is "off my island".

      You tell me why doing a standard configuration that saves the logs to a standard place (preferably on the network) or a Jabber setup that save it all on the server is different and "non-trivial" in comparison to getting everyone's email set up properly.

  15. Reuters already offers an IM client for them by Anonymous Coward · · Score: 2, Informative

    http://about.reuters.com/productinfo/messaging/

    Its actually pretty nifty, corporate IM already exists and I am sure if Reuters does not have built in logging they will add it quickly and dominate another part of IT for the financial community.

    1. Re:Reuters already offers an IM client for them by HomeGroove · · Score: 1
      They do have logging and it's auditable. C'mon, don't you guys listen to Market Place? I think they're an underwriter. At least they are an underwriter on something on NPR.

      Also, according to this page:

      Optional message logging features to meet industry compliance requirements
      I'm actually surprised that most companies do not use corporate IM services. I guess it's only a matter of time.
      --

      ----
      Spam subject of the moment: Offshore account secrets -nashville disrupt

  16. Knowledge is power or was it data-logs are power? by lordsilence · · Score: 1

    I can't for one, understand the need of gathering data and logs about everything. Sure, making sure nothing illegal is going on. But is there nothing called privacy in the US anymore?

  17. Keeping records for future lawsuits by Rosco+P.+Coltrane · · Score: 1

    So, for the purpose of having evidence for future possible lawsuits, first email messages must be recorded for 2 years or whatever, then IM messages, then what next ?

    Here's a way to take care of the problem for good : log *all* incoming and outgoing TCP, UDP and ICMP packets, so you'll have plenty of evidence when that lawsuit comes. And hire me to sift through the records to find that crucial piece of evidence : it won't take me very long and I only take $45/hr. I'll sell you hard-disks to store all the packets too if you want ...

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
  18. Yes they are... by alistair · · Score: 5, Informative

    Most banks already log phone calls, what is being added is the requirements to archive email and IM messaging.

    Do a quick search for "Basel 2" or "Basel ii" for more details on this. One very interesting quote I found is;

    "The Institute of International Finance has projected a total investment of US$2.25 trillion over 5 years for the 30,000 banks that will be affected, on top of systemsâ(TM) budgets, implementation costs and training. With such a huge increase in costs, this may precipitate another round of banking consolidation, especially in Asia. Basel 2 will certainly reward banks with sophisticated management and systems â" they should be able to generate higher returns on equity, and have less capital required by the market and regulators."

    1. Re:Yes they are... by brucmack · · Score: 1

      Thanks for pointing out my ignorance :) I had no idea it went so deep.

    2. Re:Yes they are... by richg74 · · Score: 1
      Most banks already log phone calls, what is being added is the requirements to archive email and IM messaging.

      All banks, brokerage houses, etc. in the US log phone calls from the trading/dealing room, and have for years. I worked as an IT Director on Wall Street for ~20 years, and this is a big deal. For one thing, the law requires it: the firm can be summarily closed down or heavily fined for failing to follow the rules. (And, BTW, you get audited frequently by the regulators, who are singularly lacking in a sense of humor about these things.)

      Also, it only makes sense in a business where transactions worth $ millions are routinely done over the phone. Having a record protects everyone in case of "bad memories".

  19. Already somebody's business by hrieke · · Score: 2, Informative

    IMLogic does this, and is quite good at meeting these requirements (one of their coders is a friend of mine).

    As for the daunting bit, hyperbole anyone?
    --
    III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIIIV IIVIIIIIIVIII...
  20. Re:record everything by signifying+nothing · · Score: 5, Informative
    Don't get overexcited - this is only for communications with clients, not for purely internal conversations.

    The Slashdot summary says otherwise, but the press released linked to is pretty clear.

  21. Re:If using Windows... by switzer · · Score: 1

    What about sending SMS messages (like you can in ICQ)???

    Gaim also has logging facilities - it is also churning out releases every few weeks...

  22. The obvious solution is quite easy... by ites · · Score: 1
    What businesses need are historical file systems in which every single data file is tracked through its every version. The point of logging messages is not to monitor them so much as to find the 'guilty' parties when problems have happened. A historical file system can provide this, but at every level: web, ICQ, email and documents.

    This may seem extreme, but disks are big enough, if you don't mix business and pleasure. Perhaps some partitions (swap) that are not historical...

    A killer application for Linux in the business workplace, perhaps?

    --
    Sig for sale or rent. One previous user. Inquire within.
  23. Makes sense to me by jamie(really) · · Score: 5, Insightful

    Brokerage firms make deals minute to minute, and conversations with a broker are legally binding. There isnt time to fax a contract back and forth. If you phone anyone at a brokerage firm, you will be recorded. Something to remember before you phone your mate and tell them about your weekend in ibiza. I totally understand why banks would view instant messages as the 21st century equivalent of a phone converstaion. Get over it!

  24. Trillian... by Anonymous Coward · · Score: 0

    I see a bunch of posts supporting Trillian -- for its logging capabilities. But there is another even better reason to use Trillian: automatic message encryption!

    Log this, big brother.

  25. Hmm by Ryvar · · Score: 1

    One of my best friends works as a trader (not sure of actual title but something roughly equivalent) at one of America's top three brokerages. Believe I'll be teaching him how to use Remote Desktop shortly (sorry, no X11 over SSH tunneling, he's not exactly a 'real' geek).

    --Ryv

  26. two words... by Unominous+Coward · · Score: 1

    SSH tunnel

    --
    "Smoking helps you lose weight - one lung at a time" -- A. E. Neumann
  27. Wow.... by JaJ_D · · Score: 1

    Storing all AOL/YM for 3 years!!!! If someone has to wade thought that crap! Please pity them

    Two hundred million AOL/YM - 95% of them porn.

    Wow RSI with no typing involved. That hasn't occured since the Cindy Crawford work out video

    :^]

    Jaj

    1. Re:Wow.... by Prof.Phreak · · Score: 1

      If someone has to wade thought that crap! Please pity them

      Hey, if it's a paying job, why not?

      --

      "If anything can go wrong, it will." - Murphy

  28. Where I work... by willis · · Score: 4, Informative
    I work at one of the larger investment banks...

    rules:
    All emails are kept (Archived, not by us)
    No external email accounts (it's a big offense if you use hotmail, etc, from work)
    Internal instant messaging (logged, of course)
    No external instant messaging (you crazy? Hell no -- you can't just install random software from the web on a trader's desktop
    All phone calls are recorded (not sure how)
    Cell phones are banned on the trading floors (I see them sometimes (and carry mine), but I think it's not cool).
    There might be cameras, but I don't know.

    All of this promotes accountability & transparency... and is good for clients and the market in general...

    It's not like they look/read everything, but it has to be on file in case of a lawsuit, etc.

    re: the guy talking about remote desktop, etc...
    That might work at some firms, but I'd imagine most of the bigger firms are really, really locked down.

    --

    there is no thing
    what else could you want?
    1. Re:Where I work... by Surak · · Score: 2, Informative

      All phone calls are recorded (not sure how)

      That's not difficult. I used to work for a company that does this. There are companies that make reel-to-reel recorders specifically for the purpose of being hooked through a PBX phone system so that it can record all incoming and outgoing calls made on specific extensions (or all extensions you if specify it that way I suppose)

      re: the guy talking about remote desktop, etc... That might work at some firms, but I'd imagine most of the bigger firms are really, really locked down.

      How locked down? PuTTY can do SSH through any HTTP proxy server that allows CONNECT (which most of them if you want to support SSL). And it can use SSH's X11 forwarding capabilities. So setup a Linux box on a cablemodem at home, ssh into it and start launching X applications (i.e., gaim).

    2. Re:Where I work... by willis · · Score: 1
      How locked down? PuTTY can do SSH through any HTTP proxy server that allows CONNECT (which most of them if you want to support SSL). And it can use SSH's X11 forwarding capabilities. So setup a Linux box on a cablemodem at home, ssh into it and start launching X applications (i.e., gaim).
      That's amazing. I had no idea.

      --

      there is no thing
      what else could you want?
    3. Re:Where I work... by Surak · · Score: 1

      I do it all the time. ;) Of course you need an X server running on your PC, such as Hummingbird eXceed or XFree86/CygWin...

    4. Re:Where I work... by Eevee · · Score: 3, Insightful

      Timeline:

      0700 - Get coffee, gossip with coworkers.

      0800 - Install PuTTY on company computer.

      0815 - ssh to home.

      0817 - Get escorted out of the building by two rather large and unfriendly gentlemen.

      0900 - Apply for unemployment insurance.

    5. Re:Where I work... by Anonymous Coward · · Score: 0

      "No external instant messaging"

      clients like it, many of your competitors have it.

      so, you will have it too, soon.

    6. Re:Where I work... by Anonymous Coward · · Score: 0

      I am a trader at one of the bulge bracket banks and we are not nearly as strict. We have our cell phones on the floor and they encourage us to be able to login from home (so that we can do any analytical work over the weekend). We also use external IM programs (like AOL, Hub, or Bloomberg) to talk to clients and other brokers. They are all logged though along with our phone conversations. Also, our web access to external emails isn't blocked. Of course between 9:30 and 4:00 you rarely get anytime to check that email or talk on your cell phone.

    7. Re:Where I work... by Microbrain · · Score: 0

      What type of company do you work for?
      Did you have to sign anything that says you can't do that?

    8. Re:Where I work... by kindbud · · Score: 2, Informative

      How locked down? PuTTY can do SSH through any HTTP proxy ...

      Say goodbye to your job as a trader. Exactly what is it about IM that makes people hatch plans to get fired over it?

      --
      Edith Keeler Must Die
    9. Re:Where I work... by TaraByte · · Score: 1

      if you set up Squid on your linux box, and configure it properly, then you can actually set up Trillian (Jabber, etc.) and connect to all of the IM services thru SSH.

      This is what I do at my job, to protect my personal privacy. The company has blocked all of the IM ports and logs all web activity, but thanks to SSH tunnelling, I can do what I want and have all the traffic encrypted.

      --
      Security is inversely proportional to the commitment of one desiring to circumvent it.
    10. Re:Where I work... by Anonymous Coward · · Score: 0

      jeez, y'all are not writing down every conversation you have as well? someone is gonna come down hard on your unaccountable asses but(t) quick.

      makes me glad i work in software. and not many things can do that!

    11. Re:Where I work... by Anonymous Coward · · Score: 0

      Large companies have had such restrictions in their employee manuals for a decade or more, and they've got the law to back them up.

    12. Re:Where I work... by RollingThunder · · Score: 1

      The overly-used term would probably be "addiction".

  29. Your .sig: by Anonymous Coward · · Score: 0

    III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIIIV IIVIIIIIIVIII...

    Is that supposed to be PI in roman numerals? 'Cause it looks like you have 3.1449..., instead of 3.1459...

    1. Re:Your .sig: by The+Mayor · · Score: 1

      Well, without spaces, it's a little confusing. But he actually has 3.14159....the adjacent 1 & 5 look like a 4. But, in either case, the Romans never thought in terms of decimals. I would assome a better way to write it would be something along the lines of:

      XXII / VII (approximately)

      --
      --Be human.
    2. Re:Your .sig: by Anonymous Coward · · Score: 0

      Learn PI - 3.1415...

  30. Not a problem... by httpamphibio.us · · Score: 2, Interesting

    Every other client logs except AIM... DeadAIM, AIM+, MyIM

    Problem solved.

    --
    sig.
  31. If China can do it by Anonymous Coward · · Score: 0

    then so can Wall St. brokerages. Doesn't seem too difficult.

  32. Client version? by BluGuy · · Score: 1

    Don't you think that larger firms are using more enterprise style apps tha AIM? All of the big business oriented messaging apps offer server side logging, and it's probably searchable and closed to boot. I think even AIM has a enterprise version out or coming out soon.

  33. boy i'd love to be the sysadmin by freedommatters · · Score: 1
    tail -f chat.log | grep -i "dead cert"

    john

  34. There are no daunting technical issues by arrogance · · Score: 1
    I know others have already commented on it but: standardize the client that you use and make it secure. Basically if you want to use IM at your brokerage, you have to use the one that the industry body requires. It's a useful tool but maybe if you want to do your front-running and insider trading you shouldn't use port 80 to do it.

    And who the hell seriously expects AIM (or other IMs currently out) to have good security? It's going out over HTTP. C'mon.

  35. Sametime by Anonymous Coward · · Score: 0

    For internal traffic, IBMs IM program Sametime can be made to log messages sent through it.

    As for external messaging, it supports SIP, so any external IMs will also get caught if its set up properly.

    1. Re: Sametime by I_M_Noman · · Score: 1

      That's what my firm uses. For those who absolutely have to have AIM connectivity as well (for client communication) you can configure the Sametime client to access your AIM buddy list too.

      Interesting, though -- my firm requires that we purge e-mails after 15 months, not three years.

  36. Subject to the same law as email by inepom01 · · Score: 1

    Email must be filed in a special format, and so must all IMs. There are many different IM messaging formats, so what you really have to do is be able to speak every protocol (or just any that your client might be using, which is still quite a few) out there and translate every message into the DB format. And of course you have to set up the database and make sure you don't run out of space, etc. It is quite daunting, if you think about it. Trillian logs might be good for you, but they are not for the NASD.

  37. Logging crypted traffic by arth1 · · Score: 2, Informative

    It's easy enough to log encrypted traffic. Decrypting it afterwards can become more of a problem, but not unsolvable.
    Clients can be modified to securely send a copy of their session keys to a central repository, for example.
    Or the proxy can do the authentication for the clients, pretending to be the other end, and establish its own encrypted session with the clients.
    Or, for dual-key systems, instead of the normal M*N pseudoprime, there's an M=(X*Y) where Y is a fixed value known to the company -- in effect a "master key" to allow decryption. This is already used for logging encrypted email from employees in many places.

    Another thing is whether it won't be easier to just ban instant messaging altogether. More and more companies do so, both out of productivity concerns and for multiple security reasons (not only can it open up for bringing harmful content into the environment, but also be used to quickly send confidential information to those who shouldn't get it).

    Time to revive "talk" :-)

    Regards,
    --
    *Art

  38. Re:My.sig: by hrieke · · Score: 1
    I think my sig get more attention then my messages (or it appears that way!). I have at home a email folder just on this topic. *grin*

    Long story short- my sig was in response to someone else's sig that read to the effect of "It's like calculating PI in Roman Numerals".

    And while the romans never thought in terms of decimals, they did think in terms of fractions, (giving us the word decimation for example) -

    Etymology: Latin decimatus, past participle of decimare, from decimus tenth, from decem ten.
    www.m-w.com
    --
    III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIIIV IIVIIIIIIVIII...
  39. heh... by ed.han · · Score: 1

    as someone who's had dealings with reuters and used some of their apps:

    1. this isn't a discrete app; it's part of the reuters app suite. it's bundled w/ any of their products, which generally start at $500/month.
    2. reuters does nothing "quickly".

    ed

  40. Back to basic by Groote+Ka · · Score: 1
    Well,

    There is a good reason to go back to pen and paper. Well, it'll cost you a stamp, but you'll get something in return: in the Netherlands, there's a saying "Wie schrijft, die blijft": When you write, you will be remembered.

    Only the paranoid survive - Andy Grove. Apparently, people listened to him.

  41. Most firms have done this for a long time. by michael7 · · Score: 4, Insightful

    I work at one of the large investment banks and instant messaging has become a large part of how traders do business. They communicate with people from other firms, quote prices, and even make trades. All of this is much more efficient and effective than email or even the phone. The recording of these communications is mostly there to settle disputes. If I quote a price to you over IM and you accept the trade is done, and if later you come back and dispute the price, there needs to be some way to settle it. This is the main reason phone calls and emails are all recorded and saved. It is a good deal for the banks, along for the SEC when investigations come up.

  42. lawsuits are power by ed.han · · Score: 1

    caveat: IANAL.

    remember that all company-owned equipment (hardware, software and other data alike) are just that: company-owned equipment. you do it or say it on company time, using company equipment, and especially if it's in written form, it can and will become evidence in any legal proceeding.

    do you remember a few years ago when analysts (e.g., mary meeker) that were bullish on IT were later sued after the bubble burst? part of the evidence produced by NY AG spitzer's discovery process were old e-mails in which analysts panned a stock privately while retaining a buy rating on it.

    now IIRC, those suits were settled, but don't think this had zero impact on financial services IT policies.

    this is simply an extension of the same.

    ed

  43. Re:record everything by Anonymous Coward · · Score: 1, Insightful

    Well, I work for a large trading company, and we installed IM here a few months ago. It was enabled for about 3 weeks, and then they decided it needed to be archived, and they couldn't do it, so it was disabled.

    This is for all employees, not just brokers or in communications with clients.

    So, in spite of what the press release says, paranoid companies are following these rules for all employees.

  44. re:record everything by ed.han · · Score: 1

    while that's technically true, what's the likelihood any firm's IT group won't simply say, "jeez, maintain 2 standards for internal vs. external? screw it; log it all!"

    beyond that, however, there are periodically sales/trades made internally: 2 large business units in different functions might legitimately be doing business together. then what?

    with giants like morgan stanley not meeting its numbers for the quarter, i don't think it's realistic that their IT departments are going to have the time and/or resources to deploy a two-pronged solution.

    ed

  45. paranoia by Clover_Kicker · · Score: 1

    I think we're talking about a heavily regulated and highly paranoid industry, but I admittedly don't have any direct experience.

    If I was rules enforcer for the licensing body, I wouldn't OK a naive/easily spoofed IM logger.

    If I was a techie for one of these trading companies I'd extend my day-to-day paranoia to IM logging.

  46. Just Log to Network Share? by TargetBoy · · Score: 1

    Why not just set up the IM client to create the log files on a network share instead of the client PC?

  47. Not Mentioned by endofoctober · · Score: 2, Interesting

    One aspect of this that wasn't mentioned in the article - is the NASD worried about chat sent to SMS-enabled phones they issue to brokers/workers? They seem to be pretty strong on desktop chat clients, but brokers looking for a way to chat without logging could always encourage clients to go mobile to get around it.

    --
    - Jack
  48. Tunneling by borgasm · · Score: 2, Insightful

    Unless you have a fantastic firewall, instant messaging loggin can be circumvented by tunneling.

    Currently, I have an SSH tunnel to my home, over which I encrypt all traffic, web, email, and instant messaging.

    Pefereably, I would like to have an encrypted connection everywhere (thank you GAIM plugins), but this will have to do.

    It is useless to log the SSH packets...so the only solution I see is to install a PacketShaper, and maybe filter out all SSH...but surely somebody must be using SSH legitimately...

    Bottom line: logging communications is very difficult....

    1. Re:Tunneling by LostCluster · · Score: 1

      SSH protects your traffic from being understood by anybody who intercepts it, but still results in traffic that is oviously encrypted. In this sitation, that'd be enough evidence to get you in trouble because you're hiding something even though they won't know what.

      No stock market trader is using SSH on their desk machine, they want everything they do to be logged to cover their own ass.

    2. Re:Tunneling by Anonymous Coward · · Score: 0

      Actually, the bank I work for blocks ssh, even for developers. I suspect this is pretty common among the institutions of reasonable size, since most folks know you can tunnel ssh.

      Our traders had their Reuters- or Bloomberg-based (can't recall which) IM turned off recently because of this regulation. I think that was smart, but I do wish the sysadmins would set up an internal, logged, no-encryption Jabber server so I could use it to communicate with my coworkers.

      And, off the record, it remains possible to HTTP tunnel to a privately owned Jabber server from here, just not using Exodus. ;-)

    3. Re:Tunneling by kindbud · · Score: 1

      Unless you have a fantastic firewall, instant messaging loggin can be circumvented by tunneling.

      Not a great idea to try if you are a broker who works for a firm with a IM retention policy. Your tunnel would cost you your job if discovered. And for what?

      --
      Edith Keeler Must Die
  49. What an opportunity by Caceman · · Score: 1

    Think about this. A brokerage, set up their own IM servers that will log all traffic going through them. Then, the brokerage offers an IM client to all of their clients that offers direct access to their broker. Brand it with the brokerage's logo, and charge the client a "convenience fee". Boom - non-traditional revenue.

  50. Lose Market Share? by lysium · · Score: 1
    We are talking about a free instant messaging system here. Brokerage house employees probably constitute .00001% of the total IM market. I don't see anyone rushing out to help them.

    Now proprietary, commerical IM developers....they will be the ones to capitalize on this, if any.

    ---

    --
    Together, we will drive the rats from the tundra.
  51. tech issues NASDAQ firms dont know IM by linuxislandsucks · · Score: 1

    Jabber for almost two years has had a commercial version setup for just this purpose of being able to log and save IM messages jsut for this prupose and others..

    Maybe they should checkout jabber rather an blindly trust their IT stafff?

    --
    Don't Tread on OpenSource
  52. This isn't anything new by DigitalRover · · Score: 1

    Secure and auditable Instant Messaging has been something the financial industry has been wanting for a while. If you've listened to an NPR station lately, I'm sure you've heard the ad for Reuters' IM client built around SIMPLE.

  53. Save them? by Anonymous Coward · · Score: 0

    I didn't think they were in danger of being extinct.

  54. you don't get it. by No-op · · Score: 1

    it's not a matter of coming up with a slick solution to log stuff, or writing fancy scripts; it's a big financial risk and a regulatory problem. you need to display a truly bulletproof system that not only completely controls all access, but logs all of that material regardless of the client used.

    Furthermore, you THEN have to have a complete supervisory procedure to go through that material looking for compliance violations. This equates to either an army of compliance officers, or very slick software designed for this purpose that flags content based on complex rules. It's really not all that easy- you also have to do the math on the business cost of violations, since you'll be catching them post-event. All that does is prove someone screwed up, and that's what leads most firms to block IM.

    Larger institutional equity firms, however, have taken to IM in a big way- because their customers are fund managers and the like, who have less restrictive rules since they are expected to know what they are doing (unlike joe sixpack investor). I know another IT director who had a major client insist they have direct IM access to their trading desk, otherwise they were pulling all their accounts.

    But seriously, if you think it's just some simple script job or whatever, you need to look into the world of hurt we have with email- try having to archive every single email for 7 years. and I don't mean just backing up, I mean truly archiving every little scrap of mail before the client even sees it, and having it reviewed through a compliance department, and archived with comments and/or other bits of metadata. then it has to go to OPTICAL MEDIA (that gets expensive fast!), with multiple copies, which must go offsite ASAP, but still be available within hours, and be fully indexed blah blah blah. I know others in the industry who deal with mail volume approaching a terabyte/week. now hold on to that for 7 years.

    Regulatory compliance drives the storage business.

    --
    EOM
  55. Keeping Email is Hard? by ClubStew · · Score: 1

    What's with this line here:
    "This is similar to their requirements on keeping e-mail, although technically not nearly as easy."

    Since when was keeping email hard? All the threads above talk about using a corporate server for their IM since it provides centralized logging. Well, since I'm betting that every employee's workstation does act as their own personal SMTP server, they have a centralized SMTP server, too! It's a pretty safe bet. :-)

    So, why in the world, is this hard? Simply tell the SMTP server to keep copies of all the email (perhaps after the SPAM filtration, where applicable). This is hardly hard.

    1. Re:Keeping Email is Hard? by Anonymous Coward · · Score: 0

      They never said it is hard to log email, they are saying that logging instant message traffic is not as easy to do as logging email traffic.

  56. F'n Brilliant by siliconminded · · Score: 1

    An excellent move in the right direction, I'm waiting now with baited breath for them to mandate keeping audio recordings of all spkoen exchanges for three years.

    1. Re:F'n Brilliant by CrackerJackz · · Score: 1

      Already been done.

      All our phone calls are recorded, it tends to save your ass in court when you can pull the phone logs for a trade....

  57. ICQ logs are fun by Glonoinha · · Score: 1

    Ok I admit it, after a guy in my department left the first thing I went after was his ICQ logs ... took them home and spend hours pouring through his personal life ... it is AMAZING what you can glean about a person by rifling through four months of his private ICQ chat logs.

    That said, does MSN IM (the one that comes with XP) have client side logging and if so what are the details? I as of yet have not been able to find any but that doesn't mean they don't exist.

    --
    Glonoinha the MebiByte Slayer
    1. Re:ICQ logs are fun by Anonymous Coward · · Score: 0

      Feel like posting them?

    2. Re:ICQ logs are fun by Anonymous Coward · · Score: 0

      As far as I know (which isn't much, as once I found ICQ, I stopped paying attention to the IM race), ICQ is the only one of the "Big 3" (MSM, AIM, and ICQ) to have logging enabled by default from the beginning.

  58. 2 possable solutions by CaptRespect · · Score: 1

    I see two simple solutions for firms that don't already log instant messages.

    1. Spend thousands on a new system.

    2. No instant messages at all.

    I see a lot of companies just taking the second option. But I could be wrong.

    How much do brokers use instant messages for actual work anyway?

  59. Quit fighting him by BoomerSooner · · Score: 0, Flamebait

    He obviously doesn't have a damn clue. Anyone who thinks doing anything that is regulated where one missed message (a la Martha Stewart) causes jail time/fines, is a trivial thing to do is a fool.

    Go ahead, bet your billion dollar a year business on logging AIM/MSN messages via a "shell script".

    1. Re:Quit fighting him by shaitand · · Score: 1

      umm you do know there isn't a billion dollar company in existance that doesn't use a *nix and shell script logging somewhere. You also know that all you have to show is that reasonable efforts have been made to log the data and your in the clear right? I mean you know that a shell script can equal or better a commercial logging app easily in an environment where everything is text. Hell half your logging apps for unix are hyped up shell scripts!

  60. So what is out there to do this? by jelevy01 · · Score: 1

    Speak of the Devil! My boss just told me that we need to be in complicance with this ASAP. So what are people who are already logging IM using?

    Features I would want would be:
    - Logging (duh)
    - Ability to FORCE logging, not being able to turn on regular IM and get around the logging...

    1. Re:So what is out there to do this? by gioan · · Score: 1

      www.facetime.com
      www.imlogic.com
      www.aconix.com

      Depending on product, you're looking at either having to enforce proxies on the client side, or split DNS with the native mode protocol session hijacking. Direct IM connectivity will have to be blocked at your firewall on the various ports that the client will resort to. /g

  61. Me too by truthsearch · · Score: 1

    I'm also at a large investment firm. Our rules are similar, but currently differ with IM. They're trying to figure out how to give it to us without any legal implications. Since it's currently blocked I've set up an SSH tunnel to home and proxy IM through that. The only reason I'm able to do it is because I'm a developer and get to manage my own workstation. So whatever goes on the standard users will have to abide by the rules, but for the forseeable future us developers will always have a way around those rules. I imagine it's similar elsewhere.

  62. This is why they use enterprise class tools... by Dave21212 · · Score: 2, Informative


    The "big three" personal IM clients (AOL, MSN, Yahoo) are great for talking to Aunt Martha, but if you need reliability, accountability, security, logging, programmability, presence, etc... use tools suitable for the work environment like IBM SameTime IBM already has like 80% of the big corporate IM market - and this is more bad news for the AOL/MSNs of the world. (SMBs and those with Jabber, etc, please don't feel slighted - those are great tools also I hear)

    This should be good news for Lotus/IBM as companies abandon the toys (AOL/MSN/Yahoo) and go for the tools.

    (Sorry, obligatory SCO/IBM suit reference not included ;)

    --
    "Whoever would overthrow the liberty of a nation must begin by subduing the freeness of speech."--Benjamin Franklin
  63. that's not the issue. by No-op · · Score: 1

    It has less to do with an "off the record" conversation, and more to do with the fact that all written client communication is covered under heavy regulatory rules. Client communications are mandated to be archived for 7 years, and email ( and IM ) fall under that. IM has been unregulated until now, so that's why this is a big deal ( nobody issued any statements about it from a regulatory standpoint.)

    if you HAVE TO archive it and supervise it's use, that's a pain in the butt, and if you don't do an adequate job for that you can be shut down and/or fined heavily. that's what is important.

    --
    EOM
  64. Firewall by bobthemuse · · Score: 2, Insightful

    I've seen this done for several small facilities using almost any kind of firewall which supports masquerading (which would be almost all of them). Simple forward all the IM traffic to a dedicated logging machine, which then forwards it to the true IM server. By blocking access to the IM server on all but the redirected ports, there is no way to bypass it. How is this technically difficult?

  65. Just use Trillian by sindarin2001 · · Score: 1

    Trillian can be configured to complete this very task. It'll record and save all IM's sent and recieved.

  66. AIM Enterprise by Phroggy · · Score: 2, Informative

    Isn't this exactly what AIM Enterprise was created for? Why have I not seen anyone mention it?

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    1. Re:AIM Enterprise by Anonymous Coward · · Score: 0

      or Yahoo! Enterprise Edition http://enterprise.yahoo.com/products/msg/ :encryption, screenname control, logging etc. all in one package

  67. Manual Save by kyoko21 · · Score: 1

    Maybe I should submit my resume and work there because I already manually save all my IM conversations by hand and have been doing this since 1997. Man, I'm such a t00l.

  68. Jabber by R0 · · Score: 1

    With JabberYou can do Server side logging easily with the msglog Component. Of course this applies to public servers as well (just like any IM where the messages go through the server). If that bothers you you should use something like GPG (which works well with jabber).

    1. Re:Jabber by axxackall · · Score: 1
      Either Jabber Studio is broken, or msglog is very pre-alpha, or both, but I cannot find any documents describing any features of msglog.

      The question is: if it logs end-to-end encrypted messages, does it log them along with keys used to encrypt them? And if not then what's the point to log messages if the court won't be able to read them?

      --

      Less is more !
    2. Re:Jabber by R0 · · Score: 1

      It's experimental/proof-of-concept but there's Public CVS - I was just pointing out that logging all messages isn't a big deal (with jabber).

      Of course it can't get keys for end-end encryption. There's not much point in logging encrypted messages, but I was sugesting gpg as a counter-measure to snooping on public servers - within an organisation which wanted to log messages they would need cooperation (perhaps as a condition of employment) from the workers. This is common to all comunications, and not a jabber specific problem (jabber just (optionally) offers a standardised integrated way of using end-to-end encryption).

    3. Re:Jabber by axxackall · · Score: 1
      In order to log securely (encrypted) *AND* readable-by-court I am thinking that *ALL* private keys must be stored on the server side, in some sort of "private key server", which should keep all private keys also *encrypted* with the special super key, that must be kept somewhere in very secret place of the organization. Then Jabber server can just log encrypted messages - no one, besides those private key holders can read them anyway. But if the court will issue the warrant then that special super-key can be accessed, as well as all the private keys right after that, and then all messages could be decrypted for reading.

      Alternatively, the messages could be encrypted with two keys (one of a recepient and the other one of the superuser), but I am not sure if gpg can decrypt such two-keys-ecrypted messages having only one of those key at a time.

      --

      Less is more !
  69. That *is* easy by hildjj · · Score: 1

    The XMPP server we provide from Jabber, Inc. provides the ability to log all messages that come in to and go out of the server. It is imperative that all traffic be logged at the server; some IM systems try to do without this by having the client send an extra copy of peer-to-peer messages off to a compliance server, but there are lots of ways that second connection could be defeated.

    Typically in a corporate environment, clients will connect using SSL or TLS, so the wire traffic is encrypted, but the messages themselves are plaintext for easy of retrieval from the archive solution. It is possible to do end-to-end encryption, but in these environments you would need a key escrow solution, which is more trouble that people seem to want at this point.

  70. Call Recording by Cire · · Score: 1

    Most places use a box from Nice to do call recording. It's neat. You can pick up the phone, dial an extension and listen to anyone's conversation live. You can also listen to them over the network on your computer live. They also make other nifty things like the cdfs 5000.

    Cire

  71. Oxymoron? by swordboy · · Score: 1

    Simply standardize

    ???!!

    --

    Life is the leading cause of death in America.
  72. Easy with Jabber by schouwl · · Score: 1

    We already have it inside of Dresdner Kleinwort Wasserstein using jabber.

  73. Humma by aliensporebomb · · Score: 1

    This isn't totally surprising. My firm has been doing this for months now.

    E-mail (via Assentor), IM traffic (via Facetime),
    and other means of recording/tracking are well
    implemented.

    Some are wondering "why the oppressive security?" and it's essentially because during the late 1990s when the stock market was booming some broker/traders performed unethical behavior in
    the name of getting a big payoff (some commissions
    could be larger than their entire yearly salary).

    Here we're pretty locked down..

    If management doesn't want you to get an e-mail, you never see it. Compliance reviewers look at all outside e-mail before it ever gets to you.

    If you send an e-mail outside they review it
    before it's allowed to go out.

    If you e-mail someone in the firm (say an investment banker and you're a research employee) you'll get an e-mail back saying you're not supposed to talk to that person (some of the unethical abuses were when research and investment banking were a little too cooperative together).

    What about using winsock proxy to route IM traffic
    thru port 80 as http traffic so as to just go thru
    the standard web proxies? Locked out - that trick
    was figured out pretty quick.

    What about Telnet and FTP? Long since locked out.

    What about using something like Putty to set-up an
    SSH tunnel to my Linux box at home?

    (1) the actual SSH traffic is locked out.
    (2) we do software sweeps of desktop machines to
    see if they run any nonstandard software.
    That software gets flagged in a database and
    the machine is confiscated by data security
    to see if there are any compliance violations.

    Webmail? Long since locked out. All of the
    majors and minors and new ones as they pop up.

    Modems? The few who have them use them for
    business purposes.

    Modem pool? It actually can tell if you try and
    initiate a TCP/IP style PPP connection and BOOT
    you out after 20-30 seconds. Not sure how but
    it's pretty amazing. Then data security grills
    you on why you were trying to do that.

    You might ask: "JESUS! Why so much oppressive
    security? It's not a military base is it?"

    Well, here's the deal - after the dot bomb and
    the Enron deal and the Martha Stewart thing and
    the many brokerages fined for unethical behavior,
    investors REQUIRED some evidence they were taking
    steps to "do the right thing" in enforcing the
    type of behavior they wanted to see instead of
    just letting the loose cannons run the show. It
    kind of sucks to be so oppressive/oppressed but
    it has to be done to keep things as legal as it
    possibly can be.

    The money is good but if you don't like this kind
    of environment don't work in the securities
    industry.

  74. And if that wasn't easy enough.... by Robotron2084 · · Score: 1

    If these companies are already logging all email, why create a completely new logging system infrastructure for IM?

    Install a Jabber Server. Use the JabberSMTP gateway to fork all your IM over to your mailbox, keeping your IM AND your email in the same place. It would have the added benefit of keeping the IM and Email in chronological order together.

    http://www.jabberstudio.org/projects/jsmtp/proje ct /view.php

    1. Re:And if that wasn't easy enough.... by axxackall · · Score: 1

      ... or even more simple: don't use any IM, use just SMTP (in other words - back to email), which works same fast being configured properly.

      --

      Less is more !
  75. Your Rights Online...? by Cool+Hand+Luke · · Score: 1

    ...how does brokerage houses logging IM messages affect my (our) rights online? Aren't they allowed to cover their ass if Joe Stocktrader starts sharing insider information with MakeMoneyQuick6666 on AIM?

    Just wondering...

  76. Plug: Akonix IM management by kindbud · · Score: 1

    Akonix makes software products for managing, sniffing and logging IM traffic. I've never used them, but they call me from time to time to try and get me to spearhead a project to make this a company priority so they can sell me their stuff.

    Yeah right. I'm also considering the cold call from the guy who wants me to move to a new data center. Bright idea there, cold call the person who will have to do the work and try to sell him 6 months of 12-hour days. LOL!

    --
    Edith Keeler Must Die
  77. Easy to do... by macemoneta · · Score: 1

    Just:

    tcpdump -X port 5190 >> log.file

    for AIM, for example. Not so onerous.

    --

    Can You Say Linux? I Knew That You Could.

  78. Re:Knowledge is power or was it data-logs are powe by Astin · · Score: 1

    This has been said before in the comments, but apparently needs repeating. It's not a matter of privacy since it's at work. Every employee of any brokerage firm signs off sayinfg they know their phone calls, e-mail, and internet usage is being recorded. This isn't done to check up on employees, but to make sure that clients can't reneg on orders they've placed if they go bad. I hear the phrase "play back the tape" at least once a week because someone claims they said 10,000 instead of 20,000. Once confronted with their own voice, there's not much they can do.

    --
    - In hell, treason is the work of angels.
  79. Its not easy but definitely not rocket science... by travelin_light · · Score: 1

    One architect, one engineer and the base jabber client. My colleague (we both work at top 5 Broker/Dealer) put a fully compliant version into production with capability of proxies for all major IM clients in less than four months. The largest issue seems to be the childish tug of war between the proprietary clients. I like the logging b/c one can create chat rooms on the fly through impact analysis tools to couple tech operations and application teams during Incident collaboration and mitigation, allowing managers to review at a later time how the people worked (or did not) work together. I agree with the Disk space guy, another SEC directed boon for their industry!

  80. Client side isn't good enough by Lazy+Bastard · · Score: 1

    This is pretty old news. My firm has had an AIM proxy in place for over a year. Client side logging isn't good enough. The data has to be archived to an approved, durable, tamper resistant medium (paper or optical disc are the only approved media). The firms not only have to log all Instant Messaging, they have to monitor it. For the most part, this consists of a combination of keyword searches and spot checks. This breaks down if for client based logs. Brokerages are NOT legally required to record phone conversations, but they are required to conduct some sort of review of the recordings if they record. Spot checks

  81. daunting technical issues by kirn_malinus · · Score: 1

    what, like turning on logging? doesn't even aim have the ability to do so? just log to a file server...

    --
    All circuits busy.
  82. Solutions Exist by gioan · · Score: 2, Interesting
    I've been doing security/messaging work in the banking/brokerage area for about ten years, and here's the summary, since it's clear few replying are looking at it from the industry perspective.

    There are no "daunting technical issues" to this, but rather cost concerns (and some functionality and implementation ignorance). It is relatively easy to satisfy the NASD/SEC requirements. Logging this locally (at whatever number of clients you have) is not practical (to put it tactfully). You need to log centrally, archive and ship offsite. Storage media varies, but the SEC/NASD still likes WORM due to its durability. There are offsite storage companies (like IronMountain) offering commercial storage options for this. The regulatory guidance until this memo has been fairly foggy, but essentially it's treated the same as other electronic client communications (specifically, email).

    There are a number of solutions to this, including products from Facetime (AOL's corporate product is based on it), IMLogic, and Iconix. None of these is freeware/open-source, and never will be. The goals are stability, easy access to often-nontechnical legal and compliance divisions, and most of all, accuracy and the ability to retrieve content when needed. And believe me, none of this is a laughing matter or religious open-source-versus-Microsoft debate when facing a multi-million-dollar dispute over trading executions.

  83. Reuters just implemented reliable logging for IM by dmir · · Score: 2, Interesting

    Reuters just launched "IM for financial community"
    One of the fetures: - Optional message logging features to meet industry compliance requirements
    News Release - Reuters to Expand Instant Messaging Community within the Financial Services Industry
    Reuters Products - Reuters Messaging

  84. Not just IM clients by ChartBoy · · Score: 1
    anyone stupid enough to use it in a financial industry for anything other then talking to friends and bullshitting around, should be shot

    I suspect this proposal is aimed more at "live chat" customer support services, available from a great many financial (and other) institutions, than at the various IM networks. After all, brokers and banks are urging their customers to ask questions this way.

    The suggestions in your first paragraph still apply, of course.

  85. Logged IM already in use by Anonymous Coward · · Score: 0

    Most investment banks already use IM in the form of Bloomberg messaging and Reuters (MSN) Messenger. Bloomberg messaging is a fairly old system and not logged, but the new Reuters system is designed to be compliant. From the Reuters client page:

    Meet compliance requirements
    Access the tools necessary to meet industry regulatory requirements, including a complete audit trail of all messages sent and received by your users.

  86. Jabber: All message go through server by Anm · · Score: 2

    This is one of the stronger reasons there is growing corporate support for Jabber:
    * All messages go through the server, so they are easy to log.
    * Servers can be set up internally, helping security.
    * Clients available for all desktop OSes. Good clients available for Linux & Windows. A few mobile clients already out there.
    * Gateways available for all other major IM services means clients don't need to change services. The major caveat is that not all features are in place for most carriers. In fact you can only really count on one-on-one ASCII text messaging last I checked. That is still pretty magor though!!
    * Support options available through Jabber.com

    All of these are reasons why my bets are on Jabber to gain acceptance over SIMPLE when in comes to IM. That said, SIMPLE may win a niche in minimal bandwidth specialty applications.

    Anm

    1. Re:Jabber: All message go through server by axxackall · · Score: 0, Redundant

      The major question I keep asking about Jabber's server-side logging is: if the server logs all messages and they are encrypted with some keys, then where are those keys to decrypt them? What's the guarantee that they logged on the server secure enough? And what's the chance that the court will still have the access to those keys in order to decrypt the messages?

      --

      Less is more !
  87. Ethereal? tcpdump? by callermann · · Score: 1

    Its very easy to set tcpdump and ethereal to capture packets for any of the IM clients. I suppose a secure server capturing IM traffic into and out of the network could be set up. Sessions could then be reconstructed when needed.

  88. Just use Trillian by /dev/trash · · Score: 1

    And enable auto logging. Set the log file to a central area.

  89. logging is not enough by krokodil · · Score: 1

    It is worthless to log messages, as long as you could not prove their authenticity. As we know, many protocols could be spoofed. Somebody suggested that IM with broker is legally binding. Somebody would have hard time proving it in the court if sender will say he never sent them.

    Solution? For example Fire (MacOS IM client) allows you not only encrypt, but also sign IM messages with GPG. I think it is pretty cool!

  90. Just use GAIM by PetoskeyGuy · · Score: 1

    GAIM already has a plugin archetecture and works with all existing IM protocols out there. Just create a big plugin that stores all incoming and outgoing messages in a mysql server and hack the source to always load this plugin and disable that section of the configuration files. It's all GPL, so they could keep it or release their changes as a patch.

    Better yet pay Rob Flynn and the gang to do this for them.

    That's the beauty of open source - you need something done, just find someone to do it. The price of a single lawsuit should easily cover the development costs.

  91. Shameles plug for Encrypted messenger by johnatjohnytech · · Score: 1

    See sig.

    My Karma may go down, but hey people need this.

  92. Re:My.sig: by The+Mayor · · Score: 1

    Hence my saying Pi is approximately 22/7, in roman numerals.

    --
    --Be human.
  93. Reuters sells audit-able IM software by Anonymous Coward · · Score: 0

    Reuters, one of the world's larger financial services companies, sells auditable IM software. I know about this because they advertise it constantly on NPR. I found it here online --> http://about.reuters.com/productinfo/messaging/ .

    I imagine other comapnies that line up against Reuters have or are working on similar products.

  94. deadaim by oliverjms · · Score: 0

    They should use DeadAIM to log all of there messages. www.jdennis.net

  95. Not just for the financial industry by zerofoo · · Score: 1

    I'm a network admin for a K-12 school, and we keep logs of EVERYTHING. Web access, email, IM...etc. Why?

    Accountability. We are responsible for the well being of a student while they are here. We can't have some student IMing a 45 year old pedophile. We need to control the information that flows into and out of the school. This protects the students as well as the school.

    The biggest problem we have is IM logging. Our Exchange setup does not allow Windows Messenger to be logged at the server level. That means logging happens at the workstation. This is a pain in the ass, but that's why non-administrative users can not use IM.

    -ted

  96. oh, but the larger issue... by AssFace · · Score: 1

    IM logging isn't daunting.
    what is really daunting is all thems computers out there.
    I think they should just get rid of all thems comptuers.
    problem solved.

    I also think that they should log everything that the person ever says while in the office, and ideally, they should write out everything that they think as well, and that too should be logged.

    and yes, I'm making note of this, and will save it for 3 years.

    --

    There are some odd things afoot now, in the Villa Straylight.
  97. err they better check their laws again... by Archfeld · · Score: 1

    As technical design employee that supports Stock trader's and asset management employees, we are required to keep all business communications of those class of employees for SEVEN YEARS. We've had to install a fiber SAN network and Hitachi arrays to keep all the data, and some STK tape silo's to back up the data again. The cost is INCREDIBLE, our management almost went so far as to forbid the use of tools like this because of the cost, but the folks in question make a TON of money for us and were able to show how important real time collaboration tools like this were to their business model.

    --
    errr....umm...*whooosh* *whoosh* Is this thing on ?
  98. Good news for Cerulean... by Devil · · Score: 1

    I'll bet the folks at Cerulean Studios are calling all those brokerage firms right now; Trillian does logging natively and connects to all the major networks. If you're on Windows (which I imagine a lot of these brokerages are), why use anything else?

  99. Big Question by moby · · Score: 1

    Does the ruling solely cover IM on work systems
    or does it also include SMS and those little
    personal messaging devices as well while at work?

    Everybody will simply start using their phone
    or find another non-controlled means of
    communication.

  100. Anyone seen Wallstreet? by BobRooney · · Score: 1

    Blue horseshoe loves AOL/Time Warner...

  101. already logging IMs here by Anonymous Coward · · Score: 0

    at this international financial firm all IM type traffic was blocked at the firewall until recently. Now there is specific firewall/proxy config required to use any IM and it is EXPLICITLY stated that ALL traffic will be logged. Our tech team has standardized on MSN for no particular reason to keep in touch with staff in NY, London, Sydney .... and soon in Bangalore when they sell our jobs to the lowest bidder.

  102. There is already a leader in this market space. by Anonymous Coward · · Score: 0

    Very simple IM Auditor from FaceTime Communications and yes I work for them and I am shamelessly touting our product. :-) Does a lot more than auditing.

  103. You can do with a proxy... by infernalC · · Score: 1

    ReAIM, a GPLed AIM proxy, already has the ability to dump all messages traversed into an RDBMS.

    Duh. Force them to use a transparent proxy.

  104. Sooo.... by gnovos · · Score: 1
    --
    "Your superior intellect is no match for our puny weapons!"
  105. Broker-Specific GAIM Implementation by shylock0 · · Score: 1

    GAIM is open source, and it already has a pretty neat feature to log all messages. Why couldn't a wealthy brokerage firm, or several of them, or even the NASD itself, simply commission a version of GAIM with all the necessary features. I for one would love seeing the logging features of GAIM made more customizable...

    --
    Statistically speaking, there's a 99.998% chance that my IQ is higher than yours. Get over it.
  106. enough already by No-op · · Score: 1

    I keep reading your posts on this topic and realize you're clueless about our industry. shut up already.

    If you think that traders have the ability to do something like that without getting nailed to the wall almost instantly, then that gives a good example of your understanding of the situation.

    Please refrain from spouting off endlessly about things you don't know. thanks.

    --
    EOM
    1. Re:enough already by Surak · · Score: 1

      That depends on the level of networking and computer knowledge the traders have.

      *I* could (and have) done stuff like this without getting nailed to the wall, with hardly a trace in the system logs.

      As for my other posts, as other people pointed out in my thread, there does exist software like ReAIM that allows for transparent proxying and server-level logging to a database that would be absolutely acceptable for use in your industry (or any others) I'm sure. My point wasn't to say "yeah, I know what I'm talking about" my point was to say that the task of logging is hardly daunting to smart technical people who put their brains to work. If instant messaging has a practical business case in an organization such as yours, then the company *will* spend a little money implementing transparent proxying for the purposes of logging.

      If not, they'll firewall off the ports and bust people going through the http proxy.

      That same logic can be applied to any technology in any organization in any industry.