Getting started Stay organized with collections Save and categorize content based on your preferences.
This pageapplies toApigee andApigee hybrid.
View Apigee Edge documentation.![]()
This page explains how to get started using Advanced API Security for Subscription and Pay-as-you-go organizations.
Required roles and permissions
The following sections describe the required roles and permissions to perform tasks using Advanced API Security.
Required roles for security reports
The table below shows the required roles to perform tasks related tosecurity reports.
| Security Report Task | Required Role(s) |
|---|---|
| Enable or disable Advanced API Security | Apigee Organization Admin (roles/apigee.admin) |
| Create reports | Apigee Organization Admin (roles/apigee.admin)Apigee Security Admin ( roles/apigee.securityAdmin) |
| View reports | Apigee Security Viewer (roles/apigee.securityViewer)Apigee Security Admin ( roles/apigee.securityAdmin) |
Required roles for risk assessment
The table below shows the required roles to perform tasks related torisk assessment.
| Risk Assessment Task | Required Role(s) |
|---|---|
| Create, update, or delete a custom security profile | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Organization Admin ( roles/apigee.admin) |
| Attach or detach a security profile | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Organization Admin ( roles/apigee.admin) |
| View security scores | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Security Viewer ( roles/apigee.securityViewer)Apigee Organization Admin ( roles/apigee.admin) |
| List all security profiles or get a profile | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Security Viewer ( roles/apigee.securityViewer)Apigee Organization Admin ( roles/apigee.admin) |
| Create, update, or delete a security monitoring condition | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Organization Admin ( roles/apigee.admin) |
| List and view security monitoring conditions | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Security Viewer ( roles/apigee.securityViewer)Apigee Organization Admin ( roles/apigee.admin) |
| List and view security monitoring condition metrics | Monitoring Admin (roles/monitoring.admin)Monitoring Editor ( roles/monitoring.editor) |
| Create, update, or delete monitoring alerts | SeeRequired roles (for security alerts) |
| View monitoring alerts | See Incidents for metric-based alerting policies: Before you begin |
Required roles and permissions for abuse detection
The table below shows the required roles and permissions to perform tasks related toabuse detection.
| Abuse Detection Task | Required Role(s) and Permission(s) |
|---|---|
| View incidents in the Abuse detection UI | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Security Viewer ( roles/apigee.securityViewer)Apigee Organization Admin ( roles/apigee.admin) |
| View incidentgenerative AI Insights | cloudaicompanion.instances.generateText permission |
| Opt an organization in or out ofmachine learning models for abuse detection | apigee.securitySettings.update permissionApigee Security Admin ( roles/apigee.securityAdmin)Apigee Organization Admin ( roles/apigee.admin) |
Required roles for security actions
The table below shows the required roles to perform tasks related tosecurity actions.
| Security Action Task | Required Role(s) |
|---|---|
| Create, edit, or delete security action configurations | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Organization Admin ( roles/apigee.admin) |
| View or list security actions | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Security Viewer ( roles/apigee.securityViewer)Apigee Organization Admin ( roles/apigee.admin) |
| Check the state of enforcement | Apigee Security Admin (roles/apigee.securityAdmin)Apigee Security Viewer ( roles/apigee.securityViewer)Apigee Organization Admin ( roles/apigee.admin) |
Manage Advanced API Security for Subscription organizations
To use Advanced API Security as a Subscription customer, Advanced API Security must be part of your Subscription entitlements. SeeApigee entitlements. To add Advanced API Security to your entitlements, contactApigee Sales.
Note: Apigee trial organizations can include an Apigee Advanced API Security trial for the trial period. Contact ApigeeApigee Sales for information.Once Advanced API Security is part of your entitlements, enable it in your organization:
If you are unsure whether you are using a Subscription or Pay-as-you-go Apigee organization, contact your Apigee organization administrator.
Get your Apigee add-ons configuration
In order to enable Advanced API Security for your Subscription organization, you first need to get your current Apigee add-ons configuration, using the following API call. This will also tell you whether Advanced API Security is already enabled.
curl "https://apigee.googleapis.com/v1/organizations/ORG" \ -X GET \ -H "Content-type: application/json" \ -H "Authorization: Bearer $TOKEN"
where
- ORG is the name of your organization.
$TOKENis the environment variable for anOAuth access token.
This call returns basic informationabout your organization, including a section for your Apigee add-ons configurationthat begins with the line:
"addonsConfig": {Check to see whether this section contains the following entry:
"apiSecurityConfig": { "enabled": true }If so, Advanced API Security is already enabled in the organization. Otherwise,you need to enable it, as described next.
Enable Advanced API Security for Subscription organizations
To enable Advanced API Security in a Subscription organization with the default configuration, issue aPOST request like the one shown below.
- If you create a new environment after enabling Advanced API Security, you must run the command below again to enable Advanced API Security for the new environment. Note that it isnot necessary to disable Advanced API Security before running the command again.
- If you simply detach an environment in which Advanced API Security is enabled from an instance, and then later reattach it, you donot need to run the command below again.
curl "https://apigee.googleapis.com/v1/organizations/ORG:setAddons" \ -X POST \ -H "Authorization: Bearer $TOKEN" \ -H "Content-type: application/json" \ -d '{ "addonsConfig": { "apiSecurityConfig": { "enabled": true }<Other entries of your current add-ons configuration> } }'where
- ORG is the name of your organization.
$TOKENis the environment variable for anOAuth access token.<Other entries of your current add-ons configuration>consists of any other entries of your currentApigee add-ons configuration.
For example, if the current add-ons configurationis
"addonsConfig": { "integrationConfig": { "enabled":true }, "monetizationConfig": { "enabled":true }},the command to enable Advanced API Security would be
curl "https://apigee.googleapis.com/v1/organizations/ORG:setAddons" \ -X POST \ -H "Authorization: Bearer $TOKEN" \ -H "Content-type: application/json" \ -d '{ "addonsConfig": { "apiSecurityConfig": { "enabled": true }, "integrationConfig": { "enabled": true }, "monetizationConfig": { "enabled": true } } }'After you send the request, you will see a response like the following:
{ "name": "organizations/apigee-docs-d/operations/0718a945-76e0-4393-a456-f9929603b32c", "metadata": { "@type": "type.googleapis.com/google.cloud.apigee.v1.OperationMetadata", "operationType": "UPDATE", "targetResourceName": "organizations/apigee-docs-d", "state": "IN_PROGRESS" }}Disable Advanced API Security for Subscription organizations
If for some reason you need to disable Advanced API Security in your Subscription organization, you can do so by issuing aPOST request, passing the add-ons configuration in your request body, as shown below.
curl "https://apigee.googleapis.com/v1/organizations/$ORG:setAddons" \ -X POST \ -H "Authorization: Bearer $TOKEN" \ -H "Content-type: application/json" \ -d '{"addonsConfig": { "apiSecurityConfig": { "enabled": false } <Include current add-ons configuration> } }'The following provides an example of the response showing that the operation is in progress:
{ "name": "organizations/$ORG/operations/06274ffb-8940-41da-836d-781cba190437", "metadata": { "@type": "type.googleapis.com/google.cloud.apigee.v1.OperationMetadata", "operationType": "UPDATE", "targetResourceName": "organizations/$ORG", "state": "IN_PROGRESS" }}For more information, see theConfigure organization add-ons API.
Manage Advanced API Security for Pay-as-you-go organizations
If you are aPay-as-you-go customer, you can enable Advanced API Security as a paid add-on. For more informationon enabling the Advanced API Security add-on for your Intermediate or Comprehensive Apigee environments, seeManage the Advanced API Security add-on.
If you are unsure whether you are using a Subscription or Pay-as-you-go Apigee organization, contact your Apigee organization administrator.
Manage Advanced API Security for eval organizations
The Advanced API Security add-on is automatically included with Apigeetrial (evaluation) organizations, but you'll need to enable it.
To enable it, follow the instructions inEnable Advanced API Security for Subscription organizations.
If you need to disable it, follow the instructions inDisable Advanced API Security for Subscription organizations.
Configure Advanced API Security using Terraform
Apigee supports using to manage some Advanced API Security functionality.
For example, you can use Terraform to configure:
- Security actions
- Risk Assessment v2 security profiles
- Risk Assessment v2 security monitoring conditions
For information on the currently supported functionality, see theApigee section of the Terraform Registry. Advanced API Security-related resource names start withgoogle_apigee_security. For information on general Apigee support for Terraform, seeUse Terraform with Apigee.
Next steps
Once you have enabled Advanced API Security, see:
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-17 UTC.