Serpico 1.3.0 release: penetration testing report generation and collaboration tool
SimplE RePort wrIting and CollaboratiOn tool
Serpico is a penetration testing report generation and collaboration tool. It was developed to cut down on the amount of time it takes to write a penetration testing report.
Serpico is at its core a report generation tool but targeted at creating information security reports. When building a report the user adds “findings” from the template database to the report. When there are enough findings, click ‘Generate Report’ to create the docx with your findings. The docx design comes from a Report Template which can be added through the UI; a default one is included. The Report Templates use a custom Markup Language to stub the data from the UI (i.e. findings, customer name, etc) and put them into the report.
Report Template Editing is Easy
Philosophy: Editing a report template should be easy. During peer review we would constantly run into “little things” we were fixing from the report template; an extra space here, a misspelling there. But it adds up. With Serpico, “fix” the report template, upload it back to the UI, and generate a new report; the error should be fixed permanently.
Philosophy: We do not need to write most findings from scratch. Most findings have been found in a previous assessment. In Serpico, all authors can pull findings from the template database and add to the report. A user can also ‘Upload’ a finding they made into the Template Database to share with everyone.
Philosophy: It should be easy to share files with teammates. Use the ‘Add Attachment’ functionality to store a file (e.g. screenshots, nmap scans) or share with teammates on a pen test. No thumb drive swapping or e-mailing, just log into the UI and download the files. At the end of the assessment everything traded or generated for that assessment is in one place.
This release includes a number of bug fixes and new features, to name just a few:
- report template verification tool 🔥
- multi-language support
- NIST800 scoring and reports
- better logging
- proper code formatting
Copyright (c) 2013-2017, Willis Vandevanter