Security & Governance — Design Document

As enterprise-grade AI infrastructure, Taimoe addresses four core security and compliance requirements:

1. Who can do what (IAM / RBAC / SSO)
2. How resources are isolated (Project Isolation)
3. Are invocations secure (Policy Interception)
4. Who is accountable (End-to-end Traceability)

---

1. Enterprise Identity Integration (SSO / SCIM)

To seamlessly integrate with existing enterprise IT environments, Taimoe supports standardized authentication protocols:

1.1 Single Sign-On (SSO)

• Supports SAML 2.0 and OIDC.
• Connects out-of-the-box with existing Identity Providers (IdPs), such as Google Workspace, Microsoft Entra ID (Azure AD), and Okta.
• Eliminates secondary passwords, leveraging central IT for session management and Multi-Factor Authentication (MFA).

1.2 Directory Synchronization (SCIM)

• Supports automated user and group provisioning via SCIM (System for Cross-domain Identity Management).
• When employees offboard or transfer departments, identity changes in the corporate IdP immediately propagate to Taimoe, auto-revoking or updating access rights.

---

2. Project Isolation

In multi-subsidiary conglomerates or large enterprises, AI project data across business units must remain strictly isolated.

2.1 Organization & Project Hierarchy

• Organization: Top-level tenant container representing an enterprise entity or holding group.
• Project: Resource container under an organization; all LLM traffic, Virtual Keys, Policy settings, and Audit Logs are strictly scoped within specific Projects.

flowchart TD
    subgraph Enterprise["Enterprise Tenant (Organization)"]
        OrgOwner["Org Owner / Admin"]

        subgraph ProjA["Project A (Finance App)"]
            DevA["Project Admin A"]
            VK_A["Virtual Key A"]
            PolicyA["Rate Limit & Cost Policy A"]
            AuditA["Audit Logs A"]
        end

        subgraph ProjB["Project B (Customer Support Chatbot)"]
            DevB["Project Admin B"]
            VK_B["Virtual Key B"]
            PolicyB["Rate Limit & PII Policy B"]
            AuditB["Audit Logs B"]
        end
    end

    OrgOwner -->|Manages| ProjA
    OrgOwner -->|Manages| ProjB

    VK_A -. Strictly Isolated .- VK_B
    AuditA -. Strictly Isolated .- AuditB

2.2 Isolation Boundaries

• Permission Isolation: Project A administrators cannot view or access Virtual Keys or audit logs in Project B.
• Quota Isolation: Budget and rate limit controls (Quota Guard) are enforced at the Project level, preventing traffic spikes in one project from impacting others.

---

3. Role-Based Access Control (RBAC & IAM)

We adopt a fine-grained authorization architecture aligned with public cloud standards (e.g., GCP / AWS), governing access via Role-Based Access Control (RBAC).

3.1 Predefined Roles

Resource Level	Role Name	Scope & Capabilities
Platform	Super Admin	Platform-wide administrator with full control over all Organizations.
	Support Engineer	Platform Operations engineer with read-only visibility across organizations.
Organization	Org Owner	Organization owner capable of creating Projects, managing billing, and Org-level Policies.
	Org Auditor	Auditor with read-only access to all Audit Logs within the Organization.
Project	Project Admin	Project administrator capable of issuing Virtual Keys and configuring Project Policies.
	Project Developer	Project developer with permission to view Virtual Key status and API logs.

3.2 Virtual Keys as Service Accounts

Architecturally, Virtual Keys issued to external applications are treated as Service Accounts. Binding specific Policies to a Virtual Key enforces fine-grained access boundaries and spending limits for individual client applications.

---

4. Policy & Defense

Taimoe provides global defensive mechanisms enforced at the Gateway layer:

1. Real-Time Rate Limiting (Quota Guard) Powered by Token Bucket algorithms, requests exceeding quota thresholds are blocked at the edge before reaching LLM Providers.
2. PII Redaction (Planned) Detects and masks sensitive personal identifiers (SSNs, credit card numbers) before prompts reach external models.
3. Model Armor (Planned) Defends against Prompt Injection and jailbreak attacks to maintain system integrity.

Administrators can scope policies globally, per-project, or per-key based on compliance requirements.

---

5. Audit Logs

In addition to API call traffic logs (Call Audit Log), Taimoe maintains immutable Administrative Audit Logs (Admin Audit Log).

5.1 Admin Audit Log

Records administrative configuration changes across the platform, including:

• User permission grants and revocations
• Virtual Key creation, rotation, or revocation
• Policy creation, modification, or status toggles

Each log entry includes actor_user_id, action, resource_target, old_value, and new_value, providing non-repudiable proof for security forensics.