STIGhub
STIGs
RMF Controls
Compare
← SC-3 — Security Function Isolation
CCI-001084
Definition
Isolate security functions from nonsecurity functions.
Parent Control
SC-3
Security Function Isolation
System and Communications Protection
Linked STIG Checks (176)
V-274033
CAT II
Amazon Linux 2023 must have the policycoreutils package installed.
Amazon Linux 2023 Security Technical Implementation Guide
V-274153
CAT I
Amazon Linux 2023 must use a Linux Security Module configured to enforce limits on system services.
Amazon Linux 2023 Security Technical Implementation Guide
V-214290
CAT II
The Apache web server document directory must be in a separate partition from the Apache web servers system files.
Apache Server 2.4 UNIX Site Security Technical Implementation Guide
V-214337
CAT II
The Apache web server document directory must be in a separate partition from the Apache web servers system files.
Apache Server 2.4 Windows Server Security Technical Implementation Guide
V-214382
CAT II
The Apache web server document directory must be in a separate partition from the Apache web servers system files.
Apache Server 2.4 Windows Site Security Technical Implementation Guide
V-222590
CAT II
The application must isolate security functions from non-security functions.
Application Security and Development Security Technical Implementation Guide
V-272633
CAT II
CylanceON-PREM must be configured with only one local Role to be used by the account of last resort in the event the authentication server is unavailable.
Arctic Wolf CylanceON-PREM Security Technical Implementation Guide
V-276005
CAT II
Ax-OS must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
Axonius Federal Systems Ax-OS Security Technical Implementation Guide
V-251617
CAT II
CA IDMS must isolate the security manager to which users, groups, roles are assigned authorities/permissions to resources.
CA IDMS Security Technical Implementation Guide
V-219169
CAT I
The Ubuntu operating system must be configured so that only users who need access to security functions are part of the sudo group.
Canonical Ubuntu 18.04 LTS Security Technical Implementation Guide
V-238206
CAT I
The Ubuntu operating system must ensure only users who need access to security functions are part of sudo group.
Canonical Ubuntu 20.04 LTS Security Technical Implementation Guide
V-260559
CAT I
Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group.
Canonical Ubuntu 22.04 LTS Security Technical Implementation Guide
V-270748
CAT I
Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group.
Canonical Ubuntu 24.04 LTS Security Technical Implementation Guide
V-269430
CAT II
AlmaLinux OS 9 must use a Linux Security Module configured to enforce limits on system services.
Cloud Linux AlmaLinux OS 9 Security Technical Implementation Guide
V-269431
CAT II
AlmaLinux OS 9 must have the policycoreutils package installed.
Cloud Linux AlmaLinux OS 9 Security Technical Implementation Guide
V-233125
CAT II
The container platform runtime must isolate security functions from non-security functions.
Container Platform Security Requirements Guide
V-233546
CAT II
PostgreSQL must isolate security functions from non-security functions.
Crunchy Data PostgreSQL Security Technical Implementation Guide
V-261902
CAT II
PostgreSQL must isolate security functions from nonsecurity functions.
Crunchy Data Postgres 16 Security Technical Implementation Guide
V-206571
CAT II
The DBMS must isolate security functions from non-security functions.
Database Security Requirements Guide
V-270910
CAT II
Dragos Platform must use an Identity Provider (IDP) for authentication and authorization processes.
Dragos Platform 2.x Security Technical Implementation Guide
V-224179
CAT II
The EDB Postgres Advanced Server must isolate security functions from non-security functions.
EDB Postgres Advanced Server v11 on Windows Security Technical Implementation Guide
V-213605
CAT II
The EDB Postgres Advanced Server must isolate security functions from non-security functions.
EDB Postgres Advanced Server v9.6 Security Technical Implementation Guide
V-259260
CAT II
The EDB Postgres Advanced Server must isolate security functions from nonsecurity functions.
EnterpriseDB Postgres Advanced Server (EPAS) Security Technical Implementation Guide
V-203656
CAT II
The operating system must isolate security functions from nonsecurity functions.
General Purpose Operating System Security Requirements Guide
V-215404
CAT II
AIX must turn on enhanced Role-Based Access Control (RBAC) to isolate security functions from nonsecurity functions, to grant system privileges to other operating system admins, and prohibit user installation of system software without explicit privileged status.
IBM AIX 7.x Security Technical Implementation Guide
V-213707
CAT II
DB2 must isolate security functions from non-security functions.
IBM DB2 V10.5 LUW Security Technical Implementation Guide
V-223514
CAT I
ACF2 security data sets and/or databases must be properly protected.
IBM z/OS ACF2 Security Technical Implementation Guide
V-223684
CAT I
The IBM RACF System REXX IRRPWREX security data set must be properly protected.
IBM z/OS RACF Security Technical Implementation Guide
V-223685
CAT I
IBM RACF security data sets and/or databases must be properly protected.
IBM z/OS RACF Security Technical Implementation Guide
V-223903
CAT I
CA-TSS security data sets and/or databases must be properly protected.
IBM z/OS TSS Security Technical Implementation Guide
V-237923
CAT II
CA VM:Secure must have a security group for Security Administrators only.
IBM zVM Using CA VM:Secure Security Technical Implementation Guide
V-242434
CAT I
Kubernetes Kubelet must enable kernel protection.
Kubernetes Security Technical Implementation Guide
V-213855
CAT II
SQL Server must isolate security functions from nonsecurity functions.
MS SQL Server 2014 Instance Security Technical Implementation Guide
V-213914
CAT III
SQL Server must isolate security functions from non-security functions.
MS SQL Server 2016 Database Security Technical Implementation Guide
V-205521
CAT II
The Mainframe Product must isolate security functions from nonsecurity functions.
Mainframe Product Security Requirements Guide
V-255308
CAT II
The Azure SQL Database must isolate security functions from nonsecurity functions.
Microsoft Azure SQL Database Security Technical Implementation Guide
V-276290
CAT III
Azure SQL Managed Instance must isolate security functions from nonsecurity functions.
Microsoft Azure SQL Managed Instance Security Technical Implementation Guide
V-218752
CAT II
The IIS 10.0 website document directory must be in a separate partition from the IIS 10.0 websites system files.
Microsoft IIS 10.0 Site Security Technical Implementation Guide
V-223077
CAT II
The 64-bit tab processes, when running in Enhanced Protected Mode on 64-bit versions of Windows, must be turned on.
Microsoft Internet Explorer 11 Security Technical Implementation Guide
V-223093
CAT II
Protected Mode must be enforced (Internet zone).
Microsoft Internet Explorer 11 Security Technical Implementation Guide
V-223094
CAT II
Protected Mode must be enforced (Restricted Sites zone).
Microsoft Internet Explorer 11 Security Technical Implementation Guide
V-223110
CAT II
Internet Explorer Processes for Zone Elevation must be enforced (Reserved).
Microsoft Internet Explorer 11 Security Technical Implementation Guide
V-223111
CAT II
Internet Explorer Processes for Zone Elevation must be enforced (Explorer).
Microsoft Internet Explorer 11 Security Technical Implementation Guide
V-223112
CAT II
Internet Explorer Processes for Zone Elevation must be enforced (iexplore).
Microsoft Internet Explorer 11 Security Technical Implementation Guide
V-271172
CAT II
SQL Server must isolate security functions from nonsecurity functions.
Microsoft SQL Server 2022 Database Security Technical Implementation Guide
V-220799
CAT II
Local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain systems.
Microsoft Windows 10 Security Technical Implementation Guide
V-220832
CAT II
Administrator accounts must not be enumerated during elevation.
Microsoft Windows 10 Security Technical Implementation Guide
V-220945
CAT II
User Account Control must, at minimum, prompt administrators for consent on the secure desktop.
Microsoft Windows 10 Security Technical Implementation Guide
V-220948
CAT II
User Account Control must be configured to detect application installations and prompt for elevation.
Microsoft Windows 10 Security Technical Implementation Guide
V-220949
CAT II
User Account Control must only elevate UIAccess applications that are installed in secure locations.
Microsoft Windows 10 Security Technical Implementation Guide
V-220951
CAT II
User Account Control must virtualize file and registry write failures to per-user locations.
Microsoft Windows 10 Security Technical Implementation Guide
V-253357
CAT II
Local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain systems.
Microsoft Windows 11 Security Technical Implementation Guide
V-253391
CAT II
Administrator accounts must not be enumerated during elevation.
Microsoft Windows 11 Security Technical Implementation Guide
V-253469
CAT II
User Account Control must prompt administrators for consent on the secure desktop.
Microsoft Windows 11 Security Technical Implementation Guide
V-253472
CAT II
User Account Control must be configured to detect application installations and prompt for elevation.
Microsoft Windows 11 Security Technical Implementation Guide
V-253473
CAT II
User Account Control must only elevate UIAccess applications that are installed in secure locations.
Microsoft Windows 11 Security Technical Implementation Guide
V-253475
CAT II
User Account Control must virtualize file and registry write failures to per-user locations.
Microsoft Windows 11 Security Technical Implementation Guide
V-224935
CAT II
Administrator accounts must not be enumerated during elevation.
Microsoft Windows Server 2016 Security Technical Implementation Guide
V-225008
CAT II
Local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain systems.
Microsoft Windows Server 2016 Security Technical Implementation Guide
V-225062
CAT II
UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.
Microsoft Windows Server 2016 Security Technical Implementation Guide
V-225063
CAT II
User Account Control must, at a minimum, prompt administrators for consent on the secure desktop.
Microsoft Windows Server 2016 Security Technical Implementation Guide
V-225065
CAT II
User Account Control must be configured to detect application installations and prompt for elevation.
Microsoft Windows Server 2016 Security Technical Implementation Guide
V-225066
CAT II
User Account Control must only elevate UIAccess applications that are installed in secure locations.
Microsoft Windows Server 2016 Security Technical Implementation Guide
V-225068
CAT II
User Account Control must virtualize file and registry write failures to per-user locations.
Microsoft Windows Server 2016 Security Technical Implementation Guide
V-205714
CAT II
Windows Server 2019 administrator accounts must not be enumerated during elevation.
Microsoft Windows Server 2019 Security Technical Implementation Guide
V-205715
CAT II
Windows Server 2019 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers.
Microsoft Windows Server 2019 Security Technical Implementation Guide
V-205716
CAT II
Windows Server 2019 UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.
Microsoft Windows Server 2019 Security Technical Implementation Guide
V-205717
CAT II
Windows Server 2019 User Account Control must, at a minimum, prompt administrators for consent on the secure desktop.
Microsoft Windows Server 2019 Security Technical Implementation Guide
V-205718
CAT II
Windows Server 2019 User Account Control must be configured to detect application installations and prompt for elevation.
Microsoft Windows Server 2019 Security Technical Implementation Guide
V-205719
CAT II
Windows Server 2019 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.
Microsoft Windows Server 2019 Security Technical Implementation Guide
V-205720
CAT II
Windows Server 2019 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.
Microsoft Windows Server 2019 Security Technical Implementation Guide
V-254355
CAT II
Windows Server 2022 administrator accounts must not be enumerated during elevation.
Microsoft Windows Server 2022 Security Technical Implementation Guide
V-254429
CAT II
Windows Server 2022 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers.
Microsoft Windows Server 2022 Security Technical Implementation Guide
V-254483
CAT II
Windows Server 2022 UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.
Microsoft Windows Server 2022 Security Technical Implementation Guide
V-254484
CAT II
Windows Server 2022 User Account Control (UAC) must, at a minimum, prompt administrators for consent on the secure desktop.
Microsoft Windows Server 2022 Security Technical Implementation Guide
V-254486
CAT II
Windows Server 2022 User Account Control (UAC) must be configured to detect application installations and prompt for elevation.
Microsoft Windows Server 2022 Security Technical Implementation Guide
V-254487
CAT II
Windows Server 2022 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.
Microsoft Windows Server 2022 Security Technical Implementation Guide
V-254489
CAT II
Windows Server 2022 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.
Microsoft Windows Server 2022 Security Technical Implementation Guide
V-278102
CAT II
Windows Server 2025 administrator accounts must not be enumerated during elevation.
Microsoft Windows Server 2025 Security Technical Implementation Guide
V-278178
CAT II
Windows Server 2025 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers.
Microsoft Windows Server 2025 Security Technical Implementation Guide
V-278233
CAT II
Windows Server 2025 UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.
Microsoft Windows Server 2025 Security Technical Implementation Guide
V-278234
CAT II
Windows Server 2025 User Account Control (UAC) must, at a minimum, prompt administrators for consent on the secure desktop.
Microsoft Windows Server 2025 Security Technical Implementation Guide
V-278236
CAT II
Windows Server 2025 User Account Control (UAC) must be configured to detect application installations and prompt for elevation.
Microsoft Windows Server 2025 Security Technical Implementation Guide
V-278237
CAT II
Windows Server 2025 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.
Microsoft Windows Server 2025 Security Technical Implementation Guide
V-278239
CAT II
Windows Server 2025 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.
Microsoft Windows Server 2025 Security Technical Implementation Guide
V-260933
CAT II
MKE must enable kernel protection.
Mirantis Kubernetes Engine Security Technical Implementation Guide
V-221175
CAT II
MongoDB must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).
MongoDB Enterprise Advanced 3.x Security Technical Implementation Guide
V-254225
CAT II
Nutanix AOS must be configured to run SELinux Policies.
Nutanix AOS 5.20.x OS Security Technical Implementation Guide
V-254237
CAT II
Nutanix AOS must be configured to use SELinux Enforcing mode.
Nutanix AOS 5.20.x OS Security Technical Implementation Guide
V-279623
CAT II
Nutanix OS must isolate security functions from nonsecurity functions.
Nutanix Acropolis GPOS Security Technical Implementation Guide
V-219782
CAT II
The DBMS must isolate security functions from non-security functions by means of separate security domains.
Oracle Database 11.2g Security Technical Implementation Guide
V-238445
CAT II
Administrators must utilize a separate, distinct administrative account when performing administrative activities, accessing database security functions, or accessing security-relevant information.
Oracle Database 11.2g Security Technical Implementation Guide
V-220298
CAT II
The DBMS must isolate security functions from nonsecurity functions by means of separate security domains.
Oracle Database 12c Security Technical Implementation Guide
V-237710
CAT II
Administrators must utilize a separate, distinct administrative account when performing administrative activities, accessing database security functions, or accessing security-relevant information.
Oracle Database 12c Security Technical Implementation Guide
V-270576
CAT II
Oracle Database must isolate security functions from nonsecurity functions by means of separate security domains.
Oracle Database 19c Security Technical Implementation Guide
V-221496
CAT II
OHS must have the DocumentRoot directive set to a separate partition from the OHS system files.
Oracle HTTP Server 12.1.3 Security Technical Implementation Guide
V-221497
CAT II
OHS must have the Directory directive accompanying the DocumentRoot directive set to a separate partition from the OHS system files.
Oracle HTTP Server 12.1.3 Security Technical Implementation Guide
V-248548
CAT II
OL 8 must use a Linux Security Module configured to enforce limits on system services.
Oracle Linux 8 Security Technical Implementation Guide
V-248549
CAT III
OL 8 must have the "policycoreutils" package installed.
Oracle Linux 8 Security Technical Implementation Guide
V-248590
CAT II
OL 8 must clear the page allocator to prevent use-after-free attacks.
Oracle Linux 8 Security Technical Implementation Guide
V-248591
CAT II
OL 8 must disable virtual syscalls.
Oracle Linux 8 Security Technical Implementation Guide
V-248592
CAT II
OL 8 must clear memory when it is freed to prevent use-after-free attacks.
Oracle Linux 8 Security Technical Implementation Guide
V-271452
CAT I
OL 9 must use a Linux Security Module configured to enforce limits on system services.
Oracle Linux 9 Security Technical Implementation Guide
V-271467
CAT II
OL 9 must have policycoreutils package installed.
Oracle Linux 9 Security Technical Implementation Guide
V-271734
CAT II
OL 9 must clear SLUB/SLAB objects to prevent use-after-free attacks.
Oracle Linux 9 Security Technical Implementation Guide
V-271737
CAT II
OL 9 must disable virtual system calls.
Oracle Linux 9 Security Technical Implementation Guide
V-271738
CAT II
OL 9 must clear the page allocator to prevent use-after-free attacks.
Oracle Linux 9 Security Technical Implementation Guide
V-235151
CAT II
The MySQL Database Server 8.0 must isolate security functions from non-security functions.
Oracle MySQL 8.0 Security Technical Implementation Guide
V-253524
CAT II
Users requiring access to Prisma Cloud Compute's Credential Store must be assigned and accessed by the appropriate role holders.
Palo Alto Networks Prisma Cloud Compute Security Technical Implementation Guide
V-214081
CAT II
PostgreSQL must isolate security functions from non-security functions.
PostgreSQL 9.x Security Technical Implementation Guide
V-254569
CAT II
Rancher RKE2 runtime must isolate security functions from nonsecurity functions.
Rancher Government Solutions RKE2 Security Technical Implementation Guide
V-280966
CAT II
RHEL 10 must have the "policycoreutils" package installed.
Red Hat Enterprise Linux 10 Security Technical Implementation Guide
V-281251
CAT II
RHEL 10 must use a Linux Security Module configured to enforce limits on system services.
Red Hat Enterprise Linux 10 Security Technical Implementation Guide
V-281301
CAT II
RHEL 10 must disable virtual system calls.
Red Hat Enterprise Linux 10 Security Technical Implementation Guide
V-281302
CAT II
RHEL 10 must clear the page allocator to prevent use-after-free attacks.
Red Hat Enterprise Linux 10 Security Technical Implementation Guide
V-281303
CAT II
RHEL 10 must clear memory when it is freed to prevent use-after-free attacks.
Red Hat Enterprise Linux 10 Security Technical Implementation Guide
V-230240
CAT II
RHEL 8 must use a Linux Security Module configured to enforce limits on system services.
Red Hat Enterprise Linux 8 Security Technical Implementation Guide
V-230241
CAT III
RHEL 8 must have policycoreutils package installed.
Red Hat Enterprise Linux 8 Security Technical Implementation Guide
V-230277
CAT II
RHEL 8 must clear the page allocator to prevent use-after-free attacks.
Red Hat Enterprise Linux 8 Security Technical Implementation Guide
V-230278
CAT II
RHEL 8 must disable virtual syscalls.
Red Hat Enterprise Linux 8 Security Technical Implementation Guide
V-230279
CAT II
RHEL 8 must clear memory when it is freed to prevent use-after-free attacks.
Red Hat Enterprise Linux 8 Security Technical Implementation Guide
V-257792
CAT II
RHEL 9 must disable virtual system calls.
Red Hat Enterprise Linux 9 Security Technical Implementation Guide
V-257793
CAT II
RHEL 9 must clear the page allocator to prevent use-after-free attacks.
Red Hat Enterprise Linux 9 Security Technical Implementation Guide
V-257794
CAT II
RHEL 9 must clear memory when it is freed to prevent use-after-free attacks.
Red Hat Enterprise Linux 9 Security Technical Implementation Guide
V-258078
CAT I
RHEL 9 must use a Linux Security Module configured to enforce limits on system services.
Red Hat Enterprise Linux 9 Security Technical Implementation Guide
V-258081
CAT II
RHEL 9 must have policycoreutils package installed.
Red Hat Enterprise Linux 9 Security Technical Implementation Guide
V-257547
CAT II
OpenShift runtime must isolate security functions from nonsecurity functions.
Red Hat OpenShift Container Platform 4.12 Security Technical Implementation Guide
V-257547
CAT II
OpenShift runtime must isolate security functions from nonsecurity functions.
Red Hat OpenShift Container Platform 4.x Security Technical Implementation Guide
V-275648
CAT I
Ubuntu OS must ensure only users who need access to security functions are part of sudo group.
Riverbed NetIM OS Security Technical Implementation Guide
V-206739
CAT II
The SDN controller must be configured to isolate security functions from non-security functions.
SDN Controller Security Requirements Guide
V-261368
CAT III
SLEM 5 must have policycoreutils package installed.
SUSE Linux Enterprise Micro (SLEM) 5 Security Technical Implementation Guide
V-261369
CAT I
SLEM 5 must use a Linux Security Module configured to enforce limits on system services.
SUSE Linux Enterprise Micro (SLEM) 5 Security Technical Implementation Guide
V-240988
CAT II
The Tanium Server must be configured with a connector to sync to Microsoft Active Directory for account management functions, must isolate security functions from non-security functions, and must terminate shared/group account credentials when members leave the group.
Tanium 7.0 Security Technical Implementation Guide
V-234048
CAT II
The Tanium Application Server must be configured with a connector to sync to Microsoft Active Directory for account management functions.
Tanium 7.3 Security Technical Implementation Guide
V-254904
CAT II
The Tanium cryptographic signing capabilities must be enabled on the Tanium Server.
Tanium 7.x Application on TanOS Security Technical Implementation Guide
V-254928
CAT II
The Tanium Application Server must be configured with a connector to sync to Microsoft Active Directory for account management functions.
Tanium 7.x Application on TanOS Security Technical Implementation Guide
V-253815
CAT II
The Tanium Application Server must be configured with a connector to sync to Microsoft Active Directory for account management functions.
Tanium 7.x Security Technical Implementation Guide
V-253845
CAT II
The Tanium cryptographic signing capabilities must be enabled on the Tanium Server.
Tanium 7.x Security Technical Implementation Guide
V-241142
CAT II
Trend Deep Security must isolate security functions from non-security functions.
Trend Micro Deep Security 9.x Security Technical Implementation Guide
V-252920
CAT II
TOSS must use a Linux Security Module configured to enforce limits on system services.
Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide
V-253084
CAT III
TOSS must have policycoreutils package installed.
Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide
V-282510
CAT II
TOSS 5 must use a Linux Security Module configured to enforce limits on system services.
Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide
V-240301
CAT II
The vRA PostgreSQL must not allow access to unauthorized accounts.
VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide
V-239800
CAT II
The vROps PostgreSQL DB must isolate security functions from non-security functions.
VMW vRealize Operations Manager 6.x PostgreSQL Security Technical Implementation Guide
V-240818
CAT II
tc Server HORIZON document directory must be in a separate partition from the web servers system files.
VMware vRealize Automation 7.x tc Server Security Technical Implementation Guide
V-240819
CAT II
tc Server VCO document directory must be in a separate partition from the web servers system files.
VMware vRealize Automation 7.x tc Server Security Technical Implementation Guide
V-240820
CAT II
tc Server VCAC document directory must be in a separate partition from the web servers system files.
VMware vRealize Automation 7.x tc Server Security Technical Implementation Guide
V-241673
CAT II
tc Server UI document directory must be in a separate partition from the web servers system files.
VMware vRealize Operations Manager 6.x tc Server Security Technical Implementation Guide
V-241674
CAT II
tc Server CaSa document directory must be in a separate partition from the web servers system files.
VMware vRealize Operations Manager 6.x tc Server Security Technical Implementation Guide
V-241675
CAT II
tc Server API document directory must be in a separate partition from the web servers system files.
VMware vRealize Operations Manager 6.x tc Server Security Technical Implementation Guide
V-256605
CAT II
VMware Postgres must not allow schema access to unauthorized accounts.
VMware vSphere 7.0 vCenter Appliance PostgreSQL Security Technical Implementation Guide
V-256335
CAT II
The vCenter Server users must have the correct roles assigned.
VMware vSphere 7.0 vCenter Security Technical Implementation Guide
V-258921
CAT II
The vCenter Server user roles must be verified.
VMware vSphere 8.0 vCenter Security Technical Implementation Guide
V-207402
CAT II
The VMM must isolate security functions from non-security functions.
Virtual Machine Manager Security Requirements Guide
V-206408
CAT II
The web server document directory must be in a separate partition from the web servers system files.
Web Server Security Requirements Guide
V-73487
CAT II
Administrator accounts must not be enumerated during elevation.
Windows Server 2016 Security Technical Implementation Guide
V-73487
CAT II
Administrator accounts must not be enumerated during elevation.
Windows Server 2016 Security Technical Implementation Guide
V-73495
CAT II
Local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain systems.
Windows Server 2016 Security Technical Implementation Guide
V-73495
CAT II
Local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain systems.
Windows Server 2016 Security Technical Implementation Guide
V-73709
CAT II
UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.
Windows Server 2016 Security Technical Implementation Guide
V-73709
CAT II
UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.
Windows Server 2016 Security Technical Implementation Guide
V-73711
CAT II
User Account Control must, at a minimum, prompt administrators for consent on the secure desktop.
Windows Server 2016 Security Technical Implementation Guide
V-73711
CAT II
User Account Control must, at a minimum, prompt administrators for consent on the secure desktop.
Windows Server 2016 Security Technical Implementation Guide
V-73715
CAT II
User Account Control must be configured to detect application installations and prompt for elevation.
Windows Server 2016 Security Technical Implementation Guide
V-73715
CAT II
User Account Control must be configured to detect application installations and prompt for elevation.
Windows Server 2016 Security Technical Implementation Guide
V-73717
CAT II
User Account Control must only elevate UIAccess applications that are installed in secure locations.
Windows Server 2016 Security Technical Implementation Guide
V-73717
CAT II
User Account Control must only elevate UIAccess applications that are installed in secure locations.
Windows Server 2016 Security Technical Implementation Guide
V-73721
CAT II
User Account Control must virtualize file and registry write failures to per-user locations.
Windows Server 2016 Security Technical Implementation Guide
V-73721
CAT II
User Account Control must virtualize file and registry write failures to per-user locations.
Windows Server 2016 Security Technical Implementation Guide
V-93517
CAT II
Windows Server 2019 administrator accounts must not be enumerated during elevation.
Windows Server 2019 Security Technical Implementation Guide
V-93519
CAT II
Windows Server 2019 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers.
Windows Server 2019 Security Technical Implementation Guide
V-93521
CAT II
Windows Server 2019 UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.
Windows Server 2019 Security Technical Implementation Guide
V-93523
CAT II
Windows Server 2019 User Account Control must, at a minimum, prompt administrators for consent on the secure desktop.
Windows Server 2019 Security Technical Implementation Guide
V-93525
CAT II
Windows Server 2019 User Account Control must be configured to detect application installations and prompt for elevation.
Windows Server 2019 Security Technical Implementation Guide
V-93527
CAT II
Windows Server 2019 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.
Windows Server 2019 Security Technical Implementation Guide
V-93529
CAT II
Windows Server 2019 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.
Windows Server 2019 Security Technical Implementation Guide