@zer0unplanned @Nonya_Bidniss @n_dimension Mostly because deleting/overwriting the header first is extremely fast and twarts any unauthorized data recovery early on.

  • This is a real security concern in #finance, where #ITsec literally has to deal with "Red Army Faction"-style hodtage taking scenarios as part of regulator-mandated #OpSec.
    • Like "How can access of CxO's be revoked in K&R scenarios?" is a question @BaFin and others ask not just since #wirecard went "poof!"

Just because a business doesn't have a shitton of cash at hand and banks neither doesn't mean that armed robbers would necessarily understand, much less accept.

@zer0unplanned @Nonya_Bidniss @n_dimension Either way, comitting "#AssetDenial" is more often than not necessary and one may only have a few seconds before those exercising force may realize that a "duress code" was used and going for the #LUKS headers first may be the only feasible option in a short time...
How to Nuke your Encrypted Kali Installation | Kali Linux Blog

There’s been a fair amount of discussion around the recently introduced LUKS nuke patch we added to the cryptsetup package in Kali Linux. We wanted to take this opportunity to better explain this feature, as well as demonstrate some useful approaches which are worthwhile getting to know. LUKS Nuke in a Nutshell As explained well By Michael Lee in his ZDNet article, when creating an encrypted LUKS container, a master key is generated at random. A passphrase is then used to encrypt the master key in turn. This process means that the passphrase is not directly coupled to the data. That is, if two sets of identical data are encrypted and the same passphrase used, the master keys remain unique to each set and cannot be swapped out. What this also means however, is that regardless of the passphrase used, if the master key is lost, recovering data is impossible. This process conveniently lends itself to being used as a nuke by deliberately wiping the keys.

Kali Linux