Loading...
Loading...
The system property changed by an update set does not trigger recalculation of the compliance state. The reported compliance state by ISC Hardening does not get updated and can be wrong. Note that the Steps to reproduce below only show the result for one property but there are other system properties monitored by ISC behaving the same. Steps to Reproduce 1. Set the value of glide.ui.forgetme property to false (https://<Instance_Name>.service-now.com/sys_properties.do?sys_id=20685597c611228301316264159fc184) 2. Open Instance Security Center, click Hardening tab. Under 'Hardening Compliance Configuration', click 'Medium' and select 'Session Management' from 'Categories' 3. Verify that you see 'Remove Remember Me' under 'Non-Compliant' 4. Record an update set on another instance with only one customer update that is to set glide.ui.forgetme to true or use the attached update set 5. Import the update set from Step 4 6. Preview and commit the imported update set 7. Verify that the value of glide.ui.forgetme property is changed from false to true using the link from Step 1 8. Repeat Step 2
should see 'Remove Remember Me' under 'Compliant'
see 'Remove Remember Me' under 'Non-Compliant'
As an admin user, go to Scripts - Background, select 'global' scope, tick 'Record for rollback', and run the following script: var grDep = new GlideRecord('isc_security_dependencies'); var evaluator = new GlideScopedEvaluator(); grDep.query(); while (grDep.next()) { evaluator.evaluateScript(grDep, 'harc_inbound_script', null); } After executing the above script, please run the '[PA AppSec] Daily Data Collection' job, and it will update the compliance score.
PRB1561476
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.