Credential Harvesting (Part 2)

By Ashwin Venugopal -

 






Local Security Authority Subsystem Service (LSASS)

The Windows process known as Local Security Authority Server Service (LSASS) manages and implements the operating system security policies on a machine. It checks passwords, hashes, and Kerberos tickets and confirms accounts that are currently logged in. In order to save users from having to enter credentials each time they connect, the Windows system saves credentials in the LSASS process. This allows users to access network resources including file sharing, SharePoint sites, and other network services.

However, because it retains private data about user accounts, penetration testers find the LSASS process to be a tasty target. Credential dumps are frequently used to elevate privileges, steal data, or move laterally using the LSASS. The LSASS process memory dump requires administrator access. The Windows operating system permits the production of dump files and snapshots of certain processes. To prevent LSASS from being accessed and used to get credentials from memory, Microsoft developed an LSA protection in 2012. 

Windows Credential Manager

Credential Manager is one of the Windows features to store logon-sensitive information for websites, applications, and networks. Login credentials like usernames, passwords, and internet addresses are also present in it. The four credential categories are:
  1. Web credentials contain authentication details stored in Internet browsers or other applications.
  2. Windows credentials contain Windows authentication details like NTLM or Kerberos.
  3. Generic credentials contain basic authentication details like clear-text usernames and passwords.
  4. Certificate-based credentials authenticates details based on certification.

Penetration tester can access the Windows Credential Manager via GUI or command prompt. Alternatively, a command-line built-in tool called RunAs can be used. It allows the running of Windows applications or tools under different users' permissions. It also contains the /savecred argument through which users can save his credentials in Windows Credentials Manager. Then, with Mimikatz the penetration tester can dump clear-text passwords stored in the Credential Manager from memory. 

Conclusion

This part talks about some credential harvesting techniques.














































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more