Application Security and Development Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
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.
<VulnDiscussion>Without a disaster recovery plan, the application is susceptible to interruption in service due to damage within the processi...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Data backup must be performed at required intervals in accordance with DoD policy.
<VulnDiscussion>Without proper backups, the application is not protected from the loss of data or the operating environment in the event of h...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Back-up copies of the application software or source code must be stored in a fire-rated container or stored separately (offsite).
<VulnDiscussion>Application developers and application administrators must take steps to ensure continuity of development effort and operatio...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Procedures must be in place to assure the appropriate physical and technical protection of the backup and restoration of the application.
<VulnDiscussion>Protection of backup and restoration assets is essential for the successful restore of operations after a catastrophic failur...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The application must use encryption to implement key exchange and authenticate endpoints prior to establishing a communication channel for key exchange.
<VulnDiscussion>If the application does not use encryption and authenticate endpoints prior to establishing a communication channel and prior...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The application must not contain embedded authentication data.
<VulnDiscussion>Authentication data stored in code could potentially be read and used by anonymous users to gain access to a backend database...Rule High Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The application must have the capability to mark sensitive/classified output when required.
<VulnDiscussion>Failure to properly mark output could result in a disclosure of sensitive or classified data which is an immediate loss in co...Rule High Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Prior to each release of the application, updates to system, or applying patches; tests plans and procedures must be created and executed.
<VulnDiscussion>Without test plans and procedures for application releases or updates, unexpected results may occur which could lead to a den...Rule Low Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Application files must be cryptographically hashed prior to deploying to DoD operational networks.
<VulnDiscussion>When application code and binaries are transferred from one environment to another, there is the potential for malware to be ...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
At least one tester must be designated to test for security flaws in addition to functional testing.
<VulnDiscussion>If there is no person designated to test for security flaws, vulnerabilities can potentially be missed during testing. This ...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
An application code review must be performed on the application.
<VulnDiscussion>A code review is a systematic evaluation of computer source code conducted for the purposes of identifying and remediating th...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Code coverage statistics must be maintained for each release of the application.
<VulnDiscussion>This requirement is meant to apply to developers or organizations that are doing application development work. Code coverage...Rule Low Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Flaws found during a code review must be tracked in a defect tracking system.
<VulnDiscussion>This requirement is meant to apply to developers or organizations that are doing application development work. If flaws are ...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The changes to the application must be assessed for IA and accreditation impact prior to implementation.
<VulnDiscussion>When changes are made to an application, either in the code or in the configuration of underlying components such as the OS o...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Security flaws must be fixed or addressed in the project plan.
<VulnDiscussion>This requirement is meant to apply to developers or organizations that are doing application development work. Application d...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The application development team must follow a set of coding standards.
<VulnDiscussion>Coding standards are guidelines established by the development team or individual developers that recommend programming style...Rule Low Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The designer must create and update the Design Document for each release of the application.
<VulnDiscussion>This requirement is meant to apply to developers or organizations that are doing application development work. The applicati...Rule Low Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Threat modeling is an approach for analyzing the security of an application. It is a structured approach that enables you to ...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The application must not be subject to error handling vulnerabilities.
<VulnDiscussion>Error handling is the failure to check the return values of functions or catch top level exceptions within a program. Imprope...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The system must alert an administrator when low resource conditions are encountered.
<VulnDiscussion>In order to prevent DoS type attacks, applications should be monitored when resource conditions reach a predefined threshold....Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The application development team must provide an application incident response plan.
<VulnDiscussion>An application incident response process is managed by the development team and should include a method for individuals to su...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
All products must be supported by the vendor or the development team.
<VulnDiscussion>Unsupported commercial and government developed software products should not be used because fixes to newly identified bugs w...Rule High Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The application must be decommissioned when maintenance or support is no longer available.
<VulnDiscussion>Unsupported software products should not be used because fixes to newly identified bugs will not be implemented by the vendor...Rule High Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Procedures must be in place to notify users when an application is decommissioned.
<VulnDiscussion>When maintenance no longer exists for an application, there are no individuals responsible for making security updates. The a...Rule Low Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
Unnecessary built-in application accounts must be disabled.
<VulnDiscussion>Default passwords and properties of built-in accounts are often publicly available. Anyone with necessary knowledge, internal...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.