Active Directory (Part 10.2)

By Ashwin Venugopal -

 





Enumeration

Some of the methods that can be used to enumerate AD are as follows:

  • Command Prompt: Many situations requires quick information gathering of an AD environment via Command Prompt. It may be because RDP access to a system is not available, if PowerShell use is being monitored by defenders, or if the penetration tester is using a Remote Access Trojan (RAT) for the access. The Command Prompt (CMD) tool contains an in-built command called net. This command is used to gather information about the local system and AD. It can also be useful for quick enumeration of AD information or even be included in phishing payloads to hep gather information to stage a final attack. Hence, it allows the gathering of a variety of information on an AD environment. 

         Information gathered via net command can be used in planning additional password spraying                 attacks against other enumerated user accounts. The only problem a tester might face is that the               net commands must be executed from a domain-joined machine. If it is is not joined, then it will             default to the WORKGROUP domain. Also, sometimes the net commands may not show all the              information.

  • PowerShell: It is an upgrade of Command Prompt, first released in 2006. It offers access to cmdlets (pronounced command-lets), which are ,NET classes to perform specific functions, along with the standard functionalities. There are 50+ build-in cmdlets listed in AD-RSAT. These PowerShell cmdlets can enumerate more information than the net commands. They allow the user to specify the server and domain to execute these commands using runas from a non-domain-joined machine. Own cmdlets can also be created for enumeration. Additionally, penetration testers can also use the AD-RSAT cmdlets to directly change AD objects, like reset password or add a user to a specific group.

          Its main disadvantage is that PowerShell is more often monitored by blue teams than command              prompt. This complicates things for the attackers, making the evasion harder. Also, the required              installation of AD-RSAT tool may lead to detection.

  • Bloodhound- It is an excellent tool widely used by the penetration testers to gather and analyze information of an AD environments. It allows the quick gathering and visualization of data about the relationship between different AD objects and users, helping in easy identification of potential vulnerabilities and attack paths within the environment. It uses graph theory, making it much easier to identify the privilege escalation paths and other weaknesses. It also includes a wide variety of built-in queries and reports, along with the ability to create custom queries reports to gather more targeted data. 

          However, users often confuse Sharphound with Bloodhound. Sharphound is a tool that is used in            conjunction with Bloodhound. It is specially designed to be run a system within the AD                          environment and collect data about it. That data can be imported into Bloodhound for analysis                and visualization.

AD enumeration is a massive task. Its accurate enumeration is very much necessary for better understanding of the domain's structure and identify potential exploitation paths to gain increased system privileges or access of other resources. So, some other enumerating techniques include:

  • LDAP Enumeration- Any valid AD credential pair should be able to bind to a Domain Controller's LDAP interface. It allows the penetration tester to write LDAP search queries to enumerate information regarding the AD objects in the domain. 

  • PowerView- It is a recon script part of the PowerSploit project. The PowerView scripts can prove incredibly useful in performing semi-manual enumeration of AD objects.

  • Windows Management Instrumentation (WMI)- It can be used to enumerate information from Windows hosts and has a provider that can be used to interact with AD.

Conclusion

This is the continuation of the Enumeration part and explores more factors about the topic. 



























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