One of the main areas we’re working on as part of the Autumn of Code (if you are a Dradis Pro subscriber you know what this is, for the rest of you, we’ll be writing up a bit more in a few days) is documentation.
We’re always working to make it even easier for our users to create Dradis Pro custom reports. You just need Word and a few minutes to go through the guides. We provide you with plenty of examples and sample templates (both built into Dradis and via our Extras section).
Over the last month, we have restyled and organised the Support site and so far we’ve added three brand new guides.
From Nessus to Word: a hands-on-example
This guide covers all the steps required to go from a Nessus export file (.nessus) to a Word report with custom look and feel. Map between the Nessus fields and the fields your organisation uses with the Plugin Manager, report findings by host, or list all the hosts affected by one vulnerability, etc.
Of course the best part is that the exact same methodology can be applied to generate custom reports from any of the other supported tools (Qualys, Nexpose, Burp, etc.). And you can mix and merge the results from multiple tools to generate a single consistent report in minutes.
Read more: From Nessus to Word: a hands-on-example
Dradis Pro custom Word reports 101
If you are a new user that is starting with Dradis Pro custom reports or if you’re checking out our reporting engine capabilities, this guide is the right starting point.
We cover how to create a template from scratch, how to provide the placeholders for the different types of information that will end up in the report, how to filter and sort your findings, how to style your notes, etc.
We go into some detail about the philosophy behind Dradis, how to make the most of the flexibility it provides. Learn about all the features we support so you can mix and match them to fit your oranisation’s reporting needs.
Read more: Dradis Pro custom Word reports 101
Connect Dradis to MediaWiki
Finally, a guide not strictly about the creating Dradis Pro custom reports, but useful for those wanting to get the most value out of Dradis: create a repository of reusable report entries in a wiki and connect it to Dradis so you can import issues from it. Never again rewrite the same issue description, just import it and tweak the details for each particular case.
That’s it for now, but we will be posting more updates on the Autumn of Code in the coming weeks.
If you want to learn more about Dradis Pro benefits, the Features page is the right place to start.