Destroying Camera Recordings: Automatic Deletion, Disk Destruction and Records

Destroying camera recordings: verifying loop overwriting, protected and exported clips, secure erasure of NVR disks, the destruction record and a checklist.
Technical summary
Technology
KVKK Law No. 6698, NIST SP 800-88, ATA Secure Erase, hdparm, NVR, VMS
Topic
Destroying camera recordings and recording media
Level
Intermediate
Prerequisites
  • An approved retention period policy
  • NVR/VMS admin access
  • Disk and device inventory
In this article7 sections

If you can’t show that a camera recording whose retention period has expired is really gone, your retention policy is just a document. Because deletion in video systems is often automatic, it isn’t seen as a separate process. Yet recordings locked because of an incident, exported clips, archive and backup copies, and removed disks fall outside this automatic cycle. Below we give IT and compliance teams, step by step, how to verify loop overwriting, how to destroy protected recordings, disk and device destruction methods and the fields a destruction record should contain.

Why destruction is a separate process for camera recordings

The Regulation on the Deletion, Destruction or Anonymization of Personal Data defines three methods: deletion (making data inaccessible and unusable again for the relevant users), destruction (making data inaccessible, unrecoverable and unusable again by anyone) and anonymization. For data controllers obliged to register with VERBİS, the Regulation also requires a retention and destruction policy, periodic destruction at intervals not exceeding six months, and records of the operations kept for at least three years. Check the current text on mevzuat.gov.tr.

In camera systems, three characteristics make applying this framework harder:

  • Deletion is automatic but not tied to policy: The NVR deletes the oldest recording when the disk fills. If you increase capacity or the cameras’ bitrate drops, the retention period lengthens on its own. Without anyone deciding.
  • Copies leave the system: Clips exported for incident review spread to USB sticks, email, ticket records and shared folders.
  • Deleted data stays on disk: When a VMS deletes a recording, it often only removes the index entry and file allocation information; the data physically stays on the disk until it’s overwritten. This detail becomes decisive when the disk leaves the system.

How to set the retention period is explained in the camera recordings and KVKK retention period article; here we focus on how destruction is applied when the period expires.

Verifying loop overwriting

For loop overwriting to be accepted as a destruction process, two conditions are needed: the period must be fixed by policy, and its application must be proven regularly.

  1. Define the maximum retention period: Most enterprise VMSs and NVRs offer a maximum recording duration (days) parameter per camera or channel. Set this parameter equal to the period in the policy; recordings whose period has expired are deleted even if the disk has free space.
  2. Verify that capacity covers the period: If capacity is insufficient while a maximum period is defined, the system deletes recordings before the period expires. That’s a breach of the retention policy; not a destruction problem but a data loss problem.
  3. Measure the oldest recording: Report the date of the oldest recording for each camera through the VMS, or check by sampling from the playback screen. The expected value is around “today minus the retention period.”
  4. Record deviations: If the oldest recording is older than expected, the period parameter isn’t being applied; if it’s newer, there’s a capacity or disk problem.
Observation Likely cause Action
Oldest recording older than the period Maximum period undefined or missing on some channels Fix channel settings, destroy the excess recordings
Oldest recording newer than the period Insufficient capacity, disk failure, bitrate increase Redo the capacity calculation, check disk status
Large differences between channels Different recording mode or different storage group Compare with the policy per camera group
Older recordings in the archive tier Archive retention defined separately Align the archive period with the policy

Do this measurement on the same schedule as the periodic destruction cycle. In systems with archive and backup tiers, repeat the same measurement for each tier. An example finding: the period in the policy (30 days in this example) is applied on primary storage, while the same recording has been sitting in the archive tier for months. Incident copies, exported clips and backups are also subject to the relevant retention rule. For the tiered structure, see the video recording archiving and backup guide.

Destroying protected and exported recordings

Recordings locked (placed under protection) because of an incident review, a legal request or a data subject application are exempt from loop deletion. This exemption isn’t indefinite. When the incident closes or the legal process ends, destroying the recording requires a separate decision and a separate action; it doesn’t happen by itself.

  • Protection record: Every lock is written to the protected recordings list with the camera, time range, reason, requester and review date.
  • Review: In the periodic destruction cycle, the question “does the reason for protection still apply?” is answered for each recording on the list.
  • Lifting the lock: If the reason has ended, the lock is lifted and, if the recording’s period has passed, it’s deleted through the VMS; the action is written to the audit trail.
  • Exported copies: When a clip is produced, where it was saved and to whom it was given are kept in the export record. On destruction, each of these copies is found and deleted; written confirmation of destruction is requested for copies given to outside parties.

Don’t destroy recordings that require a chain of custody without the approval of the unit owning the incident and the legal unit. The protection and handover process for these recordings is explained in the camera recording incident investigation and chain of custody article.

Disk and device destruction methods

During a disk replacement, capacity upgrade, NVR decommissioning or return of a leased server, recordings on disks may be physically readable even if they appear deleted in the VMS. Formatting isn’t destruction. NIST SP 800-88 (Guidelines for Media Sanitization), a common reference for media sanitization, classifies methods as Clear, Purge and Destroy; the document can be reviewed on csrc.nist.gov.

