Security issues
Hi,
I am using Windows 7(64bit) + True Image 2016 and find security issues on it, as follows:
1. If I create a backup profile(password protected) with a Windows account, then another Windows account will be able to open the profile and see all the settings, including the backup comments. I think that is not secure since the creator should be the only account that can access the backup profile.
2. After the backup profile is created with password, there are no way to change the password, even the original creator cannot do so. That is very strange and not convenient.
Thanks
Hi,
That's really strange. I try to update my ATIH 2016 to the latest version(6571) but I still be able to access the backup settings without any passwords. I can see the "lock" icon to indicate the backup is encrypted.
Thanks
1. If I create a backup profile(password protected) with a Windows account, then another Windows account will be able to open the profile and see all the settings, including the backup comments. I think that is not secure since the creator should be the only account that can access the backup profile.
As for the backup profiles... Acronis only runs with administrative access... hence the UAC prompt when launched. If other users have admin access to your machine they can do just about anything they want to it anway, like deleting the Acronis files/folders, opening data in other user profiles (after taking ownership or changing the security permissions on the users profile,etc.) If we're talking about security, then this is the biggest vulnerability of your entire system. If you are the only administrator, then you have nothing to worry about in Acronis or anything else on your system as only the administrators can launch Acronis and make changes.
The backup password is created via the Acronis application and has nothing to do with Windows accounts - whatever you enter at this point in time is what wiill be used to unlock the backup when you need to do so later on. Once you create the password, anyone who knows the password (hopefully just yourself) will be able to unlock the backup when prompted for credentials through the application, the bootable recovery media, when double clicking the .tib or when right clicking the .tib and mounting it. Once you unlock the backup in Acronis it will remain unlocked until you close the app. Once you unlock the backup by double clicking or mounting the .tib in Windows file explorer, it will remain stored in Windows Credential mangaer for a period of time in that windows session, I'm not sure how long though, but eventually it will close out, or it will close out if you log off or reboot. If you want to speed up the process, go to control panel >>> credential manager >>>> windows credentials... then look for generic credentials. Expand them until you find the one associated with Acronis and remove it. YOu should then be prompted for credentials if you double click the .tib again or try to mount it.
2. After the backup profile is created with password, there are no way to change the password, even the original creator cannot do so. That is very strange and not convenient.
That is correct. The password is tied to that backup and is stored in the backup. As the backup is READ only (static), you cannot modify the contents within it, to include the password that was originally set on it. You can, however, change the password on your backup task and from that point in time, that password would be needed to unlock subsequent backups, but the originally created files would still need the original password. It is not terribly inconvenient, perhaps not ideal for what you want to do, but since the backups are READ only once created and the password information is stored within them, this is why it works this way.
Hi, Bobbo_3C0X1,
Thank you for your detailed explanation.
1. For password protection, originally I think it will protect both the backup settings as well as the backup files. For backup settings, some data may be confidentical such as the backup comments. It is not good to let other Administrator accounts to be able to see the comments.
2. You said " You can, however, change the password on your backup task and from that point in time". How to do so?
Thanks
1. Yeah, unfortunately, like in Windows, an admin is an admin so if they have that access, there isn't much you can do. If you are admin on your system and so I am I, there's nothing you can do to prevent me from getting access to the data in your profile either (well, there is, liek encrypting folders wiht a password, but if I have that password, game on). User profiles are not secure at all to administrators as any adminisrator can take ownership of them and/or modify the permissions to gain access. This is worth submitting feedback on though, so I would encourage you to do so using the feedback option in the application.
2. Dang, I could have sworn you could change it if you edited options, but you're right, you can't. The only suggestion I can offer, would be to copy the existing backup task (use the dropdown at the end and "clone settings" to create an exact copy of the task, set the new password and start the backup again. Not the same though, I know.
Hi, Bobbo,
For 2, I try to clone the backup settings, but find I cannot change the password for the cloned settings as well. How to solve?
Thank you very much
Nope, you're right again. Doesn't look possible. I am not sure why it would force the same password cloning the settings either and will be submitting feedback about that. I can see it copying the password since it is a clone of the settings, but I would think it would still give you the option to set the password to something else if preferred before the backup is run. Please submit feedback about this as well.
Thinking about this, if a clone of the settings then allowed full access to the original settings in the cloned task, then having a password that protected those settings could be bypassed by this method. Having it this way, that the clone must be given the original password, protects those original settings which to me was one of the intentions of the OP who wanted to ensure that even the backup comments were secure.