Securing Legacy Mainframes Against Modern Cyber Threats
Legacy mainframes still process critical workloads across Australian banks, government departments, insurers, airlines, retailers and resource companies. Their age does not make them irrelevant; it makes them valuable targets. A compromised system can expose payment records, identity data, operational information and decades of business logic that cannot be replaced overnight.
Protecting these environments requires a practical balance between modern security controls and operational reality. Organisations need to secure COBOL applications, z/OS infrastructure, batch jobs, terminals, APIs and connected cloud services without interrupting payroll, public services or financial transactions.
Map The Mainframe Attack Surface
Start with a complete asset and data-flow inventory. Document production and disaster recovery systems, logical partitions, databases, middleware, remote access paths, privileged accounts, third-party connections and file-transfer processes. Include the less visible links to cloud platforms, mobile applications, DevOps pipelines and modern web portals.
Many breaches begin outside the mainframe. An exposed API, stolen administrator credential or vulnerable integration server can provide a route into high-value records. A financial institution in Sydney or Melbourne may have decades-old core processing connected to real-time digital banking, while a mining business in the Pilbara may link operational technology and corporate systems across remote sites.
Use vulnerability assessment and penetration testing carefully. Testing should account for mainframe-specific protocols and business continuity requirements, with production-safe methods where intrusive scanning could affect availability. A specialist security team can also review configurations, access rights and integration points that conventional endpoint tools often miss.
Modernise Identity And Access Controls
Shared accounts, broad administrator privileges and permanent credentials create unnecessary exposure. Enforce unique identities, strong authentication and role-based access for operators, developers, vendors and service accounts. Privileged access management should provide time-limited elevation, approval workflows, session recording and rapid credential revocation.
Review RACF or equivalent security controls against actual job responsibilities. Remove dormant accounts, separate development from production access and restrict sensitive datasets by need rather than convenience. Service accounts should have documented owners, rotating secrets and clearly defined permissions.
Use a zero-trust approach around every connection, including internal traffic. Network segmentation, encrypted sessions and device verification can limit lateral movement if an external application or workstation is compromised. For organisations supporting mining security initiatives, this is especially important when contractors and remote operations need access to central systems.
Monitor Mainframe Activity Continuously
Traditional monitoring often misses suspicious activity because mainframe events may sit in separate logs from cloud, network and endpoint data. Forward authentication records, privileged commands, database queries, job submissions, configuration changes and data transfers into a central SIEM platform.
Security analysts should establish a baseline for normal batch schedules, administrator behaviour and transaction volumes. Alerts can then focus on unusual events, such as an operator accessing sensitive records outside rostered hours, a sudden export of customer data or a new connection from an unfamiliar network.
Around-the-clock monitoring matters for Australian organisations operating across several time zones. A Brisbane service desk, a Perth-based resources team and an overseas support provider may all interact with the same environment. Threat intelligence and incident response playbooks should identify who can isolate accounts, block connections and preserve evidence at any hour.
Apply Patches Without Breaking Operations
Mainframe patching is often delayed because systems support essential services and tightly coupled applications. Build a risk-based patch programme that ranks vulnerabilities by exploitability, exposure, data sensitivity and business impact. Test updates in a representative environment before deploying them through controlled change windows.
Where a vendor patch cannot be applied immediately, use compensating controls. These may include application-layer filtering, network isolation, stricter access rules, virtual patching, enhanced logging and temporary removal of unnecessary services. Document each exception with an owner and a deadline rather than allowing it to become permanent.
Legacy software should also be reviewed for unsupported components, weak encryption and outdated authentication methods. Modernising every application at once is rarely realistic, but targeted refactoring of high-risk interfaces can reduce exposure while preserving stable core processing.
Align Resilience With Australian Obligations
Security controls should support the organisation’s regulatory and operational responsibilities. Australian businesses may need to consider the Privacy Act, the Notifiable Data Breaches scheme, sector-specific rules and contractual requirements. APRA-regulated entities should map controls to CPS 234, while government suppliers may need to address the Essential Eight and relevant IRAP expectations.
Resilience planning must cover ransomware, insider misuse, destructive commands, supplier compromise and prolonged system unavailability. Maintain offline or immutable backups, test restoration procedures and define recovery priorities for databases, applications and communications. A recovery plan that exists only in a document will not be enough during a fast-moving incident.
Operational Controls Worth Prioritising
- Inventory every mainframe asset, interface, dataset and privileged account
- Enforce multi-factor authentication for administrators and remote users
- Segment production, development, backup and third-party connections
- Send mainframe logs and security events to a central SIEM
- Test backups and recovery procedures at scheduled intervals
Warning Signs That Need Immediate Review
- Dormant or shared accounts still enabled in production
- Unencrypted file transfers between the mainframe and external systems
- Unsupported operating system, database or middleware components
- Privileged commands performed outside approved change windows
- Large data exports that do not match normal business activity
A mature programme combines infrastructure audits, cloud and mobile security reviews, compliance support and managed detection. It should also measure progress through meaningful indicators such as privileged-account reduction, patch-age trends, alert investigation times and recovery-test results.
Mainframes can remain secure and dependable when treated as active components of the modern digital estate rather than isolated legacy assets. Infoziant Security helps organisations assess weaknesses, monitor critical environments and build tailored protection strategies with 24/7 security operations support. Request a free VAPT report or arrange a trial engagement to identify practical improvements before attackers find them.