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 "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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Load Balancer Rate Limit": Load Balancer Rate Limit is a networking traffic control that caps request volume over a period for traffic distribution. 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.
“Ejemplo en borrador: The network engineering team used Load Balancer Rate Limit when traffic shifted between regions, so the team could protect services from overload before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Application Attack Surface": Application Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for software security and abuse resistance. 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 Application Attack Surface when a form received unusual input, so the team could prioritize risk reduction before the risk review began.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
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 "Identity Patch Window": Identity Patch Window is a security remediation schedule that sets when a fix should be applied for user and workload identity. 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.
“Ejemplo en borrador: The security team used Identity Patch Window when a service account requested access, so the team could repair systems without unnecessary disruption before the risk review began.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Incident Response Attack Surface": Incident Response Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for security event handling. 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 Incident Response Attack Surface when an alert escalated to response, so the team could prioritize risk reduction before the risk review began.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”