Cybersecurity Research & Documentation

Cosmas Saidi

Security Analyst | Penetration Tester

Welcome to my cybersecurity documentation hub. Here I document my journey through hands-on security training platforms, CTF challenges, and practical labs. This portfolio represents real skills acquired through offensive security practice—from Linux fundamentals to privilege escalation techniques.

Every writeup and note represents practical, lab-validated learning from pwn.college, Hack The Box, and TryHackMe across offensive and defensive workflows.

3
Platforms
10+
Writeups
20+
Commands
cosmas@kali:~
┌──(cosmas㉿kali)-[~]
└─$ whoami
cosmas_saidi
└─$ cat /etc/mission
Building offensive security skills
through hands-on practice and CTFs
└─$ ls ./skills
networking enumeration web_security scripting
└─$ cat ./platforms
pwn.college | TryHackMe | HackTheBox
└─$

Knowledge Base

Hands-on concepts and methodology documentation from cybersecurity training platforms. Expand each section to view detailed writeups.

PWN

pwn.college

+

File Permissions

Linux
Goal

Understand Linux file permissions and how to modify them for security hardening and exploitation.

My Approach
  • Used ls -la to view file permissions in detail
  • Identified permission bits (rwx for user, group, others)
  • Used chmod to change permissions using octal and symbolic notation
  • Understood SUID/SGID bits for privilege escalation research
Commands Used
ls -la                    # View detailed permissions
chmod 755 filename        # rwxr-xr-x (owner: full, others: read/execute)
chmod +x script.sh        # Add execute permission
chmod 600 secret.txt      # rw------- (owner only)
chmod u+x,g-w file        # Symbolic notation
Permission Reference
OctalPermissionMeaning
7rwxRead, Write, Execute
6rw-Read, Write
5r-xRead, Execute
4r--Read only
0---No permissions
Concepts Learned
  • Permissions are split into: owner, group, others
  • r=4, w=2, x=1 (octal notation)
  • chmod changes file permissions
  • Execute permission needed to run scripts
  • SUID (4000) runs program as file owner
⚠ Security Lesson

Misconfigured permissions can expose sensitive files. Always use minimum required permissions. Never use chmod 777 in production—it allows anyone to read, write, and execute.

Environment Variables

Linux
Goal

Learn how environment variables work and affect program execution for both system administration and exploitation.

My Approach
  • Viewed current variables with env
  • Set variables with export
  • Understood how PATH affects command lookup order
  • Explored variable scope (parent vs child processes)
Commands Used
env                       # View all environment variables
echo $PATH                # View specific variable
export MYVAR="value"      # Set and export variable
printenv                  # Alternative to env
unset MYVAR               # Remove variable
Important Variables
VariablePurposeSecurity Impact
PATHCommand search pathPATH hijacking attacks
LD_PRELOADLibraries to preloadCode injection
HOMEUser home directoryConfig file locations
SHELLDefault shellExecution context
Concepts Learned
  • Environment variables store system and user settings
  • PATH determines where shell looks for commands
  • Variables can be temporary or exported to child processes
  • export makes variable available to subprocesses
⚠ Security Lesson

Never store secrets in environment variables visible to other processes. PATH manipulation can be used for privilege escalation if privileged scripts call commands without full paths.

Shell Scripting Basics

Linux
Goal

Learn basic shell scripting for automation of security tasks and enumeration.

My Approach
  • Created scripts with shebang #!/bin/bash
  • Made scripts executable with chmod +x
  • Used command substitution for dynamic values
  • Built enumeration automation scripts
Script Structure
#!/bin/bash
# Shebang specifies interpreter

echo "Hello, World!"

# Variables
VAR="value"
echo $VAR

# Command substitution
RESULT=$(whoami)
echo "Current user: $RESULT"

# Make executable and run
chmod +x script.sh
./script.sh
Concepts Learned
  • Scripts need shebang line to specify interpreter
  • Command substitution: $(command) or backticks
  • Scripts need execute permission to run
  • Variables: no $ when assigning, $ when reading
⚠ Security Lesson

Always validate input in scripts. Never run untrusted scripts with elevated privileges. Be cautious of command injection through unvalidated user input.

