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

Senate Report on Equifax Raises Questions Ahead of FICO Product Announcement

Equifax is slammed in a Senate subcommittee report ahead of the announcement of a joint service with FICO.

When your company is named in a Senate subcommittee report headline that also includes the words "neglected" and "devastating" it's rarely a good thing. Equifax finds itself in just that situation this week, though the company is not letting that keep it from announcing a partnership that has some observers concerned about consumer privacy.

The staff report issued by the United States Senate Permanent Subcommittee on Investigations of the Committee on Homeland Security and Governmental Affairs is titled How Equifax Neglected Cybersecurity and Suffered a Devastating Data Breach. And the title isn't even the most blunt statement of the report. In the conclusion of the report, the staff writes that Equifax didn't prioritize security, didn't follow its own policies for patching a critical vulnerability, and left itself open to attack due to poor cybersecurity practices, among other faults.

The report also notes that Equifax could have minimized damage had it put basic controls and policies in place, rather than allowing the personal information of millions of individuals to be compromised.

Within the report there are a couple of findings that seem at odds with one another. First, the report states that Equifax executives are firm in their belief that they did everything possible to avoid the breach — in particular, the CIO who served from 2010 to 2017 said that he doesn't believe Equifax could have done anything differently.

However, fellow credit bureaus TransUnion and Experian each used the same product that was the source of the Equifax vulnerability (Apache Struts) -- and yet they avoided a breach by responding to the vulnerability very quickly and patching it long before the Equifax attack was underway.

This report is a prelude to the announcement that Equifax and FICO are joining forces in a Data Decisions Cloud that will provide deeper, more detailed financial information on consumers to companies that subscribe to the big data product. FICO is traditionally a data analysis firm best known for the credit score that's used for everything from approving loans to setting insurance rates. Equifax reports on consumers with data that includes the FICO score, and the combination of the two is seen by some privacy advocates as the worst of all possible worlds — a company with known security issues developing (and storing the data for) products that involve more personal data than ever before.

In the announcement of the new service, the two companies said that they are, "…focused on a connected, end-to-end development and decisioning management platform that allows customers to quickly explore, develop, test and deploy powerful insights into production systems across the organization." The question may not be whether the service can deliver on this promise to customers, but whether Equifax has taken sufficient action based on its huge breach to avoid being the subject of another Senate security investigation in the future.

Related content:

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Limited-Time Free Offers to Secure the Enterprise Amid COVID-19
Curtis Franklin Jr., Senior Editor at Dark Reading,  3/31/2020
COVID-19: Latest Security News & Commentary
Dark Reading Staff 4/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8096
PUBLISHED: 2020-04-07
Untrusted Search Path vulnerability in Bitdefender High-Level Antimalware SDK for Windows allows an attacker to load third party code from a DLL library in the search path. This issue affects: Bitdefender High-Level Antimalware SDK for Windows versions prior to 3.0.1.204 .
CVE-2020-11586
PUBLISHED: 2020-04-06
An XXE issue was discovered in CIPPlanner CIPAce 9.1 Build 2019092801. An unauthenticated attacker can make an API request that contains malicious XML DTD data.
CVE-2020-11587
PUBLISHED: 2020-04-06
An issue was discovered in CIPPlanner CIPAce 9.1 Build 2019092801. An unauthenticated attacker can make an API request and get the content of ETL Processes running on the server.
CVE-2020-11589
PUBLISHED: 2020-04-06
An Insecure Direct Object Reference issue was discovered in CIPPlanner CIPAce 9.1 Build 2019092801. An unauthenticated attacker can make a GET request to a certain URL and obtain information that should be provided to authenticated users only.
CVE-2020-11590
PUBLISHED: 2020-04-06
An issue was discovered in CIPPlanner CIPAce 9.1 Build 2019092801. An unauthenticated attacker can make an HTTP GET request to HealthPage.aspx and obtain the internal server name.