🛡️ Security Through Transparency and Vulnerability Management
🎯 Defense-in-Depth Architecture for Democratic Intelligence

📋 Document Owner: CEO | 📄 Version: 1.0 | 📅 Last Updated: 2026-02-20 (UTC)
🔄 Review Cycle: Quarterly | ⏰ Next Review: 2026-05-20
🏢 Owner: Hack23 AB (Org.nr 5595347807) | 🏷️ Classification: Public

This security policy establishes vulnerability disclosure and incident response procedures for Riksdagsmonitor, implementing Vulnerability Management and Incident Response Plan from Hack23 AB's ISMS framework.

Our security approach demonstrates our commitment to transparency and operational excellence, ensuring that vulnerabilities are managed systematically with documented response times and coordinated disclosure processes.

— James Pether Sörling, CEO/Founder

This project is under active development, and we provide security updates for the latest version only.

Riksdagsmonitor maintains strong security practices as documented in our Security Architecture:

• ✅ Static Site Architecture — No server-side code execution, no database vulnerabilities
• ✅ HTTPS-Only — TLS 1.3 via AWS CloudFront and GitHub Pages
• ✅ Automated Security Scanning — CodeQL, Dependabot, Secret Scanning
• ✅ Supply Chain Security — SHA-pinned GitHub Actions, step-security/harden-runner
• ✅ Multi-Region Availability — AWS CloudFront (us-east-1 primary, eu-west-1 replica) with GitHub Pages DR
• ✅ SLSA Build Provenance — Attestation for build integrity
• ✅ Content Integrity — Subresource Integrity (SRI) for CDN assets
• ✅ Security Headers — CSP, HSTS, X-Frame-Options, X-Content-Type-Options

Evidence:

• 
• Security Overview

We take the security of Riksdagsmonitor seriously. If you have found a potential security vulnerability, we kindly ask you to report it privately, so that we can assess and address the issue before it becomes publicly known.

A vulnerability is a weakness or flaw in the project that can be exploited to compromise the security, integrity, or availability of the system or its data. Examples include, but are not limited to:

• Cross-site scripting (XSS) in generated content
• Insecure external resource loading
• Exposed secrets or credentials
• Supply chain vulnerabilities in dependencies
• Content injection through data pipelines

1. On GitHub.com, navigate to the main page of the riksdagsmonitor repository.
2. Under the repository name, click Security.
3. In the left sidebar, under "Reporting", click Advisories.
4. Click Report a vulnerability to open the advisory form.
5. Fill in the advisory details form with as much information as possible.
6. At the bottom of the form, click Submit report.

Upon receipt of a vulnerability report, our team will:

1. Acknowledge the report within 48 hours
2. Validate the vulnerability within 7 days
3. Develop and release a patch or mitigation within 30 days (depending on complexity and severity)
4. Publish a security advisory with a detailed description of the vulnerability and the fix

We appreciate your effort in helping us maintain a secure project. If your report results in a confirmed security fix, we will recognize your contribution in the release notes, unless you request to remain anonymous.

Riksdagsmonitor's security practices are part of Hack23 AB's comprehensive Information Security Management System (ISMS):

• 🛡️ Security Architecture: SECURITY_ARCHITECTURE.md — Defense-in-depth controls
• 🎯 Threat Model: THREAT_MODEL.md — STRIDE analysis, MITRE ATT&CK mapping
• 🔮 Future Security: FUTURE_SECURITY_ARCHITECTURE.md — Security roadmap
• 🔧 CI/CD Security: WORKFLOWS.md — Pipeline security controls

• 🛡️ Security Architecture — System security design
• 🎯 Threat Model — Comprehensive threat analysis
• 🔮 Future Security Architecture — Security roadmap
• 🏗️ Architecture — System architecture (C4 models)
• 🔧 Workflows — CI/CD pipeline documentation

• 🤝 Contributing Guidelines — Secure contribution process
• 📜 Code of Conduct — Community standards
• 📋 README — Project overview and classification

• 🔐 Information Security Policy
• 🔍 Vulnerability Management
• 🚨 Incident Response Plan
• 🛠️ Secure Development Policy

📋 Document Control:
✅ Approved by: James Pether Sörling, CEO
📤 Distribution: Public
🏷️ Classification:
📅 Effective Date: 2026-02-20
⏰ Next Review: 2026-05-20
🎯 Framework Compliance: