Skip to content

Repository files navigation

Cybersecurity Lab Reports

Supporting portfolio evidence for security awareness and technical reporting. This repository contains five reports created from authorized TryHackMe training environments; they are lab exercises, not professional client engagements or production penetration tests.

Publication status

REVIEW REQUIRED — the original PDFs remain available in Git history and the repository tree, but they are not promoted as a recruiter-facing gallery. An automated audit found target identifiers and challenge-answer indicators, and manual source review is still required for other training values. Those details can be appropriate inside a private lab report, but sanitized public editions should be produced from the source documents before this repository is highlighted.

The audit records only counts and hashes. It never writes the matching values into logs or generated files.

Report Scope Public-gallery status
Attacktive_Directory_Pentest_Report.pdf Active Directory training lab Blocked pending source redaction
EasyPeasy_Host_Pentest_Report.pdf Single-host training lab Blocked pending source redaction
Source_Host_Pentest_Report.pdf Single-host training lab Blocked pending source redaction
VulnNet_Roasted_AD_Pentest_Report.pdf Active Directory training lab Blocked pending source redaction
Wreath_Network_Pentest_Report.pdf Multi-host network training lab Blocked pending source redaction

See the publication audit for the decision boundary and the machine-readable manifest for reproducible evidence.

Reproduce the document audit

python -m pip install -r requirements-dev.txt
python scripts/audit_reports.py --check

The check verifies that every tracked PDF is readable and that its hash, page count, embedded-link count, metadata indicators, and non-sensitive risk counts match the reviewed manifest. It fails when a PDF changes or a report is added without review.

What this repository demonstrates

  • structured security reporting in bounded training environments
  • awareness of publication, credential, and personal-data risks
  • reproducible document checks in GitHub Actions
  • an evidence-based decision not to over-promote unsafe artifacts

This is intentionally de-emphasized behind the software and data-engineering projects on the profile. The PDFs are authorized lab material, not real-client or production-system evidence, and no professional penetration-testing experience is claimed from them.

About

Authorized CTF-style lab reports with a reproducible publication-safety audit and explicit non-client boundaries.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages