Mayhem Blog

Our Mayhem GitHub Action makes it easier than ever to secure your applications using Mayhem in a GitHub CI/CD pipeline.

This post explains how Mayhem fits into the development lifecycle, continually analyzing the main branch of your repo and generating regression tests.

In this blog post, we’ll take a deeper look at the NIST guidance for software development. In particular, we’ll look at PW 8.2 in NIST 800-218.

Learn how to fuzz an API without a specification by recording transactions with the API as an HTTP Archive (.har file).

Mayhem for API supports the writing of your own plugins to guide Mayhem for API into making legitimate requests to your API.

Over the last several weeks, we’ve made a number of updates to both our flagship Mayhem for Code product and Mayhem for API. Let’s take a look at each.

When executing the target in the context of a dynamic analysis, Mayhem employs mechanisms that first identify the root cause of a potential issue and then try to resolve it by intelligently providing different configuration values.

In this post, we’ll look at bringing Mayhem into a Jenkins pipeline using both Mayhem’s command line interface (CLI) as well as using Mayhem’s Docker image.

When using Mayhem, there are a few best practices the ForAllSecure team recommends to account for branches.