When going to Compliance Management and then selecting a specific compliance package to analyze, the grid comes up with the overall status for that item.
However, I noticed that Eramba doesn’t seem to be sorting by ItemID correctly. See below - 9.10 should be the last item in this list, as it is the last PCI requirement under section 9. However, it comes after 9.1.3 and before 9.2:
Thanks,
-Noah
This is strange, we are sorting by the first column already.
Can you share the compliance package you are using with support@eramba.org (or here if you dont mind) so we have a look by testing it?
I used the PCI DSS 3.2 compliance package linked from the Eramba documentation (here: https://s3-eu-west-1.amazonaws.com/erambacompliancepackages/pci-dss-3.2.csv). Will email the actual copy of the file that I used to support.
Thanks,
-Noah
Hi all,
I just checked and am still having this problem. It appears the same thing is happening in a different Eramba Compliance package (a custom one I created).
Instead of going 10.1, 10.2, 10.3, etc., it goes 10.1, 10.10, 10.11, 10.2, etc.
Screenshot here:
Any thoughts?
Thanks,
-Noah
I have the same issue, workaround that I’m using at the moment
10.01
10.02
sorry guys , did not see this until now …
https://github.com/eramba/eramba_v2/issues/1219
We’ll try to look at it for next week release
