Riksdagsmonitor Intelligence Platform โ€” API Documentation - v1.0.102
    Preparing search index...

    Hack23 Logo

    ๐Ÿ›ก๏ธ Riksdagsmonitor โ€” CRA Conformity Assessment

    Evidence-Driven Conformity Through Systematic Assessment
    Demonstrating CRA Compliance for Swedish Parliament Intelligence Platform

    Owner Version Effective Date Review Cycle

    ๐Ÿ“‹ Document Owner: CEO | ๐Ÿ“„ Version: 1.4 | ๐Ÿ“… Last Updated: 2026-05-06 (UTC) ๐Ÿ”„ Review Cycle: Quarterly | โฐ Next Review: 2026-08-06 ๐Ÿข Owner: Hack23 AB (Org.nr 5595347807) | ๐Ÿท๏ธ Classification: Public


    Hack23 AB's CRA conformity assessment process demonstrates how systematic regulatory compliance directly enables business growth rather than creating operational burden. This assessment documents Riksdagsmonitor's compliance with the EU Cyber Resilience Act (CRA), providing evidence-based self-assessment of cybersecurity requirements for our Swedish Parliament intelligence platform.

    As a cybersecurity consulting company, our approach to CRA compliance becomes a showcase of professional implementation, demonstrating to potential clients how systematic regulatory adherence creates competitive advantages through robust security foundations while enabling EU market access.

    โ€” James Pether Sรถrling, CEO/Founder


    This process provides a concise, repeatable CRA Conformity Assessment for Riksdagsmonitor. Aligns with CRA Annex I & V, Hack23 classification, secure development, and transparency policies.

    Scope: Riksdagsmonitor platform within Asset Register requiring EU market placement.

    Process Alignment: This assessment follows the CRA Conformity Assessment Process template and is governed by the Open Source Policy for open source compliance requirements.


    Document Focus Description
    ๐Ÿ›๏ธ Architecture ๐Ÿ—๏ธ C4 Models System context, containers, components
    ๐Ÿ“Š Data Model ๐Ÿ“Š Data Entity relationships and data dictionary
    ๐Ÿ”„ Flowchart ๐Ÿ”„ Processes Business process and data flows
    ๐Ÿ“ˆ State Diagram ๐Ÿ“ˆ States System state transitions and lifecycles
    ๐Ÿง  Mindmap ๐Ÿง  Concepts System conceptual relationships
    ๐Ÿ’ผ SWOT ๐Ÿ’ผ Strategy Strategic analysis and positioning
    ๐Ÿ”ง Workflows ๐Ÿ”ง DevOps CI/CD automation and pipelines
    ๐Ÿ›ก๏ธ Security Architecture ๐Ÿ”’ Security Current security controls and design
    ๐ŸŽฏ Threat Model ๐ŸŽฏ Threats STRIDE/MITRE ATT&CK analysis
    ๐Ÿ›ก๏ธ CRA Assessment โญ โš–๏ธ Compliance EU Cyber Resilience Act conformity

    The following Hack23 AB projects demonstrate completed CRA assessments:

    ๐Ÿš€ Project ๐Ÿ“ฆ Product Type ๐Ÿท๏ธ CRA Classification ๐Ÿ“‹ Assessment Status ๐Ÿ”— Reference Link
    ๐Ÿ•ต๏ธ CIA (Citizen Intelligence Agency) Political transparency platform Standard (Non-commercial OSS) โœ… Complete ๐Ÿ“„ CRA Assessment
    โšซ Black Trigram Korean martial arts game Standard (Non-commercial OSS) โœ… Complete ๐Ÿ“„ CRA Assessment
    ๐Ÿ›ก๏ธ CIA Compliance Manager Compliance automation tool Standard (Non-commercial OSS) โœ… Complete ๐Ÿ“„ CRA Assessment
    ๐Ÿ—ณ๏ธ Riksdagsmonitor Parliament intelligence platform Standard (Non-commercial OSS) โœ… This Document ๐Ÿ“„ CRA Assessment

    Supports CRA Annex V ยง 1 - Product Description Requirements

    Field Value
    ๐Ÿ“ฆ Product Riksdagsmonitor
    ๐Ÿท๏ธ Version Tag 0.4.1 (reflects current project state)
    ๐Ÿ”— Repository https://github.com/Hack23/riksdagsmonitor
    ๐Ÿ“ง Security Contact security@hack23.org
    ๐ŸŒ Website https://riksdagsmonitor.com
    ๐ŸŽฏ Purpose (1โ€“2 lines) Static HTML/CSS intelligence platform monitoring Swedish Parliament (Riksdag) activity, providing 14-language dashboards with 50+ years of political data through CIA platform integration and automated news generation

    ๐Ÿ“‹ Evidence Links:

    • ๐Ÿ—๏ธ System Architecture: ARCHITECTURE.md โ€” Complete C4 model architecture
    • ๐Ÿ” Security Architecture: SECURITY_ARCHITECTURE.md โ€” Defense-in-depth security controls
    • ๐Ÿ›ก๏ธ Future Security Vision: FUTURE_SECURITY_ARCHITECTURE.md โ€” Security roadmap
    • ๐Ÿ“Š Data Architecture: DATA_MODEL.md โ€” Data structures, schemas, relationships
    • ๐Ÿ”„ Process Workflows: FLOWCHART.md โ€” Data processing and CI/CD workflows
    • ๐Ÿง  System Overview: MINDMAP.md โ€” Conceptual system relationships
    • ๐ŸŽฏ Strategic Analysis: SWOT.md โ€” Strategic assessment
    • ๐ŸŽฏ Threat Analysis: THREAT_MODEL.md โ€” STRIDE and MITRE ATT&CK mapping
    • ๐Ÿ”ง CI/CD Pipelines: WORKFLOWS.md โ€” 43 workflow automation documentation

    ๐Ÿ“Š Project Status & Quality Badges:

    GitHub Release OpenSSF Scorecard

    Quality Checks CodeQL TypeScript & JavaScript Testing

    ๐Ÿ“‹ Data Sources Evidence:

    • ๐Ÿ›๏ธ Swedish Parliament: data.riksdagen.se โ€” Parliamentary members, committees, documents, votes
    • ๐Ÿ—ณ๏ธ Election Authority: val.se โ€” Election data, parties, voting results
    • ๐Ÿ“Š SCB (Statistics Sweden): scb.se โ€” PxWebAPI 2.0 (scb-mcp) โ€” official Swedish statistics (economy, labour, population, education, environment)
    • ๐ŸŒ World Bank Open Data: data.worldbank.org โ€” WGI governance, environment, long-horizon social/education (world-bank-mcp)
    • ๐ŸŒ IMF Open Data: data.imf.org โ€” macro/fiscal/monetary/external-sector freshness + T+5 projections (WEO, Fiscal Monitor, IFS, GFS_COFOG); consumed via pure-TypeScript client scripts/imf-client.ts (Datamapper JSON + SDMX 3.0) โ€” not an MCP server, SBOM-covered via npm (ADR 0001)
    • ๐Ÿ•ต๏ธ CIA Platform: Citizen Intelligence Agency โ€” 19 intelligence products, risk assessments, analytics

    Supports CRA Article 6 - Scope and Article 7 - Product Classification Assessment

    Non-commercial OSS

    Community

    Standard

    ๐Ÿ“ CRA Scope Justification: Riksdagsmonitor is a non-commercial open-source static website providing Swedish Parliament transparency services through data visualization and news generation. As a volunteer-driven initiative with community distribution via GitHub under Apache 2.0 license, it falls under non-commercial OSS with Standard CRA classification enabling self-assessment approach. The static site architecture (HTML/CSS/JS with no server-side execution) significantly reduces the attack surface compared to traditional web applications.

    ๐Ÿ“‹ Classification Evidence:

    ๐Ÿ” Classification Impact:

    • Standard: Self-assessment approach (this document provides evidence)
    • Class I/II: Would require notified body assessment + additional documentation

    Supports CRA Annex V ยง 2 - Technical Documentation Requirements

    ๐Ÿ—๏ธ CRA Technical Area ๐Ÿ“ Implementation Summary ๐Ÿ“‹ Evidence Location
    ๐ŸŽจ Product Architecture (Annex V ยง 2.1) Static HTML/CSS website with C4 architecture model. Deployed on AWS CloudFront (us-east-1 primary, eu-west-1 replica) with GitHub Pages DR. 14-language support, Chart.js/D3.js dashboards ARCHITECTURE.md + SECURITY_ARCHITECTURE.md + MINDMAP.md
    ๐Ÿ“ฆ SBOM & Components (Annex I ยง 1.1) npm package management with package-lock.json. Dependabot automated dependency scanning. OpenSSF Scorecard monitoring. News pipeline additions (2026 Q1): unified, remark-parse, remark-gfm, remark-rehype, rehype-raw, rehype-sanitize, rehype-slug, rehype-autolink-headings, rehype-stringify, gray-matter โ€” all npm-managed, version-pinned in package-lock.json, Dependabot-grouped under dependencies. mermaid loaded as ESM from the same package for client-side diagram rendering (strict-mode; no eval). package.json + Dependabot Config + OpenSSF Scorecard
    ๐Ÿ” Cybersecurity Controls (Annex I ยง 1.2) Static site architecture (no server-side execution), HTTPS-only via CloudFront/GitHub Pages, CSP headers, SRI for CDN assets, SHA-pinned GitHub Actions, step-security/harden-runner. News pipeline additions: rehype-sanitize allow-list enforced at the trust boundary between AI-authored markdown and published HTML; Mermaid rendered in securityLevel: 'strict' (no eval, no click handlers); SHA-256 manifest in .manifest.json sibling to each article.md for tamper detection. Agentic control-plane additions (v0.9.40): 23 required analysis artifacts, analysis gate checks 1โ€“9b, methodology-reflection validator, safe-output PR boundary, Squid + iptables egress firewall. SECURITY_ARCHITECTURE.md ยงPolitical Intelligence Security Surface + THREAT_MODEL.md TB-PI series
    ๐Ÿ›ก๏ธ Supply Chain Security (Annex I ยง 1.3) SHA-pinned GitHub Actions, Dependabot automation, OpenSSF Scorecard monitoring, CodeQL analysis, dependency review workflow, step-security/harden-runner egress auditing WORKFLOWS.md + OpenSSF Scorecard
    ๐Ÿ”„ Update Mechanism (Annex I ยง 1.4) Automated CI/CD pipeline via GitHub Actions with security scanning (CodeQL, dependency review), dual deployment (S3 + GitHub Pages), version management via release workflow WORKFLOWS.md + Release Workflow
    ๐Ÿ“Š Security Monitoring (Annex I ยง 1.5) GitHub Security Dashboard (code scanning, secret scanning, Dependabot alerts), Lighthouse CI performance monitoring, uptime monitoring, AWS CloudWatch/CloudFront metrics SECURITY_ARCHITECTURE.md + WORKFLOWS.md
    ๐Ÿท๏ธ Data Protection (Annex I ยง 2.1) No personal data collection. Public political data only. GDPR compliant by design โ€” static site with no user accounts, no cookies, no tracking. All data sourced from public government APIs DATA_MODEL.md + THREAT_MODEL.md
    ๐Ÿ“š User Guidance (Annex I ยง 2.2) Comprehensive README with deployment instructions, architecture documentation, security configuration guides README.md + ARCHITECTURE.md + SECURITY_ARCHITECTURE.md
    ๐Ÿ” Vulnerability Disclosure (Annex I ยง 2.3) Public vulnerability disclosure policy via GitHub Security Advisories, coordinated disclosure process, 48h acknowledgment timeline SECURITY.md + Security Advisories

    ๐Ÿ“‹ Comprehensive ISMS Integration:


    Supports CRA Annex V ยง 3 - Risk Assessment Documentation

    Reference: ๐Ÿ“Š Risk Assessment Methodology and โš ๏ธ Risk Register

    ๐Ÿšจ CRA Risk Category ๐ŸŽฏ Asset ๐Ÿ“Š Likelihood ๐Ÿ’ฅ Impact (C/I/A) ๐Ÿ›ก๏ธ CRA Control Implementation โš–๏ธ Residual ๐Ÿ“‹ Evidence
    Supply Chain Attack (Art. 11) Build pipeline & npm dependencies M H/H/M SHA-pinned GitHub Actions + Dependabot automation + step-security/harden-runner egress audit + OpenSSF Scorecard monitoring + dependency review workflow L WORKFLOWS.md + OpenSSF Scorecard
    Website Defacement (Art. 11) Static website content & dashboards M M/H/M Branch protection rules + required PR reviews + CodeQL scanning + dual deployment (S3 + GitHub Pages) for DR L SECURITY_ARCHITECTURE.md + THREAT_MODEL.md
    Data Integrity Attack (Art. 11) Political data & news content M L/H/M CIA data validation schemas + automated translation validation + multi-source data verification + git-based audit trail L DATA_MODEL.md + WORKFLOWS.md
    AI Content Manipulation (Art. 11) AI-authored analysis artifacts โ†’ rendered news HTML M M/H/L rehype-sanitize allow-list at trust boundary (blocks <script>, <iframe>, inline handlers, javascript: URIs); Mermaid rendered in securityLevel: 'strict' (no eval); SHA-256 manifest per article for tamper detection; analysis gate checks 1โ€“9b; methodology-reflection validator; 23-artifact completeness gate; mandatory human PR review M SECURITY_ARCHITECTURE.md ยงPolitical Intelligence Security Surface + THREAT_MODEL.md TB-PI series + WORKFLOWS.md
    CDN/Infrastructure Compromise (Art. 11) CloudFront distribution & S3 storage L M/H/H AWS multi-region deployment + SRI for CDN assets + GitHub Pages DR failover + HTTPS-only + TLS 1.3 L SECURITY_ARCHITECTURE.md + ARCHITECTURE.md
    Component Vulnerability (Art. 11) npm dependencies (Chart.js, D3.js, Vite) M M/H/M Dependabot updates + CodeQL scanning + dependency review workflow + SRI hashes for CDN assets L Security Scanning + Dependabot

    โš–๏ธ CRA Risk Statement: LOW โ€” Static site architecture eliminates entire categories of server-side vulnerabilities. Comprehensive security controls and evidence-based monitoring support CRA essential cybersecurity requirements. โœ… Risk Acceptance: James Sรถrling, CEO Hack23 AB โ€” February 2026

    ๐Ÿ“‹ Risk Management Framework Evidence:


    Supports CRA Annex I - Essential Requirements Self-Assessment

    ๐Ÿ“‹ CRA Annex I Requirement โœ… Status ๐Ÿ“‹ Implementation Evidence
    ๐Ÿ›ก๏ธ ยง 1.1 - Secure by Design [x] Defense-in-depth Architecture โ€” Static site architecture eliminates server-side attack vectors. CSP headers, SRI hashes, HTTPS-only, multi-region deployment
    ๐Ÿ”’ ยง 1.2 - Secure by Default [x] Static HTML/CSS with no server-side execution. No user accounts, no cookies, no tracking. Security Architecture documents secure defaults
    ๐Ÿท๏ธ ยง 2.1 - Personal Data Protection [x] No personal data collection โ€” GDPR compliant by design. Public political data only. Data Model documents data handling
    ๐Ÿ” ยง 2.2 - Vulnerability Disclosure [x] SECURITY.md with GitHub Security Advisories, coordinated disclosure, 48h acknowledgment. Vulnerability Management
    ๐Ÿ“ฆ ยง 2.3 - Software Bill of Materials [x] package.json + package-lock.json provide complete dependency inventory. Dependabot provides continuous SCA
    ๐Ÿ” ยง 2.4 - Secure Updates [x] Automated CI/CD pipeline with CodeQL, dependency review, SHA-pinned actions. WORKFLOWS.md documents 43 workflows
    ๐Ÿ“Š ยง 2.5 - Security Monitoring [x] GitHub Security Dashboard (code scanning, secret scanning, Dependabot), Lighthouse CI, uptime monitoring. SECURITY_ARCHITECTURE.md
    ๐Ÿ“š ยง 2.6 - Security Documentation [x] Complete architecture documentation portfolio: ARCHITECTURE.md, SECURITY_ARCHITECTURE.md, THREAT_MODEL.md, DATA_MODEL.md + 6 future-state documents

    ๐ŸŽฏ CRA Self-Assessment Status: EVIDENCE_DOCUMENTED

    ๐Ÿ” Security Implementation Evidence:

    • ๐Ÿ›ก๏ธ Static Site Security: No server-side code execution eliminates SQL injection, RCE, SSRF, and authentication bypass vulnerabilities
    • ๐Ÿ”’ Transport Security: HTTPS-only via AWS CloudFront (TLS 1.3) and GitHub Pages
    • ๐Ÿ“Š Supply Chain: SHA-pinned GitHub Actions, Dependabot, CodeQL, step-security/harden-runner
    • ๐Ÿ” Content Integrity: Subresource Integrity (SRI) for CDN-loaded Chart.js and D3.js libraries

    Supports CRA Article 19 - Conformity Assessment Documentation

    Reference: ๐Ÿ› ๏ธ Secure Development Policy

    ๐Ÿงช Control ๐ŸŽฏ Requirement โœ… Implementation ๐Ÿ“‹ Evidence
    ๐Ÿงช Unit Testing Comprehensive test coverage โœ… Implemented Vitest โ€” 7,500+ tests across 237 test files
    ๐ŸŒ E2E Testing Critical user journeys validated โœ… Implemented Cypress E2E โ€” Multi-language homepage, dashboard, accessibility
    ๐Ÿ” SAST Scanning Zero critical/high vulnerabilities โœ… Implemented CodeQL Analysis
    ๐Ÿ“ฆ SCA Scanning Zero critical unresolved dependencies โœ… Implemented Dependabot Alerts + Dependency Review
    ๐Ÿ”’ Secret Scanning Zero exposed secrets/credentials โœ… Implemented GitHub Secret Scanning + Push protection enabled
    ๐Ÿ“Š Quality Gates HTML validation + link checking โœ… Implemented Quality Checks โ€” HTMLHint + linkinator
    ๐Ÿ” Supply Chain SHA-pinned actions + egress audit โœ… Implemented OpenSSF Scorecard + step-security/harden-runner
    ๐Ÿ“ˆ Performance Lighthouse CI monitoring โœ… Implemented Lighthouse CI โ€” Core Web Vitals tracking

    ๐Ÿ” Supply Chain Security: OpenSSF Scorecard

    ๐Ÿ›ก๏ธ Security Scanning: CodeQL Dependency Review Scorecards

    ๐Ÿ“Š Quality & Testing: Quality Checks TypeScript & JavaScript Testing

    โš–๏ธ License: license


    7๏ธโƒฃ Post-Market Surveillance

    Supports CRA Article 23 - Obligations of Economic Operators

    Reference: ๐ŸŒ ISMS Transparency Plan and ๐Ÿ“Š Security Metrics

    ๐Ÿ“ก CRA Monitoring Obligation ๐Ÿ”ง Implementation โฑ๏ธ Frequency ๐ŸŽฏ Action Trigger ๐Ÿ“‹ Evidence
    ๐Ÿ” Vulnerability Monitoring (Art. 23.1) Dependabot + GitHub advisories + CodeQL scanning + dependency review Continuous Auto-create security issues and PRs Dependabot Alerts + Security Advisories
    ๐Ÿšจ Incident Reporting (Art. 23.2) GitHub Security Dashboard + AWS CloudWatch + CloudFront access logs Real-time ENISA 24h notification prep via ISMS incident response SECURITY.md + Incident Response Plan
    ๐Ÿ“Š Security Posture Tracking (Art. 23.3) OpenSSF Scorecard + Lighthouse CI + uptime monitoring Weekly/Daily Score decline investigation via automated alerts OpenSSF Scorecard
    ๐Ÿ”„ Update Distribution (Art. 23.4) Automated GitHub releases + dual deployment (S3 + GitHub Pages) + CI/CD pipeline As needed Critical vulnerability patches via secure CI/CD pipeline Release Management + WORKFLOWS.md

    ๐Ÿ“‹ CRA Reporting Readiness: Documentation and procedures prepared for ENISA incident reporting per ๐Ÿšจ Incident Response Plan

    ๐Ÿ”— ISMS Monitoring Integration:


    Supports CRA Article 28 - EU Declaration of Conformity

    ๐Ÿข Manufacturer: Hack23 AB, Gothenburg, Sweden ๐Ÿ“ฆ Product: Riksdagsmonitor v0.9.40 ๐Ÿ“‹ CRA Compliance: Self-assessment documentation supporting CRA essential cybersecurity requirements evaluation ๐Ÿ” Assessment: Self-assessment documentation per Article 24 (non-commercial OSS with standard classification) ๐Ÿ“Š Standards: ISO/IEC 27001 security framework + OWASP web security guidelines + NIST SSDF secure development

    ๐Ÿ“… Date & Signature: 2026-05-06 โ€” James Sรถrling, CEO Hack23 AB

    ๐Ÿ“‚ Technical Documentation: This assessment + evidence bundle supports CRA Annex V technical documentation requirements


    Supports CRA Article 16 - Quality Management System Documentation

    Overall CRA Documentation Status: EVIDENCE_DOCUMENTED

    Key CRA Documentation Areas:

    • โœ… Annex I essential requirements documented with comprehensive evidence links
    • โœ… Annex V technical documentation comprehensively structured
    • โœ… Article 11 security measures implemented and documented
    • โœ… Article 23 post-market surveillance procedures operational

    Static Site Security Advantage: Riksdagsmonitor's static site architecture provides inherent security benefits:

    • No server-side code execution (eliminates SQL injection, RCE, SSRF)
    • No user authentication/session management (eliminates authentication bypass, session hijacking)
    • No database (eliminates data breach risks)
    • No cookies/tracking (GDPR compliant by design)
    • CDN-distributed content (inherent DDoS resilience)
    ๐Ÿ‘ค Role ๐Ÿ“ Name ๐Ÿ“… Date โœ๏ธ Assessment Attestation
    ๐Ÿ”’ CRA Security Assessment James Sรถrling 2026-05-06 Essential requirements documented with comprehensive evidence
    ๐ŸŽฏ Product Responsibility James Sรถrling 2026-05-06 Technical documentation complete and publicly accessible
    โš–๏ธ Legal Compliance Review James Sรถrling 2026-05-06 EU regulatory documentation requirements satisfied

    ๐Ÿ“Š CRA Assessment Status: SELF_ASSESSMENT_DOCUMENTED


    Per CRA Article 15 - Substantial Modification

    CRA assessment updated only when changes constitute "substantial modification" under CRA:

    1. ๐Ÿ—๏ธ Security Architecture Changes: New trust boundaries, encryption, or deployment topology
    2. ๐Ÿ›ก๏ธ Essential Requirement Impact: Changes affecting Annex I compliance
    3. ๐Ÿ“ฆ Critical Dependencies: New supply chain components with security implications (e.g., new CDN libraries)
    4. ๐Ÿ” Risk Profile Changes: New threats or vulnerability classes affecting political data integrity
    5. โš–๏ธ Regulatory Updates: CRA implementing acts or guidance changes

    ๐ŸŽฏ Maintenance Principle: Assessment stability preferred โ€” avoid routine updates that don't impact CRA compliance


    ๐Ÿ” CRA Article Cross-References

    • Article 6: Scope determination โ†’ Section 2 (CRA Classification)
    • Article 11: Essential cybersecurity requirements โ†’ Section 5 (Requirements Assessment)
    • Article 19: Conformity assessment โ†’ Section 6 (Evidence Documentation)
    • Article 23: Post-market obligations โ†’ Section 7 (Surveillance Documentation)
    • Article 28: Declaration of conformity โ†’ Section 8 (DoC Template)
    • Annex I: Technical requirements โ†’ Section 5 (Requirements self-assessment mapping)
    • Annex V: Technical documentation โ†’ Complete template structure
    • ๐Ÿ”„ Operational Continuity: CRA self-assessment integrated with existing security operations
    • ๐Ÿ“Š Evidence Reuse: Security metrics and monitoring serve dual ISMS/CRA documentation purposes
    • ๐ŸŽฏ Business Value: CRA readiness demonstrates cybersecurity consulting expertise
    • ๐Ÿค Client Confidence: Transparent self-assessment showcases professional implementation methodology

    Demonstrating compliance with Hack23 AB Open Source Policy

    Requirement Status Evidence
    OpenSSF Scorecard โ‰ฅ7.0 โœ… Active OpenSSF Scorecard
    Quality Gate Passed โœ… Active Quality Checks Workflow
    License Badge โœ… Active license
    Threat Model Published โœ… Active Threat Model
    STRIDE Analysis Complete โœ… Active STRIDE Analysis
    Required Artifact Status Evidence
    SECURITY_ARCHITECTURE.md โœ… Present SECURITY_ARCHITECTURE.md โ€” Defense-in-depth with Mermaid diagrams
    FUTURE_SECURITY_ARCHITECTURE.md โœ… Present FUTURE_SECURITY_ARCHITECTURE.md โ€” Security roadmap
    SECURITY.md โœ… Present SECURITY.md โ€” Coordinated vulnerability disclosure
    WORKFLOWS.md โœ… Present WORKFLOWS.md โ€” CI/CD pipeline with security gates
    LICENSE โœ… Apache 2.0 LICENSE โ€” OSI-approved
    CRA-ASSESSMENT.md โœ… Present This document
    CODE_OF_CONDUCT.md โœ… Present CODE_OF_CONDUCT.md โ€” Community standards
    CONTRIBUTING.md โœ… Present CONTRIBUTING.md โ€” Contribution guidelines
    README.md โœ… Present README.md โ€” Includes project classification section
    Requirement Status Evidence
    Supply Chain: Dependency Scanning โœ… Automated Dependabot Config
    Supply Chain: SHA-pinned Actions โœ… Enforced WORKFLOWS.md โ€” All Actions pinned to SHA
    Supply Chain: step-security/harden-runner โœ… Active Egress auditing on all workflows
    Vulnerability Management SLA โœ… Active SECURITY.md โ€” Coordinated disclosure + Dependabot auto-remediation
    SAST: CodeQL โœ… Active CodeQL Workflow
    SCA: Dependency Review โœ… Active Dependency Review Workflow
    Secret Scanning โœ… Active Security Overview
    Requirement Status Evidence
    Primary License: Apache 2.0 โœ… Approved (Permissive) LICENSE
    Dependencies: Permissive Licenses โœ… All permissive npm dependencies under MIT/ISC/Apache 2.0/BSD
    No Prohibited Licenses โœ… Verified No AGPL/GPL/advertising-clause licenses in dependency tree
    Requirement Status Evidence
    CIA Triad Classification โœ… Declared Public / High Integrity / High Availability
    Business Impact Assessment โœ… Documented SWOT.md + CRA Risk Assessment
    RTO/RPO Objectives โœ… Defined RTO: <24h (Medium) / RPO: <24h (Daily)
    Requirement Status Evidence
    No PII/GDPR data โœ… Compliant No personal data collection โ€” static site, no user accounts
    No production credentials โœ… Compliant GitHub secret scanning active
    Public data only โœ… Compliant All data sourced from public government APIs
    Requirement Status Evidence
    Contribution guidelines โœ… Published CONTRIBUTING.md
    Code of Conduct โœ… Published CODE_OF_CONDUCT.md
    PR review process โœ… Active Branch protection + required reviews

    Demonstrating compliance with Hack23 AB CRA Conformity Assessment Process

    Process Step Template Section Status Riksdagsmonitor Evidence
    1๏ธโƒฃ Project Identification CRA Annex V ยง1 โœ… Complete Section 1 โ€” Product description, badges, data sources
    2๏ธโƒฃ CRA Scope & Classification CRA Art. 6-7 โœ… Complete Section 2 โ€” Non-commercial OSS, Standard, Community distribution
    3๏ธโƒฃ Technical Documentation CRA Annex V ยง2 โœ… Complete Section 3 โ€” 9 CRA technical areas documented with evidence links
    4๏ธโƒฃ Risk Assessment CRA Annex V ยง3 โœ… Complete Section 4 โ€” 6 risk categories assessed with residual risk
    5๏ธโƒฃ Essential Requirements CRA Annex I โœ… Complete Section 5 โ€” 13 essential requirements mapped
    6๏ธโƒฃ Conformity Evidence CRA Art. 19 โœ… Complete Section 6 โ€” Badges, CI/CD evidence, release artifacts
    7๏ธโƒฃ Post-Market Surveillance CRA Art. 23 โœ… Complete Section 7 โ€” Monitoring, reporting, update mechanisms
    8๏ธโƒฃ Declaration of Conformity CRA Art. 28 โœ… Draft Section 8 โ€” DoC template ready for formal placement
    9๏ธโƒฃ Assessment Approval Internal โœ… Complete Section 9 โ€” CEO approval documented
    Classification Dimension Selected Value Justification
    ๐Ÿช Market Category OSS Apache 2.0 licensed, freely available on GitHub
    ๐Ÿ›ก๏ธ Confidentiality Public All data from public government sources
    โœ… Integrity High Political data accuracy is essential for democratic trust
    โฑ๏ธ Availability High 99.998% design availability (AWS CloudFront multi-region + GitHub Pages DR), automated failover
    ๐Ÿ• RTO Medium GitHub Pages DR available within hours
    ๐Ÿ”„ RPO Daily Git-based continuous backup, daily content generation
    ๐Ÿข CRA Applicability Non-commercial OSS Volunteer-driven, no revenue model
    ๐ŸŒ Distribution Community GitHub public repository
    ๐Ÿ“‹ CRA Classification Standard Not in Annex III/IV critical categories

    This section provides a systematic mapping of all 13 essential cybersecurity requirements from CRA Annex I, Part I to Riksdagsmonitor implementations.

    Req # Annex I Requirement Riksdagsmonitor Implementation Evidence Compliance Status
    1 Products with digital elements shall be designed, developed and produced with appropriate security, considering the risks during development Static HTML/CSS/JS architecture eliminates server-side attack surface. Secure development lifecycle with threat modeling (THREAT_MODEL.md), security architecture (SECURITY_ARCHITECTURE.md), and annual security reviews THREAT_MODEL.md, SECURITY_ARCHITECTURE.md, GitHub CodeQL scan results COMPLIANT
    2 Products shall be delivered without known exploitable vulnerabilities Dependabot automated vulnerability scanning, npm audit in CI/CD, CodeQL SAST analysis, no known CVEs in production dependencies. Pre-deployment security gate in GitHub Actions GitHub Security tab - 0 open critical/high alerts, npm audit reports in CI logs COMPLIANT
    3 Products shall have secure by default configurations, including possibility to reset to factory settings No configuration required by end users. Static site has no user-configurable settings. TLS 1.3 enforced by GitHub Pages/CloudFront. CSP headers set by default GitHub Pages HTTPS enforcement, CloudFront TLS policy, HTTP response headers COMPLIANT
    4 Products shall protect against unauthorized access through appropriate access control mechanisms Repository protected by GitHub authentication and branch protection rules. No public write access. Least privilege permissions in GitHub Actions workflows. GitHub Secrets for credential storage GitHub branch protection settings, workflow permissions YAML, GitHub Actions audit log COMPLIANT
    5 Products shall protect the confidentiality of data by appropriate means including encryption of data at rest and in transit All data in transit protected by TLS 1.3 enforced via GitHub Pages and CloudFront. No sensitive data at rest (all content is public political data). No PII collected or processed CloudFront TLS 1.3 configuration, HSTS headers, no-cookie policy COMPLIANT
    6 Products shall protect the integrity of data in transit and stored data against manipulation SLSA provenance attestation (Level 2+), Sigstore signing, Git commit signatures, GitHub content integrity guarantees. Article-level SHA-256 planned Q3 2026 SLSA attestation in GitHub Actions, Sigstore transparency log, Git commit signature verification, GitHub repository content integrity documentation COMPLIANT
    7 Products shall process only data, both personal and other, that is adequate, relevant and limited to what is necessary Zero PII collected. Platform processes only publicly available Riksdag political data. No analytics cookies. No user tracking. Data minimization by design Privacy policy (no-cookie design), source code review showing no PII collection COMPLIANT
    8 Products shall protect the availability of essential functions including protection against denial of service attacks AWS CloudFront CDN with DDoS protection at edge. GitHub Pages provides secondary availability. Route 53 health-check-based failover. 99.998% availability target CloudFront Shield Standard coverage, BCPPlan.md, dual-deployment architecture COMPLIANT
    9 Products shall minimize the negative impact on the availability of services provided by other devices or networks Static site generates no outbound network calls from user browsers beyond CDN. MCP pipeline calls are server-side in GitHub Actions (controlled, rate-limited) Source code showing no user-browser-initiated external calls, rate limiting in MCP client COMPLIANT
    10 Products shall be designed, developed and produced to limit attack surfaces, including external interfaces Attack surface minimized: no database, no server-side code, no user input forms, no cookies. Only surfaces: HTTPS static file serving, GitHub API (authenticated). No exposed ports Architecture.md showing static-only design, no open ports analysis COMPLIANT
    11 Products shall be designed, developed and produced to reduce the impact of an incident including through appropriate mechanisms for resilience Automatic failover (CloudFront origin failover <30s, DNS failover <15min). Complete Git history for rollback. Incident response procedures in BCPPlan.md and ISMS. No persistent state to lose BCPPlan.md dual-deployment, RTO metrics, Git rollback capability COMPLIANT
    12 Products shall record and/or monitor relevant internal activities in order to detect and investigate cybersecurity incidents GitHub Actions audit logs, CloudFront access logs, GitHub Security alerts, OpenSSF Scorecard monitoring, automated Dependabot alerts. step-security/harden-runner egress monitoring GitHub Audit Log API, CloudFront log groups, Security tab alert history COMPLIANT
    13 Products shall ensure that vulnerabilities can be addressed through security updates including, where technically possible, automatic updates Dependabot automated PRs for dependency updates. GitHub Actions automated vulnerability notifications. Security contact (security@hack23.com) for coordinated disclosure. SECURITY.md outlines update process Dependabot configuration, SECURITY.md, coordinated disclosure policy COMPLIANT

    Req # Annex I Part II Requirement Riksdagsmonitor Implementation Evidence Compliance Status
    1 Identify and document vulnerabilities and components contained in the product, including by drawing up a software bill of materials npm package-lock.json provides complete dependency graph. Dependabot monitors all dependencies. SBOM generation planned for 2027 via GitHub SBOM feature package-lock.json, npm audit output, Dependabot alerts PARTIAL โ€” SBOM automation planned 2027
    2 Address vulnerabilities without delay including by providing security updates Critical: <7 days. High: <30 days. Medium: <90 days. Dependabot auto-PRs for patch releases. Manual review for major version upgrades Dependabot configuration, vulnerability management in ISMS, MTTP metrics COMPLIANT
    3 Apply effective and regular testing and reviews of the security of products with digital elements CodeQL SAST on every PR and commit. Dependabot daily scans. Quarterly threat model review. Annual security architecture review. OpenSSF Scorecard monthly GitHub Actions security scan results, CodeQL alerts, Scorecard history COMPLIANT
    4 After becoming aware of a vulnerability, share information about it with ENISA without undue delay ENISA reporting procedure: notify via security@hack23.com internal triage, then report to ENISA vulnerability database within 72 hours for critical issues ISMS Incident Response Plan, coordinated disclosure procedure COMPLIANT โ€” procedure documented
    5 Establish and document a coordinated vulnerability disclosure policy SECURITY.md contains full coordinated vulnerability disclosure policy. security@hack23.com for reporting. 90-day disclosure timeline. Response SLA: acknowledge within 5 business days SECURITY.md public policy COMPLIANT
    6 Take measures to facilitate the sharing of information about vulnerabilities in the product Public GitHub Security Advisories for all confirmed vulnerabilities. SECURITY.md disclosure policy. GitHub private vulnerability reporting enabled GitHub Security Advisories tab, SECURITY.md COMPLIANT
    7 Provide for a mechanism for coordinating the vulnerability disclosure process with other manufacturers or security researchers security@hack23.com receives all vulnerability reports. GitHub private vulnerability reporting. Coordinated disclosure gives reporters credit. No retaliation policy SECURITY.md safe harbor clause COMPLIANT
    8 As long as products are supported, make available without delay security updates to address vulnerabilities Immediate security updates for critical vulnerabilities. Automated Dependabot PRs for all vulnerable dependencies. Auto-merge configured for patch-level security updates Dependabot auto-merge configuration, security update history COMPLIANT

    Assessment Method: Self-Assessment (Module A - Internal Production Control)

    Riksdagsmonitor qualifies for self-assessment under CRA Article 32(1) as it is:

    • A standard product with digital elements (not critical or important category per Annex III/IV)
    • Non-commercial open-source software distributed publicly without charge
    • A civic transparency tool with low risk profile (no safety functions, no critical infrastructure)

    Self-Assessment Process:

    1. Technical Documentation (CRA Annex V): Complete โ€” this document and linked ISMS documents
    2. Design and Development Assessment: Complete โ€” THREAT_MODEL.md, SECURITY_ARCHITECTURE.md
    3. Production Controls: Complete โ€” CI/CD pipeline with security gates documented in WORKFLOWS.md
    4. Conformity Declaration: Template in Section 8 of this document
    5. CE Marking: Applicable upon formal EU market placement (currently pre-commercial)

    Assessment Conclusion:

    CRA Area Requirements Compliant Partial Non-Compliant
    Annex I Part I 13 13 0 0
    Annex I Part II 8 7 1 0
    Annex V Documentation Complete Yes โ€” โ€”
    Vulnerability Handling Policy exists Yes โ€” โ€”
    Overall 21 20 1 0

    Open Item: SBOM automation (Annex I Part II Req 1) โ€” planned Q1 2027 via GitHub SBOM generation feature.



    This section provides a forward-looking readiness checklist for when Riksdagsmonitor formally enters EU market distribution as a commercial product.

    Area Requirement Current Readiness Action Required Target Date
    Technical Documentation CRA Annex V complete documentation 95% complete Finalize SBOM generation Q1 2027
    Conformity Assessment Self-assessment completed and documented 90% complete Formal declaration of conformity Q2 2027
    Vulnerability Handling Policy Published and accessible 100% None - SECURITY.md complete Done
    Security Update Process Documented and operational 100% None - Dependabot + MTTP policy Done
    Coordinated Disclosure Policy and contact established 100% None - security@hack23.com Done
    CE Marking Required for EU market products Not yet Apply after conformity assessment 2027
    ENISA Reporting Incident reporting procedure 85% Document ENISA contact and timeline Q2 2026
    SBOM Software Bill of Materials Partial Implement GitHub SBOM generation Q1 2027
    Post-Market Surveillance Ongoing monitoring plan 80% Formalize surveillance process doc Q3 2026
    flowchart LR
    VULN_DISCOVERED[Vulnerability Discovered] --> ASSESS[Severity Assessment]
    ASSESS --> CRITICAL{Critical CVSS 9+?}
    CRITICAL -->|Yes| PATCH_7[Patch within 7 days]
    CRITICAL -->|No| HIGH{High CVSS 7-8.9?}
    HIGH -->|Yes| PATCH_30[Patch within 30 days]
    HIGH -->|No| MED{Medium CVSS 4-6.9?}
    MED -->|Yes| PATCH_90[Patch within 90 days]
    MED -->|No| PATCH_SCHED[Patch in next release]
    PATCH_7 --> DEPLOY[Deploy Security Update]
    PATCH_30 --> DEPLOY
    PATCH_90 --> DEPLOY
    PATCH_SCHED --> DEPLOY
    DEPLOY --> NOTIFY[Notify via SECURITY.md Advisory]
    NOTIFY --> ENISA_CHECK{Significant incident?}
    ENISA_CHECK -->|Yes| ENISA_REPORT[Report to ENISA within 24h]
    ENISA_CHECK -->|No| CLOSE[Close Vulnerability Record]
    ENISA_REPORT --> CLOSE

    CRA Article 13 Manufacturer Obligations Tracking

    Obligation Article Implementation Status
    Design and produce with appropriate cybersecurity 13(1) Secure SDLC, STRIDE threat modeling Done
    Deliver without known exploitable vulnerabilities 13(2) Dependabot, npm audit, CodeQL pre-deploy Done
    Perform vulnerability assessment 13(3) Quarterly threat model review Done
    Apply security updates without undue delay 13(4) Dependabot auto-merge, MTTP policy Done
    Ensure security for expected lifetime 13(5) Lifecycle support policy documented Done
    Set support period in declaration of conformity 13(6) Support period: 5 years from last release Planned
    Provide security updates for support period 13(7) Dependabot + manual review ongoing Done
    Notify ENISA of actively exploited vulnerabilities 13(8) ENISA procedure in IR Plan Done
    Provide technical documentation 13(14) CRA-ASSESSMENT.md + SECURITY_ARCHITECTURE.md Done
    Affix CE marking 13(15) Not yet - required for market placement Planned
    Draw up EU declaration of conformity 13(16) Template exists - formal sign-off pending Planned

    CRA Article 14 Reporting Obligations

    Active Exploitation Reporting (Article 14(2)):

    • Notification timeline: Within 24 hours of becoming aware
    • Recipient: ENISA Early Warning notification system
    • Content: Product identification, vulnerability description, known exploited instances
    • Contact: security@hack23.com (internal) โ†’ ENISA online notification form

    Severe Incident Reporting (Article 14(3)):

    • Notification timeline: Within 72 hours of detection
    • Recipient: Competent market surveillance authority (MSA) and ENISA
    • For Sweden: Swedish Post and Telecom Authority (PTS) as likely MSA
    • Content: Detailed incident report including impact, affected versions, remediation

    User Notification (Article 14(8)):

    • If security update available: Notify users via GitHub Security Advisories
    • If vulnerability affects user security: Post advisory on riksdagsmonitor.com
    • Update README.md security section for significant vulnerabilities

    Riksdagsmonitor must be evaluated against CRA's product classification system to determine the applicable conformity assessment route:

    CRA Annex III โ€” Important Products with Digital Elements (Class I):

    Category Riksdagsmonitor Assessment
    Identity management software Not applicable
    Password managers Not applicable
    Browsers Not applicable
    Operating systems Not applicable
    VPNs Not applicable
    Network management software Not applicable
    Firewalls Not applicable
    Intrusion detection systems Not applicable
    Microcontrollers Not applicable
    Consumer IoT Not applicable

    Conclusion: Riksdagsmonitor does not qualify as a Class I Important Product under Annex III.

    CRA Annex IV โ€” Critical Products with Digital Elements (Class II):

    Category Riksdagsmonitor Assessment
    Critical infrastructure software Not applicable - civic transparency platform
    HSMs / Secure elements Not applicable
    Smart meters Not applicable
    Industrial control systems Not applicable

    Conclusion: Riksdagsmonitor does not qualify as a Class II Critical Product under Annex IV.

    Final Classification: Standard Product with Digital Elements โ€” eligible for Module A Self-Assessment


    Open Source Software Considerations (CRA Article 16)

    Riksdagsmonitor benefits from the CRA open source carve-out provisions:

    CRA Provision Application to Riksdagsmonitor
    Non-commercial OSS exemption (Recital 18) Riksdagsmonitor is freely available, non-commercial, no revenue model
    Commercial distribution triggers CRA (Art. 16(1)) If Riksdagsmonitor is commercialized (API subscriptions), CRA obligations apply in full
    Steward provisions Hack23 AB acts as open source steward
    Vulnerability handling (Art. 16(2)) Security policy (SECURITY.md) and coordinated disclosure required even for OSS
    Security advisories Public security advisories for known vulnerabilities

    Compliance Strategy: Maintain full CRA technical documentation now, enabling smooth transition to formal commercial compliance when API tier launches in 2027.


    The following template will be formalized upon entry into EU commercial distribution:

    EU DECLARATION OF CONFORMITY
    Riksdagsmonitor - Version [X.Y]

    Hack23 AB (Org.nr 5595347807)
    Sweden

    This declaration of conformity is issued under the sole responsibility
    of the manufacturer.

    Product: Riksdagsmonitor - Swedish Parliamentary Transparency Platform
    Version: [X.Y]
    Description: Web-based civic technology platform providing access to
    Swedish Riksdag parliamentary data, voting records, and AI-generated
    political news in 14 languages.

    Conformity Assessment Method: Module A (Self-Assessment)
    Product Category: Standard product with digital elements
    Annex III/IV Category: Not applicable

    The object of the declaration described above is in conformity with
    the relevant Union harmonisation legislation:

    Regulation (EU) 2024/2847 - Cyber Resilience Act
    - Annex I Part I: Essential cybersecurity requirements (13/13 compliant)
    - Annex I Part II: Vulnerability handling requirements (7/8 compliant)
    - Annex V: Technical documentation available at:
    github.com/Hack23/riksdagsmonitor/blob/main/CRA-ASSESSMENT.md

    Signed for and on behalf of: James Pether Sorling, CEO
    Date: [To be completed upon formal market placement]
    Place: Sweden

    ๐Ÿ“‹ Document Control: โœ… Approved by: James Pether Sรถrling, CEO ๐Ÿ“ค Distribution: Public ๐Ÿท๏ธ Classification: Confidentiality: Public ๐Ÿ“… Effective Date: 2026-05-06 โฐ Next Review: 2026-08-06 ๐ŸŽฏ CRA Alignment: Follows CRA Conformity Assessment Process template โ€” supports CRA Annex V technical documentation and self-assessment requirements ๐Ÿ”“ OSS Alignment: Conforms with Open Source Policy โ€” governance artifacts, security posture evidence, license compliance ๐Ÿข ISMS Integration: Comprehensive alignment with public ISMS framework for operational excellence ๐ŸŽฏ Framework Compliance: ISO 27001 NIST CSF 2.0 CIS Controls


    Effective: 2026-04-24 ยท Authoritative hub: analysis/imf/README.md ยท analysis/imf/agentic-integration.md ยท analysis/imf/indicators-inventory.json ยท analysis/imf/data-dictionary.md ยท .github/aw/ECONOMIC_DATA_CONTRACT.md

    Attribute Value
    Service name International Monetary Fund โ€” Public APIs (Datamapper REST + SDMX 3.0)
    Vendor International Monetary Fund (IGO; not a commercial vendor)
    Hostnames (egress allow-list) www.imf.org, api.imf.org
    Authentication Datamapper: none (anonymous public API) ยท SDMX 3.0: Azure APIM subscription key (Ocp-Apim-Subscription-Key / IMF_SDMX_SUBSCRIPTION_KEY) โ€” gates throttle/quota only; payloads are public
    Data classification consumed PUBLIC macro/fiscal/monetary/external statistics; no PII
    Data flow direction Inbound only (read-only)
    Rate limit ~30 req/min observed; self-imposed โ‰ค30 req/min with back-off
    Redundancy Two endpoints (Datamapper + SDMX) for the same underlying data
    Cache Vintage-tagged in analysis/imf/ + analysis/daily/*/economic-data.json
    Integrity SHA-256 payload pin + supersedes-chain
    Vendor security posture IMF Open Data โ€” published rate limits, public terms, no auth surface
    Licence Attribution required; redistribution permitted with citation
    CRA risk class Low (read-only, public, no PII, no credentials)
    CRA conformity decision Self-assessment Annex V โ€” no notified body required
    • Eliminates a credential-management surface that a commercial economic-data provider would introduce
    • Eliminates a supply-chain dependency on a single commercial vendor
    • Eliminates GDPR DPIA scope (no PII)
    • Provides redundancy via two independent endpoints (Datamapper + SDMX)

    Egress hosts (allow-list): www.imf.org (Datamapper REST ยท WEO/FM, unauthenticated), api.imf.org (SDMX 3.0 REST ยท IFS/BOP/DOTS/GFS/PCPS/ER/MFS_IR/MFS_PR, subscription-key authenticated via the Azure APIM Ocp-Apim-Subscription-Key header / IMF_SDMX_SUBSCRIPTION_KEY secret). Both HTTPS-only; payloads are public macro statistics with no PII.

    Canonical rule. Every economic claim in a Riksdagsmonitor article cites an IMF dataflow first; World Bank citations are reserved for governance, environment and social residue (the classes IMF does not publish). SCB is the Swedish-specific ground truth layer. See ECONOMIC_DATA_CONTRACT.md v2.1 for the banned-phrase list and vintage discipline (>6 mo โ†’ annotation).


    ๐ŸŒ Platforms ๐Ÿ“ฆ Open-Source Projects ๐Ÿ›ก๏ธ Governance & Standards
    ๐Ÿ—ณ๏ธ Riksdagsmonitor โ€” Swedish Parliament intelligence
    ๐Ÿ‡ช๐Ÿ‡บ EU Parliament Monitor โ€” European coverage
    ๐Ÿ•ต๏ธ Citizen Intelligence Agency โ€” political-data engine
    ๐ŸŒ Hack23 AB โ€” corporate site
    ๐Ÿ“ฐ Hack23 Blog โ€” engineering & policy
    ๐Ÿ’ผ Hack23 on LinkedIn
    ๐Ÿ—ณ๏ธ Hack23/riksdagsmonitor
    ๐Ÿ•ต๏ธ Hack23/cia
    ๐Ÿ‡ช๐Ÿ‡บ Hack23/euparliamentmonitor
    ๐Ÿ”Œ Hack23/european-parliament-mcp
    โœ… Hack23/cia-compliance-manager
    ๐Ÿฅ‹ Hack23/black-trigram
    ๐Ÿ  Hack23/homepage
    ๐Ÿ›ก๏ธ Hack23 ISMS-PUBLIC โ€” public ISMS
    ๐Ÿ”’ Information Security Policy
    ๐Ÿค– AI Policy
    ๐Ÿงช Secure Development Policy
    ๐ŸŽฏ Threat Modeling Policy
    โš ๏ธ Vulnerability Management
    ๐Ÿท๏ธ Classification Framework

    OpenSSF Best Practices OpenSSF Scorecard ISO 27001:2022 NIST CSF 2.0 CIS Controls v8.1 Apache 2.0

    ๐Ÿ—ณ๏ธ Empower citizens ยท ๐Ÿ” Strengthen democratic accountability ยท ๐Ÿ•ต๏ธ Illuminate the political process

    ยฉ 2008โ€“2026 Hack23 AB (Org.nr 559534-7807) ยท Maintainer: James Pether Sรถrling, CISSP CISM