Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • #355519
Closed
Open
Issue created Mar 10, 2022 by Daniel Paul Searles@dsearlesContributor1 of 2 checklist items completed1/2 checklist items

FIPS compliant Secret Detection template

Why are we doing this work

FIPS compliance is a requirement for the US Govt to utilize a piece of software. It is required for any FISMA or FedRAMP system, and cannot be waived.

In order for GitLab to be directly usable within the US Govt, we need to be compliant.

Relevant links

  • FIPS 140-2 Compliant GitLab
  • Sec section FIPS Compliance (Secure and Protect)
  • Predefined CI variable to indicate FIPS mode for security analyzers

Non-functional requirements

  • Documentation:
  • Testing:

Implementation plan

Template change consensus reached here

When FIPS mode is enabled in GitLab, the template should automatically use the FIPS version of analyzer. This will occur through a new variable _VERSION_TAG. The rules of the job will correctly set _VERSION_TAG to -fips when CI_GITLAB_FIPS_MODE is set to 'true'.

Edited Apr 15, 2022 by Lucas Charles
Assignee
Assign to
Time tracking