{"id":71994,"date":"2026-11-20T12:21:17","date_gmt":"2026-11-20T11:21:17","guid":{"rendered":"https:\/\/www.inovex.de\/?p=71994"},"modified":"2026-11-20T12:22:06","modified_gmt":"2026-11-20T11:22:06","slug":"nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/","title":{"rendered":"NIS-2, DORA &#038; CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance"},"content":{"rendered":"<p>When terms like NIS-2 (Network and Information Security), DORA (Digital Operational Resilience Act), or the CRA (Cyber \u200b\u200bResilience Act) come up in meetings, many IT leaders envision one thing above all else: a massive increase in bureaucratic overhead. This is entirely understandable. New EU regulations are often associated with just one thing: more forms, lengthy approval processes, and less time for day-to-day operations.<\/p>\n<p>The problem rarely lies with the regulation itself, but rather with how we approach it in practice. We tend to organize security into folders and checklists. Yet, a completed Excel spreadsheet will not stop an attack when it actually happens, nor will it make systems any more resilient.<\/p>\n<p>So, how do we shift from mere &#8220;paper compliance&#8221; to genuine technical resilience?<!--more--><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_89 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\"><p class=\"ez-toc-title\" style=\"cursor:inherit\"><\/p>\n<\/div><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#Why-regulatory-pressure-is-on-the-rise\" >Why regulatory pressure is on the rise<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#The-Pitfall-Treating-Security-Merely-as-a-Documentation-Project\" >The Pitfall: Treating Security Merely as a Documentation Project<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#A-practical-approach-Integrating-security-directly-into-the-technology\" >A practical approach: Integrating security directly into the technology<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#1-Keeping-the-ISMS-Alive\" >1. Keeping the ISMS Alive<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#2-Automating-Technical-Checks-DevSecOps\" >2. Automating Technical Checks (DevSecOps)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#3-Realistic-Incident-Response-Testing\" >3. Realistic Incident Response Testing<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#A-simple-real-world-example-from-abstract-risk-to-solution\" >A simple real-world example: from abstract risk to solution<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#Liability-is-a-leadership-issue-Why-senior-management-must-be-on-board\" >Liability is a leadership issue: Why senior management must be on board<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Why-regulatory-pressure-is-on-the-rise\"><\/span>Why regulatory pressure is on the rise<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The EU is increasingly replacing previous guidance with mandatory requirements. This currently affects almost every level of IT. Here is a brief summary of the key classification criteria and regulations:<\/p>\n<p><strong>NIS-2:<\/strong> This applies to companies with 50 or more employees or an annual turnover of at least \u20ac10 million within critical sectors, classifying them as either &#8220;important&#8221; or &#8220;essential&#8221; entities. This encompasses 18 sectors, as defined in Annexes 1 and 2 of the BSI Act (the Act on the Federal Office for Information Security and the security of information technology in various entities). Furthermore, regardless of company size or annual turnover, an organization may fall under the scope of NIS legislation if it operates within one of these sectors (e.g., as a DNS provider, a trust service provider, or an operator of critical infrastructure). The specific details regarding classification into NIS-2 sectors are highly complex, and the assessment process can be extremely time-consuming. Therefore, the classification process should be carried out by experienced consultants specializing in critical infrastructure (KRITIS). A key aspect involves the strict reporting deadlines for significant incidents: an initial &#8220;early warning&#8221; must be submitted to the BSI (Federal Office for Information Security) within<strong> 24 hours<\/strong>, followed by a subsequent report within <strong>72 hours<\/strong> of an incident&#8217;s discovery. A final report must be submitted within <strong>one month<\/strong> of the initial notification.<\/p>\n<p><strong>DORA<\/strong>: This regulation applies not only to banks and insurance companies but also\u2014indirectly, via contractual agreements\u2014to their IT service providers (e.g., cloud providers, data centers, and software vendors). A core component is &#8220;Threat-Led Penetration Testing&#8221; (TLPT)\u2014that is, conducting realistic, simulated attacks on IT infrastructure during live operations.<\/p>\n<p><strong>CRA<\/strong>: This requires manufacturers of products with digital elements to provide a Software Bill of Materials (SBOM) as part of their technical documentation. It also mandates the provision of free security updates for the product&#8217;s expected lifespan (with a minimum of five years). An exception applies if the anticipated service life is shorter. Furthermore, there are additional obligations, such as vulnerability management and risk management.<\/p>\n<p>Even those not directly subject to these laws may still feel their impact through the supply chain; regulated clients often simply pass these requirements on to their suppliers, software partners, and service providers.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"The-Pitfall-Treating-Security-Merely-as-a-Documentation-Project\"><\/span>The Pitfall: Treating Security Merely as a Documentation Project<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In many organizations, the immediate reaction to new regulatory requirements is to acquire templates, fill out PDFs, and draft process descriptions\u2014all for the sake of an audit.<\/p>\n<p>This approach has two major drawbacks:<\/p>\n<ol>\n<li><strong>It offers no actual protection<\/strong>: Documents do nothing to address configuration errors, weak passwords, or vulnerabilities in the code.<\/li>\n<li><strong>A brake on agile teams<\/strong>: When approval forms are required for every minor change, development speed suffers.<\/li>\n<\/ol>\n<p>Effective security is not achieved through retrospective documentation, but rather through robust IT architecture, automated processes, and security integrated directly into the development lifecycle.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"A-practical-approach-Integrating-security-directly-into-the-technology\"><\/span><strong>A practical approach<\/strong>: Integrating security directly into the technology<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>To ensure that security teams and developers aren\u2019t working at cross-purposes, security must be woven into daily operations as seamlessly as possible. This is best accomplished through automation and clearly defined responsibilities.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"1-Keeping-the-ISMS-Alive\"><\/span>1. Keeping the ISMS Alive<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>In practice, an ISMS rarely fails because of its set of rules; rather, it falters when it comes to day-to-day application. Instead of spending months drafting policies upfront, the following steps have proven effective:<\/p>\n<ul>\n<li><strong>The &#8220;Minimum Viable ISMS&#8221; as a starting point:<\/strong> Do not aim to perfectly cover all 93 controls of ISO 27001 on day one. Focus first on the 20% of risks that cause 80% of the potential damage\u2014typically identity management, missing patches, and insecure backups.<\/li>\n<li><strong>Keep policies concise and readable:<\/strong> No one reads a policy that is longer than two pages. Formulate clear rules of conduct rather than legalistic, defensive text. For example: &#8220;MFA is mandatory for all external access&#8221; is better than three paragraphs explaining the theoretical significance of authentication.<\/li>\n<li><strong>Embed processes where work already happens:<\/strong> If your team uses Jira or GitLab, the risk register shouldn&#8217;t be a separate Excel spreadsheet on SharePoint. Instead, create risks as specific ticket types within the same system used to prioritize other tasks. This allows management to see\u2014during resource planning\u2014exactly which risk is being mitigated by a given technical ticket.<\/li>\n<li><strong>Automated evidence instead of manual screenshots:<\/strong> Auditors require proof. From the outset, set up automated scripts that query the state of your systems\u2014either on a monthly basis or in preparation for an audit (e.g., &#8220;Are all hard drives encrypted?&#8221; or &#8220;Do all admins have MFA enabled?&#8221;). This saves days of searching for documentation when an audit approaches.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"2-Automating-Technical-Checks-DevSecOps\"><\/span>2. Automating Technical Checks (DevSecOps)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>To ensure that automation remains more than just a buzzword, agile teams rely on established open-source and enterprise tools:<\/p>\n<ul>\n<li><strong>Static Application Security Testing (SAST):<\/strong> Tools such as SonarQube, Semgrep, or Checkmarx examine source code during the pull-request process for common vulnerabilities (e.g., the OWASP Top 10) and block the merge if critical issues are detected.<\/li>\n<li><strong>Software Composition Analysis (SCA):<\/strong> Tools like Snyk, Trivy, OWASP Dependency-Check, or https:\/\/dependencytrack.org\/ analyze the libraries in use and automatically generate an SBOM\u2014as required by the Cyber \u200b\u200bResilience Act (CRA)\u2014in either the SPDX or CycloneDX format.<\/li>\n<li><strong>Infrastructure as Code (IaC) Scanning:<\/strong> Tools such as tfsec (now part of Trivy) or Checkov scan Terraform or Kubernetes configuration files prior to deployment, preventing misconfigurations\u2014for instance, ensuring that cloud storage (such as S3 buckets) is not inadvertently left publicly accessible.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"3-Realistic-Incident-Response-Testing\"><\/span>3. Realistic Incident Response Testing<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>NIS-2 and DORA mandate very short reporting deadlines in the event of an incident. Searching for an emergency response plan only when a crisis actually occurs wastes valuable time. A more effective approach involves conducting short, regular exercises\u2014known as &#8220;Game Days&#8221;\u2014to test monitoring tools and reporting chains under realistic conditions.<\/p>\n<p>What does a pragmatic &#8220;Game Day&#8221; look like in practice? Rather than disrupting live operations, the security team plans a two-hour scenario within a staging environment (e.g., a simulated data breach or the failure of a central database):<\/p>\n<ul>\n<li><strong>Injection<\/strong>: A technical ticket or a simulated alert is triggered\u2014without prior warning\u2014for the on-call team.<\/li>\n<li><strong>Response<\/strong>: The team must follow the predefined reporting chain, analyze log files, and isolate the breach.<\/li>\n<li><strong>Retrospective<\/strong>: Afterward, the focus is not on assigning blame, but on evaluation\u2014were the log files sufficiently informative? Did everyone know who was responsible for preparing the notification to the authorities?<\/li>\n<\/ul>\n<p>Three such exercises per year provide more genuine security than any hundred-page emergency manual. Of course, processes, workflows, and documentation are necessary\u2014but ideally, these should be the natural outcome of established, day-to-day practices.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"A-simple-real-world-example-from-abstract-risk-to-solution\"><\/span>A simple real-world example: from abstract risk to solution<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>What does this pragmatic approach look like in practice? Let\u2019s take the issue of third-party risk (a key focus of DORA and NIS-2):<\/p>\n<ol>\n<li><strong>The old way:<\/strong> The security team sends a 50-page questionnaire to every new software vendor. The vendor fills it out in a rigid, perfunctory manner, and someone simply files the document away. In reality, nothing has been effectively assessed.<\/li>\n<li><strong>The pragmatic approach:<\/strong> Define simple criteria (e.g., does the provider process personal data? Do they have access to the production network? Are there other types of critical access?). If any of these apply, a developer or &#8220;security champion&#8221; checks just two specific things: Is there a current SOC 2 or ISO certificate, and is there a clean API interface for managing permissions? The answer is then recorded directly in the system alongside the relevant tool.<\/li>\n<\/ol>\n<p>This reduces the effort required from several days to just two hours\u2014while producing a result that is audit-ready and genuinely valuable.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Liability-is-a-leadership-issue-Why-senior-management-must-be-on-board\"><\/span>Liability is a leadership issue: Why senior management must be on board<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>An often-overlooked aspect of NIS-2 and DORA is the <strong>personal responsibility of senior management<\/strong>. Executives can no longer simply &#8220;delegate&#8221; responsibility for cyber risks to the IT department.<\/p>\n<p>In practical terms, this means the following for company leadership:<\/p>\n<ul>\n<li>Regular security briefings: A standing agenda item in monthly management meetings (e.g., a 15-minute status update on cyber risks and critical vulnerabilities).<\/li>\n<li>Mandatory documentation: Verifiable training for senior management on risk management and cyber threats, ensuring compliance with legal due diligence obligations.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>There is no denying that these new regulations require effort. However, if we view these requirements not merely as red tape, but as an opportunity to modernize legacy processes and automate testing, everyone wins:<\/p>\n<p>IT becomes more stable, workflows become clearer, and the company meets regulatory requirements as a natural part of its ongoing operations. Those getting started now should begin with a thorough impact and gap analysis to establish priorities. It is precisely at this intersection of regulation and modern platforms that we help teams integrate compliance seamlessly into their existing cloud and DevOps environments. to integrate.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When terms like NIS-2 (Network and Information Security), DORA (Digital Operational Resilience Act), or the CRA (Cyber \u200b\u200bResilience Act) come up in meetings, many IT leaders envision one thing above all else: a massive increase in bureaucratic overhead. This is entirely understandable. New EU regulations are often associated with just one thing: more forms, lengthy [&hellip;]<\/p>\n","protected":false},"author":466,"featured_media":71992,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"ep_exclude_from_search":false,"footnotes":""},"tags":[],"service":[880],"level":[1280],"coauthors":[{"id":466,"display_name":"Stephan Auge","user_nicename":"sauge"}],"class_list":["post-71994","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","service-security-en"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>NIS-2, DORA &amp; CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance - inovex GmbH<\/title>\n<meta name=\"description\" content=\"Learn how to implement EU regulations\u2014such as NIS-2, DORA, and the CRA\u2014through automation, DevSecOps, and a lean ISMS, fostering genuine technical resilience rather than mere bureaucracy.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"NIS-2, DORA &amp; CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance - inovex GmbH\" \/>\n<meta property=\"og:description\" content=\"Learn how to implement EU regulations\u2014such as NIS-2, DORA, and the CRA\u2014through automation, DevSecOps, and a lean ISMS, fostering genuine technical resilience rather than mere bureaucracy.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/\" \/>\n<meta property=\"og:site_name\" content=\"inovex GmbH\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/inovexde\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-20T11:21:17+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-20T11:22:06+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.inovex.de\/wp-content\/uploads\/Cyber_Resilience.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1500\" \/>\n\t<meta property=\"og:image:height\" content=\"880\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Stephan Auge\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/www.inovex.de\/wp-content\/uploads\/Cyber_Resilience-1024x601.png\" \/>\n<meta name=\"twitter:creator\" content=\"@inovexgmbh\" \/>\n<meta name=\"twitter:site\" content=\"@inovexgmbh\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Stephan Auge\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/\"},\"author\":{\"name\":\"Stephan Auge\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/#\\\/schema\\\/person\\\/2f7996568e4fb7617d8a58fb6b7581d2\"},\"headline\":\"NIS-2, DORA &#038; CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance\",\"datePublished\":\"2026-11-20T11:21:17+00:00\",\"dateModified\":\"2026-11-20T11:22:06+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/\"},\"wordCount\":1591,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/Cyber_Resilience.png\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/\",\"name\":\"NIS-2, DORA & CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance - inovex GmbH\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/Cyber_Resilience.png\",\"datePublished\":\"2026-11-20T11:21:17+00:00\",\"dateModified\":\"2026-11-20T11:22:06+00:00\",\"description\":\"Learn how to implement EU regulations\u2014such as NIS-2, DORA, and the CRA\u2014through automation, DevSecOps, and a lean ISMS, fostering genuine technical resilience rather than mere bureaucracy.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/Cyber_Resilience.png\",\"contentUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/Cyber_Resilience.png\",\"width\":1500,\"height\":880},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"NIS-2, DORA &#038; CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/\",\"name\":\"inovex GmbH\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/#organization\",\"name\":\"inovex GmbH\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2021\\\/03\\\/inovex-logo-16-9-1.png\",\"contentUrl\":\"https:\\\/\\\/www.inovex.de\\\/wp-content\\\/uploads\\\/2021\\\/03\\\/inovex-logo-16-9-1.png\",\"width\":1921,\"height\":1081,\"caption\":\"inovex GmbH\"},\"image\":{\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/inovexde\",\"https:\\\/\\\/x.com\\\/inovexgmbh\",\"https:\\\/\\\/www.instagram.com\\\/inovexlife\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/inovex\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UC7r66GT14hROB_RQsQBAQUQ\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/#\\\/schema\\\/person\\\/2f7996568e4fb7617d8a58fb6b7581d2\",\"name\":\"Stephan Auge\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/575feb2af5f2d3c59d587c7401c0572294d08b08418293be7d58013edc25d8c9?s=96&d=retro&r=ge1645902405dbc0156237f84d63cfc2a\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/575feb2af5f2d3c59d587c7401c0572294d08b08418293be7d58013edc25d8c9?s=96&d=retro&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/575feb2af5f2d3c59d587c7401c0572294d08b08418293be7d58013edc25d8c9?s=96&d=retro&r=g\",\"caption\":\"Stephan Auge\"},\"url\":\"https:\\\/\\\/www.inovex.de\\\/en\\\/blog\\\/author\\\/sauge\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"NIS-2, DORA & CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance - inovex GmbH","description":"Learn how to implement EU regulations\u2014such as NIS-2, DORA, and the CRA\u2014through automation, DevSecOps, and a lean ISMS, fostering genuine technical resilience rather than mere bureaucracy.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/","og_locale":"en_US","og_type":"article","og_title":"NIS-2, DORA & CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance - inovex GmbH","og_description":"Learn how to implement EU regulations\u2014such as NIS-2, DORA, and the CRA\u2014through automation, DevSecOps, and a lean ISMS, fostering genuine technical resilience rather than mere bureaucracy.","og_url":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/","og_site_name":"inovex GmbH","article_publisher":"https:\/\/www.facebook.com\/inovexde","article_published_time":"2026-11-20T11:21:17+00:00","article_modified_time":"2026-11-20T11:22:06+00:00","og_image":[{"width":1500,"height":880,"url":"https:\/\/www.inovex.de\/wp-content\/uploads\/Cyber_Resilience.png","type":"image\/png"}],"author":"Stephan Auge","twitter_card":"summary_large_image","twitter_image":"https:\/\/www.inovex.de\/wp-content\/uploads\/Cyber_Resilience-1024x601.png","twitter_creator":"@inovexgmbh","twitter_site":"@inovexgmbh","twitter_misc":{"Written by":"Stephan Auge","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#article","isPartOf":{"@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/"},"author":{"name":"Stephan Auge","@id":"https:\/\/www.inovex.de\/en\/#\/schema\/person\/2f7996568e4fb7617d8a58fb6b7581d2"},"headline":"NIS-2, DORA &#038; CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance","datePublished":"2026-11-20T11:21:17+00:00","dateModified":"2026-11-20T11:22:06+00:00","mainEntityOfPage":{"@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/"},"wordCount":1591,"commentCount":0,"publisher":{"@id":"https:\/\/www.inovex.de\/en\/#organization"},"image":{"@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#primaryimage"},"thumbnailUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/Cyber_Resilience.png","inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/","url":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/","name":"NIS-2, DORA & CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance - inovex GmbH","isPartOf":{"@id":"https:\/\/www.inovex.de\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#primaryimage"},"image":{"@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#primaryimage"},"thumbnailUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/Cyber_Resilience.png","datePublished":"2026-11-20T11:21:17+00:00","dateModified":"2026-11-20T11:22:06+00:00","description":"Learn how to implement EU regulations\u2014such as NIS-2, DORA, and the CRA\u2014through automation, DevSecOps, and a lean ISMS, fostering genuine technical resilience rather than mere bureaucracy.","breadcrumb":{"@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#primaryimage","url":"https:\/\/www.inovex.de\/wp-content\/uploads\/Cyber_Resilience.png","contentUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/Cyber_Resilience.png","width":1500,"height":880},{"@type":"BreadcrumbList","@id":"https:\/\/www.inovex.de\/en\/blog\/nis-2-dora-cra-pragmatic-cybersecurity-instead-of-paper-based-compliance\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.inovex.de\/en\/"},{"@type":"ListItem","position":2,"name":"NIS-2, DORA &#038; CRA: Pragmatic Cybersecurity Instead of Paper-Based Compliance"}]},{"@type":"WebSite","@id":"https:\/\/www.inovex.de\/en\/#website","url":"https:\/\/www.inovex.de\/en\/","name":"inovex GmbH","description":"","publisher":{"@id":"https:\/\/www.inovex.de\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.inovex.de\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.inovex.de\/en\/#organization","name":"inovex GmbH","url":"https:\/\/www.inovex.de\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.inovex.de\/en\/#\/schema\/logo\/image\/","url":"https:\/\/www.inovex.de\/wp-content\/uploads\/2021\/03\/inovex-logo-16-9-1.png","contentUrl":"https:\/\/www.inovex.de\/wp-content\/uploads\/2021\/03\/inovex-logo-16-9-1.png","width":1921,"height":1081,"caption":"inovex GmbH"},"image":{"@id":"https:\/\/www.inovex.de\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/inovexde","https:\/\/x.com\/inovexgmbh","https:\/\/www.instagram.com\/inovexlife\/","https:\/\/www.linkedin.com\/company\/inovex","https:\/\/www.youtube.com\/channel\/UC7r66GT14hROB_RQsQBAQUQ"]},{"@type":"Person","@id":"https:\/\/www.inovex.de\/en\/#\/schema\/person\/2f7996568e4fb7617d8a58fb6b7581d2","name":"Stephan Auge","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/575feb2af5f2d3c59d587c7401c0572294d08b08418293be7d58013edc25d8c9?s=96&d=retro&r=ge1645902405dbc0156237f84d63cfc2a","url":"https:\/\/secure.gravatar.com\/avatar\/575feb2af5f2d3c59d587c7401c0572294d08b08418293be7d58013edc25d8c9?s=96&d=retro&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/575feb2af5f2d3c59d587c7401c0572294d08b08418293be7d58013edc25d8c9?s=96&d=retro&r=g","caption":"Stephan Auge"},"url":"https:\/\/www.inovex.de\/en\/blog\/author\/sauge\/"}]}},"_links":{"self":[{"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/posts\/71994","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/users\/466"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/comments?post=71994"}],"version-history":[{"count":4,"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/posts\/71994\/revisions"}],"predecessor-version":[{"id":71998,"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/posts\/71994\/revisions\/71998"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/media\/71992"}],"wp:attachment":[{"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/media?parent=71994"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/tags?post=71994"},{"taxonomy":"service","embeddable":true,"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/service?post=71994"},{"taxonomy":"level","embeddable":true,"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/level?post=71994"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.inovex.de\/en\/wp-json\/wp\/v2\/coauthors?post=71994"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}