Remediate vulnerabilities with IBM Concert Secure Coder in the browser

Edit online

IBM® Concert Secure Coder in the browser provides a guided conversational remediation experience that helps development and security teams investigate package dependency vulnerabilities, code exposure, generate remediation plans, and create pull requests directly from Concert.

Concert Secure Coder browser experience complements Concert Secure Coder in the IDE by providing a centralized remediation workflow for package dependency vulnerabilities that are identified through software composition analysis (SCA) scans, CI/CD pipelines, and other vulnerability discovery processes.

Secure Coder in the browser is supported on both virtual machine (VM) and Red Hat OpenShift Container Platform (OCP) deployments.

Secure Coder guides users through the remediation process by using a conversational interface. Users can follow recommended actions, review remediation plans, ask follow-up questions, and provide custom instructions throughout the remediation workflow.

What you can do

With IBM Concert Secure Coder in the browser, you can:
  • Review remediation actions that are generated from vulnerability findings.
  • Investigate package dependency vulnerabilities and their impact.
  • Investigate code exposure vulnerabilities and their impact.
  • Review remediation recommendations before changes are applied.
  • Analyze affected applications, repositories, packages, and dependencies.
  • Generate remediation plans for vulnerable packages.
  • Evaluate dependency upgrade recommendations and compatibility considerations.
  • Review proposed remediation changes before they are committed.
  • Generate pull requests that include remediation details and validation results.
  • Track remediation progress and collaborate with other teams through Concert workflows.

How Secure Coder supports remediation

Secure Coder uses vulnerability findings, repository context, and remediation intelligence to help users investigate and remediate package dependency vulnerabilities.

The remediation process typically includes the following stages:
  1. Clone the repository

    Secure Coder clones the repository that is associated with the selected remediation action and prepares a workspace for analysis and remediation activities.

  2. Review the remediation plan

    Secure Coder analyzes the repository and vulnerability information and generates a remediation plan that includes recommended fixes, potential impacts, and risk considerations.

  3. Execute remediation

    Secure Coder creates a remediation branch, applies the recommended dependency updates, and performs validation activities.

  4. Validate changes

    Users review the proposed changes and validation results to confirm that the vulnerabilities have been addressed.

  5. Create a pull request

    Secure Coder commits and pushes the remediation changes and creates a pull request that summarizes the implemented fixes and validation results.

When to use Secure Coder in the browser

Use Secure Coder in the browser when:
  • Vulnerabilities are identified through software composition analysis (SCA) scans, CI/CD pipelines, or other security scanning processes.
  • You want to review remediation recommendations before making code changes.
  • You need a centralized remediation experience that can be used across development and security teams.
  • You want to generate pull requests directly from IBM Concert.
  • You need to remediate vulnerabilities across multiple repositories.

Limitations

The following limitations apply in this release:
  • Secure Coder in the browser supports remediation of package dependency vulnerabilities only.
  • A new remediation session is started each time you access Secure Coder in the browser.
  • Secure Coder might intermittently fail to update dependency lock files such as package-lock.json. Review generated changes before merging the pull request and update lock files manually if required.

Next steps