CIS SAP HANA 2.0 Benchmark

Secure configuration guidelines for SAP HANA 2.0 database platform

v1.0.0 May 2026

Overview

▶

This CIS Benchmark provides prescriptive guidance for establishing a secure configuration posture for SAP HANA 2.0. Recommendations cover installation hardening, SSL/TLS for internal and client communication, authentication and password policies, authorization, auditing, data-at-rest and backup encryption, root key management, and operational security.

~150Recommendations
5Sections
2Profile Levels
SectionAreaFocus
1InstallationVersion, network, SSL/TLS
2AuthPasswords, lockout, roles, privileges
3AuditingGlobal audit, policies, SYSLOG trail
4EncryptionData/log/backup encryption, keys
5OperationsFile perms, services, backups

Profile Definitions

▶
ProfileDescriptionIntended Use
L1Level 1 — StandardEssential security for all SAP HANA 2.0 deployments; minimal performance impact.
L2Level 2 — HardenedAdvanced hardening for PCI-DSS, HIPAA, or high-security environments.

1 — Installation & Network

▶

1.1 Installation

▶
1.1.1 Ensure Latest SAP HANA Revision Is Installed (Automated)
L1 Auto
Description

This recommendation verifies that Latest SAP HANA Revision Is Installed on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
HDB version
# Should show latest SPS + revision
# Alternative:
hdbsql -U SYSTEM -j "SELECT VERSION FROM M_DATABASE"
Remediation
# Apply latest SAP HANA revision:
# Download the latest revision from SAP Support Portal
# Run the resident hdblcm:
/hana/shared/<SID>/hdblcm/hdblcm --action=update --batch
1.1.2 Ensure Listen Interface Is Restricted (Automated)
L1 Auto
Description

This setting ensures that Listen Interface Is Restricted on the SAP HANA 2.0 in-memory database platform. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Rationale

Unrestricted access to this capability could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the SAP HANA 2.0 in-memory database platform is essential for defense in depth.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='communication' AND KEY='listeninterface'"
# Should return: .global or specific hostname, NOT 0.0.0.0
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('communication', 'listeninterface') = '.global' WITH RECONFIGURE"
1.1.3 Ensure SAP HANA OS Users Are Properly Configured (Manual)
L1 Manual
Description

This recommendation verifies that SAP HANA OS Users Are Properly Configured on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
grep -i 'sapadm\|<sid>adm' /etc/passwd
# Verify SAP HANA OS users exist and have correct groups
id <sid>adm
Remediation
# Ensure the <sid>adm user has restricted permissions:
usermod -s /bin/false sapadm
# Set strong password:
passwd <sid>adm

1.2 Network Security

▶
1.2.1 Ensure SSL Is Enabled for Client Communication (Automated)
L1 Auto
Description

This recommendation verifies that SSL Is Enabled for Client Communication on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='communication' AND KEY='ssl'"
# Should return: ssl = on
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('communication', 'ssl') = 'on' WITH RECONFIGURE"
1.2.2 Ensure SSL Certificate Validation Is Enabled (Automated)
L1 Auto
Description

This recommendation verifies that SSL Certificate Validation Is Enabled on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='communication' AND KEY='sslValidateCertificate'"
# Should return: true
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('communication', 'sslValidateCertificate') = 'true' WITH RECONFIGURE"
1.2.3 Ensure Strong Crypto Provider Is Configured (Automated)
L1 Auto
Description

This recommendation verifies that Strong Crypto Provider Is Configured on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='communication' AND KEY='sslCryptoProvider'"
# Should return: openssl or commoncrypto
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('communication', 'sslCryptoProvider') = 'openssl' WITH RECONFIGURE"

2 — Authentication & Authorization

▶

2.1 Authentication

▶
2.1.1 Ensure SYSTEM User Account Is Deactivated (Automated)
L1 Auto
Description

