Anzen Documentation

Anzen is an integrated platform for IT service management (ITSM), risk management, and compliance. It brings together your asset inventory, ticketing, security controls, and risk reporting into a single workspace - so your team can manage incidents, track controls, and quantify cyber risk without juggling multiple tools.

First Steps

New to Anzen? A typical first day looks like this:

1. Set up your entity hierarchy - create a top-level entity for your organisation and add departments or offices underneath. Most things in Anzen scope to an entity, so doing this early pays off.
2. Invite a teammate or two - go to Users and send invites. You'll want at least one other administrator before you start ingesting data.
3. Bring in your assets - either add configuration items manually or run the network scanner under Discovery.
4. Get a controls baseline - the Library dropdown on the Controls page lets you import a curated framework template (ISO 27001, NIS2) or, with the Extract add-on, draft controls from your own policy PDFs.
5. Run your first test - open a control and click Execute test. A failing test auto-creates an issue, and the issue starts feeding the risk report.

Anzen is built so each module starts useful immediately and grows richer as you add neighbouring data. You don't need to populate everything before you can extract value.

The Dashboard

The dashboard is your daily landing page after login. It surfaces what needs attention right now: overdue control tests, open issues grouped by severity, recent tickets assigned to you, and a snapshot of your risk exposure. Each tile is clickable and drops you on the relevant list view filtered to your work.

Core Concepts

Anzen is built around a few key ideas:

• Workspaces - each organisation gets a fully isolated workspace with its own data, users, and configuration. Your data never mixes with another customer's.
• Entities - your organisational hierarchy (offices, departments, teams). Everything in Anzen is scoped to an entity, from assets to permissions.
• Configuration items - the servers, switches, firewalls, and cloud resources you manage. The foundation of your asset inventory.
• Tickets - incidents, problems, and change requests following ITIL-aligned workflows.
• Controls and issues - security controls with test procedures, test history, and automated issue creation when controls fail.
• Risk report - a real-time view of your risk exposure, calculated from active issues and the financial value of affected business processes.

How It Fits Together

The platform is designed so that data flows naturally between modules. A configuration item belongs to an entity and can be linked to business processes, tickets, and controls. When a control test fails, an issue is automatically created. That issue's severity and the financial value of affected business processes determine your risk exposure - visible in real time on the risk report.

Permissions follow the same entity hierarchy. A role scoped to "EU Engineering" automatically applies to all its child entities, so you can delegate access without duplicating configuration.

Two Interfaces

Anzen provides two web interfaces on every workspace:

• Management interface (/management) - the full administration panel for IT and security teams. Manage assets, tickets, controls, risk, users, and billing.
• Service portal (/) - a simplified interface for end-users to submit tickets, track their requests, and view assigned issues.

Browse the Documentation

Use the sidebar to navigate to any topic, or start with these:

• Workspaces - how isolation and workspace setup works.
• Entities - building your organisational structure.
• Tickets (ITSM) - incident, problem, and change management.
• Controls - defining and testing security controls.
• Risk Report - understanding your risk exposure.