Trust Direction: An Enabler for Active Directory Enumeration and Trust Exploitation
Active Directory (AD) Trusts have been a hot topic as of late. In this blog entry, we are going to focus on theoretical examples based on two separate forest domains – A and B. Domain A and Domain B are autonomous and are not members of the same AD forest. However, the trust relationship will change in context of the examples to understand the principle of trust direction. Some Background Info In essence, AD Trusts establish the authentication mechanism between domains and/or forests. AD Trusts allow for resources (e.g. security principals such as users) in one domain to honor the authentication to access resources in another domain. Of note, it is important to understand that simply establishing a trust relationship between two domains does not allow for resources from a theoretical Domain A to access resources in a theoretical Domain B. Resources in Domain A must be authorized (e.g. given permission) to access resources in a theoretical Domain B.
FEATURES
EXPLORE BY TAGS
SIMILAR TOOLS
A list of disposable email domains to detect or block disposable accounts
Encrypt Kubernetes Secrets into SealedSecrets for safe storage and controlled decryption within the cluster.
A PHP OAuth 2.0 authorization server implementation with support for various grants and RFCs.
PINNED

Checkmarx SCA
A software composition analysis tool that identifies vulnerabilities, malicious code, and license risks in open source dependencies throughout the software development lifecycle.

Orca Security
A cloud-native application protection platform that provides agentless security monitoring, vulnerability management, and compliance capabilities across multi-cloud environments.

DryRun
A GitHub application that performs automated security code reviews by analyzing contextual security aspects of code changes during pull requests.