I've raised your concerns with PM and Development for their consideration and clarified our current exclusions in the knowledge base article you've referenced.
Thank you for pointing out the error in the documentation.
Regarding updating how NPM works to better align with best practices. I've opened an internal bug case to track this request (FB104296), but unfortunately we have no immediate plans to change how this works. If there are other users who would like to see this, please post here so we can gauge the demand for this and prioritize appropriately.
Regarding updating how NPM works to better align with best practices. I've opened an internal bug case to track this request (FB104296), but unfortunately we have no immediate plans to change how this works.
Umm. Im not sure you understand. The request and susequent explanation is reguarding "what are the operating executables names used by NPM/APM?" Of the current product. ITs not a request to change the product nor even a request to document how your program internally operates nor coded, but to document your existing product on how it interacts with the operating system, particularly which executable binaries "filename.exe" that perform Disk I/O. If you change any of the excecutable names in any future bugfix or development then I would request you then state or document which changed.
I am only asking for executables that do Disk I/O that would be affected by a third party application, such as AntiVirus. But that is not limited to just AntiVirus. Certain Host Intrusion Prevention software require you specify what executable and port. Other Application "white listing" (such as Bit9) software only allow listed application binaries executables to run.
Since NPM & APM require full access into subnets to query/poll the monitored devices, firewalls have to be opened up (fairly wide open to do WMI). Most security minded profesionals will want to secure or lockdown those devices with access across the firewalls, especially those subnets that have access to sensitive data. Any malicious code or person obtaining access into the polling engine servers could use the poller as the beachhead (or jumppoint) into those systems with sensitive data.