> For the complete documentation index, see [llms.txt](https://docs.softwaresecured.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.softwaresecured.com/pentesting-with-software-secured.md).

# Pentesting with Software Secured

<figure><picture><source srcset="/files/gZ0DjiXp0jp759A19H6v" media="(prefers-color-scheme: dark)"><img src="/files/67ZjtppGW8wsxj3VmYjj" alt=""></picture><figcaption></figcaption></figure>

Welcome to this how-to guide for your penetration test—also known as a pentest—with <code class="expression">space.vars.company\_name</code>! By now, you've decided to get a pentest or other service from us, and we are looking forward to helping you improve your security and compliance across your products.&#x20;

## Penetration testing overview

When you begin a pentest with <code class="expression">space.vars.company\_name</code>, you get comprehensive and thorough testing from beginning to end.&#x20;

The testing process includes the following order of operations:

1. [Preparing your environment for the testing team](/planning/preparing-your-environment-for-the-testing-team.md).
2. Completing the [Pentest checklist](/checklist/pentest-checklist.md) (including the [Infrastructure summary](/checklist/infrastructure-summary.md)).
3. Participating in the [Kickoff call](/planning/kickoff-call.md).&#x20;
4. Monitoring progress [During the active pentest](/planning/during-the-active-pentest.md).&#x20;
5. [Viewing and acting on your pentest results](/findings/viewing-and-acting-on-your-pentest-results.md).&#x20;

Once your test is complete, you will have everything you need to start remediating any issues that were identified.

1. [Remediating vulnerabilities](/after-testing/remediating-vulnerabilities.md) and tracking your progress related to the [Service Level Agreements (SLAs)](/findings/service-level-agreements-slas.md).
2. [Retesting your vulnerabilities](/after-testing/retesting-your-vulnerabilities.md) after remediation.
3. Sending [Consultation requests](/after-testing/consultation-requests.md) to review complex issues.
4. [Viewing and downloading reports and executive summaries](/reports-and-certificates/viewing-and-downloading-reports-and-executive-summaries.md).&#x20;

## Portal overview

Use <code class="expression">space.vars.product\_name</code> during the pentest to stay on top of your test's schedule, tasks, and results all in one place. &#x20;

The following tasks are completed in <code class="expression">space.vars.product\_name</code> during your pentest:&#x20;

1. Completing [User management](/account/user-management.md) tasks and enabling any [Integrations](/account/integrations.md).
2. Filling out the [Pentest checklist](/checklist/pentest-checklist.md) (including the [Infrastructure summary](/checklist/infrastructure-summary.md)).
3. Reviewing the [Pentest start date and rescheduling](/planning/kickoff-call/pentest-start-date-and-rescheduling.md) as required.&#x20;
4. [Viewing and acting on your pentest results](/findings/viewing-and-acting-on-your-pentest-results.md).&#x20;
5. Tracking remediation with your issue-tracking integrations (such as [Jira](/account/integrations/jira.md)).&#x20;
6. Sending requests for [Retesting your vulnerabilities](/after-testing/retesting-your-vulnerabilities.md).&#x20;
7. Sending [Consultation requests](/after-testing/consultation-requests.md).&#x20;
8. [Viewing and downloading reports and executive summaries](/reports-and-certificates/viewing-and-downloading-reports-and-executive-summaries.md).&#x20;

Can't find the answer you are looking for? Send us an email at [<mark style="color:orange;">portal@softwaresecured.com</mark>](mailto:portal@softwaresecured.com).