Application Security and Development Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
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 b...Rule Medium Severity -
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 ...Rule Medium Severity -
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 proced...Rule Medium Severity -
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 bina...Rule Medium Severity -
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. ...Rule Medium Severity -
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 ap...Rule Medium Severity -
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 potenti...Rule High Severity -
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....Rule Low Severity -
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 gu...Rule Medium Severity -
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 i...Rule Medium Severity
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.