UCF STIG Viewer Logo

vRealize - Cassandra Security Technical Implementation Guide


Overview

Date Finding Count (56)
2017-06-06 CAT I (High): 7 CAT II (Med): 48 CAT III (Low): 1
STIG Description
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 email to the following address: disa.stig_spt@mail.mil.

Available Profiles



Findings (MAC II - Mission Support Classified)

Finding ID Severity Title
V-72659 High The Cassandra database must enforce the DoD standards for password complexity and lifetime.
V-72665 High The Cassandra Server must protect the confidentiality and integrity of all information at rest.
V-72687 High The Cassandra Server must implement cryptographic mechanisms preventing the unauthorized disclosure of information at rest.
V-72657 High The Cassandra Server must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
V-72663 High The Cassandra Server must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
V-72621 High The Cassandra database must have the correct authorizer value.
V-72691 High Security-relevant software updates to the Cassandra Server must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).
V-72639 Medium The Cassandra database logs must have the correct owner.
V-72677 Medium The Cassandra Server must generate time stamps, for audit records and application data, with a minimum granularity of one second.
V-72671 Medium The Cassandra Server must reveal detailed error messages only to the ISSO, ISSM, SA, and DBA.
V-72631 Medium The Cassandra database must initiate session auditing upon startup.
V-72655 Medium The Cassandra Server must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.
V-72635 Medium The Cassandra database must produce audit records containing time stamps to establish when the events occurred.
V-72637 Medium The Cassandra database logs must be protected from unauthorized read access.
V-72675 Medium The Cassandra Server must record time stamps, in audit records and application data that can be mapped to Coordinated Universal Time (UTC, formerly GMT).
V-72645 Medium The Cassandra database log configuration file must have the correct group-owner.
V-72725 Medium The Cassandra Server must generate audit records when unsuccessful accesses to objects occur.
V-72689 Medium When invalid inputs are received, the Cassandra Server must behave in a predictable and documented manner that reflects organizational and system objectives.
V-72647 Medium The Cassandra software, including configuration files, must be stored in dedicated directories, or direct-access storage device (DASD) pools, separate from the host OS and other applications.
V-72721 Medium The Cassandra Server must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.
V-72673 Medium The Cassandra Server must utilize centralized management of the content captured in audit records generated by all components of the system.
V-72681 Medium The Cassandra Server must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.
V-72623 Medium The Cassandra database must provide audit record generation capability for DoD-defined auditable events within all database components.
V-72709 Medium The Cassandra Server must generate audit records when privileges/permissions are deleted.
V-72705 Medium The Cassandra Server must generate audit records when security objects are modified.
V-72707 Medium The Cassandra Server must generate audit records when unsuccessful attempts to modify security objects occur.
V-72701 Medium The Cassandra Server must generate audit records when privileges/permissions are modified.
V-72703 Medium The Cassandra Server must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
V-72641 Medium The Cassandra database log configuration file must be protected from unauthorized read access.
V-72643 Medium The Cassandra database log configuration file must have the correct owner.
V-72633 Medium The Cassandra database must produce audit records containing sufficient information to establish what type of events occurred.
V-72661 Medium The Cassandra database log configuration file must set internode encryption.
V-72649 Medium Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by database/DBMS principals authorized for ownership.
V-72679 Medium The Cassandra database must protect the truststore file.
V-72627 Medium The Cassandra database must be able to generate audit records when privileges/permissions are retrieved.
V-72625 Medium The Cassandra database must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
V-72653 Medium Unused Cassandra database components, software, and database objects must be removed.
V-72669 Medium Access to database files must be limited to relevant processes and to authorized, administrative users.
V-72651 Medium The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be restricted to authorized users.
V-72715 Medium The Cassandra Server must generate audit records when unsuccessful attempts to delete security objects occur.
V-72723 Medium The Cassandra Server must be able to generate audit records when successful accesses to objects occur.
V-72667 Medium The Cassandra Server must isolate security functions from non-security functions.
V-72751 Medium The Cassandra database logs must have the correct group-owner.
V-72699 Medium The Cassandra Server must generate audit records when unsuccessful attempts to add privileges/permissions occur.
V-72629 Medium The Cassandra database must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
V-72713 Medium The Cassandra Server must generate audit records when security objects are deleted.
V-72693 Medium The Cassandra Server must be able to generate audit records when security objects are accessed.
V-72697 Medium The Cassandra Server must generate audit records when privileges/permissions are added.
V-72695 Medium The Cassandra Server must generate audit records when unsuccessful attempts to access security objects occur.
V-72617 Medium The Cassandra database must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
V-72719 Medium The Cassandra Server must generate audit records for all privileged activities or other system-level access.
V-72717 Medium The Cassandra Server must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.
V-72733 Medium The Cassandra Server must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.
V-72619 Medium The Cassandra database must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
V-72711 Medium The Cassandra Server must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
V-72735 Low The DBMS must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs.