Getting started

• 1: Log in to Endor Labs
• 2: Quick start
• 2.1: Quick start with GitHub App
• 2.2: Quick start with endorctl
• 3: Endor Labs License Types
• 4: Endor Labs user interface

1 - Log in to Endor Labs

1. Visit https://app.endorlabs.com to access the login page.

2. You can sign in to Endor Labs with the following options:

   • Google Workspace
   • GitHub
   • GitLab
   • Email Link
   • Supported enterprise SSO providers

3. Select Getting Started on the left sidebar to explore the available options.

   • Select Start Tour to take a guided tour of the application and understand its main features.
   • Select Explore Demo Sandbox to view Endor Labs capabilities and explore its features in a read-only tenant.
   • Select SCAN WITH GITHUB APP to install the Endor Labs GitHub App.
   • Select SCAN VIA GITHUB ACTIONS to scan a demo repository from GitHub and view findings.
   • Select SCAN VIA CLI to set up your tenant and start scanning your repositories with the CLI.

   

4. See the quick start to set up with your first project scan.

2 - Quick start

Log in to Endor Labs and select Getting Started from the left sidebar to view the options to get started.

You can choose from the following options:

• endorctl
• GitHub App

You can also use GitHub Actions to scan demo projects.

2.1 - Quick start with GitHub App

This guide provides instructions on how to get started with Endor Labs using the Endor Labs GitHub App. You can install the GitHub App or the GitHub App (Pro).

Prerequisites for GitHub App

Before installing and scanning projects with Endor Labs GitHub App, make sure you have:

• A GitHub cloud account and organization. If you don’t have one, create one at GitHub.
• Administrative permissions to your GitHub organization. Installing the Endor Labs GitHub App in your organization requires approval or permissions from your GitHub organizational administrator.
• Endor Labs GitHub App requires read permissions to Dependabot alerts, actions, administration, checks, code, commit statuses, issues, metadata, packages, pull requests, repository hooks, and security events. It does not need write access to any resources.

Quickstart with GitHub App

1. Sign in to Endor Labs and select Getting Started from the left sidebar.

2. Select SCAN WITH GITHUB APP and click Install GitHub App.

   To enable automatic PR remediation, select Enable Automated Pull Requests to install the GitHub App (Pro).

   Warning

   You can only install either the GitHub App or the GitHub App (Pro) in your environment.

   

3. Choose the user and the organization where you wish to install the app.

4. Select whether to install and authorize Endor Labs on all your repositories or select the specific repositories that you wish to scan.

5. Click Install & Authorize.

   If the button to install says Install and Request instead of Install and Authorize, you don’t have permission to install the GitHub App. Select Install and Request to notify your organizational administrator of your request.

   

6. Select the Endor Labs namespace that you want to use and click Next.

   

7. Select the scan types to enable under SCANNERS.

   

   The following scanners are available:

   • SCA: Perform software composition analysis.
   • RSPM: Scan the repository for misconfigurations.
   • Secret: Scan the repository for exposed secrets.
   • CI/CD: Scan the repository and identify all the CI/CD tools used in the repository.
   • SAST: Scan your source code for weakness and generate SAST findings.
   • AI Models: Scan your repository and discover AI models in your source code.

8. Select Include Archived Repositories to scan your archived repositories. By default, the GitHub archived repositories aren’t scanned.

9. Select the PULL REQUEST SCANS to automatically scan the PRs submitted by users.

   

   • Select Pull Request Comments to enable GitHub Actions to comment on PRs for policy violations.

   • In Define Scanning Preferences, select either:

     • Quick Scan to gain rapid visibility into your software composition. It performs dependency resolution but does not conduct reachability analysis to prioritize vulnerabilities. The quick scan enables users to swiftly identify potential vulnerabilities in dependencies, ensuring a smoother and more secure merge into the main branch.

     • Full Scan to perform dependency resolution, reachability analysis, and generate call graphs for supported languages and ecosystems. This scan enables users to get complete visibility and identifies all issues dependencies, call graph generation before merging into the main branch. Full scans may take longer to complete, potentially delaying PR merges.

     See GitHub scan options for more information on the scans that you can do with the GitHub App.

10. Click Create.

You will be redirected back to Endor Labs.

After installation, Endor Labs scans your repositories and generates findings. Subsequently, Endor Labs scans your repository every 24 hours. See Findings for more information on the findings generated by the scans.

