Popular
Popular public definitions for this language. If a reviewed translation is missing, Dictionary shows a labeled machine-assisted draft.
Popular public definitions for this language. If a reviewed translation is missing, Dictionary shows a labeled machine-assisted draft.
Automatischer Uebersetzungsentwurf (German) for "Zero Trust Phishing Resistance": Zero Trust Phishing Resistance is a security identity control that reduces success of credential theft attacks for continuous verification model. 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.
“Beispielentwurf: The security team used Zero Trust Phishing Resistance when a device changed posture, so the team could protect sign-in flows before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Zero Trust Secret Scanner": Zero Trust Secret Scanner is a security preventive control that finds credentials before they spread for continuous verification model. 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.
“Beispielentwurf: The security team used Zero Trust Secret Scanner when a device changed posture, so the team could stop accidental key exposure before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Inference Citation Builder": Inference Citation Builder is a ai attribution helper that formats source links and evidence for an AI answer for model execution for user or system requests. It uses canonical URLs, source titles, and quote limits so teams can make generated answers citeable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Inference Citation Builder when the inference route moved to a faster region, so the team could make generated answers citeable before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Endpoint Trust Boundary": Endpoint Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for user device and server protection. 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.
“Beispielentwurf: The security team used Endpoint Trust Boundary when a workstation reported suspicious activity, so the team could avoid accidental privilege crossing before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "CD Config Drift Check": CD Config Drift Check is a devops consistency check that finds differences between intended and live configuration for deployment automation and promotion. It uses desired state, live state, and diff reports so teams can avoid surprise environment behavior while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used CD Config Drift Check when the release moved toward production, so the team could avoid surprise environment behavior before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Metric Label Review": Metric Label Review is a ml quality workflow that checks annotations for consistency and usefulness for measurement of model behavior. It uses agreement metrics, reviewer queues, and adjudication so teams can improve supervised learning data while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Metric Label Review when the metric changed after data cleanup, so the team could improve supervised learning data before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Memory Response Schema": Memory Response Schema is a ai output contract that requires model output to match a known structure for persistent or session-level AI state. It uses JSON schemas, validators, retries, and error reporting so teams can make responses machine-readable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Memory Response Schema when the assistant reused earlier project context, so the team could make responses machine-readable before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Serverless Checkpoint Restore": Serverless Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for event-driven function execution. It uses snapshots, state files, and integrity checks so teams can recover long-running work while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Serverless Checkpoint Restore when the function received a traffic burst, so the team could recover long-running work before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Routing Tool Permission": Routing Tool Permission is a ai access control that decides which tools an AI workflow may call for selection among models, tools, and workflows. It uses operation allowlists, user intent checks, and protected-action gates so teams can block unsafe automation while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Routing Tool Permission when the router selected a cheaper model, so the team could block unsafe automation before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Queue Placement Strategy": Queue Placement Strategy is a compute scheduling rule that chooses where workloads should run for asynchronous work buffer. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The platform engineering team used Queue Placement Strategy when the queue depth increased, so the team could improve reliability and efficiency before the workload scaled up.”
Automatischer Uebersetzungsentwurf (German) for "Metric Calibration Curve": Metric Calibration Curve is a ml diagnostic that compares predicted confidence with observed outcomes for measurement of model behavior. It uses bucketed predictions, reliability diagrams, and threshold analysis so teams can make confidence scores useful while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Metric Calibration Curve when the metric changed after data cleanup, so the team could make confidence scores useful before the model moved into evaluation.”
Automatischer Uebersetzungsentwurf (German) for "Endpoint Evidence Chain": Endpoint Evidence Chain is a security audit record that preserves how security evidence was collected and handled for user device and server protection. It uses timestamps, hashes, owners, and storage controls so teams can support trustworthy investigation while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Endpoint Evidence Chain when a workstation reported suspicious activity, so the team could support trustworthy investigation before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Infrastructure Release Manifest": Infrastructure Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for cloud resources and platform wiring. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Infrastructure Release Manifest when a new region was added, so the team could make releases auditable before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Zero Trust Trust Boundary": Zero Trust Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for continuous verification model. 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.
“Beispielentwurf: The security team used Zero Trust Trust Boundary when a device changed posture, so the team could avoid accidental privilege crossing before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Guardrail Agent Trace": Guardrail Agent Trace is a ai observability record that captures the steps an AI workflow took for policy controls around model input and output. It uses trace identifiers, tool events, and redacted metadata so teams can debug agent behavior without exposing secrets while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The AI platform team used Guardrail Agent Trace when the model tried to include private context, so the team could debug agent behavior without exposing secrets before the agent workflow reached production.”
Automatischer Uebersetzungsentwurf (German) for "Orbital Debris Avoidance": Orbital Debris Avoidance is a space safety workflow that reduces collision risk with tracked objects and mission-generated debris for spacecraft orbit planning and station keeping. It uses conjunction screening, maneuver planning, and operator signoff so teams can avoid unsafe passes without overusing fuel while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The mission team used Orbital Debris Avoidance when a spacecraft entered a crowded orbital shell, so the team could avoid unsafe passes without overusing fuel before the next mission decision point.”
Automatischer Uebersetzungsentwurf (German) for "Observability Runbook Check": Observability Runbook Check is a devops operational test that confirms that documented procedures still work for logs, metrics, traces, and events. It uses dry runs, screenshots, and command validation so teams can keep response playbooks current while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The DevOps team used Observability Runbook Check when latency increased after deploy, so the team could keep response playbooks current before the deployment window opened.”
Automatischer Uebersetzungsentwurf (German) for "Threat Intel Trust Boundary": Threat Intel Trust Boundary is a security security boundary that defines where assumptions, identities, or permissions change for external risk and indicator context. 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.
“Beispielentwurf: The security team used Threat Intel Trust Boundary when a new campaign indicator appeared, so the team could avoid accidental privilege crossing before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Zero Trust Policy Decision": Zero Trust Policy Decision is a security authorization decision that determines whether an action should be allowed for continuous verification model. It uses identity, resource, context, and policy evaluation so teams can enforce least privilege while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The security team used Zero Trust Policy Decision when a device changed posture, so the team could enforce least privilege before the risk review began.”
Automatischer Uebersetzungsentwurf (German) for "Feature Bias Audit": Feature Bias Audit is a ml review process that looks for uneven model behavior across groups or segments for input signals used by a machine learning model. It uses slice metrics, representative data, and reviewer notes so teams can surface fairness risks while keeping evidence, reliability, and public-safe operational boundaries clear.
“Beispielentwurf: The machine learning team used Feature Bias Audit when a feature distribution shifted, so the team could surface fairness risks before the model moved into evaluation.”