\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={An Approach to a New Network Security Architecture of Nuclear and Research Facilities},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2019-01-15 (revised: 15 January 2019)}
\def\TheID{\makeatother }
\def\TheDate{2019-01-15}
\title{An Approach to a New Network Security Architecture of Nuclear and Research Facilities}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{A.B.  Ramadan}

             \author[2]{M.  Hefnawi}

\renewcommand\Authands{ and }

\date{\small \em Received: 12 December 2018 Accepted: 2 January 2019 Published: 15 January 2019}

\maketitle


\begin{abstract}
        


With the growth of information technology (IT) systems, network security is rapidly becoming a critical business concern. Due to the interconnectivity of IT systems, a comprehensive description of all of the key elements and relationships that make up an organization?s network security is needed, which can be referred as network security architecture. The value of this architecture is often questioned by organizations in terms of its practical application. This paper has presents a new approach to the network security architecture by using the Zachman Framework capabilities. The network security architecture of nuclear and academic facilities academic centers is discussed to show how a conceptual model can be applied to a real organization. This new approach makes any Local Area Network LAN more secure and more flexible than any conventional security procedures without affecting the performance of the LAN. Applying Zachman matrix provides the answers to what data assets the nuclear and research facilities controls, how they are used, and where they are located.

\end{abstract}


