Penetration Tests

Learn how to manage your penetration testing process from start to finish.

The Penetration Testing (PT) Interface simplifies the entire testing process, enabling seamless collaboration and tracking within the platform. It eliminates the need for external communication, keeping everything centralized and transparent.

Main Screen Overview

The main screen provides a comprehensive view of all your penetration tests:

• Tester: The name of the PT tester assigned to the test.
• Dates: Gives the start and end dates of the test.
• Status: Shows the current status of the test.

Click on the test to manage the process step-by-step.

Messaging Component

The platform includes a Messaging Component for direct communication with the tester. Use this to:

• Tag testers for clarification or updates.
• Provide critical details or ask questions at any stage.

The messaging feature ensures smooth collaboration without relying on external tools.

 Step 1: Scoping

This step defines the scope and expectations of the test.

• Scope File:

  • The tester provides a document outlining the test's scope.
  • View or download the file to ensure transparency and alignment.

• Requirements:

  • The tester may request credentials, URLs, or other resources needed for the test. You will be prompted to provide specific requirements for the test.

For each requirement, click Submit Requirement, then:

• Add a Link: Provide a relevant link to support the requirement.
• Upload a File: Attach a document or file as needed.

Once all requirements are submitted, the process will move to the next step: Testing.

 

Step 2: Testing

The tester is actively working on your testing.

If you have any questions or updates, use the messaging component to communicate directly with the tester.

If there are critical updates, the tester will reach out to you. Once testing is complete, they will share with you the initial report.

Once testing is complete, the process will automatically move to the next step: Initial Report.

 

Step 3: Initial Report

The third step involves reviewing the initial report and addressing findings:

You can review the findings directly in the platform and create Jira tickets for your team. After reviewing, prioritize which findings you want to focus on for re-testing.

Once resolved, mark them as ready for re-testing so the tester can validate the fixes.

The process will then move to the next step: Re-Testing.

 

Step 4: Re-Testing

In this phase, you’ve selected specific findings for re-testing after addressing them on your side.

The platform will show you which findings are currently being re-tested, giving you insights into the progress.

Once the re-testing is complete, the process will move to the final step: Final Report.