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 "Packet Ingress Rule": Packet Ingress Rule is a networking boundary rule that controls how external traffic enters a service for unit of network transmission. 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 Packet Ingress Rule when packet loss increased, so the team could keep entry points predictable before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) for "Latency Health Probe": Latency Health Probe is a networking availability check that tests whether a service or path can receive traffic for time between request and response. It uses timed requests, thresholds, and regional checks so teams can send traffic only to healthy targets while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used Latency Health Probe when a user saw slow responses, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Incident Response Phishing Resistance": Incident Response Phishing Resistance is a security identity control that reduces success of credential theft attacks for security event handling. 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 Incident Response Phishing Resistance when an alert escalated to response, so the team could protect sign-in flows before the risk review began.”
機械支援の翻訳下書き (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 "Threat Intel Detection Rule": Threat Intel Detection Rule is a security security analytic that matches suspicious behavior or known indicators for external risk and indicator context. 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 Threat Intel Detection Rule when a new campaign indicator appeared, so the team could surface actionable alerts before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Endpoint Secret Scanner": Endpoint Secret Scanner is a security preventive control that finds credentials before they spread for user device and server protection. It uses pattern matching, entropy checks, and allowlists so teams can stop accidental key exposure while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The security team used Endpoint Secret Scanner when a workstation reported suspicious activity, so the team could stop accidental key exposure before the risk review began.”
機械支援の翻訳下書き (Japanese) 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.
“例文の下書き: 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.”
機械支援の翻訳下書き (Japanese) for "Secrets Data Redaction": Secrets Data Redaction is a security privacy control that removes sensitive values before data leaves a protected context for keys, tokens, and credentials. 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 Secrets Data Redaction when a secret appeared in logs, so the team could share evidence without leaking secrets 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.”