Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #56668

Closed (moved)
Open
Opened Jan 22, 2019 by Fabio Busatto@bikebillyContributor0 of 3 tasks completed0/3 tasks

Use Container Scanning for our GitLab images

Problem to solve

We create Docker images during our GitLab development in different places:

  1. GitLab releases
  2. GitLab Review Apps
  3. GitLab security features
  4. ...

We should use our Container Scanning features to check the security of those images, and figure out if we need to introduce new features to support our internal flow.

Proposal

  • Check why Container Scanning is not used in our internal projects
  • Improve the feature to support our internal flow, if needed
  • Enable Container Scanning for our internal flow (releases, review apps, security products, etc)
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-foss#56668