Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Submitted
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Mar 20, 2024

RELATED IDEAS

Secure DevOps Buildchain / Deployment Artifact Validation

Before deploying packages to systems, it should be verified validate that release artifacts to be deployed are the same artifacts that were built via the build chain. Artifacts are looked up via their fingerprint (e.g. binary checksum) and verified to have a valid build provenance. This prevents that packages can be tampered with and and malicious code injected into the binaries.

A possible solution to this would be that buztool calculates a fingerprint (e.g. sha256) of the created package and stores the hash as a component version property. Before deploying a component version, it validates the fingerprint again after downloading the package from the artifact repository and aborts the deployment process if the checksum does not match.

Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.