Microsoft Defender for Cloud
Cloud and workloads

Technical onboarding guide for 42Crunch (preview)

In brief

The article now describes integrating 42Crunch audit and scan findings with Defender for Cloud, adds Azure DevOps configuration steps, and clarifies the DevOps connection requirement for viewing results. It also labels the integration as preview.

What Defender admins need to know

Administrators onboarding 42Crunch have clearer setup guidance for GitHub and Azure DevOps environments.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

42Crunch technical onboarding guide

Overview

42Crunch enables a standardized approach to securing APIs that automates the enforcement of API security compliance across distributed development and security teams. The 42Crunch API security platform empowers developers to build security from the integrated development environment (IDE) into the CI/CD pipeline. This seamless DevSecOps approach to API security reduces governance costs and accelerates the delivery of secure APIs.

Security testing approach

Because the quality of the API specification largely determines the scan coverage and effectiveness, it's important to ensure that your OpenAPI specification is well-defined. 42Crunch Audit performs a static analysis of the OpenAPI specification file aimed at helping the developer to improve the security and quality of the specification. The Audit determines a composite security score from 0-100 for each specification file. As developers remediate security and semantic issues identified by the Audit, the score improves. 42Crunch recommends an Audit score of at least 70 before running a Conformance scan.

EnablementEnable 42Crunch in Microsoft Defender for Cloud

Connect your DevOps environments to Microsoft Defender for Cloud

This featureViewing 42Crunch scan results in Defender for Cloud requires connecting your DevOps environment to Defender for Cloud.

See how to onboard your GitHub organizations.

The action is powered by 42Crunch API Security Audit. Security Audit performs a static analysis of the API definition that includes more than 300 checks on best practices and potential vulnerabilities on how the API defines authentication, authorization, transport, and request/response schemas.

ForConfigure 42Crunch Audit for GitHub environments

Install the 42Crunch API Security Audit plugin within your CI/CD pipeline by completing the following steps:

  1. Choose Setup a workflow yourself.
  2. Rename the workflow from main.yaml to 42crunch-audit.yml.
  3. Go to the 42Crunch REST API Static Security Testing full workflow example.
  4. Copy the full sample workflow and paste it in the workflow editor.

Navigate to Defender for Cloud

To view the 42Crunch Audit findings in Defender for Cloud, complete the following steps:

  1. Select Recommendations.
  2. Select All recommendations.
  3. Filter by searching for API security testing.

:::image type="content" source="media/onboarding-guide-42crunch/api-recommendations.png" alt-text="Screenshot showing API summary." lightbox="media/onboarding-guide-42crunch/api-recommendations.png":::

Configure 42Crunch Audit for Azure DevOps environments

To configure 42Crunch Audit in Azure DevOps, complete the following steps:

  1. Install the 42Crunch Azure DevOps extension on your organization.
  2. Create a new pipeline in your Azure DevOps project. For a tutorial for creating your first pipeline, see Create your first pipeline.

API Scan continually scans the API to ensure conformance to the OpenAPI contract and detect vulnerabilities at testing time. It detects OWASP API Security Top 10 issues early in the API lifecycle and validates that your APIs can handle unexpected requests.

The scan requires a nonproduction live API endpoint, and the required credentials (API key/access token). See the 42Crunch API security tutorial to configure the 42Crunch Scan.

Refer to the azure-pipelines-scan.yaml file in the tutorial42Crunch API Security tutorial for the ADO Azure DevOps-specific tasks.

FAQ

How is 42Crunch licensed?

42Crunch is licensed based on a combination of the number of APIs and the number of developers that are provisioned on the platform. For example pricing bundles, see the 42Crunch Developer-First API Security Platform marketplace listing. Custom pricing is available through private offers on the Azure commercial marketplace. For a custom quote, reach out to mailto:[email protected].

What's the difference between the free and paid version of 42Crunch?

Is 42Crunch available on the Azure commercial marketplace?

Yes, 42Crunch is available for purchase on the 42Crunch Developer-First API Security Platform offer on Microsoft commercial marketplace.

Purchases of 42Crunch made through the Azure commercial marketplace count towards your Minimum Azure Consumption Commitments (MACC).

Next stepsteps

[!div class="nextstepaction"] Review Microsoft Defender for APIs overview