<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">A new approach for WS-Policy Intersection using Partial Ordered Sets</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Abeer</forename><surname>Elsafie</surname></persName>
							<email>abeer.elsafie@rub.de</email>
							<affiliation key="aff0">
								<orgName type="department">Horst Görtz Institute for IT-Security</orgName>
								<orgName type="institution">Ruhr-University Bochum</orgName>
								<address>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Christian</forename><surname>Mainka</surname></persName>
							<email>christian.mainka@rub.de</email>
							<affiliation key="aff0">
								<orgName type="department">Horst Görtz Institute for IT-Security</orgName>
								<orgName type="institution">Ruhr-University Bochum</orgName>
								<address>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Jörg</forename><surname>Schwenk</surname></persName>
							<email>joerg.schwenk@rub.de</email>
							<affiliation key="aff0">
								<orgName type="department">Horst Görtz Institute for IT-Security</orgName>
								<orgName type="institution">Ruhr-University Bochum</orgName>
								<address>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">A new approach for WS-Policy Intersection using Partial Ordered Sets</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">A14E1451ACD352356F25AD7F84E5C5D3</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T05:44+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>WS-Policy Intersection</term>
					<term>Partial Ordered Sets</term>
					<term>Hasse Diagram</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>WS-Policy is a framework that can be used to describe assertions for web services message exchange. In the context of Service Oriented Architectures and Clouds, where web services are belonging to, machine-to-machine communication is one of its core ideas. When those machines try to apply WS-Policy, mainly two events can occur: First, the machine-exchanged policies have common assertions -there is an intersection. Second, there is no direct intersection and the participants must reach an agreement by minimal adjustments to the policies. This paper introduces a new approach for reaching intersection by computing adjustments to the policies using partial ordering.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>In the field of web services, requirements and capabilities can be described using XML according to the WS-Policy specification <ref type="bibr" target="#b0">[1]</ref>. The policies can be applied to the web services message exchange, which is commonly machine-to-machine communication with multiple participants, for assuring security goals. This leads to the need for WS-Policy intersection, a technique used when two or more web services want to communicate and fulfill each others policy. Currently, this approach can only handle the case that intersection within the participating policies exists <ref type="bibr" target="#b1">[2]</ref>. Otherwise it fails and the further communication cannot be achieved.</p><p>Hence, our motivation is to find a way to make intersection possible even in the case that there is no direct intersection by adjusting one or both party's policy, e.g. by adding some policy aspects. This is achieved by a multi-layer approach: First, every WS-Policy, which can be seen as a set of Boolean terms, is converted into its disjunctive normal form (DN F), so that policies are easy to compare and finding matching terms is simple. In the case that there is a match, the decision for the participants is obviously done. If there is no direct intersection, this paper introduces a model for an arbitrary number of parties, that computes these adjustments using partial order sets to enforce policy intersection for all participants.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Foundations</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">WS-Policy and Policy Intersection</head><p>WS-Policy is a framework for describing policies using XML <ref type="bibr" target="#b2">[3,</ref><ref type="bibr" target="#b0">1]</ref>. In the context of web services, it is commonly used to specify which parts of a message should be signed or encrypted using WS-SecurityPolicy <ref type="bibr" target="#b3">[4]</ref>. The structure of a WS-Policy can be seen as a Boolean term, but written in XML. It consists of an enveloping &lt;Policy/&gt; element which can contain arbitrary AND (element: &lt;All/&gt;) and XOR (element: &lt;ExactlyOne/&gt;) expressions. For each term, there exists a disjunktive normal form (DN F). It is an XOR-junction of propositions derived from the compact form using boolean algebra <ref type="bibr" target="#b4">[5]</ref>. Consider the following example, which does not use any XML for simplicity:</p><formula xml:id="formula_0">A 1 ∧ (A 2 ⊕ A 3 ) DN F = A 1 ∧ A 2 Alternative 1 ⊕ A 1 ∧ A 3 Alternative 1</formula><p>From the DN F, one can easily see the policy alternative: They are a bundle of assertions which must be fulfilled.</p><p>The WS-Policy Intersection process identifies compatible policy alternatives included in all parties policies or returns nothing if there are no matches <ref type="bibr" target="#b5">[6]</ref>. Two alternatives are compatible, if the sets of included assertions are identical.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Ordered Sets and Hasse Diagrams</head><p>A partially ordered set (poset) is a mathematic tool generalizing the concept of arranging and ordering elements. In a poset, there exists a relation between pairs of elements, e.g. the "≤"-relation, so that the elements can be compared. When this relation exists for each possible pair, then the poset is called a chain (or total ordered set). In addition a poset in which no two distinct elements are comparable is called antichain.</p><p>A Lattice is an ordered set where every pair of elements has a least upper bound (LUB) and a greatest lower bound (GLB). In our approach we assume that the posets are all Lattices.</p><p>A Hasse or Lattice diagram is a visualization of the finite poset in the form of a drawing, in which nodes are elements of the poset and arrows between related nodes represent the order relation between these elements <ref type="bibr" target="#b6">[7,</ref><ref type="bibr" target="#b7">8]</ref>. In the next section we introduce an example providing a detailed overview of the usage of Hasse diagram.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">WS-Policy Intersection Model</head><p>The evaluation of WS-Policy Intersection consists of two main layers as shown in Figure <ref type="figure" target="#fig_0">1</ref>:</p><p>The preparation layer is responsible for converting each policy into its corresponding DN F. This is achieved either manually or using an software-tool <ref type="bibr" target="#b8">[9]</ref> and is outside the scope of this research. Afterwards, the policy intersection examination unit compares the DN F policies and forwards the results to the evaluation layer. If there is intersection, which means compatible alternatives exist, they are directly forwarded to the decision making unit, which chooses the strongest alternative. In the case of no intersection, the bound extraction unit takes part. It first identifies all ordered sets, which can be chains like AES 128 &lt; AES 256 or anti-chains which cannot be compared, e.g. Sign Header and Sign Body . Afterwards, all sets are combined to one Hasse diagram as shown in Figure <ref type="figure" target="#fig_1">2</ref>. Consider the two policies P 1 and P 2 , having the alternatives A 1 P1 and A 1 P2 as shown. Obviously, they are not compatible. Using the Hasse diagram, the least upper bound (LUB) and the greatest lower bound (GLB) can be easily extracted. In general if we consider that the posets used are all lattices, where each two elements have a LUB/GLB, then we can easily use the meet and join for finding these bounds <ref type="bibr" target="#b7">[8]</ref>. Finally the bounds are forwarded to the decision unit, which has to decide if the GLB or either the LUB should be used.</p><formula xml:id="formula_1">∅ {SignHeader} {AES128} {SignBody} {AES128, SignHeader} {AES256} {AES128, SignBody} {AES256, SignHeader} {AES256, SignBody} {AES128, SignHeader+Body} {AES256, SignHeader+Body} A 1 P1 A 1 P2 LUB GLB</formula><p>Note that building the DN F can drastically increase the size of each policy and thus, building the Hasse diagram might lead to a very large model. Nevertheless, the authors believe to the best of their knowledge that this approach will hold for real examples. We stress that a real implementation and evaluation is needed to prove this.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Related Work</head><p>Researchers in <ref type="bibr" target="#b9">[10]</ref> investigated a mechanism for calculating compatibility of alternatives. An approach for comparing policies and checking compatibility between alternatives in terms of its assertions to reach intersection is shown in <ref type="bibr" target="#b10">[11]</ref> and <ref type="bibr" target="#b11">[12]</ref>. Policy reconciliation algorithm, a technique to reach policy agreement between two party communication, is introduced in <ref type="bibr" target="#b12">[13]</ref>. Another research using a web ontology language (OWL-DL) is based on the idea that policy assertions and alternatives are mapped in to program classes using OWL to measure compatibility <ref type="bibr" target="#b5">[6]</ref>. Our research focuses on how to examine intersection and find solution for policy agreement by means of partial ordering.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. Evaluating WS-Policy Intersection Model.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Signed Part and cryptographic suite combined into one Hasse diagram.</figDesc></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusions and Future Work</head><p>This paper presents a model for WS-Policy Intersection using Partial ordered sets. It is the first solution which is able to (1) handle more than two parties and (2) makes proposals for the case that the policies are not directly compatible.</p><p>For future work we plan to investigate a real protocol for multi-party negotiation which is applied to the needs and capabilities of a Web services. Additionally, we will add an implementation to show the practical usability.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<ptr target="http://www.w3.org/TR/ws-policy/,Sep.2007" />
		<title level="m">Web Service Policy 1.5 -Framework</title>
				<imprint/>
	</monogr>
	<note>W3C Recommendation</note>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<ptr target="http://www.w3.org/TR/ws-policy/,Sep.2007" />
		<title level="m">Web Service Policy Intersection</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<ptr target="http://www.w3.org/TR/ws-policy-primer/,Nov.2007" />
		<title level="m">Web Service Policy 1.5 -Primer</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<ptr target="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/" />
		<title level="m">Web Service Security Policy</title>
				<imprint>
			<date type="published" when="2009-02">Feb. 2009</date>
		</imprint>
	</monogr>
	<note>OASIS Standard</note>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Boolean algebra and its applications</title>
		<author>
			<persName><forename type="first">J</forename></persName>
		</author>
		<author>
			<persName><forename type="first">Eldon</forename><surname>Whitesitt</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1995">1995</date>
			<publisher>Courier Dover</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Representing Web Service Policies in OWL-DL</title>
		<author>
			<persName><forename type="first">V</forename><surname>Kolovski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Parsia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Katz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hendler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference (ISWC)</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2005-11">Nov. 2005</date>
			<biblScope unit="page" from="461" to="475" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">Order Relation</title>
		<author>
			<persName><forename type="first">W</forename><surname>Strunk</surname><genName>Jr</genName></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">B</forename><surname>White</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1979">1979</date>
			<publisher>Macmillan</publisher>
		</imprint>
	</monogr>
	<note>3rd ed</note>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<title level="m" type="main">Partial order</title>
		<author>
			<persName><forename type="first">M.-C</forename><surname>Van Leunen</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1979">1979</date>
			<publisher>Knopf</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<title level="m" type="main">The Apache Software Foundation</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">A S F</forename><surname>Group</surname></persName>
		</author>
		<ptr target="https://ws.apache.org/neethi/" />
		<imprint>
			<date type="published" when="2012-07">Jul. 2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Considering Web Services Security Policy Compatibility</title>
		<author>
			<persName><forename type="first">T</forename><surname>Lavarack</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Coetzee</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The 9th Annual Information Security for South Africa Conference</title>
				<imprint>
			<publisher>IEEE Press</publisher>
			<date type="published" when="2010-08">2010. Aug. 2010</date>
			<biblScope unit="page" from="1" to="8" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Domain-Specific Processing of Policies or: WS-Policy Intersection Revisited</title>
		<author>
			<persName><forename type="first">B</forename><surname>Hollunder</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IEEE 7th International Conference on Web Service (ICWS2009)</title>
				<imprint>
			<publisher>IEEE Press</publisher>
			<date type="published" when="2009-07">Jul. 2009</date>
			<biblScope unit="page" from="246" to="253" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">A Negotiation Protocol Description Language for Automated Service Level Agreement Negotiations</title>
		<author>
			<persName><forename type="first">S</forename><surname>Hudert</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Eymann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Ludwig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Wirtz</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Commerce and Enterprise Computing</title>
				<imprint>
			<publisher>IEEE Press</publisher>
			<date type="published" when="2009-08">2009. Aug 2009</date>
			<biblScope unit="page" from="162" to="169" />
		</imprint>
	</monogr>
	<note>CEC &apos;09</note>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Methods and limitations of Security Policy Reconciliation</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">P</forename><surname>Mcdaniel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">2002 IEEE Symposium on Security and Privacy</title>
				<imprint>
			<publisher>IEEE Press</publisher>
			<date type="published" when="2002-05">May 2002</date>
			<biblScope unit="page" from="73" to="87" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
