This document discusses implementing cloud computing capabilities in JCISA to improve information sharing and collaboration. It provides an overview of cloud computing concepts including definitions, service models, and deployment models. It then evaluates three courses of action for JCISA: doing nothing and letting "big Army" direct implementation; optimizing legacy systems to facilitate a future private or hybrid cloud; or immediately implementing a cloud regardless of Army efforts. The document analyzes requirements, service level agreements, comparisons of the courses of action, and ultimately recommends optimizing legacy systems to support future migration to a private or hybrid cloud.

1. JCISA Multi-National Information Sharing & Collaboration Cloud Earl J Britt Minnie Y Britt

2. Agenda Part 1 - Cloud computing overview Part 2 - Implementing Cloud Computing in JCISA decision brief

3. Part 1Cloud Computing Overview Earl Britt, JCISA Minnie Britt, MEDCOM

4. NIST Definition of Cloud Computing a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model promotes availability and is composed of five essential characteristics, three service models, and four deployment models.

5. Five Essential Characteristics of Cloud Computing 1. 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. 2. 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). 3. 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. Examples of resources include storage, processing, memory, network bandwidth, and virtual machines.

6. Five Essential Characteristics of Cloud Computing 4. 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. 5. 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.

7. Three Cloud Computing Service Models 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. 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).

8. Four Cloud Computing Deployment Models 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. 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. 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).

9. The NIST Cloud Definition Framework Hybrid Clouds Deployment Models Community Cloud PublicCloud PrivateCloud Service Models Software as a Service (SaaS) Platform as a Service (PaaS) Infrastructure as a Service (IaaS) Essential Characteristics On Demand Self-Service Broad Network Access Rapid Elasticity Resource Pooling Measured Service 9

11. Web 2.0 Computing Environment

12. Web application frameworks

13. Service Level Agreements10

14. Part 2 Implementing Cloud Computing in JCISA Earl Britt, JCISA Minnie Britt, MEDCOM

15. Why migrate to Cloud Computing? Army is accepting proposals for Area Processing Centers / Army Private Cloud (APC2) JCISA needs to participate in the coming change Lead, follow or get out of the way

16. Requirement Continue to virtualize JCISA data centers Expand the capability to exchange information in more formats with US Allies (including ROK and UNC-K) Migrate existing information sharing and collaboration capability to Cloud from legacy stove pipe client server applications.

17. Capability/Challenge/Solution Problem – collaboration and information sharing ROK – US , US – ROK. Applications: Share Point, email, web, UAV video, VTC, Video chat, chat, whiteboard, Google search, translation, Project Mgt Application. Currently – stove pipe client server applications display information that needs to be shared. IT O&M is Consolidated (Contractor) HW Requirements already virtualized (IaaS, PaaS)

18. Customer/Consumer Government, Military (US & ROK), contractor Information Sharing and collaboration Units that deploy to ROK for contingency need to be integrated into the Command & Control (C2) information sharing infrastructure.

19. Deployment Models Considered Private Hybrid Cloud Community Cloud Cannot be Public Cloud – Classified

20. Current Network & System Characteristics MAC I Classified Security Controls per DoDI 8500.2 STIG Compliance IAVM Compliance, scanning and monitoring Host Based Security System Redundancy CND SP to audit and monitor system, network and sensor logs >>> Cloud Audit

21. Legacy Characteristics Managing several workstation builds Managing several server architectures GCCS-A MS Data Center - Email, Web, File & SharePoint services Continue to implement virtual servers in Data Center with VM ESX Clustering

22. Robust Legacy Security Access and Authentication No trusts between enclaves Performance and Security monitoring Legacy Redundancy

23. Benefits/Challenges of Cloud Computing Make information sharing workstation agnostic No savings in IaaS or PaaS Build SaaS that can be accessed by agnostic workstations/devices

24. Courses of Action COA 1: Do nothing. Let big Army direct implementation. COA 2: Optimize legacy systems and applications to facilitate implementation of APC2 in JCISA COA 3: Implement Cloud in JCISA regardless of Army efforts.

25. Life Cycle Costs

26. Service Level Agreements (SLA) Determine SLA for each requirement for each COA (if required). Should include: What are the Critical Metrics? Define Parties (Customers & Providers) Service Definitions – what is the service that is required? Resource , Composite or business Metrics Service Level Objectives Obligations should the objective not be met

27. SLA Requirements Security Data Encryption Privacy Data Retention & Deletion HW Erasure & Destruct Regulatory Compliance Transparency Certification Monitoring Audit ability Metrics Machine-Readable SLAs Human Interaction Reliability

28. Requirements R1 - Security R2 - Interoperability R3 - Portability / Flexibility R4 - Disaster Recovery R5 - High Availability R6 - High Performance R7 - Data Storage Scalability R8 - Virtualization R9 - Redundancy R10 - Fault Tolerance R11 - Investment Cost R12 - O&M Costs

29. Comparison of COAs

30. Recommendation COA 2 Stand up SaaS Migrate to Cloud Rationale: Big Army has RFP to move enterprise to Cloud for SIPR, NIPR and Coalition networks. Should Pay for big ticket items. Implement Cloud enabling projects. Support USFK Transformation.

31. Questions?