A Practical Guide to Designing Secure Health Solutions Using Microsoft Azure

Today I have finished publishing my latest great work of security and compliance content. Check it out!.

A Practical Guide to Designing Secure Health Solutions Using Microsoft Azure whitepaper providers readers considerations guidance for using cloud technology, includes risk management, shared responsibility considerations, establishing an information security management system, understanding industry and local regulations, and establishing standard operating procedures. It outlines, and provides recommendations to 13 security principles that are both aligned to a standard information security management standard, such as ISO 27001, and standard development processes, such as Microsoft’s Security Development Lifecycle (SDL). The paper also gives readers a direct view of the key principles by applying them to a ‘lift and shift’ health based case study.



Whitepaper Table of Content

Compliance and security methodology  
Standard operating procedures
Incorporating regulation considerations – health industry
Shared responsibilities 
Key principles and recommendations for secure development and operations             
1.           Enable identity and authentication solutions      
2.           Use appropriate access controls
3.           Use industry-recommended, enterprise-wide antimalware solution             
4.           Effective certificate acquisition and management            
5.           Encrypt all customer data           
6.           Penetration testing        
7.           Threat modeling services and applications          
8.           Log security events, implement monitoring and visualization capabilities
9.           Determine the root cause of incidents   
10.         Train all staff in cyber security   
11.         Patch all systems and ensure security updates are deployed       
12.         Keep service and server inventory current and up-to-date           
13.         Maintain clear server configuration with security in mind            

Applying key principles in use case Lift and Shift | Implementation of a healthcare application   

Comments

Post a Comment

Popular posts from this blog

Protecting sensitive data

Image
Last month I wrote an article on key things to consider when protecting high valued assets or sensitive data. The article called Security Tip of the Month: Protecting Highly Sensitive Information addressed some of the key items that organizations should consider when protecting data that has the possible impact on an organization that is irreparable. As my article stated the cost of protecting this data tends to be higher than most data. Fact is that this data is not traditionally just sensitive such as credit card data, or HR data. Key indicators of what is High Value Data can be summed up like this. Assets that are considered to be of high value will frequently have the potential to cause the following conditions if they are lost or divulged: •        Loss of life - such as an informant list •        Regulatory fines - such as financial performance data •        Significant damage to the business - such as code signing and encryption keys (private) or trade secrets
Read more

Secure workstation - Root of trust to manage the cloud

Image
Two months ago I introduced the Azure secure workstation, and I’ve had the privilege to present the ideal to some great audiences. From the discussions, a common question I’ve been asked is a pattern that would provide the Secured PAW model lock down scenario to exclusively manage an Azure Portal (EG how to I assure only secured workstation, and users assigned to the program can manage my cloud services)? In this article I’ll provide the NEXT step to accomplish exactly that outcome. This includes additional configurations that I only lightly covered, or net new technology to apply since the publishing of the doc. Proposed outcome “ How do I” Use a Secured workstation (that I can trust) to manage my Azure cloud. Here’s how I would deploy the solution. First I will start by deploying the Secured Workstation model this using the secured profile. New technology, and capabilities to add: Hardware root of trust – in our solution we post the idea that you can
Read more

Why is privileged access important?

Image
Last year about this time I had published updates to the Azure Secure Workstation that was originally released two years ago. And This month the solution has been considerably rewritten and revised to provide a better more complete management for privileged access!  Collaborating with two great security experts James Noyce, and Mark Simos The content got a massive overhaul, and a broad perspective on what it takes to build and manage a comprehensive privileged access solution, including account management, device management, intermediaries such as VPN's and interfaces such as Web and Cloud services. Additionally, the solution was uniformly designed with three distinct security levels that anyone reading the article can deploy from a more flexible Enterprise security, to a comprehensive isolated PAW or privileged Access Management. Over the past two years I've been working to explain and illustrate how you can use a cloud-based solution to build an effective Zero tr
Read more