Viewing as , ,
Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationKeia Method· Level 2 · 2.8
Why IT can trust the record
Every change has a named person, every figure names its source, and nothing is edited quietly.
What surrounds the record
- Named ownershipEvery change, task, incident and rule has a person
- A record that cannot be quietly editedWho, what, when, before, after, on every object
- Inspectable"How was this done?" on every automatic action
- Least privilegeConnectors read-only by default
- The recordEvery space, device and job; who, what, when, before, after
- Bounded automationCaps per wave, rings, halt on failures, change windows, two people above a blast-radius threshold, a kill switch
- Restricted by defaultFloor plans, camera and door positions, IP plans and the vulnerable-firmware list are restricted by schema
- Keia is a service tooIn its own catalogue with an owner and a service level
- No rip and replaceExisting service desk, asset, fleet and network tools connect through one layer and stay the record for as long as the team wants
The 8 guarantees in full
| Guarantee | What it means |
|---|---|
| Named ownership | Every change, task, incident and rule has a person; automatic work runs under that person's rule and reports to them |
| A record that cannot be quietly edited | Who, what, when, before, after, on every object; the audit log is also the change history and the auditor's evidence |
| Inspectable | "How was this done?" on every automatic action; every figure names its source and time; the raw record one click down |
| Least privilege | Connectors read-only by default; a write scope belongs to a named rule; per-platform service accounts in a vault; vendor access scoped to a job and ending with it |
| Bounded automation | Caps per wave, rings, halt on failures, change windows, two people above a blast-radius threshold, a kill switch |
| Restricted by default | Floor plans, camera and door positions, IP plans and the vulnerable-firmware list are restricted by schema; exports are watermarked and logged; live camera feeds are never stored |
| Keia is a service too | In its own catalogue with an owner and a service level; when the fault is ours, the incident says so |
| No rip and replace | Existing service desk, asset, fleet and network tools connect through one layer and stay the record for as long as the team wants |
The standards this evidence supports
No tool can make an organisation compliant. Keia keeps the records that help its users meet their duties.
| Standard or rule | What the record holds |
|---|---|
| ISO/IEC 27001, SOC 2, Cyber Essentials | Asset inventory, access reviews, patch status, changes, incidents, vendor reviews, exportable by date range with a published control mapping |
| ISO/IEC 42001 (shape, not certification) | A register of each AI use with purpose, model, owner and risk; evaluation records; the action log |
| EU AI Act, Article 50 | An assistant says it is AI; AI-drafted text sent to people is labelled or reviewed; no emotion or engagement scoring of staff; no scoring or allocation by individual behaviour |
| NIS2 and the UK bill | Inventory of network and security devices with owner and firmware; a vendor access register; incident timers (24 h, 72 h, one month) with an exportable timeline |
Try it in the demo
Opens as Liam, the Dublin technician. Everyone in the demo is made up; nothing you do leaves this browser.
- Open the video bar in 3.09 Whooper Swan: where it is, what it is connected to, and its history.
- Every line of history names who, what and when.