Members: Join   Log In
Conv Default conversation security update to BSG Hub - updated Mar 14
by Anonymous User on Mar 14, 2008 - 12:23 PM read 604 times
 

The BSG Collaboration Hub security has been changed to default to more secure internal communication.  This was done in an expedient manner to address the dramatic growth of online conversations.  While this is not how we ultimately want to handle secure internal communications, it was the quickest way to ensure externalizing communications is deliberate.  

All conversations Conversations created by BSG employees within the BSG Hub are now defaulted to be visible only to BSG personnel by the automatic addition of the BSGLock security tag (see example below).  If you want non-BSG users to view your conversation (e.g. customers), simply delete this tag to unlock the conversation.

In addition, the following adjustments were made:

  • Conversations aggregated from BSG employee bloggers ARE NOT tagged with BSGLock.
  • Conversations created by non-BSG employees receive no default tags.
  • Individuals can opt out of default tagging from their "Preferences" page.

Note: A conversation that's not secured either by:

  1. Applying a tag under the tag group "Lock this content for an audience or Interest Group?" (a padlock icon shown next to the tag),

    or by
  2. Posting in a "Private" Interest Group

... the conversation will be pushed out to the major search engines in order to improve the visibility of BSG on the Web (e.g. Google).  You can tell if a conversation is secure by the notice at the bottom of your conversation.  Additional information on conversation security can be found here.

BSGLock.JPG

(Click image to enlarge)
  • Conv Susan Scrupski  - dumbing down the financial crisis:  http://snurl.com/48rlb works for me.
    Rank_docent
    Ugh.
    Icon-thread a reply to Default conversation security update to BSG Hub - updated Mar 14
    by Susan Scrupski on Mar 14, 2008 - 12:23 PM read 40 times
     

    Guys, I understand the need to err on the side of caution, but this is probably not a good idea.  I predict our bloggers will not physically go in and unlock each public post.  Time-- everyone is pressed for time. 

    Isn't there a better way?


    Security
    • Conv Barbara McGill - Steve Elmore--"using Yammer to regain organizational awareness in a virtual office environment"
      Rank_member
      re: Ugh
      Icon-thread a reply to Ugh.
       Icon-thread in a conversation thread started here

      by Barbara McGill on Mar 14, 2008 - 12:23 PM read 35 times
       
      Maybe blogs shouldn't be locked while discussions should be. Is that too complicated? It seems to me blogs are things people want read outside the company while discussions are more for internal purposes.

      No current tags

    • Conv Brittain
      Rank_docent
      Of course there's a better way
      Icon-thread a reply to Ugh.
       Icon-thread in a conversation thread started here

      by Brittain on Mar 14, 2008 - 12:23 PM read 37 times
       

      Tonight we're releasing a patch that'll more granularly control this policy:

      • we'll be able to auto-tag based on group memberships
      • we'll be able to include/exclude the bloggers from auto-tagging
      • individuals will be able to opt out of auto-tagging.  We won't be publishing documentation on how this is done ... it's a mini-test: if you're savvy enough to find the opt-out, then you're savvy enough not to publish company secrets to the world.  :- )

       

       


      No current tags

  • Conv BSG Hub security
    Icon-thread a reply to Default conversation security update to BSG Hub - updated Mar 14
    by Anonymous User on Mar 16, 2008 - 01:20 PM read 26 times
     

    In the financial services world, the rule is that security isn't always convenient, but is very necessary. Our job is to provide the best customer experience around tight security, not to reduce security. As we begin to try and get subscriptions to e.laborate at Merrill Lynch and Fortune 500 firms, all of us have to be make sure we are protecting the privacy of our clients information. If a customer at the firm can accidentally display confidential information to the public, we will lose that customer's trust very quickly. And, it's never the customer's fault. So, while we may not be perfect, we should be doing everything to make it easier to protect our client's information.

    Jeff - Would it be less secure if we want our customers to view conversations within the BSG hub, we give them a userid and invite them to that specific group as opposed to removing the lock (either have them self-register or do it for them)? The conversation would have to have a specific lock as opposed to just "bsglock". Then they are using e.laborate in a more secure way. I realize that this is a bigger discussion, but just want to lob this idea out....

Featured

nGen Collaboration v7.1
Project CBS
Project LIM
Project ITM
Wiki Archive
Concours Archive

Author Profile

Moderator

Subscribe

Feed for nGenera Community:
Feed_small Public Secure_feed_16 Secure

Why subscribe? What is RSS?