Why 13% of Your Sentinel Rules Never Fire
CardinalOps found 13% of SIEM rules never fire. Check thousands of Sentinel detections against Microsoft's own KQL parser — deterministically, not an LLM.
What AI costs, when it holds up, where it fails — and how the technology underneath actually works. These articles come out of real project work. Each one is published in English and German.
CardinalOps found 13% of SIEM rules never fire. Check thousands of Sentinel detections against Microsoft's own KQL parser — deterministically, not an LLM.
How we built KomplAI, a verifiable compliance AI: every legal citation an LLM makes is machine-verified against EUR-Lex before it reaches the report.
NIS2 gives you 24 hours to file an early warning — the hard part is detecting the incident that fast. What Article 23 requires, and how to build for it.
With LLMs, generating a detection query is the easy 20%; the hard 80% is trust. What works is a generate-validate-refine loop that only ships proven queries.
Million-token context windows did not kill RAG. The deciding question is not corpus size — it is whether your prompt prefix is identical for every query.
Function calling doesn't let a model run your code — it returns a request your code decides to run. How tool use works, and how to design tools an LLM can use.
Most AI tasks need one good agent, not a multi-agent system. When splitting into several agents genuinely helps — and when it just multiplies failure modes.
Being in Annex III does not make your AI high-risk. The Article 6(3) filter can rule it out — but profiling blocks it, and the exemption must be registered.
An AI system cannot pass a binary Abnahme. Owe a threshold on a frozen, hashed test set under a fixed protocol — not an output. How to write the Werkvertrag clause.
Most AI ROI numbers are fiction. How to measure the ROI of an AI project honestly: set the baseline before you build, name the account, and count the review.
Article 12 names no fields for an LLM. A log proves which corpus, model and prompt produced a RAG answer only if it pins the index snapshot. Full JSON schema.
Usually not. A vector database delete() writes a tombstone and the embedding stays on disk until compaction runs. What GDPR Art. 17 deletion really takes.
Most AI projects do not fail on technology. They fail on decisions made in the first week — scope, ownership, exceptions — then look like progress for months.
Almost any AI tool your staff use triggers co-determination under § 87 BetrVG, whatever you intended. What a works council agreement has to cover.
AI for predictive maintenance should start as condition monitoring: real prediction needs dozens of labelled failures, and most plants do not have them.
What it really takes to get your data ready for AI: where company data hides, how to inventory, clean, structure and permission it, and why good enough wins.
Securing LLM applications: prompt injection, data leakage, insecure output handling and over-privileged agents, plus the playbook to build systems you trust.
On-premise vs. cloud AI: what self-hosted LLMs really involve, the GDPR and data-sovereignty drivers, the honest trade-offs, and when each is right for you.
How to choose the right LLM for a real project: open-source vs. proprietary, cost, latency, data privacy and lock-in. Why the top benchmark is the wrong test.
When an off-the-shelf AI tool is enough and when a custom build pays off: the hidden costs of each, plus a clear build-vs-buy framework for mid-sized firms.
AI in customer service works when the model drafts and a human sends. Ground answers in your real docs, escalate on rules, and measure deflection honestly.
How to build AI on personal data without breaking GDPR: the duties that apply, where projects go wrong, and how to make compliance part of the architecture.
Concrete AI use cases for mid-sized companies in four buckets: reading documents, answering questions, automating steps, and forecasting. Where to start.
How to run an AI pilot that actually leads somewhere: how to scope it, what to measure, how to timebox it, and how to avoid the pilot that never ends.
The hardware behind on-premise LLMs: model size, why GPU memory is the real constraint, quantization, example builds, and when on-premise beats cloud.
AI for document processing pays off when the system knows which fields to trust: OCR sets the ceiling, and cross-checks beat what the model claims.
What an AI project actually costs: the real cost drivers, what you can build at each budget, the hidden running costs, and how to de-risk before you commit.
Uptime and latency stay green while an LLM system quietly gets worse. What to monitor instead, how model drift really shows up, and what maintenance costs.
The EU AI Act for mid-sized companies: the risk categories, what actually applies to you, the timeline, how it relates to GDPR, and the steps to compliance.
Evaluating LLM systems needs a golden set of real cases with known-good answers, metrics that fit the task, and regression tests — not a vibe check.
LLM hallucinations happen because a model predicts plausible text and never looks anything up. Here is what that means in practice and what actually helps.
Structure-aware chunking beats fixed size and semantic splitting for RAG. How to keep tables and headings intact, use overlap, and test on your own documents.
For most projects, Postgres with pgvector is vector database enough. Here is what a vector database actually does, and when you really need a dedicated one.
An embedding turns text into coordinates: text about the same thing lands nearby. How that powers retrieval and classification, and the traps that break it.
Deploying AI in enterprise starts with process, data, control, and rollout. Learn how to choose the right use case, govern risk, and move AI into production.
When LLM fine-tuning creates real leverage and when prompting or RAG is enough: data quality, LoRA and QLoRA, evaluation, and shipping it to production.
RAG pipelines retrieve, rank, ground, and answer. Learn how production RAG systems work, where they fail, and how to design them for reliable enterprise use.
AI agents perceive, decide, and act — repeatedly and autonomously. How they work, what separates them from chatbots, and when it is worth building one.