Integration Requires Good Security
Ryan Boyles 100000UX41 firstname.lastname@example.org | | Tags:  datapower cast-iron integration amywohl security cloud
0 Comments | 3,356 Visits
Almost every cloud computing plan will involve more than a single cloud in isolation. We want to connect private clouds to data centers and to public clouds. Much of what is appealing about cloud computing requires crossing boundaries of both governance and security. That means handling an entire set of security issues.
CIO’s see security as a prime barrier to achieving the cloud results they’re looking for – in a recent survey, three of their ten cloud concerns were integration related and security was Number One.
This cannot be avoided: if you want cloud computing you will need integration and if you perform integration you will require security.
This means a plan for handling authentication, authorization, privacy, data validation, auditability, and availability. Your organization’s needs may also include encryption, in transit and in storage. All this occurs across public networks, which can be a hostile environment.
Typically, you will need software (often, a portfolio of software) or an appliance between the integration pieces, to provide both protection and function. Security components can also be accessed as a service. IBM offers WebSphere Cast Iron Live to provide secure integration within and between the cloud and the enterprise For example, IBM’s Cast Iron Secure Cloud Connector (Read more: PDF) can establish a secure tunnel between two endpoints, allowing data flows to be initiated from either end of the connection, in conjunction with an Application Optimization license.
DataPower’s magic includes a specialized compiler a high-performing throughput-optimized engine, the ability to view everything as a transformation, and purpose built hardware to execute SOA workloads and transformations. The appliance supports monitoring and control, deep-content routing and data aggregation, functional acceleration, application-layer security and threat protection (such as XML Denial-of-Service protection) and protocol and message bridging (for example, converting WebSphere to legacy Cobol/MQ).
The cloud, from a security perspective, offers additional layers of complexity, especially when accessing function or data on public clouds, where there is less control. But the right tools for implementing a secure hybrid cloud environment exist and appropriate education and planning can permit cloud computing to succeed, even when information and governance are crossing multiple boundaries.
In a future blog post we’ll talk more about hybrid cloud environments.