Next, oscap may not be behaving as expected since the OVAL here does not validate per the OVAL schematron. See:
[blank@eclipse checks]$ oscap oval validate-xml --schematron /tmp/file_ownership_etc_skeljsnZt0.xml
<?xml version="1.0"?>
oval:scap-security-guide.testing:tst:111 - No state should be referenced when check_existence has a value of 'none_exist'.
oval:scap-security-guide.testing:tst:116 - No state should be referenced when check_existence has a value of 'none_exist'.
oval:scap-security-guide.testing:tst:112 - No state should be referenced when check_existence has a value of 'none_exist'.
oval:scap-security-guide.testing:tst:117 - No state should be referenced when check_existence has a value of 'none_exist'.
oval:scap-security-guide.testing:tst:113 - No state should be referenced when check_existence has a value of 'none_exist'.
oval:scap-security-guide.testing:tst:118 - No state should be referenced when check_existence has a value of 'none_exist'.
oval:scap-security-guide.testing:tst:114 - No state should be referenced when check_existence has a value of 'none_exist'.
oval:scap-security-guide.testing:tst:119 - No state should be referenced when check_existence has a value of 'none_exist'.
oval:scap-security-guide.testing:tst:115 - No state should be referenced when check_existence has a value of 'none_exist'.
oval:scap-security-guide.testing:tst:120 - No state should be referenced when check_existence has a value of 'none_exist'.
Invalid OVAL Definition content(5.10) in /tmp/file_ownership_etc_skeljsnZt0.xml.
Lemme add schematron validation to the Makerule ... I think it should work out of the box now, per: