- Server operating system version
- Windows Server 2019
- Plesk version and microupdate number
- Obsidian (18.x)
Hi everyone!
I am currently hosting a basic website on Godaddy's Plesk for Windows hosting service. We have a Coalition Control security scan that regularly scans the site and one of the critical findings concerns the Microsoft Remote Procedure Call (RPC) service being active/available. I am trying to figure out if this is something can can be disabled, or at least restricted on the Plesk server. The scan reports multiple instances of the service running on our server's public IP address (same IP address but different port number for each instance).
Does anyone know if this is something that can be fixed within Plesk?
I have gone through the various settings and options in Plesk but I don't see anything that appears to be directly related to this service.
Below is the "risk evidence" our report provides which seems to show the service is up and running on our server.
{
"data.service.product": "Microsoft Windows RPC"
}
Any help would be greatly appreciated!
I am currently hosting a basic website on Godaddy's Plesk for Windows hosting service. We have a Coalition Control security scan that regularly scans the site and one of the critical findings concerns the Microsoft Remote Procedure Call (RPC) service being active/available. I am trying to figure out if this is something can can be disabled, or at least restricted on the Plesk server. The scan reports multiple instances of the service running on our server's public IP address (same IP address but different port number for each instance).
Does anyone know if this is something that can be fixed within Plesk?
I have gone through the various settings and options in Plesk but I don't see anything that appears to be directly related to this service.
Below is the "risk evidence" our report provides which seems to show the service is up and running on our server.
{
"data.service.product": "Microsoft Windows RPC"
}
Any help would be greatly appreciated!