RSA: CSA GRC Stack Update for the CSA Atlanta Chapter
Upcoming SlideShare
Loading in...5

RSA: CSA GRC Stack Update for the CSA Atlanta Chapter



RSA CSA GRC Stack Update for the Atlanta CSA Chapter by Phil Agcaoili

RSA CSA GRC Stack Update for the Atlanta CSA Chapter by Phil Agcaoili



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • On-demand self-service. A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service’s provider.Broad network access. Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).Resource pooling. The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of locationindependence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, network bandwidth, and virtual machines.Rapid elasticity. Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out, and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.Measured Service. Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.
  • Cloud Software as a Service (SaaS). The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.Cloud Platform as a Service (PaaS). The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations, typically through a pay-per-use business model.Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
  • Private cloud. The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.Community cloud. The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise.Public cloud. The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds).
  • The NIST Security Content Automation Protocol (SCAP) Validation Program (SCAP) is designed to test the ability of products to use the features and functionality available through SCAP and its component standards.XBRL (eXtensible Business Reporting Language) is a freely available, standards-based way to communicate and exchange business information between business systems.
  • Do visit the websiteDo join the LinkedIn Groups – you will receive regular email updates

RSA: CSA GRC Stack Update for the CSA Atlanta Chapter RSA: CSA GRC Stack Update for the CSA Atlanta Chapter Presentation Transcript

  • RSA: Cloud Security AllianceGRC Stack Update
    Cloud Security Alliance, Atlanta Chapter
    Phil Agcaoili, Cox Communications
    Dennis Hurst, HP
    March 2011
  • Cloud ComputingNIST Definition
    UPDATED (Jan 2011) – National Institute of Standards and Technology (NIST) Special Publication 800-145 (Draft)
    Model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services)
    Rapidly provisioned and released with minimal management effort or service provider interaction
    Composed of 5 essential characteristics, 3 service models, and 4 deployment models.
  • Cloud Computing5 Essential Characteristics
    On-demand tenant self-service model for provisioning computing capabilities (server time, network storage, etc.)
    Broad network access with capabilities over the network accessible by standard mechanisms and mobile platforms
    Resource pooling through dynamically assigned physical and virtual capabilities delivered in a multi-tenant model and location independent
    Rapid elasticity of provisioned resources automatically or manually adjusted aligned with service level flexibility and needs
    Measured service to monitor, control and report on transparent resource optimization
  • Cloud Computing3 Service Models
    Software as a Service (SaaS)
    Capability made available to tenant (or consumer) to use provider’s applications running on cloud infrastructure, accessible via web browser, mobile apps, and system interfaces.
    Examples:, Drop Box,, Google Docs, WebEx
    Platform as a Service (PaaS)
    Capability made available to tenant to deploy tenant owned (created or acquired) applications using programming languages and tools supported by provider.
    Examples: Microsoft Azure, Amazon Web Services, Bungee Connect
    Infrastructure as a Service (IaaS) / Datacenter as a Service (DaaS)
    Capability made available to tenant to provision processing, storage, networks or other fundamental computing resources to host and run tenant’s applications.
    Examples: Rackspace, Terremark (Verizon), Savvis, AT&T
  • Cloud Computing4 Deployment Models
    (4) HYBRID
    • Composition of 2 or more deployment models that remain unique entities
    • Bound together by standardized or proprietary technology enabling data and application portability
  • Cloud ComputingSecurity: Largest Barrier to Adoption
  • What is Different about Cloud?
  • What is Different about Cloud?
  • What is Different about Cloud?
  • Proposal for Atlanta Chapter Objective #1: Cloud Security Contract Template
    Vendor and Customer Needs:
    A simple, but uniform security contract and questionnaire/checklist
    Standard/uniform customer response
    Minimizes unique customer requests
    Provide basic security attestation and assurance
  • What is Different about Cloud?
  • What is Different about Cloud?
  • Cloud Controls Matrix
  • Cloud Controls Matrix
    Leadership Team
    • Becky Swain – Cisco Systems, Inc.
    • Philip Agcaoili – Cox Communications
    • Marlin Pohlman – EMC, RSA
    • Kip Boyle – CSA
    V1.1 Released Dec 2010
    Rated as applicable to S-P-I with Cloud Provider / Tenant Delineation
    Controls baselined and mapped to:
    ISO/IEC 27001-2005
    PCI DSSv2.0
    BITS Shared Assessments
  • Cloud Controls MatrixGlobal Industry Contribution
    • AdalbertoAfonso A Navarro F do Valle – Deloitte LLP
    • Addison Lawrence – Dell
    • Akira Shibata – NTT DATA Corp
    • Andy Dancer
    • Anna Tang – Cisco Systems, Inc.
    • April Battle – MITRE
    • ChandrasekarUmpathy
    • Chris Brenton – Dell
    • Dale Pound – SAIC
    • Daniel Philpott – Tantus Technologies
    • Dr. Anton Chuvakin – Security Warrior Consulting
    • Elizabeth Ann Wickham – L47 Consulting Limited
    • Gary Sheehan – Advanced Server Mgmt Group, Inc.
    • Georg Heß
    • Georges Ataya Solvay – Brussels School of Economics & Mgmt
    • Glen Jones – Cisco Systems, Inc.
    • Greg Zimmerman – Jefferson Wells
    • Guy Bejerano - LivePerson
    • Henry Ojo – Kamhen Services Ltd,
    • Jakob Holm Hansen – Neupart A/S
    • Joel Cort – Xerox Corporation
    • John DiMaria – HISPI
    • John Sapp – McKesson Healthcare, HISPI
    • Joshua Schmidt – Vertafore, Inc.
    • KarthikAmrutesh – Ernst and Young LLP
    • Kelvin Arcelay – Arcelay& Associates
    • Kyle Lai – KLC Consulting, Inc.
    • Larry Harvey – Cisco Systems, Inc.
    • Laura Kuiper – Cisco Systems, Inc.
    • Lisa Peterson – Progressive Insurance
    • Lloyd Wilkerson – Robert Half International
    • Marcelo Gonzalez – Banco Central Republica Argentina
    • Mark Lobel – PricewaterhouseCoopers LLP
    • Meenu Gupta – Mittal Technologies
    • Mike Craigue, Ph.D. – Dell
    • MS Prasad, Exec Dir CSA India
    • Niall BrowneI – LiveOps
    • Patrick Sullivan
    • Patty Williams – Symetra Financial
    • Paul Stephen – Ernst and Young LLP
    • Phil Genever-Watling - Dell
    • Philip Richardson – Logicalis UK Ltd
    • PritamBankar – Infosys Technologies Ltd.
    • RamesanRamani – Paramount Computer Systems
    • Steve Primost
    • TaiyeLambo – eFortresses, Inc .
    • Tajeshwar Singh
    • Thej Mehta – KPMG LLP
    • Thomas Loczewski – Ernst and Young GmbH, Germany
    • Vincent Samuel – KPMG LLP
    • Yves Le Roux – CA Technologies
    • HISPI membership (Release ISO Review Body)
  • Cloud Controls MatrixCharacteristics
    • Objective measure to monitor activities and then take corrective action to accomplish organizational goals.
    • Comprised of a set of policies and processes (internal controls) affecting the way Cloud services are directed, administered or controlled.
    • Aligned to Information Security regulatory rules and industry accepted guidance.
    • Controls reflect the intent of the CSA Guidance as applied to existing patterns of Cloud execution.
  • Cloud Controls MatrixOptimal & Holistic Compliance
    Bridging Regulatory Governance And Practical Compliance
  • Cloud Controls Matrix11 Domains
    1. Compliance (CO)
    2. Data Governance (DG)
    3. Facility Security (FS)
    4. Human Resources (HR)
    5. Information Security (IS)
    6. Legal (LG)
    7. Operations Management (OM)
    8. Risk Management (RI)
    9. Release Management (RM)
    10. Resiliency (RS)
    11.Security Architecture (SA)
  • Cloud Controls Matrix98 Controls
    • CO01 – Audit Planning
    • CO02 – Independent Audits
    • CO03 – Third Party Audits
    • CO04 – Contact / Authority Maintenance
    • CO05 – Information System Regulatory Mapping
    • CO06 – Intellectual Property
    • LG01 - Non-Disclosure Agreements
    • LG02 - Third Party Agreements
    Data Governance
    • DG01 – Ownership / Stewardship
    • DG02 – Classification
    • DG03 – Handling / Labeling / Security Policy
    • DG04 – Retention Policy
    • DG05 – Secure Disposal
    • DG06 – Non-Production Data
    • DG07 – Information Leakage
    • DG08 – Risk Assessments
    Risk Management
    • RI01 – Program
    • RI02 – Assessments
    • RI03 – Mitigation / Acceptance
    • RI04 – Business / Policy Change Impacts
    • RI05 – Third Party Access
  • Cloud Controls Matrix98 Controls (cont.)
    • RS01 – Management Program
    • RS02 – Impact Analysis
    • RS03 – Business Continuity Planning
    • RS04 – Business Continuity Testing
    • RS05 – Environmental Risks
    • RS06 – Equipment Location
    • RS07 – Equipment Power Failures
    • RS08 – Power / Telecommunications
    Human Resources
    • HR01 – Background Screening
    • HR02 – Employment Agreements
    • HR03 – Employment Termination
    Release Management
    • RM01 – New Development / Acquisition
    • RM02 – Production Changes
    • RM03 – Quality Testing
    • RM04 – Outsourced Development
    • RM05 – Unauthorized Software Installations
    Operational Management
    • OP01 – Policy
    • OP02 – Documentation
    • OP03 – Capacity / Resource Planning
    • OP04 – Equipment Maintenance
  • Cloud Controls Matrix98 Controls (cont.)
    Security Architecture
    • SA01 – Customer Access Requirements
    • SA02 – User ID Credentials
    • SA03 – Data Security / Integrity
    • SA04 – Application Security
    • SA05 – Data Integrity
    • SA06 – Production / Non-Production Environments
    • SA07 – Remote User Multi-Factor Authentication
    • SA08 – Network Security
    • SA09 – Segmentation
    • SA10 – Wireless Security
    • SA11 – Shared Networks
    • SA12 – Clock Synchronization
    • SA13 – Equipment Identification
    • SA14 – Audit Logging / Intrusion Detection
    • SA15 – Mobile Code
    Facility Security
    • FS01 – Policy
    • FS02 – User Access
    • FS03 – Controlled Access Points
    • FS04 – Secure Area Authorization
    • FS05 – Unauthorized Persons Entry
    • FS06 – Off-Site Authorization
    • FS07 – Off-Site Equipment
    • FS08 – Asset Management
  • Cloud Controls Matrix98 Controls (cont.)
    Information Security
    • IS01 – Management Program
    • IS02 – Management Support / Involvement
    • IS03 – Policy
    • IS04 – Baseline Requirements
    • IS05 – Policy Reviews
    • IS06 – Policy Enforcement
    • IS07 – User Access Policy
    • IS08 – User Access Restriction / Authorization
    • IS09 – User Access Revocation
    • IS10 – User Access Reviews
    • IS11 – Training / Awareness
    • IS12 – Industry Knowledge / Benchmarking
    • IS13 – Roles / Responsibilities
    • IS14 – Management Oversight
    • IS15 – Segregation of Duties
    • IS16 – User Responsibility
    • IS17 – Workspace
    • IS18 – Encryption
    • IS19 – Encryption Key Management
    • IS20 – Vulnerability / Patch Management
    • IS21 – Anti-Virus / Malicious Software
    • IS22 – Incident Management
    • IS23 – Incident Reporting
    • IS24 – Incident Response Legal Preparation
    • IS25 – Incident Response Metrics
    • IS26 – Acceptable Use
    • IS27 – Asset Returns
    • IS28 – eCommerce Transactions
    • IS29 – Audit Tools Access
    • IS30 – Diagnostic / Configuration Ports Access
    • IS31 – Network Services
    • IS32 – Portable / Mobile Devices
    • IS33 – Source Code Access Restriction
    • IS34 – Utility Programs Access
  • Consensus Assessment Initiative
  • Consensus Assessment Initiative
    Research tools and processes to perform shared assessments of cloud providers
    Lightweight “common assessment criteria” concept
    Integrated with Controls Matrix
    Ver 1 CAI Questionnaire released Oct 2010, approx 140 provider questions to identify presence of security controls or practices
  • Consensus Assessment InitiativeTeam
    • Matthew Becker – Bank of America
    • Aaron Benson – Novell
    • Ken Biery – Verizon Business
    • Kristopher Fador – Bank of America
    • David Gochenaur – Aon Corporation
    • Jesus Molina – Fujitsu
    • John Nootens – AMA Association
    • HemmaPrafullchandra – Hytrust
    • GorkaSadowski – Log Logic
    • Richard Schimmel – Bank of America
    • Patrick Vowles – RSA
    • Kenneth Zoline – IBM
    • Laura Posey – Microsoft
    • Jason Witty – Bank of America
    • Marlin Pohlman – EMC, RSA
    • Earle Humphreys – ITEEx
    • Christofer Hoff – Cisco
  • Consensus Assessment InitiativeApproach
    • Build “cloud-specific” question-set
    • CSA guidance
    • Industry experts
    • Align questions with the CSA Cloud Controls Matrix
    • Release 1.0 question-set publically
    • Integrate into framework
    • Post to
  • Consensus Assessment Initiative Questionnaire (CAIQ) – 148 Qs
  • CloudAudit
  • CloudAudit
    Provide a common interface and namespace that allows cloud computing providers to automate the Audit, Assertion, Assessment, and Assurance (A6) of their environments
    Allow authorized consumers of services to do likewise via an open, extensible and secure interface and methodology.
  • CloudAuditObjective
    A structure for organizing assertions and supporting documentation for specific controls across different compliance frameworks in a way that simplifies discovery by humans and tools.
    Define a namespace that can support diverse frameworks
    Express five critical compliance frameworks in that namespace
    Define the mechanisms for requesting and responding to queries relating to specific controls
    Integrate with portals and AAA systems
  • CloudAuditAligned to Cloud Controls Matrix
    First efforts aligned to compliance frameworks as established by CSA Control Matrix:
    ISO/IEC 27001-2005
    Incorporate CSA’s CAI and additional CompliancePacks
    Expand alignment to “infrastructure” and “operations” -centric views also
  • CloudAuditSample Implementation
    CSA Compliance Pack
  • CloudAuditSample Implementation (cont.)
    CSA Compliance Pack
  • CloudAuditSample Implementation (cont.)
    CSA Compliance Pack
  • CloudAuditRelease Deliverables
    Contains all Compliance Packs, documentation and scripts needed to begin implementation of CloudAudit
    Working with Service Providers and Tool Vendors for Adoption
    Officially folded CloudAudit under the Cloud Security Alliance in October, 2010
  • CloudAuditRelease Deliverables (cont.)
    Request Flow for Users & Tools
  • CloudAuditRelease Deliverables (cont.)
    Index.html is for dumb browser consumptions
    Typically, the direct human user use case
    It can be omitted if directory browsing is enabled
    It contains JavaScript to look for the manifest.xml file, parse it, and display it as HTML.
    If no manifest.xml exists, it should list the directory contents relevant to the control in question
  • CloudAuditRelease Deliverables (cont.)
    Structured listing of control endpoints contents
    Can be extended to provide contextual information
    Primarily aimed at tool consumption
    In Atom format
  • CSA GRC Stack
  • CSA GRC Stack
    Bringing it all together to peel back the layers of control ownership and address concerns for trusted Cloud adoption.
    Provider Assertions
    Private, Community & Public Clouds
    Control Requirements
  • CSA GRC Stack
    • Whether implementing private, public or hybrid clouds, the shift to compute as a service presents new challenges across the spectrum of Governance, Risk Management and Compliance (GRC) requirements – success dependent upon:
    • Appropriate assessment criteria; and
    • Relevant control objectives and timely access to necessary supporting data.
    • CSA GRC Stack provides a toolkit for enterprises, cloud providers, security solution providers, IT auditors and other key stakeholders to instrument and assess both private and public clouds against industry established best practices, standards and critical compliance requirements.
    • Integrated suite of 3 CSA initiatives: CloudAudit, Cloud Controls Matrix (CCM) and Consensus Assessments Initiative Questionnaire (CAIQ).
    • Available now for free download at:
  • CSA GRC StackBringing it all together…
  • CSA GRC StackIndustry Collaboration & Support
    • International Organization for Standards (ISO)
    • ISO/IEC JTC 1 SC 27 (“SC 27”) WG 1, 4 and 5 in Study Period in the area of Cloud Computing Security and Privacy with active CSA representation
    • European Network and Information Security Agency (ENISA)
    • Common Assurance Maturity Model (CAMM)
    • American Institute of Certified Public Accountants (AICPA)
    • Statement on Standards for Attestation Engagements (SSAE) No. 16 SOC 2 – Service Organization Controls over Security, Confidentiality, Processing Integrity, Availability, and Privacy
    • National Institute of Standards and Technology (NIST)
    • Consolidated feedback on Federal Risk and Authorization Management Program (FedRAMP)
  • CSA GRC StackIndustry Collaboration & Support (cont.)
    • Inverse Control Framework Mappings
    • Health Information Trust Alliance (HITRUST)
    • Unified Compliance Framework (UCF)
    • Information Systems Audit and Control Association (ISACA)
    • BITS Shared Assessments SIG/AUP + TG Participation
    • Information Security Forum (ISF)
  • About the Cloud Security Alliance
  • About the Cloud Security Alliance
    Global, not-for-profit organization
    Almost 18,000 individual members, 80 corporate members
    Building best practices and a trusted cloud ecosystem
    Agile philosophy, rapid development of applied research
    GRC: Balance compliance with risk management
    Reference models: build using existing standards
    Identity: a key foundation of a functioning cloud economy
    Champion interoperability
    Advocacy of prudent public policy
    “To promote the use of best practices for providing security assurance within Cloud Computing, and provide education on the uses of Cloud Computing to help secure all other forms of computing.”
  • Contact
    Help us secure cloud computing
    Twitter: @cloudsa
  • Thank You