Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Security Auditing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Security Auditing

    Going to be changing our system from level 30 to 40. Currently getting AF's in AUDJRN on the QSYS/QAFDSAV file for all of our application programmers, and QPADEV*** devices using VRYDEV program for some of our users. I think this may be related to the way someone tried to secure the QSYS Library. The file has *PUBLIC *CHANGE, The Library has *PUBLIC *USE, but there is an auth. list with QSYS *ALL, PGMRS *USE, *PUBLIC *EXCLUDE. I'm not quite sure why this was done, but would like to know how QSYS should be secured? and what problems are going to occur by going to level 40 without changing the auth. list?

  • #2
    Security Auditing

    Kevin, Read the section on Changing to Security Level 40 in the Security Reference manual. Not all AF audit records will cause problems when you move from security level 30 to 40. I suggest that you set the QSYS library to public *USE and remove the authorizaiton list. No user should have have more than *USE public or private authority to the QSYS library. Ed Fishel

    Comment

    Working...
    X