The organizations written policy must include procedures for how often the whitelist of allowed applications is reviewed.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-213325 | MCAC-PO-000110 | SV-213325r961479_rule | CCI-001774 | medium |
| Description | ||||
| Enabling application whitelisting without adequate design and organization-specific requirements will either result in an implementation which is too relaxed or an implementation which causes denial of service to its user community. Documenting the specific requirements and trust model before configuring and deploying the Trellix Application Control software is mandatory. | ||||
| STIG | Date | |||
| Trellix Application Control 8.x Security Technical Implementation Guide | 2025-06-09 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
CM-7(5)
1.00
- DISA · V3R2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.4.8
1.00
- DISA · V3R2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-001774
1.00
- DISA · V3R2 · disa_xccdf · related
Details
Check Text (C-213325r961479_chk)
Consult with the ISSO/ISSM to review the organizational-specific written policy for the Trellix Application Control software.
Verify the written policy includes a process for how often the application whitelist is reviewed.
If no written policy exists, this is a finding.
If written policy does not include a process for how often the application whitelist is reviewed, this is a finding.
Fix Text (F-14551r309073_fix)
Follow the formal change and acceptance process to update the written policy to include a process for how often the application whitelist is reviewed.