Evaluate legacy Vuln Mgmt data models looking for data integrity issues

Topic to Evaluate

We've run into several data integrity issues in Vulnerabilities migrated from Findings. Some of the code is not reading and/or writing some of the data. Data existed in the old model, but all code is not using the new model. And data from old needs to be migrated to new.

Based on synchronous discussions in the Threat Insights group, this issue was created to ensure that other data integrity issues do not exist between legacy and current data models.

Previous data integrity issues:

• #223770
• #217600 (closed)

Tasks to Evaluate

Spike Timebox: 2 days.

• Identify redundant information in the vulnerability DB structure (can be done in tandem with #223915 (closed))
• Determine if existing data needs to be copied from its current location and create data migration issues for each of them(please make sure to propose a checksum mechanism to verify the migration was successful or at least a method to verify the record counts)
• Identify the places in application logic where different places are using different data sources(which was the root cause of #223770) for the same entity(from the end-user perspective) and create issues for each inconsistent behavior with references to places in the codebase

Note: Please create an epic to attach all the issues which are the outcome of this issue if you end up with creating more than 1 issue.

Risks and Implementation Considerations

No risks are expected from performing these tasks.