NIS2_Compliance_Service.md
May 24, 2026 Β· View on GitHub
ποΈ Hack23 AB β NIS2 Directive Compliance Service
π‘οΈ Expert NIS2 Implementation Through Proven ISMS Excellence
π― Transforming Regulatory Obligation Into Competitive Advantage
π Document Owner: CEO | π Version: 1.3 | π
Last Updated: 2026-05-10 (UTC)
π Review Cycle: Semi-Annual | β° Next Review: 2026-11-10
π― Executive Summary
Hack23 AB's NIS2 Directive Compliance Service transforms the complex EU Network and Information Security Directive (2022/2555) into a systematic, transparent implementation roadmap. As the October 2024 enforcement deadline drives urgent compliance demand across 18 critical sectors, our service package leverages our publicly documented ISMS as both proof-of-expertise and compliance templateβenabling faster, more cost-effective NIS2 implementation than traditional consultancies.
π Market Opportunity
The NIS2 Directive represents one of Europe's most comprehensive cybersecurity mandates:
- π Market Size: β¬18B+ estimated compliance spending across EU member states
- πΈπͺ Swedish Impact: 1,000+ essential and important entities requiring compliance
- β‘ Urgency: October 2024 enforcement with penalties up to β¬10M or 2% global revenue
- π― Sectors: 18 critical infrastructure sectors from energy to healthcare to digital services
- π Growth: Expanding regulatory complexity driving 3-5 year compliance lifecycle
π Hack23 Differentiation
Unlike traditional consultancies that conduct NIS2 assessments in isolation, Hack23's transparent ISMS approach provides clients with:
- π Pre-Built Compliance Templates β Our public ISMS policies already address 70-85% of NIS2 requirements
- β‘ Accelerated Implementation β Reduce compliance timeline from 12-18 months to 6-9 months
- π Automated Evidence Generation β GitHub Actions and CI/CD integrations provide continuous compliance monitoring
- π Multi-Framework Alignment β Leverage existing ISO 27001, NIST CSF, CIS Controls investments
- π° Cost Efficiency β 30-40% lower total cost of ownership through template reuse and automation
- π€ Transparent Methodology β Clients see exactly how we achieve compliance in our own operations
β James Pether SΓΆrling, CEO/Founder
π NIS2 Directive Overview
π Regulatory Context
Directive (EU) 2022/2555 (NIS2) enhances cybersecurity requirements for essential and important entities across the European Union, replacing the original NIS Directive (2016/1148).
Key Provisions:
- Article 20: Governance framework and accountability requirements
- Article 21: Ten mandatory cybersecurity risk management measures
- Article 23: Incident reporting obligations (24-hour early warning, 72-hour detailed report)
- Article 28: Supply chain security and supplier relationships
- Article 33: Jurisdiction and enforcement by national cybersecurity authorities
π― Covered Sectors (18 Critical Areas)
Essential Entities (High Criticality)
- π Energy β Electricity, oil, gas, hydrogen, district heating/cooling
- π Transport β Air, rail, water, road
- π¦ Banking β Credit institutions
- π§ Drinking Water β Supply and distribution
- π₯ Healthcare β Hospitals, medical device manufacturers
- π Digital Infrastructure β DNS, TLD registries, cloud computing, data centers, CDNs
- ποΈ Public Administration β Central government, regional government
Important Entities (Medium Criticality)
- π¬ Postal Services β Universal postal service providers
- β»οΈ Waste Management β Collection, treatment, disposal
- π§ͺ Chemical Manufacturing β Production and distribution
- π Food Production β Large-scale food manufacturing
- π Manufacturing β Medical devices, electronics, machinery, vehicles
- π¬ Research Organizations β Research infrastructure
- π Digital Service Providers β Online marketplaces, search engines, social networks
βοΈ Penalties & Enforcement
Financial Penalties:
- Essential Entities: Up to β¬10,000,000 or 2% of global annual turnover (whichever is higher)
- Important Entities: Up to β¬7,000,000 or 1.4% of global annual turnover (whichever is higher)
Additional Consequences:
- Management liability (personal accountability for board members)
- Temporary suspension of certifications
- Temporary prohibition from management positions
- Public disclosure of non-compliance
- Increased regulatory scrutiny and audit frequency
π NIS2 Article 21: Ten Cybersecurity Measures
Mandatory Risk Management Requirements
| Article | Requirement | Hack23 ISMS Alignment | Coverage |
|---|---|---|---|
| Art. 21.2(a) | Risk analysis and information security policies | π Information Security Policy | 90% |
| Art. 21.2(b) | Incident handling | π¨ Incident Response Plan | 85% |
| Art. 21.2(c) | Business continuity and crisis management | π Business Continuity Plan π Disaster Recovery Plan | 90% |
| Art. 21.2(d) | Supply chain security | π€ Third Party Management π’ Supplier Management | 75% |
| Art. 21.2(e) | Security in acquisition, development and maintenance | π οΈ Secure Development Policy | 80% |
| Art. 21.2(f) | Policies on cryptography and encryption | π Cryptography Policy | 95% |
| Art. 21.2(g) | Human resources security | π Information Security Policy Β§ 7.2 β Acceptable Use Policy | 70% |
| Art. 21.2(h) | Access control policies | π Access Control Policy | 95% |
| Art. 21.2(i) | Asset management | π» Asset Register | 90% |
| Art. 21.2(j) | Authentication: MFA, continuous authentication | π Access Control Policy Β§ 4.2 | 100% |
| Art. 21.2(k) | Secure communication: Voice, video, text, encrypted | π Network Security Policy | 85% |
| Art. 21.2(l) | Secure emergency communication systems | π Business Continuity Plan Β§ 5.3 | 80% |
| Art. 21.2(m) | Network security: Segmentation, monitoring | π Network Security Policy | 90% |
π― Hack23 NIS2 Assessment Methodology
π Five-Phase Implementation Framework
%%{
init: {
'theme': 'base',
'themeVariables': {
'primaryColor': '#1565C0',
'primaryTextColor': '#0d47a1',
'lineColor': '#1565C0',
'secondaryColor': '#4CAF50',
'tertiaryColor': '#FF9800'
}
}
}%%
flowchart TD
START(["ποΈ NIS2 Compliance Journey"]) --> PHASE1
subgraph PHASE1["π Phase 1: Scope Determination (3-5 days)"]
S1["π― Identify Sector Classification"]
S2["π Determine Entity Criticality"]
S3["βοΈ Assess Regulatory Obligations"]
S4["π Map Geographic Jurisdictions"]
S1 --> S2 --> S3 --> S4
end
PHASE1 --> DECISION{"ποΈ NIS2<br/>Applicable?"}
DECISION -->|No| EXEMPT["βͺ Not in Scope<br/>Document Exemption Rationale"]
DECISION -->|Yes| PHASE2
subgraph PHASE2["π Phase 2: Gap Analysis (8-12 days)"]
G1["π Inventory Current Controls"]
G2["π Map to Article 21 Requirements"]
G3["π Assess Coverage Percentage"]
G4["π Identify Control Gaps"]
G1 --> G2 --> G3 --> G4
end
PHASE2 --> PHASE3
subgraph PHASE3["β οΈ Phase 3: Risk Assessment (5-8 days)"]
R1["π― Identify NIS2-Specific Threats"]
R2["π Evaluate Risk Likelihood & Impact"]
R3["π° Quantify Business Consequences"]
R4["π Prioritize Risk Treatment"]
R1 --> R2 --> R3 --> R4
end
PHASE3 --> PHASE4
subgraph PHASE4["π οΈ Phase 4: Remediation Roadmap (3-5 days)"]
REM1["π
Define Implementation Timeline"]
REM2["π° Estimate Resource Requirements"]
REM3["π₯ Assign Ownership & Accountability"]
REM4["π― Set Measurable Success Criteria"]
REM1 --> REM2 --> REM3 --> REM4
end
PHASE4 --> PHASE5
subgraph PHASE5["π Phase 5: Documentation Package (5-7 days)"]
D1["π Evidence Collection & Organization"]
D2["π Compliance Report Generation"]
D3["ποΈ Authority-Ready Documentation"]
D4["π Continuous Monitoring Setup"]
D1 --> D2 --> D3 --> D4
end
PHASE5 --> COMPLIANT["β
NIS2 Compliant<br/>Continuous Monitoring Active"]
style START fill:#1565C0,stroke:#0d47a1,stroke-width:3px,color:#fff
style DECISION fill:#FF9800,stroke:#f57c00,stroke-width:3px,color:#fff
style EXEMPT fill:#9E9E9E,stroke:#616161,stroke-width:2px,color:#fff
style COMPLIANT fill:#4CAF50,stroke:#388e3c,stroke-width:3px,color:#fff
style PHASE1 fill:#E3F2FD,stroke:#1565C0,stroke-width:2px
style PHASE2 fill:#E8F5E9,stroke:#4CAF50,stroke-width:2px
style PHASE3 fill:#FFF3E0,stroke:#FF9800,stroke-width:2px
style PHASE4 fill:#F3E5F5,stroke:#7B1FA2,stroke-width:2px
style PHASE5 fill:#E8F5E9,stroke:#2E7D32,stroke-width:2px
π Typical Engagement Timeline
| Phase | Duration | Deliverables | Client Involvement |
|---|---|---|---|
| Phase 1: Scoping | 3-5 days | NIS2 applicability determination, sector classification | High (interviews, documentation) |
| Phase 2: Gap Analysis | 8-12 days | Gap analysis matrix, control coverage report | Medium (policy review, demos) |
| Phase 3: Risk Assessment | 5-8 days | NIS2 risk register, threat scenarios, risk ratings | Medium (risk workshops) |
| Phase 4: Remediation | 3-5 days | Implementation roadmap, resource plan, timeline | Low (validation meetings) |
| Phase 5: Documentation | 5-7 days | Compliance documentation package, monitoring setup | Low (final review) |
| Total | 24-37 days | Complete NIS2 compliance program | Varies by phase |
πΌ Service Packages & Pricing
π¦ Package 1: NIS2 Scoping Assessment
Duration: 3-5 days | Price: β¬4,500 - β¬7,500
Ideal For: Organizations uncertain whether NIS2 applies to their operations
Deliverables:
- β Sector classification analysis
- β Entity criticality determination (Essential vs. Important)
- β Regulatory obligation summary
- β Exemption justification (if applicable)
- β Next steps recommendation
Methodology:
- Review business operations and service portfolio
- Map to NIS2 Annex I and Annex II sector definitions
- Assess size and criticality thresholds
- Determine geographic jurisdiction (Swedish NIS2 law)
- Provide written scoping opinion with regulatory references
π¦ Package 2: NIS2 Gap Assessment
Duration: 8-12 days | Price: β¬12,000 - β¬18,000
Ideal For: Organizations confirmed in scope needing to understand current compliance posture
Deliverables:
- β Complete gap analysis matrix (Article 21 measures vs. current controls)
- β Control coverage percentage by requirement
- β Prioritized gap list with risk ratings
- β Quick win opportunities identification
- β Estimated remediation effort
- β NIS2 vs. ISO 27001 comparison (if applicable)
Methodology:
- Conduct control inventory workshops
- Map existing policies/procedures to NIS2 requirements
- Assess operational effectiveness of controls
- Identify documentation gaps
- Benchmark against Hack23 ISMS reference implementation
- Deliver comprehensive gap analysis report
Add-Ons:
- Incident Response Gap Analysis: +β¬2,500 (24/72-hour reporting readiness)
- Supply Chain Assessment: +β¬3,500 (vendor NIS2 compliance evaluation)
π¦ Package 3: NIS2 Compliance Roadmap
Duration: 16-24 days | Price: β¬24,000 - β¬36,000
Includes: Scoping + Gap Assessment + Risk Assessment + Remediation Planning
Ideal For: Organizations requiring end-to-end compliance strategy
Deliverables:
- β Complete NIS2 gap analysis
- β NIS2-specific risk register with threat scenarios
- β Detailed implementation roadmap (6-18 month timeline)
- β Resource requirements and budget estimates
- β Policy templates adapted from Hack23 ISMS
- β Incident reporting procedure (24/72-hour timelines)
- β Management presentation deck
Methodology:
- Execute Phase 1-4 of assessment methodology
- Conduct risk workshops using NIS2 threat scenarios
- Develop prioritized remediation backlog
- Create implementation timeline with dependencies
- Provide customized policy templates
- Deliver management readiness briefing
π¦ Package 4: Full NIS2 Implementation Support
Duration: 40-80 days (6-12 months elapsed) | Price: β¬60,000 - β¬120,000
Includes: Complete end-to-end NIS2 compliance implementation
Ideal For: Organizations needing hands-on implementation guidance and validation
Deliverables:
- β All deliverables from Package 3
- β Hands-on implementation support and validation
- β Policy and procedure documentation
- β Control implementation validation
- β Evidence package for authorities
- β Incident response playbook
- β Supply chain security framework
- β Management governance structure
- β Authority-ready compliance report
- β Continuous monitoring setup via GitHub Actions and CI/CD
- β 6-month post-implementation support
Methodology:
- Execute all five phases of assessment methodology
- Provide ongoing implementation guidance and validation
- Review and approve all compliance documentation
- Conduct tabletop exercises for incident response
- Validate control effectiveness through testing
- Prepare authority-ready compliance evidence
- Establish continuous compliance monitoring
- Provide ongoing support during initial operating period
Add-Ons:
- Mock Authority Audit: +β¬8,000 (simulated regulatory inspection)
- Continuous Monitoring (Annual): β¬18,000/year (automated compliance tracking)
- Quarterly Compliance Reviews: β¬6,000/quarter (ongoing assurance)
π NIS2 vs. Hack23 ISMS: Gap Analysis Matrix
π Comprehensive Requirements Mapping
The following matrix demonstrates how Hack23's existing ISMS already addresses 70-90% of NIS2 requirements, enabling faster client implementations:
| NIS2 Article | Requirement | ISMS Policy | Coverage | Gap | Priority | Effort |
|---|---|---|---|---|---|---|
| 21.2(a) | Risk analysis & security policies | Information Security Policy | 90% | NIS2-specific risk scenarios | Medium | 2-3 days |
| 21.2(b) | Incident handling | Incident Response Plan | 85% | 24/72-hour reporting timelines | High | 3-5 days |
| 21.2(c) | Business continuity, crisis, disaster recovery | Business Continuity Plan Disaster Recovery Plan | 90% | NIS2 scenario testing | Medium | 2-3 days |
| 21.2(d) | Supply chain security | Third Party Management | 75% | NIS2 supplier requirements | High | 5-7 days |
| 21.2(e) | Security in acquisition & development | Secure Development Policy | 80% | NIS2 procurement standards | Medium | 3-4 days |
| 21.2(f) | Cryptography policies | Cryptography Policy | 95% | Minor alignment | Low | 1-2 days |
| 21.2(g) | Human resources security | Information Security Policy Β§ 7.2 | 70% | Expand training requirements | High | 4-6 days |
| 21.2(h) | Access control policies | Access Control Policy | 95% | NIS2 privileged access | Low | 1-2 days |
| 21.2(i) | Asset management | Asset Register | 90% | NIS2 critical asset classification | Medium | 2-3 days |
| 21.2(j) | Authentication (MFA, continuous) | Access Control Policy Β§ 4.2 | 100% | Fully compliant | None | 0 days |
| 21.2(k) | Secure communications | Network Security Policy Β§ 4.5 | 85% | Voice/video encryption standards | Medium | 2-3 days |
| 21.2(l) | Secure emergency communications | Business Continuity Plan Β§ 5.3 | 80% | Emergency system redundancy | Medium | 3-4 days |
| 21.2(m) | Network security (segmentation) | Network Security Policy | 90% | NIS2 segmentation requirements | Low | 2-3 days |
| Art. 20 | Governance framework | Information Security Policy Β§ 4 | 85% | Board reporting structure | Medium | 2-3 days |
| Art. 23 | Incident reporting (24/72h) | Incident Response Plan | 75% | Authority notification procedures | High | 4-5 days |
| Art. 28 | Supply chain reporting | Third Party Management Β§ 6 | 70% | Supplier incident disclosure | High | 3-4 days |
π Overall ISMS Coverage: 82% average across all NIS2 requirements
π‘ Key Insight: Organizations starting with Hack23's ISMS templates can reduce NIS2 compliance implementation time by 40-50% compared to building from scratch.
π Hack23 Competitive Advantage
π Differentiation Strategy
| Factor | Traditional Consultancy | Hack23 Advantage |
|---|---|---|
| Transparency | Proprietary methodologies | Public ISMS as reference implementation |
| Speed | 12-18 month implementation | 6-9 month implementation (50% faster) |
| Cost | β¬150K-300K typical engagement | β¬60K-120K full implementation (50% savings) |
| Delivery Model | Multi-consultant teams (PM + analysts + auditors) with associated overhead | Single-CEO delivery augmented by specialist Copilot agents (compliance-reviewer, risk-assessment-specialist, security-documentation-specialist) per Information Security Strategy Β§ AI-Enabled Operations β <1 FTE overhead, faster turnaround, fully transparent agent-generated evidence chain |
| Templates | Generic templates | Battle-tested ISMS policies (35+ documents) |
| Automation | Manual evidence collection | GitHub Actions and CI/CD continuous monitoring |
| Multi-Framework | Single-framework focus | ISO 27001 + NIST + CIS + NIS2 alignment |
| Cloud Expertise | Generic infrastructure | AWS Well-Architected + cloud-native security |
| Evidence | Black box assessment | Transparent methodology + GitHub CI/CD validation |
π‘ Client Success Factors
Why Hack23 NIS2 Services Deliver Superior Outcomes:
- π Proven Methodology β Our ISMS is ISO 27001-aligned and publicly validated through CI/CD
- β‘ Rapid Implementation β Pre-built templates eliminate 40-50% of documentation work
- π Automated Compliance β GitHub Actions and CI/CD provides continuous evidence generation
- π Multi-Framework Synergy β Leverage existing ISO 27001, SOC 2, or GDPR investments
- βοΈ Cloud-Native Excellence β Deep AWS expertise for modern infrastructure compliance
- π€ Transparent Partnership β Clients see exactly how we achieve compliance internally
- π° Cost Efficiency β Lower total cost of ownership through automation and templates
- π― Sector Expertise β Specialized knowledge in digital infrastructure, cloud, and technology sectors
π― Target Market Segments
Priority Sectors (High Opportunity)
1. π Digital Infrastructure Providers
Entities: Cloud service providers, data centers, DNS providers, CDN operators, managed service providers
Why High Priority:
- Core Hack23 expertise in cloud architecture and AWS
- Typically technology-forward organizations receptive to automation
- Often already have partial ISO 27001 or SOC 2 compliance
- High compliance urgency due to essential entity classification
Expected Engagement: Full Implementation (β¬60K-120K)
2. π¦ Financial Services (Banking & FinTech)
Entities: Banks, payment processors, cryptocurrency exchanges, lending platforms, insurance companies
Why High Priority:
- Already familiar with regulatory compliance (PSD2, GDPR, AML)
- High budget allocation for cybersecurity
- Strong business case for NIS2 compliance (customer trust)
- Typically require comprehensive documentation and evidence
Expected Engagement: Compliance Roadmap or Full Implementation (β¬24K-120K)
3. π₯ Healthcare & Medical Devices
Entities: Hospitals, clinics, pharmaceutical manufacturers, medical device manufacturers, telemedicine platforms
Why High Priority:
- Critical infrastructure designation drives urgency
- Often lack mature security programs (focus on patient care)
- Regulatory intersection with Medical Device Regulation (MDR)
- High penalties and reputational risk
Expected Engagement: Full Implementation (β¬60K-120K)
4. π Transport & Logistics
Entities: Airlines, railway operators, shipping companies, logistics platforms, port authorities
Why High Priority:
- Essential entity classification with strict requirements
- Increasing digitalization creating compliance gaps
- Often legacy IT systems requiring modernization
- Cross-border operations requiring multi-jurisdiction compliance
Expected Engagement: Compliance Roadmap (β¬24K-36K)
Secondary Sectors (Medium Opportunity)
5. ποΈ Public Administration
Entities: Government agencies, municipalities, public utilities, regulatory bodies
Why Medium Priority:
- Built-in budget for compliance
- Procurement process complexity extends sales cycles
- Opportunity for long-term framework agreements
- Citizen Intelligence Agency provides relevant reference
Expected Engagement: Gap Assessment or Compliance Roadmap (β¬12K-36K)
6. π¬ Research & Education
Entities: Universities, research institutes, national labs, medical research organizations
Why Medium Priority:
- Important entity classification (lower penalties)
- Limited budgets but strong compliance motivation
- Often part of larger government/EU funding ecosystems
- Opportunity for academic partnerships
Expected Engagement: Gap Assessment (β¬12K-18K)
π’ Go-to-Market Strategy
π― Sales & Marketing Approach
Content Marketing (Lead Generation)
Blog Post Series (Q1 2026):
-
"NIS2 Compliance Explained: What Swedish Organizations Need to Know"
- Target: General awareness and SEO
- CTA: Download NIS2 Scoping Checklist
-
"The True Cost of NIS2 Non-Compliance: Beyond the Fines"
- Target: C-level decision makers
- CTA: Schedule NIS2 Scoping Assessment
-
"NIS2 and ISO 27001: Leveraging Your Existing ISMS for Faster Compliance"
- Target: Security practitioners
- CTA: Request Gap Analysis Quote
-
"Incident Reporting Under NIS2: Mastering the 24/72-Hour Timeline"
- Target: CISO and incident response teams
- CTA: Download Incident Response Template
-
"Supply Chain Security: Meeting NIS2 Article 28 Requirements"
- Target: Procurement and risk management
- CTA: Request Third-Party Assessment
Webinar Series (Q1-Q2 2026):
- "NIS2 Readiness: A 45-Minute Executive Briefing" (monthly)
- "Hands-On: Building Your NIS2 Compliance Roadmap" (quarterly)
- "NIS2 vs. ISO 27001: Integration Strategies" (quarterly)
Direct Outreach
Target Account List (Top 100 Swedish Companies):
- Digital infrastructure: 20 companies (cloud, hosting, SaaS)
- Financial services: 25 companies (banks, payment, fintech)
- Healthcare: 20 companies (hospitals, pharma, medtech)
- Transport: 15 companies (airlines, rail, shipping)
- Public sector: 20 entities (agencies, municipalities)
Outreach Strategy:
- LinkedIn connection + personalized message
- Email with NIS2 sector-specific one-pager
- Phone follow-up offering free 30-minute consultation
- Send Hack23 ISMS as reference implementation
- Propose Scoping Assessment (β¬4,500-7,500 entry point)
Partnership Development
Strategic Partners:
- Legal Firms: Partner with law firms advising on NIS2 (referral agreements)
- System Integrators: Provide security expertise for infrastructure projects
- Industry Associations: Speak at Svensk Energi, Finansiell ID-teknik, SKR events
- AWS: Leverage AWS Partner Network for cloud customer referrals
- Compliance Software Vendors: Integration partnerships for tool ecosystem
π° Revenue Projections
π Conservative Forecast (2025-2027)
| Year | Scoping | Gap Assessment | Roadmap | Full Implementation | Annual Revenue |
|---|---|---|---|---|---|
| 2025 | 8 Γ β¬6K | 5 Γ β¬15K | 3 Γ β¬30K | 1 Γ β¬90K | β¬303K |
| 2026 | 15 Γ β¬6K | 10 Γ β¬15K | 8 Γ β¬30K | 4 Γ β¬90K | β¬900K |
| 2027 | 20 Γ β¬6K | 15 Γ β¬15K | 12 Γ β¬30K | 6 Γ β¬90K | 1,425K |
Total 3-Year Revenue: β¬2.6M from NIS2 services
π― Success Metrics
Q4 2025 Targets:
- β 5 completed NIS2 assessments
- β β¬150K+ NIS2 revenue
- β 3 case studies published
- β 50+ qualified NIS2 prospects in pipeline
2026 Targets:
- β 20+ completed NIS2 projects
- β β¬600K+ NIS2 revenue
- β 40% of consulting revenue from NIS2
- β 10+ long-term compliance monitoring clients
- β NIS2 market leadership in Sweden (top 3 providers)
π Related Documents
π― Strategic & Governance
- π― Information Security Strategy β AI-first operations, Pentagon framework, and strategic NIS2 direction
- π Information Security Policy β Master security governance framework with AI-First Operations Governance
- π€ AI Policy β AI-assisted NIS2 compliance assessment and automation
- β Compliance Checklist β Multi-framework compliance mapping including NIS2
- π Risk Register β Risk assessment and treatment
- π Risk Assessment Methodology β Systematic risk analysis process
- π― SWOT Strategic Analysis β Strategic opportunity analysis for NIS2 market
π Security Policies & Controls
- π¨ Incident Response Plan β Incident handling procedures (NIS2 Art. 21.2(b))
- π Business Continuity Plan β Business continuity and crisis management (NIS2 Art. 21.2(c))
- π Disaster Recovery Plan β Technical recovery procedures
- π€ Third Party Management β Supply chain security (NIS2 Art. 21.2(d), Art. 28)
- π’ Supplier Management β Detailed supplier assessments and evidence
- π οΈ Secure Development Policy β Security in acquisition and development (NIS2 Art. 21.2(e))
- π Cryptography Policy β Encryption standards (NIS2 Art. 21.2(f))
- π Access Control Policy β Authentication and access control (NIS2 Art. 21.2(h), 21.2(j))
- π Network Security Policy β Network security and segmentation (NIS2 Art. 21.2(k), 21.2(m))
βοΈ Operational Integration
- π» Asset Register β Asset management (NIS2 Art. 21.2(i))
π Document Control:
β
Approved by: James Pether SΓΆrling, CEO
π€ Distribution: Public (Service Offering)
π·οΈ Classification:
π
Effective Date: 2026-05-10
β° Next Review: 2026-11-10
π― Framework Compliance: