Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Cloudcast: Evolving Security-as-a-Service

DZone's Guide to

The Cloudcast: Evolving Security-as-a-Service

· Cloud Zone ·
Free Resource

Site24x7 - Full stack It Infrastructure Monitoring from the cloud. Sign up for free trial.

The Cloudcast (.net) #45 - Evolving Security-as-a-Service (30:30)

Date: June 28, 2012

By: Aaron Delp and Brian Gracely

Description: Brian talks with CloudAccess CEO Kevin Nikkhoo about the evolution of remote security services, or Security-as-a-Service.


Date: June 28, 2012
Guest: Kevin Nikkhoo, CEO @ CloudAccess (@CloudAccess_)


Topic 1 - For many years now, we’ve heard security professionals say that security can’t be an after-thought, that it can’t be bolted on, that it must be considered from Day 1. That rarely seems to happen. Is Cloud Computing a new opportunity to build security in closer to Day 1 for applications?



Topic 2 - Security can have lots of aspects (authentication, encryption, threat analysis, data-loss-prevention, monitoring, etc..). What’s different when thinking about security for Cloud Computing?



Topic 3 - When we talk about all the different areas that security touches, that’s a lot of different groups within a company - some in IT, some in Legal/Compliance, etc. How do you explain security, which is inherently complex to either that broad an audience, or up the chain to someone like a CIO, who typically has less in-depth knowledge of security?



Topic 4 - Let’s talk about why it makes sense to run security-as-a-service, off premise from a companies data center? Or is CloudAccess primarily for public clouds?



Topic 5 - Can you talk about how companies can get started with security-as-a-service both in terms of costs, as well as auditing the security of their applications?

Site24x7 - Full stack It Infrastructure Monitoring from the cloud. Sign up for free trial.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}