## Summary Requesting application to be hardened. This is only for iInitial hHardening of a container. ## Version Information Current version: (State the current version of the application as you see it) ## Communication All communication should occur through this issue. This ensures that all information is documented in a centralized location and also ensures that all of the assignees are notified of updates. It is imperative that all required parties are listed as assignees of this issue and that individuals are not removed. Please do not remove anyone from the assignee list. If you need to contact the Container Hardening team, please identify your assigned point of contact. You can find your point of contact by: 1. They should be listed as an assignee on this ticket 2. They should be listed in the `hardening_manifest.yaml` file under the `maintainers` section with a field of `cht_member: true` If you have no assignee, feel free to tag Container Hardening leadership in your issue by commenting on this issue with your questions/concerns and then add `/cc @ironbank-notifications/leadership`. Gitlab will automatically notify all Container Hardening leadership to look at this issue and respond. ## Responsibilities If this application is owned by a Contributor or Vendor (identifed as `Owner::Contributor` and `Owner::Vendor` respectively), then it is your responsibility to drive this issue through completion. This means that the Container Hardening team is not here to help push any deadlines/timeframes you may have with other customers or DoD agencies. If you have issues with the activity, you may notify Container Hardening leadership above. Do not change the ownership labels.ed Container Submission for JupyterHub's k8s-image-awaiter. ## Version Information Current version: 0.11.1 ## Definition of Done Hardening: - [ ] Hardening manifest is created and adheres to the schema (https://repo1.dsop.io/ironbank-tools/ironbank-pipeline/-/blob/master/schema/hardening_manifest.schema.json) - [ ] Container builds successfully through the Gitlab CI pipeline - [ ] Branch has been merged into `development` - [ ] Project is configured for automatic renovate updates (if possible) Justifications: - [ ] All findings have been justified per the above documentation - [ ] Justifications have been attached to this issue - [ ] Apply the label `Approval` to indicate this container is ready for the approval phase Note: The justifications must be provided in a timely fashion. Failure to do so could result in new findings being identified which may start this process over. Approval Process (Container Hardening Team processes): - [ ] Peer review from Container Hardening Team - [ ] Findings Approver has reviewed and approved all justifications - [ ] Approval request has been sent to Authorizing Official - [ ] Approval request has been processed by Authorizing Official