Review the scan results

1. Sign in to the Endor Labs user interface and click Projects on the left sidebar.
2. Select your project to view the findings page. See Findings for more information.

2.2 - Quick start with endorctl

This guide provides step-by-step instructions to set up and configure an Endor Labs tenant while getting started with your first project scan in your local system.

Use the following steps to scan your first project with Endor Labs:

1. Install Endor Labs on your local system
2. Authenticate to Endor Labs
3. Clone your repository
4. Scan your first project
5. Review your results

Install Endor Labs on your local system

Install or update the Endor Labs CLI (endorctl) for your operating system.

macOS

• Homebrew
• npm
• Apple Silicon Executable
• Intel Executable

brew tap endorlabs/tap
brew install endorctl

npm install -g endorctl

### Run the following command to get the npm global bin directory:
npm config get prefix

### Open your shell configuration file and insert the path you obtained with the above command:
export PATH="/path/to/npm/global/bin:$PATH"

### Reload your shell configuration and verify endorctl is installed:
endorctl --version

### Download the latest CLI for MacOS ARM64
curl https://api.endorlabs.com/download/latest/endorctl_macos_arm64 -o endorctl

### Verify the checksum of the binary
echo "$(curl -s https://api.endorlabs.com/sha/latest/endorctl_macos_arm64)  endorctl" | shasum -a 256 -c

### Modify the permissions of the binary to ensure it is executable
chmod +x ./endorctl

### Create an alias endorctl of the binary to ensure it is available in other directory
alias endorctl="$PWD/endorctl"

### Download the latest CLI for MacOS AMD64
curl https://api.endorlabs.com/download/latest/endorctl_macos_amd64 -o endorctl

### Verify the checksum of the binary
echo "$(curl -s https://api.endorlabs.com/sha/latest/endorctl_macos_amd64)  endorctl" | shasum -a 256 -c

### Modify the permissions of the binary to ensure it is executable
chmod +x ./endorctl

### Create an alias endorctl of the binary to ensure it is available in other directory
alias endorctl="$PWD/endorctl"

Linux

• npm
• AMD64 Executable
• ARM64 Executable

npm install -g endorctl

### Run the following command to get the npm global bin directory:
npm config get prefix

### Open your shell configuration file and insert the path you obtained with the above command:
export PATH="/path/to/npm/global/bin:$PATH"

### Reload your shell configuration and verify endorctl is installed:
endorctl --version

### Download the latest CLI for Linux amd64
curl https://api.endorlabs.com/download/latest/endorctl_linux_amd64 -o endorctl

### Verify the checksum of the binary
echo "$(curl -s https://api.endorlabs.com/sha/latest/endorctl_linux_amd64)  endorctl" | sha256sum -c

### Modify the permissions of the binary to ensure it is executable
chmod +x ./endorctl

### Create an alias endorctl of the binary to ensure it is available in other directory
alias endorctl="$PWD/endorctl"

### Download the latest CLI for Linux arm64
curl https://api.endorlabs.com/download/latest/endorctl_linux_arm64 -o endorctl

### Verify the checksum of the binary
echo "$(curl -s https://api.endorlabs.com/sha/latest/endorctl_linux_arm64)  endorctl" | sha256sum -c

### Modify the permissions of the binary to ensure it is executable
chmod +x ./endorctl

### Create an alias endorctl of the binary to ensure it is available in other directory
alias endorctl="$PWD/endorctl"

Windows

• npm
• Executable

npm install -g endorctl

### Run the following command to get the npm global bin directory:
npm config get prefix

### Add the path from the above command to the System property 'Path' in your Environment variable settings.

### Open a new Command prompt and verify endorctl is installed:
endorctl --version

### Download the latest CLI for Windows
curl -O https://api.endorlabs.com/download/latest/endorctl_windows_amd64.exe

### Check the expected checksum of the binary file
curl https://api.endorlabs.com/sha/latest/endorctl_windows_amd64.exe

### Verify the expected checksum and the actual checksum of the binary match
certutil -hashfile .\endorctl_windows_amd64.exe SHA256

### Rename the binary file
ren endorctl_windows_amd64.exe endorctl.exe

For more details, see Install and configure endorctl

Authenticate to Endor Labs