Method Suitable environment Limitation
Full overwrite (Clear) A working HDD Takes a long time; may not reach reallocated sectors
ATA Secure Erase / Sanitize (Purge) HDDs and SSDs that support it Requires disk and controller support; may not work behind a RAID card
Cryptographic erase (Purge) Self-encrypting drives (SED) It must be verified that encryption was enabled from the start
Physical destruction (Destroy) Failed, inaccessible or high-risk disks The disk can’t be reused; requires an authorized company and a record

On Linux, for an HDD connected directly to a SATA port and supporting the ATA security feature, the typical flow is as follows. The commands irreversibly erase all data on the disk. Verify the device name twice and run the commands only on a workstation set aside for destruction; the wrong /dev/sdX erases the wrong disk.

# Verify the disk and serial number
lsblk -o NAME,SIZE,MODEL,SERIAL
hdparm -I /dev/sdX | grep -A8 "^Security"

# Should show "not frozen"; if frozen, retry after a system sleep/wake
hdparm --user-master u --security-set-pass Temp123 /dev/sdX
hdparm --user-master u --security-erase Temp123 /dev/sdX

# If Secure Erase isn't supported, a single-pass full overwrite
dd if=/dev/zero of=/dev/sdX bs=4M status=progress oflag=direct

Disks behind a RAID controller may not respond to these commands directly; remove the disk and connect it to a separate system, or use the controller’s own secure erase feature. A single disk removed from a RAID array may contain only fragments of recordings because of the stripe structure, but it can still hold readable video blocks. A single disk is within the scope of destruction too. For failed and unreadable disks, the most reliable route is physical destruction. Disk failure and replacement processes are covered in the NVR disk failure and RAID rebuild guide; handing the removed disk over to the destruction process during replacement should be a written step of that procedure.

There are media forgotten as often as disks: SD cards in cameras doing edge recording, the internal eMMC or system disks of NVRs (which contain configuration and user information), USB sticks used for exports and the operating system disks of VMS servers. Sending a faulty camera for service with its SD card still in it is a common mistake on site.

Destruction record fields

The record is the evidence that destruction was done and under whose responsibility. You can use separate templates for recording destruction and media destruction; the common fields are:

  • Record number, date and time
  • Type of destruction: periodic recording destruction, protected recording destruction, exported copy destruction, media destruction
  • Scope: camera or camera group, time range; for media destruction, disk model, serial number, capacity and the device it was removed from
  • Method applied and tool used (e.g. VMS deletion, ATA Secure Erase, physical shredding)
  • Verification result: oldest recording date, a read attempt after deletion or the destruction company’s certificate
  • The people who performed, approved and, if any, witnessed the action
  • If an outside company was used, the company name, handover record and destruction certificate reference

Writing the disk serial number on the record creates a one-to-one link between the device inventory and the destruction record. The question “is there a destruction record for every disk removed from the inventory?” can then be answered with a single query. No serial number, no link.

Periodic destruction checklist

Apply this list on a schedule that doesn’t exceed the maximum interval in the regulation; for many organizations, a three-month cycle is a manageable start.

  • Is the maximum retention period parameter the same as the policy in all camera groups?
  • Was the oldest recording date measured in each camera group, and deviations recorded?
  • Are there any expired recordings left in the archive and backup tiers?
  • Was the protected recordings list reviewed, and were locks whose reason has ended lifted?
  • Was the destruction, or the reason for keeping, of clips exported during the period confirmed?
  • Is there a destruction record for disks, SD cards and devices replaced or decommissioned during the period?
  • Have the records been archived and forwarded to the compliance unit?

To set up retention, deletion and destruction rules together with the policy, VMS configuration and record templates, see our camera recording retention, deletion and destruction policy work; for replacing failed disks and capacity planning, our NVR disk failure and capacity upgrade service.

Frequently asked questions

Does the NVR’s loop overwriting meet the destruction obligation?

Not on its own; it doesn’t cover exported copies, recordings set aside for incidents or backups. Loop overwriting deletes recordings when the disk fills; the actual retention period is determined by disk capacity and bitrate, not by policy. A maximum retention period should be defined per channel, the date of the oldest recording verified regularly, and this check recorded.

Can a failed NVR disk be sent to the manufacturer under warranty?

Sending it without erasing the data is risky, because readable recordings may remain on the disk. If the disk is still accessible, apply secure erasure. If not, consider physically destroying the disk in-house and giving up the warranty claim, or a warranty option where the manufacturer replaces the disk without asking for it back.

Is the overwrite method enough for SSDs?

It’s generally not considered enough. Because of wear leveling on SSDs, a logical overwrite may not reach every physical block. Use the manufacturer’s sanitize or cryptographic erase command; if that isn’t possible, choose physical destruction.

How long should destruction records be kept?

The Regulation on the Deletion, Destruction or Anonymization of Personal Data provides that records of deletion, destruction and anonymization operations are kept for at least three years, other legal obligations aside. The organization’s internal policy can set a longer period.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Video Surveillance

IP cameras, recording and central management infrastructure. We plan blind spots, retention periods and the camera network around the risks of each site.

Knowledge Center

Other articles