Finalizing Revision 1

This commit is contained in:
Noah L. Schrick 2023-03-24 17:55:39 -05:00
parent 014808c9b6
commit 47210dedb3
26 changed files with 534 additions and 507 deletions

View File

@ -227,7 +227,7 @@ doi = {10.29007/2c1q}
doi={10.1109/IMIS.2014.29}
}
@inproceedings{Android_Piracy,
@inproceedings{AndroidPiracy,
author={Kumari, Neha and Chen, Min},
booktitle={2022 IEEE 5th International Conference on Multimedia Information Processing and Retrieval (MIPR)},
title={Malware and Piracy Detection in Android Applications},
@ -235,4 +235,5 @@ doi = {10.29007/2c1q}
volume={},
number={},
pages={306-311},
doi={10.1109/MIPR54900.2022.00061}}
doi={10.1109/MIPR54900.2022.00061}
}

View File

@ -48,36 +48,44 @@
\@writefile{toc}{\contentsline {subsubsection}{\numberline {1}Automobile Maintenance}{5}{}\protected@file@percent }
\citation{DMCA}
\citation{Piracy}
\citation{Android_Piracy}
\citation{AndroidPiracy}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2}DMCA Takedown}{6}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {B}Results and Analysis}{6}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsubsection}{\numberline {1}Results for the Theoretical Automobile Environment}{6}{}\protected@file@percent }
\newlabel{sec:theo_res}{{1}{6}}
\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Results for the Non-Synchronous Firing Testing}}{6}{}\protected@file@percent }
\newlabel{table:NS-Table}{{1}{6}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2}Results for a Grouped Automobile Environment}{6}{}\protected@file@percent }
\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Synchronous Firing on Runtime}}{7}{}\protected@file@percent }
\newlabel{fig:Sync-RT}{{4}{7}}
\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces Bar Graph and Line Graph Representations of Synchronous Firing on State Space}}{7}{}\protected@file@percent }
\newlabel{fig:Sync-State}{{5}{7}}
\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Speedup (Amdahl's) Obtained When Using Synchronous Firing}}{7}{}\protected@file@percent }
\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Results for the Non-Synchronous Firing Testing}}{7}{}\protected@file@percent }
\newlabel{table:NS-Table}{{1}{7}}
\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Speedup (Amdahl's) and State Space Reduction Factor Obtained When Using Synchronous Firing}}{7}{}\protected@file@percent }
\newlabel{fig:Sync-Spd}{{6}{7}}
\@writefile{lot}{\contentsline {table}{\numberline {2}{\ignorespaces Results for the Synchronous Firing Testing}}{7}{}\protected@file@percent }
\newlabel{table:S-Table}{{2}{7}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2}Results for a Grouped Automobile Environment}{7}{}\protected@file@percent }
\@writefile{lot}{\contentsline {table}{\numberline {3}{\ignorespaces Results for the Comprehensive Services without Synchronous Firing}}{8}{}\protected@file@percent }
\newlabel{table:Non-Sync-Comp-Table}{{3}{8}}
\@writefile{lot}{\contentsline {table}{\numberline {4}{\ignorespaces Results for the Comprehensive Services with Synchronous Firing}}{8}{}\protected@file@percent }
\newlabel{table:Sync-Comp-Table}{{4}{8}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {3}Results for the DMCA Takedown Environment}{8}{}\protected@file@percent }
\newlabel{sec:dmca_res}{{3}{8}}
\@writefile{toc}{\contentsline {section}{\numberline {VI}Future Works}{8}{}\protected@file@percent }
\newlabel{sec:fw}{{VI}{8}}
\@writefile{lot}{\contentsline {table}{\numberline {4}{\ignorespaces Results for the Comprehensive Services with Synchronous Firing}}{8}{}\protected@file@percent }
\newlabel{table:Sync-Comp-Table}{{4}{8}}
\@writefile{lof}{\contentsline {figure}{\numberline {7}{\ignorespaces Synchronous Firing on Runtime}}{8}{}\protected@file@percent }
\newlabel{fig:Comp-Sync-RT}{{7}{8}}
\@writefile{lof}{\contentsline {figure}{\numberline {8}{\ignorespaces Bar Graph and Line Graph Representations of Synchronous Firing with Comprehensive Services on State Space}}{8}{}\protected@file@percent }
\newlabel{fig:Comp-Sync-State}{{8}{8}}
\@writefile{lof}{\contentsline {figure}{\numberline {9}{\ignorespaces Speedup (Amdahl's) Obtained When Using Synchronous Firing with Comprehensive Services}}{8}{}\protected@file@percent }
\newlabel{fig:Comp-Sync-Spd}{{9}{8}}
\@writefile{lof}{\contentsline {figure}{\numberline {9}{\ignorespaces Speedup (Amdahl's) Obtained When Using Synchronous Firing with Comprehensive Services}}{9}{}\protected@file@percent }
\newlabel{fig:Comp-Sync-Spd}{{9}{9}}
\@writefile{lot}{\contentsline {table}{\numberline {5}{\ignorespaces Results for the Non-Synchronous Firing Testing}}{9}{}\protected@file@percent }
\newlabel{table:DMCA-NS-Table}{{5}{9}}
\@writefile{lot}{\contentsline {table}{\numberline {6}{\ignorespaces Results for the Synchronous Firing Testing}}{9}{}\protected@file@percent }
\newlabel{table:DMCA-S-Table}{{6}{9}}
\@writefile{lof}{\contentsline {figure}{\numberline {10}{\ignorespaces Synchronous Firing on State Space and Runtime for the DMCA Takedown Environment}}{9}{}\protected@file@percent }
\newlabel{fig:DMCA-States-Runtime}{{10}{9}}
\@writefile{lof}{\contentsline {figure}{\numberline {11}{\ignorespaces Speedup (Amdahl's) and State Space Reduction Factor Obtained When Using Synchronous Firing}}{9}{}\protected@file@percent }
\newlabel{fig:DMCA-Sync-Spd}{{11}{9}}
\@writefile{toc}{\contentsline {section}{\numberline {VI}Future Works}{9}{}\protected@file@percent }
\newlabel{sec:fw}{{VI}{9}}
\bibdata{Bibliography}
\bibcite{phillips_graph-based_1998}{1}
\bibcite{schneier_modeling_1999}{2}
@ -97,7 +105,10 @@
\bibcite{louthan_hybrid_2011}{16}
\bibcite{cook_rage_2018}{17}
\bibcite{nichols_2018}{18}
\bibcite{DMCA}{19}
\bibcite{Piracy}{20}
\bibcite{AndroidPiracy}{21}
\bibstyle{ieeetr}
\@writefile{toc}{\contentsline {section}{\numberline {VII}Conclusion}{9}{}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{REFERENCES}{9}{}\protected@file@percent }
\gdef \@abspage@last{9}
\@writefile{toc}{\contentsline {section}{\numberline {VII}Conclusion}{10}{}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{REFERENCES}{10}{}\protected@file@percent }
\gdef \@abspage@last{10}

View File

@ -92,4 +92,20 @@ W.~M. Nichols, {\em {Hybrid} {Attack} {Graphs} for {Use} with a {Simulation} of
a {Cyber-Physical} {System}}.
\newblock PhD thesis, The {University} of {Tulsa}, 2018.
\bibitem{DMCA}
``H.r.2281 - {Digital {Millennium} {Copyright} {Act}}.''
\newblock Pub. L. No. 105-304. 1998 [Online]. Available:
https://www.govinfo.gov/content/pkg/PLAW-105publ304/html/PLAW-105publ304.htm.
\bibitem{Piracy}
Y.~Kim, J.~Moon, S.~J. Cho, M.~Park, and S.~Han, ``Efficient identification of
windows executable programs to prevent software piracy,'' in {\em 2014 Eighth
International Conference on Innovative Mobile and Internet Services in
Ubiquitous Computing}, pp.~236--240, 2014.
\bibitem{AndroidPiracy}
N.~Kumari and M.~Chen, ``Malware and piracy detection in android
applications,'' in {\em 2022 IEEE 5th International Conference on Multimedia
Information Processing and Retrieval (MIPR)}, pp.~306--311, 2022.
\end{thebibliography}

View File

@ -3,50 +3,47 @@ Capacity: max_strings=200000, hash_size=200000, hash_prime=170003
The top-level auxiliary file: Schrick-Noah_AG-CG-SyncFire_Revised.aux
The style file: ieeetr.bst
Database file #1: Bibliography.bib
Warning--I didn't find a database entry for "DMCA"
Warning--I didn't find a database entry for "Piracy"
Warning--I didn't find a database entry for "Android_Piracy"
Warning--empty booktitle in centrality_based
Warning--empty publisher in TVA
You've used 18 entries,
You've used 21 entries,
1876 wiz_defined-function locations,
587 strings with 6994 characters,
and the built_in function-call counts, 4246 in all, are:
= -- 415
> -- 178
599 strings with 7628 characters,
and the built_in function-call counts, 5065 in all, are:
= -- 493
> -- 204
< -- 0
+ -- 67
- -- 49
* -- 286
:= -- 624
add.period$ -- 25
call.type$ -- 18
change.case$ -- 14
+ -- 77
- -- 56
* -- 333
:= -- 722
add.period$ -- 28
call.type$ -- 21
change.case$ -- 17
chr.to.int$ -- 0
cite$ -- 20
duplicate$ -- 230
empty$ -- 405
format.name$ -- 49
if$ -- 1028
cite$ -- 23
duplicate$ -- 276
empty$ -- 497
format.name$ -- 56
if$ -- 1242
int.to.chr$ -- 0
int.to.str$ -- 18
missing$ -- 15
newline$ -- 65
num.names$ -- 18
pop$ -- 64
int.to.str$ -- 21
missing$ -- 17
newline$ -- 75
num.names$ -- 20
pop$ -- 87
preamble$ -- 1
purify$ -- 0
quote$ -- 0
skip$ -- 138
skip$ -- 172
stack$ -- 0
substring$ -- 202
swap$ -- 82
substring$ -- 258
swap$ -- 100
text.length$ -- 0
text.prefix$ -- 0
top$ -- 0
type$ -- 0
warning$ -- 2
while$ -- 35
width$ -- 20
write$ -- 178
(There were 5 warnings)
while$ -- 41
width$ -- 23
write$ -- 203
(There were 2 warnings)

View File

@ -1,8 +1,8 @@
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Arch Linux) (preloaded format=pdflatex 2023.2.27) 22 MAR 2023 18:18
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Arch Linux) (preloaded format=pdflatex 2023.2.27) 24 MAR 2023 17:47
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**Schrick-Noah_AG-CG-SyncFire_Revised.tex
**Schrick-Noah_AG-CG-SyncFire_Revised
(./Schrick-Noah_AG-CG-SyncFire_Revised.tex
LaTeX2e <2021-11-15> patch level 1
L3 programming layer <2022-04-10> (./ieeeoj.cls
@ -381,15 +381,11 @@ File: ./images/schri1.png Graphic file (type png)
<use ./images/schri1.png>
Package pdftex.def Info: ./images/schri1.png used on input line 85.
(pdftex.def) Requested size: 221.3985pt x 87.37611pt.
LaTeX Warning: Reference `fig:non-sync-ex' on page 3 undefined on input line 94
.
LaTeX Font Info: Font shape `OT1/phv/b/it' in size <9> not available
(Font) Font shape `OT1/phv/b/sl' tried instead on input line 97.
LaTeX Font Info: Trying to load font information for OT1+pcr on input line 1
01.
(/usr/share/texmf-dist/tex/latex/psnfss/ot1pcr.fd
File: ot1pcr.fd 2001/06/04 font definitions for OT1/pcr.
)
@ -455,19 +451,6 @@ Underfull \vbox (badness 10000) has occurred while \output is active []
Overfull \vbox (8.45pt too high) has occurred while \output is active []
[5 <./images/schri3.png>]
LaTeX Warning: Citation `DMCA' on page 6 undefined on input line 198.
LaTeX Warning: Citation `Piracy' on page 6 undefined on input line 198.
LaTeX Warning: Citation `Android_Piracy' on page 6 undefined on input line 198.
Underfull \vbox (badness 10000) has occurred while \output is active []
<./images/schri4.png, id=39, 602.25pt x 238.491pt>
File: ./images/schri4.png Graphic file (type png)
<use ./images/schri4.png>
@ -493,9 +476,11 @@ File: ./images/schri8.png Graphic file (type png)
<use ./images/schri8.png>
Package pdftex.def Info: ./images/schri8.png used on input line 244.
(pdftex.def) Requested size: 238.49121pt x 105.68184pt.
Underfull \vbox (badness 10000) has occurred while \output is active []
<./images/schri9.png, id=44, 535.893pt x 236.301pt>
File: ./images/schri9.png Graphic file (type png)
<use ./images/schri9.png>
Package pdftex.def Info: ./images/schri9.png used on input line 245.
(pdftex.def) Requested size: 238.49121pt x 105.15901pt.
Overfull \vbox (11.34346pt too high) has occurred while \output is active []
@ -503,6 +488,8 @@ Overfull \vbox (11.34346pt too high) has occurred while \output is active []
Overfull \vbox (11.2pt too high) has occurred while \output is active []
[6]
Underfull \vbox (badness 1158) has occurred while \output is active []
File: OJIM.png Graphic file (type png)
<use OJIM.png>
Package pdftex.def Info: OJIM.png used on input line 304.
@ -514,47 +501,63 @@ Underfull \vbox (badness 10000) has occurred while \output is active []
Overfull \vbox (8.45pt too high) has occurred while \output is active []
[7 <./images/schri4.png> <./images/schri5.png> <./images/schri6.png> <./images
/schri7.png> <./images/schri8.png>]
<./images/schri9.png, id=56, 602.25pt x 238.491pt>
File: ./images/schri9.png Graphic file (type png)
<use ./images/schri9.png>
Package pdftex.def Info: ./images/schri9.png used on input line 356.
(pdftex.def) Requested size: 238.49121pt x 94.44125pt.
<./images/schri10.png, id=57, 549.69pt x 236.301pt>
/schri7.png> <./images/schri8.png> <./images/schri9.png>]
<./images/schri10.png, id=58, 602.25pt x 238.491pt>
File: ./images/schri10.png Graphic file (type png)
<use ./images/schri10.png>
Package pdftex.def Info: ./images/schri10.png used on input line 357.
(pdftex.def) Requested size: 238.49121pt x 102.51967pt.
<./images/schri11.png, id=58, 600.717pt x 230.607pt>
Package pdftex.def Info: ./images/schri10.png used on input line 358.
(pdftex.def) Requested size: 238.49121pt x 94.44125pt.
<./images/schri11.png, id=59, 560.421pt x 236.301pt>
File: ./images/schri11.png Graphic file (type png)
<use ./images/schri11.png>
Package pdftex.def Info: ./images/schri11.png used on input line 364.
(pdftex.def) Requested size: 238.49121pt x 91.555pt.
<./images/schri12.png, id=59, 532.389pt x 236.739pt>
Package pdftex.def Info: ./images/schri11.png used on input line 359.
(pdftex.def) Requested size: 238.49121pt x 100.5618pt.
<./images/schri12.png, id=60, 600.717pt x 230.607pt>
File: ./images/schri12.png Graphic file (type png)
<use ./images/schri12.png>
Package pdftex.def Info: ./images/schri12.png used on input line 365.
(pdftex.def) Requested size: 238.49121pt x 106.05112pt.
<./images/schri13.png, id=60, 533.265pt x 236.301pt>
Package pdftex.def Info: ./images/schri12.png used on input line 366.
(pdftex.def) Requested size: 238.49121pt x 91.555pt.
<./images/schri13.png, id=61, 542.463pt x 236.739pt>
File: ./images/schri13.png Graphic file (type png)
<use ./images/schri13.png>
Package pdftex.def Info: ./images/schri13.png used on input line 372.
(pdftex.def) Requested size: 238.49121pt x 105.68184pt.
Package pdftex.def Info: ./images/schri13.png used on input line 367.
(pdftex.def) Requested size: 238.49121pt x 104.08238pt.
<./images/schri14.png, id=62, 535.893pt x 236.301pt>
File: ./images/schri14.png Graphic file (type png)
<use ./images/schri14.png>
Package pdftex.def Info: ./images/schri14.png used on input line 374.
(pdftex.def) Requested size: 238.49121pt x 105.15901pt.
Overfull \vbox (11.34346pt too high) has occurred while \output is active []
Overfull \vbox (11.2pt too high) has occurred while \output is active []
[8 <./images/schri9.png> <./images/schri10.png> <./images/schri11.png> <./imag
es/schri12.png> <./images/schri13.png>]
Underfull \vbox (badness 2990) has occurred while \output is active []
(./Schrick-Noah_AG-CG-SyncFire_Revised.bbl)
[8 <./images/schri10.png> <./images/schri11.png> <./images/schri12.png> <./ima
ges/schri13.png>]
<./images/schri15.png, id=70, 542.463pt x 236.739pt>
File: ./images/schri15.png Graphic file (type png)
<use ./images/schri15.png>
Package pdftex.def Info: ./images/schri15.png used on input line 436.
(pdftex.def) Requested size: 238.49121pt x 104.08238pt.
<./images/schri16.png, id=71, 560.421pt x 236.301pt>
File: ./images/schri16.png Graphic file (type png)
<use ./images/schri16.png>
Package pdftex.def Info: ./images/schri16.png used on input line 437.
(pdftex.def) Requested size: 238.49121pt x 100.5618pt.
<./images/schri17.png, id=72, 536.112pt x 236.301pt>
File: ./images/schri17.png Graphic file (type png)
<use ./images/schri17.png>
Package pdftex.def Info: ./images/schri17.png used on input line 444.
(pdftex.def) Requested size: 238.49121pt x 105.11935pt.
<./images/schri18.png, id=73, 535.893pt x 236.301pt>
File: ./images/schri18.png Graphic file (type png)
<use ./images/schri18.png>
Package pdftex.def Info: ./images/schri18.png used on input line 445.
(pdftex.def) Requested size: 238.49121pt x 105.15901pt.
File: OJIM.png Graphic file (type png)
<use OJIM.png>
Package pdftex.def Info: OJIM.png used on input line 393.
Package pdftex.def Info: OJIM.png used on input line 452.
(pdftex.def) Requested size: 75.09589pt x 28.0pt.
Underfull \vbox (badness 10000) has occurred while \output is active []
@ -562,24 +565,44 @@ Underfull \vbox (badness 10000) has occurred while \output is active []
Overfull \vbox (8.45pt too high) has occurred while \output is active []
[9]
[9 <./images/schri14.png> <./images/schri15.png> <./images/schri16.png> <./ima
ges/schri17.png> <./images/schri18.png>] (./Schrick-Noah_AG-CG-SyncFire_Revised
.bbl
Underfull \hbox (badness 10000) in paragraph at lines 96--99
[]\OT1/ptm/m/n/8 ``H.r.2281 - Dig-i-tal Mil-len-nium Copy-right Act.''
[]
Underfull \hbox (badness 10000) in paragraph at lines 96--99
\OT1/ptm/m/n/8 Pub. L. No. 105-304. 1998 [On-line]. Avail-able:
[]
Underfull \hbox (badness 10000) in paragraph at lines 96--99
\OT1/ptm/m/n/8 https://www.govinfo.gov/content/pkg/PLAW-105publ304/html/PLAW-
[]
)
Overfull \vbox (11.34346pt too high) has occurred while \output is active []
Overfull \vbox (11.2pt too high) has occurred while \output is active []
[10]
(./Schrick-Noah_AG-CG-SyncFire_Revised.aux)
LaTeX Font Warning: Size substitutions with differences
(Font) up to 1.7pt have occurred.
LaTeX Warning: There were undefined references.
)
Here is how much of TeX's memory you used:
4289 strings out of 478238
68042 string characters out of 5850456
376168 words of memory out of 5000000
22443 multiletter control sequences out of 15000+600000
4332 strings out of 478238
69089 string characters out of 5850456
375216 words of memory out of 5000000
22481 multiletter control sequences out of 15000+600000
528290 words of font info for 140 fonts, out of 8000000 for 9000
1141 hyphenation exceptions out of 8191
55i,14n,62p,1478b,335s stack positions out of 5000i,500n,10000p,200000b,80000s
55i,14n,62p,1519b,335s stack positions out of 5000i,500n,10000p,200000b,80000s
{/usr/share/texmf-dist/fonts/enc/dvips/base/8r.enc}</usr/share/texmf-dist/fon
ts/type1/public/amsfonts/cm/cmmi10.pfb></usr/share/texmf-dist/fonts/type1/publi
c/amsfonts/cm/cmr10.pfb></usr/share/texmf-dist/fonts/type1/public/amsfonts/cm/c
@ -590,11 +613,11 @@ vetic/uhvb8a.pfb></usr/share/texmf-dist/fonts/type1/urw/helvetic/uhvbo8a.pfb></
usr/share/texmf-dist/fonts/type1/urw/helvetic/uhvr8a.pfb></usr/share/texmf-dist
/fonts/type1/urw/times/utmb8a.pfb></usr/share/texmf-dist/fonts/type1/urw/times/
utmr8a.pfb></usr/share/texmf-dist/fonts/type1/urw/times/utmri8a.pfb>
Output written on Schrick-Noah_AG-CG-SyncFire_Revised.pdf (9 pages, 2371409 byt
es).
Output written on Schrick-Noah_AG-CG-SyncFire_Revised.pdf (10 pages, 2734531 by
tes).
PDF statistics:
124 PDF objects out of 1000 (max. 8388607)
60 compressed objects within 1 object stream
137 PDF objects out of 1000 (max. 8388607)
62 compressed objects within 1 object stream
0 named destinations out of 1000 (max. 500000)
71 words of extra memory for PDF output out of 10000 (max. 10000000)
96 words of extra memory for PDF output out of 10000 (max. 10000000)

View File

@ -91,7 +91,7 @@ Post-processing is one option at removing the unattainable states. This process
Instead, a new feature called synchronous firing can be used to prevent the generation of these states. The goal of the synchronous firing feature is to prevent the generation of unattainable states, while incurring no greater computational cost. Section \ref{sec:implementing} will discuss the development of this feature, and Section \ref{sec:Results} will examine the results when using this feature in applicable networks.
\section{Implementing Synchronous Firing} \label{sec:implementing}
Synchronous exploit firing aims to eliminate the generation of infeasible states during the generation process, rather than needing an additional post-processing step. Using Fig. \ref{fig:non-sync-ex} as an example, the goal of synchronous firing is to only generate the 3 valid, unshaded nodes, rather than generate all 16 nodes since 13 of the nodes represent an impossibility where two cars are progressing through time at different rates. Synchronous firing is accomplished through new grouping keywords in the input exploit file, which propagate through the modified attack and compliance graph engine, and prevent the firing of exploits if they are part of a group where all members are not yet available to fire.
Synchronous exploit firing aims to eliminate the generation of infeasible states during the generation process, rather than needing an additional post-processing step. Using Fig. \ref{fig:non-sync_ex} as an example, the goal of synchronous firing is to only generate the 3 valid, unshaded nodes, rather than generate all 16 nodes since 13 of the nodes represent an impossibility where two cars are progressing through time at different rates. Synchronous firing is accomplished through new grouping keywords in the input exploit file, which propagate through the modified attack and compliance graph engine, and prevent the firing of exploits if they are part of a group where all members are not yet available to fire.
For the implementation of the synchronous firing feature, there were four primary changes and additions that were required. The first is a change in the lexical analyzer, which handles the model and exploit input. Users indicate features that should fire simultaneously in these input files, and the lexical analyzer is responsible for parsing and passing that information to the graph generator. The second involves multiple changes to PostgreSQL to support the storage of group features and information. The third is the implementation of compound operators in RAGE, since enumeration of all exploits may not be possible, especially when modeling a system over time. The fourth is a change in the graph generation process, which checks to see if all exploits in a group are able to fire simultaneously before firing. The subsections in this Section describe these four alterations in greater detail.
\subsection{GNU Bison and Flex}
@ -195,7 +195,7 @@ The compliance checks are as follows:
\end{itemize}
\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.
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{AndroidPiracy} for company-supplied Android mobile devices, can be incorporated into and represented by a compliance graph.
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.
@ -217,7 +217,7 @@ The compliance checks are as follows:
\subsection{Results and Analysis}
\subsubsection{Results for the Theoretical Automobile Environment} \label{sec:theo_res}
Using the experimental setup described in Section \ref{sec:test-platform} on the platform described at the beginning of Section \ref{sec:test-platform}, results were collected in regards to the effect of synchronous firing on both state space and runtime. The graphs' edge to state ratio (E/S Ratio) was computed as well. The inclusion of this ratio allows for a comparison to be drawn regarding the usage of the synchronous firing feature. Examining this ratio can provide additional insight on how the graph's underlying topological structures change when using or not using synchronous firing. The results can be seen in Figures \ref{fig:Sync-RT} and \ref{fig:Sync-State}. The respective tables are seen in Tables \ref{table:NS-Table} and \ref{table:S-Table}. Both figures show a decrease in the number of states and a decrease in the runtime when synchronous firing is utilized. Since synchronous firing prevents the generation of unattainable states, there is no meaningful information loss that occurs in the graphs generated with the synchronous firing feature. Since the resulting number of states was also reduced, there will be increased justification for the synchronous firing approach due to a reduced runtime for the analysis process. Fig. \ref{fig:Sync-Spd} displays the speedup (according to Amdahl's Law) obtained when using synchronous firing instead of non-synchronous firing for identical setups.
Using the experimental setup described in Section \ref{sec:test-platform} on the platform described at the beginning of Section \ref{sec:test-platform}, results were collected in regards to the effect of synchronous firing on both state space and runtime. The graphs' edge to state ratio (E/S Ratio) was computed as well. The inclusion of this ratio allows for a comparison to be drawn regarding the usage of the synchronous firing feature. Examining this ratio can provide additional insight on how the graph's underlying topological structures change when using or not using synchronous firing. The results can be seen in Figures \ref{fig:Sync-RT} and \ref{fig:Sync-State}. The respective tables are seen in Tables \ref{table:NS-Table} and \ref{table:S-Table}. Both figures show a decrease in the number of states and a decrease in the runtime when synchronous firing is utilized. Since synchronous firing prevents the generation of unattainable states, there is no meaningful information loss that occurs in the graphs generated with the synchronous firing feature. Since the resulting number of states was also reduced, there will be increased justification for the synchronous firing approach due to a reduced runtime for the analysis process. Fig. \ref{fig:Sync-Spd} displays the speedup (according to Amdahl's Law) obtained when using synchronous firing instead of non-synchronous firing for identical setups, as well as the state space reduction factor.
When examining the E/S Ratio for the non-synchronous graphs, it is both expected and observed that the ratio slightly increases as the number of services increases. When more applicable exploits are used during the generation process, the number of permutations increases, which corresponds with the growing number of states and edges. However, the increase in the number of services also increases the relation between states and the new permutations.
@ -242,7 +242,8 @@ When comparing the E/S Ratio for the non-synchronous graphs to the E/S Ratio for
\begin{figure}[htp]
\centering
\includegraphics[width=3.3in]{"./images/schri8.png"}
\caption{Speedup (Amdahl's) Obtained When Using Synchronous Firing}
\includegraphics[width=3.3in]{"./images/schri9.png"}
\caption{Speedup (Amdahl's) and State Space Reduction Factor Obtained When Using Synchronous Firing}
\label{fig:Sync-Spd}
\end{figure}
@ -273,23 +274,24 @@ When comparing the E/S Ratio for the non-synchronous graphs to the E/S Ratio for
\caption{Results for the Synchronous Firing Testing}
\label{table:S-Table}
\centering
\setlength\tabcolsep{4pt}
\begin{tabular}{|c|c|c|c|c|c|}
\setlength\tabcolsep{3pt}
\begin{tabular}{|c|c|c|c|c|c|c|}
\hline
\multicolumn{6}{|c|}{Synchronous Firing} \\ \hline
\multicolumn{7}{|c|}{Synchronous Firing} \\ \hline
\textbf{\begin{tabular}[c]{@{}c@{}}Services\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}States\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}Edges\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}Runtime\\(ms)\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}E/S\\Ratio\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}Speedup\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}State Space\\Reduction\end{tabular}}
\\ \hline
1 & 6277 & 3.46E04 & 1.48E04 & 5.507 & 5.87 \\ \hline
2 & 11653 & 6.94E04 & 2.92E04 & 5.954 & 3.96 \\ \hline
3 & 25317 & 1.60E05 & 6.68E04 & 6.321 & 2.76 \\ \hline
4 & 36949 & 2.42E05 & 1.02E05 & 6.538 & 2.47 \\ \hline
5 & 83134 & 5.71E05 & 2.44E05 & 6.868 & 2.42 \\ \hline
6 & 186679 & 1.35E06 & 5.82E05 & 7.209 & 2.72 \\ \hline
1 & 6277 & 3.46E04 & 1.48E04 & 5.507 & 5.87 & 5.89 \\ \hline
2 & 11653 & 6.94E04 & 2.92E04 & 5.954 & 3.96 & 3.98 \\ \hline
3 & 25317 & 1.60E05 & 6.68E04 & 6.321 & 2.76 & 2.86 \\ \hline
4 & 36949 & 2.42E05 & 1.02E05 & 6.538 & 2.47 & 2.53 \\ \hline
5 & 83134 & 5.71E05 & 2.44E05 & 6.868 & 2.42 & 2.53 \\ \hline
6 & 186679 & 1.35E06 & 5.82E05 & 7.209 & 2.72 & 2.27 \\ \hline
\end{tabular}
\end{table}
@ -353,29 +355,31 @@ Leveraging comprehensive services with synchronous firing enables users to signi
\begin{figure}
\centering
\includegraphics[width=3.3in]{"./images/schri9.png"}
\includegraphics[width=3.3in]{"./images/schri10.png"}
\includegraphics[width=3.3in]{"./images/schri11.png"}
\caption[Synchronous Firing on Runtime]{Bar Graph and Line Graph Representations of Synchronous Firing with Comprehensive Services on Runtime}
\label{fig:Comp-Sync-RT}
\end{figure}
\begin{figure}
\centering
\includegraphics[width=3.3in]{"./images/schri11.png"}
\includegraphics[width=3.3in]{"./images/schri12.png"}
\includegraphics[width=3.3in]{"./images/schri13.png"}
\caption{Bar Graph and Line Graph Representations of Synchronous Firing with Comprehensive Services on State Space}
\label{fig:Comp-Sync-State}
\end{figure}
\begin{figure}[htp]
\centering
\includegraphics[width=3.3in]{"./images/schri13.png"}
\includegraphics[width=3.3in]{"./images/schri14.png"}
\caption{Speedup (Amdahl's) Obtained When Using Synchronous Firing with Comprehensive Services}
\label{fig:Comp-Sync-Spd}
\end{figure}
\subsubsection{Results for the DMCA Takedown Environment} \label{sec:dmca_res}
Using the experimental setup described in Section \ref{sec:test-platform} on the platform described at the beginning of Section \ref{sec:test-platform}, results were collected in regards to the effect of synchronous firing on both state space and runtime. The graphs' edge to state ratio (E/S Ratio) was computed as well.
Using the experimental setup described in Section \ref{sec:test-platform} on the platform described at the beginning of Section \ref{sec:test-platform}, results were collected in regards to the effect of synchronous firing on both state space and runtime. The graphs' edge to state ratio (E/S Ratio) was computed as well. The respective tables are seen in Tables \ref{table:DMCA-NS-Table} and \ref{table:DMCA-S-Table}. The associated figure (Fig. \ref{fig:DMCA-States-Runtime}) shows a decrease in the number of states and a decrease in the runtime when synchronous firing is utilized. Since synchronous firing prevents the generation of unattainable states, there is no meaningful information loss that occurs in the graphs generated with the synchronous firing feature. Fig. \ref{fig:DMCA-Sync-Spd} displays the speedup (according to Amdahl's Law) obtained when using synchronous firing instead of non-synchronous firing for identical setups, as well as the state space reduction factor.
In this example, the synchronous firing approach mitigates the state space explosion by an increasing factor. With traditional attack and compliance graph generation, the uninstall process is required to be broken into individual steps, causing an unnecessarily large growth in the resulting graph. This is exacerbated due to the presence of multiple employees transmitting multiple pieces of illicit data, all of which must be captured individually. Using synchronous firing allows for better modeling of real systems, where features, processes, or tasks are often combined into single steps.
\begin{table}[htp]
\caption{Results for the Non-Synchronous Firing Testing}
@ -391,13 +395,13 @@ Using the experimental setup described in Section \ref{sec:test-platform} on the
& \textbf{\begin{tabular}[c]{@{}c@{}}Runtime\\ (ms)\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}E/S\\ Ratio\end{tabular}}
\\ \hline
A & 16 & 128 & 16.334 & 8.000 \\ \hline
B & 32 & 400 & 42.791 & 12.500 \\ \hline
C & 256 & 6144 & 1754.768 & 24.000 \\ \hline
AB & 512 & 13824 & 1942.736 & 27.000 \\ \hline
AC & 4096 & 147456 & 27962.078 & 36.000 \\ \hline
BC & 8192 & 319488 & 66394.759 & 39.000 \\ \hline
ABC & 131072 & 6684672 & 1940664.745 & 51.000 \\ \hline
A & 16 & 32 & 11.109 & 2.000 \\ \hline
B & 32 & 80 & 26.202 & 2.500 \\ \hline
C & 64 & 192 & 64.012 & 3.000 \\ \hline
AB & 512 & 1984 & 906.578 & 3.875 \\ \hline
AC & 1024 & 4032 & 2154.862 & 3.938 \\ \hline
BC & 2048 & 8128 & 5154.858 & 3.969 \\ \hline
ABC & 32768 & 131008 & 105675.709 & 3.998 \\ \hline
\end{tabular}
\end{table}
@ -405,27 +409,44 @@ Using the experimental setup described in Section \ref{sec:test-platform} on the
\caption{Results for the Synchronous Firing Testing}
\label{table:DMCA-S-Table}
\centering
\setlength\tabcolsep{4pt}
\begin{tabular}{|c|c|c|c|c|c|}
\setlength\tabcolsep{3pt}
\begin{tabular}{|c|c|c|c|c|c|c|}
\hline
\multicolumn{6}{|c|}{Synchronous Firing} \\ \hline
\multicolumn{7}{|c|}{Synchronous Firing} \\ \hline
\textbf{\begin{tabular}[c]{@{}c@{}}Employees \\ Present\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}States\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}Edges\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}Runtime\\(ms)\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}E/S\\Ratio\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}Speedup\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}State Space\\Reduction\end{tabular}}
\\ \hline
A & 2 & 1 & 36.975 & 2.000 & 2.0 \\ \hline
B & 2 & 1 & 520.277 & 2.000 & 2.0 \\ \hline
C & 0 & 0 & 0 & 0 & 0 \\ \hline
AB & 2 & 1 & 11239.546 & 2.000 & 2.0 \\ \hline
AC & 4096 & 147456 & 27962.078 & 36.000 & 2.0 \\ \hline
BC & 8192 & 319488 & 66394.759 & 39.000 & 2.0 \\ \hline
ABC & 131072 & 6684672 & 1940664.745 & 51.000 & 2.0 \\ \hline
A & 2 & 1 & 3.810 & 0.500 & 2.92 & 8.00 \\ \hline
B & 2 & 1 & 5.214 & 0.500 & 5.03 & 16.00 \\ \hline
C & 2 & 1 & 9.063 & 0.500 & 7.06 & 32.00 \\ \hline
AB & 4 & 4 & 67.560 & 1.000 & 13.42 & 128.00 \\ \hline
AC & 4 & 4 & 117.833 & 1.000 & 18.29 & 256.00 \\ \hline
BC & 4 & 4 & 108.544 & 1.000 & 47.49 & 512.00 \\ \hline
ABC & 8 & 12 & 705.016 & 1.500 & 149.89 & 4096.00 \\ \hline
\end{tabular}
\end{table}
\begin{figure}
\centering
\includegraphics[width=3.3in]{"./images/schri15.png"}
\includegraphics[width=3.3in]{"./images/schri16.png"}
\caption{Synchronous Firing on State Space and Runtime for the DMCA Takedown Environment}
\label{fig:DMCA-States-Runtime}
\end{figure}
\begin{figure}[htp]
\centering
\includegraphics[width=3.3in]{"./images/schri17.png"}
\includegraphics[width=3.3in]{"./images/schri18.png"}
\caption{Speedup (Amdahl's) and State Space Reduction Factor Obtained When Using Synchronous Firing}
\label{fig:DMCA-Sync-Spd}
\end{figure}
\section{Future Works} \label{sec:fw}
As seen and discussed in Section \ref{sec:inseparable}, when unattainable states are generated, there is a compounding effect. Each unattainable state is explored, and is likely to generate additional unattainable states. Future works include examining the effect of synchronous firing when more assets are utilized. It is hypothesized that the synchronous firing approach will lead to an increased runtime reduction and state space reduction due to the increased number of unattainable state permutations. This work had a limited number of assets, but generated upwards of 400,000 states due to repeated applications of the exploit set due to the services corresponding with the compliance graph. Future work could alter the scenario to have a greater number of assets, and a standard set of exploits more akin to an attack graph rather than a compliance graph. Other future works could include measuring the performance of synchronous firing when multiple groups of inseparable features are used. This work used a single group, but multiple groups be added to examine the performance of the feature.

View File

@ -46,47 +46,43 @@
\@writefile{toc}{\contentsline {subsection}{\numberline {A}Experimental Networks and Computing Platform}{5}{}\protected@file@percent }
\newlabel{sec:test-platform}{{A}{5}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {1}{\hl {Automobile Maintenance}}}{5}{}\protected@file@percent }
\citation{DMCA}
\citation{DMCA}
\citation{DMCA}
\citation{DMCA}
\citation{Piracy}
\citation{Piracy}
\citation{Piracy}
\citation{Piracy}
\citation{Android_Piracy}
\citation{Android_Piracy}
\citation{Android_Piracy}
\citation{Android_Piracy}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2}{\hl {DMCA Takedown}}}{6}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {B}Results and Analysis}{6}{}\protected@file@percent }
\@writefile{toc}{\contentsline {subsubsection}{\numberline {1}Results for the Theoretical \DIFaddbegin {\hl {Automobile }}\DIFaddend Environment}{6}{}\protected@file@percent }
\newlabel{sec:theo_res}{{1}{6}}
\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Results for the Non-Synchronous Firing Testing}}{6}{}\protected@file@percent }
\newlabel{table:NS-Table}{{1}{6}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2}Results for a Grouped \DIFaddbegin {\hl {Automobile }}\DIFaddend Environment}{6}{}\protected@file@percent }
\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Synchronous Firing on Runtime}}{7}{}\protected@file@percent }
\newlabel{fig:Sync-RT}{{4}{7}}
\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces Bar Graph and Line Graph Representations of Synchronous Firing on State Space}}{7}{}\protected@file@percent }
\newlabel{fig:Sync-State}{{5}{7}}
\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Speedup (Amdahl's) Obtained When Using Synchronous Firing}}{7}{}\protected@file@percent }
\@writefile{lot}{\contentsline {table}{\numberline {1}{\ignorespaces Results for the Non-Synchronous Firing Testing}}{7}{}\protected@file@percent }
\newlabel{table:NS-Table}{{1}{7}}
\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Speedup (Amdahl's) \DIFaddbeginFL {\hl {and State Space Reduction Factor }}\DIFaddendFL Obtained When Using Synchronous Firing}}{7}{}\protected@file@percent }
\newlabel{fig:Sync-Spd}{{6}{7}}
\@writefile{lot}{\contentsline {table}{\numberline {2}{\ignorespaces Results for the Synchronous Firing Testing}}{7}{}\protected@file@percent }
\newlabel{table:S-Table}{{2}{7}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {2}Results for a Grouped \DIFaddbegin {\hl {Automobile }}\DIFaddend Environment}{7}{}\protected@file@percent }
\@writefile{lot}{\contentsline {table}{\numberline {3}{\ignorespaces Results for the Comprehensive Services without Synchronous Firing}}{8}{}\protected@file@percent }
\newlabel{table:Non-Sync-Comp-Table}{{3}{8}}
\@writefile{lot}{\contentsline {table}{\numberline {4}{\ignorespaces Results for the Comprehensive Services with Synchronous Firing}}{8}{}\protected@file@percent }
\newlabel{table:Sync-Comp-Table}{{4}{8}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {3}{\hl {Results for the DMCA Takedown Environment}}}{8}{}\protected@file@percent }
\newlabel{sec:dmca_res}{{3}{8}}
\@writefile{toc}{\contentsline {section}{\numberline {VI}Future Works}{8}{}\protected@file@percent }
\newlabel{sec:fw}{{VI}{8}}
\@writefile{lot}{\contentsline {table}{\numberline {4}{\ignorespaces Results for the Comprehensive Services with Synchronous Firing}}{8}{}\protected@file@percent }
\newlabel{table:Sync-Comp-Table}{{4}{8}}
\@writefile{lof}{\contentsline {figure}{\numberline {7}{\ignorespaces Synchronous Firing on Runtime}}{8}{}\protected@file@percent }
\newlabel{fig:Comp-Sync-RT}{{7}{8}}
\@writefile{lof}{\contentsline {figure}{\numberline {8}{\ignorespaces Bar Graph and Line Graph Representations of Synchronous Firing with Comprehensive Services on State Space}}{8}{}\protected@file@percent }
\newlabel{fig:Comp-Sync-State}{{8}{8}}
\@writefile{lof}{\contentsline {figure}{\numberline {9}{\ignorespaces Speedup (Amdahl's) Obtained When Using Synchronous Firing with Comprehensive Services}}{8}{}\protected@file@percent }
\newlabel{fig:Comp-Sync-Spd}{{9}{8}}
\@writefile{lof}{\contentsline {figure}{\numberline {9}{\ignorespaces Speedup (Amdahl's) Obtained When Using Synchronous Firing with Comprehensive Services}}{9}{}\protected@file@percent }
\newlabel{fig:Comp-Sync-Spd}{{9}{9}}
\@writefile{lot}{\contentsline {table}{\numberline {5}{\ignorespaces {\hl {Results for the Non-Synchronous Firing Testing}}}}{9}{}\protected@file@percent }
\newlabel{table:DMCA-NS-Table}{{5}{9}}
\@writefile{toc}{\contentsline {section}{\numberline {VI}Future Works}{9}{}\protected@file@percent }
\newlabel{sec:fw}{{VI}{9}}
\@writefile{lot}{\contentsline {table}{\numberline {6}{\ignorespaces {\hl {Results for the Synchronous Firing Testing}}}}{9}{}\protected@file@percent }
\newlabel{table:DMCA-S-Table}{{6}{9}}
\@writefile{lof}{\contentsline {figure}{\numberline {10}{\ignorespaces {\hl {Synchronous Firing on State Space and Runtime for the DMCA Takedown Environment}}}}{9}{}\protected@file@percent }
\newlabel{fig:DMCA-States-Runtime}{{10}{9}}
\@writefile{lof}{\contentsline {figure}{\numberline {11}{\ignorespaces {\hl {Speedup (Amdahl's) and State Space Reduction Factor Obtained When Using Synchronous Firing}}}}{9}{}\protected@file@percent }
\newlabel{fig:DMCA-Sync-Spd}{{11}{9}}
\bibdata{Bibliography}
\bibcite{phillips_graph-based_1998}{1}
\bibcite{schneier_modeling_1999}{2}
@ -108,8 +104,8 @@
\bibcite{nichols_2018}{18}
\bibcite{DMCA}{19}
\bibcite{Piracy}{20}
\bibcite{Android_Piracy}{21}
\bibcite{AndroidPiracy}{21}
\bibstyle{ieeetr}
\@writefile{toc}{\contentsline {section}{\numberline {VII}Conclusion}{9}{}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{REFERENCES}{9}{}\protected@file@percent }
\gdef \@abspage@last{9}
\@writefile{toc}{\contentsline {section}{\numberline {VII}Conclusion}{10}{}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{REFERENCES}{10}{}\protected@file@percent }
\gdef \@abspage@last{10}

View File

@ -103,7 +103,7 @@ Y.~Kim, J.~Moon, S.~J. Cho, M.~Park, and S.~Han, ``Efficient identification of
International Conference on Innovative Mobile and Internet Services in
Ubiquitous Computing}, pp.~236--240, 2014.
\bibitem{Android_Piracy}
\bibitem{AndroidPiracy}
N.~Kumari and M.~Chen, ``Malware and piracy detection in android
applications,'' in {\em 2022 IEEE 5th International Conference on Multimedia
Information Processing and Retrieval (MIPR)}, pp.~306--311, 2022.

View File

@ -7,7 +7,7 @@ Warning--empty booktitle in centrality_based
Warning--empty publisher in TVA
You've used 21 entries,
1876 wiz_defined-function locations,
599 strings with 7568 characters,
599 strings with 7566 characters,
and the built_in function-call counts, 5065 in all, are:
= -- 493
> -- 204

View File

@ -1,8 +1,8 @@
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Arch Linux) (preloaded format=pdflatex 2023.2.27) 22 MAR 2023 18:23
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Arch Linux) (preloaded format=pdflatex 2023.2.27) 24 MAR 2023 17:54
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**diff.tex
**diff
(./diff.tex
LaTeX2e <2021-11-15> patch level 1
L3 programming layer <2022-04-10> (./ieeeoj.cls
@ -300,14 +300,14 @@ Package: letltxmacro 2019/12/03 v1.6 Let assignment for LaTeX macros (HO)
\DIFdelgraphicsbox=\box65
\DIFdelgraphicswidth=\skip61
\DIFdelgraphicsheight=\skip62
LaTeX Info: Redefining \DIFaddbegin on input line 69.
LaTeX Info: Redefining \DIFaddend on input line 70.
LaTeX Info: Redefining \DIFdelbegin on input line 71.
LaTeX Info: Redefining \DIFdelend on input line 72.
LaTeX Info: Redefining \DIFaddbeginFL on input line 77.
LaTeX Info: Redefining \DIFaddendFL on input line 78.
LaTeX Info: Redefining \DIFdelbeginFL on input line 79.
LaTeX Info: Redefining \DIFdelendFL on input line 80.
LaTeX Info: Redefining \DIFaddbegin on input line 68.
LaTeX Info: Redefining \DIFaddend on input line 69.
LaTeX Info: Redefining \DIFdelbegin on input line 70.
LaTeX Info: Redefining \DIFdelend on input line 71.
LaTeX Info: Redefining \DIFaddbeginFL on input line 76.
LaTeX Info: Redefining \DIFaddendFL on input line 77.
LaTeX Info: Redefining \DIFdelbeginFL on input line 78.
LaTeX Info: Redefining \DIFdelendFL on input line 79.
(/usr/share/texmf-dist/tex/latex/listings/listings.sty
\lst@mode=\count286
@ -341,20 +341,20 @@ File: l3backend-pdftex.def 2022-04-14 L3 backend support: PDF output (pdfTeX)
) (./diff.aux)
\openout1 = `diff.aux'.
LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 99.
LaTeX Font Info: ... okay on input line 99.
LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 99.
LaTeX Font Info: ... okay on input line 99.
LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 99.
LaTeX Font Info: ... okay on input line 99.
LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 99.
LaTeX Font Info: ... okay on input line 99.
LaTeX Font Info: Checking defaults for TS1/cmr/m/n on input line 99.
LaTeX Font Info: ... okay on input line 99.
LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 99.
LaTeX Font Info: ... okay on input line 99.
LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 99.
LaTeX Font Info: ... okay on input line 99.
LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 98.
LaTeX Font Info: ... okay on input line 98.
LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 98.
LaTeX Font Info: ... okay on input line 98.
LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 98.
LaTeX Font Info: ... okay on input line 98.
LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 98.
LaTeX Font Info: ... okay on input line 98.
LaTeX Font Info: Checking defaults for TS1/cmr/m/n on input line 98.
LaTeX Font Info: ... okay on input line 98.
LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 98.
LaTeX Font Info: ... okay on input line 98.
LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 98.
LaTeX Font Info: ... okay on input line 98.
(/usr/share/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
@ -379,40 +379,40 @@ File: epstopdf-sys.cfg 2010/07/13 v1.3 Configuration of (r)epstopdf for TeX Liv
e
))
\c@lstlisting=\count301
Package color Info: Redefining color ojcolor on input line 99.
Package color Info: Redefining color ojcolor on input line 98.
LaTeX Font Info: Trying to load font information for OT1+phv on input line 1
14.
13.
(/usr/share/texmf-dist/tex/latex/psnfss/ot1phv.fd
File: ot1phv.fd 2020/03/25 scalable font definitions for OT1/phv.
)
** ATTENTION: \authorrefmark is deprecated (line 134). Use \IEEEauthorrefmark i
** ATTENTION: \authorrefmark is deprecated (line 133). Use \IEEEauthorrefmark i
nstead.
LaTeX Font Info: Trying to load font information for U+msa on input line 134
LaTeX Font Info: Trying to load font information for U+msa on input line 133
.
(/usr/share/texmf-dist/tex/latex/amsfonts/umsa.fd
File: umsa.fd 2013/01/14 v3.01 AMS symbols A
)
LaTeX Font Info: Trying to load font information for U+msb on input line 134
LaTeX Font Info: Trying to load font information for U+msb on input line 133
.
(/usr/share/texmf-dist/tex/latex/amsfonts/umsb.fd
File: umsb.fd 2013/01/14 v3.01 AMS symbols B
)
** ATTENTION: \authorrefmark is deprecated (line 134). Use \IEEEauthorrefmark i
** ATTENTION: \authorrefmark is deprecated (line 133). Use \IEEEauthorrefmark i
nstead.
LaTeX Font Info: Calculating math sizes for size <6.6> on input line 134.
LaTeX Font Info: Calculating math sizes for size <6.6> on input line 133.
LaTeX Font Warning: Font shape `OT1/cmr/m/n' in size <3.3> not available
(Font) size <5> substituted on input line 134.
(Font) size <5> substituted on input line 133.
LaTeX Font Warning: Font shape `OML/cmm/m/it' in size <3.3> not available
(Font) size <5> substituted on input line 134.
(Font) size <5> substituted on input line 133.
LaTeX Font Warning: Font shape `OMS/cmsy/m/n' in size <3.3> not available
(Font) size <5> substituted on input line 134.
(Font) size <5> substituted on input line 133.
Underfull \vbox (badness 10000) has occurred while \output is active []
@ -423,7 +423,7 @@ Underfull \vbox (badness 10000) has occurred while \output is active []
<OJIM.png, id=1, 6269.4225pt x 2336.73pt>
File: OJIM.png Graphic file (type png)
<use OJIM.png>
Package pdftex.def Info: OJIM.png used on input line 146.
Package pdftex.def Info: OJIM.png used on input line 145.
(pdftex.def) Requested size: 75.09589pt x 28.0pt.
Underfull \vbox (badness 10000) has occurred while \output is active []
@ -439,7 +439,7 @@ Overfull \vbox (8.922pt too high) has occurred while \output is active []
<./ojim.png>]
LaTeX Font Info: Calculating math sizes for size <10.03749> on input line 15
3.
2.
Underfull \vbox (badness 2990) has occurred while \output is active []
@ -456,43 +456,39 @@ Overfull \vbox (11.2pt too high) has occurred while \output is active []
<./images/schri1.png, id=21, 1014.79124pt x 400.49625pt>
File: ./images/schri1.png Graphic file (type png)
<use ./images/schri1.png>
Package pdftex.def Info: ./images/schri1.png used on input line 171.
Package pdftex.def Info: ./images/schri1.png used on input line 170.
(pdftex.def) Requested size: 221.3985pt x 87.37611pt.
LaTeX Warning: Reference `fig:non-sync-ex' on page 3 undefined on input line 18
0.
LaTeX Font Info: Font shape `OT1/phv/b/it' in size <9> not available
(Font) Font shape `OT1/phv/b/sl' tried instead on input line 183.
(Font) Font shape `OT1/phv/b/sl' tried instead on input line 182.
LaTeX Font Info: Trying to load font information for OT1+pcr on input line 1
87.
86.
(/usr/share/texmf-dist/tex/latex/psnfss/ot1pcr.fd
File: ot1pcr.fd 2001/06/04 font definitions for OT1/pcr.
)
Underfull \hbox (badness 10000) in paragraph at lines 189--193
Underfull \hbox (badness 10000) in paragraph at lines 188--192
[]
Underfull \hbox (badness 6032) in paragraph at lines 189--193
Underfull \hbox (badness 6032) in paragraph at lines 188--192
[]\OT1/ptm/m/n/10.03749 where the ``$\OML/cmm/m/it/10 <$\OT1/ptm/m/n/10.03749 g
roup name$\OML/cmm/m/it/10 >$\OT1/ptm/m/n/10.03749 " iden-ti-fier and ``group"
[]
Underfull \hbox (badness 10000) in paragraph at lines 194--198
Underfull \hbox (badness 10000) in paragraph at lines 193--197
[]
Underfull \hbox (badness 10000) in paragraph at lines 199--205
Underfull \hbox (badness 10000) in paragraph at lines 198--204
[]
File: OJIM.png Graphic file (type png)
<use OJIM.png>
Package pdftex.def Info: OJIM.png used on input line 205.
Package pdftex.def Info: OJIM.png used on input line 204.
(pdftex.def) Requested size: 75.09589pt x 28.0pt.
Underfull \vbox (badness 10000) has occurred while \output is active []
@ -504,7 +500,7 @@ Overfull \vbox (8.45pt too high) has occurred while \output is active []
<./images/schri2.png, id=28, 551.05875pt x 720.6925pt>
File: ./images/schri2.png Graphic file (type png)
<use ./images/schri2.png>
Package pdftex.def Info: ./images/schri2.png used on input line 208.
Package pdftex.def Info: ./images/schri2.png used on input line 207.
(pdftex.def) Requested size: 180.67499pt x 236.2897pt.
Underfull \vbox (badness 10000) has occurred while \output is active []
@ -519,11 +515,11 @@ Overfull \vbox (11.2pt too high) has occurred while \output is active []
<./images/schri3.png, id=34, 489.83pt x 1053.9375pt>
File: ./images/schri3.png Graphic file (type png)
<use ./images/schri3.png>
Package pdftex.def Info: ./images/schri3.png used on input line 236.
Package pdftex.def Info: ./images/schri3.png used on input line 235.
(pdftex.def) Requested size: 244.9144pt x 526.96747pt.
File: OJIM.png Graphic file (type png)
<use OJIM.png>
Package pdftex.def Info: OJIM.png used on input line 275.
Package pdftex.def Info: OJIM.png used on input line 274.
(pdftex.def) Requested size: 75.09589pt x 28.0pt.
Underfull \vbox (badness 10000) has occurred while \output is active []
@ -532,229 +528,83 @@ Underfull \vbox (badness 10000) has occurred while \output is active []
Overfull \vbox (8.45pt too high) has occurred while \output is active []
[5 <./images/schri3.png>]
! Missing number, treated as zero.
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Missing number, treated as zero.
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Missing number, treated as zero.
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Missing number, treated as zero.
<to be read again>
\hbox
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
\hbox
l.291 }
?
! Package soul Error: Reconstruction failed.
See the soul package documentation for explanation.
Type H <return> for immediate help.
...
l.291 }
?
! Missing number, treated as zero.
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Missing number, treated as zero.
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Missing number, treated as zero.
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Missing number, treated as zero.
<to be read again>
\hbox
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
\hbox
l.291 }
?
! Package soul Error: Reconstruction failed.
See the soul package documentation for explanation.
Type H <return> for immediate help.
...
l.291 }
?
! Missing number, treated as zero.
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Missing number, treated as zero.
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Missing number, treated as zero.
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
}
l.291 }
?
! Missing number, treated as zero.
<to be read again>
\hbox
l.291 }
?
! Illegal unit of measure (pt inserted).
<to be read again>
\hbox
l.291 }
?
! Package soul Error: Reconstruction failed.
See the soul package documentation for explanation.
Type H <return> for immediate help.
...
l.291 }
?
Underfull \vbox (badness 10000) has occurred while \output is active []
<./images/schri4.png, id=39, 602.25pt x 238.491pt>
File: ./images/schri4.png Graphic file (type png)
<use ./images/schri4.png>
Package pdftex.def Info: ./images/schri4.png used on input line 322.
Package pdftex.def Info: ./images/schri4.png used on input line 321.
(pdftex.def) Requested size: 238.49121pt x 94.44125pt.
<./images/schri5.png, id=40, 549.69pt x 236.301pt>
File: ./images/schri5.png Graphic file (type png)
<use ./images/schri5.png>
Package pdftex.def Info: ./images/schri5.png used on input line 323.
Package pdftex.def Info: ./images/schri5.png used on input line 322.
(pdftex.def) Requested size: 238.49121pt x 102.51967pt.
<./images/schri6.png, id=41, 608.163pt x 223.38pt>
File: ./images/schri6.png Graphic file (type png)
<use ./images/schri6.png>
Package pdftex.def Info: ./images/schri6.png used on input line 330.
Package pdftex.def Info: ./images/schri6.png used on input line 329.
(pdftex.def) Requested size: 238.49121pt x 87.59843pt.
<./images/schri7.png, id=42, 532.827pt x 236.739pt>
File: ./images/schri7.png Graphic file (type png)
<use ./images/schri7.png>
Package pdftex.def Info: ./images/schri7.png used on input line 331.
Package pdftex.def Info: ./images/schri7.png used on input line 330.
(pdftex.def) Requested size: 238.49121pt x 105.96442pt.
<./images/schri8.png, id=43, 533.265pt x 236.301pt>
File: ./images/schri8.png Graphic file (type png)
<use ./images/schri8.png>
Package pdftex.def Info: ./images/schri8.png used on input line 338.
Package pdftex.def Info: ./images/schri8.png used on input line 337.
(pdftex.def) Requested size: 238.49121pt x 105.68184pt.
<./images/schri9.png, id=44, 535.893pt x 236.301pt>
File: ./images/schri9.png Graphic file (type png)
<use ./images/schri9.png>
Package pdftex.def Info: ./images/schri9.png used on input line 338.
(pdftex.def) Requested size: 238.49121pt x 105.15901pt.
Underfull \vbox (badness 10000) has occurred while \output is active []
Overfull \hbox (9.2912pt too wide) in paragraph at lines 337--339
[][][]
[]
! Missing number, treated as zero.
<to be read again>
{
l.373 \DIFdelendFL \DIFaddbeginFL \tabcolsep{
3pt}
?
! Illegal unit of measure (pt inserted).
<to be read again>
{
l.373 \DIFdelendFL \DIFaddbeginFL \tabcolsep{
3pt}
?
! Misplaced \noalign.
\hline ->\noalign
{\ifnum 0=`}\fi \hrule \@height \arrayrulewidth \futurelet...
l.375 \DIFaddendFL \hline
?
! You can't use `\hrule' here except with leaders.
\hline ->\noalign {\ifnum 0=`}\fi \hrule
\@height \arrayrulewidth \futurelet...
l.375 \DIFaddendFL \hline
?
! Missing number, treated as zero.
<to be read again>
\futurelet
l.375 \DIFaddendFL \hline
?
! Illegal unit of measure (pt inserted).
<to be read again>
\futurelet
l.375 \DIFaddendFL \hline
?
! Misplaced \omit.
\multispan ->\omit
\@multispan
l.377 ... \multicolumn{7}{|c|}{Synchronous Firing}
\DIFaddendFL \\ \hline
?
Overfull \vbox (11.34346pt too high) has occurred while \output is active []
@ -764,7 +614,7 @@ Overfull \vbox (11.2pt too high) has occurred while \output is active []
[6]
File: OJIM.png Graphic file (type png)
<use OJIM.png>
Package pdftex.def Info: OJIM.png used on input line 398.
Package pdftex.def Info: OJIM.png used on input line 401.
(pdftex.def) Requested size: 75.09589pt x 28.0pt.
Underfull \vbox (badness 10000) has occurred while \output is active []
@ -773,43 +623,84 @@ Underfull \vbox (badness 10000) has occurred while \output is active []
Overfull \vbox (8.45pt too high) has occurred while \output is active []
[7 <./images/schri4.png> <./images/schri5.png> <./images/schri6.png> <./images
/schri7.png> <./images/schri8.png>]
<./images/schri9.png, id=56, 602.25pt x 238.491pt>
File: ./images/schri9.png Graphic file (type png)
<use ./images/schri9.png>
Package pdftex.def Info: ./images/schri9.png used on input line 450.
(pdftex.def) Requested size: 238.49121pt x 94.44125pt.
<./images/schri10.png, id=57, 549.69pt x 236.301pt>
/schri7.png> <./images/schri8.png> <./images/schri9.png>]
<./images/schri10.png, id=58, 602.25pt x 238.491pt>
File: ./images/schri10.png Graphic file (type png)
<use ./images/schri10.png>
Package pdftex.def Info: ./images/schri10.png used on input line 451.
(pdftex.def) Requested size: 238.49121pt x 102.51967pt.
<./images/schri11.png, id=58, 600.717pt x 230.607pt>
Package pdftex.def Info: ./images/schri10.png used on input line 457.
(pdftex.def) Requested size: 238.49121pt x 94.44125pt.
<./images/schri11.png, id=59, 560.421pt x 236.301pt>
File: ./images/schri11.png Graphic file (type png)
<use ./images/schri11.png>
Package pdftex.def Info: ./images/schri11.png used on input line 458.
(pdftex.def) Requested size: 238.49121pt x 91.555pt.
<./images/schri12.png, id=59, 532.389pt x 236.739pt>
(pdftex.def) Requested size: 238.49121pt x 100.5618pt.
Overfull \hbox (9.2912pt too wide) in paragraph at lines 457--459
[][][]
[]
<./images/schri12.png, id=60, 600.717pt x 230.607pt>
File: ./images/schri12.png Graphic file (type png)
<use ./images/schri12.png>
Package pdftex.def Info: ./images/schri12.png used on input line 459.
(pdftex.def) Requested size: 238.49121pt x 106.05112pt.
<./images/schri13.png, id=60, 533.265pt x 236.301pt>
Package pdftex.def Info: ./images/schri12.png used on input line 467.
(pdftex.def) Requested size: 238.49121pt x 91.555pt.
<./images/schri13.png, id=61, 542.463pt x 236.739pt>
File: ./images/schri13.png Graphic file (type png)
<use ./images/schri13.png>
Package pdftex.def Info: ./images/schri13.png used on input line 466.
(pdftex.def) Requested size: 238.49121pt x 105.68184pt.
Package pdftex.def Info: ./images/schri13.png used on input line 468.
(pdftex.def) Requested size: 238.49121pt x 104.08238pt.
Overfull \hbox (9.2912pt too wide) in paragraph at lines 467--469
[][][]
[]
<./images/schri14.png, id=62, 535.893pt x 236.301pt>
File: ./images/schri14.png Graphic file (type png)
<use ./images/schri14.png>
Package pdftex.def Info: ./images/schri14.png used on input line 477.
(pdftex.def) Requested size: 238.49121pt x 105.15901pt.
Overfull \hbox (9.2912pt too wide) in paragraph at lines 477--478
[][][]
[]
Overfull \vbox (11.34346pt too high) has occurred while \output is active []
Overfull \vbox (11.2pt too high) has occurred while \output is active []
[8 <./images/schri9.png> <./images/schri10.png> <./images/schri11.png> <./imag
es/schri12.png> <./images/schri13.png>]
Underfull \vbox (badness 2990) has occurred while \output is active []
[8 <./images/schri10.png> <./images/schri11.png> <./images/schri12.png> <./ima
ges/schri13.png>]
<./images/schri15.png, id=70, 542.463pt x 236.739pt>
File: ./images/schri15.png Graphic file (type png)
<use ./images/schri15.png>
Package pdftex.def Info: ./images/schri15.png used on input line 541.
(pdftex.def) Requested size: 238.49121pt x 104.08238pt.
<./images/schri16.png, id=71, 560.421pt x 236.301pt>
File: ./images/schri16.png Graphic file (type png)
<use ./images/schri16.png>
Package pdftex.def Info: ./images/schri16.png used on input line 542.
(pdftex.def) Requested size: 238.49121pt x 100.5618pt.
<./images/schri17.png, id=72, 536.112pt x 236.301pt>
File: ./images/schri17.png Graphic file (type png)
<use ./images/schri17.png>
Package pdftex.def Info: ./images/schri17.png used on input line 549.
(pdftex.def) Requested size: 238.49121pt x 105.11935pt.
<./images/schri18.png, id=73, 535.893pt x 236.301pt>
File: ./images/schri18.png Graphic file (type png)
<use ./images/schri18.png>
Package pdftex.def Info: ./images/schri18.png used on input line 550.
(pdftex.def) Requested size: 238.49121pt x 105.15901pt.
File: OJIM.png Graphic file (type png)
<use OJIM.png>
Package pdftex.def Info: OJIM.png used on input line 557.
(pdftex.def) Requested size: 75.09589pt x 28.0pt.
(./diff.bbl
Overfull \vbox (8.45pt too high) has occurred while \output is active []
[9 <./images/schri14.png> <./images/schri15.png> <./images/schri16.png> <./ima
ges/schri17.png> <./images/schri18.png>] (./diff.bbl
Underfull \hbox (badness 10000) in paragraph at lines 96--99
[]\OT1/ptm/m/n/8 ``H.r.2281 - Dig-i-tal Mil-len-nium Copy-right Act.''
[]
@ -825,34 +716,26 @@ Underfull \hbox (badness 10000) in paragraph at lines 96--99
[]
)
File: OJIM.png Graphic file (type png)
<use OJIM.png>
Package pdftex.def Info: OJIM.png used on input line 489.
(pdftex.def) Requested size: 75.09589pt x 28.0pt.
Underfull \vbox (badness 10000) has occurred while \output is active []
Overfull \vbox (11.34346pt too high) has occurred while \output is active []
Overfull \vbox (8.45pt too high) has occurred while \output is active []
Overfull \vbox (11.2pt too high) has occurred while \output is active []
[9]
[10]
(./diff.aux)
LaTeX Font Warning: Size substitutions with differences
(Font) up to 1.7pt have occurred.
LaTeX Warning: There were undefined references.
)
Here is how much of TeX's memory you used:
6176 strings out of 478238
96372 string characters out of 5850456
471532 words of memory out of 5000000
24288 multiletter control sequences out of 15000+600000
6219 strings out of 478238
97419 string characters out of 5850456
494397 words of memory out of 5000000
24326 multiletter control sequences out of 15000+600000
528709 words of font info for 142 fonts, out of 8000000 for 9000
1141 hyphenation exceptions out of 8191
55i,14n,62p,1447b,571s stack positions out of 5000i,500n,10000p,200000b,80000s
55i,17n,62p,1521b,598s stack positions out of 5000i,500n,10000p,200000b,80000s
{/usr/share/texmf-dist/fonts/enc/dvips/base/8r.enc}</usr/share/texmf-dist/fon
ts/type1/public/amsfonts/cm/cmmi10.pfb></usr/share/texmf-dist/fonts/type1/publi
c/amsfonts/cm/cmr10.pfb></usr/share/texmf-dist/fonts/type1/public/amsfonts/cm/c
@ -863,10 +746,10 @@ vetic/uhvb8a.pfb></usr/share/texmf-dist/fonts/type1/urw/helvetic/uhvbo8a.pfb></
usr/share/texmf-dist/fonts/type1/urw/helvetic/uhvr8a.pfb></usr/share/texmf-dist
/fonts/type1/urw/times/utmb8a.pfb></usr/share/texmf-dist/fonts/type1/urw/times/
utmr8a.pfb></usr/share/texmf-dist/fonts/type1/urw/times/utmri8a.pfb>
Output written on diff.pdf (9 pages, 2392386 bytes).
Output written on diff.pdf (10 pages, 2765790 bytes).
PDF statistics:
124 PDF objects out of 1000 (max. 8388607)
60 compressed objects within 1 object stream
137 PDF objects out of 1000 (max. 8388607)
62 compressed objects within 1 object stream
0 named destinations out of 1000 (max. 500000)
71 words of extra memory for PDF output out of 10000 (max. 10000000)
96 words of extra memory for PDF output out of 10000 (max. 10000000)

View File

@ -1,7 +1,7 @@
\documentclass{IEEEoj}
%DIF LATEXDIFF DIFFERENCE FILE
%DIF DEL ../Original Submission/Schrick-Noah_AG-CG-SyncFire.tex Mon Dec 12 09:02:11 2022
%DIF ADD Schrick-Noah_AG-CG-SyncFire_Revised.tex Wed Mar 22 18:17:56 2023
%DIF ADD Schrick-Noah_AG-CG-SyncFire_Revised.tex Fri Mar 24 17:47:38 2023
\usepackage{cite}
\usepackage{spverbatim}
\usepackage{amsmath,amssymb,amsfonts}
@ -19,11 +19,10 @@
\RequirePackage{color}\definecolor{RED}{rgb}{1,0,0}\definecolor{BLUE}{rgb}{0,0,1} %DIF PREAMBLE
%\providecommand{\DIFadd}[1]{{\protect\color{blue}\uwave{#1}}} %DIF PREAMBLE
%\providecommand{\DIFdel}[1]{{\protect\color{red}\sout{#1}}} %DIF PREAMBLE
%DIF SAFE PREAMBLE %DIF PREAMBLE
\usepackage{soulutf8}
\providecommand{\DIFadd}[1]{{\protect\hl{#1}}} %highlight
\providecommand{\DIFdel}[1]{} %do not show deleted
%DIF SAFE PREAMBLE %DIF PREAMBLE
\providecommand{\DIFaddbegin}{} %DIF PREAMBLE
\providecommand{\DIFaddend}{} %DIF PREAMBLE
\providecommand{\DIFdelbegin}{} %DIF PREAMBLE
@ -177,7 +176,7 @@ Post-processing is one option at removing the unattainable states. This process
Instead, a new feature called synchronous firing can be used to prevent the generation of these states. The goal of the synchronous firing feature is to prevent the generation of unattainable states, while incurring no greater computational cost. Section \ref{sec:implementing} will discuss the development of this feature, and Section \ref{sec:Results} will examine the results when using this feature in applicable networks.
\section{Implementing Synchronous Firing} \label{sec:implementing}
\DIFaddbegin \DIFadd{Synchronous exploit firing aims to eliminate the generation of infeasible states during the generation process, rather than needing an additional post-processing step. Using Fig. }\ref{fig:non-sync-ex} \DIFadd{as an example, the goal of synchronous firing is to only generate the 3 valid, unshaded nodes, rather than generate all 16 nodes since 13 of the nodes represent an impossibility where two cars are progressing through time at different rates. Synchronous firing is accomplished through new grouping keywords in the input exploit file, which propagate through the modified attack and compliance graph engine, and prevent the firing of exploits if they are part of a group where all members are not yet available to fire.
\DIFaddbegin \DIFadd{Synchronous exploit firing aims to eliminate the generation of infeasible states during the generation process, rather than needing an additional post-processing step. Using Fig. }\ref{fig:non-sync_ex} \DIFadd{as an example, the goal of synchronous firing is to only generate the 3 valid, unshaded nodes, rather than generate all 16 nodes since 13 of the nodes represent an impossibility where two cars are progressing through time at different rates. Synchronous firing is accomplished through new grouping keywords in the input exploit file, which propagate through the modified attack and compliance graph engine, and prevent the firing of exploits if they are part of a group where all members are not yet available to fire.
}\DIFaddend For the implementation of the synchronous firing feature, there were four primary changes and additions that were \DIFdelbegin \DIFdel{necessary}\DIFdelend \DIFaddbegin \DIFadd{required}\DIFaddend . The first is a change in the lexical analyzer, \DIFdelbegin \DIFdel{the }\DIFdelend \DIFaddbegin \DIFadd{which handles the model and exploit input. Users indicate features that should fire simultaneously in these input files, and the lexical analyzer is responsible for parsing and passing that information to the graph generator. The }\DIFaddend second involves multiple changes to PostgreSQL \DIFdelbegin \DIFdel{, the }\DIFdelend \DIFaddbegin \DIFadd{to support the storage of group features and information. The }\DIFaddend third is the implementation of compound operators \DIFdelbegin \DIFdel{, and lastly }\DIFdelend \DIFaddbegin \DIFadd{in RAGE, since enumeration of all exploits may not be possible, especially when modeling a system over time. The fourth }\DIFaddend is a change in the graph generation process\DIFaddbegin \DIFadd{, which checks to see if all exploits in a group are able to fire simultaneously before firing}\DIFaddend . The subsections in this Section describe these four alterations \DIFaddbegin \DIFadd{in greater detail}\DIFaddend .
\subsection{GNU Bison and Flex}
@ -281,23 +280,23 @@ The compliance checks are as follows:
\end{itemize}
\DIFaddbegin \subsubsection{\DIFadd{DMCA Takedown}}
\DIFadd{A second example of synchronous firing is illustrated through a DMCA Takedown for a fictitious organization \mbox{%DIFAUXCMD
\cite{DMCA}}\hskip0pt%DIFAUXCMD
. 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 using company resources. Detection and removal of illicit data, such as through means presented by the authors of \mbox{%DIFAUXCMD
\cite{Piracy} }\hskip0pt%DIFAUXCMD
for Windows or \mbox{%DIFAUXCMD
\cite{Android_Piracy} }\hskip0pt%DIFAUXCMD
for company-supplied Android mobile devices, can be incorporated into and represented by a compliance graph.
\DIFadd{A second example of synchronous firing is illustrated through a DMCA Takedown for a fictitious organization [19]%\mbox{%DIFAUXCMD
%\cite{DMCA}}\hskip0pt%DIFAUXCMD
. 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 %\mbox{%DIFAUXCMD
%\cite{Piracy} }\hskip0pt%DIFAUXCMD
[20] for Windows or %\mbox{%DIFAUXCMD
%\cite{AndroidPiracy} }\hskip0pt%DIFAUXCMD
[21] for company-supplied Android mobile devices, can be incorporated into and represented by a compliance graph.
}
\DIFadd{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.
\DIFadd{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}\DIFadd{. 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.
}
\DIFadd{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.}
@ -311,7 +310,7 @@ for company-supplied Android mobile devices, can be incorporated into and repres
\DIFaddend \subsection{Results and Analysis}
\subsubsection{Results for the Theoretical \DIFaddbegin \DIFadd{Automobile }\DIFaddend Environment} \label{sec:theo_res}
Using the experimental setup described in Section \ref{sec:test-platform} on the platform described at the beginning of Section \ref{sec:test-platform}, results were collected in regards to the effect of synchronous firing on both state space and runtime. The graphs' edge to state ratio (E/S Ratio) was computed as well. The inclusion of this ratio allows for a comparison to be drawn regarding the usage of the synchronous firing feature. Examining this ratio can provide additional insight on how the graph's underlying topological structures change when using or not using synchronous firing. The results can be seen in Figures \ref{fig:Sync-RT} and \ref{fig:Sync-State}. The respective tables are seen in Tables \ref{table:NS-Table} and \ref{table:S-Table}. Both figures show a decrease in the number of states and a decrease in the runtime when synchronous firing is utilized. Since synchronous firing prevents the generation of unattainable states, there is no meaningful information loss that occurs in the graphs generated with the synchronous firing feature. Since the resulting number of states was also reduced, there will be increased justification for the synchronous firing approach due to a reduced runtime for the analysis process. Fig. \ref{fig:Sync-Spd} displays the speedup (according to Amdahl's Law) obtained when using synchronous firing instead of non-synchronous firing for identical setups.
Using the experimental setup described in Section \ref{sec:test-platform} on the platform described at the beginning of Section \ref{sec:test-platform}, results were collected in regards to the effect of synchronous firing on both state space and runtime. The graphs' edge to state ratio (E/S Ratio) was computed as well. The inclusion of this ratio allows for a comparison to be drawn regarding the usage of the synchronous firing feature. Examining this ratio can provide additional insight on how the graph's underlying topological structures change when using or not using synchronous firing. The results can be seen in Figures \ref{fig:Sync-RT} and \ref{fig:Sync-State}. The respective tables are seen in Tables \ref{table:NS-Table} and \ref{table:S-Table}. Both figures show a decrease in the number of states and a decrease in the runtime when synchronous firing is utilized. Since synchronous firing prevents the generation of unattainable states, there is no meaningful information loss that occurs in the graphs generated with the synchronous firing feature. Since the resulting number of states was also reduced, there will be increased justification for the synchronous firing approach due to a reduced runtime for the analysis process. Fig. \ref{fig:Sync-Spd} displays the speedup (according to Amdahl's Law) obtained when using synchronous firing instead of non-synchronous firing for identical setups\DIFaddbegin \DIFadd{, as well as the state space reduction factor}\DIFaddend .
When examining the E/S Ratio for the non-synchronous graphs, it is both expected and observed that the ratio slightly increases as the number of services increases. When more applicable exploits are used during the generation process, the number of permutations increases, which corresponds with the growing number of states and edges. However, the increase in the number of services also increases the relation between states and the new permutations.
@ -336,7 +335,8 @@ When comparing the E/S Ratio for the non-synchronous graphs to the E/S Ratio for
\begin{figure}[htp]
\centering
\includegraphics[width=3.3in]{"./images/schri8.png"}
\caption{Speedup (Amdahl's) Obtained When Using Synchronous Firing}
\DIFaddbeginFL \includegraphics[width=3.3in]{"./images/schri9.png"}
\DIFaddendFL \caption{Speedup (Amdahl's) \DIFaddbeginFL \DIFaddFL{and State Space Reduction Factor }\DIFaddendFL Obtained When Using Synchronous Firing}
\label{fig:Sync-Spd}
\end{figure}
@ -367,23 +367,28 @@ When comparing the E/S Ratio for the non-synchronous graphs to the E/S Ratio for
\caption{Results for the Synchronous Firing Testing}
\label{table:S-Table}
\centering
\setlength\tabcolsep{4pt}
\begin{tabular}{|c|c|c|c|c|c|}
\hline
\multicolumn{6}{|c|}{Synchronous Firing} \\ \hline
\setlength\DIFdelbeginFL %DIFDELCMD < \tabcolsep{4pt}
%DIFDELCMD < \begin{tabular}{|c|c|c|c|c|c|}
%DIFDELCMD < %%%
\DIFdelendFL \DIFaddbeginFL \tabcolsep{3pt}
\begin{tabular}{|c|c|c|c|c|c|c|}
\DIFaddendFL \hline
\DIFdelbeginFL %DIFDELCMD < \multicolumn{6}{|c|}{Synchronous Firing} %%%
\DIFdelendFL \DIFaddbeginFL \multicolumn{7}{|c|}{Synchronous Firing} \DIFaddendFL \\ \hline
\textbf{\begin{tabular}[c]{@{}c@{}}Services\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}States\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}Edges\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}Runtime\\(ms)\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}E/S\\Ratio\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}Speedup\end{tabular}}
\\ \hline
1 & 6277 & 3.46E04 & 1.48E04 & 5.507 & 5.87 \\ \hline
2 & 11653 & 6.94E04 & 2.92E04 & 5.954 & 3.96 \\ \hline
3 & 25317 & 1.60E05 & 6.68E04 & 6.321 & 2.76 \\ \hline
4 & 36949 & 2.42E05 & 1.02E05 & 6.538 & 2.47 \\ \hline
5 & 83134 & 5.71E05 & 2.44E05 & 6.868 & 2.42 \\ \hline
6 & 186679 & 1.35E06 & 5.82E05 & 7.209 & 2.72 \\ \hline
\DIFaddbeginFL & \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{State Space}\\\DIFaddFL{Reduction}\end{tabular}}
\DIFaddendFL \\ \hline
1 & 6277 & 3.46E04 & 1.48E04 & 5.507 & 5.87 \DIFaddbeginFL & \DIFaddFL{5.89 }\DIFaddendFL \\ \hline
2 & 11653 & 6.94E04 & 2.92E04 & 5.954 & 3.96 \DIFaddbeginFL & \DIFaddFL{3.98 }\DIFaddendFL \\ \hline
3 & 25317 & 1.60E05 & 6.68E04 & 6.321 & 2.76 \DIFaddbeginFL & \DIFaddFL{2.86 }\DIFaddendFL \\ \hline
4 & 36949 & 2.42E05 & 1.02E05 & 6.538 & 2.47 \DIFaddbeginFL & \DIFaddFL{2.53 }\DIFaddendFL \\ \hline
5 & 83134 & 5.71E05 & 2.44E05 & 6.868 & 2.42 \DIFaddbeginFL & \DIFaddFL{2.53 }\DIFaddendFL \\ \hline
6 & 186679 & 1.35E06 & 5.82E05 & 7.209 & 2.72 \DIFaddbeginFL & \DIFaddFL{2.27 }\DIFaddendFL \\ \hline
\end{tabular}
\end{table}
@ -447,31 +452,105 @@ Leveraging comprehensive services with synchronous firing enables users to signi
\begin{figure}
\centering
\includegraphics[width=3.3in]{"./images/schri9.png"}
\includegraphics[width=3.3in]{"./images/schri10.png"}
\caption[Synchronous Firing on Runtime]{Bar Graph and Line Graph Representations of Synchronous Firing with Comprehensive Services on Runtime}
\DIFdelbeginFL %DIFDELCMD < \includegraphics[width=3.3in]{"./images/schri9.png"}
%DIFDELCMD < %%%
\DIFdelendFL \includegraphics[width=3.3in]{"./images/schri10.png"}
\DIFaddbeginFL \includegraphics[width=3.3in]{"./images/schri11.png"}
\DIFaddendFL \caption[Synchronous Firing on Runtime]{Bar Graph and Line Graph Representations of Synchronous Firing with Comprehensive Services on Runtime}
\label{fig:Comp-Sync-RT}
\end{figure}
\begin{figure}
\centering
\includegraphics[width=3.3in]{"./images/schri11.png"}
\includegraphics[width=3.3in]{"./images/schri12.png"}
\caption{Bar Graph and Line Graph Representations of Synchronous Firing with Comprehensive Services on State Space}
\DIFdelbeginFL %DIFDELCMD < \includegraphics[width=3.3in]{"./images/schri11.png"}
%DIFDELCMD < %%%
\DIFdelendFL \includegraphics[width=3.3in]{"./images/schri12.png"}
\DIFaddbeginFL \includegraphics[width=3.3in]{"./images/schri13.png"}
\DIFaddendFL \caption{Bar Graph and Line Graph Representations of Synchronous Firing with Comprehensive Services on State Space}
\label{fig:Comp-Sync-State}
\end{figure}
\begin{figure}[htp]
\centering
\includegraphics[width=3.3in]{"./images/schri13.png"}
\caption{Speedup (Amdahl's) Obtained When Using Synchronous Firing with Comprehensive Services}
\DIFdelbeginFL %DIFDELCMD < \includegraphics[width=3.3in]{"./images/schri13.png"}
%DIFDELCMD < %%%
\DIFdelendFL \DIFaddbeginFL \includegraphics[width=3.3in]{"./images/schri14.png"}
\DIFaddendFL \caption{Speedup (Amdahl's) Obtained When Using Synchronous Firing with Comprehensive Services}
\label{fig:Comp-Sync-Spd}
\end{figure}
\DIFaddbegin
\DIFaddbeginFL \end{figure}
\subsubsection{\DIFadd{Results for the DMCA Takedown Environment}} \label{sec:dmca_res}
\DIFadd{Using the experimental setup described in Section }\ref{sec:test-platform} \DIFadd{on the platform described at the beginning of Section }\ref{sec:test-platform}\DIFadd{, results were collected in regards to the effect of synchronous firing on both state space and runtime. The graphs' edge to state ratio (E/S Ratio) was computed as well.
}\DIFaddend
\DIFadd{Using the experimental setup described in Section }\ref{sec:test-platform} \DIFadd{on the platform described at the beginning of Section }\ref{sec:test-platform}\DIFadd{, results were collected in regards to the effect of synchronous firing on both state space and runtime. The graphs' edge to state ratio (E/S Ratio) was computed as well. The respective tables are seen in Tables }\ref{table:DMCA-NS-Table} \DIFadd{and }\ref{table:DMCA-S-Table}\DIFadd{. The associated figure (Fig. }\ref{fig:DMCA-States-Runtime}\DIFadd{) shows a decrease in the number of states and a decrease in the runtime when synchronous firing is utilized. Since synchronous firing prevents the generation of unattainable states, there is no meaningful information loss that occurs in the graphs generated with the synchronous firing feature. Fig. }\ref{fig:DMCA-Sync-Spd} \DIFadd{displays the speedup (according to Amdahl's Law) obtained when using synchronous firing instead of non-synchronous firing for identical setups, as well as the state space reduction factor.
}
\DIFadd{In this example, the synchronous firing approach mitigates the state space explosion by an increasing factor. With traditional attack and compliance graph generation, the uninstall process is required to be broken into individual steps, causing an unnecessarily large growth in the resulting graph. This is exacerbated due to the presence of multiple employees transmitting multiple pieces of illicit data, all of which must be captured individually. Using synchronous firing allows for better modeling of real systems, where features, processes, or tasks are often combined into single steps.
}
\begin{table}[htp]
\caption{\DIFaddFL{Results for the Non-Synchronous Firing Testing}}
\label{table:DMCA-NS-Table}
\centering
\setlength\tabcolsep{4pt}
\begin{tabular}{|c|c|c|c|c|}
\hline
\multicolumn{5}{|c|}{Non-Synchronous Firing} \\ \hline
\textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{Employees }\\ \DIFaddFL{Present}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{Number of }\\ \DIFaddFL{States}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{Number of }\\ \DIFaddFL{Edges}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{Runtime}\\ \DIFaddFL{(ms)}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{E/S}\\ \DIFaddFL{Ratio}\end{tabular}}
\\ \hline
\DIFaddFL{A }& \DIFaddFL{16 }& \DIFaddFL{32 }& \DIFaddFL{11.109 }& \DIFaddFL{2.000 }\\ \hline
\DIFaddFL{B }& \DIFaddFL{32 }& \DIFaddFL{80 }& \DIFaddFL{26.202 }& \DIFaddFL{2.500 }\\ \hline
\DIFaddFL{C }& \DIFaddFL{64 }& \DIFaddFL{192 }& \DIFaddFL{64.012 }& \DIFaddFL{3.000 }\\ \hline
\DIFaddFL{AB }& \DIFaddFL{512 }& \DIFaddFL{1984 }& \DIFaddFL{906.578 }& \DIFaddFL{3.875 }\\ \hline
\DIFaddFL{AC }& \DIFaddFL{1024 }& \DIFaddFL{4032 }& \DIFaddFL{2154.862 }& \DIFaddFL{3.938 }\\ \hline
\DIFaddFL{BC }& \DIFaddFL{2048 }& \DIFaddFL{8128 }& \DIFaddFL{5154.858 }& \DIFaddFL{3.969 }\\ \hline
\DIFaddFL{ABC }& \DIFaddFL{32768 }& \DIFaddFL{131008 }& \DIFaddFL{105675.709 }& \DIFaddFL{3.998 }\\ \hline
\end{tabular}
\end{table}
\begin{table}[htp]
\caption{\DIFaddFL{Results for the Synchronous Firing Testing}}
\label{table:DMCA-S-Table}
\centering
\setlength\tabcolsep{3pt}
\begin{tabular}{|c|c|c|c|c|c|c|}
\hline
\multicolumn{7}{|c|}{Synchronous Firing} \\ \hline
\textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{Employees }\\ \DIFaddFL{Present}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{States}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{Edges}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{Runtime}\\\DIFaddFL{(ms)}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{E/S}\\\DIFaddFL{Ratio}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{Speedup}\end{tabular}}
& \textbf{\begin{tabular}[c]{@{}c@{}}\DIFaddFL{State Space}\\\DIFaddFL{Reduction}\end{tabular}}
\\ \hline
\DIFaddFL{A }& \DIFaddFL{2 }& \DIFaddFL{1 }& \DIFaddFL{3.810 }& \DIFaddFL{0.500 }& \DIFaddFL{2.92 }& \DIFaddFL{8.00 }\\ \hline
\DIFaddFL{B }& \DIFaddFL{2 }& \DIFaddFL{1 }& \DIFaddFL{5.214 }& \DIFaddFL{0.500 }& \DIFaddFL{5.03 }& \DIFaddFL{16.00 }\\ \hline
\DIFaddFL{C }& \DIFaddFL{2 }& \DIFaddFL{1 }& \DIFaddFL{9.063 }& \DIFaddFL{0.500 }& \DIFaddFL{7.06 }& \DIFaddFL{32.00 }\\ \hline
\DIFaddFL{AB }& \DIFaddFL{4 }& \DIFaddFL{4 }& \DIFaddFL{67.560 }& \DIFaddFL{1.000 }& \DIFaddFL{13.42 }& \DIFaddFL{128.00 }\\ \hline
\DIFaddFL{AC }& \DIFaddFL{4 }& \DIFaddFL{4 }& \DIFaddFL{117.833 }& \DIFaddFL{1.000 }& \DIFaddFL{18.29 }& \DIFaddFL{256.00 }\\ \hline
\DIFaddFL{BC }& \DIFaddFL{4 }& \DIFaddFL{4 }& \DIFaddFL{108.544 }& \DIFaddFL{1.000 }& \DIFaddFL{47.49 }& \DIFaddFL{512.00 }\\ \hline
\DIFaddFL{ABC }& \DIFaddFL{8 }& \DIFaddFL{12 }& \DIFaddFL{705.016 }& \DIFaddFL{1.500 }& \DIFaddFL{149.89 }& \DIFaddFL{4096.00 }\\ \hline
\end{tabular}
\end{table}
\begin{figure}
\centering
\includegraphics[width=3.3in]{"./images/schri15.png"}
\includegraphics[width=3.3in]{"./images/schri16.png"}
\caption{\DIFaddFL{Synchronous Firing on State Space and Runtime for the DMCA Takedown Environment}}
\label{fig:DMCA-States-Runtime}
\end{figure}
\begin{figure}[htp]
\centering
\includegraphics[width=3.3in]{"./images/schri17.png"}
\includegraphics[width=3.3in]{"./images/schri18.png"}
\caption{\DIFaddFL{Speedup (Amdahl's) and State Space Reduction Factor Obtained When Using Synchronous Firing}}
\label{fig:DMCA-Sync-Spd}
\DIFaddendFL \end{figure}
\section{Future Works} \label{sec:fw}
As seen and discussed in Section \ref{sec:inseparable}, when unattainable states are generated, there is a compounding effect. Each unattainable state is explored, and is likely to generate additional unattainable states. Future works include examining the effect of synchronous firing when more assets are utilized. It is hypothesized that the synchronous firing approach will lead to an increased runtime reduction and state space reduction due to the increased number of unattainable state permutations. This work had a limited number of assets, but generated upwards of 400,000 states due to repeated applications of the exploit set due to the services corresponding with the compliance graph. Future work could alter the scenario to have a greater number of assets, and a standard set of exploits more akin to an attack graph rather than a compliance graph. Other future works could include measuring the performance of synchronous firing when multiple groups of inseparable features are used. This work used a single group, but multiple groups be added to examine the performance of the feature.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 89 KiB

After

Width:  |  Height:  |  Size: 35 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 85 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 90 KiB

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 40 KiB

After

Width:  |  Height:  |  Size: 88 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 37 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 84 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 83 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 78 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 48 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 35 KiB

After

Width:  |  Height:  |  Size: 46 KiB

Binary file not shown.