diff --git a/PBDSecPaper.tex b/PBDSecPaper.tex
index a7f5d93..8d68334 100644
--- a/PBDSecPaper.tex
+++ b/PBDSecPaper.tex
@@ -223,11 +223,10 @@ \section{Security}
 	\begin{itemize}
 	\item When automating the development of security systems there are three key elements of the system that need to be examined/accounted for in the virtualization stage: security mechanisms, security principles, and security policies.
 		\begin{itemize}
-		\item Security Mechanisms - system artifacts that are used to enforece system security policies.
-		\item Security Principles - guidelines or rules that when followed during system design will aid in making the system secure.
-		\item Security Policies - organizational security policies are ``the set of laws, rules, and practices that regulate how an organization manages, protects, and distributes sensitive information.''  System Security Policies are rules that the information system enforces relative to the resources under its control to reflect the organizational security policy.
+		\item For the purpose of reiteration, security mechanisms are the system artifacts that are used to enforece system security policies.  Security principles are the guidelines or rules that when followed during system design will aid in making the system secure.  Organizational security policies are ``the set of laws, rules, and practices that regulate how an organization manages, protects, and distributes sensitive information.''~\cite{Benzel2005}  System Security Policies are rules that the information system enforces relative to the resources under its control to reflect the organizational security policy.  
+		\item Each of these aspects plays its part in determining the behvaior and function of the overall security system.  \textbf{Illustrate the importance of these different security elements (mechanisms, principles and policies) and talk a little about the difference between organizational security policies and system security policies}.  The security prinicples set the groundwork for how the system should behave and interact based on the expected user interactions.  The security policies (both organizational and system) govern the rules and practices that regulate how the system, and its resources, is managed, how the information is protected, and how the system controls and distributes sensitive information.  The security mechanisms are the implementations on these previous two aspects by being the system artifacts that are used to enforce the system security policies.
 		\end{itemize}
-	\item In the same manner that these various security aspects (e.g. mechanisms, principles, policies) must be considered during developemtn automation, the software and hardware aspects must also come under consideration based on the desired behavior/functionality of the system under design.  Could have security elements that attempt to optimize themselves to the system they are in based on a few pivot points (power, time, efficiency, level of randomness).  Another option for the automated tool could trade out specific security components as an easier way to increase security without requireing re-design/re-construction of the underlying element.  There is always the requirement that the overall trustworthiness of a new system must meet the standards of the security policies that `rule' the system.
+	\item In the same manner that these various security aspects (e.g. mechanisms, principles, policies) must be considered during developemtn automation, the software and hardware aspects must also come under consideration based on the desired behavior/functionality of the system under design.  Could have security elements that attempt to optimize themselves to the system they are in based on a few pivot points (power, time, efficiency, level of randomness).  Another option for the automated tool could trade out specific security components as an easier way to increase security without requiring re-design/re-construction of the underlying element.  There is always the requirement that the overall trustworthiness of a new system must meet the standards of the security policies that `rule' the system.  For these reasons a user would desire rigorous documentation that would lay out the requirements of each component, so that in the case of trying to replace faulty or damaged components there would be no loss to the overall trustworthiness of the system while also not introducing any vulnerabilities due to the inclusion of new system components.
 	\item Virtualization should be used for exploring the design space, as it is hoped that it is obvious as to why.  Not only is the cost of prototyping incredably expensive, but redesign is equally costly.  Virtualization aids by removing the need for a physical prototyping (less monitary costs) and allows for more rapid exploration of the full design space.  While the design time for such powerful tools will be expensive (both in monitary and temporal costs), the rewards of developing, validating, and evaluating this virtualization tool will offset the early design phase costs of an automation of security component design.
 	\end{itemize}
 \item Mapping of Security onto PBD structure