|
||
SecureMyi.com Security and Systems Management Newsletter for the IBM i
May 27, 2015 - Vol 5, Issue 7
|
||
|
||
|
Feature Article
|
|
In This Issue
Quick Links
Our Newsletter Sponsors
Platinum Sponsor |
IBM i Security ResourcesIBM i Security Videos - SecureMyi RedBook - Security Guide IBM i Open Security Foundation - DataLoss DB National Vulnerability Database - NIST |
|
|
||
|
|
|
Security Shorts
By Dan Riehl - SecureMyi.com When deciding who will be authorized to use a particular command, like ENDSBS(End Subsystem), it is important that you do not leave anyone out that needs to use the command. You do not want to get a call at 3:00am telling you that the batch job just blew up because the job was running under the user profile JSMITH, and you neglected to add JSMITH to the authorization list that secures the ENDSBS command. I suggest that before you implement new restrictions CL command usage that you get some history of who is using the commands. Once you have a list of users that use the commands, you can then restrict usage to just that select group. To get a history of who is using a command, you will need to start auditing the command usage and then generate your command usage reports. To start auditing the use of the ENDSBS command you can use the command: CHGOBJAUD OBJ(QSYS/ENDSBS) OBJTYPE(*CMD) OBJAUD(*ALL) To get reports on command usage you can use the command: CPYAUDJRNE ENTTYP(CD) OUTFILE(MYLIB/QAUDIT) This command will create the file QAUDITCD that you can view with SQL, Query or download to Excel. You will need to filter the result file to select only those records where the Command used is ENDSBS. |
Sponsored Links
IBM i, iSeries and AS/400
|
|
|
||
|
||
Send your IBM i Security and Systems Management News and Events! Send your Questions, Comments, Tips and Stories Copyright 2015 - SecureMyi.com, all rights reserved SecureMyi.com | St Louis MO 63017 |