This document provides an introduction to Adabas SAF Security (ADASAF).
The System Authorization Facility (SAF) is used by z/OS and compatible sites to provide rigorous control of the resources available to a user or group of users. Security packages such as RACF, CA-ACF2, and CA-Top Secret allow the system administrator:
to maintain user identification credentials such as User ID and password; and
to establish profiles determining the datasets, storage volumes, transactions, and reports available to a user.
The resulting security repository and the infrastructure to administer it represent a significant investment. At the same time, the volume of critical information held by a business is constantly growing, as is the number of users referencing the data. The challenge of controlling these ever-increasing accesses requires a solution that is flexible, easy to implement and, above all, one that safeguards the company's investment.
Adabas SAF Security (ADASAF) enhances the scope of SAF-based security packages by integrating Adabas resources into the central security repository. ADASAF enables
a single control and audit system for all resources;
industry-standard protection of Adabas data;
maximized return on investment in the security repository.
Adabas SAF Security can be used to protect the following resources:
Adabas SAF Security can be used to protect the following Adabas resources:
|Adabas Nucleus|| Only authorized users are allowed to:
|Adabas Utilities||Only authorized users are allowed to execute utilities, and then only the appropriate ones. Authorization can be restricted by utility name/function/file as well as Database ID. For example, a user or group of users might be permitted to run ADAREP but not ADASAV against a particular database.|
|Database Files||Users or groups of users can be permitted (or denied) access to the basic resource of database files.|
|Database Commands|| Access (
|Production Environment Data||Distinction can be made between a user operating in a production system and the same user operating in a test environment. This is known as cross-level checking and could be used, for example, to prevent damage by an application program inadvertently cataloged against the wrong Database ID.|
|Transaction Data|| ADASAF can optionally validate requests to store or retrieve
|Adabas Operator Commands||Restrictions can be placed on Adabas operator commands that can be issued from the MVS console.|
|File Passwords and Cipher Codes||Passwords and codes can be held in the security repository or supplied by a user exit and dynamically applied by ADASAF. This eliminates the need for the application to manage security data and removes the requirement to transmit sensitive information from the client to the database.|
|Adabas Basic Services||Adabas Basic Services can be protected with ADASAF by selecting the level of protection required (main functions only or main functions and subfunctions) and defining the appropriate resource profiles and granting the necessary users access to those profiles.|
|Stored Procedures||Only authorized users are allowed to invoke stored procedures.|
This protection is provided by running Adabas SAF Security in the Adabas nucleus and utilities.
Adabas SAF Security can be used to protect the online administration resources of the following COR-based Add-on products:
Adabas SAF Security (SYSAAF)
Adabas Fastpath (SYSAFP)
Adabas Transaction Manager (SYSATM)
Adabas Vista (SYSAVI)
Adabas System Coordinator (SYSCOR)
This protection is provided by running Adabas SAF Security in the Adabas System Coordinator daemon.
Adabas SAF Security can be used to protect the following Entire Net-Work resources:
Only authorized users are allowed to:
This protection is provided by running Adabas SAF Security under Entire Net-Work.
Adabas SAF Security runs in the address space of the job whose resources it is protecting.
The graphic below shows an example of the ADASAF main module running under an Adabas nucleus.
All users must first log on to their system using their Logon ID, usually a user name or code. Through the operating system or TP monitor, the installed security package performs authentication checks using the user’s supplied Logon ID and password.
When access is from a remote workstation or non-IBM platform, the Logon ID and logon password must be given to Adabas SAF Security using a remote logon procedure, as described in the section Logging On to a Database.
For Adabas, the router extracts the user's Logon ID from the system ACEE and makes it available in the Adabas nucleus for subsequent authorization checking.