Application Security and Development Security Technical Implementation Guide

Version: 6

Updated: 26 Nov 2025

Findings: 286

Findings

V-222387 - The application must provide a capability to limit the number of logon sessions per user. (medium)
V-222388 - The application must clear temporary storage and cookies when the session is terminated. (medium)
V-222389 - 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. (medium)
V-222390 - The application must automatically terminate the admin user session and log off admin users after a 10 minute idle time period is exceeded. (medium)
V-222391 - Applications requiring user access authentication must provide a logoff capability for user initiated communication session. (medium)
V-222392 - The application must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions. (low)
V-222393 - The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in storage. (medium)
V-222394 - The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in process. (medium)
V-222395 - The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission. (medium)
V-222396 - The application must implement DoD-approved encryption to protect the confidentiality of remote access sessions. (medium)
V-222397 - The application must implement cryptographic mechanisms to protect the integrity of remote access sessions. (medium)
V-222398 - 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. (medium)
V-222399 - Messages protected with WS_Security must use time stamps with creation and expiration times. (high)
V-222400 - Validity periods must be verified on all application messages using WS-Security or SAML assertions. (high)
V-222401 - The application must ensure each unique asserting party provides unique assertion ID references for each SAML assertion. (medium)
V-222402 - 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. (medium)
V-222403 - The application must use the NotOnOrAfter condition when using the SubjectConfirmation element in a SAML assertion. (high)
V-222404 - The application must use both the NotBefore and NotOnOrAfter elements or OneTimeUse element when using the Conditions element in a SAML assertion. (high)
V-222405 - 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. (medium)
V-222406 - The application must ensure messages are encrypted when the SessionIndex is tied to privacy data. (medium)
V-222407 - The application must provide automated mechanisms for supporting account management functions. (medium)
V-222408 - Shared/group account credentials must be terminated when members leave the group. (medium)
V-222409 - The application must automatically remove or disable temporary user accounts 72 hours after account creation. (medium)
V-222410 - The application must have a process, feature or function that prevents removal or disabling of emergency accounts. (low)
V-222411 - The application must automatically disable accounts after a 35 day period of account inactivity. (low)
V-222412 - Unnecessary application accounts must be disabled, or deleted. (medium)
V-222413 - The application must automatically audit account creation. (medium)
V-222414 - The application must automatically audit account modification. (medium)
V-222415 - The application must automatically audit account disabling actions. (medium)
V-222416 - The application must automatically audit account removal actions. (medium)
V-222417 - The application must notify system administrators (SAs) and information system security officers (ISSOs) when accounts are created. (low)
V-222418 - The application must notify system administrators (SAs) and information system security officers (ISSOs) when accounts are modified. (low)
V-222419 - The application must notify system administrators (SAs) and information system security officers (ISSOs) of account disabling actions. (low)
V-222420 - The application must notify system administrators (SAs) and information system security officers (ISSOs) of account removal actions. (low)
V-222421 - The application must automatically audit account enabling actions. (medium)
V-222422 - The application must notify system administrators (SAs) and information system security officers (ISSOs) of account enabling actions. (low)
V-222423 - Application data protection requirements must be identified and documented. (medium)
V-222424 - The application must utilize organization-defined data mining detection techniques for organization-defined data storage objects to adequately detect data mining attempts. (medium)
V-222425 - The application must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. (high)
V-222426 - The application must enforce organization-defined discretionary access control policies over defined subjects and objects. (medium)
V-222427 - The application must enforce approved authorizations for controlling the flow of information within the system based on organization-defined information flow control policies. (medium)
V-222428 - The application must enforce approved authorizations for controlling the flow of information between interconnected systems based on organization-defined information flow control policies. (medium)
V-222429 - The application must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. (medium)
V-222430 - The application must execute without excessive account permissions. (high)
V-222431 - The application must audit the execution of privileged functions. (medium)
V-222432 - The application must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period. (high)
V-222433 - The application administrator must follow an approved process to unlock locked user accounts. (medium)
V-222434 - The application must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application. (low)
V-222435 - 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. (low)
V-222436 - The publicly accessible application must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application. (low)
V-222437 - The application must display the time and date of the users last successful logon. (low)
V-222438 - 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. (medium)
V-222439 - 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. (medium)
V-222441 - The application must provide audit record generation capability for the creation of session IDs. (medium)
V-222442 - The application must provide audit record generation capability for the destruction of session IDs. (medium)
V-222443 - The application must provide audit record generation capability for the renewal of session IDs. (medium)
V-222444 - The application must not write sensitive data into the application logs. (medium)
V-222445 - The application must provide audit record generation capability for session timeouts. (medium)
V-222446 - The application must record a time stamp indicating when the event occurred. (medium)
V-222447 - The application must provide audit record generation capability for HTTP headers including User-Agent, Referer, GET, and POST. (medium)
V-222448 - The application must provide audit record generation capability for connecting system IP addresses. (medium)
V-222449 - The application must record the username or user ID of the user associated with the event. (medium)
V-222450 - The application must generate audit records when successful/unsuccessful attempts to grant privileges occur. (medium)
V-222451 - The application must generate audit records when successful/unsuccessful attempts to access security objects occur. (medium)
V-222452 - The application must generate audit records when successful/unsuccessful attempts to access security levels occur. (medium)
V-222453 - The application must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. (medium)
V-222454 - The application must generate audit records when successful/unsuccessful attempts to modify privileges occur. (medium)
V-222455 - The application must generate audit records when successful/unsuccessful attempts to modify security objects occur. (medium)
V-222456 - The application must generate audit records when successful/unsuccessful attempts to modify security levels occur. (medium)
V-222457 - The application must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. (medium)
V-222458 - The application must generate audit records when successful/unsuccessful attempts to delete privileges occur. (medium)
V-222459 - The application must generate audit records when successful/unsuccessful attempts to delete security levels occur. (medium)
V-222460 - The application must generate audit records when successful/unsuccessful attempts to delete application database security objects occur. (medium)
V-222461 - The application must generate audit records when successful/unsuccessful attempts to delete categories of information (e.g., classification levels) occur. (medium)
V-222462 - The application must generate audit records when successful/unsuccessful logon attempts occur. (medium)
V-222463 - The application must generate audit records for privileged activities or other system-level access. (medium)
V-222464 - The application must generate audit records showing starting and ending time for user access to the system. (medium)
V-222465 - The application must generate audit records when successful/unsuccessful accesses to objects occur. (medium)
V-222466 - The application must generate audit records for all direct access to the information system. (medium)
V-222467 - The application must generate audit records for all account creations, modifications, disabling, and termination events. (medium)
V-222468 - The application must initiate session auditing upon startup. (medium)
V-222469 - The application must log application shutdown events. (medium)
V-222470 - The application must log destination IP addresses. (medium)
V-222471 - The application must log user actions involving access to data. (medium)
V-222472 - The application must log user actions involving changes to data. (medium)
V-222473 - The application must produce audit records containing information to establish when (date and time) the events occurred. (medium)
V-222474 - The application must produce audit records containing enough information to establish which component, feature or function of the application triggered the audit event. (medium)
V-222475 - When using centralized logging; the application must include a unique identifier in order to distinguish itself from other application logs. (medium)
V-222476 - The application must produce audit records that contain information to establish the outcome of the events. (medium)
V-222477 - The application must generate audit records containing information that establishes the identity of any individual or process associated with the event. (medium)
V-222478 - The application must generate audit records containing the full-text recording of privileged commands or the individual identities of group account users. (medium)
V-222479 - The application must implement transaction recovery logs when transaction based. (medium)
V-222480 - The application must provide centralized management and configuration of the content to be captured in audit records generated by all application components. (medium)
V-222481 - The application must off-load audit records onto a different system or media than the system being audited. (medium)
V-222482 - The application must be configured to write application logs to a centralized log repository. (medium)
V-222483 - 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. (medium)
V-222484 - 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. (medium)
V-222485 - The application must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. (medium)
V-222486 - The application must shut down by default upon audit failure (unless availability is an overriding concern). (medium)
V-222487 - The application must provide the capability to centrally review and analyze audit records from multiple components within the system. (medium)
V-222488 - The application must provide the capability to filter audit records for events of interest based upon organization-defined criteria. (medium)
V-222489 - The application must provide an audit reduction capability that supports on-demand reporting requirements. (medium)
V-222490 - The application must provide an audit reduction capability that supports on-demand audit review and analysis. (medium)
V-222491 - The application must provide an audit reduction capability that supports after-the-fact investigations of security incidents. (medium)
V-222492 - The application must provide a report generation capability that supports on-demand audit review and analysis. (medium)
V-222493 - The application must provide a report generation capability that supports on-demand reporting requirements. (medium)
V-222494 - The application must provide a report generation capability that supports after-the-fact investigations of security incidents. (medium)
V-222495 - The application must provide an audit reduction capability that does not alter original content or time ordering of audit records. (medium)
V-222496 - The application must provide a report generation capability that does not alter original content or time ordering of audit records. (medium)
V-222497 - The applications must use internal system clocks to generate time stamps for audit records. (medium)
V-222498 - The application must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). (medium)
V-222499 - The application must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision. (medium)
V-222500 - The application must protect audit information from any type of unauthorized read access. (medium)
V-222501 - The application must protect audit information from unauthorized modification. (medium)
V-222502 - The application must protect audit information from unauthorized deletion. (medium)
V-222503 - The application must protect audit tools from unauthorized access. (medium)
V-222504 - The application must protect audit tools from unauthorized modification. (medium)
V-222505 - The application must protect audit tools from unauthorized deletion. (medium)
V-222506 - 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. (medium)
V-222507 - The application must use cryptographic mechanisms to protect the integrity of audit information. (medium)
V-222508 - Application audit tools must be cryptographically hashed. (medium)
V-222509 - The integrity of the audit tools must be validated by checking the files for changes in the cryptographic hash value. (medium)
V-222510 - The application must prohibit user installation of software without explicit privileged status. (medium)
V-222511 - The application must enforce access restrictions associated with changes to application configuration. (medium)
V-222512 - The application must audit who makes configuration changes to the application. (medium)
V-222513 - 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. (medium)
V-222514 - The applications must limit privileges to change the software resident within software libraries. (medium)
V-222515 - An application vulnerability assessment must be conducted. (medium)
V-222516 - 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. (medium)
V-222517 - The application must employ a deny-all, permit-by-exception (whitelist) policy to allow the execution of authorized software programs. (medium)
V-222518 - The application must be configured to disable non-essential capabilities. (medium)
V-222519 - The application must be configured to use only functions, ports, and protocols permitted to it in the PPSM CAL. (medium)
V-222520 - The application must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. (medium)
V-222521 - The application must require devices to reauthenticate when organization-defined circumstances or situations requiring reauthentication. (medium)
V-222522 - The application must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). (high)
V-222523 - The application must use multifactor (Alt. Token) authentication for network access to privileged accounts. (medium)
V-222524 - The application must accept Personal Identity Verification (PIV) credentials. (medium)
V-222525 - The application must electronically verify Personal Identity Verification (PIV) credentials. (medium)
V-222526 - The application must use multifactor (e.g., CAC, Alt. Token) authentication for network access to non-privileged accounts. (medium)
V-222527 - The application must use multifactor (Alt. Token) authentication for local access to privileged accounts. (medium)
V-222528 - The application must use multifactor (e.g., CAC, Alt. Token) authentication for local access to nonprivileged accounts. (medium)
V-222529 - The application must ensure users are authenticated with an individual authenticator prior to using a group authenticator. (medium)
V-222530 - The application must implement replay-resistant authentication mechanisms for network access to privileged accounts. (medium)
V-222531 - The application must implement replay-resistant authentication mechanisms for network access to nonprivileged accounts. (medium)
V-222532 - The application must utilize mutual authentication when endpoint device non-repudiation protections are required by DoD policy or by the data owner. (medium)
V-222533 - The application must authenticate all network connected endpoint devices before establishing any connection. (medium)
V-222534 - Service-Oriented Applications handling non-releasable data must authenticate endpoint devices via mutual SSL/TLS. (medium)
V-222535 - The application must disable device identifiers after 35 days of inactivity unless a cryptographic certificate is used for authentication. (medium)
V-222536 - The application must enforce a minimum 15-character password length. (high)
V-222537 - The application must enforce password complexity by requiring that at least one uppercase character be used. (medium)
V-222538 - The application must enforce password complexity by requiring that at least one lowercase character be used. (medium)
V-222539 - The application must enforce password complexity by requiring that at least one numeric character be used. (medium)
V-222540 - The application must enforce password complexity by requiring that at least one special character be used. (medium)
V-222541 - The application must require the change of at least eight of the total number of characters when passwords are changed. (medium)
V-222542 - The application must only store cryptographic representations of passwords. (high)
V-222543 - The application must transmit only cryptographically-protected passwords. (high)
V-222544 - The application must enforce 24 hours/1 day as the minimum password lifetime. (medium)
V-222545 - The application must enforce a 60-day maximum password lifetime restriction. (medium)
V-222546 - The application must prohibit password reuse for a minimum of five generations. (medium)
V-222547 - The application must allow the use of a temporary password for system logons with an immediate change to a permanent password. (medium)
V-222548 - The application password must not be changeable by users other than the administrator or the user with which the password is associated. (medium)
V-222549 - The application must terminate existing user sessions upon account deletion. (medium)
V-222550 - The application, when utilizing PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. (high)
V-222551 - The application, when using PKI-based authentication, must enforce authorized access to the corresponding private key. (high)
V-222552 - The application must map the authenticated identity to the individual user or group account for PKI-based authentication. (medium)
V-222553 - 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. (medium)
V-222554 - The application must not display passwords/PINs as clear text. (high)
V-222555 - 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. (high)
V-222556 - The application must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). (medium)
V-222557 - The application must accept Personal Identity Verification (PIV) credentials from other federal agencies. (medium)
V-222558 - The application must electronically verify Personal Identity Verification (PIV) credentials from other federal agencies. (medium)
V-222559 - The application must accept Federal Identity, Credential, and Access Management (FICAM)-approved third-party credentials. (medium)
V-222560 - The application must conform to Federal Identity, Credential, and Access Management (FICAM)-issued profiles. (medium)
V-222561 - Applications used for non-local maintenance sessions must audit non-local maintenance and diagnostic sessions for organization-defined auditable events. (medium)
V-222562 - Applications used for non-local maintenance sessions must implement cryptographic mechanisms to protect the integrity of non-local maintenance and diagnostic communications. (medium)
V-222563 - Applications used for non-local maintenance sessions must implement cryptographic mechanisms to protect the confidentiality of non-local maintenance and diagnostic communications. (medium)
V-222564 - Applications used for non-local maintenance sessions must verify remote disconnection at the termination of non-local maintenance and diagnostic sessions. (medium)
V-222565 - The application must employ strong authenticators in the establishment of non-local maintenance and diagnostic sessions. (medium)
V-222566 - The application must terminate all sessions and network connections when nonlocal maintenance is completed. (medium)
V-222567 - The application must not be vulnerable to race conditions. (medium)
V-222568 - The application must terminate all network connections associated with a communications session at the end of the session. (medium)
V-222570 - The application must utilize FIPS-validated cryptographic modules when signing application components. (medium)
V-222571 - The application must utilize FIPS-validated cryptographic modules when generating cryptographic hashes. (medium)
V-222572 - The application must utilize FIPS-validated cryptographic modules when protecting unclassified information that requires cryptographic protection. (medium)
V-222573 - Applications making SAML assertions must use FIPS-approved random numbers in the generation of SessionIndex in the SAML element AuthnStatement. (medium)
V-222574 - The application user interface must be either physically or logically separated from data storage and management interfaces. (medium)
V-222575 - The application must set the HTTPOnly flag on session cookies. (medium)
V-222576 - The application must set the secure flag on session cookies. (medium)
V-222577 - The application must not expose session IDs. (high)
V-222578 - The application must destroy the session ID value and/or cookie on logoff or browser close. (high)
V-222579 - Applications must use system-generated session identifiers that protect against session fixation. (medium)
V-222580 - Applications must validate session identifiers. (medium)
V-222581 - Applications must not use URL embedded session IDs. (medium)
V-222582 - The application must not re-use or recycle session IDs. (medium)
V-222583 - The application must generate a unique session identifier using a FIPS 140-2/140-3 approved random number generator. (medium)
V-222584 - The application must only allow the use of DoD-approved certificate authorities for verification of the establishment of protected sessions. (medium)
V-222585 - The application must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. (high)
V-222586 - 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. (medium)
V-222587 - The application must protect the confidentiality and integrity of stored information when required by DOD policy or the information owner. (medium)
V-222588 - The application must implement approved cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest on organization-defined information system components. (high)
V-222589 - The application must use appropriate cryptography in order to protect stored DOD information when required by the information owner or DOD policy. (high)
V-222590 - The application must isolate security functions from non-security functions. (medium)
V-222591 - The application must maintain a separate execution domain for each executing process. (medium)
V-222592 - Applications must prevent unauthorized and unintended information transfer via shared system resources. (medium)
V-222593 - XML-based applications must mitigate DoS attacks by using XML filters, parser options, or gateways. (medium)
V-222594 - The application must restrict the ability to launch Denial of Service (DoS) attacks against itself or other information systems. (medium)
V-222595 - The web service design must include redundancy mechanisms when used with high-availability systems. (medium)
V-222596 - The application must protect the confidentiality and integrity of transmitted information. (high)
V-222597 - 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). (medium)
V-222598 - The application must maintain the confidentiality and integrity of information during preparation for transmission. (medium)
V-222599 - The application must maintain the confidentiality and integrity of information during reception. (medium)
V-222600 - The application must not disclose unnecessary information to users. (medium)
V-222601 - The application must not store sensitive information in hidden fields. (high)
V-222602 - The application must protect from Cross-Site Scripting (XSS) vulnerabilities. (high)
V-222603 - The application must protect from Cross-Site Request Forgery (CSRF) vulnerabilities. (medium)
V-222604 - The application must protect from command injection. (high)
V-222605 - The application must protect from canonical representation vulnerabilities. (medium)
V-222606 - The application must validate all input. (medium)
V-222607 - The application must not be vulnerable to SQL Injection. (high)
V-222608 - The application must not be vulnerable to XML-oriented attacks. (high)
V-222609 - The application must not be subject to input handling vulnerabilities. (high)
V-222610 - The application must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. (medium)
V-222611 - The application must reveal error messages only to the ISSO, ISSM, or SA. (medium)
V-222612 - The application must not be vulnerable to overflow attacks. (high)
V-222613 - The application must remove organization-defined software components after updated versions have been installed. (medium)
V-222614 - Security-relevant software updates and patches must be kept up to date. (medium)
V-222615 - The application performing organization-defined security functions must verify correct operation of security functions. (medium)
V-222616 - 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. (medium)
V-222617 - The application must notify the ISSO and ISSM of failed security verification tests. (low)
V-222618 - Unsigned Category 1A mobile code must not be used in the application in accordance with DoD policy. (medium)
V-222619 - 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. (medium)
V-222620 - 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. (high)
V-222621 - The ISSO must ensure application audit trails are retained for at least 30 months (12 months active + 18 months cold storage) for applications without SAMI data and five years for applications including SAMI data. (medium)
V-222622 - The ISSO must review audit trails periodically based on system documentation recommendations or immediately upon system security events. (medium)
V-222623 - The ISSO must report all suspected violations of IA policies in accordance with DoD information system IA procedures. (medium)
V-222624 - The ISSO must ensure active vulnerability testing is performed. (medium)
V-222625 - Execution flow diagrams and design documents must be created to show how deadlock and recursion issues in web services are being mitigated. (medium)
V-222626 - The designer must ensure the application does not store configuration and control files in the same directory as user data. (medium)
V-222627 - 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. (medium)
V-222628 - 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) (medium)
V-222629 - The application must be registered with the DoD Ports and Protocols Database. (medium)
V-222630 - The Configuration Management (CM) repository must be properly patched and STIG compliant. (medium)
V-222631 - Access privileges to the Configuration Management (CM) repository must be reviewed every three months. (medium)
V-222632 - 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. (medium)
V-222633 - A Configuration Control Board (CCB) that meets at least every release cycle, for managing the Configuration Management (CM) process must be established. (medium)
V-222634 - The application services and interfaces must be compatible with and ready for IPv6 networks. (medium)
V-222635 - The application must not be hosted on a general purpose machine if the application is designated as critical or high availability by the ISSO. (medium)
V-222636 - A contingency plan must exist in accordance with DOD policy based on the application's availability requirements. (medium)
V-222637 - 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. (medium)
V-222638 - Data backup must be performed at required intervals in accordance with DoD policy. (medium)
V-222639 - Back-up copies of the application software or source code must be stored in a fire-rated container or stored separately (offsite). (medium)
V-222640 - Procedures must be in place to assure the appropriate physical and technical protection of the backup and restoration of the application. (medium)
V-222641 - The application must use encryption to implement key exchange and authenticate endpoints prior to establishing a communication channel for key exchange. (medium)
V-222642 - The application must not contain embedded authentication data. (high)
V-222643 - The application must have the capability to mark sensitive/classified output when required. (high)
V-222644 - Prior to each release of the application, updates to system, or applying patches; tests plans and procedures must be created and executed. (low)
V-222645 - Application files must be cryptographically hashed prior to deploying to DoD operational networks. (medium)
V-222646 - At least one tester must be designated to test for security flaws in addition to functional testing. (medium)
V-222647 - 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. (low)
V-222648 - An application code review must be performed on the application. (medium)
V-222649 - Code coverage statistics must be maintained for each release of the application. (low)
V-222650 - Flaws found during a code review must be tracked in a defect tracking system. (medium)
V-222651 - The changes to the application must be assessed for IA and accreditation impact prior to implementation. (medium)
V-222652 - Security flaws must be fixed or addressed in the project plan. (medium)
V-222653 - The application development team must follow a set of coding standards. (low)
V-222654 - The designer must create and update the Design Document for each release of the application. (low)
V-222655 - 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. (medium)
V-222656 - The application must not be subject to error handling vulnerabilities. (medium)
V-222657 - The application development team must provide an application incident response plan. (medium)
V-222658 - All products must be supported by the vendor or the development team. (high)
V-222659 - The application must be decommissioned when maintenance or support is no longer available. (high)
V-222660 - Procedures must be in place to notify users when an application is decommissioned. (low)
V-222661 - Unnecessary built-in application accounts must be disabled. (medium)
V-222662 - Default passwords must be changed. (high)
V-222663 - An Application Configuration Guide must be created and included with the application. (medium)
V-222664 - If the application contains classified data, a Security Classification Guide must exist containing data elements and their classification. (medium)
V-222665 - The designer must ensure uncategorized or emerging mobile code is not used in applications. (medium)
V-222666 - Production database exports must have database administration credentials and sensitive data removed before releasing the export. (medium)
V-222667 - Protections against DoS attacks must be implemented. (medium)
V-222668 - The system must alert an administrator when low resource conditions are encountered. (medium)
V-222669 - At least one application administrator must be registered to receive update notifications, or security alerts, when automated alerts are available. (low)
V-222670 - The application must provide notifications or alerts when product update and security related patches are available. (low)
V-222671 - Connections between the DoD enclave and the Internet or other public or commercial wide area networks must require a DMZ. (medium)
V-222672 - The application must generate audit records when concurrent logons from different workstations occur. (low)
V-222673 - The Program Manager must verify all levels of program management, designers, developers, and testers receive annual security training pertaining to their job function. (medium)
V-265634 - The application must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. (medium)