---
title: "Identity Security & Recovery | SHIFT 2026 On-Demand"
type: "WebPage"
language: "en-US"
url: "https://www.commvault.com/resources/video/identity-lift-and-shift"
date: "2026-11-16T16:27:26-05:00"
modified: "2026-11-16T16:27:26-05:00"
description: "Discover strategies to protect identities, strengthen identity security, and improve recovery readiness against cyber threats. Watch SHIFT 2026 on demand."
image: "https://www.commvault.com/wp-content/uploads/2026/11/Identity-Lift-and-Shift-Building-Identity-Resilience-Across-Hybrid-Environments.png"
breadcrumbs:
  - name: "Commvault Home"
    url: "https://www.commvault.com/"
  - name: "Resources"
    url: "https://www.commvault.com/resources"
  - name: "Video"
    url: "https://www.commvault.com/resources/video"
  - name: "Identity lift and shift"
---

# The Recovery Advantage • SHIFT 2026 On-Demand

- [Home](/)
- Videos
- The Recovery Advantage • SHIFT 2026 On-Demand

ON-DEMAND SESSION

## Identity Lift and Shift: Building Identity Resilience Across Hybrid Environments

Learn how AmeriGas and UGI approach hybrid identity resilience as environments expand across directories, cloud platforms, machine identities, and AI workloads.

[Request a demo](/request-demo)