To authenticate your client with Endor Labs, utilize the built-in command endorctl init along with an external identity provider. Endor Labs supports multiple identity providers, including Google, GitHub, GitLab, Email link authentication, and Custom Identity Provider through Enterprise SSO. Examples of such enterprise SSO solutions include Google, GitHub, GitLab, or your organization’s specific choice.

For more information, see Install and configure endorctl.

• Google
• GitHub
• GitLab
• Email
• SSO

endorctl init --auth-mode=google

endorctl init --auth-mode=github

endorctl init --auth-mode=gitlab

endorctl init --auth-email=<insert_email_address>

endorctl init --auth-mode=sso --auth-tenant=<insert-your-tenant>

Clone your repository

Upon successful authentication to Endor Labs using endorctl, proceed to clone the repository you intend to scan. If you prefer initiating with a dummy app for scanning, feel free to skip to the next step.

To clone a Git repository, use the git clone command followed by the clone link of the repository. You can find the URL on the repository’s page on a platform like GitHub or GitLab. For example,

git clone https://github.com/username/repo-name.git

Finally, navigate to the repository you’ve cloned to complete the following steps:

cd <repo-name>

Run your first scan

Endor Labs supports three distinct scan types. See each section for instructions on how to run each scan type with Endor Labs.

• Scan for OSS risk
• Scan for leaked secrets
• Scan for GitHub misconfigurations

Scan for OSS risk

Follow these steps to scan with Endor Labs for open source risk:

1. Install software prerequisites
2. Clone your repository
3. Build your software
4. Scan with Endor Labs for OSS risk

Install software prerequisites

The following prerequisites must be met to scan with Endor Labs for OSS risk:

• A local installation of Git or the ability to clone repositories in CI. See the Git documentation for instructions on installing Git
• A runtime environment and build tools for supported software development languages your team uses must be installed on any system used for testing. For more information, see Supported languages and frameworks.

For more information on supported languages, package managers and build systems and the requirements for each language, see their respective page.

For more information, see endorctl commands and working with the API.

Build your software

To run a complete and accurate scan with Endor Labs, ensure that the software can be successfully built, incorporating well-formatted manifest files. To maximize the benefits of an Endor Labs OSS scan, you should perform a comprehensive testing as a post-build step, either locally or in a CI pipeline. Use the following commands to verify that the software can be built successfully with well-formatted manifest files before initiating the scan.

• Java (Maven)
• Java (Gradle)
• JavaScript (npm)
• JavaScript (yarn)
• JavaScript (pnpm)
• .NET (dotnet)
• PHP (composer)
• Golang
• Python (pip)
• Python (poetry)
• Ruby (bundler)
• Swift/Objective-C
• Scala (sbt)
• Rust (Cargo)

mvn dependency:tree
mvn clean install

gradle dependencies --configuration compileClasspath
./gradlew assemble
# Use `gradle assemble` if you do not have a gradle wrapper
# in your repository

npm install

yarn install

export ENDOR_PNPM_ENABLED=true
pnpm install

dotnet restore
dotnet build

composer install

go mod tidy

python3 -m venv venv
source venv/bin/activate
venv/bin/python3 -m pip install

poetry install

bundler install

pod install

sbt projects
sbt compile
sbt dependencyTree

cargo build

Scan your project for OSS risk

To scan and monitor all packages in a given repository from the root of the repository, run the following command:

endorctl scan

Scanning an example repository

To scan an example repository https://github.com/OWASP-Benchmark/BenchmarkJava.git, you must perform the following steps after successfully authenticating to Endor Labs:

1. Clone the repository https://github.com/OWASP-Benchmark/BenchmarkJava.git

   git clone https://github.com/OWASP-Benchmark/BenchmarkJava.git
   

2. Navigate to the repository on your local system

   cd BenchmarkJava
   

3. Build the repositories package with Maven:

   mvn clean install
   

4. Scan the repository

   endorctl scan
   

Scanning for leaked secrets

The following procedure should be used to scan with Endor Labs for potential secrets leaked into your source code.

To scan for all potentially leaked secrets in the checked out branch of your repository, run the following command:

endorctl scan --secrets

Often, secrets are leaked outside the context of your repositories main branch and can be found in older branches or those that are under active development. To identify these, Endor Labs inspects the Git logs of the repository.

To scan for all potentially leaked secrets in all branches of your repository, run the following command:

