Projects
Projects Overview
Understand how projects work in Vulnsy, representing individual pentest engagements with types, dates, team assignments, and linked reports.
A project in Vulnsy represents a single penetration testing engagement. Projects belong to a client and contain all the reports, findings, and scope details for that engagement.
What Is a Project?
Each project captures the key details of an engagement:
| Field | Description |
|---|---|
| Name | A descriptive name for the engagement |
| Description | Summary of the engagement scope and objectives |
| Client | The client company this project belongs to |
| Type | The category of assessment being performed |
| Status | Current state of the engagement |
| Start Date | When testing begins |
| End Date | When testing is expected to conclude |
| Operators | Team members (consultants) assigned to the project |
Project Types
Vulnsy supports the following project types:
| Type | Description |
|---|---|
web_app | Web application penetration test |
infrastructure | Internal or external infrastructure assessment |
mobile | Mobile application security testing |
cloud | Cloud environment security review |
api | API security assessment |
iot | IoT device and firmware testing |
The project type is included in report exports via the {project.type} template tag, so it appears in your deliverables automatically.
How Projects Fit into Vulnsy
Projects connect clients to reports:
- A Client has one or more Projects
- A Project contains one or more Reports
- Each Report contains Findings (vulnerabilities)
Project details like name, type, and dates are available as template tags in your DOCX exports, reducing manual data entry when generating reports.
Next Steps
- Creating Projects — set up a new engagement
- Scoping Calculator — estimate effort and costs
- Reports — build and export reports within a project