A pentest engagement can contain findings before its final report is ready. The Sythe platform keeps those views separate so you can inspect the work without treating an unfinished deliverable as the final record.
Start in Pentest inside your organization and open an engagement you can access. This is a walkthrough of the customer view. It does not assume you hold a tester's editing permissions.
Resolve the engagement prerequisite
If the engagement presents a liability-waiver signing card, review and complete the required authorization before expecting the engagement panels to appear. The person signing needs the authority to approve that agreement.
For an existing authorized engagement, open Activity. The Live findings section is the place to inspect findings made available through the engagement. Select a finding to read its detail rather than relying on the summary list alone.
Keep the finding's described scope in view when discussing it with engineering. A result about one route or asset should not quietly become a claim about every system your company operates.
Review coverage separately from findings
Open Coverage map to review the completed engagement's surface coverage. The customer view explains when coverage is not yet available. Treat that state as unfinished work, not as evidence that every surface has been tested.
The engagement also provides a Network diagram tab. Use the available engagement context when aligning your team's understanding of scope. A diagram and a findings list answer different questions; neither should substitute for the agreed testing boundaries.
In a tailored demo, this is a useful point to ask which product, environment, and account roles the buyer needs tested. The discussion should stay grounded in the engagement rather than a generic promise to test everything.
Read the published PDF when it is available
Open Report. If the report is not published, the page shows Report in preparation. Once the published PDF is available, review it and use Download PDF to obtain the delivered document.
Check the report's scope and date before using it in a customer security review. If you share a limited version through another process, identify that version clearly and retain the full delivered report under the appropriate access controls.
The platform overview explains how penetration testing fits beside the other security workflows. An engagement's report remains a specific deliverable with its own scope.
Agree on the next verification step
When engineering has addressed a finding, coordinate verification through your engagement contact and agreed retest process. This customer walkthrough does not include a self-service retest button or assume that changing a ticket status verifies the repair.
Before sending the report onward, decide who owns any remaining findings and what evidence the recipient needs about their resolution. A published PDF establishes delivery; it does not make an open issue disappear.