Process Control

Linux
Goal

Learn to manage processes in Linux for system administration and security analysis.

My Approach
  • Started background processes with &
  • Used fg to bring to foreground
  • Used bg to continue stopped processes
  • Switched users with su
  • Analyzed running processes for suspicious activity
Commands Used
command &                 # Run in background
fg                        # Bring to foreground
bg                        # Continue in background
jobs                      # List current jobs
Ctrl+Z                    # Suspend current process
ps aux                    # List all processes
ps auxf                   # Process tree
su username               # Switch user
kill PID                  # Terminate process
kill -9 PID               # Force kill
Key Process Information
ColumnMeaning
PIDProcess ID
PPIDParent process ID
USERProcess owner
%CPUCPU usage
COMMANDWhat's running
Concepts Learned
  • & runs command in background
  • Ctrl+Z suspends current process
  • fg brings background job to foreground
  • jobs lists current shell jobs
  • su switches user context
⚠ Security Lesson

Background processes can persist after logout. Identify services running as root. Find processes with network connections. Detect hidden or suspicious processes during investigation.

PATH Manipulation

Linux
Goal

Understand how PATH affects command execution and how it can be exploited for privilege escalation.

My Approach
  • Examined current PATH configuration
  • Modified PATH to include custom directories
  • Understood command resolution order (left to right)
  • Practiced PATH hijacking techniques
Commands Used
echo $PATH                # View current PATH
export PATH=/my/dir:$PATH # Prepend directory
which command             # Find command location

# Dangerous: current directory in PATH
export PATH=".:$PATH"     # DON'T do this!
Concepts Learned
  • PATH is searched left to right for commands
  • First match is executed
  • Adding directory to PATH allows running scripts without full path
  • Prepending vs appending to PATH matters for security
⚠ Security Lesson

PATH manipulation is a classic privilege escalation technique. If a privileged script calls commands without full paths (e.g., cat instead of /bin/cat), an attacker can hijack execution by placing malicious binaries in an earlier PATH directory.

Piping & Redirection

Linux
Goal

Learn to chain commands using pipes and control input/output redirection.

My Approach
  • Used | to send output of one command to another
  • Combined with text processing tools
  • Built command pipelines for data extraction
  • Redirected output to files for logging
Commands Used
cat file | head           # Pipe to head
ls | grep pattern         # Filter output
cmd1 | cmd2 | cmd3        # Chain multiple commands
cat file | tr 'a' 'b'     # Translate characters

# Redirection
command > file            # Redirect output to file (overwrite)
command >> file           # Append to file
command < file            # Read input from file
2>&1                      # Redirect stderr to stdout
Concepts Learned
  • | sends stdout of left command to stdin of right command
  • Pipes allow chaining multiple commands
  • head shows first lines/bytes
  • tr translates characters
  • Redirection controls where output goes
⚠ Security Lesson

Be careful piping sensitive data—intermediate commands may log or expose information. Use pipes for chaining security tools efficiently during enumeration.

Data Dealings (Binary Basics)

Binary
Goal

Understand encoding, data representation, and byte-level manipulation for binary analysis.

Concepts Learned
  • UTF-8 encoding and byte representation
  • Encoding vs encryption (encoding is reversible, not secure)
  • Base64 and hex encoding/decoding
  • Obfuscation ≠ security
  • Reading program logic to reverse transformations
  • Handling raw bytes in CLI
Commands Used
# Base64
echo -n "hello" | base64          # Encode
echo "aGVsbG8=" | base64 -d       # Decode

# Hex
echo -n "hello" | xxd -p          # Encode
echo "68656c6c6f" | xxd -r -p     # Decode
Python Methods
# Python raw bytes
bytes.fromhex("68656c6c6f")

import sys
sys.stdout.buffer.write(data)

import base64
base64.b64decode("aGVsbG8=")
⚠ Security Lesson

Encoding is NOT encryption. Always read the code—understand transformations. Programs compare bytes, not characters. Obfuscation provides no real security.

HTTP Basics

Web
Goal

Understand HTTP communication, manual request crafting, and how clients interact with web servers.

