Create database columns to store CVSS vector

added to epic &11213 (closed)

changed the description

added database groupthreat insights workflowready for development labels

@Quintasan, thank you for moving this issue to workflowready for development.

Please add a type:: label to indicate the work type classification.

This message was generated automatically. You're welcome to improve it.

added devopsgovern sectionsec labels

added featureaddition typefeature labels

set weight to 1

marked this issue as blocking #424020 (closed)

mentioned in issue #422032 (closed)

changed milestone to %16.5

This issue made it to workflowready for development without the addition of a frontend or backend tech stack label. Both will be assigned as a result. Bot policy.

added backend frontend labels

mentioned in issue gitlab-org/database-team/team-tasks#371 (closed)

mentioned in issue gitlab-org/quality/triage-reports#13981 (closed)

removed frontend label

@Quintasan, is the plan to keep adding cvss_vX columns to the DB?

Is there a pattern where the version and the value are in separate columns? e.g.: cvss_vector, cvss_vector_version.

On the same note, the MVC says that we're only supporting v3.1 to start. I'm not opposed to increasing the scope, as long as it doesn't increase the effort. Trying to keep it tight so we deliver on the required due date.

Is there a pattern where the version and the value are in separate columns? e.g.: cvss_vector, cvss_vector_version.

No, at least not in our codebase.

On the same note, the MVC says that we're only supporting v3.1 to start. I'm not opposed to increasing the scope, as long as it doesn't increase the effort. Trying to keep it tight so we deliver on the required due date.

I don't suppose two columns instead of one is a significant effort increase.