This recommendation verifies that SYSTEM User Account Is Deactivated on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT USER_NAME, IS_PASSWORD_ENABLED, IS_DEACTIVATED FROM SYS.USERS WHERE IS_PASSWORD_ENABLED='TRUE' AND USER_NAME='SYSTEM'"
Remediation
hdbsql -U SYSTEM -j "ALTER USER SYSTEM DEACTIVATE USER NOW"
# Or set a very strong password and restrict usage:
hdbsql -U SYSTEM -j "ALTER USER SYSTEM PASSWORD \"<StrongPassword>\" NO FORCE_FIRST_PASSWORD_CHANGE"
2.1.2 Ensure Minimum Password Length Is Set (Automated)
L1 Auto
Description

This recommendation verifies that Minimum Password Length Is Set on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='password policy' AND KEY='minimal_password_length'"
# Should be >= 8
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('password policy', 'minimal_password_length') = '14' WITH RECONFIGURE"
2.1.3 Ensure Password Lifetime Is Configured (Automated)
L1 Auto
Description

This recommendation verifies that Password Lifetime Is Configured on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='password policy' AND KEY='password_lifetime'"
# Should be <= 90
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('password policy', 'password_lifetime') = '90' WITH RECONFIGURE"
2.1.4 Ensure Account Lockout Threshold Is Set (Automated)
L1 Auto
Description

This recommendation verifies that Account Lockout Threshold Is Set on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='password policy' AND KEY='maximum_invalid_connect_attempts'"
# Should be <= 5
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('password policy', 'maximum_invalid_connect_attempts') = '5' WITH RECONFIGURE"
2.1.5 Ensure Password History Is Configured (Automated)
L1 Auto
Description

This recommendation verifies that Password History Is Configured on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='password policy' AND KEY='last_used_passwords'"
# Should be >= 5 (password history)
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('password policy', 'last_used_passwords') = '10' WITH RECONFIGURE"

2.2 Authorization

▶
2.2.1 Ensure PUBLIC Role Privileges Are Restricted (Automated)
L1 Auto
Description

This setting ensures that PUBLIC Role Privileges Are Restricted on the SAP HANA 2.0 in-memory database platform. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Rationale

Unrestricted access to this capability could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the SAP HANA 2.0 in-memory database platform is essential for defense in depth.

Audit
hdbsql -U SYSTEM -j "SELECT GRANTEE, PRIVILEGE, IS_GRANTABLE FROM SYS.GRANTED_PRIVILEGES WHERE GRANTEE='PUBLIC' ORDER BY PRIVILEGE"
Remediation
hdbsql -U SYSTEM -j "REVOKE CREATE ANY ON SCHEMA PUBLIC FROM PUBLIC"
hdbsql -U SYSTEM -j "REVOKE SELECT ON SCHEMA SYS FROM PUBLIC"
2.2.2 Ensure Powerful Roles Are Reviewed (Manual)
L1 Manual
Description

This recommendation verifies that Powerful Roles Are Reviewed on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT GRANTEE, GRANTEE_TYPE, ROLE_NAME FROM SYS.GRANTED_ROLES WHERE ROLE_NAME='CONTENT_ADMIN' OR ROLE_NAME='MODELING'"
# Review users with powerful roles
Remediation
hdbsql -U SYSTEM -j "REVOKE CONTENT_ADMIN FROM <user>"
# Grant least privilege roles instead:
hdbsql -U SYSTEM -j "GRANT <specific_role> TO <user>"
2.2.3 Ensure DATA ADMIN Privilege Is Restricted (Manual)
L1 Manual
Description

This setting ensures that DATA ADMIN Privilege Is Restricted on the SAP HANA 2.0 in-memory database platform. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Rationale

Unrestricted access to this capability could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the SAP HANA 2.0 in-memory database platform is essential for defense in depth.

