We are using the provided alfresco enterprise containers to deploy Alfresco in the Azure Kubernetes Cluster.
In terms of container security we are using trivy to scan the images for vulnerabilities.
We have used trivy to scan the acs image in version 7.0.1 with following command:
trivy -d quay.io/alfresco/alfresco-content-repository:7.0.1
The result is:
quay.io/alfresco/alfresco-content-repository:7.0.1 (centos 8.4.2105)
====================================================================
Total: 337 (UNKNOWN: 0, LOW: 139, MEDIUM: 178, HIGH: 16, CRITICAL: 4)
Even the new Alfresco Content repository 7.1.0 image has several known security issues, even more than the older version.
quay.io/alfresco/alfresco-content-repository:7.1.0 (centos 7.9.2009)
====================================================================
Total: 810 (UNKNOWN: 0, LOW: 410, MEDIUM: 389, HIGH: 9, CRITICAL: 2)
Fun fact: For the newer version of acs there is a os-downgrade to centos 7.9 (instead of centos 8.4 in acs-7.0.1), so it would explain the higher number of issues.
For me these results are not acceptable as we need to deploy a docker container of an Enterprise software on a customer platform with high and critical issues.
@angelborroy : Do you know more about the process behind docker container updates and fixing security issues? Do you already scan your docker images for security issues? Do you know where to submit these issues- In the github project https://github.com/Alfresco/acs-packaging/ or as support ticket?
