Complete Securityfor IBM i.Built for the New Threat Frontier.
Security Audit, Threat Detection & Offensive Security.
Deep security expertise for the systems that run your business.
Why we only work on IBM i?
Most banks, insurers, manufacturers, and distributors still run their most critical operations on IBM i, whether they call it that or still say AS/400 or iSeries. Yet most security firms treat it as an afterthought, running the same generic scans they'd run against anything else and calling it a day. We built iRadix around the opposite bet: that a platform this important deserves a team that actually knows it, down to the exit points and authority lists most testers never look at.
Financial and Regulatory Risk
IBM i usually runs the data and processes your organization is most heavily regulated on. A compromise or outage here becomes a board-level problem, not just an IT ticket. And that doesn't change if you move to a managed environment. The provider runs the infrastructure, but the risk still sits with you.
Four Disciplines. One Platform.
Security Assessment
A structured review of IBM i configuration, object authorities, exit points, and system values, measured against platform-specific hardening benchmarks, not generic checklists.
Compliance Audit
Evidence-based audits mapped to the frameworks that govern your industry, translated into the specific realities of authority lists, adopted authority, journaling, and IFS exposure.
Penetration Testing
Adversarial testing of IBM i attack paths, including exit programs, command line access, authority escalation, and network services, executed with production-safe methodology.
Threat Detection & Response
Exclusive to IBM i ServersContinuous, platform-native monitoring of authority use, exit point activity, and journal events on IBM i, with alerting and response built for the threats this platform actually faces, not generic SIEM rules ported from other systems.
A Disciplined, Repeatable Process
- 01
Discovery
Platform inventory, exposure mapping, and scope definition specific to your IBM i environment.
- 02
Configuration Review
Manual analysis of system values, authority structures, exit points, and network exposure.
- 03
Controlled Testing
Exploitation attempts performed with production-safe technique and constant client coordination.
- 04
Reporting
Findings delivered with technical evidence, business risk context, and prioritized remediation guidance.
- 05
Remediation Support
Direct guidance through hardening and retesting until every exposure is closed.
Why IBM i Demands Specialists
IBM i has run mission-critical workloads for decades, and its security model differs fundamentally from Windows, Linux, and cloud-native systems.
Object-level authorities, exit points, and journaling require platform-specific expertise that general penetration testers rarely hold.
A single misconfigured authority list or open exit point can expose decades of financial, healthcare, or operational data.
Discuss Your IBM i Environment
Every engagement begins with a confidential conversation about your environment, scope, and objectives.