
Security
AI and security: the invisible risk of “homemade” automations
Is your AI secure? Discover the risks of homemade automations and how Oksigenia protects your data with secure workflows, n8n and isolated Docker environments.
Published updated 3 min read

In the race for efficiency, many companies have fallen into a dangerous trap: the democratisation of access to artificial intelligence. Today, any employee with initiative can try to connect a customer database to a language model to “optimise” processes. However, what looks like a cost saving is usually, in reality, a security breach left wide open.
At Oksigenia, we don't just build workflows; we shield the integrity of your information.

The mirage of the “free tool”
Imagine a sales director who, with the best of intentions, decides to use a simple automation tool so that an AI can analyse customer complaints and draft automatic replies. To do so, they upload a CSV file with names, email addresses and purchase history to a third-party cloud platform.
Without realising it, that director has just made three critical mistakes:
- Loss of data sovereignty: That data now sits on other people's servers, feeding external AI models.
- GDPR non-compliance: Sensitive information has left the company's controlled environment without the proper encryption measures.
- Exposed API keys: Many “homemade” setups leave access keys (tokens) exposed in poorly protected scripts, allowing an attacker to take control of the linked accounts.
The case of the “silent leak”
A few months ago, a company in the home goods sector (a sector in which we also operate through our retail branch) suffered what we call a “silent leak”. They set up an AI bot to classify leads. The bot worked wonderfully, but the connection between their CRM and the AI had no secure tunnel.
A malicious actor intercepted the traffic and obtained the contact details of 5,000 potential customers before anyone noticed. There was no spectacular “hack”; they simply took advantage of a lazy architecture. The cost in fines and lost reputation far exceeded what they would have invested in a professional implementation from day one.
How we do it at Oksigenia: the digital bunker
When a client asks us for an AI automation, we don't run cables at random. Our methodology is based on segregation and total control:
- Isolated Docker environments: We deploy automation tools (such as n8n) in Docker containers within our distributed infrastructure. This means your data doesn't “fly” across the internet; it is processed in a sealed environment that we control.
- Secrets management: Credentials and APIs are never written in plain code. We use secrets management systems that rotate keys and keep them encrypted, out of reach of prying eyes.
- Sanitisation layer: Before any data reaches an AI model, our workflows go through a “cleaning” stage that ensures no unnecessary sensitive information is sent, in strict compliance with current regulations.
Don't roll the dice with your reputation
Artificial intelligence is the most powerful engine of the 21st century, but like a high-displacement engine, without the right brakes and lubrication it will end up seizing or causing an accident.
Automating is a necessity to compete, but doing it the “homemade” way is a risk your brand cannot afford. At Oksigenia, we design your business intelligence on foundations of steel.

