Cybersecurity 101back-iconWhat is Silver Ticket?

What is Silver Ticket?

Silver Ticket is a Kerberos attack where an attacker forges a service ticket to access a specific application or service without contacting the domain controller.

In Microsoft Active Directory environments, Silver Ticket attacks abuse the trust Kerberos places in service tickets. Once an attacker has the password hash of a service account, they can create a forged ticket for that service and impersonate users locally to the target service.

How does it work?

Kerberos normally uses a Key Distribution Center to issue tickets that prove a user’s identity. In a Silver Ticket attack, the attacker bypasses normal ticket issuance by creating a fake Ticket Granting Service ticket encrypted with the compromised service account key.

Because the forged ticket is presented directly to the target service, the domain controller may not see the authentication request. This makes Silver Ticket activity harder to detect than attacks that interact heavily with domain controllers.

Attack stage What happens
Credential theft The attacker obtains a service account password hash, often from a compromised endpoint or poorly protected credential store.
Ticket forgery A fake Kerberos service ticket is generated for a specific service, host, or application.
Service access The forged ticket is used to access the target service without requiring fresh validation from the domain controller.

Silver Ticket vs Golden Ticket

A Silver Ticket targets one specific service by abusing a compromised service account key. A Golden Ticket is broader and more severe because it uses the KRBTGT account key to forge Ticket Granting Tickets across the domain.

Both attacks indicate credential compromise, but Silver Ticket activity can be quieter. It is limited in scope, yet dangerous when the targeted service holds sensitive data, administrative functions, or lateral movement paths.

How Hexnode supports Silver Ticket defense

Hexnode supports Silver Ticket defense by improving endpoint visibility and reducing credential exposure across managed devices. Security teams can enforce baseline configurations, restrict risky applications, deploy patches, monitor compliance status, and take remote actions when a device shows signs of compromise.

For organizations investigating Kerberos abuse, Hexnode helps validate the endpoint side of the incident. Teams can identify non-compliant devices, remove unauthorized tools, enforce security policies, and support remediation workflows before attackers reuse stolen service credentials.

When should organizations use it?

Organizations should prioritize Silver Ticket detection and prevention when they rely on Active Directory, Kerberos authentication, Windows servers, or service accounts with elevated access. It is especially important for environments with legacy systems, shared administrative tools, or sensitive internal applications.

Defenses should include strong service account hygiene, least privilege, regular password rotation for service accounts, endpoint hardening, credential protection, and monitoring for unusual service access patterns. Silver Ticket risk is not solved by one control; it requires identity, endpoint, and logging practices to work together.

FAQs

Yes. The attacker does not need domain admin rights if they already have the correct service account hash for the targeted service.

The forged ticket may be presented directly to the service, so normal domain controller authentication logs may not show the full activity. Endpoint and service-level logs become critical.

Service accounts with broad permissions, weak passwords, old credentials, or access to sensitive systems create the highest Silver Ticket risk.