Add trivy yaml v2

[Naveen-Pal]

Resolves #1288

[coderabbitai]

Summary by CodeRabbit

• New Features
  • Enhanced vulnerability scanning configuration for more flexible and precise security checks.
  • Introduced new configurable settings that allow the system to specify scan exclusions, set timeouts, and automatically ignore selected vulnerabilities.

Walkthrough

This PR updates the CI/CD workflow by replacing explicit severity parameters with a new configuration file reference (trivy-config: trivy.yaml) in multiple scanning jobs. It also adds two new files: a .trivyignore to list specific CVEs for Trivy to ignore, and a trivy.yaml that defines scanning settings (skipped directories, timeout, vulnerability rules, and severity levels).

Changes

File	Change Summary
.github/workflows/run-ci-cd.yaml	Updated four jobs (scan-code, scan-ci-dependencies, scan-staging-images, scan-production-images) by replacing severity: HIGH,CRITICAL with trivy-config: trivy.yaml.
.trivyignore and trivy.yaml	Added new files: .trivyignore listing specific CVEs to ignore and trivy.yaml with configuration for scan exclusions, timeout, and vulnerability settings.

Assessment against linked issues

Objective	Addressed	Explanation
Introduce a trivy.yaml configuration file for vulnerability scanning (#1288)	✅
Address specific vulnerabilities (e.g., CVE-2023-2953, CVE-2023-31484, CVE-2023-45853) and implement vulnerability management (#1288)	❌	The PR does not include changes for patching or exception handling for the specified CVEs.

Possibly related PRs

• Added trivy.yaml #1289: Modifies the same CI/CD workflow by replacing the explicit severity parameter with a reference to the trivy.yaml configuration file.

Suggested reviewers

• arkid15r

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

trivy.yaml (1)

1-18: Configuration File Structure and Content
The new trivy.yaml is well-structured and clearly defines the scanner settings. It designates directories to skip, sets a timeout, and configures vulnerability scanning (including ignoring unfixed issues and specifying severity levels).

Consideration: Verify that the unquoted timeout value (10m) is interpreted correctly by Trivy. If needed, quoting (e.g., "10m") might prevent any misinterpretation.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between acce9b7 and e1838b2.

📒 Files selected for processing (3)

• .github/workflows/run-ci-cd.yaml (4 hunks)
• .trivyignore (1 hunks)
• trivy.yaml (1 hunks)

🔇 Additional comments (7)

.trivyignore (1)

1-8: Clear CVE Ignore List
The .trivyignore file clearly lists the CVE identifiers along with brief comments for context. This enables Trivy to ignore the specified vulnerabilities. Ensure that the decision to ignore these CVEs has been thoroughly reviewed for risk.

.github/workflows/run-ci-cd.yaml (6)

186-186: Centralized Trivy Configuration in Code Scan Job
Replaced the explicit severity setting with trivy-config: trivy.yaml in the repository scanning step. This centralizes the scanner configuration and improves maintainability. Please confirm that the Trivy action version in use supports this new parameter.

---

200-201: Unified Configuration for Filesystem Scan
For the CI dependencies scan, the explicit severity parameter has been replaced with trivy-config: trivy.yaml, ensuring the scan uses the centralized configuration.

---

273-274: Standardized Trivy Settings for Staging Backend Scan
The staging backend image scan now uses trivy-config: trivy.yaml instead of hardcoded severity values, ensuring consistency with the overall scan configuration.

---

280-281: Standardized Trivy Settings for Staging Frontend Scan
Similarly, the staging frontend image scan now references trivy-config: trivy.yaml, aligning its configuration with other scan jobs.

---

437-438: Centralized Configuration for Production Backend Scan
For the production backend image scan, using trivy-config: trivy.yaml replaces the explicit severity parameters. This promotes a unified scanning configuration across environments.

---

444-445: Centralized Configuration for Production Frontend Scan
The production frontend image scan now also utilizes trivy-config: trivy.yaml, ensuring all production scans are consistently configured.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[arkid15r]

Fixed in cb4a110