Credential Harvesting (Part 3)

By Ashwin Venugopal -

 






Domain Controller

New Technologies Directory Services (NTDS) is a database that contains all Active Directory data, including objects, attributes, credentials, etc. The NTDS.DTS data consists of following three tables:
  1. Schema Table contains types of objects and their relationships. 
  2. Link Table contains the object's attributes and their values.
  3. Data Type contains users and groups.

Ntdsutil is a Windows utility tool to manage and maintain Active Directory configurations. It can be used to:

  1. Restore deleted objects in AD.
  2. Perform maintenance for the AD database.
  3. AD snapshot management.
  4. Set Directory Services Restore Mode (DSRM) administrative passwords.

Local dumping is usually done if there are no credentials available but there is administrator access to the domain controller. Also, the popular attack DC Sync can be used to dump credentials remotely. The penetration tester can leverage these configurations to perform domain replication. 

Local Administrator Password Solution (LAPS)

There is a built-in Administrator account in a Windows OS, that can be accessed via password. But changing passwords in a large Windows environment is challenging. Hence, Microsoft used Group Policy Preference (GPP) to implement a method for changing local administrator accounts across workstations.

After the deployment of GPP, different XML files are created in the SYSVOL folder. However, in 2015, Microsoft stopped storing the encrypted password in the SYSVOL folder and introduced Local Administrator Password Solution. LAPS offers a much more secured approach to remotely manage the local administrator password. 

This new method includes two new attributes of computer objects in AD. One of them contains a clear-text password of the local administrator, while the other contains the expiration time to reset the password. There are many other attacks to obtain credentials from memory or various files within the Windows operating system, they are:
  1. Kerberoasting.
  2. AS-REP Roasting.
  3. SMB Relay Attack.
  4. LLMNR/NBNS Poisoning.

Conclusion:

This marks the end of Credential harvesting related topics here.








 



































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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more