Attachment_J-8_Definitions_Amendment_0001.pdf

PDF 113 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 0001

View the file

Other files for this federal contract opportunity

Other files attached to JEDI Cloud RFP, newest first.
File Type Posted
Attachment_L-5_Price_Scenario_Price_Build-up_Template_Updated_.xlsx XLSX spreadsheet
Attachment_J-7_DD_Form_254,_DoD_Contract_Security_Classification_Specification_for_IDIQ_Amendment_0003_(1).pdf PDF
HQ0034-18-R-0077_0003_Change_Page.pdf PDF
Attachment_J-7_DD_Form_254,_DoD_Contract_Security_Classification_Specification_for_ID_IQ_Amendment_0002.pdf PDF
Attachment_L-2_Price_Scenarios_Amendment_0002.pdf PDF
HQ0034-18-R-0077_0002.pdf PDF
Amendment_0002_Summary_of_Changes.pdf PDF
JEDI_Cloud_Industry_and_Gov_QA_Final_RFP.pdf PDF
HQ0034-18-R-0077_0001.pdf PDF
Attachment_J-10_Small_Business_Participation_Commitment_Document_0001.pdf PDF
JEDI_Cloud_Comment_Resolution_Matrix_for_Amendment_0001.xlsx XLSX spreadsheet
Attachment_L-2_Price_Scenarios_Amendment_0001.pdf PDF
Amendment_0001_Summary_of_Changes.pdf PDF
Attachment_L-1_Statement_of_Objectives_Amendment_0001.pdf PDF
Oracle_Protest_Exhibits.pdf PDF
JEDI_CDRL_A001_-_Contract_Monthly_Progress_Report.pdf PDF
JEDI_CDRL_A002_-_Transition_Out_Plan.pdf PDF
JEDI_Cloud_Comment_Resolution_Matrix_for_Final_RFP.xlsx XLSX spreadsheet
JEDI_Cloud_Industry_and_Gov_QA_dRFP2.pdf PDF
JEDI_CDRL_A008_-_Contract_Ordering_Guide.pdf PDF
180510_Final_Cloud_Combined_Congressional_Report__vg7_PDF_Redacted.pdf PDF
Attachment_L-7_OCI_Analysis_Disclosure_Form.pdf PDF
DoD_CIO_RFP_Release_Letter_26_Jul.pdf PDF
CNSSP15.pdf PDF
Attachment_L-6__Small_Business_Subcontracting_Plan_Template.docx DOCX document
JEDI_CDRL_A011_-_Security_Authorization_Package.pdf PDF
Attachment_L-8_PWS-SOO_Crosswalk_Matrix.xlsx XLSX spreadsheet
JEDI_CDRL_A005_-_System_Administrator_Training_Material.pdf PDF
JEDI_CDRL_A010_-_Quality_Control_Plan.pdf PDF
JEDI_Single_Award_DF-USD(AS)__17July18.pdf PDF
JEDI_CDRL_A012_-_Technical_Report.pdf PDF
In-Person_Q&A_Session_Information.pdf PDF
JEDI_CDRL_A003_-_Contract_Security_Management_Plan.pdf PDF
HQ0034-18-R-0077.pdf PDF
Attachment_L-5_Price_Scenario_Price_Build-up_Template.xlsx XLSX spreadsheet
Attachment_L-3_Task_Order_001_PWS.pdf PDF
JEDI_CDRL_A006_-_Role-Based_User_Training_Materials.pdf PDF
MIL-STD-810G_CN1.pdf PDF
JEDI_CDRL_A014_-_Portability_Test.pdf PDF
JEDI_CDRL_A004_Technology_Refresh_Plan.pdf PDF
Attachment_L-4_Task_Order_002_PWS.pdf PDF
Attachment_L-9__Company_Non-Disclosure_Agreement_for_JEDI_Cloud.pdf PDF
Attachment_J-8_Definitions.pdf PDF
JEDI_CDRL_A007_-_Portability_Plan.pdf PDF
Attachment_J-10__Small_Business_Participation_Commitment_Document.pdf PDF
Attachment_J-7_Form_DD254.pdf PDF
Attachment_J-6_JEDI_Cyber_Security_Plan.pdf PDF
JEDI_CDRL_A015_-_Task_Order_Monthly_Progress_Report.pdf PDF
JEDI_CDRL_A013_-_Small_Business_Reporting.pdf PDF
JEDI_CDRL_A016_-_Meeting_Materials.pdf PDF
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 1 Joint Enterprise Defense Infrastructure (JEDI) Cloud 2

