# Staying Organized

1. Make sure that your project folders are well organized
2. Have a clear folder structure in your attack machine to save data

```shell-session
Projects/
└── Acme Company
    ├── EPT [ external penetration test ]
    │   ├── evidence
    │   │   ├── credentials
    │   │   ├── data
    │   │   └── screenshots
    │   ├── logs
    │   ├── scans
    │   ├── scope
    │   └── tools
    └── IPT [ internal penetration test ]
        ├── evidence
        │   ├── credentials
        │   ├── data
        │   └── screenshots
        ├── logs
        ├── scans
        ├── scope
        └── tools
```

Keeping penetration testing structured can save time.

1. Create a folder for each target host and save screenshots within it
2. Organize notes by host or network and save screenshots directly into the note-taking tool.

Note-taking tools:

* <https://www.giuspen.com/cherrytree>
* <https://www.notion.so/>
* <https://notepad-plus-plus.org/downloads>
* <https://code.visualstudio.com/>
* <https://www.gitbook.com/>
* <https://evernote.com/>
* <https://www.sublimetext.com/>

> build a findings/vulnerability database include a finding title, description, impact, remediation advice, and references.

1. Aggregating every payload, command
2. Maintain checklists
3. Maintain report templates for various assessment types
4. Build a findings/vulnerability database


---

# 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://purplebyteone.gitbook.io/index/notes/education/base/purple-team/htb/htb-academy/job-role-path/penetration-tester/getting-started/staying-organized.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.