Great content! Question for you: if the backup allows data to be anonymized for regulatory purposes (GDPR requests), is it still considered 'immutable'? If yes, why?
Great question, Kylie! That's a good one. Anonymization is allowed to modify the data for that very specific purpose so it's not immutable at that point. After all processing has been done by the backup system and it is considered final, then the backup can be considered immutable by the software and stored. I hope this answers your question.
If malicious dormant code is in the immutable backup. What happens when a need for system restore triggers the malicious code back at on-prem. How does someone know they are not backing up infected data to WORM storage?
Superb Sir. Thank you so much.
Thank you very much..super clear
Great content! Question for you: if the backup allows data to be anonymized for regulatory purposes (GDPR requests), is it still considered 'immutable'? If yes, why?
Great question, Kylie! That's a good one. Anonymization is allowed to modify the data for that very specific purpose so it's not immutable at that point. After all processing has been done by the backup system and it is considered final, then the backup can be considered immutable by the software and stored. I hope this answers your question.
If malicious dormant code is in the immutable backup. What happens when a need for system restore triggers the malicious code back at on-prem. How does someone know they are not backing up infected data to WORM storage?