Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
2,337 definitions
Automatischer Uebersetzungsentwurf (German) for "HTTP Rate Limit": HTTP Rate Limit is a networking traffic control that caps request volume over a period for application-layer request routing. 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.
“Beispielentwurf: The network engineering team used HTTP Rate Limit when a client retried a request, so the team could protect services from overload before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Firewall Ingress Rule": Firewall Ingress Rule is a networking boundary rule that controls how external traffic enters a service for network traffic filtering. 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.
“Beispielentwurf: The network engineering team used Firewall Ingress Rule when a new rule matched traffic, so the team could keep entry points predictable before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Endpoint Trust Boundary": Endpoint Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for user device and server protection. It uses network edges, service roles, and data classifications so teams can avoid accidental privilege crossing while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Endpoint Trust Boundary when a workstation reported suspicious activity, so the team could avoid accidental privilege crossing before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Application Containment Plan": Application Containment Plan is a security response plan that limits damage after a suspected compromise for software security and abuse resistance. It uses isolation steps, credential rotation, and communication paths so teams can reduce attacker dwell time while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Application Containment Plan when a form received unusual input, so the team could reduce attacker dwell time before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Identity Secret Scanner": Identity Secret Scanner is a security preventive control that finds credentials before they spread for user and workload identity. 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.
“Beispielentwurf: The security team used Identity Secret Scanner when a service account requested access, so the team could stop accidental key exposure before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "CDN Resolver Cache": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Data Loss Patch Window": Data Loss Patch Window is a security remediation schedule that sets when a fix should be applied for sensitive data exposure risk. 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.
“Beispielentwurf: The security team used Data Loss Patch Window when a report included private metadata, so the team could repair systems without unnecessary disruption before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "VPN Anycast Endpoint": VPN Anycast Endpoint is a networking routing pattern that advertises one address from multiple locations for private tunnel connectivity. 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.
“Beispielentwurf: The network engineering team used VPN Anycast Endpoint when a remote user connected, so the team could serve users from nearby healthy sites before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Load Balancer Ingress Rule": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Application Abuse Throttle": Application Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for software security and abuse resistance. 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.
“Beispielentwurf: The security team used Application Abuse Throttle when a form received unusual input, so the team could protect public access without a login wall before the risk review began.”