ServiceNow lifecycle & offboarding security checks
Dormant accounts, leavers with access, unowned assets and change-management gaps — the checks that catch what HR processes miss.
On ServiceNow, Black Cat runs 4 checks in this area on every scan. Each one below lists its severity, how to fix it, and the compliance controls it satisfies where a control applies. See what access the ServiceNow connector needs.
Checks (4)
severity: low Incident Auto-Assignment Disabled fix difficulty: easy #
Enable incident auto-assignment to ensure incidents are routed to the appropriate team automatically
- Navigate to System Properties > Incident
- Locate the property "glide.ui.autoassign"
- Change the value to "true"
- Save the property
- Verify that new incidents are automatically assigned based on assignment rules
Satisfies: NIS2 Directive NIS2-21.b.2 DORA (SaaS Security) DORA-17.2
severity: high Change Approval Not Required fix difficulty: medium #
Enable change approval requirements to ensure all changes are authorized before implementation
- Navigate to Change > Administration > Change Properties
- Locate the property "com.snc.change_management.approval.required"
- Change the value to "true"
- Save the property
- Define approval workflows for normal and emergency change types
- Test the approval process end-to-end with a sample change request
Satisfies: NIS2 Directive NIS2-21.b.2 DORA (SaaS Security) DORA-17.2
severity: medium Change Risk Assessment Disabled fix difficulty: medium #
Enable change risk assessment to ensure all changes are evaluated for risk before approval
- Navigate to Change > Administration > Change Properties
- Locate the property "change.risk.assessment_required"
- Change the value to "true"
- Save the property
- Configure risk assessment questions and scoring thresholds
- Test risk assessment with a sample change request
Satisfies: NIS2 Directive NIS2-21.b.2 DORA (SaaS Security) DORA-17.2
severity: medium CMDB Stale Records fix difficulty: hard #
Reduce the percentage of stale CMDB CI records by running discovery or updating records manually
- Navigate to Configuration > CI Class Manager
- Identify the CI classes with the highest number of stale records
- Schedule or run Discovery to automatically update CI attributes
- For manually managed CIs, bulk-update records with current information
- Consider setting up automated health checks or aging policies
- Target less than 10% stale CIs across all classes
Satisfies: NIS2 Directive NIS2-21.i.3 DORA (SaaS Security) DORA-8.1