Change Default Passwords
Plain English Translation
Organizations must change all default passwords on newly installed devices, software, and systems before deploying them into the production environment. Leaving vendor default credentials unchanged creates a severe vulnerability, as these passwords are often publicly known and easily exploited by attackers to gain unauthorized access.
Technical Implementation
Use the tabs below to select your organization size.
Required Actions (startup)
- Identify all network devices, routers, and firewalls.
- Manually log in and change all default administrative passwords to strong, unique passwords.
Required Actions (scaleup)
- Maintain a secure password manager to store administrative credentials.
- Implement internal hardening checklists that require password changes before device deployment.
- Regularly audit systems for default credentials using automated tools.
Required Actions (enterprise)
- Automate device provisioning and configuration management to enforce password changes.
- Use centralized identity and access management for device administration where supported.
- Employ automated vulnerability scanners to detect default credentials continuously.
Default passwords are pre-configured credentials assigned by manufacturers so users can initially access a device. Organizations must change them because these passwords are widely known and publicly documented, making them an easy target for attackers seeking unauthorized access.
CyberSecure Canada Section 5.4.2.1(a) mandates that organizations implement secure configurations for all their devices by changing all default passwords. This is a critical baseline control to prevent unauthorized network intrusion.
You can prove compliance by providing documented internal hardening standards, configuration management evidence, and vulnerability scan results that demonstrate no systems are flagged for default credentials. Auditors may also request a live sample of device login configurations. Tools like WatchDog Security's Compliance Center can help map this control to required evidence (policies, scan reports, change records) and maintain an audit-ready trail of uploads and attestations.
Organizations can use automated vulnerability scanning tools that check for known vendor default credentials across the network. Regular penetration testing and a default credentials audit checklist also help identify missed devices. Tools like WatchDog Security's Vulnerability Management can ingest scanner findings, track remediation owners and due dates, and report MTTR for default-credential exposures.
Admin passwords for network infrastructure should be strong, unique, and securely stored in a centralized password manager with restricted access. For better security, organizations should integrate devices with centralized authentication services to avoid shared local admin accounts.
Yes, all connected devices, including embedded systems, printers, cameras, and IoT devices, fall under the secure device configuration requirements. Their default passwords must be changed before they are connected to the network.
After the initial default password change, privileged passwords should be rotated periodically according to your organization's password policy for privileged accounts and admin logins, or immediately if a compromise is suspected or an administrator leaves the organization.
If a device does not allow the default password to be changed, it poses a severe risk and should ideally be replaced. If replacement is not immediately possible, it must be strictly isolated on a segmented network behind a firewall, with access tightly controlled.
Changing default passwords is a fundamental requirement across almost all security frameworks, such as CIS Control 4.2, which emphasizes establishing and maintaining secure configurations by removing default credentials.
Organizations can enforce default password changes by incorporating mandatory credential updates into Mobile Device Management (MDM) enrollment profiles or Infrastructure as Code (IaC) provisioning scripts. This ensures no device goes live without meeting secure configuration standards.
Default credential risk often comes from incomplete inventories, unclear ownership, and inconsistent deployment steps. Tools like WatchDog Security's Asset Inventory can help identify and track in-scope devices, while WatchDog Security's Compliance Center can assign remediation tasks, record exceptions with approvals, and centralize evidence that default passwords were changed before production use.
Auditors typically look for a clear standard (hardening baseline), implementation proof (configuration change records), and validation proof (scan results showing no default credentials). Tools like WatchDog Security's Compliance Center can organize these artifacts per control, and WatchDog Security's Vulnerability Management can attach and track scanner findings and remediation status over time.
| Version | Date | Author | Description |
|---|---|---|---|
| 1.0.0 | 2026-02-24 | WatchDog Security GRC Team | Initial publication |