My Approach
  • Sent raw HTTP requests using netcat
  • Used curl for quick HTTP interactions
  • Automated requests with Python requests library
  • Understood Host header for virtual host routing
Commands Used
# Netcat raw HTTP
nc example.com 80
GET / HTTP/1.1
Host: example.com

# Curl requests
curl http://example.com
curl -H "Host: app.example.com" http://target-ip
curl -v http://example.com            # Verbose output

# Python requests
import requests
r = requests.get("http://example.com", headers={"Host": "app.example.com"})
print(r.text)
HTTP Request Structure
PartExamplePurpose
MethodGETAction to perform
Path/resourceResource requested
VersionHTTP/1.1Protocol version
Hostexample.comTarget virtual host
Concepts Learned
  • HTTP request structure (method, path, version, headers)
  • Host header determines which virtual host responds
  • Manual request crafting with netcat
  • Response headers can contain sensitive data
  • Virtual host enumeration for subdomain discovery
⚠ Security Lesson

Understanding raw HTTP is essential for web exploitation. The Host header can be manipulated to access hidden virtual hosts. Response headers often leak sensitive information not visible in page body.

HTB

Hack The Box Academy

+

System Enumeration

Linux
Overview

After gaining access, enumeration reveals escalation paths and valuable data. This is the foundation of post-exploitation.

System Information
uname -a                  # Kernel version
cat /etc/os-release       # OS details
hostname                  # System name
cat /proc/version         # Kernel info
User Enumeration
whoami                    # Current user
id                        # UID, GID, groups
sudo -l                   # Sudo permissions
cat /etc/passwd           # All users
cat /etc/shadow           # Password hashes (if readable)
history                   # Command history
Network Enumeration
ip a                      # Interfaces
netstat -tuln             # Listening ports
ss -tuln                  # Alternative
cat /etc/hosts            # Host mappings
arp -a                    # ARP cache
Interesting Files
# SUID binaries (potential escalation)
find / -perm -4000 2>/dev/null

# Writable directories
find / -writable -type d 2>/dev/null

# Recent files
find / -mtime -1 2>/dev/null

# Configuration files
find / -name "*.conf" 2>/dev/null
Credential Hunting
# SSH keys
ls -la ~/.ssh/
cat ~/.ssh/id_rsa

# Bash history
cat ~/.bash_history

# Config files with passwords
grep -r "password" /etc/ 2>/dev/null
⚠ Security Relevance

SUID binaries may allow privilege escalation. Readable config files may contain credentials. Cron jobs may run vulnerable scripts. Kernel version indicates potential exploits.

User & Group Management

Linux
Overview

User accounts and privileges are primary targets. Understanding user management helps identify misconfigurations and escalation paths.

Commands
# User information
whoami                    # Current user
id                        # User ID, groups
groups                    # Group memberships
cat /etc/passwd           # All users
cat /etc/shadow           # Password hashes (root only)
cat /etc/group            # All groups

# Switch users
su - username             # Switch user (need password)
sudo -l                   # List sudo privileges
sudo command              # Run as root
sudo -u user command      # Run as specific user
Important Files
FileContents
/etc/passwdUser accounts (readable by all)
/etc/shadowPassword hashes (root only)
/etc/groupGroup definitions
/etc/sudoersSudo permissions
/etc/passwd Format
username:x:UID:GID:comment:home:shell
root:x:0:0:root:/root:/bin/bash
Enumeration Techniques
# Users with shell access
grep -v "nologin\|false" /etc/passwd

# Users in sudo group
getent group sudo

# Check sudo permissions
sudo -l
⚠ Common Issues

Weak sudo configurations, users in privileged groups, accounts with no password, service accounts with shell access.

Network Interface Discovery

Linux
Skills Practiced
  • Identifying current user and permissions
  • Inspecting network interfaces
  • Understanding MTU configuration
  • Mapping internal network structure
Commands Used
ip a                      # All interfaces with IPs
ip link                   # Link layer info
ifconfig                  # Legacy command
netstat -rn               # Routing table
cat /etc/resolv.conf      # DNS servers
Concepts Learned
  • Network interface discovery
  • Linux kernel version identification
  • System architecture awareness
  • Home directory structure
THM

TryHackMe

+

