Skip to content

notetaking-organization.md

Latest commit

 

History

History
313 lines (259 loc) · 9.14 KB

notetaking-organization.md

File metadata and controls

313 lines (259 loc) · 9.14 KB

Notetaking & Organization

🎯 Overview

Thorough notetaking is critical during assessments. Notes and tool output become the raw inputs for reports - typically the only deliverable clients see. Organized documentation saves time during reporting and provides essential references for client questions and team collaboration.

📋 Essential Notetaking Structure

Core Categories

# Primary sections for comprehensive documentation:
1. Attack Path           # Complete exploitation chain with screenshots
2. Credentials          # Centralized credential tracking
3. Findings            # Individual vulnerabilities with evidence
4. Vulnerability Scan Research    # Scanner analysis and research
5. Service Enumeration Research   # Service investigation notes
6. Web Application Research      # Web app discoveries and testing
7. AD Enumeration Research       # Active Directory investigation
8. OSINT                # Open source intelligence gathering
9. Administrative Information    # Contacts, objectives, RoE
10. Scoping Information         # IP ranges, URLs, provided credentials
11. Activity Log               # High-level activity tracking
12. Payload Log               # Uploaded files and cleanup tracking

Folder Structure

# Recommended directory organization:
mkdir -p PROJECT/{Admin,Deliverables,Evidence/{Findings,Scans/{Vuln,Service,Web,'AD Enumeration'},Notes,OSINT,Wireless,'Logging output','Misc Files'},Retest}

# Result:
PROJECT/
├── Admin/                    # SOW, kickoff notes, status reports
├── Deliverables/            # Reports, spreadsheets, presentations
├── Evidence/
│   ├── Findings/           # Per-finding evidence folders
│   ├── Scans/
│   │   ├── Vuln/          # Vulnerability scanner output
│   │   ├── Service/       # Nmap, Masscan results
│   │   ├── Web/           # Burp, ZAP, EyeWitness data
│   │   └── AD Enumeration/ # BloodHound, PowerView data
│   ├── Notes/              # Structured note files
│   ├── OSINT/             # Intelligence gathering output
│   ├── Wireless/          # WiFi testing results
│   ├── Logging output/    # Tmux, tool logs
│   └── Misc Files/        # Payloads, scripts, tools
└── Retest/                # Retest evidence (separate)

🛠️ Recommended Tools

Notetaking Applications

# Local storage (secure for client data):
- Obsidian           # Markdown-based, local storage
- CherryTree         # Hierarchical notes
- Notion (local)     # All-in-one workspace
- Visual Studio Code # Code editor with markdown

# Cloud-based (training only):
- GitBook           # Documentation platform
- Outline           # Team collaboration
- Standard Notes    # Encrypted notes
- Evernote          # Traditional note-taking

Session Logging

# Terminal logging solutions:
- Tmux + logging plugin    # Comprehensive session logging
- Script command          # Built-in Unix logging
- Terminator logging      # GUI terminal logging
- Windows Terminal        # Windows PowerShell logging

📺 Tmux Logging Setup

Installation

# Clone Tmux Plugin Manager
git clone https://github.com/tmux-plugins/tpm ~/.tmux/plugins/tpm

# Create configuration file
cat > ~/.tmux.conf << EOF
# List of plugins
set -g @plugin 'tmux-plugins/tpm'
set -g @plugin 'tmux-plugins/tmux-sensible'
set -g @plugin 'tmux-plugins/tmux-logging'

# Increase history limit
set -g history-limit 50000

# Initialize TMUX plugin manager (keep at bottom)
run '~/.tmux/plugins/tpm/tpm'
EOF

# Apply configuration
tmux source ~/.tmux.conf

Usage

# Start new session
tmux new -s assessment

# Install plugins (first time)
# Press: Ctrl+B, Shift+I

# Start logging current session
# Press: Ctrl+B, Shift+P

# Stop logging
# Press: Ctrl+B, Shift+P (again)

# Retroactive logging (save current pane)
# Press: Ctrl+B, Alt+Shift+P

# Screen capture of current pane
# Press: Ctrl+B, Alt+P

# Clear pane history
# Press: Ctrl+B, Alt+C

Key Bindings

# Essential Tmux commands:
Ctrl+B, Shift+%     # Split panes vertically
Ctrl+B, Shift+"     # Split panes horizontally  
Ctrl+B, O           # Switch between panes
Ctrl+B, Shift+P     # Start/stop logging
Ctrl+B, Alt+Shift+P # Retroactive logging
Ctrl+B, Alt+P       # Screen capture

📊 Evidence Collection

What to Capture

