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 "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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Firewall Rate Limit": Firewall Rate Limit is a networking traffic control that caps request volume over a period for network traffic filtering. 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.
“Exemplo em rascunho: The network engineering team used Firewall Rate Limit when a new rule matched traffic, so the team could protect services from overload before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "CDN Traffic Shaper": CDN Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for content delivery and edge caching. 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 CDN Traffic Shaper when a cache region served an asset, so the team could protect important traffic before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) 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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Vulnerability Evidence Chain": Vulnerability Evidence Chain is a security audit record that preserves how security evidence was collected and handled for weakness tracking and remediation. It uses timestamps, hashes, owners, and storage controls so teams can support trustworthy investigation while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The security team used Vulnerability Evidence Chain when a scanner found a critical issue, so the team could support trustworthy investigation before the risk review began.”
Rascunho de traducao automatica (Portuguese) for "Access Patch Window": Access Patch Window is a security remediation schedule that sets when a fix should be applied for authorization and privilege control. 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.
“Exemplo em rascunho: The security team used Access Patch Window when a role gained new permissions, so the team could repair systems without unnecessary disruption before the risk review began.”
Rascunho de traducao automatica (Portuguese) for "Firewall Resolver Cache": Firewall Resolver Cache is a networking performance layer that stores DNS answers for reuse until they expire for network traffic filtering. 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 Firewall Resolver Cache when a new rule matched traffic, so the team could reduce lookup latency 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 "Data Loss Abuse Throttle": Data Loss Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for sensitive data exposure risk. 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 Data Loss Abuse Throttle when a report included private metadata, so the team could protect public access without a login wall before the risk review began.”