Home > Misc > 10 Must-Do Security Checks To Prevent Virtual World Event Disruption

10 Must-Do Security Checks To Prevent Virtual World Event Disruption

November 13th, 2009

LockVirtual world event management is, in the large, similar to real life event management. You’ve got to make sure that guests and performers are lined up, that marketing and advertising is effective, and if it is a broadcast event, that the technical and support staff logistics have been completed. Security is a bit different in virtual world settings, and requires special handling in order to avoid enabling disruptions at your event. This post focuses on some specifics for Second Life™ security management; however, the principles are similar for other virtual world platforms.

Event Disruption Categories

  • Purposeful region crashes (exploiting a bug to cause the region to crash “on demand”)
  • Littering (leaving objects in inconvenient places, placing them out during an event, or moving them around in the way of the event)
  • Pollution (planting a particle generator that creates a spray of smoke, fog or distasteful imagery)
  • Disruptive chat or voice participation

Must-Do Security Checks

The good news is that through careful implementation of these 10 security checks, you can dramatically limit or eliminate most of these of disruptions.

  1. Make sure that there is always someone on hand during a major event who has Estate Manager privileges. Make sure this person understands how to use and interpret the “Top Colliders” and “Top Scripts” options on the Region/Estate Debug panel.
  2. Make sure that there is always someone on hand during a major event who has clearance to contact Linden Lab Concierge. The Concierge group provides 7 x 24 telephone support to region owners and any named representatives.  Concierge will only talk to you if you are the region owner, or if the region owner has submitted a ticket to name you as a person who should be permitted to talk to a Concierge.
  3. Restart the region about two hours before the event. This allows enough time to allow for a slow shutdown, and enough time to call Concierge in case the region does not come back up, with enough time for the systems folks to troubleshoot any issues.  Make sure to test all functions that you need for your event, including scripts, rezzing objects and any special capabilities, to be sure that the region started up in fully operational form.
  4. Make sure that you know where EVERY parcel is on your region, and DISABLE CREATE OBJECTS, OBJECT ENTRY and RUN SCRIPTS for “All Residents”.  These can be set to on for “Group”.  It might be worthwhile to redo this step very carefully. It is surprising how many times small parcels get missed when trying to tighten down security for the first time.
  5. Make sure that you know and trust everyone in the group that has permissions to create objects and run scripts.
  6. Make sure that areas on the boundary of your region also have Create Objects and Run Scripts disabled, to prevent particle generators on the boundary of your region from wafting particles onto your event area.  If your region is surrounded by water this is not necessary.
  7. Disable voice chat if you do not want attendees to be talking during the event. Note that if you want certain areas to have voice chat enabled, you can do so by creating a separate parcel (often the stage area of a performance space will be a separate parcel so that you can set security settings differently than the audience area).
  8. Staff to include people who can work with attendees, both to answer questions and monitor or coach disruptive attendees as needed.
  9. Clean up your region, removing all objects that were not created by someone you know, or that should not be present.
  10. If someone has managed to find a way to wriggle past your security settings (or perhaps you’ve missed  a parcel, or they found another loophole), remember that you can call Concierge 7 x 24 (you’ve got someone on hand with that privilege, right… see #2 above!).  PLEASE NOTE: If your event does not include a live broadcast component (ie. large base of current participants), Concierge may ask you to file a ticket, especially if they are very busy at the moment. However, it is worth calling in case of a severe disruption, as they may be able to dispatch help quickly to get your event back on its feet.

Hopefully this checklist will help your next event to be a smooth, uninterrupted and successful experience for all!

Categories: Misc Tags: , ,
  1. November 18th, 2009 at 17:11 | #1

    I need to learn more about the Region/Estate Debug panel.:( .. I would also stress using a separate group for your VIPs and Guests and a separate group for parcels.
    Also , have someone doublecheck permissions on major equipment before the event. Ive seen contest boards fly across sims, because “anyone can move” was checked

    Great Post ! 🙂

  2. November 18th, 2009 at 20:19 | #2

    Thanks Isis-O! Remembering to have separate groups and double-check permissions everywhere are great tips, especially where there are changes happening to the build on a regular basis.

  1. No trackbacks yet.
Comments are closed.