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.

Vulnerabilities / Threats

1/12/2009
01:46 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

IRS Security Holes Leave Taxpayer Data At Risk, GAO Says

New report highlights lingering security weaknesses in the Internal Revenue Service's network and systems

Just in time for tax season: The Internal Revenue Service (IRS) is under fire again for failing to take the necessary steps needed to prevent security breaches targeting sensitive taxpayer information.

A new Government Accountability Office (GAO) report (PDF) says the IRS still has not addressed most security weaknesses previously highlighted in past audits by the watchdog agency.

The GAO has advised IRS commissioner Douglas Shulman to deploy an agencywide security program, and has provided the IRS with recommendations on how to correct the outstanding security weaknesses in the agency's network and systems infrastructure. The GAO's findings are based on an audit conducted between April 2008 and January 2009.

One big hole: The IRS still allows any user on its internal network to get IDs and passwords for mission-critical applications even if his job doesn't require it, leaving the door open for abuse, according to the GAO.

"Despite IRS' progress, information security control weaknesses continue to jeopardize the confidentiality, integrity, and availability of financial and sensitive taxpayer information. IRS did not consistently implement controls that were intended to prevent, limit, and detect unauthorized access to its systems and information," the report says.

Among the security woes documented in the GAO report: The IRS didn't always enforce strong passwords, and it didn't ensure that only authorized users access applications. The agency also did not consistently encrypt some sensitive data, nor did it "effectively" monitor changes on its mainframe or protect is computer resources "physically."

The IRS still transmits data unencrypted from its financial accounting system, for instance, according to the GAO.

The GAO says the main reason the IRS still hasn't corrected these security weaknesses is that it has not yet implemented an agencywide security program. "Specifically, IRS did not annually review risk assessments for certain systems, comprehensively test for certain controls, or always validate the effectiveness of remedial actions," the GAO report says. "Until these weaknesses are corrected, the agency remains particularly vulnerable to insider threats, and IRS is at increased risk of unauthorized access to and disclosure, modification, or destruction of financial and taxpayer information, as well as inadvertent or deliberate disruption of system."

Some good news, however, did emerge from the GAO report: The IRS has fixed 49 of 115 problems cited by the GAO in previous audits, including implementing controls for unauthenticated network access and user IDs on the mainframe, encrypting sensitive data that travels over its network, improving vulnerability patching, and updating its contingency plans.

According to the GAO, the IRS' Shulman said the IRS is committed to locking down security on its systems and will create an action plan to address each of the GAO's recommendations.

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 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

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/17/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25789
PUBLISHED: 2020-09-19
An issue was discovered in Tiny Tiny RSS (aka tt-rss) before 2020-09-16. The cached_url feature mishandles JavaScript inside an SVG document.
CVE-2020-25790
PUBLISHED: 2020-09-19
** DISPUTED ** Typesetter CMS 5.x through 5.1 allows admins to upload and execute arbitrary PHP code via a .php file inside a ZIP archive. NOTE: the vendor disputes the significance of this report because "admins are considered trustworthy"; however, the behavior "contradicts our secu...
CVE-2020-25791
PUBLISHED: 2020-09-19
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with unit().
CVE-2020-25792
PUBLISHED: 2020-09-19
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with pair().
CVE-2020-25793
PUBLISHED: 2020-09-19
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with From<InlineArray<A, T>>.