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 "Identity Attack Surface": Identity Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for user and workload identity. It uses asset inventory, route discovery, and permission mapping so teams can prioritize risk reduction while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The security team used Identity Attack Surface when a service account requested access, so the team could prioritize risk reduction before the risk review began.”
Borrador de traduccion automatica (Spanish) for "VPN Ingress Rule": VPN Ingress Rule is a networking boundary rule that controls how external traffic enters a service for private tunnel connectivity. 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 VPN Ingress Rule when a remote user connected, so the team could keep entry points predictable before traffic crossed a service boundary.”
Borrador de traduccion automatica (Spanish) for "Data Loss Evidence Chain": Data Loss Evidence Chain is a security audit record that preserves how security evidence was collected and handled for sensitive data exposure risk. 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 Data Loss Evidence Chain when a report included private metadata, so the team could support trustworthy investigation 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 "Application Phishing Resistance": Application Phishing Resistance is a security identity control that reduces success of credential theft attacks for software security and abuse resistance. 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 Application Phishing Resistance when a form received unusual input, so the team could protect sign-in flows before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Firewall Traffic Shaper": Firewall Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for network traffic filtering. 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.
“Ejemplo en borrador: The network engineering team used Firewall Traffic Shaper when a new rule matched traffic, so the team could protect important traffic before traffic crossed a service boundary.”
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 "Incident Response Detection Rule": Incident Response Detection Rule is a security security analytic that matches suspicious behavior or known indicators for security event handling. It uses logs, thresholds, signatures, and behavioral context so teams can surface actionable alerts while keeping evidence, reliability, and public-safe operational boundaries clear.
“Ejemplo en borrador: The security team used Incident Response Detection Rule when an alert escalated to response, so the team could surface actionable alerts before the risk review began.”
Borrador de traduccion automatica (Spanish) for "Cloud Containment Plan": Cloud Containment Plan is a security response plan that limits damage after a suspected compromise for cloud account and resource security. 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 Cloud Containment Plan when a storage bucket changed policy, so the team could reduce attacker dwell time 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.”