İçereği Atla
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Portal
  • English (US) Français Deutsch Español Türkçe
  • Demoyu açın
  • Ana Sayfa
  • COD Genel Bakış
    Platform
    Genel BakışPlatform: müşteriler ve markaÖzelliklerSorunlar ve ÇözümlerMimariDocumentationEntegrasyonlarFiyatlar
    İşletme ve Ağ
    MonitoringAğNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Güvenlik ve Dayanıklılık
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprOtomasyon
    Çözümler ve Daha Fazlası
    NIS2 & CompliancecodPassYapay zekâ ile dokümantasyon (InfraScan ek modülü)Demoyu açınReferanslarİndirilenlerSSS
  • Fiyatlar
  • Haberler
    • Blog
    • Yol Haritası
  • SSS
  • Hakkımızda
    • Hakkımızda
    • Kariyer
    • İş ortakları
    • Referanslar
  • Academy
  • İletişim
COD powered by extocode GmbH
  • 0
    • Ana Sayfa
    • COD Genel Bakış
    • Fiyatlar
    • Haberler
      • Blog
      • Yol Haritası
    • SSS
    • Hakkımızda
      • Hakkımızda
      • Kariyer
      • İş ortakları
      • Referanslar
    • Academy
    • İletişim
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Portal
  • Demoyu açın
  1. Home
  2. Documentation
  3. Security

Security

This page describes the security features of COD and what you do for them in operation. It only states what is confirmed for COD 3.8.6.

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
  • 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
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Access and roles

PropertyValue
RoleBelongs to a tenant. Rights apply per module and per location
RightsFive individually assignable rights: create, read, update, delete and CSV import. They can be combined freely
CSV importOnly for Asset, Network, Backup and NAC
Without read rightThe module's menu item does not appear for that user
Smallest boundaryThe location is the smallest boundary for rights and data. There are no rights per device. If you want to set devices apart, separate them by location
Installation-wideBranding, asset catalogues and asset names apply to the whole installation
CheckEvery call to a module goes through COD. COD checks the module rights with every request. The modules also check the signed sign-in token themselves
Directory groupEach role can carry a group from Active Directory or LDAP
Directory syncThe scheduled sync locks accounts that are no longer in the access group. It creates no accounts and unlocks none
LockingAccounts are locked with a reason. The trail is kept
Manager accountOnly the Manager account enables modules for a tenant. Only the Manager role changes the branding

The page Tenants, locations and roles also gives an overview of the rights.

Sign-in

PropertyValue
AccountsLocal accounts or sign-in through Active Directory or LDAP
Directory serviceLDAPS is switched on out of the box. You store the certificate authority of your directory service in COD
Directory service outageKeep a local access, for example the manager account.
Second factorTOTP with recovery codes. A role can require the second factor. An administrator can reset the factor of an account
OTP moduleStores one-time codes for other systems. It is separate from the second factor of the COD sign-in
Local accountsA new user without a password receives an invitation. The link to set the password works once. COD notifies the account when its password or email address changes
Manager accountBuilt-in emergency and administration account with TOTP. The setup wizard creates it and shows the TOTP QR code exactly once. The email address of the Manager account cannot be changed later
SessionLasts up to seven days
TransportHTTPS is mandatory in operation. Without HTTPS, sign-in only works locally on the COD server. Session cookies are marked secure and are only sent over HTTPS
PasskeeprThe web vault locks after one hour without activity. Each person can choose a shorter time. The administrator's time under “Auto-lock when idle” is the upper limit

Recommendation: Keep the TOTP access of the Manager account separate from the server and separate from personal accounts. The Manager account is your emergency access.

Encryption

AreaMethod
Browser to CODHTTPS. Certificate from the installation's own certificate authority created by the setup wizard, your own certificate, or a reverse proxy in front
Stored credentials for devices and systemsEncrypted in the database. The keys belong to the installation
Switch configuration (Ansible)Credentials encrypted in the vault of the Ansible service
Configuration backups (Backup)Optionally encrypted, switched on per host or template. Applies to backups stored locally. Folder backups are excluded
PasskeeprEnd-to-end encrypted. The server stores only ciphertext. Argon2id for key derivation, X25519 for keys, AES-GCM for items
TACACS+Passwords as an Argon2id hash, not reversible. Sensitive fields with AES-256-GCM
Audit to your SIEMSyslog over TLS with certificates on both sides

Passkeepr has one deliberate exception: enterprise vaults belong to the organisation. The organisation account can open them too. Its unlocks and changes are logged.

Note: Without the installation's keys, encrypted credentials cannot be restored. Include these keys in the backup of the COD server. You receive the complete list as part of the project.

Audit and logs

LogContentProtection
GRC, history per objectEvery change to assets, controls, policies and risk assessments: who, when, what, where, why. Field-level diff, batch changes traced through a correlation IDAppend-only. Database triggers prevent later changes and deletion. Separate PostgreSQL database. Since 3.7.8, COD seals new entries every night in a signed checkpoint
“Admin Area > Audit” (since 3.7.8)Changes and access across the modules, sign-ins and exports. Report for the annual access reviewThe database does not allow changes to entries. COD seals new entries every night with a signature

