Custom Policies created in code (in YAML) support more complex logic than those created with the Visual Editor. This includes the ability to define a policy based on a resource’s Connection-State and the use of more complex AND/OR logic.
See here for a walk-through of the Code Editor.
A Custom Policy in code consists of these components:
- Metadata (e.g., name, severity, etc.)
- Scope/Provider (e.g., AWS)
- Policy Definition (e.g., minimum password length configured = >x).
- A policy specifies the desired state of an aspect of the configuration of a specific type of cloud resource.
- A resource that is not in the defined state is non-compliant with the policy and will appear in the Incident queue after a Brigecrew scan.
The Custom Policy below is assigned to the category general with a severity level of critical and declares that an AWS resource is non-compliant if it does not have a tag whose value is env.
See the full specifications of each policy component below.
A Policy’s metadata component defines:
- Category - based on Bridgecrew category definitions
- Severity - displayed with Errors (Incidents) found by Bridgecrew scans and can be used for filtering
Policy description and fix details in case of a policy error
The area of cloud functionality the Policy relates to, for example, IAM or Storage
The Scope component of a custom policy associates the policy with a cloud provider.
Cloud Service Provider
A Policy Definition consists of:
- Defintion Block(s)- either Attribute Block(s) or Connection State Block(s) or both
- Logical Operator(s) (optional)
- Filter (optional)
- Attribute - The policy describes resources with a certain configuration as defined by a configuration attribute and its value (per Terraform), or by the presence/absence of an attribute.
- Connection State - The policy describes resources in a particular Connection State, in other words, connected, or not connected to another type of resource (for example, a security group).
Using AND/OR Logic
A policy definition may include multiple blocks (Attribute, Connection State or both), associated by AND/OR logic.
An Attribute Block in a policy's definition, indicates that a resource will be non-compliant if a certain configuration attribute does not have a specified value, or if it exists/doesn't exist.
Bridgecrew's Custom Policies support both Terraform and CloudFormation attribute libraries and syntaxes.
Policies written using Terraform attributes will apply for Terraform (.tf and plan files). These policies will also apply when evaluating runtime cloud resources on AWS, Azure and GCP.
Policies written using CloudFormation attributes will apply for the following IaC frameworks:
The Attribute Block in the Definition in the example below, is used to ensure that a proper backup policy is configured for Redshift clusters.
definition: cond_type: "attribute" resource_types: - "aws_redshift_cluster" attribute: "automated_snapshot_retention_period" operator: "not_equals" value: "0"
Value in YAML
Not Starts With
Not Ends With
Not RegEx Match
Greater Than or Equal
Less Than or Equal
Json Path Equals
Json Path Exists
collection of strings
Attribute of defined resource types
value (not relevant for operator:
string / number / boolean
See Examples of Multiple Attribute Blocks using AND/OR Logic
For examples of Policy Definitions with multiple Attribute Blocks using AND/OR logic, see:
A Connection State Block indicates a type of resource that has/doesn't have a connection to another type of resource.
In the example presented in the table below, in order to be compliant
aws_elb must have connections to either
The Connection State Block below indicates that to be compliant with the policy, resources of type
aws_lb or of type
aws_elb must be connected to either a resource of type
aws_security_group or a resource of type
definition: cond_type: "connection" resource_types: - "aws_elb" connected_resource_types: - "aws_security_group" - "aws_default_security_group" operator: "exists"
Collection of strings
Filters can be used to limit the types of resources relevant to a condition. Filters are most commonly used for Connection Blocks. (For Attribute Blocks you can easily limit the resource type with the resource_type parameter.)
For example, you may want to enforce a policy only for specific resource type(s) from specific groups defined in the conditions. Filters are available only for AND logic, at the top level.
The Custom Policy in this example ensures that all ELBs are attached to security groups as shown in the table below.
In line with best practices, connections of this nature should be defined using security_groups key.
defintion: and: - cond_type: "filter" resource_types: - "aws_elb" attribute: “resource_type” operator: "within” - cond_type: "connection" resource_types: - "aws_elb" connected_resource_types: - "aws_security_group" - "aws_default_security_group" operator: "exists"
The condition above uses AND logic. See additional examples of complex logic in policy definitions.
See Examples of Complex Definitions with Connection State Blocks and Filters
Bridgecrew Cloud allows combination of definition blocks using AND/OR operators.
- The top-level logical operator is the first key below "definition" (and not an item in a collection). It defines the relationship of all of the definition blocks in the specific YAML policy definition.
- Filter blocks apply (only) to the top-level and constitute an AND condition. For example, if you'd like to indicate a requirement for a Connection State between types of resources, but only within a certain subset of all of those resources.
- Every other logical operator applies within a collection. For example, you can use AND/OR logic in a collection of key-value pairs.
The logic in the policy definition shown below is
AND[block 1,block 2,OR[block 3,block 4]].
#.... defintion: and: - #filter block 1 - #block 2 - or: - #block 3 - #block 4
See All Examples
Updated 3 months ago