Clean up the use of project_fingerprint and ignore the unnecessary column project_fingerprint from the security_findings table, vulnerability_findings table and all related entities

Why are we doing this work

We are in the process of deprecating the usage of the project_fingerprint attribute of the findings. By using uuid values to identify findings, we can easily associate any related entity with finding.

As we already have the uuid attribute for security_findings, we can remove the unnecessary columns from this table and for the vulnerability_findings table.

Implementation plan

• backend Clean up the use of project_fingerprint
• backend Ignore the project_fingerprint column from the vulnerability_occurrences table
• backend Ignore the project_fingerprint column from the security_findings table
• backend Ignore the project_fingerprint column from the vulnerability_feedback table