-
Notifications
You must be signed in to change notification settings - Fork 2
/
threagile.yaml
1943 lines (1871 loc) · 77.1 KB
/
threagile.yaml
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
threagile_version: 1.0.0
# NOTE:
#
# For a perfect editing experience within your IDE of choice you can easily
# get model syntax validation and autocompletion (very handy for enum values)
# as well as live templates: Just import the schema.json into your IDE and assign
# it as "schema" to each Threagile YAML file. Also try to import individual parts
# from the live-templates.txt file into your IDE as live editing templates.
#
# You might also want to try the REST API when running in server mode...
# This is only a stub for simple quick editing and is not complete.
# For a complete usable example model see the "-create-example-model" option.
title: Argo CD
date: 2022-11-13
author:
name: Argoproj Maintainers
homepage: argoproj.io
management_summary_comment: >
Just some <b>more</b> custom summary possible here...
business_criticality: important # values: archive, operational, important, critical, mission-critical
business_overview:
description: Some more <i>demo text</i> here and even images...
images:
# - custom-image-1.png: Some dummy image 1
# - custom-image-2.png: Some dummy image 2
technical_overview:
description: Some more <i>demo text</i> here and even images...
images:
# - custom-image-1.png: Some dummy image 1
# - custom-image-2.png: Some dummy image 2
questions: # simply use "" as answer to signal "unanswered"
Some question without an answer?: ""
Some question with an answer?: >
Some answer
abuse_cases:
Denial-of-Service: >
As an attacker, I want to disturb the functionality of the backend system in order to cause indirect reputational damage via unusable features.
CPU Cycle Theft / Deploying Crypto-Miner: >
As an attacker, I want to compromise an Argo CD instance, in order to deploy a crypto-miner, to seek financial gains through stealing resources.
Ransomware: >
As a attacker I want to encrypt the storage and file systems in order to demand ransom.
Identity Theft: >
As a attacker I want to steal identity data in order to reuse credentials and/or keys on other targets of the same company or outside.
PII Theft: >
As a attacker I want to steal PII (Personally Identifiable Information) data in order to blackmail the company and/or damage
their repudiation by publishing them.
Database Compromise: >
As a attacker I want to access the database backend of the SQL or Redis Database in order to steal/modify sensitive
business data.
Cross-Site Scripting Attacks: >
As a attacker I want to execute Cross-Site Scripting (XSS) and similar attacks in order to takeover victim sessions and
cause reputational damage.
# Argo specific
Denial-of-Service of Argo CD Functionality: >
As a attacker I want to disturb the functionality of Argo CD application areas in order to cause reputational and direct damage.
Denial-of-Service of Argo CD User Functionality: >
As a attacker I want to disturb the functionality of Argo CD user application areas in order to cause reputational and direct damage.
Supply Chain Compromise:
As a attacker I want to inflitrate the codebase of Argo CD so that I can introduce threats to the Argo project,
and potentially projects using Argo CD causing both tangiable and reputational damage.
Secrets System Compromise:
As a attacker I want to find out Argo CD user secrets by attacking an Argo CD user's secrets manager
Code Repository Compromise:
As a attacker I want to infiltrate the codebase of an Argo CD user to affect their continuous delivery.
Kubernetes Pod Container Compromise:
As a attacker I want to compromise the integrity of a Kubernetes Container in order to conduct an attack.
Kubernetes Pod Shared Storage Compromise:
As a attacker I want to compromise the integrity of Kubernetes pod shared storage in order to conduct an attack.
Kubernetes Pod Network Resources Compromise:
As a attacker I want to compromise the integrity of a Kubernetes pod network resources in order to conduct an attack.
Kubernetes Pod Init Container Compromise:
As a attacker I want to compromise the integrity of a Kubernetes init container in order to conduct an attack.
Kubernetes Node Compromise:
As a attacker I want to compromise the integrity of a Kubernetes init container in order to conduct an attack.
Kubernetes Cluster Compromise:
As a attacker I want to compromise the integrity of a Kubernetes init container in order to conduct an attack.
Argo CD Server Compromise:
As a attacker I want to compromise the integrity of an Argo CD server in order to find information on users to perform attacks
Poor validation:
As a attacker I want to find areas in the system where validation is performed poorly so that I can attack systems.
Malicious-In-The-Middle Attack:
As a attacker I want to compromise Argo CD events, Argo CD rollouts and potentional connections between servers to enumerate as attack on a system
security_requirements:
Users are restricted by RBAC: >
RBAC rules defined by an Argo CD operator are actually enforced for API access.
Input Validation: >
Strict input validation is required to reduce the overall attack surface.
Encryption During Transit: >
Data must be transported through parts of the system encrypted to prevent Malicious-In-The-Middle Attack.
Encryption at Rest: >
If sensitive data is stored within the Argo CD system, then this must be encrypted to prevent an attacker retrieving this data during breach.
# Tags can be used for anything, it's just a tag. Also risk rules can act based on tags if you like.
# Tags can be used for example to name the products used (which is more concrete than the technology types that only specify the type)
tags_available:
- aws
- aws:apigateway
- aws:dynamodb
- aws:ebs
- aws:ec2
- aws:iam
- aws:lambda
- aws:rds
- aws:s3
- aws:sqs
- aws:vpc
- azure
- docker
- gcp
- git
- kubernetes
- nexus
- ocp
- openshift
- tomcat
- argocd
- redis
- postgres
data_assets:
Argo CD GitHub Push Token:
id: argo-cd-github-push-token
description: A token granting push access to the Argo CD GitHub repo.
usage: devops
origin: GitHub UI or API
quantity: few
confidentiality: strictly-confidential
integrity: mission-critical
availability: operational
Argo CD Container Image:
id: argo-cd-container-image
description: Argo CD container image, primarily hosted on Quay.
usage: devops
origin: Argo CD GitHub build pipeline
quantity: many
confidentiality: public
integrity: mission-critical
availability: operational
Rendered Manifests:
id: rendered-manifests
description: Some Description
usage: devops # values: business, devops
origin: Some Origin
owner: Argo CD
quantity: many # values: very-few, few, many, very-many
confidentiality: confidential # values: public, internal, restricted, confidential, strictly-confidential
integrity: mission-critical # values: archive, operational, important, critical, mission-critical
availability: important # values: archive, operational, important, critical, mission-critical
justification_cia_rating: >
The manifests are potentially-sensitive, especially in a multi-tenant Argo CD installation. They shouldn't contain
any secrets. Integrity is important to ensure the correct manifests are deployed. The cache helps mitigate denial-of-service
on the controller and API server, but Argo CD can still function without the cache.
Manifest Sources:
id: manifest-sources
description: Some Description
usage: devops # values: business, devops
origin: Some Origin
owner: Argo CD
quantity: many # values: very-few, few, many, very-many
confidentiality: confidential # values: public, internal, restricted, confidential, strictly-confidential
integrity: mission-critical # values: archive, operational, important, critical, mission-critical
availability: operational # values: archive, operational, important, critical, mission-critical
justification_cia_rating: >
The manifest sources are potentially-sensitive, especially in a multi-tenant Argo CD installation. They shouldn't contain
any secrets. Integrity is important to ensure the correct manifests are deployed. The cache helps mitigate denial-of-service
on the controller and API server, but Argo CD can still function without the cache.
Application Name:
id: application-name
description: Name of the Application
usage: devops # values: business, devops
origin: Some Origin
owner: Argo CD
quantity: many # values: very-few, few, many, very-many
confidentiality: restricted # values: public, internal, restricted, confidential, strictly-confidential
integrity: operational # values: archive, operational, important, critical, mission-critical
availability: operational # values: archive, operational, important, critical, mission-critical
justification_cia_rating: >
The application name is used to identify the application and the project which controls it. It should be protected
from tenants or users who do not have access to that application.
Application Manifest:
id: application-manifest
description: Manifest of an Application, defining things such as manifest source and destination cluster.
usage: devops
origin: Argo CD Operator or Users
owner: Argo CD Operator
quantity: many
confidentiality: confidential
integrity: important
availability: operational
AppProject Manifest:
id: appproject-manifest
description: Manifest of an AppProject, a CRD which expresses certain rules applied to Applications.
usage: devops
origin: Argo CD Operator or Users
owner: Argo CD Operator
quantity: few
confidentiality: confidential
integrity: mission-critical
availability: operational
Live Manifests:
id: live-manifests
description: Live manifests representing some Kubernetes resource. May include contents of secrets.
usage: devops
origin: Kubernetes
owner: Argo CD User
quantity: very-many
confidentiality: strictly-confidential
integrity: mission-critical
availability: operational
OIDC Tokens:
id: oidc-tokens
description: JWTs holding user information, including group membership.
usage: business
origin: OIDC provider
quantity: very-many
confidentiality: strictly-confidential
integrity: operational
availability: operational
Argo Tokens:
id: argo-tokens
description: API access tokens generated by the API server and validated by the API server.
usage: devops
origin: Argo CD API Server
quantity: very-many
confidentiality: strictly-confidential
integrity: operational
availability: operational
API Server Secret:
id: api-server-secret
description: A randomly-generated key used by the API server to sign access tokens.
usage: devops
origin: Argo CD API Server
quantity: few
confidentiality: strictly-confidential
integrity: operational
availability: operational
# CLI Configuration File:
# CLI Binary:
# integrity: mission-critical
# justification_cia_rating: >
# If an attacker could modify the CLI binary, they could, for example, exfiltrate an access token, or use the access
# token to make changes to cluster resources such as the Argo CD configuration itself.
# Argo CD Frontend Dependencies:
# Argo CD Go Dependencies:
Argo CD Base Image:
id: argo-cd-base-image
description: Ubuntu base image which the Argo CD image is built on.
usage: devops
origin: Ubuntu
quantity: very-few
confidentiality: public
integrity: mission-critical
availability: operational
# Argo CD Debian Packages:
# Argo CD Dex HAProxy Manifests:
# Argo CD Redis HA Manifests:
# Argo CD Source Repo Push Token:
Cluster Access Credentials:
id: cluster-access-credentials
description: Credentials granting access to manage an external Kubernetes cluster's resources.
usage: devops
origin: External cluster API.
quantity: many
confidentiality: strictly-confidential
integrity: operational
availability: operational
Cluster Access Configuration:
id: cluster-access-configuration
description: Configuration for external cluster access. Includes clusterResources boolean and namespaces list.
usage: devops
origin: Argo CD Operator
quantity: many
confidentiality: restricted
integrity: critical
availability: operational
justification_cia_rating: >
Integrity is critical because an attacker could disable TLS validation or enable write access to cluster resources
or out-of-bounds namespaces, of those were previously restricted at the cluster config level. Resource scope and
destinations may be restricted elsewhere as well (for example, in an AppProject).
OIDC Public Keys:
id: oidc-public-keys
description: Public keys used to validate OIDC tokens.
usage: business
origin: OIDC provider
quantity: few
confidentiality: public
integrity: mission-critical
availability: operational
OIDC Configuration:
id: oidc-configuration
description: Configuration of Argo CD's OIDC provider (either bundled Dex instance or external).
usage: business
origin: Argo CD Operator
quantity: very-few
confidentiality: internal # This block represents the non-secret part of the configuration.
integrity: mission-critical
availability: important
justification_cia_rating: >
The OIDC configuration is "internal," because it informs users' CLIs or UIs how to log a user in. But that
information should not be public if Argo CD is not exposed to the public internet.
The integrity of the configuration is mission critical, because if someone can change the configuration, they can
cause Argo CD to trust identity information from an untrustworthy source.
Availability is important, because without the configuration, users will be unable to log into Argo CD.
Availability is not mission critical, because the core Argo CD components (controller, repo-server, Redis) will be
unaffected. An administrator can use Kubernetes API access to restore the configuration.
OIDC Client Secret:
id: oidc-client-secret
description: Client secret used by the API server to authenticate with an OIDC provider.
usage: business
origin: OIDC Provider
quantity: very-few
confidentiality: strictly-confidential
integrity: important
availability: important
Repo Access Credentials:
id: repo-access-credentials
description: Credentials for retrieving manifest sources from a source control manager (git, Helm, etc.).
usage: devops
origin: Argo CD Operator
quantity: many
confidentiality: confidential
integrity: operational
availability: operational
# Repo Access Configuration:
Git Repo URL:
id: git-repo-url
description: URL of a git repo.
usage: devops
origin: SCM API or Argo CD User
quantity: many
confidentiality: confidential
integrity: important
availability: operational
Git Repo Name:
id: git-repo-name
description: Name of a git repo.
usage: devops
origin: SCM API or Argo CD User
quantity: many
confidentiality: restricted
integrity: operational
availability: operational
Git Branch Name:
id: git-branch-name
description: Name of a branch in a git repo.
usage: devops
origin: SCM API or Argo CD User
quantity: very-many
confidentiality: confidential
integrity: critical
availability: operational
Git Organization Name:
id: git-org-name
description: Name of an organization/project in a git source control management system.
usage: devops
origin: SCM API or Argo CD User
quantity: many
confidentiality: confidential
integrity: important
availability: operational
ApplicationSet Name:
id: applicationset-name
description: Name of an ApplicationSet.
usage: devops
origin: Argo CD Operator
quantity: many
confidentiality: restricted
integrity: critical
availability: operational
ApplicationSet Manifest:
id: applicationset-manifest
description: Manifest representing an ApplicationSet.
usage: devops
origin: Argo CD Operator
quantity: many
confidentiality: restricted
integrity: mission-critical
availability: operational
Quay Push Token:
id: quay-push-token
description: Quay token with push access to the Argo CD repository.
usage: devops
origin: Quay
owner: Argo CD build team.
quantity: very-few
confidentiality: strictly-confidential
integrity: operational
availability: operational
Argo CD Container Image Tag:
id: argo-cd-container-image-tag
description: Repo name/tag for the Argo CD container image.
usage: devops
origin: Manifests repository.
quantity: very-few
confidentiality: public
integrity: mission-critical
availability: operational
Argo CD Source:
id: argo-cd-source
description: The source code for Argo CD.
usage: devops
origin: Argo CD maintainers
quantity: very-few
confidentiality: public
integrity: mission-critical
availability: operational
Argo CD RBAC Config:
id: argo-cd-rbac-config
description: The RBAC settings for an Argo CD instance.
usage: devops
origin: Argo CD Operator
quantity: very-few
confidentiality: confidential
integrity: mission-critical
availability: operational
Argo CD Database Export:
id: argocd-db-export
description: Export once Argo CD admin export command is run. Also contains configuration and potentially secrets
usage: devops # values: business, devops
tags:
- redis
- kubernetes
- argocd
origin: Argo CD
owner: Argo CD
quantity: very-few # values: very-few, few, many, very-many
confidentiality: strictly-confidential # values: public, internal, restricted, confidential, strictly-confidential
integrity: critical # values: archive, operational, important, critical, mission-critical
availability: critical # values: archive, operational, important, critical, mission-critical
justification_cia_rating: >
Data for customizing of the DB system, which might include full database dumps.
Argo CD User Provided Secret:
id: user-provided-secret
description: Secrets within Argo CD that come from Kubernetes shown in the UI but not in the deployment.
usage: devops # values: business, devops
tags:
- kubernetes
origin: Argo CD User
owner: Kubernetes
quantity: very-many # values: very-few, few, many, very-many
confidentiality: strictly-confidential # values: public, internal, restricted, confidential, strictly-confidential
integrity: mission-critical # values: archive, operational, important, critical, mission-critical
availability: mission-critical # values: archive, operational, important, critical, mission-critical
justification_cia_rating: >
Potentially very sensitive data being shown within UI. Care here must be shown with regards to transport to UI.
Bundled UI Code:
id: bundled-ui-code
description: Webpack bundled UI code which runs the Argo CD single-page app.
usage: devops
origin: Argo CD Maintainers
quantity: very-few
confidentiality: public
integrity: mission-critical
availability: operational
technical_assets:
Argo CD Maintainer Git Client:
id: argo-cd-maintainer-git-client
description: Git client (and configuration) used by an Argo CD maintainer.
type: process
usage: devops
used_as_client_by_human: true
out_of_scope: false
size: application
technology: cli
internet: false
machine: physical
encryption: data-with-symmetric-shared-key
owner: Argo CD Maintainer
confidentiality: strictly-confidential
integrity: mission-critical
availability: operational
multi_tenant: false
redundant: false
data_assets_processed:
- argo-cd-source
- argo-cd-container-image-tag
data_assets_stored:
- argo-cd-source
- argo-cd-container-image-tag
- argo-cd-github-push-token
data_formats_accepted:
- file
communication_links:
Push Code/Tags to GitHub:
target: argo-cd-source-repo
description: >
Push code to the Argo CD repo (as when cherry-picking changes) and/or push tags (as when cutting a release).
protocol: https
authentication: two-factor
authorization: enduser-identity-propagation
vpn: false
ip_filtered: false
readonly: false
usage: devops
data_assets_sent:
- argo-cd-github-push-token
- argo-cd-source
- argo-cd-container-image-tag
data_assets_received:
- argo-cd-source
- argo-cd-container-image-tag
Quay:
id: quay
description: Quay image repository.
type: datastore
usage: devops
used_as_client_by_human: false
out_of_scope: false
size: system
technology: artifact-registry
internet: true
machine: virtual
encryption: data-with-symmetric-shared-key
owner: Red Hat
confidentiality: public
integrity: mission-critical
availability: operational
multi_tenant: true
redundant: false
data_assets_processed:
- argo-cd-container-image
- argo-cd-container-image-tag
- quay-push-token
data_assets_stored:
- argo-cd-container-image
Docker Hub:
id: docker-hub
description: Docker Hub image repository.
type: datastore
usage: devops
used_as_client_by_human: false
out_of_scope: false
size: system
technology: artifact-registry
internet: true
machine: virtual
encryption: data-with-symmetric-shared-key
owner: Ubuntu
confidentiality: public
integrity: mission-critical
availability: operational
multi_tenant: true
redundant: false
data_assets_processed:
- argo-cd-base-image
data_assets_stored:
- argo-cd-base-image
Argo CD Source Repo (GitHub):
id: argo-cd-source-repo
description: GitHub repo holding the Argo CD source code.
type: datastore
usage: devops
used_as_client_by_human: false
out_of_scope: false
size: application
technology: sourcecode-repository
internet: true
machine: virtual
encryption: data-with-symmetric-shared-key
owner: GitHub
confidentiality: public
integrity: mission-critical
availability: operational
multi_tenant: true
redundant: false
data_assets_processed:
- argo-cd-source
- argo-cd-container-image-tag
- argo-cd-github-push-token
data_assets_stored:
- argo-cd-source
- argo-cd-container-image-tag
Argo CD Build Pipeline (GitHub Actions):
id: argo-cd-build-pipeline
description: Argo CD build pipeline, hosted on GitHub Actions.
type: process
usage: devops
used_as_client_by_human: false
out_of_scope: false
size: application
technology: build-pipeline
internet: true
machine: virtual
encryption: data-with-symmetric-shared-key
owner: GitHub
confidentiality: strictly-confidential
integrity: mission-critical
availability: operational
multi_tenant: true
redundant: false
data_assets_processed:
- argo-cd-container-image
- argo-cd-source
- argo-cd-base-image
- quay-push-token
data_assets_stored:
- quay-push-token
- argo-cd-github-push-token
communication_links:
Pull Source:
target: argo-cd-source-repo
description: Pull the Argo CD source from the GitHub repo.
protocol: https
authentication: token
authorization: technical-user
vpn: false
ip_filtered: false
readonly: true
usage: devops
data_assets_sent:
data_assets_received:
- argo-cd-source
Pull Base Image from Docker Hub:
target: docker-hub
description: Pull the Ubuntu base image from Docker Hub.
protocol: https
authentication: none
authorization: none
vpn: false
ip_filtered: false
readonly: true
usage: devops
data_assets_sent:
data_assets_received:
- argo-cd-base-image
Push Image to Quay:
target: quay
description: Quay image repository.
protocol: https
authentication: token
authorization: technical-user
vpn: false
ip_filtered: false
readonly: false
usage: devops
data_assets_sent:
- quay-push-token
- argo-cd-container-image
data_assets_received:
API Server:
id: api-server
description: Argo CD API server. Accepts requests from the UI and CLI.
type: process
usage: devops
used_as_client_by_human: false
out_of_scope: false
size: component
technology: application-server
internet: false
machine: container
encryption: data-with-symmetric-shared-key
owner: Argo CD Operator
confidentiality: confidential
integrity: mission-critical
availability: operational
multi_tenant: true
redundant: true
data_assets_processed:
- argo-cd-rbac-config
- rendered-manifests
- application-name
- live-manifests
- oidc-tokens
- oidc-public-keys
- cluster-access-credentials
- cluster-access-configuration
- api-server-secret
- argo-tokens
- repo-access-credentials
- appproject-manifest
- applicationset-manifest
- application-manifest
- argo-cd-container-image-tag
- argo-cd-container-image
- argocd-db-export
- manifest-sources # When sent for server-side generation or override sync.
- oidc-configuration
- oidc-client-secret
data_assets_stored:
- oidc-public-keys
- argo-cd-rbac-config
- oidc-configuration
- bundled-ui-code
data_assets_sent:
- argocd-db-export
- oidc-configuration
- bundled-ui-code
data_assets_produced:
- argocd-db-export
data_formats_accepted:
- json
- csv
- file
communication_links:
Export Database:
target: user-cli
description: Send database export to Admin Argo CD User
protocol: https # values: see help
authentication: token # values: none, credentials, session-id, token, client-certificate, two-factor
authorization: enduser-identity-propagation # values: none, technical-user, enduser-identity-propagation
tags:
vpn: false
ip_filtered: false
readonly: false
usage: devops # values: business, devops
data_assets_sent: # sequence of IDs to reference
- argocd-db-export
data_assets_received:
- oidc-tokens
# Pull Argo CD Image:
# target: quay
# description: Pull the Argo CD container image from Quay.
# protocol: https
# authentication: none
# authorization: none
# vpn: false
# ip_filtered: false
# readonly: true
# usage: devops
# data_assets_sent:
# - argo-cd-container-image-tag
# data_assets_received:
# - argo-cd-container-image
Fetching Rendered Manifests:
target: repo-server
description: Fetch manifests from the repo server to display via UI or CLI.
protocol: https # values: see help
authentication: none # values: none, credentials, session-id, token, client-certificate, two-factor
authorization: none # values: none, technical-user, enduser-identity-propagation
tags:
vpn: false
ip_filtered: true
readonly: true
usage: devops # values: business, devops
data_assets_sent: # sequence of IDs to reference
- application-name
data_assets_received: # sequence of IDs to reference
- rendered-manifests
Get/Update/Delete Live Resource State from Kubernetes (Host):
target: host-cluster-kubernetes-api
description: Get the live state of an Argo CD-managed resource, or potentially update or delete a resource.
protocol: https
authentication: token
authorization: technical-user
readonly: false
usage: devops
data_assets_sent:
- application-name
- rendered-manifests
- cluster-access-credentials
- cluster-access-configuration
- argo-cd-rbac-config
- repo-access-credentials
- oidc-configuration
- oidc-client-secret
vpn: false
ip_filtered: false
data_assets_received:
- live-manifests
- api-server-secret
- cluster-access-credentials
- cluster-access-configuration
- repo-access-credentials
- argo-cd-rbac-config
- oidc-configuration
- oidc-client-secret
Get/Update/Delete Live Resource State from Kubernetes (External):
target: external-cluster-kubernetes-api
description: >
Get the live state of an Argo CD-managed resource, or potentially update or delete a resource on an
external cluster.
protocol: https
authentication: token
authorization: technical-user
readonly: false
usage: devops
data_assets_sent:
- application-name
- rendered-manifests
- cluster-access-credentials
vpn: false
ip_filtered: false
data_assets_received:
- live-manifests
Update Repo Access Credentials:
target: host-cluster-kubernetes-api
description: Write changes from the UI/CLI/API to repo secrets.
protocol: https
authentication: token
authorization: technical-user
readonly: false
usage: devops
vpn: false
ip_filtered: false
data_assets_sent:
- repo-access-credentials
data_assets_received:
- repo-access-credentials
Update Cluster Access Config:
target: host-cluster-kubernetes-api
description: Write changes from the UI/CLI/API to cluster secrets.
protocol: https
authentication: token
authorization: technical-user
readonly: false
usage: devops
vpn: false
ip_filtered: false
data_assets_sent:
- cluster-access-credentials
- cluster-access-configuration
data_assets_received:
- cluster-access-credentials
- cluster-access-configuration
Update RBAC Config:
target: host-cluster-kubernetes-api
description: Write changes from the UI/CLI/API to RBAC config.
protocol: https
authentication: token
authorization: technical-user
readonly: false
usage: devops
vpn: false
ip_filtered: false
data_assets_sent:
- argo-cd-rbac-config
data_assets_received:
- argo-cd-rbac-config
Validate Dex OIDC Token:
target: dex-server
description: Get public keys from Dex server to validate tokens.
protocol: https
authentication: none
authorization: none
readonly: true
usage: devops
vpn: false
ip_filtered: true
data_assets_received:
- oidc-public-keys
data_assets_sent:
Validate External OIDC Token:
target: oidc-provider
description: Get public keys from OIDC provider to validate tokens.
protocol: https
authentication: none
authorization: none
readonly: true
usage: business
vpn: false
ip_filtered: false
data_assets_received:
- oidc-public-keys
data_assets_sent:
Application Controller:
id: application-controller
description: Some Description
type: process # values: external-entity, process, datastore
usage: devops # values: business, devops
used_as_client_by_human: false
out_of_scope: false
size: component # values: system, service, application, component
technology: web-service-rest # values: see help
internet: false
machine: container # values: physical, virtual, container, serverless
encryption: data-with-symmetric-shared-key # values: none, transparent, data-with-symmetric-shared-key, data-with-asymmetric-shared-key, data-with-enduser-individual-key
owner: Argo CD Operator
confidentiality: confidential # values: public, internal, restricted, confidential, strictly-confidential
integrity: mission-critical # values: archive, operational, important, critical, mission-critical
availability: critical # values: archive, operational, important, critical, mission-critical
justification_cia_rating: >
The application controller is responsible for deploying applications. It contains sensitive information, i.e.
deployment manifests. Changes to these manifests can change what's deployed. If the application controller is
down, no other services will be disrupted, but no deployments will be made.
multi_tenant: true
redundant: false
custom_developed_parts: true
data_assets_processed: # sequence of IDs to reference
- rendered-manifests
- cluster-access-credentials
- cluster-access-configuration
- live-manifests
- argo-cd-container-image-tag
- argo-cd-container-image
data_assets_stored: # sequence of IDs to reference
data_formats_accepted: # sequence of formats like: json, xml, serialization, file, csv
- json
communication_links:
# Pull Argo CD Image:
# target: quay
# description: Pull the Argo CD container image from Quay.
# protocol: https
# authentication: none
# authorization: none
# vpn: false
# ip_filtered: false
# readonly: true
# usage: devops
# data_assets_sent:
# - argo-cd-container-image-tag
# data_assets_received:
# - argo-cd-container-image
Rendered Manifest Requests:
target: repo-server
description: Fetch manifests from the repo server to be applied to the cluster.
protocol: https # values: see help
authentication: none # values: none, credentials, session-id, token, client-certificate, two-factor
authorization: none # values: none, technical-user, enduser-identity-propagation
tags:
vpn: false
ip_filtered: true
readonly: true
usage: devops # values: business, devops
data_assets_sent: # sequence of IDs to reference
- application-name
data_assets_received: # sequence of IDs to reference
- rendered-manifests
Reconcile Resource State (Host Cluster):
target: host-cluster-kubernetes-api
description: Reconcile the current desired manifests with the live state.
protocol: https
authorization: technical-user
authentication: token
vpn: false
ip_filtered: false
readonly: false
usage: devops
data_assets_sent:
- rendered-manifests
- application-name
data_assets_received:
- live-manifests
Reconcile Resource State (External Cluster):
target: external-cluster-kubernetes-api
description: Reconcile the current desired manifests with the live state in an external cluster.
protocol: https
authorization: technical-user
authentication: token
vpn: false
ip_filtered: false
readonly: false
usage: devops
data_assets_sent:
- rendered-manifests
- application-name
- cluster-access-credentials
data_assets_received:
- live-manifests
ApplicationSet Controller:
id: applicationset-controller
description: Some Description
type: process # values: external-entity, process, datastore
usage: devops # values: business, devops
used_as_client_by_human: false
out_of_scope: false
size: component # values: system, service, application, component
technology: web-service-rest # values: see help
internet: false
machine: container # values: physical, virtual, container, serverless
encryption: data-with-symmetric-shared-key # values: none, transparent, data-with-symmetric-shared-key, data-with-asymmetric-shared-key, data-with-enduser-individual-key
owner: Argo CD Operator
confidentiality: confidential # values: public, internal, restricted, confidential, strictly-confidential
integrity: mission-critical # values: archive, operational, important, critical, mission-critical
availability: critical # values: archive, operational, important, critical, mission-critical
justification_cia_rating: >
The ApplicationSet controller is responsible for deploying ApplicationSets. It contains sensitive information, i.e.
deployment manifests. Changes to these manifests can change what's deployed.
multi_tenant: true
redundant: false
custom_developed_parts: true
data_assets_processed: # sequence of IDs to reference
- cluster-access-credentials
- cluster-access-configuration