{"id":8866,"date":"2025-12-11T12:00:00","date_gmt":"2025-12-11T10:00:00","guid":{"rendered":"https:\/\/blog.eset.ee\/et\/?p=8866"},"modified":"2026-06-14T19:54:58","modified_gmt":"2026-06-14T16:54:58","slug":"locks-socs-and-a-cat-in-a-box-what-schr%c3%b6dinger-can-teach-us-about-cybersecurity","status":"publish","type":"post","link":"https:\/\/blog.eset.ee\/et\/en\/2025\/12\/11\/locks-socs-and-a-cat-in-a-box-what-schr%c3%b6dinger-can-teach-us-about-cybersecurity\/","title":{"rendered":"Locks, SOCs and a cat in a box: What Schr\u00f6dinger can teach us about cybersecurity"},"content":{"rendered":"<p>I recently had, what I thought, was a unique brainwave. (Spoiler alert: it wasn\u2019t, but please read on!)<\/p>\n<p>As a marketing leader at ESET UK, part of my role is to communicate how our powerful and comprehensive solutions can be implemented to protect organisations, in a way that helps clarify the case for upgrading to higher levels of cybersecurity. And that need for clarity is now more urgent than ever.<\/p>\n<p>Cybersecurity leaders and agencies, including the UK\u2019s National Cyber Security Centre (<a href=\"https:\/\/www.ncsc.gov.uk\/collection\/ncsc-annual-review-2025\/chapter-02-resilience-at-scale\/dont-wait-for-the-breach\">NCSC<\/a>), are often quoted as saying that cyberattacks are not \u201ca matter of if, but when.\u201d So perhaps it\u2019s not too much of a stretch to describe every organisation as existing in a \u201cpre-breach state\u201d, or a condition where threats may already be present but stay under the radar.<\/p>\n<p>Which brings to mind <a href=\"https:\/\/en.wikipedia.org\/wiki\/Schr%C3%B6dinger%27s_cat\">Schr\u00f6dinger\u2019s cat<\/a>, the famous thought experiment where a cat in a sealed box is simultaneously alive and dead \u2013 until you look inside. This might be challenging the analogy a bit, but in cybersecurity terms, your organisation lives in a similar state: it\u2019s both breached and not breached \u2013 until you look. Without visibility, you simply don\u2019t know. And by the time you do, the damage may already be done.<\/p>\n<p>Accepting this reality demands a shift in mindset and a shift in strategy. Indeed, for organisations without the requisite tools for internal threat hunting and monitoring of malicious behaviour, one could further argue that this, actually, represents a duality of state encountered in quantum theory and, therefore, these organisations are in a kind of \u201cquantum breach state\u201d.<\/p>\n<p>It came as no surprise when I found that my brainwave <a href=\"https:\/\/www.linkedin.com\/pulse\/schr%C3%B6dingers-cat-cybersecurity-paradox-uncertainty-jackson-jaikar--7wfgc\">was shared<\/a> amongst at least <a href=\"https:\/\/advantage.nz\/schrodingers-breach-the-uncertainty-principle-in-cybersecurity\/\">a few others<\/a>, who had <a href=\"https:\/\/cyberstrategyinstitute.com\/your-security-tools-are-lying-to-you-what-happens-when-threats-go-unobserved-schrodinger-cat-paradox-within-cybersecurity\/\">used this analogy<\/a> to explain the new reality and encourage organisations to revisit their cybersecurity strategy accordingly. A bit disappointing from an egotistical perspective, but also not too much because it\u2019s clearly a train of thought that resonated with at least those few, too.<\/p>\n<p>But now I\u2019m going to pick holes in the analogy a little whilst hoping to underscore the key message.<\/p>\n<h2>Random and not-so-random<\/h2>\n<p>The original thought experiment \u2013 first described by Austrian physicist Erwin Schr\u00f6dinger 90 years ago, almost to the day \u2013 relied on the random chance of the radioactive decay of an element emitting a particle that hit a detector, which triggered the release of poison into the box, thereby snuffing out the cat. This is a random chance determined by quantum decay, whereas the timing of the \u201cdetonation\u201d of malware by criminals within an organisation is, more often than not, planned.<\/p>\n<p>The loose grouping of English-speaking criminals known as Scattered Spider, who were behind the Marks and Spencer (M&amp;S) breach in the UK, were thought to have been moving through the company\u2019s systems <a href=\"https:\/\/securityjournaluk.com\/m-and-s-cyber-attack\/\">undetected, <em>for weeks<\/em><\/a>. This same group is thought to be behind the, oft-referenced, Jaguar Land Rover (JLR) breach, which is estimated to have cost over \u00a32 billion to the UK economy and is <a href=\"https:\/\/www.bbc.co.uk\/news\/articles\/cy9pdld4y81o\">officially the costliest in UK history<\/a>.<\/p>\n<p>It is fair to assume that the same tactics may have been employed, although details of how long the attackers were present in JLR\u2019s systems <a href=\"https:\/\/www.ft.com\/content\/49a49961-0dc9-4d19-bb26-7020e07e465c\">are sketchy<\/a>. In the case of M&amp;S, the perpetrators spent a long (dwell) time \u2018living off the land\u2019, unleashing the chaos at the start of the Easter holiday weekend. The JLR attack, meanwhile, was triggered on the 31<sup>st<\/sup> of August 2025, on the eve of the UK car industry\u2019s equivalent of Christmas and Thanksgiving rolled into one: the new car registration day (\u201cnew plate day\u201d) on the 1<sup>st<\/sup> of September.<\/p>\n<p>Random? I don\u2019t think so.<\/p>\n<p>Therefore, the quantum breach analogy doesn\u2019t quite hold. If I were to venture a guess, the date was carefully planned for maximum disruption \u2013 and it worked spectacularly well for the attackers (and spectacularly badly for JLR, of course).<\/p>\n<p>At this point, it\u2019s worth reminding ourselves of a few statistics. According to IBM\u2019s <a href=\"https:\/\/www.ibm.com\/reports\/data-breach\">Cost of a Data Breach Report 2025<\/a>, the global mean time to identify and contain a breach (i.e., the entire breach lifecycle) is 241 days, while the mean time to identify a breach is 181 days \u2013 we\u2019re talking about big numbers here either way. The uncomfortable reality is that many organisations are breached long before they realise it. And the longer the dwell time, the more damaging the eventual \u201cdetonation\u201d of the attack is likely to be.<\/p>\n<h2>Solutions: Locks and\/or SOCs<\/h2>\n<p>If, by now, you have accepted my \u201ctheory\u201d that your organisation is in a pre-breach state, you might now think about solutions. One such solution is, usually, procuring\/upgrading your security (i.e., buy a bigger lock) or go the whole hog and upgrade to EDR or XDR tools and then go threat-hunting. The latter would equate to \u201copening the box\u201d and observing, of course.<\/p>\n<p>Opting for the former (bigger locks) doesn\u2019t necessarily help when you consider the insider threat and social engineering and other attack strategies employed by cybercrime groups like Scattered Spider, which were behind both JLR and Marks &amp; Spencer breaches. No matter the size of the lock, stealing the keys (or having them, effectively, given away by clicking on a malicious link or being <a href=\"https:\/\/www.welivesecurity.com\/en\/business-security\/it-service-desks-security-blind-spot-business\/\">tricked into giving away or resetting a password<\/a>) makes them obsolete in this instance.<\/p>\n<p>So, what about SOCs?<\/p>\n<p>For this to work, of course, firstly you\u2019ll need to create a SOC of some sort and then staff it with security analysts. Very expensive and time-consuming \u2013 this can take months to set up and cost hundreds of thousands of pounds\/dollars\/euros. And that\u2019s even if you can recruit enough people due to the much reported, cybersecurity skills shortage. So, let\u2019s \u2018go commando\u2019 then; i.e., do it ourselves.<\/p>\n<p>This option needs to be considered with caution \u2013 the skill required to operate these powerful tools is not to be underestimated and when they are activated, many (most\/all) organisations will find the sheer volume of telemetry, alerts and alarms so overwhelming that they end up disabling many of them just to dampen the noise. So, whilst the \u201cquantum state\u201d of the breach is now resolved \u2013 i.e., you\u2019re now observing your systems \u2013 it may create a worse situation and lead to a false sense of security. You now <em>think <\/em>you\u2019re ok when you\u2019re <em>potentially <\/em>not, because you may not have the requisite skills to properly analyse what\u2019s being observed.<\/p>\n<p>Add to the mix that, here at ESET, we\u2019ve seen an increasing number of cyber insurance policies, shared by clients, that insist on EDR solutions being in place to even qualify for cover, which can leave security professionals with a real conundrum. Forced into using tools that require highly skilled operators, without the ability to use them correctly for the policy to remain applicable in the event of the (inevitable) breach. Stress is probably one of the words most used in cybersecurity teams the world over, when describing their day-to-day \u2013 and it\u2019s hardly surprising.<\/p>\n<p>But there is a third way. Turning for help to the vendors that create the tools and offer services to threat hunt, monitor and remediate these threats is increasingly the direction of travel for organisations of all sizes. Managed detection and response (MDR) services resolve this dilemma: experts managing the tools, round the clock monitoring, proactive threat hunting, rapid detection and remediation, amongst others \u2013 this all de-stresses the situation, resolves the \u201cquantum breach state\u201d and defuses the cyber-bomb, and ultimately goes a long way to help meet insurance and compliance requirements and most importantly, mitigates the damage created by longer-dwelling APT and cybercrime groups.<\/p>\n<h2>The reality check<\/h2>\n<ul>\n<li>You really don\u2019t know you\u2019ve been breached until you observe the reality within your systems. Do you know you haven\u2019t been?<\/li>\n<li>Unless you have the requisite skills to threat hunt and remediate, the tools you try and use yourself can be counter-productive and create more noise behind which the attackers could hide. Do you have the skills?<\/li>\n<li>Even if you have the in-house skills to deploy EDR\/XDR solutions, the mean time to detect and respond (MTTD &amp; MTTR) are going to be hundreds of times longer than a third-party vendor can achieve (i.e., <a href=\"https:\/\/www.eset.com\/us\/business\/services\/managed-detection-and-response\/\">ESET \u2018s MTTD &lt; 1 minute; MTTR &lt; 6 minutes<\/a>). Do you know what your own MTTD and MTTR times are?<\/li>\n<li>It\u2019s incredibly expensive to build the necessary SOC and provide 24\/7\/365 monitoring \u2013 for most companies this is prohibitive. Do you have the time (and money) to build and staff a SOC?<\/li>\n<li>MDR services, via MSPs and MSSPs, can be activated for ANY size of organisation \u2013 from one seat\/employee up.<\/li>\n<\/ul>\n<h2>References:<\/h2>\n<ul type=\"disc\">\n<li><em>\u201cSchr\u00f6dinger\u2019s Cat in Cybersecurity: The Paradox of Uncertainty\u201d<\/em> \u2013 compares vulnerabilities to the cat\u2019s fate, stressing proactive monitoring. <a href=\"https:\/\/www.linkedin.com\/pulse\/schr%C3%B6dingers-cat-cybersecurity-paradox-uncertainty-jackson-jaikar--7wfgc\">[linkedin.com]<\/a><\/li>\n<li><em>\u201cSchr\u00f6dinger\u2019s Breach\u201d<\/em> \u2013 highlights dwell time and the illusion of security until proven otherwise. <a href=\"https:\/\/advantage.nz\/schrodingers-breach-the-uncertainty-principle-in-cybersecurity\/\">[advantage.nz]<\/a><\/li>\n<li><em>Cyber Strategy Institute<\/em> \u2013 uses the analogy to explain trust and risk as quantum-like dual states. <a href=\"https:\/\/cyberstrategyinstitute.com\/your-security-tools-are-lying-to-you-what-happens-when-threats-go-unobserved-schrodinger-cat-paradox-within-cybersecurity\/\">[cyberstrat&#8230;titute.com]<\/a><\/li>\n<\/ul>\n<p class=\"wls-source\"><a href=\"https:\/\/www.welivesecurity.com\/en\/business-security\/locks-socs-cat-box-what-schrodinger-can-teach-us-about-cybersecurity\/\" rel=\"nofollow noopener\" target=\"_blank\">Read the full analysis on WeLiveSecurity \u2192<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you don\u2019t look inside your environment, you can\u2019t know its true state \u2013 and attackers count on that<\/p>\n","protected":false},"author":5,"featured_media":8870,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2879],"tags":[],"class_list":["post-8866","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-security"],"acf":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/posts\/8866","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/comments?post=8866"}],"version-history":[{"count":1,"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/posts\/8866\/revisions"}],"predecessor-version":[{"id":9582,"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/posts\/8866\/revisions\/9582"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/media\/8870"}],"wp:attachment":[{"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/media?parent=8866"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/categories?post=8866"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.eset.ee\/et\/en\/wp-json\/wp\/v2\/tags?post=8866"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}