Offensive & Defensive Security Intro

Web
Scenario

Practiced directory enumeration to discover non-obvious web routes, then shifted to SOC response to investigate and mitigate a web discovery attack pattern.

Offensive Workflow
  • Ran dirb http://target-site with common wordlist-based endpoint discovery
  • Interpreted HTTP status codes (200, 301, 404) during brute forcing
  • Identified hidden endpoints that were not linked in the main interface
  • Recognized business-logic weaknesses caused by missing authorization checks
Defensive Workflow
  • Investigated a SIEM alert categorized as Web Discovery Attack
  • Correlated suspicious traffic patterns to a single hostile source
  • Applied temporary source blocking as immediate containment
  • Applied rate limiting and updated WAF rules to reduce recurrence risk
Tools Used
  • dirb
  • Web browser
  • Linux terminal
  • SOC dashboard / SIEM interface
Core Skills Gained
  • Web enumeration and hidden endpoint discovery
  • Business logic vulnerability recognition
  • SIEM-based threat investigation
  • Incident response and layered defensive controls

Computer Fundamentals & OS Security

Systems
Scope

Core computing concepts: hardware architecture, boot process, virtualization, cloud computing, client-server models, and OS security principles.

Hardware & Boot Concepts
  • Core components: CPU, RAM, Storage, GPU, PSU, Motherboard
  • Boot sequence: BIOS/UEFI → POST → Bootloader → OS
  • Computer types and optimization for different tasks
Virtualization & Cloud
  • Virtual Machine concepts and use cases
  • Hypervisor types: Type 1 (bare-metal) vs Type 2
  • Cloud providers: AWS, Azure, Google Cloud
  • Cloud resources: VMs, storage, databases, networks
OS Security Concepts
  • Kernel space vs user space separation
  • User accounts, authentication, permissions
  • Firewalls and security updates
  • Endpoint security and threat detection
Client-Server Architecture
  • Request/response communication model
  • HTTP request and response flow
  • Remote access via SSH

Web Fundamentals

Web
Scope

Expanded foundation across networking, DNS, HTTP communication, web architecture, and client-side web security concepts.

Networking & DNS Concepts
  • DNS resolution flow and record types: A, MX, TXT, CNAME
  • Connectivity testing with ping and ICMP metrics (latency, packet loss)
  • Network topology models: star, ring, and bus
  • OSI 7-layer model for communication and troubleshooting context
Web Communication Concepts
  • HTTP request/response lifecycle and communication flow
  • Methods: GET, POST, PUT, DELETE
  • Status codes: 200, 301, 403, 404, 500
  • Header roles: Host, User-Agent, Authorization, Cookie
Client-Side Security Concepts
  • Cookie/session handling fundamentals
  • Sensitive data exposure through client-visible source code
  • HTML injection risk from unsafe rendering paths
  • XSS fundamentals and browser-impact overview
Tools Used
  • nslookup
  • ping
  • Wireshark
  • Burp Suite
  • Browser source/dev tools

Security Fundamentals, Crypto & Recon

Foundations
Security Principles
  • CIA triad: confidentiality, integrity, and availability as the basis for evaluating controls
  • Encryption as a method for protecting data confidentiality during storage and transmission
  • Difference between encryption, encoding, and hashing in security contexts
Cryptography Concepts
  • Symmetric encryption uses a single shared key and is efficient for bulk data protection
  • Asymmetric encryption uses public/private key pairs to support secure key exchange
  • Modern secure communication often combines both models for performance and security
Reconnaissance & Analysis
  • Packet capture and filtering for DNS, ICMP, and layered protocol inspection
  • Service discovery and attack-surface mapping through safe reconnaissance workflows
  • Technology fingerprinting using headers, framework indicators, and browser inspection
  • Application route discovery concepts for identifying exposed paths and content
Software & Data Concepts
  • Binary and hexadecimal representations for understanding stored and transmitted data
  • Encoding formats such as Base64 and URL encoding in web and authentication workflows
  • Programming awareness across Python, JavaScript, SQL, and Node.js for security analysis
Tools Used
  • Wireshark
  • Nmap
  • WhatWeb
  • Gobuster
  • Hydra
  • curl
  • xxd / hexdump / base64