JEDI Cloud Definitions 3 Updated 22 August 2018 4

1 Purpose 5 While other definitions of these terms and acronyms may exist, these are the specific 7 definitions that apply to the JEDI Cloud requirement unless a particular JEDI Cloud document 8 defines the term otherwise, in which case the other document is controlling. 9 2 Definitions 11

1. Account - See JEDI Cloud Cyber Security Plan. 13

2. Addressing - See JEDI Cloud Cyber Security Plan. 15

3. Administrative Access - See JEDI Cloud Cyber Security Plan. 17

4. Artificial Intelligence (AI) - A system capable of rationally solving complex problems 19 or taking appropriate actions to achieve its goals in whatever contextual circumstances it 20 encounters. 21

5. Allocation - See JEDI Cloud Cyber Security Plan. 23

6. Antifragile - See JEDI Cloud Cyber Security Plan. 25

7. Application Programming Interface (API) - A system that supports modern protocols 27 such as HTTPS for the purpose of machine-to-machine data transmission, both for 28 reading and writing data. 29

8. Application - See JEDI Cloud Cyber Security Plan. 31

9. Application Server - Physical infrastructure where the end user loads a commodity 33 operating system and at least two application runtimes into a virtualized environment 34 hosted on the physical servers (for example, a network router would not satisfy this 35 definition of application server). 36

10. AT-AT - The DoD's provisioning tool, known as the Account Tracking and Automation 38 Tool (AT-AT), will manage user identity, access control, billing configuration, and 39 security and configuration policy compliance for the purposes of accessing the JEDI 40

Cloud. All automation and integration will be centrally managed by the CCPO. 41

11. Availability Zones / Regions - Availability zones have independent power and network 43 backbone. A “region” of a cloud service provider would encompass multiple availability 44 zones such that systems and data in a region with a failed availability zone could 45 seamlessly transfer to another zone and continue operation. 46

12. Bring Your Own License (BYOL) - The ability of a JEDI Cloud user to deploy 48 software or platform offerings from the online marketplace into JEDI Cloud without 49 additional licensing cost for that software or platform offering because the JEDI Cloud 50 user already possesses a valid license from a separate contracting action. 51

13. Classified infrastructure - See JEDI Cloud Cyber Security Plan. 53

14. Classified media - Any device which is capable of storing data used in classified 55 infrastructure. 56

15. Closed-loop system - System that is able to operate with no external connectivity. 58

16. Cloud - The practice of pooling physical servers and using them to provide services that 60 can be rapidly provisioned with minimal effort and time, often over the Internet. The term 61 is applied to a variety of different technologies (often without clarifying modifiers), but, 62 for the purpose of this document, cloud refers to physical computing and storage 63 resources pooled to provide virtual computing, storage, or higher-level services. 64

17. Cloud Boundary - Physical boundary between the JEDI Cloud and any external systems, 66 or networks. 67

18. Commercial cloud - Means that a commercial cloud service provider is maintaining, 69 operating, and managing the computing, networking, and storage resources that are being 70 made available to customers. Depending on the contract, the commercial cloud service 71 provider may be performing in commercial facilities or on premises. 72

