{"id":18258,"date":"2021-04-22T21:44:24","date_gmt":"2021-04-22T17:44:24","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/trello-data-leaks\/18258\/"},"modified":"2021-04-22T21:44:41","modified_gmt":"2021-04-22T17:44:41","slug":"trello-data-leaks","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/trello-data-leaks\/18258\/","title":{"rendered":"Trello data leak"},"content":{"rendered":"<p>Data belonging to users from hundreds of large and thousands of small companies has been leaked from Trello, <a href=\"https:\/\/mainichi.jp\/english\/articles\/20210407\/p2a\/00m\/0na\/019000c\" target=\"_blank\" rel=\"nofollow noopener\">according to some media reports<\/a>. It was not a leak in the normal sense of the word; the companies had been using Trello for years without bothering to configure the privacy settings properly, and the current fuss is about some researchers making that information public.<\/p>\n<p>In truth, reports of another company storing important data openly in Trello make the news every couple of years. Researcher Kushagra Pathak <a href=\"https:\/\/medium.com\/free-code-camp\/discovering-the-hidden-mine-of-credentials-and-sensitive-information-8e5ccfef2724\" target=\"_blank\" rel=\"nofollow noopener\">attempted to highlight the issue<\/a> on Medium three years ago. Unfortunately, such warnings tend to have only a brief effect.<\/p>\n<h2>What got leaked, and why<\/h2>\n<p>Trello members use boards to collaborate on projects. The boards are private \u2014 not viewable by anyone outside of the team \u2014 by default, but when users need to show a board to anyone not on the team, they set the board\u2019s visibility to <em>public<\/em>. At that point, any user can open the board with a direct link, and search engines can index the information on it. Access to each board is configured separately.<\/p>\n<p>An appropriately formed search query can uncover lots of public boards belonging to various companies. Among them lurk website credentials, document scans, and confidential business discussions, which various researchers have been finding and publishing.<\/p>\n<p>Unauthorized access to your company\u2019s Trello workspace can spell trouble even if you do not keep any confidential documents or passwords there. Attackers can use business information to make their social engineering attacks more persuasive, for example, by initiating correspondence with an employee and quieting their vigilance by mentioning details from current projects.<\/p>\n<h2>Configuring Trello to keep information private<\/h2>\n<p>By changing just two settings, you can stop search engines from indexing data in your Trello workspace. The less important one is workspace visibility; more important, each board\u2019s visibility.<\/p>\n<p>Workspaces have two visibility settings: private and public. The choice is clear.<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2021\/04\/22214433\/trello-data-leaks-Workspace-EN.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2021\/04\/22214433\/trello-data-leaks-Workspace-EN.jpg\" alt=\"Trello workspace visibility settings\" width=\"316\" height=\"279\" class=\"aligncenter size-full wp-image-18259\"><\/a><\/p>\n<p>Boards allow more options: private (only board members have access), workspace (all workspace members have access), organization (all employees have access \u2014 this is for business accounts only), and public (everyone has access). The current Trello interface provides a clear enough description of visibility options, which suggest Web crawlers have access to public boards only, so any other option but public would have prevented the so-called leakage.<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2021\/04\/22214440\/trello-data-leaks-board-EN.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2021\/04\/22214440\/trello-data-leaks-board-EN.jpg\" alt=\"Trello board visibility settings\" width=\"376\" height=\"399\" class=\"aligncenter size-full wp-image-18261\"><\/a><\/p>\n<p>We believe work-related information should be restricted to a minimum of employees, and therefore, using a private option is always better. It\u2019s a bit more work \u2014 someone will have to manage who has access to each board \u2014 but it helps ensure information integrity.<\/p>\n<h2>Ensuring secure collaboration<\/h2>\n<p>Configuring your Trello boards for appropriate visibility will prevent the information from going public. Consider these other important measures as well:<\/p>\n<ul>\n<li>Carefully manage the list of users who have access to your Trello workspace and each board. If anyone leaves the project, the team, or the entire company, revoke their access right away;<\/li>\n<li>Educate employees about the importance of using <a href=\"https:\/\/www.kaspersky.com\/blog\/strong-password-day\/25519\/\" target=\"_blank\" rel=\"noopener nofollow\">strong passwords<\/a>, and recommend they activate Trello\u2019s <a href=\"https:\/\/www.kaspersky.com\/blog\/2fa-practical-guide\/24219\/\" target=\"_blank\" rel=\"noopener nofollow\">two-factor authentication<\/a> option;<\/li>\n<li>Ensure that every employee responsible for information security knows which online collaboration tools all employees use and what information they store in those tools and services. That information is required for assessing risks and creating a threat model;<\/li>\n<li>Install a <a href=\"https:\/\/me-en.kaspersky.com\/small-to-medium-business-security?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder_______\" target=\"_blank\" rel=\"noopener\">security solution<\/a> on every computer, bearing in mind that any collaboration tool can be turned into a channel for spreading cyberthreats (malicious files or links).<\/li>\n<\/ul>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kesb-trial\">\n","protected":false},"excerpt":{"rendered":"<p>What happened with Trello wasn\u2019t a traditional data leak \u2014 so, what happened?<\/p>\n","protected":false},"author":700,"featured_media":18263,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1318,1917],"tags":[2262,1183,1892],"class_list":{"0":"post-18258","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-collaboration","10":"tag-leaks","11":"tag-trello"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/trello-data-leaks\/18258\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/trello-data-leaks\/22776\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/trello-data-leaks\/24620\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/trello-data-leaks\/22648\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/trello-data-leaks\/21740\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/trello-data-leaks\/25136\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/trello-data-leaks\/24470\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/trello-data-leaks\/30566\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/trello-data-leaks\/9569\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/trello-data-leaks\/39497\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/trello-data-leaks\/16830\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/trello-data-leaks\/17386\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/trello-data-leaks\/14730\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/trello-data-leaks\/26569\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/trello-data-leaks\/30605\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/trello-data-leaks\/26963\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/trello-data-leaks\/23801\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/trello-data-leaks\/29151\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/trello-data-leaks\/28949\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/leaks\/","name":"leaks"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/18258","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/700"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=18258"}],"version-history":[{"count":2,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/18258\/revisions"}],"predecessor-version":[{"id":18262,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/18258\/revisions\/18262"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/18263"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=18258"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=18258"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=18258"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}