22
Mon, Apr
1 New Articles

Things You Hope Your Auditor Never Understands About IBM i Security

IBM i (OS/400, i5/OS)
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

It's a well-known fact that many auditors aren't knowledgeable about IBM i. But they're learning! Here are several IBM i configuration settings that you'd better hope your auditor never fully understands.

Because auditors aren't usually IBM i-savvy, administrators will often choose a configuration or provide an answer that, if fully understood by their auditor, would never be allowed. Here are some of the things that fall into that category. And yes, I'm hoping that your auditor reads this article!

User Class

Many auditors - and system administrators - put too much emphasis on profiles' user class settings. While the user class can be used to initially create the profile, it is never used as a source for user's authority. Therefore, ensuring most users are in the *USER user class could be ignoring the fact that all users have been granted *ALLOBJ special authority, for example. Focus on the User class setting must stop and be redirected to the special authorities granted. Which brings me to my next topic...

Special Authority Granted to the User's Groups

Assigning a user's special authority to their group profile is something I advocate. I actually encourage this behavior as a way of implementing role-based access (RBAC). The problem is when auditors aren't aware of this feature and only examine the user's special authorities and never look to see what might be inherited by one or more groups. While this is an issue of auditors not understanding IBM i, this next issue is solely administrators trying to fool their auditors. That's when a user gets *ALLOBJ via one of their groups and then, to make it appear that users are prevented from running one or more commands or from accessing sensitive files, the administrator grants the users a private authority of *EXCLUDE. Because authority granted to the user itself takes precedence over authorities or special authorities granted to the user's groups, when the user attempts to open one of the files, for example, they receive the "Not authorized to file ABC in library XYZ." The auditors accept the error and go on to the next issue. The problem is that all the user has to do is simply submit a job to run as a profile that isn't restricted; then they have all authority to the sensitive files as well as the ability to run commands that they supposedly can't access. Assigning *ALLOBJ to a user's group and then thinking you can prevent users' access to selected commands or objects is a theory fraught with numerous opportunities to bypass the controls you've attempted to put into place. That's an approach I do not recommend. Note to auditors: Heads up if an administrator says they're not authorized to specific commands or files! Be sure to have them show you how they've been restricted.

What Special Authorities Are and the Capabilities They Provide

Most auditors seem to be aware of *ALLOBJ special authority. They equate it to root in the UNIX/Linux world and Admin in the Windows world. Many also are aware of *SECADM special authority, understanding that it's required when working with user profiles. But I've found very few who are aware of the capabilities provided by the rest of the special authorities. Since this was the topic of a previous article, I'll just refer them here.

QSECURITY Level

Most auditors have a "playbook" or set of instructions from their company that explains what the auditor should be examining. Most auditor playbooks describe that the system should be running at QSECURITY level 40 or 50. But I saw one auditing firm a few years ago that was using outdated information and tried to demand that their client down-level their system to security level 30! We used IBM documentation to help them understand that that would be a bad idea!

Another misunderstanding is that one can pick and choose which parts of the operating system use the features that cause the system to be at security level 40. At least that's the excuse I heard a customer attempt to give their auditor for why their system was not running at security level 40. They claimed that their application wasn't using the features of security level 40. (Huh?!) All applications - regardless of vendor-supplied or written in-house - use the operating system, and it's the operating system that changes behavior at the various security levels. One cannot choose which parts of the operating system your application uses; therefore, this argument has no logic and should not be believed or accepted as a valid reason for a system not running at security level 40 or 50!

What the Limited Capability Attribute Does and Doesn't Do

Back in the day, setting a user to be limited capability (LMTCPB) *YES was the way to lock a user into a menu. It's still the method used to lock users into a menu if they sign on interactively, but it is not an effective method of restricting access via interfaces such as FTP and ODBC. If administrators claim their users are locked into a menu and can't access data directly but the administrators haven't either implemented object-level security or fully implemented an exit point solution such as HelpSystems' NetworkSecurity product, then their claim is not true. End users can access data - at least to download it and quite possibly to modify it.

