Does the destruction of sensitive information limit the choice of hard drives to non-flash based devices?












1














Working with a non-profit organization,it's common to reuse hard drives that have previously stored highly sensitive information such as medical and financial records. This is primarily driven by cost-saving measures to reduce purchasing new hard drives.



If the destruction of sensitive information is the first requirement, does this limit the choice in selecting the type of storage medium?



For example, do non-flash based devices provide a higher level of assurance in the destruction of data using ATA Secure Erase and a single wipe in comparison to SSDs including self-encrypting drives?










share|improve this question
























  • SATA is just a standard for communication and interfaces. SATA drives can either be spinning rust hard disks or solid state drives. Also the ATA command set is not unique to SATA. It also works with SAS (a similar standard more common in enterprise environments).
    – forest
    1 hour ago












  • @forest - That is correct. I have updated the question.
    – Motivated
    1 hour ago
















1














Working with a non-profit organization,it's common to reuse hard drives that have previously stored highly sensitive information such as medical and financial records. This is primarily driven by cost-saving measures to reduce purchasing new hard drives.



If the destruction of sensitive information is the first requirement, does this limit the choice in selecting the type of storage medium?



For example, do non-flash based devices provide a higher level of assurance in the destruction of data using ATA Secure Erase and a single wipe in comparison to SSDs including self-encrypting drives?










share|improve this question
























  • SATA is just a standard for communication and interfaces. SATA drives can either be spinning rust hard disks or solid state drives. Also the ATA command set is not unique to SATA. It also works with SAS (a similar standard more common in enterprise environments).
    – forest
    1 hour ago












  • @forest - That is correct. I have updated the question.
    – Motivated
    1 hour ago














1












1








1


1





Working with a non-profit organization,it's common to reuse hard drives that have previously stored highly sensitive information such as medical and financial records. This is primarily driven by cost-saving measures to reduce purchasing new hard drives.



If the destruction of sensitive information is the first requirement, does this limit the choice in selecting the type of storage medium?



For example, do non-flash based devices provide a higher level of assurance in the destruction of data using ATA Secure Erase and a single wipe in comparison to SSDs including self-encrypting drives?










share|improve this question















Working with a non-profit organization,it's common to reuse hard drives that have previously stored highly sensitive information such as medical and financial records. This is primarily driven by cost-saving measures to reduce purchasing new hard drives.



If the destruction of sensitive information is the first requirement, does this limit the choice in selecting the type of storage medium?



For example, do non-flash based devices provide a higher level of assurance in the destruction of data using ATA Secure Erase and a single wipe in comparison to SSDs including self-encrypting drives?







storage deletion sensitive-data-exposure ssd sata






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 59 mins ago







Motivated

















asked 1 hour ago









MotivatedMotivated

351110




351110












  • SATA is just a standard for communication and interfaces. SATA drives can either be spinning rust hard disks or solid state drives. Also the ATA command set is not unique to SATA. It also works with SAS (a similar standard more common in enterprise environments).
    – forest
    1 hour ago












  • @forest - That is correct. I have updated the question.
    – Motivated
    1 hour ago


















  • SATA is just a standard for communication and interfaces. SATA drives can either be spinning rust hard disks or solid state drives. Also the ATA command set is not unique to SATA. It also works with SAS (a similar standard more common in enterprise environments).
    – forest
    1 hour ago












  • @forest - That is correct. I have updated the question.
    – Motivated
    1 hour ago
















SATA is just a standard for communication and interfaces. SATA drives can either be spinning rust hard disks or solid state drives. Also the ATA command set is not unique to SATA. It also works with SAS (a similar standard more common in enterprise environments).
– forest
1 hour ago






SATA is just a standard for communication and interfaces. SATA drives can either be spinning rust hard disks or solid state drives. Also the ATA command set is not unique to SATA. It also works with SAS (a similar standard more common in enterprise environments).
– forest
1 hour ago














@forest - That is correct. I have updated the question.
– Motivated
1 hour ago




@forest - That is correct. I have updated the question.
– Motivated
1 hour ago










2 Answers
2






active

oldest

votes


















3














Placing a dependency on the type of media is not the right way to approach the problem, because the technology is always evolving and changing, and you can never be in 100% control of all IT spend. Remember that disks were never designed for security first - they are designed for the opposite: reliable access. (Some disk makers like to maximize profits by selling their products as “security solutions”, but that still doesn’t make them the best choice for the job.)



