DSS 2026 — One Year Later: Surviving the SOC 2 Type 2 Observation Window in DeFi Roxanne Bartnos Source video: https://www.youtube.com/watch?v=vDE3hQERIKE Automatic captions — not human-reviewed. Complete spoken-audio coverage is unverified. Source language tag: en (English). Source export SHA256: 6ac21583a96e8236ee084e28826f5f1d1c4e61b5427953fcff12067492b24b6a [0:01] Hi everybody. I'm Roxanne Bodnos from [0:04] Zero Shadow. I head up risk and security [0:07] management [0:09] focusing more on the proactive security [0:12] side at Zero Shadow. [0:15] So [0:16] I was supposed to be speaking on with my [0:19] client [0:20] and Pierre Yovan from 1 inch. [0:22] Unfortunately, he wasn't able to make [0:24] it, so I will be taking over. [0:28] So we will be focusing on [0:31] assurance, SOC 2, ISO 27001 [0:36] and and how it works in terms of the [0:39] framework that Zero Shadow has [0:42] developed, security risk management. [0:46] So when a business achieves ISO 27001 or [0:50] completes its SOC 2 audit, [0:53] it's an important milestone. [0:57] But what happens next? [1:00] What happens the next day, the next [1:01] week, the next month? [1:03] The risks are still there. [1:05] The business is still changing and [1:07] people still have to operate those [1:09] controls. [1:10] That is what I want to talk about today, [1:13] security risk management or SRM, a [1:16] security risk management framework that [1:18] Zero Shadow has developed. [1:21] And I want to talk about how our [1:22] partnership with 1 inch developed from [1:25] understanding their exposure into [1:27] embedding security in the way they work. [1:40] Right. So there's been a lot of trending [1:42] posts on LinkedIn regarding Binance [1:45] um and I thought that Binance the [1:48] Binance incident brings this [1:49] conversation into focus. [1:52] Um here is an organization that has [1:54] publicly announced [1:56] SOC 2 Type 2 and ISO credentials and has [2:00] reported a serious security incident. [2:05] That does not mean the standards are [2:08] worthless or that the incident proves [2:10] Binance treated compliance as a [2:11] checkbox. [2:13] What it does remind us is that insurance [2:16] or assurance cannot guarantee that an [2:19] organization will never get breached. It [2:22] provides confidence about specified [2:25] aspects of a program. It cannot remove [2:28] every exposure or anticipate every [2:31] change. [2:33] The problem [2:34] for any organization [2:39] is achieving [2:41] or the problem for any organization is [2:43] when achieving the report becomes the [2:45] objective. So they work towards SOC 2 [2:48] attestation or their ISO 27001 [2:52] certificate and they think, hey, the [2:54] job's done. [2:56] But this is where the work behind then [2:58] loses attention afterwards. [3:00] A control still needs to operate when [3:03] someone joins, when application changes, [3:06] or when an unusual transaction appears. [3:09] That is the connection between SRM. [3:13] We keep asking what could hurt the [3:16] business, whether our response is [3:18] working, and whether our people are [3:21] prepared. [3:22] So let me bring that back to how the [3:25] journey with 1 inch started. [3:32] The first step that we took with 1 inch [3:35] with the partnership was developing a [3:37] shared understanding of 1 inches risk [3:40] exposure. [3:42] Before we could build a useful strategy, [3:45] we needed to understand where the [3:48] attention was required. [3:50] Now that meant looking beyond a list of [3:53] technical controls [3:55] because technology is just part of it. [3:57] The systems, access, and infrastructure [4:00] that supports the business, that's just [4:02] a a single part. [4:04] But also what we need to understand is [4:06] who operates those systems, how [4:09] ownership works, and what happens when [4:11] an issue needs a decision. [4:14] Then there is the operational picture. [4:18] What visibility does the organization [4:20] have? [4:21] How do you or how do concerns reach the [4:24] right people? [4:25] What would happen if a routine issue [4:29] became an incident? [4:31] The assessment that we did with 1 inch [4:33] gave us a starting point for those [4:35] conversations. [4:37] It helped us move from a long list of [4:41] possible improvements to a shared view [4:43] of what matters most. [4:47] That was the foundation of our journey. [4:49] Understanding the exposure, recognizing [4:52] the gaps, and agree where to act. The [4:54] security strategy could then develop [4:58] around the realities of the business [5:00] with a clear reason behind the work we [5:03] were asking people to do. [5:11] Sorry, I think I need to go one back. [5:18] All right, so [5:20] once we understood the exposure, we then [5:23] started prioritizing. [5:25] We knew we could not treat every gap as [5:28] equally urgent, and completing the [5:30] easiest tasks would not necessarily [5:33] address the most important risks. [5:36] We focused attention on the areas that [5:39] had the greatest potential to impact the [5:41] business. Then worked through how those [5:44] risks could be mitigated. That meant [5:47] agreeing what needed to change, who [5:50] could make it happen, and how would we [5:53] know the action has addressed the risks [5:55] associated with that control. [5:58] Now as the work progressed, the strategy [6:01] became more informed. We were able to [6:04] connect [6:05] immediate improvements to the longer [6:06] term direction, adding value right from [6:09] the start, [6:10] rather than dealing with each [6:12] requirement as isolated tasks. So we [6:15] removed the siloed approach and we took [6:17] a holistic approach. [6:19] In 1 inch's own account, we saw the [6:21] operational areas that needed attention. [6:24] Um software as a service, access [6:26] removal, cloud resilience and [6:28] configuration, [6:30] um endpoint enforcement and clearer [6:32] control on ownership across the [6:35] business. Now these are examples from [6:37] their journey. [6:39] This is SRM in practice. This is what [6:42] security risk management does. The [6:44] exposure gives us the reason to act. [6:47] Prioritization gives us the order. [6:51] Ownership gives us a way to get the work [6:53] done. But even a well-designed technical [6:57] team or technical control depends on the [7:00] people expected to run it. [7:08] Right. So [7:11] this is the strongest example in 1 [7:14] inch's journey. [7:16] Policy acknowledgement moved from 47% to [7:19] 100% of employees in scope. [7:22] The interesting part is what changed [7:24] underneath that number. [7:26] When the process relied on Slack [7:28] reminders and goodwill, people still had [7:31] competing priorities. [7:34] Once it became systematic, the [7:36] organization had a clearer way of making [7:39] the task happen. [7:41] There was one source of truth, monthly [7:43] reconciliations between HR and [7:46] compliance records helped keep the [7:47] population accurate. But the 1 inch team [7:51] built automated nudges. They named [7:53] owners and leadership escalation meant [7:56] outstanding actions had somewhere to go. [8:02] That is how 1 inch started changing [8:03] habits. They started changing culture. [8:06] They made their expectation clear, made [8:09] the action part of the routine and gave [8:11] people the support and accountability to [8:14] follow through. [8:16] Acknowledging a policy does not on its [8:18] own prove that someone understands it or [8:22] behaves securely, but the example shown [8:25] shows how an incomplete process became a [8:28] repeatable process. [8:30] The same thinking applies to the people [8:32] running access reviews, approving [8:34] changes, or reporting incidents. The [8:36] first step is intent, understanding the [8:38] intent of the organization. [8:41] Yvonne and the broader One H team [8:43] deserve the credit for embedding that [8:45] change. Zero Shadow guided and [8:48] challenged the program, but their [8:51] leadership and teams inside the business [8:53] had to make it work. [9:01] So [9:03] we know that preparedness starts with [9:05] policy acknowledgments, understanding [9:07] the intent of the organization. So how [9:10] do we take this further? [9:13] Preparedness is where we look at whether [9:16] people can act when the situation stops [9:19] being routine. [9:20] Having a document available is only part [9:22] of that. [9:24] We need to ask [9:25] can people recognize the the signals [9:28] that matter? [9:30] Do they understand what needs to be [9:31] reported and where to raise it? [9:34] Once something is reported, who can make [9:37] the decisions? The team needs to [9:39] understand its authority, escalation [9:42] paths, and the actions it can take to [9:45] contain the problem. [9:47] Then we need to practice, and exercise [9:50] helps reveal whether the people [9:52] understand the responsibilities and [9:54] whether the response works [9:58] with the systems and dependencies [10:00] dependencies they actually use. [10:03] Finally, we need to learn findings from [10:06] exercises, audits, and real incidents [10:09] should influence priorities and [10:11] controls. [10:12] Otherwise, we keep producing reports [10:14] while repeating the same weaknesses. [10:17] Now, those are the SRM operating [10:19] principles. The point is that [10:22] preparedness has to connect the plan to [10:25] the people expected to act. [10:27] Your people are your biggest assets, but [10:29] also can be your greatest weakness. [10:32] Their understanding, judgment, and [10:34] ability to work together are part of the [10:36] organization's [10:38] resilience. [10:42] So, let's talk about internal audits [10:46] and how expectation met operating [10:50] reality. [10:52] Zero Shadow conducted the first internal [10:54] audit for [10:56] 1 inch, bringing into focus 1 inch's [10:58] expectation versus the operating [11:00] reality. [11:02] The observation window that we had [11:05] brought those lessons into focus. [11:07] These are the themes that came through [11:09] in 1 inch's own account. [11:12] One's expectation [11:14] One expectation was that you can fix the [11:17] gaps before the audit. The reality was [11:19] that the controls still need to operate [11:22] throughout the period [11:24] cuz when a failure appears, someone [11:26] needs to see it, understand it, and [11:29] understand its significance in order to [11:31] act. [11:33] Another expectation that the team had is [11:36] that security will drive compliance, [11:39] but security cannot perform every [11:41] control across HR, [11:43] engineering, and the rest of the [11:45] business. Each team needs to understand [11:48] their own part [11:50] in the ownership and what they [11:52] contribute to security um in the [11:55] organization. [11:56] Then there's the assumption that strong [11:59] technical controls will be enough, [12:02] but those controls still depend on [12:04] people making the right decisions and [12:07] performing the right actions [12:09] consistently. [12:11] This is what embedding [12:13] security into your organization means. [12:16] The control becomes part of how the [12:18] organization works and the evidence [12:20] reflects that it works. [12:22] That was an important shift in the [12:24] journey. [12:25] Less dependence on someone chasing an [12:27] audit task and more ownership of an [12:30] ongoing responsibility. [12:35] So the assurance milestones do matter in [12:38] every organization. One Inch achieved [12:40] ISO 27001 certification in 2025, [12:44] maintained it through its 2026 [12:46] surveillance audit with zero [12:47] non-conformities and reached its SOC 2 [12:50] milestone in 2026. [12:53] Zero Shadow supported that work through [12:56] activities including the internal audit, [12:58] head of surveillance, and participation [13:00] in auditor sessions, but the outcome [13:03] depended on the program the One Inch [13:05] team was operating. [13:07] It is also important to be precise on [13:10] what is SOC 2 and what is ISO 27001 [13:13] about. [13:14] SOC 2 Type 2 examines control design and [13:17] operating effectiveness over a defined [13:20] scope and period. It produces an [13:22] attestation report, whilst ISO 27001 [13:26] addresses a management system that [13:28] already includes risk management and [13:30] continual improvement. [13:32] So security risk management belongs [13:34] within that picture. It keeps the [13:37] underlying disciplines active as the [13:40] business changes. The issue with the [13:42] tick box approach is allowing the report [13:44] to become the finish line. [13:46] For us, the more useful question is, can [13:49] the organization sustain the work that [13:51] supports the assurance and can its [13:54] people respond when something happens [13:57] despite the controls? [14:01] So where is One Inch today in their [14:02] journey? Their journey currently [14:04] reflects an ongoing [14:07] proactive approach to security. They [14:09] have reached important assurance [14:10] milestones and made parts of their [14:12] operating environment more systematic. [14:15] The work continues as the organization [14:17] changes. [14:18] Our partnership extends through [14:20] assurance support and operational [14:21] security work. [14:23] The broader SRM responsibility remains [14:26] active, continuously reviewing risk [14:29] exposure, assessing whether the [14:32] treatments we have in place are working [14:33] and respond when risks emerge. That [14:37] requires ownership inside One Inch [14:39] alongside advice and challenge from Zero [14:42] Shadow. [14:43] Now this also supports the business [14:45] conversation. A TradFi partner wants to [14:48] understand who is accountable, how risk [14:51] is managed, and what evidence supports [14:53] the answer. [14:54] A functioning program gives One Inch a [14:57] stronger basis for the discussion. It [14:59] also creates a foundation for assessing [15:02] the additional requirements of new and [15:04] emerging markets. That does not [15:06] guarantee market access or mean a breach [15:08] cannot happen. [15:10] It means the organization is better [15:12] placed to explain and manage its [15:14] exposure. [15:15] You can see the value of that ongoing [15:18] work in how One Inch describes the [15:20] payoff. [15:23] So this is what they look at it from [15:25] this perspective. Their due diligence [15:27] conversation became easier to support [15:30] with an established certificate, [15:32] attestation report, and policy pack. [15:35] Structured vendor management helped with [15:37] assess suppliers and respond when others [15:40] assessed them. They also described [15:43] greater confidence from investors and [15:45] leadership and an ability to strengthen [15:47] their posture while retaining their DeFi [15:50] operating culture. [15:51] That is the commercial connection to [15:53] SRM. A functioning program gives the [15:56] business a more credible way to explain [15:58] its risk management while helping the [16:01] team operate more consistently. So let [16:03] me close with the four lessons from [16:05] their journey. [16:12] First, SOC 2 Type 2 adds examination of [16:14] operating effectiveness over the period. [16:17] The important idea for our discussion is [16:19] that the controls need to work as part [16:21] of normal operations. The broad [16:24] statement about 2026 losses is one [16:26] inches framing rather than a claim that [16:29] an audit predicts or prevents every [16:31] exploit. [16:32] Second, compliance can help expose [16:34] weaknesses and establish useful habits [16:37] when the work stays connected to the [16:39] underlying risk. [16:40] Third, culture needs visible ownership. [16:43] The policy acknowledgement example shows [16:46] the difference a systematic approach, [16:49] automation, and leadership escalation [16:51] can make. [16:52] Finally, a DeFi business can retain its [16:55] operating culture while developing the [16:58] assurance its institutional partners [17:00] need. [17:01] Bring that back to our starting point. [17:03] The journey began with understanding [17:04] exposure and prioritizing the gaps. It [17:08] developed through strategy, controls, [17:10] and people's habits with assurance [17:12] marking progress along the way. I will [17:15] end with saying assurance is a [17:17] milestone. Security risk management is [17:20] what the organization does every day. [17:23] Thank you.