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

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