Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36,968
    • Issues 36,968
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,430
    • Merge requests 1,430
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #323281

Closed
Open
Created Mar 02, 2021 by Russell Dickenson@rdickensonMaintainer

Improve the introductory Secure docs to help those who are responsible for oversight of vulnerabilities and issues

Problem to solve

Secure's documentation is largely aimed at the Developer persona. We should also be providing content for those who monitor, manage, and report on projects' security status.

Proposal

Implementation:

  • Highlight the vulnerability oversight features available in GitLab:
    • Security Dashboard
    • Vulnerability Report
    • Security Center

This content could be added to the introductory Secure docs page.

Who can address the issue

Other links/references

technical-writing#343

Assignee
Assign to
13.12
Milestone
13.12
Assign milestone
Time tracking