Cloud
Guest Blog // Selected Security Content Provided By Intel
What's This?
7/16/2014
04:45 PM
Tom Quillin
Tom Quillin
Guest Blogs
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

Create a Foundation for Cloud Security

Security and operations don't have to be at odds. You can turn security into an operations tool, creating a secure and agile environment that extends your tools and processes.

Statistics and trends support the notion that cloud computing has become a business requirement, rather than an optional capability. However, the adoption of cloud services continues to be inhibited by lack of trust and confidence related to concerns around the security of sensitive data and regulatory issues.

There appear to be two main culprits: the inability of traditional data center security tools to adapt to cloud services models and a lack of transparency and control. Both issues affect public, private, and hybrid clouds. The traditional data center security environment is static, slow to change, contained (e.g., DMZ), single tenant, and physical. Cloud security environments are dynamic (e.g., live-migration, burst), fast (e.g., automated, scale change), distributed (e.g., hybrid), multi-tenant, and abstracted. On top of these differences, managing external cloud service providers brings coordination costs and risks. Cloud service providers and users must agree on how to create confidence that implementations are trustworthy from top to bottom.

Within these challenges lies an opportunity. We are used to thinking of security as a tradeoff -- better security is often considered synonymous with worse performance, agility, and user experience. As a result, there is a constant tug-of-war between operations and security. The opportunity is to turn security into a tool for operations, resulting in an environment that is more secure, more agile, and extends tools and processes.

To do this, instead of thinking in terms of managing security based on physical objects (that is, specific servers), you can substitute logical objects for them. A logical object attribute could be a "trusted server" that's established via measured boot and attestation process characteristics. We can associate other configuration information with the trustworthiness of the server (e.g., its physical location or tenant association). We can now create pools of trusted servers and manage against the pool association of a given server (e.g., deploy pools of workloads of certain types on predefined resource pools = "trusted compute pools"), as opposed to against that server's specific identity. Management applications can consume the trust attributes to execute policy and record event logs. This approach leverages measured boot -- a protection against attacks that target lower levels of the launch environment to form pools of trusted servers that can be used securely for mission-critical workloads.

What action can I take today? If you have an interest in implementing secure, trusted computing environments, either within your own infrastructure or working with cloud providers, the Trusted Computing Group offers resources for implementing standards-based architecture and solution stacks.

Follow me on Twitter: @TomQuillin.

Tom is responsible for identifying and addressing Intel product security risks as well as planning products that solve tomorrow's security challenges and also manages Intel's policy positions on security and privacy. View Full Bio
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.