# Infographics

{% hint style="info" %}
None of the actual content is new or special. It's just my own representation of commonly available information to help remember and visualize some of the basic stuff.
{% endhint %}

## DHCP Basics

<figure><img src="/files/UV2AeTlhFs1uRm8cYkkL" alt=""><figcaption><p>Basic dynamic host configuration protocol (DHCP) communication for an initial IP address assignment</p></figcaption></figure>

## Kerberoasting

![Very basic workflow of a kerberoasting attack](/files/fBhlnyNcdPYAYd2C3fyI)

## Kerberos Authentication

<figure><img src="/files/Auj67NvjYWu1RntMp6Z8" alt=""><figcaption><p>Basic kerberos authentication flow (see <a href="https://web.archive.org/web/20230708145448/https://en.wikipedia.org/wiki/Kerberos_%28protocol%29">here</a> for a cleaner visual representation)</p></figcaption></figure>

## Network Topology - Physical 3-Tier-Model

<figure><img src="/files/73RDXhCP69VG9R1qZpWW" alt=""><figcaption><p>Example of the classical 3-layer network architecture with some basic information on common concepts surrounding this model</p></figcaption></figure>

## OAuth2 Basics

<figure><img src="/files/5TC3bdjJXzy3uonVfaIS" alt=""><figcaption><p>Basic workflow of an OAuth2 authorization (OAuth2 is an authorization protocol - do not use for authentication)</p></figcaption></figure>

## Pivoting

![A small high level overview of pivoting possibilities](/files/b7h4Na3oFm9z1jPxJKB0)

## Resource Based Constrained Delegation (RBCD) via WebDAV

<figure><img src="/files/qtRzjzGCJtyTeCspMDKZ" alt=""><figcaption><p>Cheatsheet for abusing WebDAV for privilege escalation, setting up RBCD to gain access</p></figcaption></figure>

## SSH Local Port Forwarding

![Visualizing SSH port forwarding based on this great explanation](/files/X92hqugwM4v3mwZttuIN)

## SSH Remote Port Forwarding

![Visualizing SSH port forwarding based on this great explanation](/files/VQ3FoCi5CjfGJo84Xn3U)

## The Basic Heap Layout

<figure><img src="/files/NePU2F6fHX0gfx3cd9BQ" alt=""><figcaption><p>A basic representation of allocated and free chunks on the heap</p></figcaption></figure>

## The Cyber Kill Chain

![Yet another visualization of Lockheed Martin's "Cyber Kill Chain"](/files/-MhmRJjjadtntsLZ2ezd)

## The Domain Name System

![A simplified overview of the steps involved in DNS](/files/-MhmSQfDlLJC-xytctXo)

## The OSI and TCP/IP Model

![The Open Systems Interconnection model](/files/-MhmPvWOSqMAvOZrBY9n)

## The Penetration Testing Execution Standard

<figure><img src="/files/4cd1LWwLfLpqlmnyJggG" alt=""><figcaption><p>Visualisation of the seven steps of the Penetration Testing Execution Standard (PTES)</p></figcaption></figure>

## The PNG File Structure

![Structure of a PNG file that might help for a CTF](/files/68EsEpz8GMA7wbMS69rC)

## The (32-bit) Stack Layout&#x20;

![A detailed representation of the stack layout during a function call on a 32-bit processor](/files/-MhmTTV5XQn3lxe_Ae5C)

## The Sudoers File

Check [the official documentation](https://www.sudo.ws/man/1.8.13/sudoers.man.html) for a complete list of available options and values.

![A small guide for entries in the /etc/sudoers file including the most common options](/files/2RVcUGwN6ejSuRscUgGu)

## The VirtualBox NatNetwork

This diagram shall visualize the default addresses in a NatNetwork in VirtualBox as most [documentation](https://docs.oracle.com/en/virtualization/virtualbox/6.0/admin/changenat.html) seems a bit unclear or not accurate. Analyzing some basic network traffic we can determine the following structure though.

![](/files/wNug073UVfBmX6plD7CQ)

{% hint style="info" %}
The infographics were created using <https://www.canva.com> and <https://www.draw.io>.
{% endhint %}

##


---

# Agent Instructions: 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:

```
GET https://ccat.gitbook.io/cyber-sec/infographics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.