Eclipse Foundation-Project
Published deadline passed
The published deadline has passed. For multi-stage competitions a later tender deadline may still apply — check the notice or portal for the current phase.
- Qualification deadline
- Aug 6, 2024Expired
- Procedure
- Without prior noticeTwo stages
- Agreement
- Buying services
Brief
As a research and development service, the contract is excluded from the scope of public procurement law (cf. § 116(1)(2) GWB). The Eclipse Foundation AISBL is the host to some of the most widely utilized Java-based open source technologies, including Eclipse Jetty, Jakarta EE, Eclipse IDE, and Eclipse Glassfish. Part of the project is the implementation of improvements to the Eclipse Foundation projects’ infrastructure and security. The procurements objective is to help some of the key projects of the Eclipse Foundation to harden their software supply chain, by continuously monitoring for new vulnerabilities and generating Software Bills of Materials. This is key to mitigate the major threats to their supply chain and the one of their downstream consumers. The proposed activities contribute to the improvement and maintenance of Eclipse Foundation projects, especially with regard to security and resilience. Th Eclipse-Project will mainly focus on two work packages. A first objective would be to have projects generate a Software Bill of Materials (SBOM) as part of their build pipelines. An SBOM is a list of all the software components, dependencies, and metadata associated with an application. A second objective would be to continue to improve the vulnerability management processes. The activities for this objective would be: - Implement a continuous vulnerability monitoring solution. This will help identify vulnerabilities in project dependencies as soon as they are discovered, even after the software has been released. - Educate the developers and maintainers on how to handle vulnerability reports from researchers. This includes understanding how to triage vulnerabilities, prioritize them, and remediate them effectively. - Invest in tooling to help manage and fix vulnerabilities. This could include a vulnerability scanner, a vulnerability management platform, or other tools that can help to automate the process of remediating vulnerabilities.
Forskning og utdanning
Result
- Eclipse Foundation AISBLWinner
- 0Number of tenders received
- Not statedContract value
Previous winners
Who are you up against?
The suppliers who have won similar contracts at SPRIND GmbH
Will you bid?
The agent sets up the bid and writes the first draft. Free for 14 days.
From the notice
As a research and development service, the contract is excluded from the scope of public procurement law (cf. § 116(1)(2) GWB). The Eclipse Foundation AISBL is the host to some of the most widely utilized Java-based open source technologies, including Eclipse Jetty, Jakarta EE, Eclipse IDE, and Eclipse Glassfish. Part of the project is the implementation of improvements to the Eclipse Foundation projects’ infrastructure and security. The procurements objective is to help some of the key projects of the Eclipse Foundation to harden their software supply chain, by continuously monitoring for new vulnerabilities and generating Software Bills of Materials. This is key to mitigate the major threats to their supply chain and the one of their downstream consumers. The proposed activities contribute to the improvement and maintenance of Eclipse Foundation projects, especially with regard to security and resilience. Th Eclipse-Project will mainly focus on two work packages. A first objective would be to have projects generate a Software Bill of Materials (SBOM) as part of their build pipelines. An SBOM is a list of all the software components, dependencies, and metadata associated with an application. A second objective would be to continue to improve the vulnerability management processes. The activities for this objective would be: - Implement a continuous vulnerability monitoring solution. This will help identify vulnerabilities in project dependencies as soon as they are discovered, even after the software has been released. - Educate the developers and maintainers on how to handle vulnerability reports from researchers. This includes understanding how to triage vulnerabilities, prioritize them, and remediate them effectively. - Invest in tooling to help manage and fix vulnerabilities. This could include a vulnerability scanner, a vulnerability management platform, or other tools that can help to automate the process of remediating vulnerabilities.
Contact
INFO@SPRIND.ORG- Result · PrequalificationType
- 73110000Main codeResearch services
- 73300000Design and execution of research and development