Repositories rarely rivet and rope themselves together quite like the union that has been forming between JFrog and GitHub. The company known for its bullfrog-themed universal repository manager for software application artifacts spanning dependencies, binaries and configuration files continues to forge a partnership with the widely popular web-based developer code collaboration platform.

The suggestion from users is that the two platforms coming together and forming an increasing number of integration points helps software supply chain security by displaying source-based security findings from GitHub alongside binary-based security findings from JFrog under GitHub’s Security tab.

Step 1 of 7

14%

Which of the following best describes how you currently monitor and manage systems across your hybrid cloud environment?(Required)

Multiple separate tools for different environments

Multiple separate tools for different monitoring and management functions

Single consolidated dashboard

Custom built monitoring and management solution

No full monitoring and management solution

Don’t know

How valuable would it be for your monitoring and management solution to incorporate predictive analytics to help you identify and address system issues that are critical and not waste time or effort working through all the data and “noise” that is not critical?(Required)

Extremely valuable

Moderately valuable

Somewhat valuable

Slightly valuable

Not valuable

How do you most typically address potential system issues BEFORE they impact your operations?(Required)

Automated workflows and playbooks to remediate potential issues as soon as they are detected

An orchestrated response process that leverages automation, AI, and human expertise to rapidly respond to potential issues

Advanced monitoring tools such as predictive analytics and anomaly detection to proactively identify and address potential issues

Respond to issues as they arise, using manual processes and troubleshooting techniques

A combination of automated remediation, orchestrated response, and/or proactive monitoring to address potential system issues

Don’t know

Other

What methods does your organization use to control and monitor cloud/IT spending?(Required)

Centralized procurement processes

Pre-approved budget thresholds

Automated cost monitoring tools

Department-level spending controls

Regular cost audits and reviews

Cloud cost optimization platform

Approval workflows for resource provisioning

Native financial operations tools provided by the cloud provider

No formal controls in place

Don’t know

Other

Please specify:

Which methods do you rely on most to detect security vulnerabilities in your systems?(Required)

Automated scanning tools

Manual assessments

Vendor notifications

Threat modeling (for early detection)

None of these

Don’t know

Other

Please specify:

What are the TWO most common ways you prioritize vulnerabilities to address within your environment?(Required)

Based on potential impact

Based on exploitability

Regulatory compliance requirements

Based on CVSS scores

Risk-based analysis of multiple factors

First-in-first-out approach

No formal prioritization process

Don’t know

How do you typically handle system updates and security patches?(Required)

Automated updates and patches

Manually review and apply updates and patches on a regular schedule

A combination of automation and manual review

Apply updates and patches on an as-needed basis.

Outsourced update and patch management

No defined process

Don’t know

Other

Δ

Vulnerability Remediation

Developments now see the organizations releasing two updates that deepen the connection between the platforms. JFrog’s platform now integrates with GitHub Advanced Security, enabling GitHub Copilot Autofix to remediate vulnerabilities detected by JFrog SAST automatically. 

GitHub Copilot Autofix analyzes vulnerabilities in software code and explains why they matter so that developers get a more rounded contextual understanding of what is happening. It then offers code suggestions that help software engineers fix vulnerabilities as they are found. JFrog SAST takes its name from Static Application Security Testing, a type of application security testing that scans applications in a “static state” (i.e. where no additional code or data input is occurring) to detect input validation errors, insecure dependencies, bad coding practices and other vulnerabilities that are intrinsic to the code itself.

In addition, JFrog Runtime Security findings have now been added to the JFrog Job Summary page in GitHub Actions.

¿Hablo Python, Java, JavaScript & Go?

JFrog’s Advanced Security offers static application security testing coverage, identifying a range of vulnerabilities across multiple languages such as Python, Java, JavaScript and Go. This analysis, combined with targeted remediation advice, helps developers address and rectify security flaws.

How does this affect development teams?

According to the JFrog blogging team, “A recent IDC report suggests that over two-thirds of developers agree that their security-related responsibilities require them to switch contexts frequently. This context-switching can significantly impact productivity and potentially lead to security oversights.”

Integration, Identification, Remediation

Now, JFrog’s SAST capabilities integrate with GitHub Copilot Autofix, to bring security fixes directly into the developer’s workflow. This allows developers to address issues across multiple languages as noted. JFrog identifies “problematic code” in pull requests, flagging security vulnerabilities to Copilot Autofix, which then uses this information to generate specific fix suggestions, showing developers what code changes are needed.

Copilot Autofix also provides developers with the ability to automatically generate new pull requests with suggested fixes for security issues found in the existing codebase. Software engineers can review these changes and merge them. Each suggestion includes an explanation of the issue and the reasoning behind the fix, improving developer security awareness and keeping them in control of the process.

By integrating the JFrog Platform’s advanced SAST capabilities directly into the GitHub workflow, the two organizations say that they’re making it easier for developers to write secure code because they no longer need to switch contexts between the development environment and security tools.

“Beyond DevOps and DevSecOps practices, the future will require advanced interactions with AI tools. Chatting with GitHub’s Copilot to select the right and secure software package based on the extensive metadata stored in the JFrog Catalog can be a game-changer. This integration will significantly enhance the efficiency of Copilot users across the software supply chain; binary-focused and code environments. This partnership offers the best of both worlds,” said John Nuttall, director of technology at AT&T.

Real-Time Runtime Reality

The goal for all developer teams is of course to identify and remediate vulnerabilities and accurately track all runtime components. Because runtime security is crucial for protecting applications in production environments, where the most challenging and potentially damaging threats often emerge, JFrog says its Runtime Security tool is a real-time Kubernetes monitoring solution that protects applications during execution and addresses core security challenges.

JFrog Runtime’s integration brings real-time production monitoring data directly into a GitHub workflow. After a build is completed in GitHub Actions, a link to the JFrog Runtime Live assessment dashboard is automatically added to the JFrog Job Summary page. This creates a new “Runtime Monitoring” section, filtered for the specific component built into that action. Developers and security teams can move from their GitHub workflow to a detailed view confirming the integrity and lineage of their build and deployment in one mouse click.

By combining JFrog’s security insights with GitHub’s development platform, the two organizations aim to help solidify and verify application integrity in production, so that software engineering teams can maintain a continuous security posture from code commit to the point of live production deployment.