HP UX 11i Role-based Access Control (RBAC) Software manual Viewing Audit Logs

Page 80
-p
-c system_call -t
-s
-uuser-name
-lterminal-name
80 Standard Mode Security Extensions
-f

NOTE: If the primary audit log continues to grow past the FSS point, a system-defined parameter, minfree, can be reached. All auditable actions are suspended for regular users at this point. Restore the system to operation by archiving the audit data, or specifying a new audit log file on a file system with space.

NOTE: If other activities consume space on the file system, or the file system chosen has insufficient space for the AFS size chosen, the File Space Switch point can be reached before the Audit File Switch point.

Choose a file system with adequate space for your audit log files. You can assess the size of your file systems using the bdf command. HP recommends you configure your log files to at least the following parameters:

The file system must have more than 5000 KB available for the primary audit log file.

It must have more than 20% of its total file space available.

TIP: HP recommends that the primary and auxiliary audit log files reside on separate file systems.

The growth of audit log files is closely monitored by the audit overflow monitor daemon, audomon, to insure that no audit data is lost.

Configuring Audit Log Files

Use the audsys command to specify the primary audit log file and the (optional) auxiliary audit log file to collect auditing data. For example:

#audsys -c primary_audit_file -s 5000 -x auxiliary_audit_file -z 2500

This example specifies a primary audit file 5000K in size, and an auxiliary audit file 2500K in size. Refer to audsys(1M) for more information about using the audsys command to configure audit log files.

NOTE: If you specify the name of an existing file as your auxiliary audit log file, the contents of the file will be overwritten.

CAUTION: If the file system containing the primary log file is full and no auxiliary log file is specified, any non root process that generates audit data will block inside the kernel. Also, if a non root process is connected to the system terminal, it will be terminated. For details see the WARNINGS section of the audsys(1M) manpage.

Viewing Audit Logs

Auditing accumulates a lot of data. Use the audisp command to selects the data you want to view:

#/usr/sbin/audisp audit_file

The following options are available with the audisp command:

Displays failed events only.

Displays successful events only.

Displays the selected system call.

Displays start time.

Displays end time.

Displays information for a specific user.

Displays information for a specific terminal.

