Application Security and Development Security Technical Implementation Guide

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: [email protected]

Details

Version / Release: V4R8

Published: 2018-09-13

Updated At: 2018-11-03 10:27:25

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-83861r1_rule APSC-DV-000010 CCI-000054 MEDIUM The application must provide a capability to limit the number of logon sessions per user. Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allowed users and sessions per user is helpful in limiting risks related to DoS attacks. This requirement may
    SV-83863r1_rule APSC-DV-000060 CCI-002361 MEDIUM The application must clear temporary storage and cookies when the session is terminated. Persistent cookies are a primary means by which a web application will store application state and user information. Since HTTP is a stateless protocol, this persistence allows the web application developer to provide a robust and customizable user exper
    SV-83865r1_rule APSC-DV-000070 CCI-002361 MEDIUM The application must automatically terminate the non-privileged user session and log off non-privileged users after a 15 minute idle time period has elapsed. Leaving a user’s application session established for an indefinite period of time increases the risk of session hijacking. Session termination terminates an individual user's logical application session after 15 minutes of application inactivity at whi
    SV-83867r1_rule APSC-DV-000080 CCI-002361 MEDIUM The application must automatically terminate the admin user session and log off admin users after a 10 minute idle time period is exceeded. Leaving an admin user's application session established for an indefinite period of time increases the risk of session hijacking. Session termination terminates an individual user's logical application session after 10 minutes of application inactivity a
    SV-83869r1_rule APSC-DV-000090 CCI-002363 MEDIUM Applications requiring user access authentication must provide a logoff capability for user initiated communication session. If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker. Applications providing user access must provide the ability for users to manually terminate their sessions and log off.
    SV-83871r1_rule APSC-DV-000100 CCI-002364 LOW The application must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions. If a user is not explicitly notified that their application session has been terminated, they cannot be certain that their session did not remain open. Applications with a user access interface must provide an explicit logoff message to the user upon succ
    SV-83873r1_rule APSC-DV-000110 CCI-002262 MEDIUM The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in storage. Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions representing the basic properties or characteristics of an entity
    SV-83875r1_rule APSC-DV-000120 CCI-002263 MEDIUM The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in process. Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions representing the basic properties or characteristics of an entity
    SV-83877r1_rule APSC-DV-000130 CCI-002264 MEDIUM The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission. Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions representing the basic properties or characteristics of an entity
    SV-83879r1_rule APSC-DV-000160 CCI-000068 MEDIUM The application must implement DoD-approved encryption to protect the confidentiality of remote access sessions. Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) co
    SV-83881r1_rule APSC-DV-000170 CCI-001453 MEDIUM The application must implement cryptographic mechanisms to protect the integrity of remote access sessions. Without integrity protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communic
    SV-83883r1_rule APSC-DV-000180 CCI-001453 MEDIUM Applications with SOAP messages requiring integrity must include the following message elements:-Message ID-Service Request-Timestamp-SAML Assertion (optionally included in messages) and all elements of the message must be digitally signed. Digitally signed SOAP messages provide message integrity and authenticity of the signer of the message independent of the transport layer. Service requests may be intercepted and changed in transit and the data integrity may be at risk if the SOAP message
    SV-83901r1_rule APSC-DV-000190 CCI-000068 HIGH Messages protected with WS_Security must use time stamps with creation and expiration times. The lack of time stamps could lead to the eventual replay of the message, leaving the application susceptible to replay events which may result in an immediate loss of confidentiality.
    SV-83903r1_rule APSC-DV-000200 CCI-000068 HIGH Validity periods must be verified on all application messages using WS-Security or SAML assertions. When using WS-Security in SOAP messages, the application should check the validity of the time stamps with creation and expiration times. Time stamps that are not validated may lead to a replay event and provide immediate unauthorized access of the applic
    SV-83905r2_rule APSC-DV-000210 CCI-000068 MEDIUM The application must ensure each unique asserting party provides unique assertion ID references for each SAML assertion. SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens containing assertions to pass information about a principal (usually an end user) between a SAML authority, (identity provider), an
    SV-83907r1_rule APSC-DV-000220 CCI-000068 MEDIUM The application must ensure encrypted assertions, or equivalent confidentiality protections are used when assertion data is passed through an intermediary, and confidentiality of the assertion data is required when passing through the intermediary. SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens containing assertions to pass information about a principal (usually an end user) between a SAML authority, (identity provider), a
    SV-83909r1_rule APSC-DV-000230 CCI-000068 HIGH The application must use the NotOnOrAfter condition when using the SubjectConfirmation element in a SAML assertion. SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens containing assertions to pass information about a principal (usually an end user) between a SAML authority, (identity provider), a
    SV-83911r1_rule APSC-DV-000240 CCI-000068 HIGH The application must use both the NotBefore and NotOnOrAfter elements or OneTimeUse element when using the Conditions element in a SAML assertion. SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens containing assertions to pass information about a principal (usually an end user) between a SAML authority, (identity provider), a
    SV-83913r1_rule APSC-DV-000250 CCI-000068 MEDIUM The application must ensure if a OneTimeUse element is used in an assertion, there is only one of the same used in the Conditions element portion of an assertion. Multiple elements used in a SAML assertion can lead to elevation of privileges, if the application does not process SAML assertions correctly.
    SV-83915r1_rule APSC-DV-000260 CCI-000068 MEDIUM The application must ensure messages are encrypted when the SessionIndex is tied to privacy data. When the SessionIndex is tied to privacy data (e.g., attributes containing privacy data) the message should be encrypted. If the message is not encrypted there is the possibility of compromise of privacy data.
    SV-83917r1_rule APSC-DV-000280 CCI-000015 MEDIUM The application must provide automated mechanisms for supporting account management functions. Enterprise environments make application account management challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. Manual examples include but are not limited to admin staff loggi
    SV-83919r1_rule APSC-DV-000290 CCI-002142 MEDIUM Shared/group account credentials must be terminated when members leave the group. If shared/group account credentials are not terminated when individuals leave the group, the user that left the group can still gain access even though they are no longer authorized. A shared/group account credential is a shared form of authentication tha
    SV-83921r1_rule APSC-DV-000300 CCI-000016 MEDIUM The application must automatically remove or disable temporary user accounts 72 hours after account creation. If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. T
    SV-83923r1_rule APSC-DV-000320 CCI-000017 LOW The application must automatically disable accounts after a 35 day period of account inactivity. Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Applications need t
    SV-83925r1_rule APSC-DV-000330 CCI-000017 MEDIUM Unnecessary application accounts must be disabled, or deleted. Test or demonstration accounts are sometimes created during the application installation process. This creates a security risk as these accounts often remain after the initial installation process and can be used to gain unauthorized access to the applica
    SV-83927r1_rule APSC-DV-000340 CCI-000018 MEDIUM The application must automatically audit account creation. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Auditing of account creation is on
    SV-83929r1_rule APSC-DV-000350 CCI-001403 MEDIUM The application must automatically audit account modification. One way for an attacker to establish persistent access is for the attacker to modify or copy an existing account. Auditing of account modification is one method for mitigating this risk. A comprehensive account management process will ensure an audit trai
    SV-83931r1_rule APSC-DV-000360 CCI-001404 MEDIUM The application must automatically audit account disabling actions. When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events affecting user acc
    SV-83933r1_rule APSC-DV-000370 CCI-001405 MEDIUM The application must automatically audit account removal actions. When application accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events affecting user acce
    SV-83935r1_rule APSC-DV-000380 CCI-001683 LOW The application must notify System Administrators and Information System Security Officers when accounts are created. Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Notification of account creation is one me
    SV-83937r1_rule APSC-DV-000390 CCI-001684 LOW The application must notify System Administrators and Information System Security Officers when accounts are modified. Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Notification of account creation is one me
    SV-83939r1_rule APSC-DV-000400 CCI-001685 LOW The application must notify System Administrators and Information System Security Officers of account disabling actions. Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Notification of account creation is one me
    SV-83941r1_rule APSC-DV-000410 CCI-001686 LOW The application must notify System Administrators and Information System Security Officers of account removal actions. Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Notification of account creation is one me
    SV-83943r1_rule APSC-DV-000420 CCI-002130 MEDIUM The application must automatically audit account enabling actions. When application accounts are enabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events affecting user acce
    SV-83945r1_rule APSC-DV-000430 CCI-002132 LOW The application must notify System Administrators and Information System Security Officers of account enabling actions. Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply enable an existing account that has been previously disabled. No
    SV-83947r1_rule APSC-DV-000440 CCI-002346 MEDIUM Application data protection requirements must be identified and documented. Failure to protect organizational information from data mining may result in a compromise of information. In order to assign the appropriate data protections, application data must be identified and then protection requirements assigned. Access to sensiti
    SV-83949r1_rule APSC-DV-000450 CCI-002347 MEDIUM The application must utilize organization-defined data mining detection techniques for organization-defined data storage objects to adequately detect data mining attempts. Failure to protect organizational information from data mining may result in a compromise of information. Data mining occurs when the application is programmatically probed and data is automatically extracted. While there are valid uses for data mining w
    SV-83951r1_rule APSC-DV-000460 CCI-000213 HIGH The application must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., networks, web servers, and web portals) must be properly configured to incorporate access cont
    SV-83953r1_rule APSC-DV-000470 CCI-002165 MEDIUM The application must enforce organization-defined discretionary access control policies over defined subjects and objects. Discretionary Access Control allows users to determine who is allowed to access their data. To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., ne
    SV-83955r1_rule APSC-DV-000480 CCI-001368 MEDIUM The application must enforce approved authorizations for controlling the flow of information within the system based on organization-defined information flow control policies. A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations, the system may become compromised. Information flow contro
    SV-83957r1_rule APSC-DV-000490 CCI-001414 MEDIUM The application must enforce approved authorizations for controlling the flow of information between interconnected systems based on organization-defined information flow control policies. A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations, the system may become compromised. Information flow contro
    SV-83959r1_rule APSC-DV-000500 CCI-002235 MEDIUM The application must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. Privileged functions include, for example, establishing accounts,
    SV-83961r1_rule APSC-DV-000510 CCI-002233 HIGH The application must execute without excessive account permissions. Applications are often designed to utilize a user account. The account represents a means to control application permissions and access to OS resources, application resources or both. When the application is designed and installed, care must be taken
    SV-83963r1_rule APSC-DV-000520 CCI-002234 MEDIUM The application must audit the execution of privileged functions. Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts
    SV-83965r1_rule APSC-DV-000530 CCI-000044 HIGH The application must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period. By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account. User notification when three failed logon attemp
    SV-83969r1_rule APSC-DV-000540 CCI-002238 MEDIUM The application administrator must follow an approved process to unlock locked user accounts. Once a user account has been locked, it must be unlocked by an administrator. An ISSM and ISSO approved process must be created and followed to ensure the user requesting access is properly authenticated prior to access being re-established. The process
    SV-83971r2_rule APSC-DV-000550 CCI-000048 LOW The application must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application. Display of the DoD-approved use notification before granting access to the application ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and
    SV-83973r2_rule APSC-DV-000560 CCI-000050 LOW The application must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access. The banner must be acknowledged by the user prior to allowing the user access to the application. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD
    SV-83975r1_rule APSC-DV-000570 CCI-001384 LOW The publicly accessible application must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application. Display of a standardized and approved use notification before granting access to the publicly accessible application ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policie
    SV-83977r1_rule APSC-DV-000580 CCI-000052 LOW The application must display the time and date of the users last successful logon. Providing a last successful logon date and time stamp notification to the user when they authenticate and access the application allows the user to determine if their application account has been used without their knowledge. Armed with that information
    SV-83979r1_rule APSC-DV-000590 CCI-000166 MEDIUM The application must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation. Without non-repudiation, it is impossible to positively attribute an action to an individual (or process acting on behalf of an individual). Non-repudiation services can be used to determine if information originated from a particular individual, or if a
    SV-83981r1_rule APSC-DV-000600 CCI-000174 MEDIUM For applications providing audit record aggregation, the application must compile audit records from organization-defined information system components into a system-wide audit trail that is time-correlated with an organization-defined level of tolerance for the relationship between time stamps of individual records in the audit trail. Without the ability to collate records based on the time when the events occurred, the ability to perform forensic analysis and investigations across multiple components is significantly degraded. Audit trails are time-correlated if the time stamps in th
    SV-83983r1_rule APSC-DV-000610 CCI-001914 MEDIUM The application must provide the capability for organization-identified individuals or roles to change the auditing to be performed on all application components, based on all selectable event criteria within organization-defined time thresholds. If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to effectively respond, and important forensic information may be lost. This requirement enable
    SV-83985r1_rule APSC-DV-000620 CCI-000169 MEDIUM The application must provide audit record generation capability for the creation of session IDs. Applications create session IDs at the onset of a user session in order to manage user access to the application and differentiate between different user sessions. It is important to log the creation of these session ID creation events for forensic purpos
    SV-83987r1_rule APSC-DV-000630 CCI-000169 MEDIUM The application must provide audit record generation capability for the destruction of session IDs. Applications should destroy session IDs at the end of a user session in order to terminate user access to the application session and to reduce the possibility of an unauthorized attacker high jacking the session and impersonating the user. It is importan
    SV-83989r1_rule APSC-DV-000640 CCI-000169 MEDIUM The application must provide audit record generation capability for the renewal of session IDs. Application design sometimes requires the renewal of session IDs in order to continue approved user access to the application. Session renewal is done on a case by case basis under circumstances defined by the application architecture. The following are
    SV-83991r1_rule APSC-DV-000650 CCI-000169 MEDIUM The application must not write sensitive data into the application logs. It is important to identify and exclude certain types of data that is written into the logs. If the logs are compromised and sensitive data is included in the logs, this could assist an attacker in furthering their attack or it could completely compromise
    SV-83993r1_rule APSC-DV-000660 CCI-000169 MEDIUM The application must provide audit record generation capability for session timeouts. When a user's session times out, it is important to be able to identify these events in the application logs. Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incid
    SV-83995r1_rule APSC-DV-000670 CCI-000169 MEDIUM The application must record a time stamp indicating when the event occurred. It is important to include the time stamps for when an event occurred. Failure to include time stamps in the event logs is detrimental to forensic analysis.
    SV-83997r1_rule APSC-DV-000680 CCI-000169 MEDIUM The application must provide audit record generation capability for HTTP headers including User-Agent, Referer, GET, and POST. HTTP header information is a critical component of data that is used when evaluating forensic activity. Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, o
    SV-83999r1_rule APSC-DV-000690 CCI-000169 MEDIUM The application must provide audit record generation capability for connecting system IP addresses. Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit records can be generated from various components within the
    SV-84001r1_rule APSC-DV-000700 CCI-000169 MEDIUM The application must record the username or user ID of the user associated with the event. When users conduct activity within an application, that user’s identity must be recorded in the audit log. Failing to record the identity of the user responsible for the activity within the application is detrimental to forensic analysis.
    SV-84003r1_rule APSC-DV-000710 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to access privileges occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit reco
    SV-84005r1_rule APSC-DV-000720 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to access security objects occur. Security objects represent application objects that provide or require security protections or have a security role within the application. Examples include but are not limited to, files, application modules, folders, and database records. Essentially, if
    SV-84007r1_rule APSC-DV-000730 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to access security levels occur. A security level denotes a permissions or authorization capability within the application. This is most often associated with a user role. Attempts to access a security level can occur when a user attempts an action such as escalating their privilege from
    SV-84009r1_rule APSC-DV-000740 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Categories
    SV-84011r1_rule APSC-DV-000750 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to modify privileges occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit reco
    SV-84013r1_rule APSC-DV-000760 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to modify security objects occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit reco
    SV-84015r1_rule APSC-DV-000770 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to modify security levels occur. A security level denotes a permissions or authorization capability within the application. This is most often associated with a user role. Attempts to modify a security level can be construed as an attempt to change the configuration of the application so
    SV-84017r1_rule APSC-DV-000780 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit reco
    SV-84019r1_rule APSC-DV-000790 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to delete privileges occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit reco
    SV-84021r1_rule APSC-DV-000800 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to delete security levels occur. A security level denotes a permissions or authorization capability within the application. This is most often associated with a user role. Attempts to delete a security level can be construed as an attempt to change the configuration of the application so
    SV-84023r1_rule APSC-DV-000810 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to delete application database security objects occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit reco
    SV-84025r1_rule APSC-DV-000820 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful attempts to delete categories of information (e.g., classification levels) occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit reco
    SV-84027r1_rule APSC-DV-000830 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful logon attempts occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit reco
    SV-84029r1_rule APSC-DV-000840 CCI-000172 MEDIUM The application must generate audit records for privileged activities or other system-level access. Privileged activities include the tasks or actions taken by users in an administrative role (admin, backup operator, manager, etc.) which are used to manage or reconfigure application function. Examples include but are not limited to: Modifying applicati
    SV-84031r1_rule APSC-DV-000850 CCI-000172 MEDIUM The application must generate audit records showing starting and ending time for user access to the system. Knowing when a user’s application session began and when it ended is critical information that aids in forensic analysis.
    SV-84033r1_rule APSC-DV-000860 CCI-000172 MEDIUM The application must generate audit records when successful/unsuccessful accesses to objects occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Applicatio
    SV-84035r1_rule APSC-DV-000870 CCI-000172 MEDIUM The application must generate audit records for all direct access to the information system. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. When an ap
    SV-84037r1_rule APSC-DV-000880 CCI-000172 MEDIUM The application must generate audit records for all account creations, modifications, disabling, and termination events. When application user accounts are created, modified, disabled or terminated the event must be logged. Centralized management of user accounts allows for rapid response to user related security events and also provides ease of management. Allowing the c
    SV-84039r1_rule APSC-DV-000900 CCI-001919 MEDIUM The application must provide the capability for authorized users to select a user session to capture/record or view/hear. This is a specialized requirement for monitoring applications. Not all applications will be required to capture/record or view/hear user sessions.
    SV-84041r1_rule APSC-DV-000910 CCI-001464 MEDIUM The application must initiate session auditing upon startup. If the application does not begin logging upon startup, important log events could be missed.
    SV-84043r1_rule APSC-DV-000940 CCI-000130 MEDIUM The application must log application shutdown events. Forensics is a large part of security incident response. Applications must provide a record of their actions so application events can be investigated post-event. Attackers may attempt to shut off the application logging capability to cover their acti
    SV-84045r1_rule APSC-DV-000950 CCI-000130 MEDIUM The application must log destination IP addresses. The IP addresses of the systems that the application connects to are an important aspect of identifying application network related activity. Recording the IP addresses of the system the application connects to in the application logs provides forensic ev
    SV-84047r1_rule APSC-DV-000960 CCI-000130 MEDIUM The application must log user actions involving access to data. When users access application data, there is risk of data compromise or seepage if the account used to access is compromised or access is granted improperly. To be able to investigate which account accessed data, the account access must be logged. Without
    SV-84049r1_rule APSC-DV-000970 CCI-000130 MEDIUM The application must log user actions involving changes to data. When users change/modify application data, there is risk of data compromise if the account used to access is compromised or access is granted improperly. To be able to investigate which account accessed data, the account making the data changes must be lo
    SV-84051r1_rule APSC-DV-000980 CCI-000131 MEDIUM The application must produce audit records containing information to establish when (date and time) the events occurred. Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personne
    SV-84053r1_rule APSC-DV-000990 CCI-000132 MEDIUM The application must produce audit records containing enough information to establish which component, feature or function of the application triggered the audit event. It is impossible to establish, correlate, and investigate the events relating to an incident if the details regarding the source of the event it not available. In order to compile an accurate risk assessment, and provide forensic analysis, it is essentia
    SV-84055r1_rule APSC-DV-001000 CCI-000133 MEDIUM When using centralized logging; the application must include a unique identifier in order to distinguish itself from other application logs. Without establishing the source, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In the case of centralized logging, or other instances where log files are consolidated, there is risk that the appli
    SV-84057r1_rule APSC-DV-001010 CCI-000134 MEDIUM The application must produce audit records that contain information to establish the outcome of the events. Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event succ
    SV-84059r1_rule APSC-DV-001020 CCI-001487 MEDIUM The application must generate audit records containing information that establishes the identity of any individual or process associated with the event. Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. Event identifiers (if
    SV-84061r1_rule APSC-DV-001030 CCI-000135 MEDIUM The application must generate audit records containing the full-text recording of privileged commands or the individual identities of group account users. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requi
    SV-84063r1_rule APSC-DV-001040 CCI-000135 MEDIUM The application must implement transaction recovery logs when transaction based. Without required logging and access control, security issues related to data changes will not be identified. This could lead to security compromises such as data misuse, unauthorized changes, or unauthorized access. Transaction logs contain a sequential
    SV-84065r1_rule APSC-DV-001050 CCI-001844 MEDIUM The application must provide centralized management and configuration of the content to be captured in audit records generated by all application components. Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. This re
    SV-84067r1_rule APSC-DV-001070 CCI-001851 MEDIUM The application must off-load audit records onto a different system or media than the system being audited. Information stored in one location is vulnerable to accidental or incidental deletion or alteration. In addition, attackers often manipulate logs to hide or obfuscate their activity. The goal is to off-load application logs to a separate server as quick
    SV-84069r1_rule APSC-DV-001080 CCI-001851 MEDIUM The application must be configured to write application logs to a centralized log repository. Information stored in one location is vulnerable to accidental or incidental deletion or alteration. In addition, attackers often manipulate logs to hide or obfuscate their activity. Off-loading is a common process in information systems with limited au
    SV-84071r1_rule APSC-DV-001090 CCI-001855 MEDIUM The application must provide an immediate warning to the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity. If security personnel are not notified immediately upon storage volume utilization reaching 75%, they are unable to plan for storage capacity expansion. Due to variances in application usage and audit records storage usage, the SA and the ISSO may evalua
    SV-84073r1_rule APSC-DV-001100 CCI-001858 MEDIUM Applications categorized as having a moderate or high impact must provide an immediate real-time alert to the SA and ISSO (at a minimum) for all audit failure events. Applications that are categorized as having a high or moderate impact on the organization must provide immediate alerts when encountering failures with the application audit system. It is critical for the appropriate personnel to be aware if a system is
    SV-84075r1_rule APSC-DV-001110 CCI-000139 MEDIUM The application must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability and system opera
    SV-84077r1_rule APSC-DV-001120 CCI-000140 MEDIUM The application must shut down by default upon audit failure (unless availability is an overriding concern). It is critical that when the application is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit st
    SV-84079r1_rule APSC-DV-001130 CCI-000154 MEDIUM The application must provide the capability to centrally review and analyze audit records from multiple components within the system. Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. If the application does not provide the ability
    SV-84081r1_rule APSC-DV-001140 CCI-000158 MEDIUM The application must provide the capability to filter audit records for events of interest based upon organization-defined criteria. The ability to specify the event criteria that are of interest provides the persons reviewing the logs with the ability to quickly isolate and identify these events without having to review entries that are of little or no consequence to the investigation
    SV-84083r1_rule APSC-DV-001150 CCI-001876 MEDIUM The application must provide an audit reduction capability that supports on-demand reporting requirements. The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security i
    SV-84085r1_rule APSC-DV-001160 CCI-001875 MEDIUM The application must provide an audit reduction capability that supports on-demand audit review and analysis. The ability to perform on-demand audit review and analysis, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more c
    SV-84087r1_rule APSC-DV-001170 CCI-001877 MEDIUM The application must provide an audit reduction capability that supports after-the-fact investigations of security incidents. If the audit reduction capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack, or identify those responses for one. This capability is also required
    SV-84089r1_rule APSC-DV-001180 CCI-001878 MEDIUM The application must provide a report generation capability that supports on-demand audit review and analysis. The report generation capability must support on-demand review and analysis in order to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. Report generation must
    SV-84091r1_rule APSC-DV-001190 CCI-001879 MEDIUM The application must provide a report generation capability that supports on-demand reporting requirements. The report generation capability must support on-demand reporting in order to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. The report generation capability
    SV-84093r1_rule APSC-DV-001200 CCI-001880 MEDIUM The application must provide a report generation capability that supports after-the-fact investigations of security incidents. If the report generation capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack, or identify those responses for one. This capability is also require
    SV-84095r1_rule APSC-DV-001210 CCI-001881 MEDIUM The application must provide an audit reduction capability that does not alter original content or time ordering of audit records. If the audit reduction capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis. Time ordering refers to the chronological organization o
    SV-84097r1_rule APSC-DV-001220 CCI-001882 MEDIUM The application must provide a report generation capability that does not alter original content or time ordering of audit records. If the audit report generation capability alters the original content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis. Time ordering refers to the chronologic
    SV-84099r1_rule APSC-DV-001250 CCI-000159 MEDIUM The applications must use internal system clocks to generate time stamps for audit records. Without an internal clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysis would be impeded. Determining the correct time a particular event occurred on a system is critical when
    SV-84101r1_rule APSC-DV-001260 CCI-001890 MEDIUM The application must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the application include date and time. Time is commonly expressed in Coordinated Universal Time (UTC
    SV-84103r1_rule APSC-DV-001270 CCI-001889 MEDIUM The application must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision. Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the application include date and time. Granularity of time measurements refers to the degree of synchro
    SV-84105r1_rule APSC-DV-001280 CCI-000162 MEDIUM The application must protect audit information from any type of unauthorized read access. If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult if not impossible to achieve. In addition, access to audit records provides information an at
    SV-84107r1_rule APSC-DV-001290 CCI-000163 MEDIUM The application must protect audit information from unauthorized modification. If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the information system and/or the application must
    SV-84109r1_rule APSC-DV-001300 CCI-000164 MEDIUM The application must protect audit information from unauthorized deletion. If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the information system and/or the application must
    SV-84111r1_rule APSC-DV-001310 CCI-001493 MEDIUM The application must protect audit tools from unauthorized access. Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with
    SV-84113r1_rule APSC-DV-001320 CCI-001494 MEDIUM The application must protect audit tools from unauthorized modification. Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with
    SV-84115r1_rule APSC-DV-001330 CCI-001495 MEDIUM The application must protect audit tools from unauthorized deletion. Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with
    SV-84117r1_rule APSC-DV-001340 CCI-001348 MEDIUM The application must back up audit records at least every seven days onto a different system or system component than the system or component being audited. Protection of log data includes assuring log data is not accidentally lost or deleted. Backing up audit records to a different system or onto separate media than the system being audited on an organizationally defined frequency helps to assure in the even
    SV-84119r1_rule APSC-DV-001350 CCI-001350 MEDIUM The application must use cryptographic mechanisms to protect the integrity of audit information. Audit records may be tampered with; if the integrity of audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. Protection of audit records and audi
    SV-84121r1_rule APSC-DV-001360 CCI-001496 MEDIUM Application audit tools must be cryptographically hashed. Protecting the integrity of the tools used for auditing purposes is a critical step to ensuring the integrity of audit data. Audit data includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit informat
    SV-84123r1_rule APSC-DV-001370 CCI-001496 MEDIUM The integrity of the audit tools must be validated by checking the files for changes in the cryptographic hash value. Protecting the integrity of the tools used for auditing purposes is a critical step to ensuring the integrity of audit data. Audit data includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit informat
    SV-84125r1_rule APSC-DV-001390 CCI-001812 MEDIUM The application must prohibit user installation of software without explicit privileged status. Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular use
    SV-84127r1_rule APSC-DV-001410 CCI-001813 MEDIUM The application must enforce access restrictions associated with changes to application configuration. Failure to provide logical access restrictions associated with changes to application configuration may have significant effects on the overall security of the system. When dealing with access restrictions pertaining to change control, it should be noted
    SV-84129r1_rule APSC-DV-001420 CCI-001814 MEDIUM The application must audit who makes configuration changes to the application. Without auditing the enforcement of access restrictions against changes to the application configuration, it will be difficult to identify attempted attacks and an audit trail will not be available for forensic investigation for after-the-fact actions. E
    SV-84131r1_rule APSC-DV-001430 CCI-001749 MEDIUM The application must have the capability to prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization. Changes to any software components can have significant effects on the overall security of the application. Verifying software components have been digitally signed using a certificate that is recognized and approved by the organization ensures the softwa
    SV-84133r1_rule APSC-DV-001440 CCI-001499 MEDIUM The applications must limit privileges to change the software resident within software libraries. If the application were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. This requirement applie
    SV-84135r1_rule APSC-DV-001460 CCI-000366 MEDIUM An application vulnerability assessment must be conducted. An application vulnerability assessment is a test conducted in order to identify weaknesses and security vulnerabilities that may exist within an application. The testing must cover all aspects and components of the application architecture. If an appli
    SV-84137r1_rule APSC-DV-001480 CCI-001764 MEDIUM The application must prevent program execution in accordance with organization-defined policies regarding software program usage and restrictions, and/or rules authorizing the terms and conditions of software program usage. Control of application execution is a mechanism used to prevent execution of unauthorized applications in order to follow the rules of least privilege. Some applications may provide a capability that runs counter to the mission or provides users with func
    SV-84139r1_rule APSC-DV-001490 CCI-001774 MEDIUM The application must employ a deny-all, permit-by-exception (whitelist) policy to allow the execution of authorized software programs. Utilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. The organization must identify aut
    SV-84141r1_rule APSC-DV-001500 CCI-000381 MEDIUM The application must be configured to disable non-essential capabilities. It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to
    SV-84143r1_rule APSC-DV-001510 CCI-000382 MEDIUM The application must be configured to use only functions, ports, and protocols permitted to it in the PPSM CAL. In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical po
    SV-84145r1_rule APSC-DV-001520 CCI-002038 MEDIUM The application must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the functional capability of the application, it is critical the
    SV-84147r1_rule APSC-DV-001530 CCI-002039 MEDIUM The application must require devices to reauthenticate when organization-defined circumstances or situations requiring reauthentication. Without reauthenticating devices, unidentified or unknown devices may be introduced; thereby facilitating malicious activity. In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of de
    SV-84149r1_rule APSC-DV-001540 CCI-000764 HIGH The application must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the orga
    SV-84151r1_rule APSC-DV-001550 CCI-000765 MEDIUM The application must use multifactor (Alt. Token) authentication for network access to privileged accounts. Multifactor authentication requires using two or more factors to achieve authentication and access. Factors include: (i) something a user knows (e.g., password/PIN); (ii) something a user has (e.g., cryptographic identification device, token); or (iii) s
    SV-84153r1_rule APSC-DV-001560 CCI-001953 MEDIUM The application must accept Personal Identity Verification (PIV) credentials. The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under HSPD 12, as well as a primary com
    SV-84155r1_rule APSC-DV-001570 CCI-001954 MEDIUM The application must electronically verify Personal Identity Verification (PIV) credentials. The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under HSPD 12, as well as a primary com
    SV-84157r1_rule APSC-DV-001580 CCI-000766 MEDIUM The application must use multifactor (e.g., CAC, Alt. Token) authentication for network access to non-privileged accounts. To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication uses two or more factors to achieve authenticat
    SV-84159r1_rule APSC-DV-001590 CCI-000767 MEDIUM The application must use multifactor (Alt. Token) authentication for local access to privileged accounts. Multifactor authentication requires using two or more factors to achieve authentication and access. Factors include: (i) something a user knows (e.g., password/PIN); (ii) something a user has (e.g., cryptographic identification device, token); or (iii) s
    SV-84161r1_rule APSC-DV-001600 CCI-000768 MEDIUM The application must use multifactor (e.g., CAC, Alt. Token) authentication for local access to non-privileged accounts. To assure accountability, prevent unauthenticated access, and prevent misuse of the system, privileged users must utilize multifactor authentication for local access. Multifactor authentication is defined as: using two or more factors to achieve authenti
    SV-84163r1_rule APSC-DV-001610 CCI-000770 MEDIUM The application must ensure users are authenticated with an individual authenticator prior to using a group authenticator. To assure individual accountability and prevent unauthorized access, application users must be individually identified and authenticated. Individual accountability mandates that each user is uniquely identified. A group authenticator is a shared account
    SV-84165r1_rule APSC-DV-001620 CCI-001941 MEDIUM The application must implement replay-resistant authentication mechanisms for network access to privileged accounts. A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack. An authentication process
    SV-84167r1_rule APSC-DV-001630 CCI-001942 MEDIUM The application must implement replay-resistant authentication mechanisms for network access to non-privileged accounts. A replay attack is a man-in-the-middle style attack which allows an attacker to repeat or alter a valid data transmission that may enable unauthorized access to the application. Authentication sessions between the authenticating client and the application
    SV-84169r1_rule APSC-DV-001640 CCI-000778 MEDIUM The application must utilize mutual authentication when endpoint device non-repudiation protections are required by DoD policy or by the data owner. Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. With one way SSL authentication which is the typical form of SSL authentication done between a web browser client and a web server, t
    SV-84171r1_rule APSC-DV-001650 CCI-001958 MEDIUM The application must authenticate all network connected endpoint devices before establishing any connection. Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. For distributed architectures (e.g., service-oriented architectures), the decisions regarding the validation of authentication cla
    SV-84173r1_rule APSC-DV-001660 CCI-001967 MEDIUM Service-Oriented Applications handling non-releasable data must authenticate endpoint devices via mutual SSL/TLS. Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. One way SSL/TLS authentication is the typical form of authentication done between a web browser client and a web server. The client
    SV-84175r2_rule APSC-DV-001670 CCI-000795 MEDIUM The application must disable device identifiers after 35 days of inactivity unless a cryptographic certificate is used for authentication. Device identifiers are used to identify hardware devices that interact with the application much like a user account is used to identify an application user. Examples of hardware devices include but are not limited to mobile phones, application gateways
    SV-84177r1_rule APSC-DV-001680 CCI-000205 HIGH The application must enforce a minimum 15-character password length. The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Use of passwords for application authentication is intended only for limited situations and should not be used as a replace
    SV-84179r1_rule APSC-DV-001690 CCI-000192 MEDIUM The application must enforce password complexity by requiring that at least one upper-case character be used. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84181r1_rule APSC-DV-001700 CCI-000193 MEDIUM The application must enforce password complexity by requiring that at least one lower-case character be used. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84183r1_rule APSC-DV-001710 CCI-000194 MEDIUM The application must enforce password complexity by requiring that at least one numeric character be used. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84185r1_rule APSC-DV-001720 CCI-001619 MEDIUM The application must enforce password complexity by requiring that at least one special character be used. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84187r1_rule APSC-DV-001730 CCI-000195 MEDIUM The application must require the change of at least 8 of the total number of characters when passwords are changed. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84189r1_rule APSC-DV-001740 CCI-000196 HIGH The application must only store cryptographic representations of passwords. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84191r1_rule APSC-DV-001750 CCI-000197 HIGH The application must transmit only cryptographically-protected passwords. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84193r1_rule APSC-DV-001760 CCI-000198 MEDIUM The application must enforce 24 hours/1 day as the minimum password lifetime. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84195r1_rule APSC-DV-001770 CCI-000199 MEDIUM The application must enforce a 60-day maximum password lifetime restriction. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84197r1_rule APSC-DV-001780 CCI-000200 MEDIUM The application must prohibit password reuse for a minimum of five generations. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84199r1_rule APSC-DV-001790 CCI-002041 MEDIUM The application must allow the use of a temporary password for system logons with an immediate change to a permanent password. Use of passwords for application authentication is intended only for limited situations and should not be used as a replacement for two-factor CAC-enabled authentication. Examples of situations where a user ID and password might be used include but are n
    SV-84767r1_rule APSC-DV-001795 CCI-000184 MEDIUM The application password must not be changeable by users other than the administrator or the user with which the password is associated. If the application allows user A to change user B's password, user B can be locked out of the application, and user A is provided the ability to grant themselves access to the application as user B. This violates application integrity and availability p
    SV-84769r2_rule APSC-DV-001800 CCI-002007 MEDIUM The application must terminate existing user sessions upon account deletion. The application must ensure that a user does not retain any rights that may have been granted or retain access to the application after the user's authorization or role within the application has been deleted or modified. This means once a user's role/ac
    SV-84771r1_rule APSC-DV-001810 CCI-000185 HIGH The application, when utilizing PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. A trust anchor is an authoritative entity represented via a public key and associated data. It is
    SV-84773r1_rule APSC-DV-001820 CCI-000186 HIGH The application, when using PKI-based authentication, must enforce authorized access to the corresponding private key. If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the privat
    SV-84775r1_rule APSC-DV-001830 CCI-000187 MEDIUM The application must map the authenticated identity to the individual user or group account for PKI-based authentication. Without mapping the certificate used to authenticate to a corresponding user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis. Some CAs will include identifying information like an
    SV-84777r1_rule APSC-DV-001840 CCI-001991 MEDIUM The application, for PKI-based authentication, must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. A local cache of revocation data is also known as a CRL list. This list contains a list of revoked certificates and can be periodically downloaded to ensure certificates can still be checked for revocation when network access is not available or access to
    SV-84779r2_rule APSC-DV-001850 CCI-000206 HIGH The application must not display passwords/PINs as clear text. To prevent the compromise of authentication information such as passwords during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication m
    SV-84781r2_rule APSC-DV-001860 CCI-000803 MEDIUM The application must use mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. A cryptographic module is a hardware or software device or component that performs cryptographic operations securely within a physical or logical boundary, using a hardware, software or hybrid cryptographic engine contained within the boundary, and crypto
    SV-84783r1_rule APSC-DV-001870 CCI-000804 MEDIUM The application must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). Lack of authentication and identification enables non-organizational users to gain access to the application or possibly other information systems and provides an opportunity for intruders to compromise resources within the application or information syst
    SV-84785r1_rule APSC-DV-001880 CCI-002009 MEDIUM The application must accept Personal Identity Verification (PIV) credentials from other federal agencies. Access may be denied to authorized users if federal agency PIV credentials are not accepted. Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance do
    SV-84787r1_rule APSC-DV-001890 CCI-002010 MEDIUM The application must electronically verify Personal Identity Verification (PIV) credentials from other federal agencies. Inappropriate access may be granted to unauthorized users if federal agency PIV credentials are not electronically verified. Personal Identity Verification (PIV) credentials are those credentials issued by federal agencies that conform to FIPS Publicatio
    SV-84789r1_rule APSC-DV-001900 CCI-002011 MEDIUM The application must accept FICAM-approved third-party credentials. FICAM establishes a federated identity framework for the Federal Government. FICAM provides Government-wide services for common Identity, Credential and Access Management (ICAM) requirements. The FICAM Trust Framework Solutions (TFS) is the federated ide
    SV-84791r1_rule APSC-DV-001910 CCI-002014 MEDIUM The application must conform to FICAM-issued profiles. FICAM establishes a federated identity framework for the Federal Government. FICAM provides Government-wide services for common Identity, Credential, and Access Management (ICAM) requirements. The FICAM Trust Framework Solutions (TFS) is the federated id
    SV-84793r1_rule APSC-DV-001930 CCI-002884 MEDIUM Applications used for non-local maintenance sessions must audit non-local maintenance and diagnostic sessions for organization-defined auditable events. Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those ac
    SV-84795r1_rule APSC-DV-000310 CCI-000011 LOW The application must have a process, feature or function that prevents removal or disabling of emergency accounts. Emergency accounts are administrator accounts which are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If th
    SV-84797r1_rule APSC-DV-001940 CCI-002890 MEDIUM Applications used for non-local maintenance sessions must implement cryptographic mechanisms to protect the integrity of non-local maintenance and diagnostic communications. Privileged access contains control and configuration information which is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms to protect integrity. Non-local maintenance and diagnostic act
    SV-84799r1_rule APSC-DV-001950 CCI-003123 MEDIUM Applications used for non-local maintenance sessions must implement cryptographic mechanisms to protect the confidentiality of non-local maintenance and diagnostic communications. Privileged access contains control and configuration information which is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms to protect confidentiality. Non-local maintenance and diagnost
    SV-84801r1_rule APSC-DV-001960 CCI-002891 MEDIUM Applications used for non-local maintenance sessions must verify remote disconnection at the termination of non-local maintenance and diagnostic sessions. Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network. Local maintenance and diagnostic activities are those ac
    SV-84803r1_rule APSC-DV-001970 CCI-000877 MEDIUM The application must employ strong authenticators in the establishment of non-local maintenance and diagnostic sessions. If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing systems and applications includes the ability to access sensitive application information, such as, system
    SV-84805r1_rule APSC-DV-001980 CCI-000879 MEDIUM The application must terminate all sessions and network connections when non-local maintenance is completed. If a maintenance session or connection remains open after maintenance is completed, it may be hijacked by an attacker and used to compromise or damage the system. Non-local maintenance and diagnostic activities are those activities conducted by individua
    SV-84807r1_rule APSC-DV-001995 CCI-003178 MEDIUM The application must not be vulnerable to race conditions. A race condition is a timing event within an application that can become a security vulnerability. A race condition can occur when a pair of programming calls operating simultaneously do not work in a sequential or coordinated manner. A race condition i
    SV-84809r1_rule APSC-DV-002000 CCI-001133 MEDIUM The application must terminate all network connections associated with a communications session at the end of the session. Networked applications routinely open connections to and from other systems as part of their design and function. When connections are opened by the application, system resources are consumed. Terminating the network connection at the end of the applica
    SV-84811r2_rule APSC-DV-002010 CCI-002450 MEDIUM The application must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect classified data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this p
    SV-84813r2_rule APSC-DV-002020 CCI-002450 MEDIUM The application must utilize FIPS-validated cryptographic modules when signing application components. Applications that distribute components of the application must sign the components to provide an identity assurance to consumers of the application component. Components can include application messages or application code. Use of weak or untested encry
    SV-84815r2_rule APSC-DV-002030 CCI-002450 MEDIUM The application must utilize FIPS-validated cryptographic modules when generating cryptographic hashes. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides ass
    SV-84817r1_rule APSC-DV-002040 CCI-002450 MEDIUM The application must utilize FIPS-validated cryptographic modules when protecting unclassified information that requires cryptographic protection. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides ass
    SV-84819r1_rule APSC-DV-002050 CCI-002450 MEDIUM Applications making SAML assertions must use FIPS-approved random numbers in the generation of SessionIndex in the SAML element AuthnStatement. A predictable SessionIndex could lead to an attacker computing a future SessionIndex, thereby, possibly compromising the application. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The appli
    SV-84821r1_rule APSC-DV-002150 CCI-001082 MEDIUM The application user interface must be either physically or logically separated from data storage and management interfaces. Application management functionality includes functions necessary for administration and requires privileged user access. Allowing non-privileged users to access application management functionality capabilities increases the risk that non-privileged user
    SV-84823r1_rule APSC-DV-002210 CCI-001184 MEDIUM The application must set the HTTPOnly flag on session cookies. HTTPOnly is a flag included in a Set-Cookie HTTP response header. If the HTTPOnly flag is included in the HTTP response header, the cookie cannot be accessed through client side scripts like JavaScript. If the HTTPOnly flag is set, even if a cross-site s
    SV-84825r1_rule APSC-DV-002220 CCI-001184 MEDIUM The application must set the secure flag on session cookies. Many web development frameworks such as PHP, .NET, ASP as well as application servers include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management framework. Setting the secure bit on
    SV-84827r1_rule APSC-DV-002230 CCI-001184 HIGH The application must not expose session IDs. Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. Application communication sessions are protected utilizing transport encryption protocols, such as SSL o
    SV-84829r1_rule APSC-DV-002240 CCI-001185 HIGH The application must destroy the session ID value and/or cookie on logoff or browser close. Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management framework. Session cookies contain application session informat
    SV-84831r1_rule APSC-DV-002250 CCI-001664 MEDIUM Applications must use system-generated session identifiers that protect against session fixation. Session fixation allows an attacker to hijack a valid user’s application session. The attack focuses on the manner in which a web application manages the user’s session ID. Applications become vulnerable when they do not assign a new session ID when a
    SV-84833r1_rule APSC-DV-002260 CCI-001664 MEDIUM Applications must validate session identifiers. Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management framework.
    SV-84835r1_rule APSC-DV-002270 CCI-001664 MEDIUM Applications must not use URL embedded session IDs. Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management framework. Using a session ID that is copied to the URL introdu
    SV-84837r1_rule APSC-DV-002280 CCI-001664 MEDIUM The application must not re-use or recycle session IDs. Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management framework. Session identifiers are assigned to application user
    SV-84839r1_rule APSC-DV-002290 CCI-001188 MEDIUM The application must use the Federal Information Processing Standard (FIPS) 140-2-validated cryptographic modules and random number generator if the application implements encryption, key exchange, digital signature, and hash functionality. Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generation of unique session identifiers helps to protect against brute-force attacks to determine future session identifiers. Unique sess
    SV-84841r1_rule APSC-DV-002300 CCI-002470 MEDIUM The application must only allow the use of DoD-approved certificate authorities for verification of the establishment of protected sessions. Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate
    SV-84843r1_rule APSC-DV-002310 CCI-001190 HIGH The application must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Applications or systems that fail suddenly and with no incorporated failure state planning may leave the ho
    SV-84845r1_rule APSC-DV-002320 CCI-001665 MEDIUM In the event of a system failure, applications must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes. Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the
    SV-84847r1_rule APSC-DV-002330 CCI-001199 MEDIUM The application must protect the confidentiality and integrity of stored information when required by DoD policy or the information owner. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive) within an organizational information system. Mobile devices, laptops, desktops, and storage devices can be either los
    SV-84849r1_rule APSC-DV-002340 CCI-002475 MEDIUM The application must implement approved cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest on organization-defined information system components. Applications handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. Selection of a cryptographic mechanism is based on the need to protect th
    SV-84851r1_rule APSC-DV-002350 CCI-002476 MEDIUM The application must use appropriate cryptography in order to protect stored DoD information when required by the information owner or DoD policy. Applications handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. Selection of a cryptographic mechanism is based on the need to protect th
    SV-84853r1_rule APSC-DV-002360 CCI-001084 MEDIUM The application must isolate security functions from non-security functions. An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software, and/or firmware of the information system responsible for enf
    SV-84855r1_rule APSC-DV-002370 CCI-002530 MEDIUM The application must maintain a separate execution domain for each executing process. Applications can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is performed in a manner controlled throu
    SV-84857r1_rule APSC-DV-002380 CCI-001090 MEDIUM Applications must prevent unauthorized and unintended information transfer via shared system resources. Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from bein
    SV-84859r1_rule APSC-DV-002390 CCI-002385 MEDIUM XML-based applications must mitigate DoS attacks by using XML filters, parser options, or gateways. DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. XML-based applications are susceptible to DoS attacks due to the natur
    SV-84861r1_rule APSC-DV-002400 CCI-001094 MEDIUM The application must restrict the ability to launch Denial of Service (DoS) attacks against itself or other information systems. Denial of Service (DoS) is a condition where a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. Individuals of concern can include hostile inside
    SV-84863r1_rule APSC-DV-002410 CCI-001095 MEDIUM The web service design must include redundancy mechanisms when used with high-availability systems. DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. In the case of application DoS attacks, care must be taken when design
    SV-84865r1_rule APSC-DV-002420 CCI-001125 MEDIUM An XML firewall function must be deployed to protect web services when exposed to untrusted networks. Web Services are vulnerable to many types of attacks such as XML injection or XML External Entity (XXE) attacks. The risks increase when these applications are exposed to untrusted networks. XML-based firewall functionality can be used to prevent common
    SV-84867r1_rule APSC-DV-002440 CCI-002418 HIGH The application must protect the confidentiality and integrity of transmitted information. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies to those applications that transmit data, or all
    SV-84869r1_rule APSC-DV-002450 CCI-002421 MEDIUM The application must implement cryptographic mechanisms to prevent unauthorized disclosure of information and/or detect changes to information during transmission unless otherwise protected by alternative physical safeguards, such as, at a minimum, a Protected Distribution System (PDS). Data is subject to manipulation and other integrity related attacks whenever that data is transferred across a network. To protect data integrity during transmission, the application must implement mechanisms to ensure the integrity of all transmitted inf
    SV-84871r1_rule APSC-DV-002460 CCI-002420 MEDIUM The application must maintain the confidentiality and integrity of information during preparation for transmission. Data is subject to manipulation and other integrity related attacks whenever that data is transferred across a network. To protect data integrity during transmission, the application must implement mechanisms to ensure the integrity of all transmitted inf
    SV-84873r1_rule APSC-DV-002470 CCI-002422 MEDIUM The application must maintain the confidentiality and integrity of information during reception. Data is subject to manipulation and other integrity related attacks whenever that data is transferred across a network. To protect data integrity during transmission, the application must implement mechanisms to ensure the integrity of all transmitted inf
    SV-84875r1_rule APSC-DV-002480 CCI-002420 MEDIUM The application must not disclose unnecessary information to users. Applications should not disclose information not required for the transaction. (e.g., a web application should not divulge the fact there is a SQL server database and/or its version). These events usually occur when the web application has not been confi
    SV-84877r1_rule APSC-DV-002485 CCI-002420 HIGH The application must not store sensitive information in hidden fields. Hidden fields allow developers to process application data without having to display it on the screen. Using hidden fields to pass data in forms is a common practice among web applications and by itself is not a security risk. However, hidden fields a
    SV-84879r1_rule APSC-DV-002490 CCI-001310 HIGH The application must protect from Cross-Site Scripting (XSS) vulnerabilities. XSS attacks are essentially code injection attacks against the various language interpreters contained within the browser. XSS can be executed via HTML, JavaScript, VBScript, ActiveX; essentially any scripting language a browser is capable of processing.
    SV-84881r1_rule APSC-DV-002500 CCI-001310 MEDIUM The application must protect from Cross-Site Request Forgery (CSRF) vulnerabilities. Cross-Site Request Forgery (CSRF) is an attack where a website user is forced to execute an unwanted action on a website that he or she is currently authenticated to. An attacker, through social engineering (e.g., e-mail or chat) creates a hyperlink which
    SV-84883r1_rule APSC-DV-002510 CCI-001310 HIGH The application must protect from command injection. A command injection attack is an attack on a vulnerable application where improperly validated input is passed to a command shell setup in the application. The result is the ability of an attacker to execute OS commands via the application. A command inj
    SV-84885r1_rule APSC-DV-002520 CCI-001310 MEDIUM The application must protect from canonical representation vulnerabilities. Canonical representation vulnerabilities can occur when a data conversion process does not convert the data to its simplest form resulting in the possible misrepresentation of the data. The application may behave in an unexpected manner when acting on in
    SV-84887r1_rule APSC-DV-002530 CCI-001310 MEDIUM The application must validate all input. Checking the valid syntax and semantics of information system inputs (e.g., character set, length, numerical range, and acceptable values) verifies that inputs match specified definitions for format and content. Software applications typically follow well
    SV-84889r1_rule APSC-DV-002540 CCI-001310 HIGH The application must not be vulnerable to SQL Injection. SQL Injection is a code injection attack against database applications. Malicious SQL statements are inserted into an application data entry field where they are submitted to the database and executed. This is a direct result of not validating input that
    SV-84891r1_rule APSC-DV-002550 CCI-001310 HIGH The application must not be vulnerable to XML-oriented attacks. Extensible Markup Language (XML) is widely employed in web technology and applications like web services (SOAP, REST, and WSDL) and is also used for configuration files. XML vulnerability examples include XML injection, XML Spoofing, XML-based Denial of S
    SV-84893r1_rule APSC-DV-002560 CCI-002754 HIGH The application must not be subject to input handling vulnerabilities. A common application vulnerability is unpredictable behavior due to improper input validation. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be d
    SV-84895r1_rule APSC-DV-002570 CCI-001312 MEDIUM The application must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify application components. Additionally, Personally Identifiable Information (PII) and o
    SV-84897r1_rule APSC-DV-002580 CCI-001314 MEDIUM The application must reveal error messages only to the ISSO, ISSM, or SA. Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify application components. Additionally, Personally Identifiable Information (PII) and o
    SV-84899r1_rule APSC-DV-002590 CCI-002824 HIGH The application must not be vulnerable to overflow attacks. A buffer overflow occurs when a program exceeds the amount of data allocated to a buffer. The buffer is a sequential section of memory and when the data is written outside the memory bounds, the program can crash or malicious code can be executed. Securi
    SV-84901r1_rule APSC-DV-002610 CCI-002617 MEDIUM The application must remove organization-defined software components after updated versions have been installed. Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the
    SV-84903r1_rule APSC-DV-002630 CCI-002605 MEDIUM Security-relevant software updates and patches must be kept up to date. Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to
    SV-84905r1_rule APSC-DV-002760 CCI-002696 MEDIUM The application performing organization-defined security functions must verify correct operation of security functions. Without verification, security functions may not operate correctly and this failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy a
    SV-84907r1_rule APSC-DV-002770 CCI-002699 MEDIUM The application must perform verification of the correct operation of security functions: upon system startup and/or restart; upon command by a user with privileged access; and/or every 30 days. Without verification, security functions may not operate correctly and this failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy a
    SV-84909r1_rule APSC-DV-002780 CCI-001294 LOW The application must notify the ISSO and ISSM of failed security verification tests. If personnel are not notified of failed security verification tests, they will not be able to take corrective action and the unsecure condition(s) will remain. Security function is defined as the hardware, software, and/or firmware of the information sys
    SV-84911r1_rule APSC-DV-002870 CCI-001166 MEDIUM Unsigned Category 1A mobile code must not be used in the application in accordance with DoD policy. Use of un-trusted Level 1A mobile code technologies can introduce security vulnerabilities and malicious code into the client system. 1A code is defined as: - ActiveX controls - Mobile code script (JavaScript, VBScript) - Windows Scripting Host (WSH) (d
    SV-84913r1_rule APSC-DV-002880 CCI-002121 MEDIUM The ISSO must ensure an account management process is implemented, verifying only authorized users can gain access to the application, and individual accounts designated as inactive, suspended, or terminated are promptly removed. A comprehensive account management process will ensure that only authorized users can gain access to applications and that individual accounts designated as inactive, suspended, or terminated are promptly deactivated. Such a process greatly reduces the ri
    SV-84915r1_rule APSC-DV-002890 CCI-002225 HIGH Application web servers must be on a separate network segment from the application and database servers if it is a tiered application operating in the DoD DMZ. A tiered application usually consists of 3 tiers, the web layer (presentation tier), the application layer (application logic tier), and the database layer (data storage tier). Using one system for hosting all 3 tiers introduces risk that if one tier is
    SV-84917r1_rule APSC-DV-002900 CCI-000167 MEDIUM The ISSO must ensure application audit trails are retained for at least 1 year for applications without SAMI data, and 5 years for applications including SAMI data. Log files are a requirement to trace intruder activity or to audit user activity.
    SV-84919r1_rule APSC-DV-002910 CCI-001872 MEDIUM The ISSO must review audit trails periodically based on system documentation recommendations or immediately upon system security events. Without access control the data is not secure. It can be compromised, misused, or changed by unauthorized access at any time.
    SV-84923r1_rule APSC-DV-002920 CCI-000149 MEDIUM The ISSO must report all suspected violations of IA policies in accordance with DoD information system IA procedures. Violations of IA policies must be reviewed and reported. If there are no policies regarding the reporting of IA violations, IA violations may not be tracked or addressed in a proper manner.
    SV-84925r1_rule APSC-DV-002930 CCI-000256 MEDIUM The ISSO must ensure active vulnerability testing is performed. Use of automated scanning tools accompanied with manual testing/validation which confirms or expands on the automated test results is an accepted best practice when performing application security testing. Automated scanning tools expedite and help to sta
    SV-84929r1_rule APSC-DV-002950 CCI-000336 MEDIUM Execution flow diagrams and design documents must be created to show how deadlock and recursion issues in web services are being mitigated. In order to understand data flows within web services, the process flow of data must be developed and documented. There are several different ways that web service deadlock occurs, many times it is due to when a client invokes a synchronous method on a w
    SV-84931r1_rule APSC-DV-002960 CCI-000345 MEDIUM The designer must ensure the application does not store configuration and control files in the same directory as user data. Application configuration settings and user data are required to be stored in separate locations in order to prevent application users from possibly being able to access application configuration settings or application data files. Without proper access c
    SV-84933r1_rule APSC-DV-002970 CCI-000363 MEDIUM The ISSO must ensure if a DoD STIG or NSA guide is not available, a third-party product will be configured by following available guidance. Not all COTS products are covered by a STIG. Those products not covered by a STIG, should follow commercially accepted best practices, independent testing results and vendors lock down guides and recommendations if they are available.
    SV-84935r1_rule APSC-DV-002980 CCI-000388 MEDIUM New IP addresses, data services, and associated ports used by the application must be submitted to the appropriate approving authority for the organization, which in turn will be submitted through the DoD Ports, Protocols, and Services Management (DoD PPSM). Failure to comply with DoD Ports, Protocols, and Services (PPS) Vulnerability Analysis and associated PPS mitigations may result in compromise of enclave boundary protections and/or functionality of the application.
    SV-84939r2_rule APSC-DV-002990 CCI-000388 MEDIUM The application must be registered with the DoD Ports and Protocols Database. Failure to register the applications usage of ports, protocols, and services with the DoD PPS Database may result in a Denial of Service (DoS) because of enclave boundary protections at other end points within the network.
    SV-84961r1_rule APSC-DV-002995 CCI-001795 MEDIUM The Configuration Management (CM) repository must be properly patched and STIG compliant. A Configuration Management (CM) repository is used to manage application code versions and to securely store application code. Failure to properly apply security patches and secure the software Configuration Management system could affect the confidentia
    SV-84963r1_rule APSC-DV-003000 CCI-001795 MEDIUM Access privileges to the Configuration Management (CM) repository must be reviewed every three months. A Configuration Management (CM) repository is used to manage application code versions and to securely store application code. Incorrect access privileges to the CM repository can lead to malicious code or unintentional code being introduced into the app
    SV-84965r1_rule APSC-DV-003010 CCI-001795 MEDIUM A Software Configuration Management (SCM) plan describing the configuration control and change management process of application objects developed by the organization and the roles and responsibilities of the organization must be created and maintained. Software Configuration Management (SCM) is very important in tracking code releases, baselines, and managing access to the configuration management repository. The SCM plan identifies what should be under configuration management control. Without an SCM
    SV-84967r1_rule APSC-DV-003020 CCI-001795 MEDIUM A Configuration Control Board (CCB) that meets at least every release cycle, for managing the Configuration Management (CM) process must be established. Software Configuration Management (SCM) is very important in tracking code releases, baselines, and managing access to the configuration management repository. The SCM plan identifies what should be under configuration management control. Without an SCM p
    SV-84969r1_rule APSC-DV-003030 CCI-002853 MEDIUM The application services and interfaces must be compatible with and ready for IPv6 networks. If the application has not been upgraded to execute on an IPv6-only network, there is a possibility the application will not execute properly, and as a result, a denial of service could occur. In order to operate on an IPV6 network, the application must
    SV-84971r1_rule APSC-DV-003040 CCI-002828 MEDIUM The application must not be hosted on a general purpose machine if the application is designated as critical or high availability by the ISSO. Critical applications should not be hosted on a multi-purpose server with other applications. Applications that share resources are susceptible to the other shared application security defects. Even if the critical application is designed and deployed sec
    SV-84973r1_rule APSC-DV-003050 CCI-000445 MEDIUM A disaster recovery/continuity plan must exist in accordance with DoD policy based on the applications availability requirements. All applications must document disaster recovery/continuity procedures to include business recovery plans, system contingency plans, facility disaster recovery plans, and plan acceptance.
    SV-84975r1_rule APSC-DV-003060 CCI-000448 MEDIUM Recovery procedures and technical system features must exist so recovery is performed in a secure and verifiable manner. The ISSO will document circumstances inhibiting a trusted recovery. Without a disaster recovery plan, the application is susceptible to interruption in service due to damage within the processing site. If the application is part of the site’s disaster recovery plan, ensure that the plan contains detailed instructions p
    SV-84977r1_rule APSC-DV-003070 CCI-000537 MEDIUM Data backup must be performed at required intervals in accordance with DoD policy. Without proper backups, the application is not protected from the loss of data or the operating environment in the event of hardware or software failure.
    SV-84979r1_rule APSC-DV-003080 CCI-000540 MEDIUM Back-up copies of the application software or source code must be stored in a fire-rated container or stored separately (offsite). Application developers and application administrators must take steps to ensure continuity of development effort and operations should a disaster strike. Steps include protecting back-up copies of development code and application software. Improper st
    SV-84981r1_rule APSC-DV-003090 CCI-000540 MEDIUM Procedures must be in place to assure the appropriate physical and technical protection of the backup and restoration of the application. Protection of backup and restoration assets is essential for the successful restore of operations after a catastrophic failure or damage to the system or data files. Failure to follow proper procedures may result in the permanent loss of system data and/o
    SV-84983r1_rule APSC-DV-003100 CCI-000201 MEDIUM The application must use encryption to implement key exchange and authenticate endpoints prior to establishing a communication channel for key exchange. If the application does not use encryption and authenticate endpoints prior to establishing a communication channel and prior to transmitting encryption keys, these keys may be intercepted, and could be used to decrypt the traffic of the current session,
    SV-84985r1_rule APSC-DV-003110 CCI-002367 HIGH The application must not contain embedded authentication data. Authentication data stored in code could potentially be read and used by anonymous users to gain access to a backend database or application servers. This could lead to compromise of application data.
    SV-84987r1_rule APSC-DV-003120 CCI-001010 HIGH The application must have the capability to mark sensitive/classified output when required. Failure to properly mark output could result in a disclosure of sensitive or classified data which is an immediate loss in confidentiality.
    SV-84989r1_rule APSC-DV-003130 CCI-003004 LOW Prior to each release of the application, updates to system, or applying patches; tests plans and procedures must be created and executed. Without test plans and procedures for application releases or updates, unexpected results may occur which could lead to a denial of service to the application or components. This requirement is meant to apply to developers or organizations that are doing
    SV-84991r2_rule APSC-DV-003140 CCI-000698 MEDIUM Application files must be cryptographically hashed prior to deploying to DoD operational networks. When application code and binaries are transferred from one environment to another, there is the potential for malware to be introduced into either the application code or even the application binaries themselves. Care must be taken to ensure that applica
    SV-84993r1_rule APSC-DV-003150 CCI-003182 MEDIUM At least one tester must be designated to test for security flaws in addition to functional testing. If there is no person designated to test for security flaws, vulnerabilities can potentially be missed during testing. This requirement is meant to apply to developers or organizations that are doing development work.
    SV-84995r1_rule APSC-DV-003160 CCI-003182 LOW Test procedures must be created and at least annually executed to ensure system initialization, shutdown, and aborts are configured to verify the system remains in a secure state. Secure state assurance cannot be accomplished without testing the system state at least annually to ensure the system remains in a secure state upon initialization, shutdown, and aborts.
    SV-84997r1_rule APSC-DV-003170 CCI-003187 MEDIUM An application code review must be performed on the application. A code review is a systematic evaluation of computer source code conducted for the purposes of identifying and remediating the security flaws in the software. This requirement is meant to apply to developers or organizations that are doing application de
    SV-84999r1_rule APSC-DV-003180 CCI-003188 LOW Code coverage statistics must be maintained for each release of the application. This requirement is meant to apply to developers or organizations that are doing application development work. Code coverage statistics describes the overall functionality provided by the application and how much of the source code has been tested during
    SV-85001r1_rule APSC-DV-003190 CCI-003197 MEDIUM Flaws found during a code review must be tracked in a defect tracking system. This requirement is meant to apply to developers or organizations that are doing application development work. If flaws are not tracked they may possibly be forgotten to be included in a release. Tracking flaws in the configuration management repository
    SV-85003r1_rule APSC-DV-003200 CCI-003173 MEDIUM The changes to the application must be assessed for IA and accreditation impact prior to implementation. When changes are made to an application, either in the code or in the configuration of underlying components such as the OS or the web or application server, there is the potential for security vulnerabilities to be opened up on the system. IA assessment
    SV-85005r1_rule APSC-DV-003210 CCI-003178 MEDIUM Security flaws must be fixed or addressed in the project plan. This requirement is meant to apply to developers or organizations that are doing application development work. Application development efforts include the creation of a project plan to track and organize the development work. If security flaws are not t
    SV-85007r1_rule APSC-DV-003215 CCI-003233 LOW The application development team must follow a set of coding standards. Coding standards are guidelines established by the development team or individual developers that recommend programming style, practices and methods. The coding standards employed will vary based upon the programming language that is being used to develo
    SV-85009r1_rule APSC-DV-003220 CCI-003233 LOW The designer must create and update the Design Document for each release of the application. This requirement is meant to apply to developers or organizations that are doing application development work. The application design document or configuration guide includes configuration settings, recommendations and best practices that pertain to the
    SV-85011r1_rule APSC-DV-003230 CCI-003256 MEDIUM Threat models must be documented and reviewed for each application release and updated as required by design and functionality changes or when new threats are discovered. Threat modeling is an approach for analyzing the security of an application. It is a structured approach that enables you to identify, quantify, and address the security risks associated with an application. Threat modeling is not an approach to reviewing
    SV-85013r1_rule APSC-DV-003235 CCI-003272 MEDIUM The application must not be subject to error handling vulnerabilities. Error handling is the failure to check the return values of functions or catch top level exceptions within a program. Improper error handling in an application can lead to an application failure or possibly result in the application entering an insecure s
    SV-85015r1_rule APSC-DV-003236 CCI-003289 MEDIUM The application development team must provide an application incident response plan. An application incident response process is managed by the development team and should include a method for individuals to submit potential security vulnerabilities to the development or maintenance team. The plan should dictate what is to be done with
    SV-85017r2_rule APSC-DV-003240 CCI-003376 HIGH All products must be supported by the vendor or the development team. Unsupported commercial and government developed software products should not be used because fixes to newly identified bugs will not be implemented by the vendor or development team. The lack of security updates can result in potential vulnerabilities.
    SV-85019r1_rule APSC-DV-003250 CCI-003376 HIGH The application must be decommissioned when maintenance or support is no longer available. Unsupported software products should not be used because fixes to newly identified bugs will not be implemented by the vendor or development team. The lack of security updates can result in potential vulnerabilities. When maintenance updates and patches
    SV-85021r1_rule APSC-DV-003260 CCI-003374 LOW Procedures must be in place to notify users when an application is decommissioned. When maintenance no longer exists for an application, there are no individuals responsible for making security updates. The application support staff should maintain procedures for decommissioning. The decommissioning process should include notifying user
    SV-85023r1_rule APSC-DV-003270 CCI-003109 MEDIUM Unnecessary built-in application accounts must be disabled. Default passwords and properties of built-in accounts are often publicly available. Anyone with necessary knowledge, internal or external, can compromise an application using built-in accounts. Built-in accounts are those that are added as part of the in
    SV-85025r1_rule APSC-DV-003280 CCI-003109 HIGH Default passwords must be changed. Default passwords can easily be compromised by attackers allowing immediate access to the applications.
    SV-85027r1_rule APSC-DV-003285 CCI-003124 MEDIUM An Application Configuration Guide must be created and included with the application. The Application Configuration Guide is any document or collection of documents used to configure the application. These documents may be part of a user guide, secure configuration guide, or any guidance that satisfies the requirements provided herein.
    SV-85029r1_rule APSC-DV-003290 CCI-003124 MEDIUM If the application contains classified data, a Security Classification Guide must exist containing data elements and their classification. Without a classification guide the marking, storage, and output media of classified material can be inadvertently mixed with unclassified material, leading to its possible loss or compromise.
    SV-85031r2_rule APSC-DV-003300 CCI-001167 MEDIUM The designer must ensure uncategorized or emerging mobile code is not used in applications. By definition, mobile code is software obtained from remote systems outside the enclave boundary, transferred across a network, and then downloaded and executed on a local system without explicit installation or execution by the recipient. For a comple
    SV-85033r1_rule APSC-DV-003310 CCI-002478 MEDIUM Production database exports must have database administration credentials and sensitive data removed before releasing the export. Production database exports are often used to populate development databases. Test and development environments do not typically have the same rigid security protections that production environments do. When production data is used in test and development
    SV-85035r1_rule APSC-DV-003320 CCI-002386 MEDIUM Protections against DoS attacks must be implemented. Known DoS threats documented in the threat model should be mitigated, to prevent DoS type attacks.
    SV-85037r2_rule APSC-DV-003330 CCI-001274 MEDIUM The system must alert an administrator when low resource conditions are encountered. In order to prevent DoS type attacks, applications should be monitored when resource conditions reach a predefined threshold. This could indicate the onset of a DoS attack or could be the precursor to an application outage.
    SV-85039r1_rule APSC-DV-003340 CCI-001285 LOW At least one application administrator must be registered to receive update notifications, or security alerts, when automated alerts are available. Administrators should register for updates to all COTS and custom-developed software, so when security flaws are identified, they can be tracked for testing and updates of the application can be applied. Admin personnel should be registered to receive up
    SV-85041r1_rule APSC-DV-003345 CCI-001286 LOW The application must provide notifications or alerts when product update and security related patches are available. An application vulnerability management and update process must be in place to notify and provide users and administrators with a means of obtaining security patches and updates for the application. An important part of the maintenance phase of an applic
    SV-85043r1_rule APSC-DV-003350 CCI-001119 MEDIUM Connections between the DoD enclave and the Internet or other public or commercial wide area networks must require a DMZ. In order to protect DoD data and systems, all remote access to DoD information systems must be mediated through a managed access control point, such as a remote access server in a DMZ.
    SV-85045r1_rule APSC-DV-003360 CCI-000172 LOW The application must generate audit records when concurrent logons from different workstations occur. When an application provides users with the ability to concurrently logon, an event must be recorded that indicates the user has logged on from different workstations. It is important to ensure that audit logs differentiate between the two sessions. The
    SV-85047r2_rule APSC-DV-003400 CCI-002052 MEDIUM The Program Manager must verify all levels of program management, designers, developers, and testers receive annual security training pertaining to their job function. Many application team members may not be aware of the security implications regarding the code that they design, write and test. To address this concern, the Program Manager will ensure all levels of program management receive security training regarding