Stay organized with collections
Save and categorize content based on your preferences.
A security profile group is a container for custom security profiles.
A mirroring rule references a security profile group to enable the processing
of network traffic within Network Security Integration.
This document provides a detailed overview of security profile groups and
their capabilities.
Specifications
A security profile group is an organizational level resource.
You can add only one security profile
of type CUSTOM_MIRRORING to a security profile group.
Each security profile group is uniquely identified by a URL with
the following elements:
Organization ID: ID of the organization.
Location: scope of the security profile group. Location is always
set to global.
Name: security profile group name in the following format:
A string 1-63 characters long
Includes only lowercase alphanumeric characters or hyphens (-)
Must start with a letter
To construct a unique URL identifier for a security profile group, use the
following format:
Depending on the mirroring rule's flag direction, the rule affects both
incoming and outgoing traffic within the Virtual Private Cloud (VPC) network.
The mirrored traffic is then sent to the mirroring endpoint group defined
in the security profile referenced by the configured security profile group.
Subsequently, the mirroring endpoint group redirects the mirrored traffic
to the producer deployment group attached by third-party deployments.
Each security profile group must have an associated project ID. The associated
project is used for quotas and access restrictions on security
profile group resources. If you authenticate your service account by using the
gcloud auth activate-service-account command,
you can associate your service account with the security profile group.
To learn more about how to create a security profile group,
see Create and manage security profile groups.
Identity and Access Management roles
Identity and Access Management (IAM) roles govern the following security profile group
actions:
Creating a security profile group in an organization
Modifying or deleting a security profile group
Viewing details of a security profile group
Viewing a list of security profile groups in an organization
Using a security profile group in a packet mirroring policy rule
The following table describes the roles that are necessary for each step.
Ability
Necessary role
Create a security profile group
Security Profile Admin role (networksecurity.securityProfileAdmin)
on the organization where the security profile group is created.
Modify a security profile group
Security Profile Admin role (networksecurity.securityProfileAdmin)
on the organization where the security profile group is created.
View details about the security profile group in an organization
If you don't have the
Security Profile Admin role (roles/networksecurity.securityProfileAdmin),
you can create and manage security profile groups with the following permissions:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Security profile groups overview\n\nA security profile group is a container for custom security profiles.\nA mirroring rule references a security profile group to enable the processing\nof network traffic within Network Security Integration.\n\nThis document provides a detailed overview of security profile groups and\ntheir capabilities.\n\nSpecifications\n--------------\n\n- A security profile group is an organizational level resource.\n\n- You can add only one [security profile](/network-security-integration/docs/security-profiles-overview)\n of type `CUSTOM_MIRRORING` to a security profile group.\n\n- Each security profile group is uniquely identified by a URL with\n the following elements:\n\n - **Organization ID**: ID of the organization.\n - **Location** : scope of the security profile group. Location is always set to `global`.\n - **Name** : security profile group name in the following format:\n - A string 1-63 characters long\n - Includes only lowercase alphanumeric characters or hyphens (-)\n - Must start with a letter\n\n To construct a unique URL identifier for a security profile group, use the\n following format: \n\n organization/\u003cvar translate=\"no\"\u003eORGANIZATION_ID\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e/securityProfileGroups/\u003cvar translate=\"no\"\u003eSECURITY_PROFILE_GROUP_NAME\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eORGANIZATION_ID\u003c/var\u003e: ID of the organization.\n\n - \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: scope of the security profile group.\n Location is always set to `global`.\n\n - \u003cvar translate=\"no\"\u003eSECURITY_PROFILE_GROUP_NAME\u003c/var\u003e: the name of the security\n profile group.\n\n For example, a `global` security profile group `example-security-profile-group`\n in organization `2345678432` has the following unique identifier: \n\n organization/2345678432/locations/global/securityProfileGroups/example-security-profile-group\n\n- A mirroring rule must contain the name of the security profile group to be\n used by the mirroring endpoints.\n\n- Security profile groups apply to packet mirroring policies only when you add\n a mirroring rule with the action `MIRROR`. You can configure security profile\n groups in [hierarchical firewall policy rules](/firewall/docs/using-firewall-policies#create-rules)\n and [global network firewall policy rules](/firewall/docs/use-network-firewall-policies#create-rules).\n\n- Depending on the mirroring rule's flag direction, the rule affects both\n incoming and outgoing traffic within the Virtual Private Cloud (VPC) network.\n The mirrored traffic is then sent to the mirroring endpoint group defined\n in the security profile referenced by the configured security profile group.\n Subsequently, the mirroring endpoint group redirects the mirrored traffic\n to the producer deployment group attached by third-party deployments.\n\n- Each security profile group must have an associated project ID. The associated\n project is used for quotas and access restrictions on security\n profile group resources. If you authenticate your service account by using the\n [`gcloud auth activate-service-account` command](/sdk/gcloud/reference/auth/activate-service-account),\n you can associate your service account with the security profile group.\n To learn more about how to create a security profile group,\n see [Create and manage security profile groups](/network-security-integration/docs/configure-security-profile-groups).\n\nIdentity and Access Management roles\n------------------------------------\n\nIdentity and Access Management (IAM) roles govern the following security profile group\nactions:\n\n- Creating a security profile group in an organization\n- Modifying or deleting a security profile group\n- Viewing details of a security profile group\n- Viewing a list of security profile groups in an organization\n- Using a security profile group in a packet mirroring policy rule\n\nThe following table describes the roles that are necessary for each step.\n\nIf you don't have the\n[Security Profile Admin role](/iam/docs/understanding-roles#networksecurity.securityProfileAdmin) (`roles/networksecurity.securityProfileAdmin`),\nyou can create and manage security profile groups with the following permissions:\n\n- `networksecurity.securityProfileGroups.create`\n- `networksecurity.securityProfileGroups.delete`\n- `networksecurity.securityProfileGroups.get`\n- `networksecurity.securityProfileGroups.list`\n- `networksecurity.securityProfileGroups.update`\n- `networksecurity.securityProfileGroups.use`\n\nFor more information about IAM permissions and predefined roles,\nsee [IAM permissions reference](/iam/docs/permissions-reference).\n\nQuotas\n------\n\nTo view quotas associated with security profile groups, see\n[Quotas and limits](/network-security-integration/docs/quotas).\n\nWhat's next\n-----------\n\n- [Create and manage security profile groups](/network-security-integration/docs/configure-security-profile-groups)\n- [Create and manage custom security profiles](/network-security-integration/docs/out-of-band/configure-custom-security-profiles)"]]