Recurring proof that the measures are implemented
Verrattu 4 lainkäyttöalueella
Alueella Saksa
Prove implementation to the BSI every three years (Nachweis)
Operators of a kritische Anlage prove implementation by Sicherheitsaudits, Prüfungen oder Zertifizierungen on a three-year cycle. This is a document deliverable to the regulator, which is what distinguishes it from the Directive's ad-hoc audit power: nobody has to suspect anything for the Nachweis to fall due. Operators designated under § 5(7) KRITISDachG are exempt.
Milloin: Every three years. The first evidence is due at the earliest three years after first becoming an operator of a kritische Anlage.
Tämä koskee, kun
- The KRITIS duty overlay: five duties that size alone never triggers
Miltä näyttö näyttää
- The last Nachweis, with its date
- The Mängelliste that accompanied it
- The remediation plan for those Mängel, with owners and dates
Alueella Puola
Audit the information system every three years and file the report with the authority
A key entity audits, at its own cost, the information system used to provide the service, at least once every three years, counted from the signature date of the previous report. The first audit is due within 24 months of meeting the criteria — which puts the transitional cohort at 3 April 2028. An electronic copy of the report goes to the competent authority within three working days. Independence is defined negatively and narrowly: the auditor may not be a person who performs, or who performed within the year before the audit began, the art. 8 tasks or the art. 9–13 tasks. That rules out your own ISMS and incident staff and anyone who held those duties in the preceding twelve months.
Milloin: At least every three years; first audit within 24 months of meeting the criteria; report copy to the authority within three working days.
Miltä näyttö näyttää
- The signed audit report, with its signature date
- Proof the copy reached the competent authority inside three working days
- An independence declaration covering the twelve months before the audit began
Alueella Tšekki
Run a cybersecurity audit as a named organisational security measure
The audit kybernetické bezpečnosti is one of the named organisational security measures, which makes it an explicit statutory internal-audit obligation rather than something inferred from a general duty to assess effectiveness. We state no cycle and no filing deadline for it: no statutory frequency and no duty to submit the audit to NÚKIB were located, and inventing either would be worse than saying so. Treat the frequency as a matter for your own risk-based judgement and for your counsel, not as a number we can give you.
Milloin: None located. Do not read the absence as “no audit is needed” — the measure itself is mandatory; it is the cycle and any filing duty that are unestablished.
Miltä näyttö näyttää
- The most recent cybersecurity audit report and its date
- The audit’s scope, matched against the stanovený rozsah
- The remediation actions raised by the audit and their status
Alueella Viro
Send the E-ITS audit conclusion to RIA within 30 days of receiving it
A provider that is under an audit obligation must send the E-ITS audit conclusion or decision to RIA within 30 days of receiving the audit, by e-mail. Two things this duty does NOT tell you, and which no published source states: how often you must be audited, and what credentials the auditor needs. The "three-year cycle" and the CISA-type credentials in circulation are vendor content, not law. Whether an audit obligation applies to you at all is also not something this tool can determine from published sources.
Milloin: Thirty days from receiving the audit. No frequency is published, so there is no cycle to plan against here — only a filing deadline once an audit has happened.
Miltä näyttö näyttää
- The audit conclusion or decision as received
- The e-mail transmitting it to RIA, with its date