SAP HANA security (Haun, Jonathan)（Z-Library）

【One-Line Pitch】 A hands-on administrator's guide to locking down an SAP HANA system, walking from the platform's hardware and memory model through users, privileges, roles, and repository-based security. Best for SAP basis admins, security consultants, and DBAs who already touch HANA and need to design and operate a defensible access model. 【Book Arc】 - **Opening (~0%–10%)**: Orients you in the SAP HANA appliance — hardware layers, in-memory/column-store architecture, and the SAP HANA Studio environment — so later security decisions rest on how the platform actually stores and processes data. - **Early (~10%–32%)**: Builds the object and identity foundation: catalog objects (schemas, tables, views, procedures), object privileges, and creating/managing user accounts via SQL and Studio, including password, lockout, and authentication settings. - **Middle (~32%–52%)**: Moves into privilege and role mechanics — granting/revoking privileges, the EFFECTIVE_PRIVILEGES view for auditing, assigning roles, and the case for role-based rather than per-user grants. - **Late (~52%–70%)**: Covers database roles and repository roles in depth, including the _SYS_REPO account, grantor semantics, design-time role scripts, and the full privilege taxonomy (system, schema, object, structured, analytic, application, package). - **Ending (~70%–100%)**: Excerpts do not cover this range in detail; expect operational topics such as user provisioning workflows (e.g., LDAP/CSV-driven account loading) and transport/backup of the security model. 【Key Takeaways】 - **Security starts with architecture** (Opening): Understanding DRAM/CPU-cache storage and column-store parallelism explains why HANA's performance profile also shapes its security surface — you secure a system you understand. - **Object privileges govern SQL verbs on catalog objects** (Early): They control who can SELECT, EXECUTE, DELETE, or ALTER tables, views, procedures, and schemas; GUIs like Studio silently translate clicks into these SQL grants, so admins should know what's happening underneath. - **User lifecycle is a first-class security control** (Early): ALTER USER handles forced password changes, lockout resets, SAML/Kerberos toggles, password lifetime, and per-statement memory limits — small settings with large blast-radius implications. - **Dropping users is dangerous by design** (Early): RESTRICT (the default) blocks deletion when ownership conflicts exist; CASCADE wipes owned schemas, objects, synonyms, and revokes granted privileges — choose deliberately. - **Roles are the backbone of a scalable model** (Middle): Granting roles instead of individual privileges keeps hundreds of users manageable; role updates propagate automatically to all grantees, and EFFECTIVE_PRIVILEGES lets you audit what a user actually holds. - **Repository roles extend security into development** (Late): Design-time scripts define roles inside packages, with grantor/privilege semantics tied to _SYS_REPO — bridging database security and the development lifecycle. - **Know the privilege taxonomy** (Late): System, schema, object, structured, remote-source, analytic, application, and package privileges each answer a different question; mixing them up is a common source of over- or under-granting. - **Avoid deleting roles still in use** (Middle): Deletion revokes the role and its privileges from every grantee; query EFFECTIVE_ROLE_GRANTEES first to see who's affected. 【Reading Tips】 - **Skim the Studio navigation material** (window/tab management, connection dialogs) unless you're new to the tool; deep-read the privilege and role chapters, which carry the durable concepts. - **Treat SQL syntax blocks as reference, not prose**: the ALTER USER, DROP USER, and GRANT examples are worth bookmarking for daily admin work. - **Watch the GUI-vs-SQL distinction**: whenever the book shows a Studio workflow, ask what SQL it generates — that mental habit is the real takeaway. - **Pause on CASCADE/RESTRICT and role deletion**: these are the irreversible operations; rehearse them in a sandbox before production. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book (architecture, users, privileges, roles, repository roles); later operational chapters are only partially represented, so specifics there are not summarized.