Suppose a system administrator became aware of a service running on their server that both created a named pipe that allowed access by remote clients (e.g., ordinary domain users), and that had an exploitable vulnerability that could be triggered over that named pipe.
In this situation, the administrator may want to either prevent any remote clients from gaining access to that specific named pipe, or do audit logging of any users attempting to open that named pipe.
How could that administrator accomplish those goals?
Assume that the vulnerable service is a third-party binary, and the administrator cannot change it. Also assume that users must be able to access other named pipes on this system besides the vulnerable one. Ideally, a solution would involve configurable option(s) within Windows, but third party products that can provide a solution would suffice.