endorctl scan --secrets --git-logs

Scan for GitHub misconfigurations

Endor Labs allows teams to scan their repository for configuration best practices in alignment with organizational policy.

Pre-requisites

To scan the GitHub repository, you must have:

• The GitHub repository HTTPS clone URL
• A personal access token with access administrative access to the repository. For help creating a personal access token see GitHub documentation.

If you are on a self-hosted GitHub Enterprise Server, you should also have:

• The GitHub API URL (This is typically the FQDN of the GitHub server)
• A local copy of the CA Certificate if the certificate is self-signed or from a private CA

Running a misconfiguration scan

To scan a GitHub repository for misconfigurations:

1. Export your personal access token as an environment variable:

   export GITHUB_TOKEN=<personal_access_token>
   

2. Scan the repository to retrieve configuration information and analyze the configuration against organizational policy or configuration best practices:

   endorctl scan --repository-http-clone-url=https://github.com/<organization>/<repository>.git --github
   

For source control systems on the GitHub Enterprise Server, you must set the --github-api-url flag to your GitHub Enterprise server domain name:

endorctl scan --github-api-url=https://<fully_qualified_domain_name_to_GitHub_Enterprise_Server> --repository-http-clone-url=https://<fully_qualified_domain_name_to_GitHub_Enterprise_Server>/<organization>/<repository>.git --github

Review the results of your project

• Sign in to the Endor Labs user interface, click Projects on the left sidebar.

• The Findings section provides a summary of vulnerabilities found in each project, categorized by severity:

  • C: Critical
  • H: High
  • M: Medium
  • L: Low

• Under Packages, the number indicates the identified packages. Click on the icon next to the number to open a right sidebar containing the following details :

  • Project metadata: Information such as UUID, repository details, dependencies, and repository versions.
  • Findings: A breakdown of the detected vulnerabilities categorized by dependency, package, repository, secrets, and CI workflows.
  • Tools used during analysis: A list of tools involved in the scanning process.

• Select your project to view its details. See Findings for more information.

3 - Endor Labs License Types

Endor Labs application is available as the following offerings:

For more details on Endor Labs’ offerings and the features they include, see Pricing and packaging.

4 - Endor Labs user interface

The Endor Labs user interface is designed for efficient navigation, with the primary menu located in the left sidebar.

To access the Endor Labs user interface, sign into Endor Labs with your credentials.

The Endor Labs user interface page is structured into three main sections:

• Left sidebar: The left sidebar provides quick access to different modules and features of the platform.
• Main content panel: This section displays the primary information and data relevant to the selected module.
• Right sidebar: This section provides the detail drawers of the selected view in the main content area offering quick access to supplementary data.

Dashboard

The Dashboard gives a quick and clear view of your project’s security status.

See Dashboard Documentation for more information.

Projects

The Projects page helps you manage and track your software packages and dependencies.

You can:

• Search and filter projects across different namespaces.
• View findings associated with each project to assess security risks.
• Add new projects to your workspace by clicking the Add Project option.

See Manage Projects for more information.

Dependencies

The Dependencies page gives detailed insights into package dependencies.

You can:

• Search and filter dependencies based on specific criteria.
• Export filtered dependency data as a CSV file for further analysis.

See Dependencies for more information.

AI models

The AI Models page helps you find and evaluate AI models used in your projects, providing insights into their usage, status, and impact. These models are flagged during scans and are evaluated for risks and operational security.

See AI Model for more information.

Findings

The Findings page helps you to identify and analyze security risks across different areas.

See View Findings for more information.

SBOM hub

The SBOM Hub helps you manage and track Software Bill of Materials (SBOMs) in one place.

You can:

• Import SBOMs easily using the Import SBOM button.
• Use filters to narrow down searches and find specific SBOMs quickly.

See Manage SBOMs for more information.

DroidGPT

DroidGPT is an AI-powered assistant that helps developers find and evaluate open-source software components with minimal risk.

Users can:

• Search for relevant OSS components based on your project needs.
• Get AI-driven insights and recommendations on security, dependencies, and best practices.

See DroidGPT Documentation for more information.

OSS packages

The OSS Packages page allows users to find and track open-source dependencies, identifying security risks and licensing concerns.

See Open Source Packages for more information.

AI models

