Outsourced ProgrammersPowered by StealthAgents

What share of loaner devices are returned with data intact?

A protocol for tracking loaner devices from handoff to wipe, counting the returns with residual data, and separating a missed wipe from an unreadable disk.

What share of loaner devices are returned with data intact?
WORK_LANE / RESEARCH BRIEF / DATAREVIEW QUEUEACCEPTANCEPASSowner review requiredEVIDENCE TRAILTICKET → BRANCH → REVIEW → CLIENT RELEASE
Table of contents
  1. Research context
  2. Practical application
  3. Operating controls
  4. Sources
  5. Frequently asked questions

Research context

This protocol measures the share of loaner devices that return with residual data still readable. The unit is one loaned device, identified by the asset tag and the loan record. Residual data means any client record, credential, or user profile that remains accessible after the return process. The study describes return hygiene, not the security of the device model.

Define the loan population as every device issued in the window, including replacements and short loans. Record the asset tag, the assigned person, the issue date, and the expected return date. Exclude a device that never left the store. Test the population against the asset list before sampling.

Define the return process as the approved steps in the runbook, including account removal, session revocation, and the wipe. Record the runbook version and the date it took effect. If the process changes during the window, split the sample at the change date. A different process can change the result.

Define residual data by category, such as a signed-in browser profile, a local file, a saved credential, or a cached record. Test for each category with an approved method. Do not open customer records during the check. Record the category and the evidence rather than the content.

Record the device state at return, including the enrollment status, the last sync time, and the wipe result from the management console. A console that reports success is not enough if the local disk still opens a profile. Compare the console result with a local check on a sample. Report the difference.

Practical application

Report the number of devices returned, the number with a recorded wipe, the number with residual data, and the number that could not be checked. Show the counts by loan length and by return channel. Present the devices that returned late. Use the same denominator for every rate.

Separate a missed wipe from an unreadable disk. A missed wipe is a process gap, while a disk that cannot be read may be a hardware failure or a check limitation. Report the two categories separately. Record the reason beside each device that could not be checked.

Inspect the devices returned in the last week before a holiday or a contract end. A cluster may mean the return check is skipped when the office is busy. Compare the pattern with the loan volume. A quarterly average can hide a monthly gap.

Do not treat a low residual count as proof that the process works. A device may be wiped by the previous user before return, or the check may miss a category. Report the check method and the categories covered. A narrow check produces a narrow result.

The record cannot show whether data was copied off the device before return or whether a cloud service still holds a session. It can show only whether the local check found residual data. A clean disk is not proof that no copy exists, and a dirty disk is not proof that data was used. The protocol also cannot inspect an encrypted disk that will not mount.

Operating controls

A useful additional view is the share of devices with a named return confirmation from the contractor. A device that arrives without a confirmation is harder to trace. Record the confirmation date and the person who sent it. That field turns a count into a review of the handoff.

Give the result to the client asset owner and the offshore delivery lead with one observable change. The change might be a return checklist, a wipe verification step, a shorter loan period, or a named return contact. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions after the change.

Close the review with one change and a date to re-measure. The change should address the most common residual category rather than the easiest device to check. Record the expected effect and the evidence that will prove it. A return process that is never checked is only an assumption.

Report the devices that never came back as a separate count. A missing device is a different risk from a dirty disk. Record the last contact date and the asset owner. The study should not fold a lost device into the return rate.

Sources

  1. NIST SP 800-53 security and privacy controls
  2. NIST SP 800-124r1 mobile device security
  3. CIS Controls
  4. CISA Secure by Design

Frequently asked questions

What should happen first?

Begin with a bounded ticket, approved access, explicit acceptance evidence, and a named reviewer.

Who approves production changes?

The client's technical owner keeps final merge and release authority.

Build a programming lane your technical owner can review.

Bring the stack, backlog, acceptance checks, and release boundaries. We will help scope the role around the work.

Discuss your programming needs