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 Rate Limit": CDN Rate Limit is a networking traffic control that caps request volume over a period for content delivery and edge caching. 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 CDN Rate Limit when a cache region served an asset, so the team could protect services from overload before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Zero Trust Evidence Chain": Zero Trust Evidence Chain is a security audit record that preserves how security evidence was collected and handled for continuous verification model. It uses timestamps, hashes, owners, and storage controls so teams can support trustworthy investigation while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The security team used Zero Trust Evidence Chain when a device changed posture, so the team could support trustworthy investigation before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Supply Chain Trust Boundary": Supply Chain Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for dependencies, builds, and artifacts. 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 Supply Chain Trust Boundary when a package update arrived, so the team could avoid accidental privilege crossing before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Incident Response Detection Rule": Incident Response Detection Rule is a security security analytic that matches suspicious behavior or known indicators for security event handling. It uses logs, thresholds, signatures, and behavioral context so teams can surface actionable alerts while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The security team used Incident Response Detection Rule when an alert escalated to response, so the team could surface actionable alerts before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Endpoint Phishing Resistance": Endpoint Phishing Resistance is a security identity control that reduces success of credential theft attacks for user device and server protection. 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 Endpoint Phishing Resistance when a workstation reported suspicious activity, so the team could protect sign-in flows before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Incident Response Abuse Throttle": Incident Response Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for security event handling. 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 Incident Response Abuse Throttle when an alert escalated to response, so the team could protect public access without a login wall before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Packet Egress Policy": Packet Egress Policy is a networking outbound control that decides where workloads may send traffic for unit of network transmission. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used Packet Egress Policy when packet loss increased, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Data Loss Secret Scanner": Data Loss Secret Scanner is a security preventive control that finds credentials before they spread for sensitive data exposure risk. 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 Data Loss Secret Scanner when a report included private metadata, so the team could stop accidental key exposure before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Endpoint Policy Decision": Endpoint Policy Decision is a security authorization decision that determines whether an action should be allowed for user device and server protection. It uses identity, resource, context, and policy evaluation so teams can enforce least privilege while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The security team used Endpoint Policy Decision when a workstation reported suspicious activity, so the team could enforce least privilege before the risk review began.”