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.


12:33 PM
Connect Directly

Cutting Through The Mystique Of Testing The Mainframe

Mainframes are not enterprise dinosaurs -- they're modern systems running mission-critical data that must be scrutinized as much as any other part of the IT infrastructure

BLACK HAT USA -- Las Vegas -- While most IT security teams tend to lump mainframe systems into the category of legacy systems unnecessary or impossible to scrutinize during regular audits, that couldn't be farther from the truth, says a researcher at Black Hat USA who this week released a number of free tools meant to help bridge the understanding gap between mainframe experts and security professionals.

Click here for more of Dark Reading's Black Hat articles.

"I see them described as legacy all the time: 'Oh, we don't need to implement this policy because it's a legacy system.' Calling a mainframe legacy is like calling Windows 2012 Server legacy because parts of the Window NT kernel are still in the code. Or it's like calling my car legacy because it's still got tires," said Philip "Soldier of Fortran" Young, explaining that most enterprise mainframes today run off the IBM z/OS platform. "It's not an old operating system -- it's got all the same security controls you'd expect from other modern operating systems."

Additionally, security folks shouldn't fall for the common misconception that mainframes are somehow slowly going the way of the dodo. In fact, Young mentioned the fact that they're still going strong and that 70% of Fortune 500 companies run mainframes.

"These companies are large companies and they're processing their critical data through a mainframe," he said. "They're not running their email servers on it and they're not running their internal intranet sites. They're running critical data."

The difficulty with securing these highly sensitive environments is that the people tasked with testing and assessing mainframes generally have limited knowledge about how mainframes work. To demonstrate this, he took a straw poll amongst his audience members about who had ever been responsible for assessing or analyzing mainframes for security. He then asked those large number with their hands up to keep them up if they'd ever administered or implemented a mainframe before. Only one hand stayed up.

Meanwhile, he asked a similar question about how many people had been responsible for assessing Linux or Unix boxes and nearly all of the hands stayed up when he asked if they had ever administered or built those systems before.

Young stressed that not only is it really important for security people to push for better access to mainframes, work as a community to develop better tools for assessing them and dedicate the time to learning more about these systems,but time is of the essence. Because mainframes aren't legacy systems and they're not going to be retired from the enterprise anytime soon, the people who know the most about them will be. He pointed to statistics that show that over 75% of mainframe administrators are over 50.

In addition to walking the audience through a number of techniques to probe a mainframe's security (PDF), Young said he hoped to spur the industry on to come together and develop better tools to automate mainframe security testing. He expressed particular frustration at the state of testing tools for the mainframe, which up until now have been virtually non-existent.

"There's really nothing out there, it's really frustrating," he said. The tools that are there are out of date or they're wrong. And there's no framework that includes z/OS. No Nessus, no NMAP and no Metasploit," he said.

Young has done his part to start getting auditors and testers the tools they need by showcasing at Black Hat a number of tools he developed that offer functionality like user enumeration, password sniffing and a way to turn a vulnerability in the fundamental way mainframes handle FTP traffic to execute commands on z/OS. However, he said there is more work to be done and he hopes other people can help as well.

"I'm working on getting some of these things implemented in Metasploit, and I need everyone's help because it's a very challenging environment -- you can understand that some people don't want these things developed so I can't ask for help from them," he said, explaining that even if security folk can't get access to their corporate mainframes due to worries about bringing down a mission critical production system, they can start experimenting on emulators, including the IBM zPDT and Hercules emulators.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Ninja
8/4/2013 | 12:29:17 PM
re: Cutting Through The Mystique Of Testing The Mainframe
the term "main frame" refers to a structure of square tube steel welded up to create a "frame" onto which the main components of a computer could be mounted

the integrated circuit -- used on micro chips obviated the need for the steel structure -- along with the crane needed to put one in place.

"multi programming" -- which is what the computer built on the "main frame" was supposed to do -- failed -- although it helped for a time .

what we wanted was multiple computers working on one task -- not one computer working on everybody's tasks

Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Zero Trust doesn't have to break your budget!
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-06-16
SQL Injection vulnerability in phpCMS 2007 SP6 build 0805 via the digg_mod parameter to digg_add.php.
PUBLISHED: 2021-06-16
Directory Traversal vulnerability in phpCMS 9.1.13 via the q parameter to public_get_suggest_keyword.
PUBLISHED: 2021-06-16
phpCMS 2008 sp4 allowas remote malicious users to execute arbitrary php commands via the pagesize parameter to yp/product.php.
PUBLISHED: 2021-06-16
IBM Security Identity Manager 6.0.2 is vulnerable to server-side request forgery (SSRF). By sending a specially crafted request, a remote authenticated attacker could exploit this vulnerability to obtain sensitive data. IBM X-Force ID: 197591.
PUBLISHED: 2021-06-16
IBM Security Identity Manager 6.0.2 could allow an authenticated malicious user to change the passowrds of other users in the Windows AD enviornemnt when IBM Security Identity Manager Windows Password Synch Plug-in is deployed and configured. IBM X-Force ID: 197789.