Hello, we found that, after enabling the Microsoft 365 Connector in SEM, we obtained a lot of new nodes for the different logs of M365, and some of those are not useful to monitor for us and just consume a node license. We think that the connector should be modified to permit the collection of just some of the logs that…
Currently, Juniper Mist Access Point (AP) will be sending all logs/statistics to Juniper Mist Marvis (AP Cloud Controller), however the logs and statistics can only be kept for 7 days. Juniper Mist Cloud Controller does not have the option to send syglog to external SIEM or SEM. Having an API call to get AP logs and…
The standard widgets supplied with the SEM dashboard are not fit for purpose. Many are limited to 10,000 events and give no indication of what timescale they cover. We are seeing over 1,200 EPS. So these widgets might max out in less than 10 seconds! The figures shown in the widgets are meaningless without some additional…
Currently, widgets cannot be customized to display custom time frames. If it is possible to display custom time frames, it is much clearer how many new events have occurred and what action needs to be taken.
Here is a link to the documentation that explains where the logs are kept and how to read them. https://enterprise.arcgis.com/en/server/latest/administer/windows/work-with-server-logs.htm
Cisco Duo is a common MFA application. SEM can ingest several other vendors' logs, but apparently not Duo (Verified with support on 5/17/24). I would like to see a connector developed for these logs. Duo has the format documented at Understanding Duo Authentication Proxy SIEM Logging.
I have the same suggestion or request for future feature. As the SEM Admin, I need a solution to build out widgets & dashboards and then have the ability to share them with other users.
We recently deployed Cisco FPR-1120 and were trying to add them to our SEM. There is no connector specifically for this platform to use. I worked with support and they had me set up the Generic Syslog in order to have the SEM start ingesting traffic. I also noticed that the PIX/IOS connector works somewhat, but it must be…
We are integrating with a CMDB and want to inventory the SEM agent ID from the client. It would be great if the ID were written to the config file or in the registry. The configuration file would be most cross platform compatible. Having to read through the log file to find the agent ID is not ideal.
It looks like you're new here. Sign in or register to get started.