19. Commercial Cloud Offering (CCO) - Defined as the IaaS and PaaS offerings that are 74 publicly-available and currently sold in the commercial marketplace, but excluding any 75 Software as a Service (SaaS) offerings. 76

20. Commercial Parity - Equivalency of the services and capabilities offered between the 78 JEDI Cloud and the contractor’s publicly-available commercial cloud in the continental 79

United States. 80

21. Cryptographic certainty - See JEDI Cloud Cyber Security Plan. 82

22. CSP - Cloud Service Provider or Cyber Security Plan depending on context. 84

23. Data center - See JEDI Cloud Cyber Security Plan. 86

24. Direct fiber link - A connection between two locations such that any traffic flowing 88 between those locations transverses only dedicated channels or circuits, and not the 89 Internet or other publically shared infrastructure. 90

25. Elastic - Capabilities that can be provisioned and released to scale outward and inward 92 commensurate with demand. To the consumer, the capabilities available for provisioning 93 often appear to be unlimited and can be provisioned in any quantity at any time. 94

26. Erase - Apply logical techniques to sanitize data in all addressable storage locations for 96 protection against simple non-invasive data recovery techniques; typically applied 97 through the standard Read and Write commands to the storage device, such as by 98 rewriting with a new value or using a menu option to reset the device to the factory state 99 (where rewriting is not supported). The term Clear in NIST SP 800-88 Revision 1 is 100 similarly defined. 101

27. Failover - See JEDI Cloud Cyber Security Plan. 103

28. Federated identity - an assured process that allows for the conveyance of authentication 105 and subscriber attribute information across networked systems, in this case between the 106 CCO vendor’s identity management system and DoD systems. 107

29. Hypervisor - a collection of software modules that provides virtualization of hardware 109 resources (such as CPU/GPU, Memory, Network and Storage) on a single physical host. 110

30. Impact Level 5 (IL5) - See JEDI Cloud Cyber Security Plan. 112

31. Impact Level 6 (IL6) - See JEDI Cloud Cyber Security Plan. 114

32. Infrastructure - See JEDI Cloud Cyber Security Plan. 116

33. Infrastructure as a Service (IaaS) - The capability provided to the consumer to 118 provision processing, storage, networks, and other fundamental computing resources 119 where the consumer is able to deploy and run arbitrary software, which can include 120 operating systems and applications. The consumer does not manage or control the 121 underlying cloud infrastructure but has control over operating systems, storage, deployed 122 applications, and possibly limited control of select networking components (e.g., host 123 firewalls). 124

34. Investigation - See JEDI Cloud Cyber Security Plan. 126

35. IV&V Testing - Independent Verification & Validation. An independent system 128 assessment that analyzes and test the target system to 1) ensure that it performs its 129 intended functions correctly, 2) ensure that it performs no unintended functions, and 3) 130 measure its quality and reliability. 131

36. Logical Separation - See JEDI Cloud Cyber Security Plan. 133

37. Machine Learning (ML) - a statistical process that starts with a body of data and tries to 135 derive a rule or procedure that explains the data or can predict future data rather than 136 programming specific rules to explain data or predict future data. 137

38. Migration - the act of moving an application from one infrastructure or platform to 139 another infrastructure or platform. 140

39. Mitigation - See JEDI Cloud Cyber Security Plan. 142

40. Meet Me Point (MMP) - A connection to or from the DoDIN or other DoD networks 144 from the cloud service provider. 145

41. Nearline storage - Storage not immediately available, but can be brought online quickly 147 without human intervention. 148

42. Network - See JEDI Cloud Cyber Security Plan. 150

43. Offline Storage - Data not immediately available, requiring some human or scheduled 152 intervention to become online. Also known as Cold Storage. 153

44. Online storage - Storage that is immediately accessible to applications without human 155 intervention. 156

45. Platform as a Service (PaaS) - The capability provided through software, on top of an 158

