![]() |
||
SecureMyi.com Security and Systems Management Newsletter for the IBM i
October 9, 2013 - Vol 3, Issue 37
|
||
![]() |
||
![]() ![]() ![]() |
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 ![]() ![]() ![]() |
![]() ![]() |
![]() October Events2013 IBM Power Systems Technical University at Enterprise2013
Building Effective Security Dashboards November Events
Live Hands-On - IBM i System Administration and Control Workshop |
![]() ![]() |
|
Security ShortsDanger - Any Libraries Higher than QSYS?By Dan Riehl If you, or your software provider, places a library higher than QSYS on the system library list, like ALTQSYS, make sure that the library authority is set to no higher than *PUBLIC AUT(*USE). This will restrict *PUBLIC users from placing new objects into the library. Also make sure that you secure the individual objects in the library with *PUBLIC AUT(*USE) for programs, commands and other static object types, and *PUBLIC AUT(*CHANGE) or less for dynamic objects like database files and data areas. Since we rely heavily on resolving object references using the job's library list, any object in a library ahead of QSYS can override the expected functioning of the operating system and your application software. In this respect, programs and commands can act as a Trojan Horse on your system. Numerous 3rd party software vendors require a library ahead of QSYS, but do not secure the libraries with *PUBLIC AUT(*USE). Instead, they are mostly installed as *PUBLIC AUT(*CHANGE), or even *PUBLIC AUT(*ALL). Check with your vendor for their solution to the integrity vulnerability they have introduced onto your system. |
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 2013 - SecureMyi.com, all rights reserved SecureMyi.com | St Louis MO 63017 |