Security Account Manager
Parent: T1003
Description
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored. The SAM is a database file that contains local accounts for the host, typically those found with the <code>net user</code> command. Enumerating the SAM database requires SYSTEM level access. A number of tools can be used to retrieve the SAM file through in-memory techniques: * pwdumpx.exe * [gsecdump](https://attack.mitre.org/software/S0008) * [Mimikatz](https://attack.mitre.org/software/S0002) * secretsdump.py Alternatively, the SAM can be extracted from the Registry with Reg: * <code>reg save HKLM\sam sam</code> * <code>reg save HKLM\system system</code> Creddump7 can then be used to process the SAM database locally to retrieve hashes.(Citation: GitHub Creddump7) Notes: * RID 500 account is the local, built-in administrator. * RID 501 is the guest account. * User accounts start with a RID of 1,000+.
Mapped SPARTA techniques
No techniques mapped to this control.
Cross-framework references
Relationships published by the source frameworks themselves, reproduced here with attribution. They are not SafeMode Space mappings and carry no confidence rating of ours.
Countered by 14 in MITRE D3FEND (Defensive Techniques)
- D3-ABPIApplication-based Process Isolation
- D3-DIData Inventory
- D3-HBPIHardware-based Process Isolation
- D3-HRHost Reboot
- D3-HSHost Shutdown
- D3-KBPIKernel-based Process Isolation
- D3-PLAProcess Lineage Analysis
- D3-PSProcess Suspension
- D3-PSAProcess Spawn Analysis
- D3-PSMDProcess Self-Modification Detection
- D3-PTProcess Termination
- D3-RDRestore Database
- D3-SCFSystem Call Filtering
- D3-WSAMWeb Session Access Mediation
Cite as SafeMode Space, mitre-attack-enterprise T1003.002.