Storage security (part 1)

By Ashwin Venugopal -

 


To read part 2 please click here

Data Sovereignty

Data sovereignty is the concept that information which has been converted and stored in binary digital form is subject to the laws of the country or region in which it is located. Most of the current concerns that surrounds data sovereignty relate to enforcing privacy regulations and preventing data that is stored in a foreign country or region from being subpoenaed by the host country or the region's government.

In Azure, the customer data might be replicated within a selected geographic area for enhanced data durability in case of a major data center disaster, and in some cases will not be replicated outside it.

Paired regions

Azure operates in multiple geographies around the world. Each Azure region is paired with the another region within the same geography, forming the regional pair (except Brazil South). It is recommended to configure Business Continuity and Disaster Recovery (BCDR) across regional pairs to benefit from Azure's isolation and VM policies. Using both regions in a regional pair where ever possible for the applications that supports the multiple active regions, will ensure optimal availability for applications and minimized recovery time in the event of a disaster.

Benefits of the Azure paired regions

  • Physical isolation- When ever possible, Azure services prefers at least 300 miles of separation between datacenters in a regional pair. Isolation is subject to the constraints within the geography, such as geography size, power, and network infrastructure availability, and regulations.

  • Platform-provided replication- Some services such as geo-redundant storage provide automatic replication to the paired region.

  • Region recovery order- In the event of a broad outage, recovery of one region is prioritized out of every pair. Applications that are deployed across paired regions are guaranteed to have one of the regions recovered with priority, but if they are not paired, then the recovery might be delayed. In the worst case the chosen regions might be the last two to be recovered.

  • Sequential updates- Planned Azure system updates are rolled out to paired regions sequentially, not at the same time, which helps minimize downtime, the effect of bugs, and logical failures in the rare event of a bad update.

  • Data residency- To meet the data residency requirements for tax and law enforcement jurisdiction purposes, a region resides within the same geography as its pair (except Brazil South).  

Microsoft also complies with the international data protection laws regarding transfers of the customer data across borders. It will not transfer to any third party (not even for storage purposes) the data that you provide to Microsoft through the use of business cloud services, and that are covered under the Microsoft Online Services Terms.

Note- No matter where the customer data is stored, Microsoft does not control or limit the locations from the customers, or their end users might access their data.  

Azure Storage Access

Overview of Access Control for Storage Account

Every request made against a secured resource in the Blob, Fire, Queue, or Table service must be authorized which ensures that the resources in your storage account are accessible only when you want them to be, and only to those users or applications to whom you grant access.

Options for authorizing requests to Azure Storage includes:

  • Azure AD- Azure Storage provides integration with Azure AD for identity-based authorization of requests to the Blob and Queue services. When you use Azure AD to authorize requests made from your applications, you avoid having to store your account access key with your code, as you do with the Shared Key authorization. While you can continue to use Shared Key authorization with your blob and queue applications, Microsoft recommends moving to Azure AD where ever possible.

  • Azure AD Domain Services authorization for Azure files- Azure Files supports identity-based authorization over Server Message Block (SMB) through Azure AD DS. You can use RBAC for fine-grained control over a client's access to Azure Files resources in a storage account. 

  • Shared key- This authorization relies on your account access keys and other parameters to produce an encrypted signature string that is passed on via request in the Authorization header.

  • Share access signatures (SAS)- It is a URI that grants restricted access rights to the Azure Storage resources. You can provide an SAS to the client who should not be trusted with your storage account key but to whom you wish to delegate access to certain storage account resources. A client who is in possession of the SAS can make a request against Azure Storage with just the SAS URI, and the information contained in the SAS token is used to authorize the request.

  • Anonymous access to containers and blobs- You can enable anonymous, public read access to a container and its blobs in the Azure Blob Storage. Public read access is the best for the scenarios where you want certain blobs to always be available for anonymous read access. For more fine-grained control, look to using the shared access signature described above.  

Authenticating and authorizing access to blob and queue data with Azure AD provides superior security and ease of use over other authorization options. Where ever possible use authorizing applications that access Azure Storage using Azure AD. It provides better security and ease of use over other authorization options.


To read part 2 please click here





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