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 "Threat Intel Containment Plan": Threat Intel Containment Plan is a security response plan that limits damage after a suspected compromise for external risk and indicator context. 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 Threat Intel Containment Plan when a new campaign indicator appeared, so the team could reduce attacker dwell time before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Latency Failover Policy": Latency Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for time between request and response. It uses health signals, priorities, and cooldown windows so teams can recover from outages predictably while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used Latency Failover Policy when a user saw slow responses, so the team could recover from outages predictably before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Access Data Redaction": Access Data Redaction is a security privacy control that removes sensitive values before data leaves a protected context for authorization and privilege control. 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 Access Data Redaction when a role gained new permissions, so the team could share evidence without leaking secrets before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Latency Egress Policy": Latency Egress Policy is a networking outbound control that decides where workloads may send traffic for time between request and response. It uses allowlists, identity, and logging so teams can reduce exfiltration and SSRF risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used Latency Egress Policy when a user saw slow responses, so the team could reduce exfiltration and SSRF risk before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Subnet Packet Capture": Subnet Packet Capture is a networking diagnostic artifact that records network packets for analysis for address segmentation. 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 Subnet Packet Capture when a workload moved networks, so the team could investigate protocol behavior safely before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Service Mesh Health Probe": Service Mesh Health Probe is a networking availability check that tests whether a service or path can receive traffic for east-west service communication. 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 Service Mesh Health Probe when a service called another service, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Access Detection Rule": Access Detection Rule is a security security analytic that matches suspicious behavior or known indicators for authorization and privilege control. 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 Access Detection Rule when a role gained new permissions, so the team could surface actionable alerts before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Identity Detection Rule": Identity Detection Rule is a security security analytic that matches suspicious behavior or known indicators for user and workload identity. 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 Identity Detection Rule when a service account requested access, so the team could surface actionable alerts before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Endpoint Containment Plan": Endpoint Containment Plan is a security response plan that limits damage after a suspected compromise for user device and server protection. 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 Endpoint Containment Plan when a workstation reported suspicious activity, so the team could reduce attacker dwell time before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Threat Intel Abuse Throttle": Threat Intel Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for external risk and indicator context. 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 Threat Intel Abuse Throttle when a new campaign indicator appeared, so the team could protect public access without a login wall before the risk review began.”