Projects: on-demand pentesting

Projects let you run on-demand offensive security assessments carried out by experts (Strikers) on a defined scope.

Unlike the platform's continuous testing, Projects are built to dive into specific scenarios at a given point in time, with a manual, targeted approach.

When to use a Project

Projects are meant for scenarios that aren't covered by continuous testing of web applications or APIs.

Use them when you need to:

• Validate a new feature before launch

• Meet compliance requirements

• Assess a specific system in depth

• Run a traditional pentest within Strike's model

👉 They work as a complementary layer to continuous testing.

How to create a Project

From the Projects section:

1. Create a new project

2. Define the scope (assets / targets)

3. Set testing objectives

4. Upload relevant documentation

The project will be assigned to experts who will run the testing.

The flow of a Project

A pentesting project follows a structured flow:

1. Scope definition and quote request

2. Review and quoting by the operations team

3. Budget approval

4. Testing execution

5. Report and validation

Once the scope is defined, you'll need to coordinate with your assigned Account Manager, who handles the quote with the operations team. Once the budget is approved, the project kicks off.

Project dashboard

Every Project has a centralized view where you can:

• See the defined scope

• Check the targets

• Access files and documentation

• Track the project's status

How pricing works

Projects aren't part of the continuous model — they're contracted on an on-demand basis.

That means:

1. A Project is created or defined with its scope

2. The Strike team reviews it

3. A quote is prepared based on the effort required

4. Once the budget is approved, execution starts

Its scope depends on:

• System size

• Testing complexity

• Defined objectives

👉 They're structured as one-off assessments within the service.