Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Adversaries may use alternate authentication material, such as password hashes, Kerberos tickets, and application access tokens, in order to move laterally within an environment and bypass normal s...
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✗→✓ | ▲ Improved | -34% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 29% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -22% | 0% |
| case-12 | ✗→✓ | ▲ Improved | -24% | 0% |
| case-13 | ✗→✓ | ▲ Improved | 0% | 0% |
Adversaries may use alternate authentication material, such as password hashes, Kerberos tickets, and application access tokens, in order to move laterally within an environment and bypass normal system access controls.
Authentication processes generally require a valid identity (e.g., username) along with one or more authentication factors (e.g., password, pin, physical smart card, token generator, etc.). Alternate authentication material is legitimately generated by systems after a user or application successfully authenticates by providing a valid identity and the required authentication factor(s). Alternate authentication material may also be generated during the identity creation process.
Caching alternate authentication material allows the system to verify an identity has successfully authenticated without asking the user to reenter authentication factor(s). Because the alternate authentication must be maintained by the system—either in memory or on disk—it may be at risk of being stolen through Credential Access techniques. By stealing alternate authentication material, adversaries are able to bypass system access controls and authenticate to systems without knowing the plaintext password or any additional authentication factors.
Platforms: Windows, SaaS, IaaS, Containers, Identity Provider, Office Suite, Linux
> Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
Perform audits or scans of systems, permissions, insecure software, insecure configurations, etc. to identify potential weaknesses.
Set and enforce secure password policies for accounts.
Where possible, consider restricting the use of authentication material outside of expected contexts.
Limit credential overlap across systems to prevent the damage of credential compromise and reduce the adversary's ability to perform Lateral Movement between systems.
Configure Active Directory to prevent use of certain techniques; use SID Filtering, etc.
Consider implementing token binding strategies, such as Azure AD token protection or OAuth Proof of Possession, that cryptographically bind a token to a secret. This may prevent the token from being used without knowledge of the secret or possession of the device the token is tied to.
Enforce the principle of least-privilege. Do not allow a domain user to be in the local administrator group on multiple systems.
| Finding | Severity | Impact | | ---------------------------------------------------------- | -------- | --------------- | | Use Alternate Authentication Material technique applicable | High | Defense Evasion |
| CWE ID | Title | | ------- | ---------------------------- | | CWE-693 | Protection Mechanism Failure |
Other measured skills in the registry, with their headline benchmark lift.