Senserva Diagrams

This entry breaks down some Core Senserva items as an introduction.  My video covers these in more detail and I will continue to explain these in future blogs.

First, the Fearsome Foursome of Cloud security is our core.  All these items run in the Cloud, but the same code can run as a command line, or as a Raspberry Pi Service.  Its the power of small, tight design and code tied to the powerful nature of Microsoft's .NET.  We also build our UIs with Microsoft Blazor which has worked really well for us, we love it.

Senserva is a full solution. Customizable data readers, analyzers, the Senserva Security Cache, and a drill-down UI. No need to create queries or spend hours digging in data, Senserva data never leaves your tenant, it’s your data not Senserva’s.

Senserva is based on a Cache to make data de-dup and analysis fast, and low impact.  The cache can have a database backend, or no database, or it can be a distributed Redis Cache by design.  The Cache is key because we process and cross references so much data, but at the same time we keep costs low.

Next are some break downs of our components.

Senserva continually reviews all configuration updates, activities, connections and interactions. Reporting problems in both high level analytics and the details, only sending the data you need when you need it.

Senserva reads from any API or Log, finding difficult to get information so you do not have to. The first, and very key, step in automation.

Senserva’s user interface handles the KQL and drill-down graphs, so you do not need to. Unless you want to, then the UI works with you too.

Senserva predicts when problems may occur. We are not log dependent, instead we are API driven. We use logs because they give us great clues of what will happen again. This is a core and unique value.

Senserva data stays in your tenant. Senserva reads and writes via the Log Analytics Workspace, enabling full compatibility with what you already are using. Our we can write directly to your databases.

This is a very complex diagram but it's a great example, so I put it here, it was done with one of our MSSP partners and it shows our overall architecture, from data to UI.  This is just one example to start, we do a number of things like this. For Intune but for Azure Active Directory's Access and MFA for example, but more on that soon.