chore(SprintOrg): Prepare for the upcoming Sprint

[lolaapenna]

Task Description*
To organize all Apeiro and Heureka sprint activities

Acceptance Criteria:

• Apeiro Backlog: Review committed epics for sprint 12
• Apeiro Backlog: Outline stakeholder-understandable epics planned for Sprint 13
• Apeiro Backlog: Review Apeiro commitments in the next Heureka Core Meeting on 11th Dec.
• Apeiro Backlog: Update Apeiro project board - Next Apeiro Monthly backlog meeting takes place on 13th Dec.
• Heureka Backlog: Review committed epics for sprint 12
• Heureka Backlog: Outline epics for sprint 13

[lolaapenna]

For Apeiro

Post-User interviews activities

Continuous scan update
The job tracking (improved scanner) protocol has been completed - enable comms between scanners and heureka core
Distributed, asynchronous and fault tolerant

[lolaapenna]

Apeiro Management Updtes

Epics for Takt 13

1. (heureka): Implement Continuous Scans for the Scanners#30

Update:
The job tracking protocol for the improved scanner has been completed. This enables communication between the scanners and the Heureka core. The system is now distributed, asynchronous, and fault-tolerant, ensuring robust and efficient operations.

2. (heureka): Enable Multiple Clusters for the Scanners#29

No Update - Probably move 2 sprints ahead

3. (heureka): Requirements Definition for Remediation Management

### Description
Following the user interviews conducted during the workshop, user feedback on existing implementations as well as expectations regarding the remediation of issues will be translated to define requirements for the Remediation Management feature of Heureka.

### Objectives
Understand common challenges: analyze the difficulties users experience with the current patch management process to inform feature development.
Cluster user expectations: consolidate user suggestions for the remediation management feature of Heureka.
Prioritize development efforts: assess and prioritize potential features and improvements based on the feedback and their anticipated impact on efficiency.
Enhance UX: Improve the overall user experience by addressing pain points on the current state of Heureka.

### Acceptance Criteria
- [ ] Break down the requirements into smaller, actionable tasks or user stories. 
- [ ] Conduct a detailed analysis of user interview data to identify key themes and challenges related to remediation management.
- [ ] Compile a list of user-suggested features and improvements, categorizing them by priority and feasibility.
- [ ] Develop a prioritized roadmap for feature implementation based on user feedback and strategic goals.
- [ ] Document all requirements clearly and concisely, ensuring they are actionable and measurable.
- [ ] Review the finalized requirements before proceeding to development.

4. **(heureka): Deployment of the Scanners**

### Description
The implementation of a CI/CD build and deployment Pipeline for Heureka.

### Objectives
To streamline and automate the process of integrating code changes, testing, and deployments.

### Acceptance Criteria
- [ ] Enablement for Deployment Implementations
- [ ] Documentation for Deployment Implementations
- [ ] Deployment for Heureka Core
- [ ] Deployment for Keppel
- [ ] Deployment for NVD Scanner
- [ ] Deployment for K8s Assets Scanner

Epics For Takt 14

**(heureka): Enable Multiple Clusters for the Scanners**

### Description
We currently only scan 2 clusters without scanning within the cluster (local scan). We need to onboard multiple clusters and scan from within the clusters. 

### Objectives
- Work on the Deployment of Scanners to multiple clusters
- Investigate further potential errors occurring on additional data sets
- Maintain or improve the performance and accuracy of the scanners based on new data sets

### Acceptance Criteria
- [ ] Kubernetes Scanner is enabled and running on multiple clusters
- [ ] Image Scanner is enabled and running on multiple clusters
- [ ] Scanner Logs are available for investigation 
- [ ] Scans occur at least daily
- [ ] Heureka db partially wiped daily to ensure remediated issues disappear (workaround)

(heureka): Implement Ordering of Primary Entities
----Service and Issue Match Ordering

[lolaapenna]

Sprint 12/24 Retrospective

Duration Nov 18 - Dec 15

Planned Epics

• December Workshop (Req for Remediation Management + 2025 Roadmap)
• Deployment of the Scanners
• Implement Continuous Scans for the Scanners
• Implement Authentication
• Implement Ordering for IssueMatch and Service
• Implement Hardening Guide 2.1 Compliance Scan
• Conduct Design Sessions for the Implementation of OpenStack Compliance Scan

Closed Epics:

• December Workshop (Req for Remediation Management + 2025 Roadmap)
• Conduct Design Sessions for the Implementation of OpenStack Compliance Scan

Touched Epics:

• Deployment of the Scanners
• Implement Continuous Scans for the Scanners
• Implement Authentication
• Implement Hardening Guide 2.1 Compliance Scan
• Implement Ordering for IssueMatch and Service

Untouched Epics

Sprint 13/24 Planning

Duration Dec 17 - Jan 12

Sprint Goal: Demo-able PoC

---- Consideration - Have fun names for sprints eg. names of stars from the galaxies, or figures from star wars, lord of the rings, 1st (some characters of the month) character of the month, famous mathematicians,.

Availability:

Vacations: Hoda - 4 weeks, Michael, Wolfram, Dusrin - 2 weeks, public holiday, Victor - 2 weeks,

Rolled-over Epics – Touched Epics from 12/24

• Deployment of the Scanners
• Implement Continuous Scans for the Scanners
• Implement Authentication
• Implement Hardening Guide 2.1 Compliance Scan
• Implement Ordering for IssueMatch and Service

Planned Epics

• December Workshop (Req for Remediation Management + 2025 Roadmap)
• Deployment of the Scanners
• Implement Continuous Scans for the Scanners
• Implement Authentication
• Implement Ordering for IssueMatch and Service
• Implement Hardening Guide 2.1 Compliance Scan
• Conduct Design Sessions for the Implementation of OpenStack Compliance Scan