Microsoft Security Copilot helps security and IT teams to protect organizations at the speed and scale of AI. It is available in a standalone experience or embedded into other Microsoft Security products.
N/A
SolarWinds Security Event Manager (SEM)
Score 8.0 out of 10
N/A
SolarWinds LEM is security information and event management (SIEM) software.
Microsoft Security Copilot is well-suited for environments where security teams face high alert volumes and need rapid triage. It is effective during active threat response, helping us establish timelines and suggest remediation steps quickly. Copilot also excels in executive reporting, generating clear summaries for leadership without much effort. Security Copilot is less effective outside of Microsoft's ecosystem because it doesn't integrate well with other products.
Solarwinds SEM is great for generating reports for investigation purposes. Once you set up the connectors you can walk away and the product runs without needing maintenance. It was however pretty difficult to create the reports and alerts when now starting out and it can be very intimidating for new users.
SolarWinds easily provides the much needed visibily into changes in an Active Directory (AD) environment. Email alerting can be configured to alert a team if an account is locked out, disabled by another users, or if users and/or computers accounts are created.
SolarWinds allowed a searchable audit feature. Microsoft Windows can be configured to log many different parts of a system, but search those logs can be difficult. SEM allows you to search for specific users or events.
I think this product can do much better in terms of static code analysis. I don't think it has the full bit of knowledge on various languages. If the product can improve on SaaS and also help with threat modeling, that should be a great addition.
Compared to other SIEMs, there are features that are missing. Machine learning, automatic event correlation, ability to correlate multiple sources together.
The UI is clunky, and the *New* event log analyzer page felt really disjointed from the rest of the product.
In my experience, the dashboards were almost unusable. They persisted across login per device, and even then they sometimes would reset and go back to the ''Getting Started'' look.
It is pretty likely that we will renew SEM when the time comes up. It is easy to use and maintain so there isn't much of a need to replace this product. It is also a pretty fair price for the capabilities provided by the SEM
It is easily accessible and provides a similar Copilot interface as other Microsoft services. The natural language processing allows users to interact with it in plain language which greatly reduces the learning curve. Theoretically, even non-technical users within a company could utilize the product to get data for reporting or analysis.
It is very good - but you get what you pay for. The intent is not for a Fortune 500 that needs more "heavy lifting" with SolarWinds Security Event Manager & for whom the price tag is not (much of) a consideration.
The quality of support can vary depending on whom you end up speaking with. I was fortunate enough to work with a support representative who was very familiar with the product. He had even authored some of the support documentation on the website. On the flip side, I had two other experiences where I was simply directed to online training material.
Microsoft Security Copilot is more orientated towards the work I do and business I work for which is Security in Azure or Microsoft Products. Comparing the products has minor differences unless given explicit scenarios. In general use all of the products can fit a need but Microsoft Security Copilot suits mine in my security role the best.
The compare well against the others - the pricing models for all but Splunk (free version) are based on EPS/TB consumed... the problem they pose is guesstimating the price tag per month. SolarWinds Security Event Manager gets around that.
Helps reduce time spent creating a baseline script.
Some errors get corrected but then get reintroduced while adding functionality.
I noticed that when using this for PowerShell it will sometimes have you install the module in the script without verifying if it is already installed. You must read the script before executing.
It saves a lot of time when we had issues trying to figure out where the user account lockout was coming from.
With it being an affordable SIEM, we are able to have the ability to do the actions associated with a SIEM and the advantages of not “breaking the bank account”.
