Q: We recently implemented Advanced Peer-to-Peer Net-working (APPN) connectivity between a network of about 40 AS/400s. In the process of experimenting with the Submit Remote Command (SBMRMTCMD) command, I found that I was able to submit commands on a remote system without even having a password.
Both systems are running at security level 30. On the remote system, we use a default user profile that has PASSWORD(*NONE), yet we were able to submit commands.
I have discovered that I can block this by changing the DDM request access (DDMACC) network attribute on the target system to *REJECT. However, this also blocks a function we need. Is there a way to limit the use of SBMRMTCMD?
A: There is a way to prevent the use of the SBMRMTCMD command and the Client Access/400 Remote Command (RMTCMD) program other than setting the DDMACC network attribute to *REJECT. You can specify the name of a user exit program in the DDMACC network attribute of the target system. The program will supplement AS/400 object level security and determine whether to allow a request from a remote system. The user exit program is passed a structure (shown in 1) that describes the type of request. There are additional fields in the structure, but the first 30 bytes are all that is needed to determine if the request is a remote command.
A: There is a way to prevent the use of the SBMRMTCMD command and the Client Access/400 Remote Command (RMTCMD) program other than setting the DDMACC network attribute to *REJECT. You can specify the name of a user exit program in the DDMACC network attribute of the target system. The program will supplement AS/400 object level security and determine whether to allow a request from a remote system. The user exit program is passed a structure (shown in Figure 1) that describes the type of request. There are additional fields in the structure, but the first 30 bytes are all that is needed to determine if the request is a remote command.
The exit program STOPCMDS (shown in 2) looks at the structure to determine if the request is a command (sent by SBMRMTCMD or RMTCMD) and, if so, prevents the request by setting the return code. The subapplication function of 'COMMAND' indicates that a command string is submitted by SBMRMTCMD from another AS/400 or RMTCMD from Client Access. After you have created the program in 2, assign it to the DDMACC network attribute with the following command:
The exit program STOPCMDS (shown in Figure 2) looks at the structure to determine if the request is a command (sent by SBMRMTCMD or RMTCMD) and, if so, prevents the request by setting the return code. The subapplication function of 'COMMAND' indicates that a command string is submitted by SBMRMTCMD from another AS/400 or RMTCMD from Client Access. After you have created the program in Figure 2, assign it to the DDMACC network attribute with the following command:
CHGNETA DDMACC(XXX/STOPCMDS)
If you want to read more, the details of the exit program are in the V3R1 Distributed Data Management guide (SC41-3307, CD-ROM QBKAHL00).
Q: I have certain users who need *SPLCTL special authority on the AS/400 to allow them to start or vary on printers. The problem is, if they are given this authority, they have the ability to view all spool files, which can give them access to some sensitive information. Is there a way to give a user the authority to start and vary on printers without giving them the ability to view spool files?
A: One of the most common security problems that I see on systems is too many users with *SPLCTL authority. You do not need to give users *SPLCTL authority to allow them to start print writers. There are two alternatives that can be employed.
The first alternative is to give users special authority of *JOBCTL rather than *SPLCTL.
The attributes of an output queue are important when securing spooled files (see Security Patrol, MC, March 1995 for a full description of how the output queue attributes interact with printing functions). The default attributes for creating an output queue are DSPDTA(*NO) OPRCTL(*YES) AUTCHK(*OWNER). A user who has *JOBCTL special authority can start and stop the print writers associated with output queues created with these attributes; *SPLCTL authority is not required.
Sensitive output that you do not want users with *JOBCTL authority to display should be sent on an output queue with increased security. The attributes of a secure output queue should be DSPDTA(*NO or *OWNER) OPRCTL(*NO) and AUTCHK(*OWNER).
Only the owner of the output queue and users with *SPLCTL authority can view spool files that reside in secured (as described above) output queues. If the output queue is owned by a group profile that has *USE access to the printer device description, then all members of the group can start a print writer and display the spool files on this output queue.
The second option does not give users *JOBCTL special authority. Instead it adopts authority when starting print writers.
If you are reluctant to give users *JOBCTL authority because the user can access other users' jobs, then you can create two CL programs (as shown in 3 and 4) that adopt the authority of a user who has *JOBCTL. The function of these two CL programs (STRWTR1 and ENDWTR1) is to allow the user to start or stop print writers.
If you are reluctant to give users *JOBCTL authority because the user can access other users' jobs, then you can create two CL programs (as shown in Figure 3 and Figure 4) that adopt the authority of a user who has *JOBCTL. The function of these two CL programs (STRWTR1 and ENDWTR1) is to allow the user to start or stop print writers.
The Work with Writers (WRKWTR) command has options to start and stop a print writer, but it also has a command line. You should not allow the user access to a command line while adopting authority, and that is why two programs are required.
Security Patrol
Figure 1: Parameter List for User Exit Program
Field Type Len Description User Char 10 User profile name of target DDM job. Application Char 10 Application name: '*DDM ' for Distributed Data Management Subapplication Char 10 Requested function: 'ADDMBR ' 'DELETE ' 'RENAME ' 'CHANGE ' 'EXTRACT ' 'RGZMBR ' 'CHGMBR ' 'INITIALIZE' 'RMVMBR ' 'CLEAR ' 'LOAD ' 'RNMMBR ' 'COMMAND ' 'LOCK ' 'UNLOAD ' 'COPY ' 'MOVE ' 'CREATE ' 'OPEN
Security Patrol
Figure 2: CL Program STOPCMDS
/*===============================================================*/ /* To compile: */ /* */ /* CRTCLPGM PGM(XXX/STOPCMDS) SRCFILE(XXX/QCLSRC) */ /* */ /*===============================================================*/ PGM PARM(&RTNCODE &DATA) DCL VAR(&RTNCODE) TYPE(*CHAR) LEN(1) DCL VAR(&DATA) TYPE(*CHAR) LEN(30) DCL VAR(&APPL) TYPE(*CHAR) LEN(10) CHGVAR VAR(&APPL) VALUE(%SST(&DATA 21 10)) IF COND(&APPL = COMMAND) THEN(CHGVAR + VAR(&RTNCODE) VALUE(0)) ELSE CMD(CHGVAR VAR(&RTNCODE) VALUE(1)) ENDPGM
Security Patrol
Figure 3: CL Program STRWTR1
/*===============================================================*/ /* To compile: */ /* */ /* CRTCLPGM PGM(XXX/STRWTR1) SRCFILE(XXX/QCLSRC) + */ /* USRPRF(*OWNER) */ /* */ /*===============================================================*/ PGM ?STRPRTWTR ENDPGM
Security Patrol
Figure 4: CL Program ENDWTR1
/*===============================================================*/ /* To compile: */ /* */ /* CRTCLPGM PGM(XXX/ENDWTR1) SRCFILE(XXX/QCLSRC) + */ /* USRPRF(*OWNER) */ /* */ /*===============================================================*/ PGM ?ENDWTR ENDPGM
More 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.
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. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms 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.
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:
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.
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:
LATEST COMMENTS
MC Press Online