D-Secure Trust Center
How we sign erasure reports, what we record, how we handle data, which standards our erasure methods apply, and how to report a security issue.
Security Posture & Controls
Every erasure produces a report signed with SHA-256 and a 2048-bit key, and every erasure is recorded in our backend ledger. Read how that works and how to reach us about a security concern.
- How Reports Are Signed
- Report a Security Issue
- Every report is signed with SHA-256 and a 2048-bit key.
Privacy & Legal Disclosures
The documents that govern how we process your data and how you may use D-Secure software.
Regulatory Compliance Support
D-Secure Drive Eraser applies NIST SP 800-88 Clear and Purge methods and produces digitally signed erasure reports to support your own audit documentation.
Operational Integrity & Verifiable Results
Erasure Runs on the Machine Itself
Drive Eraser boots from a USB stick as an x64 ISO, with UEFI and Secure Boot supported, so the erasure does not depend on the operating system installed on the drive being wiped. The drives are erased by the machine they are attached to, and the signed report records the result.
Results You Can Check Yourself
An erased drive should give data recovery tools nothing to recover. You are welcome to test that with recovery software of your choice. Our verification methods guide explains how to sample erased drives as part of your own quality checks.
How Erasure Reports Are Signed
An erasure report is only useful as evidence if nobody can quietly edit it later. That is why each report is digitally signed when it is created. Here is what happens after every erasure.
- STEP 01
The erasure finishes
Drive Eraser or File Eraser completes the job and records what was erased, which method was used (for drives, for example a NIST SP 800-88 Clear or Purge method, cryptographic erase or a DoD 5220.22-M overwrite) and whether the job succeeded.
- STEP 02
The report is assembled
Page 1 is the erasure certificate. Page 2 onwards is the detailed summary of the job. The same data is also available as JSON for systems that need to read it automatically.
- STEP 03
The report is signed
A SHA-256 hash of the report content is signed with a 2048-bit key. If anyone changes the content afterwards, even a single character, the signature no longer matches and the report fails verification.
- STEP 04
The erasure is recorded in the ledger
An entry for the erasure is kept in the D-Secure backend ledger, and the report is available in the report repository of your admin console.
What "tamper-evident" means in practice
The signature does not stop someone from opening a PDF in an editor. It makes any edit detectable: the signed hash was calculated over the original content, so a changed report no longer matches its signature. When an auditor asks how you know a certificate is genuine, the answer is the signature plus the matching entry in the ledger, not the look of the document. See reports and certificates for what a report contains.
The Backend Erasure Ledger
Alongside the signed report, D-Secure keeps a ledger of erasures in its backend. The report is the document you hand to an auditor or a customer; the ledger is the independent record that the erasure took place.
Having both matters in two situations. If a report file is lost or deleted on a local machine, the record of the erasure still exists. And if a report is ever disputed, it can be compared with the ledger entry instead of relying on the PDF alone.
Administrators see reports in the report repository of the admin console, which is also where users and licenses are managed.
How We Handle Data
- Account data. We hold the details needed to run your account: users, licenses and the erasure reports your organization produces.
- Erasure reports. A report describes the device or files that were erased, the method and the result. Its purpose is to prove the erasure, so it records the job, not the content that was removed.
- Website analytics. Analytics on this website load only after you accept them in the cookie banner. The cookie policy lists what is used.
- Your rights. How we collect, use and retain personal data, and how to request access or deletion, is set out in the privacy policy.
Standards, Stated Plainly
Security questionnaires often ask the same few questions. These are our direct answers.
| Standard | Where D-Secure stands | What it means for you |
|---|---|---|
| NIST SP 800-88 | Drive Eraser applies the Clear and Purge methods described in NIST SP 800-88, including cryptographic erase on drives that support it, and also offers overwrite patterns such as DoD 5220.22-M. The report records which method was used. | Destroy, the third NIST category, is physical destruction and is not something software performs. Every report names the method applied to each drive, so auditors see exactly how Clear or Purge was carried out. |
| ISO/IEC 27001 | Our internal practices follow ISO 27001 controls. | Erasure runs inside a documented, controlled process, and every job produces a signed report you can file with your own ISMS records. |
| SOC 2 | Our team answers SOC 2-style vendor security questionnaires directly, with our documented security practices. | Send your questionnaire early and we return precise answers on report signing, data handling and the erasure ledger. |
| GDPR, HIPAA and similar laws | Signed erasure reports give you a record of what was erased, when and how. | These laws do not prescribe a specific erasure product or certificate. Using D-Secure supports your records; compliance remains your organization's responsibility. |
For a deeper look at the sanitization categories, read our NIST SP 800-88 overview or the wider compliance hub.
Report a Security Issue
If you believe you have found a vulnerability in D-Secure software, the admin console or this website, email support@dsecuretech.com and start the subject line with "Security report". A clear report helps us reproduce and fix the problem faster. Please include:
- The product, version or page affected.
- The steps needed to reproduce the issue.
- What you expected to happen and what actually happened.
- Screenshots or logs, with any personal data removed.
While investigating, please do not access, change or delete data that does not belong to you, and give us a reasonable chance to fix the issue before you share details publicly.
Trust Center FAQ
Does D-Secure hold ISO 27001 or SOC 2?
No. D-Secure does not hold an ISO 27001 certification or a SOC 2 report. Our practices follow ISO 27001 controls, and every erasure is backed by a signed report and a ledger record you can verify yourself.
How can I tell that an erasure report has not been altered?
Every report is signed with a SHA-256 hash and a 2048-bit key. Changing the content breaks the signature, so an edited report fails verification. The erasure is also recorded in the backend ledger, which gives you a second record to compare against.
Does using D-Secure make my organization compliant with NIST SP 800-88 or GDPR?
No software can do that on its own. Drive Eraser applies NIST SP 800-88 Clear and Purge methods and produces signed reports that support your documentation. Your policies, processes and records decide whether your organization is compliant.
Where are my erasure reports stored?
Reports are available in the report repository of the admin console, where administrators manage users, licenses and reports. The erasure itself is also recorded in the D-Secure backend ledger.
How do I report a security vulnerability?
Email support@dsecuretech.com and start the subject line with "Security report". Include the affected product or page, steps to reproduce, and what you observed. Please do not access or change data that does not belong to you while investigating.