Linux Privilege Escalation Methodology

Linux
Methodology Checklist
# 1. User Context
whoami
id
sudo -l

# 2. System Info
uname -a
cat /etc/os-release

# 3. SUID Binaries
find / -perm -4000 2>/dev/null
# Check GTFOBins for exploitation

# 4. Writable Files
find / -writable -type f 2>/dev/null

# 5. Cron Jobs
cat /etc/crontab
ls -la /etc/cron.*

# 6. PATH Hijacking
echo $PATH
# Check if writable directories are in PATH

# 7. Credentials
cat ~/.bash_history
grep -r "password" /etc/ 2>/dev/null
Common Vectors
  • Misconfigured sudo permissions
  • SUID binaries (check GTFOBins)
  • Writable scripts in cron
  • Kernel exploits
  • Credentials in config files
Tools
LinPEAS                   # Automated enumeration
GTFOBins                  # Binary exploitation reference
sudo -l                   # Check sudo rights
find -perm                # Find special permissions

Operational Notes & Intelligence Journal

Professional, expandable security notes covering architecture, methodology, offensive workflow, and defensive translation — all readable directly on this site.

Operating Systems, Shell, and Linux Control Surface

Core Expand

This block captures system-control fundamentals used in both penetration testing and defensive hardening.

  • Execution model: User → Shell → Kernel → Hardware and privilege-boundary implications.
  • Linux operations: navigation, file manipulation, permission control, ownership, and process management.
  • Privilege context: repeatable checks with identity, group, and sudo scope inspection.
  • Operational discipline: least privilege, controlled script execution, and auditability.
whoami
id
sudo -l
ls -la
chmod 640 notes.txt
chown user:group notes.txt
ps aux

Networking Fundamentals, Recon, and Service Enumeration

Network Expand

Reconnaissance is treated as a structured intelligence phase for attack-surface definition and defensive visibility.

  • Protocol literacy: HTTP/HTTPS, DNS, FTP, SMTP/POP3/IMAP, ICMP.
  • Discovery flow: host discovery → port exposure → service/version profiling.
  • Web surface mapping: technology fingerprinting and route/content enumeration.
  • Defensive value: confirms externally reachable assets and monitoring priorities.
nmap 10.10.10.10
nmap -sV 10.10.10.10
nslookup example.com
whatweb target
gobuster dir -u http://target -w wordlist.txt

Traffic Analysis and Protocol Inspection

Analysis Expand

Packet analysis is used for troubleshooting, incident confirmation, and protocol-level anomaly detection.

  • Collection: capture live traffic with CLI and GUI tooling.
  • Filtering: isolate DNS, ICMP, HTTP, and session patterns quickly.
  • Interpretation: map packet behavior to user activity and potential attack paths.
  • IR context: supports triage for suspicious outbound connections and credential leakage patterns.
tcpdump -i eth0
wireshark
# common display filters
icmp
dns
http

Cryptography, Hashing, and Password Security

Security Expand

Focus is on practical security interpretation of confidentiality, integrity, and authentication controls.

  • CIA triad: used as a control-quality evaluation lens.
  • Crypto models: symmetric (AES/DES) vs asymmetric (RSA/ECC) trade-offs.
  • Hashing: one-way, deterministic, fixed-length outputs for password and integrity workflows.
  • Credential risk: weak password policy increases offline cracking exposure.
echo "hello" | base64
echo "aGVsbG8=" | base64 -d
echo "hello" | xxd
john --show hash.txt

Authentication Risk: NTLM/NetNTLMv2 and Outlook Moniker Case

Threat Expand

High-level risk analysis of credential-exposure patterns and modern phishing-triggered authentication abuse.

  • NTLM model: challenge-response mechanics and captured-hash risk.
  • Capture simulation: authorized lab workflows using Responder.
  • CVE context: Outlook Moniker Link risk (CVE-2024-21413) as a credential-harvest case study.
  • Response priorities: patching, NTLM reduction, SMB egress control, user awareness.
sudo responder -I eth0
# analyze suspicious authentication behavior
# validate outbound SMB controls

Practical Attack Lifecycle and Defensive Translation

Workflow Expand

