How to Excel in Community in 2018

[SamanthaO_isc2]

Earn the (ISC)² Excel badge for demonstrating excelling in engaging in the (ISC)² Community to advance our industry through the months of October and November.

To qualify, you must complete these 5 activities:

• Receive at least 3 kudos
• Give at least 5 kudos
• Create at least 3 replies (can include comments on blogs, too)
• Make at least 3 posts (meaning you need to start a brand new topic/thread in the Community)
• Tag at least 5 (ISC)² Community posts

Why Tagging?  Tagging posts in the Community helps others to find content quickly. A good way to tag an article is to think of other ways people may talk about the topic. Here’s an example – talking about a Chief Information Security Officer?  You might want to tag the post with “CISO” so other users can easily search for other articles related to this topic.

Why Kudos?  Kudos can have many meanings, but they work best when you want to show someone you read through their article, appreciate (or agree) with their insights, give a thank you for supplying the information, or if you just want to say “Job well done!”

Thank you for your commitment to Enrich. Enable. Excel. with us! Your participation helps peers and fellow (ISC)² members remain well-rounded and informed as cybersecurity professionals.

[bukoskey]

Okay rslade, I started with giving you a kudo for pointing out the obvious 🙂 ! Now I just need to find the time over the next 4 days and not let my day job and family life interfere with the pursuit of a badge.... 

[rslade]

"Now I just need to find the time over the next 4 days and not let my day job and family life interfere with the pursuit of a badge...."

That's the spirit!  Never let the real world interfere with your pursuit of a shiny digital novelty!

[JGomez]

What about isolating these devices on a dedicated protected VLAN or other isolated network from your non-medical devices?   This could help reduce your threat footprint.

[bukoskey]

Isolation might be an approach, but most hospitals run pretty flat networks, I would think we'd have a better chance of having the BioMeds server facing out to download the updates/patches, then transfer the downloads to a server on the network with the med devices that need the update/patch, or maybe the BioMeds has their own isolated vlan that they can access/have a gateway to the vendors/manufactures network to acquire the patches/updates, then the BioMeds can attached the device to this isolated network, perform the update and put it back into service. Especially since you don't want the device to be updated when it's in clinical mode anyway... Just a thought.