Applies to: Pro, Enterprise and Audit
Purpose
Saved defaults determine the starting configuration for new sessions and are particularly important for Windows Explorer integration. They should reflect an approved baseline, not an individual operator’s temporary preference.
Save current settings as defaults
- Open CertErase.
- Select the approved erasure method.
- Configure verification, alternate data stream handling, identity changes, metadata handling, and post-deletion cleanup.
- Review the complete setting set.
- Open the Integration tab.
- Select Make Default (Make Current Settings Default).
- Confirm the saved result.
- Close and reopen CertErase, then verify that the expected settings are restored.
Initial defaults
A new configuration selects the single-pass method and leaves advanced controls disabled. The rename count is three, and the Random N-pass method initially uses three passes. These values are application defaults, not recommendations for every data class or storage type.
Recommended organizational baselines
Define named baselines outside the application, for example:
- Routine logical file erasure: approved single-pass profile, verification enabled, alternate data streams enabled on NTFS, no automatic free-space wipe.
- Elevated workstation cleanup: routine controls plus file identity and timestamp handling.
- Decommissioning preparation: use device-level sanitization tooling, such as DriveErase, rather than relying on file-level defaults alone.
Change control
Record changes to production defaults. At minimum, document:
- Old and new setting values;
- Reason for the change;
- Approving authority;
- Product version tested;
- Representative media tested;
- Effective date;
- Affected procedures.
Important limitation
Defaults are configuration convenience. They do not confirm that the current target is suitable for logical overwrite, that the operator has selected the correct data, or that a standards-based sanitization decision has been made.