How to Enable server.useServerWideRequiredSystemConfig on a Rust Server

Set server.useServerWideRequiredSystemConfig to true to require TPM 2.0 and Secure Boot for every player connecting to your Rust server. Servers enforcing these requirements for all players receive the Secure tag in Rust’s server browser.

Configure server.cfg

Locate the identity selected by your +server.identity startup argument. The configuration file for that identity is:

rust/server/<server.identity>/cfg/server.cfg

Add this line without a leading + or -:

server.useServerWideRequiredSystemConfig true

Save the file and restart the server. Rust reads server.cfg during startup, and values in the file take priority over command-line values.

Verify the Secure tag

After startup, find the server in Rust’s server browser and confirm that it displays the Secure tag. Opening an entry with additional system requirements shows players what is required and whether their system supports those requirements.

The separate convar below enables requirements associated with individual player accounts:

server.usePerPlayerRequiredSystemConfig true

It does not grant the Secure tag, which requires enforcing the additional requirements for every player.

For continuing update context, follow sourced Rust coverage on TOP OF GAMES.

Help players check their systems

Facepunch’s preparation guide instructs Windows players to press Windows key plus R and run:

tpm.msc

The TPM window should report that the TPM is ready for use. Players can then run:

msinfo32

In System Information, Secure Boot State should be On.

If Secure Boot is unavailable because the computer uses Legacy or CSM boot mode, changing the boot mode to UEFI may be necessary. Facepunch warns that this change can prevent a computer from starting properly, so players should consult instructions for their exact motherboard model or obtain experienced help before proceeding.