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

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more