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.

Perimeter

8/28/2009
03:53 PM
John H. Sawyer
John H. Sawyer
Commentary
50%
50%

Lessons From The Credit Union Penetration-Test Debacle

Determining who is "in the loop" during a penetration test is an important step not always properly planned during the beginning phases of an engagement. The recent media release from the National Credit Union Association (NCUA) provides an excellent example of what can go wrong.

Determining who is "in the loop" during a penetration test is an important step not always properly planned during the beginning phases of an engagement. The recent media release from the National Credit Union Association (NCUA) provides an excellent example of what can go wrong.Sometimes upper management hire pentesters without the IT team knowing anything about it. Other times everyone knows about it. Usually, however, it's a combination, where key managers will know what's going on, while most everyone else is left in the dark. There's good reason for the latter approach: On Aug. 25, NCUA released an alert about a credit union receiving a bogus letter stating it was a NCUA FRAUD Alert accompanied by two CDs that claimed to be training materials in need of reviewed.

Remember the awesome story here on Dark Reading by Steve Stasiukonis? His company was hired to pen-test a credit union and left USB flash drives "infected" with their custom backdoor in the credit union parking lot as part of the test: 75 percent of the flash drives ended up being plugged into company computers.

It turns out that the letter and CDs received by the credit union referenced in the NCUA media release were part of a similar pen-test (See SANS ISC Diary). Can you imagine the embarrassment the credit union and pen-testers must be feeling? There was an obvious failure in communications because whoever makes the decision to take concerns, such as the letter and CDs to NCUA, should have been in the loop about the pen-test.

Having the right people aware of a pen-test is very important, but for obvious reasons we don't want everyone to know about it. If IT knows a pen-test is going to happen,then they may end up being extra diligent in their monitoring, which makes the test completely unrealistic. Why? It's simple. An attacker isn't going to notify them first. They should be on guard at all times, not just during audits and pen-tests.

I'm sure a few people learned their lessons in this mishap. Next time you're planning a pen-test, make sure you have the right people in the know before you begin so you don't end up in a situation that accidentally gets national attention.

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
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
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
CVE-2020-15821
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, a user without permission is able to create an article draft.
CVE-2020-15823
PUBLISHED: 2020-08-08
JetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
CVE-2020-15824
PUBLISHED: 2020-08-08
In JetBrains Kotlin before 1.4.0, there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.
CVE-2020-15825
PUBLISHED: 2020-08-08
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges.