Writing
Articles
Beyond the Source Code
Beyond the source code: the hidden licensing crisis in open AI
Open-weight AI models are served through cloud intermediaries that preserve legal obligations in theory but eliminate licensing visibility in practice.
26 min · EU · UK · USIs my subsidiary in scope of NIS2?
Is a small MSP subsidiary in scope of NIS2? This article explains why the answer depends on group-size calculation, linked enterprises, Recital 16 and national transposition.
Supply chain email fraud: how NIS2, DORA and the GDPR reshape civil liability
Supply chain email fraud: how NIS2, DORA and the GDPR reshape civil liability Introduction Business email compromise, commonly referred to as BEC, is a form of cyber-enabled fraud in which an …
Supply chain email fraud: which party pays when the supplier gets hacked?
Supply chain email fraud: civil liability in the EU, US and Canada
The EU AI Act’s operator model: what every company needs to know before deploying AI
When does a company stop being a “user” of AI, and becomes its legal provider? Under the EU AI Act, the answer depends entirely on what you do with a system, not who built it. In my latest analysis, I break down the EU AI Act’s operator model — and why organisations may acquire provider status far more easily than they expect. From rebranding and substantial modification to fine-tuning and internal deployment, the Act assigns responsibility based on factual conduct, not contractual labels or technical authorship. If your company integrates, adapts, or modifies AI systems — especially in high-risk environments — these mechanisms determine your compliance burden.
No articles in this category yet.
Stay in the conversation.
New analysis delivered directly. No noise.