{"id":2646,"date":"2026-10-14T09:00:00","date_gmt":"2026-10-14T06:00:00","guid":{"rendered":"https:\/\/www.dataeye.ro\/?p=2646"},"modified":"2026-10-28T02:09:28","modified_gmt":"2026-10-28T00:09:28","slug":"what-is-a-gap-analysis-and-when-does-it-make-sense","status":"publish","type":"post","link":"https:\/\/www.dataeye.ro\/en\/blog\/what-is-a-gap-analysis-and-when-does-it-make-sense\/","title":{"rendered":"What is a gap analysis and when does it make sense?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A gap analysis is one of the simplest and most useful assessments an organisation can carry out before an audit, an inspection or a transformation project. The basic idea is a comparison: what you have now and what you should have, according to a standard or requirement.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">When a gap analysis makes sense<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A gap analysis is the right choice when you want to understand the level of compliance and maturity of your existing controls before an audit, a compliance assessment or an inspection. We often carry it out against the NIS2 Directive, the DORA Regulation, ADR requirements for electronic archiving or the Cyber Resilience Act, activating only the requirements relevant to each organisation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is important to know what it is not: a gap analysis is not a certification and does not, in itself, guarantee full compliance. It provides a structured view of the level of alignment and recommendations for remediation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Documentation and implementation, assessed separately<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">We don\u2019t just check whether a policy or procedure exists. For each area, we give two separate scores: documentation maturity and implementation maturity. We use a five-level maturity model, from <em>Initial<\/em> (there is no standardised process) to <em>Optimising<\/em> (the process is continuously monitored and indicators are used for improvement).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The difference matters: an approved procedure that is not applied in practice does not protect the organisation, even if it looks good on paper.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How it works<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Initiation and scope definition<\/strong> \u2013 we establish the applicable obligations and the systems, processes and vendors in scope.<\/li>\n\n\n\n<li><strong>Requirements mapping<\/strong> \u2013 we turn legal requirements into control criteria and assessment questions.<\/li>\n\n\n\n<li><strong>Information gathering<\/strong> \u2013 we review documentation, hold interviews and check evidence and configurations.<\/li>\n\n\n\n<li><strong>Maturity assessment<\/strong> \u2013 we score each area and identify the gaps against the target level.<\/li>\n\n\n\n<li><strong>Gap analysis and prioritisation<\/strong> \u2013 we identify deficiencies, their causes and impact, and set remediation priorities.<\/li>\n\n\n\n<li><strong>Reporting<\/strong> \u2013 we consolidate the conclusions and present them to management.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">What you get at the end<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The gap analysis report includes maturity scores by area, a register of gaps against requirements and prioritised recommendations. You get a clear picture of what is missing to achieve compliance or the desired level of maturity, and a concrete basis for the remediation plan.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A gap analysis compares what you have now with what you should have. Here is how it works, how maturity is measured and what you get at the end.<\/p>\n","protected":false},"author":1,"featured_media":2676,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[24],"tags":[],"class_list":["post-2646","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-audit-and-compliance"],"_links":{"self":[{"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/posts\/2646","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/comments?post=2646"}],"version-history":[{"count":1,"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/posts\/2646\/revisions"}],"predecessor-version":[{"id":2654,"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/posts\/2646\/revisions\/2654"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/media\/2676"}],"wp:attachment":[{"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/media?parent=2646"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/categories?post=2646"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dataeye.ro\/en\/wp-json\/wp\/v2\/tags?post=2646"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}