IaaS solution, that allows the consumer to replicate, scale, host, and secure consumer-159 created or acquired applications on the cloud infrastructure. The consumer does not 160 manage or control the underlying cloud infrastructure including network, servers, 161 operating systems, or storage, but has control over the deployed applications and possibly 162 application hosting environment configurations. 163

46. Points of Presence - A demarcation point or interface point between communicating 165 entities. For purposes of JEDI Cloud, this is intended to be a network access point under 166 the Offeror's control, as defined in Section C4 of the RFP/resulting contract, where JEDI 167 Cloud is accessible to DoD. 168

47. Provisioning - In the context of the JEDI Cloud contract, “provisioning” is the act of 170 creating something in the cloud environment (e.g., accounts, compute instances, users, 171 storage mechanisms) in either a manual or automated fashion. 172

48. Purge - Apply physical or logical techniques that render data recovery infeasible using 174 state of the art laboratory techniques. 175

49. Resource pooling - The provider’s computing resources are pooled to serve multiple 177 consumers using a multi-tenant model, with different physical and virtual resources 178 dynamically assigned and re-assigned according to consumer demand. There is a sense of 179 location independence in that the customer generally has no control or knowledge over 180 the exact location of the provided resources but may be able to specify location at a 181 higher level of abstraction (e.g., country, state, or datacenter). Examples of resources 182 include storage, processing, memory, and network bandwidth. 183

50. Robust Infrastructure - Assured infrastructure that is responsive, resilient, redundant, 185 and reliable. 186

51. Role - A job function, with associated privileges, to which people or other system entities 188 may be assigned in a system. 189

52. Ruggedized - System specifically designed to meet or exceed MIL-STD-810G standards 191 to ensure reliable operations in harsh usage conditions. Whether the system needs to be 192 tested and certified as meeting the standard is at the discretion of the Government. 193

53. Self-service - The ability of an end-user to access data and perform actions without any 195 human interaction or third party approval. 196

54. Server - See JEDI Cloud Cyber Security Plan. 198

55. Software as a Service (SaaS) - The capability provided to the consumer is to use the 200 provider’s applications running on a cloud infrastructure. The applications are accessible 201 from various client devices through a thin client interface such as a web browser (e.g., 202 web-based email). The consumer does not manage or control the underlying cloud 203 infrastructure including network, servers, operating systems, storage, or even individual 204 application capabilities, with the possible exception of limited user-specific application 205 configuration settings. 206

56. Tactical Edge - Environments covering the full range of military operations, including, 208 but not limited to forces deployed in support of a Geographic Combatant Commander or 209 applicable training exercises, on various platforms (e.g., dismounted infantry patrol, 210 forward operating base, and aircraft carrier) and with the ability to operate in austere and 211 connectivity-deprived environments. 212

57. Tactical Edge Device - Durable and portable computing and storage capability able to 214 operate in the tactical edge. 215

58. Testing - See JEDI Cloud Cyber Security Plan. 217

59. Traffic - See JEDI Cloud Cyber Security Plan. 219

60. Unclassified infrastructure - See JEDI Cloud Cyber Security Plan. 221

61. User - Provisioned identity able to manage infrastructure. 223

62. U.S. Person - The term “United States person” means any United States citizen, any 225 alien lawfully admitted for permanent residence in the United States, and any 226 corporation, partnership, or other organization organized under the laws of the United 227 States that is not under the control of a foreign government. 228

63. Virtual Enclave - On-demand configurable pool of shared computing and storage 230 resources within a multi-tenant cloud environment that is logically isolated from other 231 tenants. 232

64. Virtual Machine (VM) - Software that emulates the physical hardware of a computer. 234

65. Vulnerability - See JEDI Cloud Cyber Security Plan. 236

66. Workspace - A collection of cloud resources and services, which may be billed 238 independently, used for a specific project or by a particular organization. Sometimes 239 referred to as a cloud services account or cloud provider account. 240

File details come from the government source that posted it.