Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

5/3/2006
04:30 AM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Bank Looks for Anomalies

Investment bank Thomas Weisel Partners has decided to forego intrusion detection systems in favor of anomaly detection

Thomas Weisel Partners was looking for a way to ensure that all of its Internet traffic would exit the network through secure servers, without bringing worms and viruses in. But like any good investment bank, Thomas Weisel bypassed the conventional choice -- and found something better.

Instead of deploying an intrusion detection systems, as most companies would do in a similar situation, Thomas Weisel is using an anomaly detection system, Arbor Networks Inc.'s PeakflowX, to solve its security problem.

The San Francisco-based banking firm -- which employs about 550 people and maintains offices in Boston, New York, Palo Alto, and Mumbai -- was looking for a tool that would maximize the resources of its small IT security staff, according to CISO Beth Cannon. Initially, when an outbreak occurred, Cannon and the IT staff would search through logs and deploy packet analyzers to determine what was happening on the network -- a process that was extremely time-intensive.

Cannon and her staff considered an IDS, but after investigating further, determined that such a system would actually add to the workload -- without providing detailed information necessary to take action against misbehaving hosts. The team then took a closer look at PeakflowX, because it "would give a view of what was happening on the internal network and by default what was going in and out of the network."

After deploying PeakFlowX, Thomas Weisel suffered two incidents in which malware was introduced to the network via laptops. The bank uses Symantec anti-virus software, but the AV product did not detect new variants on the laptops. With PeakFlowX, Cannon can issue trouble tickets asking the IT staff to investigate a misbehaving computer before the infection escalates. Cannon didn't track the productivity savings for the incidents, but in the cases where network traffic was slightly degraded during an early outbreak, she estimates that the IT group cut its time expenditure by a ratio of about forty to one.

Cannon also integrated PeakflowX into Microsoft's Active Directory so that she could tie a user to a computer. She could then correlate "what machine [and user account] tried to access a financial server that it had never accessed previously" -- a key element for Sarbanes-Oxley compliance reporting as well as for meeting Securities and Exchange Commission and NASD requirements for logging all electronic transmissions.

Cannon does have to explain to auditors why anomaly detection is as good as, or better than, having an IDS. A signature-based IDS won't detect problems it doesn't know about, but with PeakFlowX, Cannon can combine information from vendors such as Websense and Symantec, as well as controls on servers, with reports from the anomaly detection system to provide immediate, useable information about intrusions and anomalous activity. "What we find, and probably every security manager finds, is that no one system gives you everything," Cannon says. "With a few systems combined, you can get a reasonable picture of network activity."

— Mike Fratto, Editor at Large, Dark Reading

Organizations mentioned in this story

  • Arbor Networks Inc.
  • Microsoft Corp. (Nasdaq: MSFT)
  • Securities and Exchange Commission (SEC)
  • Symantec Corp. (Nasdaq: SYMC)
  • Websense Inc. (Nasdaq: WBSN)
  • Thomas Weisel Partners

    Mike Fratto is a principal analyst at Current Analysis, covering the Enterprise Networking and Data Center Technology markets. Prior to that, Mike was with UBM Tech for 15 years, and served as editor of Network Computing. He was also lead analyst for InformationWeek Analytics ... View Full Bio
     

    Recommended Reading:

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    COVID-19: Latest Security News & Commentary
    Dark Reading Staff 5/28/2020
    Stay-at-Home Orders Coincide With Massive DNS Surge
    Robert Lemos, Contributing Writer,  5/27/2020
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    Write a Caption, Win a Starbucks Card! Click Here
    Latest Comment: Can you smell me now?
    Current Issue
    How Cybersecurity Incident Response Programs Work (and Why Some Don't)
    This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
    Flash Poll
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2020-11844
    PUBLISHED: 2020-05-29
    There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
    CVE-2020-6937
    PUBLISHED: 2020-05-29
    A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
    CVE-2020-7648
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
    CVE-2020-7650
    PUBLISHED: 2020-05-29
    All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
    CVE-2020-7654
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.