Sami Mokaddem 2022-11-02 11:38:45 +01:00
commit 71b31f5116
No known key found for this signature in database
GPG Key ID: 164C473F627A06FA
1 changed files with 0 additions and 33 deletions

View File

@ -329,18 +329,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?
@ -419,27 +407,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}