Skip to main content

​
Create and run an engagement

Use this workflow when you are moving from setup into live delivery work. Diagram of the engagement lifecycle from customer setup through portal delivery

​
Prerequisites

  • You can open Customers and Engagements
  • A valid customer record exists, or you can create one with customer-creation access
  • A team already exists if your org requires team assignment at engagement creation
  • You have engagement-creation access if you will create the record yourself

​
Steps

1

Confirm or create customer context

Open Customers and verify the customer record and points of contact are current. If no customer exists yet, use Create Customer to add the record and primary point of contact first.
2

Create the engagement

Open Engagements and select Create Engagement. Complete the intake form: title, description, engagement type, scope summary, dates, customer, team, report title, report template, and finding layout. Add optional tags, supporting notes, and a QA reviewer. New scoping-file uploads are unavailable in the pilot.
3

Open the initial report workspace

After a successful create, Strikepoint redirects you into the engagement’s first structured report workspace. Confirm the template and report title match your delivery plan.
4

Review the engagement detail page

Return to the engagement workspace to confirm linked customer, team, any existing scoping artifacts, collaborators, and active status.
5

Align collaborators and credentials

Use the collaborator and credential sections on the engagement detail page so the right people and access material are assigned before work begins. Store credentials only after pilot GO and reveal them only through the current-password step-up flow.
6

Capture endpoints and service context

Add endpoints manually, import Nmap XML if available, or use the service inventory view to understand exposed services and prepare for finding creation.
7

Draft findings and track remediation

Create findings from the engagement, then open the finding detail route for full writeup fields, existing evidence attachments, and remediation workflow state. New evidence-file uploads are unavailable in the pilot. Use the remediation page or remediation dashboard when you need owner, due date, retest, and SLA tracking.
8

Prepare for reporting and portal delivery

Once findings are stable enough for delivery, continue in the report workspace, coordinate review, and publish approved snapshots to the customer portal when ready.