25 Cybersecurity Bad Practices: More Than Just Bad Habits - Computer 2000

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.

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.

Now we’re on to our own recommendations of some common, bad cybersecurity practices that should be avoided:

  1. Use of Windows 7 without ESU or air-gaping
  2. No disaster recovery or incident response plan
  3. Not practicing disaster recovery or not utilizing incident response plans
  4. In workgroup environments, giving users file share access with admin credentials
  5. Not performing permissions audits quarterly, or more frequently
  6. Not monitoring for suspicious log-in activity
  7. Leaving SMBv1 enabled
  8. Not using a password manager to facilitate auditing, reduce password reuse, and enforce password strength
  9. Not forcing session timeouts
  10. Giving client business owners full admin access
  11. Not segmenting unmanaged BYOD to their own network or VLAN
  12. Not segmenting IoT devices to their own network or VLAN
  13. Not implementing physical access controls for server rooms/telco closets
  14. No documented security framework
  15. Not documenting and planning remediation for discovered vulnerabilities
  16. Not monitoring for and automatically disabling accounts that haven’t been used in more than 90 days
  17. Not implementing a principle of least-privilege approach to permissions
  18. Leaving Windows’ built-in administrator account enabled
  19. 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
  20. Assuming a traditional AV is enough to protect endpoints
  21. Not using an email security and filtering solution
  22. Not having external security audits of your internal processes
  23. Not performing quarterly or yearly penetration testing
  24. Leaving RDP ports open to the internet, because “hey, it’s free”
  25. Not disabling RDP in environments that do not need it

If this information is helpful to you read our blog for more interesting and useful content, tips and guidelines on similar topics. Contact the team of COMPUTER 2000 Bulgaria now if you have a specific question. Our specialists will be assisting you with your query.

Content curated by the team of COMPUTER 2000 on the bases of marketing materials provided by our partners.

Follow us to learn more

CONTACT US

Let’s walk through the journey of digital transformation together.

By clicking on the SEND button you agree to the processing of personal data. In accordance with our Privacy Policy

5 + 6 =