\keywords{computer network, LAN?s security, zachaman, information technology (IT), Information systems architecture (ISA).}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
he industry is moving toward more formal development and documentation of enterprise architectures based on Enterprise Architecture Frameworks. The term "architecture" has been used for many years within the information technology (IT) community to refer to various types of overviews that provide guidance to software systems and applications developers. The term is obviously a metaphor derived from the building trade \hyperref[b0]{[1,}\hyperref[b7]{8]}. Like a homeowner which is designing a home. Information technology managers work with an architect to provide an agreed upon architectural drawing of the enterprise's information systems and processes. This high-level Architectural drawing does not change with tactical decisions to deploy improved technology since it is simply built around a framework of business processes and the information that they need \hyperref[b1]{[2]}.\par
Today, there is a growing movement among both business managers and IT managers to use the term "enterprise architecture" to refer to a comprehensive description of all of the key elements and relationships that make up an organization. Based on this, enterprise information architecture provides a framework for reducing information system complexity and enabling enterprise information sharing. Since most enterprises have existing information systems, the architectural drawing provides the future state and facilitates the best possible strategy to remodel with the least amount of inconvenience to the business \hyperref[b0]{[1]}.\par
The rapidly growing interconnectivity of IT systems, and the convergence of their technology, renders these systems increasingly vulnerable to malicious attacks. Network attacks cause organizations several hours or days of downtime and serious breaches in data confidentiality and integrity. Depending on the level of the attack and the type of information that has been compromised, the consequences of network attacks vary in degree from mildly annoying to completely debilitating, and the cost of recovery from attacks can range from hundreds to millions of dollars \hyperref[b2]{[3]}.\par
This paper presents a network security architecture based on the Zachman Framework. The aim of this architecture is to organize the data, process, and technology around the points of view taken by various players instead of representing them as entirely separate entities. For this, we'll consider the Zachman Framework in more detail in Section 2. In Section 3, the relation between network security and the Zachman Framework is discussed. An example for designing security architecture of Nuclear and Research facilities based on the Zachman Framework is presented in this work. 
\section[{II.}]{II.} 
\section[{The Zachman Framework}]{The Zachman Framework}\par
The Zachman Framework for Information Systems Architecture (ISA), defined in 1987, is a logical construct to define and control the interfaces and integration of all components of a system. The framework of the Zachman model enables systematic capture of system specific information from the various perspectives with respect to system architecture \hyperref[b3]{[4]}. Table  {\ref 1} illustrates the Zachman model, tailored to support a network security system. 
\section[{Table 1: The Zachman Framework}]{Table 1: The Zachman Framework}\par
In this customization of the model, the system developers have an existing operational system in place. The rows at the top are the most abstract and are oriented toward very broad goals and plans. If we were building a house, this layer would describe the diagrams, pictures, and plans the architect would discuss with the owner. The next level is more specific, but still abstract. These are the diagrams that the architect would discuss with the contractor. In a similar way, the top level of the Zachman Framework, labeled "Scope," is focused on the concerns of senior executives. The second is focused on the slightly more detailed concerns of business managers. A lower level focuses on concerns that business and IS manager's work together on, and then, finally, on a detail that IS managers and developers work on \hyperref[b0]{[1]}. The columns in the Zachman framework represent different areas of interest for each perspective. The columns describe the dimensions of the systems development effort. The Zachman Framework has two very distinctive features that make it ideal for information modeling. The framework may be applied at any level of abstraction in the system development process, from a global enterprise, to a system, subsystem, or major module level. The framework also gives the modeler latitude in that any data representation technique can be used to model the inner workings of each cell. The system model becomes more implementation specific. However, the requirements traceability between layers can be maintained through backward references to upper layers of cells. This traceability is critical in security requirements engineering, where tracing a global access control requirement may translate into explicit setting of access controls on specific files or directories within an operating system. The framework provides taxonomy: that helps us understand the perspectives of various players in the development of an information system and the descriptions of the system that can be produced during its creation \hyperref[b3]{[4]}.\par
The model is frequently used as a framework during information systems activities to support the solicitation, identification and mapping of the following information re-engineering associated with an information system's \hyperref[b3]{[4]} such as goals, objectives, environment, customers served, time constraints, functional description, information architecture, supporting infrastructure. In short, the Zachman ISA can provide a consolidated view of a system, to whatever level of detail a modeler chooses. 
\section[{III. Network Security and The Zachman Framework}]{III. Network Security and The Zachman Framework}\par
The objective of network security architecture is to provide the conceptual design of the network security infrastructure, related security mechanisms, and related security policies and procedures. The security architecture links the components of the security infrastructure as one cohesive unit. The goal of this cohesive unit is to protect corporate information \hyperref[b2]{[3]}. The security architecture should be developed by both the network design and the IT security teams. It is typically integrated into the existing enterprise network and is dependent on the IT services that are offered through the net-work infrastructure. The access and security requirements of each IT service should be defined before the network is divided into modules with clearly identified trust levels. Each module can be treated separately and assigned a different security model. The goal is to have layers of security so that a "successful" intruder's access is constrained to a limited part of the network. Just as the bulkhead design in a ship can contain a leak so that the entire ship does not sink, the layered security design limits the damage a security breach has on the health of the entire network. In addition, the architecture should define common security services to be implemented across the network \hyperref[b6]{[7]}.\par
For security architecture modeling purposes, the first three levels of the perspective hierarchy (planner, owner, and designer) and the Network cell of the Builder's view are useful. They provide the consumer perspective of the system's end user, the perspective of the system "owner" or contracting entity, and the perspective of the designer, or systems engineer. In other words, the "as built" and used in daily operation perspective, the "as desired" operation perspective, and "as actually specified" perspective. The highest level, the Planner View, defines a clear and coordinated boundary (domain) of the system for the purposes of identifying the people, subsystems, and needs impacted by the system. The Owner's View captures the business and organizational relationships, and their external interfaces. It also documents sources of system requirements, including those derived from legacy systems. The Designer's View establishes and documents the security architectural design and provides a basis for system measurement. Finally, the Builder's View provides a detailed description of the design and methodology for monitoring and correcting system performance \hyperref[b1]{[2]}.\par
Similarly, the first three columns of the Zachman matrix (data, function, and network) provide the answers to what data assets the organization controls, how they are used and where they are located \hyperref[b4]{[5]}. As shown in Table  {\ref 1}, these are: Data: Each of the rows in this column address understanding of and dealing with an enterprise's data. This begins in Row One with a list of the security concerns of the enterprise and its directions and purposes. Row Two is a contiguous model of the security problems seen by the participants in the business. Also, relationships may be shown which themselves have attributes. Row Three provides more of an information based perspective of the network security, resolving the rules and relationships, along with relationships containing their own attributes. Indeed, attributes are more exhaustively defined and unique identifiers are specified. 
\section[{Function:}]{Function:}\par
The rows in the function column describe the process of translating the mission of the network security system of the enterprise into successively more detailed definitions of its operations. Where Row One is a list of the kinds of network security related activities the enterprise conducts, Row Two describes these activities in a contiguous model. Row Three portrays them in terms of data transforming processes, described exclusively in terms of the conversion of input data into output data.\par
Network: This column is concerned with the geographical distribution of the enterprise's activities. At the strategic level (Row One), this is simply a listing of the places where the enterprise does business. At Row Two, this becomes a more detailed communications chart, describing how the various locations interact with each other. Row Three produces the network architecture for data distribution, itemizing the special security policy for the enterprise. In Row Four, this distribution is translated into the kinds of computer and network facilities that are required in each location to force the security policy. 
\section[{IV.}]{IV.}\par
The Network Security of Nuclear and Academic Facilities\par
Nuclear and Research facilities, as major users of information and communication technology (especially Internet), also need security; however, because of their special structure and requirements, the traditional solutions and policies to limit access to the Internet are not effective for them. These institutions face concerns about the security of computing resources and information. The security problems in these environments are divided into two categories \hyperref[b2]{[3,}\hyperref[b5]{6]}: problems with research information and problems with administrative information. Although the corporate and research environments face common security problems they can't choose similar methods to solve them, because of their different structures. In a corporate environment, the natural place to draw a security perimeter is around the corporation itself. However, in a nuclear and research facilities research environment, it is very difficult to draw a perimeter surrounding all of the people who need to access information resources and only those people. This is mainly because of different types of information resources in these environments and also different users who want to access them. So if the security perimeter chosen is too big it includes untrusted people and if it is chosen too small it excludes some of the authorized people.\par
In addition, corporations can put serious limitations on the Internet connectivity in the name of security but research organizations simply cannot function under such limitations. First, trusted users need unrestricted and transparent access to Internet resources (including World Wide Web (WWW), FTP, Gopher, and electronic mail) located outside the security perimeter. Researchers rely on fingertip access to online library catalogs and bibliographies, preprints of papers, and other network resources supporting collaborative work. Second, trusted users need the unrestricted ability to publish and disseminate information to people outside the security perimeter via anonymous FTP, or WWW. This dissemination of research results and papers is critical to the research community. Third, the security perimeter must allow access to protected resources from trusted users located outside the security perimeter. An increasing number of users work at home or while traveling. Research collaborators may also need to enter the security perimeter from remote hosts. If we consider these centers as an enterprise, the security architecture of their network can be designed based on the ZachmanFramework. For the first four rows and first three columns of the framework the cells can be completed as described in the following sections: 
\section[{a) Planner's View}]{a) Planner's View}\par
An overall organizational policy would be implemented in the Planner's View. The first cell is the list of things important to the Nuclear and Research facilities. Research groups often need to maintain the privacy of their work, ideas for future research, or results of research in progress. Administrative organizations need to prevent leakage of student grades, personal contact information, and faculty and staff personnel records. Moreover, the cost of security compromises is high. A research group could lose its competitive edge, and administrative organizations could face legal proceedings for unauthorized information release. On the other hand, nuclear and research facilities and research institutions are ideal environments for hackers and intruders and many of them are physically located in these places and they are highly motivated to access and modify grades and other information. There are several reports of break-ins and deletion of data from educational institutions \hyperref[b2]{[3,}\hyperref[b5]{6]}.\par
The second cell in this row is the list of the processes important to the enterprise. This can also be divided into two categories: processes done by nuclear facilities, such as radiation monitoring and control; and research processes, such as conducting projects and disseminating information. The next cell (the network cell) is the locations of the entire research and nuclear facilities. 
\section[{b) Owner's View}]{b) Owner's View}\par
The next level down, the Owner's View, considers the groupings of data and means of access available to both internal and external users. For the first cell (data), we can see three categories of information in a university:\par
1. The information officially disseminated by the nuclear facilities (such as news and events articles). 2. The information gathered and used by network users. 3. The information not allowed to be publicly disseminated.\par
Based on the above categories, three types of function servers (second cell) may be proposed in the research facilities which are supervised by nuclear facilities:\par
1. Public servers, which are used to support information dissemination. 2. Experimental servers, which are used for researchers to develop and test their own software packages and protocols. 3. Trusted servers, which are used for administrative purposes or keeping confidential information. These servers are the places where functions occur with respect to the data \hyperref[b8]{[9]}.\par
The other requirement of a nuclear facilities environment is to let its trusted members access the resources of the network from outside of the security perimeter (e.g., from home or on trips). Another problem that causes serious trouble for the university is network viruses. These viruses are distributed through the network when users are accessing special sites. Proxy servers can be used to control this problem. Of course these proxy servers should be transparent. The network cell of the framework in this layer is shown in Figure \hyperref[fig_1]{2}. At the next level, the Designer's View, we introduce mechanisms to protect the network. To achieve the goals described in owner's view, the logical data model (first cell) of the proposed network security policy was designed based on seven basic rules: 1. Packets to or from the public servers are unrestricted if they are from authorized ports. The authorized port is the port that the special service is on. Of course, each public server should be protected itself. The server level security means to enforce stronger access controls on that level. 2. Packets to or from the experimental servers are unrestricted. These servers can be located outside of the security perimeter. 3. Packets to or from the authorized ports of trusted servers are allowed only from or to the authorized clients inside the security perimeter. 4. All of the outgoing packets are allowed to travel outside after port address translation. The incoming packets are allowed if they can be determined to be responses to outbound requests. 5. The packets to or from trusted users of hosts outside the security perimeter are allowed. 6. All of the requests from particular applications such as http should be passed through a proxy server. 7. All the packets to or from outside the security perimeter should be passed through the Intrusion Detection System (IDS).\par
Rule 1 is based on our need to support information dissemination in a research environment. Public servers must be separated from trusted hosts and protect them at the server level. Because of they may be compromised, so it should make a plan to recover them from information kept securely behind the security perimeter.\par
Rule 2 follows from recognition that researchers sometimes need to develop and test insecure software packages and protocols on the Internet. Of course they should be alerted that their server is not secure and their information may be corrupted.\par
Rule 3 is based on the fact that con fidential information must be protected. These servers are most important resources to be protected and therefore they should be put in a special secure zone.\par
Rule 4 follows from recognition that open network access is a necessary component of a research environment. On the other hand it is not allowed to any user to set up Internet servers without permission. The address translation prevents outside systems from accessing internal resources except those listed as public servers.\par
Rule 5 grants access to protected resources to users as they work from home or while traveling, as well as to collaborators located outside the research group.\par
Rule 6 is based on the need to block some Internet sites that contain viruses.\par
Rule 7 follows from recognition that the above rules should be monitored somehow. IDS can be a proper tool to monitor the network and check if there is any violation of proposed rules. The network cell is shown in Figure \hyperref[fig_1]{2}. Finally, the Builder's View describes how technology may be used to address the information processing needs identified in the previous rows. For network security purposes, mainly the network cell is needed. Generally, two ways can be proposed to implement the designed network: first, to use hardware firewalls and caches; and second, to use general purpose servers with proper software packages as cache, proxy, and firewall. In our case study in the nuclear facilities the proxy and cache is used as transparent server, and IPTABLES as the firewall for packet filtering, in which the different zones of the network were defined. Also Network Address is used as Translation of the IPTABLES for implementing the rules in design view. Of course each server in the network had also its own security rules and guards. For restricting access to special websites (mainly to avoid viruses) special software was utilized. SNORT is used as as IDS. The network cell is shown in Figure \hyperref[fig_3]{3}.\par
V. 
\section[{Conclusion}]{Conclusion}\par
Security architecture for computer network makes any Local Area Network LAN more secure and more flexible than any conventional security procedures without affecting the performance of the LAN. Creating Security architecture for nuclear and research facilities, it is possible to develop descriptive security architecture. It provides the "as built" and used in daily operation perspective, the "as desired" operation perspective, and "as actually specified" perspective. Similarly, Creating security architecture for nuclear and research facilities by the Zachman matrix (data, function, and network) provide the answers to what data assets the organization controls, how they are used, and where they are located. Nuclear facilities, as one of the major users of information and communication technology, present a good case study for applying the proposed architecture. The key point of the research is to design the network security architecture of these facilities based on a framework so it provides the consumer perspective of the system's end user, the perspective of the system "owner" or contracting entity, and the perspective of the designer or systems engineer simultaneously.  \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-4.png}
\caption{\label{fig_2}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 3}\end{figure}
 			\footnote{© 2019 Global Journals} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Hey]{b4}\label{b4} 	 		‘A different kind of life cycle: the Zachman Framework’.  		 			D C Hey 		.  		 \url{http://www.essentialstrategies.com/documents/zachman2000.pdf.2000}  	 	 		\textit{Essential Strategies Inc. Available}  		 	 
\bibitem[Mohajerani and Moeini ()]{b2}\label{b2} 	 		‘An approach to a new network security architecture for research environments’.  		 			M R Mohajerani 		,  		 			A Moeini 		.  	 	 		\textit{Proc. Of the 21st International SAFECOMP Conference},  				 (Of the 21st International SAFECOMP ConferenceItaly)  		2002.  	 
\bibitem[Delooze ()]{b1}\label{b1} 	 		‘Applying security to an enterprise using the Zachman Framework’.  		 			L L Delooze 		.  		 \url{http://www.sans.org/rr/paper.php?id=367}  	 	 		\textit{SANSPublications. Available}  		2001.  	 
\bibitem[Greenwald ()]{b5}\label{b5} 	 		‘Designing an research firewall: policy, practice and experience with SURF’.  		 			M Greenwald 		.  	 	 		\textit{IEEE Proceedings of 1966 Symposium of Network and Distributed Systems Security},  				1996.  	 
\bibitem[Ramachandran ()]{b6}\label{b6} 	 		\textit{Designing security architecture solutions},  		 			J Ramachandran 		.  		2002. Hoboken: John Wiley and Sons.  	 
\bibitem[Harmon ()]{b0}\label{b0} 	 		\textit{Developing an enterprise architecture},  		 			P Harmon 		.  		 \url{http://database.ittoolbox.com/documents/document.asp?i=2385}  		2002.  	 	 (Business Process Trends. Available at) 
\bibitem[Heaney ()]{b7}\label{b7} 	 		‘Information assurance for enterprise engineering’.  		 			J Heaney 		.  	 	 		\textit{Proc. of the 9th Conference on Pattern Language of Programs},  				 (of the 9th Conference on Pattern Language of ProgramsMonticello, Illinois)  		2002.  	 
\bibitem[Rosenthal and Coopers ()]{b8}\label{b8} 	 		‘Three-zone model to depict enterprise security \& technology architectures’.  		 			M Rosenthal 		,  		 			P Coopers 		.  	 	 		\textit{28th Annual Computer Security Conference},  				 (Washington D.C)  		2001.  	 
\bibitem[Henning and Corporation ()]{b3}\label{b3} 	 		‘Use of the Zachman architecture for security engineering’.  		 			R Henning 		,  		 			H Corporation 		.  	 	 		\textit{Proc. of the 19 th National Information Systems Security Conference},  				 (of the 19 th National Information Systems Security ConferenceBaltimore, MD)  		1996.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
