HP UX 11i Role-based Access Control (RBAC) Software manual Network Rules

Page 65

/* allow the children to access UNIX domain */ /* sockets created by the parent compartment */

grant uxsock server_children

Access

Specifies whether the rule is object-centric or subject-centric. The

 

options are:

 

grant: Specifies an object-centric rule. This rule allows processes

 

in the compartment compartment_name to access the specified

 

IPC mechanism in the current compartment.

 

access: Specifies a subject-centric rule. This rule allows processes

 

in the current compartment to access the specified IPC mechanism

 

in the compartment compartment_name.

Method

Specifies the method of communication this rule applies to. The options

 

are:

 

pty: Specifies that the rule applies to pty used in interprocess

 

communication.

 

fifo: Specifies that the rule applies to FIFOs.

 

uxsock: Specifies that the rule applies to UNIX domain sockets.

 

ipc: Specifies that the rule applies to SYSV and POSIX IPC objects,

 

such as shared memory, semaphores, and message queues.

compartment_name

The name of the other compartment where processes in this

 

compartment can communicate with.

The second type of IPC rule governs process access. The syntax for this type of rule is as follows:

(sendreceive) signal <compartment_name>

For example:

/* allow the parent to send signals to children */ send signal server_children

Direction

Specifies whether processes in the current compartment have access

 

to view and alter process behavior from another specified compartment.

 

The options are:

 

send: Specifies a subject-centric rule. Allows processes in the

 

current compartment to send signals view process data in the

 

compartment compartment_name.

 

receive: Specifies an object-centric rule. Allows processes in the

 

compartment compartment_name to send signals and view

 

process data in the current compartment.

signal

Specifies that this rule applies to signals and process visibility.

compartment_name

The name of the other compartment where processes in the current

 

compartment can have access to view process information or to be

 

viewed from.

Network Rules

Network rules govern access to network interfaces. Network rules also govern communication between processes that use INET domain communication (TCP/IP sockets and streams). The default behavior is to deny access to the network.

Network endpoints are treated as objects labeled with the compartment of the process that creates them. However, a network endpoint can be created by one process, then passed to another

Compartment Rules and Syntax 65

Image 65
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 Intended Audience About This DocumentNew 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 HP-UX 11i Security Containment Introduction AuthorizationConceptual Overview Account Policy ManagementDefined Terms Features and BenefitsIsolation AuditingFeatures Benefits Prerequisites and System Requirements InstallationInstalling HP-UX 11i Security Containment # swlist -d @ /tmp/securitycontainmentbundle.depot Verifying the HP-UX 11i Security Containment Installation# swverify SecurityExt # swlist -a state -l fileset SecurityExtVerifying the HP-UX Role-Based Access Control Installation Installing HP-UX Role-Based Access ControlInstalling HP-UX Standard Mode Security Extensions # swverify RbacUninstalling HP-UX Rbac Uninstalling HP-UX 11i Security Containment# 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 HP-UX Rbac Components Example of Authorizations Per RoleHP-UX Rbac Configuration Files HP-UX Rbac Access Control Policy SwitchHP-UX Rbac Commands HP-UX Rbac Configuration FilesHP-UX Rbac Manpages HP-UX Rbac CommandsHP-UX Rbac Architecture HP-UX Rbac ManpagesHP-UX Rbac Architecture HP-UX Rbac Example Usage and OperationPlanning the Roles Planning Authorizations for the RolesPlanning the HP-UX Rbac Deployment HP-UX Rbac Limitations and Restrictions Planning Command MappingsConfiguring 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 Hierarchical Roles Example Roles Configuration in HP-UX Rbac B.11.23.02Overview Examples of Hierarchical RolesExample 3-1 The authadm Command Syntax Changes to the authadm Command for Hierarchical RolesExample 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 GID Configuring HP-UX Rbac to Generate Audit TrailsProcedure for Auditing HP-UX Rbac Criteria Following is the privrun command syntax Using HP-UX Rbac# 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 Fine-Grained Privileges Commands CommandsFine-Grained Privileges Fine-Grained Privileges ComponentsManpages Available PrivilegesFine-Grained Privileges Manpages Available PrivilegesOr launch policy Configuring Applications with Fine-Grained Privileges# setfilexsec options filename Privilege ModelCompound Privileges Troubleshooting Fine-Grained Privileges Fine-Grained Privileges in HP Serviceguard ClustersSecurity Implications of Fine-Grained Privileges Privilege Escalation# getprocxsec options pid Compartment Architecture CompartmentsCompartment Architecture Planning the Compartment Structure Default Compartment ConfigurationActivating Compartments Modifying Compartment Configuration# setrules -p # cmpttune -eCompartment Components Compartment Configuration FilesChanging Compartment Rules Changing Compartment NamesCompartment Configuration Files Compartment CommandsCompartment Commands Compartment ManpagesFile System Rules Compartment Rules and SyntaxCompartment Definition Permissionlist IPC RulesIPC mechanism in the current compartment Network RulesAccess Interface Miscellaneous RulesExample Rules File Configuring Applications in CompartmentsTroubleshooting Compartments # vhardlinks Configured rules are loaded into the kernelDo not configure standby LAN interfaces in a compartment Compartments in HP Serviceguard ClustersStandard Mode Security Extensions Configuration Files Configuring Systemwide AttributesSecurity Attributes and the User Database System Security AttributesManpages CommandsAttributes Troubleshooting the User Database Configuring Attributes in the User DatabaseAuditing Auditing ComponentsAuditing Your System Audit CommandsPlanning Your Auditing Implementation Enabling AuditingAUDEVENTARGS1 = -P -F -e admin -e login -e moddac # audevent -P -F -e admin -e login -e moddacMonitoring Audit Files #audsys -n -c primaryauditfile -sAuditing Users Guidelines for Administering Your Auditing SystemPerformance Considerations #audsys -fAuditing Events Audevent command optionsStreamlining Audit Log Data # /usr/sbin/userdbset -u user-nameAUDITFLAG=1Self-auditing processes Audit Log Files#/usr/sbin/audisp auditfile Configuring Audit Log FilesViewing Audit Logs Examples of Using the audisp Command Page Index SymbolsSecurity attribute defining
Related manuals
Manual 10 pages 36.76 Kb