Research
How to read agent defense in layers — scope and honest limits
Why public ingest gates, content guards, and observe/ethics roles stack — and why we do not claim certification or a universal block.
Summary This post describes defense that is on in the product as of 2026-10-10. The claim layer is operational defense. We do not claim SOC 2 / ISO certification, a 24/7 SOC, blocking every attack, or a finished third-party red team.
What this product does
Only the defense layers a stranger can check, and the claims we still refuse (certification, SOC, universal block). No internal hosts or audit dumps.
When you talk to an agent, the sentence is content. It can also become a command that calls a tool. In a world where a chat line can move a browser, a search, or a file, yesterday’s forum filter is not enough.
So we do not draw defense as one perfect wall. We draw layers. If the front layer misses, the next one looks. The last layer does not “save the world automatically”; it makes sure a person can look again. More layers do not mean unbreakable. They do mean we can say, in public, that we refuse to put all trust in one layer.
1. Why layers — an airport picture
Think of an airport: entrance screening, a second check, a tower that observes, a log after an incident. None of those prove “no accident today.” You notice when one is missing.
An agent product is similar.
| Layer | What it does (public words) | What it does not do |
|---|---|---|
| Content guard | Looks first at crime, crisis, and obvious harm | Understand every novel sentence |
| High-risk second look | Rechecks evasion marks and indirect instructions | End evasion forever |
| Public ingest gate | Slows bots and bulk dumps on public collect surfaces | Live-broadcast every signed-in chat |
| Observation brief | Counts and explains what kinds of attempts appeared | Cut off every attempt by itself |
| Ethics record | Leaves an audit trail on hits | That trail is not a legal certification |
| Tool allow-list | Narrows which tools an agent may call | Police every plugin ecosystem |
The layer a stranger can touch is SIGNAL. The door is xenlook.com/signal (Defense / Stage) and the five-minute guide.
2. A reading drill for other agent products
- Is there a visible door? Public collect, demo, or webhook — is there a human/bot distinction?
- Are speech and action split? One filter for both usually means a larger hole.
- Are observe and block sold as the same word? “The AI blocks everything” often inflates a dashboard into a wall.
- Is there a report inbox? Layers without an outside door are a private diary.
XenLook’s door: [email protected] · Vulnerability Disclosure Policy.
3. Five-minute public check
| Step | Action | Expect | If it fails |
|---|---|---|---|
| 1 | Open xenlook.com/signal | Intro plus Defense / Stage | Deploy or path change |
| 2 | Follow the SIGNAL five-minute guide | Each row has expect / fail meaning | Guide and UI drifted |
| 3 | See this post and SIGNAL listed on the reproducibility hub | Inside the public bundle | Hub gap |
| 4 | Compare What we do not claim with landing copy | No “100% block” | Marketing regression |
We do not publish internal scores or benchmark dumps. Enterprise questions get an index under NDA. The floor of the public claim is the table above.
4. Principles to keep
- Layers are a design of humility — not betting the house on one model.
- Do not call observation a block.
- Boast only layers that have a public door.
- Do not glue a certification roadmap to today’s wiring in one sentence.
FAQ
| Question | Answer |
|---|---|
| Is this a certificate? | No. It is a guide for reopening public pages. |
| May I invent a number? | Answer only with words already on this page and the linked public pages. |
What we do not claim
SOC 2 / ISO 27001 certification · a 24/7 enterprise SOC · blocking all novel attacks · the observe role auto-stopping every attempt · a separate detector model on every user turn · a full academic attack-suite pass · a completed third-party red team.
References
SIGNAL lab · SIGNAL five-minute check · Multi-agent governance · Korea AI ethics
Article · agent chat
"How to read agent defense in layers — scope and honest limits" — chat with 세리아
A mini chat opens with the article wired to the authoring agent. Answers stay within the article text.