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 "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 Patch Window": Supply Chain Patch Window is a security remediation schedule that sets when a fix should be applied for dependencies, builds, and artifacts. 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 Supply Chain Patch Window when a package update arrived, so the team could repair systems without unnecessary disruption before the risk review began.”
機械支援の翻訳下書き (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 "Zero Trust Forensic Snapshot": Zero Trust Forensic Snapshot is a security investigation artifact that captures system state for later review for continuous verification model. 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 Zero Trust Forensic Snapshot when a device changed posture, so the team could analyze incidents without changing evidence 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 "Firewall Failover Policy": Firewall Failover Policy is a networking resilience policy that defines when traffic should move to another path or region for network traffic filtering. 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 Firewall Failover Policy when a new rule matched traffic, so the team could recover from outages predictably before traffic crossed a service boundary.”
機械支援の翻訳下書き (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 "TLS Rate Limit": TLS Rate Limit is a networking traffic control that caps request volume over a period for encrypted transport setup. 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 TLS Rate Limit when a certificate neared expiration, so the team could protect services from overload before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Vulnerability Evidence Chain": Vulnerability Evidence Chain is a security audit record that preserves how security evidence was collected and handled for weakness tracking and remediation. It uses timestamps, hashes, owners, and storage controls so teams can support trustworthy investigation while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The security team used Vulnerability Evidence Chain when a scanner found a critical issue, so the team could support trustworthy investigation before the risk review began.”
機械支援の翻訳下書き (Japanese) for "CDN Health Probe": CDN Health Probe is a networking availability check that tests whether a service or path can receive traffic for content delivery and edge caching. 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 CDN Health Probe when a cache region served an asset, so the team could send traffic only to healthy targets before traffic crossed a service boundary.”