For example, Shadow IT (aka the boss’s kid) is good at buying consumer equipment like SSDs, and installing it in the department desktops without asking permission. Or a non-profit might have to accept a generous donation of a hundred drives from some corporate sponsor (for political or marketing reasons), but that don’t support Secure Erase. Decent corporate laptops don’t even offer spinny disks as an option anymore, while wear-leveling algorithms ensure that SSDs always risk leaking some data in the slack spaces of the drive.



Instead, look to something that is designed to solve this exact security problem, and is something that you can control enterprise-wide, such as installing encrypted file systems that can be wiped as quickly as deleting the key. For example, in a Windows shop enforcing BitLocker via Group Policy would protect all the drives, not just the special ones you ordered.






share|improve this answer





















  • It's not uncommon for donated devices to be provisioned with non-flash devices. If so and since wear leveling algorithms have a risk of data leakage, it seems that non-flash devices offer a higher level of assurance when employing secure destruction methods such as ATA secure erase and overwriting.
    – Motivated
    55 mins ago



















3














Data destruction is a technique of last resort. If you are planning to use a new storage device, you should use full disk encryption. This allows you to either destroy the encrypted master key or simply forget the password, effectively rendering all data unrecoverable, despite no data actually being wiped. Encryption is a solution for both solid state and standard hard drives. Use a strong algorithm like AES.



If you absolutely need to use a hard drive without full disk encryption, you should get one which supports SED, which is transparent hardware encryption. SED transparently encrypts all data written to the drive, but keeps the encryption key stored in a special area. When you initiate secure erasure, this key is all that is destroyed. This feature is supported on most modern SSDs and HDDs. If you do not know if a drive supports it, you can often conclude that it is supported if the estimated ATA Secure Erase time is showing as only two minutes, regardless of how large the drive itself is.



There is nothing intrinsic to the data storage methods used by solid state media that makes it hard to perform data destruction, but their firmware makes it impossible for the operating system to overwrite specific sectors due wear leveling, a feature that spreads writes around the drive to decrease the wear and tear on individual flash cells (each of which has a finite lifespan). This does mean that you cannot overwrite data on SSDs reliably. You can still use SED if the drive implements it, and you can use ATA Security Erase as well, but if you need to manually overwrite a range of sectors, use an HDD.



Note that, if you do use an SSD and are using full disk encryption and you have TRIM enabled, the drive will leak a limited amount of metadata, as explained in this excellent blog post. You can usually disable TRIM at a small performance penalty, but you will avoid metadata leakage. Whether or not the exact metadata leaked is problematic depends on your specific threat model.






share|improve this answer























  • How reliable is the implementation of SED in comparison to non-flash devices that have been encrypted when data destruction is employed?
    – Motivated
    1 hour ago










  • @Motivated SED is generally implemented pretty well, but as is usual with storage drive firmware, it could be broken. Software-based full disk encryption (like LUKS) with a strong password on an HDD may be better.
    – forest
    1 hour ago












  • Assuming that full disk encryption is reliably implemented using LUKS for example, will ATA secure erase and secure wipe e.g. dd if=/dev/urandom on a non-flash device provide a higher level of assurance when data destruction is a requirement?
    – Motivated
    1 hour ago










  • @Motivated Simply wiping the password (e.g. with cryptsetup erase /dev/sda1) should be just as effective, if not more effective, than overwriting-based erasure.
    – forest
    1 hour ago






  • 1




    Let us continue this discussion in chat.
    – Motivated
    1 hour ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "162"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f201257%2fdoes-the-destruction-of-sensitive-information-limit-the-choice-of-hard-drives-to%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














Placing a dependency on the type of media is not the right way to approach the problem, because the technology is always evolving and changing, and you can never be in 100% control of all IT spend. Remember that disks were never designed for security first - they are designed for the opposite: reliable access. (Some disk makers like to maximize profits by selling their products as “security solutions”, but that still doesn’t make them the best choice for the job.)



For example, Shadow IT (aka the boss’s kid) is good at buying consumer equipment like SSDs, and installing it in the department desktops without asking permission. Or a non-profit might have to accept a generous donation of a hundred drives from some corporate sponsor (for political or marketing reasons), but that don’t support Secure Erase. Decent corporate laptops don’t even offer spinny disks as an option anymore, while wear-leveling algorithms ensure that SSDs always risk leaking some data in the slack spaces of the drive.



