From 5187338f2838cb7b38e272564e425bd89e6bd1a1 Mon Sep 17 00:00:00 2001
From: iglocska <andras.iklody@gmail.com>
Date: Wed, 2 Nov 2022 11:38:04 +0100
Subject: [PATCH] chg: updates to firstcti22

---
 firstcti2022/content.tex | 33 ---------------------------------
 1 file changed, 33 deletions(-)

diff --git a/firstcti2022/content.tex b/firstcti2022/content.tex
index 76942b2..076e349 100644
--- a/firstcti2022/content.tex
+++ b/firstcti2022/content.tex
@@ -319,18 +319,6 @@ Basically the same strategy as the one used in MISP:
     \end{center}
 \end{frame}
 
-\begin{frame}
-\frametitle{Data sharing: Planned synchronisation strategies}
-Two synchronisation strategies:
-    \begin{enumerate}
-        \item \textbf{Standard}: Only fetch and save new records
-        \item \textbf{Trusted upstream source}: Remote Cerebrate acts as an authoritative instance
-    \end{enumerate}
-    \begin{center}
-        \includegraphics[width=0.7\linewidth]{pictures/brood-edit.png}
-    \end{center}
-\end{frame}
-
 \begin{frame}
 \frametitle{Managing local tools}
 Why would Cerebrate have integration with other tools?
@@ -409,27 +397,6 @@ There will inevitably be integration between local tools and Cerebrate. Why not
     \end{center}
 \end{frame}
 
-\begin{frame}
-\frametitle{Local tool interconnection via Cerebrate}
-    \begin{itemize}
-        \item Local tools can be \textbf{exposed} to other Cerebrate nodes
-        \item \textbf{Inter-connection requests} can be issued from one node to another
-        \item Following a 3-way handshake protocol, inter-connections can be:
-        \begin{itemize}
-            \item Issued
-            \item Accepted
-            \item Finalised
-        \end{itemize}
-    \end{itemize}
-\end{frame}
-
-\begin{frame}
-\frametitle{Local tool interconnection via Cerebrate}
-    \begin{center}
-        \includegraphics[width=0.40\linewidth]{pictures/guys-chatting.png}
-    \end{center}
-\end{frame}
-
 \begin{frame}
 \frametitle{MISP interconnection via Cerebrate}
     \begin{center}