%% pi1_bare_conf.tex
%% V1.1
%% Nov 27, 2007
%% by Felix Freiling
%%
%% Changes:
%% V1.0 Nov 27, 2007   Initial version
%% V1.1 Feb 5, 2008    Enabled page numbers
%%
%% based on bare_conf.tex V1.3 by Michael Shell
%%
%% This is a skeleton file demonstrating the use of IEEEtran.cls
%% (requires IEEEtran.cls version 1.7 or later) for a paper 
%% in one of the conference seminars of PI1, University of Mannheim
%%
%% Support sites:
%% http://www.michaelshell.org/tex/ieeetran/
%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/
%% http://www.ieee.org/
%%
%% and for PI1:
%% http://pi1.informatik.uni-mannheim.de

% for final version:
\documentclass[twoside,a4paper]{IEEEtran}
% for submission:
%\documentclass[draftclsnofoot,onecolumn,conference,a4paper]{IEEEtran}
%
\usepackage{cite}
\ifCLASSINFOpdf
  \usepackage[pdftex]{graphicx}
  \DeclareGraphicsExtensions{.pdf,.jpeg,.png,.jpg}
\else
  \usepackage[dvips]{graphicx}
  \DeclareGraphicsExtensions{.eps}
\fi
%
% re-enable \thanks command
\IEEEoverridecommandlockouts{}
%
% ----------------------------------------------------------------------
\begin{document}
%
% paper title
% can use linebreaks \\ within to get better formatting as desired
\title{My Great PI1 Conference Seminar Paper\thanks{This paper was
    written as part of the conference seminar ``Insert Name of Seminar
    Here'' which was organized by the laboratory of dependable
    distributed systems at the University of Mannheim during
    winter term 2008.}}


% author names and affiliations
% use a multiple column layout for up to three different
% affiliations
\author{
  \IEEEauthorblockN{Homer Simpson\\}
  \IEEEauthorblockA{University of Mannheim}
}

\maketitle


\begin{abstract}
  % 
  The abstract goes here and can sound like this.
  Incident Response and Computer Forensics are two areas with similar
  goals but distinct process models. While in both cases the goal is
  to investigate computer security incidents and contain their
  effects, Incident Response focusses more on restoration of normal
  service and Computer Forensics on the provision of evidence that can
  be used in a court of law. In this paper we present a common model
  for both Incident Response and Computer Forensics processes which
  combines their advantages in a flexible way: It allows for a
  management oriented approach in digital investigations while
  retaining the possibility of a rigorous forensics investigation.
  % 
\end{abstract}



\section{Introduction}

This demo file is intended to serve as a ``starter file''
for IEEE conference papers produced under \LaTeX\ using
IEEEtran.cls version 1.7 and later.
I wish you the best of success.

Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.

\subsection{Subsection Heading Here}

Subsection text here.
Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.


\subsubsection{Subsubsection Heading Here}

Subsubsection text here.
Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.

Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.

Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.

Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.


% Example for a figure
\begin{figure}[t]
  \centering
  \includegraphics[width=2.5in]{myfigure}
  \caption{Simulation Results}
  \label{fig_sim}
\end{figure}

Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.

% Example for a table
\begin{table}[t]
  \caption{An Example of a Table}
  \label{table_example}
  \centering
  \begin{tabular}{|c||c|}
    \hline
    One & Two\\
    \hline
    Three & Four\\
    \hline
  \end{tabular}
\end{table}

Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.



\section{Conclusion}

The conclusion goes here.
Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.

Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.

Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.

Incident Response and Computer Forensics are two areas with similar
goals but distinct process models. While in both cases the goal is to
investigate computer security incidents and contain their effects,
Incident Response focusses more on restoration of normal service and
Computer Forensics on the provision of evidence that can be used in a
court of law. In this paper we present a common model for both
Incident Response and Computer Forensics processes which combines
their advantages in a flexible way: It allows for a management
oriented approach in digital investigations while retaining the
possibility of a rigorous forensics investigation.






% can use a bibliography generated by BibTeX as a .bbl file
% BibTeX documentation can be easily obtained at:
% http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/
% The IEEEtran BibTeX style support page is at:
% http://www.michaelshell.org/tex/ieeetran/bibtex/
%\bibliographystyle{IEEEtran}
% argument is your BibTeX string definitions and bibliography database(s)
%\bibliography{IEEEabrv,../bib/paper}
%
% <OR> manually copy in the resultant .bbl file
% set second argument of \begin to the number of references
% (used to reserve space for the reference number labels box)
\begin{thebibliography}{1}

\bibitem{IEEEhowto:kopka}
H.~Kopka and P.~W. Daly, \emph{A Guide to \LaTeX}, 3rd~ed.\hskip 1em plus
  0.5em minus 0.4em\relax Harlow, England: Addison-Wesley, 1999.

\end{thebibliography}


\end{document}


