Why the fuss about special authorities? Skipping a discussion of *ALLOBJ for the moment, special authorities provide users with the capability to perform specialized functions. If that capability falls outside of their job responsibilities, they shouldn't have the special authority. Assigning users only the capabilities sufficient to perform their job functions is a requirement of several laws and regulations (including PCI Data Security Standards). In addition, it makes good business sense to allow users only the capabilities that they need.
*ALLOBJ is slightly different. Users assigned *ALLOBJ special authority can access all objects. Once you assign a user *ALLOBJ, that user cannot be prevented from accessing any object on the system. I heard the other day of an administrator trying to restrict programmers' access to several libraries. However, they had been assigned *ALLOBJ. Given the way i5/OS performs its authority checks, users with *ALLOBJ will always have access to an object. Attempting to restrict their access was a waste of time.
Why are special authorities out of control? Because most profiles are not created from "scratch." Most profiles are created by copying another profile. So if the original profile has more special authorities than necessary, the new profile will also have those special authorities.
Here are the capabilities (special authorities) you can grant users and the functions they provide:
| Special Authorities and Their Functions | |
| *AUDIT | Configuration of i5/OS auditing attributes |
| *IOSYSCFG | Communications configuration and management |
| *JOBCTL | Management of a job on the system |
| *SAVSYS | Ability to save and restore the entire system or any object on the system, regardless of authority to the object |
| *SECADM | Create/change/delete user profiles |
| *SERVICE | Ability to use Service Tools, perform a service trace, debug another user's job |
| *SPLCTL | Access to every spooled file on the system regardless of authority to the outq (the "*ALLOBJ" of spooled files) |
| *ALLOBJ | Access to every object on the system. It is impossible to prevent an *ALLOBJ user from accessing an object! |
Taking Control
The best way to rework the assignment of special authorities is to first assign users to a role. Typical roles include system administrator, operator, programmer, change control administrator, database administrator, analyst, and end user. Next, list the tasks each role typically performs. Finally, list the special authorities required by each task. This determines which special authorities each role requires.
How Skyview Policy Minder Can Help
To detect when users have gained special authorities they shouldn't have, there are two ways that Policy Minder can help.
First, you can define a user profile template, choosing to include all users of a particular user class (such as *SECOFR or *USER) or a specific group; then, specify which special authorities the users in the user class or group are to have. For example, you may specify that all users in the *SYSOPR user class are to have *SAVSYS and *JOBCTL special authorities. When you run a compliance check, the special authorities assigned to the profiles belonging to the specified user will be checked against the template (policy) you created. Any profile's special authorities that don't match the policy will be flagged as being out of compliance with the policy.
The second way that you can check special authorities with Policy Minder is to create a slightly different user profile template. In this template, you include all users who have a specific special authority—for example, *ALLOBJ. Then you specify *NO for the attribute "Allow new user profile." The first time you run a compliance check, it establishes the baseline of all users who currently have the special authority (in our example, *ALLOBJ.) The next time you run a compliance check, any profile that has been created with, changed to have, or restored with *ALLOBJ assigned will be flagged as *NEW and, therefore, out of compliance. This method is especially helpful in keeping track of the very powerful special authorities such as *ALLOBJ as well as the special authorities auditors may want to limit, such as *AUDIT.
Carol Woodbury is President and co-founder of SkyView Partners Inc., a company specializing in security policy and compliance software and services. Carol is a system security expert and an award-winning author and presenter. She is also the co-author of Experts' Guide to OS/400 and i5/OS Security.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online