Browse A-Z

機械支援の翻訳下書き (Japanese) for "Ancient Polymath": A ancient polymath is a multidisciplinary figure from the ancient era in the Polymaths timeline, represented by Aristotle, Hypatia of Alexandria, Zhang Heng.

“例文の下書き: The timeline helps compare a ancient polymath with figures from other eras.”

機械支援の翻訳下書き (Japanese) for "Anki": Anki is a tool in the Polymaths resource set. Spaced-repetition flashcards for durable cross-domain retention.

“例文の下書き: Anki can support a learner building a polymathic practice in Memory.”

機械支援の翻訳下書き (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 "Application Attack Surface": Application Attack Surface is a security exposure model that lists reachable systems, actions, and trust boundaries for software security and abuse resistance. 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 Application Attack Surface when a form received unusual input, so the team could prioritize risk reduction before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Containment Plan": Application Containment Plan is a security response plan that limits damage after a suspected compromise for software security and abuse resistance. 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 Application Containment Plan when a form received unusual input, so the team could reduce attacker dwell time before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Data Redaction": Application Data Redaction is a security privacy control that removes sensitive values before data leaves a protected context for software security and abuse resistance. 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 Application Data Redaction when a form received unusual input, so the team could share evidence without leaking secrets before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Detection Rule": Application Detection Rule is a security security analytic that matches suspicious behavior or known indicators for software security and abuse resistance. 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 Application Detection Rule when a form received unusual input, so the team could surface actionable alerts before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Evidence Chain": Application Evidence Chain is a security audit record that preserves how security evidence was collected and handled for software security and abuse resistance. 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 Application Evidence Chain when a form received unusual input, so the team could support trustworthy investigation before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Forensic Snapshot": Application Forensic Snapshot is a security investigation artifact that captures system state for later review for software security and abuse resistance. 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 Application Forensic Snapshot when a form received unusual input, so the team could analyze incidents without changing evidence before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Patch Window": Application Patch Window is a security remediation schedule that sets when a fix should be applied for software security and abuse resistance. 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 Application Patch Window when a form received unusual input, so the team could repair systems without unnecessary disruption before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Phishing Resistance": Application Phishing Resistance is a security identity control that reduces success of credential theft attacks for software security and abuse resistance. 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 Application Phishing Resistance when a form received unusual input, so the team could protect sign-in flows before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Policy Decision": Application Policy Decision is a security authorization decision that determines whether an action should be allowed for software security and abuse resistance. 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 Application Policy Decision when a form received unusual input, so the team could enforce least privilege before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Secret Scanner": Application Secret Scanner is a security preventive control that finds credentials before they spread for software security and abuse resistance. 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 Application Secret Scanner when a form received unusual input, so the team could stop accidental key exposure before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Application Trust Boundary": Application Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for software security and abuse resistance. 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 Application Trust Boundary when a form received unusual input, so the team could avoid accidental privilege crossing before the risk review began.”

機械支援の翻訳下書き (Japanese) for "Approval Check": The Approval Check is a validation checkpoint used in PlatPhorm News editorial operations for approval work. It clarifies how an article, listing, source, or definition moves from discovery to publication while remaining auditable.

“例文の下書き: The editor used the Approval Check to decide whether the article listing was ready for publication.”

機械支援の翻訳下書き (Japanese) for "Approval Note": The Approval Note is a editorial annotation used in PlatPhorm News editorial operations for approval work. It clarifies how an article, listing, source, or definition moves from discovery to publication while remaining auditable.

“例文の下書き: The editor used the Approval Note to decide whether the article listing was ready for publication.”

機械支援の翻訳下書き (Japanese) for "Approval Queue": The Approval Queue is a ordered work list used in PlatPhorm News editorial operations for approval work. It clarifies how an article, listing, source, or definition moves from discovery to publication while remaining auditable.

“例文の下書き: The editor used the Approval Queue to decide whether the article listing was ready for publication.”

機械支援の翻訳下書き (Japanese) for "Approval State": The Approval State is a workflow condition used in PlatPhorm News editorial operations for approval work. It clarifies how an article, listing, source, or definition moves from discovery to publication while remaining auditable.

“例文の下書き: The editor used the Approval State to decide whether the article listing was ready for publication.”

機械支援の翻訳下書き (Japanese) for "Approval Step": The Approval Step is a process stage used in PlatPhorm News editorial operations for approval work. It clarifies how an article, listing, source, or definition moves from discovery to publication while remaining auditable.

“例文の下書き: The editor used the Approval Step to decide whether the article listing was ready for publication.”

機械支援の翻訳下書き (Japanese) for "Archive Check": The Archive Check is a validation checkpoint used in PlatPhorm News editorial operations for archive work. It clarifies how an article, listing, source, or definition moves from discovery to publication while remaining auditable.

“例文の下書き: The editor used the Archive Check to decide whether the article listing was ready for publication.”