Secure your code, from the start.

Build secure coding skills at every stage of the SSDLC

9th October 2020

Add developer-centric training to industry-standard SARIF files, directly in GitHub code scanning workflows with our new GitHub Action.

On September 30th, GitHub officially announced the general availability of GitHub code scanning. GitHub code scanning is a developer-first, GitHub-native approach to easily finding security vulnerabilities before they reach production.

Code scanning integrates with GitHub Actions — or an existing CI/CD environment — to maximize flexibility for development teams. It scans code as it’s created, surfacing actionable security reviews within pull requests, and automating security as a part of a GitHub workflow.

A seamless approach to security for developers.

Built on the open SARIF (Static Analysis Results Interchange Format) standard, code scanning is designed to flex with the ever-growing needs of organization, so they can include things like open-source and commercial static application security testing (SAST) solutions within the same GitHub-native experience.

Third-party code scanning tools can be initiated with a GitHub Action or a GitHub App based on an event in GitHub itself, like a pull request. The results are formatted as SARIF and uploaded to the GitHub Security Alerts tab. Alerts are then aggregated per tool, and GitHub can track and suppress duplicate alerts. This allows developers to use their tool of choice for any of their projects on GitHub, all within the native GitHub experience. Quite simply, it cuts through the disruption of some traditional approaches to security, and it respects the developer workflow.

Yesterday, Secure Code Warrior was featured by GitHub as the only developer-centric training provider in their blog post, Third-Party Code Scanning Tools: Static Analysis & Developer Security Training, alongside Synk, Checkmarx, Fortify On Demand, Synopsis and Veracode.

While many SCA/SAST solutions provide lots of details for each of the vulnerabilities discovered, and references to published advisories and associated CWEs, not every developer is a security expert, nor should that be expected of them. Practical, usable advice and tools are the key to actionable awareness.

Contextual micro-learning.

The more context developers have for vulnerabilities, the more they’re able to understand the risks, prioritize fixing the most pressing issues and ultimately prevent them in the first place. That’s where Secure Code Warrior® comes in. Our mission is to empower developers to write secure code from the very beginning through fun, engaging, and framework-specific training, helping them think and code with a security mindset to achieve rapid improvements in security compliance, consistency, quality and development speed.

GitHub code scanning integration

Secure Code Warrior has built a GitHub Action that brings contextual learning to GitHub code scanning. This means developers can use a third-party action like the Snyk Container Action to find vulnerabilities, and then augment the output with CWE-specific, hyper-relevant learning.

The Secure Code Warrior GitHub Action processes an industry-standard SARIF file and appends contextual learning based upon CWE references in a SARIF rule object. This empowers development and security teams to not only find vulnerabilities, but enrich supported SAST tool reports with actionable knowledge that helps them prevent vulnerabilities from reoccurring.

Ready to try it out for yourself?

Get the action for free directly from the GitHub Marketplace here.
Learn more about the Secure Code Warrior GitHub Action here.

Matias is the co-founder and CTO of Secure Code Warrior. He has over a decade of hands-on software security experience, holding a Ph.D. in computer engineering from Ghent University.

View Comments