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 "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.
“Exemplo em rascunho: 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.”
Rascunho de traducao automatica (Portuguese) for "Endpoint Containment Plan": Endpoint Containment Plan is a security response plan that limits damage after a suspected compromise for user device and server protection. 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.
“Exemplo em rascunho: The security team used Endpoint Containment Plan when a workstation reported suspicious activity, so the team could reduce attacker dwell time before the risk review began.”
Rascunho de traducao automatica (Portuguese) for "Incident Response Phishing Resistance": Incident Response Phishing Resistance is a security identity control that reduces success of credential theft attacks for security event handling. 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.
“Exemplo em rascunho: The security team used Incident Response Phishing Resistance when an alert escalated to response, so the team could protect sign-in flows before the risk review began.”
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 "Endpoint Secret Scanner": Endpoint Secret Scanner is a security preventive control that finds credentials before they spread for user device and server protection. 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.
“Exemplo em rascunho: The security team used Endpoint Secret Scanner when a workstation reported suspicious activity, so the team could stop accidental key exposure before the risk review began.”
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 "Access Phishing Resistance": Access Phishing Resistance is a security identity control that reduces success of credential theft attacks for authorization and privilege control. 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.
“Exemplo em rascunho: The security team used Access Phishing Resistance when a role gained new permissions, so the team could protect sign-in flows before the risk review began.”
Rascunho de traducao automatica (Portuguese) for "Service Mesh Ingress Rule": Service Mesh Ingress Rule is a networking boundary rule that controls how external traffic enters a service for east-west service communication. 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 Service Mesh Ingress Rule when a service called another service, 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 "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.”