Audit
hdbsql -U SYSTEM -j "SELECT GRANTEE, PRIVILEGE, IS_GRANTABLE FROM SYS.GRANTED_PRIVILEGES WHERE PRIVILEGE='DATA ADMIN' OR PRIVILEGE='CATALOG READ'"
# Review users with DATA ADMIN privilege
Remediation
# Remove DATA ADMIN where not required:
hdbsql -U SYSTEM -j "REVOKE DATA ADMIN FROM <user>"
# Grant specific object-level privileges instead:
hdbsql -U SYSTEM -j "GRANT SELECT ON SCHEMA <schema> TO <user>"

3 — Auditing & Logging

▶

3.1 Audit Configuration

▶
3.1.1 Ensure Global Auditing Is Enabled (Automated)
L1 Auto
Description

This recommendation verifies that Global Auditing Is Enabled on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='auditing configuration' AND KEY='global_auditing_state'"
# Should return: true
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('auditing configuration', 'global_auditing_state') = 'true' WITH RECONFIGURE"
3.1.2 Ensure Audit Policies Are Defined (Automated)
L1 Auto
Description

This recommendation verifies that Audit Policies Are Defined on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT AUDIT_POLICY_NAME, IS_AUDIT_POLICY_ACTIVE, EVENT_STATUS, EVENT_ACTION FROM SYS.AUDIT_POLICIES"
Remediation
hdbsql -U SYSTEM -j "CREATE AUDIT POLICY pol_system_config AUDITING ALL SYSTEM CONFIGURATION CHANGE LEVEL CRITICAL"
hdbsql -U SYSTEM -j "ALTER AUDIT POLICY pol_system_config ENABLE"
3.1.3 Ensure Audit Trail Is Set to SYSLOG (Automated)
L1 Auto
Description

This recommendation verifies that Audit Trail Is Set to SYSLOG on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='auditing configuration' AND KEY LIKE '%default_audit_trail%'"
# default_audit_trail_type should be SYSLOG for centralized logging
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('auditing configuration', 'default_audit_trail_type') = 'SYSLOG' WITH RECONFIGURE"
3.1.4 Ensure Logon and Privilege Events Are Audited (Automated)
L1 Auto
Description

This recommendation verifies that Logon and Privilege Events Are Audited on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT AUDIT_POLICY_NAME, EVENT_ACTION FROM SYS.AUDIT_POLICIES WHERE EVENT_ACTION LIKE '%CONNECT%' OR EVENT_ACTION LIKE '%GRANT%'"
Remediation
hdbsql -U SYSTEM -j "CREATE AUDIT POLICY pol_logon AUDITING SUCCESSFUL CONNECT, UNSUCCESSFUL CONNECT LEVEL INFO"
hdbsql -U SYSTEM -j "ALTER AUDIT POLICY pol_logon ENABLE"
hdbsql -U SYSTEM -j "CREATE AUDIT POLICY pol_privs AUDITING ALL GRANT PRIVILEGE, REVOKE PRIVILEGE LEVEL INFO"
hdbsql -U SYSTEM -j "ALTER AUDIT POLICY pol_privs ENABLE"

4 — Encryption & Key Management

▶

4.1 Encryption

▶
4.1.1 Ensure Data Volume Encryption Is Enabled (Automated)
L1 Auto
Description

This recommendation verifies that Data Volume Encryption Is Enabled on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='persistence' AND KEY='encryption'"
# Should return: true (data volume encryption)
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('persistence', 'encryption') = 'true' WITH RECONFIGURE"
4.1.2 Ensure Log Volume Encryption Is Enabled (Automated)
L1 Auto
Description

This recommendation verifies that Log Volume Encryption Is Enabled on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='persistence' AND KEY='log_encryption'"
# Should return: true (log volume encryption)
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('persistence', 'log_encryption') = 'true' WITH RECONFIGURE"
4.1.3 Ensure Backup Encryption Is Enabled (Automated)
L1 Auto
Description

This recommendation verifies that Backup Encryption Is Enabled on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='backup' AND KEY='encryption'"
# Should return: true (backup encryption)
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('backup', 'encryption') = 'true' WITH RECONFIGURE"

4.2 Key Management

