SAP HANA on Azure (Large Instances) Security

By Ashwin Venugopal -

 




SAP HANA on Azure (Large Instances) Security

Encryption of data on transit

Data transferred between HANA Large Instance and VMs is generally not encrypted but you can enable the application level encryption between the HANA DBMS and JDBC/ODBC- based applications.

Encryption of data at rest

You can enable this encryption easily whenever you want to deploy a HANA Large instance unit and you can also change the encrypted volumes after the deployment. However, the move from non-encrypted to encrypted volumes is transparent and doesn't require downtime. 

  • By default, the HANA Large Instances uses stirage encryption based on TDE (Transparent Data Encryption) for the data at rest.

  • Data in transit between HANA Large Instances and the VMs is not encrypted and you have to enable the application-specific encryption to encrypt the data transfer.

  • Isolation provides security between the tenants in the multi-tenant HANA Large Instance environment according to which tenants are isolated using their own VLAN.

  • Azure network security best practices offer helpful guidance.

  • Operating system hardening is recommended as with any other deployment.

  • Access to secure datacenters is limited to authorized personnel only for physical security and no customers can access the physical servers. 

SAP HANA on Azure (Large Instance) licensing

According to the licensing point of view, you should also account for the following:
  • Licenses for SUSE Linux Enterprise Server 12 for SAP Applications- The operating system that Microsoft delivers is neither registered with SUSE nor connected to a Subscription Management Tool instance. Hence, to remediate this you should deploy SUSE Linux Subscription Management Tool in an Azure VM which provides the capability for SAP HANA on Azure (Large Instances) to be registered and updated by SUSE respectively.

  • Licenses for Red Hat Enterprise Linux 6.7 or 7.x for SAP HANA- The operating system that's always delivered by Microsoft is neither registered nor connected to a  Red Hat Subscription Manager instance. To remediate this, you have to deploy the Red Hat Subscription Manager deployed in an Azure VM which also provides the capability for SAP HANA on Azure (Large Instances) to registered as well as updated by Red Hat respectively.

You should have a support contract with your Linux provider for SAP which isn't removed by the solution of HANA Large Instances or the fact that you run Linux in Azure. The service fee is not included in the solution offer of HANA Large Instance and you will have to fulfill the requirements of SAP regarding the support contracts with the Linux distributor. 





Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more