> For the complete documentation index, see [llms.txt](https://codex-7.gitbook.io/codexs-terminal-window/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codex-7.gitbook.io/codexs-terminal-window/ctf-solutions/cyber-defenders-discovery-camp-2021.md).

# Cyber Defenders Discovery Camp 2021

Team Name: Pogtopia

Final placement: 2nd runner up

![Final Placement](/files/OYV03yv0iywXCrrOXqGU)

![Challenges solved](/files/Dl5mRJ1HAxScLD5HuItd)

This was a CTF hosted by DSTA in 2021.\
The challenge categories in the CTF were:

**1. Lets Go Hunting - OSINT**

**2. Linux Rules The World! - Linux**

**3. Going Active - Active reconnaissance**

**4. Web Takedown 1 - Web (day 1)**

**5. Web Takedown 2 - Web (day 2)**

**6. File it Away - Pwn**

**7. Post Mortem - Forensics**

**8. Break It Down - Crypto**

**9. Behind The Mask - Windows/Active Directory**

I focused mostly on the OSINT, Linux, active recon, web and Windows AD categories due to their\
offensive nature, so the other categories may not be as well documented in this page.

Probably the least stable CTF infrastructure I've ever encountered. This CTF had technical\
difficulties from start to end, with the CTF being delayed a whole day, boxes being constantly\
down, challenges being able to be tampered with, an unstable CTF platform and lack of\
technical support, especially near the end.

In the final hours of the CTF, not just the linux challenges, but the pwn, web and other linux\
hosts were griefed and rendered unusable. While tampering with challenges is not permitted\
according to CTF rules, there should have been a reset system for the boxes, like in other\
CTFs.

With that said, I enjoyed playing with the Active Directory challenges, and learnt some new\
OSINT techniques along the way that might help with offensive operations in the future.

### Challenge Writeups

{% content-ref url="/pages/7zLMyKYNksXvXFz0nRvY" %}
[Lets Go Hunting](/codexs-terminal-window/ctf-solutions/cyber-defenders-discovery-camp-2021/lets-go-hunting.md)
{% endcontent-ref %}

{% content-ref url="/pages/paboyINxmgQMs6a206JH" %}
[Linux Rules The World!](/codexs-terminal-window/ctf-solutions/cyber-defenders-discovery-camp-2021/linux-rules-the-world.md)
{% endcontent-ref %}

{% content-ref url="/pages/CBLbTHqmfQt2lnDFgCM0" %}
[Going active](/codexs-terminal-window/ctf-solutions/cyber-defenders-discovery-camp-2021/going-active.md)
{% endcontent-ref %}

{% content-ref url="/pages/NAuaKZa0FcagTipu3U8q" %}
[File it away](/codexs-terminal-window/ctf-solutions/cyber-defenders-discovery-camp-2021/file-it-away.md)
{% endcontent-ref %}

{% content-ref url="/pages/b2yN4K3ZxSFXdQ1y3y51" %}
[Behind the mask](/codexs-terminal-window/ctf-solutions/cyber-defenders-discovery-camp-2021/behind-the-mask.md)
{% endcontent-ref %}

Some challenges we solved could not be properly documented due to challenge hosts being\
taken offline shortly after the CTF ended.


---

# 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://codex-7.gitbook.io/codexs-terminal-window/ctf-solutions/cyber-defenders-discovery-camp-2021.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.