How intuitem/ciso-assistant-community works
Purpose and entry points
CISO Assistant is an API-first cybersecurity GRC platform: it manages reusable controls, compliance assessments, risks, evidence, remediation, third parties, privacy, and reporting. The primary server entry points are the Django project at backend/manage.py, backend/ciso_assistant/urls.py, and ASGI/WSGI modules in backend/ciso_assistant/asgi.py and backend/ciso_assistant/wsgi.py. The user-facing application is a SvelteKit frontend rooted at frontend/src/routes/+layout.svelte, with the authenticated app under frontend/src/routes/(app).
Delivery topology and runtimes
The core runtime is Python/Django behind Gunicorn, plus a Node/SvelteKit SSR frontend. Huey executes asynchronous/background tasks, including notifications, integrations, and domain work. Docker Compose is the standard local/self-hosted deployment path (docker-compose.yml, backend/startup.sh); generated deployment variants live in config/templates. Kubernetes is supported through Helm (charts/ciso-assistant-next/templates/backend/deployment.yaml, charts/ciso-assistant-next/templates/frontend/deployment.yaml). Caddy is the default reverse-proxy/TLS boundary (Caddyfile, frontend/Caddyfile).
Persistent data uses SQLite by default or PostgreSQL in production; attachments can remain filesystem-backed or use S3-compatible/AWS S3 or Azure Blob storage. The database schema is Django-model/migration driven.
Core GRC domain and API boundary
backend/core/models.py is the central domain model for assets, perimeters, controls, evidence, assessments, risks, findings, incidents, tasks, and related shared concepts. backend/core/views.py, backend/core/serializers.py, and backend/core/urls.py expose the main REST surface. The frontend’s generic model routes proxy/render these resources through frontend/src/routes/(app)/(internal)/[model=urlmodel].
A defining design principle is separation of reusable control implementation from framework-specific compliance assessment. Assessment results, applied controls, evidence, risk scenarios, and action plans can therefore be related across scopes rather than duplicated. Mapping logic is a dedicated cross-framework boundary in backend/core/mappings/engine.py and backend/core/mappings/merge.py.
Libraries, frameworks, and assessment lifecycle
Versioned YAML libraries provide frameworks, control catalogs, threat catalogs, mappings, risk matrices, presets, quick forms, and workflow templates under backend/library/libraries. The library subsystem parses/builds/stores these artifacts and exposes import/load operations through backend/library/builder.py, backend/library/models.py, and backend/library/views.py.
Libraries instantiate framework structures used by compliance assessments; assessments collect requirement-level answers/evidence, calculate scores, derive mappings and remediation, then export reports. The interactive framework builder is implemented in frontend/src/lib/components/FrameworkBuilder/FrameworkBuilder.svelte; library authoring/import is available through frontend/src/routes/(app)/(internal)/experimental/library-builder.
Identity, tenancy/scoping, and portals
IAM is an architectural gate before domain access: users, roles, assignments, folders, service accounts, SSO, MFA, and SCIM are implemented in backend/iam/models.py, backend/iam/authentication.py, and backend/iam/scim/views.py. Folder/domain scope and permission checks constrain API queries and UI context. Authentication supports local accounts plus OIDC/SAML (backend/iam/sso/oidc/views.py, backend/iam/sso/saml/views.py).
The frontend separates internal users from constrained third-party/auditee experiences in frontend/src/routes/(app)/(third-party). Public trust/portal publication is a separate exposure boundary via backend/portals/views.py and frontend/src/routes/trust.
Automation, events, and integrations
The workflow engine models executable graphs with triggers, actions, scheduling, authorization, validation, and run state in backend/automation/workflows/engine.py, backend/automation/workflows/graph.py, and backend/automation/workflows/triggers.py. Its visual editor is frontend/src/routes/(app)/(internal)/workflows/[id=uuid]/WorkflowCanvas.svelte. Shipped workflow-library YAML can instantiate operational automations.
External boundaries include Jira and ServiceNow synchronization (backend/integrations/itsm/jira/integration.py, backend/integrations/itsm/servicenow/integration.py), outbound webhooks (backend/webhooks/service.py), and Kafka command ingestion through the standalone dispatcher (dispatcher/dispatcher.py, dispatcher/utils/kafka.py). The Python CLI/MCP server provides programmatic and agent-facing API access (cli/clica.py, cli/ca_mcp/server.py). n8n and Power BI connectors are maintained integration packages under automation/n8n/n8n-nodes-ca and automation/powerbi/connector.
Specialized intelligence and domain modules
Risk extends from qualitative assessments in core to EBIOS RM (backend/ebios_rm/models.py), quantitative cyber risk (backend/crq/models.py), resilience/BIA and DORA reporting (backend/resilience/models.py), and third-party risk (backend/tprm/models.py). Privacy processing/register functionality is isolated in backend/privacy/models.py.
AI/chat is a bounded subsystem: provider abstraction, scoped RAG, embeddings, knowledge graph, tool calls, and background indexing reside in backend/chat/providers.py, backend/chat/rag.py, and backend/chat/knowledge_graph.py; it can use external/local AI providers and Qdrant indexing. Security-intelligence feeds enrich advisory/vulnerability data through backend/sec_intel/feeds.py.
Main entry points: urls.py Django REST API · models.py Core GRC domain · +layout.svelte SvelteKit SSR frontend · builder.py Versioned YAML libraries
Components 21
Edge & Delivery
- Caddy reverse proxy · Routes browser traffic to frontend and backend services.
Caddyfile - Operational database · Django model and migration managed persistence.
- Attachment storage · Filesystem, S3-compatible, AWS S3, or Azure Blob attachments.
Django Platform
- Django REST API · Primary API entry point and domain service boundary.
backend/ciso_assistant/urls.py - IAM and tenancy · Authenticates identities and enforces scoped permissions.
backend/iam/authentication.py - Core GRC domain · Controls, assessments, evidence, risks, findings, incidents, and tasks.
backend/core/models.py - Cross-framework mappings · Derives relationships without duplicating reusable controls.
backend/core/mappings/engine.py - Versioned YAML libraries · Builds and imports frameworks, catalogs, mappings, and workflow templates.
backend/library/builder.py - Assessment lifecycle · Instantiates requirements, captures evidence, scores, and creates remediation.
backend/core/views.py
SvelteKit Experiences
- SvelteKit SSR frontend · Internal GRC app, third-party views, and UI rendering.
frontend/src/routes/+layout.svelte - Generic model UI · Renders and proxies core resource screens.
frontend/src/routes/(app)/(internal)/[model=urlmodel] - Framework builder
frontend/src/lib/components/FrameworkBuilder/FrameworkBuilder.svelte - Third-party portal UI
frontend/src/routes/(app)/(third-party)
Automation & Integrations
- Huey workers · Runs notifications, integrations, and deferred domain work.
- Workflow engine · Executes validated trigger-action graphs and records runs.
backend/automation/workflows/engine.py - Workflow canvas
frontend/src/routes/(app)/(internal)/workflows/[id=uuid]/WorkflowCanvas.svelte - ITSM and webhooks · Synchronizes Jira/ServiceNow and delivers outbound events.
backend/integrations/itsm/jira/integration.py - Kafka dispatcher · Consumes commands for platform processing.
dispatcher/dispatcher.py
Specialized Domains
- Risk, resilience, privacy · EBIOS RM, quantitative risk, BIA/DORA, TPRM, and privacy registers.
backend/ebios_rm/models.py - AI and security intelligence · Scoped RAG, indexing, tool calls, and advisory/vulnerability feeds.
backend/chat/rag.py - AI providers & Qdrant
Connections 24
- Caddy reverse proxy → SvelteKit SSR frontend: serves UI
- Caddy reverse proxy → Django REST API: routes API
- SvelteKit SSR frontend → Generic model UI: hosts
- SvelteKit SSR frontend → Third-party portal UI: separates experience
- Generic model UI → Django REST API: uses REST resources
- Framework builder → Versioned YAML libraries: authors/imports
- Third-party portal UI → Django REST API: constrained access
- Django REST API → IAM and tenancy: authenticates and scopes
- Django REST API → Core GRC domain: exposes
- Django REST API → Versioned YAML libraries: loads and imports
- Core GRC domain → Assessment lifecycle: drives
- Versioned YAML libraries → Assessment lifecycle: instantiates frameworks
- Assessment lifecycle → Cross-framework mappings: derives mappings
- Core GRC domain → Operational database: persists
- Core GRC domain → Attachment storage: stores evidence
- Django REST API → Huey workers: queues work
- Workflow engine → Huey workers: runs asynchronously
- Workflow canvas → Workflow engine: edits graphs
- Huey workers → ITSM and webhooks: syncs and notifies
- Kafka dispatcher → Django REST API: ingests commands
- Django REST API → Risk, resilience, privacy: serves specialist modules
- Core GRC domain → Risk, resilience, privacy: shares GRC context
- Huey workers → AI and security intelligence: indexes asynchronously
- AI and security intelligence → AI providers & Qdrant: queries and indexes