Why oscap(Security Content Automation Protocol) is failing for screensaver functionality despite of minimal installation?
Issue
-
Why
oscap
(Security Content Automation Protocol) is showing below fail messages?itle Set GNOME3 Screensaver Inactivity Timeout Rule xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_idle_delay Ident CCE-80110-0 Result fail Title Enable GNOME3 Screensaver Idle Activation Rule xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_idle_activation_enabled Ident CCE-80111-8 Result fail Title Enable GNOME3 Screensaver Lock After Idle Period Rule xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_lock_enabled Ident CCE-80112-6 Result fail Title Set GNOME3 Screensaver Lock Delay After Activation Period Rule xccdf_org.ssgproject.content_rule_dconf_gnome_screensaver_lock_delay Ident CCE-80370-0 Result fail Title Ensure Users Cannot Change GNOME3 Session Settings Rule xccdf_org.ssgproject.content_rule_dconf_gnome_session_user_locks Ident CCE-80371-8 Result fail
Environment
- Red Hat Enterprise Linux 7
- openscap-scanner
- scap-security-guide
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.