Date: Fri, 29 Mar 2024 05:41:49 +0000 (UTC) Message-ID: <1744972906.8440.1711690909272@support.blancco.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8439_42642767.1711690909272" ------=_Part_8439_42642767.1711690909272 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Blancco Driver Eraser user can select= the level of verification of the erasure. The idea is to read sectors thro= ughout the drive in order to make sure that the erasure's overwriting patte= rns were written correctly.
The minimum verification corresponds =
to checking 1% of the surface of the drive (fast process), while the full v=
erification corresponds to checking 100% of the surface of the drive (slowe=
r process). There is an exception though: the NIST standards =E2=80=9CNIST =
800-88 Purge=E2=80=9D and =E2=80=9CNIST 800-88 Clear=E2=80=9D always perfor=
m by design a verification of at least 10% of the surface of the drive.
=
Taking samples across the drive's sur= face can efficiently detect any problems in the erasure, while being faster= than reading all the overwritten data. = Blancco Driver Eraser user can increase the level of verificati= on from the default 1% all the way up to 100% (full verification) when high= er level of security is required. If the verification finds any data left o= n the drive (overwriting patterns are missing), it will alert the user that= the erasure process has failed.
Different verifications for differ= ent erasure steps:
A systematic verification step is alw= ays enforced after the last erasure round. In addition, starting with v6.2.= 0, quick verification steps are carried out between overwriting rounds.