Scope
Define the client, targets, methodology and limitations. Set the context before the findings.
PXLQuill / Security reporting
Your expertise.
Clearly delivered.
Turn assessment notes, findings and evidence into reports your clients can understand—and their teams can act on.
Invitation-managed access. Your own workspace. Your report, your brand.
Explore the real workspaceSynthetic data · Actual application captures
Structured findings + evidenceFive editable report designsVersioned PDF + Word exportsShared PXLAccess sign-in
The complete workspace
More than a polished
document.
Follow the work from first scope to final handover. Choose a workflow below to explore the actual interface.
01 / Write
A report starts with a clear story.
Build the scope, executive narrative and technical detail together. Shape the document around the assessment—not around a blank page.
- Engagements and client recordsAssessments, dates, scope, exclusions, client details and contacts.
- Rich narrative editingHeadings, quotes, lists, tables, links, text colour and highlights.
- Autosave and recoverySaved-state feedback, retry controls and version-conflict handling.
02 / Findings
Technical depth. Reader-first structure.
Give every issue a useful explanation, reproducible steps and a defensible assessment. Keep severity, validation and remediation separate.
- Structured finding authoringDescription, impact, proof, remediation and affected components.
- Severity and scoringSeverity selection, supported CVSS scoring and CWE references.
- OWASP classificationRecord the OWASP Top 10 categories supported by the finding.
03 / Evidence
Give the reader something to follow.
Keep supporting material beside the claim it supports. Control captions and image placement, then inspect the generated document.
- Evidence attachmentsAttach supported screenshots and files to the assessment.
- Narrative illustrationsInsert attached evidence images into the supported narrative editors.
- Captions and orderingExplain each illustration and control the selected report order.
04 / Reuse
Your knowledge should compound.
Reuse strong starting points without carrying yesterday’s customer data into tomorrow’s engagement.
- Finding libraryStart from reusable finding patterns and adapt them to observed evidence.
- Engagement templatesReuse supported scope, methodology and report-purpose defaults.
- Reusable report sectionsMaintain shared chapter content and select it deliberately.
05 / Design
The report should look like your work.
Choose a starting design, then tune the brand and structure. Preview templates without creating an engagement.
- Five starter designsClassic, Modern, Minimal, Editorial and Technical.
- Cover and closing pagesCustomise supported branding, wording, author details and contact information.
- Layout controlsConfigure section order, spacing, image sizing and finding page starts.
06 / Deliver
One deliberate version at a time.
Review the version you intend to share. Preserve the history when the working draft changes.
- PDF and Word exportGenerate actual PDF and DOCX deliverables from saved content.
- Four report purposesTechnical, management summary, narrative / red-team and no-findings reports.
- Frozen report versionsKeep generated content and design separate from later draft edits.
From first note to final version
A connected reporting workflow.
Not another blank document.
Keep the scope, the technical detail and the story in one engagement. Generate a deliberate snapshot when you are ready to review.
Substantiate
Write clear findings, attach evidence and distinguish validation from severity.
Shape
Choose an editable design. Build the executive story alongside the technical detail.
Deliver
Generate a version, review it and export the files you intend to share.
01 / AUTHORMake the finding
Make the finding
make sense.
Write the impact, reproduction and remediation in a structured workspace. Keep evidence close, use consistent severity and make uncertainty explicit. Reusable finding patterns give you a starting point without replacing your judgement.
Explore the workflow ↗02 / SUBSTANTIATEEvidence with context.
Evidence with context.
Not loose attachments.
Connect screenshots and supporting material to the assessment. Add captions that explain what the reader is seeing, then check their placement in the actual report.
Explore the workflow ↗Your expertise. Your identity.
Five starting points.
Make one your own.
Explore the cover, report body and closing page for every design. These are real Quill template previews, not illustrated mockups.
Editable report profile
Classic
A formal structure with a strong margin and clear document details.
- Brand, accent and classification
- Cover and closing content
- Section order and layout controls
- Reuse across future reports
These previews illustrate the design. Generate a report to inspect final PDF and Word pagination.
04 / CONFIDENCEThe version you review.
The version you review.
The version you deliver.
Working drafts and generated reports have different jobs. Save an immutable report version, check its readiness, review the content and keep the history when the draft changes. Export PDF and Word for your delivery workflow.
Explore the workflow ↗Built around the people doing the work
Different teams.
A clearer handover.
Standalone focus. Shared access.
Use Quill on its own.
Connect through PXL.
PXLQuill is a reporting product in its own right. You do not need PXLLens or PXLRadar to write and deliver reports.
- Enter through PXLHub and sign in with PXLAccess.
- Keep personal work and organisation workspaces separate.
- Grant product access deliberately through managed invitations.
- Use PDF and Word in your existing delivery process.
Shared identity does not mean automatic access to every product. Cross-product scan-to-report automation is not promised by this page.
Choose the document, not just the cover
One assessment.
Four report purposes.
Technical report
The full technical story: finding detail, proof, evidence and remediation.
Management summary
A concise leadership view. Detailed proof, attachments and retests are omitted from this output.
Narrative / red-team
An operation story with scenarios, custom chapters and a conclusion. Findings are optional.
No-findings report
Document the scope, limitations and conclusion. An explicit no-findings result is not a security certification.
Built for the whole reporting process
The details make the difference.
A practical feature reference. Expand a category to see the controls behind the workflow.
01Write5 capabilities
- Engagements and client records
- Assessments, dates, scope, exclusions, client details and contacts.
- Rich narrative editing
- Headings, quotes, lists, tables, links, text colour and highlights.
- Autosave and recovery
- Saved-state feedback, retry controls and version-conflict handling.
- Custom report chapters
- Add an attack narrative, recommendations or an appendix in the supported section positions.
- Methodology and limitations
- Document the approach and the boundaries of your conclusions.
02Findings6 capabilities
- Structured finding authoring
- Description, impact, proof, remediation and affected components.
- Severity and scoring
- Severity selection, supported CVSS scoring and CWE references.
- OWASP classification
- Record the OWASP Top 10 categories supported by the finding.
- Affected instances
- Track occurrences without duplicating the entire finding narrative.
- Custom fields and field sets
- Capture additional structured detail and reuse supported field sets.
- Report inclusion
- Choose included findings independently of the current list filters.
03Evidence4 capabilities
- Evidence attachments
- Attach supported screenshots and files to the assessment.
- Narrative illustrations
- Insert attached evidence images into the supported narrative editors.
- Captions and ordering
- Explain each illustration and control the selected report order.
- Evidence manifest
- Generated reports document the supporting material and provenance.
04Reuse5 capabilities
- Finding library
- Start from reusable finding patterns and adapt them to observed evidence.
- Engagement templates
- Reuse supported scope, methodology and report-purpose defaults.
- Reusable report sections
- Maintain shared chapter content and select it deliberately.
- Burp XML import
- Preview and select imported findings before completing their report context.
- Nessus import
- Bring scanner results into the reporting workflow for review and validation.
05Design5 capabilities
- Five starter designs
- Classic, Modern, Minimal, Editorial and Technical.
- Cover and closing pages
- Customise supported branding, wording, author details and contact information.
- Layout controls
- Configure section order, spacing, image sizing and finding page starts.
- Saved report profiles
- Search, preview and reuse profiles across future report versions.
- Custom Word templates
- Use compatible DOCX templates. PDF retains its built-in renderer.
06Deliver7 capabilities
- PDF and Word export
- Generate actual PDF and DOCX deliverables from saved content.
- Four report purposes
- Technical, management summary, narrative / red-team and no-findings reports.
- Frozen report versions
- Keep generated content and design separate from later draft edits.
- Version comparison and archive
- Find and compare the saved versions relevant to your handover.
- Editorial review
- Review comments, wording suggestions, readiness and approval controls.
- Retest records
- Document follow-up observations and remediation outcomes.
- Delivery packages
- Prepare the eligible saved version and supporting files for your delivery process.
PXLHub + PXLAccess
Shared sign-in, selected workspaces and managed invitations. Enable Quill on its own; other product seats are optional.
Access and workspaces ↗The actual deliverable
Open the report.
See what leaves your desk.
Eleven pages, generated by Quill. Fictional organisations, findings and evidence. Inspect every page here before downloading.
Look closer
The details, not just the headline.
Product datasheet
An in-depth look at workflows, features, access, report outputs and use cases.
Download PDF ↗The complete guide
Step-by-step documentation with full-interface screenshots and practical troubleshooting.
Read documentation ↗A report you can inspect
A real Quill-generated report using a fictional assessment and clearly labelled synthetic evidence.
Open sample report ↗Good questions
Before your
first report.
Can I use PXLQuill without the other products?
Yes. Quill can be enabled on its own. PXLAccess provides the shared identity and PXLHub provides the workspace entry point; other product seats are optional.
Can I customise the cover, closing page and report design?
Yes. Start with one of five designs and edit the supported report-profile fields. Preview the result before generating. Custom Word layouts are a separate feature and do not replace the built-in PDF renderer.
Does it save my work automatically?
Supported draft edits autosave. Watch the saved acknowledgement, and keep the tab open if a network or session problem leaves a change unsaved. The documentation explains retry and recovery.
Does Quill find or verify vulnerabilities for me?
Quill is a reporting workspace. Authors supply and validate their findings and evidence. Imported scanner results and reusable library entries still require review.
Do older report versions change when I edit the draft?
No. Generated report versions are snapshots. Generate a new version to include later edits.
How do I get access?
Request access and describe your reporting workflow. Access is provisioned through an invitation. Public self-registration and self-service paid checkout are not offered on this page.
Your next assessment. Clearly delivered.
Give your work
the report it deserves.
Tell us how your team writes, reviews and delivers security reports.
Support: [email protected] · All product examples on this page use synthetic data.