Security
Oversight stays with people.
This page separates controls implemented in this repository from the operating model Ciright intends. It does not publish an audit certification, a data-residency promise, or a statement that the system cannot fail.
Implemented on this site
- Sign-in uses the existing Keyra OAuth handoff. ADM does not create a second account system.
- A successful sign-in stores a signed, HTTP-only session cookie. In production the cookie is marked secure. The session is checked with a time limit of twelve hours and can be cleared by signing out.
- Public marketing pages can be read without signing in. The workspace requires a Keyra session. Without one, it does not return workspace records.
- An accepted demo request is stored on this site. A refused request is not stored. It is not sent to a separate CRM.
Intended oversight, not certified here
- IdentityKeyra identifies the person. A display name in the header is not a new identity.
- Scoped accessApplications and objects remain limited to what that person, organization, and action allow.
- ApprovalSensitive actions wait. An agent does not approve its own sensitive work or grant itself tools.
- ActivityOn The Line is the named history product. A timeline is not, by itself, immutable or non-repudiable.
What this page will not say
No compliance badge, penetration-test result, residency region, or uptime promise is published, because this repository does not contain that evidence. Status colors above are paired with words so the state is not communicated by color alone.