[DOCS-4939] Gazzang References Created: 30/Jun/14  Updated: 27/Jul/16  Resolved: 17/Mar/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Sheena Badani Assignee: Michael Paik
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-3773 Update Data at Rest Encryption Closed
Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

We need to remove all references to Gazzang on our .org and .com website. Since they have been acquired by Cloudera, they are not taking on new MongoDB customers and therefore we shouldn't promote it as an option.

Here is one reference on .org: http://docs.mongodb.org/manual/core/security-introduction/
Change Gazzang paragraph to the following: MongoDB has a partnership with Vormetric to encrypt and secure sensitive data within MongoDB. The Vormetric Data Security platform for MongoDB provides transparent encryption, key management, privileged user access control, and security intelligence. Vormetric can monitor and block non-database users or processes from accessing or viewing the database in a MongoDB environment.
More information here: http://www.vormetric.com/

We also need to remove the following links from our .com site:
http://www.mongodb.com/presentations/securing-data-mongodb-gazzang
http://www.mongodb.com/presentations/automating-secure-mongodb-deployment-opscode-and-gazzang
http://www.mongodb.com/presentations/mongodb-boston-2012/securing-data-mongodb-gazzang-and-chef
https://www.mongodb.com/sites/default/files/downloads/Gazzang%20-%20MongoDB%20-%201%20pager.pdf
(Remove Gazzang link) - http://www.mongodb.com/presentations/event/1483

I think that is all. Let me know if you come across other Gazzang references.

Sheena



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Comment by Githook User [ 17/Mar/15 ]

Author:

{u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}

Message: DOCS-4939
Branch: v2.2
https://github.com/mongodb/docs/commit/c7c4bd3fc112bd390f8531c0a7e0aa55c8f8b367

Comment by Githook User [ 17/Mar/15 ]

Author:

{u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}

Message: DOCS-4939
Branch: v2.4
https://github.com/mongodb/docs/commit/303994540124df2dd74ee3e095ea99defb9c31a8

Comment by Sheena Badani [ 14/Jul/14 ]

Hi samk, what is the status of this JIRA ticket? Thanks!

Comment by justin.dunham@10gen.com [ 02/Jul/14 ]

Sam can help with getting the docs changed.

Generated at Thu Feb 08 07:49:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.