RE: security of spooled files

["Mark A. Manske" <mmanske@xxxxxxxxxxxxxxxxxx>]

For starters,  Limit capabilities should equal *YES, sec level should be 40,
user class should be *user, special authority should not be control spool
files, no group that has more authority should be attached to the users that
can see these files, the commands (wrksplf, wrkoutq, ect. should be
restricted with user profiles or an auth list) There are many other issues
dealing with security; and though these few words look innocent enough, if
the AS/400 has been left wide open so that "people could work" then you have
a long, hard road ahead to clean up the holes with-in your own organization.

HTH and gets you started

Mark A. Manske
[mailto:mmanske@minter-weisman.com]
Sr. Project Lead
Minter-Weisman



-----Original Message-----
From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
Behalf Of Lynette Chronister
Sent: Tuesday, October 17, 2000 1:38 PM
To: RPG400-L@midrange.com
Subject: security of spooled files


I was wondering if anyone had any ideas of how to secure my payroll
processor's spool files.  Her reports and etc are accessible to others.

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---