Why build it
Lab completions alone do not explain the investigation, evidence, or lessons behind them. TALA gives cybersecurity practice a structured home, connecting write-ups to the skills and techniques actually used.


A personal cybersecurity lab journal that turns hands-on practice into structured write-ups, evidence, and a record of learning.
Lab completions alone do not explain the investigation, evidence, or lessons behind them. TALA gives cybersecurity practice a structured home, connecting write-ups to the skills and techniques actually used.
Bring lab notes, CTF challenges, evidence, and learning goals into one personal workspace, then share selected work without publishing private reflections or evidence by default.
Create a lab or CTF challenge with category, difficulty, and status. Structure the write-up around the objective, environment, methodology, findings, analysis, and lessons learned.
Attach screenshots, logs, PCAPs, or reports. Associate the skills and tools practiced, and explain why each MITRE ATT&CK technique applies.
Use activity dashboards and a learning roadmap to see completed work, learning hours, practiced skills, and technique coverage derived from stored records.
Mark a lab portfolio-ready to publish its write-up. Evidence stays private unless explicitly shared, and the Reflection field remains private. Export lab reports or learning summaries as PDF or Markdown.
Uploads are checked against allowed extensions and file signatures, with UTF-8 validation for text files. SHA-256 hashes are recorded alongside file metadata, and downloads pass through authenticated ownership checks.
Lab and CTF technique associations include a required justification. The mapping records why a technique applies rather than treating ATT&CK labels as decoration.
Skills, tools, and techniques are shared reference records across labs and CTF challenges. Activity statistics come from those relationships rather than self-rated proficiency percentages.
TALA documents work performed in external labs and authorized environments. It is a single-user journal; it does not run scans, execute exploits, or solve challenges automatically.
A React interface connects to a FastAPI service and PostgreSQL database. Evidence files are stored separately from their database metadata. Authentication uses JWT sessions in HttpOnly cookies.