STIGQter: STIG Summary: Xylok Security Suite 20.x Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 05 Jan 2026:

Xylok Security Suite must limit system resources consumed by the application.

DISA Rule

SV-269570r1053485_rule

Vulnerability Number

V-269570

Group Title

SRG-APP-000001

Rule Version

XYLK-20-000001

Severity

CAT II

CCI(s)

CCI-000054 - Limit the number of concurrent sessions for each organization-defined account and/or account type to an organization-defined number.
CCI-002385 - Protect against or limit the effects of organization-defined types of denial of service events.

Weight

Fix Recommendation

Configure the Xylok Security Suite to limit CPU and memory usage using this procedure on the host machine. As root, open /etc/xylok.conf in a text editor.

1. Add the following settings if not present. All settings should be in the format "NAME=value". For example, the first required setting might appear as "LIMIT_MEM=4096m" in the configuration file, with no quotes.
- LIMIT_MEM: Set to 2048m or greater, and less than 100 percent of the host machine's memory.
- LIMIT_CPU: Set to 128 or greater, not to exceed 1000. This value can range from 1 to 1024, where 1024 allows usage of 100 percent of the CPU.

2. Save configuration file.

3. Restart Xylok to apply settings:
# systemctl restart xylok

Check Contents

Determine if Xylok is configured to limit its maximum CPU and memory usage with the following command, run from the host machine as a normal user:

$ grep LIMIT_ /etc/xylok.conf

Verify the following settings are configured:
- LIMIT_MEM set to less than 100 percent of the host machine's memory.

- LIMIT_CPU set to less than 1000.

If any of the above settings are not present or are blank, this is a finding.

Vulnerability Number

V-269570

Documentable

False

Rule Version

XYLK-20-000001

Severity Override Guidance

Check Content Reference

Target Key

5665