Policies

Policies are rules that allow you to customize the behavior of the Endor Labs scan.

You can use policies to:

• Enable, disable, or edit out-of-the-box features
• Create custom findings
• Set guardrails for the development process
• Create custom ticketing or messaging workflows

Endor Labs comes with various out-of-the-box policies that enable you to quickly get started with the product. Policy templates are available to help you easily create custom findings and configure workflows around known vulnerabilities, outdated, unmaintained, or unused software dependencies, license risks, code review guidelines, repository configurations, and more.

You can also write policies from scratch using Rego policy language and customize policies based on organizational rules and needs.

Policy types

There are two types of policies that you can set up with Endor Labs.

1. Finding policies - Enable or disable out-of-the-box features and create custom finding policies to identify and raise findings for issues in your development environment. For example, you can create a finding policy to raise findings for missing, unknown, problematic, or incompatible licenses.
2. Action policies - Create action policies to define the system behavior and set up workflows when a finding with a given set of properties is raised. For example, you can create an action policy to create a Jira task when packages with outdated dependencies are included in your projects.

Key benefits

Policies are essential to define risk tolerance, set automated rules for open source components, check your repository or organization configuration, and more.

• Identify and triage issues - Policies give you a quick and automated way to identify and triage issues in your environment. This saves valuable development time and ensures developers consider security issues at the early stages of application development.
• Improve decision-making - Automating enforcement simplifies decision-making in an organization and reduces complexity. Policies make assessing the OSS components simpler and allow developers to focus on violations critical to the organization.
• Establish governance - Use policies to set up an organization’s governance methods such as enforcing Multi-Factor Authentication, setting up code review guidelines, guidelines on the use of the open source components, preventing misconfiguration of source code repositories, and more.