SAP HANA 2.0 Administration · Security: Users, Privileges, Authentication, Auditing & Encryption

Why should you NOT grant predelivered standard catalog roles (MONITORING, CONTENT_ADMIN) directly, and what's the exception for SAP_INTERNAL_HANA_SUPPORT?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Security: Users, Privileges, Authentication, Auditing & Encryption

You enabled client-side TLS on SAP HANA and assume node-to-node traffic is now protected too. Why is the internal channel still in the clear?

Which authentication mechanisms does SAP HANA support?

A regional sales manager must see only their own region's rows inside a calculation view. Why won't an object (SELECT) privilege accomplish this, and what does?

You granted SELECT ON SCHEMA to a reporting user. Months later a developer creates a new table in that schema with sensitive data. Who can read it, and why is that the cost of a schema grant?

A user has too much access via a role, and you want to carve out one schema as forbidden. Why can't you just add a deny, and what does HANA do the moment it finds a matching grant?

Two HANA catalog objects look identical at runtime, but one is owned by _SYS_REPO and one by a developer. Which is which, and why does the ownership difference matter operationally?

Start learning today

Free to start — download the app or use it in your browser.