Instead, look to something that is designed to solve this exact security problem, and is something that you can control enterprise-wide, such as installing encrypted file systems that can be wiped as quickly as deleting the key. For example, in a Windows shop enforcing BitLocker via Group Policy would protect all the drives, not just the special ones you ordered.






share|improve this answer





















  • It's not uncommon for donated devices to be provisioned with non-flash devices. If so and since wear leveling algorithms have a risk of data leakage, it seems that non-flash devices offer a higher level of assurance when employing secure destruction methods such as ATA secure erase and overwriting.
    – Motivated
    55 mins ago
















3














Placing a dependency on the type of media is not the right way to approach the problem, because the technology is always evolving and changing, and you can never be in 100% control of all IT spend. Remember that disks were never designed for security first - they are designed for the opposite: reliable access. (Some disk makers like to maximize profits by selling their products as “security solutions”, but that still doesn’t make them the best choice for the job.)



For example, Shadow IT (aka the boss’s kid) is good at buying consumer equipment like SSDs, and installing it in the department desktops without asking permission. Or a non-profit might have to accept a generous donation of a hundred drives from some corporate sponsor (for political or marketing reasons), but that don’t support Secure Erase. Decent corporate laptops don’t even offer spinny disks as an option anymore, while wear-leveling algorithms ensure that SSDs always risk leaking some data in the slack spaces of the drive.



Instead, look to something that is designed to solve this exact security problem, and is something that you can control enterprise-wide, such as installing encrypted file systems that can be wiped as quickly as deleting the key. For example, in a Windows shop enforcing BitLocker via Group Policy would protect all the drives, not just the special ones you ordered.






share|improve this answer





















  • It's not uncommon for donated devices to be provisioned with non-flash devices. If so and since wear leveling algorithms have a risk of data leakage, it seems that non-flash devices offer a higher level of assurance when employing secure destruction methods such as ATA secure erase and overwriting.
    – Motivated
    55 mins ago














3












3








3






Placing a dependency on the type of media is not the right way to approach the problem, because the technology is always evolving and changing, and you can never be in 100% control of all IT spend. Remember that disks were never designed for security first - they are designed for the opposite: reliable access. (Some disk makers like to maximize profits by selling their products as “security solutions”, but that still doesn’t make them the best choice for the job.)



For example, Shadow IT (aka the boss’s kid) is good at buying consumer equipment like SSDs, and installing it in the department desktops without asking permission. Or a non-profit might have to accept a generous donation of a hundred drives from some corporate sponsor (for political or marketing reasons), but that don’t support Secure Erase. Decent corporate laptops don’t even offer spinny disks as an option anymore, while wear-leveling algorithms ensure that SSDs always risk leaking some data in the slack spaces of the drive.



Instead, look to something that is designed to solve this exact security problem, and is something that you can control enterprise-wide, such as installing encrypted file systems that can be wiped as quickly as deleting the key. For example, in a Windows shop enforcing BitLocker via Group Policy would protect all the drives, not just the special ones you ordered.






share|improve this answer












Placing a dependency on the type of media is not the right way to approach the problem, because the technology is always evolving and changing, and you can never be in 100% control of all IT spend. Remember that disks were never designed for security first - they are designed for the opposite: reliable access. (Some disk makers like to maximize profits by selling their products as “security solutions”, but that still doesn’t make them the best choice for the job.)



For example, Shadow IT (aka the boss’s kid) is good at buying consumer equipment like SSDs, and installing it in the department desktops without asking permission. Or a non-profit might have to accept a generous donation of a hundred drives from some corporate sponsor (for political or marketing reasons), but that don’t support Secure Erase. Decent corporate laptops don’t even offer spinny disks as an option anymore, while wear-leveling algorithms ensure that SSDs always risk leaking some data in the slack spaces of the drive.



Instead, look to something that is designed to solve this exact security problem, and is something that you can control enterprise-wide, such as installing encrypted file systems that can be wiped as quickly as deleting the key. For example, in a Windows shop enforcing BitLocker via Group Policy would protect all the drives, not just the special ones you ordered.







share|improve this answer












share|improve this answer



share|improve this answer










answered 1 hour ago









John DetersJohn Deters

26.3k24087




