Projects : About Projects

About Projects

A project contains the workspace that you use to perform the different steps for a penetration test and store the data that you collect from the target. Projects are useful tools that you can use to set up tests and organize the data that you gather from target machines. You can create as many projects as you need, and you can switch between projects while tasks are in progress.
From within a project, you define the targets that you want to test and configure the tasks that you want to run against those targets. You can scan targets for active services and hosts, attempt to exploit vulnerabilities, collect data from exploited machines, and generate reports that detail your findings.
Every project has an owner. The owner can choose the users who can access the project to edit, view, and run tasks. However, users with administrative access can view and edit any project, regardless of whether or not the project owner gives them access.
You can create projects to separate an engagement into logical groupings. Oftentimes, you may have different requirements for the various departments, or subnets, within an organization. Therefore, it may be more efficient for you to have different projects to represent those requirements.
For example, you may want to create a project for the human resources department and another project for the IT department. Your requirements for these departments may vary greatly, so it would be logical for you to separate the targets into different projects. At the end of the engagement, you can generate separate reports for each department to perform a comparative analysis and present your findings to your organization or client.