Cloud Armor Security Policy

Docs > DDSQL Reference > Data Directory > Cloud Armor Security Policy

Cloud Armor Security Policy in Google Cloud is a set of rules that help protect applications and services from web-based threats and attacks. It provides defense against DDoS, mitigates common vulnerabilities, and allows you to control access based on attributes like IP address, geography, or request headers. This policy is applied at the edge of Google’s network to ensure security and performance before traffic reaches your backend services.

gcp.compute_security_policy

Fields

ID	Type	Data Type	Description
_key	core	string
adaptive_protection_config	core	json
advanced_options_config	core	json
ancestors	core	array<string>
creation_timestamp	core	timestamp	[Output Only] Creation timestamp in RFC3339 text format.
datadog_display_name	core	string
ddos_protection_config	core	json
description	core	string	An optional description of this resource. Provide this property when you create the resource.
id	core	string	[Output Only] The unique identifier for the resource. This identifier is defined by the server.
kind	core	string	[Output only] Type of the resource. Always compute#securityPolicyfor security policies
labels	core	array<string>	Labels for this resource. These can only be added or modified by the setLabels method. Each label key/value pair must comply with RFC1035. Label values may be empty.
name	core	string	Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression `[a-z]([-a-z0-9]*[a-z0-9])?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
organization_id	core	string
parent	core	string
project_id	core	string
project_number	core	string
recaptcha_options_config	core	json
region	core	string	[Output Only] URL of the region where the regional security policy resides. This field is not applicable to global security policies.
resource_name	core	string
rules	core	json	A list of rules that belong to this policy. There must always be a default rule which is a rule with priority 2147483647 and match all condition (for the match condition this means match "" for srcIpRanges and for the networkMatch condition every field must be either match "" or not set). If no rules are provided when creating a security policy, a default rule with action "allow" will be added.
self_link	core	string	[Output Only] Server-defined URL for the resource.
tags	core	hstore
type	core	string	The type indicates the intended use of the security policy. - CLOUD_ARMOR: Cloud Armor backend security policies can be configured to filter incoming HTTP requests targeting backend services. They filter requests before they hit the origin servers. - CLOUD_ARMOR_EDGE: Cloud Armor edge security policies can be configured to filter incoming HTTP requests targeting backend services (including Cloud CDN-enabled) as well as backend buckets (Cloud Storage). They filter requests before the request is served from Google's cache. - CLOUD_ARMOR_INTERNAL_SERVICE: Cloud Armor internal service policies can be configured to filter HTTP requests targeting services managed by Traffic Director in a service mesh. They filter requests before the request is served from the application. - CLOUD_ARMOR_NETWORK: Cloud Armor network policies can be configured to filter packets targeting network load balancing resources such as backend services, target pools, target instances, and instances with external IPs. They filter requests before the request is served from the application. This field can be set only at resource creation time.
user_defined_fields	core	json	Definitions of user-defined fields for CLOUD_ARMOR_NETWORK policies. A user-defined field consists of up to 4 bytes extracted from a fixed offset in the packet, relative to the IPv4, IPv6, TCP, or UDP header, with an optional mask to select certain bits. Rules may then specify matching values for these fields. Example: userDefinedFields: - name: "ipv4_fragment_offset" base: IPV4 offset: 6 size: 2 mask: "0x1fff"