# High-priority evidence:
- Command execution and output
- Screenshots of GUI applications
- Network scan results
- Vulnerability scanner output
- Successful exploitation attempts
- Failed attempts (for thoroughness)
- System information and configuration
- Credential discoveries

Screenshot Best Practices

# Technical guidelines:
- Include address bar in browser screenshots
- Crop to relevant information only
- Add minimal border for document contrast
- Use annotations (arrows, boxes) for clarity
- Redact credentials and PII properly

# Redaction methods:
✅ Solid black bars (secure)
❌ Pixelation/blurring (reversible)
❌ CSS/HTML styling (easily bypassed)

Terminal Output Formatting

# Preferred: Copy-paste terminal text
# Benefits:
- Easier redaction and highlighting
- Smaller file sizes
- Copy-paste friendly for client reproduction
- Professional appearance

# Format example:
┌─[htb-student]─[10.10.14.3]─[~/tools]
└──╼ $ crackmapexec smb 172.16.5.5 -u administrator -p '<REDACTED>'
SMB    172.16.5.5    445    DC01    [+] INLANEFREIGHT.LOCAL\administrator:<REDACTED> (Pwn3d!)

📝 Artifact Tracking

Payload Documentation

# Essential tracking information:
- Timestamp of payload deployment
- Target host IP/hostname
- File path on target system
- File hash (SHA256/MD5)
- Cleanup status (removed/needs cleanup)
- Purpose/functionality of payload

System Modifications

# Required documentation:
- Host IP/hostname where change was made
- Timestamp of modification
- Description of change made
- Location of change on host
- Application/service affected
- Account created (if applicable)
- Reversion status and procedures

Sample Tracking Format

## Payload Log

| Timestamp | Host | Path | Hash | Status | Notes |
|-----------|------|------|------|--------|-------|
| 2025-01-15 14:30 | 10.10.10.50 | C:\temp\shell.exe | a1b2c3d4... | Removed | Reverse shell payload |
| 2025-01-15 15:45 | 10.10.10.51 | /var/www/html/cmd.php | e5f6g7h8... | Needs cleanup | Web shell |

## Account Modifications

| Timestamp | Host | Change | Account | Status |
|-----------|------|--------|---------|--------|
| 2025-01-15 16:00 | DC01 | User created | testuser | Removed |
| 2025-01-15 16:15 | WEB01 | Added to Admins | htb-user | Reverted |

🎯 HTB Academy Lab Solutions

Lab Questions

# Question 1: Session logging tool
# Answer: tmux

# Question 2: Vertical pane split key combination
# Answer: [Ctrl] + [B] + [Shift] + [%]

Practical Exercises

# Optional lab access:
xfreerdp /v:10.129.203.82 /u:htb-student /p:HTB_@cademy_stdnt!

# Activities:
1. Explore Obsidian sample notebook
2. Practice Tmux logging setup
3. Test pane splitting and navigation
4. Experiment with evidence organization

🔄 Assessment Workflow

Pre-Assessment Setup

# 1. Create project directory structure
mkdir -p CLIENT-ASSESSMENT/{Admin,Deliverables,Evidence/{Findings,Scans/{Vuln,Service,Web,'AD Enumeration'},Notes,OSINT,'Logging output','Misc Files'}}

# 2. Initialize notetaking tool (Obsidian/CherryTree)
# 3. Configure Tmux logging
# 4. Set up evidence collection templates

During Assessment

# Continuous documentation:
- Log all commands and output
- Screenshot significant findings
- Track credentials in centralized location
- Document failed attempts for thoroughness
- Maintain activity timeline
- Track all uploaded files and modifications

Post-Assessment

# Report preparation:
- Organize evidence by findings
- Redact sensitive information
- Verify command reproducibility
- Clean up temporary files
- Archive complete assessment data

⚠️ Data Handling Guidelines

What NOT to Collect

# Avoid collecting:
- Unredacted PII (personal information)
- Potentially criminal content
- Legally discoverable documents
- Sensitive file contents (screenshot directory listing instead)
- Client proprietary information beyond scope

Compliance Considerations

# Legal obligations:
- GDPR compliance for EU clients
- Data retention policies
- Secure storage requirements
- Client data handling agreements
- Evidence chain of custody

💡 Key Takeaways

  1. Structured approach essential for comprehensive documentation
  2. Tmux logging provides complete session recording
  3. Evidence organization saves time during reporting
  4. Proper redaction protects sensitive information
  5. Terminal output preferred over screenshots when possible
  6. Artifact tracking critical for professional assessments
  7. Tool selection should match company policies and client requirements

Effective notetaking and organization form the foundation of professional penetration testing deliverables and ensure comprehensive evidence collection throughout assessments.