Join our Newsletter — 33% off our NHI Course
Authentication, Authorisation & Trust

Service Ticket

← Back to Glossary
By NHI Mgmt Group Updated November 2, 2026 Domain: Authentication, Authorisation & Trust

A service ticket is the Kerberos ticket that grants access to a specific service, such as LDAP or host access, after authentication succeeds. It is distinct from the initial login ticket. In trust abuse scenarios, service tickets are the practical payload attackers seek because they enable access to targeted systems and services.

What a service ticket does in Kerberos

A service ticket is the Kerberos artifact that turns a successful login into access to one specific service. It is not the initial authentication ticket, and that distinction matters because the service ticket is what the client presents when it wants to talk to LDAP, a host, or another protected service without reauthenticating from scratch.

In practice, the service ticket is the access-bearing object. It proves that the Kerberos exchange completed and that the user or principal is allowed to request a particular service, subject to the service’s own trust in the Kerberos infrastructure.

How service tickets fit into Kerberos access flow

Kerberos separates authentication from service access. First, the client proves who it is and obtains a ticket granting ticket or equivalent session context; after that, it requests service tickets for specific targets. This split reduces repeated password exposure and lets the ticketing system issue narrowly scoped access for each service request.

That design also means compromise of one ticket type does not automatically equal full access to everything. A service ticket is scoped to a service principal, so it can be used only where that service accepts the ticket and the surrounding authorization checks allow the session to proceed.

Why service tickets are security-sensitive

Service tickets become security-sensitive because they are the practical payload in many trust abuse scenarios. If an attacker can steal or forge a valid service ticket, they may be able to reach the target service directly, often without needing the original password, MFA step, or initial logon sequence.

For that reason, service tickets are not just protocol objects, they are access tokens in the operational sense. Their value comes from the trust the service places in Kerberos validation and from the fact that they can sometimes be replayed until they expire or are otherwise invalidated.

Common operational characteristics and limits

Service tickets are usually time-bound and service-specific, which is why they are useful for both usability and control. They can be renewed or reissued depending on policy, but they are still bounded by the Kerberos realm, the service principal, and the ticket lifetime chosen by the environment.

They are also only one part of the access story. A valid service ticket does not guarantee the requested action inside the service, only that the Kerberos front door has been passed. The application, directory, or host still has to enforce its own permissions, group membership checks, and session rules.

Risk and Threat Considerations

Service tickets are attractive to attackers because they can be used as ready-made access to a specific target once obtained. If an adversary steals, reuses, or forges a ticket, they may gain direct service access and move laterally without reentering credentials.

Failure mechanism: Ticket theft, replay, or abuse turns a trusted Kerberos artifact into an access shortcut, especially where tickets live in memory, are exported from endpoints, or remain valid long enough to be reused.

Impact: The attacker may reach directory services, hosts, or other Kerberos-protected systems, then pivot further by harvesting data, issuing administrative actions, or chaining the access into broader lateral movement.

Standards & Framework Alignment

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

MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5, NIST Zero Trust (SP 800-207) and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1550 — Use Alternate Authentication MaterialService tickets can be stolen or replayed as alternate auth material.
Recommendation — Detect ticket theft and replay paths, then hunt for lateral movement using harvested Kerberos material.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementService tickets are authenticator-like material with issuance and lifecycle exposure.
IA-2 — Identification and Authentication (Organizational Users)Kerberos service tickets support authenticated access for organizational principals.
Recommendation — Manage ticket lifecycle, lifetime, and protection with authenticator controls. Require strong authenticated access before issuing or accepting service tickets.
NIST Zero Trust (SP 800-207)Zero Trust ArchitectureKerberos service tickets illustrate scoped, continuously evaluated access to services.
Recommendation — Limit trust in any single ticket and re-evaluate access at each service boundary.
CIS Controls v85 — Account ManagementService ticket exposure depends on account and access lifecycle hygiene.
Recommendation — Review and revoke accounts and service access paths that could enable ticket abuse.

Practitioner Guidance

What to watch for: Treat service tickets as sensitive authentication material and monitor for unusual ticket issuance patterns, anomalous service use, and signs that a ticket has been replayed outside normal workstation-to-service behavior.

Governance implication: Ticket lifetime, service principal trust, and endpoint exposure should be managed as part of access control design, not as a purely protocol-level detail. If the environment allows long-lived or easily extracted tickets, the trust boundary is weaker than it looks.

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 November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org