Do not use vendor-supplied defaults for system passwords and other security parameters |
Malicious individuals (both external attackers and insiders) often use vendor default passwords and other vendor default settings to compromise systems, including endpoints. Such passwords and settings are published and distributed by hacker communities and can be obtained from public sources. The following subsections address different aspects of default settings and enable automatic assessment per PCI DSS requirements.
2.1: Change Vendor Defaults and Disable Default Accounts
Always change vendor-supplied defaults and remove or disable unnecessary default accounts
2.2: Configuration Standards and System Hardening
Develop configuration standards for all system components to address all known security vulnerabilities
2.3: Encrypt All Non-Console Administrative Access
String encryption for administrator access and disabling of non-secure remote login
2.4: Inventory of System Components
Maintain a list of hardware and software components for the CDE
Sign-up for Action1 Free Edition to streamline compliance efforts for your network of endpoints. Such as you can simplify assessments of PCI DSS: Requirement 2 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.
Find more information on PCI DSS: Requirement 2
at Microsoft TechNet.