Credentials Harvesting

Overview

This room focuses on harvesting credentials from an internal foothold. It covers where credentials live on Windows systems and in AD environments, how to extract them from local files, registry, SAM, LSASS memory, and related stores, and why credential access is a key step for lateral movement and impersonation.

Core idea: once you have system access, credentials become one of the highest-value targets because they let you move, blend in, and escalate without relying only on exploits.

1) What Credentials Harvesting Is

Credentials harvesting is the process of obtaining usernames, passwords, hashes, tickets, or any authentication material that can be reused.

Legitimate credentials are especially useful because they support quieter lateral movement and make attacker behaviour harder to distinguish from real users.

2) Common Credential Locations

The room highlights several places where credentials may appear inside a compromised environment:

Practical takeaway: credential access is not one technique, it is a collection of many collection points across disk, registry, memory, and the network.

3) Clear-Text Files and Registry Hunting

Some of the fastest wins come from careless storage.

These techniques are low-noise and should usually be checked before memory dumping.

4) Password Managers and Application Stores

Password managers and saved application credentials are another strong source of secrets.

Misconfiguration, weak protection, or local compromise can expose these stores to an attacker.

5) Local Accounts and the SAM Database

Windows stores local account information in the Security Account Manager (SAM) database.

This is one of the classic starting points for local credential dumping.

6) Volume Shadow Copy and Registry Hive Dumps

The room demonstrates two native ways to extract the files needed for local hash recovery.

Once transferred off-host, tools like secretsdump.py can decrypt and extract local hashes.

7) LSASS Memory

LSASS is one of the highest-value processes on a Windows system because it handles authentication material.

Why it matters: dumping LSASS can provide far more than local SAM hashes because it captures active authentication context rather than only static local account storage.

8) Dumping LSASS

The room shows multiple ways to capture LSASS memory for offline or direct analysis.

Because this is a well-known technique, defensive products often monitor or block it, so expect real-world friction here.

9) Mimikatz and Live Credential Extraction

Mimikatz is a central post-exploitation tool for Windows credential access.

This is one of the most direct ways to move from local admin access into reusable credential material.

10) AD and Network-Based Credential Sources

The room also reminds you that not all credential harvesting is purely local.

Exam Notes (PT1)