In an article by Rich Loeber about raising the level of your iSeries security. The author notes, "Moving from level 30 and higher is fairly easy and just requires that you make the change to the system value and perform an IPL. If you are uncertain about your third-party software, you can activate audit logging for a few weeks before you make the change and then review the logs to see if there are any potential problems at level 40...
or 50." This sounds like a great unobtrusive planning step that I would want to implement, but it doesn't explain further. What am I looking for in audit logging and how do it activate it?
You are right. While not complex, there are a few details you need to consider before moving to security level 40. Here's an MCPressOnline Security Patrol .r2vsa6Cn84f.3@.6ae55a97>article that I wrote that provides more details.
MORE INFORMATION ON THIS TOPIC
The Best Web Links: tips, tutorials and more.
Search400's targeted search engine: Get relevant information on security.
Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.
Dig deeper on iSeries system and application security
Related Q&A from Carol Woodbury
Before changing password levels and upgrading operating systems on the AS/400, ensure the clients connecting to the NetServer do not need the old ...continue reading
Look in the audit journal (QAUDJRN) on the AS/400 for an authority failure message with the name of the library as the object name. Use the ...continue reading
When error messages arise concerning attempts to use a permanent system object without authority, find the source of the issue by looking for an AF ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.