Active Directory (Part 12.3)

By Ashwin Venugopal -

 






Exploitation

Several methods can be used to exploit misconfiguration in an Active Directory environment. Such methods includes AD delegation, forcing authentication relays, targeting AD users, domain trusts, and using Group Policy Objects or Silver and Golden Tickets. Other methods can also be used according to the AD environment.

Certificates- AD Certificate Services (AD CS) is Microsoft's Public Key Infrastructure (PKI) implementation. AD CS is used for many things like encrypting file systems, creating and verifying digital signatures, and user authentication, making it a promising avenue for attackers.

It is a privileged function and generally runs on selected domain controllers. So, normal users cannot really interact with the service directly. Administrators of AD CS can create several templates that can allow any user relevant permissions to request a certificate themselves. Hence, to find a vulnerable template, the penetration tester must enumerate the available ones and check for certain characteristics indicating vulnerability. 

A vulnerable temple is one which has the characteristics easy to attack and exploit. Some of the characteristics include:
  • Allowing key archival- key archival allows the private key associated with the certificate to be backed up and restored, which can be a potential vulnerability if the key is not secured. 

  • Allowing private key export- it may allow an attacker to extract the private key associated with the certificate and use it to impersonate the owner of the certificate.

  • Allowing key recovery- key recovery allows the private key linked with the certificate to be recovered if it is lost or forgotten, which is a potential vulnerability if the recovery process is not properly secured.

Domain Trusts- They allow the user of one domain to access resources in another domain. They establish a connection between domains in an AD network and outline how they can communicate with each other. Some of the different types of domain trusts are:
  • Parent-child trusts- These trusts are established between a parent domain and a child domain that is a subdomain of a parent.

  • Shortcut trusts- These trusts are established between two domains in the same forest to allow users of one domain access to resources present in another domain more quickly.

  • External trusts- These trusts are established between two domains of different forests to allow users in one domain access to the resources in another domain. 

  • Forest trusts- these trusts are established between two forests to allow users in one forest access to the resources in another forest.

The two main types of trusts that can be configured between domains are:

  1. Directional- The direction of trust flows from a trusting domain to a trusted domain.
  2. Transitive- The trust relationship expands beyond just two domains to include other trusted domains.

However, domain trusts can be vulnerable to various types of attacks, including:

  • Trust spoofing- In this type of attack, an attacker creates fake trust between two domains to gain access to resources that are normally restricted to users in the trusted domain. 

  • Trust hijacking- In this attack, an attackers takes control of an existing trust between two domains to gain access to resources that are normally restricted to users in the trusted domain.

  • Trust elevation- This attack involves an attacker using a trust relationship to gain higher privileges than they would normally have in a domain.

Conclusion:

This part discuss the remaining exploitation methods of Active Directory. With this, the Active directory topic and its related sub topics are complete.


















Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more