Does the Applicant ensure sensitive data is permanently removed (e.g., degaussing, overwriting with 1's and 0's, physical destruction but not merely deleting) from hard drives and other storage media before equipment is discarded or sold and from paper records prior to disposal?
This is application question 37 of 63 on the Markel MADB 5001 02 11. It is a control question and reaches 7 controls. The wording is the carrier's, quoted verbatim.
Held from the DataBreach Application for Data Breach and Privacy Liability, Data Breach Loss to Insured and Electronic Media Liability Insurance (form MADB 5001 02 11) (read 2026-10-17), jurisdiction United States. All Markel questions.
Facets: control: Does the Applicant ensure sensitive data is permanently removed (e.g., degaussing, overwriting with 1's and 0's, physical destruction but not merely deleting) from hard drives and other storage media before equipment is discarded or sold and from paper records prior to disposal?; population: records
What this question reaches
- ISO 27001:2022 A.5.33: Protection of records (direct)
Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file: the retention schedule for the records the question names; the disposal or destruction record for a dated batch, with the method - ISO 27001:2022 A.8.10: Information deletion (supporting)
Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file: the retention schedule for the records the question names; the disposal or destruction record for a dated batch, with the method - ISO 27001:2022 A.7.14: Secure disposal or re-use of equipment (supporting)
Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file: the retention schedule for the records the question names; the disposal or destruction record for a dated batch, with the method - SOC 2 P4.2: Retaining personal information (direct)
Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file: the retention schedule for the records the question names; the disposal or destruction record for a dated batch, with the method - SOC 2 P4.3: Securely disposing of personal information (supporting)
Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file: the retention schedule for the records the question names; the disposal or destruction record for a dated batch, with the method - NIST CSF 2.0 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected (direct)
Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file: the retention schedule for the records the question names; the disposal or destruction record for a dated batch, with the method - PCI DSS 4.0 Requirement 3: Protect Stored Account Data (supporting)
Establishes the retention or disposal practice asked about; it does not establish that every record followed it.
Evidence to have on file: the retention schedule for the records the question names; the disposal or destruction record for a dated batch, with the method
Subject: retention_disposal. Owner a broker routes it to: Privacy and records owner.
The same control on other applications
Hiscox Q16, AXIS Insurance Q18, AXIS Insurance Q19, AXIS Insurance Q54, Munich Re Q114, Munich Re Q115, Aon Q33, Arch Insurance Q24, Arch Insurance Q70, Argonaut Insurance Company Q3, Northbridge General Insurance Corporation Q24, Northbridge General Insurance Corporation Q25.
Map your own answers in the tool. See the Markel page, the controls index, the island and the answers.