For the CISOIRIS8
Where does our data go?
It stays in your environment. This page sets out who can reach it, what is logged and what we send for your review.
Your briefIRIS8
What you answer for
- 01Where regulated data is processed
- 02Who had access, and proof of what they did
- 03What happens to the model and the data if the supplier leaves
QuestionsIRIS8
Five questions CISOs ask us
The answers we give on the first call.
- 01
Where is our data processed, and does any of it leave?
Training and inference run in your VPC or on-prem. Your data stays in your environment. The one path out is a request to a frontier model, and that happens only for tasks you allow, through your gateway, with sensitive fields masked first.
- 02
How do your engineers get access, and how does it end?
Named IRIS8 engineers are given scoped, task-bound access inside your VPC or data centre. Every action they take is written to the same record as the model. Access is granted by your team and can be removed by your team.
- 03
What is logged, and where does the log live?
The gateway records each request, the route it took and the response. The model record holds datasets, training runs, test scores and approvals. Both stay in your environment, and findings can be exported to your SIEM in OCSF format. We do not keep a second copy outside.
- 04
What does the gateway stop?
It masks sensitive fields before a request leaves your boundary, by rules you set per team and data class. It can run in alert-only mode first, then enforce. Prompt-injection checks run on the request path, and each detection is logged.
- 05
What certifications do you hold?
We do not hold SOC 2 or ISO 27001 certification today. The model runs in your environment under your controls, and we answer your security questionnaire in full and in writing. If a certification is a condition for you, tell us on the first call.
Boundary and access logIRIS8
- Frontier modelOptional, masked, through your gateway
- IRIS8 engineerScoped, logged access
- 09:12IRIS8 engineerAccess granted: retrainScoped to task
- 09:14IRIS8 engineerTraining run startedLogged
- 10:58Head of Credit OperationsVersion v4 approvedLogged
- 11:03IRIS8 engineerAccess endedLogged
- 11:20GatewayAccount number maskedLogged
Every row is something your team can check in your own environment.
Security reviewIRIS8
What we send for a security review
- 01Architecture and data-flow diagram for your deployment
- 02Access model for IRIS8 engineers
- 03Logging specification: what is recorded and where
- 04Incident process and contacts
- 05Answers to your security questionnaire
For your teamIRIS8
Take back to your team
Next stepIRIS8