ehud.amiri | October 9th, 2019
One of the main obstacles to delivering security at scale is confidence. When we send new configurations to production, are we confident they will run without errors or performance issues? When we enable new capabilities in our environment, are we sure these new capabilities were enabled correctly and will be acceptable by our various user communities? As the cybersecurity landscape evolves, how do we deliver the trusted experiences our users and customers will love? The answer for all of these is that we can promote changes to our production with confidence only after we conducted the appropriate acceptance and system testing.
To achieve this, developers require lower environments where they can test changes before going to production. For a while, OneLogin has offered customers a simple, developer-oriented sandbox environment. At Connect19 in San Francisco, we announced the additional availability of enterprise sandbox environments. These environments will enable administrators to fully or partially clone production data and safely test changes in an isolated environment before promoting these changes to production.
So, what is Sandbox?
If you’re reading this—chances are—you’re already familiar with the concept of a sandbox. A sandbox is a clean environment where developers and testers can collaborate in building and testing their code before it goes to production. The OneLogin Sandbox is ideal for testing new integrations, functionality, new product capabilities, performance, and snapshot backups of production data.
How does it work?
Sandbox is designed with DevOps principles in mind. By providing developers a blank environment, they are able to design, build, test, and release without affecting the production environment. As deployments become more complex, testing new configurations for hundreds of apps and thousands of users becomes a challenge. How do you experiment and build the confidence necessary to promote new deployments to production?
To start, you can’t just test using synthetic data. To avoid surprises in production and test under semi-production conditions, the Enterprise Sandbox enables your team to clone production-level data for testing within the secure confines of a separate, semi-production environment. Which is great, because mistakes happen. And when they do, it’s reassuring to know you can roll back bad deployments without adversely affecting production environments. This provides stability, confidence, and precision in deployments.
Why are we announcing this now?
As companies come to see identity as the nucleus of their organization’s infrastructure, there’s a growing need to support a comprehensive identity strategy that includes a continuous delivery model. With more apps, users, and customers, businesses must be able to deploy new configurations not only at scale, but also with confidence. If your identity platform goes down, so too, does the ability to login and remain productive. Sandbox addresses that concern by empowering developers to properly test using real-life data and, in turn, deploy with certainty.
Testing in a sandbox environment is about safety. It allows customers to clone data and test in an environment that remains separate from live production data. By testing with data that’s reflective of real life, we hope customers can deliver mission critical infrastructure with peace of mind.
If you’d like to learn more about sandbox, please contact your OneLogin account manager.