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
機械支援の翻訳下書き (Japanese) for "Firewall Route Leak Guard": Firewall Route Leak Guard is a networking routing control that detects and blocks accidental route propagation for network traffic filtering. It uses prefix filters, validation, and peer policy so teams can protect reachability while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used Firewall Route Leak Guard when a new rule matched traffic, so the team could protect reachability before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Supply Chain Trust Boundary": Supply Chain Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for dependencies, builds, and artifacts. It uses network edges, service roles, and data classifications so teams can avoid accidental privilege crossing while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The security team used Supply Chain Trust Boundary when a package update arrived, so the team could avoid accidental privilege crossing before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Service Mesh Traffic Shaper": Service Mesh Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for east-west service communication. 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.
“例文の下書き: The network engineering team used Service Mesh Traffic Shaper when a service called another service, so the team could protect important traffic before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Application Policy Decision": Application Policy Decision is a security authorization decision that determines whether an action should be allowed for software security and abuse resistance. It uses identity, resource, context, and policy evaluation so teams can enforce least privilege while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The security team used Application Policy Decision when a form received unusual input, so the team could enforce least privilege before the risk review began.”
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) for "Supply Chain Abuse Throttle": Supply Chain Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for dependencies, builds, and artifacts. 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.
“例文の下書き: The security team used Supply Chain Abuse Throttle when a package update arrived, so the team could protect public access without a login wall before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Incident Response Containment Plan": Incident Response Containment Plan is a security response plan that limits damage after a suspected compromise for security event handling. 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.
“例文の下書き: The security team used Incident Response Containment Plan when an alert escalated to response, so the team could reduce attacker dwell time before the risk review began.”
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) for "Endpoint Patch Window": Endpoint Patch Window is a security remediation schedule that sets when a fix should be applied for user device and server protection. 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.
“例文の下書き: The security team used Endpoint Patch Window when a workstation reported suspicious activity, so the team could repair systems without unnecessary disruption before the risk review began.”