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 "Data Loss Containment Plan": Data Loss Containment Plan is a security response plan that limits damage after a suspected compromise for sensitive data exposure risk. 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 Data Loss Containment Plan when a report included private metadata, so the team could reduce attacker dwell time before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Incident Response Trust Boundary": Incident Response Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for security event handling. 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 Incident Response Trust Boundary when an alert escalated to response, so the team could avoid accidental privilege crossing before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Secrets Patch Window": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Identity Attack Surface": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Supply Chain Abuse Throttle": 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.
“Beispielentwurf: 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.”
Automatischer Uebersetzungsentwurf (German) for "Supply Chain Patch Window": Supply Chain Patch Window is a security remediation schedule that sets when a fix should be applied for dependencies, builds, and artifacts. 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 Supply Chain Patch Window when a package update arrived, so the team could repair systems without unnecessary disruption before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "HTTP Resolver Cache": HTTP Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for application-layer request routing. 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 HTTP Resolver Cache when a client retried a request, so the team could reduce lookup latency before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Firewall Route Leak Guard": Firewall Route Leak Guard is a networking routing control that detects and blocks accidental route propagation for network traffic filtering. It uses prefix filters, validation, and peer policy so teams can protect reachability while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The network engineering team used Firewall Route Leak Guard when a new rule matched traffic, so the team could protect reachability before traffic crossed a service boundary.”
Automatischer Uebersetzungsentwurf (German) for "Access Secret Scanner": Access Secret Scanner is a security preventive control that finds credentials before they spread for authorization and privilege control. 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 Access Secret Scanner when a role gained new permissions, so the team could stop accidental key exposure before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Packet Packet Capture": Packet Packet Capture is a networking diagnostic artifact that records network packets for analysis for unit of network transmission. 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 Packet Packet Capture when packet loss increased, so the team could investigate protocol behavior safely before traffic crossed a service boundary.”