TCP Class
Each record in the TCP class defines a TCP/IP service such as mail, ftp, and http. When the TCP class is being used for authorization, hosts can obtain services from the local host only if the TCP resources grant access. Also, users or groups on a local host can use the TCP/IP services to access remote hosts only if the TCP resources grant access.
capamsc141
Each record in the TCP class defines a TCP/IP service such as mail, ftp, and http. When the TCP class is being used for authorization, hosts can obtain services from the local host only if the TCP resources grant access. Also, users or groups on a local host can use the TCP/IP services to access remote hosts only if the TCP resources grant access.
The ACL in a TCP record can specify access types for hosts (HOST), groups of hosts (GHOST), networks (HOSTNET), and sets of hosts (HOSTNP).
The CACL in a TCP record can specify access types for hosts (HOST), groups of hosts (GHOST), networks (HOSTNET), and sets of hosts (HOSTNP), and can also specify access types for users and groups.
You can set rules based on IPv4 or IPv6 addresses, not just on host names. This means that you can cater for a domain name change.
The key of the TCP record is the name of the TCP/IP service. The TCP class controls both outgoing services and incoming services.
The following definitions describe the properties contained in a TCP class record. Most properties are modifiable and can be manipulated using selang or the administration interfaces. Non-modifiable properties are marked
informational.
- ACLDefines the hosts for which the local host provides service and the access types that are allowed.Each element in the access control list contains the following information:
- Host referenceDefines a HOST, GHOST, HOSTNET, or HOSTNP record.
- Permitted accessThe access authority that the referenced host has to the resource. The valid access authorities are:
- noneDoes not allow the host to perform any operations.
- readAllows the host to obtain TCP service from the local host.
- CACLA list of accessors (users and groups) permitted to access the resource and the host or hosts they can access. Each element in the conditional access control list (CACL) contains the following information:
- AccessorDefines an accessor.
- Host referenceDefines a HOST, GHOST, HOSTNET, or HOSTNP record
- AccessDefines the access authority that the accessor has to the resource. The valid access types are:
- writeAllows the accessor to use this service to access the host or group of hosts.
- noneDoes not allow the accessor to use this service to access the host or group of hosts.
- COMMENTDefines additional information that you want to include in the record.Privileged Access Managerdoes not use this information for authorization.Limit:255 characters.
- CREATE_TIME(Informational) Displays the date and time when the record was created.
- DAYTIMEDefines 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.
- GROUPSDefines 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.
- NACLTheNACLproperty 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:
- AccessorDefines an accessor.
- AccessDefines the type of access that is denied to the accessor.Use the authorize deniedaccess command, or the authorize- deniedaccess- command, to modify this property.
- NOTIFYDefines the user to be notified when a resource or user generates an audit event.Privileged Access Managercan email the audit record to the specified user.Limit:30 characters.
- OWNERDefines the user or group that owns the record.
- RAUDITDefines the types of access events thatPrivileged Access Managerrecords in the audit log. RAUDIT derives its name fromResourceAUDIT. Valid values are:
- allAll access requests.
- successGranted access requests.
- failureDenied access requests (default).
- none
- No access requests.Privileged Access Managerrecords 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.
- UACCDefines the default access authority for the resource, which indicates the access granted to accessors who are not defined toPrivileged Access Manageror 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.
- WARNINGSpecifies 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.
Example 1:
Prevent incoming connections from a remote host by using Telnet.Step 1:
Disable HOST and CONNECT classes, and enable TCP class.PAMSC> so class-(HOST)PAMSC> so class-(CONNECT)PAMSC> so class+(TCP)
Step 2:
Add a remote host (My_Remote_Host.example.com) in /etc/hosts. Run the following command at the command prompt.vi /etc/hosts
Step 3:
For network interception, the lookahead database "ladb" must be properly entered with the remote host address. To ensure this works, run the following command at the command prompt../sebuildla -h
Step 4:
Run the following command at the command prompt to verify that the remote host (My_Remote_Host.example.com) is added to /etc/hosts../sebuildla -H
Step 5:
Define a remote host (My_Remote_Host.example.com) from which we prevent incoming Telnet connections.PAMSC> nr HOST My_Remote_Host.example.com
Step 6:
Define a TCP resource for the Telnet service which allows outgoing Telnet connections.PAMSC> nr TCP telnet owner(nobody) defaccess(w)
Step 7:
Set a rule that prevents incoming connections from the remote host (My_Remote_Host.example.com) by using Telnet.PAMSC> authorize TCP telnet HOST(My_Remote_Host.example.com) access(n)
Step 8:
Try connecting from the remote host to the Privileged Access Manager
endpoint by using Telnet. The connection fails but other connections are not affected.Example 2:
Prevent a user from accessing all remote hosts by using Telnet service.Step 1:
Disable HOST and CONNECT classes, and enable TCP class.PAMSC> so class-(HOST)PAMSC> so class-(CONNECT)PAMSC> so class+(TCP)
Step 2:
Execute the following command at the command prompt and add all remote hosts to /etc/hosts.vi /etc/hosts
Step 3:
For network interception, the lookahead database "ladb" must be properly entered with the remote host address. To ensure this works, run the following command at the command prompt../sebuildla -h
Step 4:
Define remote hosts as resources by creating a host name pattern that covers all the remote hosts.PAMSC> nr HOSTNP *
Step 5:
Set a rule that denies a user (john) from accessing all the remote hosts.PAMSC> auth TCP telnet uid(john) hostnp(*) access(n)
Step 6:
Log in as john and try to access any remote host by using Telnet. The connection fails.