Spotlight: An SAP Security Architect Comments on Methods to Keep SAP HANA Secure
- by Gary Byrne, Managing Editor, Financials Expert and SCM Expert
- February 14, 2014
SAP Professional Journal
In this question-and-answer article, you’ll learn what measures to take to secure SAP HANA-based applications.
To find out what security issues SAP HANA presents to IT organizations, I asked Aman Dhillon, SAP security architect at Layer Seven Security, a series of questions. See what he had to say about monitoring access to SAP HANA-based applications and determining if your SAP HANA-based environment has the optimal level of protection. Aman also comments on key areas on which to focus to ensure optimal protection against a new form of malware that targets SAP systems.
Aman, what are some key security points an organization should consider before implementing SAP HANA?
First, organizations should be aware that there are some trade-offs to adopting SAP HANA with respect to security. In-memory databases are a relatively new technology, and therefore, do not offer the same range of security measures as conventional persistent databases that have benefited from 30 years of evolution.
This includes label-based rules for more granular control over data access, data redaction to mask the display of sensitive data, and utilities to apply patches without interrupting the availability of database services. However, these drawbacks are a caveat for the use of SAP HANA and should not be used as an argument against the implementation of in-memory databases. The performance edge delivered by SAP HANA is extraordinary and, in most cases, outweighs any security disadvantages.
Would you like to see this full item?