Attacks/Breaches
6/18/2010
11:41 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Microsoft Offers Developers Cloud Security Tips

New paper provides best practices for writing applications for Windows Azure.

Microsoft this week published a best practices guide for writing applications to its Windows Azure cloud computing environment.

"We wrote this paper because no matter how many defenses we add to Windows Azure, it is important that people building software or hosting services in 'The Cloud' understand that they must also build software with security in mind from the start," blogged Michael Howard, principal security program manager of Microsof's Security Development Lifecycle team.

The best practices for developing secure cloud apps detailed in the paper encompass service layer and application security, the Azure platform's built-in protections, the network infrastructure, and hardening user privilege services.

Among the security services for Azure that address the sticky identity management problem surrounding the cloud are Windows Identity Foundation, Active Directory Federation Services 2.0, and Windows Azure AppFabric Access Control Service.

The paper is aimed at teaching developers how to mitigate the threats to the cloud, as well as "explaining some of the threats you may be susceptible to, such as port scanning, denial-of-service, and so on," Howard said in a video blog post.

At the service layer of the cloud framework, developers should map their regular, noncloud security requirements for apps to Windows Azure services. "Any remaining threats must be mitigated by the application or service," Microsoft's "Security Best Practices For Windows Azure Applications" paper says.

The paper also notes Azure platform services that provide authentication, authorization, and auditing, as well as the methods used to invoke them in apps, are much different than their counterpart tools in on-premise networks, such as Kerberos, Active Directory, and Windows Event Logs. Among the wide range of developer tips from Microsoft:

  • Use a custom domain rather than *servicename*.cloudapp.net in order to separate the cloud from the enterprise space -- the cloudapp.net namespace is used by all Microsoft Azure customers.
  • Isolate Web roles and separate duties of individual roles.
  • Isolate privileged access by using a "gatekeeper" design pattern that provides a separation of duties.
  • Use multiple storage keys.

One Azure subscription can have up to five storage keys. "This diversity can be used to minimize exposure of a particular key to theft by placing lower-trust keys on lower-trust roles and higher-trust keys on higher-trust roles," Microsoft said in its paper.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2037
Published: 2014-11-26
Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads. NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

CVE-2014-6609
Published: 2014-11-26
The res_pjsip_pubsub module in Asterisk Open Source 12.x before 12.5.1 allows remote authenticated users to cause a denial of service (crash) via crafted headers in a SIP SUBSCRIBE request for an event package.

CVE-2014-6610
Published: 2014-11-26
Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dia...

CVE-2014-7141
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.

CVE-2014-7142
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (crash) via a crafted (1) ICMP or (2) ICMP6 packet size.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?