filter by Fix/Ignore

filter by AI Component Tags

If they select "No Grouping" instead of "Group by Rule" they will see false positive or true positive recommendations directly in their findings.

Learn more

For most SAST products, framework coverage starts and ends with rule support. Semgrep Code now has framework-specific analysis capabilities built into the engine, meaning it can reason about Python source code in the context of specific frameworks. This ensures that implicit flows are captured and analyzed effectively.

As a result, benchmarks show an 84% true positive rate for our updated Python support. For benchmark details, or to learn more about our new framework coverage in Python, read the announcement blog!

foo($_, $_)

can match code like

foo(1, 2)

Happy rule writing!

Users can now self-serve these SCMs by navigating to Settings > SCM and clicking the corresponding button. Users can also test the connection to ensure it has been set up correctly.

What features are supported?

• PR Comments (Semgrep Code)

  • We’ve introduced Semgrep Code PR comments for both Azure DevOps Cloud and Bitbucket Data Center

  • This includes both inline comments and unanchored comments for individual and grouped findings, respectively.

• PR Comments (Semgrep Supply Chain - license violations)

  • These are now available for both Azure DevOps and Bitbucket Data Center, ensuring developers will always use compliant dependencies.

• Hyperlinks in the findings UI

  • Finding hyperlinks for both Azure DevOps and Bitbucket Data Center work across all parts of the findings UI (commit URL, branch URL, line of code URL, etc.).

  • The findings experience for both ADOC and BBDC are now at parity with other supported SCMs.

Note that no changes have been made to C/C++ support in Semgrep OSS - the languages will stay experimental due to constraints with OSS engine capabilities.

If you have any questions regarding coverage or performance in comparison to other SAST solutions that scan C/C++, please reach out to your account team!

Learn more

This improved analysis and coverage comes with no performance/speed cost, which is why we're making it the default scan type! You may notice new findings after your next scan due to the increased scope of analysis.

Since all scans now run with cross-function analysis, the "Pro Engine" toggle in settings is now a toggle for cross-file analysis (which is still optional due to the potential impact on scan speeds):

To learn more, read the announcement post where we go through an example of how easy it is to write a custom secrets rule and add it to a Semgrep policy.

Note that Semgrep Secrets supports validation out-of-the-box and comes with validator rules for many common services - this update allows users to write their own custom validator rules for internal services, services with custom subdomains, etc.

Learn more

Note that scans that were never completed currently appear before the latest scans - in a future update these projects will at the bottom of the list.

Admins will of course have access to all teams.

Happy scanning!

A few things to note:

• Historical scanning can be slow with large repos.

• Findings from historical scans will not be automatically be marked as fixed. Currently these findings can only exist in two states: Open or Ignored.

Please don't hesitate to share any feedback with your account team!

These rules can be found in the registry, and a subset of them (medium/high confidence rules) are available via the p/elixir ruleset for easy access.
To use them, users must be logged in and use the Pro engine via the --pro option!

Many thanks to Holden Oullette (maintainer of Sobelow) for helping us ship this update!

Check out the docs or read the announcement blog post.

All three of our products are powered by the same core analysis engine, and as we continue to unify and consolidate things on the front-end it should be much easier for anyone familiar with other parts of the Semgrep AppSec Platform to quickly get their bearings with our best-in-breed supply chain tool.

The new interface brings many of the core SAST capabilities and workflows that our users love to Semgrep Supply Chain:

• Group vulnerabilities by rule

• Bulk triage of findings

• More comprehensive filtering

• One unified API for findings across Semgrep Code and Semgrep Supply Chain

• /fp <comment> For triaging a finding to ignored with the triage reason "false positive"

• /ar <comment> For triaging a finding to ignored with the reason "acceptable risk"

• /other <comment> For triaging a finding to ignored without any specific reason "No triage reason"

  • Note: These are the same as the previous /semgrep ignore functionality

• /open To re-open a finding

  • Note: This is the same as the previous /semgrep open functionality

• /remember <comment> For adding Assistant memories.

  • Note: This is the same as the previous /semgrep remember functionality

Please note that all previous commands are still supported for backwards compatibility. For example: previous commands /semgrep ignore , /semgrep open , /semgrep remember will continue to be available, and developers may continue to use these commands.

Support is currently limited to Github, but is coming soon for Gitlab customers!

• Example/template rules are now categorized

• Each example has an explanation of what patterns are being matched with links to relevant documentation

• Example rules are more "real world" and better showcase the common use cases for rules

• Customers with secrets enabled will now will see an additional property for HTTP validation (learn more about custom secrets rules)

  

Happy rule-writing!

For organizations with thousands of developers and repositories, the importance of role based access controls goes beyond compliance - security engineers only want to see findings for the repositories and microservices they are responsible for, and access controls that work at the project level make this possible.

For more information, read our documentation on the new teams view in our access controls menu (found under settings).

Note: we only list tags if they are associated with at least 1 project. If a tag is not showing up as an option, it’s most likely because it’s not yet linked to any particular project.

PS: there are more filtering capabilities on the horizon, so stay tuned!

The rules are in p/default and you should start to see new results in your next scan. If you'd like to see results on a local scan first, run $ semgrep login && semgrep ci --pro

Please don't hesitate to share any feedback you have on the results with your account team or one of our product managers!

Semgrep Assistant is free for all customers, and uses AI to greatly speed up existing workflows across prioritization, triage, and remediation. New features include Assistant generated custom rules and Priority Inbox - to learn more about these capabilities read the blog post.

Semgrep Assistant is super easy to set up - just go into settings and turn it on (your developers will appreciate the additional context):

• Semgrep Code Search is only currently available for repos hosted on Github.com

• Semgrep Code Search is only available for current Code customers or users with an active trial license.

Semgrep managed scanning lets you add Semgrep to your projects without the need to change existing CI/CD configurations, whether you have one, hundreds, or even tens of thousands of repositories.

Code scans are run on Semgrep AppSec Platform’s infrastructure instead of in your CI/CD infrastructure. So there is no need for you to spend CI minutes or coordinate with other teams to set up scanning.

Once enabled, Semgrep managed scanning automatically runs full scans weekly and on every PR. Semgrep findings presented as PR comments are still available, and determined according to your policy settings for monitor, comment, or blocking modes.

For more, check out the Semgrep managed scanning announcement blog post.

Structure Mode replaces the now deprecated "Simple Mode", as it offers more robust functionality paired with an intuitive interface that's just as easy (if not easier) to understand than Simple Mode.

To learn more about Structure Mode, read our blog post which outlines all of the shiny new capabilities in detail.

This means that Swift now meets the strict syntax and parse-rate requirements for GA status with our Pro Engine. This release includes 57 Pro rules covering a broad range of vulnerability classes - as usual, we'll continuously monitor and update them to ensure they meet our standards for accuracy and comprehensiveness.

Happy coding!

Our future roadmap for the ecosystem includes reachability and the addition of CocoaPods as a supported package manager.

Users will need a Package.resolved in their repository for us to successfully parse all their dependencies. Official documentation on how users can generate one can be found here.

Check out the docs or read the announcement blog post.

Learn more