{"id":30080,"date":"2026-01-14T16:42:45","date_gmt":"2026-01-14T11:12:45","guid":{"rendered":"https:\/\/www.kaspersky.co.in\/blog\/transparency-independent-study\/30080\/"},"modified":"2026-01-14T16:42:53","modified_gmt":"2026-01-14T11:12:53","slug":"transparency-independent-study","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.in\/blog\/transparency-independent-study\/30080\/","title":{"rendered":"Trust but verify: how we set the standard for transparency and trust"},"content":{"rendered":"<p>The life of a modern head of information security (also known as CISO \u2013 Chief Information Security Officer) is not just about fighting hackers. It\u2019s also an endless quest that goes by the name of \u201ccompliance\u201d. Regulators keep tightening the screws, standards pop up like mushrooms, and headaches only get worse; but wait\u2026 \u2013 there\u2019s more: CISOs are responsible not only for their own perimeter, but what goes on outside it too: for their entire supply chain, all their contractors, and the whole hodge-podge of software their business processes run on. Though the logic here is solid, it\u2019s also unfortunately ruthless: if a hole is found at your supplier, but the problems hit you, in the end it\u2019s you who\u2019s held accountable. This logic applies to security software too.<\/p>\n<p>Back in the day, companies rarely thought about what was actually inside the security solutions and products they used. Now, however, businesses \u2013 especially large ones \u2013 want to know everything: what\u2019s really inside the box? Who wrote the code? Is it going to break some critical function or could it even bring everything down? (We\u2019ve seen such precedents; example: the <a href=\"https:\/\/en.wikipedia.org\/wiki\/2024_CrowdStrike-related_IT_outages\" target=\"_blank\" rel=\"noopener nofollow\">Crowdstrike 2024 update incident<\/a>.) Where and how is data processed? And these are the right questions to ask.<\/p>\n<p>The problem lies in the fact that almost all customers <strong>trust<\/strong> their vendors to answer accurately when asked such questions \u2013 very often because they have no other choice. A more mature approach in today\u2019s cyber-reality is to <strong>verify<\/strong>.<\/p>\n<p>In corporate-speak this is called supply-chain trust, and trying to solve this puzzle on your own is a serious headache. You need help from vendors. A responsible vendor is ready to show what\u2019s under the hood of its solutions, to open up the source code to partners and customers for review, and, in general, to earn trust not with nice slides but with solid, practical steps.<\/p>\n<p>So who\u2019s already doing this, and who\u2019s still stuck in the past? A <a href=\"https:\/\/www.av-comparatives.org\/independent-study-highlights-transparency-and-data-practices-in-leading-cybersecurity-products\/\" target=\"_blank\" rel=\"noopener nofollow\">fresh, in-depth study<\/a> from our colleagues in Europe has the answer. It was conducted by the respected testing lab AV-Comparatives, the Tyrol Chamber of Commerce (<a href=\"https:\/\/www.wko.at\/tirol\/information-consulting\/unternehmensberatung-buchhaltung-informationstechnologie\/transparenz-ist-kein-nice-to-have--sondern-sicherheitsfaktor\" target=\"_blank\" rel=\"noopener nofollow\">WKO<\/a>), the MCI Entrepreneurial School, and the law firm Studio Legale Tremolada.<\/p>\n<p>The main conclusion of the study is that the era of \u201cblack boxes\u201d in cybersecurity is over. RIP. Amen. The future belongs to those who don\u2019t hide their source code and vulnerability reports, and who give customers maximum choice when configuring their products. And the report clearly states who doesn\u2019t just promise but actually delivers. Guess who!\u2026<\/p>\n<p>What a great guess! Yes \u2013 it\u2019s us!<\/p>\n<p>We give our customers something that is still, unfortunately, a rare and endangered species in the industry: transparency centers, source code reviews of our products, a detailed software bill of materials (<a href=\"https:\/\/www.kaspersky.com\/about\/press-releases\/kaspersky-announces-software-bill-of-materials-available-for-its-customers-and-partners\" target=\"_blank\" rel=\"noopener nofollow\">SBOM<\/a>), and the ability to check update history and control rollouts. And of course we provide everything that\u2019s already become the industry standard. You can study all the details in the full <a href=\"https:\/\/www.wko.at\/tirol\/information-consulting\/transparency-review-and-accountability-in-cyber-security-tra.pdf\" target=\"_blank\" rel=\"noopener nofollow\">\u201cTransparency and Accountability in Cybersecurity\u201d (TRACS) report<\/a>, or in <a href=\"https:\/\/gti.kaspersky.com\/report\/protection_beyond_detection_why_trust_and_transparency_decide_your_cybersecurity_future.pdf\" target=\"_blank\" rel=\"noopener\">our summary<\/a>. Below, I\u2019ll walk through some of the most interesting bits.<\/p>\n<h2>Not mixing apples and oranges<\/h2>\n<p>TRACS reviewed 14 popular vendors and their EPP\/EDR products \u2013 from Bitdefender and CrowdStrike to <a href=\"https:\/\/www.kaspersky.co.in\/next-edr-optimum?icid=in_kdailyplacehold_acq_ona_smm__onl_b2b_kdaily_wpplaceholder_sm-team___knext____31e69e5626732573\" target=\"_blank\" rel=\"noopener\">our EDR Optimum<\/a> and WithSecure. The objective was to understand which vendors don\u2019t just say \u201ctrust us\u201d, but actually let you verify their claims. The study covered 60 criteria: from <a href=\"https:\/\/en.wikipedia.org\/wiki\/General_Data_Protection_Regulation\" target=\"_blank\" rel=\"noopener nofollow\">GDPR<\/a> (General Data Protection Regulation \u2013 it\u2019s a European study after all) compliance and ISO 27001 audits, to the ability to process all telemetry locally and access a product\u2019s source code. But the authors decided not to give points for each category or form a single overall ranking.<\/p>\n<p>Why? Because everyone has different threat models and risks. What is a feature for one may be a bug and a disaster for another. Take fast, fully automatic installation of updates. For a small business or a retail company with thousands of tiny independent branches, this is a blessing: they\u2019d never have enough IT staff to manage all of that manually. But for a factory where a computer controls the conveyor it would be totally unacceptable. A defective update can bring a production line to a standstill, which in terms of business impact could be fatal (or at least worse than the <a href=\"https:\/\/ics-cert.kaspersky.com\/publications\/reports\/2025\/12\/18\/a-brief-overview-of-the-main-incidents-in-industrial-cybersecurity-q3-2025\/#intsidenty-v-krupnykh-organizatsiyakh\" target=\"_blank\" rel=\"noopener\">recent Jaguar Land Rover cyberattack<\/a>); here, every update needs to be tested first. It\u2019s the same story with telemetry. A PR agency sends data from its computers to the vendor\u2019s cloud to participate in detecting cyberthreats and get protection instantly. Perfect. A company that processes patients\u2019 medical records or highly classified technical designs on its computers? Its telemetry settings would need to be reconsidered.<\/p>\n<p>Ideally, each company should assign \u201cweights\u201d to every criterion, and calculate its own \u201ccompatibility rating\u201d with EDR\/EPP vendors. But one thing is obvious: whoever gives customers choices, wins.<\/p>\n<p>Take file reputation analysis of suspicious files. It can work in two ways: through the vendor\u2019s common cloud, or through a private micro-cloud within a single organization. Plus there\u2019s the option to disable this analysis altogether and work completely offline. Very few vendors give customers all three options. For example, \u201con-premise\u201d reputation analysis is available from only eight vendors in the test. It goes without saying we\u2019re one of them.<\/p>\n<h2>Raising the bar<\/h2>\n<p>In every category of the test the situation is roughly the same as with the reputation service. Going carefully through all 45 pages of the report, we\u2019re either ahead of our competitors or among the leaders. And we can proudly say that in roughly a third of the comparative categories we offer significantly better capabilities than most of our peers. See for yourself:<\/p>\n<p>Visiting a transparency center and reviewing the source code? Verifying that the product binaries are built from this source code? Only three vendors in the test provide these things. And for one of them \u2013 it\u2019s only for government customers. Our transparency centers are the most numerous and geographically spread out, and offer customers the widest range of options.<\/p>\n<div id=\"attachment_55128\" style=\"width: 1210px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2026\/01\/14164251\/transparency-independent-study-center.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-55128\" class=\"wp-image-55128 size-full\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2026\/01\/14164251\/transparency-independent-study-center.jpg\" alt=\"The opening of our first transparency center back in 2018\" width=\"1200\" height=\"801\"><\/a><p id=\"caption-attachment-55128\" class=\"wp-caption-text\">The opening of our first transparency center back in 2018<\/p><\/div>\n<p>Downloading database updates and rechecking them? Only six players \u2013 including us \u2013 provide this.<\/p>\n<p>Configuring multi-stage rollout of updates? This isn\u2019t exactly rare, but it\u2019s not widespread either \u2013 only seven vendors besides us support it.<\/p>\n<p>Reading the results of an external security audit of the company? Only we and six other vendors are ready to share this with customers.<\/p>\n<p>Breaking down a supply chain into separate links using an SBOM? This is rare too: you can request an SBOM from only three vendors. One of them is the green-colored company that happens to bear my name.<\/p>\n<p>Of course, there are categories where everyone does well: all of them have successfully passed an ISO\/IEC 27001 audit, comply with GDPR, follow secure development practices, and accept vulnerability reports.<\/p>\n<p>Finally, there\u2019s the matter of technical indicators. All products that work online send certain technical data about protected computers, and information about infected files. For many businesses this isn\u2019t a problem, and they\u2019re glad it improves effectiveness of protection. But for those seriously focused on minimizing data flows, AV-Comparatives measures those too \u2013 and we just so happen to collect the least amounts of telemetry compared to other vendors.<\/p>\n<h2>Practical conclusions<\/h2>\n<p>Thanks to the Austrian experts, CISOs and their teams now have a much simpler task ahead when checking their security vendors. And not just the 14 that were tested. The same framework can be applied to other security solution vendors and to software in general. But there are strategic conclusions too\u2026<\/p>\n<p><strong>Transparency makes risk management easier<\/strong>. If you\u2019re responsible for keeping a business running, you don\u2019t want to guess whether your protection tool will become your weak point. You need predictability and accountability. The WKO and AV-Comparatives study confirms that our model reduces these risks and makes them manageable.<\/p>\n<p><strong>Evidence instead of slogans<\/strong>. In this business, it\u2019s not enough to be able write \u201cwe are secure\u201d on your website. You need audit mechanisms. The customer has to be able to drop by and verify things for themselves. We provide that. Others are still catching up.<\/p>\n<p><strong>Transparency and maturity go hand in hand<\/strong>. Vendors that are transparent for their customers usually also have more mature processes for product development, incident response, and vulnerability handling. Their products and services are more reliable.<\/p>\n<p><strong>Our approach to transparency (<\/strong><a href=\"https:\/\/www.kaspersky.com\/transparency-center\" target=\"_blank\" rel=\"noopener nofollow\"><strong>GTI<\/strong><\/a><strong>) works<\/strong>. When we announced our initiative several years ago and opened Transparency Centers around the world, we heard all kinds of things from critics \u2013 like that it was a waste of money and that nobody needed it. Now independent European experts are saying that this is how a vendor should operate in 2025 and beyond.<\/p>\n<p>It was a real pleasure reading this report. Not just because it praises us, but because the industry is finally turning in the right direction \u2013 toward transparency and accountability.<\/p>\n<p>We started this trend, we\u2019re leading it, and we\u2019re going to keep pioneering within it. So, dear readers and users, don\u2019t forget: trust is one thing; being able to fully verify is another.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Who can you trust in the cybersecurity solutions market? Fourteen major vendors were compared in terms of transparency, security management, and data-handling practices \u2013 and guess which was a leader across the board?!&#8230;<\/p>\n","protected":false},"author":13,"featured_media":30083,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2036,2609,2610],"tags":[2364,3488,2247],"class_list":{"0":"post-30080","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-enterprise","9":"category-smb","10":"tag-av-comparatives","11":"tag-risk-management","12":"tag-transparency"},"hreflang":[{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/transparency-independent-study\/30080\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/transparency-independent-study\/25144\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/transparency-independent-study\/29960\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/transparency-independent-study\/28895\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/transparency-independent-study\/31780\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/transparency-independent-study\/30470\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/transparency-independent-study\/41159\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/transparency-independent-study\/14173\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/transparency-independent-study\/55120\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/transparency-independent-study\/23571\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/transparency-independent-study\/33087\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/transparency-independent-study\/30173\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/transparency-independent-study\/35845\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/transparency-independent-study\/35500\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.in\/blog\/tag\/transparency\/","name":"transparency"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/30080","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/comments?post=30080"}],"version-history":[{"count":1,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/30080\/revisions"}],"predecessor-version":[{"id":30082,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/30080\/revisions\/30082"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media\/30083"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media?parent=30080"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/categories?post=30080"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/tags?post=30080"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}