forked from metanorma/csa-ccm-tools
-
Notifications
You must be signed in to change notification settings - Fork 0
/
official-csa-caiq-elastic-cloud.answers.yaml.unlinted
3147 lines (3006 loc) · 169 KB
/
official-csa-caiq-elastic-cloud.answers.yaml.unlinted
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
---
ccm:
metadata:
version: '3.1'
title: CONSENSUS ASSESSMENTS INITIATIVE QUESTIONNAIRE v3.1
source-file: official-csa-caiq-elastic-cloud.xlsx
answers:
- control-id: AAC-01
question-id: AAC-01.1
answer: 'yes'
comment: "Annual security reviews/ audits are performed by independent third parties.\n\nElastic
has completed the SOC 2 Type 2 certification, including the security control
requirements defined by the Cloud Security Alliance (CSA), HIPAA Attestation
of Compliance, and ISO 27001 27017 and 27018 certifications for Elastic Cloud.\n\nAn
up to date list of our certifications and attestations is available at https://www.elastic.co/security-and-compliance.
\n\nOur code is free and open and frequently reviewed by members of the open
source community. We also run a bug bounty program that rewards independent
researchers who identify vulnerabilities in our products."
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AAC-01
question-id: AAC-01.2
answer: 'yes'
comment: Our audit program and certifications take into account the effectiveness
of security operations and progress against security objectives.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AAC-02
question-id: AAC-02.1
answer: 'yes'
comment: |-
We are happy to share our current SOC 2 Type 2 report, which includes the CSA STAR CCM criteria, upon request.
Our ISO certificates can be found on our public site at: https://www.elastic.co/security-and-compliance
We authorized as FedRAMP Moderate and listed on the FedRAMP Marketplace: https://marketplace.fedramp.gov/#!/product/elastic-cloud?sort=productName&productNameSearch=elastic
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AAC-02
question-id: AAC-02.2
answer: 'yes'
comment: Elastic performs penetration testing on an annual basis. Both Network
and Application Security controls are tested.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AAC-02
question-id: AAC-02.3
answer: 'yes'
comment: Elastic performs penetration testing on an annual basis. Both Network
and Application Security controls are tested.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AAC-02
question-id: AAC-02.4
answer: 'yes'
comment: 'Internal audits/ reviews are performed by the Internal Audit team, as
well as the Information Security team which is responsible for security assurance,
engineering and risk and compliance activities for the company.
'
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AAC-02
question-id: AAC-02.5
answer: 'yes'
comment: "Annual security reviews/ audits are performed by independent third parties.\n\nElastic
has completed the SOC 2 Type 2 certification, including the security control
requirements defined by the Cloud Security Alliance (CSA), HIPAA Attestation
of Compliance, and ISO 27001 27017 and 27018 certifications for Elastic Cloud.\n\nAn
up to date list of our certifications and attestations is available at https://www.elastic.co/security-and-compliance.
\n\nOur code is free and open and frequently reviewed by members of the open
source community. We also run a bug bounty program that rewards independent
researchers who identify vulnerabilities in our products. \n\n"
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AAC-02
question-id: AAC-02.6
answer: 'yes'
comment: |-
Elastic performs penetration testing on an annual basis. Both Network and Application Security controls are tested.
Elastic will share the executive summary of our latest penetration test upon request.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AAC-02
question-id: AAC-02.7
answer: 'yes'
comment: |-
We are happy to share our current SOC 2 Type 2 report, which includes the CSA STAR CCM criteria, upon request.
Our ISO certificates can be found on our public site at: https://www.elastic.co/security-and-compliance
We authorized as FedRAMP Moderate and listed on the FedRAMP Marketplace: https://marketplace.fedramp.gov/#!/product/elastic-cloud?sort=productName&productNameSearch=elastic
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AAC-03
question-id: AAC-03.1
answer: 'yes'
comment: |-
Elastic has an extensive security program, led by Elastic's CISO and supported by the company's Information Security staff.
The program includes the ability to monitor changes to the regulatory requirements in relevant jurisdictions, adjusting the security program for changes to legal requirements, and ensuring compliance with relevant regulatory requirements.
Elastic has a cross-functional privacy team that reports to the Chief Information Security Officer and the Chief Legal Officer. The Chief Legal Officer is ultimately accountable for compliance with applicable privacy law.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-01
question-id: AIS-01.1
answer: 'yes'
comment: |-
A formal systems development life cycle (SDLC) methodology is in place. This is the overall process of developing, implementing, and retiring information systems through a multistep process from initiation, analysis, design, implementation, and maintenance to disposal. The process consists of a series of defined steps or phases where information security must be integrated into the SDLC to ensure appropriate protection for the Elastic information that the system transmits, processes, and stores.
This internal SDLC program that is built around our unique open source development model. We ensure our developers are aware of common security problems, how to identify and resolve them, as well as how to report such problems to the appropriate teams for remiation and verification. Changes are vetted by multiple security aware reviewers. We have programs in place to understand third party components, track known issues in them as well as updating the components as needed. Releases receive scrutiny to identify any issues in the supply chain and product itself. We are a CVE CNA and publish security alerts as part of the overall lifecycle program. We regularly conduct 3rd party code reviews of our products, have a private bug bounty program, and accept external reports from anyone regarding the security of our software.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-01
question-id: AIS-01.2
answer: 'yes'
comment: |
Deployment to production is controlled via Change Management.
- Changes are branches in repository, version controlled.
- All changes are automatically tested by a pipeline of tools including security checks.
- All testing is registered in GitHub and must pass before testing is complete.
- To merge new code into production, needs approval by another developer/engineer.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-01
question-id: AIS-01.3
answer: 'yes'
comment: "A code review process in place.\n\nThe software and cloud infrastructure
change management process requires that software and cloud infrastructure change
requests are: \n● Authorized.\n● Formally documented\n● Peer reviewed \n● Tested
prior to migration to production\n● Reviewed by management (where required)
to make sure that the change is appropriate, followed the change management
process, and was scheduled for release appropriately."
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-01
question-id: AIS-01.4
answer: 'yes'
comment: As part of the Elastic Third Party Vendor Review process, Elastic reviews
the security practices of its third parties to ensure controls such as this
are in place.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-01
question-id: AIS-01.5
answer: 'yes'
comment: |-
Releases receive scrutiny to identify any issues in the supply chain and product itself. We are a CVE CNA and publish security alerts as part of the overall lifecycle program. We regularly conduct 3rd party code reviews of our products, have a bug bounty program, and accept external reports from anyone regarding the security of our software.
Elastic source code is available and open for review by community and customers alike. It is available at https://www.github.com/elastic.
Elastic maintains a documented public process for submitting vulnerabilities and security-related issues at https://www.elastic.co/community/security. The company follows a documented (internal) process on responding to vulnerability and other security-related reports.
The company has created a team of the most security-knowledgeable people on each product team who collaborate, evaluate and respond to reports in a private mailing list. The company also publishes vulnerabilities via Bugtraq and also public announcements at https://discuss.elastic.co/c/security-announcements.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-02
question-id: AIS-02.1
answer: 'yes'
comment: |-
Before accessing Elastic Cloud, customers are required to accept our Terms of Agreeement and Privacy Statement.
https://www.elastic.co/legal/elastic-cloud-account-terms
https://www.elastic.co/legal/privacy-statement
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-02
question-id: AIS-02.2
answer: 'yes'
comment: |-
Requirements and trust levels are defined contractually and via the Terms of Agreeement and Privacy Statement.
https://www.elastic.co/legal/elastic-cloud-account-terms
https://www.elastic.co/legal/privacy-statement
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-03
question-id: AIS-03.1
answer: 'yes'
comment: All access to the production environment is logged, monitored and audited
at multiple levels. Access to tenant data is logged at a granular level, down
to individual operating system commands or API calls that are attributable to
an individual. Automatic alerting is in place, with documented response procedures
for the InfoSec team to act on alerts.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-03
question-id: AIS-03.2
answer: 'yes'
comment: |-
Elastic uses data integrity controls to ensure that data inputs to application systems are accurate and within the expected range of values.
Where appropriate, data inputs are sanitized or otherwise rendered safe before being inputted to an application system.
Input and output integrity routines such as SHA hashes and checksums are used throughout our platform and application code to prevent processing errors and corruption.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: AIS-04
question-id: AIS-04.1
answer: 'yes'
comment: |-
Elastic maintains and regularly updates the Information Security Program Policy which establishes the mandate for Information Security across the organization. The policy and supporting standards address the purpose, scope, roles and responsibilities, requirements, and coordination among the teams involved in delivering Elastic Cloud.
Our security program and architecture are aligned wih and certified against industry standards including ISO 27001, CSA Star, SOC2 and FedRAMP.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-01
question-id: BCR-01.1
answer: 'yes'
comment: A Business Continuity Standard and documented disaster recovery (DR)
plan is in place for Elastic Cloud and tested annually to ensure continued effectiveness.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-01
question-id: BCR-01.2
answer: 'yes'
comment: "Elastic Cloud customers have complete control to select the cloud (IAAS)
provider and geographic region on a per-deployment basis. \n\nSupport for new
regions in each IAAS provider is added regularly. It is possible to configure
cross-cluster replication across regions and providers.\n\nThe currently available
regions for each provider can be found at: https://www.elastic.co/guide/en/cloud/current/ec-reference-regions.html"
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-01
question-id: BCR-01.3
answer: 'yes'
comment: |-
Elastic Cloud customers have complete control to select the cloud (IAAS) provider and geographic region on a per-deployment basis.
High Availability is achieved within the selected region by hosting the deployment in multiple availability zones. This is configurable by the customer and enabled by default. Elastic recommends that Production deployments are in at least two availability zones.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-01
question-id: BCR-01.4
answer: 'yes'
comment: Our observability monitoring includes upstream providers.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-01
question-id: BCR-01.5
answer: 'yes'
comment: |-
Current and historical operational redundancy summaries are available at:
https://cloud-status.elastic.co
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-01
question-id: BCR-01.6
answer: 'yes'
comment: "High Availability is achieved within a region by hosting the deployment
in multiple availability zones. \n\nThis is configurable by the customer and
enabled by default. Elastic recommends that Production deployments are in at
least two availability zones.\n\nTenant triggered failover or high-availability
across regions could be configured by the customer using Cross-Cluster Replication."
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-01
question-id: BCR-01.7
answer: 'yes'
comment: |-
Access to in-scope system components is determined by role and based on least privilege.
All access is terminated within 24 hours of an employee leaving the company and tracked via a ticketing system.
In addition, quarterly user access reviews are performed by functional leaders for the in-scope system components to ensure that access is restricted appropriately. Access removal is tracked to remove access as necessary in a timely manner.
Authorized Elastic employees are only provided access to tenant data where this is required to help deliver the service.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-02
question-id: BCR-02.1
answer: 'yes'
comment: A Business Continuity Standard and documented disaster recovery (DR)
plan is in place for Elastic Cloud and tested annually to ensure continued effectiveness.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-03
question-id: BCR-03.1
answer: 'no'
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers.\n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nPhysical Security, media and hardware controls
are the responsibility of the IaaS provider, more details on the controls they
have in place can be found at:\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/ \nFor Azure,
see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-03
question-id: BCR-03.2
answer: 'yes'
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers.\n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nPhysical Security, media and hardware controls
are the responsibility of the IaaS provider, more details on the controls they
have in place can be found at:\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/ \nFor Azure,
see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-04
question-id: BCR-04.1
answer: 'yes'
comment: Extensive documentation, including installation and operating procedures,
security standards and build documentation is maintained and made available
to authorized personnel.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-05
question-id: BCR-05.1
answer: NA
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers. \n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/\nFor Azure, see
https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-06
question-id: BCR-06.1
answer: 'no'
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers. \n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/\nFor Azure, see
https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-07
question-id: BCR-07.1
answer: NA
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers.\n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nPhysical Security, media and hardware controls
are the responsibility of the IaaS provider, more details on the controls they
have in place can be found at:\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/ \nFor Azure,
see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-07
question-id: BCR-07.2
answer: NA
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers.\n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nPhysical Security, media and hardware controls
are the responsibility of the IaaS provider, more details on the controls they
have in place can be found at:\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/ \nFor Azure,
see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-08
question-id: BCR-08.1
answer: 'yes'
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers. All physical controls are provided by the
IaaS provider.\n\nElastic Cloud customers have the flexibility to choose the
underlying IaaS provider and geographical region for their data on a per-deployment
basis.\n\nFor AWS, see https://aws.amazon.com/compliance/programs/ \nFor GCP,
see https://cloud.google.com/security/compliance/#/\nFor Azure, see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-09
question-id: BCR-09.1
answer: 'yes'
comment: These concepts and standards are used in the development and maintanence
of our Business Continuity Standard and Disaster Recovery plans.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-09
question-id: BCR-09.2
answer: 'yes'
comment: |-
SLA performance information is provided at: https://cloud-status.elastic.co
Customers can also monitor their deployments by shipping logs to a separate monitoring deployment, as described in https://www.elastic.co/blog/monitoring-elastic-cloud-deployment-logs-and-metrics.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-10
question-id: BCR-10.1
answer: 'yes'
comment: Policies and procedures are established are made available for all personnel
to adequately support service operations roles.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-11
question-id: BCR-11.1
answer: 'yes'
comment: "Elastic Cloud customers can use Index Lifecycle Management to manage
retention schedules and migration to different data tiers at a granular level.\n\nFor
more details see: https://www.elastic.co/guide/en/elasticsearch/reference/current/set-up-lifecycle-policy.html
\n\nElastic Cloud customers can delete data at their discretion and at any time
without Elastic involvement."
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-11
question-id: BCR-11.2
answer: 'yes'
comment: "Elastic Cloud customers can use Index Lifecycle Management to manage
retention schedules and migration to different data tiers at a granular level.\n\nFor
more details see: https://www.elastic.co/guide/en/elasticsearch/reference/current/set-up-lifecycle-policy.html
\n\nElastic Cloud customers can delete data at their discretion and at any time
without Elastic involvement."
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-11
question-id: BCR-11.3
answer: 'yes'
comment: |-
Backup snapshots are taken on a per-deployment basis and are configurable by the customer. The default snapshot interval is 30 minutes. Customers can restore data to the same or a different deployment on-demand and without involvement from Elastic.
High Availability is achieved within the selected region by hosting the deployment in multiple availability zones. This is configurable by the customer and enabled by default. Elastic recommends that Production deployments are in at least two availability zones.
Elastic Cloud customers have access to delete data at thier own discretion and at any time without the involvement of Elastic.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-11
question-id: BCR-11.4
answer: 'yes'
comment: Elastic cloud uses the virtualized infrastructure provided by the underlying
cloud providers.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-11
question-id: BCR-11.5
answer: 'yes'
comment: |-
Virtual machines are not applicable in a SAAS product, but we do make this capability availalbe for tenant deployments of Elastic Cloud.
Backup snapshots are taken on a per-deployment basis and are configurable by the customer. The default snapshot interval is 30 minutes. Customers can restore data to the same or a different deployment on-demand and without involvement from Elastic.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-11
question-id: BCR-11.6
answer: 'yes'
comment: Backup snapshots are taken on a per-deployment basis and are configurable
by the customer. The default snapshot interval is 30 minutes. Customers can
restore data to the same or a different deployment on-demand and without involvement
from Elastic.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: BCR-11
question-id: BCR-11.7
answer: 'yes'
comment: Backup and redundancy mechanisms are tested at least annually.
infosec-function: Security Assurance
infosec-service: 'Svc: Customer Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-01
question-id: CCC-01.1
answer: 'yes'
comment: A formal systems development life cycle (SDLC) methodology is in place.
This is the overall process of developing, implementing, and retiring information
systems through a multistep process from initiation, analysis, design, implementation,
and maintenance to disposal. The process consists of a series of defined steps
or phases where information security must be integrated into the SDLC to ensure
appropriate protection for the Elastic information that the system transmits,
processes, and stores.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-02
question-id: CCC-02.1
answer: 'yes'
comment: "Our SDLC process is built around our unique open source development
model. \n\nAll engineers and developers receive annual training to ensure they
are aware of common security problems, how to identify and resolve them, as
well as how to report such problems to the appropriate teams for remiation and
verification.\n\nChanges are vetted by multiple security aware reviewers. We
have programs in place to understand third party components, track known issues
in them as well as updating the components as needed. Releases receive scrutiny
to identify any issues in the supply chain and product itself. \n\nWe are a
CVE CNA and publish security alerts as part of the overall lifecycle program.\n\nWe
regularly conduct 3rd party code reviews of our products, run a bug bounty program,
and accept external reports from anyone regarding the security of our software."
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-02
question-id: CCC-02.2
answer: 'yes'
comment: |-
All source code is managed through the same process and subject to the SDLC controls described in this document.
Source code that is contributed by open source contributors can only be merged into the codebase by Elastic employees.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-03
question-id: CCC-03.1
answer: 'yes'
comment: |-
Deployment to production is controlled via Change Management.
- Changes are branches in repository, version controlled.
- All changes are automatically tested by a pipeline of tools including security checks.
- All testing is registered in GitHub and must pass before testing is complete.
- To merge new code into production, needs approval by another developer/engineer
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-03
question-id: CCC-03.2
answer: 'yes'
comment: "Elastic source code and issue tracking is available and open for review
by community and customers alike. It's available at github.com/elastic. \n\nWe
are a CVE CNA and publish security alerts as part of the overall lifecycle program.
We regularly conduct 3rd party code reviews of our products, have a private
bug bounty program, and accept external reports from anyone regarding the security
of our software.\n\nElastic maintains a documented public process for submitting
vulnerabilities and security-related issues at https://www.elastic.co/community/security.\n\nThe
company also publishes vulnerabilities via Bugtraq and also public announcements
at https://discuss.elastic.co/c/security-announcements."
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-03
question-id: CCC-03.3
answer: 'yes'
comment: "Elastic maintains a documented public process for submitting vulnerabilities
and security-related issues at https://www.elastic.co/community/security \n\nThe
company follows a documented (internal) process on responding to vulnerability
and other security-related reports. The company has created a team of the most
security-knowledgeable people on each product collaborating to evaluate and
respond to reports in a private mailing list. The company also publishes vulnerabilities
via Bugtraq and also public announcements at https://discuss.elastic.co/c/security-announcements"
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-03
question-id: CCC-03.4
answer: 'yes'
comment: "Our SDLC process is built around our unique open source development
model. \n\nAll engineers and developers receive annual training to ensure they
are aware of common security problems, how to identify and resolve them, as
well as how to report such problems to the appropriate teams for remiation and
verification.\n\nChanges are vetted by multiple security aware reviewers. We
have programs in place to understand third party components, track known issues
in them as well as updating the components as needed. Releases receive scrutiny
to identify any issues in the supply chain and product itself. \n\nWe are a
CVE CNA and publish security alerts as part of the overall lifecycle program.\n\nWe
regularly conduct 3rd party code reviews of our products, run a bug bounty program,
and accept external reports from anyone regarding the security of our software."
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-03
question-id: CCC-03.5
answer: 'yes'
comment: |-
All source code is managed through the same process and subject to the SDLC controls described in this document.
Source code that is contributed by open source contributors can only be merged into the codebase by Elastic employees.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-03
question-id: CCC-03.6
answer: 'yes'
comment: "Our SDLC process and controls including peer review ensure that debugging
and test code elements are removed. \n\nTesting takes place as part of a structured
CI/CD pipeline during software builds.\n\nWe conduct 3rd party code reviews
of our products including prior to major releases."
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-04
question-id: CCC-04.1
answer: 'yes'
comment: We have a number of controls in place to address this requirement as
part of a defense in depth approach. These include Access Control, Configuration
Management, Audit Logging, and Monitoring.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-05
question-id: CCC-05.1
answer: NA
comment: |-
We have a Change Management Standard which ensures requirements for change management are designed to control and manage the propagation of software and infrastructure changes to a production environment. This process ensures that changes proposed are reviewed, authorized, tested, implemented, and released in a controlled manner, and that the status of each proposed change is documented and monitored. The requirements related to Emergency Changes are also included in this document.
Included within the Change Management Standard are our formal requirements for our Systems Development Life Cycle (SDLC). This is the overall process of developing, implementing, and retiring information systems through a multistep process from initiation, analysis, design, implementation, and maintenance to disposal. We do not share such policies externally.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-05
question-id: CCC-05.2
answer: 'yes'
comment: |-
We have a Change Management Standard which ensures requirements for change management are designed to control and manage the propagation of software and infrastructure changes to a production environment. This process ensures that changes proposed are reviewed, authorized, tested, implemented, and released in a controlled manner, and that the status of each proposed change is documented and monitored. The requirements related to Emergency Changes are also included in this document.
Included within the Change Management Standard are our formal requirements for our Systems Development Life Cycle (SDLC). This is the overall process of developing, implementing, and retiring information systems through a multistep process from initiation, analysis, design, implementation, and maintenance to disposal. We do not share such policies externally.
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: CCC-05
question-id: CCC-05.3
answer: 'yes'
comment: |-
Deployment to production is controlled via Change Management.
- Changes are branches in repository, version controlled.
- All changes are automatically tested by a pipeline of tools including security checks.
- All testing is registered in GitHub and must pass before testing is complete.
- To merge new code into production, needs approval by another developer/engineer
- Security or operationally sensitive portions of the codebase require specific review/approval from the appropriate team (e.g. Security).
infosec-function: Product Security
infosec-service: 'Svc: Product Security'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-01
question-id: DCS-01.1
answer: 'yes'
comment: All critical assets are required to be registered in our asset inventory.
Elastic performs ongoing reviews of our asset inventory for completeness and
accuracy.
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-01
question-id: DCS-01.2
answer: 'yes'
comment: As part of the Elastic Third Party Information Risk Management process,
Elastic reviews the security practices of its third parties to ensure adequate
security controls are in place. As part of this process, we maintain an inventory
of critical suppliers.
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-02
question-id: DCS-02.1
answer: 'yes'
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers.\n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nPhysical Security, media and hardware controls
are the responsibility of the IaaS provider, more details on the controls they
have in place can be found at:\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/ \nFor Azure,
see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-03
question-id: DCS-03.1
answer: 'yes'
comment: "Customers can integrate Elastic Cloud deployments with their own Identity
Provider (IdP) using SAML.\n\nIf the customer IdP supports geographic location
as a factor, this could be utilized in authentication requests for Elastic Cloud.
\n\nhttps://www.elastic.co/guide/en/cloud/current/ec-securing-clusters-SAML.html"
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-03
question-id: DCS-03.2
answer: NA
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers.\n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nPhysical Security, media and hardware controls
are the responsibility of the IaaS provider, more details on the controls they
have in place can be found at:\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/ \nFor Azure,
see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-04
question-id: DCS-04.1
answer: NA
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers.\n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nPhysical Security, media and hardware controls
are the responsibility of the IaaS provider, more details on the controls they
have in place can be found at:\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/ \nFor Azure,
see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-05
question-id: DCS-05.1
answer: NA
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers.\n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nPhysical Security, media and hardware controls
are the responsibility of the IaaS provider, more details on the controls they
have in place can be found at:\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/ \nFor Azure,
see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-06
question-id: DCS-06.1
answer: 'yes'
comment: |-
Elastic is SOC2 Type 2 compliant. Customers and prospective customers can request copies of our SOC2 reports which contain evidence of the policies, standards and procedures that have been audited as part of the process.
Our ISO 27001 Certificate is available at: https://www.elastic.co/security-and-compliance
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-06
question-id: DCS-06.2
answer: 'yes'
comment: |-
Elastic is SOC2 Type 2 compliant. Customers and prospective customers can request copies of our SOC2 reports which contain evidence of the policies, standards and procedures that have been audited as part of the process.
Our ISO 27001 Certificate is available at: https://www.elastic.co/security-and-compliance
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-07
question-id: DCS-07.1
answer: NA
comment: "Elastic utilizes Infrastructure as a Service providers (IaaS) and does
not maintain its own data centers.\n\nElastic Cloud customers have the flexibility
to choose the underlying IaaS provider and geographical region for their data
on a per-deployment basis.\n\nPhysical Security, media and hardware controls
are the responsibility of the IaaS provider, more details on the controls they
have in place can be found at:\n\nFor AWS, see https://aws.amazon.com/compliance/programs/
\nFor GCP, see https://cloud.google.com/security/compliance/#/ \nFor Azure,
see https://docs.microsoft.com/en-us/azure/compliance/"
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-08
question-id: DCS-08.1
answer: NA
comment: |-
Elastic utilizes Infrastructure as a Service providers (IaaS) and does not maintain its own data centers.
Elastic Cloud customers have the flexibility to choose the underlying IaaS provider and geographical region for their data on a per-deployment basis.
Physical Security, media and hardware controls are the responsibility of the IaaS provider, more details on the controls they have in place can be found at:
For AWS, see https://aws.amazon.com/compliance/programs/
For GCP, see https://cloud.google.com/security/compliance/#/
For Azure, see https://docs.microsoft.com/en-us/azure/compliance/
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DCS-09
question-id: DCS-09.1
answer: NA
comment: |-
Elastic utilizes Infrastructure as a Service providers (IaaS) and does not maintain its own data centers.
Elastic Cloud customers have the flexibility to choose the underlying IaaS provider and geographical region for their data on a per-deployment basis.
Physical Security, media and hardware controls are the responsibility of the IaaS provider, more details on the controls they have in place can be found at:
For AWS, see https://aws.amazon.com/compliance/programs/
For GCP, see https://cloud.google.com/security/compliance/#/
For Azure, see https://docs.microsoft.com/en-us/azure/compliance/
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-01
question-id: DSI-01.1
answer: 'yes'
comment: |-
Elastic Cloud is a SaaS service. While we use these underlying capabilities at the infrastructure layer, they are not directly exposed to the customer.
Elastic Cloud customers are provided with the flexibility to choose the underlying IaaS provider and geographical region on a per-deployment basis.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-01
question-id: DSI-01.2
answer: NA
comment: Elastic uses hosted infrastructure as a service and does not have direct
access to hardware. This control is inherited from the IaaS provider.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-02
question-id: DSI-02.1
answer: 'yes'
comment: This is done via documented data flows which are documented and maintained.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-02
question-id: DSI-02.2
answer: 'yes'
comment: |-
Elastic Cloud customers are provided with the flexibility to choose the underlying IaaS provider and geographical region on a per-deployment basis.
Available regions can be found at: https://www.elastic.co/cloud/regions
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-03
question-id: DSI-03.1
answer: 'yes'
comment: Data in transit to, from and within the Elastic Cloud environment is
encrypted using the open encryption standard TLS 1.2 with strong ciphers. TLS
versions older than 1.2 are disabled.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-03
question-id: DSI-03.2
answer: 'yes'
comment: Data in transit to, from and within the Elastic Cloud environment is
encrypted using the open encryption standard TLS 1.2 with strong ciphers. TLS
versions older than 1.2 are disabled.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-04
question-id: DSI-04.1
answer: 'yes'
comment: The company’s Information Security Program Policy specifies the Data
Classification Standard which governs labeling, handling and the security of
information. Elastic classifies all customer data as 'Restricted' according
to the standard. This, in turn, receives the highest level of protection.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-04
question-id: DSI-04.2
answer: 'yes'
comment: Customers choose what data is stored and how it is secured. Internally,
we use a Data Classification Standard that identifies all customer data as RESTRICTED.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-04
question-id: DSI-04.3
answer: 'yes'
comment: The company’s Information Security Program Policy specifies the Data
Classification Standard which governs labeling, handling and the security of
information. Elastic classifies all customer data as 'Restricted' according
to the standard. This, in turn, receives the highest level of protection.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-05
question-id: DSI-05.1
answer: 'yes'
comment: |-
Non-production environments are segregated from production environments at multiple levels including network and IaaS provider account.
Customer data is never used in testing or other non-production environments without explicit, documented approval from all customers whose data is affected.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-06
question-id: DSI-06.1
answer: 'yes'
comment: The company’s Information Security Program Policy specifies the Data
Classification Standard which governs labeling, handling and the security of
information. Elastic classifies all customer data as 'Restricted' according
to the standard which in turn, receives the highest level of protection.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-07
question-id: DSI-07.1
answer: 'yes'
comment: |-
All customer information is stored in our cloud based data centers. As a part of our customer off boarding process, we securely delete any information from the customer as well as the customer cluster.
Elastic Cloud customers are able to delete data at thier own discretion and at any time without Elastic involvement.
Controls around secure disposal of media and hardware are inherited from the underlying IaaS provider, as chosen by the customer.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: DSI-07
question-id: DSI-07.2
answer: 'yes'
comment: |-
This is agreed contractually. All customer information is stored in our cloud based data centers. As part of our customer off boarding process, we securely delete any information from the customer as well as the customer cluster.
Elastic Cloud customers are able to delete data at thier own discretion and at any time without Elastic involvement.
infosec-function: Risk Management
infosec-service: 'Svc: Info Risk Mgmt'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: EKM-01
question-id: EKM-01.1
answer: 'yes'
comment: Key Management policies, standards or procedures are documented and maintained
as Infrastructure-as-Code and/or as part of the operational documentation for
each applicable component or service.
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: EKM-02
question-id: EKM-02.1
answer: 'no'
comment: "Full disk encryption is in place on each virtual server host. Each virtual
server has a unique encryption key.\n\nIt is possible that multiple tenant deployments
exist on the same virtual server. All tenants are separated by containerization
that ensures separate logical storage volumes for each deployment, with no possibility
to access data across tenants. \n\n"
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: EKM-02
question-id: EKM-02.2
answer: 'yes'
comment: Elastic Cloud manages encryption keys on behalf of all tenants. We do
not currently support a Bring Your Own Key model.
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: EKM-02
question-id: EKM-02.3
answer: 'yes'
comment: Key Management policies, standards or procedures are documented and maintained
as Infrastructure-as-Code and/or as part of the operational documentation for
each applicable component or service.
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: EKM-02
question-id: EKM-02.4
answer: 'yes'
comment: |-
Key Management policies, standards or procedures are documented and maintained as Infrastructure-as-Code and/or as part of the operational documentation for each applicable component or service.
Keys for data encryption at rest never leave the host where they are generated and are considered disposable. They are automatically generated whenever a virtual machine host is created or replaced.
Key Management for encryption in the underlying IaaS services is automated using the Key Management System of the provider.
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: EKM-02
question-id: EKM-02.5
answer: 'yes'
comment: Key Management for encryption in the underlying IaaS services is automated
using the Key Management System of the provider.
infosec-function: Security Assurance
infosec-service: 'Svc: Security Assurance'
infosec-last-review-date: '2021-06-30T00:00:00+00:00'
- control-id: EKM-03
question-id: EKM-03.1
answer: 'yes'
comment: Data at rest for Elastic Cloud deployments is encrypted at rest using
the aes-xts-plain64 algorithm (AES-256) and a minimum key length of 256 bits.
infosec-function: Security Assurance