Bug 1629490

Summary:	anaconda hardening report is full of errors
Product:	Red Hat Enterprise Linux 7	Reporter:	Marek Haicman <mhaicman>
Component:	scap-security-guide	Assignee:	Watson Yuuma Sato <wsato>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.6	CC:	matyc, mhaicman, openscap-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-12 18:23:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marek Haicman 2018-09-16 21:24:42 UTC

Description of problem:
When security profile is selected during installation through anaconda, report of the hardening run exists in `/root/eval_remediate_report.html`. This report is full of `error` results that seemingly make no sense. This is tue to the way how service checking OVAL and remediations work. For check `service_XXX_enabled`, OVAL and remediation checks not only enablement, but also that the service is running.

As anaconda remediation runs in chroot, systemd won't allow checks of service runtime, resulting in fails. Fail after remediation is reported as error. This is but a display bug, though, as if you run the scan after reboot, these rules are passing.
 
Version-Release number of selected component (if applicable):
scap-security-guide-0.1.40-5.el7

How reproducible:
reliably

Steps to Reproduce:
1. install through anaconda (for example profile `stig-rhel7-disa`) 
2. open `/root/eval_remediate_report.html`
3.

Actual results:
Errors for basic checks like `rule_service_sshd_enabled`

Expected results:
No errors in general, but in this particular case no errors for service related rules.

Additional info:
This idea behind checking runtime as well is to make sure that service can run at all. To catch situation as such as service is enabled, but because of malformed configuration does not start.

Comment 2 Marek Haicman 2019-03-12 18:23:35 UTC

This issue was not selected to be included in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small number of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.