Shows all insecure system services and protocols to verify that their usage is justified per configuration standards |
This query lists all potentially insecure services enabled on the managed endpoints and its output can be used to demonstrate your compliance with this section of PCI. Examples of services include remote Remote Access, remote execution (psexec or PowerShell), unnecessary IIS web servers and more. They might be needed for business purposes, but they are also commonly used by attackers to compromise endpoints and gain control over them.
Sign-up for Action1 Free Edition to streamline compliance efforts for your network of endpoints. Such as you can simplify assessments of 2.2.2.b: Insecure System Services and Protocols for your internal or external auditors, create instant or regular compliance reports that prove your compliance while reducing the costs. Action1 Endpoint Security Platform is entirely SaaS, with online web interface (no management tools to install) and it has zero cost for basic functionality. Running in the Cloud, Action1 discovers all of your endpoints within seconds and allows you to pass compliance audits and maintain continuous compliance with ease.
Respond to Threatsin Real-Time
Ask questions in plain English such as "list of installed software" or "all running processes".
Get answers instantly from live systems or subscribe to real-time alerts.
Related Alerts and Reports:
2.2.2.a: Enabled System Services and Protocols
Allows to inspect enabled system services and protocols to verify that only necessary services are enabled
2.2.3: Additional Security Features
Inspect configuration settings to verify that security features are implemented in insecure services and protocols
2.2.4.c: Common Security Parameters
Inspect the common security parameters to verify that they are set per security standards
2.2.5.a: Unnecessary Functionality is Removed
Inspect the configurations to verify that all unnecessary functionality is removed, such as drivers and features
Keywords: Shows all insecure system services and protocols to verify that their usage is justified per configuration standards,Action1 2.2.2.b: Insecure System Services and Protocols.
Find more information on 2.2.2.b: Insecure System Services and Protocols at Microsoft TechNet.