Image 80
Contents HP-UX 11i Security Containment Administrators Guide Copyright 2007 Hewlett-Packard Development Company, L.P Table of Contents Fine-Grained Privileges Index Page List of Figures Page List of Tables Page List of Examples Page About This Document Intended AudienceNew and Changed Information in This Edition Publishing HistoryUserInput Typographic ConventionsHP-UX Release Name and Release Identifier HP-UX 11i Releases Related InformationHP Encourages Your Comments Page Authorization HP-UX 11i Security Containment IntroductionConceptual Overview Account Policy ManagementFeatures and Benefits Defined TermsIsolation AuditingFeatures Benefits Prerequisites and System Requirements InstallationInstalling HP-UX 11i Security Containment Verifying the HP-UX 11i Security Containment Installation # swlist -d @ /tmp/securitycontainmentbundle.depot# swverify SecurityExt # swlist -a state -l fileset SecurityExtInstalling HP-UX Role-Based Access Control Verifying the HP-UX Role-Based Access Control InstallationInstalling HP-UX Standard Mode Security Extensions # swverify RbacUninstalling HP-UX 11i Security Containment Uninstalling HP-UX Rbac# swverify TrustedMigration # swlist -a state -l fileset TrustedMigration# swremove TrustedMigration Uninstalling HP-UX Standard Mode Security Extensions# swremove Rbac Page Overview HP-UX Role-Based Access ControlHP-UX Rbac Versus Other Rbac Solutions Example of Authorizations Per User Access Control BasicsSimplifying Access Control with Roles Example of Authorizations Per Role HP-UX Rbac ComponentsHP-UX Rbac Access Control Policy Switch HP-UX Rbac Configuration FilesHP-UX Rbac Commands HP-UX Rbac Configuration FilesHP-UX Rbac Commands HP-UX Rbac ManpagesHP-UX Rbac Architecture HP-UX Rbac ManpagesHP-UX Rbac Example Usage and Operation HP-UX Rbac ArchitecturePlanning the Roles Planning Authorizations for the RolesPlanning the HP-UX Rbac Deployment Planning Command Mappings HP-UX Rbac Limitations and RestrictionsConfiguring HP-UX Rbac Example Planning Results Configuring RolesCreating Roles Assigning Roles to Groups Configuring AuthorizationsAssigning Roles to Users Configuring Additional Command Authorizations and Privileges Is mainly intended for scripts Example Roles Configuration in HP-UX Rbac B.11.23.02 Hierarchical RolesOverview Examples of Hierarchical RolesChanges to the authadm Command for Hierarchical Roles Example 3-1 The authadm Command SyntaxExample 3-2 Example of the authadm Command Usage Hierarchical Roles ConsiderationsConfiguring HP-UX Rbac with Fine-Grained Privileges Matches the following /etc/rbac/cmdpriv entries Configuring HP-UX Rbac with CompartmentsCommand Configuring HP-UX Rbac to Generate Audit Trails GIDProcedure for Auditing HP-UX Rbac Criteria Using HP-UX Rbac Following is the privrun command syntax# privrun ipfstat HP-UX Rbac in Serviceguard Clusters Customizing privrun and privedit Using the Acps Privrun -v Information Troubleshooting HP-UX RbacRbacdbchk Database Syntax Tool Commands Fine-Grained Privileges CommandsFine-Grained Privileges Fine-Grained Privileges ComponentsAvailable Privileges ManpagesFine-Grained Privileges Manpages Available PrivilegesConfiguring Applications with Fine-Grained Privileges Or launch policy# setfilexsec options filename Privilege ModelCompound Privileges Fine-Grained Privileges in HP Serviceguard Clusters Troubleshooting Fine-Grained PrivilegesSecurity Implications of Fine-Grained Privileges Privilege Escalation# getprocxsec options pid Compartments Compartment ArchitectureCompartment Architecture Default Compartment Configuration Planning the Compartment StructureModifying Compartment Configuration Activating Compartments# setrules -p # cmpttune -eCompartment Configuration Files Compartment ComponentsChanging Compartment Rules Changing Compartment NamesCompartment Commands Compartment Configuration FilesCompartment Commands Compartment ManpagesFile System Rules Compartment Rules and SyntaxCompartment Definition IPC Rules PermissionlistNetwork Rules IPC mechanism in the current compartmentAccess Miscellaneous Rules InterfaceExample Rules File Configuring Applications in CompartmentsTroubleshooting Compartments Configured rules are loaded into the kernel # vhardlinksCompartments in HP Serviceguard Clusters Do not configure standby LAN interfaces in a compartmentStandard Mode Security Extensions Configuring Systemwide Attributes Configuration FilesSecurity Attributes and the User Database System Security AttributesManpages CommandsAttributes Configuring Attributes in the User Database Troubleshooting the User DatabaseAuditing Auditing ComponentsAudit Commands Auditing Your SystemPlanning Your Auditing Implementation Enabling Auditing# audevent -P -F -e admin -e login -e moddac AUDEVENTARGS1 = -P -F -e admin -e login -e moddacMonitoring Audit Files #audsys -n -c primaryauditfile -sGuidelines for Administering Your Auditing System Auditing UsersPerformance Considerations #audsys -fAudevent command options Auditing EventsStreamlining Audit Log Data # /usr/sbin/userdbset -u user-nameAUDITFLAG=1Audit Log Files Self-auditing processes#/usr/sbin/audisp auditfile Configuring Audit Log FilesViewing Audit Logs Examples of Using the audisp Command Page Symbols IndexSecurity attribute defining
Related manuals
Manual 10 pages 36.76 Kb