29
Implementing Enterprise 2.0 in a Controlled Environment: Lessons Learned Carl Frappaolo Information Architected, Inc.

Esecurity e202

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Esecurity e202

Implementing Enterprise 2.0 in a

Controlled Environment: Lessons Learned

Carl FrappaoloInformation Architected, Inc.

Page 2: Esecurity e202

The company treads a delicate balance between social computing

and privacy.

Page 3: Esecurity e202

Oh ReallyReally ?

Page 4: Esecurity e202

Risk Management

KnowledgeManagement

Visualization

Collaboration

Social Network

Computing

Search

TaxonomyFacets

ContentAnalytics

RecordsManagement

DocumentManagement

ContentManagement

DRMDAM

BPMWorkflow

Authentication

PortalsWebsites

Control & Secure Collaborate & Innovate

Information Architecture / Sourcing Strategy

IDExtraction

IRM/ERM

Contextual

Filtering

ePublishingTagging &

Voting

Community Analytics

Email IM Shared Drives html Multimedia DBs …

COLD

Page 5: Esecurity e202

“Enterprise 2.0 platforms, are by their nature more open, transparent, and visible than communication channels like email. Most of my work has stressed the benefits of using these platforms, but there are also potential drawbacks… Perhaps the most obvious of these goes by the label ‘security.’ It's the fear that the wrong content will show up on the platform, and/or that it will be viewed by the wrong people.” - Prof. Andrew McAfee

Page 6: Esecurity e202
Page 7: Esecurity e202

“You have to deal with this. Times have

changed. “

“This is the biggest unspoken hurdle

companies will face in this area.”

Page 8: Esecurity e202

2 General Findings• Very few best practices exist

• There is no single “approach” or perspective

Page 9: Esecurity e202

CULTURE> vertical industry & European presence

Page 10: Esecurity e202

Privacy = Security = Legal Compliance

Page 11: Esecurity e202

Build on the Past

Page 12: Esecurity e202

Challenge Assumptions

Think Anew

Page 13: Esecurity e202

Lowest Common

Denominator

Page 14: Esecurity e202

Policy

Technology-driven Enforcement

Page 15: Esecurity e202

“There are no new risks - just

more opportunity for them to occur”

Page 16: Esecurity e202

Opt-in• Popular & Simple

• Challenges Exist• Granularity• Criticality• Basic rights• “Practical” / pressure• Reciprocity issues• Potentially undermines the initiative• Innatley revealing

• Poor analytics

Page 17: Esecurity e202

Piloting• Not Universally Used

• Introduction to E2.0 and Security

• Scale and Scope are Critical to Value

• Start in areas where content is not confidential

Page 18: Esecurity e202

Automated Tracking & Reporting

• Not reliable or always permitted

• Can constitute a violation in itself

• Exceptions•“Having our solution provide abuse reports was a huge win. These tools make it easier for employees to create anything, We can see if an employee posts something inappropriate.”

Page 19: Esecurity e202

Avoid• Bookmarking

• Tagging

• Voting

• Social Network Analysis

Page 20: Esecurity e202

Approaches• Cyclical

• Ongoing

• Situational

•“This is not a one-and-done situation”

Page 21: Esecurity e202

Policy Guidelines• KISS

• High level

• Formally “informal”

• Allow for interpretation

• Stress individual accountability / ethics

Page 22: Esecurity e202

Other Words of Advice• Know how/where your software gathers personal data• Understand user concerns

• Bring all parties to the table as early as possible• Don’t own the content

• Policy policy policy ... evolve, evolve, evolve

• Remember these concerns are solvable

Page 23: Esecurity e202

CIO: ...Does the Enterprise 2.0 industry need to do something to improve security?

McAfee: ... very little, if anything, needs to be done with it. I ask for horror stories all the time when I talk to groups, especially compliance or security-related horror stories. My collection is empty. People know how to do their jobs. By this point, none of these tools are a week old, so the rules for using them aren't unclear. ...

Page 24: Esecurity e202

Jane Doe v. Norwalk Community College

EFF v USTEKsystems

Souvalian v. GoogleCrispin v. Audigier

Page 25: Esecurity e202

Risk Management

KnowledgeManagement

Visualization

Collaboration

Social Network

Computing

Search

TaxonomyFacets

ContentAnalytics

RecordsManagement

DocumentManagement

ContentManagement

DRMDAM

BPMWorkflow

Authentication

PortalsWebsites

Control & Secure Collaborate & Innovate

Information Architecture / Sourcing Strategy

IDExtraction

IRM/ERM

Contextual

Filtering

ePublishingTagging &

Voting

Community Analytics

Email IM Shared Drives html Multimedia DBs …

COLD

Page 26: Esecurity e202

“Ask what is the lost potential value if compliance is strictly enforced.”

“If we do this then what can go wrong? What is the potential damage if that happens?”

“Our goal was to enable usage of technology to the highest degree PRACTICAL”

Page 27: Esecurity e202

“For us the local laws have been trumped by the greater good of the business.”

“The business models and advantages offered by E2.0 are compelling and so you have to work through the risk issues.”

“How we balance the legitimate demand for appropriate privacy and security against the need for knowledge exchange to support an effective and efficient community is the defining issue of the 21st century.”

Page 28: Esecurity e202

Social Media Policies:http://alturl.com/kvra

Thank you Doug Cornelius

Page 29: Esecurity e202

Let’s Get 2.0

[email protected] Facebook: Carl Frappaolo Twitter: @carlfrappaolo

www.informationarchitected.com Facebook: Information Architected Twitter: @IAI

Text