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 Policy Decision": Incident Response Policy Decision is a security authorization decision that determines whether an action should be allowed for security event handling. It uses identity, resource, context, and policy evaluation so teams can enforce least privilege while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The security team used Incident Response Policy Decision when an alert escalated to response, so the team could enforce least privilege 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 "CDN Ingress Rule": CDN Ingress Rule is a networking boundary rule that controls how external traffic enters a service for content delivery and edge caching. 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 CDN Ingress Rule when a cache region served an asset, so the team could keep entry points predictable before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Firewall Health Probe": Firewall Health Probe is a networking availability check that tests whether a service or path can receive traffic for network traffic filtering. 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.
“Exemplo em rascunho: The network engineering team used Firewall Health Probe when a new rule matched traffic, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "VPN Rate Limit": VPN Rate Limit is a networking traffic control that caps request volume over a period for private tunnel connectivity. 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 VPN Rate Limit when a remote user connected, so the team could protect services from overload before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Load Balancer Packet Capture": Load Balancer Packet Capture is a networking diagnostic artifact that records network packets for analysis for traffic distribution. It uses bounded capture windows, filters, and redaction so teams can investigate protocol behavior safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used Load Balancer Packet Capture when traffic shifted between regions, so the team could investigate protocol behavior safely before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Load Balancer Certificate Monitor": Load Balancer Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for traffic distribution. It uses expiry checks, chain validation, and alerting so teams can avoid trust failures while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The network engineering team used Load Balancer Certificate Monitor when traffic shifted between regions, so the team could avoid trust failures before traffic crossed a service boundary.”
Rascunho de traducao automatica (Portuguese) for "Application Patch Window": Application Patch Window is a security remediation schedule that sets when a fix should be applied for software security and abuse resistance. 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 Application Patch Window when a form received unusual input, so the team could repair systems without unnecessary disruption before the risk review began.”
Rascunho de traducao automatica (Portuguese) for "Access Policy Decision": Access Policy Decision is a security authorization decision that determines whether an action should be allowed for authorization and privilege control. It uses identity, resource, context, and policy evaluation so teams can enforce least privilege while keeping evidence, reliability, and public-safe operational boundaries clear.
“Exemplo em rascunho: The security team used Access Policy Decision when a role gained new permissions, so the team could enforce least privilege before the risk review began.”
Rascunho de traducao automatica (Portuguese) for "Latency Traffic Shaper": Latency Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for time between request and response. 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 Latency Traffic Shaper when a user saw slow responses, so the team could protect important traffic before traffic crossed a service boundary.”