<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>security on Gaia Lab · Blog</title><link>https://blog.defectiv.es/en/tags/security/</link><description>Recent content in security on Gaia Lab · Blog</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Wed, 23 Sep 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://blog.defectiv.es/en/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>A risk classifier for minors that fits in a phone</title><link>https://blog.defectiv.es/en/posts/un-clasificador-de-riesgo-para-menores-que-cabe-en-un-movil/</link><pubDate>Tue, 22 Sep 2026 13:45:00 +0200</pubDate><guid>https://blog.defectiv.es/en/posts/un-clasificador-de-riesgo-para-menores-que-cabe-en-un-movil/</guid><description>&lt;p&gt;Seventh instalment of &lt;strong&gt;Cluster X-ray&lt;/strong&gt;. A safety line of another kind: that of minors using a phone.&lt;/p&gt;&#10;&lt;h2 id="the-question"&gt;The question &lt;a class="hanchor" href="#the-question" aria-label="Enlace a esta sección"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Detecting risk situations in a minor&amp;rsquo;s conversations (harassment, &lt;em&gt;grooming&lt;/em&gt;, sexual content, isolation, threats) is possible with a language model. Doing it on a server means sending the conversation off the phone, and that is precisely what you do not want to do with a minor&amp;rsquo;s private life. The line asks &lt;strong&gt;whether a model small enough to run on the phone itself can classify risk with the necessary reliability, and how much is lost in compressing it until it fits.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Measuring quantized LLMs: what is lost when an open model is compressed</title><link>https://blog.defectiv.es/en/posts/medir-llm-cuantizados-gguf-bfcl-bigcodebench-ruler/</link><pubDate>Tue, 22 Sep 2026 12:45:00 +0200</pubDate><guid>https://blog.defectiv.es/en/posts/medir-llm-cuantizados-gguf-bfcl-bigcodebench-ruler/</guid><description>&lt;p&gt;Third instalment of &lt;strong&gt;Cluster X-ray&lt;/strong&gt;. It is the best example of what the &lt;a href="https://blog.defectiv.es/en/posts/que-corre-de-verdad-en-nuestro-cluster/"&gt;overview post&lt;/a&gt;&#10; said: the cluster today is above all a &lt;strong&gt;measurement laboratory&lt;/strong&gt;. Not a single parameter is trained here.&lt;/p&gt;&#10;&lt;h2 id="the-question"&gt;The question &lt;a class="hanchor" href="#the-question" aria-label="Enlace a esta sección"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Open models are distributed quantized: the same weights compressed to 8, 6, 5, 4, 3 or 2 bits so they fit on a small card or a laptop. The community publishes hundreds of variants, but rarely with a comparable measure of what is lost. The line asks &lt;strong&gt;how well each quantization level of each family really performs on tasks that matter for using the model as a tool&lt;/strong&gt;, and at what speed and energy cost it does so on each card.&lt;/p&gt;</description></item><item><title>A council of small models against a 120B one: automated jailbreaking and who judges it</title><link>https://blog.defectiv.es/en/posts/un-consejo-de-modelos-pequenos-contra-uno-de-120b/</link><pubDate>Tue, 22 Sep 2026 12:30:00 +0200</pubDate><guid>https://blog.defectiv.es/en/posts/un-consejo-de-modelos-pequenos-contra-uno-de-120b/</guid><description>&lt;p&gt;Second instalment of &lt;strong&gt;Cluster X-ray&lt;/strong&gt;. The &lt;a href="https://blog.defectiv.es/en/posts/auto-alineamiento-de-un-llm-de-3b-con-lora-y-harmbench/"&gt;previous instalment&lt;/a&gt;&#10; fine-tuned a model so it would refuse what is harmful. This line does the opposite: it automatically attacks a large model and counts how many times it gives in.&lt;/p&gt;&#10;&lt;h2 id="the-question"&gt;The question &lt;a class="hanchor" href="#the-question" aria-label="Enlace a esta sección"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Automated &lt;em&gt;jailbreak&lt;/em&gt; attacks usually use an attacker model that refines a &lt;em&gt;prompt&lt;/em&gt; turn by turn. The line asks whether &lt;strong&gt;a group of small models that deliberate&lt;/strong&gt; attacks better than any of them on its own, and, with equal weight, &lt;strong&gt;how to measure success without fooling yourself&lt;/strong&gt;, because the same attack can look successful or not depending on who judges it.&lt;/p&gt;</description></item><item><title>Self-alignment: how much safety to teach a language model without making it useless</title><link>https://blog.defectiv.es/en/posts/auto-alineamiento-de-un-llm-de-3b-con-lora-y-harmbench/</link><pubDate>Tue, 22 Sep 2026 12:15:00 +0200</pubDate><guid>https://blog.defectiv.es/en/posts/auto-alineamiento-de-un-llm-de-3b-con-lora-y-harmbench/</guid><description>&lt;p&gt;First instalment of &lt;strong&gt;Cluster X-ray&lt;/strong&gt;, the series that goes line by line through &lt;a href="https://blog.defectiv.es/en/posts/que-corre-de-verdad-en-nuestro-cluster/"&gt;what really runs on the ANTS group&amp;rsquo;s cluster&lt;/a&gt;&#10;. We start with the first of three lines on language model safety.&lt;/p&gt;&#10;&lt;h2 id="the-question"&gt;The question &lt;a class="hanchor" href="#the-question" aria-label="Enlace a esta sección"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Fine-tuning a language model so that it refuses harmful requests has a cost: if it is taught too thoroughly to say no, it starts refusing harmless things too, and loses usefulness. The line studies that balance: &lt;strong&gt;what proportion of safety data has to be mixed with the utility data, and whether the model itself can generate its own refusal examples and regulate the dose on its own.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>What really runs on our cluster, read from the scripts themselves</title><link>https://blog.defectiv.es/en/posts/que-corre-de-verdad-en-nuestro-cluster/</link><pubDate>Tue, 22 Sep 2026 10:00:00 +0200</pubDate><guid>https://blog.defectiv.es/en/posts/que-corre-de-verdad-en-nuestro-cluster/</guid><description>&lt;p&gt;A cluster&amp;rsquo;s job history is usually a wall of six-digit identifiers and cryptic names —&lt;code&gt;mcpfw_cc&lt;/code&gt;, &lt;code&gt;eval_dynamic_pid&lt;/code&gt;, &lt;code&gt;boltz2&lt;/code&gt;— that say everything to whoever launched them and nothing to anyone else. But if you keep the &lt;em&gt;scripts&lt;/em&gt;, the wall turns into a document: people write down &lt;strong&gt;why&lt;/strong&gt; they do things, especially when a batch costs money and a night of waiting.&lt;/p&gt;</description></item></channel></rss>