15.
Microsoft Cloud Solution Security
Overview (Cont.)
• The “human” and “Data” layers are the users’
responsibility and how they manage their data
and its permissions (more information about the
data on Azure to be followed)
• The “Application Layer” depend on the developer
and the security used on it
• Authentication
• Input validation ….
• Recommend to develop using SDL (security
development lifecycle) designed for windows
Vista, Windows 7 and windows Azure

19.
Data Security on Azure
• Windows Azure Compute and Windows Azure
Storage are 2 different things each of them is
hosted on different hardware resources
• In the Storage Architecture the top layer
validates, authenticates, and authorizes requests,
routing them to the partition layer and data layer
where the data exists
• Protect against Data Loss, there are always three
replicates of your data whatever happens

20.
Data Security on Azure
• Isolation: all your data are isolated from the
others by 2 ways:
– Logically
– Physically
• Each type of storage has its own way of access
depending on the developer
• NO DATA ARE ACCESSIBLE BY THE PUBLIC
EXCEPT THE PUBLIC BLOB

22.
Secure Networking
• No communication is possible to be made
between the VLANs without passing through
several routers for preventing faking traffic
and eavesdropping on other traffic
• The communication is permitted from the FC
VLAN or the Device VLAN to the main VLAN
but not initiated from the main VLAN

23.
Secure Networking
• Azure has the largest internet connections in the
industry
• It is unlikely that someone can cut azure out of
public by producing enough malicious traffic
• If your application on azure is attacked, azure will
create several compute instances to maintain
your application until the attack passes
• Microsoft is considering ways to identify
malicious traffic and block it as it enters the Azure
Fabric, but this sort of protection has not yet
been deployed.

25.
Identity On Azure
• Windows Azure supports 2 types of identity in
the Cloud:
– Role based
– Claim Based
• Role based is using Username and password
• Claim based is using Token containing a
collection of Claims

26.
Identity On Azure: Role based
authorization
• It can be used by SQL Azure, Azure Connect
and ASP.NET membership provider
• You only use the username and the password
and the rest are kept in the identity store
• Simple, easy to use and possible to implement
Domain join

28.
Identity on Azure : Claim Based
• Claim is a piece of information
• Token is a collection of Claims and are signed
• Security Token Service map the credentials to the
token
• Application is provide with all the identity
information needed
• The management of the identity is not the
application responsibility
• Integration between several identity providers
• Less infrastructure code

29.
Identity On Azure: AppFabric
Access Control
• Enable the developer of using claim based
authorization from enterprises like active
directory, SQL Server
• Also enable the usage of the other identity
provider like live ID, Facebook, Google and
Yahoo.