This section maps offensive workflow stages to concrete defensive controls and detection opportunities.

  • Lifecycle: recon → scanning → enumeration → validation → post-exploitation reasoning.
  • Lab scope: MS17-010/EternalBlue-class exposure awareness in authorized environments.
  • Platform practice: Metasploitable and virtualized labs for controlled service abuse simulation.
  • Blue-team translation: monitor auth anomalies, harden credentials, and reduce lateral-movement paths.
# workflow discipline
recon -> enumerate -> validate -> report
# defensive translation
patch -> harden auth -> monitor -> contain

Skills Matrix

Professional capability areas developed through lab practice and repeatable methodology.

🐧

Linux Security

+
Tools & Commands
chmod chown ls find grep ps top cat head tail

Documentation

Why It Matters

Linux powers most servers, security tools, and target systems. Mastery of the command line is essential for any security role.

Essential Commands
pwd                     # Current directory
ls -la                  # List with permissions
cd /path                # Change directory
cat file.txt            # View file
head -n 20 file         # First 20 lines
tail -f /var/log/syslog # Follow log in real-time
grep "pattern" file     # Search in file
find / -name "*.conf"   # Find files
id                      # Current user/groups
File System Structure

/etc - Configuration files (may contain credentials)
/var/log - System logs
/home - User directories
/tmp - Temporary files (often world-writable, common attack vector)
/root - Root user home

🔍

System Enumeration

+
Tools & Commands
LinPEAS netstat ss ip arp find uname whoami

Documentation

Why It Matters

After gaining access, enumeration reveals escalation paths and valuable data. This is the foundation of post-exploitation.

System & User Info
uname -a                # Kernel version
cat /etc/os-release     # OS details
whoami                  # Current user
id                      # UID, GID, groups
sudo -l                 # Sudo permissions
cat /etc/passwd         # All users
Finding Interesting Files
find / -perm -4000 2>/dev/null  # SUID binaries
find / -writable -type d 2>/dev/null  # Writable dirs
grep -r "password" /etc/ 2>/dev/null  # Credentials

Privilege Escalation

+
Tools & Commands
GTFOBins LinPEAS sudo su cron

Documentation

Methodology
# 1. User Context
whoami && id && sudo -l

# 2. SUID Binaries
find / -perm -4000 2>/dev/null

# 3. Cron Jobs
cat /etc/crontab
ls -la /etc/cron.*

# 4. PATH Hijacking
echo $PATH
Common Vectors

• Misconfigured sudo permissions
• SUID binaries (check GTFOBins)
• Writable scripts in cron
• Credentials in config files
• Kernel exploits

📜

Shell Scripting

+
Tools & Commands
bash sh awk sed grep tr

Documentation

Script Basics
#!/bin/bash
echo "Hello"
VAR=$(command)    # Command substitution
chmod +x script.sh
./script.sh
Key Concepts

