A shared terminal is a point-of-work device used by multiple employees across shifts or roles. The device itself may be constant, but the person using it changes frequently. Without strong authentication at handoff, shared terminals can obscure who performed a transaction or made a system change.
Expanded Definition
A shared terminal is not just a common workstation; it is an access handoff point where identity assurance can collapse if the operator is not re-established at each shift change. In NHI and IAM practice, the device may be stable while the human context is transient, which makes attribution, approval traceability, and session continuity materially different from single-user endpoints. That distinction matters because a terminal used by many operators often becomes a bridge between role-based access, just-in-time access, and activity logging. NIST Cybersecurity Framework 2.0 frames this problem through identity, access, and logging outcomes, but definitions vary across vendors when shared terminals are implemented in kiosks, control rooms, or plant-floor systems. NHI Management Group treats the term as an operational identity boundary, not merely a hardware category, because the security question is who had authority at the moment of action. The most common misapplication is treating the device as trusted by default, which occurs when shifts change without re-authentication and per-user audit linkage.
Examples and Use Cases
Implementing shared terminals rigorously often introduces workflow friction, requiring organisations to weigh speed at the handoff against accurate attribution and stronger session controls.
- A warehouse picking station is used by multiple operators across shifts, so each login must map cleanly to the individual responsible for inventory adjustments and exceptions.
- A hospital nurse station uses the same terminal for charting, medication checks, and order verification, making fast re-authentication essential to preserve accountability.
- A manufacturing floor terminal allows technicians to approve machine overrides, where shared access must be paired with short sessions and clear operator identification.
- A security operations console is passed between analysts during a handover, and the organisation needs per-user audit trails to distinguish investigation activity from administrative changes.
- A shared terminal in a branch office is used for customer servicing, where weak handoff controls can blur who initiated account updates or credential resets.
These patterns align with broader identity guidance in the NIST Cybersecurity Framework 2.0 and with the NHI governance emphasis in Ultimate Guide to NHIs, which highlights how weak identity boundaries increase risk across shared operational contexts.
Why It Matters in NHI Security
Shared terminals matter because the same physical endpoint may be stable while the effective identity changes repeatedly, and that creates a high-risk zone for service accounts, delegated credentials, cached sessions, and administrative actions. When authentication at handoff is weak, logs may show what happened without reliably showing who did it, which undermines incident response, segregation of duties, and post-event forensics. This becomes especially important where human operators also trigger or supervise NHIs, because an action taken from a shared terminal can mask whether a person, an agent, or a privileged service workflow initiated the request. NHI Management Group notes that only 5.7% of organisations have full visibility into their service accounts, a reminder that attribution gaps often extend beyond the terminal itself and into the identities behind it. The control objective is not just screen access but trustworthy operator identity at every use. Organisational risk becomes visible only after an unexplained change, a disputed transaction, or an incident review, at which point shared terminal controls become operationally unavoidable to address.
For governance and containment, teams should also align this pattern with Ultimate Guide to NHIs as a reference for identity visibility and lifecycle control.
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 and OWASP Agentic AI Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207) and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-01 | Shared terminals amplify NHI attribution gaps and weak operator identity assurance. |
| NIST CSF 2.0 | PR.AC-7 | Identity verification and access control are central when many users share one device. |
| NIST Zero Trust (SP 800-207) | 4.1 | Zero Trust requires continuous verification even on trusted internal devices. |
| NIST SP 800-63 | AAL2 | Shared terminals need stronger authenticator assurance at each user change. |
| OWASP Agentic AI Top 10 | A2 | Agentic and delegated actions can be obscured when multiple operators use one console. |
Separate human and agent attribution in logs and enforce explicit operator confirmation.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 24, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
