Sidebar

Security Patrol

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

Security Patrol discusses security topics and implementation tips and answers your security questions. I welcome questions, recommendations, and suggestions for security topics you would like discussed in detail. You can submit your correspondence through MC-BBS at 619-931-9909; by E-mail at This email address is being protected from spambots. You need JavaScript enabled to view it.; or by fax at 520-578-7786. I cannot answer every question, but I'll try to publish those questions of a general nature. Please include your phone number.

-Wayne O. Evans, chief of security

Q: During an audit of our AS/400, one of the findings was the use of default user profiles named in the communications entries. The default user profile in several different communications entries names the user profile OWNPROD. This profile is the owner of production data files and has a password of *NONE. If I change the entries in the communications subsystem QCMN to replace this default user profile with *NONE, jobs from other systems that use DDM or ICF to access data on our system fail.

I do not fully understand how default user profiles work with communications entries. Are default user profiles in communications a security exposure? If so, how can I remove them without causing disruption to our production applications?

A: The default user in the communications entry of a subsystem has three possible values:

*NONE-Security information must be entered. Requests without security information will be rejected.

*SYS-All user-evoked requests require security information. A default user profile will be used for IBM-defined transaction programs.

User Profile-The name of the default user profile used for evoked requests that enter the subsystem through this entry and contain no security information. (This option is a potential security exposure).

If the display of your communications entries in your communications subsystem is similar to that shown in 1, where a default user profile such as OWNPROD is specified, then there is a security exposure.

If the display of your communications entries in your communications subsystem is similar to that shown in Figure 1, where a default user profile such as OWNPROD is specified, then there is a security exposure.

If a default user profile name is specified and the remote system did not provide any security information, the job will start using the default user profile. If the default user profile has authority to production data, as your OWNPROD profile does, the communications job will have full access to production data.

The exposure is that a remote system can start a job on your AS/400 using the default user profile. A hacker can easily exploit the default user profile because there is no password or user profile name required to start a job as the default user.

Correcting this security exposure is the challenge. From a security standpoint, the best solution is to change the communications entries to remove the default user. However, if you do, production applications are likely to fail. The applications that depend upon the default user profile to access production data need to be started using the profile name of the default user. I have two potential solutions:

1. Create an explicit device specification.

2. Remove the default user.

This first solution reduces the security exposure so only specific systems can use the default user profile. The initial subsystem description shown in 1 allows *ANY communications device to start jobs with the default user profile OWNPROD. You can limit the exposure to specific systems by changing the subsystem description to remove the default user profile name for the *ALL devices entry. Next, create a configuration entry with an explicitly named communications device associated with the remote system you want to communicate with and place the user profile name in that entry. 2 illustrates this configuration for two remote systems: SYSTEM1 and SYSTEM2.

This first solution reduces the security exposure so only specific systems can use the default user profile. The initial subsystem description shown in Figure 1 allows *ANY communications device to start jobs with the default user profile OWNPROD. You can limit the exposure to specific systems by changing the subsystem description to remove the default user profile name for the *ALL devices entry. Next, create a configuration entry with an explicitly named communications device associated with the remote system you want to communicate with and place the user profile name in that entry. Figure 2 illustrates this configuration for two remote systems: SYSTEM1 and SYSTEM2.

If you use this option, I recommend the use of a location password (LOC-PWD) for the device descriptions for systems (SYSTEM1 and SYSTEM2) that use the default user profile. The LOCPWD ensures that the communication is with the desired systems.

Before I describe the second solution, I want to explain some details about communications configurations so you understand this solution. The communications configuration on your AS/400 defines the Advanced Program-to-Program Network (APPN) devices that determine which remote systems can connect to your AS/400. Two communications configuration parameters (Secure location and Location password) control the security of remote communications. There are two ways to specify these security parameters. The device description or the remote configuration list specifies the attributes of the communications configuration. For more detail, refer to these commands:

o Change Device APPC

(CHGDEVAPPC)

o Create Device APPC (CRTDEVAPPC)

o Add Configuration List Entries

(ADDCFGLE)

o Change Configuration List Entries (CHGCFGLE)

The Secure location (SECURELOC) parameter determines if your system will accept security information from a remote system. The default value of *NO indicates that your system requires remote systems to supply security information. When *NO is specified for SECURELOC, the remote system must supply both a user profile and a password to start a job on your system or send no security information (blanks as user profile and password). Sending blanks will be accepted only if your system has configured a default user (which we want to avoid). When *YES is specified for the SECURELOC parameter, your system will accept a user profile name and no password from the remote system. Your system "trusts" the remote system to validate the user profile as correct.

