Peer review compliance

Peer code reviews are a key component of delivering secure and compliant software. The DevSecOps reference implementation helps to enforce the review of code changes before they are merged and promoted to production.

Managing Peer-review Check in CI/CD Toolchains

This documentation provides instructions for enabling and disabling the Peer-review check within Continuous Integration (CI) and optional within Continuous Delivery (CD) toolchains.

Continuous Integration (CI) Toolchain

By default, the peer-review check is enabled in the CI toolchain. To modify this setting:

To enable the peer-review check, set the value of the peer-review-compliance environment variable to 1.
To disable the peer-review check, set the value of the peer-review-compliance environment variable to 0.

Continuous Delivery (CD) Toolchain

The following environment variables allow you to manage the Peer-review check within your CD toolchain:

To retrieve a list of pull requests and their associated titles for your ongoing deployment, set the peer-review-collection environment variable to 1. Note that this variable is set to 1 by default. To deactivate this listing, set peer-review-collection to 0.
To enable the peer review validation for all pull requests associated with your current deployment, set the peer-review-compliance environment variable to 1. By default, this variable is set to 0. To bypass this validation, set peer-review-compliance to 0.

Important points

You must conduct peer reviews only on the protected (base) branch, which is where the inventory is updated. If you are running a CI pipeline on a feature branch, set the environment variable peer-review-compliance to 0 for that specific trigger to prevent the peer review check on the feature branch.

The adherence to peer-review compliance is contingent upon the completion of a successful Continuous Integration (CI) pipeline run and the subsequent entry to inventory. As a result, the initial run of the CI pipeline will skip the peer review compliance check.

To ensure compliance with peer review standards, it is assumed that inventory updates in the ci-finish stage occur on the master branch. However, if your inventory updates are performed on a different branch other than master, you can set the environment variable inventory-repo-branch to indicate the branch where the inventory updates are taking place.

It is expected that in Continuous Deployment (CD) pipeline, all inventory updates made to the inventory repository will be promoted to the target branch being deployed, ensuring no commits are missed. By default, during deployment, the inventory repository will be checked out to the target branch. However, if your inventory promotion target branch misses some commits between the base branch and the target branch, you can set the inventory-repo-branch environment variable to specify the base branch where all inventory commits are located.

By default, the Continuous Integration (CI) pipeline will automatically perform a commit to the inventory repository at the conclusion of the run, using the application name as the inventory entry. However, if you intend to modify the inventory entry during the release stage, it is recommended to incorporate an environment property named inventory-entry-name into your toolchain. This property should contain the modified inventory name for working for peer review process.

If you have an automation that pushes commits directly to your protected branch and you want to avoid issues with peer review compliance checks, ensure that your commit message includes ##AUTOMATED_COMMIT##.

The reference implementation discovers instances of code that are not peer reviewed, collects evidence, and creates incident issues to track these items.

Before you can merge code in the master (protected) branch, the code must be reviewed by a person who did not upload the modified code.

The code repository (repo) must have at least two members: one member who has admin privileges, and another member who has write privileges. If code is merged into a repo without a review, the action must be visible in the code repo audit trail. Periodically scan the audit trail to identify and analyze these exceptional situations.

The pipeline collects peer review compliance data during builds and deployments to create the audit trail from code pull/merge request merges to change requests.

In this diagram, PR1, PR2 are the pull/merge requests that are approved before merging. Similarly, for PR4, PR5, and PR7. However, PR3 and PR6, highlighted in red, are merged without an approval, which is a peer review compliance violation. This is captured as evidence.

By default, the sample application in the CI toolchain attempts to set the minimum number of reviewers to 1. If you want to change the number of reviewers, set the peer_review_approvers envronment property as required. For more information on setting the minimum number of reviewers required for a pull/merge request, see the following GitHub and GitLab resources:

Data collected in continuous integration build runs

This data collection contains a list of all of the commits for the pull/merge requests that were merged in app repos since the last build.

Pull request data is collected directly from the app repos. Data for each pull/merge request that is related to commits between the repo commit that triggered the previous build and the currently available commit is collected.

Commits that do not contain a pull/merge request create a compliance incident issue in the following releases of the pipeline. You cannot commit directly to the master branch.

A compliance incident typically holds the following information:

List of pull/merge request URLs for the associated commit ID.
Application repository.
Commit ID.
Required number of approvals.

Collected data is saved as an evidence artifact, which is uploaded to the evidence locker, and then referred to in the evidence itself. The final evidence result is determined by the approved pull/merge requests. Unapproved, but merged pull/merge requests fail this type of evidence.

Data that is collected in continuous deployment runs

This data collection contains a list of all of the pull/merge requests that were merged in app repos since the last deployment.

Pull request data is collected from the evidence locker and the incident issue repo.

The inventory gathers data from all builds on related artifacts since the last deployment.
The evidence locker collects stored peer review data from the builds.
The incident issue repo collects information about open pull/merge request incidents.

The app repos are not accessed during this data collection. Because continuous deployment pipelines are assumed to be located in isolated environments, you cannot cross those boundaries.

Change request content

The following data is included in the automatically generated change request:

List of pull/merge request incidents that are not remediated. This data includes the asset details and the incident URL.

Non-remediated pull/merge request incidents impact the deployment readiness of the change request. If any pull/merge request incidents are found, they are considered vulnerabilities and the change request must be reviewed and approved manually.

Pull request incident remediation

Pull request incidents are considered vulnerabilities because they indicate that unchecked code is contained in the released artifacts. To remediate these incidents, complete the following steps:

Retroactively review the merged change.
Create an issue about how to fix any existing problems with the code.
Add the exempt label or close the pull/merge request incident issue.

The author of the pull/merge request and the person who closes the pull/merge request incident issue cannot be the same person.

Troubleshooting

Case 1:

Problem

Failure in collect_peer_review_commits in prod-start stage of the CD pipeline results in other stages failing with errors. When the following error occurs in the prod_start stage

| ERROR | 2023-12-20T07:00:48.978Z | index.ts:25:14 | The inventory entry has no such property ('pipeline_run_id').

Solution

Users who possess inventory entries that are not supported by the one-pipeline must add an ignore file in the inventory. This action ensures that those files are not considered for any computations.

Known issues

Peer review compliance is reliant on the inclusion of inventory entry in the release step following each iteration of the Continuous Integration (CI) pipeline. Skipping to include the inventory entry for any failed CI pipeline run might result in the peer review evidence for that specific CI pipeline run being disregarded in your Continuous Delivery (CD) pipeline.