That said, setting user profiles to LMTCPB *YES is a good thing. You don't want to give end users the ability to enter all commands on the system. Most commands are not allowed to be run by a limited user. Which brings me to my next point. Commands can be changed to allow them to be run by a limited user. I've run into a situation where many commands had been changed so even those users set to limited capability *YES were allowed to be run by a limited user, including all of the commands a programmer needs to debug production issues: Display Physical File Member (DSPPFM), Display File Description (DSPFD), Start Debug (STRDBG), etc. For some reason, this organization thought it was better to have all (and I do mean all) of their users set to LMTCPB(*YES) and to change these commands so all users could run them. Clearly, they were relying on "security by obscurity." Now I'm not saying you should never change any command, but you must consider the full ramifications of changing a command to be allowed by a user. Auditors: Ask for the list of commands that can be allowed by a limited user.

Finally, let me clarify what the setting of limited capability *PARTIAL restricts. Users with limited capability *PARTIAL cannot modify the Program/procedure field on the sign-on display. In addition, they can't modify their current library or attention program once logged on. They can enter commands.

Overriding Attributes in the User Profile

As you know, a handful of system value settings can be overridden at the user profile, including the limit device sessions and block password change attributes. But the one I see overridden most often is the password expiration interval. This attribute is appropriately set to *NOMAX (meaning that the password never expires) for profiles such as service accounts - those profiles that are typically used to make connections to or from other servers. However, what I see on occasion are profiles associated with people - especially administrators - that have been set to *NOMAX (meaning that the administrator's profile never has to be changed!). While there has been some debate over the benefits of changing passwords regularly, I am still an advocate that profiles should be changed periodically. The worst cases are when literally every profile has been overridden at the profile level to a value of *NOMAX while the system value, QPWDEXPITV, is set to 90 (days.) To an auditor, it would appear that passwords are being changed regularly, but under the covers, they aren't. Auditors: Make sure you are examining profiles' password expiration interval!

Default Passwords

I've heard all sorts of excuses from administrators about how profiles with a default password aren't a risk. My favorite is when the assertion is made that it isn't a risk because the password has been set to be expired so it will have to be changed the first time the user signs on. Someone intending to do harm could just as easily change the password at first sign-on as the individual to whom the profile belongs, so that's not a rational argument! The second excuse that I hear is that the profile can't be used for sign-on because the initial program is set to *NONE and the initial menu to *SIGNOFF. While the profile may not be able to sign on interactively, it can absolutely be used to make an ODBC connection or FTP transfer. Another excuse I hear is that the profile is status of disabled and so can't be used for sign-on. I will agree that this is of less risk than either of the first two excuses. But I'm still uncomfortable with it because profiles can often be re-enabled. I've seen Identity Management systems that automatically enable all of a user's accounts throughout an organization. In this case, it would also enable any IBM i account associated with the user - including one with a default password. I've also seen instances where all profiles on the system have been enabled during a role swap. The safest configuration is to not have default passwords! Auditors: Don't listen to justifications for profiles having a default password. Even profiles created by vendor software should be able to be changed to be something other than a default.

Summary

I'm hoping that none of these situations apply to you, but if they do, please consider what you're actually doing. You're only harming your organization by not taking full advantage of IBM i security features. Please reconsider your choices.

Carol Woodbury

 

Carol Woodbury is President and CTO of DXR Security and has over 30 years’ experience with IBM i Security. She started her career as Security Team Leader and Chief Engineering Manager for iSeries Security at IBM in Rochester, MN. Since leaving IBM, she has co-founded two companies – SkyView Partners and DXR Security. Her current company - DXR Security - specializes in penetration testing for IBM i. Her practical experience together with her intimate knowledge of the system combine for a unique viewpoint and experience level that cannot be matched.

Carol is known world-wide as an author and award-winning speaker on security technology, specializing in IBM i Security topics. She has written seven books on IBM i Security. Carol has been named an IBM Champion since 2018 and holds her CISSP and CRISC security certifications.

 


MC Press books written by Carol Woodbury available now on the MC Press Bookstore.

IBM i Security Administration and Compliance: Third Edition IBM i Security Administration and Compliance: Third Edition
Don't miss the newest edition by the industry’s #1 IBM i security expert.
List Price $71.95

Now On Sale

IBM i Security Administration and Compliance: Second Edition IBM i Security Administration and Compliance: Second Edition
Get the must-have guide by the industry’s #1 security authority.
List Price $71.95

Now On Sale

IBM i Security Administration and Compliance IBM i Security Administration and Compliance
For beginners to veterans, this is the definitive security resource.
List Price $69.95

Now On Sale

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$0.00 Raised:
$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: