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.
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.
Use it forApprove pentests in a legally clean way.
Use it forRecord test mandates bindingly.