Item Search

NameAudit NamePluginCategory
DG0102-ORACLE11 - DBMS processes or services should run under custom, dedicated OS accounts - 'tns services are using correct service account'DISA STIG Oracle 11 Instance v9r1 OS UnixUnix

ACCESS CONTROL

DO6747-ORACLE11 - Remote administration should be disabled for the Oracle connection manager - '$ORACLE_HOME/network/admin/cman.ora REMOTE_ADMIN = no'DISA STIG Oracle 11 Installation v9r1 LinuxUnix

ACCESS CONTROL

MD4X-00-000700 - MongoDB must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).DISA STIG MongoDB Enterprise Advanced 4.x v1r4 DBMongoDB

SYSTEM AND COMMUNICATIONS PROTECTION

MD4X-00-002600 - Unused database components that are integrated in MongoDB and cannot be uninstalled must be disabled.DISA STIG MongoDB Enterprise Advanced 4.x v1r4 OSUnix

CONFIGURATION MANAGEMENT

MD4X-00-004200 - MongoDB must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.DISA STIG MongoDB Enterprise Advanced 4.x v1r4 OSUnix

SYSTEM AND INFORMATION INTEGRITY

MD4X-00-004900 - MongoDB must allocate audit record storage capacity in accordance with site audit record storage requirements.DISA STIG MongoDB Enterprise Advanced 4.x v1r4 OSUnix

AUDIT AND ACCOUNTABILITY

MOTO-09-000200 - The Motorola Android Pie must be configured to not allow passwords that include more than two repeating or sequential characters - Minimum complex charactersMobileIron - DISA Motorola Android Pie.x COBO v1r2MDM

CONFIGURATION MANAGEMENT

MOTO-09-000200 - The Motorola Android Pie must be configured to not allow passwords that include more than two repeating or sequential characters - NumbersAirWatch - DISA Motorola Android Pie.x COPE v1r2MDM

CONFIGURATION MANAGEMENT

MOTO-09-000200 - The Motorola Android Pie must be configured to not allow passwords that include more than two repeating or sequential characters - TypeMobileIron - DISA Motorola Android Pie.x COPE v1r2MDM

CONFIGURATION MANAGEMENT

MOTO-09-000400 - The Motorola Android Pie must be configured to lock the display after 15 minutes (or less) of inactivity - or less of inactivity.AirWatch - DISA Motorola Android Pie.x COBO v1r2MDM

ACCESS CONTROL

MOTO-09-008700 - Motorola Android Pie users must complete required training.MobileIron - DISA Motorola Android Pie.x COBO v1r2MDM

CONFIGURATION MANAGEMENT

MOTO-09-008700 - Motorola Android Pie users must complete required training.AirWatch - DISA Motorola Android Pie.x COPE v1r2MDM

CONFIGURATION MANAGEMENT

MOTO-09-008800 - Motorola Android Pie must be configured to enforce that Wi-Fi Sharing is disabled.MobileIron - DISA Motorola Android Pie.x COPE v1r2MDM

CONFIGURATION MANAGEMENT

MOTO-09-009000 - Motorola Android Pie must have the DoD root and intermediate PKI certificates installed.AirWatch - DISA Motorola Android Pie.x COBO v1r2MDM

CONFIGURATION MANAGEMENT

MOTO-09-010000 - Motorola Android Pie Work Profile must be configured to disable the autofill services.AirWatch - DISA Motorola Android Pie.x COPE v1r2MDM

CONFIGURATION MANAGEMENT

MOTO-09-010000 - Motorola Android Pie Work Profile must be configured to disable the autofill services.MobileIron - DISA Motorola Android Pie.x COPE v1r2MDM

CONFIGURATION MANAGEMENT

MOTS-11-010200 - Motorola Solutions Android 11 must be configured to disallow configuration of date and time.MobileIron - DISA Motorola Solutions Android 11 COBO v1r3MDM

CONFIGURATION MANAGEMENT

OL6-00-000539 - The Oracle Linux operating system must not be configured to bypass password requirements for privilege escalation.DISA STIG Oracle Linux 6 v2r7Unix

IDENTIFICATION AND AUTHENTICATION

SQL2-00-012100 - SQL Server must produce audit records containing sufficient information to establish the sources (origins) of the events - 'Event ID 113'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012100 - SQL Server must produce audit records containing sufficient information to establish the sources (origins) of the events - 'Event ID 129'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012100 - SQL Server must produce audit records containing sufficient information to establish the sources (origins) of the events - 'Event ID 130'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012100 - SQL Server must produce audit records containing sufficient information to establish the sources (origins) of the events - 'Event ID 135'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012100 - SQL Server must produce audit records containing sufficient information to establish the sources (origins) of the events - 'Event ID 173'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012200 - SQL Server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events - 'Event ID 15'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012200 - SQL Server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events - 'Event ID 18'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012200 - SQL Server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events - 'Event ID 109'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012200 - SQL Server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events - 'Event ID 132'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012200 - SQL Server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events - 'Event ID 152'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012200 - SQL Server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events - 'Event ID 172'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012200 - SQL Server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events - 'Event ID 177'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012200 - SQL Server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events - 'Event ID 178'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 15'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 20'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 102'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 105'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 106'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 111'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 116'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 117'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 131'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 133'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 135'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 170'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-012300 - SQL Server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event - 'Event ID 172'DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

AUDIT AND ACCOUNTABILITY

SQL2-00-017000 - Unused database components that are integrated in SQL Server and cannot be uninstalled must be disabled.DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

CONFIGURATION MANAGEMENT

SQL2-00-018200 - SQL Server backups of system-level information per organization-defined frequency must be performed that is consistent with recovery time and recovery point objectives.DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

CONTINGENCY PLANNING

SQL2-00-020000 - SQL Server must protect the integrity of publicly available information and SQL Servers configuration from unauthorized Securables access.DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

CONFIGURATION MANAGEMENT

SQL2-00-020200 - SQL Server must protect the integrity of publicly available information and SQL Servers configuration from unauthorized User Mapping access.DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

CONFIGURATION MANAGEMENT

SQL2-00-021500 - SQL Server must isolate security functions from nonsecurity functions by means of separate security domains.DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

SYSTEM AND COMMUNICATIONS PROTECTION

SQL2-00-022400 - SQL Server must ensure, if Database Availability Groups are being used and there is a server failure, that none of the potential failover servers would suffer from resource exhaustion.DISA STIG SQL Server 2012 DB Instance Security v1r20MS_SQLDB

SYSTEM AND COMMUNICATIONS PROTECTION