Zum Hauptinhalt springen
tsecurity.de LIVE
Echtzeit-Radar & Feeds
Alle RSS Feeds
👥 Community & Social
IT Security NachrichtenOne URL, Three Different Tricks, (Thu, Sep 24th)(24.09.2026 um 08:25 Uhr)
IT Security NachrichtenGartner: 41 Prozent der CISOs melden Deepfakes(24.09.2026 um 08:04 Uhr)
AI & KI NachrichtenJobstart: Rund die Hälfte erwartet KI-Kenntnisse(24.09.2026 um 08:05 Uhr)
AI & KI NachrichtenIT-Dienstleister im Vergleich 2026 - CHIP(24.09.2026 um 01:15 Uhr)
IT Security NachrichtenGefahren durch Berlins exfiltrierte Verwaltungsdaten - IT&Production(24.09.2026 um 02:51 Uhr)
IT Security NachrichtenWeb, Cloud und Security zusammen denken - Swiss IT Magazine(24.09.2026 um 06:56 Uhr)
IT Security NachrichtenAnzeige KI in der IT-Sicherheit für Pentesting und Resilienz - Golem.de(24.09.2026 um 07:20 Uhr)
IT Security NachrichtenOne URL, Three Different Tricks, (Thu, Sep 24th)(24.09.2026 um 08:25 Uhr)
IT Security NachrichtenGartner: 41 Prozent der CISOs melden Deepfakes(24.09.2026 um 08:04 Uhr)
AI & KI NachrichtenJobstart: Rund die Hälfte erwartet KI-Kenntnisse(24.09.2026 um 08:05 Uhr)
AI & KI NachrichtenIT-Dienstleister im Vergleich 2026 - CHIP(24.09.2026 um 01:15 Uhr)
IT Security NachrichtenGefahren durch Berlins exfiltrierte Verwaltungsdaten - IT&Production(24.09.2026 um 02:51 Uhr)
IT Security NachrichtenWeb, Cloud und Security zusammen denken - Swiss IT Magazine(24.09.2026 um 06:56 Uhr)
IT Security NachrichtenAnzeige KI in der IT-Sicherheit für Pentesting und Resilienz - Golem.de(24.09.2026 um 07:20 Uhr)
Intelligence View
⚡ tsecurity.de Intelligence

LLMs Are Not Deterministic. And Making Them Reliable Is Expensive (In Both the Bad Way and the Good Way)

Let’s start with a statement that should be obvious but still feels controversial: Large Language Models are not deterministic systems. They are probabilistic sequence predictors. Given a context, they sample the next token from a p…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

Let’s start with a statement that should be obvious but still feels controversial: Large Language Models are not deterministic systems. They are probabilistic sequence predictors. Given a context, they sample the next token from a probability distribution. That is their nature. There is no hidden reasoning engine, no symbolic truth layer, no internal notion of correctness.




You can influence their behavior. You can constrain it. You can shape it. But you cannot turn probability into certainty.




Somewhere between keynote stages, funding decks, and product demos, a comforting narrative emerged: models are getting cheaper and smarter, therefore AI will soon become trivial. The logic sounds reasonable. Token prices are dropping. Model quality is improving. Demos look impressive. From the outside, it feels like we are approaching a phase where AI becomes a solved commodity.



From the inside, it feels very different.



There is a massive gap between a good demo and a reliable product. A demo is usually a single prompt and a single model call. It looks magical. It sells. A product cannot live there. The moment you try to ship that architecture to real users, reality shows up fast. The model hallucinates. It partially answers. It ignores constraints. It produces something that sounds fluent but is subtly wrong. And the model has no idea it failed.



This is not a moral flaw. It is a design property.



So engineers do what engineers always do when a component is powerful but unreliable. They build structure around it.



The moment you care about reliability, your architecture stops being “call an LLM” and starts becoming a pipeline. Input is cleaned and normalized. A generation step produces a candidate answer. Another step evaluates that answer. A routing layer decides whether the answer is acceptable or if the system should try again. Sometimes it retries with a modified prompt. Sometimes with a different model. Sometimes with a corrective pass. Only after this loop does something reach the user.



At no point did the LLM become deterministic. What changed is that the system gained control loops.



This distinction matters. We are not converting probability into certainty. We are reducing uncertainty through redundancy and validation. That reduction costs computation. Computation costs money.



This is why quoting token prices in isolation is misleading. A single model call might be cheap. A serious system rarely uses a single call. One user request can trigger several model invocations: generation, evaluation, regeneration, formatting, tool calls, memory lookups. The user experiences “one answer.” The backend executes a small workflow.



Token cost is component cost. Reliable AI is system cost.



Saying “tokens are cheap, therefore AI is cheap” is like saying screws are cheap, therefore airplanes are cheap.



This leads to an uncomfortable but important truth. AI becomes expensive in two very different ways.



If you implement it poorly, it becomes expensive because you burn money and still do not get reliability. You keep tweaking prompts. You keep firefighting. You keep patching symptoms. Nothing stabilizes.



If you implement it well, it becomes expensive because you intentionally pay for control. You pay for evaluators. You pay for retries. You pay for observability. You pay for redundancy. But you get something in return: a system that behaves in a bounded, inspectable, and improvable way.



There is no cheap version of “reliable.”



Another source of confusion comes from mixing up different kinds of expertise. High-profile founders and executives are excellent at describing futures. They talk about where markets are going and what will be possible. That is their role. It is not their role to debug why an evaluator prompt leaks instructions or why a routing threshold oscillates under load. Money success does not imply operational intimacy.



On the ground, building serious AI feels much closer to distributed systems engineering than to science fiction. You worry about data quality. You worry about regressions. You worry about latency and cost per request. You design schemas. You version prompts. You inspect traces. You run benchmarks. You tune thresholds. It is slow, unglamorous, and deeply technical.



LLMs made AI more accessible. They did not make serious AI simpler. They shifted complexity upward into systems.



So when someone says, “Soon we’ll just call an API and everything will work,” what they usually mean is, “Soon an enormous amount of engineering will be hidden behind that API.”



That is fine. That is progress.



But pretending that reliable AI is cheap, trivial, or solved is misleading.



The honest version is this: LLMs are powerful probabilistic components. Turning them into dependable products requires layers of control. Those layers cost money. They also create real value.



Serious AI today is expensive in the bad way if you do not know what you are doing.



Serious AI today is expensive in the good way if you actually want it to work.



And anyone selling “cheap deterministic AI” is selling a story, not a system.

SOC Incident Playbook: Remote Code Execution (RCE) Defense
title: Detect Exploitation - LLMs Are Not Deterministic. And Making Them Reliable Is Expensive (In Both the Bad Way and the Good Way)
id: 319d0adc-03d2-42d1-a449-391c1dba6691
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-24
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-24"
        description = "YARA Signature for "
    strings:
        $str = "LLMs Are Not Deterministic. An" ascii wide
    condition:
        any of them
}
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich LLMs Are Not Deterministic. And Making T.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten LLMs Are Not Deterministic. And Making Them Reliable Is Expensive (In Both the Bad Way and the Good Way)

Thematisch verwandte Begriffe: LLMs, Deterministic, Making, Them · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-96676 | A vulnerability was identified in Fast FAC1900R 20190827_2.0.2. The impa…
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel Rechts: nächster Artikel unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel TTP ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

Zurück: vorheriger Vor: nächster
↗ Original-Quelle
Social Reaktionen Deine Reaktion zählt
Einstufung & Relevanz-Poll 0 Stimmen
In sozialen Netzwerken teilen 1-Klick