## Why are we doing this work The Secure section of GitLab uses inconsistent and sometimes ambiguous terminology across its UI and documentation. This creates confusion for users and internal teams, slows down onboarding, and makes it harder to maintain the product over time. To address this, we need to perform a comprehensive audit of terminology usage and establish a consistent mapping to standardized terms. This work is part of the broader effort to align terminology across the Secure section. ## Relevant links - Epic: https://gitlab.com/groups/gitlab-org/-/epics/17820 - Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/503371 (Introduced Report Type and Scanner filters) ## Non-functional requirements - [ ] Documentation: xx - [ ] Feature flag: We can use a feature flag for now. - [ ] Performance: Doesn't Apply - [ ] Testing: ## Implementation plan Main focus areas - Use Report Type instead of “Tool” or “Scan Type” where appropriate - Ensure Scanner is used consistently across all UI components - Display Vendor where relevant, using clear and accurate labeling - Make Identifier handling consistent and easy to understand Key principles throughout - UI labels should match glossary definitions exactly - Filtered search components should use standardized filter keys and display names - Help text and tooltips should clarify terminology when needed - Avoid introducing or reusing deprecated terms (e.g. Tool, Analyzer) --- This issue will be split into three child issues: #### Vulnerability Report _Goals:_ - Replace `Tool` with `Report `Type` in all relevant places - Standardize filter names and column headers - Ensure terminology is consistent between project and group-level views _Updates needed in:_ - Individual Vulnerability Report page - Filtered search components use standardized filter names #### Security Dashboard _Goals:_ - Replace “Tool” and “Scan Type” with “Report Type” where relevant - Ensure consistent use of “Scanner” and “Vendor” - Update all filter names, group-by options, and column headers _Updates needed in:_ - Project, group, and instance-level Security Dashboards - Development Vulnerabilities (Group level) filters - Operational Vulnerabilities (Group level) filters #### Pipeline Security ## Verification steps <!-- Add verification steps to help GitLab team members test the implementation. This is particularly useful during the MR review and the gitlab~11090870 step. You may not know exactly what the verification steps should be during issue refinement, so you can always come back later to add them. 1. Check-out the corresponding branch 1. ... 1. Profit! -->