2,339 definitions
CDN Rate Limit is a networking traffic control that caps request volume over a period for content delivery and edge caching. It uses identity keys, windows, and response policies so teams can protect services from overload while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used CDN Rate Limit when a cache region served an asset, so the team could protect services from overload before traffic crossed a service boundary.”
Access Patch Window is a security remediation schedule that sets when a fix should be applied for authorization and privilege control. It uses risk severity, testing needs, and maintenance constraints so teams can repair systems without unnecessary disruption while keeping evidence, reliability, and public-safe operational boundaries clear.
“The security team used Access Patch Window when a role gained new permissions, so the team could repair systems without unnecessary disruption before the risk review began.”
CDN Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for content delivery and edge caching. It uses TTL rules, cache keys, and invalidation so teams can reduce lookup latency while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used CDN Resolver Cache when a cache region served an asset, so the team could reduce lookup latency before traffic crossed a service boundary.”
Subnet Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for address segmentation. It uses regional announcements, health checks, and traffic steering so teams can serve users from nearby healthy sites while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used Subnet Anycast Endpoint when a workload moved networks, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
Service Mesh Route Leak Guard is a networking routing control that detects and blocks accidental route propagation for east-west service communication. It uses prefix filters, validation, and peer policy so teams can protect reachability while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used Service Mesh Route Leak Guard when a service called another service, so the team could protect reachability before traffic crossed a service boundary.”
Secrets Patch Window is a security remediation schedule that sets when a fix should be applied for keys, tokens, and credentials. It uses risk severity, testing needs, and maintenance constraints so teams can repair systems without unnecessary disruption while keeping evidence, reliability, and public-safe operational boundaries clear.
“The security team used Secrets Patch Window when a secret appeared in logs, so the team could repair systems without unnecessary disruption before the risk review began.”
HTTP Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for application-layer request routing. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used HTTP Failover Policy when a client retried a request, so the team could recover from outages predictably before traffic crossed a service boundary.”
Identity Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for user and workload identity. It uses asset inventory, route discovery, and permission mapping so teams can prioritize risk reduction while keeping evidence, reliability, and public-safe operational boundaries clear.
“The security team used Identity Attack Surface when a service account requested access, so the team could prioritize risk reduction before the risk review began.”
Access Detection Rule is a security security analytic that matches suspicious behavior or known indicators for authorization and privilege control. It uses logs, thresholds, signatures, and behavioral context so teams can surface actionable alerts while keeping evidence, reliability, and public-safe operational boundaries clear.
“The security team used Access Detection Rule when a role gained new permissions, so the team could surface actionable alerts before the risk review began.”
Service Mesh Ingress Rule is a networking boundary rule that controls how external traffic enters a service for east-west service communication. It uses hostnames, paths, protocols, and policy checks so teams can keep entry points predictable while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used Service Mesh Ingress Rule when a service called another service, so the team could keep entry points predictable before traffic crossed a service boundary.”