Play Video      ![Video thumbnail](https://img.youtube.com/vi/cHvEk7bqNI8/maxresdefault.jpg)

---

- [Key Takeaways](#Takeaways)
- [About This Session](#About)
- [Related Resources](#Resources)
- [FAQs](#FAQs)

[Back to all on-demand sessions](/shift#watch-now)

---

## Key Takeaways

**Map Dependencies**

Document recovery order before identity disruptions occur.

**Test Identity Recovery**

Validate interdependent recovery through tabletop and sandbox exercises.

**Protect Identity Data**

Use immutable backups across hybrid identity environments.

**Monitor Continuously**

Capture evidence and track changes across identity systems.

**Share Responsibility**

Coordinate access, infrastructure, security, cloud, and application teams.

**Educate Constantly**

Keep teams aligned as technology and dependencies evolve.

---

## About This Session

#### **Identity is the New Perimeter**

Identity is the new perimeter, and hybrid environments make it increasingly complex to protect and recover. Multiple identity providers, cloud platforms, machine identities, and AI workloads create dependencies that can turn a contained identity issue into broad operational disruption.

#### **Follow the Identity Journey**

The conversation follows AmeriGas and UGI Corporation as they move from siloed business-unit directories toward shared services. Eric Frost explains how Active Directory, Entra ID, AWS, Azure, and emerging AI workloads depend on one another across the organization.

#### **A Routine Change Can Disrupt Everything**

A routine cleanup accidentally deleted an essential Active Directory group, triggering hundreds of calls and application failures. The team recovered quickly, then used the event to strengthen testing, evidence capture, dependency mapping, and cross-functional recovery practices.

#### **Build a Resilience Framework**

The session closes with five practical actions: assume identity systems can be compromised, protect them with immutable backups, monitor continuously, test recovery regularly, and document operational evidence. It also emphasizes shared responsibility and continuous education as identity environments evolve.

#### **Map Dependencies Before a Crisis**

A current dependency map helps teams understand recovery order, reduce uncertainty, and adapt as new systems, workloads, machine identities, and AI agents are introduced.

#### **Test And Learn Continuously**

Treat mistakes like attacks and test identity recovery like any other critical service. Tabletop exercises, sandbox exercises, and regular validation help teams recover interdependent identity services with confidence.

CONTINUOUS IDENTITY RECOVERY

## IDRecover

Assess risk, detect threats, and recover trusted identity.

[Explore solution](/solutions/id-recover)

CONTINUOUS CORE RECOVERY

## CoreRecover

Unified, validated infrastructure recovery.

[Explore solution](/solutions/core-recover)

---

## Related Resources

WHITEPAPER

## Build Identity Resilience

Learn how to protect, detect, and recover identity infrastructure.

[Read whitepaper about Build Identity Resilience](https://www.commvault.com/resources/whitepaper/how-do-you-build-identity-resilience)

SOLUTION BRIEF

## Protect Active Directory

Explore visibility, control, and recovery for identity systems.

[Read solution brief about Protect Active Directory](https://www.commvault.com/resources/solution-brief/help-protect-and-recover-the-keys-to-your-enterprise)

DATASHEET

## Identity Resilience for Okta

Protect Okta objects, view changes, and restore services.

[View datasheet about Identity Resilience for Okta](https://www.commvault.com/resources/datasheet/commvault-cloud-identity-resilience-for-okta)

---

## Frequently Asked Questions

What makes identity attacks difficult to see?

Identity attacks can resemble ordinary employee activity because attackers log in with valid credentials. A single login, group lookup, password reset, or account creation may not look dangerous alone; correlating events across identity platforms reveals the attack sequence.

How can an ordinary user lead to privilege?

An ordinary user can inherit indirect privilege through nested group relationships. In the scenario, Alex belongs to a group nested into another group that can reset service-account passwords, including an account in Domain Admins.

Why correlate identity events across platforms?

Organizations often represent one person across Okta, Entra ID, and Active Directory. A unified timeline connects otherwise routine events across those systems, helping teams identify privilege escalation and understand the full scope of an attack.

What does attack surface intelligence reveal?

Attack surface intelligence identifies objects with administrative control and the relationships that can provide that control. It can also show when a change expands the attack surface, helping teams prioritize risky changes for remediation.

When is full identity recovery needed?

Full recovery is needed when an attacker has persisted or made changes that containment does not undo. Restoring the identity system to a point before compromise helps validate and reestablish trust in the environment.

---

## Transcript

View full transcript

Welcome to Identity Lift and Shift. How do you build identity resilience in hybrid environments?

My name is Michael Thelander with Commvault. But my real guest here today to talk about this topic is Mr. Eric Frost, Director of Infrastructure for UGI Corporation and AmeriGas. Eric, how are you doing today? I’m doing really, really well, thank you very much. Eric AmeriGas is a large corporation.

It’s an organization that has, I think, thousands of outlets, millions of customers. Tell me a little bit about the organization and your specific role in it.

Yugi energy Services and Mountaineer gas. So we have a very varied, number of business units and all work together. And over the last several years, we’ve been kind of coming together, with an initiative called what, your gi. So we’re starting to standardize and integrate as much as we can across the business units to use similar technologies for efficiency.

That’s a great lead in to what we’re going to talk about today, because the notion of one Yugi and integrating your identity systems is, is is is, an initiative that many, many organizations are grappling with, with.

Whenever we look at an identity discussion, we tend to always use this phrase. Identity is the new perimeter. Identity has sort of always been a critical facet of our of our cyber security structures.

But it is, a very different animal than it used to be in the past. We’re now seeing really 90% of organizations of any size experiencing identity related attacks and exploits or breaches in the last 12 months. We know that hybrid growth, which I think is something that we can talk about with AmeriGas, has really challenged organizations. 75% of organizations use two or more identity providers, or IDPs

As they start pulling together different partners, different customers, different environments, they’re, they’re working with, it adds a lot of complexity to their overall identity landscape. And then obviously, just the increase of the sheer number of identities. We’re not just talking about people, obviously, we’re talking about the explosion in machine identities and of course, the genetic identities across that entire state.

So, Eric, for you looking at AmeriGas and what you do, when you look at your environment, especially over the last few years, as your needs have evolved, as the company grows, how is your identity strategy actually change and evolved over that same time?

Quite a bit. I mean, our debt landscape is basically a record of every major change the company has been through over the last several years.

Historically, our business units each ran their own technology, their own silos, which included identity management. We had separate directories, different admin team, separate ways of doing things. Many, many forest domains.

But as part of that, reorganization of one PGI, we started coming together. We’ve been through a really big structural change. We’re moving towards a shared service model with one infrastructure team now supporting five business units. It’s much more, effective. But it also means that the identity now is a shared dependency. It’s not only shared between teams, but between companies as well.

So one, UGI is not just a slogan for for AmeriGas and UGI. It is literally a guiding principle, not just for the organization itself, but your technology. How you pull all those pieces together is what it sounds like.

Absolutely. We’ve added, the cloud inter ID, multiple clouds. So now not only do you have Add, but you’ve inter add which sits on top of add AWS Azure. Each have their own identity planes. And now we’re seeing gen AI workloads leaner AWS which we have another area to look at. And they all depend on each other.

So it’s getting more complex every day.

You’ve pointed out something that, many, many, many of our customers are dealing with going through, trying to navigate. And that’s really as you move from sort of active Directory infrastructure as your primary IDP, that’s your primary provider for identities, and you start adding things like Entrer ID, some of our customers are adding on to Okta into their environment.

So they’re dealing with really heterogeneous identity environments, and it creates a whole different set of challenges. Identity used to be, I think really singular, dealing with just the IT organization. But now this added complexity increases risk and increases exposure. Certainly vulnerabilities. We may have situations where especially where we’re rolling up organizations through acquisition, where we’ve got siloed tools and blind spots, and that can be identity vulnerabilities that we’re dealing with or configurations or even just sort of lack of consistent policies for things like recovery and then as we get to that, recovery is complex and it’s highly manual and it’s highly risky.

Can you walk us through like, and I assume that all of these things are, are true as well for AmeriGas and UGI as they are for every company. But can you walk us through a time when you might have had an identity issue that was contained, but had a much broader operational impact that sort of spills over some of those environmental boundaries?

Absolutely. So fairly recently we had, one of our people on our identity management team, and they were doing some cleanup. We always do this. Unfortunately, the naming of the clean up of one of the what was supposed to be a distribution group was unintentionally named appropriately. So they put a ticket in with through change management.

Supposed to be a simple change giver distribution group. They hit. Click next. And immediately following that, within minutes, we started getting hundreds and hundreds and hundreds and hundreds of calls that people couldn’t get into their system. So they ended up, deleting one of the most essential, groups in Active Directory. And immediately became what we refer to as AP1 call, a party, one call that there is a business impact that’s affecting many people.

We all jumped on the call. We looked at, many different things. Thankfully, we have a really great team and everyone is transparent with each other. And the individual did say, look, I made a change about ten minutes ago. This is what it was. Here’s the change ticket. We looked into it. We realized really quickly that yes, what he did, in fact, did delete all these, administrative accounts and access accounts.

And within few seconds, applications started failing. Then the hard part came is we know what it is. We know, we know. Don’t we? Have to fix. How do we fix it? Well, we were very, very fortunate, that we had a recovery tool. And we were able to recover that very, very rapidly.

So once we knew what it was, we hit recover, once it was recovered. The hard part was knowing which groups the permissions had had been removed. We had restored them in the right order, and they confirmed that the cloud side had synced up.

That is sort of a classic bad day for identity systems and not due to malfeasance, not due to, you know, in outside forces or a cyberattack or anything like that. It’s just the complexity, the sort of brittleness of modern identity systems and that that begs sort of the question about resilience. Like what?

What did you going through an experience like that or other experiences like that? What does that teach you? What does how does that inform you? How does that prepare you to think about recovery and resilience?

It changed our whole, our whole mindset. So for years, you think you’ve done things the right way, but you’re never really sure how things are going to work out until you’re tested. So that’s something that we’re now looking at a little more aggressively now, is testing more often to ensure that when something does go bump at night, when something either intentionally, unintentionally, or malicious happens, we have a way to recover and we know what the steps are and we confident that it can be done quickly.

Effectively, and be able to work at the business in a way that they understand the expectations only from us, but of our users and how long it it’ll be before they are recovering from an impact.

Now and that highlight something that we talk about consistently in the talks that we do, in events that we do, talking about the need for evidence, the need to capture that evidence and actually recorded. So I see how you’re kind of like evolving along with the overall industry. That is resilience and what that means. I’d like to talk a little bit more of like, once you’ve decided I need to establish sort of a resilience framework, a, culture of resilience, how do you measure resilience?

Like what are the what does a resilient identity strategy need to do for AmeriGas? What does it need to accomplish for you?

It’s a huge moving target because the the landscape is evolving so rapidly. So our first choice was to find a partner we could work with that had technology that evolved at a similar pace. We chose cobalt on many years ago initially, and we continue to partner partner with them as we go forward.

Every time there’s a new way of doing something complex seems to be pretty close to the edge of where that change or this technology is going.

And we’ve been very, very fortunate that we’ve had a great team to work with. And it’s been bidirectional. We tell them sort of what our needs are. They work very well with us to make sure that we have tools or processes in place, and then vice versa. Occasionally we’re on the bleeding edge. So we find something that maybe hasn’t quite adopted yet.

They take what we say and probably other customers with similar requirements. And then very quickly they turn it around and add feature and functionality into the tools.

This this path that we go on from assessing what an identity environment like, what are the potential misconfigurations and vulnerabilities to building of protection strategy, including immutable and aggregate backups, making sure that we do continuous monitoring and detection of the state of those environments. as a company with end users and customers, especially in the utility space?

What are your you’re sort of always on expectations for those identity systems.

Again, different business units have different, sort of SLAs. So, I’ll talk specifically about our utility business, our utility business as well. Utility. If our customers are not getting natural gas to their homes, they are not they are not warm. And in the winter, that’s very impactful, if not even life threatening. So we want to make sure that all of our, users, as well as all our customers, can interface with each other.

And we have many, many systems that integrate from all sorts of ways. We have pipeline systems that tell us historically where all the gas lines are that we’ve ever put in the ground. Going back almost a hundred years. In addition to that, we have maps and routes to tell our drivers and our repair teams where to go.

How to get there, because, again, natural gas and propane, there are some restrictions of what road you can take, how you get from point A to point B. So a lot of these systems are very, very important to help our people get to help our customers.

And to sort of add additional complexity to it, you have those demands as a utility. But also you are dealing with a multi IDP sort of hybrid environment that you’re dealing with as well. And to what extent are you seeing the need to start practicing some of those failures and like working through some of those sort of recovery scenarios in your organization.

It’s happening a lot more often now because as we start adding more, more technology, that makes the job easier for our users.

It adds some complexity on the back end, because as you automate and make things a little more effective and efficient, you take some of the manual controls out of there and we take some of the controls out of there.

The people that run and operate it and recover it don’t always know how and how to do it and what the steps are. So we’re doing a lot more, tabletop exercises as well as sandbox exercises to test that out. If this one feature or this one functionality was to break. What is the repercussions like? You know, the business needs to operate even when it entity doesn’t.

So we have to make sure that we have identity as bulletproof as possible, because that is sort of the foundational technology across everything.

We see that, from many of our customers, but I think it’s increasingly, it’s more crucial for those that are sort of on the frontline providing utility services. I put it in the same sort of priority as like providing health care services or providing public services like police and fire. I think that notion of like, not only being always on and there, but always testing those systems, always testing the resilience of those systems when we think about readiness, this is sort of a question for you that now shifts over to the organizational point of view.

Everybody there’s five actions that we always recommend, you know, to strengthen their their identity systems or that that makes that heterogeneous identity environment assume those identity systems can be compromised. That’s really talking taking about zero trust strategies that we’ve really adopted as an industry over the last ten years. I think that we’ve been talking about zero trust strategies, making sure that we have the right protection in place.

We’ve had immutable identity backups in place and really across multiple environments, not just for Adi, but also for track ID in octave. That tends to be a a component or an IDP that’s used in the organization. Continuously monitoring the identity infrastructure. We just talked about the notion, the need to have regular testing using operational evidence, as I said, to like track that evidence so that we can make a history of how we’ve kind of improved our own resilience and put those brought those systems back on line and put them together.

But apart from these sort of tactical steps, what are the organizational things that you feel you really need to do to like make the organization understand really the criticality and importance of those identity systems and really take what you’re talking about with one UI and translate it from a technical implementation team to here’s how we’re going to deliver value, and how do you sort of foster those relationships internally to make that happen?

Well, we we’re pretty lucky that, we have a number of teams. And then over the years, as we’ve been moving towards the one year, you guys bottle the the walls and the boundaries between teams are starting to get a little more permeable.

So historically, I didn’t have access. Management was a team, systems was a team. Networking was a team, potentially firewall was team, security, which historically a lot of organizations wasn’t really fully blown out.

Is now a team. So now we’re starting to put together, organizational groups that have people from all the different teams together. So as we look at, recovery, as we look at innovation, as we look at testing, we bring multiple people in from multiple teams to look at it from multiple angles. So we don’t look at it anymore as, hey, something fails, a team recovers that know when something fails.

We look at it from all angles, and we make sure that there’s not a security aspect.

And that’s an important part of like when we talk about resource strategies at, at at Commvault, talking about the ability for these sort of disparate functions to actually work together under one sort of consistent framework.

And we list steps like these, like these five steps. And I would encourage anybody looking at this online to like take a snapshot, decide how you’re going to structure, like what are the actions that you can take.

But if we look at these, where is a good place to start?

Eric. And if you’d like, if you’ve been able to tell Eric from three or 4 or 5 years ago, what is what are the thing that I should start on of these, which would you kind of focus on first?

I think right now, the thing in hindsight, in hindsight, always 2020 is that we really need to map out your application dependencies to know what processes break when a given directory or group or synchronization fails.

You know, your map kind of tells your recovery order. If you don’t know where to go, what to do when X breaks.

It makes it very challenging. And of course, when something’s down, the adrenaline’s up. Anxiety’s up. Leadership is highly involved. But not always in a helpful way. So having a map or having an organizational structure of saying this is how my world is, is defined today. And again, that definition changes very aggressively and very rapidly in the world because we’re adding all sorts of stuff, especially with AI workloads.

But having that’s a good foundational, if you can go back to what, you know, it’s very easy to build on that small piece of foundational knowledge. The other thing is that we’re treating mistakes, as if they were, you know, an attack. Even though, like, that event that happened to us was unintentional, was absolutely innocent. We looked at that is, if this was a malicious attack.

How would we have done this differently?

Use the same energy and process to like. Yeah. To test that. Yeah.

Learn our lessons, whether it’s self-inflicted or they are actually something that was, malicious.

The other thing is that we’re going to start testing identity recovery like we test everything else.

Historically, we tested our recovery. Okay. A server goes down, it’s backed up, a database goes down, it’s backed up, it’s recovered. You know, now we’re treating identity very much like we treated applications in the past. It’s not just a simple bringing a server back on line. You’re good to go. We have to make sure that all the interdependencies at all the different levels are now recovered in an appropriate way.

And I think that goes back to your point to of, of all of these things mapping those dependencies. And that’s not a one and done especially with an evolving, maturing organization like AmeriGas. It’s not like you just map those dependencies and you’re done. You’re constantly adding new systems, new workloads, new machine identities, things that put stress on that identity environment.

Right. You have to look at it as a continuous project.

Yeah. Those non-human identities now are multiply very rapidly. And what was named users that now are these AI agents, and these AI agents and workloads are just growing as the business finds opportunity to leverage this. We continue to, so, like every organization, we’re looking at efficiency. If we can use AI to make our business more efficient, allow our human, employees people to function and focus more on our customers, on the business, on service, and take some of the day to day operational things that usually took up time for our employees and move that to AI.

It benefits the business because it gives us the ability to be more strategic on how we put our workforce, to work on the on the challenges of the business.

But and then you have sort of the same challenges, those, genetic identities that are being created. And then of course, tracking those, making sure that those are also traceable. And that to go back to your question or your point, I’m sorry, on mapping dependencies, I think it’s it’s a bad time when systems go down or there’s a crisis to discover that there’s a dependency within the a genetic system or autonomous system that’s brought online.

Definitely. Yeah. We’ve had all sorts of the the challenges. It’s just very disruptive. And we have to continue to be proactive in the mapping of our dependencies. You know, right now, identity is a shared responsibility. What was formerly like the Disney Access management team. Is it the admin access management? It’s infrastructure security. It’s even the application owners and even our cloud teams, that that are implementing some of these new technologies.

We have to make sure everyone’s on the same page. And which historically was, again, siloed, workloads. Now it’s not it’s very much becoming, a joint effort across many, many, not only teams but now across multiple business units.

Of one one last question before I get to where we wrap this up and that that triggers for me something as, as, as you go from being this sort of standalone, hey, we’re the identity team, but everybody being having identity as a shared responsibility, to what extent have you also had to educate those adjacent teams on some of the dependencies and identities, some of the brittleness of those systems, identity systems, some of the sort of the interdependencies across those systems between different IDPs, different things that you’re using for authorization or authentication.

Does there is there an educational component that comes along with that shared identity responsibility?

Absolutely. Yeah. All the teams now are in in a constant education model. So it’s one of those things that we are they always say never stop being a student. We are students of technology. Technology is evolving at a very rapid pace. So we have to try to keep our people and our teams educated at a similar pace.

So we just can’t learn something, sit on our laurels for a period of time, and then

check back in in six months. It’s kind of a constant education. And every time something goes right or, and, you know, sometimes when something goes wrong, we learn more about our environment and how the interdependencies work. So not only is there educational technology, but there’s also organizational education that as we innovate or we integrate new applications and functions in our organization, that education is kind of permeating down to all the different teams.

That’s a great example. I like that story. And thank you, Eric, very much for kind of sharing with us a little bit of that journey. And we appreciate Commvault being along with AmeriGas to you on that, on that journey,

We have some, new research that’s come out that we’d like to share with everybody that, may be looking at this question of like, as we talk about the complexity of bringing back these somewhat brittle, very interdependent identity systems, how do I simplify it?

How do I accelerate that process? We actually have a new report that came out from Omdia. Conmebol did recover radically Simplifying and Accelerating Recovery and Active Directory. It is critical to understand like how we simplify a complex system like Active Directory that could have 100 or more 120 steps in its recovery process and take something from, you know, what could be days to do a restoration, to bring it down to hours or to minutes.

But it’s it does apply across sort of the universe, the whole ecosystem of identity. And I think it’s a good report to have. I want to share that with everybody.

Eric, I want to just thank you again for taking time with us, for walking us through a little bit of a Mary gases story. Thank you for being a vault customer.

I hope we can have some more of these conversations down the road as, as as you guys continue your identity journey as we start learning things more and more together about resilience and recovery. Thanks again for joining us.

It was my pleasure, Michael. And thank you. And for, being great partners. It’s been a relationship that’s been very beneficial for many years, and we continue to look forward to working with you.
