Average IBM i Security Levels (QSECURITY) on Power Systems
Each year, the State of IBM i Security Study analyzes the latest data around cybersecurity controls around this powerful operating system. The data comes from Security Scans performed by HelpSystems throughout the previous year, and shows what organizations are actually doing to secure their IBM i data—and it reveals areas where the failure to follow best practices can leave organizations vulnerable to data leaks or breaches.
IBM i security best practices start with the configuration of numerous system values, which regulate how easy or difficult it is for an outsider to use or abuse your system. Poorly configured or unmonitored system values are an unacceptable security risk.
What is QSECURITY Level and what’s the risk?
The system security level (QSECURTY) sets the overall tone, although it is often undermined by other settings. IBM recommends and ships security level 40 as the minimum, due to documented vulnerability found in level 30 and below. It should be noted that, despite the change to the default setting, a server migration will typically reload this to the same value as found on the previous generation of the server.
Power Systems servers can be configured at one of five different security levels:
- Level 10 — No Security. No password required. User IDs are created for any user who attempts to sign on. IBM no longer supports level 10.
- Level 20 — Password Security. Every user must have a valid ID and password. Every user with a valid ID and password assumes root-level authority (*ALLOBJ) by default.
- Level 30 — Resource Security. Object-level authority is enforced as users do not assume root-level authority by default. A moderately knowledgeable programmer or operator can bypass resource-level security and assume root-level authority.
- Level 40 — Operating System Security. Level 30 protection plus additional operating system integrity. It is possible for an extremely knowledgeable programmer with access to your system to elevate his or her level of authority, possibly as high as root-level authority.
- Level 50 — Enhanced Operating System Security. Level 40 protection plus enhanced operating system integrity. A properly secured system at security level 50 is the best defense. However, even at level 50, other system configuration issues must be addressed.
The data on system security level
Figure 2 shows the distribution of security settings on the systems included in the 2019 dataset. Out of the 244 systems studied, 24 percent were running system security level 30 and four percent were running at security level 20. Overall, nearly 30 percent fell short of IBM’s recommended minimum level (Figure 2A). This percentage is disturbingly high since the vulnerabilities at levels 20 and 30 are well-known and considering previous studies showed this aspect of IBM i security improving. In the previous State of IBM i Security Study, only 19 percent of systems studied fell below level 40.
How to reduce your risk
Bringing your system up to QSECURITY level 40 or higher is a critical step toward protecting your system. Organizations that are unsure of the potential impact of system value changes may want to consult with IBM i security professionals first, but a solution should be applied quickly. Outsourcing this task to security professionals like the team at HelpSystems is a way to eliminate quickly all the guesswork from the process.
Find out where IBM i systems tend to be secure and where they're often vulnerable. Download the complete State of IBM i Security Study today.