For: Companies Private IT Partner v1.0.816 · Swiss Made
For: v1.0.816 · Swiss Made

Rules of engagement

BETA

The ground rules and approvals before security tests may be run at a client.

Rules of Engagement: documented approvals and boundaries for pentests per client.

← All modules
A LOOK INSIDE
Rules of engagement · Overview Rules of engagement · Overview
Overview Sample data

Before a security test starts at a client, clear ground rules are needed. In the Rules of Engagement you record what may be tested, in which time window and with which contact persons. The client signs the document online or on paper. Only then do you create the pentests and audits that belong to the engagement.

The engagement hub takes each engagement through four phases: definition, signature, delivery, result. An engagement covers client, period, testing hours, scope of services and the Rules of Engagement with scope, exclusions, allowed and forbidden methods, contacts and emergency contacts. A click builder based on ROE templates compiles answers into the text fields; an AI assistant drafts rules text and methods. For signature, a capability link goes to the client by e-mail; alternatively you upload the signed PDF or skip the signature at the client's request. Only then does the portal provision pentests, audits and reports.

Features
  • Create an engagement: choose client, period and scope of services (pentests, audits, OSINT)
  • Assemble the ground rules via a click questionnaire or enter them as text
  • Have a draft of the rules text created with AI assistance
  • Output the document as PDF or Word and send it to the client for signature
  • Record the signature online via link or as an uploaded PDF
  • After signature, create the pentests, audits and reports for the engagement
  • Four process phases with counters: definition, signature, delivery, result
  • Scope of services from pentest, audit and OSINT types; determines template and later deliverables
  • Click builder from ROE templates compiling into scope, methods, testing hours and rules
  • AI draft for rules text plus allowed and forbidden methods
  • PDF and Word export in the partner document layout; assets with in-scope marking
  • Signature via e-mail link (name and confirmation), PDF upload or deliberate skipping
  • Status not signed, sent, signed, skipped, expired; sending and signing in the audit log
  • Signing freezes the document with a hash; it is then locked, and the signature can be revoked
How it works
  1. Create an engagement and choose client and scope of services.
  2. Answer the questionnaire or enter scope, time window and contacts as text.
  3. Send the document for signature or upload the signed PDF.
  4. After signature, create the pentests and audits and start the test.
  1. Create the engagement with client, period and scope of services.
  2. Work through the click builder and compile the answers, or use the AI draft.
  3. Export the PDF or send the signature link to the client.
  4. After signature, provision the deliverables and start delivery.

Use it forApprove pentests in a legally clean way.

Use it forRecord test mandates bindingly.