The communications experts refer to this support as "already verified." The remote system has already verified the user profile password, so no password is required. You do not want to specify SECURELOC(*YES) for another system unless you are confident about the security implementation at the other system. Specifying SECURELOC(*YES) is reasonable for systems within your own company but should never be specified for systems of outside vendors. Since you are trusting the remote computer, you need to be assured that the system you are communicating with is actually the computer you intend. The second parameter of the device configuration, LOCPWD, validates the remote computer as the system intended. LOCPWD is 1-16 hexadecimal numbers that must be the same at both the local and remote systems, or the communications session will be rejected. If you attach to multiple locations, the LOCPWDs should be unique and random. I recommend that you not record the LOCPWDs. Should you need to reconfigure the system, contact the remote system to assign a new LOCPWD.

You may be wondering why I spent so much time on SECURELOC and how it relates to your problem of removing the default user profile names in your system. The Secure location parameter value of *YES is required to be able to start a communications job from a remote system without sending the password on the communications evoked. The IBM DDM support does not allow you to specify a user profile and password. I will use Secure location in the second method.

The second method to remove the default user in the communications entries is shown in 3.

The second method to remove the default user in the communications entries is shown in Figure 3.

If the communications device description specifies SECURELOC(*YES) and the remote system is running a job as user OWNPROD, the SECURELOC(*YES) allows the job to perform DDM operations using the user profile OWNPROD when the remote system opens a DDM file. Starting jobs using the OWNPROD user profile depends upon two conditions.

1. The device or location description must be created with SECURELOC(*YES).

2. The job at the remote system runs with user profile OWNPROD.

You can change the device description using the CHGDEVAPPC, Change Configuration List (CHGCFGL), or the Work with Configuration Lists (WRKCFGL) command to specify a secure location. Vary off the communications device to change the SECURELOC parameter. Changing SECURELOC is adequate, but I recommend specifying a LOCPWD at the same time. If you specify a LOCPWD, you will need to change the corresponding device description on the remote system.

The job on the remote system should be running with the user profile OWNPROD. The remote system jobs are either batch jobs or interactive sessions. Individual users should sign on with their user profiles, not OWNPROD. The challenge is to change the job prior to doing a communications function. The program SWAP, shown in 4, swaps the OWNPROD profile before opening the DDM or ICF file. You should add the following command to the user's initial program.

The job on the remote system should be running with the user profile OWNPROD. The remote system jobs are either batch jobs or interactive sessions. Individual users should sign on with their user profiles, not OWNPROD. The challenge is to change the job prior to doing a communications function. The program SWAP, shown in Figure 4, swaps the OWNPROD profile before opening the DDM or ICF file. You should add the following command to the user's initial program.

 CALL PGM(SWAP) PARM('*OWNER') 

You should restrict access to the program SWAP since it changes the job on the remote system to run as user OWNPROD. If the OWNPROD profile can enter commands, you should swap the users back to their original user profiles by specifying the following command prior to allowing any command access.

 CALL PGM(SWAP) PARM('*USER') 

(For more information about the subject of communications configurations, see Security Patrol, MC, September 1994.)

Security Patrol

Figure 1: All Devices with Default User


Security Patrol

Figure 2: Specific Devices for Default User


Security Patrol

Figure 3: Subsystem Communications Entries with No Default User



Security Patrol

Figure 4: CL Program to Swap User Profiles

 /*==================================================================*/ /* To compile: */ /* */ /* CRTCLPGM PGM(XXX/SWAP) SRCFILE(XXX/QCLSRC) + */ /* USRPRF(*OWNER) */ /* */ /* CHGOBJOWN OBJ(XXX/SWAP) OBJTYPE(*PGM) + */ /* NEWOWN(QSECOFR) */ /* */ /*==================================================================*/ PGM PARM(&OPTION) DCL VAR(&OPTION) TYPE(*CHAR) LEN(10) DCL VAR(&NEWUSR) TYPE(*CHAR) LEN(10) + VALUE('OWNPROD') DCL VAR(&HANDLE) TYPE(*CHAR) LEN(12) IF COND(&OPTION *NE '*OWNER') THEN(RTVJOBA + USER(&NEWUSR)) CALL PGM(QSYGETPH) PARM(&NEWUSR '*NOPWD' &HANDLE) CALL PGM(QWTSETP) PARM(&HANDLE) CALL PGM(QSYRLSPH) PARM(&HANDLE) ENDPGM 
BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things


    Read Node.js for Enterprise IBM i Modernization Now!

     

  • Profound Logic Solution Guide

    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 companyare not aligned with the current IT environment.

    Get your copy of this important guide today!

     

  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.

     

  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline

     

     

  • The Power of Coding in a Low-Code Solution

    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:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Why Migrate When You Can Modernize?

    LANSABusiness 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.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.

     

  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    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:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact

     

  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.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. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using NodeRun.com as a pre-built development environment

     

     

  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.

     

     

  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.

     

     

  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails

     

  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.

     

     

  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen 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:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave 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.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

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

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine 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:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. 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:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

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

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.