These docs are under active development and cover the v0.20 Kobicha security model.
On this page
§2.1

Token Structure

A token is the kernel's representation of a security context. Every process MUST have an associated primary token. A process MAY additionally hold an impersonation token.

§2.1.1 Required fields

A conforming token MUST contain the following fields:

§2.1.1.1 User SID

The User SID identifies the principal the token represents. This MUST be a valid SID as defined in the SID specification.

§2.1.1.2 Group SIDs

A token MUST contain zero or more group SIDs. Each group SID SHOULD have associated attributes indicating whether the group is enabled for access checking.

§2.1.1.3 Privileges

A token MAY contain privileges. Each privilege MUST be identified by a LUID and MUST have an enabled/disabled state. An implementation MUST NOT grant access based on a disabled privilege.

§2.1.2 Integrity level

Every token MUST carry an integrity level. The integrity level MUST be one of: Untrusted, Low, Medium, High, or System.