Allero is a policy tool that prevents misconfigurations in CI/CD pipelines. This helps prevent failures and security risks from reaching production. It also allows R&D teams be less dependent on DevOps engineers when building and maintaining CI/CD pipelines. Allero comes with built-in rules, and developed to be as friendly as possible for you to create your own rules!
Here are a few use-cases that can be mitigated with Allero:

1. Prevent Log4shell vulnerability by making sure SCA runs in every pipeline.
2. Prevent the use of deprecated language versions. (e.g. Node version <= 12)
3. Ensure all IaC manifests are scanned for misconfigurations. (e.g. Run checkov on any terraform file)

Allero supports GitHub Actions and GitLab Pipelines.

Linux & MacOS: curl https://get.allero.io | /bin/bash
Brew: brew install allero-io/allero/allero
Windows: iwr -useb https://get.allero.io/windows_install.ps1 | iex

• Run allero validate {DIRECTORY_PATH}

• Fetch your organizations and/or repositories: allero fetch github dapr/dapr
• Validate your pipelines across all your fetched data: allero validate

Fetching data from a private GitHub organization requires a personal access token (PAT).

1. Create a GitHub PAT with access to the repos you want to scan. More information about how to create a Github PAT can be found here Generate the token with the following read permissions:

   • repo:
     • repo:status
     • repo_deployment
     • public_repo
     • repo:invite
     • security_events

2. Once the token is generated, run export ALLERO_GITHUB_TOKEN={YOUR_TOKEN}.

• When running Allero from GitHub Actions, the PAT should be stored as an encrypted secret.

3. Fetch your private repositories: allero fetch github {your_repo}

Fetching data from a private GitLab group requires an access token.

1. Create a GitLab Access Token with access to the repos you want to scan. More information about how to create a GitLab Token can be found here Generate the token with the following permissions:
   • read_api
2. Once the token is generated, run export ALLERO_GITLAB_TOKEN={YOUR_TOKEN}.
3. Fetch your private repositories: allero fetch gitlab {your_repo}

Allero can fail a PR if the repo's pipelines don't meet the policy. Use this GitHub Action to trigger allero validation on a PR event.

To achieve a continuous assessment, allero needs to periodically scan the entire organization.
Implementing with GitHub Actions: We created a GitHub Action that runs Allero everyday at 8am on your entire organization.

1. Fork Allero repo
2. Create a GitHub Personal Access Token and store it in your forked repo as an encrypted secret named ALLERO_GITHUB_TOKEN.
3. GitHub disables scheduled Actions on a forked repo by default. To enable the Allero Action, browse to your forked allero repo, navigate to GitHub Actions and enable the workflow.

Using any other scheduler: as a CLI tool, Allero can be easily run in - CI/CD, docker scheduler, crontab, kubernetes - anywhere!

Some rules apply to everyone, while others are very stack-specific. That is why some rules are enabled by default and others are disabled. Learn how to enable and disable rules here.

A policy is a set of rules, and it is represented by a token.
To generate a token, go to this page, choose the rules you want and generate the token. The token will be sent to your email.
To run the policy, you need to set the token by running allero config set token {your_token} and re-run allero validate.

Tokens can be temporarily ignored during a single validation by running allero validate --ignore-token

Tokens can be cleared from the CLI by running allero config clear token | ensure-sca-scanner | Make sure every repository has at least one pipeline with sca scanner | Keep production secured | ensure-terraform-scanner | Make sure every repository has at least one pipeline with terraform scanner | Keep production secured

Rules can be defined using the Json Schema format. Json Schema rules should be based on our data schema. An example of our data schema structure can be found here.

1. Create a new json file and define your rule. Example rules can be found here. Make sure to update the rule description and failureMessage.
2. Copy-paste the rule-files to ~/.allero/rules/github/ and ~/.allero/rules/gitlab/.
3. Run allero validate

We encourage you to contribute to Allero!

1. Fork our repo
2. Read how to add your own rule here
3. Add your rule to pkg/rulesConfig/github or to pkg/rulesConfig/gitlab directories
4. Create a PR!

Interested in contributing more to the CLI? We will provide a more detailed explanation on how to contribute soon. If you're intrested, you can contact us to get our help with your first PR!

Your privacy and code integrity are very important to us. That's why our CLI operates locally only, and doesn't save any sensitive information related to your code anywhere. We only track metrics that reflect your usage of the CLI :)

Open an issue or shoot us an email.