Xylok Security Suite 20.x Security Technical Implementation Guide

The Xylok Security Suite 20.x Security Technical Implementation Guide (V1 R2) has 19 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

19STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V1 · R2

CurrentPublished Mon Jan 05 2026

The Xylok Security Suite configuration for DEBUG must be False.

Xylok Security Suite 20.x Security Technical Implementation Guide

Assessment Title

Rule Text

The Xylok Security Suite configuration for DEBUG must be False.

Description

Discussion Text

Providing too much information in error messages risks compromising the data and security of the Xylok Security Suite and system. If DEBUG is set to True, it will show stack traces in error messages to assist with contact Xylok Support, but potentially reveal secure information.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-269580

Rule

SV-269580r1053515_rule

Severity

medium

Rule Version

XYLK-20-000109

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

Verify DEBUG is configured. Execute the following:
$ grep DEBUG /etc/xylok.conf

DEBUG=False

If "DEBUG" is not set to False or is missing, this is a finding.

Implementation Procedure

Fix Text

Set DEBUG:

1. As root, open /etc/xylok.conf in a text editor.

2. Add/Amend "DEBUG=False" to the configuration file.

3. Restart Xylok to apply settings by executing the following:
    # systemctl restart xylok

STIG check 12 of 19 in the Xylok Security Suite 20.x STIG checklist

← Previous · V-269579Xylok Security Suite must disable nonessential capabilities.Next · V-269581 →Xylok Security Suite must not allow local user or groups.