Follow container hardening process for IB pipeline image

This template is ONLY used for enhancement requests. Bug reporting or new feature request issues should use the other template options for issue submission.

Current Behavior

Purpose

Our goal is to only use hardened containers for each stage in the pipeline. Within our design for this, we've decided there is a need for an all-in-one container that runs most of the pipeline, while using already hardened and approved containers for Anchore and ClamAV. To fit this need, we had to create a custom container for the pipeline based off of Redhat's python36 image, and now we're going through the process of hardening it.

Plan

• justifications
• security signoff
• PM signoff

Acceptance Criteria

• submitted to Nic for review
• container approved