Biltocker: Wodurch Eingabe Widerherstellungschlüssel erforderlich - Einbrucfh
Moin,
vor drei Wochen konnte ich feststellen, dass jmd versucht hat mein mit Bitlocker und TPM gesichertes System zu starten.
Ich fahre den PC abends runter und muss morgens die PIN für das TPM eingeben. Nachts ist der PC also aus. Der PC steht in einem Raum der verschlossen ist und nur 5 Mitarbeiter einen Schlüssel haben.
Gestern musste ich feststellen, dass wieder einer an meinem PC rumgefingert hat. Diesmal erschien bei PC-Start aber gleich die Abfrage des Wiederherstellungsschlüssels.
Jetzt ist meine Frage, welches Handeln löst dieses Ereignis aus. Was muss man tun bzw. versuchen damit die Meldung kommt?
Ich habe die Geschäftsleitung informiert und wir werden Strafanzeige stellen. Google konnte mir aber nicht sagen, was diese Mld ausslöst.
Weiß jmd was?
VG von der Küste Kev
vor drei Wochen konnte ich feststellen, dass jmd versucht hat mein mit Bitlocker und TPM gesichertes System zu starten.
Ich fahre den PC abends runter und muss morgens die PIN für das TPM eingeben. Nachts ist der PC also aus. Der PC steht in einem Raum der verschlossen ist und nur 5 Mitarbeiter einen Schlüssel haben.
Gestern musste ich feststellen, dass wieder einer an meinem PC rumgefingert hat. Diesmal erschien bei PC-Start aber gleich die Abfrage des Wiederherstellungsschlüssels.
Jetzt ist meine Frage, welches Handeln löst dieses Ereignis aus. Was muss man tun bzw. versuchen damit die Meldung kommt?
Ich habe die Geschäftsleitung informiert und wir werden Strafanzeige stellen. Google konnte mir aber nicht sagen, was diese Mld ausslöst.
Weiß jmd was?
VG von der Küste Kev
Bitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 357402
Url: https://administrator.de/forum/biltocker-wodurch-eingabe-widerherstellungschluessel-erforderlich-einbrucfh-357402.html
Ausgedruckt am: 23.12.2024 um 02:12 Uhr
7 Kommentare
Neuester Kommentar
Hi.
Das ist alles bei MS dokumentiert. Die gekürzte Fassung: Der Recoverykey wird abgefragt, wenn
-man die Bootoptionen ändert (SecureBoot aus, anderes primäres Bootgerät)
-man die Firmware des Rechners aktualisiert
-man einen bestimmten Schutzmechanismus per Kennwortfalscheingabe im laufenden aber gesperrten Windows auslöst (den müsstest Du jedoch selbst aktiviert haben und wüsstest davon, zudem war der Rechner auch aus)
Das ist alles bei MS dokumentiert. Die gekürzte Fassung: Der Recoverykey wird abgefragt, wenn
-man die Bootoptionen ändert (SecureBoot aus, anderes primäres Bootgerät)
-man die Firmware des Rechners aktualisiert
-man einen bestimmten Schutzmechanismus per Kennwortfalscheingabe im laufenden aber gesperrten Windows auslöst (den müsstest Du jedoch selbst aktiviert haben und wüsstest davon, zudem war der Rechner auch aus)
Hier steht alles dazu
What causes BitLocker to start into recovery mode when attempting to start the operating system drive?
Issues Resulting in Bitlocker Recovery Mode and Their Resolution
What causes BitLocker to start into recovery mode when attempting to start the operating system drive?
Issues Resulting in Bitlocker Recovery Mode and Their Resolution
What causes BitLocker to start into recovery mode when attempting to start the operating system drive?
The following list provides examples of specific events that will cause BitLocker to enter recovery mode when attempting to start the operating system drive:
Changing any boot configuration data (BCD) boot entry data type settings with the exception of the following items:
DESCRIPTION
RAMDISKIMAGEOFFSET
PASSCOUNT
TESTMIX
FAILURECOUNT
TESTTOFAIL
WarningWarning
When installing a language pack, an additional option in the language pack installation wizard asks if the user wants to apply language settings to All users and system accounts. If this option is selected, it will change the local computer BCD settings (if the user-only option is selected, BCD settings are not changed). This change will result in a modification of a BCD setting to the new locale value. If you are using a TPM with BitLocker, this is interpreted as a boot attack on reboot and the computer will require that the user enter the recovery password or recovery key to start the computer.
We recommend that you suspend BitLocker before changing locales or installing a language pack, just as you would before making any major computer configuration change, such as updating the BIOS.
Changing the BIOS boot order to boot another drive in advance of the hard drive.
Having the CD or DVD drive before the hard drive in the BIOS boot order and then inserting or removing a CD or DVD.
Failing to boot from a network drive before booting from the hard drive.
Docking or undocking a portable computer. In some instances (depending on the computer manufacturer and the BIOS), the docking condition of the portable computer is part of the system measurement and must be consistent to validate the system status and unlock BitLocker. This means that if a portable computer is connected to its docking station when BitLocker is turned on, then it might also need to be connected to the docking station when it is unlocked. Conversely, if a portable computer is not connected to its docking station when BitLocker is turned on, then it might need to be disconnected from the docking station when it is unlocked.
Changes to the NTFS partition table on the disk including creating, deleting, or resizing a primary partition.
Entering the personal identification number (PIN) incorrectly too many times so that the anti-hammering logic of the TPM is activated. Anti-hammering logic is software or hardware methods that increase the difficulty and cost of a brute force attack on a PIN by not accepting PIN entries until after a certain amount of time has passed.
Turning off the BIOS support for reading the USB device in the pre-boot environment if you are using USB-based keys instead of a TPM.
Turning off, disabling, deactivating, or clearing the TPM.
Upgrading critical early startup components, such as a BIOS upgrade, causing the BIOS measurements to change.
Forgetting the PIN when PIN authentication has been enabled.
Updating option ROM firmware.
Upgrading TPM firmware.
Adding or removing hardware. For example, inserting a new card in the computer, including some PCMIA wireless cards.
Removing, inserting, or completely depleting the charge on a smart battery on a portable computer.
Changes to the master boot record on the disk.
Changes to the boot manager on the disk.
Hiding the TPM from the operating system. Some BIOS settings can be used to prevent the enumeration of the TPM to the operating system. When implemented, this option can make the TPM hidden from the operating system. When the TPM is hidden, BIOS secure startup is disabled, and the TPM does not respond to commands from any software.
Using a different keyboard that does not correctly enter the PIN or whose keyboard map does not match the keyboard map assumed by the pre-boot environment. This can prevent the entry of enhanced PINs.
Modifying the Platform Configuration Registers (PCRs) used by the TPM validation profile. For example, including PCR[1] would result in most changes to BIOS settings, causing BitLocker to enter recovery mode.
noteNote
Some computers have BIOS settings that skip measurements to certain PCRs, such as PCR[2]. Changing this setting in the BIOS would cause BitLocker to enter recovery mode because the PCR measurement will be different.
Moving the BitLocker-protected drive into a new computer.
Upgrading the motherboard to a new one with a new TPM.
Losing the USB flash drive containing the startup key when startup key authentication has been enabled.
Failing the TPM self test.
Having a BIOS or an option ROM component that is not compliant with the relevant Trusted Computing Group standards for a client computer. For example, a non-compliant implementation may record volatile data (such as time) in the TPM measurements, causing different measurements on each startup and causing BitLocker to start in recovery mode.
Changing the usage authorization for the storage root key of the TPM to a non-zero value.
noteNote
The BitLocker TPM initialization process sets the usage authorization value to zero, so another user or process must explicitly have changed this value.
Disabling the code integrity check or enabling test signing on Windows Boot Manager (Bootmgr).
Pressing the F8 or F10 key during the boot process.
Adding or removing add-in cards (such as video or network cards), or upgrading firmware on add-in cards.
Using a BIOS hot key during the boot process to change the boot order to something other than the hard drive.
Can I swap hard disks on the same computer if BitLocker is enabled on the operating system drive?
Yes, you can swap multiple hard disks on the same computer if BitLocker is enabled, but only if the hard disks were BitLocker-protected on the same computer. The BitLocker keys are unique to the TPM and operating system drive, so if you want to prepare a backup operating system or data drive for use in case of disk failure, you need to make sure that they were matched with the correct TPM. You can also configure different hard drives for different operating systems and then enable BitLocker on each one with different authentication methods (such as one with TPM-only and one with TPM+PIN) without any conflicts.
Can I access my BitLocker-protected drive if I insert the hard disk into a different computer?
Yes, if the drive is a data drive, you can unlock it from the BitLocker Drive Encryption Control Panel item just as you would any other data drive by using a password or smart card. If the data drive was configured for automatic unlock only, you will have to unlock it by using the recovery key. If it is an operating system drive mounted on another computer running Windows 7, the encrypted hard disk can be unlocked by a data recovery agent if one was configured or it can be unlocked by using the recovery key.