26.3k24087












  • It's not uncommon for donated devices to be provisioned with non-flash devices. If so and since wear leveling algorithms have a risk of data leakage, it seems that non-flash devices offer a higher level of assurance when employing secure destruction methods such as ATA secure erase and overwriting.
    – Motivated
    55 mins ago


















  • It's not uncommon for donated devices to be provisioned with non-flash devices. If so and since wear leveling algorithms have a risk of data leakage, it seems that non-flash devices offer a higher level of assurance when employing secure destruction methods such as ATA secure erase and overwriting.
    – Motivated
    55 mins ago
















It's not uncommon for donated devices to be provisioned with non-flash devices. If so and since wear leveling algorithms have a risk of data leakage, it seems that non-flash devices offer a higher level of assurance when employing secure destruction methods such as ATA secure erase and overwriting.
– Motivated
55 mins ago




It's not uncommon for donated devices to be provisioned with non-flash devices. If so and since wear leveling algorithms have a risk of data leakage, it seems that non-flash devices offer a higher level of assurance when employing secure destruction methods such as ATA secure erase and overwriting.
– Motivated
55 mins ago













3














Data destruction is a technique of last resort. If you are planning to use a new storage device, you should use full disk encryption. This allows you to either destroy the encrypted master key or simply forget the password, effectively rendering all data unrecoverable, despite no data actually being wiped. Encryption is a solution for both solid state and standard hard drives. Use a strong algorithm like AES.



If you absolutely need to use a hard drive without full disk encryption, you should get one which supports SED, which is transparent hardware encryption. SED transparently encrypts all data written to the drive, but keeps the encryption key stored in a special area. When you initiate secure erasure, this key is all that is destroyed. This feature is supported on most modern SSDs and HDDs. If you do not know if a drive supports it, you can often conclude that it is supported if the estimated ATA Secure Erase time is showing as only two minutes, regardless of how large the drive itself is.



There is nothing intrinsic to the data storage methods used by solid state media that makes it hard to perform data destruction, but their firmware makes it impossible for the operating system to overwrite specific sectors due wear leveling, a feature that spreads writes around the drive to decrease the wear and tear on individual flash cells (each of which has a finite lifespan). This does mean that you cannot overwrite data on SSDs reliably. You can still use SED if the drive implements it, and you can use ATA Security Erase as well, but if you need to manually overwrite a range of sectors, use an HDD.



Note that, if you do use an SSD and are using full disk encryption and you have TRIM enabled, the drive will leak a limited amount of metadata, as explained in this excellent blog post. You can usually disable TRIM at a small performance penalty, but you will avoid metadata leakage. Whether or not the exact metadata leaked is problematic depends on your specific threat model.






share|improve this answer























  • How reliable is the implementation of SED in comparison to non-flash devices that have been encrypted when data destruction is employed?
    – Motivated
    1 hour ago










  • @Motivated SED is generally implemented pretty well, but as is usual with storage drive firmware, it could be broken. Software-based full disk encryption (like LUKS) with a strong password on an HDD may be better.
    – forest
    1 hour ago












  • Assuming that full disk encryption is reliably implemented using LUKS for example, will ATA secure erase and secure wipe e.g. dd if=/dev/urandom on a non-flash device provide a higher level of assurance when data destruction is a requirement?
    – Motivated
    1 hour ago










  • @Motivated Simply wiping the password (e.g. with cryptsetup erase /dev/sda1) should be just as effective, if not more effective, than overwriting-based erasure.
    – forest
    1 hour ago






  • 1




    Let us continue this discussion in chat.
    – Motivated
    1 hour ago
















3














Data destruction is a technique of last resort. If you are planning to use a new storage device, you should use full disk encryption. This allows you to either destroy the encrypted master key or simply forget the password, effectively rendering all data unrecoverable, despite no data actually being wiped. Encryption is a solution for both solid state and standard hard drives. Use a strong algorithm like AES.



If you absolutely need to use a hard drive without full disk encryption, you should get one which supports SED, which is transparent hardware encryption. SED transparently encrypts all data written to the drive, but keeps the encryption key stored in a special area. When you initiate secure erasure, this key is all that is destroyed. This feature is supported on most modern SSDs and HDDs. If you do not know if a drive supports it, you can often conclude that it is supported if the estimated ATA Secure Erase time is showing as only two minutes, regardless of how large the drive itself is.



