Skip to content

Security: Harden Dependabot Rules and Set Up Snyk Container Scanner #428

Description

@EDOHWARES

Description

Audit and secure backend Docker images and dependencies through automated scanning workflows.

Current Problem

The repository has Snyk workflows but they lack permission controls and Dependabot is not configured for weekly updates.

Proposed Solution

Create a standard Dependabot configuration and set up Snyk security actions to audit node packages and docker containers.

Technical Tasks

  • Add a `.github/dependabot.yml` configuration file
  • Refactor `.github/workflows/snyk.yml` to include proper security permissions and fail rules
  • Add a Snyk container scan step analyzing the backend Dockerfile
  • Configure slack/email notifications for discovered vulnerability alerts

Acceptance Criteria

  • Dependabot checks for workspace dependencies weekly, opening update PRs
  • Snyk container scan runs on every main branch update and pull request
  • Builds fail if vulnerabilities exceeding the configured threshold (e.g. Critical/High) are detected

Testing Requirements

  • Inject an outdated dependency and verify that build logs report security failures

Metadata

  • Priority: Medium
  • Difficulty: Medium

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave programgithub_actionsPull requests that update GitHub Actions codesecurity

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions