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 "Load Balancer Ingress Rule": Load Balancer Ingress Rule is a networking boundary rule that controls how external traffic enters a service for traffic distribution. 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.
“Ejemplo en borrador: The network engineering team used Load Balancer Ingress Rule when traffic shifted between regions, so the team could keep entry points predictable before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Subnet Certificate Monitor": Subnet Certificate Monitor is a networking security monitor that tracks certificate validity and configuration for address segmentation. 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 Subnet Certificate Monitor when a workload moved networks, so the team could avoid trust failures before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Service Mesh Rate Limit": Service Mesh Rate Limit is a networking traffic control that caps request volume over a period for east-west service communication. 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.
“Ejemplo en borrador: The network engineering team used Service Mesh Rate Limit when a service called another service, so the team could protect services from overload before traffic crossed a service boundary.”
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 "Data Loss Containment Plan": Data Loss Containment Plan is a security response plan that limits damage after a suspected compromise for sensitive data exposure risk. 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.
“Ejemplo en borrador: The security team used Data Loss Containment Plan when a report included private metadata, so the team could reduce attacker dwell time before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Cloud Evidence Chain": Cloud Evidence Chain is a security audit record that preserves how security evidence was collected and handled for cloud account and resource security. It uses timestamps, hashes, owners, and storage controls so teams can support trustworthy investigation while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The security team used Cloud Evidence Chain when a storage bucket changed policy, so the team could support trustworthy investigation before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Secrets Patch Window": Secrets Patch Window is a security remediation schedule that sets when a fix should be applied for keys, tokens, and credentials. 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 Secrets Patch Window when a secret appeared in logs, so the team could repair systems without unnecessary disruption before the risk review began.”
Borrador de traduccion automatica (Spanish) 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.
“Ejemplo en borrador: 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.”
Borrador de traduccion automatica (Spanish) for "Vulnerability Forensic Snapshot": Vulnerability Forensic Snapshot is a security investigation artifact that captures system state for later review for weakness tracking and remediation. 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 Vulnerability Forensic Snapshot when a scanner found a critical issue, so the team could analyze incidents without changing evidence before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Application Abuse Throttle": Application Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for software security and abuse resistance. 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.
“Ejemplo en borrador: The security team used Application Abuse Throttle when a form received unusual input, so the team could protect public access without a login wall before the risk review began.”