▶
4.2.1 Ensure Root Encryption Key Is Rotated (Manual)
L1 Manual
Description

This recommendation verifies that Root Encryption Key Is Rotated on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='persistence' AND KEY='internal_encryption_root_key_status'"
# Review root encryption key status
Remediation
# Rotate the root encryption key:
hdbsql -U SYSTEM -j "ALTER SYSTEM APPLICATION ENCRYPTION ROOT KEY CREATE"
4.2.2 Ensure Secure User Store Is Reviewed (Manual)
L1 Manual
Description

This recommendation verifies that Secure User Store Is Reviewed on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbuserstore list
# Review stored credentials — verify no plaintext passwords
# Check for unnecessary key entries
Remediation
# Remove unused secure store entries:
hdbuserstore delete <KEY>

# Add entries with proper credentials:
hdbuserstore set <KEY> <host>:3<inst>13 <user> <password>

5 — Operational Security

▶

5.1 OS & Services

▶
5.1.1 Ensure Configuration File Permissions Are Correct (Automated)
L1 Auto
Description

This recommendation verifies that Configuration File Permissions Are Correct on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
ls -la /hana/shared/<SID>/global/hdb/custom/config/
# Config files should be owned by <sid>adm
find /hana/shared -name '*.ini' -exec ls -la {} \;
Remediation
chown -R <sid>adm:sapsys /hana/shared/<SID>/global/hdb/custom/config/
chmod 640 /hana/shared/<SID>/global/hdb/custom/config/*.ini
5.1.2 Ensure Embedded HTTP Server Is Disabled (Automated)
L1 Auto
Description

This recommendation verifies that Embedded HTTP Server Is Disabled on the SAP HANA 2.0 in-memory database platform. Disabling or removing unnecessary components reduces the attack surface and limits potential vectors for exploitation.

Rationale

Running unnecessary components on the SAP HANA 2.0 in-memory database platform increases the attack surface and the risk of exploitation. Disabling or removing them follows the principle of least functionality and reduces exposure to known vulnerabilities.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='httpserver' AND KEY='embedded'"
# Should be: false (disable if not needed)
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('httpserver', 'embedded') = 'false' WITH RECONFIGURE"
5.1.3 Ensure Public Hostname Resolution Is Restricted (Automated)
L2 Auto
Description

This setting ensures that Public Hostname Resolution Is Restricted on the SAP HANA 2.0 in-memory database platform. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Rationale

Unrestricted access to this capability could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the SAP HANA 2.0 in-memory database platform is essential for defense in depth.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='public_hostname_resolution' AND KEY='use_default_route'"
# Review hostname resolution config
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('public_hostname_resolution', 'use_default_route') = 'no' WITH RECONFIGURE"

5.2 Backup Configuration

▶
5.2.1 Ensure Regular Backups Are Configured (Manual)
L1 Manual
Description

This recommendation verifies that Regular Backups Are Configured on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT ENTRY_TYPE_NAME, UTC_START_TIME, STATE_NAME FROM M_BACKUP_CATALOG ORDER BY UTC_START_TIME DESC"
# Verify recent full and log backups exist
Remediation
# Create a full data backup:
hdbsql -U SYSTEM -j "BACKUP DATA USING FILE ('/hana/backup/data/COMPLETE_DATA_BACKUP')"

# Schedule regular backups via cron or SAP HANA Cockpit
5.2.2 Ensure Log Mode Is Set to Normal (Automated)
L1 Auto
Description

This recommendation verifies that Log Mode Is Set to Normal on the SAP HANA 2.0 in-memory database platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the SAP HANA 2.0 in-memory database platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
hdbsql -U SYSTEM -j "SELECT KEY, VALUE FROM M_INIFILE_CONTENTS WHERE SECTION='persistence' AND KEY='log_mode'"
# Should return: overwrite (for log mode normal) or blank (log mode normal is default)
Remediation
hdbsql -U SYSTEM -j "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('persistence', 'log_mode') = 'normal' WITH RECONFIGURE"