Another Cloud Computing Conference
As I sat down on the plane, I took a look back at the conference brochure to remind myself of everything I had covered for the week. Before I had left to come to this conference, there was nothing less exciting to me than information security. However, it was the compliance and legal areas I learned about where I had gotten the most out of the conference.
Learning more about corporate governance in the cloud was my first priority in gathering information at the conference. So glad that so many sessions at least noted this after hearing the urgency needed for improved federated identity management in a time when more and more technologies were moving into the cloud. And oh yes, the cloud….the place were all things could happen, and would with information technology in our near future.
Beyond any doubt, my company’s effort to send me to the cloud conference was worthwhile. So much of what I learned was not only going to do me good, but it would serve us well as our company decided to migrate to the cloud by the end of the fiscal quarter. This information learned and the all the vendors I met was a great way to apply some best practices and share concerns from the industry on this work.
I recalled my notes from Laura Smith, a lead writer for SearchCIO.com, who noted in an interview with Benjamin Doyle, a pioneer user for Salesforce.com, one must be fairly aggressive in adopting new solutions. In doing so, Doyle noted, that security and identity management had become the number one concern from IT professionals (Smith, 2011). As I thought about it, it sure made sense. With so many technologies moving to the cloud for many mobile and internet technologies, I had no doubt that identity management was going to be a growing concern.
Even Doyle noted in this interview that traditional technologies like Microsoft’s Active Directory were great at integrating with traditional software, but the cloud presented many new challenges which his company had never experienced before. He noted in his shopping spree to find the right vendor solution that there was over 200 services they looked at in helping them move to the cloud (Active Directory Management, 2011). I had a note next to that statement to check when returning to the office which read, “review processes” as a reminder to look deeper into the decisions we had made in selecting our vendor, Trea Services.
True, Trea had been called because of our need to offer more mobile services in the cloud, but it was also because of their outstanding record in the field with identity management which caught our eye. Making more of our services available via an online sign on system complicated the issue of moving to the cloud, but Trea has experts in identity management which makes all the work they do worthwhile after some of the horror stories I heard at this conference.
Dealing with people’s identity was no small business anymore. Even in our own research we had used some guiding ISA experts to both provide a future reference to our framework, and to adopt a true security life cycle which we felt was in line with our business needs. Jan Killmeyer and Windley were those noted experts to us. As he notes in his work, “Information Security Architecture: An Integrated Approach to Security in the Organization, Second Edition,” there were four areas which now created our security life cycle. Those included:
- Performing security and risk assessments
- Developing an infrastructure to reduce the risk and meet defined security goals and objectives that support the business goals and objectives
- Implementing what has been developed
- Measuring the effectiveness of what has been implemented, and maintaining that infrastructure to meet the needs of the organization (Killmeyer, 2006)
We recognized early that if we were going to help set the tone for compliance in the ISA process, we were going to need to produce the “mechanisms” which would make those processes achieve at consistently high levels. It was apparent that our company was going to need to elicit some clear compliance measures based on industry standards and aligned to our business needs.
We adopted some guiding principles based on an article which sparked discussion about a year back called, “Top Considerations for Compliance in the Cloud,” by Marisa Peacock (2011). In this article, we love the analogy of thinking of moving to the cloud as moving in general. Thus, she encourages the adoption of five key principles to include:
- Choosing the right neighborhood
As you might have guessed, different systems and modules offer different types of customer control and place different obligations and responsibilities upon both customers and service providers with respect to security and compliance.
- Meeting the neighbors,
Like any real estate, it’s important to think about its proximity to the places you go, the quality of the roads, can the neighbors see over the bushes, and reputation of the neighborhood — in other words, consider vendor lock-in, portability of data and applications, interoperability, data privacy, and data repatriation.
- Selecting the governing body,
Just like an HOA on the cloud, if you’re public or private, there are specific laws and regulations, and the related regulatory guidance and requirements that can affect an organization. From HIPAA, GLBA, and PCI DSS — your organization will need to examine the ins and outs of each to figure out what security controls are already in place and what’s needed to get the rest up to code.
- Preparing for home inspection,
Once up to code, however, it’s important to understand that it will be necessary, even required, to assess the control state for the cloud service several times a year — on a regular basis. For example, PCI DSS requires quarterly vulnerability scans be conducted for systems.
- Selecting the mortgage
Living on the cloud requires some long-term commitment. Is your neighborhood the place where your data can grow old? Are you still going to be able to meet compliance as your company grows or shrinks? What about the economy? (Peacock, 2011)
With these in consideration, there was no question that making the move to the cloud deserved some serious consideration, planning, and resources to be applied. As this discussion continued, our CIO also chimed in with two frames of reference of which to view compliance.
“I am a firm believer that all systems benefit from a diversified perspective. Therefore, based on the recommendation provided by Killmeyer and Windley, we understand that there are two important points here we needed to consider.” He was right. Both experts he referenced were subjecting their own personal view of how to manage security effectively. In Killmeyer’s view the business drives the security management process more than Windley who supported his technology end. Both perspectives are important and need to be taken into consideration when implementing. Overall, this will minimize risk and increase our changes of a successful migration to the cloud.
With that in mind, it was time to go back and suggest that we form our Security Team who would help to oversee the cloud migration process. As Killmeyer notes, “The Security Team should be involved in reviewing the results of all audit, control, or security reviews that occur within the organization. The Security Team is tasked with understanding why the results may not have been so spectacular and what was the systemic reason for lax or ineffective controls. The team responds to these results by assessing the policies, standards, and procedures that have been implemented and determining whether they are realistic and can be achieved with the resources at hand. If they cannot, it is the responsibility of the Security Team to communicate to the Board of Directors or executive-level management and make them aware of the risks and attempt to obtain the necessary resources to improve the architecture” (Killmeyer, 2006).
Brilliant. With a team in place and a more defined strategy for compliance. It finally came down to defining security responsibilities for each individual with the organization and communicating those throughout the organization. Thus, as Killmeyer noted to us, that process implementation should include:
- Providing the necessary resources such as hiring appropriate personnel to be able to execute the responsibilities that have been defined
- Providing the resources to train personnel to perform those responsibilities effectively
- Developing weekly, monthly, and quarterly meetings to discuss security issues and concerns; and make progress with the ISA as well as understanding where in the security life cycle the organization stands
- Enforcing the policies, standards, and procedures that have been developed
- Educating all users throughout the organization on security through security awareness training
- Purchasing and installation of hardware and software tools to effectively assess, monitor, and alert the security teams of potential security breaches and issues
- Providing the necessary financial, personnel, and time resources to improve the organization’s processing environment by reducing risk and addressing the security concerns that have been discovered in the assessment phase.
Clearly, this would set us up well for getting to the maintenance phase, and as my colleague Chuck would say, “we can always maintenance one more system.” Perhaps Chuck, but as I heard the seat belt sign come on, there was clearly some great ideas I had to add to the Security Team, we had a good implementation strategy in place, and we could now see the world through a solid compliance structure. Indeed, it was going to be a great journey into the cloud.
Reference Page
Active Directory Management, Easing Cloud Concerns with Federated Identity, Retrieved March 14, 2011., http://activedirectorymanagement.com/ease-cloud-security-concerns-with-federated-identity-windows-it-pro/
Killmeyer, Jan. (2006). Information Security Architecture: An Integrated Approach to Security in the Organization, Second Edition. Auerbach Publications.
Peacock, M. Top Considerations of Compliance in the Cloud, Retrieved March 14, 2011.,
http://www.cmswire.com/cms/enterprise-cms/top-considerations-for-compliance-in-the-cloud-006474.php
Smith, Laura. Federated identity management urgently needed in the cloud, Retrieved March 14, 2011., http://searchcio.techtarget.com/news/2240033256/Federated-identity-management-urgently-needed-in-the-cloud
Staff, Aspatore Books., (2005). Inside the Minds: Winning Legal Strategies for Corporate Governance: Leading Lawyers on Effective Programs for Understanding Regulations, Maintaining Compliance, and Avoiding Liability. Aspatore Books.
Tech Republic, Cloud Computing Essentials For Security And Availability, Retrieved March 14, 2011.,
Tipton, Harold F., & Krause, Micki. (2007). Information Security Management Handbook, Sixth Edition. Auerbach Publications.
Windley, Phillip, (2005). Digital Identity, O-Reilly: Bejing.
1 Comment