İç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. Modules
  4. GRC

GRC

This page describes how the GRC module keeps its data, which standards it maps, how the audit log is protected and which imports exist.

What the module does is described on the 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

PropertyValue
PurposeManagement system for information security, quality and continuity: risks, controls, policies, documents, registers, metrics, training
Data basisCOD's asset inventory. Network, Firewall and Monitoring use the same inventory
Data storageIts own PostgreSQL database for the compliance data, PostgreSQL version 18 or later
StandardsISO/IEC 27001 and 27002, ISO 9001, ISO 22301, NIS2, BSI 200-3 method and more, see Standards catalogue
Connection and directionNo outbound connection of its own in operation. Optionally COD opens connections to DokuWiki, to a Git server (both HTTPS) and to your SIEM (syslog over TLS)
InterfaceGRC API key per location
ResultMapping and evidence. No certification and no promise of compliance

Requirements

RequirementWhy
PostgreSQL version 18 or laterGRC has its own database. The setup script creates it or uses an existing server
Time synchronisation via NTP on the COD server and database serversWithout it, the audit status shows “degraded”
A maintained asset inventoryRisks are assessed on the asset. See Inventory and CMDB import
A role with GRC permissionRooms, racks and layer 1 cables need GRC permissions too
Optional: SIEM with syslog over TLS per RFC 5424Forwarding of the audit log. Certificates in both directions
Optional: DokuWiki with remote access switched on and a dedicated accountImport of wiki pages
Optional: Git repository with Markdown, reachable over HTTPSImport of documents

Customers and partners receive the list of connections and firewall rules as part of the project.

Setup

Set up GRC once locations, roles and assets are in place.

  1. The manager account enables the module: “Admin Area > Tenant > Modules”. Then sign out and in again.
  2. Grant the GRC permission to the roles that work with the management system.
  3. Choose a home location for GRC and assign the locations it covers. This gives you one GRC for the whole organisation.
  4. Decide which standards your GRC shows. Switch on ISO/IEC 27019 if needed.
  5. Optional: import existing documents from DokuWiki or from a Git repository.
  6. Optional: set up forwarding of the audit log to your SIEM.

Technical details

Standards catalogue

Standard or methodNote
ISO/IEC 27001 and 27002All 93 Annex A controls
ISO 9001Quality
ISO 22301Continuity
NIS2 directiveRequirements from Art. 20, 21 and 23 as a standard in the catalogue and in the statement of applicability (SoA)
BSI 200-3Method and defaults of the risk assessment
ISO/IEC 27019For the energy sector, can be switched on
BSI IT-Grundschutz Compendium 2023In the catalogue
BSI guidance on attack detection systemsIn COD as “BSI OH SzA 1.2”
  • The catalogue is versioned.
  • An SoA across several standards merges overlapping requirements into one row with all standard tags.
  • For each control you maintain applicability, implementation status, notes and linked policies.
  • The SoA catalogue texts can be shown in German or English and output as a PDF.
  • The threat catalogue applies installation-wide.

Audit log

PropertyImplementation
WritingAppend-only
ProtectionDatabase triggers prevent changing and deleting entries
ContentWho, when, what, where, why. Field-level diff. Batch changes traceable through a correlation ID
CheckpointSince COD 3.7.8, COD seals new entries every night in a signed checkpoint
ForwardingOptional via syslog over TLS per RFC 5424 to your central log system, with certificates in both directions
TimeNTP on all servers involved. Otherwise audit status “degraded”

The checkpoint makes a change visible afterwards. It does not make it impossible. Forwarding to a SIEM keeps a second copy outside COD.

Across the modules, the Admin Area keeps a further log under “Audit” with changes, module access and a report for the annual access review. You can also reach the report through “GRC > Compliance > Reports”.

Link to the asset

  • The name of an asset in a risk comes live from the inventory.
  • Risks are assessed on the asset and versioned, with BSI 200-3 defaults.
  • With GRC permission, the asset shows risk, contract, contact and the process that depends on it through its asset group.
  • COD redraws a layer 2 or layer 3 map in a GRC document each time it is viewed and with each PDF.
  • GRC does not show an operating state, monitoring state or backup status.

Import from DokuWiki

  1. Switch on remote access in DokuWiki (setting remote).
  2. Create a dedicated account for COD in the wiki and enter it under remoteuser.
  3. Enter the wiki's address and account in COD and start the import.

COD opens the connection to the wiki over HTTPS.

Import from Git

COD reads Markdown files from a Git repository over HTTPS. It fetches a shallow clone for this. An access token is optional. Use one for repositories that require a sign-in.

GRC API key

The GRC API key applies per location. Treat it like a password.

Rooms, racks and layer 1

Rooms, racks and layer 1 cables belong to the inventory but need GRC permissions. Details under Inventory and CMDB import.

Known limits

LimitWhat you can do
No certification, no promise of complianceCOD maps and makes things demonstrable. Assessing your obligations stays with you or your legal advisers
The signed checkpoint does not prevent changes, it makes them visibleForward the log to a SIEM and keep database access tight
Without time synchronisation, audit status “degraded”Set up NTP on the COD server and the database servers
GRC does not show an operating stateUse Network and Monitoring for this
The threat catalogue applies installation-wideAgree changes to the catalogue between the tenants of an installation
Rooms, racks and layer 1 only with GRC permissionGive the GRC permission to the roles that maintain the inventory
The DokuWiki import needs remote access in the wikiSwitch it on for a dedicated account
Risks depend on the asset inventoryKeep assets complete before you assess risks

Further reading

  • GRC module page
  • Inventory and CMDB import
  • Time and DNS
  • Security
  • Integrations
  • Troubleshooting
  • Questions about the modules
← Previous: PasskeeprNext: Inventory and CMDB import →
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