Modules
One page per module with requirements, setup, technical details and known limits. What a module does is described on its module page.
As of: November 2026, COD 3.8.6
Documentation contents
- Overview
- Getting started
- Requirements
- Names and addresses
- Network devices
- Time and DNS
- Installation
- Deployment shapes
- Initial setup
- Updates
- Modules
- Network and MikroTik
- Automation
- NAC
- TACACS+
- Firewall
- Captive Portal
- Monitoring
- Backup
- Hypervisor
- OTP
- Passkeepr
- GRC
- Inventory and CMDB import
- Troubleshooting
- Security
- Versions
- Version history
- Support
Documentation
- Overview
- Getting started
- Requirements
- Names and addresses
- Network devices
- Time and DNS
- Installation
- Deployment shapes
- Initial setup
- Updates
- Modules
- Network and MikroTik
- Automation
- NAC
- TACACS+
- Firewall
- Captive Portal
- Monitoring
- Backup
- Hypervisor
- OTP
- Passkeepr
- GRC
- Inventory and CMDB import
- Troubleshooting
- Security
- Versions
- Version history
- Support
Overview
| Module | Connects to | Who opens the connection | Documentation |
|---|---|---|---|
| Network and MikroTik | Switches and routers from nine vendors, MikroTik routers | COD server to the device, over SNMP, SSH and vendor API | Network and MikroTik |
| Automation | Switches from Allied Telesis, Cisco and Ruijie | Ansible service to the switch, over SSH | Automation |
| NAC | Switches and access points with 802.1X or MAC authentication | Device to the NAC service, over RADIUS | NAC |
| TACACS+ | Network devices with a TACACS+ client | Device to the TACACS+ service | TACACS+ |
| Firewall | AIMdefense, OPNsense, pfSense, DynFi | COD server to the firewall, over HTTPS API and SSH | Firewall |
| Captive Portal | OPNsense captive portal | COD server to the firewall | Captive Portal |
| Monitoring | Your existing Zabbix | COD server to the Zabbix API | Monitoring |
| Backup | Devices and servers with SSH, MariaDB | Backup service to the device, over SSH or SFTP | Backup |
| Hypervisor | VMware vCenter and ESXi | Hypervisor service on the COD server, over HTTPS | Hypervisor |
| OTP | no external systems | only within COD | OTP |
| Passkeepr | Browser extension for Chrome and Firefox | Browser to COD, over HTTPS | Passkeepr |
| GRC | optionally DokuWiki and Git | COD server to the source, once during import | GRC |
| Inventory and CMDB import | i-doit, CSV | COD server to i-doit, read-only | Inventory and CMDB import |
Planned, not a commitment: The roadmap lists Patch and update management and Vulnerabilities at a glance. Both items are meant to build on InfraScan. There is no technical documentation for them yet.
Enabling modules
Modules are enabled for the tenant and set up per site. NAC, backup, Passkeepr, Ansible and TACACS+ run as services of their own, on the COD server or on separate servers. How this works is described under Initial setup and Deployment shapes.
What your network needs per module
The network and device requirements per module are collected under Requirements. Customers and partners receive the list of connections and firewall rules as part of the project.