Vulnerability schema for leaked job artifacts

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Secret detection in job artifacts is different than leaked secrets found in code. There will be some subtle changes to how a vulnerability finding and record appears for this new type of leaked secret.

Proposed schema

• Description: Use the same description for secrets detected in code.
• Severity: Critical
• Project: Project Path
• Report type: Secret Detection
• Scanner: Job Artifact^1.
• Location: link to artifact/ job
• Identifiers: Rule ID

_{1. This will allow users to quickly filter for all secrets detected in job artifacts on the vulnerability report.}