Detections
Analytics
DB2X-00-005100 - DB2 must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values
Information
One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known.The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2 approved random number generator.
However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking. Therefore, other techniques are acceptable, provided they are demonstrated to be effective.
Solution
Use the following commands to set the protocol and ports as per PPSM guidance:$db2 update dbm cfg using svcename [service_name | port_number]
$db2 update dbm cfg using ssl_svcename [ssl_service_name | port_number]
Note: http://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5.0/com.ibm.db2.luw.admin.sec.doc/doc/t0025241.html
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_IBM_DB2_V10-5_LUW_V2R1_STIG.zip
Item Details
Audit Name: DISA STIG IBM DB2 v10.5 LUW v2r1 OS Linux
Category: SYSTEM AND COMMUNICATIONS PROTECTION
References: 800-53|SC-23(3), CAT|II, CCI|CCI-001188, Rule-ID|SV-213704r879639_rule, STIG-ID|DB2X-00-005100, STIG-Legacy|SV-89171, STIG-Legacy|V-74497, Vuln-ID|V-213704
Plugin: Unix
Control ID: b18bc4e8cb9260d3e1451a8fcc8b19ccdac81c8aae6e993a4768d308ac305702