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 "Secrets Containment Plan": Secrets Containment Plan is a security response plan that limits damage after a suspected compromise for keys, tokens, and credentials. 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 Secrets Containment Plan when a secret appeared in logs, so the team could reduce attacker dwell time before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Supply Chain Detection Rule": Supply Chain Detection Rule is a security security analytic that matches suspicious behavior or known indicators for dependencies, builds, and artifacts. 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 Supply Chain Detection Rule when a package update arrived, so the team could surface actionable alerts before the risk review began.”
機械支援の翻訳下書き (Japanese) for "HTTP Failover Policy": HTTP Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for application-layer request routing. 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 HTTP Failover Policy when a client retried a request, so the team could recover from outages predictably before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Secrets Detection Rule": Secrets Detection Rule is a security security analytic that matches suspicious behavior or known indicators for keys, tokens, and credentials. 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 Secrets Detection Rule when a secret appeared in logs, so the team could surface actionable alerts before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Incident Response Trust Boundary": Incident Response Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for security event handling. 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 Incident Response Trust Boundary when an alert escalated to response, so the team could avoid accidental privilege crossing 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 "Incident Response Forensic Snapshot": Incident Response Forensic Snapshot is a security investigation artifact that captures system state for later review for security event handling. It uses logs, configuration, hashes, and time-bounded data so teams can analyze incidents without changing evidence while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The security team used Incident Response Forensic Snapshot when an alert escalated to response, so the team could analyze incidents without changing evidence before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Identity Secret Scanner": Identity Secret Scanner is a security preventive control that finds credentials before they spread for user and workload identity. 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 Identity Secret Scanner when a service account requested access, so the team could stop accidental key exposure before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Incident Response Abuse Throttle": Incident Response Abuse Throttle is a security anti-abuse control that slows or blocks suspicious repeated behavior for security event handling. 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 Incident Response Abuse Throttle when an alert escalated to response, so the team could protect public access without a login wall before the risk review began.”
機械支援の翻訳下書き (Japanese) for "Zero Trust Data Redaction": Zero Trust Data Redaction is a security privacy control that removes sensitive values before data leaves a protected context for continuous verification model. 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 Zero Trust Data Redaction when a device changed posture, so the team could share evidence without leaking secrets before the risk review began.”