2022-11-02 09:11:29 +01:00
% DO NOT COMPILE THIS FILE DIRECTLY!
% This is included by the other .tex files.
\begin { frame} [t,plain]
\titlepage
\end { frame}
\begin { frame}
\frametitle { Plan for this session}
\begin { itemize}
\item MeliCERTes II
\item MISP community management hurdles
\item Cerebrate
\item Future plans
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { MeliCERTes II}
\begin { itemize}
\item MeliCERTes
\item Common tooling for CSIRTs
\item Cerebrate a central component of the new tooling
\item Takes care of:
\begin { itemize}
\item Contact management
\item Constituency lookup
\item Interconnection Orchestration
\item Tool orchestration
\item Sharing group distribution and management
\item Cryptographic key lookup
\end { itemize}
\end { itemize}
2022-11-02 12:12:00 +01:00
\vspace { 0.5em}
\begin { center}
\includegraphics [width=0.55\linewidth] { pictures/melicertes.png}
\end { center}
2022-11-02 09:11:29 +01:00
\end { frame}
\begin { frame}
\frametitle { Managing large communities is difficult}
\begin { itemize}
\item Our MISP communities started out small
\item Most communities acted as islands
\item Interconnecting communities came with its own problems
\begin { itemize}
\item Interconnection requests
2022-11-02 12:12:00 +01:00
\item Organisation management
2022-11-02 09:11:29 +01:00
\item Enrollment process
\end { itemize}
2022-11-02 12:12:00 +01:00
\item Finding and communicating with the right parties is difficult
2022-11-02 09:11:29 +01:00
\item Managing multiple MISP instances can be tedious
\end { itemize}
\end { frame}
2022-11-02 09:32:32 +01:00
\section { Let us take a step back and look at a use-case}
2022-11-02 09:11:29 +01:00
\begin { frame}
\frametitle { Some stats about one of our MISP instance: MISPPriv (1)}
\includegraphics [width=0.45\linewidth] { pictures/misppriv-usage.png}
\includegraphics [width=0.45\linewidth] { pictures/misppriv-user-org-stats.png}
\end { frame}
\begin { frame}
\frametitle { Some stats about one of our MISP instance: MISPPriv (2)}
\begin { center}
2022-11-02 09:32:32 +01:00
\includegraphics [width=1.0\linewidth] { pictures/bokeh_ new_ org.png}
2022-11-02 09:11:29 +01:00
\end { center}
\end { frame}
\begin { frame}
\frametitle { Issues we're trying to solve}
Rising number of communities is great!
\begin { itemize}
\item \textbf { Bridge the gap} between between communities
\item Sharing with peers that face \textbf { similar threats}
\item \textbf { Reuse} of TTPs across sectors
\item \textbf { Hybrid threats} How seemingly unrelated things may be interesting to correlate
\item \textbf { Spread the love} , as our field is ahead of several other sectors when it comes to information sharing
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Issues we're trying to solve}
However, broader and more diverse communities lead to more issues
\begin { itemize}
\item { Non-technical issues}
\begin { itemize}
\item Overwhelming amount of points of contacts
2022-11-02 11:38:09 +01:00
\item Sharing difficulties in terms of social interactions (e.g trust)
2022-11-02 09:11:29 +01:00
\end { itemize}
\end { itemize}
2022-11-02 11:38:09 +01:00
\vspace { 1em}
\begin { minipage} { 0.27\textwidth }
\includegraphics [scale=0.4] { pictures/firstcti-hastag.png}
\end { minipage}
\begin { minipage} { 0.6\textwidth }
{ \large greatly helps in that aspect!}
\end { minipage}
\end { frame}
2022-11-02 09:11:29 +01:00
2022-11-02 11:38:09 +01:00
\begin { frame}
\frametitle { Issues we're trying to solve}
2022-11-02 09:11:29 +01:00
\begin { itemize}
\item { Technical issues}
\begin { itemize}
\item Centralised identity management
\item Loads of UUIDs to manually process
\item Distribution list management is difficult across communities
\end { itemize}
\end { itemize}
\begin { center}
2022-11-02 12:12:00 +01:00
\includegraphics [width=1.0\linewidth] { pictures/org-circl.png}
2022-11-02 09:11:29 +01:00
\end { center}
\end { frame}
\begin { frame}
\frametitle { Issues we're trying to solve with Cerebrate}
2022-11-02 09:32:32 +01:00
\begin { itemize}
\item Constituencies of organisations
2022-11-02 09:11:29 +01:00
\begin { itemize}
2022-11-02 09:32:32 +01:00
\item Geographic \& sectorial
\item But also technical: CIDR blocks \& AS Numbers
2022-11-02 09:11:29 +01:00
\end { itemize}
2022-11-02 12:12:00 +01:00
\vspace { 0.5em}
2022-11-02 09:32:32 +01:00
\item Cryptographic key lookup for information signing
2022-11-02 09:11:29 +01:00
\begin { itemize}
2022-11-02 09:32:32 +01:00
\item MISP's protected event feature
\item Future: Protected Sharing groups?
2022-11-02 09:11:29 +01:00
\end { itemize}
2022-11-02 09:32:32 +01:00
\end { itemize}
2022-11-02 09:11:29 +01:00
\end { frame}
\begin { frame}
\frametitle { Issues we're trying to solve with Cerebrate}
\begin { itemize}
\item Customisable data model adaptable to each community
\begin { itemize}
\item Communities with an existing registry want to build on their data-set, rather than rebuild
\item Different types of concerns for different communtiies
\item Based on the sheer amount of different types of communities, \textbf { it's a must}
\end { itemize}
\item Sharing group management
\item Synchronisation and lookup system
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Our attempt at solving them: Cerebrate}
\begin { itemize}
\item Open source community management and orchestration tool
\end { itemize}
\begin { center}
\includegraphics [width=0.15\linewidth] { pictures/logo.png}
\linebreak
\includegraphics [width=0.99\linewidth] { pictures/cerebrate-github.png}
\end { center}
\begin { itemize}
\item Central tool for the \textbf { Melicertes 2 project} (Co-funded by the EU as a CEF project - SMART 2018/1024)
\item Rich \textbf { Contact Database}
\item Tightly coupled management system and companion for MISP (and other tools)
\begin { itemize}
\item Get in touch with us if you need help building integrations!
\end { itemize}
\item Planned as the primary MISP \textbf { fleet management} tool
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Goals and design}
\begin { itemize}
\item Goals: Simplicity, lightweight and open-source
\item Technologies used: PHP, cakephp4, BS5, ...
\begin { itemize}
\item (almost) the same as in MISP for easier \textbf { maintainability} and \textbf { code re-use}
\end { itemize}
\item IAM centric design
\begin { itemize}
\item Tightly integrated with Keycloak
\end { itemize}
\item Core functionalities: Auditing, API
\begin { itemize}
\item Strong auditing/traceability capabilities are a requirement for trust
\item Automation is key
\end { itemize}
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Goals and design}
\begin { itemize}
\item Built with tool integration in mind, acting as a contact database
\end { itemize}
\begin { center}
\includegraphics [width=0.85\linewidth] { pictures/misp-cerebrate.png} \\
MISP is able to ingest Organisations \& Sharing Groups in Cerebrate
\end { center}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's place in a typical CSIRT software stack}
\begin { center}
\includegraphics [width=0.42\linewidth] { pictures/software-stack.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database}
\begin { itemize}
\item Contact database for the CSIRT network
\begin { itemize}
\item Common contact fields such as \texttt { UUID} , \texttt { name} , \texttt { contact email address} , \texttt { nationality} , \texttt { URL} , ...
\end { itemize}
\end { itemize}
\begin { center}
\includegraphics [width=0.8\linewidth] { pictures/contact-database-1.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database}
\begin { center}
\includegraphics [width=0.99\linewidth] { pictures/contact-database-2.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database: Meta-fields}
\begin { itemize}
\item Flexible system to store additional information: \texttt { meta-fields} (KV-store)
\item These \texttt { meta-fields} are part of a larger structure called \texttt { meta-templates}
\item Support of multiple templates used by various entities out there
\begin { itemize}
\item FIRST Directory
2022-11-02 12:12:00 +01:00
\item ENISA CSIRT inventory
2022-11-02 09:11:29 +01:00
\item CSIRT Constituency (CIDR blocks, AS Numbers, ...)
\end { itemize}
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database: Meta-fields}
\begin { center}
\includegraphics [width=0.99\linewidth] { pictures/meta-fields-first.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database: Meta-fields}
\begin { center}
\includegraphics [width=0.99\linewidth] { pictures/meta-templates-first.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database: Meta-fields}
\begin { center}
\includegraphics [width=0.99\linewidth] { pictures/meta-template-repo.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database: Sharing group management}
\begin { itemize}
\item Easy way to \textbf { create} and \textbf { share} distribution lists
\item Allow sharing groups to be \textbf { reusable}
\item Circumvent limitations of traditional Threat Intelligence Sharing Platform
\begin { itemize}
\item The exchange of sharing groups on creation / modification rather than on data exchange
\item Avoids the duplication of similar sharing groups
\end { itemize}
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database: Sharing group management}
\begin { center}
\includegraphics [width=0.9\linewidth] { pictures/sharinggroup.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database: Identity and Signing}
\begin { itemize}
\item Cerebrate can act as a trusted contact database containing cryptographic keys (PGP, S/MIME)
\item Which can be used by other applications to sign and validate information
\begin { itemize}
2022-11-02 09:32:32 +01:00
\item See MISP's protected Event feature
2022-11-02 09:11:29 +01:00
\end { itemize}
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database: Identity and Signing}
\begin { center}
\includegraphics [width=0.95\linewidth] { pictures/pgp.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Cerebrate's contact database: Open Directory}
\begin { itemize}
\item Cerebrate can be configured to act as an \textbf { open} directory of contact information
\item Other tools (including other Cerebrate nodes) can use this directory
\item Allows for information and information source validation
\end { itemize}
\begin { center}
\includegraphics [width=0.8\linewidth] { pictures/open-directory.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Data sharing}
Basically the same strategy as the one used in MISP:
\begin { itemize}
\item \textbf { Connect} with other Cerebrate nodes
\item \textbf { Diagnose} connectivity issues
\item Remotely \textbf { browse} data of the other node
\item \textbf { Fetch and save} organisation, individual, sharing-group data
\end { itemize}
\end { frame}
\begin { frame}
2022-11-02 09:32:32 +01:00
\frametitle { Data sharing - Connected Cerebrate instances}
2022-11-02 09:11:29 +01:00
\begin { center}
\includegraphics [width=0.95\linewidth] { pictures/brood-index.png}
\end { center}
\end { frame}
\begin { frame}
2022-11-02 09:32:32 +01:00
\frametitle { Data sharing - Browsing a remote Cerebrate instance}
2022-11-02 09:11:29 +01:00
\begin { center}
\includegraphics [width=0.95\linewidth] { pictures/brood-view.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Managing local tools}
Why would Cerebrate have integration with other tools?
\begin { itemize}
\item To support information sharing, being able to validate information sources is crucial
\item Traditional information sharing software stacks have to have their own organisation database
\item Why re-invent the wheel everytime?
\end { itemize}
\begin { center}
\includegraphics [width=0.2\linewidth] { pictures/software-stack.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Managing local tools}
There will inevitably be integration between local tools and Cerebrate. Why not go a step further?
\begin { itemize}
2022-11-02 12:12:00 +01:00
\item Cerebrate exposes a modular system to { \bf manage these local tools}
2022-11-02 09:11:29 +01:00
\item Based on a configuration file, user interfaces can be created to visualise data and instruct local tools to perform operations
\end { itemize}
\begin { center}
2022-11-02 12:12:00 +01:00
\includegraphics [width=1.0\linewidth] { pictures/github-local-tool.png}
2022-11-02 09:11:29 +01:00
\end { center}
\end { frame}
\begin { frame}
\frametitle { Local tools: MISP Connector capabilities}
\begin { itemize}
\item \textbf { Configure} a MISP instances via server settings
\item \textbf { Fetch} Organisations \& Sharing Groups
\item \textbf { Diagnose} other connected MISP servers
\item \textbf { Manage} users, ...
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Local tool: MISP Connector capabilities}
\begin { center}
\includegraphics [width=0.97\linewidth] { pictures/localtool-view.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Local tool: MISP Connector capabilities}
Why do one when we can do many?
\begin { itemize}
\item Cerebrate can connect to multiple tools via its associated connector
\item Allowing local tool fleet management
\begin { itemize}
\item MISP fleet management!
\end { itemize}
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Local tool: MISP Fleet management}
\begin { center}
\includegraphics [width=0.97\linewidth] { pictures/localtools-index.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Local tool interconnection via Cerebrate}
\begin { itemize}
\item Cerebrate's main goal is to \textbf { ease community management}
\item Select which local tools are meant to be exposed to the community for requests
\item Open dialogues to community members to request tool-to-tool interconnections
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { Local tool interconnection via Cerebrate}
Cerebrate can leverage its access to local tool to reach out to tools from other Cerebrate nodes
\begin { center}
\includegraphics [width=0.85\linewidth] { pictures/tools-made-available.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { MISP interconnection via Cerebrate}
\begin { center}
\includegraphics [width=0.98\linewidth] { pictures/connection_ request.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { What else does Cerebrate have?}
\begin { itemize}
\item Mailing list management
\item ACL system
\item Inbox system
\begin { itemize}
\item Inter-connection requests, enrolment requests
\end { itemize}
\item Tagging
\item Update system
\item Audit logs
\item Open API
\end { itemize}
\end { frame}
\begin { frame}
\frametitle { What else does Cerebrate have?}
Cerebrate has \colorbox { black!90} { \color { white} \texttt { dark theme} } and \textbf { { \color { blue!70} m} { \color { red!70} o} { \color { purple!90} r} { \color { orange!70} e} } !
\linebreak
\begin { center}
\includegraphics [width=0.42\linewidth] { pictures/theme-1.png}
\includegraphics [width=0.42\linewidth] { pictures/theme-2.png}
\end { center}
\begin { center}
\includegraphics [width=0.42\linewidth] { pictures/theme-3.png}
\end { center}
\end { frame}
\begin { frame}
\frametitle { Current roadmap}
\begin { itemize}
\item Data signing / validation
\begin { itemize}
\item Community centric PKI
\item Enable data validation services for tools such as MISP
\end { itemize}
\item Integration with other tools
\begin { itemize}
\item Ticketing systems
\item Tighter Mailing list integration (Mailman)
\item Messaging App (Mattermost)
\end { itemize}
\end { itemize}
\end { frame}