-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathusdl-sec.ttl
1044 lines (530 loc) · 47.8 KB
/
usdl-sec.ttl
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
@prefix org: <http://www.w3.org/ns/org#> .
@prefix vcard: <http://www.w3.org/2006/vcard/ns#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix xml: <http://www.w3.org/XML/1998/namespace> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ctag: <http://commontag.org/ns#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix secont: <http://www.ida.liu.se/~almhe/Security.owl#> .
@prefix dctypes: <http://purl.org/dc/dcmitype/> .
@prefix : <http://www.linked-usdl.org/ns/usdl-sec#> .
@prefix time: <http://www.w3.org/2006/time#> .
@prefix msm: <http://cms-wg.sti2.org/ns/minimal-service-model#> .
@prefix gr: <http://purl.org/goodrelations/v1#> .
@prefix usdl-core: <http://www.linked-usdl.org/ns/usdl-core#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix dcterms: <http://dublincore.org/2010/10/11/dcterms.rdf#> .
@base <http://www.linked-usdl.org/ns/usdl-sec#> .
<http://www.linked-usdl.org/ns/usdl-sec#> rdf:type owl:Ontology ;
rdfs:label "Linked Open Data Vocabulary for Security Features" ;
dcterms:created "2012-03-27" ;
dcterms:title "USDL Security" ;
dcterms:modified "2012-10-03" ;
owl:versionInfo "0.9.5" ;
dcterms:description """USDL Linked Data Vocabulary for Security (USDL-SEC). USDL-SEC aims at describing the main security properties and feaures of a service, described with USDL.
Service providers can use this specification to describe the security features of their services, and thus to support users in finding adequate alternatives to fulfil their needs.
The USDL-SEC description can be expressed using a top-down approach: from high-level properties (the Security Goals), to different solutions (Security Mechanism) and the corrisponding implementations (Security Technologies).
USDL-SEC reuses some information defined in the Security Ontology (referred as secont, available at http://www.ida.liu.se/~almhe/Security.owl).
USDL-SEC is globally organised in three main layers:
– Security topic: This is a high level representation of the security feature of a service.
– Security solution: This is a security mechanism that contributes towards satisfying a particular security topic.
– Security technology: It refers to the technical implementations of the security solutions.
This three-layered model is materialized into a concrete description
model, composed by the following elements:
– Security Profile: the root node of the model and the entry point from USDL to USDL-SEC. This node should appear as a pointer element of Usdl to the security properties of the service.
– Security Goal: the security goal refers to the highest abstraction layer referring to a security topic. It can take the values of the most well known security concepts like Anonymity, Confidentiality, Privacy, Authentication etc. This list is defined using another vocabulary (referred as sec-goal).
– Security Mechanism: is a set of security solutions that can contribute to achieve a security goal. These mechanisms are theoretical solutions that answer to specific security requirements like Access control, Cryptography, Obligations, etc. This list is defined using another vocabulary (referred as sec-mea).
These solutions can be applied under three realization levels: The network level, the application level, and the service level.
– Security Technology: is a set of concrete implementations and tools that realizes the security mechanisms. Like for example the encryption on the network level is implemented by IPSec. """@en ;
dcterms:contributor :Francesco_Di_Cerbo ,
:Slim_Trabelsi ,
:Torsten_Leidig ;
dcterms:creator :Torsten_Leidig .
#################################################################
#
# Annotation properties
#
#################################################################
#################################################################
#
# Datatypes
#
#################################################################
#################################################################
#
# Object Properties
#
#################################################################
### http://www.linked-usdl.org/ns/usdl-sec#hasSecurityGoal
:hasSecurityGoal rdf:type owl:ObjectProperty ;
rdfs:label "has security goal"@en ;
rdfs:comment "This relation connects a Security Profile with an high-level Security Goal; a vocabulary for Security Goals can be found using the sec-goal taxonomy."@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> ;
rdfs:range :SecurityGoal ;
rdfs:domain :SecurityProfile .
:isImplementedBy rdf:type owl:ObjectProperty ;
rdfs:label "is implemented by"@en ;
rdfs:comment "This relation associates to a Security Goal, a Security Mechanism that is used to implement the former or, alternatively, a USDL description of another service, that is used to implement the Security Goal."@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> ;
rdfs:domain :SecurityGoal ;
rdfs:range [ rdf:type owl:Class ;
owl:unionOf ( usdl-core:Service
:SecurityMechanism
)
] .
### http://www.linked-usdl.org/ns/usdl-sec#hasSecurityProfile
:hasSecurityProfile rdf:type owl:ObjectProperty ;
rdfs:label "has security profile" ;
rdfs:comment "this relation binds a USDL service description with its USDL-SEC security profile."@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> ;
rdfs:range :SecurityProfile .
### http://www.linked-usdl.org/ns/usdl-sec#hasSecurityRealizationType
:hasSecurityRealizationType rdf:type owl:ObjectProperty ;
rdfs:label "has securty realization type" ;
rdfs:comment "This relation describes at which level a Security Mechanism operates. It ideally refers to an ISO/OSI protocol stack, in order to understand in which layer a certain mechanism is active."@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> ;
rdfs:domain :SecurityMechanism ;
rdfs:range :SecurityRealizationType .
### http://www.linked-usdl.org/ns/usdl-sec#isRealizedByTechnology
:isRealizedByTechnology rdf:type owl:ObjectProperty ;
rdfs:label "is realized by technology" ;
rdfs:comment "This relation expresses how a certain Security Mechanism is implemented, by means of a Security Technology."@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> ;
rdfs:domain :SecurityMechanism ;
rdfs:range :SecurityTechnology .
### http://www.linked-usdl.org/ns/usdl-sec#securityMechanismType
#:securityMechanismType rdf:type owl:ObjectProperty ;
# rdfs:label "is achieved by Security Mechanism"@en ;
# rdfs:comment "This relation expresses which Security Mechanism is used by a service (and thus, is associated with its Security Profile)."@en ;
# rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#usesMechanism
#:usesMechanism rdf:type owl:ObjectProperty ;
# removed in v0.9.5 --> seems just a useless complexity and redundant wrt to the relation sec goals -> sec mechanisms
# rdfs:label "is achieved by Security Mechanism"@en ;
# rdfs:comment "This relation expresses which Security Mechanism is used by a service (and thus, is associated with its Security Profile)."@en ;
# rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> ;
# rdfs:range :SecurityMechanism ;
# rdfs:domain :SecurityProfile .
#################################################################
#
# Classes
#
#################################################################
### http://www.linked-usdl.org/ns/usdl-sec#SecurityGoal
:SecurityGoal rdfs:label "security goal" ;
skos:definition "A Security Goal refers to the highest abstraction layer referring to a security topic. It can take the values of the most well known security concepts like Anonymity, Confidentiality, Privacy, Authentication etc. This list is defined using another vocabulary, sec-goal."@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#SecurityMechanism
:SecurityMechanism rdfs:label "Security Mechanism" ;
rdfs:comment "A Security Mechanism is a set of security solutions that can achieve a security goal. These mechanisms are theoretical solutions that answer to specific security requirements like Access control, Cryptography, Obligations, etc. These solutions can be applied under three realization levels: The network level, the application level, and the service level (expressed with the relation hasSecurityRealizationType). "@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#SecurityProfile
:SecurityProfile rdf:type owl:Class ;
rdfs:label "security profile" ;
rdfs:subClassOf [ rdf:type owl:Restriction ;
owl:onProperty :hasSecurityGoal ;
owl:someValuesFrom :SecurityGoal
] ,
[ rdf:type owl:Restriction ;
owl:onProperty :usesMechanism ;
owl:someValuesFrom :SecurityMechanism
] ;
rdfs:comment "A Security Profile is the root node of the model and the entry point from a service description language to USDL-SEC. This node can conceptually be similar to a pointer element from the general service description, to the security properties of the service. "@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#SecurityRealizationType
:SecurityRealizationType rdf:type owl:Class ;
rdfs:label "security realization type" ;
rdfs:subClassOf skos:Concept ;
rdfs:comment "This field explains where the Security Mechanism operates, referring to an ISO/OSI-like stack model. Network, Application and Service are valid values."@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#SecurityTechnology
:SecurityTechnology rdfs:label "security technology" ;
rdfs:comment """The Security Tecnology is a set of concrete implementations and tools that realizes the Security Mechanisms. Like for example the encryption on the network level is implemented by IPSec .
Security Technology elements can be defined by each vocabulary user."""@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
#################################################################
#
# Individuals
#
#################################################################
### http://www.linked-usdl.org/ns/usdl-sec#Access_Control
:Access_Control rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "The prevention of unauthorized use of a resource, including the prevention of use of a resource in an unauthorised manner. (CCITT)"^^xsd:string ,
"The process of ensuring that only authorized subjects are allowed access to a resource. (sec-ont)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Accountability
:Accountability rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:label "Accountability"@en ;
rdfs:comment "The property that ensures that the actions of an entity may be traced uniquely to the entity. (CCITT) The process allowing for the auditing of IS activities to be traced to a source that may then be held responsible. (Phoha)"@en ;
skos:exactMatch secont:Accountability ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Anonymity
:Anonymity rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:label "Anonymity"@en ;
rdfs:comment "A condition in which an individual's true identity is unknown. (www.microsoft.com/security/glossary.mspx)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#ApplicationType
#:ApplicationType rdf:type owl:NamedIndividual .
### http://www.linked-usdl.org/ns/usdl-sec#Auditing
:Auditing rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Collection of data about events which have occurred in a system. (sec-ont)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Authentication
:Authentication rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "The process of reliably determining the identify of a communicating party or source of a message. (Phoha)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Authenticity
:Authenticity rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "A security principle that ensures that a message is received in exactly the form in which it was sent. (Phoha)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Authorization
:Authorization rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "Permission to access a resource. (Phoha)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Availability
:Availability rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "The property of being accessible and useable upon demand by an authorised entity. (CCITT) Timely, reliable access to data and information services for authorised users. (Phoha) The ability of a product to be in a state to perform a required function under given conditions at a given instant of time or over a given time interval assuming that the required external resources are provide. (Meul) The prevention of the unauthorised withholding of information or resources (ITSEC)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#BiometricData
:BiometricData rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Data originated from \"the measurement of an anatomical, physiological or behavioural characteristic of the user, rather than knowledge or possession of information or a key.\" (secont:Literature#Phoha)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Certificate
:Certificate rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "A certificate authority (CA) issues an encrypted digital certificate containing the applicant's public key and a variety of other identification information. The CA makes its own public key readily available through print publicity or perhaps on the Internet. The recipient of an encrypted message uses the CA's public key to decode the digital certificate attached to the message, verifies it as issued by the CA and then obtains the sender's public key and identification information held within the certificate. With this information, the recipient can send an encrypted reply. (Webopedia)"^^xsd:string ,
"A data structure signed with a public key digital signature stating that a specified public key belongs to someone or something with a specified identification. (ISD)"^^xsd:string ,
"A document with a digital signature. Such a certificate is used to authenticate identity. Digital certificates are often signed by a trusted third party known as a certificate authority. (secont:Literature#ODotI)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#CertificateExchange
:CertificateExchange rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "A certificate exchange is a method with which digital certificates from two different communication endpoints are transmitted to the other endpoint. The aim of the exchange is, in general terms, to assure the identities of the two communication peers, especially when using Public Key Infrastructure (PKI) certificates, that are endorsed by a Certification Authority."^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Certification
:Certification rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Comprehensive evaluation of the technical and non-technical security safeguards of an information system to support the accreditation process that establishes the extent to which a particular design and implementation meets a set of specified security requirements (CNSS Instruction 4009)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Challenge-Response
:Challenge-Response rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "In computer security, challenge-response is a family of protocols in which one party presents a question, the \"challenge\", and another party must provide a valid answer, the \"response\". (adapted from Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Checksum
:Checksum rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "A checksum or hash sum is a fixed-size datum computed from an arbitrary block of digital data for the purpose of detecting accidental errors or deliberate modifications that may have been introduced during its transmission or storage. The integrity of the data can be checked at any later time by recomputing the checksum and comparing it with the stored one. If the checksums match, the data were almost certainly not altered (either intentionally or unintentionally). (adapted from Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Confidentiality
:Confidentiality rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "The property that information is not made available or disclosed to unauthorised individuals, entities or processes. (CCITT) The property of not being divulged to unauthorised parties. (Phoha) The prevention of the unauthorised disclosure of information (ITSEC)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Control_Code
:Control_Code rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "In information theory and coding theory with applications in computer science and telecommunication, error detection and correction or error control or control codes are techniques that enable reliable delivery of digital data over unreliable communication channels. Many communication channels are subject to channel noise, and thus errors may be introduced during transmission from the source to a receiver. Other channels might not be fully trusted, due to the possible presence of communication tampering entities. Error detection techniques allow detecting such errors or abuses . (adapted from Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Correctness
:Correctness rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "A property of a representation of a Target of Evaluation such thtat it accurately reflects the stated security target for that system or product (ITSEC)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Cryptography
:Cryptography rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Discipline which embodies principles, means, and methods for the transformation of data in order to hide its information content, prevent its undetected modification and/or prevent its unauthorised use. (secont:Literature#CCITT)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Delegation
:Delegation rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Delegation represents a process with which the owner of an identity (or a user with an associated role) authorizes the owner of another (validated) identity to use his identity, or to act as herself. (Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Digest
:Digest rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "A cryptographic hash function is a hash function that can be defined as a deterministic procedure that takes an arbitrary block of data and returns a fixed-size bit string, the (cryptographic) hash value, such that an accidental or intentional change to the data will change the hash value. The data to be encoded is often called the \"message\", and the hash value is sometimes called the message digest or simply digest. (adapted from Wikipedia) "^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#DigitalSignature
:DigitalSignature rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "A digital signature or digital signature scheme is a mathematical scheme for demonstrating the authenticity of a digital message or document. A valid digital signature gives a recipient reason to believe that the message was created by a known sender, and that it was not altered in transit. Digital signatures are commonly used for software distribution, financial transactions, and in other cases where it is important to detect forgery or tampering.(Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy ;
rdfs:isDefinedBy <http://www.linked-usdl.org/ns/usdl-sec-mea#> .
### http://www.linked-usdl.org/ns/usdl-sec#Filtering
:Filtering rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Filtering is a mechanism that prevents certain entities to access to a resource, an application or a service. An example can be represented by web site blacklists. "^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Francesco_Di_Cerbo
:Francesco_Di_Cerbo rdf:type owl:NamedIndividual ,
foaf:Person ;
foaf:name "Francesco Di Cerbo" ;
foaf:lastName "Di Cerbo" ;
foaf:title "Dr" ;
foaf:firstName "Francesco" ;
foaf:phone "+33 49228-6445" .
### http://www.linked-usdl.org/ns/usdl-sec#Identification
:Identification rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "Possibility to include a certain identifier in a request, but without starting an authentication process involving credentials transmission."@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#InStorageType
:InStorageType rdf:type :SecurityRealizationType ,
owl:NamedIndividual ;
rdfs:comment "The Service realization type explains that a certain Security Technology operates at service level, if considering an ideal ISO/OSI stack protocol model."@en ;
skos:prefLabel "service realization type"@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#InTransitType
:InTransitType rdf:type :SecurityRealizationType ,
owl:NamedIndividual ;
skos:prefLabel "InTransit (network) realization type"@en ;
rdfs:comment "The Network realization type explains that a certain Security Technology operates at network level, if considering an ideal ISO/OSI stack protocol model."@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#InUsage
:InUsage rdf:type :SecurityRealizationType ,
owl:NamedIndividual ;
rdfs:comment "The Application realization type explains that a certain Security Technology operates at application level, if considering an ideal ISO/OSI stack protocol model. "@en ;
skos:prefLabel "application realization type"@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#Integrity
:Integrity rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "A condition in which data (or a system itself) has not been modified or corrupted without authorisation. A system protects the integrity of data if it prevents unauthorised modification, as opposed to protecting the confidentiality of data, which prevents unauthorised disclosure. (Phoha) The degree to which a system or component prevents unauthorised access to, or modification of, computer programs or data (IEEE Std 610.12)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#KeyManagement
:KeyManagement rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Key management is the set of techniques and procedures supporting the establishment and maintenance of keying relationships between authorised parties. (secont:Literature#MOV97)"^^xsd:string ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Load_Balancing
:Load_Balancing rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Load balancing is a computer networking methodology to distribute workload across multiple computers or a computer cluster, network links, central processing units, disk drives, or other resources, to achieve optimal resource utilization, maximize throughput, minimize response time, and avoid overload. It can also be seen as a security defense, for instance to contrast Denial of Service (DoS) attacks. Using multiple components with load balancing, instead of a single component, may increase reliability through redundancy. The load balancing service is usually provided by dedicated software or hardware, such as a multilayer switch or a Domain Name System server. (adapted from Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Logging
:Logging rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Computer data logging is the process of recording events, with an automated computer program, in a certain scope in order to provide an audit trail that can be used to understand the activity of the system and to diagnose problems or to detect abuses, attacks and so on. (adapted from Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Monitoring
:Monitoring rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Used for checking the status, progress and operation of a system (sec-ont)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#NetworkType
#:NetworkType rdf:type owl:NamedIndividual .
### http://www.linked-usdl.org/ns/usdl-sec#Non-Repudiation
:Non-Repudiation rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "The property of a scheme ... in which the recipient is able to prove to a third party that data has been sent by the sender or received by the receiver. This property protects against the sender denying having sent the message and the receiver denying having received the message. The sender is provided with a proof of delivery and receiver is assured of sender's identity. (Phoha) Repudiation: Denial by one of the entities involved in a communication of having participated in all or part of the communication. (CCITT)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Obfuscation
:Obfuscation rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "In cryptography, obfuscation refers to encoding the input data before it is sent to a hash function or other encryption scheme. This technique helps to make brute force attacks unfeasible, as it is difficult to determine the correct cleartext. (Wikipedia)"^^xsd:string ,
"In network security, obfuscation refers to methods used to obscure an attack payload from inspection by network protection systems. (Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Obligation
:Obligation rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "An obligation is a requirement to take some course of action. (Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#PasswordExchange
:PasswordExchange rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "A process that enables the transmission of a unique character string held by an user, a copy of which is stored within the system. The password entered by the intending user must correspond with the stored value before the user is accepted by the system. (secont:Literature#ODoC)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#PolicyCompliance
:PolicyCompliance rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "also: compliance with laws, regulations"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Privacy
:Privacy rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "Protection from the unauthorised disclosure of data. Security purists use confidentiality for this and use privacy to refer to the protection of personal information; privacy legislation consists of laws requiring government and business to justify which data they keep about people, and to tell people what information those organisations are storing about them. (Phoha) The right of individuals to control or influence what information related to them may be collected and stored and by whom and to whom that information may be disclosed. Note: Because this term relates to the right of individuals, it cannot be very precise and its use should be avoided except as a motivation for requiring security. (CCITT)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Pseudonym
:Pseudonym rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description """On the Internet, pseudonymous remailers utilise cryptography that achieves persistent pseudonymity, so that two-way communication can be achieved, and reputations can be established, without linking physical identities to their respective pseudonyms. Aliasing is the use of multiple names for the same data location.
More sophisticated cryptographic systems, such as Anonymous Digital credentials, enable users to communicate pseudonymously (i.e., by identifying themselves by means of pseudonyms). In well-defined abuse cases, a designated authority may be able to revoke the pseudonyms and reveal the individuals' real identity. (Wikipedia) """^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Recommendation
:Recommendation rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "a Recommendation assesses the qualities, or characteristics, or capabilities of an application or service being recommended, in terms of that subject’s ability to perform a particular task or function. User recommendation expressed on social media, or as comments or reviews in software marketplace, contribute in different means to decision making processes. When a recommendation comes from a trusted person, the recommended resource can more easily be trusted by other persons."^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Replication
:Replication rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Replication is the process of sharing information so as to ensure consistency between redundant resources, such as software or hardware components, to improve reliability, fault-tolerance, or accessibility. It could be data replication if the same data is stored on multiple storage devices, or computation replication if the same computing task is executed many times. A computational task is typically replicated in space, i.e. executed on separate devices, or it could be replicated in time, if it is executed repeatedly on a single device. (Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Reputation
:Reputation rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Reputation of a social entity (a person, a group of people, an organization) is an opinion about that entity, typically a result of social evaluation on a set of criteria. Reputation may be considered as a component of the identity as defined by others. (Wikipedia) "^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#SecurityGoal
:SecurityGoal rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:label "security goal" ;
skos:definition "A Security Goal refers to the highest abstraction layer referring to a security topic. It can take the values of the most well known security concepts like Anonymity, Confidentiality, Privacy, Authentication etc. This list is defined using another vocabulary, sec-goal."@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#SecurityMechanism
:SecurityMechanism rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:label "Security Mechanism" ;
rdfs:comment "A Security Mechanism is a set of security solutions that can achieve a security goal. These mechanisms are theoretical solutions that answer to specific security requirements like Access control, Cryptography, Obligations, etc. These solutions can be applied under three realization levels: The network level, the application level, and the service level (expressed with the relation hasSecurityRealizationType). "@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#SecurityProfile
:SecurityProfile rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:label "security profile" ;
rdfs:comment "A Security Profile is the root node of the model and the entry point from a service description language to USDL-SEC. This node can conceptually be similar to a pointer element from the general service description, to the security properties of the service. "@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#SecurityTechnology
:SecurityTechnology rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:label "security technology" ;
rdfs:comment """The Security Tecnology is a set of concrete implementations and tools that realizes the Security Mechanisms. Like for example the encryption on the network level is implemented by IPSec .
Security Technology elements can be defined by each vocabulary user."""@en ;
rdfs:isDefinedBy <http://linked-usdl.org/ns/usdl-sec> .
### http://www.linked-usdl.org/ns/usdl-sec#ServiceType
#:ServiceType rdf:type owl:NamedIndividual .
### http://www.linked-usdl.org/ns/usdl-sec#SharedSecret
:SharedSecret rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "In cryptography, a shared secret is a piece of data, known only to the parties involved, in a secure communication. The shared secret can be a password, a passphrase, a big number or an array of randomly chosen bytes. (Wikipedia)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy ;
rdfs:isDefinedBy <http://www.linked-usdl.org/ns/usdl-sec-mea#> .
### http://www.linked-usdl.org/ns/usdl-sec#Slim_Trabelsi
:Slim_Trabelsi rdf:type owl:NamedIndividual ,
foaf:Person ;
foaf:name "Slim Trabelsi" ;
foaf:phone "+33 49228-6345" ;
foaf:firstName "Slim" ;
foaf:lastName "Trabelsi" ;
foaf:title "Dr" .
### http://www.linked-usdl.org/ns/usdl-sec#Steganography
:Steganography rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Means by which two or more parties may employ subliminal or invisible communication. (secont:Literature#ISD)"^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#TestSecGoalConcept
#:TestSecGoalConcept rdf:type owl:NamedIndividual ,
# skos:Concept ;
# skos:broader :SecurityGoal ;
# skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Token
:Token rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description """A security token (or sometimes a hardware token, hardbad token, authentication token, USB token, cryptographic token, or key fob) may be a physical device that an authorized user of computer services is given to ease authentication. The term may also refer to software tokens.
Security tokens are used to prove one's identity electronically (as in the case of a customer trying to access their bank account). The token is used in addition to or in place of a password to prove that the customer is who they claim to be. The token acts like an electronic key to access something. (Wikipedia)"""^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Torsten_Leidig
:Torsten_Leidig rdf:type owl:NamedIndividual ,
foaf:Person ;
foaf:phone "+49 6227 7 52535" ;
foaf:name "Torsten Leidig" ;
foaf:title "Dr" ;
foaf:lastName "Leidig" ;
foaf:firstName "Torsten" .
### http://www.linked-usdl.org/ns/usdl-sec#Trust
:Trust rdf:type owl:NamedIndividual ,
skos:Concept ;
rdfs:comment "The firm belief in the competence of an entity to act dependably, securely, and reliably within a specified context. (Grandison, 2000) Trust is a particular level of the subjective probability with which an agent will perform a particular action, both before we can monitor such action (or independently of his capacity of ever to be able to monitor it) and in a context in which it affects our action. (Gambetta, 1990) Trust is a subjective expectation an agent has about another agent’s future behavior. (L. Mui, 2003)"@en ;
skos:broader :SecurityGoal ;
skos:inScheme :securityGoalsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#Usage_Control
:Usage_Control rdf:type owl:NamedIndividual ,
skos:Concept ;
dcterms:description "Usage control refers to ability for a resource owner to enforce the use of that resource only in the allowed contexts."^^xsd:string ;
skos:broader :SecurityMechanism ;
skos:inScheme :securityMechanismsTaxonomy .
### http://www.linked-usdl.org/ns/usdl-sec#securityGoalsTaxonomy
:securityGoalsTaxonomy rdf:type skos:ConceptScheme ;
dcterms:title "A simple taxonomy for security goals"@en ;
skos:hasTopConcept :SecurityGoal .