Security and trust Useful agents,
controlled access.
What Atipol does for your data and your access, written without adjectives.
Security and trust
Your repositories stay with you
- Agents work on your machines or your runners, in your repositories.
- A delivery sends the version reference, never the file contents.
- The scope and the list of delivered files (paths and line counts) are stored encrypted per organization; file contents and diffs are never sent.
Encryption per organization
- AES-256-GCM envelope encryption: one key per project, protected by the organization's key, itself protected by a hardware master key (HSM).
- The master key is kept in Azure Key Vault Premium, France Central region.
- Key openings by the server are recorded in the audit log.
Least-privilege agents
- Permissions tool by tool: allowed, subject to a person's approval, or denied. A new tool starts out denied.
- One identity per agent: you know who did what, and you can cut off one agent without touching the others.
- Human approval is given for one specific call, once.
- A sub-agent never has more permissions than the agent delegating to it.
MCP servers under control
- A catalog of servers allowed by the organization.
- Three modes: open workspaces, catalog only, or mandatory approval; a workspace can tighten the rules, never loosen them.
- Connections shared by the organization: workspaces use them without ever seeing the key.
- Off-catalog requests are decided by an administrator, and logged.
Keys and vault
- Model provider and tool keys are kept in the vault and never shown again.
- Each key has its own scope and monthly budget, with an alert at 80%.
- Rotation and key requests from the console.
Access and traceability
- Ready-made roles (Admin, Owner, Lead, Contributor, Viewer, Auditor) and custom roles.
- Two-factor authentication can be enforced across the organization.
- Audit log exportable to CSV; ticket contents never appear in it.
- A log of every tool call, with its result.
Security questions
Does Atipol see my code?
No. Agents work in your repositories, on your machines; Atipol receives the reference of the delivered version and the changed files as measured by Git, never their contents.
Where is my data?
Project metadata is encrypted per organization. The master key that protects it sits in an Azure Key Vault Premium HSM, France Central region.
What happens if an agent wants to take a sensitive action?
If the tool is set to approval, the call waits for a person's decision. If it is denied, the call is refused and logged.
Does Atipol help with the AI Act?
Article 14 of the AI Act requires human oversight with the ability to interrupt. Atipol's approvals, reviews and log provide the record of it. Atipol does not replace your own compliance analysis.
How do I report a vulnerability?
Write to [email protected]. We acknowledge receipt and keep you informed until it is fixed.
Publisher: ETCSEC, a French security software publisher, Gif-sur-Yvette. Page updated November 9, 2026.