Closed SharmainePopov closed 4 months ago
@SharmainePopov yes, we've fixed this issue due to API changes that weren't made public until recently. It should work as expected as we've updated the policy to comply with the new API requirements, and this has been confirmed through testing.
I'll close this issue, but please feel free to re-open or open a new issue if you find any issues.
The policy v1.0 was reporting false negative (showing non-compliance) for case where MDFC set value matched the required parameter value for minimum severity. The same policy was recently updated to v 2.0 and the issue seems to be fixed in initial testing. Woud like confirmation that the issue was in fact address in v 2.0
Steps to reproduce
Repeat for each policy v 1.0 and v 2.0 Screenshots