SV-223844r604139_rule
V-223844
SRG-OS-000080-GPOS-00048
RACF-US-000070
CAT II
10
SURROGAT class BPX resources are used in conjunction with server applications that are performing tasks on behalf of client users that may not supply an authenticator to the server. This can be the case when clients are otherwise validated or when the requested service is performed from userids representing groups.
Configure the default access for each BPX.SRV.userid resource must be no access. Access can be permitted only to system software processes that act as servers under z/OS UNIX (e.g., web servers) and users whose access and approval are identified in the Site Security Plan.
A sample is provided here:
RDEF SURROGAT BPX.SRV.user UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ))
-RACF rules for all BPX.SRV.user SURROGAT resources must restrict access to system software processes (e.g., web servers) that act as servers under z/OS UNIX.
RDEF SURROGAT BPX.SRV.user UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ))
PE BPX.SRV.user CL(SURROGAT) ID(<server>)
From the ISPF Command Shell enter:
RL SURROGAT BPX.SRV AUTHUSER
If the RACF rules for all BPX.SRV.user SURROGAT resources specify a default access of NONE, this is not a finding.
If the RACF rules for all BPX.SRV.user SURROGAT resources restrict access to system software processes (e.g., web servers) that act as servers under z/OS UNIX, this is not a finding.
If the RACF rules for all BPX.SRV.user SURROGAT resources restrict access to authorized users identified in the Site Security Plan, this is not a finding.
V-223844
False
RACF-US-000070
From the ISPF Command Shell enter:
RL SURROGAT BPX.SRV AUTHUSER
If the RACF rules for all BPX.SRV.user SURROGAT resources specify a default access of NONE, this is not a finding.
If the RACF rules for all BPX.SRV.user SURROGAT resources restrict access to system software processes (e.g., web servers) that act as servers under z/OS UNIX, this is not a finding.
If the RACF rules for all BPX.SRV.user SURROGAT resources restrict access to authorized users identified in the Site Security Plan, this is not a finding.
M
4101