Who This Topic Is For
Users evaluating premium automated engagement paths or managing partner workflows.
Help
Premium And Partners Help
How-to for the live $297 Penetration Test and $497 Comprehensive Pentest, plus affiliate portal questions.
Prerequisites
Before You Start
Use this checklist to make sure the workflow guidance applies cleanly to your current task.
- You can define whether your need is self-serve automation or scoped premium engagement.
- You can describe the assurance level and business timeline for the engagement.
Playbook
Step-By-Step Guidance
Follow these steps in order for a reliable and repeatable outcome.
Confirm whether premium is the correct path.
Use a Penetration Test or Comprehensive Pentest when you need verified automated active testing with HTML and PDF, not a routine credit scan on the dashboard.
Pick the live pentest level.
Penetration Test is $297 with HTML, PDF, and one included retest.
Comprehensive Pentest is $497 with extra engines, up to five extra verified hosts tested, a two-role matrix when two profiles are supplied, a detailed, actionable PDF for security specialists and developers, ticket-ready remediation, an auditor-ready evidence pack, and two retests.
Cloud beta is a waitlist, not a live scanning product.
Complete consent, primary verify, and optional authenticated setup.
Confirm authorization, verify the primary hostname, and attach a healthy login profile if you need authenticated families tested. Comprehensive can add a second profile for the two-role matrix.
On Comprehensive, finish the extra-host gate and optional uploads.
Toggle up to five discovered extra hosts and verify them, or continue with the primary hostname only. Optionally paste an OpenAPI spec or upload a repository zip.
Plan confirmation stays blocked until the extra-host gate is complete.
Confirm the plan, then start now or schedule.
Review the engagement plan, then start immediately or set a start window with timezone and blackouts. Track status in the premium workspace until HTML and PDF are ready, then use the included retests for that tier.
Route partner operations through the affiliate portal.
Use the affiliate portal to enroll, share a vanity ? ref= code (clicks count for 90 days), track 20% rewards on first Pro/Team and first credit pack, and connect Stripe for payouts after the 30-day hold.
Operations
Operational Playbook
Use this long-form guidance to execute the workflow consistently across planning, implementation, and validation.
Select Premium Path Based On Assurance Objective
Premium engagement decisions should begin with assurance objective clarity. Define what confidence outcome is required, which stakeholders depend on it, and what timeline constraints apply. Premium assessments are appropriate when scoped, higher-assurance outcomes are needed beyond routine automated cadence. If the objective is still category-specific or early exploratory validation, standard tool and scan workflows may be more efficient. Objective-first selection prevents unnecessary escalation and keeps premium capacity focused on the highest-value use cases. It also improves stakeholder alignment because expectations are grounded in explicit goals rather than generic desire for deeper review.
Align Stakeholders On Live Pentest Options
Execution planning should reflect the two live pentest levels. Penetration Test is $297 with HTML, PDF, and one included retest. Comprehensive Pentest is $497 with extra engines, up to five extra verified hosts tested, a two-role matrix when two profiles are supplied, a detailed, actionable PDF for security specialists and developers, ticket-ready remediation, an auditor-ready evidence pack, and two retests. Communicate this early so commercial and technical stakeholders plan timelines around the live path they actually ordered. When teams fail to align on the selected level, they create avoidable schedule risk and expectation mismatch. Include the ordered tier in kickoff notes and repeat it during planning checkpoints. This simple control improves reliability and helps preserve trust with external and internal stakeholders who rely on accurate delivery commitments.
Define Scope Boundaries Before Engagement Starts
Comprehensive premium outcomes require clear scope boundaries before work begins. Specify which assets, environments, and objective criteria are included, and identify what is explicitly out of scope. Ambiguity here is the most common source of mid-cycle rework and delayed sign-off. Scope definition should also include communication cadence, expected deliverables, and escalation contacts. When scope is clear, both teams can execute confidently and evaluate outcomes against agreed criteria. This improves quality and reduces negotiation during delivery. For partner-assisted workflows, shared scope understanding is especially important to preserve referral trust and predictable operations.
Use The Intake, Checkout, And Queue Workflow Deliberately
Premium Assessments are not just landing pages. After payment the workspace walks authorization consent, primary hostname verification, optional login profiles, Comprehensive extra-host verify-or-continue, optional API spec or repository zip, engagement-plan confirmation, then start-now or a scheduled start window. Full refund remains available until engines start. Reports are usually ready 30 to 60 minutes after testing starts. Treat those stages as one connected workflow so stakeholders do not confuse checkout with a finished engagement.
Operate Partner Workflow Through The Correct Portal Path
Affiliate and partner operations should run through the dedicated portal workflow to maintain consistent attribution, reward tracking, and payout visibility. Avoid informal side channels for referral-state decisions, because they fragment records and create reconciliation issues. Define who within your organization can submit partner updates and who verifies payout-relevant events. This governance helps avoid disputes and supports cleaner commercial reporting. If portal behavior does not match expectation, escalate with reproducible context and account identifiers so support can resolve quickly. Structured partner operations reduce overhead and preserve relationship quality.
Build Early Escalation Habit For Commercial Edge Cases
Premium and partner workflows can involve cross-functional dependencies that are not obvious at first contact. If uncertainty appears around scope, path status, referral state, or timeline expectations, escalate early with complete context. Early escalation prevents last-minute coordination breakdowns and keeps delivery confidence high. Include intended objective, current blocker, expected milestone, and affected stakeholders in the request. Over time, this habit creates a smoother operating model where commercial and technical workflows reinforce each other instead of competing for urgency.
Measure Premium And Partner Outcomes For Continuous Improvement
A comprehensive premium and partner help model should include outcome measurement, not only process steps. Track indicators such as time to scope alignment, time to delivery milestone completion, quality of escalation context, and recurring partner workflow issues. Review these indicators on a defined cadence so patterns are identified early and process adjustments are data-driven. When one category repeatedly causes friction, update guidance and intake templates so future cycles improve. Outcome measurement supports both operational quality and trust with stakeholders, because improvements are visible over time. It also makes support interactions more effective since teams can reference prior patterns rather than troubleshooting each case as if it were entirely new.
Validation
Validation Checklist
Use this checklist to confirm the workflow was completed correctly.
- Selected path aligns with assurance and scope requirements.
- Stakeholders understand which live pentest level was ordered.
- Scope and expected outcomes are documented before engagement start.
- Premium lifecycle status is visible after the order is placed.
- Partner account is using the correct portal workflow.
- Commercial edge cases are escalated before deadlines.
Troubleshooting
Common Problems And Fixes
If something does not match expectation, check these common failure modes first.
Assuming premium path is required for all concerns
Many concerns are resolved through tools and normal scan workflows; reserve premium for scoped higher-assurance needs.
Using wrong route for partner operations
Use the affiliate portal to enroll, share a partner code, and track Stripe payouts. Commission is 20% on first Pro/Team and first credit pack only.
Planning around a pentest level that was not ordered
Confirm whether the order is the $297 Penetration Test or the $497 Comprehensive Pentest so timelines and stakeholder commitments match the live deliverable.
Treating cloud beta waitlist as a fully live cloud scanning product
The cloud beta path is currently a waitlist used to validate demand and identify qualified early testers. It should be described as interest capture, not as a generally available scanning workflow.
Plan confirmation stays blocked on Comprehensive
Verify selected extra hosts or choose continue with the primary hostname only before confirming the engagement plan.
Starting engagement without a login profile and expecting authenticated findings
Without a healthy login profile, account takeover, object-level authorization, privilege escalation, and logout session handling are not tested.
Assuming checkout means the report is already ready
Use the premium queue and status workflow after order creation so payment, intake, verification, automated execution, and final report delivery are tracked separately.
Navigate
Related Pages
Use these links to continue your workflow without losing context.
Documentation: Premium Assessments
Open Documentation: Premium Assessments to continue this workflow.
Pentest Methodology
Open Pentest Methodology to continue this workflow.
$297 Sample Report
Open $297 Sample Report to continue this workflow.
Pricing
Open Pricing to continue this workflow.
Affiliate Portal
Open Affiliate Portal to continue this workflow.
Contact Support
Open Contact Support to continue this workflow.
FAQ
Premium And Partners Help FAQs
Common questions for this topic.
Next Recommended Action
Continue to the best next page based on where you are in your workflow.