The AI Models page is a search tool to find and explore AI models available within the platform.

This page displays the top AI models from Hugging Face with information like model name, security score, activity score, operational score, and more.

See AI models for more information.

Tools

The Tools page lists all detected CI/CD tools in the environment. Users can filter these tools based on categories such as build systems, version control, and deployment tools, helping them identify and manage security risks effectively.

See CI/CD Tools for more information.

Artifacts

The Artifacts page displays signed artifacts along with detailed provenance data. This helps ensure that artifacts are securely generated, traced, and verified within the CI/CD pipeline, reducing the risk of tampering or unauthorized modifications.

See Sign artifacts for more information.

Access control

The Access Control page lets you manage who can access your workspace and how they authenticate.

It includes the following features:

• Auth Policy: Set rules for user authentication and access control, including password policies, multi-factor authentication (MFA) requirements, and session management settings, ensuring that only authorized users can access the system.
• API Keys: Users can create and manage API keys to enable secure system access for automated processes, integrations, and external applications.
• Custom Identity Provider: Connects third-party authentication providers to enable Single Sign-On (SSO) and centralized authentication for user.
• Invitations: Users can send and manage invitations for new users to join the workspace. It allows to invite users via email, track the status of invitations, and resend or revoke invitations.

See Manage access to Endor Labs for more information.

Integrations

The Integrations page allows you to connect Endor Labs with external tools and services to enhance functionality and streamline workflows. You can set up integrations with security scanners, CI/CD pipelines, ticketing systems, and more. These integrations help automate security checks, improve vulnerability tracking, and ensure seamless communication between Endor Labs and other development tools.

See Endor Labs Integration for more information.

Namespaces

The Namespaces page allows users to organize their projects logically and manage access controls within the organization.

• Create a namespace: Users can create namespaces to group projects according to organizational units, project requirements, or teams.
• Edit a namespace: Users can modify the description and tags of an existing namespace.
• Delete a namespace: Users can delete a namespace which will permanently remove all its child namespaces and projects within it.

See Namespaces for more information.

Notifications

The Notifications page keeps you updated on security events and policy violations.

It is organized into three categories:

• Open: Displays active notifications that require attention.
• Resolved: Displays notifications that have been addressed.
• All: Displays a complete history of all notifications.

Users can set up notification integrations for email, Jira, Slack, Vanta, webhooks, GitHub PR remediation, and GitHub PR comments.

Use filters to sort by time range and quickly find key details like timestamps, related policies, project names, evaluation times, violations, namespaces, and tags.

Policies and rules

The Policies & Rules page allows users to define security and compliance policies for their projects.

It includes:

• Finding Policies: These policies enable users to detect and categorize security issues within their projects. Administrators can create custom finding policies to address specific security needs and ensure the detection of vulnerabilities.
• Exception Policies: These policies allow users to define conditions under which certain findings can be marked as exceptions. This helps in filtering out known issues that have been accepted as risks.
• Action Policies: These policies enable the automation of responses to policy violations.
• Remediation Policies: These policies define guidelines for fixing identified security issues.
• Secret Rules: These rules are used to detect and manage exposed secrets within the codebase. They help in identifying sensitive information.
• CI/CD Rules: These are rules specifically designed to enforce security standards within CI/CD pipelines. They ensure that security checks are integral to the build process.
• SAST Rules: These rules enable users to perform automated analysis on their source code to detect potential security vulnerabilities.

See Policies for more information.

Settings

Settings enables users to configure platform preferences, security policies, and integrations.

It includes:

• System Settings: These settings allow users to manage essential configurations such as Endor Patches, Policies & Rules, and SBOM configurations.
• License: This section provides details about the licensing information for Endor Labs products. Users can view current license status, manage license renewals, and upgrade license plans
• Saved Filters: Users can create and manage reusable filters for findings and dependencies. They help users to apply custom views and criteria to their data.
• Scan Profiles: This feature allows users to define and customize scanning configurations. A scan profile can include specific parameters, toolchains, and paths to different projects.
• Build Tools: This allows users to set up integrations for dependency analysis ensuring that the software build process incorporates dependency checks.

See Administration for more information.

Getting started

The Getting started page is designed to help you quickly familiarize yourself with Endor Labs and make the most of its features. It provides a step-by-step guide to setting up your first project and understanding key functionalities.

See Getting started for more information.