## 6 Data Analysis
### Analysis of BYOD Security Policy Techniques Based on Privacy and Security Requirements
\begin{table}
\begin{tabular}{c c c c c c} \hline \hline
**Ref** & **Technology Employed** & **Performance Analysis** & **Advantage** & **Limitation** \\ \hline
[104] & Enforce access control policy architecture. & NA & Simple policy. & It is only a preliminary proposal that needs implementation \\
[105] & STRIDE-based BYOD & NA & BYOD concerns affect corporate data & Only provides an initial model. \\
[106] & An investigation framework. & Safe-Logic experts evaluated based on particular criteria. & EXCID threats and solutions. & Only provides an initial model. \\
[107] & Proactive approach based & NA & Creating benchmarks for BYOD security protocols. & Only identified security metric. \\
[108] & OPPRIM model. & Mathematical analysis and quantitative model. & Integrating trust and risk management mechanisms with threat analysis & Only provides an initial model. \\
[109] & Poise policy for device, app. & Prototype implementation. & It is network analysis. & It should build and test a complete prototype. \\
[110] & Fine-grained policies (BYODroid model). & Case Study. & Apply policy on the infrastructure layer. & Implementation is needed to verify rules. \\
[111,112] & Security architecture. & Case Study. & Flexible and adaptable to various business fields. & Only provides a starting point. \\
[113] & Metamodeling techniques. & Case study (Interview domain experts at the Ottawa Hospital to validate). & Identify key BYOD risk assessment metamodel concepts. & Initial and limited architecture. \\
[114,115] & Other methods (middleboxes and alert systems). & Prototype implementation. & Accurate transparency, usability, and performance with HTTPS security. & It is only a preliminary proposal that needs implementation. \\
[116] & Plugin Framework Based fine-grained security policy. & Prototype implementation. & Policy execution on any device connection network & No other systems (only Android). \\
[117] & BYOD security framework & Case study (Australian, questionnaire instrument) & Building new framework to improve attack and threat defence. & Discusses only the theoretical aspect. \\ \hline \hline \end{tabular}
\end{table} 
Table 11: Summary of techniques based on multiple security and privacy requirements. \begin{table}
\begin{tabular}{c c c c c} \hline \hline
**Privacy** & **Ref** & **Technology Employed** & **Performance Analysis** & **Advantage** & **Limitation** \\ \hline Confidentiality and Authentication. & [99] & AES,HMAC algorithm & Prototype implementation. & \
\begin{tabular}{c} Authentication- \\ based cryptography \\ secures networks \\ and users. \\ \end{tabular} &
\begin{tabular}{c} Certificate \\ management challenges. \\ \end{tabular} \\ Confidentiality and Authentication. & [100] & Optimizing and encrypting & Prototype implementation. & Protects data from key leakage. & Secure but complicated. \\ Confidentiality and Authentication. & [101] & Biohashing technique. & Mathematical analysis, experimental. & Increases security and lowers error rates. & Data increases collision probability. \\ Attack Detection, Authentication, and Confidentiality. & [102] & SDN and 2 FA (TOTP)-based virtualization method. & Prototype implementation, Proof of concept. & Security and assault reduction. & ARP spoofing is the only attack allowed with this method. \\  & & PHE encryption, tracing, and revoking (tracing, algorithm, public revocation & Simulation, experimental analysis (an RBAC simulation system with ten classes and around ten users per class). & Tracking and key service interruptions provide safety. \\ \hline \hline \end{tabular}
\end{table} 
Table 12: Summary of the techniques that did not consider any of the proposed requirements.