[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CCVNTDFN4MA6YRGX8DB5X":3,"skill-same:01M73CCVNTDFN4MA6YRGX8DB5X":93},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M73CCVNTDFN4MA6YRGX8DB5X","implementing-api-threat-protection-with-apigee",null,"Implement API threat protection using Google Apigee policies including JSON\u002FXML threat protection, OAuth 2.0, SpikeArrest, and Advanced API Security for OWASP Top 10 defense.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-api-threat-protection-with-apigee\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-api-threat-protection-with-apigee\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-api-threat-protection-with-apigee\ndescription: Implement API threat protection using Google Apigee policies including\n  JSON\u002FXML threat protection, OAuth 2.0, SpikeArrest, and Advanced API Security for\n  OWASP Top 10 defense.\ndomain: cybersecurity\nsubdomain: api-security\ntags:\n- apigee\n- api-gateway\n- threat-protection\n- json-threat-protection\n- xml-threat-protection\n- spike-arrest\n- oauth2\n- google-cloud\n- owasp-api-top-10\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1552.001\n- T1078.004\n- T1530\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\nnote: \"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.\"\n---\n\n# Implementing API Threat Protection with Apigee\n\n## Overview\n\nGoogle Apigee is an enterprise API management platform that provides native security policies for threat protection, including JSON and XML content validation, OAuth 2.0 enforcement, SpikeArrest rate limiting, regular expression threat protection, and Advanced API Security for detecting malicious clients and API abuse patterns. Apigee operates as a reverse proxy that intercepts all API traffic, applying security policies before requests reach backend services, effectively shielding APIs against the OWASP API Security Top 10 threats.\n\n\n## When to Use\n\n- When deploying or configuring implementing api threat protection with apigee capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Google Cloud Platform account with Apigee organization provisioned\n- Apigee X or Apigee hybrid environment configured\n- Backend API services deployed and accessible from Apigee\n- Google Cloud CLI (gcloud) installed and authenticated\n- OpenAPI specification for target APIs\n- Understanding of Apigee proxy bundle structure\n\n## Core Security Policies\n\n### 1. JSON Threat Protection\n\nProtects against JSON-based denial-of-service attacks by limiting structural depth, entry counts, and string lengths:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CJSONThreatProtection name=\"JSON-Threat-Protection-1\">\n    \u003CDisplayName>JSON Threat Protection\u003C\u002FDisplayName>\n    \u003CSource>request\u003C\u002FSource>\n    \u003C!-- Maximum nesting depth of JSON structure -->\n    \u003CObjectEntryNameLength>50\u003C\u002FObjectEntryNameLength>\n    \u003CObjectEntryCount>25\u003C\u002FObjectEntryCount>\n    \u003CArrayElementCount>100\u003C\u002FArrayElementCount>\n    \u003CContainerDepth>5\u003C\u002FContainerDepth>\n    \u003CStringValueLength>500\u003C\u002FStringValueLength>\n\u003C\u002FJSONThreatProtection>\n```\n\n### 2. XML Threat Protection\n\nShields against XML bombs, XXE attacks, and oversized XML payloads:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CXMLThreatProtection name=\"XML-Threat-Protection-1\">\n    \u003CDisplayName>XML Threat Protection\u003C\u002FDisplayName>\n    \u003CSource>request\u003C\u002FSource>\n    \u003CNameLimits>\n        \u003CElement>50\u003C\u002FElement>\n        \u003CAttribute>50\u003C\u002FAttribute>\n        \u003CNamespacePrefix>20\u003C\u002FNamespacePrefix>\n        \u003CProcessingInstructionTarget>50\u003C\u002FProcessingInstructionTarget>\n    \u003C\u002FNameLimits>\n    \u003CValueLimits>\n        \u003CText>1000\u003C\u002FText>\n        \u003CAttribute>500\u003C\u002FAttribute>\n        \u003CNamespaceURI>256\u003C\u002FNamespaceURI>\n        \u003CComment>256\u003C\u002FComment>\n        \u003CProcessingInstructionData>256\u003C\u002FProcessingInstructionData>\n    \u003C\u002FValueLimits>\n    \u003CStructureLimits>\n        \u003CNodeDepth>5\u003C\u002FNodeDepth>\n        \u003CAttributeCountPerElement>5\u003C\u002FAttributeCountPerElement>\n        \u003CNamespaceCountPerElement>3\u003C\u002FNamespaceCountPerElement>\n        \u003CChildCount>25\u003C\u002FChildCount>\n    \u003C\u002FStructureLimits>\n\u003C\u002FXMLThreatProtection>\n```\n\n### 3. Regular Expression Threat Protection\n\nDetects SQL injection, XSS, and other injection patterns in request parameters:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CRegularExpressionProtection name=\"RegEx-Threat-Protection-1\">\n    \u003CDisplayName>Regex Injection Protection\u003C\u002FDisplayName>\n    \u003CSource>request\u003C\u002FSource>\n    \u003CIgnoreUnresolvedVariables>false\u003C\u002FIgnoreUnresolvedVariables>\n\n    \u003C!-- SQL Injection patterns -->\n    \u003CQueryParam name=\"*\">\n        \u003CPattern>[\\s]*((delete)|(exec)|(drop\\s*table)|(insert)|(shutdown)|(update)|(\\bor\\b))\u003C\u002FPattern>\n    \u003C\u002FQueryParam>\n\n    \u003C!-- XSS patterns -->\n    \u003CQueryParam name=\"*\">\n        \u003CPattern>[\\s]*&lt;\\s*script\\b[^&gt;]*&gt;[^&lt;]+&lt;\\s*\u002F\\s*script\\s*&gt;\u003C\u002FPattern>\n    \u003C\u002FQueryParam>\n\n    \u003C!-- Header injection -->\n    \u003CHeader name=\"*\">\n        \u003CPattern>[\\r\\n]\u003C\u002FPattern>\n    \u003C\u002FHeader>\n\n    \u003C!-- URI path traversal -->\n    \u003CURIPath>\n        \u003CPattern>(\u002F\\.\\.)|(\\.\\.\u002F)\u003C\u002FPattern>\n    \u003C\u002FURIPath>\n\n    \u003C!-- JSON body injection -->\n    \u003CJSONPayload>\n        \u003CJSONPath>$.*\u003C\u002FJSONPath>\n        \u003CPattern>[\\s]*((delete)|(exec)|(drop\\s*table)|(insert)|(shutdown)|(update))\u003C\u002FPattern>\n    \u003C\u002FJSONPayload>\n\u003C\u002FRegularExpressionProtection>\n```\n\n### 4. SpikeArrest Policy\n\nPrevents traffic spikes from overwhelming backend services:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CSpikeArrest name=\"Spike-Arrest-1\">\n    \u003CDisplayName>API Spike Arrest\u003C\u002FDisplayName>\n    \u003CRate>30ps\u003C\u002FRate> \u003C!-- 30 per second smoothed -->\n    \u003CIdentifier ref=\"request.header.x-api-key\"\u002F>\n    \u003CMessageWeight ref=\"request.header.x-request-weight\"\u002F>\n    \u003CUseEffectiveCount>true\u003C\u002FUseEffectiveCount>\n\u003C\u002FSpikeArrest>\n```\n\n### 5. OAuth 2.0 Token Validation\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003COAuthV2 name=\"Verify-OAuth-Token\">\n    \u003CDisplayName>Verify OAuth 2.0 Access Token\u003C\u002FDisplayName>\n    \u003COperation>VerifyAccessToken\u003C\u002FOperation>\n    \u003CExternalAuthorization>false\u003C\u002FExternalAuthorization>\n    \u003CExternalAccessToken>request.header.Authorization\u003C\u002FExternalAccessToken>\n    \u003CSupportedGrantTypes>\n        \u003CGrantType>authorization_code\u003C\u002FGrantType>\n        \u003CGrantType>client_credentials\u003C\u002FGrantType>\n    \u003C\u002FSupportedGrantTypes>\n    \u003CScope>read write\u003C\u002FScope>\n    \u003CGenerateResponse enabled=\"true\"\u002F>\n\u003C\u002FOAuthV2>\n```\n\n### 6. API Key Validation\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CVerifyAPIKey name=\"Verify-API-Key-1\">\n    \u003CDisplayName>Verify API Key\u003C\u002FDisplayName>\n    \u003CAPIKey ref=\"request.header.x-api-key\"\u002F>\n\u003C\u002FVerifyAPIKey>\n```\n\n## Proxy Bundle Configuration\n\n### Complete Secure Proxy Flow\n\n```xml\n\u003C!-- apiproxy\u002Fproxies\u002Fdefault.xml -->\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CProxyEndpoint name=\"default\">\n    \u003CPreFlow name=\"PreFlow\">\n        \u003CRequest>\n            \u003C!-- Step 1: Verify API Key or OAuth token -->\n            \u003CStep>\n                \u003CName>Verify-OAuth-Token\u003C\u002FName>\n            \u003C\u002FStep>\n            \u003C!-- Step 2: Rate limiting -->\n            \u003CStep>\n                \u003CName>Spike-Arrest-1\u003C\u002FName>\n            \u003C\u002FStep>\n            \u003C!-- Step 3: Threat protection -->\n            \u003CStep>\n                \u003CName>JSON-Threat-Protection-1\u003C\u002FName>\n                \u003CCondition>request.header.Content-Type = \"application\u002Fjson\"\u003C\u002FCondition>\n            \u003C\u002FStep>\n            \u003CStep>\n                \u003CName>XML-Threat-Protection-1\u003C\u002FName>\n                \u003CCondition>request.header.Content-Type = \"text\u002Fxml\"\u003C\u002FCondition>\n            \u003C\u002FStep>\n            \u003C!-- Step 4: Injection prevention -->\n            \u003CStep>\n                \u003CName>RegEx-Threat-Protection-1\u003C\u002FName>\n            \u003C\u002FStep>\n            \u003C!-- Step 5: CORS enforcement -->\n            \u003CStep>\n                \u003CName>CORS-Policy\u003C\u002FName>\n            \u003C\u002FStep>\n        \u003C\u002FRequest>\n        \u003CResponse>\n            \u003C!-- Remove internal headers from response -->\n            \u003CStep>\n                \u003CName>Remove-Internal-Headers\u003C\u002FName>\n            \u003C\u002FStep>\n            \u003C!-- Add security headers -->\n            \u003CStep>\n                \u003CName>Add-Security-Headers\u003C\u002FName>\n            \u003C\u002FStep>\n        \u003C\u002FResponse>\n    \u003C\u002FPreFlow>\n\n    \u003CFlows>\n        \u003CFlow name=\"sensitive-operations\">\n            \u003CDescription>Additional protection for sensitive endpoints\u003C\u002FDescription>\n            \u003CRequest>\n                \u003CStep>\n                    \u003CName>Quota-Strict\u003C\u002FName>\n                \u003C\u002FStep>\n            \u003C\u002FRequest>\n            \u003CCondition>(proxy.pathsuffix MatchesPath \"\u002Fadmin\u002F**\") or\n                       (proxy.pathsuffix MatchesPath \"\u002Fusers\u002F*\u002Fsensitive\")\u003C\u002FCondition>\n        \u003C\u002FFlow>\n    \u003C\u002FFlows>\n\n    \u003CHTTPProxyConnection>\n        \u003CBasePath>\u002Fv1\u003C\u002FBasePath>\n        \u003CVirtualHost>secure\u003C\u002FVirtualHost>\n    \u003C\u002FHTTPProxyConnection>\n\n    \u003CRouteRule name=\"default\">\n        \u003CTargetEndpoint>default\u003C\u002FTargetEndpoint>\n    \u003C\u002FRouteRule>\n\u003C\u002FProxyEndpoint>\n```\n\n### Security Headers Policy\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CAssignMessage name=\"Add-Security-Headers\">\n    \u003CDisplayName>Add Security Response Headers\u003C\u002FDisplayName>\n    \u003CSet>\n        \u003CHeaders>\n            \u003CHeader name=\"X-Content-Type-Options\">nosniff\u003C\u002FHeader>\n            \u003CHeader name=\"X-Frame-Options\">DENY\u003C\u002FHeader>\n            \u003CHeader name=\"Strict-Transport-Security\">max-age=31536000; includeSubDomains\u003C\u002FHeader>\n            \u003CHeader name=\"Cache-Control\">no-store, no-cache, must-revalidate\u003C\u002FHeader>\n            \u003CHeader name=\"Content-Security-Policy\">default-src 'none'\u003C\u002FHeader>\n            \u003CHeader name=\"X-Request-ID\">{messageid}\u003C\u002FHeader>\n        \u003C\u002FHeaders>\n    \u003C\u002FSet>\n    \u003CRemove>\n        \u003CHeaders>\n            \u003CHeader name=\"X-Powered-By\"\u002F>\n            \u003CHeader name=\"Server\"\u002F>\n        \u003C\u002FHeaders>\n    \u003C\u002FRemove>\n    \u003CIgnoreUnresolvedVariables>false\u003C\u002FIgnoreUnresolvedVariables>\n    \u003CAssignTo createNew=\"false\" transport=\"http\" type=\"response\"\u002F>\n\u003C\u002FAssignMessage>\n```\n\n## Advanced API Security\n\nEnable Apigee's Advanced API Security add-on for machine-learning-based threat detection:\n\n```bash\n# Enable Advanced API Security on Apigee X instance\ngcloud apigee organizations update $ORG_NAME \\\n  --advanced-api-security-config=enabled\n\n# View detected abuse alerts\ngcloud apigee apis security-reports list \\\n  --organization=$ORG_NAME \\\n  --environment=$ENV_NAME\n\n# Create security action to block suspicious traffic\ngcloud apigee security-actions create \\\n  --organization=$ORG_NAME \\\n  --environment=$ENV_NAME \\\n  --action-type=DENY \\\n  --condition-type=IP_ADDRESS \\\n  --condition-values=\"192.168.1.100,10.0.0.50\" \\\n  --description=\"Block identified malicious IPs\"\n```\n\n## Deployment\n\n```bash\n# Deploy proxy bundle with security policies\ngcloud apigee apis deploy \\\n  --api=$API_NAME \\\n  --environment=$ENV_NAME \\\n  --revision=$REVISION \\\n  --organization=$ORG_NAME\n\n# Validate deployment\ngcloud apigee apis list-deployments \\\n  --api=$API_NAME \\\n  --organization=$ORG_NAME\n```\n\n## References\n\n- Apigee JSON Threat Protection: https:\u002F\u002Fcloud.google.com\u002Fapigee\u002Fdocs\u002Fapi-platform\u002Freference\u002Fpolicies\u002Fjson-threat-protection-policy\n- Google Cloud Apigee Security Best Practices: https:\u002F\u002Fcloud.google.com\u002Farchitecture\u002Fbest-practices-securing-applications-and-apis-using-apigee\n- Apigee Advanced API Security: https:\u002F\u002Fdocs.cloud.google.com\u002Fapigee\u002Fdocs\u002Fapi-security\n- Apigee OWASP API Top 10: https:\u002F\u002Fdocs.apigee.com\u002Fapi-platform\u002Ffaq\u002Fowasp-top-api-threats\n- Wallarm Apigee Security Policies Guide: https:\u002F\u002Flab.wallarm.com\u002Fwhat\u002Fapigee-api-security-policies-howto\u002F\n","# Implementing API Threat Protection with Apigee\n\n## Overview\n\nGoogle Apigee is an enterprise API management platform that provides native security policies for threat protection, including JSON and XML content validation, OAuth 2.0 enforcement, SpikeArrest rate limiting, regular expression threat protection, and Advanced API Security for detecting malicious clients and API abuse patterns. Apigee operates as a reverse proxy that intercepts all API traffic, applying security policies before requests reach backend services, effectively shielding APIs against the OWASP API Security Top 10 threats.\n\n\n## When to Use\n\n- When deploying or configuring implementing api threat protection with apigee capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Google Cloud Platform account with Apigee organization provisioned\n- Apigee X or Apigee hybrid environment configured\n- Backend API services deployed and accessible from Apigee\n- Google Cloud CLI (gcloud) installed and authenticated\n- OpenAPI specification for target APIs\n- Understanding of Apigee proxy bundle structure\n\n## Core Security Policies\n\n### 1. JSON Threat Protection\n\nProtects against JSON-based denial-of-service attacks by limiting structural depth, entry counts, and string lengths:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CJSONThreatProtection name=\"JSON-Threat-Protection-1\">\n    \u003CDisplayName>JSON Threat Protection\u003C\u002FDisplayName>\n    \u003CSource>request\u003C\u002FSource>\n    \u003C!-- Maximum nesting depth of JSON structure -->\n    \u003CObjectEntryNameLength>50\u003C\u002FObjectEntryNameLength>\n    \u003CObjectEntryCount>25\u003C\u002FObjectEntryCount>\n    \u003CArrayElementCount>100\u003C\u002FArrayElementCount>\n    \u003CContainerDepth>5\u003C\u002FContainerDepth>\n    \u003CStringValueLength>500\u003C\u002FStringValueLength>\n\u003C\u002FJSONThreatProtection>\n```\n\n### 2. XML Threat Protection\n\nShields against XML bombs, XXE attacks, and oversized XML payloads:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CXMLThreatProtection name=\"XML-Threat-Protection-1\">\n    \u003CDisplayName>XML Threat Protection\u003C\u002FDisplayName>\n    \u003CSource>request\u003C\u002FSource>\n    \u003CNameLimits>\n        \u003CElement>50\u003C\u002FElement>\n        \u003CAttribute>50\u003C\u002FAttribute>\n        \u003CNamespacePrefix>20\u003C\u002FNamespacePrefix>\n        \u003CProcessingInstructionTarget>50\u003C\u002FProcessingInstructionTarget>\n    \u003C\u002FNameLimits>\n    \u003CValueLimits>\n        \u003CText>1000\u003C\u002FText>\n        \u003CAttribute>500\u003C\u002FAttribute>\n        \u003CNamespaceURI>256\u003C\u002FNamespaceURI>\n        \u003CComment>256\u003C\u002FComment>\n        \u003CProcessingInstructionData>256\u003C\u002FProcessingInstructionData>\n    \u003C\u002FValueLimits>\n    \u003CStructureLimits>\n        \u003CNodeDepth>5\u003C\u002FNodeDepth>\n        \u003CAttributeCountPerElement>5\u003C\u002FAttributeCountPerElement>\n        \u003CNamespaceCountPerElement>3\u003C\u002FNamespaceCountPerElement>\n        \u003CChildCount>25\u003C\u002FChildCount>\n    \u003C\u002FStructureLimits>\n\u003C\u002FXMLThreatProtection>\n```\n\n### 3. Regular Expression Threat Protection\n\nDetects SQL injection, XSS, and other injection patterns in request parameters:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CRegularExpressionProtection name=\"RegEx-Threat-Protection-1\">\n    \u003CDisplayName>Regex Injection Protection\u003C\u002FDisplayName>\n    \u003CSource>request\u003C\u002FSource>\n    \u003CIgnoreUnresolvedVariables>false\u003C\u002FIgnoreUnresolvedVariables>\n\n    \u003C!-- SQL Injection patterns -->\n    \u003CQueryParam name=\"*\">\n        \u003CPattern>[\\s]*((delete)|(exec)|(drop\\s*table)|(insert)|(shutdown)|(update)|(\\bor\\b))\u003C\u002FPattern>\n    \u003C\u002FQueryParam>\n\n    \u003C!-- XSS patterns -->\n    \u003CQueryParam name=\"*\">\n        \u003CPattern>[\\s]*&lt;\\s*script\\b[^&gt;]*&gt;[^&lt;]+&lt;\\s*\u002F\\s*script\\s*&gt;\u003C\u002FPattern>\n    \u003C\u002FQueryParam>\n\n    \u003C!-- Header injection -->\n    \u003CHeader name=\"*\">\n        \u003CPattern>[\\r\\n]\u003C\u002FPattern>\n    \u003C\u002FHeader>\n\n    \u003C!-- URI path traversal -->\n    \u003CURIPath>\n        \u003CPattern>(\u002F\\.\\.)|(\\.\\.\u002F)\u003C\u002FPattern>\n    \u003C\u002FURIPath>\n\n    \u003C!-- JSON body injection -->\n    \u003CJSONPayload>\n        \u003CJSONPath>$.*\u003C\u002FJSONPath>\n        \u003CPattern>[\\s]*((delete)|(exec)|(drop\\s*table)|(insert)|(shutdown)|(update))\u003C\u002FPattern>\n    \u003C\u002FJSONPayload>\n\u003C\u002FRegularExpressionProtection>\n```\n\n### 4. SpikeArrest Policy\n\nPrevents traffic spikes from overwhelming backend services:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CSpikeArrest name=\"Spike-Arrest-1\">\n    \u003CDisplayName>API Spike Arrest\u003C\u002FDisplayName>\n    \u003CRate>30ps\u003C\u002FRate> \u003C!-- 30 per second smoothed -->\n    \u003CIdentifier ref=\"request.header.x-api-key\"\u002F>\n    \u003CMessageWeight ref=\"request.header.x-request-weight\"\u002F>\n    \u003CUseEffectiveCount>true\u003C\u002FUseEffectiveCount>\n\u003C\u002FSpikeArrest>\n```\n\n### 5. OAuth 2.0 Token Validation\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003COAuthV2 name=\"Verify-OAuth-Token\">\n    \u003CDisplayName>Verify OAuth 2.0 Access Token\u003C\u002FDisplayName>\n    \u003COperation>VerifyAccessToken\u003C\u002FOperation>\n    \u003CExternalAuthorization>false\u003C\u002FExternalAuthorization>\n    \u003CExternalAccessToken>request.header.Authorization\u003C\u002FExternalAccessToken>\n    \u003CSupportedGrantTypes>\n        \u003CGrantType>authorization_code\u003C\u002FGrantType>\n        \u003CGrantType>client_credentials\u003C\u002FGrantType>\n    \u003C\u002FSupportedGrantTypes>\n    \u003CScope>read write\u003C\u002FScope>\n    \u003CGenerateResponse enabled=\"true\"\u002F>\n\u003C\u002FOAuthV2>\n```\n\n### 6. API Key Validation\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CVerifyAPIKey name=\"Verify-API-Key-1\">\n    \u003CDisplayName>Verify API Key\u003C\u002FDisplayName>\n    \u003CAPIKey ref=\"request.header.x-api-key\"\u002F>\n\u003C\u002FVerifyAPIKey>\n```\n\n## Proxy Bundle Configuration\n\n### Complete Secure Proxy Flow\n\n```xml\n\u003C!-- apiproxy\u002Fproxies\u002Fdefault.xml -->\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CProxyEndpoint name=\"default\">\n    \u003CPreFlow name=\"PreFlow\">\n        \u003CRequest>\n            \u003C!-- Step 1: Verify API Key or OAuth token -->\n            \u003CStep>\n                \u003CName>Verify-OAuth-Token\u003C\u002FName>\n            \u003C\u002FStep>\n            \u003C!-- Step 2: Rate limiting -->\n            \u003CStep>\n                \u003CName>Spike-Arrest-1\u003C\u002FName>\n            \u003C\u002FStep>\n            \u003C!-- Step 3: Threat protection -->\n            \u003CStep>\n                \u003CName>JSON-Threat-Protection-1\u003C\u002FName>\n                \u003CCondition>request.header.Content-Type = \"application\u002Fjson\"\u003C\u002FCondition>\n            \u003C\u002FStep>\n            \u003CStep>\n                \u003CName>XML-Threat-Protection-1\u003C\u002FName>\n                \u003CCondition>request.header.Content-Type = \"text\u002Fxml\"\u003C\u002FCondition>\n            \u003C\u002FStep>\n            \u003C!-- Step 4: Injection prevention -->\n            \u003CStep>\n                \u003CName>RegEx-Threat-Protection-1\u003C\u002FName>\n            \u003C\u002FStep>\n            \u003C!-- Step 5: CORS enforcement -->\n            \u003CStep>\n                \u003CName>CORS-Policy\u003C\u002FName>\n            \u003C\u002FStep>\n        \u003C\u002FRequest>\n        \u003CResponse>\n            \u003C!-- Remove internal headers from response -->\n            \u003CStep>\n                \u003CName>Remove-Internal-Headers\u003C\u002FName>\n            \u003C\u002FStep>\n            \u003C!-- Add security headers -->\n            \u003CStep>\n                \u003CName>Add-Security-Headers\u003C\u002FName>\n            \u003C\u002FStep>\n        \u003C\u002FResponse>\n    \u003C\u002FPreFlow>\n\n    \u003CFlows>\n        \u003CFlow name=\"sensitive-operations\">\n            \u003CDescription>Additional protection for sensitive endpoints\u003C\u002FDescription>\n            \u003CRequest>\n                \u003CStep>\n                    \u003CName>Quota-Strict\u003C\u002FName>\n                \u003C\u002FStep>\n            \u003C\u002FRequest>\n            \u003CCondition>(proxy.pathsuffix MatchesPath \"\u002Fadmin\u002F**\") or\n                       (proxy.pathsuffix MatchesPath \"\u002Fusers\u002F*\u002Fsensitive\")\u003C\u002FCondition>\n        \u003C\u002FFlow>\n    \u003C\u002FFlows>\n\n    \u003CHTTPProxyConnection>\n        \u003CBasePath>\u002Fv1\u003C\u002FBasePath>\n        \u003CVirtualHost>secure\u003C\u002FVirtualHost>\n    \u003C\u002FHTTPProxyConnection>\n\n    \u003CRouteRule name=\"default\">\n        \u003CTargetEndpoint>default\u003C\u002FTargetEndpoint>\n    \u003C\u002FRouteRule>\n\u003C\u002FProxyEndpoint>\n```\n\n### Security Headers Policy\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n\u003CAssignMessage name=\"Add-Security-Headers\">\n    \u003CDisplayName>Add Security Response Headers\u003C\u002FDisplayName>\n    \u003CSet>\n        \u003CHeaders>\n            \u003CHeader name=\"X-Content-Type-Options\">nosniff\u003C\u002FHeader>\n            \u003CHeader name=\"X-Frame-Options\">DENY\u003C\u002FHeader>\n            \u003CHeader name=\"Strict-Transport-Security\">max-age=31536000; includeSubDomains\u003C\u002FHeader>\n            \u003CHeader name=\"Cache-Control\">no-store, no-cache, must-revalidate\u003C\u002FHeader>\n            \u003CHeader name=\"Content-Security-Policy\">default-src 'none'\u003C\u002FHeader>\n            \u003CHeader name=\"X-Request-ID\">{messageid}\u003C\u002FHeader>\n        \u003C\u002FHeaders>\n    \u003C\u002FSet>\n    \u003CRemove>\n        \u003CHeaders>\n            \u003CHeader name=\"X-Powered-By\"\u002F>\n            \u003CHeader name=\"Server\"\u002F>\n        \u003C\u002FHeaders>\n    \u003C\u002FRemove>\n    \u003CIgnoreUnresolvedVariables>false\u003C\u002FIgnoreUnresolvedVariables>\n    \u003CAssignTo createNew=\"false\" transport=\"http\" type=\"response\"\u002F>\n\u003C\u002FAssignMessage>\n```\n\n## Advanced API Security\n\nEnable Apigee's Advanced API Security add-on for machine-learning-based threat detection:\n\n```bash\n# Enable Advanced API Security on Apigee X instance\ngcloud apigee organizations update $ORG_NAME \\\n  --advanced-api-security-config=enabled\n\n# View detected abuse alerts\ngcloud apigee apis security-reports list \\\n  --organization=$ORG_NAME \\\n  --environment=$ENV_NAME\n\n# Create security action to block suspicious traffic\ngcloud apigee security-actions create \\\n  --organization=$ORG_NAME \\\n  --environment=$ENV_NAME \\\n  --action-type=DENY \\\n  --condition-type=IP_ADDRESS \\\n  --condition-values=\"192.168.1.100,10.0.0.50\" \\\n  --description=\"Block identified malicious IPs\"\n```\n\n## Deployment\n\n```bash\n# Deploy proxy bundle with security policies\ngcloud apigee apis deploy \\\n  --api=$API_NAME \\\n  --environment=$ENV_NAME \\\n  --revision=$REVISION \\\n  --organization=$ORG_NAME\n\n# Validate deployment\ngcloud apigee apis list-deployments \\\n  --api=$API_NAME \\\n  --organization=$ORG_NAME\n```\n\n## References\n\n- Apigee JSON Threat Protection: https:\u002F\u002Fcloud.google.com\u002Fapigee\u002Fdocs\u002Fapi-platform\u002Freference\u002Fpolicies\u002Fjson-threat-protection-policy\n- Google Cloud Apigee Security Best Practices: https:\u002F\u002Fcloud.google.com\u002Farchitecture\u002Fbest-practices-securing-applications-and-apis-using-apigee\n- Apigee Advanced API Security: https:\u002F\u002Fdocs.cloud.google.com\u002Fapigee\u002Fdocs\u002Fapi-security\n- Apigee OWASP API Top 10: https:\u002F\u002Fdocs.apigee.com\u002Fapi-platform\u002Ffaq\u002Fowasp-top-api-threats\n- Wallarm Apigee Security Policies Guide: https:\u002F\u002Flab.wallarm.com\u002Fwhat\u002Fapigee-api-security-policies-howto\u002F\n",{"name":5,"note":25,"tags":26,"author":36,"domain":37,"source":38,"license":15,"version":39,"nist_csf":40,"subdomain":45,"description":7,"mitre_attack":46,"source_commit":52},"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.",[27,28,29,30,31,32,33,34,35],"apigee","api-gateway","threat-protection","json-threat-protection","xml-threat-protection","spike-arrest","oauth2","google-cloud","owasp-api-top-10","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[41,42,43,44],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01","api-security",[47,48,49,50,51],"T1190","T1059.007","T1552.001","T1078.004","T1530","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fimplementing-api-threat-protection-with-apigee",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-api-threat-protection-with-apigee",{"tool":69,"command":70},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-api-threat-protection-with-apigee",{"tool":72,"command":73},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-api-threat-protection-with-apigee","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-api-threat-protection-with-apigee\u002FSKILL.md",true,[77,81,87],{"path":78,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fapi-reference.md","REFERENCE","参考文档",1687,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-api-threat-protection-with-apigee\u002Freferences\u002Fapi-reference.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fagent.py","SCRIPT","脚本",6625,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-api-threat-protection-with-apigee\u002Fscripts\u002Fagent.py",[94,102,109,117,125,133],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]