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.

Analytics

11/16/2007
04:58 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Financial Consulting Firm Fixes Security Flaws

InCharge Institute of America runs F5 Networks's BIG-IP Application Security Manager to shore up security

Mark Nagiel's first task as the new vice president of IT at InCharge Institute of America was to conduct a security audit. He found that the company had done a good job securing its perimeter, guarding information in its databases, tracking intrusion activities, and educating employees on key security issues. But he also discovered some gaping holes in the financial consulting firm's defenses.

Turns out data was flowing over the company’s port 80, which is used for Web traffic, as well as over port 443, which supports Secure Sockets Layer information. And some of InCharge's internally developed applications hadn't been properly bulletproofed.

InCharge, a nonprofit focused mainly on supplying credit counseling and debt management advice to consumers through its InCharge Debt Solutions program, has more custom application development than many other organizations because its business is so multi-faceted. It has several offshoot businesses, including Brightscore.com, which helps clients monitor and examine up-to-date credit information, and the InCharge Educational Foundation, which offers educational products and services so individuals understand their personal financial needs.

Sealing up InCharge's newfound security holes was important because the company, which has 50,000 to 100,000 customers in various stages of rectifying their credit problems, deals with sensitive personal information such as credit card and Social Security numbers. Because it works with financial data, the nonprofit also must comply with various data security regulations for the privacy and the protection of a person’s financial data. “We are treated differently in almost every state, ranging from states where there is no regulatory control to New York where we are audited on annual basis, just like Bank of America,” Nagiel says.

Nagiel didn't just take his own word for potential problems in the company's security architecture -- he hired a third-party consulting firm to probe the weak spots as well. The firm found cross-site scripting, cookie poisoning, SQL/OS injection, as well as the open port 80 and port 443 vulnerabilities. Although these flaws hadn't led to any data being compromised, they were found in some of the company’s applications.

InCharge, with the help of the consultants, ended up selecting F5 Networks's BIG-IP Application Security Manager (ASM) to remedy its security weaknesses. One appealing feature, according to the company, was the auto-adaptive approach where the system passively monitors traffic patterns, identifies where changes need to be made, and updates security policies based on the observed traffic patterns.

The financial services company got the BIG-IP ASM up and running quickly in late 2005, but the more challenging step was revamping the company’s application development processes, Nagiel says. It was difficult for the nonprofit's software engineers to adapt to building their applications with security in mind.

Today, new software releases and upgrades include tighter security checks. And InCharge's IT systems have a better security reputation now. Each year, the Credit Bureau audits InCharge’s business processes: “The first year, they spent time examining our DMZ,” Nagiel says. “After we implemented ASM, they spent no time there because they felt the F5 system enabled us to close up any possible vulnerability.”

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

  • F5 Networks Inc. (Nasdaq: FFIV)

    Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... 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.