Many companies use shared directories or files to allow different users to access the information and if necessary modify them.
When I am on customer site implementing new NetEye projects, it happens very often that there is the need to monitor the accesses on these shared files.
To satisfy this requirement it is necessary to enable the “Audit Object Access” in the group policy of the domain or of the machine itself.
Based on the different configurations, in fact, all the activities (listen, read or write) performed on these files can be monitored.
The results can later be viewed in the Event Viewer of NetEye and in particular all the logs are stored in the security container. In addition, by identifying the event id it is also possible to configure the Agent Safed that collects and send these logs to the NetEye syslog server that archives and indexes them.
Tobias Goller
NetEye Solution Architect at Würth Phoenix
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth Phoenix, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
Author
Latest posts by Tobias Goller
10. 07. 2023
Unified Monitoring
ntop News in the Next Release
27. 04. 2023
Anomaly Detection, Unified Monitoring
Alerting on Network Traffic Anomalies with ntopng
01. 03. 2023
NetEye
Enable DNS Caching on RedHat 8
Hi Tobias, I’m working on this solution but unfortunately Syslog View doesn’t send notifications.
Of course, it’s a really good repository to store audit events.
I’m trying a different way like enabling snmp trap on the server and manage the “Audit Object Access” with Trap Handler module in NetEye.
It works quite good!