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
| Property | Value |
|---|---|
| Purpose | Management system for information security, quality and continuity: risks, controls, policies, documents, registers, metrics, training |
| Data basis | COD's asset inventory. Network, Firewall and Monitoring use the same inventory |
| Data storage | Its own PostgreSQL database for the compliance data, PostgreSQL version 18 or later |
| Standards | ISO/IEC 27001 and 27002, ISO 9001, ISO 22301, NIS2, BSI 200-3 method and more, see Standards catalogue |
| Connection and direction | No 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) |
| Interface | GRC API key per location |
| Result | Mapping and evidence. No certification and no promise of compliance |
Requirements
| Requirement | Why |
|---|---|
| PostgreSQL version 18 or later | GRC has its own database. The setup script creates it or uses an existing server |
| Time synchronisation via NTP on the COD server and database servers | Without it, the audit status shows “degraded” |
| A maintained asset inventory | Risks are assessed on the asset. See Inventory and CMDB import |
| A role with GRC permission | Rooms, racks and layer 1 cables need GRC permissions too |
| Optional: SIEM with syslog over TLS per RFC 5424 | Forwarding of the audit log. Certificates in both directions |
| Optional: DokuWiki with remote access switched on and a dedicated account | Import of wiki pages |
| Optional: Git repository with Markdown, reachable over HTTPS | Import 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.
- The manager account enables the module: “Admin Area > Tenant > Modules”. Then sign out and in again.
- Grant the GRC permission to the roles that work with the management system.
- Choose a home location for GRC and assign the locations it covers. This gives you one GRC for the whole organisation.
- Decide which standards your GRC shows. Switch on ISO/IEC 27019 if needed.
- Optional: import existing documents from DokuWiki or from a Git repository.
- Optional: set up forwarding of the audit log to your SIEM.
Technical details
Standards catalogue
| Standard or method | Note |
|---|---|
| ISO/IEC 27001 and 27002 | All 93 Annex A controls |
| ISO 9001 | Quality |
| ISO 22301 | Continuity |
| NIS2 directive | Requirements from Art. 20, 21 and 23 as a standard in the catalogue and in the statement of applicability (SoA) |
| BSI 200-3 | Method and defaults of the risk assessment |
| ISO/IEC 27019 | For the energy sector, can be switched on |
| BSI IT-Grundschutz Compendium 2023 | In the catalogue |
| BSI guidance on attack detection systems | In 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
| Property | Implementation |
|---|---|
| Writing | Append-only |
| Protection | Database triggers prevent changing and deleting entries |
| Content | Who, when, what, where, why. Field-level diff. Batch changes traceable through a correlation ID |
| Checkpoint | Since COD 3.7.8, COD seals new entries every night in a signed checkpoint |
| Forwarding | Optional via syslog over TLS per RFC 5424 to your central log system, with certificates in both directions |
| Time | NTP 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
- Switch on remote access in DokuWiki (setting
remote). - Create a dedicated account for COD in the wiki and enter it under
remoteuser. - 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
| Limit | What you can do |
|---|---|
| No certification, no promise of compliance | COD 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 visible | Forward 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 state | Use Network and Monitoring for this |
| The threat catalogue applies installation-wide | Agree changes to the catalogue between the tenants of an installation |
| Rooms, racks and layer 1 only with GRC permission | Give the GRC permission to the roles that maintain the inventory |
| The DokuWiki import needs remote access in the wiki | Switch it on for a dedicated account |
| Risks depend on the asset inventory | Keep 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