Novell OPEN ENTERPRISE SERVER 2 SP2 - ADMINISTRATION, Implementation Manual, Page: 275 / 288

System User and Group Management in OES 2 SP2 275
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
I.8 Auditing System Users
It is the nature of the Linux operating system and the POSIX security model that the
root
user has
access to all system information stored on the local server. Due to this fact, some organizations
choose to monitor the activities of privileged users.
If you are interested in monitoring such activities, two Novell products can assist you.
Š
Novell Sentinel: Universal Password events can be monitored using Novell Sentinel. You
enable this by modifying the NMAS Login Policy Object. For instructions, see Auditing
NMAS Events (http://www.novell.com/documentation/nmas33/admin/data/bwmt40o.html) .
Then refer to the Novell Sentinel Documentation (http://www.novell.com/documentation/
sentinel6/) for further instructions.
Š Privileged User Manager: This product lets you monitor root user activities on the OES
server by collecting data, analyzing keystrokes, and creating indelible audit trailes. For more
information, see the
Novell Privileged User Manager Documentation (http://www.novell.com/
documentation/privilegedusermanager22/index.html) .
www Apache
Tomcat
QuickFinder
Apache (wwwrun) and tomcat (novlwww) use the
group ID (gid) of this group to run.
QuickFinder requires that all users who manage the
service (including the eDirectory Admin user) belong
to this group.
User
novlxsrvd
is in the group because it needs
access to an Apache domain socket.
When NSS is installed on the Linux server, this group
is removed from the local system and created in
eDirectory. This is required because members of this
group must have access to NSS data, and all NSS
access is controlled through eDirectory.
System User or Group Name Associated Service Purpose