Continuous projects are suitable for projects that don't have a specific end-date or are never completed, for example:
- Vulnerability assessments
- SOC
We support three primary use cases: Manual Import Run based, Integrated Scanner Run based, and Real-time. You can choose the appropriate use case during creation in the Project Template or later in the Project Settings under the Runs tab.
1. Manual Import Run based
This use case is designed for periodic scans (e.g., weekly or monthly iterations) where you manually add or import findings.
2. Integrated Scanner Run based
This use case is suitable when a vulnerability scanner is integrated to automatically sync and manage findings.
3. Real-time
When you require an ongoing project where findings are not linked to periodic runs, use the Real-time scenario.
Working with Runs
When working in a Run-based use case, you add or import findings to a Draft Run. You are fully permitted to edit Draft Runs as well as Completed Runs to refine your data before finalizing.
Once all findings are prepared in your manual draft, click Complete Draft Run. This merges your draft with existing findings from previous runs. During this merge, the platform calculates which findings are New and which are Fixed compared to the previous run. Clients only see findings from Completed Runs.
New vs Fixed
When you complete a run, the platform calculates the status of findings compared to the previous run:
New: The finding was not present in the previous Run.
Fixed: The finding was present in the previous Run but is no longer in the current Draft/Latest run.
Processing Run Complete
When the Draft Run is completed—either manually or by an Integrated Scanner—you can determine how the system processes matching data:
Fields data on finding match:
Keep existing finding fields data: When a finding matches a previous one, no data is modified.
Override fields data with new matched finding: When a finding matches a previous one, this option will override finding fields (recommendations, remediation, description, etc.) with the new matched finding data.
Close Finding when:
- There is no matching Finding - This closes the finding to the Fixed status when the Finding is not in the Draft Run.
- There is no matching Finding and Assets are up (there are other Findings for the same Assets) - This checks if the Asset is up by the presence of any finding for that Asset. This option should be using in combination with the "Not aggregate findings evidence" in the import, so you get 1 finding per Asset. When the Finding is not present in the Draft Run, but the Asset is up, the Finding is marked as "Not Found", but it's not closed, keeps current status.
Report Generation
You can trigger automatic report generation per scan iteration by activating the Automatically generate report on Run Complete setting in your Run configurations.