2,338 definitions
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.”
Load Balancer Ingress Rule is a networking boundary rule that controls how external traffic enters a service for traffic distribution. 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 Load Balancer Ingress Rule when traffic shifted between regions, so the team could keep entry points predictable before traffic crossed a service boundary.”
Supply Chain Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for dependencies, builds, and artifacts. It uses rate limits, reputation signals, and challenge steps so teams can protect public access without a login wall while keeping evidence, reliability, and public-safe operational boundaries clear.
“The security team used Supply Chain Abuse Throttle when a package update arrived, so the team could protect public access without a login wall before the risk review began.”
CDN Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for content delivery and edge caching. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used CDN Path Trace when a cache region served an asset, so the team could debug connectivity issues before traffic crossed a service boundary.”
Zero Trust Detection Rule is a security security analytic that matches suspicious behavior or known indicators for continuous verification model. 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 Zero Trust Detection Rule when a device changed posture, so the team could surface actionable alerts before the risk review began.”
Identity Forensic Snapshot is a security investigation artifact that captures system state for later review for user and workload identity. It uses logs, configuration, hashes, and time-bounded data so teams can analyze incidents without changing evidence while keeping evidence, reliability, and public-safe operational boundaries clear.
“The security team used Identity Forensic Snapshot when a service account requested access, so the team could analyze incidents without changing evidence before the risk review began.”
Application Secret Scanner is a security preventive control that finds credentials before they spread for software security and abuse resistance. It uses pattern matching, entropy checks, and allowlists so teams can stop accidental key exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“The security team used Application Secret Scanner when a form received unusual input, so the team could stop accidental key exposure before the risk review began.”
Firewall Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for network traffic filtering. 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 Firewall Failover Policy when a new rule matched traffic, so the team could recover from outages predictably before traffic crossed a service boundary.”
Service Mesh Path Trace is a networking diagnostic record that shows where traffic travels and where delay or loss appears for east-west service communication. It uses hop data, timing, and network metadata so teams can debug connectivity issues while keeping evidence, reliability, and public-safe operational boundaries clear.
“The network engineering team used Service Mesh Path Trace when a service called another service, so the team could debug connectivity issues 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.”