Skip to content
HackIT

E-ITS audit or penetration test: what's the difference

An E-ITS audit checks that security management meets the Estonian standard; a penetration test tries to break a system. What each is and when you need both.

HackIT Security Team

Explainer cover: E-ITS audit or penetration test: what's the difference

In short: An E-ITS audit is an independent assessment, required every three years for most service providers that must apply the standard, of whether their information security management and measures meet the Estonian information security standard. A penetration test is an authorised, simulated attack on a system to find weaknesses; in E-ITS it is covered by catalogue measures, not a substitute for the audit. Neither replaces the other: the audit checks a sample of the measures an organisation has planned, and penetration testing can be one of them.

The texts below are as checked on 5 November 2026: the E-ITS regulation in force since 1 September 2026, Government regulation nr 121 as in force from 1 October 2026, the Cybersecurity Act as in force from 16 October 2026, and the E-ITS 2026 catalogue on RIA's portal.

What is E-ITS?

E-ITS, the Estonian information security standard, is set under the Cybersecurity Act, which says the government or its authorised minister sets, by regulation, information security management requirements under the general title "Estonian information security standard" (§ 7(5)).

The current text is the regulation "Eesti infoturbestandard" of the Minister of Justice and Digital Affairs, nr 30 of 25 August 2026, in force since 1 September 2026. It replaced the previous E-ITS regulation, nr 101 of 2022. Under it, applying E-ITS means managing information security and having the security measures audited.

The regulation has three parts: the requirements for the management system, in its main text; the security catalogue, as Annex 1; and the auditing rules, as Annex 2. Since the 2026 version, the catalogue's detailed measures are no longer part of the regulation, which sets only each module's aim, RIA explains; the measures are published on the E-ITS portal and can be changed during the year.

Who has to apply E-ITS and be audited?

The duty is set in Government regulation nr 121. A service provider under the Cybersecurity Act, meaning an essential or an important entity, applies E-ITS at least to the systems linked to the activities listed in § 3(2) to (5) of the Act.

There are exceptions. E-ITS does not apply to a service provider whose security measures meet ISO/IEC 27001 for those systems and which has given RIA a valid certificate. Nor does it apply to service providers with on average fewer than 50 employees and an annual balance sheet or turnover of no more than €10 million, or to some named public bodies, most of them with fewer than 50 employees.

A service provider under E-ITS must have a compliance audit every three years (§ 4(1)). Its first audit is due within three years of the duty arising; providers of vital services follow the deadline set under § 83(4), clause 3, of the kriisiolukorra ja riigikaitse seadus. The audit duty does not apply to providers that meet the ISO/IEC 27001 conditions, nor to some museums, municipal bodies and schools unless they are the controller or processor of a database (andmekogu) under the Public Information Act.

RIA's E-ITS portal summarises this more broadly, saying the duty, including the audit, applies to the whole scope of the Cybersecurity Act. Regulation nr 121 itself sets the exceptions above; the two texts do not match.

What is an E-ITS audit?

The audit assesses whether the organisation's information security management system, and the measures it has implemented, meet the requirements of the regulation's chapter 2 and protect its business processes and objectives (§ 10(1)). It is an independent assessment by an auditor from outside the organisation, carried out under the auditing rules in Annex 2.

What it covers. The audit assesses whether the management system meets the requirements, whether the security documentation is current and relevant, and whether the measures are appropriate, risk-based and proportionate. Its scope must include at least the systems linked to the activities in § 3(2) to (5) of the Cybersecurity Act.

How it is done. The auditor checks a sample of the measures, chosen by risk, previous findings and incidents, following the agreed audit plan. Audit procedures make up at least 60% of the audit and include at least interviews, checks that measures work, including technical checks, on-site inspections and review of documents and evidence. The rules do not say what a technical check involves.

Who may do it. The lead auditor must hold CISA, or an IRCA or PECB lead auditor certificate for ISO/IEC 27001, and needs at least four years' experience in IT audit, IT management or information security. Audit team members must not have helped design or implement the management system, including consulting on it, in the three years before the audit. The same audit firm and lead auditor may not audit an organisation more than twice in a row.

