Q: The users on my system are members of a group profile that is the owner of production files. The application package requires that users be members of the group profile that owns the production files. The users are limited to menus, and the application limits what users can do, so this has not been a security exposure.
I want to allow some users to analyze production data using Query/400 on the production files. I am concerned that the outfile option of Query/400 could be used to modify the production files. Is there a way that I can block the outfile capability?
A: I am not aware of any method to block the outfile capability, but I do have an alternative solution that gives the users read-only access while running a query.
Your concern that users can modify the production files in a query is justified. If users have *CHANGE authority to a file, they can use the outfile feature of Query/400 to modify the production files.
I am aware of a case where production data was accidently destroyed. A user wanted to create a modified version of production data in an outfile but specified the production master file by mistake and wrote data over the production files.
If users are allowed to define queries using the Work With Queries (WRKQRY) command, they should not be a member of the group profile that owns the production files or has *CHANGE authority to production files. One solution would be to give the users a second user profile that would be used for their query work. This is not convenient for the users because they would be required to sign-on with a second profile.
You can dynamically change a group profile with the Set Group Profile (SETGRPPRF) command presented in the "Dynamic Change of Group Profile," MC, May 1994. However, if you want to change the group profile back to what it was prior to running the SETGRPPRF command, you have to specify the old group profile name.
I have enhanced the SETGRPPRF command to allow you to easily reset the group profile back to what is was. With the new version, you simply specify *RESET for the group profile (GRPPRF) parameter of the SETGRPPRF command.
When users select the option to define a query, change the user's group profile to one that has read-only access. Here are the steps you need to follow:
1. Create another user profile. I called it GRPPRDUSE (Group Production Use). Give the GRPPRDUSE profile *USE authority to the production files.
2. Prior to allowing users to define a query, change their group profile to GRPPRDUSE with the SETGRPPRF command. 1 shows the CL commands that can be executed when users select a menu option to initiate the query.
2. Prior to allowing users to define a query, change their group profile to GRPPRDUSE with the SETGRPPRF command. Figure 1 shows the CL commands that can be executed when users select a menu option to initiate the query.
When the user exits from the query, change the group profile back to the production group profile. This is done using the *RESET option of the SETGRPPRF command (see 1).
When the user exits from the query, change the group profile back to the production group profile. This is done using the *RESET option of the SETGRPPRF command (see Figure 1).
2 contains the enhanced SETGRPPRF command source and 3 contains the Command Processing Program (CPP) program to dynamically change a group profile (GRP004CL). The additions for *RESET are shaded.
Figure 2 contains the enhanced SETGRPPRF command source and Figure 3 contains the Command Processing Program (CPP) program to dynamically change a group profile (GRP004CL). The additions for *RESET are shaded.
V3R1 will allow multiple supplemental group profiles to be assigned to a user profile so the dynamic change of group profiles will not be required to give users access. For more information, look for my article on V3R1 security enhancements in an upcoming issue of MC. The dynamic change of profiles will still be useful when you want to restrict users' access in special cases as illustrated by this question.
Security Patrol: Security Questions & Answers
Figure 1 Starting Query Using a Group Profile with *USE Aut
. . SETGRPPRF GRPPRF(GRPPRDUSE) WRKQRY SETGRPPRF GRPPRF(*RESET) . . .
Security Patrol: Security Questions & Answers
Figure 2 The SETGRPPRF Command Source
/*===============================================================*/ /* To compile: */ /* */ /* CRTCMD CMD(XXX/SETGRPPRF) PGM(XXX/GRP004CL) + */ /* SRCFILE(XXX/QCMDSRC) */ /* */ /*===============================================================*/ SETGRPPRF: CMD PROMPT('Set Group Profile') PARM KWD(GRPPRF) TYPE(*NAME) LEN(10) DFT(' ') + SPCVAL((*RESET)) PROMPT('Group profile')
Security Patrol: Security Questions & Answers
Figure 3 Command Processing Program GRP004CL
/*==================================================================*/ /* To compile: */ /* */ /* CRTCLPGM PGM(XXX/GRP004CL) SRCFILE(XXX/QCLSRC) + */ /* USRPRF(*OWNER) */ /* */ /*==================================================================*/ GRP004CL: + PGM PARM(&NEWGROUP) DCL VAR(&NEWGROUP) TYPE(*CHAR) LEN(10) DCL VAR(&OLDGROUP) TYPE(*CHAR) LEN(10) DCL VAR(&USER) TYPE(*CHAR) LEN(10) DCL VAR(&HANDLE) TYPE(*CHAR) LEN(12) DCL VAR(&ERRORSW) TYPE(*LGL) DCL VAR(&MSGID) TYPE(*CHAR) LEN(7) DCL VAR(&MSG) TYPE(*CHAR) LEN(512) DCL VAR(&MSGDTA) TYPE(*CHAR) LEN(512) DCL VAR(&MSGF) TYPE(*CHAR) LEN(10) DCL VAR(&MSGFLIB) TYPE(*CHAR) LEN(10) DCL VAR(&KEYVAR) TYPE(*CHAR) LEN(4) DCL VAR(&KEYVAR2) TYPE(*CHAR) LEN(4) DCL VAR(&RTNTYPE) TYPE(*CHAR) LEN(2) MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL(STDERR1)) RTVJOBA USER(&USER) IF COND(&NEWGROUP = '*RESET') THEN(DO) CALL PGM(QSYGETPH) PARM(&USER '*NOPWD' &HANDLE) CALL PGM(QWTSETP) PARM(&HANDLE) CALL PGM(QSYRLSPH) PARM(&HANDLE) RMVMSG CLEAR(*ALL) GOTO CMDLBL(ENDPGM) ENDDO ELSE CMD(DO) RTVUSRPRF USRPRF(&USER) GRPPRF(&OLDGROUP) CHGUSRPRF USRPRF(&USER) GRPPRF(&NEWGROUP) IF COND(&OLDGROUP *NE '*NONE') THEN(DO) GRTOBJAUT OBJ(QSYS/&OLDGROUP) OBJTYPE(*USRPRF) USER(&USER) + AUT(*OBJOPR *OBJMGT *READ *DLT *UPD *ADD) ENDDO CALL PGM(QSYGETPH) PARM(&USER '*NOPWD' &HANDLE) CALL PGM(QWTSETP) PARM(&HANDLE) CALL PGM(QSYRLSPH) PARM(&HANDLE) CHGUSRPRF USRPRF(&USER) GRPPRF(&OLDGROUP) GRTOBJAUT OBJ(QSYS/&NEWGROUP) OBJTYPE(*USRPRF) USER(&USER) + AUT(*OBJOPR *OBJMGT *READ *DLT *UPD *ADD) RMVMSG CLEAR(*ALL) GOTO CMDLBL(ENDPGM) ENDDO STDERR1: + /* Standard error handling routine */ IF COND(&ERRORSW) THEN(SNDPGMMSG MSGID(CPF9999) MSGF(QCPFMSG) + MSGTYPE(*ESCAPE)) CHGVAR VAR(&ERRORSW) VALUE('1') /* Set to fail on error */ RCVMSG MSGTYPE(*EXCP) RMV(*NO) KEYVAR(&KEYVAR) STDERR2: + RCVMSG MSGTYPE(*PRV) MSGKEY(&KEYVAR) RMV(*NO) KEYVAR(&KEYVAR2) + MSG(&MSG) MSGDTA(&MSGDTA) MSGID(&MSGID) RTNTYPE(&RTNTYPE) + MSGF(&MSGF) SNDMSGFLIB(&MSGFLIB) IF COND(&RTNTYPE *NE '02') THEN(GOTO CMDLBL(STDERR3)) IF COND(&MSGID *NE ' ') THEN(SNDPGMMSG MSGID(&MSGID) + MSGF(&MSGFLIB/&MSGF) MSGDTA(&MSGDTA) MSGTYPE(*DIAG)) IF COND(&MSGID *EQ ' ') THEN(SNDPGMMSG MSG(&MSG) MSGTYPE(*DIAG)) RMVMSG MSGKEY(&KEYVAR2) STDERR3: + RCVMSG MSGKEY(&KEYVAR) MSGDTA(&MSGDTA) MSGID(&MSGID) MSGF(&MSGF) + SNDMSGFLIB(&MSGFLIB) SNDPGMMSG MSGID(&MSGID) MSGF(&MSGFLIB/&MSGF) MSGDTA(&MSGDTA) + MSGTYPE(*ESCAPE) ENDPGM: + 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