Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 51,742
    • Issues 51,742
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,574
    • Merge requests 1,574
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #350408
Closed
Open
Issue created Jan 14, 2022 by Connor Gilbert@connorgilbert⏳Developer

Assign Severity values to Security Code Scan findings

Problem

The Security Code Scan analyzer (for .NET/C#) currently outputs all findings with a severity level of Unknown.

Impacts include:

  • It's harder for security and development teams to understand which findings need to be addressed.
  • Customers can't implement merge request approvals and other controls based on finding severity.

Anticipated solution

Adopt a similar approach to other analyzers where we provide a severity based on our analysis of associated CWEs, likely following the approach outlined on &4004.

ℹ This issue is promoted from previous discussions in other contexts, including on the parent epic.

Edited Jan 21, 2022 by Connor Gilbert
Assignee
Assign to
Time tracking