IBM i Security News Bytes

Linoma releases Managed File Transfer Solution GoAnywhere Director 4.0
Review the announcement from Linoma
In the last week of the year, the folks at Linoma Software released Version 4.0 of their managed file transfer solution.

Raz-Lee's iSecurity Certified for IBM's Q1 Labs Security Intelligence Partner Program
More information on the Q1 Labs Partnership
Raz-Lee continues to grow iSecurity partnerships through integrating iSecurity with enhanced formats for data transfer including LEEF (Log Event Enhanced Format), AXIS (Asset Exchange Information Souce) and other Q1 Labs' standard formats.

The 400 School, Inc. and SecureMyi.com
Live Online Security Workshop from The 400 School and SecureMyi.com
Dan Riehl presents his 4-Day Live Online Hands-on Security Workshop for the IBM i
Jan 17-20, 2012. Very limited seating. Register early to reserve your seat in the class.

IBM i Security Calendar of Events

Live Security Webcasts for IBM i

Using Policy Minder for IBM i for PCI Compliance
Presented by Carol Woodbury - Sponsored by Skyview Partners
Wednesday January 26 10:00 a.m. PST
More Information and Register to Attend

More Security Events

Jan 17-20 - The 400 School - Live Online Security Workshop

May 6-9 - COMMON-A User Group - Annual Conference and Expo - Anaheim, CA

Security Shorts - Who Removed my Exit Program?
(WRKREGINF)

By Dan Riehl

I have heard the question many times; 'Who removed my exit program?" Or 'Where did my FTP and Create User Profile registered exit programs go? Perhaps a more interesting question might be "How did that exit program get there?"

If you have created the QAUDJRN journal, and have set the associated System Values(QAUDCTL and QAUDLVL) correctly, you have an audit trail of all changes that have been made to your exit point registry. There are 2 auditing methods you can use to collect information about Exit Point Registry changes. You can use Object Auditing, and/or you can use Event auditing. When dealing with the exit point registry, I think you will find that Event auditing may be a better choice. But, I'll present both methods and you can choose which one you like. You may prefer to use both, which is what I recommend.

Auditing the Object

The Exit Point Registry is stored in the object QUSEXRGOBJ in library QUSRSYS. The object type is *EXITRG.

In order to start auditing the Exit Point Registry object you first need to ensure that the QAUDCTL system value includes the value *OBJAUD. This allows you to being auditing access to objects. Once this is done, you can then start auditing changes to the registry object using the following command.

CHGOBJAUD OBJ(QUSRSYS/QUSEXRGOBJ) OBJTYPE(*EXITRG) OBJAUD(*CHANGE)

Now, whenever a change is made to the registry, a ZC(Object Accessed for Change) journal entry is written to the QAUDJRN journal, indicating that the QUSEXRGOBJ object was accessed in Update mode, and/or was changed. Additional information provided in the ZC journal entry includes information like Job User, Current User, Job Name, Program that made the change, the timestamp of the entry, etc.

The operations that can be audited for the QUSEXRGOBJ object are:

ADDEXITPGM --- Add Exit Program CL Command  
QUSADDEP --- Add Exit Program API 
QusAddExitProgram --- Add Exit Program API 
QUSDRGPT --- Unregister Exit Point API 
QusDeregisterExitPoint --- Unregister Exit Point API 
QUSRGPT --- Register Exit Point API 
QusRegisterExitPoint --- Register Exit Point API 
QUSRMVEP --- Remove Exit Program API 
QusRemoveExitProgram --- Remove Exit Program API 
RMVEXITPGM --- Remove Exit Program CL Command 
WRKREGINF --- Work with Registration Information CL Command  

To review all ZC entries, you can use your favorite QAUDJRN reporting software. In V5R4 IBM provided the command CPYAUDJRNE(Copy Audit Journal Entries) which is a very nice command to extract information from QAUDJRN. Here's the command you can use to extract the ZC(Object Accessed for Change) entries into a formatted output file.

CPYAUDJRNE ENTTYP(ZC) OUTFILE(MYLIB/QAUDIT)

This will create a file QAUDITZC in library MYLIB. The columns in the output file are specific to the ZC journal entry type. To list the ZC entries, you can use the command:

RUNQRY *N MYLIB/QAUDITZC

If you are auditing numerous objects on your system, you will need to select only the records where the object name is QUSEXRGOBJ.

Auditing the Event of a change to the Exit Point Registry

To audit security configuration events, like a change to the exit point registry, you set the System value QAUDCTL to include the value *AUDLVL, and include the value *SECCFG or *SECURITY in the QAUDLVL, or QAUDLVL2, system value.

If this is done, and someone or some process manipulates the Exit Point Registry, a journal entry is written to the QAUDJRN journal. The journal entry type for this access is GR(Generic Record). As of IBM i 6.1, all GR entries are related to the Exit Point Registry.

You can review the GR entries just like the ZC entries. Here's the command you can use to extract the GR entries into a formatted output file.

CPYAUDJRNE ENTTYP(GR) OUTFILE(MYLIB/QAUDIT)

This will create a file QAUDITGR in library MYLIB. The columns in the output file are specific to the GR journal entry type. To list the GR entries, you can use the command:

RUNQRY *N MYLIB/QAUDITGR

The information provided includes what function was performed, Job User, Current User, Job Name, Program used, Timestamp, etc.