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

Pentests

BETA

The overview of the security tests you run for clients.

Coordination and documentation of pentests across the managed client companies.

← All modules
A LOOK INSIDE
Pentests · Overview Pentests · Overview
Overview Sample data

Here you manage the security tests you perform for clients. A pentest originates from a signed engagement (Rules of Engagement). You work through a test plan, record the vulnerabilities found and track how they are dealt with. The findings feed into the client report.

The module runs pentest runs with an identifier (PT number), target, type, tester, period and status (scheduled, active, report delivered, cancelled). Runs originate from an engagement, via provisioning or manually in the ROE context. The detail view bundles the methodology test plan with categories and test steps including status and notes, the assets from the ROE with scope selection, the findings and the linked reports. Findings carry severity, CVSS vector and score, description, observation, remediation, PoC, tools and commands, CWE, CVE and WSTG ID.

Features
  • Manage pentests per client with target, test type, tester, period and status
  • Apply a test plan from a methodology template and tick it off step by step
  • Record vulnerabilities with severity, description, observation and recommendation
  • Take templates from the vulnerability library into a finding
  • Track the state of each finding; improve texts with AI assistance
  • Run types: web app, internal and external network, social engineering, wireless, mobile, cloud, API, OSINT, full scope
  • Methodology test plan from system or own templates; status and notes per test step, finding directly from the step
  • Findings with severity, CVSS, observation, remediation, PoC, tools, commands, CWE, CVE, WSTG ID and images
  • Insertion from the vulnerability library into the finding editor
  • AI text assistant for description, observation, remediation and PoC
  • Finding counters per severity; links to reports and engagement
How it works
  1. Create the pentest from within the engagement.
  2. Apply the matching methodology template and work through the test plan.
  3. Record findings directly from the test step or from the library.
  4. Keep the finding status up to date and create the report.
  1. Provision the run from the engagement or create it there manually.
  2. Apply the methodology template and set the status per test step.
  3. Raise findings from test steps or from the library and complete them.
  4. Progress the finding status and generate the report.

Use it forPlan pentests and record results.

Use it forSteer test engagements and track findings.