Security and privacy
A platform that asks for proof has to give it.
A company that sells evidence cannot run on trust. This page is what we answer in any due diligence, published before it is asked for.
01Isolation
One organisation does not see another.
Isolation is enforced in the database, through row-level security, and not only in the application. Automated tests verify it on every change. It is a rule we do not negotiate, and a breach of it is treated as a serious incident.
- Exceptions are few, named, minimal in surface and covered by tests. Login is one of them, because it happens before the person’s organisation is identified.
- Connector credentials are stored encrypted at rest, never displayed again after saving, and decrypted only at the moment of use.
- Indene team access to a client environment is individual, with a mandatory second factor, and logged in an immutable platform trail.
02What we read
Read-only, minimum scope, no writing.
By default, collection runs from the cloud with a read credential of reduced scope. In a closed environment, the customer can install a local agent that runs inside their network, keeps the credential there and only makes outbound connections to Indene. In both cases, Indene does not write to your tools.
- Connectors read inventory, copy state, CVE, event and configuration. They do not read file contents.
- Evidence is documents the customer chooses to upload. Egress connectors read volume, never the content of the traffic.
- Every reading records date, origin and expiry, and that is what becomes evidence.
03Aegis
The AI suggests; a person decides.
Every AI call goes through a single access point, is logged and has its cost measured. Requests ask the provider not to retain the content or use it to train models. Nothing Aegis produces enters the number without human acceptance.
- No model output changes a score, a number or a report on its own.
- Every suggestion accepted, edited or refused stays on the trail, with author and date.
- Turning Aegis off per organisation is a rule in the database, applied at the customer’s request.
04Trail
Every mutation stays on the record.
Scores, evidence, decisions and exports write an immutable trail with author, date and previous value. It is what allows answering supervisors with no manual collection.
- Minimum retention of five years, per CMN 5.274 and BCB 538. The customer can extend it.
- The statement of applicability comes out per framework, with the origin of every proof.
- Every AI calibration proposal is recorded with the decision of the person.
Found a flaw?
Write to the dedicated channel. We answer every good-faith disclosure and we do not take legal action against anyone who reports responsibly.
Planned certifications
- ISO/IEC 27001
- SOC 2 Type II
- ISO 22301