Ransomware no longer announces itself with locked files and changed extensions. New variants destroy directory entries, keep entropy low and leave timestamps untouched, so a backup that looks clean can hold corrupted data. Security teams that cannot tell which copy is clean face a recovery measured in weeks, not hours.
In this interview on TFiR, Jim McGann, CMO at Index Engines, breaks down what the company’s ransomware lab found across more than 1,000 detonated strains and how teams can identify a clean recovery point before an attack.
Guest: Jim McGann, CMO at Index Engines
Show: The Agentic Enterprise
LinkedIn: Jim McGann
Watch the discussion on YouTube
Here is what every security team and backup administrator needs to know.
Technical Deep Dive
Q: How do you find a clean recovery point after a ransomware attack?
Jim McGann, CMO at Index Engines, says the answer is point-in-time analysis of data held in snapshots or backups, compared over time so teams can say with confidence that a copy is good. McGann notes that attackers now use byte-level replacement and corrupt pages inside Oracle or SAP databases, which can keep running while throwing errors that many teams mistake for database faults. Scanning snapshots and backups to separate clean from corrupted data is the focus of CyberSense.
“With these threat actors around now, you can’t assume that any data is good, not even data in a database.” Jim McGann, CMO, Index Engines
Q: Why does a ransomware-hit backup look clean when the data is corrupted?
Variants such as Encoder destroy data without changing file names, sizes, modification times, entropy or compression rate, so tools that watch those indicators of compromise see nothing unusual. McGann says attackers can also query which security tools, scanning tools and storage an environment runs, then choose variants that work against it. A data resiliency strategy built only on indicators, without inspecting the content of a file or database, can be circumvented.
“It doesn’t change the file name, file size, entropy, or compression rate of the file.” Jim McGann, CMO, Index Engines
Q: How does directory-entry destruction work, and does paying the ransom get data back?
Attackers want bulk corruption, because corrupting an entire directory makes access to its files very difficult. McGann says the technique comes from nation-state attacks, where the goal is destruction rather than ransom. Index Engines’ research found directory-entry destruction in 47.8% of the strains tested. Directory structures corrupted this way cannot be unlocked with decryption keys, so paying the ransom does not guarantee the data comes back.
“If they’re using these tools to corrupt directory structures and so on, those structures can’t simply be restored using decryption keys.” Jim McGann, CMO, Index Engines
Q: How fast does ransomware corrupt files, and what can a response team do?
The research cites a median of 97,000 files corrupted per hour, and McGann says hundreds of thousands of files can be hit within minutes. Tools can shut down or disconnect an affected server, but the work then becomes triage and post-attack forensics: where the clean copies are and what needs to be recovered. Attackers favor partial or intermittent encryption because it is harder to detect and much faster, and they use dwell time to target finance servers and production databases first.
“If they’re fast and target high-impact, business-critical data, any tools designed to shut them down may not be able to prevent the damage from already being done.” Jim McGann, CMO, Index Engines
Q: Why do signature-based tools fail against polymorphic ransomware?
Polymorphic ransomware regenerates its signatures between builds, changing names, extensions and encryption algorithms, so a signature or YARA rule never sees the same malware twice. McGann cites more than 60 percent polymorphic variants in the lab’s white paper. He says signature and YARA scanning still make sense at the point of recovery, when the ransomware in use is known and its executable can be removed, but they will not find everything else in the data.
” The signature they’re looking for is constantly changing. It’s a never-ending battle.” Jim McGann, CMO, Index Engines
Q: How are attackers using AI in ransomware attacks?
McGann says attackers use AI heavily, but mostly to break into the data center, find vulnerabilities and entry points, and automate and speed up attacks, rather than to build new ransomware variants. During dwell time, AI helps them find high-impact data such as sensitive content and legal contracts. The lab has not seen AI used to corrupt data, and variant behavior has not changed much beyond partial or intermittent encryption. McGann expects AI-enabled variants to arrive.
“We predict that, in the future, they’ll use AI quite aggressively, developing AI-enabled variants that will make detection even more difficult.” Jim McGann, CMO, Index Engines
Q: Do immutable backups protect against ransomware if the data was already corrupted?
Snapshots, backups and immutability are critical, but McGann warns that without analyzing the data, teams can lock down and make immutable bad copies. Recovery then reintroduces ransomware that can detonate again, along with corrupted data. His answer is continual data integrity through daily scanning, so immutability and isolation build on a copy that is already known to be good. Without it, finding the good copy can take weeks.
“The worst time to discover that data is corrupted, unusable, or otherwise compromised, whether it’s in SAP or a SQL database, is when you try to recover it and bring it back online.” Jim McGann, CMO, Index Engines
Q: How does a ransomware lab find and study new variants?
McGann says the lab downloads every available variant, thousands a day, uses AI to pick out the few hundred that are novel, and narrows those to a dozen or 20 to detonate and study. The process is automated and patented, and it reveals trends in attacker behavior. The lab finds that corruption approaches are stealthy, so changes in extension, file size, compression or entropy are no longer reliable indicators. Index Engines provides a 99.99% detection confidence SLA to its partners. AI also lowers the barrier for attackers to create variants.
“You could type a description of what you’re looking for into any engine and create a ransomware variant designed to corrupt data.” Jim McGann, CMO, Index Engines
Q: How does data integrity scanning separate ransomware damage from normal change?
The product scans files, databases and other critical data assets, tracks how they change over time, and applies AI to decide whether a change came from ransomware or from normal user behavior. McGann describes this as the last mile: dealing with the results of what threat actors do to data, rather than keeping them out. Backups and snapshots copy bad data if it is already corrupted, so the scan shows what is good and what is bad to assist recovery.
“If the data has already been corrupted, you’re simply copying bad or corrupted data.” Jim McGann, CMO, Index Engines
Q: What questions should you ask to know you have a clean copy of data?
McGann says teams should ask whether they are confident they have a clean copy of data for recovery, where it is once data is corrupted, and how long it takes to validate it and resume production. A backup team that makes backups every day is not answering that. Recovery should take hours or days, not weeks or months. McGann says CyberSense is deployed through partners including Dell, Hitachi, IBM, Lenovo and Infinidat, with the aim of making cyber recovery as routine as recovery from a fire or flood.
“We want to turn a cyber recovery process into a normal disaster recovery process.” Jim McGann, CMO, Index Engines
Resources & Documentation
- CyberSense, a data integrity scanning product that analyzes files, databases and other critical data assets for ransomware damage
***
👇 Click to Read Full Raw Transcript
Swapnil Bhartiya: There was a time when ransomware used to announce themselves. Files would get locked, extension changed, entropy spiked, and your backup was the clean copy that you trusted and you can always go back to it. But that’s not the case anymore. The new variants destroy data quickly, wiping directory entries, keeping entropy low, leaving timestamps untouched. So a backup that may look clean on surface may actually not be that clean. Now, if you look at Index Engines, their lab detonated over 1,000 ransomware strains in the first half of 2026 and found that directory-entry destruction in 47.8% of them and more than twice the share using full encryption. What does it mean? Today we have with us Jim McGann, Chief Marketing Officer at Index Engines. Hi, Sridhar. Index Engines to understand the modern or current state of ransomware. But before we talk about any of that, first of all, it’s great to have you on the show, Jim.
Jim McGann: Thank you. I appreciate the time.
Swapnil Bhartiya: It’s my pleasure. I would love to know a bit about the Index Engines so our audience, they do know the context, who we are talking to and why these insights matter.
Jim McGann: We are a software company and we are focused on indexing enterprise data, whether it be file data or databases, critical infrastructure, to understand how that data changes over time. And in the most recent iteration or product of our company, which is CyberSense, that change over time is focused on cybersecurity and ransomware and what ransomware does to the data. So as you know, there’s hundreds and hundreds of companies that are trying to keep bad actors out and trying to prevent bad bad things from happening. But we know that that is not as successful because we hear about ransomware attacks all the time. So what we are focused on is more the last mile or the results of what the threat actors are doing to data and manipulating data. So we built a scanning product that scans files, databases, and other critical data assets and understands how they change over time And we’ve applied AI to analyze those changes and determine, is it something that ransomware did to the data or is that normal user behavior? So our customers have deployed us to really understand the impact of ransomware, but also to understand what they need to do to recover from an attack. As you mentioned earlier in the intro, you know, organizations depend on backups or snapshots, which are copies of data. If the data’s already been corrupted, you’re just copying bad data or corrupted data. With our CyberSense product, you can understand what is bad and what is good and assist in the recovery process.
Swapnil Bhartiya: Now let’s talk about the shift that I briefly mentioned. The full encryption showed up only in 18.3% of the strains your lab detonated, if my numbers are correct, in the first half of 2026. How does that compare with what you saw in earlier rounds of this research and if this trend is something that you expected to happen or it’s worrisome?
Jim McGann: So when we first started out with our product, we read research, we read what was thought to be happening to the data, and we quickly realized that for us to be effective, we would have to really study the ransomware itself and study the detonate— and detonate ransomware and study the behavior. That, you know, if you’re entering, you know, for example, the World Cup game and you have an opponent, you’re going to study what they’re doing and how they act and how they play the game. We’re doing that exact type of activity with the threat actors, you know, the people that are actually executing these variants. So what we do is we’ve set up a lab where we actually download all the variants that are available on the market. It’s thousands a day. And then we analyze them using AI to determine which ones are the novel or the unique ones that have never been seen before. And that’s a few hundred. And then we narrow those down to a dozen or 20 variants that we actually detonate and study the behavior. And with that, that process, it’s an automated process that we actually have patented. We can see the trends in what’s happening. And as you mentioned, there’s some stats that we have in our white paper that talks about over 60-plus percent are polymorphic variants. So they’re changing completely. Yeah. and morphing into new variants. So if you’re trying to find them using signatures, that’s— you’re not going to win that battle because the signatures are constantly changing. But more importantly, we’re finding that the corruption approaches that they’re doing are very stealth. You know, if you’re looking for indicators of compromise like change in extension or change in file size or change in compression rates or entropy, those days are over. You know, they’re doing things that circumvent those kind of detection. And they’ve become far more sophisticated. And as you know, you know, with AI and the tools that are out there, it’s not difficult for them to create variants. You could type into any engine, describe what you’re looking for, and create a ransomware variant to corrupt data. So the game has changed, and we understand that. And by analyzing what they’re actually doing, we provide a level of confidence that CyberSense will detect that corruption with 99.99%. Confidence. It’s an SLA that we provide to our partners that are deploying our software.
Swapnil Bhartiya: I will talk about AI because that’s a big thing, but I will keep it for the very, very end. I also want to talk about some of these nuances. Like if you look at the directory-entry destruction was the most common behavior in your finding, like showing almost 47.8% of the strains. Can you walk us through what actually happens to a file when ransom destroys its directory entry?
Jim McGann: Well, you know, instead of, you know, the bad actors want to create as much chaos and as much difficulty in recovering and impact as much data as possible. So if you put yourself in their shoes, you know, what they wanna do is kind of have bulk corruption. So if you corrupt an entire directory of data, it makes access to those files very difficult. And the way that they’re doing that is there’s a number of different techniques that they’re using. Okay. But they want to make it difficult to really get access. And I think some of these tools are from, you know, nation-state attacks. If you think about a nation-state attack as the difference between that and a ransomware attack, nation-state attacks are not going to ask for a ransom. They just want to destroy things. So directory destruction came from that environment where they’re destroying data. But, you know, when customers think that The threat actors are gonna, if they pay the ransom, which a lot of them do, that they’re gonna get their data back. But if they’re using these tools to corrupt directory structures and so on, those can’t just be unlocked using decryption keys. So again, the game is changing, and I think they’re not using, we don’t see the threat actors using AI to actually manipulate or corrupt data. But we’re starting to see them using it in their reconnaissance, right? When they’re sitting in their dwell time and they’re looking around and saying, okay, what is the high-impact data that I can go and manipulate? AI is a perfect tool to find that, to find sensitive content or legal contracts, things that look like important documents. And then we’re also seeing a trend where they could use AI to manipulate the data in different ways. If it’s a database, use this kind of corruption. If it’s these kind of files, use this kind of corruption. And, you know, we’ve seen one of the stats that we have in the report is that we’re seeing the speed of the attack happening incredibly fast. So, you know, in minutes you’re going to have hundreds of thousands of files impacted. So before you even know something’s happening, you’re already going to be losing critical functionality. So there’s a lot of trends that we’re seeing, and I think it’s interesting for organizations to understand it because In order to fight these battles, they need to know the direction that these bad actors are heading. And that’s really the premise of why we release this research.
Swapnil Bhartiya: I don’t want to say this, but when I look at some of these bad actors, they’re like some of the smartest guys. They’re so innovative. They keep coming up with new ways. As Linus once says that, I wish these people were on our side. They’re very creative people, very innovative. Now, if you look at all those creativities, your lab also found variants built to look Preserving file extensions, faking timestamps, encrypting slowly, keeping entropy low. The Encoder variant is the clearest example here, destroying data while leaving files’ names, sizes, timestamps, entropy unchanged. When your team runs a surface scan over that data, what did it report and how easy and difficult is it to find things like Encoder?
Jim McGann: There’s 2 pieces, right? Finding the actual variant is the challenge that a lot of these security tools that are scanning using signatures or YARA rules are trying to find it and stop it. But, and we have capabilities that can do that as well. But once it executes, you know, it doesn’t change the file name, it doesn’t change the file size, it doesn’t change the entropy or the compression rate of the file. In fact, it doesn’t change the modification times and things like that. So a lot of storage vendors or folks in the infrastructure space, you know, the data protection vendors, have added these capabilities to say, tell me when, you know, the snapshot, the compression rate of the snapshot changes significantly. That means there’s probably a lot of encryption happening or change me, tell me when there’s a lot of file extensions that have changed more so than normal. So they kind of look for, you know, behavior that’s out of the norm, but very much as something like Encoder, which doesn’t change any of those properties, we’re giving you those signals or indicators of compromise, yet the file is unusable. Those are out there and those variants— Excuse me. Exist. And I think if you base your data resiliency strategy on just looking for some kind of indicators of compromise without expecting inside the content of a file or a database, they’re going to circumvent those tools. And we know, as you said, they’re very smart. So when they get into the data center, They can understand and query what security tools, what scanning tools are you using, what data protection tools are you using, what storage environment do you have. And they’re going to share that information and say, hey, these are the variants, this is what you should use against that environment because it works really well. So they, they map out their plan and they map out the environment and they know that they can just go under the covers. And I think the biggest challenge that we see from organizations is once they’ve been attacked, is to answer the questions is like, what was impacted? Where’s a clean copy of data? And how long will it take that clean copy to get recovered? And a lot of times most people say, I don’t know. So then the powers that be will say, let’s just, you know, file an insurance claim and pay the ransom and hope we can recover, you know, 40% of the data and see if we can just rebuild the business. That’s not a great resiliency strategy. And I think organizations suffer. I mean, I mean, you see healthcare organizations going back to paper and pencil. What’s the quality of patient care there? You know, and I think they have to be able to answer those questions, you know, how quickly they can recover. And it needs to be, you know, hours or days, not weeks or months, right?
Swapnil Bhartiya: When corruption is engineered to look like nothing happened, how does an organization decide which copy of its data is safe to restore from? Because I mean, it’s like finding the needle in a haystack.
Jim McGann: No. That’s, that’s the million-dollar question that organizations need to face. So, you know, now they’re using tools that do, say, byte-level replacement. So they’re corrupting individual bytes in a file, and the file at that point will not work. You know, when you corrupt the header of a file or individual bytes, the file will not operate as normal. But if you corrupt, you know, pages inside of an Oracle database or SAP database, That will still run. And those pages, if accessed, will give you error messages, which a lot of organizations think, oh, you know, it’s a problem with the database. I’ll, you know, use database cleaning tools to fix it later. But that’s ransomware. So I think, how do they know if the data has been cleaned or corrupted? You know, that’s really the focus of what we’re doing is scanning data, being part of the infrastructure, you know, either snapshots or backups. So you can have a point-in-time analysis of that data. Yeah. Compare it, how it changes over time, and say with confidence, this data is good. So I think an organization doesn’t have those tools in place. You know, they don’t really think about data integrity. They just assume it’s good. But, you know, with these threat actors now, you can’t assume the data is good, even a database, right?
Swapnil Bhartiya: Let’s talk about speed. Of course, AI is changing things when it comes to speed there. Your detonation showed A median of 97,000 files corrupted per hour. I mean, the rate is incredible with 10,000 files hit in about 6 minutes. I mean, which is faster than most things, incidents that you’ve seen. What can a response team actually do at that speed? Is there any tools at their disposal at all? All they have to do is just sit back and just watch the tsunami and then think of some damage control afterwards?
Jim McGann: Well, there’s tools that’ll, you know, if it’s detected that that’s happening on a server, they’ll shut the server down, right? So they’ll disconnect it. It’s the triage or the post-attack forensics, like, okay, it’s shut down now. What’s good and what, you know, ’cause they’re snapshotting or copying data on a regular basis. It’s like, where are the clean copies? What needs to be recovered here? So I think if you think of, you know, within an hour, you know, how much damage can be done and how much they can prevent. It’s a race against time, right? So, and then what they can recover. And I think some of the tools that we’re seeing in our research is that they’re using what we call partial or intermittent encryption, which is not fully encrypting a file. It’s just partially encrypting pieces of it, which is enough. And the reason they do that is, one, because it’s difficult to detect, but two, it’s incredibly faster. You know, you’re not encrypting the entire file. You’re just saying, just encrypt a little bit and move on to the next one. Yeah. So they’re focused on speed. They know that there’s, you know, tools out there that can stop them and, and just, you know, disconnect the network or disconnect the path, you know, where they go in lateral damage and lateral expansion throughout the environment. But the speed of what they could impact, and I think that’s where AI comes in, is like analyzing the environment. It’s like, you know, if I go and I wipe out, you know, the marketing servers, Will the business suffer? Not as much as if they wipe out the finance servers or wipe out the production databases. So they’re being smart in using their dwell time to do that reconnaissance and knowing that if they’re fast and if they hit the high-impact business-critical data, you know, any tools that are there to shut them down, the damage will have already been done, right?
Swapnil Bhartiya: Now let’s talk about AI. I mean, of course we keep hearing about AI and also that AI is not only speeding things up, it’s making attacks more sophisticated, but your lab found that none of the 1,064 strains used AI at the destructive payload stage, if I’m not wrong. The industry research you cite puts AI earlier in the attack lifecycle, compressing reconnaissance and lateral movement. But what does it actually mean in terms of how bad actors are using AI in the ransomware space?
Jim McGann: They’re using it pretty heavily, pretty aggressively. So they’re using it to really More so to break into the data center. I mean, you see with Anthropic and some of those tools that are, you know, they’re being used for good. I mean, you scan the environment and you find these vulnerabilities that are out there. I mean, the latest one, this PHP vulnerability that CISA just did an alert on saying that all these websites running old versions of PHP are going to be incredibly vulnerable. And they’re using that to find the the weak points or the vulnerabilities in an organization. And especially if it’s an organization that really shares access to their environment through open networks or through the internet or with vendors and partners. If you say, well, I need to patch all the websites with a new, say for example, updated PHP, how long is that going to take? So they’re using those tools to analyze the environment and find the entry points more aggressively so than building the ransomware variants. And the truth be told is the variants that they’ve been using, they are— they haven’t changed significantly except for some of these new intermittent or partial encryption algorithms and so on. But they haven’t changed significantly in terms of their behavior because it doesn’t really necessarily need to. And that’s the whole premise of our lab is to analyze them to see when those changes, because we use AI on our side as well. So, you know, AI for good is using and studying and teaching our product what the behavior looks like and how the behavior changes. And as they change that behavior, we put out a new release and updates of the software so that customers will benefit from that behavior change. But it’s not major in terms of— it’s been, you know, they become more sophisticated, but I think most of the AI usage on the bad actor side is really about how to break in and how to automate and be more aggressive in terms of their attack approach. And the encryption, I mean, we’ve seen there’s thousands and thousands of ransomware variants out there and they’re all very similar in terms of their behavior. So, but we predict though in the future they are gonna use AI pretty aggressively and to, I mean, the polymorphic stuff is interesting, but they’re gonna use AI in terms of AI-enabled variants that’ll be coming out, which will make it even more difficult to detect.
Swapnil Bhartiya: And if I’m not wrong, a lot of industry’s answers to ransomware has been immutable or get backup copies. I mean, as you also said, just unplug the server and that’s the best thing you can do, you know, shut everything down. But that will also disrupt business. What if the corruption happened before the backup was ever taken? What does immutability actually buy in an organization? And some of these— I’m sorry, Administrator— some of the approaches that we have for ransomware, predates AI and GenAI. So do we also need new approach to it?
Jim McGann: So, you know, snapshots or backups and copying the data, making it immutable, locking everything down is critical. But if you’re not analyzing the data, you could be saving and locking down and making immutable bad copies. The last time or the worst time to find out that data is not good and is corrupted and not usable, whether it be SAP or a SQL database, is when you try to recover it and run it. And it’s It’s that cycle that people see in the recovery process that when they recover, they’re not only recovering ransomware back into the network, so it’s going to detonate again. So they don’t know that those are bad files to recover, but they’re also recovering corrupted data. And that’s why they need to go through a process and create a clean room and test it to make sure it’s good. It’s a very long-term process. Our opinion is that data integrity needs to be a continual process through daily scanning and daily analysis of the data so that when You do have an attack, you don’t have to figure out where the good data is. You know where the good data is, and immutability and isolation only add to that. So for example, if you had a lot of terabytes or petabytes of critical data and you scan it and CyberSense says 99.99% confidence the state is good, that— and then you lock it down and make it immutable and make it isolated. You know you’ve got a copy in a vault somewhere or a snapshot somewhere that if something happens, you know where to go to recover. And that’s the confidence. Whereas if you don’t have that and you go to the isolated immutable copies, you’re like, now I have to figure out which one is the good copy. And that could take weeks to do that, right?
Swapnil Bhartiya: If I’m not wrong, 2/3 of the samples you analyzed were polymorphic, regenerating their file signatures between builds. So signature-based tools never see the same malware twice. How does detection keep up when the fingerprint keeps changing?
Jim McGann: That’s a good question. So signature scanning has been out there for a long time, and a lot of customers and users depend on it to find the ransomware, the malware. And the threat actors are now saying, well, I’ll just start implementing polymorphic ransomware that’s gonna continually change. So mild changes like the change of the name, change of the extension, change of the encryption algorithm, So that signature that they’re looking for is constantly changing. It’s a never-ending battle, right? So those are— I think the important point is a lot of these technologies are looking at the past behavior of what these bad actors are doing and building technology based on that, like signature scanning or YARA rules or so on. Whereas we’re looking into the future as where they’re heading and what they’re going to do in the future to be able to build technology that will detect that type of behavior. So I think, you know, signature scanning and YARA rule scanning and so on at the point of recovery makes sense because at that point you’ll know what ransomware is being used and you can find, make sure the executable is not in there, but you won’t find other stuff that’s in there too. So I think, again, it’s a sign that the, you know, the cyber criminals that are out there are ramping up their game, changing their behavior, becoming much smarter. They are smart, they’re well-funded, they’re making a lot of money, they can invest in this technology, and they’re doing exactly that.
Swapnil Bhartiya: Well, let’s try to give some solution to folks, those who are watching. If someone watching this takes one lesson from your research, or also they’re like, hey, of course there are a lot of vendors in this space, this is a crowded space, you know, so this is not a new problem, new solution, but at what time should they reach out to you folks? Because sometimes once the damage is done, it’s too late. And the way you folks work indexing, it happens before. So talk a bit about some practical steps they should take to protect themselves from ransomware attacks, and at what point should they contact you folks?
Jim McGann: I think organizations need to ask the difficult question is, are we confident that we have a clean copy of data for recovery? And if the answer is, oh, the backup team, you know, makes backups every day, and it’s like, okay, you’re not answering the right question. You know, you’re making a copy of data. Is it good? Is it not good? So I think asking, where do we have a clean copy of data when it— once it’s corrupted? Because it will be. And then how long can we validate that it’s clean and bring it into recovery and resume production? It’s those simple questions that I think are asked. And I think if you If you don’t have confident answers to those questions, I think we should talk because we are, we are doing data integrity validation on a regular basis. We’ve got thousands of customers globally through strategic partners like Dell, Hitachi, IBM, Lenovo, Infinidat, and others coming soon that are deploying this out there in production so that if, if and when the You know, the attack, you know, shows up on your doorstep, you know, I can recover, I have copy of data, it’s not the end of the world. So we want to turn a cyber recovery process into a normal disaster recovery process, saying, you know, like a fire and a flood, a cyberattack will be like, we’ve been attacked, we have to bring data back. And we know that where the clean data is and turn it into a normal recovery process. And that’s what we’re doing. And customers are being attacked and recovering using our technology in a much smarter and faster way at this point.
Swapnil Bhartiya: Jim, thank you so much for breaking it all down. And of course, those who are watching, please go and check indexengines.com to learn more about how you can keep yourself secure and protected from ransomware. And Jim, once again, thank you so much for your time, and I look forward to our next conversation. Thank you.
Jim McGann: Yeah, thank you very much. Appreciate it.





