PROCESS Class

Each record in the PROCESS class defines a program-an executable file-that runs in its own address space and that needs to be protected from being killed or getting debugged. Major utilities and database servers are good candidates for such protection since these processes are the main targets for denial-of-service attacks.
capamsc141
Each record in the PROCESS class defines a program-an executable file-that runs in its own address space and that needs to be protected from being killed or getting debugged. Major utilities and database servers are good candidates for such protection since these processes are the main targets for denial-of-service attacks.
Note:
When defining a program in the PROCESS class, we recommend that you also define it in the FILE class. This protects the executable by preventing someone from modifying (replacing or corrupting) the executable without authorization.
The PROCESS class now contains the following two access control attributes:
  • read
    Allows the process to be killed
  • attach
    Allows the process to be attached
Both the attributes are mutually independent and can be set together.
Note:
The ATTACH attribute of the PROCESS class that is introduced in the current release is not available in the Endpoint Management UI. The ATTACH access right is not applied to the rule even if the access right All is selected for the PROCESS class objects, in the Endpoint Management UI.
KILL Attribute
Privileged Access Manager
can protect against three terminate (kill) signals: the regular terminate signal (SIGTERM) and the two signals that an application cannot mask (SIGKILL and SIGSTOP):
Environment
Signal
Number
Windows
KILL
Win32 API
UNIX
Terminate Process
9
UNIX and Windows
STOP
Machine Dependent
UNIX and Windows
TERM
15
Other signals, such as SIGHUP or SIGUSR1, are passed to the process that they target and that process decides whether to ignore the terminate signal or whether to react to it in some way.
The key of the PROCESS class record is the name of the program the record protects. Specify the full path.
ATTACH Attribute
The ATTACH attribute of the PROCESS class authorizes the defined process for being attached by other processes for debugging or tracing; provided those processes are running under an authorized user.
Note:
Only the Linux and AIX operating systems support the ATTACH attribute.
To define the ATTACH attribute using the PROCESS class, create a record for a process that you want to authorize. Create the record without an owner and any access right defined. Using a Selang rule, you can authorize the process that you have created to be attached by any other process running under root.
If you had denied KILL access to a process and allowed ATTACH access to the same process, then the process can be killed by a process which has the access right ATTACH.
PROCESS Class Properties
The following definitions describe the properties contained in this class record. Most properties are modifiable and can be manipulated using selang or the administration interfaces. Properties marked as
informational
cannot be modified.
  • ACL
    Defines a list of accessors (users and groups) permitted to access the resource, and the accessors' access types.
    Each element in the access control list (ACL) contains the following information:
    • Accessor
      Defines an accessor.
    • Access
      Defines the access authority that the accessor has to the resource.
    Use the access parameter with the authorize or authorize- command to modify the ACL.
  • CATEGORY
    Defines one or more security categories assigned to a user or a resource.
  • COMMENT
    Defines additional information that you want to include in the record. 
    Privileged Access Manager
    does not use this information for authorization.
    Limit:
    255 characters.
  • CREATE_TIME
    (Informational) Displays the date and time when the record was created.
  • DAYTIME
    Defines the day and time restrictions that govern when an accessor can access a resource.
    Use the restrictions parameter with the chres, ch[x]usr, or ch[x]grp commands to modify this property.
    The resolution of daytime restrictions is one minute.
  • GROUPS
    Defines the list of CONTAINER records that a resource record belongs to.
    To modify this property in a class record, change the MEMBERS property in the appropriate CONTAINER record.
    Use the mem+ or mem- parameter with the chres, editres or newres command to modify this property.
  • NACL
The
NACL
property of a resource is an access control list that defines the accessors that are denied authorization to a resource, together with the type of access that they are denied (for example, write). See also ACL, CALACL, PACL. Each entry in the NACL contains the following information:
Accessor
Defines an accessor.
  • Access
    Defines the type of access that is denied to the accessor.
Use the authorize deniedaccess command, or the authorize- deniedaccess- command, to modify this property.
NOTIFY
Defines the user to be notified when a resource or user generates an audit event. 
Privileged Access Manager
can email the audit record to the specified user
.
Limit:
30 characters.
OWNER
Defines the user or group that owns the record.
PACL
Defines a list of accessors that are permitted to access the resource when the access request is made by a specific program (or a program that matches a name-pattern) and their access types. Each element in the program access control list (PACL) contains the following information:
  • Accessor
    Defines an accessor.
  • Program
    Defines a reference to a record in the PROGRAM class, either specifically or by wildcard pattern matching.
  • Access
    Defines the access authority that the accessor has to the resource.
Note:
You can use wildcard characters to specify the resource in a PACL.
Use the via(
pgm
) parameter with the selang authorize command to add programs, accessors, and their access types to a PACL, You can use the authorize- command to remove accessors from a PACL.
RAUDIT
Defines the types of access events that 
Privileged Access Manager
records in the audit log. RAUDIT derives its name from
R
esource
AUDIT
. Valid values are:
  • all
    All access requests.
  • success
    Granted access requests.
  • failure
    Denied access requests (default).
  • none
    No access requests.
Privileged Access Manager
 records events on each attempted access to a resource, and does not record whether the access rules were applied directly to the resource, or were applied to a group or class that had the resource as a member.
Use the audit parameter of the chres and chfile commands to modify the audit mode.
SECLABEL
Defines the security label of a user or resource.
Note:
The SECLABEL property corresponds to the label[-] parameter of the chres and ch[x]usr commands.
SECLEVEL
Defines the security level of an accessor or resource.
Note:
This property corresponds to the level[-] parameter of the ch[x]usr and chres commands.
UACC
Defines the default access authority for the resource, which indicates the access granted to accessors who are not defined to 
Privileged Access Manager
or who do not appear in the ACL of the resource.
Use the defaccess parameter with the chres, editres, or newres command to modify this property.
UPDATE_TIME
(Informational) Displays the date and time when the record was last modified.
UPDATE_WHO
(Informational) Displays the administrator who performed the update.
WARNING
Specifies whether Warning mode is enabled. When Warning mode is enabled on a resource, all access requests to the resource are granted, and if an access request violates an access rule, a record is written to the audit log.