Engagement FAQ
Quick answers on scope, timing, confidentiality, and delivery so you can move forward with confidence.
What exactly is tested during a pentest engagement?
Testing is tailored to your agreed scope and usually covers authentication, input handling, access control, business-logic abuse, exposed services, and common attack paths in your web app, API, or network surface.
How does scoping work before the project starts?
We run a short scoping call to confirm assets, goals, test windows, and constraints. You then receive a clear written scope and quote before any testing begins.
How long does a typical pentest take?
Most SMB engagements are completed within 5 to 10 business days from test start to final report, depending on scope size, environment readiness, and whether multiple systems are included.
What deliverables will we receive?
You receive an executive summary for stakeholders, technical findings with severity ratings, clear reproduction steps, remediation guidance, and a live walkthrough to answer questions with your team.
How is confidentiality and data handling managed?
Confidentiality is built into every engagement through NDA-friendly workflows, least-privilege access, secure evidence handling, and sanitized reporting practices that avoid exposing sensitive business or customer data.
Can we request re-testing after fixes are deployed?
Yes. Targeted re-testing can be scheduled once fixes are live, and confirmed results are documented in an updated verification note so you can show closure to clients, auditors, or internal leadership.
Start Your Pentest Conversation
Request a Quote for Expert-Led Penetration Testing
Get fast scoping, clear communication, and direct collaboration with the specialist doing the work.