Good Cyber Hygiene

good cyber hygiene

Certainly everyone with any connection to information technology and networked devices is concerned with cybersecurity. However, often we just miss the basics – we do not practice good cyber hygiene. While not intended to be comprehensive or state-of-the-art, here are some security basics (or as some call it, “cyber hygiene”) that one should consider when developing devices that will be networked.

  1. Use a firewall and periodically maintain its configuration
  2. Change those vendor supplied defaults for usernames, passwords, identifiers, etc.
  3. Encrypt data at-rest and in transport. It’s just too easy to always protect data. Just do it.
  4. Use anti-virus software on development systems, test systems, and other systems that “touch” the product
  5. Install vendor supplied security patches
  6. Limit access to data – de-identify data early in the process.
  7. Obviously, use unique IDs for authentication and add something that is not obvious, e.g., 4 digit number added to first name and last name
  8. Restrict access to physical locations where data is retained
  9. Manage users, both incoming and termination, and monitor activity
  10. Periodically test security layers and re-assess acceptability
  11. Create policy in addition to procedure for security expectations for employees and sub-contractors
  12. Any cybersecurity expectations of our customers/users should be clearly communicated in product labeling

FDA has provided two guidance documents (find them on our Popular Resources page) and there are standards and technical reports that can be helpful as well.  Here are a few that we recommend:

Our partner Sherman Eagles provides periodic updates on standards and technical reports affecting medical device systems and software, and also provides a unique, one-of-a-kind concierge-level mentoring.  See our subscription options to start receiving Sherman’s updates today and engage with Sherman to raise your quality system bar!

About the author

Brian is a biomedical software engineer - whatever that is! Started writing machine code for the Intel 8080 in 1983. Still enjoys designing and developing code. But probably enjoys his garden more now and watching plants grow ... and grandkids grow!

SoftwareCPR Training Courses:

IEC 62304 and other Emerging Standards Impacting Medical Device Software

Being Agile & Yet Compliant

ISO 14971 SaMD Risk Management

Software Risk Management

Medical Device Cybersecurity

Software Verification

IEC 62366 Usability Process and Documentation

Contact Me

Fields marked with an * are required

Or just email training@softwarecpr.com for more info.

Corporate Office

15148 Springview St.
Tampa, FL 33624
USA
+1-781-721-2921
Partners located in the US (CA, FL, MA, MN, TX) and Canada.