There is nothing intrinsic to the data storage methods used by solid state media that makes it hard to perform data destruction, but their firmware makes it impossible for the operating system to overwrite specific sectors due wear leveling, a feature that spreads writes around the drive to decrease the wear and tear on individual flash cells (each of which has a finite lifespan). This does mean that you cannot overwrite data on SSDs reliably. You can still use SED if the drive implements it, and you can use ATA Security Erase as well, but if you need to manually overwrite a range of sectors, use an HDD.



Note that, if you do use an SSD and are using full disk encryption and you have TRIM enabled, the drive will leak a limited amount of metadata, as explained in this excellent blog post. You can usually disable TRIM at a small performance penalty, but you will avoid metadata leakage. Whether or not the exact metadata leaked is problematic depends on your specific threat model.






share|improve this answer























  • How reliable is the implementation of SED in comparison to non-flash devices that have been encrypted when data destruction is employed?
    – Motivated
    1 hour ago










  • @Motivated SED is generally implemented pretty well, but as is usual with storage drive firmware, it could be broken. Software-based full disk encryption (like LUKS) with a strong password on an HDD may be better.
    – forest
    1 hour ago












  • Assuming that full disk encryption is reliably implemented using LUKS for example, will ATA secure erase and secure wipe e.g. dd if=/dev/urandom on a non-flash device provide a higher level of assurance when data destruction is a requirement?
    – Motivated
    1 hour ago










  • @Motivated Simply wiping the password (e.g. with cryptsetup erase /dev/sda1) should be just as effective, if not more effective, than overwriting-based erasure.
    – forest
    1 hour ago






  • 1




    Let us continue this discussion in chat.
    – Motivated
    1 hour ago














3












3








3






Data destruction is a technique of last resort. If you are planning to use a new storage device, you should use full disk encryption. This allows you to either destroy the encrypted master key or simply forget the password, effectively rendering all data unrecoverable, despite no data actually being wiped. Encryption is a solution for both solid state and standard hard drives. Use a strong algorithm like AES.



If you absolutely need to use a hard drive without full disk encryption, you should get one which supports SED, which is transparent hardware encryption. SED transparently encrypts all data written to the drive, but keeps the encryption key stored in a special area. When you initiate secure erasure, this key is all that is destroyed. This feature is supported on most modern SSDs and HDDs. If you do not know if a drive supports it, you can often conclude that it is supported if the estimated ATA Secure Erase time is showing as only two minutes, regardless of how large the drive itself is.



There is nothing intrinsic to the data storage methods used by solid state media that makes it hard to perform data destruction, but their firmware makes it impossible for the operating system to overwrite specific sectors due wear leveling, a feature that spreads writes around the drive to decrease the wear and tear on individual flash cells (each of which has a finite lifespan). This does mean that you cannot overwrite data on SSDs reliably. You can still use SED if the drive implements it, and you can use ATA Security Erase as well, but if you need to manually overwrite a range of sectors, use an HDD.



Note that, if you do use an SSD and are using full disk encryption and you have TRIM enabled, the drive will leak a limited amount of metadata, as explained in this excellent blog post. You can usually disable TRIM at a small performance penalty, but you will avoid metadata leakage. Whether or not the exact metadata leaked is problematic depends on your specific threat model.






share|improve this answer














Data destruction is a technique of last resort. If you are planning to use a new storage device, you should use full disk encryption. This allows you to either destroy the encrypted master key or simply forget the password, effectively rendering all data unrecoverable, despite no data actually being wiped. Encryption is a solution for both solid state and standard hard drives. Use a strong algorithm like AES.



If you absolutely need to use a hard drive without full disk encryption, you should get one which supports SED, which is transparent hardware encryption. SED transparently encrypts all data written to the drive, but keeps the encryption key stored in a special area. When you initiate secure erasure, this key is all that is destroyed. This feature is supported on most modern SSDs and HDDs. If you do not know if a drive supports it, you can often conclude that it is supported if the estimated ATA Secure Erase time is showing as only two minutes, regardless of how large the drive itself is.



There is nothing intrinsic to the data storage methods used by solid state media that makes it hard to perform data destruction, but their firmware makes it impossible for the operating system to overwrite specific sectors due wear leveling, a feature that spreads writes around the drive to decrease the wear and tear on individual flash cells (each of which has a finite lifespan). This does mean that you cannot overwrite data on SSDs reliably. You can still use SED if the drive implements it, and you can use ATA Security Erase as well, but if you need to manually overwrite a range of sectors, use an HDD.



