The CISA (Cybersecurity & Infrastructure Security Agency) recently started an initiative to create a catalogue of exceptionally risky cybersecurity bad practices. While this will be a welcome and very useful tool once it is complete, only two practices are currently listed. Since cybersecurity and business decisions can be time-sensitive, we wanted to expand on the CISA’s list. Our Head Sales and Marketing Nerd, Stefanie Hammond, is also covering the number one, cybersecurity-related business bad practice that managed services providers should be aware of—click here to read it.
We encourage you to read through all the cybersecurity and business bad practices regardless of what your role and responsibilities are within your organization. Most of them do not arise out of ill intentions but rather out of bad habits, or a lack of guidance and planning. It would be a worthwhile use of your organization’s time to make sure none of these bad practices are at play in your MSP business or your clients’ environments.
Cybersecurity bad practices
According to the CISA, the number one bad practice is the use of unsupported or end-of-life software—and they consider it to be “especially egregious in internet-accessible technologies.” Attempting to support and protect EOL hardware and software can be a challenge in some situations and impossible in others. Sometimes you’re left crossing your fingers and hoping that nothing breaks. This isn’t sustainable long-term, and it makes it difficult to deliver on a promise to offer your clients the best protection possible.
Use of known/fixed/default passwords or credentials is number two on the CISA’s list. We all know it’s important to change the default password on managed switches or other appliances, but are you verifying it? Make sure you have an audit process in place to ensure default credentials are not being left in place.
Now we’re on to our own recommendations of some common, bad cybersecurity practices that should be avoided:
- Use of Windows 7 without ESU or air-gaping
- No disaster recovery or incident response plan
- Not practicing disaster recovery or not utilizing incident response plans
- In workgroup environments, giving users file share access with admin credentials
- Not performing permissions audits quarterly, or more frequently
- Not monitoring for suspicious log-in activity
- Leaving SMBv1 enabled
- Not using a password manager to facilitate auditing, reduce password reuse, and enforce password strength
- Not forcing session timeouts
- Giving client business owners full admin access
- Not segmenting unmanaged BYOD to their own network or VLAN
- Not segmenting IoT devices to their own network or VLAN
- Not implementing physical access controls for server rooms/telco closets
- No documented security framework
- Not documenting and planning remediation for discovered vulnerabilities
- Not monitoring for and automatically disabling accounts that haven’t been used in more than 90 days
- Not implementing a principle of least-privilege approach to permissions
- Leaving Windows’ built-in administrator account enabled
- Using Windows Automatic Updates to handle patching instead of a dedicated solution, which creates a lack of visibility across an environment of current patch status
- Assuming a traditional AV is enough to protect endpoints
- Not using an email security and filtering solution
- Not having external security audits of your internal processes
- Not performing quarterly or yearly penetration testing
- Leaving RDP ports open to the internet, because “hey, it’s free”
- Not disabling RDP in environments that do not need it
The list of cybersecurity bad practices could go on, but we’re going to switch gears and encourage you to read more about the number one, business bad practice concerning cybersecurity that MSPs should avoid. If you would like to have a more in-depth conversation about any of the cybersecurity bad practices listed, please reach out via the contact information below.
Lewis Pope is the Head Security Nerd at N-able. You can follow him on
© 2021 N-able Solutions ULC and N-able Technologies Ltd. All rights reserved.
The N-able trademarks, service marks, and logos are the exclusive property of N-able Solutions ULC and N-able Technologies Ltd. All other trademarks are the property of their respective owners.
This document is provided for informational purposes only. Information and views expressed in this document may change and/or may not be applicable to you. N-able makes no warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information contained herein.