Outline of Sophisticated Covert Channel Prevention for Activity validate

  • Klaus-Peter Fischer-Hellmann
Part of the IT im Unternehmen book series (ITU, volume 1)


In order to allow for type validation of a variable containing visibility-restricted information in cases where no risk of information leakage exists, it has to be made sure that throwing the standard bpel:invalidVariables fault does not allow conclusions to be drawn as to the value of the information currently contained in this variable. Validation with respect to the proper type of the value contained in a variable may either be caused by a validate activity or by indication of attribute validate=”true” in an assign activity. A more sophisticated check for covert channel prevention with type validation than that proposed in the main part of the book would require assuring that no value restricted subtype of a type is being applied in validation.


Information Theory Main Part Range Restriction Information Flow Data Security 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Copyright information

© Vieweg+Teubner Verlag | Springer Fachmedien Wiesbaden 2012

Authors and Affiliations

  • Klaus-Peter Fischer-Hellmann
    • 1
  1. 1.MühltalGermany

Personalised recommendations