Mapping of Organizations, Workspaces, Projects and Repositories to the Mend AppSec Platform

Overview

The organizations, workspaces, projects and/or repositories that are installed in the Developer Platform are mapped to the Mend AppSec Platform once they are scanned.

For all SCMs (GitHub, Azure, Bitbucket), a “many to one” mapping is supported in regards to organizations, i.e multiple SCM organizations can be linked to a single Mend organization.

Below is the structure of the mapping for the integrations supported in the Developer Platform.

Azure DevOps Repos

Hierarchy

Organization
- Project
  - Repository
  - Repository
  - Repository
- Project
  - Repository
  - Repository
  - Repository
- Project
  - Repository
  - Repository
  - Repository

Mapping to the Mend AppSec Platform

Structure

Mend Organization
- Mend Application = AZ_{azdo organization name}/{azdo project name}
  - Mend Project = AZ_{repository name}_{branch name}

Note: {branch name} is default branch or base branch.

Example

Mend Organization = peters sandbox
- Mend Application = AZ_test_org/test_project
  - Mend Project = AZ_repo_1_main
  - Mend Project = AZ_repo_1_base1
  - Mend Project = AZ_repo_2_main

Bitbucket Cloud

Hierarchy

Workspace
- Project
  - Repository
  - Repository
  - Repository
- Project
  - Repository
  - Repository
  - Repository
- Project
  - Repository
  - Repository
  - Repository

Mapping to the Mend AppSec Platform

Structure

Mend Organization
- Mend Application = BB_{workspace name}
  - Mend Project = BB_{repository name}_{branch name}

Note: {branch name} is default branch or base branch.

Example

Mend Organization = brians sandbox
- Mend Application = BB_brians_workspace
  - Mend Project = BB_repo1_main
  - Mend Project = BB_repo2_main
  - Mend Project = BB_repo2_base1