No matter how well-structured your DevOps process is, direct production changes still happen. A critical hotfix, a minor sign-on URL change, or an urgent access request - these seemingly small changes can cause major disruptions. These are some of the key reasons that knowing exactly what changed and having the ability to instantly revert or restore when needed are so critical.

Salto’s Catch-it-all Change Log, which is a complete record of every configuration change in your tenant, allows you to restore to any previous version or granularly revert specific changes, without guesswork, manual tracking, or prolonged downtime.

Why it matters

Imagine this: An IAM admin updates an authentication policy rule in Okta, thinking it’s a minor tweak. Hours later, an entire department loses access to critical systems. The team scrambles for three hours to investigate, identify the issue, and manually revert the changes, resulting in lost productivity and business impact.

Automatically maintaining a complete change log, as well as version history, could have resolved this incident in minutes. Using Salto teams can restore configurations to a previous state or selectively revert specific changes. Okta teams are thus able to reduce MTTR and increase availability of the service.

How it works

Salto continuously tracks all changes, capturing modifications made through Salto deployments as well as direct changes in production via automated configuration fetches. The Change Log organizes these changes into:

• Deployments – Changes applied through Salto.
• Fetches – Direct production changes detected via scheduled syncs (hourly, daily, weekly).

From there, you can:

• Restore your environment to a previous version – Quickly recover from incidents by rolling back to a known good state.
• Granularly revert specific changes – Compare versions and select individual changes to undo without affecting the rest of your configuration.
• Maintain a real-time, always-up-to-date log – Ensure visibility and accountability over all configuration changes.

Easy, stress-free recovery

1. Restore your entire environment

If you need to recover from an unexpected error, you can restore your environment to a previous version in a few clicks:

• Open the Change Log tab.
• Select a previous version from the list of Fetches or Deployments.
• See the differences between that version and your current configuration and decide if you want to go ahead with a full restore. Click restore and Salto will instantly restore that state of your environment.

2. Granularly revert specific changes

If you don’t need a full rollback but just need to undo a particular change:

• Compare your current configuration with a previous version.
• Select specific changes to revert. Salto will automatically detect relevant dependencies you will need in the deployment, and suggest you select them as well.
• Deploy the changes back safely—without affecting anything else.

Be ready before you need it

Having an Okta ****configuration backup and restore solution isn’t a luxury, it’s a necessity. Don’t wait for a major incident to realize how critical it is. Request a demo and see how easy it is to track, restore, and revert changes, or try it yourself with Salto’s free trial.