The signed checkpoint makes a later change visible. It does not make it impossible.

Under “History”, Passkeepr shows earlier versions of each item, who saved them and what differs (since 3.8.6). The operating logs of COD and of the NAC, Backup, Passkeepr and TACACS+ services are under “Admin Area > Log”. You pick the service under “Service”.

TopicRule
ForwardingOn request, the audit log goes to your SIEM or central log system by Syslog over TLS according to RFC 5424. COD opens the connection
TimeNTP on the COD server, the database servers and the module servers. Without time sync, the audit status shows “degraded”

More on time: Time and DNS.

Network and operation

  • COD installs no agents on network devices. It reads and controls them through SNMP, SSH and vendor APIs. COD opens the connection to the device.
  • Restrict device access for SNMP, SSH and API to the source address of the COD server and the module servers.
  • Manage devices from a dedicated management network.
  • The connection between COD and module servers belongs in a trusted network. Keep Passkeepr on the COD server where possible.
  • The Hypervisor service is only reachable locally on the COD server. The Ansible service listens only locally out of the box.
  • You decide whether the interface should be reachable from outside.
  • The packages set up no firewall rules on the server. Customers and partners receive the list of connections and firewall rules as part of the project.
  • Recommended: a dedicated service user for COD on each device and system, not a personal account. Rights as small as possible. You receive the minimum rights as part of the project. Whether SSH keys can be used instead of passwords is clarified in the project.

Limits

LimitWhat you can do
SNMP only in v1 and v2c with a community. The community travels in clear textGrant the community read-only. Allow SNMP only from the management network and only from the source address of the COD server
Configuration backup requires SSHSwitch on SSH on the device and restrict it to the source address of the backup host

Details per device: Preparing network devices.

Which data leaves the installation

The table applies to Self Hosted. With Shared Hosted and Private Hosted, extocode operates the instance.

ConnectionWhenWhat is sentFrom
Package sources: apt.extoco.de plus the package sources of Ubuntu, Node.js and, on 22.04 and 24.04, PostgreSQLInstallation and updatePackage download, directly or through an HTTP proxyAll COD servers
Vendor name list for MAC addressesOnce a weekDownload of the list. You receive the address as part of the project.COD server
Feedback to extocodeOnly when a user sends a messageContent of the message, to the vendor's issue tracker or by emailCOD server
Leak check in PasskeeprWhen Passkeepr checks a passwordThe first five characters of the password's hash, never the password. The target is the public Pwned Passwords serviceThe user's browser

Beyond this, COD needs no internet access. You set up connections to your own systems, such as the directory service, Zabbix, mail server or SIEM, yourself. For isolated environments, an offline bundle is available on request as a local package source.

Security fixes

  • Security fixes are provided only for the latest version. Keep COD up to date for this reason.
  • Automatic updates are not set up for the COD packages out of the box. You apply updates yourself.
  • With Shared Hosted and Private Hosted, extocode applies new versions itself.
  • One example: COD 3.8.6 contains security fixes for assets, logs and Active Directory.

How to update: Applying updates. Which version is current: Versions.

Reporting vulnerabilities

Report suspected vulnerabilities in COD confidentially by e-mail to security@extocode.com.

Please include:

  • the COD version, for example from apt policy cod-backend
  • the affected component, for example module, service, package or browser extension
  • the steps to reproduce the issue
  • how we can reach you
RuleWhy
Test only on your own installations or with the operator's permissionOther installations, including hosted instances of other customers, are off limits
Do not send real passwords, keys or customer dataSample data is enough to reproduce the issue
Treat the report confidentiallyThose affected should receive a fix first

We do not commit to deadlines for a reply or a fix, and we offer no reward. Security fixes are released for the latest version, see Security fixes.

Further reading

  • Tenants, locations and roles
  • COD architecture
  • Passkeepr module in the docs
  • GRC module in the docs
  • Initial setup with HTTPS and the Manager account
  • Security FAQ
← Previous: TroubleshootingNext: Versions →
Folgen Sie uns
​
  • COD Genel Bakış
  • Özellikler
  • Demo
  • Fiyatlar
  • Entegrasyonlar
  • NIS2
  • codPass
  • Referanslar

Help

  • SSS
  • Documentation
  • İndirilenler
  • İletişim

Kotzinger Straße 21 • 83278 Traunstein • Deutschland

  • ​+49 (861) 88 00 32 00
  • ​info@extocode.com
Datenschutz Impressum ​
Copyright © extocode GmbH
English (US) Français Deutsch Español Türkçe

Bu web sitesinde size daha iyi bir kullanıcı deneyimi sunmak için çerezleri kullanıyoruz. Gizlilik Politikası

Reddet Kabul et