Let's see now work with the emphasis on looks and practice.
Let's take a look at the properties of our hard disk work with bit locker results and the fact that
the TPM module needs to be initiated and then we can turn on bit locker in order to do so.
We must not only have the right version but also have the correct edition of Windows the Enterprise
Edition allows encryption.
While the professional does not since we're starting this process for the first time we need to protect
the key with an additional password as we've already mentioned.
This means that there will be two copies of the key for the password to be safe.
It has to be generated for us.
We can also save it to a file and move it from the disk to a safer place.
We can also print it or put it on a USP flash drive the whole procedure after the initiation of the
TPM module was almost ready.
Clicking two more times would have started the encryption of disks see.
Let's see now if the TPM module is initialized more operations may be related to the TPM module
as can be seen we can configure operations supported by a given TPM module in our case the TPM module
has already been initialized meaning it's been turned on and protected by a password.
You can only turn off reset or clear the password.
The TPM module that is prepared in this way is sufficient for the correct operation of bit Lucker.
From now we encrypt the system disk or additional disks.
However working with the EFA system is a bit more complicated.
On the disk let's create a text file and save some text in it.
Encryption results in the setting of a certain NTFS object attribute file or folder
open the object's advanced attributes where we can compress or encrypt the file
when encrypting a file will have the opportunity to see a warning telling us that folders rather than
files should be encrypted.
Folder encryption means encrypting all the files in that folder.
In that case why should we encrypt folders that files.
Because having an encrypted folder newly created files in that folder will also be encrypted many programs
including programs in office create temporary copies of files with which we're working if the folder
is unencrypted and we work with an encrypted file the created copies will not be encrypted.
It should be deleted when we finish work.
But that does not always happen.
We however encrypt the file or self what had happened.
We can see the files encrypted but its name is marked in a green font.
We also had the opportunity to see that Windows cares for us since the computer issued us a certificate
and yes a file.
It now reminds us to copy and store it in a safe place such as on a flash drive kept in a safe place.
If something happens to our profile we will still have problems with access to this file.
Let's take a look now at the first attribute of this file.
In fact we're the only person that has access to the thicky copy.
There is no one else.
There is no recovery agent.
We do not belong to a domain so there is no administrator who would care for these things.
We also see that everyone has authorization to this file.
It seems so all users have full control.
We'll see what happens.
Now if someone tries to read the file switched now to the account of another user try to open the txt
file you created earlier.
We have privileges to this file but we cannot see its content
we can delete it.
The encryption protects the confidentiality of data and nothing more.
We have mentioned this several times.
If something is encrypted it does not mean that it cannot be changed or deleted.
In this module we discussed technologies that allow protecting all data stored on hard disks.
We focused on the encryption of entire disks and in particular the encryption using bit locker technology.
We also talked of how ESF technology complements bit locker technology.
I hope that the information in this module will help you ensure confidentiality of data even if the
data carrier falls into the wrong hands.
Thank you.