Configure Scan Engine parameters

Configure the primary scanning capabilities and configuration options for scheduled, on-demand, and real-time scans.

Before you begin

Review these properties before you Run your first scan with the Scan Engine or to make changes to Scan Engine behavior.

Role required: scan_engine_admin and Impact _admin

Procedure

1. Navigate to ALL > Impact > Configuration > Scan Engine Properties.
2. Select Activate Scan Engine to ensure the Scan Engine runs against your instance.
3. Select Run Scheduled Scan to schedule nightly, weekly, or monthly scans and configure these options.

   Table 1. Schedule options

   Field	Description
   Run	Daily, Weekly, or Monthly scheduled scan run times.
   Day of Week	The day of the week on which to run weekly scans.
   Day of Month	The day of the month on which to run monthly scans.
   Time Zone	Your time zone.
   Time	Field type = glide_utc_time The time the scan should begin in 24-hour format (HH:MM:SS).

4. Configure scan scope and finding tracking configuration settings.

   Field	Description
   Scan Non-Configuration Records	Includes non-configuration tables (which do not extend sys_metadata) in the scan.
   Scan Read-Only Records	Includes read-only records in the scan. scan_read_only: Default: true. Read-only records are scanned by default.
   Track Resolved Findings	Logs any resolved findings as part of the scan and includes them in the View Resolved Findings module of the dashboard.
   Scan Findings Limit	scan_findings_limit The maximum number of findings that can be generated for each definition during a scan. The limit is applied per applicable table. For example, if the limit is set to 100, a maximum of 100 findings will be generated for each applicable table. Prevents excessive or redundant findings and optimizes scan performance.
   Custom Workday	By default, technical debt is calculated as a 24-hour day, which allows you to specify a number of hours for a workday. For example, developer workdays can be set to 8 hours instead of 24. Note: This is used to calculate various metrics that appear in the Analytics Dashboards.
   Average hourly rate of development	This figure calculates the cost of technical debt that displays on your dashboard by multiplying it by the estimated time to resolve each finding in the system.
   Batch Record Size	full_scan_batch_size Default: 50,000 records. Specifies the maximum number of records allowed to be analyzed in a single batch scan for an applicable table. This value does not limit the total number of records that can be scanned. When a table's record count exceeds this threshold (50,000), the table is assigned to its own dedicated batch during scan processing to optimize performance. This value determines when an applicable table warrants its own batch during scans. Note: This is a read-only system property that cannot be modified through the UI.
   Scheduled Scan Logging Frequency	Default: false Leave blank to disable verbose logging. When set, logs scan progress after processing the specified number of records
   Days of scan finding histories to keep	keep_days_finding_history Sets the retention period for finding history records. Note: This controls how long historical scan data is retained, not the findings themselves.The default value is 30 days.
   Include review findings in technical debt	Displays findings on the dashboard where the level of the rule is equal to Review.
   Enable instance specific definitions	instance_specific_definitions Select to restrict scan definitions to run only on designated instances. When disabled, all active definitions run on all instances. When enabled without matching instances: If the sn_se_my_sn_instances table is empty, all definitions run (system assumes feature is not in use) If the sn_se_my_sn_instances table has entries but the current instance is not listed, only 'All Instances' definitions execute" Note: Configuration option that controls whether definitions run only on specified instances.
   Scan Non-Configuration Records	scan_non_configuration_records Default: true When enabled, includes non-configuration tables (tables that do not extend sys_metadata) in full scans.