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
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Data Loss Trust Boundary": Data Loss Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for sensitive data exposure risk. 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.
“Ejemplo en borrador: The security team used Data Loss Trust Boundary when a report included private metadata, so the team could avoid accidental privilege crossing before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Service Mesh Traffic Shaper": Service Mesh Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for east-west service communication. It uses queues, rate limits, and quality-of-service rules so teams can protect important traffic while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used Service Mesh Traffic Shaper when a service called another service, so the team could protect important traffic before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Supply Chain Attack Surface": Supply Chain Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for dependencies, builds, and artifacts. 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.
“Ejemplo en borrador: The security team used Supply Chain Attack Surface when a package update arrived, so the team could prioritize risk reduction before the risk review began.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Latency Failover Policy": Latency Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for time between request and response. 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.
“Ejemplo en borrador: The network engineering team used Latency Failover Policy when a user saw slow responses, so the team could recover from outages predictably before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "HTTP Health Probe": HTTP Health Probe is a networking availability check that tests whether a service or path can receive traffic for application-layer request routing. It uses timed requests, thresholds, and regional checks so teams can send traffic only to healthy targets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used HTTP Health Probe when a client retried a request, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Incident Response Phishing Resistance": Incident Response Phishing Resistance is a security identity control that reduces success of credential theft attacks for security event handling. 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.
“Ejemplo en borrador: The security team used Incident Response Phishing Resistance when an alert escalated to response, so the team could protect sign-in flows before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Access Phishing Resistance": Access Phishing Resistance is a security identity control that reduces success of credential theft attacks for authorization and privilege control. 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.
“Ejemplo en borrador: The security team used Access Phishing Resistance when a role gained new permissions, so the team could protect sign-in flows before the risk review began.”
Borrador de traduccion automatica (Spanish) for "VPN Resolver Cache": VPN Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for private tunnel connectivity. It uses TTL rules, cache keys, and invalidation so teams can reduce lookup latency while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used VPN Resolver Cache when a remote user connected, so the team could reduce lookup latency before traffic crossed a service boundary.”