1:1-2 | Scope: the security audits and security scans foreseen in 3 kap. 5 to 7 §§ of the Cybersecurity Act (2025:1506); chapter 2 applies only where a supervisory authority engages an ind | 0 |
1:3-4 | Definitions: expressions follow the Cybersecurity Act; digital environment, sector-critical system, system, security audit, security scanning and important societal function are de | 0 |
2:1 | A security audit must assess the operator's level of cybersecurity and whether its security measures meet the requirements of the Cybersecurity Act and its subordinate regulation | 1 |
2:10 | If a previously unpublished vulnerability is found in the operator's digital environment during an audit, the supervisory authority must ensure the independent body informs the ope | 1 |
2:11 | After the audit the supervisory authority must ensure the independent body compiles the results in a written report and hands the report and other relevant documentation to the aut | 1 |
2:2 | The independent body engaged for a security audit must be a legal person or sole trader whose staff have knowledge sufficient for the design of the assignment and, where needed, of | 1 |
2:3 | The supervisory authority must ensure the independent body audits impartially, independently and objectively, is bound by no confidentiality agreement with the operator that limits | 2 |
2:4 | When a security audit starts, the supervisory authority must inform the operator of the assignment's scope, of its right to report shortcomings in the independent body's conduct of | 1 |
2:5 | The supervisory authority must ensure the independent body documents every deviation from compliance with the Cybersecurity Act and its subordinate regulation | 1 |
2:6 | A security audit checks both the design and the application of security measures and must be designed so it causes the operator no more cost or inconvenience than necessary | 1 |
2:7 | A security audit includes at least document review, interviews with relevant staff, technical checks of systems and segments and, where needed, inspection of premises, with the las | 1 |
2:8 | The audit follows a documented methodology that allows a systematic, risk-based examination of organisational, technical, operational and physical security measures, and the superv | 1 |
2:9 | Before a security audit begins the supervisory authority must have approved its scope and approach | 1 |
3:1 | Through security scanning the supervisory authority assesses the effectiveness of the security measures implemented in the operator's digital environment | 1 |
3:2 | A security scan is performed by a supervisory authority, which may engage an external actor, and by personnel with knowledge sufficient for the assignment | 1 |
3:3 | The supervisory authority must ensure a security scan goes no further than supervision requires and covers only systems the operator controls within its own activities | 1 |
3:4 | The supervisory authority must ensure a security scan is carried out so that negative impact on system functionality and other adverse consequences for the operator are minimised | 1 |
3:5 | When an external actor performs a security scan, the supervisory authority must ensure it is bound by no confidentiality agreement with the operator that limits the authority's acc | 1 |
3:6 | In choosing a scanning method the supervisory authority must consider the systems' importance to the operator's activities, and where a significant risk of adverse consequences is | 1 |
3:7 | Before deciding to scan, the supervisory authority must ensure the operator and the systems were selected by a risk-based method and that the methods to be used suit the identified | 1 |
3:8 | Before a security scan, unless special reasons weigh against it, the supervisory authority together with the operator must assess the risk of operational impact, plan the scan to m | 1 |
3:9 | The supervisory authority must ensure the operator is informed without delay and in an appropriate manner of shortcomings and vulnerabilities found in a security scan so that it ca | 1 |
status | Legal basis in 38 § point 7 of the Cybersecurity Ordinance (2025:1507), the non-binding status of the general advice, decision on 15 June 2026 and entry into force on 1 October 202 | 0 |