EHAT is the short name for Ethical Hacking Activity Tracking platform, developed by LUTECH-TMS-CERT years ago. Actually, EHAT-NG is definitely more than just an activity tracking tool. It's SERPICO-on-steroids:
- Import XML report from Nexpose
- New Statistics & Charts
- New risk scoring system w/ auto CVSS Calculator
- Generate Remediation Plan in XLSX
- Auto Summarize of findings overview thanks to NLP (Natural Language Processing)
- ..and much more
EHAT-NG has been developed by LUTECH-TMS-CERT, largely thanks to the contribution of its Andrea De Dominicis. Andrea has another SERPICO fork on Github. LUTECH-TMS-CERT decided to release EHAT-NG in opensource for the benefit of all. LUTECH-TMS-CERT is willing to collaborate with the community to make it grow and is looking for technical joint ventures with other organizations to proactively support the community and evolve the project.
You may contact LUTECH-TMS-CERT at security at lutech dot it
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.
Video Demo of Functionality:
The installation options are:
-
Install Official Release: The prefered method of installation which includes all dependencies in one package.
-
Developer Build: Simple Instructions to build from clone
-
Windows Developer Build: Serpico can also be built and run on Windows
Initialize the database:
/opt/Serpico/init_serpico.sh
And then start Serpico:
/opt/Serpico/start_serpico.sh
Initialize the database:
/Users/Shared/Serpico/init_serpico.sh
Start Serpico:
/Users/Shared/Serpico/start_serpico.sh
Initialize the database:
C:\Serpico\init_serpico.bat
Start Serpico:
C:\Serpico\start_serpico.bat
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.
Philosophy: Editing a report template should be easy. During peer review we would constantly ran 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 through 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.
The Meta language used for Microsoft Word was designed to be as simple as possible while still serving enough features to create a basic penetration test report. That being said it has a learning curve (and many bugs) and I highly suggest looking at "Serpico - Report.docx" or "Serpico - No DREAD.docx" and editing these rather than working from scratch.
See also:
-
Inserting Screenshots: This is an area we know needs development so e-mail us with any ideas.
- Wiki: We try to add most common questions to the wiki.
- IRC: #therealserpico on freenode
- Issue : If you have found a bug or would like a new feature
- E-mail Support: For teams of users or template related questions
- Microsoft has a really annoying habit of changing a character for you. Always beware of this when working with the meta language