Application Security and Development Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-APP-000220
<GroupDescription></GroupDescription>Group -
Applications must use system-generated session identifiers that protect against session fixation.
<VulnDiscussion>Session fixation allows an attacker to hijack a valid user’s application session. The attack focuses on the manner in which a...Rule Medium Severity -
SRG-APP-000223
<GroupDescription></GroupDescription>Group -
Applications must validate session identifiers.
<VulnDiscussion>Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever poss...Rule Medium Severity -
SRG-APP-000223
<GroupDescription></GroupDescription>Group -
Applications must not use URL embedded session IDs.
<VulnDiscussion>Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever poss...Rule Medium Severity -
SRG-APP-000223
<GroupDescription></GroupDescription>Group -
The application must not re-use or recycle session IDs.
<VulnDiscussion>Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever poss...Rule Medium Severity -
SRG-APP-000224
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generatio...Rule Medium Severity -
SRG-APP-000427
<GroupDescription></GroupDescription>Group -
The application must only allow the use of DoD-approved certificate authorities for verification of the establishment of protected sessions.
<VulnDiscussion>Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that se...Rule Medium Severity -
SRG-APP-000225
<GroupDescription></GroupDescription>Group -
The application must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
<VulnDiscussion>Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized acces...Rule High Severity -
SRG-APP-000226
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Fa...Rule Medium Severity -
SRG-APP-000231
<GroupDescription></GroupDescription>Group -
The application must protect the confidentiality and integrity of stored information when required by DoD policy or the information owner.
<VulnDiscussion>Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and...Rule Medium Severity -
SRG-APP-000428
<GroupDescription></GroupDescription>Group -
The application must implement approved cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest on organization-defined information system components.
<VulnDiscussion>Applications handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized ...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.