Binary Large Object (BLOB) is one of the four core storage services that are secure, scalable and easy to access. Itz the simplest way to store text or binary data with Windows Azure.
As the concept, each storage account has access to blob storage. For each account there can be 0..n containers. Each container contains the actual blobs, which is a raw byte array. Containers can be public or private. In public containers, the URLs to the blobs can be accessed over the internet while in a private container, only the account holder can access those blob URLs.
Each Blob can have a set of metadata set as a NameValueCollection of strings. Key terms are explained in the below list:
Storage Account – All access to Windows Azure Storage is done through a storage account. This is the highest level of the namespace for accessing blobs An account can have many Blob Containers
Blob Container – A container provides a grouping of a set of blobs. The container name is scoped by the account.
Blob – Blobs are stored in and scoped by Blob Containers. Each blob can be up to 50GB. A blob has a unique string name within the container. Blobs can have metadata associated with them, which are pairs, and they are up to 8KB in size per blob. The blob metadata can be gotten and set separately from the blob data bits
What are the checking that needs to be done so that the blob data that is passed from and to the browser is not tampered by the man in the middle or a user who is having a genuine account? Like that of a Citi Breakin. Is there any additional security provided by cloud providers apart from using https? What about code injection or sql injection?
ReplyDeletegreat question srini. Recently Somasegar wrote abt WIF as the next gen security framework, which is the solution apart from https. Therez an interesting related Q&A at social msdn http://social.msdn.microsoft.com/Forums/en-US/windowsazuresecurity/thread/ce184009-b0e9-4198-b4d7-79d8f1e5abcc
ReplyDelete