add distributed TOE clarification statement to MDM agent description

Author: crpezol

input/mdm.xml

@@ -305,38 +305,29 @@ DONE:
 			consist of a separate Mobile Application Store (MAS) server or a subordinate MDM server. 
 
 			<!-- 1.3.1 TOE Boundary -->
-			<section id="tb" title="TOE Boundary"> The MDM system operational environment consists of the MD on which the MDM agent resides, 
-				the platform on which the MDM server runs, and an untrusted wireless network over which they communicate, as pictured below.
-				<h:br/><h:br/>
+			<section id="tb" title="TOE Boundary">
+        <h:p>
+        The MDM system operational environment consists of the MD on which the MDM agent resides, the platform on which the MDM server runs, and an untrusted wireless network over which they communicate, as pictured below.
+        </h:p>
+				<h:p>
 				<figure entity="images/MDMSystem.png" title="MDM System Operating Environment" id="agentoperatingenvironment"/>
-				<h:br/><h:br/>
-				The <h:b>MDM server</h:b> is software (an application, service, etc.) on a general-purpose platform, a network device, or cloud architecture executing
-				in a trusted network environment. The MDM server provides administration of MD policies and reporting on the device behavior.
-				The MDM server is responsible for managing device enrollment, configuring and sending policies to the MDM agents, collecting reports on device
-				status, and sending commands to the agents. The MDM server may be standalone or distributed, where a distributed TOE is one that requires
-				multiple distinct components to operate as a logical whole in order to fulfill the requirements of this PP (a more extensive description of 
-				distributed MDMs is given in section 3). 
-				<h:br/><h:br/>
-				The <h:b>MDM agent</h:b> establishes a secure connection back to the
-				MDM server controlled by an enterprise administrator and configures the
-				MD per the administrator's policies. The MDM agent is addressed in the <xref to="mod-mdmagent"/>. If the MDM agent is installed on a MD as an application
-				developed by the MDM developer, the PP-Module extends this PP and is included in the TOE. In this case, the TOE security 
-				functionality specified in this PP must be
-				addressed by the MDM agent in addition to the MDM
-				Server. Otherwise, the MDM agent is provided by the MD vendor
-				and is out of scope of this PP; however, MDMs are
-				required to indicate the device platforms supported by the MDM server and
-				must be tested against the native MDM agent of those platforms.
-				<h:br/><h:br/>
-				The <h:b>Mobile Application Store (MAS)</h:b> hosts applications for the enterprise, authenticates agents, and securely transmits 
-				applications to enrolled MDs. The MAS functionality can be included as part of the MDM server Software or can be logically
-				distinct. If the MAS functionality is on a physically separate server, then the TOE is
-				distributed with the MDM server and MAS server being 
-				separate components.<h:br/><h:br/>
-        The <h:b>Subordinate MDM Server</h:b> is an optional, physically separate, server that sits between a primary MDM server and an MDM agent on a managed device. The purpose of the subordinate MDM server is to forward signed policies from a primary MDM server to an MDM agent on a managed device for which the subordinate MDM is responsible. The subordinate MDM server can either directly pass these signed policies to the managed device, or can interpret the policy into a different format if necessary. This interpretation process will follow well defined rules to ensure that the resulting interpreted policy matches the actions defined in the original policy. This interpreted policy is signed by the subordinate MDM server for delivery to the MDM agent. Any alerts or notifications generated by an MDM agent will be passed by the subordinate MDM server back to the primary MDM server to alert the enterprise administrators.
-        <h:br/><h:br/>
+        </h:p>
+        <h:p>
+				The <h:b>MDM server</h:b> is software (an application, service, etc.) on a general-purpose platform, a network device, or cloud architecture executing in a trusted network environment. The MDM server provides administration of MD policies and reporting on the device behavior. The MDM server is responsible for managing device enrollment, configuring and sending policies to the MDM agents, collecting reports on device status, and sending commands to the agents. The MDM server may be standalone or distributed, where a distributed TOE is one that requires multiple distinct components to operate as a logical whole in order to fulfill the requirements of this PP (a more extensive description of distributed MDMs is given in section 3).
+        </h:p>
+        <h:p> 
+				The <h:b>MDM agent</h:b> establishes a secure connection back to the MDM server controlled by an enterprise administrator and configures the MD per the administrator's policies. The MDM agent is addressed in the <xref to="mod-mdmagent"/>. If the MDM agent is installed on a MD as an application developed by the MDM developer, the PP-Module extends this PP and is included in the TOE. In this case the TOE security functionality specified in this PP must be addressed by the MDM agent in addition to the MDM Server, additionally the TOE can be considered distributed. Otherwise, the MDM agent is provided by the MD vendor and is out of scope of this PP; however, MDMs are required to indicate the device platforms supported by the MDM server and must be tested against the native MDM agent of those platforms.
+        </h:p>
+        <h:p>
+				The <h:b>Mobile Application Store (MAS)</h:b> hosts applications for the enterprise, authenticates agents, and securely transmits applications to enrolled MDs. The MAS functionality can be included as part of the MDM server Software or can be logically
+				distinct. If the MAS functionality is on a physically separate server, then the TOE is distributed with the MDM server and MAS server being separate components.
+        </h:p>
+        <h:p>
+        The <h:b>Subordinate MDM Server</h:b> is an optional, physically separate, server that sits between a primary MDM server and an MDM agent on a managed device. The purpose of the subordinate MDM server is to forward signed policies from a primary MDM server to an MDM agent on a managed device for which the subordinate MDM is responsible. The subordinate MDM server can either directly pass these signed policies to the managed device, or can interpret the policy into a different format if necessary. This interpretation process will follow well defined rules to ensure that the resulting interpreted policy matches the actions defined in the original policy. This interpreted policy is signed by the subordinate MDM server for delivery to the MDM agent. Any alerts or notifications generated by an MDM agent will be passed by the subordinate MDM server back to the primary MDM server to alert the enterprise administrators. The subordinate MDM server and primary MDM servers are two separate TOE's and would be evaluated independently of each-other, they do not form a distributed TOE. 
+        </h:p>
+        <h:p>
         <figure entity="images/SubordinateMDMSystem.png" title="MDM System with Subordinate MDM" id="subordinateMDMDiagram"/>
-				<h:br/><h:br/>
+        </h:p>
 			</section>
 		</section>
 
@@ -1114,7 +1105,7 @@ DONE:
 			Only those SFRs included in the ST are required to be audited. The ST for a distributed TOE must include a mapping of SFRs to each of the components 
 			of the TOE. (Note that this deliverable is examined as part of the ASE_TSS.1 and AVA_VAN.1 Evaluation Activities.) The ST for a distributed TOE 
 			may also introduce a "minimum configuration" and identify components that may have instances added to an operational configuration without affecting 
-			the validity of the CC certification. Appendix E describes Evaluation Activities relating to these equivalency aspects of a distributed TOE (and
+			the validity of the CC certification. <xref to="EACDT"/> describes Evaluation Activities relating to these equivalency aspects of a distributed TOE (and
 			hence what is expected in the ST). 
 		</section>