Talk:CipherCloud
This article was nominated for deletion. Please review the prior discussions if you are considering re-nomination:
|
This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||
|
This page is obvious marketing — Preceding unsigned comment added by Mikefromnyc (talk • contribs) 11:54, 7 October 2013 (UTC)
PR Puffery
editAs others have noted on this talk page, this article contains a lot of puffery and reads very much like an advertisement for CipherCloud. As a result, I have added the Advert Template to this page. In addition, very many publicly available articles on CipherCloud mention the DCMA takedown issue. I find it very suspicious that this page has consistently been edited to remove that from the page, even though it was a very public and widely documented controversy. For that reason, I am adding a discussion of that issue into a new section, with several publicly available secondary sources. BurritoSlayer (talk) 15:54, 8 September 2015 (UTC)
DCMA
editHi,
I moved the DCMA take-down notice material up to the "History" section in a previous edit. In the move, I removed the Wired magazine sentence for the paragraph, as it is used as the source for supporting the section. This was my edit: "In April 2013, CipherCloud filed a Digital Millennium Copyright Act takedown notice against Stack Exchange Network for posting a discussion titled "How is CipherCloud doing homomorphic encryption?", which CipherCloud claimed contained copyrighted marketing material to criticize the company.[13]" Does this work and/or should it be in that section? I think it reads better imo. Thanks for your comments! Jppcap (talk) 15:31, 10 May 2014 (UTC)
- Thoughts on edit? Jppcap (talk) 23:48, 13 May 2014 (UTC)
- Made edit in section. I think it works higher up on the page in the History. Thoughts? Jppcap (talk) — Preceding undated comment added 23:42, 21 May 2014 (UTC)
The paragraph about the DMCA notice has been removed, presumably by an employee of ciphercloud. The discussion targeted by the notice might be worth a link as well, since it's the only publicly available analysis of their product I can find. I won't revert that change, since my involvement in the incident constitutes a conflict of interest. CodesInChaos (talk) 17:25, 29 June 2015 (UTC)
Watch for P.R. Puffery
editThe most recent edit was a P.R. piece that was planted. I reverted it and seek comment here. BeenAroundAWhile (talk) 05:47, 6 May 2015 (UTC)
Contro section
editSaw this on my WL w/ expansion further than my edit suggestions above. Tagging for pov, will await feedback here. Jppcap (talk) 22:12, 19 October 2015 (UTC)
- Hi there. I'm the one who made the edit. As you can see with my talk page post above, I believed the page was being patrolled by users who were filling the page with language reminiscent of public relations and advertising. When I did some research, I found several sources that dealt with the DCMA takedown controversy, and I thought it was sufficient to include in the article. While I'm open to suggestions and/or working with others on how to improve the section, I believe it should remain on the page. BurritoSlayer (talk) 21:38, 22 October 2015 (UTC)
- Thanks for reaching out, BurritoSlayer. Just checked out the revision history and definitely found some overt advertising here and here for sure. At a quick glance, there's a lot more to comb through, both ott editing and npov. Definitely agree that the page has gotten out of hand on that front. Regarding DCMA.. I proposed this edit here based on issues w/ WP:Quotefarm and clarity. The newest controversy section is more expansive than previously and contains WP:synthesis, WP:original research and borderline WP:soap. Welcome suggestions here. Jppcap (talk) 18:45, 28 October 2015 (UTC)
- Proposed (per here): "In April 2013, CipherCloud filed a Digital Millennium Copyright Act takedown notice against Stack Exchange Network for posting a discussion titled "How is CipherCloud doing homomorphic encryption?", which CipherCloud claimed contained copyrighted marketing material to criticize the company." Jppcap (talk) 19:31, 3 November 2015 (UTC)
- Hi Jppcap, I agree that my edit may have gone a little overboard. I think your edit is good, but are you proposing to replace the entire section with those two sentences? If so, I think at least there should be a sentence that the claim was ultimately dismissed. Maybe keep "The takedown complaint was ultimately dismissed, but the incident generated renewed scrutiny of CipherCloud’s security claims"? BurritoSlayer (talk) 20:44, 10 November 2015 (UTC)
- Thanks for reaching out, BurritoSlayer. Yeah, that was my proposal, but "In April 2013, CipherCloud filed a Digital Millennium Copyright Act takedown notice against Stack Exchange Network for posting a discussion titled "How is CipherCloud doing homomorphic encryption?", which CipherCloud claimed contained copyrighted marketing material to criticize the company. The takedown complaint was dismissed." without going into soap. Let me know. Jppcap (talk) 14:30, 11 November 2015 (UTC)
- Hi Jppcap, I'm not sure that goes far enough to explain the full situation. The whole incident got written up in the mainstream press by large outlets like TechCrunch and WIRED, and the incident did bring scrutiny on their security claims. I believe the primary problem is original research, not nececssarily soapboxing. May I propose this edit? "A StackExchange user posted a question on its Cryptography board asking how CipherCloud does encryption. Several users suggested that CipherCloud was not using homomorphic encryption, based on the information available online (a white paper, a promotional video, and a security conference presentation). Many users suggested that the company was instead using deterministic encryption, a weaker method. CipherCloud sent a DMCA takedown notice and defamation complaint to StackExchange about the dialogue/postings. The takedown complaint was ultimately dismissed, but the incident generated scrutiny of CipherCloud’s security claims and approach." Let me know what you think and hopefully we can find a compromise solution. BurritoSlayer (talk) 20:05, 23 November 2015 (UTC)
- BurritoSlayer, didn't see a TechCrunch article, but agree that this was covered in reputable news. I pulled from Wired/our proposal edits, see here. Jppcap (talk) 21:18, 4 December 2015 (UTC)
- The next issue is the excess advertising mentioned above. I cut some, but this needs work. Will circle back. Jppcap (talk) 21:24, 4 December 2015 (UTC)
- BurritoSlayer, didn't see a TechCrunch article, but agree that this was covered in reputable news. I pulled from Wired/our proposal edits, see here. Jppcap (talk) 21:18, 4 December 2015 (UTC)
- Hi Jppcap, I'm not sure that goes far enough to explain the full situation. The whole incident got written up in the mainstream press by large outlets like TechCrunch and WIRED, and the incident did bring scrutiny on their security claims. I believe the primary problem is original research, not nececssarily soapboxing. May I propose this edit? "A StackExchange user posted a question on its Cryptography board asking how CipherCloud does encryption. Several users suggested that CipherCloud was not using homomorphic encryption, based on the information available online (a white paper, a promotional video, and a security conference presentation). Many users suggested that the company was instead using deterministic encryption, a weaker method. CipherCloud sent a DMCA takedown notice and defamation complaint to StackExchange about the dialogue/postings. The takedown complaint was ultimately dismissed, but the incident generated scrutiny of CipherCloud’s security claims and approach." Let me know what you think and hopefully we can find a compromise solution. BurritoSlayer (talk) 20:05, 23 November 2015 (UTC)
- Thanks for reaching out, BurritoSlayer. Yeah, that was my proposal, but "In April 2013, CipherCloud filed a Digital Millennium Copyright Act takedown notice against Stack Exchange Network for posting a discussion titled "How is CipherCloud doing homomorphic encryption?", which CipherCloud claimed contained copyrighted marketing material to criticize the company. The takedown complaint was dismissed." without going into soap. Let me know. Jppcap (talk) 14:30, 11 November 2015 (UTC)
- Hi Jppcap, I agree that my edit may have gone a little overboard. I think your edit is good, but are you proposing to replace the entire section with those two sentences? If so, I think at least there should be a sentence that the claim was ultimately dismissed. Maybe keep "The takedown complaint was ultimately dismissed, but the incident generated renewed scrutiny of CipherCloud’s security claims"? BurritoSlayer (talk) 20:44, 10 November 2015 (UTC)
- Proposed (per here): "In April 2013, CipherCloud filed a Digital Millennium Copyright Act takedown notice against Stack Exchange Network for posting a discussion titled "How is CipherCloud doing homomorphic encryption?", which CipherCloud claimed contained copyrighted marketing material to criticize the company." Jppcap (talk) 19:31, 3 November 2015 (UTC)
- Thanks for reaching out, BurritoSlayer. Just checked out the revision history and definitely found some overt advertising here and here for sure. At a quick glance, there's a lot more to comb through, both ott editing and npov. Definitely agree that the page has gotten out of hand on that front. Regarding DCMA.. I proposed this edit here based on issues w/ WP:Quotefarm and clarity. The newest controversy section is more expansive than previously and contains WP:synthesis, WP:original research and borderline WP:soap. Welcome suggestions here. Jppcap (talk) 18:45, 28 October 2015 (UTC)
Suggested edits and discussions
editHi, MrOllie, I saw that in the last week you reverted a number of edits for this page without any reasonable explanation. It makes impression of non-constructive behavior probably related to your based opinion. I want to inform you that I wrote to the Wikimedia Foundation Arbitrage regarding this company's page to ask for a second unbiased opinion about new suggested edits. I want to remind you that Wikipedia pages do not belong to anyone and the tags are removable given the fact that the conditions for removal are met. I proclaim that I'm a neutral curious editor who edits from time to time different pages. Also, I have a strong impression that you over-use your power on the Wikipedia and treat many editors with condescending manner of not even being able to spend extra time and justify your reverts also making an impression of using a bot automatically working on reverts. If you decide to participate in the discussion, you are more than welcome to do it. Here are the suggested edits:
Lead Section
editCipherCloud is a cloud security software company based in San Jose, California. The company enables businesses to adopt cloud services while ensuring data security and regulatory compliance. CipherCloud platform provides risk visibility, cloud control, end-to-end encryption, threat protection, data sovereignty, and global data protection compliance. CipherCloud is in two categories of security vendors classified by Gartner as cloud access security broker[4] and Cloud Encryption Gateway[5].
Hello, I suggest to remove "end-to-end encryption" and "data sovereignty" as they are redundant and a bit promotional. Additionally, Gartner announced in 2019 that the CASB space is evolving to SASE where CipherCloud[1] fits well.
CipherCloud is a cloud security software company based in San Jose, California. The company enables businesses to adopt cloud services while ensuring data security and regulatory compliance. CipherCloud platform provides risk visibility, cloud control, threat protection, and global data protection compliance. CipherCloud is in three categories of security vendors classified by Gartner as cloud access security broker(CASB)[2], Cloud Encryption Gateway[3], and Secure Access Service Edge(SASE) [4].
History
editCipherCloud was founded in 2010 by Pravin Kothari, who previously co-founded ArcSight. [6][7] The company launched in February 2011 and worked solely in Salesforce.com environments initially.[8] It added Amazon Web Services integration in 2011.[9] CipherCloud raised $1.4 million in seed funding from Andreessen Horowitz later that year.[6] CipherCloud released its Gmail encryption solution in June 2012.[10] By September 2012 CipherCloud's platform could also encrypt Force.com, Chatter, Microsoft Office 365.[11] It also launched Connect AnyApp, which allowed users to "simply specify fields on Web pages to be encrypted," and data format and operations would be preserved.[11] CipherCloud closed a $30 million funding round led by Andreessen Horowitz and Index Ventures in December 2012.[12][13] Deutsche Telekom also participated in the funding round through T-Ventures, the telecommunications company's venture capital arm.[14] John M. Jack, a partner at Andreessen Horowitz and former CEO of Fortify Software, joined the CipherCloud board following the investment.[12][13] The company opened its European headquarters in London, England in the same month.[9] CipherCloud added an Australian headquarters in 2013.[15] In February 2013, CipherCloud joined Box Inc. (formerly Box.net), an online file sharing and cloud-content management service, to bring CipherCloud's encryption to file-sharing and file-hosting services such as Box.[16] In January 2014, CipherCloud acquired CloudUp Networks.[17] CloudUp Networks developed software that helped users track data as it moved through cloud environments and restricted that data from leaving the cloud without authorization.[18] In April 2014 CipherCloud released a new product, CipherCloud for Cloud Discovery.[19] Cloud Discovery analyzes cloud applications, which enterprises use for visibility and determine the risk of applications within the organization.[20][21] According to Forbes, Cloud Discovery analyzes cloud applications such as "CRM, finance, HR, IT management, file sharing, collaboration, and productivity."[22] In November 2014, the company announced closing its Series B funding round of $50 million. Transamerica Ventures led the round, joined by Delta Partners, and existing investors Andreessen Horowitz and T-Ventures, the venture capital arm of Deutsche Telekom.[23] In April 2015, CipherCloud acquired Anicut Systems, a privately held provider of adaptive security as a service. The acquisition was made to incorporate cloud security analytics technology and accelerate enterprise cloud adoption.[24] In November 2017, CipherCloud joined the VMware Mobile Security Alliance to provide end-to-end information protection across cloud, mobile and endpoints.[25][26] In April 2018, CipherCloud announced the launch of CASB+ platform, that enabled cloud data protection in multi-mode deployment: API mode and Inline mode (reverse and forward proxy). In March 2019, CipherCloud announced the availability of Secure SaaS Workspace solution as part of its CASB+ platform, that extended enterprise security controls to the cloud data and eliminated the need to route access to SaaS applications through enterprise's infrastructure.[27] In 2018-2019, CipherCloud was on the Gartner’s Magic Quadrant List for Cloud Access Security Brokers (CASB) in the “Visionary” category.[28][29][30]
please include minor edits of the description I made on the main page today.Peter9970 (talk) 07:25, 26 April 2020 (UTC)
Product and technology
editCipherCloud's CASB+ platform provides data protection, deep visibility, adaptive access control, advanced threat protection and centralized compliance capabilities across major SaaS and IaaS clouds, including Office 365, Dropbox, Google Suite, Amazon Web Services, Microsoft Azure, Adobe Analytics and more.[2][29] The Zero-Trust security model adopted by CASB+ enables a single, consistent platform for all cloud applications, delivering seamless data protection with continuous risk assessment and automatic compliance, allowing businesses to get the most from their cloud applications. CASB+ also includes built-in connectors for all the popular cloud applications, that serve as a cloud encryption gateway and encrypt sensitive data in real-time before sending it to the cloud environment. CipherCloud's industry-first Searchable Strong Encryption (SSE) technology, built using standard cryptographic modules and validated by FIPS 140-2, preserves the cloud functionality, allowing users to seamlessly perform basic cloud operations on the encrypted data, such as search and sort.[15][8][14][31]
please change "platform" to "product and technology"; remove promotional words "deep", "advanced", "centralized", "seamless", etc. Keep either "single" or "consistent", but not both, etc. see the following revision:
CipherCloud's CASB+ platform provides visibility, adaptive access control, data security, threat protection and compliance capabilities across SaaS and IaaS clouds, including Office 365, Salesforce, ServiceNow, Slack, Box, Dropbox, Google Suite, Amazon Web Services, Microsoft Azure, etc.[2][29] CipherCloud provides a Zero-Trust security model delivering CASB life-cycle with automated security processes so that organizations can adopt more clouds securely. CASB+ also includes Searchable Strong Encryption (SSE) technology allowing users to perform operations on encrypted data, such as search, sort and analytics.
According to Gartner’s recently released 2019 Magic Quadrant Critical Capabilities for CASB report, CipherCloud received the highest ratings of 26.5 out of 30, leading the CASB market in functionality.[5]
Industry Awards
edit2019. SaaS Security Solution of the Year (in Cloud Security category) (CyberSecurity Breakthrough)[32][33][34] 2016. Best Cloud Computing Security Solution (SC Magazine 2016 Awards)[35] 2014. 10th Info Security Global Excellence Awards[36] 2013. "Information Security Product of the Year" (SC Magazine's Excellence Awards)[37] 2013. Best Emerging Technology in Information Security (SC Magazine's Excellence Awards)[38]
All the updates are confirmed by existing or new sources 2601:1C0:CB01:2660:A8F3:B5E:FA09:5E2E (talk) 01:36, 25 April 2020 (UTC)
- Here are my suggestions for making this seem less advertorial. Try to stick to the facts. I would avoid vague statements as much as possible. For instance, "enables businesses to adopt cloud services while ensuring data security and regulatory compliance." While this might be true from the perspective of the company, it is an opinionated statement. For instance, according to whom does the company "ensure" data security? My point is not that you must list what that is coming from but that the statement shouldn't be included in the article as it is opinionated. I don't know much more information so it's hard to give you advice on what to replace it with, but for example this sentence could essentially be shortened to "a cloud services company" (as all cloud services companies I would think would try to ensure data security). Note that this is just an example and there are other instances of this in your text. Let me know if I should provide some more examples. Sam-2727 (talk) 03:53, 25 April 2020 (UTC)
- Update: I just saw that that is already in the article. It should definitely be deleted, but I will provide some comments on your specific draft now. Sam-2727 (talk) 03:55, 25 April 2020 (UTC)
- Ok. I'm just looking at one of your most recent changes (I presume this is you) under the "products" section. Long quotes are discouraged on Wikipedia. In fact in general, quotes should be used quite sparingly. Although given the presence of the quote it's fairly obvious that this is an opinion, the length of the quote makes it appear as this is the opinion of the article, while in reality the article shouldn't have an opinion. If you remove the very long quote and just put the text "Gartner described CipherCloud products in its annual research report "Magic Quadrant for Cloud Access Security Broker, Oct 2019"" in the recognition section, this would merit consideration in the article. Sam-2727 (talk) 03:59, 25 April 2020 (UTC)
- Update: I just saw that that is already in the article. It should definitely be deleted, but I will provide some comments on your specific draft now. Sam-2727 (talk) 03:55, 25 April 2020 (UTC)
- Here are my suggestions for making this seem less advertorial. Try to stick to the facts. I would avoid vague statements as much as possible. For instance, "enables businesses to adopt cloud services while ensuring data security and regulatory compliance." While this might be true from the perspective of the company, it is an opinionated statement. For instance, according to whom does the company "ensure" data security? My point is not that you must list what that is coming from but that the statement shouldn't be included in the article as it is opinionated. I don't know much more information so it's hard to give you advice on what to replace it with, but for example this sentence could essentially be shortened to "a cloud services company" (as all cloud services companies I would think would try to ensure data security). Note that this is just an example and there are other instances of this in your text. Let me know if I should provide some more examples. Sam-2727 (talk) 03:53, 25 April 2020 (UTC)
References
- ^ https://www.brighttalk.com/webcast/17800/395573/a-cloud-first-security-architecture-secure-access-service-edge-sase
- ^ https://www.gartner.com/it-glossary/cloud-access-security-brokers-casbs/
- ^ https://www.gartner.com/it-glossary/cloud-encryption-gateways
- ^ https://blogs.gartner.com/andrew-lerner/2019/12/23/say-hello-sase-secure-access-service-edge/
- ^ https://www.ciphercloud.com/ciphercloud-achieves-highest-gartner-mq-critical-capabilities-scores/
Clean up and tag removal
editI've just done additional clean up of the page, removing duplicate information in the Lead section and cleaning the History section from all the buzz and redundant words. I thought the tag could be removed after that. Let me know if you still find any issues with the text - please, be specific while addressing the issues. 2601:1C0:CB01:2660:ED91:DC4A:596A:50AD (talk) 22:48, 5 June 2020 (UTC)