ibibek commited on
Commit
8a752cf
1 Parent(s): ae0b7f2

Upload ae_ontology.ttl

Browse files
Files changed (1) hide show
  1. docs/ae_ontology.ttl +794 -0
docs/ae_ontology.ttl ADDED
@@ -0,0 +1,794 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+ @prefix attack: <https://ontology.adversaryengagement.org/ae/attack/> .
3
+ @prefix engagement: <https://ontology.adversaryengagement.org/ae/engagement/> .
4
+ @prefix identity: <https://ontology.adversaryengagement.org/ae/identity/> .
5
+ @prefix objective: <https://ontology.adversaryengagement.org/ae/objective/> .
6
+ @prefix owl: <http://www.w3.org/2002/07/owl#> .
7
+ @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
8
+ @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
9
+ @prefix role: <https://ontology.adversaryengagement.org/ae/role/> .
10
+ @prefix sh: <http://www.w3.org/ns/shacl#> .
11
+ @prefix uco-action: <https://ontology.unifiedcyberontology.org/uco/action/> .
12
+ @prefix uco-core: <https://ontology.unifiedcyberontology.org/uco/core/> .
13
+ @prefix uco-identity: <https://ontology.unifiedcyberontology.org/uco/identity/> .
14
+ @prefix uco-observable: <https://ontology.unifiedcyberontology.org/uco/observable/> .
15
+ @prefix uco-role: <https://ontology.unifiedcyberontology.org/uco/role/> .
16
+ @prefix uco-types: <https://ontology.unifiedcyberontology.org/uco/types/> .
17
+ @prefix vocabulary: <https://ontology.adversaryengagement.org/ae/vocabulary/> .
18
+ @prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
19
+
20
+
21
+
22
+
23
+ attack:AttackPattern a owl:Class,
24
+ sh:NodeShape ;
25
+ rdfs:label "AttackPattern"@en ;
26
+ rdfs:comment "An attack pattern is a common approach (set of actions) utilized by a person or organization to carry out malicious activity intended to achieve some particular objective (within a particular context) against a targeted victim."@en ;
27
+ rdfs:subClassOf uco-action:ActionPattern ;
28
+ sh:property
29
+ [
30
+ sh:class engagement:Objective ;
31
+ sh:nodeKind sh:IRI ;
32
+ sh:path objective:hasObjective
33
+ ] ;
34
+ sh:targetClass attack:AttackPattern .
35
+
36
+
37
+
38
+ attack:CyberKillChain a owl:Class,
39
+ sh:NodeShape ;
40
+ rdfs:label "CyberKillChain"@en ;
41
+ rdfs:comment "An cyber kill chain is an ordered sequence of actions or events describing a lifecycle from some framework."@en ;
42
+ rdfs:subClassOf uco-action:ActionLifecycle ;
43
+ sh:targetClass attack:CyberKillChain .
44
+
45
+
46
+
47
+
48
+ attack:DefensePattern a owl:Class,
49
+ sh:NodeShape ;
50
+ rdfs:label "AttackPattern"@en ;
51
+ rdfs:comment "A defense pattern is a common approach (set of actions) utilized by a person or organization to carry out defensive activity intended to achieve some particular objective (within a particular context) against malicious activity."@en ;
52
+ rdfs:subClassOf uco-action:ActionPattern ;
53
+ sh:property
54
+ [
55
+ sh:class engagement:Objective ;
56
+ sh:nodeKind sh:IRI ;
57
+ sh:path objective:hasObjective
58
+ ] ;
59
+ sh:targetClass attack:DefensePattern .
60
+
61
+
62
+ # Actions
63
+
64
+ #Release Version: 0.1.8
65
+ engagement:Access a owl:Class,
66
+ sh:NodeShape ;
67
+ rdfs:label "Access"@en ;
68
+ rdfs:comment "An Access action refers to an observed or deduced interaction between an entity and an object."@en ;
69
+ rdfs:subClassOf uco-action:Action ;
70
+ sh:property
71
+ [
72
+ sh:datatype xsd:string ;
73
+ sh:hasValue "Access" ;
74
+ sh:maxCount "1"^^xsd:integer ;
75
+ sh:minCount "1"^^xsd:integer ;
76
+ sh:nodeKind sh:Literal ;
77
+ sh:path uco-core:name ;
78
+ ] ;
79
+ sh:targetClass engagement:Access .
80
+
81
+ engagement:Alert a owl:Class,
82
+ sh:NodeShape ;
83
+ rdfs:label "Alert"@en ;
84
+ rdfs:comment "An Alert action involves notification to some entity that some condition or event of particular interest has occurred."@en ;
85
+ rdfs:subClassOf uco-action:Action ;
86
+ sh:property
87
+ [
88
+ sh:datatype xsd:string ;
89
+ sh:hasValue "Alert" ;
90
+ sh:maxCount "1"^^xsd:integer ;
91
+ sh:minCount "1"^^xsd:integer ;
92
+ sh:nodeKind sh:Literal ;
93
+ sh:path uco-core:name ;
94
+ ] ;
95
+ sh:targetClass engagement:Alert .
96
+
97
+
98
+ #Date Added: 2023-03-31
99
+ #Recent Date Modified: 2023-07-02
100
+ #Release Version: 0.2.0
101
+ #On-going Challenges: How to restrict the performer to be any UcoObject except Identity
102
+ engagement:Beacon a owl:Class,
103
+ sh:NodeShape ;
104
+ rdfs:label "Beacon"@en ;
105
+ rdfs:comment "An Beacon action is refer to communication between two objects where the performer is an object and the object property is an object or dataTarqet. Beacon is designed to differentiate between actions performed by and onto objects and actions performed by and onto identities. "@en ;
106
+ rdfs:subClassOf uco-action:Action ;
107
+ sh:property
108
+ [
109
+ sh:datatype xsd:string ;
110
+ sh:hasValue "Beacon" ;
111
+ sh:maxCount "1"^^xsd:integer ;
112
+ sh:minCount "1"^^xsd:integer ;
113
+ sh:nodeKind sh:Literal ;
114
+ sh:path uco-core:name ;
115
+ ] ;
116
+ sh:targetClass engagement:Beacon .
117
+
118
+
119
+ #Release Version: 0.1.8
120
+ engagement:Deploy a owl:Class,
121
+ sh:NodeShape ;
122
+ rdfs:label "Deploy"@en ;
123
+ rdfs:comment "A Deploy action involves instantiating some deception objects prior or during an operation."@en ;
124
+ rdfs:subClassOf uco-action:Action ;
125
+ sh:property
126
+ [
127
+ sh:datatype xsd:string ;
128
+ sh:hasValue "Deploy" ;
129
+ sh:maxCount "1"^^xsd:integer ;
130
+ sh:minCount "1"^^xsd:integer ;
131
+ sh:nodeKind sh:Literal ;
132
+ sh:path uco-core:name ;
133
+ ] ;
134
+ sh:targetClass engagement:Deploy .
135
+
136
+ engagement:Obfuscate a owl:Class,
137
+ sh:NodeShape ;
138
+ rdfs:label "Obfuscate"@en ;
139
+ rdfs:comment "An Obfuscate action is a transformative action an entity or tool performs to some object to reduce available information associated with that object."@en ;
140
+ rdfs:subClassOf uco-action:Action ;
141
+ sh:property
142
+ [
143
+ sh:datatype xsd:string ;
144
+ sh:hasValue "Obfuscate" ;
145
+ sh:maxCount "1"^^xsd:integer ;
146
+ sh:minCount "1"^^xsd:integer ;
147
+ sh:nodeKind sh:Literal ;
148
+ sh:path uco-core:name ;
149
+ ] ;
150
+ sh:targetClass engagement:Obfuscate .
151
+
152
+ engagement:Respond a owl:Class,
153
+ sh:NodeShape ;
154
+ rdfs:label "Respond"@en ;
155
+ rdfs:comment "A Respond action is a reactive, defensive action to some adversarial detection or alert."@en ;
156
+ rdfs:subClassOf uco-action:Action ;
157
+ sh:property
158
+ [
159
+ sh:datatype xsd:string ;
160
+ sh:hasValue "Respond" ;
161
+ sh:maxCount "1"^^xsd:integer ;
162
+ sh:minCount "1"^^xsd:integer ;
163
+ sh:nodeKind sh:Literal ;
164
+ sh:path uco-core:name ;
165
+ ] ;
166
+ sh:targetClass engagement:Respond .
167
+
168
+
169
+ # Objects
170
+
171
+ #Date Added: 2023-03-31
172
+ #Recent Date Modified: 2023-03-31
173
+ #Release Version: 0.1.9
174
+ engagement:Breadcrumb a owl:Class,
175
+ sh:NodeShape ;
176
+ rdfs:label "Breadcrumb"@en ;
177
+ rdfs:comment "A Breadcrumb is a set of objects placed to be at least partially, sequentially interacted by an adversary to ellicit an explicit response, often in the context of lateral movement."@en ;
178
+ rdfs:subClassOf engagement:LureObject ;
179
+ sh:property
180
+ [
181
+ sh:class uco-core:UcoObject ;
182
+ sh:minCount 1 ;
183
+ sh:nodeKind sh:IRI ;
184
+ sh:path engagement:breadcrumbTargetObject
185
+ ],
186
+ [
187
+ sh:class uco-core:UcoObject ;
188
+ sh:nodeKind sh:IRI ;
189
+ sh:path engagement:hasCharacterization
190
+ ] ;
191
+ sh:targetClass engagement:Breadcrumb .
192
+
193
+
194
+ #Date Added: 2023-03-31
195
+ #Recent Date Modified: 2023-03-31
196
+ #Release Version: 0.1.9
197
+ engagement:BreadcrumbTrail a owl:Class,
198
+ sh:NodeShape ;
199
+ rdfs:label "BreadcrumbTrail"@en ;
200
+ rdfs:comment "A breadcrumb trail is a sequence of observed breadcrumbs where partial order of observation of breadcrumbs matter."@en ;
201
+ rdfs:subClassOf uco-core:UcoObject ;
202
+ sh:property
203
+ [
204
+ sh:class objective:Objective ;
205
+ sh:minCount 1 ;
206
+ sh:nodeKind sh:IRI ;
207
+ sh:path engagement:hasObjective
208
+ ],
209
+ [
210
+ sh:class uco-core:UcoObject ;
211
+ sh:minCount 1 ;
212
+ sh:nodeKind sh:IRI ;
213
+ sh:path engagement:breadcrumbTargetObject
214
+ ],
215
+ [
216
+ sh:class uco-types:Thread ;
217
+ sh:minCount 1 ;
218
+ sh:nodeKind sh:IRI ;
219
+ sh:path engagement:hasBreadcrumb
220
+ ] ;
221
+ sh:targetClass engagement:BreadcrumbTrail .
222
+
223
+
224
+ #Release Version: 0.1.8
225
+ engagement:DataSource a owl:Class,
226
+ sh:NodeShape ;
227
+ rdfs:label "DataSource"@en ;
228
+ rdfs:comment "A datasource is a grouping of characteristics unique to a specific source of data (e.g. a tool that generates event logs)."@en ;
229
+ rdfs:subClassOf uco-core:UcoObject ;
230
+ sh:targetClass engagement:DataSource .
231
+
232
+
233
+ #Release Version: 0.1.9
234
+ engagement:DataTarget a owl:Class,
235
+ sh:NodeShape ;
236
+ rdfs:label "DataTarget"@en ;
237
+ rdfs:comment "A datatarget is a grouping of characteristics unique to a specific target/listener that receives data (e.g. a listening port)."@en ;
238
+ rdfs:subClassOf uco-core:UcoObject ;
239
+ sh:targetClass engagement:DataTarget .
240
+
241
+ #Release Version: 0.1.8
242
+ engagement:Decoy a owl:Class,
243
+ sh:NodeShape ;
244
+ rdfs:label "Decoy"@en ;
245
+ rdfs:comment " A decoy is a placed object that has the perception of enough value to an adversary to pursue but contains no real value."@en ;
246
+ rdfs:subClassOf engagement:LureObject ;
247
+ sh:targetClass engagement:Decoy .
248
+
249
+ engagement:HoneyObject a owl:Class,
250
+ sh:NodeShape ;
251
+ rdfs:label "HoneyObject"@en ;
252
+ rdfs:comment " An domain object that is created to be percieved by an adversary to have high value to pursue in an adversary engagement operation that has no value out of scope of the operation's intended perception."@en ;
253
+ rdfs:subClassOf engagement:LureObject ;
254
+ sh:targetClass engagement:HoneyObject .
255
+
256
+ engagement:Honeypot a owl:Class,
257
+ sh:NodeShape ;
258
+ rdfs:label "Honeypot"@en ;
259
+ rdfs:comment " A controlled environment intended to be probed, compromised or attacked by adversaries or malware."@en ;
260
+ rdfs:subClassOf engagement:HoneyObject ;
261
+ sh:property
262
+ [
263
+ sh:datatype vocabulary:HoneypotInteractionTypeVocab ;
264
+ sh:message "Value is outside the default vocabulary HoneypotInteractionTypeVocab." ;
265
+ sh:path engagement:honeypotInteractionType ;
266
+ sh:severity sh:Info ;
267
+ ] ,
268
+ [
269
+ sh:maxCount "1"^^xsd:integer ;
270
+ sh:nodeKind sh:Literal ;
271
+ sh:or ([ sh:datatype vocabulary:HoneypotInteractionTypeVocab ;] [ sh:datatype xsd:string ;]) ;
272
+ sh:path engagement:honeypotInteractionType ;
273
+ ] ,
274
+ [
275
+ sh:message "Value is not member of the vocabulary HoneypotInteractionTypeVocab." ;
276
+ sh:or ([ sh:datatype vocabulary:HoneypotInteractionTypeVocab ;
277
+ sh:in (
278
+ "High"^^vocabulary:HoneypotTypeVocab
279
+ "Low"^^vocabulary:HoneypotTypeVocab
280
+ "Dynamic"^^vocabulary:HoneypotTypeVocab
281
+ ) ;
282
+ ] [ sh:datatype xsd:string ;]) ;
283
+ sh:path engagement:honeypotInteractionType ;
284
+ ] ;
285
+ sh:targetClass engagement:Honeypot .
286
+
287
+ engagement:HoneyToken a owl:Class,
288
+ sh:NodeShape ;
289
+ rdfs:label "HoneyToken"@en ;
290
+ rdfs:comment "A honey token gives an adversary direct access to a honeypot."@en ;
291
+ rdfs:subClassOf engagement:HoneyObject ;
292
+ sh:targetClass engagement:HoneyToken .
293
+
294
+ engagement:LureObject a owl:Class,
295
+ sh:NodeShape ;
296
+ rdfs:label "LureObject"@en ;
297
+ rdfs:comment " An object or set of objects used to attract an adversary that has the perception of high value regardless if it actually has high value."@en ;
298
+ rdfs:subClassOf uco-core:UcoObject ;
299
+ sh:property
300
+ [
301
+ sh:class uco-core:UcoObject ;
302
+ sh:minCount 1 ;
303
+ sh:nodeKind sh:IRI ;
304
+ sh:path engagement:hasCharacterization
305
+ ] ,
306
+ [
307
+ sh:class uco-core:UcoObject ;
308
+ sh:minCount 1 ;
309
+ sh:nodeKind sh:IRI ;
310
+ sh:path engagement:hasPerceptionCharacterization
311
+ ] ,
312
+ [
313
+ sh:class uco-core:UcoObject ;
314
+ sh:minCount 1 ;
315
+ sh:nodeKind sh:IRI ;
316
+ sh:path engagement:hasAttackSurface
317
+ ] ;
318
+ sh:targetClass engagement:LureObject .
319
+
320
+ engagement:Malware a owl:Class,
321
+ sh:NodeShape ;
322
+ rdfs:label "Malware"@en ;
323
+ rdfs:comment "Malware, also known as malicious code and malicious software, refers to a program that is inserted into a system, usually covertly, with the intent of compromising the confidentiality, integrity, or availability of the victim's data, applications, or operating system (OS) or of otherwise annoying or disrupting the victim. Malware such as viruses and worms are usually designed to perform these nefarious functions in such a way that users are unaware of them, at least initially."@en ;
324
+ rdfs:subClassOf uco-core:UcoObject ;
325
+ sh:targetClass engagement:Malware .
326
+
327
+
328
+ # Planning & Narrative Concepts
329
+
330
+ #Release Version: 0.1.8
331
+ engagement:Event a owl:Class,
332
+ sh:NodeShape ;
333
+ rdfs:label "Event"@en ;
334
+ rdfs:comment "An Event characterizes some occurence."@en ;
335
+ rdfs:subClassOf uco-core:UcoObject ;
336
+ sh:property
337
+ [
338
+ sh:datatype xsd:string ;
339
+ sh:nodeKind sh:Literal ;
340
+ sh:path engagement:eventType ;
341
+ ],
342
+ [
343
+ sh:nodeKind sh:IRI ;
344
+ sh:class uco-core:UcoObject ;
345
+ sh:path engagement:eventContext ;
346
+ ],
347
+ [
348
+ sh:datatype xsd:string ;
349
+ sh:nodeKind sh:Literal ;
350
+ sh:path uco-core:startTime ;
351
+ ],
352
+ [
353
+ sh:datatype xsd:string ;
354
+ sh:nodeKind sh:Literal ;
355
+ sh:path uco-core:endTime ;
356
+ ],
357
+ [
358
+ sh:nodeKind sh:IRI ;
359
+ sh:class uco-types:Dictionary ;
360
+ sh:path engagement:eventAttribute ;
361
+ ] ;
362
+ sh:targetClass engagement:Event .
363
+
364
+ engagement:Narrative a owl:Class,
365
+ sh:NodeShape ;
366
+ rdfs:label "Narrative"@en ;
367
+ rdfs:comment "A narrative is a script of all expected sequence of actions, events, entities and their interactions."@en ;
368
+ rdfs:subClassOf uco-core:UcoObject ;
369
+ sh:property
370
+ [
371
+ sh:class uco-core:UcoObject ;
372
+ sh:minCount 1 ;
373
+ sh:nodeKind sh:IRI ;
374
+ sh:path engagement:hasStoryline
375
+ ] ,
376
+ [
377
+ sh:class uco-core:UcoObject ;
378
+ sh:minCount 1 ;
379
+ sh:nodeKind sh:IRI ;
380
+ sh:path engagement:hasObjective
381
+ ] ;
382
+ sh:targetClass engagement:Narrative .
383
+
384
+ engagement:PlannedEvent a owl:Class,
385
+ sh:NodeShape ;
386
+ rdfs:label "PlannedEvent"@en ;
387
+ rdfs:comment "A PlannedEvent is a collection of actions, entities, interactions designated to be performed at some sequentially indexed time in a Storyline or Narrative"@en ;
388
+ rdfs:subClassOf uco-core:UcoObject ;
389
+ sh:property
390
+ [
391
+ sh:class uco-core:UcoObject ;
392
+ sh:minCount 1 ;
393
+ sh:nodeKind sh:IRI ;
394
+ sh:path engagement:eventContext
395
+ ] ,
396
+ [
397
+ sh:class uco-core:UcoObject ;
398
+ sh:minCount 1 ;
399
+ sh:nodeKind sh:IRI ;
400
+ sh:path engagement:hasObjective
401
+ ] ;
402
+ sh:targetClass engagement:PlannedEvent .
403
+
404
+ engagement:PocketLitter a owl:Class,
405
+ sh:NodeShape ;
406
+ rdfs:label "PocketLitter"@en ;
407
+ rdfs:comment "Pocket litter describes objects placed prior or during an adversary engagement operation for the purpose of realism."@en ;
408
+ rdfs:subClassOf uco-core:UcoObject ;
409
+ sh:property
410
+ [
411
+ sh:class uco-core:UcoObject ;
412
+ sh:minCount 1 ;
413
+ sh:nodeKind sh:IRI ;
414
+ sh:path engagement:hasCharacterization
415
+ ] ;
416
+ sh:targetClass engagement:PocketLitter .
417
+
418
+ engagement:Resource a owl:Class,
419
+ sh:NodeShape ;
420
+ rdfs:label "Resource"@en ;
421
+ rdfs:comment " A resource can be a tool, location or object which requires some operational cost to enable availability."@en ;
422
+ rdfs:subClassOf uco-core:UcoObject ;
423
+ sh:targetClass engagement:Resource .
424
+
425
+ engagement:Sandbox a owl:Class,
426
+ sh:NodeShape ;
427
+ rdfs:label "Sandbox"@en ;
428
+ rdfs:comment " A controlled environment intended for malware detonation and malware analysis."@en ;
429
+ rdfs:subClassOf uco-core:UcoObject ;
430
+ sh:property
431
+ [
432
+ sh:class uco-core:UcoObject ;
433
+ sh:minCount 1 ;
434
+ sh:nodeKind sh:IRI ;
435
+ sh:path engagement:hasCharacterization
436
+ ] ;
437
+ sh:targetClass engagement:Sandbox .
438
+
439
+
440
+ engagement:Storyline a owl:Class,
441
+ sh:NodeShape ;
442
+ rdfs:label "Storyline"@en ;
443
+ rdfs:comment "A Storyline is a sequence of semi-ordered planned events as an expected trajectory for a narrative."@en ;
444
+ rdfs:subClassOf uco-core:UcoObject ;
445
+ sh:property
446
+ [
447
+ sh:class uco-types:Thread ;
448
+ sh:minCount 1 ;
449
+ sh:nodeKind sh:IRI ;
450
+ sh:path engagement:hasEvent ;
451
+ ] ;
452
+ sh:targetClass engagement:Storyline .
453
+
454
+
455
+
456
+ # Properties
457
+
458
+ #Release Version: 0.1.8
459
+ engagement:alertContext a owl:ObjectProperty;
460
+ rdfs:label "alertContext"@en ;
461
+ rdfs:comment "An alert context describes the association of actions and objects relating to an alert."@en ;
462
+ rdfs:range uco-core:UcoObject .
463
+
464
+ #Date Added: 2023-07-23
465
+ #Release Version: 0.2.0
466
+ engagement:hasAttackSurface a owl:ObjectProperty,
467
+ sh:NodeShape ;
468
+ rdfs:label "hasAttackSurface"@en ;
469
+ rdfs:comment "hasAttackSurface is an object property which describes the UcoObjects which compose the attack surface which is expected to interacted with by an adversary."@en ;
470
+ rdfs:range uco-core:UcoObject .
471
+
472
+ #Release Version: 0.1.8
473
+ engagement:eventContext a owl:ObjectProperty;
474
+ rdfs:label "eventContext"@en ;
475
+ rdfs:comment "An event context describes the association of actions and objects relating to an event."@en ;
476
+ rdfs:range uco-core:UcoObject .
477
+
478
+ engagement:eventAttribute a owl:ObjectProperty;
479
+ rdfs:label "eventAttribute"@en ;
480
+ rdfs:comment "An event attribute specifies an ad-hoc attribute/value for an event."@en ;
481
+ rdfs:range uco-types:Dictionary .
482
+
483
+ engagement:eventType a owl:DatatypeProperty;
484
+ rdfs:label "eventType"@en ;
485
+ rdfs:comment "An event type specifies a classification type for the event."@en ;
486
+ rdfs:range xsd:string .
487
+
488
+ #Date Added: 2023-03-31
489
+ #Recent Date Modified: 2023-03-31
490
+ #Release Version: 0.1.9
491
+ engagement:breadcrumbTargetObject a owl:ObjectProperty;
492
+ rdfs:label "breadcrumbTargetObject"@en ;
493
+ rdfs:comment "breadcrumbTargetObject specifies the target object or resource which the breadcrumb is luring an adversary to."@en ;
494
+ rdfs:range uco-core:UcoObject .
495
+
496
+ #Release Version: 0.1.8
497
+ engagement:hasCharacterization a owl:ObjectProperty,
498
+ sh:NodeShape ;
499
+ rdfs:label "hasCharacterization"@en ;
500
+ rdfs:comment "hasCharacterization is an object property which describes the UcoObjects which compose a deception object or adversary engagement concept."@en ;
501
+ rdfs:range uco-core:UcoObject .
502
+
503
+ #Date Added: 2023-07-23
504
+ #Release Version: 0.2.0
505
+ engagement:hasPerceptionCharacterization a owl:ObjectProperty,
506
+ sh:NodeShape ;
507
+ rdfs:label "hasPerceptionCharacterization"@en ;
508
+ rdfs:comment "hasPerceptionCharacterization is an object property which describes the UcoObjects which compose the perception object which an adversary perceives."@en ;
509
+ rdfs:range uco-core:UcoObject .
510
+
511
+
512
+ engagement:hasEvent a owl:ObjectProperty;
513
+ rdfs:label "hasEvent"@en ;
514
+ rdfs:comment "hasEvent specifies an ordered list of associated Events."@en ;
515
+ rdfs:range uco-types:Thread .
516
+
517
+ engagement:hasBreadcrumb a owl:ObjectProperty;
518
+ rdfs:label "hasBreadcrumb"@en ;
519
+ rdfs:comment "hasBreadcrumb specifies an ordered list of associated Breadcrumbs."@en ;
520
+ rdfs:range uco-types:Thread .
521
+
522
+ engagement:hasStoryline a owl:ObjectProperty;
523
+ rdfs:label "hasStoryline"@en ;
524
+ rdfs:comment "hasStoryline identifies a Storyline that is part of a Narrative."@en ;
525
+ rdfs:range engagement:Storyline .
526
+
527
+ engagement:honeypotInteractionType a owl:DatatypeProperty ;
528
+ rdfs:label "honeypotInteractionType"@en ;
529
+ rdfs:comment "The interaction class intended for a honeypot."@en ;
530
+ rdfs:range [ a rdfs:Datatype ;
531
+ owl:unionOf ( vocabulary:HoneypotInteractionTypeVocab xsd:string ) ] .
532
+
533
+
534
+
535
+
536
+
537
+
538
+
539
+ identity:Persona a owl:Class,
540
+ sh:NodeShape ;
541
+ rdfs:label "Persona"@en ;
542
+ rdfs:comment " An persona is a facticious entity created to serve a purpose in a deception operation."@en ;
543
+ rdfs:subClassOf uco-identity:Identity ;
544
+ sh:targetClass identity:Persona .
545
+
546
+
547
+ identity:Team a owl:Class,
548
+ sh:NodeShape ;
549
+ rdfs:label "Team"@en ;
550
+ rdfs:comment "The conventional reference to group of identities that are associated with some unified identity with a team objective"@en ;
551
+ rdfs:subClassOf uco-identity:Organization ;
552
+ sh:property
553
+ [
554
+ sh:class objective:Objective ;
555
+ sh:nodeKind sh:IRI ;
556
+ sh:path objective:hasObjective
557
+ ] ;
558
+ sh:targetClass identity:Team .
559
+
560
+
561
+ # Classes
562
+
563
+ objective:Objective a owl:Class,
564
+ sh:NodeShape ;
565
+ rdfs:label "Objective"@en ;
566
+ rdfs:comment "An objective is some particular condition or state that is desired to be achieved and toward which effort is directed: an aim, goal, or end of action."@en ;
567
+ rdfs:subClassOf uco-core:UcoObject ;
568
+ sh:targetClass objective:Objective .
569
+
570
+
571
+ # Properties
572
+
573
+ objective:hasObjective a owl:ObjectProperty,
574
+ sh:NodeShape ;
575
+ uco-core:name "hasObjective"@en ;
576
+ uco-core:description "An object which can be associated with an objective."@en ;
577
+ rdfs:range objective:Objective .
578
+
579
+ # Individuals
580
+
581
+ # ATT&CK Objectives
582
+
583
+
584
+ objective:CommandAndControl a objective:Objective ;
585
+ uco-core:name "Command and Control"@en ;
586
+ uco-core:description "A Command and Control objective is defined by MITRE ATT&CK Tactic TA0011 (Command and Control) and involves an adversary's capability to communicate with compromised systems to control them."@en ;
587
+ .
588
+
589
+
590
+
591
+ objective:CredentialAccess a objective:Objective ;
592
+ uco-core:name "Access Credentials"@en ;
593
+ uco-core:description "An Access Credentials (Credential Access) objective is defined by MITRE ATT&CK Tactic TA0006 (Credential Access) and involves an adversary's capability to steal account names and passwords."@en ;
594
+ .
595
+
596
+
597
+ objective:DevelopResource a objective:Objective ;
598
+ uco-core:name "Develop Resource"@en ;
599
+ uco-core:description "A Develop Resource (Resource Development) objective is defined by MITRE ATT&CK Tactic TA0042 (Resource Development) and involves an adversary's capability to establish resources they can use to support operations."@en ;
600
+ .
601
+
602
+
603
+
604
+ objective:Discover a objective:Objective ;
605
+ uco-core:name "Discover"@en ;
606
+ uco-core:description "A Discover (Discovery) objective is defined by MITRE ATT&CK Tactic TA0007 (Discovery) and involves an adversary's capability to learn about and understand details of a targeted environment."@en ;
607
+ .
608
+
609
+
610
+ objective:EscalatePrivilege a objective:Objective ;
611
+ uco-core:name "Escalate Privilege"@en ;
612
+ uco-core:description "An Escalate Privilege (PrivilegeEscalation) objective is defined by MITRE ATT&CK Tactic TA0004 (Privilege Escalation) and involves an adversary's capability to gain higher-level permissions within a targeted environment."@en ;
613
+ .
614
+
615
+
616
+ objective:Evade a objective:Objective ;
617
+ uco-core:name "Evade"@en ;
618
+ uco-core:description "An Evade (Defense Evasion) objective is defined by MITRE ATT&CK Tactic TA0005 (Defense Evasion) and involves an adversary's capability to avoid detection from some defense or entity."@en ;
619
+ .
620
+
621
+
622
+ objective:Execute a objective:Objective ;
623
+ uco-core:name "Execute"@en ;
624
+ uco-core:description "An Execute (Execution) objective is defined by MITRE ATT&CK Tactic TA0002 (Execution) and involves an adversary's capability to run malicious code within a targeted environment."@en ;
625
+ .
626
+
627
+
628
+ objective:Exfilitrate a objective:Objective ;
629
+ uco-core:name "Exfilitrate"@en ;
630
+ uco-core:description "An Exfilitrate (Exfiltration) is defined by MITRE ATT&CK Tactic TA0010 (Exfiltration) and involves an adversary's capability to remove stolen data from targeted environments."@en ;
631
+ .
632
+
633
+
634
+ objective:GainInitialAccess a objective:Objective ;
635
+ uco-core:name "Gain Initial Access"@en ;
636
+ uco-core:description "A Gain Initial Access (InitialAccess) objective is defined by MITRE ATT&CK Tactic TA0001 (Initial Access) and involves an adversary's capability to penetrate and gain illicit access to a targeted environment."@en ;
637
+ .
638
+
639
+
640
+ objective:Impact a objective:Objective ;
641
+ uco-core:name "Impact"@en ;
642
+ uco-core:description "An Impact objective is defined by MITRE ATT&CK Tactic TA0040 (Impact) and involves an adversary's capability to manipulate, interrupt, or destroy targeted systems and data."@en ;
643
+ .
644
+
645
+
646
+ objective:MoveLaterally a objective:Objective ;
647
+ uco-core:name "MoveLaterally"@en ;
648
+ uco-core:description "A Move Laterally (Lateral Movement) objective is defined by MITRE ATT&CK Tactic TA0008 (Lateral Movement) and involves an adversary's capability to move through a targeted environment."@en ;
649
+ .
650
+
651
+
652
+ objective:Persist a objective:Objective ;
653
+ uco-core:name "Persist"@en ;
654
+ uco-core:description "A Persist (Persistence) objective is defined by MITRE ATT&CK Tactic TA0003 (Persistence) and involves an adversary's capability to maintain their access foothold within a changing targeted environment."@en ;
655
+ .
656
+
657
+
658
+ objective:Reconnaissance a objective:Objective ;
659
+ uco-core:name "Reconnaissance"@en ;
660
+ uco-core:description "A Reconnaissance objective is defined by MITRE ATT&CK Tactic TA0043 (Reconnaissance) and involves an adversary's capability to gather information they can use to plan future operations."@en ;
661
+ .
662
+
663
+
664
+ # ENGAGE Objectives
665
+
666
+ objective:Affect a objective:Objective ;
667
+ uco-core:name "Affect"@en ;
668
+ uco-core:description "An Affect objective is defined by MITRE ENGAGE EGO0002 (Affect) and involves the capability to negatively impact an adversary's operations. Affect is ultimately about changing the cost-value proposition in cyber operations for the adversary. The defender may want to increase the adversary’s cost to operate or drive down the value they derive from their operations. For example, the defender can negatively impact the adversary’s on-network operations to drive up the resource cost of doing operations by slowing down or selectively resetting connections to impact exfiltration. This type of activity increases the adversary’s time on target and wastes their resources. To drive down the value of stolen data, a defender could provide an adversary deliberately conflicting information. Providing such information requires an adversary to either choose to believe one piece of data over another, disregard both, collect more data, or continue with uncertainty."@en ;
669
+ .
670
+
671
+ objective:Collect a objective:Objective ;
672
+ uco-core:name "Collect"@en ;
673
+ uco-core:description "A Collect (Collection) objective is defined by MITRE ATT&CK Tactic TA0009 (Collection) and by MITRE ENGAGE EAP0001 (Collect) and involves the capability to gather data of interest to a particular goal. MITRE ATT&CK defines this within the context of an adversary's goal to gather data from a targeted environment. MITRE ENGAGE defines this within the context of a defender's goal to gather data about an adversary's tools, tactics, or other raw intelligence about the adversary’s activity."@en ;
674
+ .
675
+
676
+ objective:Detect a objective:Objective ;
677
+ uco-core:name "Detect"@en ;
678
+ uco-core:description "A Detect objective is defined by MITRE ENGAGE EAP0002 (Detect) and involves the capability to establish or maintain awareness regarding adversary activity. Detection activities focus on the defender’s ability to monitor adversary activity throughout an environment, often by creating high-fidelity detections. These detections can be produced in several ways. For example, a defender can deploy lures as tripwires in the environment. The defender may create custom alerts based on TTPs or IOCs observed during a malware detonation operation. Finally, the defender may write customer decoders to analyze and alert on malicious traffic. In all these cases, detection activities allow the defender to produce a high-fidelity alert to monitor adversary activities. Often Detection activities are also good cybersecurity practices. However, in Engage, these activities will focus exclusively on the intersection of denial, deception, and adversary engagement technologies and the defender’s ability to Expose the adversary."@en ;
679
+ .
680
+
681
+ objective:Direct a objective:Objective ;
682
+ uco-core:name "Direct"@en ;
683
+ uco-core:description "A Direct objective is defined by MITRE ENGAGE EAP0004 (Direct) and involves the capability to encourage or discourage an adversary from conducting their operation as intended. Direction activities focus on moving the adversary towards or away from an intended path. This forced direction can be accomplished by removing or disabling some resources, while adding or enabling others. The defender can add lures or otherwise manipulate the environment to attempt to elicit specific responses from the adversary. Additionally, the defender can tighten some security controls while leaving others overly permissive or weakened. Finally, the defender can physically move the adversary by moving threats from their intended environment and into a safe engagement environment. For example, a suspicious email attachment can be moved from the intended target to an engagement environment for analysis. No matter how the direction is achieved, the defender hopes to force the adversary to take unintended actions or stop intended actions."@en ;
684
+ .
685
+
686
+ objective:Disrupt a objective:Objective ;
687
+ uco-core:name "Disrupt"@en ;
688
+ uco-core:description "A Disrupt objective is defined by MITRE ENGAGE EAP0005 (Disrupt) and involves the capability to impair an adversary’s ability to conduct their operation as intended. Disruption activities are used to stop or discourage an adversary from conducting part or all of their mission. This disruption may increase the time, skills, or resources needed for the adversary to accomplish a specific task. For example, a defender may degrade network speeds as the adversary attempts to exfiltrate large blocks of data. As a second example, the defender may manipulate the output of commonly used discovery commands to show targets that do not exist or to hide real targets. In either case, the adversary may waste resources acting on partial or falsified data. Disruptions may also include planting misinformation designed to influence the adversary’s decision-makers to make the wrong decisions or to waste resources."@en ;
689
+ .
690
+
691
+ objective:Elicit a objective:Objective ;
692
+ uco-core:name "Elicit"@en ;
693
+ uco-core:description "An Elicit objective is defined by MITRE ENGAGE EGO0003 (Elicit) and involves the capability to learn about an adversary's tactics, techniques, and procedures (TTPs). Elicit encourages adversaries to reveal additional or more advanced TTPs and goals while operating in defender-controlled engagement environments. These high-fidelity, synthetic engagement environments are uniquely tailored to engage with specific adversaries. They may contain a combination of documents, browser artifacts, etc. to reassure an adversary and reduce suspicion. Further, they may offer enticing data and exploitable vulnerabilities to motivate an adversary to operate in the defender’s environment. These environments can either be left as a dangle, i.e., honeypot. Other times, the defender may self-infect with malware. In either case, observing an adversary as they operate can provide organizations with actionable cyber threat intelligence and potential understanding of the adversary’s goals."@en ;
694
+ .
695
+
696
+ objective:Expose a objective:Objective ;
697
+ uco-core:name "Expose"@en ;
698
+ uco-core:description "An Expose objective is defined by MITRE ENGAGE EGO0001 (Expose) and involves the capability to reveal the presence of ongoing adversary operations. Expose is about discovering previously undetected adversaries engaging in one of two behaviors. First, the adversary may be attempting to gain access to the networks. Second, the adversary may be currently operating on the networks. Both categories of adversary behavior contain vulnerabilities that can be advantageous for a defender seeking to expose the adversary. As an example of such a vulnerability, when an adversary interacts with network or system resources, they are vulnerable to trigger tripwires. The defender can make and leak fake credentials both inside and outside of the network. The defender can then monitor for the use of these credentials. Then, when an adversary uses a fake credential, the defender will receive a high-fidelity alert. In addition, if the credentials are unique, a defender may be able to detect how and when an adversary collected the credentials. Whenever a defender seeks to engage with an adversary, operational safety is paramount. To maintain this safety, it is a best practice to monitor adversaries as they operate in an engagement environment. Additionally, the defender must be able to observe the adversary. Therefore, collection and detection activities can often be utilized even when a defender may have other strategic goals in mind."@en ;
699
+ .
700
+
701
+ objective:Motivate a objective:Objective ;
702
+ uco-core:name "Motivate"@en ;
703
+ uco-core:description "A Motivate objective is defined by MITRE ENGAGE EAP0007 (Motivate) and involves the capability to encourage an adversary to conduct part or all of their mission. Motivating activities is used to encourage an adversary to conduct part or all of their mission by providing a target-rich environment. To do this, the defender can use unpatched versions of operating systems and software, remove end-point detection software, and use weak passwords. Additionally, the defender can open firewall ports, add proxy capabilities, or introduce elements that an adversary can easily leverage to bypass an obstacle in their operations. Finally, the defender can include enticing data to the environment to encourage the adversary to steal the data."@en ;
704
+ .
705
+
706
+ objective:Plan a objective:Objective ;
707
+ uco-core:name "Plan"@en ;
708
+ uco-core:description "A Plan objective is defined by MITRE ENGAGE SAP0001 (Plan) and involves the capability to identify and align an operation with a desired end-state. Planning is used to identify and align an operation within the context of strategic goals. By helping the defender to first identify their goals, Planning ensures that all engagement activities are focused and driving forward progress. Additionally, planning ensures that the defender can integrate the inputs of the various stakeholders at the beginning of an operation to ensure that the operation is efficient, effective, and safe. Finally, Planning activities ensure that each operation is informed by the successes and learns from the failures of past operations."@en ;
709
+ .
710
+
711
+ objective:Prepare a objective:Objective ;
712
+ uco-core:name "Prepare"@en ;
713
+ uco-core:description "A Prepare objective is defined by MITRE ENGAGE SGO0001 (Prepare) and involves the capability to help a defender think about what they want to accomplish with operations. Prepare is used to ensure the defender drives progress during adversary engagement operations towards a desired end-state or Strategic Goal. To support this aim, the defender must first generate a clear picture of their organization and the threat landscape. This understanding should include their current security posture, including known strengths and weaknesses, and an inventory of priority cyber assets, including key intellectual property. The defender should then examine and update the threat models for any identified adversaries. These various assessments and models should enable the defender to identify their strategic goal. At this point, all activities should be aligned with this goal. Once a goal has been selected, the defender must work to plan for the operation by identifying a target adversary, creating the necessary Personas, generating an operational storyboard, etc. Finally, the key stakeholders should be called on to establish rules for operational safety and acceptable risk. At each step in the planning process, the defender should incorporate intelligence gained from previous operations to ensure that future operations can run more effectively and efficiently. Engage seeks to highlight that denial, deception, and adversary engagement activities cannot be viewed as `fire and forget`. Unlike many defensive technologies, these activities must be viewed only in context of how they inform and drive progress towards larger strategic goals. To this end, Prepare is essential to ensure that every action taken in an engagement operation drives progress towards a unified goal."@en ;
714
+ .
715
+
716
+ objective:Prevent a objective:Objective ;
717
+ uco-core:name "Prevent"@en ;
718
+ uco-core:description "A Prevent objective is defined by MITRE ENGAGE EAP0003 (Prevent) and involves the capability to stop all or part of an adversary’s ability to conduct their operation as intended. Prevention activities focus on stopping the adversary’s ability to conduct their operations as intended. The defender can physically or virtually remove or disable resources, tighten security controls, or otherwise impair the adversary’s ability to operate. A defender might prevent an adversary from operating to force them to reveal different, possibly more advanced, capabilities. Additionally, a defender can use prevention activities to discourage the adversary from operating against a specific target. In this case, the defender may be attempting to encourage the adversary to focus elsewhere in the engagement environment. There are many more prevention activities that are also good cybersecurity practices. However, in Engage, we are focused on a subset of activities. Those are focused exclusively on the intersection of denial, deception, and adversary engagement technologies and the defender’s ability to Affect the adversary."@en ;
719
+ .
720
+
721
+ objective:Reassure a objective:Objective ;
722
+ uco-core:name "Reassure"@en ;
723
+ uco-core:description "A Reassure objective is defined by MITRE ENGAGE EAP0006 (Reassure) and involves the capability to add authenticity to deceptive components to convince an adversary that an environment is real. Reassurance activities are used to add authenticity to deceptive components to reduce adversary suspicion about the legitimacy of the environment. Activities include adding realistic user accounts, files, system activity, and any other content that an adversary might expect to find on the system. These activities may add new artifacts, such as peripherals and pocket litter, while concealing others, such as how recently an environment was stood up. If done correctly, reassuring an adversary may help to make them feel more comfortable upon landing in a new environment. This initial level of comfort can help anchor the adversary in the environment, increasing their tolerance to faults or weaknesses discovered later."@en ;
724
+ .
725
+
726
+
727
+ # Adversary Engagement Ontology Native Objectives
728
+
729
+ objective:Deny a objective:Objective ;
730
+ uco-core:name "Deny"@en ;
731
+ uco-core:description "A Deny (Denial) objective is to limit an adversary's capabilities or accessibility to a resource."@en ;
732
+ .
733
+
734
+ objective:ElicitBehavior a objective:Objective ;
735
+ uco-core:name "Elicit Behavior"@en ;
736
+ uco-core:description "An Elicit Behavior objective is to have an adversary or target object to exhibit some expected behavior."@en ;
737
+ .
738
+
739
+ objective:Lure a objective:Objective ;
740
+ uco-core:name "Lure"@en ;
741
+ uco-core:description "A Lure objective is to have an adversary laterally move or take actions to reach some target lure, usually performed through the deployment of breadcrumbs and honeypots."@en ;
742
+ .
743
+
744
+ objective:TimeSink a objective:Objective ;
745
+ uco-core:name "Time Sink"@en ;
746
+ uco-core:description "A Time Sink objective is to increase an adversary's operation time cost by having them interact with objects in a network."@en ;
747
+ .
748
+
749
+ objective:Track a objective:Objective ;
750
+ uco-core:name "Track"@en ;
751
+ uco-core:description "A Track objective is to be capable of identifying and tracing an adversary throughout a network."@en ;
752
+ .
753
+
754
+ objective:Trap a objective:Objective ;
755
+ uco-core:name "Trap"@en ;
756
+ uco-core:description "A Trap objective is to limit an adversary's scope of reachability to a confined environment."@en ;
757
+ .
758
+
759
+
760
+
761
+ role:Adversary a uco-role:Role ;
762
+ uco-core:name "Adversary"@en;
763
+ uco-core:description "An adversary is an instance of a contextualized role that holds opposing interests to a defender role."@en;
764
+ .
765
+
766
+ role:BlueTeam a uco-role:Role ;
767
+ uco-core:name "Blue Team"@en;
768
+ uco-core:description "An organizational role focused on ensuring the defensibility of targeted environments against attack."@en;
769
+ .
770
+
771
+ role:Defender a uco-role:Role ;
772
+ uco-core:name "Defender"@en;
773
+ uco-core:description "An defender is an instance of a contextualized role that defends some object or asset for some objective."@en;
774
+ .
775
+
776
+ role:PurpleTeam a uco-role:Role ;
777
+ uco-core:name "Purple Team"@en;
778
+ uco-core:description "An organizational role focused on evaluating and ensuring the defensibility of targeted environments against attack through a collaborative combination of BlueTeam (outward focused defense) and RedTeam (inward focused emulation of adversary attack) roles."@en;
779
+ .
780
+
781
+ role:RedTeam a uco-role:Role ;
782
+ uco-core:name "Red Team"@en;
783
+ uco-core:description "An organizational role focused on evaluating the defensibility of targeted environments against attack by actively emulating the persona, perspective, practices and actions of adversaries."@en;
784
+ .
785
+
786
+
787
+
788
+
789
+ vocabulary:HoneypotInteractionTypeVocab a rdfs:Datatype ;
790
+ rdfs:label "Action Name Vocabulary"@en-US ;
791
+ rdfs:comment "Defines a vocabulary of honeypot interaction characteristics."@en ;
792
+ rdfs:subClassOf rdfs:Resource ;
793
+ owl:oneOf ( "High"^^vocabulary:HoneypotTypeVocab "Low"^^vocabulary:HoneypotTypeVocab "Dynamic"^^vocabulary:HoneypotTypeVocab ) .
794
+