The Pental Product Demo
- 0:00IntroductionWhat the demo follows: a demonstration firm, Calderwood Security, from a new engagement to a retest, then everything that makes the platform its own.
- 0:16Your Own Sign-in PageCalderwood Security, a demonstration firm, signs in at its own address with a second factor.
- 0:27The Dashboard and Your ClientsThe day’s work at a glance: an engagement waiting for a lead tester, a report ready to deliver, every open finding by severity; and one record for each client, with their contact, engagements and portal users.
- 0:48A New EngagementAn engagement in phases, each with its own type, days and scope, its title written by AI, credentials asked for before it starts, and a lead tester.
- 1:17The Testing CalendarWho is testing what, and when, with the engagements nobody holds yet waiting underneath.
- 1:29The EngagementThe engagement’s own page, with a switch on each part for what the client sees, and the method’s checklist for each phase.
- 1:42Writing a Finding with AI and the LibraryA tester’s rough notes pasted in, every field of the finding drafted from them in the firm’s own style, then saved as a draft in one click and shown to the client while the test is still running; and wording the firm has already agreed, brought in from its library.
- 2:32Findings from a ScannerA Nessus export brought in as findings: one for each issue with every host listed, in the library’s wording where it has the issue, and nothing written until it has been seen.
- 2:45The Executive Summary and the Report’s SectionsThe executive summary drafted from every finding and the notes; then the caveats, the retest summary and the firm’s own Attack Path section, each drafted by AI to its own prompt and kept as a draft until it is final.
- 3:07Every Finding in One PlaceEvery finding from every engagement in one place: the tester’s own first, then the team’s, filtered, sorted and updated together.
- 3:21Quality ReviewA second tester reviews it in the QA queue: a comment on a finding, and a change suggested in place and accepted in one click.
- 3:36The Report, DeliveredThe report made from the engagement in the firm’s own style; delivery held while anything is still a draft, then made, the client told by email; and the letter of attestation a click away.
- 4:04Your Client’s PortalThe client’s portal, under the firm’s brand: every engagement, each finding as it is found, marked as a draft until the write-up is final, and the reports to download.
- 4:24Retests and FeedbackA retest asked for on a finding in one click, or by closing a ticket in the client’s own Jira, ServiceNow or GitHub, which they connect from their portal; done by the firm and recorded on the finding; and the client’s rating of the work, or a Google review.
- 5:08Your BrandOne product, four firms. The logo, colours, typefaces and sign-in page, and the whole portal follows.
- 5:29Your Report Templates and FilesMore than one report template: the firm’s own, and the ones of the consultancies it takes overflow work from; the report it already sends, turned into its template by the Document Builder; every file named the firm’s way; and its testing IP addresses printed on every report.
- 6:04Your Fields and PromptsEvery finding field renamed, reordered, required or added, and the prompt each one is written with.
- 6:22Your Report’s Sections and MethodologyThe report’s sections renamed, reordered and chosen for the report and the client, with sections of the firm’s own; and its methodology, a checklist or runbook for each kind of test, starting from OWASP and NIST.
- 6:49Your Own AI and Your FilesThe firm’s own key for OpenAI, Anthropic or Groq, stored encrypted in its own database, or a local model; and every report and file kept in step with its SharePoint or Google Drive.
- 7:06Security and Your EmailsSessions that end when the firm says, a second factor on every account, any device signed out; and every email in the firm’s words and colours, sent only where it chooses.
- 7:31Automation and ModulesEngagements that start and complete on their dates, clients reminded to send credentials, and whatever the firm does not use switched off for everyone.
- 7:45Your Team, Your Client’s People and DashboardsThe team, each with the role they need; the client’s own people, who see their own work and nothing else; and every role’s dashboard laid out the firm’s way.
- 8:11External Teams and Their ViewExternal testers for the overflow, one at a time or a team from another consultancy; an engagement handed to a team, which everyone in it works on; and an external tester’s own screen, with the work handed to them and their team and nothing else of the firm’s.
- 8:35Your Own DatabaseA database the firm owns, which Pental cannot read a row of, and a full backup one download away.
8:57, narrated, in 24 chapters: running an engagement from a new client to a delivered report, findings written with AI in your own style, quality review, your client’s portal and retests, external testers and teams for the overflow, and everything that makes the portal your own. What each part shows