Spaces:
Paused
Paused
| # π Citizen Intelligence Agency | |
| > An independent, volunteer-driven OSINT platform monitoring Swedish political activity | |
| ## π― Mission | |
| The Citizen Intelligence Agency is a volunteer-driven, open-source intelligence (OSINT) project that provides comprehensive analysis of political activities in Sweden. Through advanced monitoring of key political figures and institutions, we deliver: | |
| - π Financial performance metrics | |
| - β οΈ Risk assessment analytics | |
| - π Political trend analysis | |
| - π Politician ranking system | |
| - π Performance comparisons | |
| - π Transparency insights | |
| Our initiative remains strictly independent and non-partisan, focused on fostering informed decision-making and enhancing democratic engagement. | |
| ## π Quality Metrics | |
| [](https://hack23.github.io/cia/jacoco/) | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| [](https://deepwiki.com/Hack23/cia) | |
| **Coverage Policy:** Per [Secure Development Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Secure_Development_Policy.md), we maintain minimum 80% line coverage and 70% branch coverage across all modules. | |
| ## β¨ Features | |
| Explore our [comprehensive feature set](https://hack23.com/cia-features.html) including: | |
| - π Interactive dashboards | |
| - π Political scoreboard systems | |
| - π Critical analytics tools | |
| - π Transparency metrics | |
| - βοΈ Accountability measures | |
| - π± Data-driven insights | |
| For a conceptual view of our system architecture and components, see our [Architecture Documentation](ARCHITECTURE.md) and [System Mindmaps](MINDMAP.md). | |
| ## π Blog Posts & Technical Analysis | |
| Explore in-depth technical analysis and architectural insights about this project through our team's blog posts: | |
| ### π€ GitHub Copilot Custom Agents | |
| <div align="left"> | |
| We maintain a collection of [custom GitHub Copilot agents](.github/agents/) specialized for different aspects of the project: | |
| - π **[Task Agent](.github/agents/task-agent.md)** - Product quality, GitHub issue management, ISMS compliance | |
| - π οΈ **[Stack Specialist](.github/agents/stack-specialist.md)** - Java, Spring, Vaadin, PostgreSQL expertise | |
| - π¨ **[UI Enhancement Specialist](.github/agents/ui-enhancement-specialist.md)** - Vaadin, accessibility, data visualization | |
| - π **[Intelligence Operative](.github/agents/intelligence-operative.md)** - Political analysis, OSINT methodologies | |
| - π° **[Business Development Specialist](.github/agents/business-development-specialist.md)** - Strategic planning, partnerships | |
| - π’ **[Marketing Specialist](.github/agents/marketing-specialist.md)** - Digital marketing, content strategy | |
| See the [agents README](.github/agents/README.md) for detailed information on using these specialized profiles. | |
| </div> | |
| ### β Simon Moon's Architecture Chronicles | |
| <div align="left"> | |
| System Architect [Simon Moon](https://github.com/Hack23/homepage/blob/master/.github/agents/simon-moon.md) provides deep architectural analysis of the CIA platform through the lens of sacred geometry and pattern recognition: | |
| #### ποΈ CIA Platform Architecture & Security | |
| - **[CIA Architecture: The Five Pentacles](https://hack23.com/blog-cia-architecture.html)** - Five container types crystallized from the parliamentary domain. Architecture that mirrors political realityβpower flows documented in code. | |
| - **[CIA Security: Defense Through Transparency](https://hack23.com/blog-cia-security.html)** - Security through mathematical proof, not mystical obscurity. Five defensive layers. OpenSSF Scorecard 7.2/10. Zero critical vulnerabilities across 5 years. | |
| - **[CIA Future Security: The Pentagon of Tomorrow](https://hack23.com/blog-cia-future-security.html)** - Post-quantum cryptography before quantum computers threaten. AI-augmented detection before AI attacks dominate. | |
| - **[CIA Financial Strategy: $24.70/Day Democracy](https://hack23.com/blog-cia-financial-strategy.html)** - Democracy costs $24.70/day when architecture channels cosmic financial patterns through AWS optimization. | |
| - **[CIA Workflows: Five-Stage CI/CD & State Machines](https://hack23.com/blog-cia-workflows.html)** - Five GitHub Actions workflows orchestrating DevSecOps automation. Data processing through five state transitions. | |
| - **[CIA Mindmaps: Conceptual Sacred Geometry](https://hack23.com/blog-cia-mindmaps.html)** - Hierarchical thinking revealing natural organizational patterns: 4 current domains expanding into 5 future dimensions. | |
| </div> | |
| ### π» George Dorn's Code Analysis | |
| <div align="left"> | |
| Developer [George Dorn](https://github.com/Hack23/homepage/blob/master/.github/agents/george-dorn.md) provides hands-on code analysis based on actual repository inspection: | |
| #### π Repository Deep-Dives | |
| - **[CIA Code Analysis](https://hack23.com/blog-george-dorn-cia-code.html)** - Repository deep-dive examining Maven POMs, 49 modules, 1,372 Java files, verified OpenSSF Scorecard 7.2/10. Based on actual repository inspection. | |
| *For the complete collection of 50+ blog posts covering cybersecurity, ISMS policies, and architectural patterns, visit the [Hack23 Security Blog](https://hack23.com/blog.html).* | |
| </div> | |
| ## π’ About Hack23 | |
| - π **Website**: [www.hack23.com](https://www.hack23.com) | |
| - πΌ **LinkedIn**: [James SΓΆrling](https://www.linkedin.com/in/jamessorling) | |
| ## π Commitment to Transparency and Security | |
| At Hack23 AB, we believe that true security comes through transparency and demonstrable practices. Our Information Security Management System (ISMS) is publicly available, showcasing our commitment to security excellence and organizational transparency. | |
| <table> | |
| <tr> | |
| <td width="50%"> | |
| <div align="center"> | |
| <h3>π Public ISMS Repository</h3> | |
| <p>Complete Information Security Management System documentation</p> | |
| <a href="https://github.com/Hack23/ISMS-PUBLIC"> | |
| <img src="https://img.shields.io/badge/ISMS-PUBLIC-0066CC?style=for-the-badge&logo=github&logoColor=white" alt="ISMS Public Repository"> | |
| </a> | |
| </div> | |
| </td> | |
| <td width="50%"> | |
| <div align="center"> | |
| <h3>π Information Security Policy</h3> | |
| <p>Enterprise-grade security framework and governance</p> | |
| <a href="https://github.com/Hack23/ISMS-PUBLIC/blob/main/Information_Security_Policy.md"> | |
| <img src="https://img.shields.io/badge/Security-Policy-DC143C?style=for-the-badge&logo=shield&logoColor=white" alt="Information Security Policy"> | |
| </a> | |
| </div> | |
| </td> | |
| </tr> | |
| </table> | |
| ### π Security Through Transparency | |
| Our approach to cybersecurity consulting is built on a foundation of transparent practices: | |
| - **π Open Documentation**: Complete ISMS framework available for review | |
| - **π Policy Transparency**: Detailed security policies and procedures publicly accessible | |
| - **π― Demonstrable Expertise**: Our own security implementation serves as a live demonstration | |
| - **π Continuous Improvement**: Public documentation enables community feedback and enhancement | |
| <div align="center"> | |
| <p><em>"Our commitment to transparency extends to our security practices - demonstrating that true security comes from robust processes, continuous improvement, and a culture where security considerations are integrated into every business decision."</em></p> | |
| <p><strong>β James Pether SΓΆrling, CEO/Founder</strong></p> | |
| </div> | |
| #### π ISMS Compliance Mapping | |
| For a comprehensive view of how ISMS-PUBLIC policies map to CIA platform security controls: | |
| <div align="center"> | |
| <a href="ISMS_COMPLIANCE_MAPPING.md"> | |
| <img src="https://img.shields.io/badge/View-ISMS_Compliance_Mapping-DC143C?style=for-the-badge&logo=shield&logoColor=white" alt="ISMS Compliance Mapping"> | |
| </a> | |
| </div> | |
| **Coverage:** 32 ISMS policies β’ 100+ security controls β’ ISO 27001 β’ NIST CSF 2.0 β’ CIS Controls v8.1 | |
| --- | |
| ## π‘οΈ Security & Compliance Evidence | |
| Our commitment to security transparency is demonstrated through publicly verifiable evidence: | |
| ### π Supply Chain Security | |
| [](https://scorecard.dev/viewer/?uri=github.com/Hack23/cia) | |
| [](https://github.com/Hack23/cia/attestations) | |
| [](https://bestpractices.coreinfrastructure.org/projects/770) | |
| **Evidence:** | |
| - **OpenSSF Scorecard**: [Full Supply Chain Analysis](https://scorecard.dev/viewer/?uri=github.com/Hack23/cia) | |
| - **SLSA Attestations**: [Build Provenance & SBOM](https://github.com/Hack23/cia/attestations) | |
| - **CII Best Practices**: [Open Source Security Maturity](https://bestpractices.coreinfrastructure.org/projects/770) | |
| ### π Security Scanning | |
| [](https://github.com/Hack23/cia/security/code-scanning) | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| **Evidence:** | |
| - **CodeQL Scanning**: [Security Code Analysis Results](https://github.com/Hack23/cia/security/code-scanning) | |
| - **SonarCloud Security**: [Vulnerability Dashboard](https://sonarcloud.io/project/security_hotspots?id=Hack23_cia) | |
| - **Dependabot**: [Dependency Vulnerability Alerts](https://github.com/Hack23/cia/security/dependabot) | |
| ### β Quality Gates | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| **Evidence:** | |
| - **Quality Gate**: [SonarCloud Quality Dashboard](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| - **Code Metrics**: [Technical Debt & Maintainability](https://sonarcloud.io/component_measures?id=Hack23_cia&metric=sqale_index) | |
| ### π License Compliance | |
| [](https://app.fossa.io/projects/git%2Bgithub.com%2FHack23%2Fcia?ref=badge_shield) | |
| [](https://github.com/Hack23/cia/blob/master/LICENSE.txt) | |
| **Evidence:** | |
| - **FOSSA Analysis**: [License Compliance Report](https://app.fossa.io/projects/git%2Bgithub.com%2FHack23%2Fcia) | |
| - **License**: [Apache License 2.0](https://github.com/Hack23/cia/blob/master/LICENSE.txt) | |
| ### π― Security Architecture Documentation | |
| [](https://github.com/Hack23/cia/blob/master/THREAT_MODEL.md) | |
| [](https://github.com/Hack23/cia/blob/master/SECURITY_ARCHITECTURE.md) | |
| [](https://github.com/Hack23/cia/blob/master/CRA-ASSESSMENT.md) | |
| **Evidence:** | |
| - **Threat Model**: [STRIDE Analysis & Attack Trees](https://github.com/Hack23/cia/blob/master/THREAT_MODEL.md) | |
| - **Security Architecture**: [Defense-in-Depth Design](https://github.com/Hack23/cia/blob/master/SECURITY_ARCHITECTURE.md) | |
| - **CRA Assessment**: [EU Cyber Resilience Act Compliance](https://github.com/Hack23/cia/blob/master/CRA-ASSESSMENT.md) | |
| --- | |
| **π Transparency Commitment**: All security evidence is publicly accessible for stakeholder verification. We believe security through transparency builds trust and demonstrates our commitment to cybersecurity excellence. | |
| --- | |
| ## π Data Sources | |
| Our analysis is powered by authoritative Swedish government and international data sources: | |
| | Source | Description | | |
| |--------|-------------| | |
| | ποΈ [Swedish Parliament Open Data](http://data.riksdagen.se/) | Parliamentary members, committees, and official documents | | |
| | π³οΈ [Swedish Election Authority](http://www.val.se/) | Election data, political parties, and voting results | | |
| | π [World Bank Open Data](http://data.worldbank.org/) | Global economic indicators and demographic data | | |
| | πΉ [Swedish Financial Management Authority](https://www.esv.se/) | Government finances and economic trends | | |
| ## π Project Status | |
| <div align="center"> | |
| [](https://github.com/Hack23/cia/releases) | |
| [](https://deepwiki.com/Hack23/cia) | |
| [](https://github.com/Hack23/cia/actions/workflows/release.yml) | |
| [](https://github.com/Hack23/cia/actions/workflows/codeql-analysis.yml) | |
| [](https://sonarcloud.io/summary/new_code?id=Hack23_cia) | |
| [](https://isitmaintained.com/project/Hack23/cia "Average time to resolve an issue") | |
| [](https://isitmaintained.com/project/Hack23/cia "Percentage of issues still open") | |
| [](https://cla-assistant.io/Hack23/cia) | |
| **For comprehensive security and compliance evidence, see [Security & Compliance Evidence](#security--compliance-evidence) section above.** | |
| </div> | |
| ## π Runtime Environment | |
| <div align="center"> | |
| | JDK Version | Status | Release Info | | |
| |-------------|--------|--------------| | |
| |  | Supported | LTS Release | | |
| |  | Compatible | Feature Release | | |
| |  | Compatible | Feature Release | | |
| |  | Compatible | Feature Release | | |
| |  | Supported | Current LTS | | |
| </div> | |
| For details on our technology lifecycle management, see the [End-of-Life Strategy](End-of-Life-Strategy.md). | |
| ## π Architecture Documentation Map | |
| <div class="documentation-map"> | |
| | Document | Focus | Description | Documentation Link | | |
| | --------------------------------------------------- | --------------- | ----------------------------------------- | ------------------------------------------------------------------------------- | | |
| | **[Architecture](ARCHITECTURE.md)** | ποΈ Architecture | C4 model showing current system structure | [View Source](https://github.com/Hack23/cia/blob/master/ARCHITECTURE.md) | | |
| | **[Future Architecture](FUTURE_ARCHITECTURE.md)** | ποΈ Architecture | C4 model showing future system structure | [View Source](https://github.com/Hack23/cia/blob/master/FUTURE_ARCHITECTURE.md) | | |
| | **[Security Architecture](SECURITY_ARCHITECTURE.md)** | π Security | Security architecture | [View Source](https://github.com/Hack23/cia/blob/master/SECURITY_ARCHITECTURE.md) | | |
| | **[Future Security Architecture](FUTURE_SECURITY_ARCHITECTURE.md)** | π Security | Future Security architecture | [View Source](https://github.com/Hack23/cia/blob/master/FUTURE_SECURITY_ARCHITECTURE.md) | | |
| | **[Mindmaps](MINDMAP.md)** | π§ Concept | Current system component relationships | [View Source](https://github.com/Hack23/cia/blob/master/MINDMAP.md) | | |
| | **[Future Mindmaps](FUTURE_MINDMAP.md)** | π§ Concept | Future capability evolution | [View Source](https://github.com/Hack23/cia/blob/master/FUTURE_MINDMAP.md) | | |
| | **[SWOT Analysis](SWOT.md)** | πΌ Business | Current strategic assessment | [View Source](https://github.com/Hack23/cia/blob/master/SWOT.md) | | |
| | **[Future SWOT Analysis](FUTURE_SWOT.md)** | πΌ Business | Future strategic opportunities | [View Source](https://github.com/Hack23/cia/blob/master/FUTURE_SWOT.md) | | |
| | **[Data Model](DATA_MODEL.md)** | π Data | Current data structures and relationships | [View Source](https://github.com/Hack23/cia/blob/master/DATA_MODEL.md) | | |
| | **[Future Data Model](FUTURE_DATA_MODEL.md)** | π Data | Enhanced political data architecture | [View Source](https://github.com/Hack23/cia/blob/master/FUTURE_DATA_MODEL.md) | | |
| | **[Flowcharts](FLOWCHART.md)** | π Process | Current data processing workflows | [View Source](https://github.com/Hack23/cia/blob/master/FLOWCHART.md) | | |
| | **[Future Flowcharts](FUTURE_FLOWCHART.md)** | π Process | Enhanced AI-driven workflows | [View Source](https://github.com/Hack23/cia/blob/master/FUTURE_FLOWCHART.md) | | |
| | **[State Diagrams](STATEDIAGRAM.md)** | π Behavior | Current system state transitions | [View Source](https://github.com/Hack23/cia/blob/master/STATEDIAGRAM.md) | | |
| | **[Future State Diagrams](FUTURE_STATEDIAGRAM.md)** | π Behavior | Enhanced adaptive state transitions | [View Source](https://github.com/Hack23/cia/blob/master/FUTURE_STATEDIAGRAM.md) | | |
| | **[CI/CD Workflows](WORKFLOWS.md)** | π§ DevOps | Current automation processes | [View Source](https://github.com/Hack23/cia/blob/master/WORKFLOWS.md) | | |
| | **[Future Workflows](FUTURE_WORKFLOWS.md)** | π§ DevOps | Enhanced CI/CD with ML | [View Source](https://github.com/Hack23/cia/blob/master/FUTURE_WORKFLOWS.md) | | |
| | **[End-of-Life Strategy](End-of-Life-Strategy.md)** | π Lifecycle | Maintenance and EOL planning | [View Source](https://github.com/Hack23/cia/blob/master/End-of-Life-Strategy.md) | | |
| | **[Financial Security Plan](FinancialSecurityPlan.md)** | π° Security | Cost and security implementation | [View Source](https://github.com/Hack23/cia/blob/master/FinancialSecurityPlan.md) | | |
| | **[CIA Features](https://hack23.com/cia-features.html)** | π Features | Platform features overview | [View on hack23.com](https://hack23.com/cia-features.html) | | |
| | **[Threat Model](THREAT_MODEL.md)** | π‘οΈ Security | STRIDE / MITRE risk analysis | [View Source](https://github.com/Hack23/cia/blob/master/THREAT_MODEL.md) | | |
| | **[Unit Test Plan](UnitTestPlan.md)** | π§ͺ Testing | Comprehensive testing strategy & coverage | [View Source](https://github.com/Hack23/cia/blob/master/UnitTestPlan.md) | | |
| </div> | |
| ## π Intelligence & Analytics Documentation | |
| <div class="intelligence-documentation"> | |
| The CIA platform provides comprehensive intelligence operations (INTOP) and open-source intelligence (OSINT) capabilities. Our intelligence documentation tracks the evolution of analytical frameworks, risk assessment rules, and database views that power political intelligence products. | |
| ### π Intelligence Changelogs | |
| Track the evolution of intelligence capabilities and analytical infrastructure: | |
| | Document | Focus | Description | Documentation Link | | |
| |----------|-------|-------------|-------------------| | |
| | **[Intelligence Analysis Changelog](CHANGELOG_INTELLIGENCE_ANALYSIS.md)** | π Intelligence | Complete history of intelligence capabilities, frameworks, and OSINT enhancements | [View Source](https://github.com/Hack23/cia/blob/master/CHANGELOG_INTELLIGENCE_ANALYSIS.md) | | |
| | **[Database Views Changelog](CHANGELOG_DATABASE_VIEWS.md)** | ποΈ Views | Detailed tracking of all 85 database views with schema specifications | [View Source](https://github.com/Hack23/cia/blob/master/CHANGELOG_DATABASE_VIEWS.md) | | |
| | **[Risk Rules Changelog](CHANGELOG_RISK_RULES.md)** | π΄ Risk Rules | Evolution of 50 behavioral assessment rules across 5 domains | [View Source](https://github.com/Hack23/cia/blob/master/CHANGELOG_RISK_RULES.md) | | |
| ### π Core Intelligence Documentation | |
| Comprehensive documentation of analytical capabilities and methodologies: | |
| | Document | Focus | Description | Documentation Link | | |
| |----------|-------|-------------|-------------------| | |
| | **[Data Analysis - INTOP OSINT](DATA_ANALYSIS_INTOP_OSINT.md)** | π― Frameworks | 6 analysis frameworks (Temporal, Comparative, Pattern Recognition, Predictive, Network, Decision) | [View Source](https://github.com/Hack23/cia/blob/master/DATA_ANALYSIS_INTOP_OSINT.md) | | |
| | **[Risk Rules Documentation](RISK_RULES_INTOP_OSINT.md)** | π΄ Risk Rules | 50 behavioral detection rules (24 politician, 10 party, 4 committee, 4 ministry, 5 decision, 3 other) | [View Source](https://github.com/Hack23/cia/blob/master/RISK_RULES_INTOP_OSINT.md) | | |
| | **[Database View Intelligence Catalog](DATABASE_VIEW_INTELLIGENCE_CATALOG.md)** | ποΈ Views | Complete catalog of 85 database views (57 regular + 28 materialized) | [View Source](https://github.com/Hack23/cia/blob/master/DATABASE_VIEW_INTELLIGENCE_CATALOG.md) | | |
| | **[Intelligence Data Flow Map](INTELLIGENCE_DATA_FLOW.md)** | πΊοΈ Pipeline | Data pipeline mappings and framework-to-view relationships | [View Source](https://github.com/Hack23/cia/blob/master/INTELLIGENCE_DATA_FLOW.md) | | |
| | **[Liquibase Intelligence Analysis](LIQUIBASE_CHANGELOG_INTELLIGENCE_ANALYSIS.md)** | ποΈ Schema | Database schema evolution from intelligence perspective | [View Source](https://github.com/Hack23/cia/blob/master/LIQUIBASE_CHANGELOG_INTELLIGENCE_ANALYSIS.md) | | |
| ### π οΈ Intelligence Automation | |
| | Tool | Purpose | Location | | |
| |------|---------|----------| | |
| | **Intelligence Changelog Generator** | Automated detection of view changes, risk rule updates, and framework enhancements | [Script](.github/scripts/generate-intelligence-changelog.sh) | | |
| | **GitHub Actions Workflow** | Automated changelog generation on demand | [Workflow](.github/workflows/generate-intelligence-changelog.yml) | | |
| **Usage:** | |
| ```bash | |
| # Generate intelligence changelog from recent changes | |
| .github/scripts/generate-intelligence-changelog.sh | |
| # Compare specific commits | |
| .github/scripts/generate-intelligence-changelog.sh <prev_commit> <current_commit> | |
| ``` | |
| ### π Intelligence Metrics (v1.36.0) | |
| | Category | Count | Description | | |
| |----------|-------|-------------| | |
| | **Analysis Frameworks** | 6 | Temporal, Comparative, Pattern Recognition, Predictive, Network, Decision Intelligence | | |
| | **Risk Rules** | 50 | 24 politician + 10 party + 4 committee + 4 ministry + 5 decision + 3 other | | |
| | **Database Views** | 85 | 57 regular views + 28 materialized views | | |
| | **OSINT Data Sources** | 4 | Riksdagen API, Election Authority, World Bank, Financial Authority | | |
| | **Intelligence Products** | 10+ | Scorecards, Coalition Analysis, Risk Assessments, Trend Reports, Decision Tracking | | |
| </div> | |
| ## π Reporting Security Issues | |
| Please follow the instructions in our [SECURITY.md](https://github.com/Hack23/cia/blob/master/SECURITY.md) file for reporting security issues. | |
| ## π§ Project Technology Stack | |
| <div align="center"> | |
| ### π Core Technology Stack | |
| This document provides a high-level overview of the key technologies used within the **Citizen Intelligence Agency (CIA)** project. Each technology plays a vital role in supporting CIAβs goals for data analysis, security, and scalability within the political intelligence domain. | |
| | **Category** | **Technologies** | | |
| |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | |
| | **Core Framework** | [Spring Framework](https://spring.io/projects/spring-framework) | | |
| | **Security** | [Spring Security](https://spring.io/projects/spring-security), [Bouncy Castle](https://www.bouncycastle.org/) | | |
| | **Data Access** | [Hibernate](https://hibernate.org/orm/), [JPA](https://jakarta.ee/specifications/persistence/), [PostgreSQL](https://www.postgresql.org/), [JDBC](https://docs.oracle.com/javase/tutorial/jdbc/overview/index.html) | | |
| | **Transaction Management**| [Narayana](https://narayana.io/) (Integrated with Spring `JpaTransactionManager`) | | |
| | **Data Auditing** | [Javers](https://javers.org/) | | |
| | **Business Rules Engine** | [Drools](https://www.drools.org/) | | |
| | **Messaging** | [ActiveMQ Artemis](https://activemq.apache.org/components/artemis/), [Spring JMS](https://spring.io/projects/spring-framework) | | |
| | **Web/UI Layer** | [Vaadin](https://vaadin.com/), [Vaadin Sass Compiler](http://vaadin.com/), [Vaadin Themes](https://vaadin.com/) | | |
| | **Monitoring** | [JavaMelody](https://github.com/javamelody/javamelody), [AWS SDK for CloudWatch](https://aws.amazon.com/cloudwatch/) | | |
| | **Testing** | [JUnit](https://junit.org/), [Mockito](https://site.mockito.org/), [Spring Test](https://docs.spring.io/spring-framework/docs/current/reference/html/testing.html), [Selenium WebDriver](https://www.selenium.dev/documentation/en/webdriver/) | | |
| | **Utilities** | [Apache Commons](https://commons.apache.org/), [Google Guava](https://guava.dev/), [SLF4J](http://www.slf4j.org/), [Logback](https://logback.qos.ch/), [Jackson](https://github.com/FasterXML/jackson) | | |
| | **Build & Dependency Management** | [Maven](https://maven.apache.org/) | | |
| ## Stack Summary | |
| This stack comprises: | |
| - **Core Framework**: The project uses **Spring Framework** to provide a foundation for dependency injection, component management, and service configuration across modules. | |
| - **Security**: **Spring Security** manages authentication and authorization, complemented by **Bouncy Castle** for cryptographic operations. | |
| - **Data Access**: A combination of **Hibernate**, **JPA**, and **PostgreSQL** supports robust ORM-based data persistence, with **JDBC** facilitating additional database connectivity needs. | |
| - **Transaction Management**: The project uses **Narayana** as the transaction manager implementation, integrated with **Springβs JpaTransactionManager** for distributed transaction support and ensuring transactional integrity. | |
| - **Data Auditing**: **Javers** provides auditing and historical versioning, allowing for tracking and comparing changes to data over time. | |
| - **Business Rules Engine** : **Drools** is integrated into the CIA project to enable a robust business rules engine. | |
| - **Messaging**: **ActiveMQ Artemis** and **Spring JMS** enable asynchronous communication between application components, supporting distributed and event-driven designs. | |
| - **Web/UI Layer**: **Vaadin** powers the UI with a server-driven architecture, providing components like **Vaadin Themes** and **Sass Compiler** for a rich, interactive frontend experience directly in Java. | |
| - **Monitoring**: **JavaMelody** and **AWS SDK for CloudWatch** provide real-time application monitoring and logging capabilities, supporting both local and cloud environments. | |
| - **Testing**: **JUnit**, **Mockito**, **Spring Test** and **Selenium WebDriver** are used extensively for unit, integration, system, browser and mock testing to ensure application reliability and robustness. | |
| - **Utilities**: **Apache Commons**, **Google Guava**, **SLF4J**, and **Logback** offer utility functions and structured logging, enhancing application maintainability and monitoring. | |
| - **Build & Dependency Management**: **Maven** handles project builds, dependency management, and plugin configurations, enabling smooth project management and modular builds. | |
| </div> | |
| ## βοΈ AWS Services Stack | |
| <div align="center"> | |
| ### AWS Infrastructure Components | |
| This document provides a comprehensive summary of the AWS services utilized in the **Citizen Intelligence Agency (CIA)** project infrastructure, as defined by its CloudFormation template. These services work together to ensure a secure, resilient, and scalable deployment environment. | |
| | **Category** | **AWS Services** | **NIST CSF Function, Category & Subcategory** | **ISO 27001:2022 Control & Link** | | |
| |-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | |
| | **Networking and Security** | - [Amazon VPC](https://aws.amazon.com/vpc/): Configures a custom network environment with public/private subnets, route tables, NAT Gateway, Network ACLs (NACLs) for traffic control, and VPC Flow Logs.<br> - [VPC Endpoints](https://docs.aws.amazon.com/vpc/latest/privatelink/): Enables private access to AWS services (e.g., S3, EC2, SSM, CloudWatch Logs).<br> - [AWS WAF](https://aws.amazon.com/waf/): Protects against web attacks at the ALB layer.<br> - [AWS IAM](https://aws.amazon.com/iam/): Manages role-based access control.<br> - [AWS KMS](https://aws.amazon.com/kms/): Manages encryption for data at rest. | **[Identify (ID)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/id/)**:<br> - [Asset Management (ID.AM-2)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/id/am/2/)<br> **[Protect (PR)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/)**:<br> - [Access Control (PR.AC-1, PR.AC-3, PR.AC-5)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ac/)<br> - [Data Security (PR.DS-1, PR.DS-2)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ds/)<br> - [Protective Technology (PR.PT-3)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/pt/3/)<br> **[Detect (DE)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/de/)**:<br> - [Security Continuous Monitoring (DE.CM-3)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/de/cm/3/) | - **A.8.1**: Asset management<br> - **A.9.4.1**: Access control policy<br> - **A.13.1.1**: Network controls<br> - **A.13.1.3**: Segregation in networks<br> - **A.18.1.5**: Regulation and compliance (see [ISO 27001](https://www.iso.org/standard/82875.html)) | | |
| | **Domain and SSL Management** | - [Amazon Route 53](https://aws.amazon.com/route53/): Manages domain registration and DNS routing.<br> - [AWS Certificate Manager (ACM)](https://aws.amazon.com/certificate-manager/): Issues and manages SSL/TLS certificates. | **[Protect (PR)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/)**:<br> - [Data Security (PR.DS-5)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ds/5/)<br> **[Detect (DE)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/de/)**:<br> - [Anomalies and Events (DE.AE-3)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/de/ae/3/) | - **A.10.1.1**: Cryptographic controls for data protection<br> - **A.12.4.3**: Security of network services | | |
| | **Compute** | - [Amazon EC2](https://aws.amazon.com/ec2/): Provides scalable compute instances. | **[Protect (PR)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/)**:<br> - [Protective Technology (PR.PT-1)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/pt/1/)<br> **[Respond (RS)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rs/)**:<br> - [Analysis (RS.AN-1)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rs/an/1/), [Mitigation (RS.MI-2)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rs/mi/2/) | - **A.12.1.3**: Capacity management for IT infrastructure and services | | |
| | **Load Balancing** | - [Application Load Balancer (ALB)](https://aws.amazon.com/elasticloadbalancing/application-load-balancer/): Distributes HTTP/HTTPS traffic across EC2 instances. | **[Protect (PR)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/)**:<br> - [Protective Technology (PR.PT-3)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/pt/3/)<br> **[Respond (RS)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rs/)**:<br> - [Communications (RS.CO-2)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rs/co/2/) | - **A.13.1.1**: Network controls<br> - **A.13.2.1**: Information transfer policies | | |
| | **Data Storage** | - [Amazon S3](https://aws.amazon.com/s3/): Stores application artifacts and logs with encryption, access control, and lifecycle policies.<br> - [Amazon RDS](https://aws.amazon.com/rds/): PostgreSQL database with multi-AZ deployment. | **[Protect (PR)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/)**:<br> - [Data Security (PR.DS-1, PR.DS-5)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ds/)<br> - [Information Protection Processes and Procedures (PR.IP-3, PR.IP-4)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ip/)<br> - [Maintenance (PR.MA-1)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ma/1/)<br> **[Recover (RC)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rc/)**:<br> - [Recovery Planning (RC.RP-1)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rc/rp/1/), [Communications (RC.CO-2)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rc/co/2/) | - **A.8.2.3**: Information backup<br> - **A.10.1.1**: Use of cryptographic controls | | |
| | **Secrets Management** | - [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/): Securely stores and rotates sensitive credentials with Lambda rotation support. | **[Protect (PR)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/)**:<br> - [Access Control (PR.AC-1, PR.AC-4)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ac/)<br> - [Data Security (PR.DS-6)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ds/6/)<br> - [Identity Management and Access Control (PR.AC-7)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ac/7/) | - **A.9.2.2**: User access provisioning<br> - **A.10.1.1**: Management of encryption keys and secret information | | |
| | **Monitoring and Alarms** | - [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/): Provides real-time metrics, logs, and alarms to monitor performance and health. | **[Detect (DE)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/de/)**:<br> - [Security Continuous Monitoring (DE.CM-3)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/de/cm/3/) | - **A.12.4.1**: Monitoring activities | | |
| | **Resilience and Disaster Recovery** | - [AWS Resilience Hub](https://aws.amazon.com/resilience-hub/): Assesses and improves the architectureβs resilience, recommending strategies for fault tolerance and disaster recovery. | **[Recover (RC)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rc/)**:<br> - [Recovery Planning (RC.RP-1)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rc/rp/1/)<br> - [Improvements (RC.IM-1)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/rc/im/1/) | - **A.17.1.2**: Implementing continuity controls<br> - **A.17.2.1**: Availability of information processing facilities | | |
| | **Automation and Maintenance** | - [AWS Systems Manager (SSM)](https://aws.amazon.com/systems-manager/): Automates inventory, patching, and maintenance tasks, with **SSM Maintenance Windows** and **SSM Patch Baselines** for streamlined operations. | **[Protect (PR)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/)**:<br> - [Maintenance (PR.MA-1, PR.MA-2)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/ma/)<br> - [Protective Technology (PR.PT-1)](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/pr/pt/1) | - **A.12.6.1**: Control of technical vulnerabilities<br> - **A.12.7.1**: Information systems audit considerations | | |
| ## AWS Stack Summary | |
| - **Networking and Security**: [Amazon VPC](https://aws.amazon.com/vpc/) creates an isolated network environment with NAT Gateway, NACLs, and VPC Flow Logs. [VPC Endpoints](https://docs.aws.amazon.com/vpc/latest/privatelink/) provide private access to AWS services (e.g., S3, EC2, SSM), [AWS WAF](https://aws.amazon.com/waf/) protects against web attacks, [AWS IAM](https://aws.amazon.com/iam/) secures access control, and [AWS KMS](https://aws.amazon.com/kms/) encrypts data at rest. | |
| - **Domain and SSL Management**: [Amazon Route 53](https://aws.amazon.com/route53/) handles DNS and domain registration, while [AWS Certificate Manager (ACM)](https://aws.amazon.com/certificate-manager/) provides SSL/TLS certificates for HTTPS security. | |
| - **Compute Layer**: [Amazon EC2](https://aws.amazon.com/ec2/) instances host the application, providing flexible and scalable compute resources. | |
| - **Load Balancing**: The [Application Load Balancer (ALB)](https://aws.amazon.com/elasticloadbalancing/application-load-balancer/) distributes HTTP/HTTPS traffic across EC2 instances, optimizing for high availability and resilience. | |
| - **Data Storage**: [Amazon RDS](https://aws.amazon.com/rds/) offers a resilient PostgreSQL setup with multi-AZ deployment and custom parameter groups. [Amazon S3](https://aws.amazon.com/s3/) securely stores artifacts and logs, with lifecycle policies and KMS-managed encryption keys for compliance. | |
| - **Secrets Management**: [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) securely stores and rotates credentials, such as database passwords, with automated Lambda support for rotation. | |
| - **Monitoring and Alarms**: [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/) monitors infrastructure health through metrics, logs, and alarms, enabling proactive management. | |
| - **Resilience and Disaster Recovery**: [AWS Resilience Hub](https://aws.amazon.com/resilience-hub/) assesses and recommends enhancements to improve the system's resilience, providing disaster recovery and fault-tolerant strategies. | |
| - **Automation and Maintenance**: [AWS Systems Manager (SSM)](https://aws.amazon.com/systems-manager/) automates inventory, patching, and other maintenance tasks, increasing operational efficiency. | |
| </div> | |
| For detailed security implementation, see the [Financial Security Plan](FinancialSecurityPlan.md). | |
| ## π Deployment Options | |
| ### AWS CloudFormation Deployment | |
| The Citizen Intelligence Agency can be deployed on AWS using our provided CloudFormation template: | |
| 1. Download the [CloudFormation stack file](cia-dist-cloudformation/src/main/resources/cia-dist-cloudformation.json) | |
| 2. Create a new stack in the AWS CloudFormation console | |
| 3. Upload the template file and configure parameters | |
| 4. Acknowledge IAM resource creation and launch the stack | |
| 5. Access the application via the URL in the stack outputs | |
| #### CloudFormation Stack Diagram | |
|  | |
| ### Debian/Ubuntu Installation | |
| For local or self-hosted deployment on Debian/Ubuntu 24.4+: | |
| 1. Install prerequisites: | |
| ```bash | |
| sudo apt-get install openjdk-21-jdk postgresql-16 postgresql-contrib postgresql-16-pgaudit postgresql-16-pgvector | |
| ``` | |
| 2. Configure PostgreSQL as detailed below. | |
| ## PostgreSQL 16 Configuration Guide | |
| A step-by-step guide to configure PostgreSQL 16 with SSL, prepared transactions, and required extensions. | |
| ### 1. Enable Prepared Transactions and Required Extensions | |
| 1. **Edit** `/etc/postgresql/16/main/postgresql.conf` and add or update the following lines: | |
| ```ini | |
| max_prepared_transactions = 100 | |
| shared_preload_libraries = 'pg_stat_statements, pgaudit, pgcrypto' | |
| pgaudit.log = ddl | |
| pg_stat_statements.track = all | |
| pg_stat_statements.max = 10000 | |
| ``` | |
| 2. **Save and close** the file. | |
| ### 2. Update `pg_hba.conf` for IPv6 Loopback Access | |
| 1. **Edit** `/etc/postgresql/16/main/pg_hba.conf` and add the following line: | |
| ```ini | |
| host all all ::1/128 md5 | |
| ``` | |
| 2. **Save and close** the file. | |
| ### 3. Generate SSL Certificates and Keys | |
| 1. Generate a secure random passphrase: | |
| ```bash | |
| openssl rand -base64 48 > passphrase.txt | |
| ``` | |
| 2. Create a passphrase-protected private key: | |
| ```bash | |
| openssl genrsa -des3 -passout file:passphrase.txt -out server.pass.key 2048 | |
| ``` | |
| 3. Remove the passphrase protection from the private key: | |
| ```bash | |
| openssl rsa -passin file:passphrase.txt -in server.pass.key -out server.key | |
| rm server.pass.key | |
| ``` | |
| 4. Create a Certificate Signing Request (CSR): | |
| ```bash | |
| openssl req -new -key server.key -out server.csr \ | |
| -subj "/C=UK/ST=Postgresqll/L=Docker/O=Hack23/OU=demo/CN=127.0.0.1" | |
| ``` | |
| 5. Self-sign the certificate (valid for 10 years / 3650 days): | |
| ```bash | |
| openssl x509 -req -days 3650 -in server.csr -signkey server.key -out server.crt | |
| ``` | |
| 6. Clean up temporary files: | |
| ```bash | |
| rm passphrase.txt | |
| rm server.csr | |
| ``` | |
| ### 4. Deploy the SSL Certificate and Key for PostgreSQL | |
| 1. Copy the new certificate and key into the PostgreSQL data directory: | |
| ```bash | |
| cp server.crt /var/lib/postgresql/16/main/server.crt | |
| cp server.key /var/lib/postgresql/16/main/server.key | |
| rm server.key | |
| ``` | |
| 2. Secure the certificate and key: | |
| ```bash | |
| chmod 700 /var/lib/postgresql/16/main/server.key | |
| chmod 700 /var/lib/postgresql/16/main/server.crt | |
| chown -R postgres:postgres /var/lib/postgresql/16/main/ | |
| ``` | |
| 3. Enable SSL in PostgreSQL by adding the following lines to | |
| `/etc/postgresql/16/main/postgresql.conf`: | |
| ```bash | |
| echo "ssl_cert_file = '/var/lib/postgresql/16/main/server.crt'" \ | |
| >> /etc/postgresql/16/main/postgresql.conf | |
| echo "ssl_key_file = '/var/lib/postgresql/16/main/server.key'" \ | |
| >> /etc/postgresql/16/main/postgresql.conf | |
| ``` | |
| ### 5. Provide SSL Certificate to the `cia` User | |
| 1. Create a `.postgresql` directory for the `cia` user: | |
| ```bash | |
| mkdir -p /opt/cia/.postgresql | |
| ``` | |
| 2. Copy the server certificate into this directory: | |
| ```bash | |
| cp server.crt /opt/cia/.postgresql/root.crt | |
| chmod 700 /opt/cia/.postgresql/root.crt | |
| chown -R cia:cia /opt/cia/.postgresql/root.crt | |
| ``` | |
| 3. Remove the server certificate from the current directory (if desired): | |
| ```bash | |
| rm server.crt | |
| ``` | |
| ### 6. Performance Tuning (Recommended) | |
| For optimal performance with the CIA platform's 85+ views and 93 tables, add the following settings to `/etc/postgresql/16/main/postgresql.conf`. Values should be adjusted based on your server's available RAM. | |
| #### Memory Settings | |
| Configure memory settings proportionally to your system RAM: | |
| | Setting | 4GB RAM | 8GB RAM | 16GB+ RAM (Production) | | |
| |--------------------------|---------|---------|------------------------| | |
| | `shared_buffers` | 1GB | 2GB | 4GB | | |
| | `effective_cache_size` | 3GB | 6GB | 12GB | | |
| | `maintenance_work_mem` | 256MB | 512MB | 1GB | | |
| | `work_mem` | 16MB | 32MB | 50MB | | |
| Apply settings using SQL commands (use values from the table above for your RAM configuration): | |
| ```sql | |
| -- Example for 8GB RAM server - adjust values from the table above for your configuration | |
| -- shared_buffers: ~25% of RAM | |
| -- effective_cache_size: ~75% of RAM | |
| -- maintenance_work_mem: For VACUUM, CREATE INDEX operations | |
| -- work_mem: Per-operation memory for sorts, joins | |
| ALTER SYSTEM SET shared_buffers = '2GB'; | |
| ALTER SYSTEM SET effective_cache_size = '6GB'; | |
| ALTER SYSTEM SET maintenance_work_mem = '512MB'; | |
| ALTER SYSTEM SET work_mem = '32MB'; | |
| ``` | |
| #### Checkpoint Settings | |
| Configure checkpoint settings for optimal write performance: | |
| ```sql | |
| ALTER SYSTEM SET checkpoint_completion_target = 0.9; | |
| ALTER SYSTEM SET wal_buffers = '16MB'; | |
| ALTER SYSTEM SET max_wal_size = '4GB'; | |
| ALTER SYSTEM SET min_wal_size = '1GB'; | |
| ``` | |
| #### Query Planning Optimizations | |
| For SSD storage (recommended), optimize query planning: | |
| ```sql | |
| ALTER SYSTEM SET random_page_cost = 1.1; -- For SSD storage | |
| ALTER SYSTEM SET effective_io_concurrency = 200; -- For SSD storage | |
| ``` | |
| #### Connection Settings | |
| Configure connection limits: | |
| ```sql | |
| ALTER SYSTEM SET max_connections = 200; | |
| ``` | |
| #### Apply Settings | |
| After making changes, apply them: | |
| ```bash | |
| # Reload configuration (for settings that don't require restart) | |
| sudo -u postgres psql -c "SELECT pg_reload_conf();" | |
| # For settings requiring restart (shared_buffers, max_connections): | |
| sudo systemctl restart postgresql | |
| ``` | |
| #### Verify Settings | |
| Confirm settings are applied: | |
| ```sql | |
| -- Check current settings | |
| SHOW shared_buffers; | |
| SHOW effective_cache_size; | |
| SHOW work_mem; | |
| SHOW maintenance_work_mem; | |
| SHOW checkpoint_completion_target; | |
| SHOW random_page_cost; | |
| SHOW max_connections; | |
| ``` | |
| > **π Note:** For detailed performance tuning guidelines, database health monitoring, and advanced configuration options, see [service.data.impl/README-SCHEMA-MAINTENANCE.md](service.data.impl/README-SCHEMA-MAINTENANCE.md). | |
| ### Final Steps | |
| 1. **Restart PostgreSQL** to apply all changes: | |
| ```bash | |
| systemctl restart postgresql | |
| ``` | |
| 2. Verify that PostgreSQL is running with SSL by checking the logs or using an SSL-enabled client. | |
| 3. Confirm that prepared transactions and required extensions are enabled: | |
| ```sql | |
| SHOW max_prepared_transactions; | |
| \dx | |
| ``` | |
| 4. Confirm the new IPv6 entry in `pg_hba.conf` is functioning as expected by connecting via `psql` over `::1`. | |
| ## Database Setup | |
| Create an empty database: | |
| Below instructions set the default username/password and database name used for development. We recommend using custom credentials and updating the configuration at `/opt/cia/webapps/cia/WEB-INF/database.properties` to define your own username/password and database name. | |
| ```bash | |
| $ sudo su - postgres | |
| $ psql | |
| postgres=# CREATE USER eris WITH password 'discord'; | |
| postgres=# CREATE DATABASE cia_dev; | |
| postgres=# GRANT ALL PRIVILEGES ON DATABASE cia_dev to eris; | |
| ``` | |
| ## Install CIA Debian Package | |
| 1. Download the CIA Debian package: | |
| ```bash | |
| wget https://github.com/Hack23/cia/releases/download/2025.1.2/cia-dist-deb-2025.1.2.all.deb | |
| ``` | |
| 2. Install the Debian package: | |
| ```bash | |
| sudo dpkg -i cia-dist-deb-2025.1.2.all.deb | |
| ``` | |
| 3. Access the server at [https://localhost:28443/cia/](https://localhost:28443/cia/). | |
| ## π Political Dashboards | |
| - **English**: Our [dashboard](https://github.com/Hack23/cia/blob/master/dashboard.md) provides comprehensive analytics on Swedish political figures and institutions. | |
| - **Swedish**: VΓ₯r [dashboard](https://github.com/Hack23/cia/blob/master/dashboard_sv.md) erbjuder en detaljerad ΓΆversikt ΓΆver politiska figurer och olika departement i Sverige. | |
| ## π€ AI and Data Visualization | |
| This project is powered by advanced AI technologies for data processing and analysis. We integrate data from various open sources and visualize findings through modern data visualization tools. | |
| For our future vision incorporating more advanced AI capabilities, see our [Future Architecture Vision](FUTURE_MINDMAP.md). | |
| ## ποΈ Citizen Intelligence Agency Project Classification | |
| ### π― Project Classification | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#project-type-classifications) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#project-type-classifications) | |
| ### π Security Classification | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#confidentiality-levels) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#integrity-levels) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#availability-levels) | |
| ### β±οΈ Business Continuity | |
| [-yellow?style=for-the-badge&logo=clock&logoColor=white)](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#rto-classifications) | |
| [-lightgreen?style=for-the-badge&logo=database&logoColor=white)](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#rpo-classifications) | |
| ### π° Business Impact Analysis Matrix | |
| | Impact Category | Financial | Operational | Reputational | Regulatory | | |
| |-----------------|-----------|-------------|--------------|------------| | |
| | **π Confidentiality** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#financial-impact-levels) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#operational-impact-levels) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#reputational-impact-levels) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#regulatory-impact-levels) | | |
| | **β Integrity** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#financial-impact-levels) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#operational-impact-levels) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#reputational-impact-levels) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#regulatory-impact-levels) | | |
| | **β±οΈ Availability** | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#financial-impact-levels) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#operational-impact-levels) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#reputational-impact-levels) | [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#regulatory-impact-levels) | | |
| ### π‘οΈ Security Investment Returns | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#security-investment-returns) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#security-investment-returns) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#security-investment-returns) | |
| ### π― Competitive Differentiation | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#competitive-differentiation) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#competitive-differentiation) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#competitive-differentiation) | |
| ### π Porter's Five Forces Strategic Impact | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#porters-five-forces) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#porters-five-forces) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#porters-five-forces) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#porters-five-forces) | |
| [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#porters-five-forces) | |
| ## π Related Documents | |
| ### ποΈ Architecture & Design | |
| - [ποΈ Architecture Documentation](ARCHITECTURE.md) - C4 model system architecture | |
| - [π§ System Mindmaps](MINDMAP.md) - Conceptual overview and component relationships | |
| - [π Future Architecture Vision](FUTURE_MINDMAP.md) - AI-enhanced capabilities roadmap | |
| - [π Data Model](DATA_MODEL.md) - Database schema and entity relationships | |
| - [ποΈ Entity Model Documentation](https://hack23.github.io/cia/service.data.impl/hbm2doc/entities/index.html) - Detailed database entity reference | |
| - [π API Documentation](https://hack23.github.io/cia/apidocs/index.html) - Complete API reference | |
| - [π¦ Package Dependencies](https://hack23.github.io/cia/apidocs/package-dependencies.svg) - Visual code package structure | |
| ### π‘οΈ Security & Compliance | |
| - [π Security Architecture](SECURITY_ARCHITECTURE.md) - Defense-in-depth security implementation | |
| - [π Future Security Architecture](FUTURE_SECURITY_ARCHITECTURE.md) - Advanced security capabilities roadmap | |
| - [π― Threat Model](THREAT_MODEL.md) - STRIDE/MITRE ATT&CK threat analysis | |
| - [π ISMS Compliance Mapping](ISMS_COMPLIANCE_MAPPING.md) - Complete ISMS-PUBLIC policy integration | |
| - [π° Financial Security Plan](FinancialSecurityPlan.md) - AWS security deployment and costs | |
| - [π CRA Assessment](CRA-ASSESSMENT.md) - EU Cyber Resilience Act compliance | |
| - [π Security Policy](SECURITY.md) - Vulnerability disclosure and security reporting | |
| ### π Operations & Development | |
| - [β‘ Workflows](WORKFLOWS.md) - CI/CD pipelines and DevSecOps automation | |
| - [π End-of-Life Strategy](End-of-Life-Strategy.md) - Technology maintenance and lifecycle planning | |
| - [π§ͺ Unit Test Plan](UnitTestPlan.md) - Testing strategy and coverage requirements | |
| - [π E2E Test Plan](E2ETestPlan.md) - End-to-end testing documentation | |
| - [π€ Contributing Guidelines](CONTRIBUTING.md) - Development contribution guide | |
| - [π Code of Conduct](CODE_OF_CONDUCT.md) - Community standards and expectations | |
| ### π¨ Features & Dashboards | |
| - [β¨ CIA Features Showcase](https://hack23.com/cia-features.html) - Comprehensive feature demonstrations | |
| - [π Political Dashboard (English)](dashboard.md) - Swedish political analytics | |
| - [π Politisk Dashboard (Svenska)](dashboard_sv.md) - Svensk politisk analys | |
| ### π€ AI & Development Tools | |
| - [π€ GitHub Copilot Instructions](.github/copilot-instructions.md) - AI-assisted development guidelines | |
| - [π₯ Custom Copilot Agents](.github/agents/README.md) - Specialized AI agents for different project aspects | |
| ### π ISMS-PUBLIC Policy Framework | |
| *These policies from Hack23 AB's public ISMS govern this project's security and development practices:* | |
| - [π οΈ Secure Development Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Secure_Development_Policy.md) - SDLC security requirements (80% coverage minimum) | |
| - [π Information Security Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Information_Security_Policy.md) - Overall security governance framework | |
| - [π·οΈ Classification Framework](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) - Data classification and business impact analysis | |
| - [π― Threat Modeling Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Threat_Modeling.md) - STRIDE framework and threat analysis methodology | |
| - [π Vulnerability Management](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Vulnerability_Management.md) - Security testing and remediation processes | |
| - [π¨ Incident Response Plan](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Incident_Response_Plan.md) - Security incident handling procedures | |
| - [π Network Security Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Network_Security_Policy.md) - Network protection and segmentation | |
| - [π Access Control Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Access_Control_Policy.md) - Identity and access management | |
| - [π Cryptography Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Cryptography_Policy.md) - Encryption standards and key management | |
| - [πΎ Backup & Recovery Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Backup_Recovery_Policy.md) - Data protection and recovery procedures | |
| For complete ISMS framework, visit: [](https://github.com/Hack23/ISMS-PUBLIC) | |
| --- | |
| **π Project Classification:** | |
| **π·οΈ Classification:** [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#confidentiality-levels) [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#integrity-levels) [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md#availability-levels) | |
| **π Project Type:** Data Analytics Platform (OSINT) | **βοΈ Process Type:** Operations | |
| **π― Framework Compliance:** [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) [](https://github.com/Hack23/ISMS-PUBLIC/blob/main/CLASSIFICATION.md) | |