SAF
The standard way z/OS and its software ask the security manager: is this allowed?
Also written System Authorization Facility
Why it matters. When you open a dataset and RACF says no, SAF carried the question.
Remember
- Programs call SAF, for example with the RACROUTE macro. They don't call RACF directly.
- SAF passes the question to whichever security manager is installed. It answers allowed, not allowed, or no decision when it has no rule.
- That is why RACF, ACF2 and Top Secret can replace each other.
The usual mistake
SAF is another name for RACF.
SAF is the way of asking. RACF is one security manager that answers.
SAF asks the question. RACF decides the answer.
On real z/OS
MF/OS has RACF only. SAF isn't a separate layer you can see: there is no RACROUTE to call and no other security product to swap in. Its code makes the access checks directly.
Where can I practise SAF?
Right here, at ZedBank. You take a junior job at a simulated bank and use SAF in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- RACFThe security manager for z/OS, which decides who may sign on, read a dataset, or run a transaction.
- Access levelHow much a user may do to a resource: read it, change it, or control it, with each level including the ones below.
- SubsystemA major piece of software running under z/OS that provides a service to applications, such as a database or a transaction manager.
- z/OSThe main operating system that runs on IBM mainframes, in the same way Windows or Linux runs on a laptop or server.
- Dataset profileA security rule describing which datasets it covers and who is allowed to do what to them.