Re: [ossec-list] Unable to connect with agent

2017-05-12 Thread dan (ddp)
On Fri, May 12, 2017 at 4:45 AM, Akash Munjal wrote: > Hi dan, > > Thanks for the response. I tried this, but problem remains same. > If you have another method to solve this please share. > I would have to find out what the problem is first. You tried what? What were

Re: [ossec-list] TargetUserName is not mapped to an indexed field

2017-05-12 Thread dan (ddp)
On Fri, May 12, 2017 at 4:40 AM, AntonH wrote: > Hello, > > I'm using Wazuh and I don't know how to map TargetUserName to an indexed > field. > Security events are generated but the associated username is not mapped so > there is no way to search for or display the

Re: [ossec-list] Re: OSSEC Reporting Dump to CSV and reporting range setting

2017-05-12 Thread Pedro Sanchez
You could also take a look into "OSSEC Reportd" tool, you could aggregate stats for rules ids, groups, location etc..: - http://ossec-docs.readthedocs.io/en/latest/programs/ossec-reportd.html For CSV output you could

Re: [ossec-list] Unable to connect with agent

2017-05-12 Thread Akash Munjal
Hi dan, Thanks for the response. I tried this, but problem remains same. If you have another method to solve this please share. Best Regards, Akashdeep Munjal -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group

[ossec-list] TargetUserName is not mapped to an indexed field

2017-05-12 Thread AntonH
Hello, I'm using Wazuh and I don't know how to map *TargetUserName* to an indexed field. Security events are generated but the associated username is not mapped so there is no way to search for or display the culprit. The field marked yellow is not mapped or indexed.