slug: google-cloud-armor
provider: Google Cloud Armor
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: Security Policies
  spec_file: google-cloud-armor-security-policies-api-openapi.yml
  capability_id: BC-620
  capability_id_l1: BC-620
  capability_name: Cybersecurity Management
  confidence: 0.8
  evidence: '"manage security policies, rules, and threat intelligence configurations for protecting applications
    from DDoS attacks and web-based threats"; createSecurityPolicy'
  reason: WAF/DDoS security policy management is plainly a cybersecurity control capability. Ambiguous
    between security architecture/controls and threat response sub-capabilities, so only the L1 is asserted.
- tag: SecurityPolicyRules
  spec_file: google-cloud-armor-securitypolicyrules-api-openapi.yml
  capability_id: BC-620
  capability_id_l1: BC-620
  capability_name: Cybersecurity Management
  confidence: 0.78
  evidence: POST .../securityPolicies/{securityPolicy}/addRule "Add a rule to a security policy"; schema
    SecurityPolicyRule
  reason: Adding/removing WAF rules that block malicious traffic is operational cybersecurity control
    management; sub-capability is ambiguous so L1 only.