Before it starts. The organisation must assess itself regularly, and that assessment may be done by an outside person; deficiencies found must be fixed, and the risks of measures left unimplemented accepted, by the start of the audit.

The result. The lead auditor signs two documents: an audit conclusion and a final report. The conclusion gives an overall assessment, including whether and how many nonconformities and high-level risks were found. A high-level risk must be removed within six months; if that is not possible, the organisation draws up a risk treatment plan. If the conclusion refers to a high-level risk, the final report also goes to the supervisor.

The two texts in force give different deadlines for sending the conclusion: regulation nr 121 says within 30 days of receiving it, which is also what RIA's page, last updated on 15 June 2026, says, while the auditing rules, in force since 1 September 2026, say within 14 days.

What is a penetration test?

E-ITS's own glossary defines a penetration test ("läbistustest") as an authorised, simulated cyber attack on a computer system, carried out to evaluate its security and find weaknesses. NIST SP 800-115 describes it as security testing in which evaluators mimic real-world attacks to find ways around the security features of an application, system or network.

In E-ITS, penetration testing appears in the catalogue, not in the regulation or the auditing rules. The module OPS.1.10 "Turvanõrkuste haldus" (vulnerability management) has three measures on it:

  • OPS.1.10.M11 requires a security testing procedure for regular or risk-based penetration testing of IT components, with results documented and shortcomings addressed as soon as possible.
  • OPS.1.10.M12 says web application security is checked regularly against OWASP ASVS requirements.
  • OPS.1.10.M13 requires a software penetration testing guide setting methods and result criteria; vulnerabilities found are documented, and significant ones fixed before the software goes into use.

A separate measure, OPS.1.10.M6, covers automated vulnerability scanning. The module DER.3 covers security testing and exercises more generally: a programme planned from risk assessments, a defined scope and documented method for each test, documented results, and testing that can be stopped at any time. Penetration testing also appears in other modules, for example GRC.4 on personal data protection, which counts penetration tests of applications as part of testing, and INF.7.1 on building technical systems, which sets tests before a system goes into use and after significant changes.

The three OPS.1.10 measures are standard measures. E-ITS's advisory implementation guide matches standard measures to a high protection need. An organisation's implementation plan includes the relevant catalogue measures, and the regulation lists two conditions for replacing a measure with an equivalent one, or leaving it out: the protection need is met; the organisation has accepted the risk (§ 7(6)).

OPS.1.10 gives no frequency for penetration tests, and E-ITS names no OWASP ASVS version.

Audit and penetration test side by side

E-ITS auditPenetration test in E-ITS
What it isIndependent assessment of the management system and measuresAuthorised simulated attack to find weaknesses
Where it is requiredRegulation nr 121 § 4(1), for most service providers under E-ITSCatalogue measures such as OPS.1.10.M11 to M13, if in the organisation's plan
How oftenEvery three yearsOPS.1.10: "regular or risk-based"; no frequency given
Who performs itExternal auditor with set qualifications and independenceNo qualifications set; DER.3 also covers tests ordered from outside
What it looks atThe whole management system, checking a sample of measuresSpecific IT components, web applications or software
ResultSigned conclusion and final report; the conclusion goes to RIA, the report too if it refers to a high-level riskDocumented results; shortcomings addressed as soon as possible

When do you need both?

No text says a penetration test can replace the E-ITS audit, or the other way round. They answer different questions: the audit asks whether the organisation manages security as the standard requires; a penetration test asks whether a particular system can be broken into.

For most organisations under E-ITS, the audit is required by law every three years. Penetration testing is required only through the catalogue: if measures such as OPS.1.10.M11 to M13 are in the organisation's implementation plan, the tests have to be done and documented. Because the auditor checks a sample of the planned measures, those testing measures can be part of what the audit looks at.

How a penetration test fits in

OPS.1.10.M12 ties web application testing to OWASP ASVS. Our post on what a web application penetration test covers explains ASVS area by area, and a web application penetration test is one way to check an application against it.

Check how it applies to you with RIA or your legal adviser.

If you want your web applications checked against OWASP ASVS, talk to a tester.

Sources