01 · Access controls

Access you can defend

Sign in through your identity provider with SAML SSO, with multi-factor authentication mandatory for every account. Restrict where people connect from with IP allowlisting.

  • Permissions come from groups, and an administrator can grant no more than they hold themselves.
  • Auditors get a group of their own, so they can read the record without being able to change it.
  • Separation of duties is built in: nobody both uploads a document and approves it.

Why it matters

Who can see and do what is explicit, and joiners and leavers follow your identity provider.

GroupsNew group
GroupMembersPermissions
Administrators2Manage people, groups and programmes
Programme managers3Run programmes, assign owners, approve evidence
Owners14Answer for what they own
Contributors38Supply evidence when asked
Auditors1Read the programme and its report
Sign-inEnforced
SAML single sign-on
Authenticator app (TOTP)
IP allowlistOn
203.0.113.0/24 · Head office 198.51.100.8/32 · VPN

02 · Audit logging

A record nobody can quietly rewrite

What was done, by whom and when is written to an append-only log. It is enforced in the database itself, so an entry cannot be edited or removed after the fact.

  • Evidence files are versioned and locked against change, so what the auditor reads is what was supplied.
  • A model's opinion and a person's decision are recorded apart, and only the second one counts.
  • Finished programmes are retired, not deleted, so the history stays readable.

Why it matters

When someone asks who changed what, the answer is on the record, and it can be trusted.

Rita Okonkwo supplied a documentCylanto Intelligence read it: holds all of itDana Alcott accepted the verdict Okta MFA policy export · 09:41CTL-IAM-04 · 3 of 3 readings · 09:43PCI DSS 8.4.2 now compliant · 11:02 Priya Raman read the report on compliance Read access · 16:20

03 · Data control

Your data, your rules

Decide what is uploaded, define how long it is retained, delete it when you choose, and keep it within your required geographic region.

  • Encrypted at rest, with separate keys for the database and for evidence.
  • Kept apart from every other customer, enforced at the database row and tested.
  • The AWS connection is a read-only role, with no keys stored.

Why it matters

Your data is your most valuable asset. Cylanto is designed so you stay in control of it.

What is uploaded How long it stays When it is deleted Which region

04 · Your inputs stay yours

Never used for training

Your inputs, outputs, prompts, and uploaded documents are never used to train the underlying models.

See what your stack already says about you.

Start with a discovery of your own domain. We will walk you through what we found, the frameworks that apply, who would own what, and where your evidence already stands.