enforcer-5.0 issueshttps://repo1.dso.mil/dsop/aqua-security/enterprise/enforcer-5.0/-/issues2021-09-08T17:37:09Zhttps://repo1.dso.mil/dsop/aqua-security/enterprise/enforcer-5.0/-/issues/5Archive request2021-09-08T17:37:09ZAviv ShavitArchive request## Summary
Requesting this application be archived due to one of the following reasons:
- [x] Version is no longer supported by vendor
- [ ] Application is End-Of-Life
- [ ] License violation.
- [ ] Other. See below.
## Detailed Descri...## Summary
Requesting this application be archived due to one of the following reasons:
- [x] Version is no longer supported by vendor
- [ ] Application is End-Of-Life
- [ ] License violation.
- [ ] Other. See below.
## Detailed Description
Aqua will no longer update version 5.0 on the Ironbank
## Definition of Done
- [ ] Application has been reviewed for archival
- [ ] Project is officially marked as stale
- [ ] Iron Bank frontend no longer lists application as available or approvedAl FontaineAl Fontainehttps://repo1.dso.mil/dsop/aqua-security/enterprise/enforcer-5.0/-/issues/4chore(findings): aqua-security/enterprise/enforcer-5.02021-06-24T16:05:21Zsean.melissarichore(findings): aqua-security/enterprise/enforcer-5.0
## Summary
aqua-security/enterprise/enforcer-5.0 has 15 new findings discovered during continuous monitoring.
| id | source | package |
| -- | ------ | ------- |
| CVE-2021-20231 | anchore_cve | gnutls-3.6.14-7.el8_3 |
| CVE-2021-2023...
## Summary
aqua-security/enterprise/enforcer-5.0 has 15 new findings discovered during continuous monitoring.
| id | source | package |
| -- | ------ | ------- |
| CVE-2021-20231 | anchore_cve | gnutls-3.6.14-7.el8_3 |
| CVE-2021-20232 | anchore_cve | gnutls-3.6.14-7.el8_3 |
| CVE-2021-20305 | anchore_cve | gnutls-3.6.14-7.el8_3 |
| CVE-2021-20305 | anchore_cve | nettle-3.4.1-2.el8 |
| CVE-2021-23840 | anchore_cve | openssl-1.1.1g-15.el8_3 |
| CVE-2021-23841 | anchore_cve | openssl-1.1.1g-15.el8_3 |
| CVE-2020-13776 | anchore_cve | systemd-libs-239-41.el8_3.1 |
| CVE-2021-20305 | oscap_cve | gnutls |
| RHSA-2021:1206 | oscap_cve | gnutls |
| CVE-2021-20231 | twistlock_cve | gnutls-3.6.14-7.el8_3 |
| CVE-2021-20232 | twistlock_cve | gnutls-3.6.14-7.el8_3 |
See csv output stage for complete list of new findings.
## Definition of Done
Justifications:
- [ ] All findings have been justified
- [ ] Justifications have been provided to the container hardening team
- [ ] Approval label has been applied
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:
- [ ] Findings Approver has reviewed and approved all justifications
- [ ] Approval request has been sent to Authorizing Official
- [ ] Approval request has been processed by Authorizing Official
Note: If the above approval process is kicked back for any reason, the Approval label will be removed and the issue will be sent back to Open. Any comments will be listed in this issue for you to address. Once they have been addressed, you may re-add the Approval label.Al FontaineAl Fontainehttps://repo1.dso.mil/dsop/aqua-security/enterprise/enforcer-5.0/-/issues/3update application to release 5.0.203342020-12-28T18:17:27ZAviv Shavitupdate application to release 5.0.20334## Summary
Requesting application be updated to a newer version.
branch aqua_5.0.20334_update
## Version Information
Current version: 5.0.0
Updated version: 5.0.20344
Under support: minor release under support
## Definition of D...## Summary
Requesting application be updated to a newer version.
branch aqua_5.0.20334_update
## Version Information
Current version: 5.0.0
Updated version: 5.0.20344
Under support: minor release under support
## Definition of Done
Hardening:
- [x] Container builds successfully
- [x] Container version has been updated in greylist file
- [x] Branch has been merged into `development`
No new findings:
- [x] There are no new findings in this update. Skip the Justifications and Approval Process steps and apply the label ~"Approval".
Justifications:
- [ ] All findings have been justified per the above documentation
- [ ] Justifications have been provided to the container hardening team
Approval Process:
- [ ] 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 OfficialAl FontaineAl Fontainehttps://repo1.dso.mil/dsop/aqua-security/enterprise/enforcer-5.0/-/issues/2aqua enforcer-5.0 initial2021-04-28T10:28:10ZAl Fontaineaqua enforcer-5.0 initial## Summary
Requesting application to be hardened. This is only for initial hardening of a container.
## Version Information
Current version: (State the current version of the application as you see it)
Under support: (Is the updated...## Summary
Requesting application to be hardened. This is only for initial hardening of a container.
## Version Information
Current version: (State the current version of the application as you see it)
Under support: (Is the updated version within the same major version of the application or is this a new major version?)
## Definition of Done
Hardening:
- [x] Container builds successfully
- [x] Greylist file has been created (requires a member from container hardening)
- [x] Branch has been merged into `development`
Justifications:
- [x] All findings have been justified per the above documentation
- [x] Justifications have been provided to the container hardening team
Approval Process (container hardening team processes):
- [x] Peer review from Container Hardening Team
- [x] Findings Approver has reviewed and approved all justifications
- [x] Approval request has been sent to Authorizing Official
- [x] Approval request has been processed by Authorizing OfficialAl FontaineHunter StevensAl Fontainehttps://repo1.dso.mil/dsop/aqua-security/enterprise/enforcer-5.0/-/issues/1Initial container hardening2020-10-14T20:11:44ZbalexandInitial container hardening## Summary
Requesting application to be hardened. This is only for initial hardening of a container.
## Version Information
Current version: (State the current version of the application as you see it)
Under support: (Is the update...## Summary
Requesting application to be hardened. This is only for initial hardening of a container.
## Version Information
Current version: (State the current version of the application as you see it)
Under support: (Is the updated version within the same major version of the application or is this a new major version?)
## Definition of Done
Hardening:
- [ ] Container builds successfully
- [ ] Greylist file has been created (requires a member from container hardening)
- [ ] Branch has been merged into `development`
Justifications:
- [ ] All findings have been justified per the above documentation
- [ ] Justifications have been provided to the container hardening team
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