GitLab

Issue was dropped due to lack of response from external contributor

All work is owned by members of the Container Hardening Team within Iron Bank

A Vendor is managing the containerization and updates to this product. All work is owned by the vendor with the exception of the approval process.

Issues that are dropped for various reasons: no response, no longer needed, etc.

Label used for tracking metrics on Renovate automation

Final notification after 42 days of inactivity, the issue is being moved to Iron Bank Leadership to adjudicate why no work is happening.

An Automated label to notify of inactivity - applied after 28 days of no update to the issue

An Automated label to notify of inactivity - applied after 14 days of no update to the issue

Containers that have new findings based on continuous monitoring, that need to be addressed before being approved again. 

Initial hardening of container: This is the first time a container is going through the Iron Bank pipeline.

Containers whose approval is expiring soon

General questions

The container is going through an Official Review from the authorizing official and we are awaiting the final approval and or comments.

The container is going through Local Security Review prior to a Local Review for approval (we are aiming for an average of 3-5 business days) for this stage.

The container is going through Local Review prior to final submission for approval (we are aiming for an average of 3-5 business days) for this stage.

Awaiting response from contributor

Containers that are being updated to a new version

Questions for onboarding team

Questions for leadership