Applies to: All editions
Logical versus physical scope
CertErase operates through Windows-accessible file and volume interfaces. It can overwrite addressable file content, process accessible alternate streams, modify selected metadata, request deletion, and fill addressable free space with temporary data.
It cannot directly control every physical or external location where data may exist.
SSDs and flash media
Solid-state storage commonly uses wear levelling, garbage collection, over-provisioning, bad-block management, and a flash translation layer. A host write to a logical address can be redirected to a different physical page. Prior pages may remain outside ordinary host access until controller-managed erasure occurs.
For whole-device sanitization of flash storage, use a technique approved for the specific device and threat model, such as a validated device sanitize command, cryptographic erase where applicable, or physical destruction under policy. Do not rely on repeated file overwrites as proof of whole-device purge. For whole-device sanitization, we recommend using Probativa DriveErase.
Remapped and inaccessible sectors
Hard drives and other devices can remap failed sectors. Data in a sector no longer exposed to the host cannot be overwritten by normal file access. Device-level commands or destruction may be required for higher assurance.
Snapshots, backups, and synchronization
CertErase does not automatically delete:
- Volume Shadow Copies;
- Backup sets and catalogues;
- Cloud version history;
- Synchronized replicas;
- Storage-array snapshots;
- Email attachments or collaboration copies;
- Endpoint telemetry or data-loss-prevention records;
- Caches and search indexes on other systems.
Address each copy under the responsible system’s retention and deletion controls.
Virtual machines and thin provisioning
Inside a virtual machine, writes are mediated by the guest file system, virtual disk, hypervisor, host file system, and physical storage. Snapshots and thin-provisioned blocks can retain earlier versions. Permission to run in a VM does not make guest-level overwrite equivalent to host- or device-level sanitization.
Remote and cloud storage
A successful application result on a network path proves only the logical operations visible to the client. Obtain provider-specific deletion, retention, replication, encryption, and media-disposition evidence where required.
Decision rule
Use CertErase when the approved outcome is logical erasure of addressable data in a supported Windows environment. Escalate to device-level sanitize, cryptographic erase, or physical destruction when policy or media characteristics require stronger assurance. For device-level sanitize, Probativa DriveErase should be used instead.