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
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "VPN Ingress Rule": VPN Ingress Rule is a networking boundary rule that controls how external traffic enters a service for private tunnel connectivity. 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.
“Exemplo em rascunho: The network engineering team used VPN Ingress Rule when a remote user connected, so the team could keep entry points predictable before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Service Mesh Route Leak Guard": Service Mesh Route Leak Guard is a networking routing control that detects and blocks accidental route propagation for east-west service communication. It uses prefix filters, validation, and peer policy so teams can protect reachability while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used Service Mesh Route Leak Guard when a service called another service, so the team could protect reachability before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Secrets Data Redaction": Secrets Data Redaction is a security privacy control that removes sensitive values before data leaves a protected context for keys, tokens, and credentials. It uses field rules, hashing, and safe logging so teams can share evidence without leaking secrets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The security team used Secrets Data Redaction when a secret appeared in logs, so the team could share evidence without leaking secrets before the risk review began.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Secrets Detection Rule": Secrets Detection Rule is a security security analytic that matches suspicious behavior or known indicators for keys, tokens, and credentials. It uses logs, thresholds, signatures, and behavioral context so teams can surface actionable alerts while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The security team used Secrets Detection Rule when a secret appeared in logs, so the team could surface actionable alerts before the risk review began.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Firewall Traffic Shaper": Firewall Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for network traffic filtering. 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.
“Exemplo em rascunho: The network engineering team used Firewall Traffic Shaper when a new rule matched traffic, so the team could protect important traffic before traffic crossed a service boundary.”