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 "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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) for "VPN Rate Limit": VPN Rate Limit is a networking traffic control that caps request volume over a period for private tunnel connectivity. 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.
“例文の下書き: The network engineering team used VPN Rate Limit when a remote user connected, so the team could protect services from overload before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "HTTP Route Leak Guard": HTTP Route Leak Guard is a networking routing control that detects and blocks accidental route propagation for application-layer request routing. 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 HTTP Route Leak Guard when a client retried a request, so the team could protect reachability before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Supply Chain Data Redaction": Supply Chain Data Redaction is a security privacy control that removes sensitive values before data leaves a protected context for dependencies, builds, and artifacts. It uses field rules, hashing, and safe logging so teams can share evidence without leaking secrets while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The security team used Supply Chain Data Redaction when a package update arrived, so the team could share evidence without leaking secrets before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Endpoint Phishing Resistance": Endpoint Phishing Resistance is a security identity control that reduces success of credential theft attacks for user device and server protection. 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.
“例文の下書き: The security team used Endpoint Phishing Resistance when a workstation reported suspicious activity, so the team could protect sign-in flows before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Zero Trust Detection Rule": Zero Trust Detection Rule is a security security analytic that matches suspicious behavior or known indicators for continuous verification model. It uses logs, thresholds, signatures, and behavioral context so teams can surface actionable alerts while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The security team used Zero Trust Detection Rule when a device changed posture, so the team could surface actionable alerts before the risk review began.”
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) for "Access Patch Window": Access Patch Window is a security remediation schedule that sets when a fix should be applied for authorization and privilege control. 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 Access Patch Window when a role gained new permissions, so the team could repair systems without unnecessary disruption before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Subnet Ingress Rule": Subnet Ingress Rule is a networking boundary rule that controls how external traffic enters a service for address segmentation. 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.
“例文の下書き: The network engineering team used Subnet Ingress Rule when a workload moved networks, so the team could keep entry points predictable before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Endpoint Policy Decision": Endpoint Policy Decision is a security authorization decision that determines whether an action should be allowed for user device and server protection. 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 Endpoint Policy Decision when a workstation reported suspicious activity, so the team could enforce least privilege before the risk review began.”