6th European Conference - Academic Conferences

More documents

Recommendations

Info

Harm Schotanus et al. The security requirements are minimal, as the binding between the document and the label is weak at this point. Basically the label only needs to contain a reference to the original document. Within an information domain, it could be used for enforcing need-to-know separation or communities of interest. Figure 2 shows an abstraction of the functionality needed for this approach. Labelling application Workstation Labels and documents Information management system Figure 2: Labelling for information lifecycle management purposes Essentially, the architecture for this set-up contains only two main aspects: An application that can create labels. An information management system: an environment or system that can be used to store information and labels together. When a user creates information, the labelling application can be used to link several attributes to the information. The information and the label will both be stored in the information management system (IMS). The user may disseminate the information either through the IMS or by separate means. The IMS can in the latter case be used to retrieve the label, when the information is presented. 3.2 Disseminating cross-domain information We can extend the information lifecycle management functionality so that it is possible to inform a recipient of information in another information domain about the way the information should be treated; e.g. under what memorandum of understanding it is exchanged or what classification is attached to the information. In this case when a user sends the information to a recipient, the label with the necessary meta-information has to be sent as well. This purpose is mostly intended of information-sharing across different information domains, where each information domain has the same or a very similar security policy. The label here has an informative, procedural aim and does not necessarily form a technical enforcement. Labelling application Workstation Labels and documents Document Information management system Figure 3: Labelling for disseminating cross-domain information 232 Label Release mechanism
Harm Schotanus et al. In this setup we add a third element, namely the release mechanism. Essentially, the other elements stay the same. This release mechanism has a two-fold purpose. The first is to verify that a suitable label accompanies the information and if not, try to retrieve the label from the information management system. The suitability is established by validating that all the necessary information is present. The second purpose is the ability to translate an internal label to an external label. For example certain elements may be removed from the document (such as the name of the author) or other information may be added (e.g. the date of information exchange), or a different labelling structure may be used for internal and external purposes 2 . 3.3 Integrity protection The third step in extending the labelling architecture is to realise integrity protection of information. Integrity protection refers to the means to establish whether a document is authentic or has been changed. And as a secondary benefit, it may be established who assessed the authenticity. The label has to be extended to include a secure binding to link the information and the label together, in such a way that it can always be detected if an existing label is attached to other (different or altered) information, or if the label content has been changed. Making a change to an information object can be detected because that would result in a different object. For the binding to be secure we need cryptographic support. A method, amongst others, of realising this is through a PKI. A user has to use a private key to sign the binding in the label, which links the binding also directly to the user. That is, it can easily be determined who created the label. To validate the integrity of the document, the public key of the user that created the binding can be used to verify the binding in the label. In case any changes have been made, the verification will fail. Certificates and CRL Labelling application Trusted OS Workstation Labels and documents PKI Document Information management system Label Release mechanism and IEG Figure 4: Labelling for integrity protection For a high assurance environment 3 , we also need to ensure that the labelling process works correctly. In other words we must have a level of assurance that the information the user actually labelled is the correct information and has not been modified unbeknownst to the user during the process. We cannot attain that level of assurance on a normal platform (operating system); therefore we need an operating system or platform that can provide us the needed assurance. This has been named a trusted operating system. Essentially, each step in the process of labelling must be carried out under 2 Note that the release mechanism does not comprise the entire interconnection here, there may be other elements needed too, for instance cryptographic units or firewalls to ensure a secure connection. 3 For instance information domains which process highly classified information. 233
Page 1 and 2:
The Proceedings of the 6th Internat
Page 3 and 4:
Contents Paper Title Author(s) Page
Page 5 and 6:
Preface These Proceedings are the w
Page 7 and 8:
Biographies of contributing authors
Page 9 and 10:
Department of Computer Science, IQR
Page 11 and 12:
Using the Longest Common Substring
Page 13 and 14:
Jaime Acosta Some techniques that u
Page 15 and 16:
Jaime Acosta assigned by an anti-vi
Page 17 and 18:
Jaime Acosta Cormen, T.H., Leiserso
Page 19 and 20:
Hind Al Falasi and Liren Zhang tran
Page 21 and 22:
Hind Al Falasi and Liren Zhang ther
Page 23 and 24:
Hind Al Falasi and Liren Zhang the
Page 25 and 26:
Edwin Leigh Armistead and Thomas Mu
Page 27 and 28:
Deception Operations Security (OPS
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
The Uses and Limits of Game Theory
Page 35 and 36:
3. Limits to using game theory 3.1
Page 37 and 38:
Merritt Baer Effective cyberintrusi
Page 39 and 40:
Merritt Baer 1.5), there seems to b
Page 41 and 42:
Merritt Baer Report of the Defense
Page 43 and 44:
Ivan Burke and Renier van Heerden F
Page 45 and 46:
Ivan Burke and Renier van Heerden a
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Marco Carvalho et al. systems start
Page 55 and 56:
Marco Carvalho et al. Benatallah, 2
Page 57 and 58:
Marco Carvalho et al. management la
Page 59 and 60:
Marco Carvalho et al. Figure 4: Sta
Page 61 and 62:
Marco Carvalho et al. Sorrels, D.,
Page 63 and 64:
Manoj Cherukuri and Srinivas Mukkam
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Mecealus Cronkrite et al. to see bo
Page 81 and 82:
Mecealus Cronkrite et al. trivial.
Page 83 and 84:
Mecealus Cronkrite et al. socially
Page 85 and 86:
Mecealus Cronkrite et al. The views
Page 87 and 88:
Vincent Garramone and Daniel Likari
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Stephen Groat et al. Sections 4 and
Page 97 and 98:
Stephen Groat et al. probability fo
Page 99 and 100:
Stephen Groat et al. host. In this
Page 101 and 102:
Stephen Groat et al. changing addre
Page 103 and 104:
Marthie Grobler et al. leadership,
Page 105 and 106:
Marthie Grobler et al. apply to sta
Page 107 and 108:
Marthie Grobler et al. 6. Working t
Page 109 and 110:
Cyber Strategy and the Law of Armed
Page 111 and 112:
Ulf Haeussler Alliance and Allies r
Page 113 and 114:
Ulf Haeussler following the invocat
Page 115 and 116:
Ulf Haeussler NCSA (2009) NCSA Supp
Page 117 and 118:
Karim Hamza and Van Dalen of respon
Page 119 and 120:
Karim Hamza and Van Dalen From a mi
Page 121 and 122:
Karim Hamza and Van Dalen productiv
Page 123 and 124:
Intelligence-Driven Computer Networ
Page 125 and 126:
Eric Hutchins et al. of defensive a
Page 127 and 128:
Eric Hutchins et al. Defenders can
Page 129 and 130:
Eric Hutchins et al. Equally as imp
Page 131 and 132:
Eric Hutchins et al. X-Mailer: Yaho
Page 133 and 134:
Eric Hutchins et al. Received: (qma
Page 135 and 136:
Eric Hutchins et al. U.S.-China Eco
Page 137 and 138:
Saara Jantunen and Aki-Mauri Huhtin
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Brian Jewell and Justin Beaver In t
Page 147 and 148:
Brian Jewell and Justin Beaver Figu
Page 149 and 150:
4. Evaluation Brian Jewell and Just
Page 151 and 152:
Brian Jewell and Justin Beaver othe
Page 153 and 154:
Detection of YASS Using Calibration
Page 155 and 156:
Kesav Kancherla and Srinivas Mukkam
Page 157 and 158:
M M M Su−2 Sv ∑∑ u= 1 v= 1 h(
Page 159 and 160:
5.2 ROC curves Kesav Kancherla and
Page 161 and 162:
Developing a Knowledge System for I
Page 163 and 164:
Louise Leenen et al. We distinction
Page 165 and 166:
Louise Leenen et al. There is growi
Page 167 and 168:
3.1 Needs analysis Louise Leenen et
Page 169 and 170:
Louise Leenen et al. Kroenke, D.M.
Page 171 and 172:
Jose Mas y Rubi et al. As we can se
Page 173 and 174:
Figure 2: CALEA forensic model (Pel
Page 175 and 176:
Jose Mas y Rubi et al. Table 2: Com
Page 177 and 178:
Jose Mas y Rubi et al. Another pend
Page 179 and 180:
Tree of Objectives Acknowledgements
Page 181 and 182:
Secure Proactive Recovery - a Hardw
Page 183 and 184:
Ruchika Mehresh et al. implementing
Page 185 and 186:
Ruchika Mehresh et al. The coordina
Page 187 and 188:
Ruchika Mehresh et al. multiplicati
Page 189 and 190:
Ruchika Mehresh et al. Table 2: App
Page 191 and 192: 2. Network infiltration detection D
Page 193 and 194: David Merritt and Barry Mullins on
Page 195 and 196: David Merritt and Barry Mullins Ess
Page 197 and 198: David Merritt and Barry Mullins Dev
Page 199 and 200: Muhammad Naveed Pakistan Computer E
Page 201 and 202: Muhammad Naveed response could also
Page 203 and 204: Muhammad Naveed Table 10: Aggressiv
Page 205 and 206: Muhammad Naveed 2006 Tcp Open Mysql
Page 207 and 208: Muhammad Naveed 8009 Tcp Open Ajp13
Page 209 and 210: Muhammad Naveed Austalian Taxation
Page 211 and 212: Alexandru Nitu world and bring it i
Page 213 and 214: Alexandru Nitu Article 51 restricts
Page 215 and 216: Alexandru Nitu As IW strategy and t
Page 217 and 218: Cyberwarfare and Anonymity Christop
Page 219 and 220: Christopher Perr attacks again help
Page 221 and 222: Christopher Perr about the current
Page 223 and 224: Catch me if you can: Cyber Anonymit
Page 225 and 226: David Rohret and Michael Kraft reve
Page 227 and 228: David Rohret and Michael Kraft sary
Page 229 and 230: Data (Evidence) Removal Shield Davi
Page 231 and 232: Neutrality in the Context of Cyberw
Page 233 and 234: Julie Ryan and Daniel Ryan 18th cen
Page 235 and 236: Julie Ryan and Daniel Ryan “Decla
Page 237 and 238: Julie Ryan and Daniel Ryan von Glah
Page 239 and 240: Harm Schotanus et al. In the remain
Page 241: Harm Schotanus et al. 2.3.1 Secure
Page 245 and 246: Harm Schotanus et al. the label (by
Page 247 and 248: Harm Schotanus et al. these aspects
Page 249 and 250: Maria Semmelrock-Picej et al. they
Page 251 and 252: Maria Semmelrock-Picej et al. User
Page 253 and 254: Maria Semmelrock-Picej et al. SPIKE
Page 255 and 256: Maria Semmelrock-Picej et al. A cl
Page 257 and 258: Maria Semmelrock-Picej et al. in co
Page 259 and 260: Maria Semmelrock-Picej et al. In th
Page 261 and 262: Maria Semmelrock-Picej et al. Fuchs
Page 263 and 264: Madhu Shankarapani and Srinivas Muk
Page 265 and 266: Figure 1: UPX packed Trojan Figure
Page 267 and 268: Trojan.Zb ot- 1342.mal Trojan.Sp y.
Page 269 and 270: Madhu Shankarapani and Srinivas Muk
Page 271 and 272: Namosha Veerasamy and Marthie Grobl
Page 277 and 278: 4. Conclusion Namosha Veerasamy and
Page 279 and 280: Tanya Zlateva et al. Computer Infor
Page 281 and 282: Tanya Zlateva et al. security and v
Page 283 and 284: Tanya Zlateva et al. court opinions
Page 285 and 286: Tanya Zlateva et al. 5. Pedagogy, e
Page 287 and 288: PhD Research Papers 277
Page 289 and 290: Shada Alsalamah et al. Level 3 all
Page 291 and 292: Shada Alsalamah et al. assure the a
Page 293 and 294:
Shada Alsalamah et al. for Health I
Page 295 and 296:
3. Hematology Laboratory System Who
Page 297 and 298:
Shada Alsalamah et al. Pirnejad, H.
Page 299 and 300:
Michael Bilzor a diverse base of U.
Page 301 and 302:
Michael Bilzor In our current exper
Page 303 and 304:
5. Execution monitor theory Michael
Page 305 and 306:
Michael Bilzor design was run in si
Page 307 and 308:
Michael Bilzor over testbench metho
Page 309 and 310:
Evan Dembskey and Elmarie Biermann
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Theoretical Offensive Cyber Militia
Page 319 and 320:
Rain Ottis Last, but not least, it
Page 321 and 322:
Rain Ottis an infantry battalion, w
Page 323 and 324:
Rain Ottis Ottis, R. (2008) “Anal
Page 325 and 326:
Work in Progress Papers 315
Page 327 and 328:
Large-Scale Analysis of Continuous
Page 329 and 330:
References William Acosta Abadi, D.
Page 331 and 332:
Natarajan Vijayarangan top box unit
Page 333 and 334:
Natarajan Vijayarangan The proposed
show all

6th European Conference - Academic Conferences

Create successful ePaper yourself

Delete template?

Save as template?