> For the complete documentation index, see [llms.txt](https://alomancy.gitbook.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alomancy.gitbook.io/guides/beginners/getting-started.md).

# Getting Started

## Learning By Videos

For Those that like watching videos and going through structured courses I would recommend looking at some free courses on one of the following:

* <https://cybrary.it>
* <https://www.hacker101.com/sessions/introduction.html>

## Learning By Practice

For those that like to dive in at the deep end and hope they float. There is only really one resource that is "noob" friendly and that is the complete beginner path from tryhack me:

* ​<https://tryhackme.com/paths>

![](/files/-MYcFtqZDts7Obi7z7Ct)

## Other Resources

Another great place to find help and information is on twitch/youtube. The List below shares InfoSec Streamers that are more than likely to either be learning themselves. Or be more than willing to answer any questions:

* <https://infosecstreams.github.io/>

## Cert Path

Sec+ > PT+ PEH -> {eCPPT -> OSCP} -> {CRTP -> CRTO -> eCPTX}


---

# 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://alomancy.gitbook.io/guides/beginners/getting-started.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.