SCOPING

Work out what your assessment needs.

Select your target systems, specify asset quantities and architectures, and define operational constraints to build a structured scope summary ready to attach to your proposal request.

Effort is indicative and defined in technical assessment units. Nothing entered leaves your browser.

What needs testing?

Choose every assessment area that applies. Provide the relevant details for each selection.

Web applicationOne application, authenticated, two to three roles, moderate distinct functionalityMobile applicationOne platform, plus its backing API. Both platforms is not double, because the backend is sharedExternal networkPerimeter, up to roughly fifty distinct live hostsInternal networkOne site or segment, assumed-breach starting positionAPIDocumented, one authorisation model. Undocumented adds discoveryCloud configuration reviewOne account or subscription, against a recognised benchmarkSecure code reviewTargeted at security-relevant components, not the whole treeRed teamObjective-based, multi-vector, several weeks of elapsed time

Constraints and testing conditions

Production access, restrictive windows, multiple environments and dependencies affect scope and delivery planning.

Target environment: production or staging?

Production testing requires coordinated rollback planning and safe execution, whereas staging environments must accurately mirror production configurations.

When can the assessment take place?

Assessments during standard working hours allow direct engineer contact, while night or weekend restrictions require planned out-of-hours coordination.

Target engagement timeline

Available lead time and delivery goals determine team availability, testing milestones, and whether parallel test streams are needed.

Retesting and remediation verification

Verification testing confirms whether reported vulnerabilities were remediated effectively and provides objective evidence for stakeholders and auditors.

Retesting is included only where specified in the accepted quotation or agreement.

What to do with your scope summary

Use your summary to start a focused discussion about the systems you need assessed, the access available and the boundaries your team needs to maintain. It gives both sides a clearer starting point for defining the engagement.

The summary is preliminary, not a quotation or authorization to test. Before work begins, Trixent Security confirms the final scope, testing conditions, deliverables and commercial terms with the client.

Talk to Our Team