IBM i Security Exposure Check
Answer twelve questions about the controls running on your IBM i. You will get an instant readiness reading, a visual breakdown of the weak areas, and the three fixes worth doing first.
The 12-Question IBM i Exposure Reading
Choose the answer you can prove today. If you are not sure, choose the uncertain answer. That uncertainty is useful because it tells you which evidence to collect first.
Readiness result
Control-area reading
The bars make weak areas visible without hiding them inside a single score.
Your first three fixes
Evidence to collect next
Use these items to replace self-reported answers with proof from the system.
This is a triage reading based on your answers. It is not a penetration test, vulnerability scan, or compliance attestation.
What the Reading Measures
The result measures whether the main IBM i security layers are present, enforced, and backed by evidence. It gives uncertain answers real weight because an unverified control cannot be trusted during an incident.
The six control areas in the reading
| Control area | What a strong answer proves | Useful evidence |
|---|---|---|
| Foundation | The operating-system baseline and user-profile inventory are current | QSECURITY plus a dated profile report |
| Authority | Powerful and default access are limited by design | Special-authority and object-authority reports |
| Network access | Services cannot bypass sign-on controls or use plain transport | Exit-point rules and client-side connection tests |
| Detection | Useful events are collected and reach a named reviewer | QAUD values, sample events, alerts, and review records |
| Data protection | Sensitive live data and recovery copies are encrypted with recoverable keys | Data map, key records, and a restore result |
| Identity and recovery | Strong identity reaches the real entry routes and a clean recovery remains possible | MFA coverage map and isolated restore proof |
Use the Answer Without Turning It Into Shelfware
Verify the first finding
Collect the evidence named in the result. Replace assumptions with current system output before changing production.
Test the control
Prove the proposed change against real application and network traffic in a safe environment.
Make one owner responsible
Give the fix a person, a completion date, and a clear test for done.
Run the reading again
Use the same answers after remediation so the improvement is visible and the next weak area moves up.
A high reading does not prove the absence of a vulnerability. It proves that the broad control layers in this tool are better covered by the answers and evidence you supplied. Use the security assessment and audit process for deeper verification.