noah/Synchronous_Firing
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rewording sync fire illustration description for DMCA ex

Browse Source
This commit is contained in:
Noah L. Schrick 2023-03-24 16:03:03 -05:00
parent d7e42b0cc6
commit 014808c9b6
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
OJ_Template/First Revise and Resubmit/Schrick-Noah_AG-CG-SyncFire_Revised.tex
View File

@ -197,13 +197,13 @@ The compliance checks are as follows:
\subsubsection{DMCA Takedown}
A second example of synchronous firing is illustrated through a DMCA Takedown for a fictitious organization \cite{DMCA}. In this example, a DMCA Takedown is issued to an organization after a group of employees were found to be engaging in online piracy with torrenting software on company devices and while using company resources. Detection and removal of illicit data, such as through means presented by the authors of \cite{Piracy} for Windows or \cite{Android_Piracy} for company-supplied Android mobile devices, can be incorporated into and represented by a compliance graph.
Only the subset of the organization's network which contains the illicit data is used for this example. The graph generation process walks through as a system administrator removes the torrenting software and the illicit data from the company devices. When removing torrenting software, the data associated with the torrenting program can be removed at the same time; an administrator does not need to remove the torrenting program and then separately remove the data. This example highlights the capability of synchronous firing by grouping the removal of software and data together, as opposed to traditional attack and compliance graphs requiring at least two separate steps to remove the software and data.
For this example, various graphs are generated based on the permutations of employees present. In one graph, only Employee A is present in the network. In another graph, Employees B and C are present in the network. All permutations are tested and are show in \ref{sec:dmca_res}. The graph generation process walks through as a system administrator removes the torrenting software and the illicit data from the company devices. Typically when removing torrenting software, the data associated with the torrenting program can be removed at the same time as the uninstall automatically; an administrator does not need to remove the torrenting program and then separately remove the data. Without the use of synchronous firing, attack and compliance graphs must individually remove all data and all programs individually. This example highlights the capability of synchronous firing by grouping the removal of software and data together through ``uninstall" groups, as opposed to traditional attack and compliance graphs requiring multiple steps to remove the software and data.
This experimental setup is as follows:
\begin{itemize}
\item{Employee A has torrenting software, and is actively uploading and downloading 3 programs.}
\item{Employee B has torrenting software, and is actively uploading and downloading 4 programs.}
\item{Employee C has torrenting software, and is actively uploading and downloading 7 programs.}
\item{Employee C has torrenting software, and is actively uploading and downloading 5 programs.}
\item{If synchronous firing is not enabled, the administrator removes each illicit program one-by-one after the removal of the torrenting software.}
\item{If synchronous firing is enabled, the administrator removes the torrenting software and all programs off a single device simultaneously.}
\item{Graph visualization was not timed. Only the generation and database operation time was measured.}