What changed in Trellix Application Control 8.x STIG V3R2V3R2 changes

Trellix Application Control 8.x STIG V3R2 (2025-07-02) replaced V3R1 (2024-07-24): 1 check removed, 7 updated. It has 31 checks, against 32 in V3R1.

  • 0 added
  • 1 removed
  • 7 updated

Updated fields: CCIs 7

Removed since V3R1 (1)

  • V-213335CAT IIOrganization-specific Trellix Applications Control Options policies must be created and applied to all endpoints.

Updated in V3R2 (7)

V-213318CAT IIThe Solidcore client Command Line Interface (CLI) Access password complexity requirements must be documented in the organizations written policy.CCIs

CCIs

CCI-004066CCI-004066,CCI-001619

V-213320CAT IIThe requirement for scheduled Solidcore client Command Line Interface (CLI) Access Password changes must be documented in the organizations written policy.CCIs

CCIs

CCI-004066CCI-004066,CCI-000199

V-213322CAT IIThe Trellix Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be confined to the organizations enclave.CCIs

CCIs

CCI-004964,CCI-004965,CCI-001240

V-213330CAT IIThe Trellix Application Control Options Reputation setting must be configured to use the Trellix Global Threat Intelligence (Trellix GTI) option.CCIs

CCIs

CCI-004964,CCI-004965,CCI-001240

V-213332CAT IIThe Trellix Application Control Options Advanced Threat Defense (ATD) settings must not be enabled unless an internal ATD is maintained by the organization.CCIs

CCIs

CCI-004964,CCI-004965,CCI-001240

V-213333CAT IIThe Trellix Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be configured to send all binaries with a reputation of Might be Trusted and below for analysis.CCIs

CCIs

CCI-004964,CCI-004965,CCI-001240

V-213334CAT IIThe Trellix Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be configured to only send binaries with a size of 5MB or less.CCIs

CCIs

CCI-004964,CCI-004965,CCI-001240

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V3R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.