Note that, if you do use an SSD and are using full disk encryption and you have TRIM enabled, the drive will leak a limited amount of metadata, as explained in this excellent blog post. You can usually disable TRIM at a small performance penalty, but you will avoid metadata leakage. Whether or not the exact metadata leaked is problematic depends on your specific threat model.







share|improve this answer














share|improve this answer



share|improve this answer








edited 33 mins ago

























answered 1 hour ago









forestforest

33.8k16109115




33.8k16109115












  • How reliable is the implementation of SED in comparison to non-flash devices that have been encrypted when data destruction is employed?
    – Motivated
    1 hour ago










  • @Motivated SED is generally implemented pretty well, but as is usual with storage drive firmware, it could be broken. Software-based full disk encryption (like LUKS) with a strong password on an HDD may be better.
    – forest
    1 hour ago












  • Assuming that full disk encryption is reliably implemented using LUKS for example, will ATA secure erase and secure wipe e.g. dd if=/dev/urandom on a non-flash device provide a higher level of assurance when data destruction is a requirement?
    – Motivated
    1 hour ago










  • @Motivated Simply wiping the password (e.g. with cryptsetup erase /dev/sda1) should be just as effective, if not more effective, than overwriting-based erasure.
    – forest
    1 hour ago






  • 1




    Let us continue this discussion in chat.
    – Motivated
    1 hour ago


















  • How reliable is the implementation of SED in comparison to non-flash devices that have been encrypted when data destruction is employed?
    – Motivated
    1 hour ago










  • @Motivated SED is generally implemented pretty well, but as is usual with storage drive firmware, it could be broken. Software-based full disk encryption (like LUKS) with a strong password on an HDD may be better.
    – forest
    1 hour ago












  • Assuming that full disk encryption is reliably implemented using LUKS for example, will ATA secure erase and secure wipe e.g. dd if=/dev/urandom on a non-flash device provide a higher level of assurance when data destruction is a requirement?
    – Motivated
    1 hour ago










  • @Motivated Simply wiping the password (e.g. with cryptsetup erase /dev/sda1) should be just as effective, if not more effective, than overwriting-based erasure.
    – forest
    1 hour ago






  • 1




    Let us continue this discussion in chat.
    – Motivated
    1 hour ago
















How reliable is the implementation of SED in comparison to non-flash devices that have been encrypted when data destruction is employed?
– Motivated
1 hour ago




How reliable is the implementation of SED in comparison to non-flash devices that have been encrypted when data destruction is employed?
– Motivated
1 hour ago












@Motivated SED is generally implemented pretty well, but as is usual with storage drive firmware, it could be broken. Software-based full disk encryption (like LUKS) with a strong password on an HDD may be better.
– forest
1 hour ago






@Motivated SED is generally implemented pretty well, but as is usual with storage drive firmware, it could be broken. Software-based full disk encryption (like LUKS) with a strong password on an HDD may be better.
– forest
1 hour ago














Assuming that full disk encryption is reliably implemented using LUKS for example, will ATA secure erase and secure wipe e.g. dd if=/dev/urandom on a non-flash device provide a higher level of assurance when data destruction is a requirement?
– Motivated
1 hour ago




Assuming that full disk encryption is reliably implemented using LUKS for example, will ATA secure erase and secure wipe e.g. dd if=/dev/urandom on a non-flash device provide a higher level of assurance when data destruction is a requirement?
– Motivated
1 hour ago












@Motivated Simply wiping the password (e.g. with cryptsetup erase /dev/sda1) should be just as effective, if not more effective, than overwriting-based erasure.
– forest
1 hour ago




@Motivated Simply wiping the password (e.g. with cryptsetup erase /dev/sda1) should be just as effective, if not more effective, than overwriting-based erasure.
– forest
1 hour ago




1




1




Let us continue this discussion in chat.
– Motivated
1 hour ago




Let us continue this discussion in chat.
– Motivated
1 hour ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Information Security Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f201257%2fdoes-the-destruction-of-sensitive-information-limit-the-choice-of-hard-drives-to%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Ronny Ackermann

Köttigit

MySQL 8.0.15 starts normally but any connection hangs