NewEra Software Launches Stand Alone Environment 18
Press Release
Glennon Bagsby, CEO of NewEra Software, Inc., announced major enhancements to SAE. Now SAE18, The Stand Alone Environment version 18, is a z/OS system utility designed to support System Programmers in their ongoing work to enhance the integrity and security of an IBM Mainframe complex, including the newly announced z17.
SAE 18 operates stand alone, on bare metal, providing access to critical channel pathways that house system storage devices and configuration settings. Operated from the Hardware Management Console (HMC), SAE’s findings are shown via a bespoke interface that is, in every way, comparable to ISPF. For example, a key use case is when updates to Parmlib Libraries are necessary, allowing SAE users to benefit from a familiar working environment.
While SAE18 contains numerous enhancements, Bagsby stressed his focus on the need to provide access to storage devices on alternate sub-channel sets. Responding to customer requests, SAE18 now goes beyond Sub-Channel-Set 0 and “sees” all other sub-channels for in-depth analysis and corrective edit and erasure operations.
He offers the availability of Customer Briefings and technical support to prospects conducting a Proof-of-Concept (POC) by sending a request to support@newera.com.
What is SAE’s Role in a Cyber Vault Environment?
What this diagram is showing is that cyber recovery is no longer just about restoring data — it’s about restoring trust in the environment.
At the top, we have Precision Recovery. This is where we use tools like LCP to surgically restore specific datasets. It’s fast and efficient, but it assumes we know exactly what is corrupted and that the rest of the system can be trusted.
If that assumption breaks down, we move to Clean Room Recovery. This is the CyberVault or AirGapmodel, where we restore into a completely isolated environment. There is no shared DASD, no external access, and no dependency on production. Here, we validate that the data is clean before bringing anything back.
At the foundation, we have Stand Alone Environment, or SAE. This operates below the operating system. It allows us to access volumes and recover data even if z/OS cannot IPL or if core system datasets are compromised. This is our last line of defense.
The arrows represent a decrease in trust. As confidence in the environment drops, we move down the stack.
So, the key takeaway is simple: we’re not just restoring data — we’re restoring trust. And the real challenge is knowing which recovery path to take, at the right time.