Easylab AI×  OpenClaw

Security by Design11 Independent Layers

Each layer protects independently. If one fails, the others continue.

Our philosophy

We don't claim the system is infallible. We assume it will be tested, pushed to its limits, and that one day a layer will break. That's why there are eleven.

Every incident is documented publicly. Every flaw discovered strengthens the system. Transparency is not a risk — it's our best protection.

The 11 Protection Layers

Click on a layer to see the details

01

Control Hierarchy

Three distinct authority levels. Each level has explicit and non-extensible permissions.

02

Locked Configuration

Security parameters are protected by an immutable system flag. The agent cannot modify its own rules.

03

PIN Code for Sensitive Actions

Any high-impact action requires human PIN validation.

04

External Content Isolation

External content is treated as pure data, never as executable instructions.

05

3-Layer Email Pipeline

Reading via fixed script, analysis in sandbox, processing on allowlist only.

06

One-Shot Messaging Architecture

Each message creates an isolated session that terminates after processing.

07

Independent Monitoring

The monitoring system alerts the operator directly without going through the agent.

08

Loopback-Only Network Gateway

The gateway only responds to local connections. No external access possible.

09

Secure Boot Order

Security configuration is loaded before any other module.

10

Messaging Pairing

Every new contact must be manually approved before interaction.

11

Contact Allowlist

Only listed contacts trigger actions. Any other source is ignored.

Documented Incidents

Full transparency on what happened and how we responded.

01

PIN leaked via messaging

Cause

The security PIN was exposed in a message processed by a sub-agent. The old code was compromised through reasoning visible in session logs.

Resolution

PIN changed immediately. Client messaging architecture redesigned: dedicated monitoring daemon, isolated one-shot sub-agents. PIN no longer transits through messaging sessions.

02

Corrupted default agent

Cause

A secondary agent became the default agent instead of the main agent. For 3 days, all commands were routed to an agent without the right permissions.

Resolution

Default agent restored. Added a healthcheck that verifies default agent configuration at startup. Consistency alerts added.

03

Internal reasoning leak

Cause

The agent's internal reasoning (chain of thought) was included in a response, exposing implementation details.

Resolution

Output filter added to strip reasoning blocks before sending. Response format validation made mandatory.

What the System Does Not Do

Transparency on current limitations.

  • Does not make autonomous financial decisions
  • Does not contact persons not on the allowlist
  • Does not modify its own security rules
  • Does not retain sensitive data between sessions
  • Does not self-replicate or deploy new agents without approval
OpenClaw × Easylab — L'IA autonome au coeur de nos operations