Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS). After a user logs on, the system generates and stores a variety of credential materials in LSASS process memory. These credential materials can be harvested by an administrative user or SYSTEM and used to conduct Lateral Movement using Use Alternate Authentication Material.

As well as in-memory techniques, the LSASS process memory can be dumped from the target host and analyzed on a local system.

For example, on the target host use procdump:

Locally, mimikatz can be run using:

Built-in Windows tools such as comsvcs.dll can also be used:

Similar to Image File Execution Options Injection, the silent process exit mechanism can be abused to create a memory dump of lsass.exe through Windows Error Reporting (WerFault.exe).[3]

Windows Security Support Provider (SSP) DLLs are loaded into LSASS process at system start. Once loaded into the LSA, SSP DLLs have access to encrypted and plaintext passwords that are stored in Windows, such as any logged-on user's Domain password or smart card PINs. The SSP configuration is stored in two Registry keys: HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages and HKLM\SYSTEM\CurrentControlSet\Control\Lsa\OSConfig\Security Packages. An adversary may modify these Registry keys to add new SSPs, which will be loaded the next time the system boots, or when the AddSecurityPackage Windows API function is called.[4]

The following SSPs can be used to access credentials:

References

  1. Gruzweig, J. et al. (2021, March 2). Operation Exchange Marauder: Active Exploitation of Multiple Zero-Day Microsoft Exchange Vulnerabilities. Retrieved March 3, 2021.
  2. Symantec. (2021, June 10). Attacks Against the Government Sector. Retrieved September 28, 2021.
  3. Gilboa, A. (2021, February 16). LSASS Memory Dumps are Stealthier than Ever Before - Part 2. Retrieved December 27, 2023.
  4. Graeber, M. (2014, October). Analysis of Malicious Security Support Provider DLLs. Retrieved March 1, 2017.
  5. Wilson, B. (2016, April 18). The Importance of KB2871997 and KB2928120 for Credential Protection. Retrieved April 11, 2018.

Kwistjonijiet marbuta

Links
Tip ta’ link Kwistjoni
is related to Techniques
is blocked by Operating System Configuration
is blocked by Credential Access Protection
is blocked by Detection of Credential Dumping from LSASS Memory via Access and Dump Sequence
is blocked by Privileged Process Integrity
is blocked by Privileged Account Management
is blocked by User Training
is blocked by Behavior Prevention on Endpoint
is blocked by Password Policies
is blocked by Prohibition Of Changes
is blocked by Statutory, Regulatory & Contractual Compliance
is blocked by Configuration Management Program
is blocked by Least Functionality
is blocked by Continuous Monitoring Policy
is blocked by Encrypting Data In Transit
is blocked by Malicious Code Protection (Antimalware)
is blocked by Personnel Transfer
is blocked by Identity & Access Management (IAM)
is blocked by Privileged Account Management (PAM)
is blocked by Password-Based Authentication
is blocked by Authenticator Feedback
is blocked by Restrictions on Shared Groups / Accounts
is blocked by Data Flow Enforcement – Access Control Lists (ACLs)
is blocked by Alignment With Enterprise Architecture
is blocked by Security Function Isolation
is blocked by Vulnerability Ranking
is blocked by Access Restriction For Change
is blocked by Executive Leadership Oversight of Security, Compliance & Resilience Controls
is blocked by Secure Baseline Configurations
is blocked by Continuous Monitoring
is blocked by Encrypting Data At Rest
is blocked by Separation of Duties (SoD)
is blocked by Account Management
is blocked by Authenticator Management
is blocked by Access Enforcement
is blocked by Least Privilege
is blocked by Identification & Authentication for Organizational Users
is blocked by Process Isolation
is blocked by Memory Protection
is blocked by Software & Firmware Patching