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 "Zero Trust Forensic Snapshot": Zero Trust Forensic Snapshot is a security investigation artifact that captures system state for later review for continuous verification model. 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.
“Ejemplo en borrador: The security team used Zero Trust Forensic Snapshot when a device changed posture, so the team could analyze incidents without changing evidence before the risk review began.”
Borrador de traduccion automatica (Spanish) for "CDN Certificate Monitor": CDN Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for content delivery and edge caching. It uses expiry checks, chain validation, and alerting so teams can avoid trust failures while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The network engineering team used CDN Certificate Monitor when a cache region served an asset, so the team could avoid trust failures before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Incident Response Patch Window": Incident Response Patch Window is a security remediation schedule that sets when a fix should be applied for security event handling. 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.
“Ejemplo en borrador: The security team used Incident Response Patch Window when an alert escalated to response, so the team could repair systems without unnecessary disruption before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Secrets Phishing Resistance": Secrets Phishing Resistance is a security identity control that reduces success of credential theft attacks for keys, tokens, and credentials. 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 Secrets Phishing Resistance when a secret appeared in logs, so the team could protect sign-in flows before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Firewall Egress Policy": Firewall Egress Policy is a networking outbound control that decides where workloads may send traffic for network traffic filtering. 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 Firewall Egress Policy when a new rule matched traffic, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Latency Egress Policy": Latency Egress Policy is a networking outbound control that decides where workloads may send traffic for time between request and response. 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 Latency Egress Policy when a user saw slow responses, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”