Validate support Security Report versions in Security Report parsing
Problem to solve
Within our Security Report parsing logic we should validate a minimum supported report version. This better ensures we have consistent parsing and an expectation for minimum viable data.
Intended users
User experience goal
More consistency in data quality and better guarantees for normalized data within our vulnerability/finding data.
Proposal
Enforce a minimum version within our security report parser based on our security report schemas
Further details
Permissions and Security
No change to permissions
Documentation
See #223937 (closed) for documentation
Availability & Testing
What does success look like, and how can we measure that?
More consistency in vulnerability/finding data quality and fewer exceptions due to incomplete data
What is the type of buyer?
Is this a cross-stage feature?
devopssecure only