• Scripts need shebang (#!/bin/bash) to specify interpreter
• Command substitution: $(command) or backticks
• Variables: no $ when assigning, $ when reading
• Always validate input, never run untrusted scripts as root

⚙️

Process Management

+
Tools & Commands
ps top htop kill jobs lsof

Documentation

Why It Matters

Understanding running processes helps identify suspicious activity, find vulnerable services, and manage system resources during testing.

Process Control
ps aux                  # All processes
ps auxf                 # Process tree
command &               # Run in background
jobs                    # List background jobs
fg %1                   # Bring to foreground
kill PID                # Graceful termination
kill -9 PID             # Force kill
lsof -i :80             # What's using port 80
💻

Virtualization

+
Concepts & Tools
VirtualBox VMware Hyper-V KVM QEMU Docker Snapshots

Documentation

Why It Matters

Virtualization enables isolated testing environments, malware analysis, and resource optimization. Critical for security labs, CTFs, and enterprise infrastructure.

Virtual Machine Concepts

VM: Software-based computer with its own OS running inside a host
Host: Physical machine running the hypervisor
Guest: Virtual machine running on the host
Snapshot: Point-in-time state capture for rollback

Hypervisor Types
# Type 1 (Bare-metal)
- Runs directly on hardware
- VMware ESXi, Hyper-V, KVM
- Better performance, enterprise use

# Type 2 (Hosted)
- Runs on top of host OS
- VirtualBox, VMware Workstation
- Easier setup, desktop use
Security Use Cases

Malware Analysis: Isolate suspicious files from host
Penetration Testing: Attack lab networks safely
Snapshot Testing: Test exploits, restore clean state
Network Isolation: Segmented lab environments
Multi-OS Testing: Run Windows, Linux, Kali simultaneously

☁️

Cloud Computing

+
Platforms & Tools
AWS Azure Google Cloud SSH EC2 S3 IAM

Documentation

Why It Matters

Most modern infrastructure runs in the cloud. Understanding cloud architecture is essential for security assessments, incident response, and secure deployments.

Cloud Service Models

IaaS: Infrastructure as a Service (VMs, storage, networks)
PaaS: Platform as a Service (managed runtime, databases)
SaaS: Software as a Service (end-user applications)

Cloud Resources
# Common cloud resources
- Virtual Machines (EC2, Azure VMs)
- Storage (S3, Blob Storage)
- Databases (RDS, CosmosDB)
- Networks (VPC, Virtual Networks)
- Identity (IAM, Azure AD)

# Remote access
ssh -i key.pem user@instance-ip
Security Considerations

IAM Policies: Principle of least privilege
Security Groups: Cloud-based firewalls
Encryption: Data at rest and in transit
Logging: CloudTrail, Azure Monitor for audit
Misconfigurations: #1 cloud vulnerability

🛡️

OS Security

+
Concepts & Tools
Kernel User Space Firewalls Permissions Authentication Endpoint Security

Documentation

Why It Matters

Operating systems are the foundation of all computing. Understanding OS security is critical for hardening systems, detecting threats, and performing security assessments.

Kernel vs User Space

Kernel Space: Unrestricted hardware access, runs OS core
User Space: Restricted permissions, runs applications
Security Goal: Prevent user space from accessing kernel directly
Exploitation: Kernel exploits grant full system control

Security Components
# Authentication
- Passwords, SSH keys, MFA
- /etc/passwd, /etc/shadow (Linux)
- SAM database (Windows)

# Authorization
- File permissions (rwx)
- User/group policies
- sudo, UAC

# Network Security
- Firewalls (iptables, Windows Firewall)
- Network segmentation
Hardening Checklist

Updates: Patch vulnerabilities promptly
Least Privilege: Minimal user permissions
Firewall: Block unnecessary ports
Logging: Monitor for suspicious activity
Endpoint Protection: Antivirus, EDR solutions
Disable Unused Services: Reduce attack surface

🔐

Cryptography

+
Concepts & Standards
CIA Triad AES RSA ECC TLS Base64 Hashing

Documentation

Why It Matters

Cryptography protects data confidentiality, supports integrity checks, and underpins secure communication protocols used across modern systems.

Encryption Models
# Symmetric encryption
- One shared key for encryption and decryption
- Fast and efficient for large data volumes
- Main challenge: secure key distribution

# Asymmetric encryption
- Public key encrypts, private key decrypts
- Supports safer key exchange
- Slower, often combined with symmetric encryption
Important Distinctions

Encryption: Protects secrecy
Encoding: Transforms format for transport or compatibility
Hashing: Supports integrity validation and password verification workflows

Security Relevance

• TLS combines asymmetric and symmetric cryptography
• Weak key handling breaks otherwise strong encryption
• Encoding should never be confused with encryption
• Integrity controls are critical alongside confidentiality

📦

Packet Analysis

+
Tools & Techniques
Wireshark tcpdump tshark pcap Protocol Analysis Traffic Filtering Stream Reconstruction

Documentation

Why It Matters

Packet analysis is essential for network troubleshooting, intrusion detection, forensic investigation, and understanding how applications communicate at the protocol level.

Core Concepts
# Packet Capture
Recording raw network traffic into pcap files
for later analysis and forensic investigation

# Protocol Layers
Ethernet → IP → TCP/UDP → Application
Each layer reveals different information

# Deep Packet Inspection
Examining packet payloads for patterns,
credentials, or malicious content
Wireshark Filters
ip.addr == 192.168.1.1    # Filter by IP
tcp.port == 80            # Filter by port
http.request.method == GET # HTTP GET requests
dns                       # DNS traffic only
tcp.flags.syn == 1        # SYN packets (connections)
Analysis Techniques

Follow Stream: Reconstruct full TCP conversations
Statistics: Protocol hierarchy, endpoints, conversations
Export Objects: Extract files transferred over HTTP/FTP
Coloring Rules: Visual identification of traffic types

Security Applications

• Detecting unauthorized connections and data exfiltration
• Identifying malware command-and-control traffic
• Investigating security incidents post-breach
• Validating encryption and secure protocol usage

🔍

Reconnaissance

+
Tools & Techniques
Nmap WhatWeb Gobuster WHOIS dig netcat Banner Grabbing Port Scanning

Documentation

Why It Matters

Reconnaissance is the first phase of penetration testing—gathering information about targets before exploitation. Better recon means a clearer understanding of the attack surface.

Passive vs Active
# Passive Reconnaissance
Gathering info WITHOUT touching the target
- WHOIS lookups, DNS records
- Google dorking, social media
- Public documentation review

# Active Reconnaissance
Directly probing the target system
- Port scanning, service enumeration
- Web fingerprinting, directory discovery
Key Activities
# Port Scanning
nmap -sV -sC target      # Service detection

# Web Fingerprinting
whatweb target           # Detect technologies

# Directory Discovery
gobuster dir -u target -w wordlist

# Banner Grabbing
nc target 22             # Read service banners
Information Gathered

Open Ports: Which services are exposed
Service Versions: Software and version numbers
Technologies: CMS, frameworks, server software
Hidden Content: Admin panels, backup files, APIs
Infrastructure: Subdomains, IP ranges, hosting

Ethical Considerations

• Always have written authorization before scanning
• Understand legal boundaries in your jurisdiction
• Passive recon is generally safer from legal perspective
• Active scanning can trigger IDS/IPS and log entries

🔧

Environment & PATH

+
Tools & Commands
env export printenv which unset

Documentation

Why It Matters

Environment variables control program behavior. Manipulating them can bypass security controls or exploit vulnerable configurations.

Commands
env                     # View all variables
echo $PATH              # View specific variable
export VAR="value"      # Set and export
export PATH="/my/dir:$PATH" # Prepend to PATH
Security Impact

PATH hijacking: Place malicious binary in earlier PATH directory
LD_PRELOAD: Inject shared library into process
Defense: Use full paths in scripts: /usr/bin/cat not cat

🌐

Web Security

+
Tools & Commands
curl netcat dirb Nmap WhatWeb Gobuster Python requests Browser DevTools SIEM nslookup ping Wireshark Burp Suite Hydra

Documentation

Why It Matters

Web applications are primary attack targets. Understanding HTTP, enumeration, and both offensive and defensive workflows is essential.

HTTP & Enumeration
# Raw HTTP with netcat
nc target.com 80
GET / HTTP/1.1
Host: target.com

# Curl requests
curl -v http://target.com
curl -H "Host: admin.target.com" http://ip

# Directory enumeration
dirb http://target.com
Offensive Skills

• Directory brute forcing to find hidden endpoints
• HTTP status code analysis (200, 301, 404)
• Host header manipulation for virtual host discovery
• Business logic vulnerability identification

Recon & Fingerprinting Added

• Service and exposed-port awareness using safe network reconnaissance
• Technology fingerprinting through Server and X-Powered-By headers
• Route and content discovery with wordlist-based enumeration concepts
• Authentication attack awareness and the need for MFA, rate limiting, and monitoring

Defensive Skills

• SIEM alert triage and investigation
• SOC incident response workflow
• IP blocking and rate limiting
• WAF rule tuning to block enumeration patterns

Web Fundamentals Added

• DNS records and query analysis (A, MX, TXT, CNAME)
• Network diagnostics with ICMP and latency interpretation
• OSI layers and network topology understanding
• HTTP headers, cookies, and request/response behavior
• Intro risk models: sensitive data exposure, HTML injection, and XSS

Let's Connect

Open to collaboration, learning opportunities, and cybersecurity discussions.