Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› What should organisations do when a personal device…
Cyber Security

What should organisations do when a personal device is lost, stolen, or involved in a security incident?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: Cyber Security

The response plan should specify immediate reporting, access revocation, containment steps, and investigation procedures. Organisations should be able to isolate work data, reset affected credentials, and confirm whether company information was exposed. Offboarding processes should also address how data and access are removed from personal devices when employment ends, so risk does not persist after departure.

When a personal device is lost, stolen, or suspected in an incident, organisations should treat it as a time-sensitive access problem, not just an IT support issue. The first priority is to preserve evidence and cut off paths into company data, then confirm what the device could reach, what may already have been exposed, and whether any ongoing access remains active.

That means the response plan should define who is notified, who can trigger containment, and what actions happen in the first hour. For BYOD environments, the plan should also cover how work data is separated from personal data, because selective wipe, session revocation, and token invalidation are only effective if the organisation can reach the right controls quickly. See the BYOD Policy Template and the Lost or Stolen Device Response Checklist.

If the device is used for email, chat, VPN, SSO, or app access, the incident can extend well beyond the physical loss. Lost sessions, cached tokens, and remembered authenticator state can outlive the handset or laptop itself, so the review should include which services were reachable, whether any privileged apps were installed, and whether the device was protected by encryption and remote-wipe capability. The Mobile Device Security Guide and the Infostealer Threat Guide are useful for understanding how device exposure can turn into account exposure.

What should the first response accomplish?

The first response should accomplish three things: stop further access, establish scope, and preserve enough evidence to investigate properly. For a lost or stolen personal device, that usually means reporting the event promptly, revoking active sessions where possible, resetting the credentials most likely to be reused, and checking whether the device stored synchronised work data, cached files, or corporate credentials. If the device was only partially managed, the organisation may need to use app-level containment instead of full-device administration.

This is also where response quality is often decided. If reporting is slow, the attacker or finder may have a window to open mail, approve prompts, or use authenticated apps before the organisation acts. If containment is too aggressive, employees may lose personal data or evidence may be destroyed unnecessarily. The response process should therefore make a clear distinction between containment, data removal, and forensic preservation.

For incident handling structure, the Incident Response Policy Template helps define reporting duty, containment authority, and review responsibilities in a way that fits mobile and BYOD events.

How should organisations verify exposure and remove access?

Verification should focus on what the device could access, not just whether it is physically recoverable. Teams should check whether the device had active sessions, cached mail, downloaded documents, offline app data, synced notes, browser tokens, or saved credentials, then decide whether selective wipe, full wipe, or account-level reset is the right outcome. If there is any possibility that company information was stored locally, the organisation should confirm the encryption state and whether recovery can still be blocked.

Access removal should be coordinated across identity, mobile management, and application controls. A single password reset is often not enough if refresh tokens, remembered devices, or app sessions remain valid. Where the organisation uses FIDO or other strong authenticators, it should also confirm whether backup credentials or recovery paths need review. The practical objective is to remove every route that still lets the missing device act as if it were trusted.

For a deeper operational view of device containment and remediation, the Stolen or Lost Phone guide and the BYOD Policy Template both map well to the exposure and removal decisions that matter most here.

What changes when the device belongs to an employee?

Employee-owned devices add a lifecycle problem as much as an incident problem. Organisations need to know whether the device still has enrolment, whether work profiles or managed apps can be selectively wiped, and what happens to data and credentials when the person leaves the company. If offboarding is weak, the same control gap that leaves data on a lost phone can leave access behind after employment ends.

That makes end-of-employment handling part of the same control family as lost-device response. The organisation should be able to remove corporate access, retire any managed app containers, and revoke remaining sessions or tokens without relying on the employee to do the right thing manually. Where personal and work uses are tightly blended, the cleaner the separation policy is up front, the easier the incident response will be later.

Risk and Threat Considerations

Lost or stolen personal devices create a real exposure window because attackers or unauthorised finders can often use the device faster than the organisation can react. The main risk is not just device loss, but residual trust: stored sessions, cached data, saved passwords, and app tokens can turn a physical incident into account compromise or data disclosure.

Failure mechanism: A device is lost or taken while it still holds authenticated sessions, offline data, or reusable credentials, and those artefacts remain valid long enough for misuse or extraction.

Impact: Company email, documents, chat history, and connected services may be exposed, and the organisation may have to investigate whether the event was a simple loss, a targeted theft, or the start of broader account abuse.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP Non-Human Identity Top 10 addresses the attack surface, CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-6 — Access Control ManagementLost-device response depends on revoking stale access and sessions quickly.
Recommendation — Revoke device-linked access and invalidate sessions as soon as the loss is reported.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementThe incident can expose reusable credentials, tokens, and recovery paths.
IR-4 — Incident HandlingThe question is about containment, reporting, and investigation of a security incident.
Recommendation — Rotate compromised authenticators and invalidate any device-bound credentials. Apply incident-handling procedures to triage, contain, and investigate the device event.
ISO/IEC 27001:2022A.5.24 — Information security incident management planning and preparationThe response plan needs predefined incident roles, triggers, and containment steps.
Recommendation — Prepare and rehearse mobile-device incident procedures before a loss occurs.
OWASP Non-Human Identity Top 10NHI-01 — Improper OffboardingPersonal devices can retain corporate access after the employee departs.
Recommendation — Remove access paths and work data from personal devices during offboarding.

Practitioner Guidance

What to verify: Confirm that the response plan can revoke sessions, isolate work data, and distinguish between container wipe and full-device wipe before an incident happens. If those actions depend on a single admin console or one mobile platform feature, that dependency should be tested in advance rather than assumed.

Decision rule: If the device can authenticate to any production or sensitive system, treat the event as an identity and access incident as well as a device incident. Prioritise credential and session reset before spending time on device recovery details.

Practitioner takeaway: Good lost-device handling is really about reducing the lifetime of trust in the device, once that trust is broken, response speed, data separation, and session control matter more than the physical handset itself.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org