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 "Incident Response Forensic Snapshot": Incident Response Forensic Snapshot is a security investigation artifact that captures system state for later review for security event handling. 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.
“Beispielentwurf: The security team used Incident Response Forensic Snapshot when an alert escalated to response, so the team could analyze incidents without changing evidence before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Vulnerability Attack Surface": Vulnerability Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for weakness tracking and remediation. 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.
“Beispielentwurf: The security team used Vulnerability Attack Surface when a scanner found a critical issue, so the team could prioritize risk reduction before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Subnet Anycast Endpoint": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Service Mesh Path Trace": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Vulnerability Phishing Resistance": Vulnerability Phishing Resistance is a security identity control that reduces success of credential theft attacks for weakness tracking and remediation. It uses passkeys, hardware-backed factors, and origin checks so teams can protect sign-in flows while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Vulnerability Phishing Resistance when a scanner found a critical issue, so the team could protect sign-in flows 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 "CDN Packet Capture": CDN Packet Capture is a networking diagnostic artifact that records network packets for analysis for content delivery and edge caching. It uses bounded capture windows, filters, and redaction so teams can investigate protocol behavior safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used CDN Packet Capture when a cache region served an asset, so the team could investigate protocol behavior safely before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Packet Ingress Rule": Packet Ingress Rule is a networking boundary rule that controls how external traffic enters a service for unit of network transmission. 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 Packet Ingress Rule when packet loss increased, so the team could keep entry points predictable before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "HTTP Failover Policy": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Packet Failover Policy": Packet Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for unit of network transmission. 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.
“Beispielentwurf: The network engineering team used Packet Failover Policy when packet loss increased, so the team could recover from outages predictably before traffic crossed a service boundary.”