Customising Finding Fields, Prompts and Dashboards

Every firm has a way of writing a finding and a set of things it always records. A platform that makes you write its way instead is a platform your testers work around. In Pental the fields are yours to shape, the AI writes to your prompts, and each role’s dashboard shows what that role needs first.

Finding fields

Settings, Findings, Finding Fields lists every field of a finding, in the order the finding form and the finding page use. For each one you can:

• Rename it to what your reports call it: Recommendation instead of Remediation, Business Impact instead of Impact. The new name is used on the form, on the finding and in your reports.
• Reorder it with its arrows, or drag it by its handle. Title and Severity always stay at the top; the report’s own order is set on its template.
• Require it, so a finding cannot be saved as final without it. A finding missing a required field is a draft until it is filled.
• Untick Show in form for one your firm does not record, and it leaves the finding form.
• Tick Reuse from Library for one that belongs with the issue rather than the engagement, such as the description, so it is stored on Library entries and filled in from them.

Add Custom Field adds one of your own, in the style that suits it: rich text, plain text, a single line, a short value, a number, a date, a dropdown, multiple choice, yes or no, or a link. A field that holds a value sits in the finding’s header beside its severity and score; a passage gets a card of its own. Every style can be written by AI.

A prompt for each field the AI writes

Each field the AI writes has an AI prompt link under it, which opens the prompt it is written to: shown in full when nothing has been saved, with Reset to default to go back. Change it and every finding written from then on follows: descriptions that open with the business impact, remediation as numbered steps, titles in your house style. Writing a pentest finding from your notes with AI shows the prompts at work, and writing remediation a developer will actually action is worth reading before you change the remediation prompt.

Your report’s sections and your methodology

The report’s sections are set the same way, on Settings, Assessments: rename and reorder them, choose what goes in the report and what the client sees, and add sections of your own. The executive summary and the report’s sections covers each control. Your methodology, a checklist or runbook for each kind of test, starting from the curated OWASP and NIST based templates and changed to suit how you work, is covered in checklists and runbooks.

A dashboard for each role

Settings, Dashboard, Dashboard Layout Editor builds the dashboard every member of a role sees. Choose the role under Editing, then drag a card from Cards to add into a row, or press its + to add it at the end. A row holds up to three cards side by side, or two where one of them needs more room, and every row stacks on a phone.

Rows move with Move Up and Move Down, Preview shows the dashboard as that role will see it, and Save Layout applies it to everybody with that role. The Role status line shows which roles have a layout of your own and which use the default, with Reset beside each of yours.

Testers might lead with what is starting soon and in progress, a reviewer with the QA queue and what is ready to deliver, and your clients’ own dashboard with their findings and their documents.

Switching off what you do not use

A module you do not use can go entirely, from everyone’s navigation and every screen that mentions it: switching off the parts of the platform you do not use explains how.