Web application and interfaces
The website, app and APIs that citizens use to log in, and the interfaces with the underlying systems.
Service
Your annual ICT security assessment, with Logius on time and right first time.
Does your organisation have a DigiD connection? Then an IT auditor must test every year whether that connection is secure, and you submit the report to Logius before 1 May. Our IT auditors perform the audit, coordinate with your suppliers and deliver the report in the prescribed format. You speak directly with the auditor who signs.
Or call 085 7609740
Citizens use DigiD to log in to your website, portal or app. Because sensitive personal data is involved, the government sets requirements for the security of every connection. Those requirements are laid down in the standard for DigiD ICT security assessments: 21 guidelines, derived from the NCSC's security guidelines for web applications.
In the audit, officially the DigiD ICT security assessment, an IT auditor tests whether your connection meets those guidelines. The report goes to Logius, the organisation that manages DigiD. You receive an opinion on each guideline: compliant or not compliant.
Every organisation with an active DigiD connection. The obligation applies per connection. In practice this often means:
Do you outsource development or hosting? As the connection holder you remain ultimately responsible. Your supplier accounts for its part with its own assurance report, which you submit to Logius together with your own report.
The audit follows the route a citizen takes: from the login page to the systems behind it. We test all 21 guidelines for design and existence. We also test five guidelines for operating effectiveness: for those you must be able to show that the control has worked over a longer period.
The website, app and APIs that citizens use to log in, and the interfaces with the underlying systems.
The environment in which the application runs: servers, network, access management and the hosting provider.
How you implement changes, fix vulnerabilities, grant access and handle incidents.
A penetration test and a vulnerability assessment are part of testing the technical guidelines.
Earlier than most organisations think. The report must reach Logius between 1 January and 1 May and covers the previous year. But the five guidelines that are tested for operating effectiveness require a test period of at least six consecutive months that includes 31 December.
This means your controls must demonstrably work by 1 July at the latest. If you only start in January, you can no longer make up that period. That is why we plan a pre-audit in the spring or summer, so that you know what still needs to be done while there is still time.
Do you have a new connection? Then Logius expects the first report within two months of activation. That first audit covers design and existence only.
Plan the preliminary review in spring or summer, so there is still time to fix shortcomings. In an introductory meeting we draw up a timeline for your connections and suppliers.
Almost no organisation manages the entire DigiD chain itself. For the guidelines that are the responsibility of your software supplier or hosting provider, you rely on their assurance report: the service organisation's report, formerly known as a TPM.
In practice, this is where things often go wrong. The report arrives too late, does not cover all the guidelines or is too old: on the date of your own report it may be no more than twelve months old. A SOC 2 report from your supplier is only partly usable.
At the start we map out which guidelines are your responsibility and which are your suppliers', assess whether their reports are usable and request what is missing in good time.
Five steps, with a schedule in advance that also shows the time needed from your own people.
Which connections do you have, which suppliers are involved and which guidelines are whose responsibility?
Well before the end of the year we test where you stand, so that you can still fix shortcomings.
We test the guidelines for design, existence and operating effectiveness and assess the results of the technical tests.
You receive the assurance report in the format prescribed by Logius, signed by the IT auditor.
We explain the findings in plain language and discuss what you can do differently next year.
It happens, and it is not a disaster if you know in time. For each guideline, Logius sets a period within which you resolve the shortcoming and then asks for a reassessment by the auditor.
Submitting late is more troublesome: a notice of default is then sent to the board, and ultimately Logius can disconnect the connection. A pre-audit and a realistic schedule prevent both.
Every year between 1 January and 1 May, covering the previous year. For a new connection, within two months of activation.
An IT auditor (RE) who is registered with NOREA, the professional body for IT auditors. The auditor signs the report personally.
No. Your supplier's report only covers the guidelines for which that supplier is responsible. As the connection holder you remain ultimately responsible and need a report of your own.
Five of the 21 guidelines. For those you show that the control has worked for at least six consecutive months, in a period that includes 31 December.
That depends on the number of connections and on what you have outsourced. You mainly provide evidence and answer questions. The schedule you receive in advance shows what we ask of you and when.
Yes. For municipalities the DigiD audit is part of ENSIA, together with Suwinet. We perform both.
In a short conversation we discuss your connections, your suppliers and a schedule that fits the 1 May deadline.