Central log collection
Firewalls, routers, switches, servers, storage and backup systems send their logs via standard syslog to one place. No more hunting through individual devices.
In a NIS2 audit you will have to show that you keep logs for at least 12 months (Slovak NBÚ Decree No. 227/2025 Coll., Annex 1, item 116), that they are protected against modification and that time is synchronised. The auditor will ask for them. GRIS collects, sorts and seals logs from your devices every day – and prepares the report for the auditor in one click.
On your own server or as a service · connected to the NIS2 Compliance module
Illustrative report preview
minimum log retention under item 116
records must be protected against modification and unauthorised access
first audit or self-assessment within 24 months of registration
or 2% of worldwide turnover – the fine ceiling for essential entities under NIS2
Logging is one of the requirements you cannot meet with a policy on paper. The auditor wants to see real records and proof that they are complete and unaltered. GRIS prepares the evidence straight from the system.
A report with the oldest stored record and retention periods per category. By default GRIS keeps security events, sign-ins and configuration changes for 12 months.
An overview of messages sorted into categories: security events, sign-ins and access, configuration changes, errors and routine operation.
The GRIS monitoring agent collects interactive and RDP sign-ins from Windows without system accounts (4624, 4778/4779), failed attempts (4625), sign-ins with explicit credentials (4648) and with administrator rights (4672), and Kerberos and NTLM failures on domain controllers.
Auditors ask about sign-ins to e-mail and cloud services almost every time – and Microsoft keeps them in Entra ID for only 7 days, 30 days with a P1/P2 licence. Every 5 minutes GRIS archives Entra ID sign-ins – successful and failed, with MFA, IP address, application, risky sign-ins and legacy protocols – and keeps them for 365 days with seals.
In Windows: account creation, change, disabling and deletion, password resets, group membership changes and account lockouts. In Entra ID: changes to roles, passwords, app consents and conditional access, and the account lifecycle.
GRIS records log clearing (1102, 104), audit policy changes (4719), service installation (4697, 7045) and scheduled task changes as security events. From Microsoft 365 also mail forwarding and rules, mailbox permissions, external and anonymous sharing and eDiscovery exports.
Daily SHA-256 seals and their verification result right in the report. If anyone altered a stored record afterwards, verification would reveal it.
Access to logs is governed by GRIS permissions and every view is recorded – who, when and what.
A list of log sources with status and time of the last message. The source watchdog alerts you when a device goes silent.
A time-synchronisation check for log sources – records from different devices stay in the right order and can be reliably compared.
Download the report as a PDF and attach it as evidence to the measure in the NIS2 Compliance module. The audit outcome is the auditor’s call – GRIS gives them the logging evidence clearly and in one place.
Twelve months of history cannot be filled in afterwards. The auditor may ask for a record from a year ago – and you will only have it if it was being collected back then. If you start collecting logs just before the audit, you will have nothing to show for the time before.
connect your devices and collection starts
GRIS sorts, seals and watches the records
you have a full year of history for the audit
Set it up once. From then on GRIS collects, sorts, retains and watches the records every day, and you come back to them when you need them – after an incident or for an audit.
Firewalls, routers, switches, servers, storage and backup systems send their logs via standard syslog to one place. No more hunting through individual devices.
Every message is classified on arrival: security events, sign-ins and access, configuration changes, errors and routine operation. What matters does not get lost in the noise.
The GRIS monitoring agent collects the essential security events from Windows servers and workstations with no setup and resumes where it left off after a restart. If a server is missing the Windows audit settings, GRIS shows it and an administrator enables them with one confirmed click; on domain controllers it points to the GPO setting.
GRIS archives sign-ins and audit records from Entra ID and Microsoft 365 every 5 minutes. Your administrator simply approves access – even via a link, without a GRIS account. Access is read-only and the application keys never leave our system.
By default GRIS keeps security events, sign-ins and configuration changes for 12 months, as item 116 of NBÚ Decree No. 227/2025 Coll. requires. Routine noise is removed sooner, so the archive does not grow needlessly. Retention periods are adjustable.
GRIS closes each day’s records with a digital seal. Verify at any time whether anyone has altered a stored record afterwards.
When a device starts spewing thousands of messages, GRIS does not choke. Critical and security messages are never dropped.
When a device stops sending logs, GRIS alerts you – so a gap in the records does not surface only at the audit.
GRIS checks that sources send the correct time. Records from different devices stay in order and can be reliably compared when investigating an incident.
Who viewed the logs and when is recorded. Access is governed by GRIS permissions.
Prepare an audit overview in one click: log sources, oldest record, retention periods, seal verification, time synchronisation and access to logs.
Attach the report as evidence to the measure in the Compliance module. Turn a suspicious event into a security incident with monitored reporting deadlines.
The foundation is standard syslog – sent by almost every network device, server and storage system. Windows servers and workstations connect through the GRIS monitoring agent, Microsoft 365 by simply approving access.
Administrator sign-ins, blocked connections, VPN and rule changes.
Configuration changes, port outages and sign-ins to device management.
SSH sign-ins, sudo, service messages and system errors.
Events from hypervisors, cluster nodes and backups.
Sign-ins to NAS management, blocked addresses and system events.
The GRIS monitoring agent automatically collects the essential Windows security events – sign-ins including RDP and failed attempts, account and group changes, log clearing, audit policy changes, new services and scheduled tasks. Events get a readable description and are kept in the archive for 365 days with seals. GRIS also accepts messages from an existing syslog forwarder.
Any device that can send syslog – for example network printers or a UPS with a network card.
Entra ID sign-ins (successful and failed, MFA, IP address, application, risky sign-ins, legacy protocols), Entra ID audit (roles, passwords, app consents, conditional access, account lifecycle) and Microsoft 365 audit (mail forwarding and rules, mailbox permissions, send-as, external and anonymous sharing, eDiscovery and exports, DLP and retention, security alerts). GRIS archives them every 5 minutes and keeps them for 365 days with seals – Microsoft itself keeps Entra ID sign-ins for only 7 days, 30 days with a P1/P2 licence.
Received over UDP and TCP in RFC 3164 and RFC 5424 formats. GRIS automatically recognises sign-ins from OpenSSH, MikroTik RouterOS, Synology DSM and Windows (events 4624 and 4625). The brands listed are examples – what matters is that the device can send syslog.
No agents on network devices and servers – standard syslog, supported by most equipment, is all it takes. Windows connects through the GRIS agent.
Configure your devices to send syslog to GRIS. We help you with this during deployment.
Each message is classified and stored with the retention period that applies to it.
Every day GRIS seals the records, checks that all sources are reporting and verifies the time.
Download the PDF report for the auditor and attach it to the measure in the NIS2 Compliance module.
Two comparisons that capture what the NIS2 log archive does.
Like an aircraft flight recorder, it continuously records what happens on your network. When something goes wrong, you can trace back when it started, which devices were involved and who signed in where.
As if a notary stamped the pages of a logbook every day: the previous day’s records are sealed and any later change shows up on verification. That is why an auditor can rely on them.
The NIS2 log archive is part of GRIS – it works on its own as well as together with the NIS2 Compliance module and other modules.
Operators of essential services covered by the Slovak Cybersecurity Act and NBÚ Decree No. 227/2025 Coll. – for example manufacturing, energy, transport, healthcare or public administration. The cybersecurity manager has the logs and the audit evidence in one place.
IT service providers collect logs from several clients in one GRIS – each one separately, with its own retention periods – and help their clients with audit requirements without building their own solution.
Managed service providers, cloud and data centre operators are also covered by Implementing Regulation (EU) 2024/2690, whose point 3.2 deals with monitoring and logging. GRIS helps keep logs collected, protected and verifiable.
GRIS runs on your server in your network – logs never leave your infrastructure.
GRANDCOM operates GRIS and you only make sure your devices send their logs.
What cybersecurity managers and IT leads ask most often.
Slovak NBÚ Decree No. 227/2025 Coll., Annex 1, item 116 requires that relevant operational and security logs are created and kept for at least 12 months, capturing activities, exceptions, faults and other relevant events, while preventing changes to their integrity and unauthorised access to them. Item 93 additionally requires system time synchronised with approved time sources. The entity determines the scope of measures based on its risk analysis.
Because 12 months of history cannot be created retroactively. The archive reaches the required length only a year after the devices are connected. The first audit or self-assessment is due within 24 months of registration – if you start in time, you will have something to show the auditor.
Any device that can send logs via syslog – for example firewalls, routers, switches, Wi-Fi controllers, Linux servers, hypervisors, network storage or backup systems. Windows servers and workstations connect through the GRIS monitoring agent, which collects the essential security events automatically. During deployment we go through which sources matter for the audit.
The GRIS monitoring agent collects the essential security events automatically: interactive and RDP sign-ins without system accounts (4624, 4778/4779), failed sign-ins (4625), sign-ins with explicit credentials (4648) and with administrator rights (4672), Kerberos and NTLM failures on domain controllers, account and group changes, account lockouts, log clearing (1102, 104), audit policy changes (4719), service installation (4697, 7045) and scheduled tasks. It deliberately does not collect the whole security log, only what matters for the audit. Events are only generated when Windows auditing is enabled – if the setting is missing, GRIS shows it and an administrator enables it on the server with one confirmed click. On domain controllers GRIS points out that auditing must be configured in Group Policy (GPO).
Yes. Every 5 minutes GRIS archives Entra ID sign-ins (successful and failed, with MFA, IP address, application, risky sign-ins and legacy protocols), Entra ID audit (roles, passwords, app consents, conditional access, account lifecycle) and security-relevant events from the Microsoft 365 audit – such as mail forwarding, mailbox permissions, external sharing, eDiscovery exports, DLP or security alerts. It keeps them for 365 days with seals, while Microsoft keeps Entra ID sign-ins for only 7 days, 30 days with a P1/P2 licence. Connecting is easy: your administrator simply approves access, even via a link without a GRIS account. Access is read-only and the application keys never leave our system.
Auditing must be enabled in Microsoft 365 (Microsoft Purview) – it is usually on by default and we check it with you during deployment. Complete sign-in records from Entra ID require a Microsoft Entra ID P1 licence, included for example in Microsoft 365 Business Premium. Without it, GRIS takes sign-ins from the Microsoft 365 audit.
GRIS sorts the messages: security events, sign-ins and configuration changes are kept for 12 months, errors for a shorter time and routine noise for 30 days by default. The archive holds what the audit needs and does not needlessly accumulate personal data that logs may contain (such as names or IP addresses). Access to logs is permission-based and recorded.
Each day’s records are closed with a SHA-256 seal. GRIS verifies the seals – if a stored record were altered afterwards, the mismatch would show. The verification result is part of the PDF report for the auditor.
Your choice: on your own server in your network, or in a GRIS operated for you by GRANDCOM as a service. Either way the logs are connected to the NIS2 Compliance module.
No – the audit outcome is assessed by the auditor and your organisation is responsible for its security measures. GRIS helps you meet the audit requirements for logging: it collects and retains records, protects their integrity, watches the sources and prepares the evidence for the auditor.
We will show you the NIS2 log archive in a live GRIS, go through your devices and suggest how to set up collection for your network.