+SYS.1.7.A9 Multi-Client Capability in z/OS (B)

SYS.1.7.A9 Multi-Client Capability in z/OS (B)

If a z/OS system is to be used by clients, an RACF concept for client separation MUST be created. The data and applications of the clients MUST be segregated by means of RACF profiles. High-level authorisations in RACF (SPECIAL, OPERATIONS, AUDITOR) and change access to files of the z/OS operating system MUST ONLY be granted to employees of the operator. The maintenance time slots in which the z/OS system will not be available MUST be coordinated with all the clients working on the system concerned.

1. Yleiskatsaus

1.1 Viittaukset

1.2 Tunnistetut vaatimukset

1.3 Liittyvät säädökset

2. Tunnistetut vaatimukset

Vaatimukset

3. Liittyvät säädökset

Säädökset

Linkitetyt tehtävät

Linkit
blocks G 0.14 Interception of Information / Espionage
blocks G 0.18 Poor Planning or Lack of Adaptation
blocks G 0.19 Disclosure of Sensitive Information
blocks G 0.21 Manipulation with Hardware or Software
blocks G 0.22 Manipulation of Information
blocks G 0.30 Unauthorised Use or Administration of Devices and Systems
blocks G 0.31 Incorrect Use or Administration of Devices and Systems
blocks G 0.32 Misuse of Authorisation
blocks G 0.36 Identity theft
blocks G 0.37 Repudiation of Actions
blocks G 0.39 Malware
blocks G 0.43 Attack with Specially Crafted Messages
blocks G 0.45 Data Loss
blocks G 0.46 Loss of Integrity of Sensitive Information