# OffSec-Reporting supplies OffSec exam report templates for SysReptor > A repository that collects report templates for OffSec certifications from OSCP+ to OSTH, built on the SysReptor reporting platform. It is a template gallery rather than an application, and the actual software lives in the SysReptor project. **Syslifters/OffSec-Reporting** — Offensive Security OSCP+, OSEP, OSWP, OSWA, OSWE, OSED, OSMR, OSEE, OSDA, OSIR, OSTH Exam and Lab Reporting / Note-Taking Tool - Repository: https://github.com/Syslifters/OffSec-Reporting - Website: https://docs.sysreptor.com/ - Stars: 954 · Forks: 120 - Language: Unknown - License: not declared - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/syslifters-offsec-reporting ## A gallery of templates, not a reporting application OffSec-Reporting is described as a collection of OffSec report templates built with SysReptor, a fully customizable pentest reporting platform. The distinction matters more here than in most projects, because the repository itself contains almost nothing. The top level entries are README.md and an assets/ directory. There is no source code, no package manifest, no build, and no test suite, and the primary language of the repository is not even recorded. What the repository does is point at templates that live elsewhere. The pages are published under the SysReptor documentation site, each exam report is offered as a PDF preview, and the editable templates are distributed as a bundle named offsec-designs.tar.gz, which SysReptor imports as designs. So there are two moving parts. SysReptor is the application that renders reports, and OffSec-Reporting is the set of designs that make it produce a document shaped for an OffSec exam. The people behind both are Syslifters, and the same organisation runs the hosted instance, which is where most people will start. The practical reading for an engineer is that this repository is documentation with downloads attached. It is worth reading, and it is worth using as a pointer, but you will not be building anything on top of it. ## Twelve certifications, split by track The supported list is long, and the structure of the list is more informative than the list itself. The certifications covered are OSCP+, OSEP, OSWP, OSWA, OSWE, OSED, OSMR, OSEE, OSAI, OSDA, OSIR and OSTH. The README groups the previews by what the exam tests rather than by vendor tier, and the group headings are the key to the coverage. Penetration Testing covers the OSCP+ exam report. Web Application Security covers OSWA and OSWE. Exploit Development covers OSED, OSMR and OSEE. AI Red Teaming has its own group with the OSAI report. Defensive Security covers OSDA, OSIR and OSTH. That last group is the one worth pausing on, because a reporting tool that also covers defensive and AI red teaming tracks is not exclusively an offensive security artefact. The project is filed under offensive security topics in the repository's topic tags, but the template set spans both sides, and the same tool serves a defender writing up an incident as it serves a penetration tester. The README also includes an abbreviations table mapping each exam acronym to its full name, its lab name and its course name, which is a genuinely useful table for anyone who has to talk about these credentials without mixing up PWK with the exam itself. The visible part of the table starts with OSCP+, Offensive Security Certified Professional, lab PWK, course Penetration Testing with Kali Linux. One point about provenance is stated plainly. The structure follows the official OffSec reports, with kind permission by OffSec. That is the sort of detail that matters when a report has to be submitted to the vendor. ## The hosted instance, and the appeal of no local troubleshooting The quickest route is the hosted one. The README points at a signup page for OffSec users on the SysReptor service and states that it is free, with a separate login link for people who already have an account. The benefits list is short and worth quoting in spirit rather than verbatim: it is free, you write in markdown, it renders to PDF, it covers the listed certifications, it is fully customizable, and there is no local software troubleshooting. That last one is the real product decision for the audience. Candidates taking an OffSec exam are frequently working on a laptop that already has Kali Linux, a VPN client and a cracked workstation running, and the appeal of a browser-based editor is that it adds nothing to that machine. Writing in markdown is the other meaningful choice. A report is a long structured document with headings, code blocks and images, and markdown gives you that structure without a word processor in the way. The PDF rendering is what the exam submission process needs at the end. The trade-off is that a hosted service means your notes, your screenshots and your unfinished exam reports live on someone else's infrastructure, and the free tier is the one being offered to candidates. For a document that will be read by examiners, that is a risk worth thinking about, and the self-hosting route exists for exactly that reason. ## Importing the designs into your own SysReptor instance If you would rather run the platform yourself, the documented path is to install SysReptor first, using the installation guide in the SysReptor documentation, and then import the OffSec designs into the running instance. The import is a single pipeline that fetches the design bundle and hands it to the application's data import command: ```bash cd sysreptor/deploy url="https://docs.sysreptor.com/assets/offsec-designs.tar.gz" curl -s "$url" | docker compose exec --no-TTY app python3 manage.py importdemodata --type=design ``` The mechanics of that command are worth noting. It runs inside the container rather than on the host, so the design data is written by the application itself and lands in the right database, and the --type=design flag restricts the import to designs, so a bundle containing other demo content would not flood the instance. The --no-TTY flag is there because the import is not interactive, and a TTY would make the command wait for input that never comes. The bundle is downloaded rather than cloned, which means the templates arrive through the documentation site rather than from a version control checkout. That has an upside, since there is nothing to keep in sync, and a downside, since the documentation does not describe how to pin a specific version of the bundle or how to tell what changed between two imports. For anyone who wants to see the result before installing anything, the same documentation publishes the rendered PDFs, one per exam, which is the fastest way to judge whether the structure suits the way you write. ## Where the customisation actually lives, and what the README leaves out The SysReptor project is described as fully customizable, and the designs in this repository are the customization in practice: the design defines how a report of that type is laid out, which fields it collects, and how it renders. Editing a design in the running application and exporting it as your own template is the mechanism SysReptor provides, and once a candidate has imported the OffSec designs, the report they write is no longer limited to the stock structure. What this repository does not tell you is where the boundary lies for the exam use case. It does not document which fields of the imported designs are mandatory for OffSec submission, whether the exam submission process accepts a report that deviates from the structure, or whether the templates will be revised as OffSec changes its expected report format. There is no changelog here, no issue tracker referenced for template bugs, and no version pinning for the design bundle. A template that was correct for one exam sitting can be quietly out of date for the next. That is a documentation gap rather than a defect, and it is a gap the SysReptor documentation and the linked contact address are there to fill. Missing a template or having a question is explicitly a supported route in the README, which points to an issue or a contact page, so the project treats template coverage as a live conversation rather than a fixed set. The last push to this repository was on 2026-09-04, the repository is not archived, and it publishes no GitHub releases. Treat it as a maintained pointer to SysReptor rather than as a versioned artefact. ## Conclusion OffSec-Reporting is worth your attention if you are sitting an OffSec exam and want to spend your revision time on the machines rather than on document layout, because it hands you templates that already follow the structure OffSec expects. It is not a tool you can run on its own: the repository holds a README and assets, while the reporting platform and the template bundle belong to SysReptor. Verify the exam you are taking is on the supported list, since the templates are split by certification and by track, and check the OffSec-OSCP-Exam-Report.pdf preview in the documentation before you commit to a structure, because the documentation does not describe how the templates are edited after import. ## FAQ ### What is Syslifters/OffSec-Reporting? It is a repository showcasing OffSec report templates built with SysReptor, a customizable pentest reporting platform, covering exams including OSCP+, OSEP, OSWP, OSWA, OSWE, OSED, OSMR, OSEE, OSAI, OSDA, OSIR and OSTH. ### How do I import the OffSec templates into my own SysReptor instance? After installing SysReptor, run the import from the deploy directory: curl the offsec-designs.tar.gz bundle and pipe it into docker compose exec app python3 manage.py importdemodata --type=design. The documentation has the exact command. ### Is the hosted SysReptor instance free? The README states that the signup for the OffSec instance is free, and that self-hosting is also free. The benefits list adds that you write in markdown, it renders to PDF, and there is no local software troubleshooting. ### Do the OffSec report templates follow the official OffSec report structure? The README states that the structure follows the official OffSec reports, with kind permission by OffSec. A rendered PDF preview of each exam report is published in the SysReptor documentation. ## Sources - [Issues](https://github.com/Syslifters/OffSec-Reporting/issues) - [Project website](https://docs.sysreptor.com/) - [README](https://github.com/Syslifters/OffSec-Reporting/blob/main/README.md) - [Syslifters/OffSec-Reporting on GitHub](https://github.com/Syslifters/OffSec-Reporting) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/syslifters-offsec-reporting