Attachment_J-8_Definitions.pdf
PDF 35 KB Posted
- Attached to
- JEDI Cloud RFP Federal contract opportunity
- Solicitation number
- HQ003418R0077_JEDI_CLOUD_RFP
- Issued by
- DOD Washington Headquarters Service
About this file
Attachment J-8 : Definitions
View the file
Other files for this federal contract opportunity
Show all 50
JEDI Cloud RFP has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment J-8 Joint Enterprise Defense Infrastructure (JEDI) Cloud
JEDI Cloud Definitions Updated 23 July 2018
1 Purpose
While other definitions of these terms and acronyms may exist, these are the specific definitions that apply to the JEDI Cloud requirement unless a particular JEDI Cloud document defines the term otherwise, in which case the other document is controlling.
2 Definitions
1. Account - See JEDI Cloud Cyber Security Plan.
2. Addressing - See JEDI Cloud Cyber Security Plan.
3. Administrative Access - See JEDI Cloud Cyber Security Plan.
4. Artificial Intelligence (AI) - A system capable of rationally solving complex problems or taking appropriate actions to achieve its goals in whatever contextual circumstances it encounters.
5. Allocation - See JEDI Cloud Cyber Security Plan.
6. Antifragile - See JEDI Cloud Cyber Security Plan.
7. Application Programming Interface (API) - A system that supports modern protocols such as HTTPS for the purpose of machine-to-machine data transmission, both for reading and writing data.
8. Application - See JEDI Cloud Cyber Security Plan.
9. Application Server - Physical infrastructure where the end user loads a commodity operating system and at least two application runtimes into a virtualized environment hosted on the physical servers (for example, a network router would not satisfy this definition of application server).
10. AT-AT - The DoD's provisioning tool, known as the Account Tracking and Automation Tool (AT-AT), will manage user identity, access control, billing configuration, and security and configuration policy compliance for the purposes of accessing the JEDI
Cloud. All automation and integration will be centrally managed by the CCPO.
11. Availability Zones / Regions - Availability zones have independent power and network backbone. A “region” of a cloud service provider would encompass multiple availability zones such that systems and data in a region with a failed availability zone could seamlessly transfer to another zone and continue operation.
12. Bring Your Own License (BYOL) - The ability of a JEDI Cloud user to deploy software or platform offerings from the online marketplace into JEDI Cloud without additional licensing cost for that software or platform offering because the JEDI Cloud user already possesses a valid license from a separate contracting action.
13. Classified infrastructure - See JEDI Cloud Cyber Security Plan.
14. Classified media - Any device which is capable of storing data used in classified infrastructure.
15. Closed-loop system - System that is able to operate with no external connectivity.
16. Cloud - The practice of pooling physical servers and using them to provide services that can be rapidly provisioned with minimal effort and time, often over the Internet. The term is applied to a variety of different technologies (often without clarifying modifiers), but, for the purpose of this document, cloud refers to physical computing and storage resources pooled to provide virtual computing, storage, or higher-level services.
17. Cloud Boundary - Physical boundary between the JEDI Cloud and any external systems, or networks.
18. Commercial cloud - Means that a commercial cloud service provider is maintaining, operating, and managing the computing, networking, and storage resources that are being made available to customers. Depending on the contract, the commercial cloud service provider may be performing in commercial facilities or on premises.
19. Commercial Cloud Offering (CCO) - Defined as the IaaS and PaaS offerings that are publicly-available and currently sold in the commercial marketplace, but excluding any Software as a Service (SaaS) offerings.
20. Commercial Parity - Equivalency of the services and capabilities offered between the JEDI Cloud and the contractor’s publicly-available commercial cloud in the continental
United States.
21. Cryptographic certainty - See JEDI Cloud Cyber Security Plan.
22. CSP - Cloud Service Provider or Cyber Security Plan depending on context.
23. Data center - See JEDI Cloud Cyber Security Plan.
24. Elastic - Capabilities that can be provisioned and released to scale outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be provisioned in any quantity at any time.
25. Erase - Apply logical techniques to sanitize data in all addressable storage locations for protection against simple non-invasive data recovery techniques; typically applied through the standard Read and Write commands to the storage device, such as by rewriting with a new value or using a menu option to reset the device to the factory state (where rewriting is not supported). The term Clear in NIST SP 800-88 Revision 1 is similarly defined.
26. Failover - See JEDI Cloud Cyber Security Plan.
27. Federated identity - an assured process that allows for the conveyance of authentication and subscriber attribute information across networked systems, in this case between the CCO vendor’s identity management system and DoD systems.
28. Hypervisor - a collection of software modules that provides virtualization of hardware resources (such as CPU/GPU, Memory, Network and Storage) on a single physical host.
29. Impact Level 5 (IL5) - See JEDI Cloud Cyber Security Plan.
30. Impact Level 6 (IL6) - See JEDI Cloud Cyber Security Plan.
31. Infrastructure - See JEDI Cloud Cyber Security Plan.
32. Infrastructure as a Service (IaaS) - The capability provided to the consumer 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).
33. Investigation - See JEDI Cloud Cyber Security Plan.
34. IV&V Testing - Independent Verification & Validation. An independent system assessment that analyzes and test the target system to 1) ensure that it performs its intended functions correctly, 2) ensure that it performs no unintended functions, and 3) measure its quality and reliability.
35. Logical Separation - See JEDI Cloud Cyber Security Plan.
36. Machine Learning (ML) - a statistical process that starts with a body of data and tries to derive a rule or procedure that explains the data or can predict future data rather than programming specific rules to explain data or predict future data.
37. Migration - the act of moving an application from one infrastructure or platform to another infrastructure or platform.
38. Mitigation - See JEDI Cloud Cyber Security Plan.
39. Meet Me Point (MMP) - A connection to or from the DoDIN or other DoD networks from the cloud service provider.
40. Nearline storage - Storage not immediately available, but can be brought online quickly without human intervention.
41. Network - See JEDI Cloud Cyber Security Plan.
42. Offline Storage - Data not immediately available, requiring some human or scheduled intervention to become online. Also known as Cold Storage.
43. Online storage - Storage that is immediately accessible to applications without human intervention.
44. Platform as a Service (PaaS) - The capability provided through software, on top of an
IaaS solution, that allows the consumer to replicate, scale, host, and secure consumer-created or acquired applications on the cloud infrastructure. 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.
45. Points of Presence - A demarcation point or interface point between communicating entities.
46. Provisioning - In the context of the JEDI Cloud contract, “provisioning” is the act of creating something in the cloud environment (e.g., accounts, compute instances, users, storage mechanisms) in either a manual or automated fashion.
47. Purge - Apply physical or logical techniques that render data recovery infeasible using state of the art laboratory techniques.
48. 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 re-assigned according to consumer demand. There is a sense of location independence 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, and network bandwidth.
49. Robust Infrastructure - Assured infrastructure that is responsive, resilient, redundant, and reliable.
50. Role - A job function, with associated privileges, to which people or other system entities may be assigned in a system.
51. Ruggedized - System specifically designed to meet or exceed MIL-STD-810G standards to ensure reliable operations in harsh usage conditions. Whether the system needs to be tested and certified as meeting the standard is at the discretion of the Government.
52. Self-service - The ability of an end-user to access data and perform actions without any human interaction or third party approval.
53. Server - See JEDI Cloud Cyber Security Plan.
54. 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.
55. Tactical Edge - Environments covering the full range of military operations, including, but not limited to forces deployed in support of a Geographic Combatant Commander or applicable training exercises, on various platforms (e.g., dismounted infantry patrol, forward operating base, and aircraft carrier) and with the ability to operate in austere and connectivity-deprived environments.
56. Tactical Edge Device - Durable and portable computing and storage capability able to operate in the tactical edge.
57. Testing - See JEDI Cloud Cyber Security Plan.
58. Traffic - See JEDI Cloud Cyber Security Plan.
59. Unclassified infrastructure - See JEDI Cloud Cyber Security Plan.
60. User - Provisioned identity able to manage infrastructure.
61. U.S. Person - The term “United States person” means any United States citizen, any alien lawfully admitted for permanent residence in the United States, and any corporation, partnership, or other organization organized under the laws of the United States that is not under the control of a foreign government.
62. Virtual Enclave - On-demand configurable pool of shared computing and storage resources within a multi-tenant cloud environment that is logically isolated from other tenants.
63. Virtual Machine (VM) - Software that emulates the physical hardware of a computer.
64. Vulnerability - See JEDI Cloud Cyber Security Plan.
File details come from the government source that posted it.