DSS 2026 — The Missing Certification: What Web3 Can Gain from Standards Suryansh Singh Source video: https://www.youtube.com/watch?v=VEYrHqznO_o Automatic captions — not human-reviewed. Complete spoken-audio coverage is unverified. Source language tag: en (English). Source export SHA256: 8f56dfb216bba869bcadbcec63c1fa5d1f330d82258c8ea958197301916aa7c1 [0:01] Hello guys. [0:04] I'm Suryansh Singh. [0:07] I'm a security researcher at Open [0:09] Zeppelin. [0:10] I also go by 0x Monsoon on X. Maybe you [0:13] know me by my pseudonym. And today I'm [0:16] going to see [0:17] I'm today I'm going to speak about [0:20] standards, how they work in different [0:22] industries, [0:23] what kind of standards we need in Web [0:25] three and how they can help us. [0:31] So [0:33] let's first start with what a standard [0:35] is [0:36] and why a standard is needed [0:38] in let's say any industry. [0:41] So [0:43] a standard in my opinion can be you know [0:46] defined in three ways like it has three [0:48] jobs. [0:49] First, it sets a floor for something. [0:54] Like [0:56] for a security standard, it would set a [0:58] certain floor [1:00] about what security measures your [1:02] project or your software [1:05] or your processes need to have to [1:07] qualify. [1:08] Secondly, [1:10] a lot of industries [1:13] are very technical [1:14] and they may not make a lot of sense to [1:16] people outside the industry. So for for [1:19] someone who works in software like the [1:21] aviation industry doesn't make a lot of [1:23] sense to me and it would be vice versa. [1:26] So it needs to send a signal [1:28] about what it is actually certifying to [1:31] people who are outside the industry. [1:34] So it serves as a signal. [1:37] Third, [1:38] it also serves as a memory [1:40] for what the industry has learned. So [1:43] like every newcomer doesn't need to [1:45] re-derive all the best practices and [1:48] avoid all the pitfalls [1:50] for things that other players in the [1:52] space have already through trial and [1:54] error found out. [1:58] So [2:00] that is a standard was. So, what [2:04] is a good standard in my opinion? [2:07] So, a good standard does not [2:11] give qualities [2:14] to the work that has been assessed. It [2:16] wouldn't say, let's say a software is [2:18] secure [2:19] or it wouldn't say that [2:22] an airplane [2:24] can never go down. [2:26] Right? So, it would like [2:28] give you very specific claims and it [2:31] would tell you like how it has been [2:33] reached and how that has been assessed. [2:36] It wouldn't claim that every the [2:38] assessor has like assessed everything [2:40] that is about the thing it's assessing [2:43] and it would also give [2:47] like when the assessment was done, for [2:49] how long it is valid [2:51] and it wouldn't [2:54] try to claim like once anything has a [2:56] certain certification that it's good for [2:58] life. [3:00] So, [3:01] even in the tech industry, I [3:03] I think like PCI DSS is a good security [3:06] standard [3:07] that a lot of you may be familiar with. [3:11] So, if you're not, it's basically a [3:13] standard for the payments industry that [3:15] deals [3:16] with payments using credit cards and [3:17] debit cards. [3:19] So, [3:20] in that any merchant or any gateway that [3:25] is processing payments using credit [3:27] cards [3:28] has a certain standard of checklist of [3:32] processes [3:34] of [3:35] how it assesses vendors and how how it [3:38] gives permissions to everyone in the [3:39] company who can [3:41] gain access access to user data [3:45] and [3:48] there's a certified assessor [3:51] who'll come and who'll look at the [3:53] complete system. They'll scope it out [3:56] and [3:57] see if [3:59] the entire system meets those standards [4:03] or those points or not [4:05] and then it would give them a PCI DSS [4:07] compliance certificate and which is [4:10] valid for a certain number [4:13] or certain amount of time. [4:16] So let's discuss some certificates in [4:19] detail in in other industries like I [4:20] gave example of one. Let's go through [4:23] two or three quickly and then I'll come [4:24] to [4:26] Web 3 and how [4:30] standards can help in our industry. [4:33] So [4:35] when the jet [4:36] engine age began in the 1940s and 50s [4:41] there were almost like 40 fatal [4:43] accidents per million flights. [4:47] Right now the number is less than 0.05. [4:51] So what happened was [4:54] it [4:55] was regulated by lawmakers that anytime [4:58] something [5:00] would fly [5:01] before that it would need an air [5:03] worthiness certificate from the [5:05] regulator [5:06] and [5:08] in that there were a lot of best [5:10] practices, things you cannot do, types [5:12] of designs you can have. So all of those [5:14] things were required and this [5:16] certification is for a design. [5:19] So you need to get the design approved [5:21] then you can actually build it and then [5:23] there'll there be another there'll be [5:26] more tests. [5:28] So this [5:31] also serves as a really good [5:34] example of what a memory is because [5:35] every time something goes wrong in a [5:37] flight there's a fatal or near fatal [5:39] accident [5:41] there's a big investigation that happens [5:44] and all of this conclusions are actually [5:46] added to the standard [5:49] and then all the previous aircrafts that [5:51] were certified needs to be recertified [5:54] and any new aircraft would actually need [5:56] to have the certification [5:58] so that it's ensured that those same [6:00] problems aren't [6:02] in the other aircrafts. [6:07] Um, [6:08] during the age of maritime shipping that [6:11] when it was booming in the 1500s, 1600s [6:14] and so on. [6:16] Um, [6:18] at that point [6:20] there was [6:21] no quick communication systems. [6:24] So anytime a voyage went whether it [6:28] actually was successful [6:30] you would only know when it came back. [6:33] So it would take a few months, sometimes [6:35] maybe even years to understand that. And [6:38] there were [6:40] companies and people who were invested [6:42] investing in these voyages, a lot of [6:44] lots of big sums of money. [6:46] And they wanted to understand like what [6:48] are we actually [6:51] uh investing in. [6:53] And to protect themselves they wanted [6:55] insurance. [6:57] But uh to get insurance the insurers [7:00] needed to understand like how [7:03] well built a ship is. [7:06] So basically [7:07] uh [7:08] there was a society called a registered [7:09] society and started it at a coffee house [7:11] in London. [7:13] And they started asking [7:17] uh all of these [7:19] uh like investors who wanted to get [7:21] their voyages insured [7:23] to get like hull certificates. So [7:26] basically uh [7:27] team of experts would come in, they [7:29] would [7:30] um go through [7:32] the ship, check its hull, check its [7:33] other things. [7:35] And it would [7:37] give them a certificate of how good it [7:39] is. And on based of that the insurers [7:42] would underwrite it and set the premiums [7:43] and so on. [7:45] So in this case there's no global [7:47] regulator, there's no entity that would [7:49] fine you. [7:50] But here [7:52] the forcing function was [7:54] you need you needed to have a hull [7:56] certificate to [7:58] get [8:00] insurance. [8:02] And the example is FIPS 140 which is uh [8:06] standard by the US government. Anytime [8:08] the US government or any of its agencies [8:10] want to buy [8:13] any software that has a new [8:16] encryption system, [8:19] they basically have to go through [8:21] through the standard. [8:23] It takes a while to get certified [8:27] and implementation is usually checked by [8:29] experts and then it's also put on a [8:31] public list for a year or two where [8:34] anyone can break it. [8:36] So basically here it's this [8:40] certification is forced by the buyer [8:41] because if we don't have it, the US [8:43] government or its agencies cannot buy [8:45] your software by law. [8:48] So we we went through like three regimes [8:51] and all of them were attesting different [8:54] things for aviation was a design, for [8:55] shipping it was a vessel, [8:57] for crypto modules it's an [8:58] implementation. [9:00] You have different forcing functions. [9:02] Sometimes it's insurers, sometimes it's [9:04] regulators, sometimes it's buyers. [9:07] So Web3 is also writing its flows. [9:10] So we have a few nascent standards in [9:12] Web3 already. [9:14] So let's go through [9:16] the ones we have and what the standards [9:18] are for and then maybe we can discuss [9:21] like [9:22] what are the forcing functions that Web3 [9:23] has right now or can have in the future. [9:28] [snorts] So let's first go through CCSS. [9:30] It's a standard for custody basically. [9:33] Think about any centralized exchanges, [9:35] think about custodians, think about [9:39] it can also also apply to self-custody. [9:42] Think about there are a lot of digital [9:44] asset trust fund trust [9:46] funds that are listing on the exchanges [9:48] now. They are they are custodying [9:50] crypto. So it's it's for all of them. [9:53] So it basically deals with how key [9:55] material is generated, stored, accessed, [9:58] used [10:00] and who can actually [10:04] like who are the people who have access [10:05] to it, how like are their background [10:08] background verified or not, [10:10] do they undergo constant training or [10:12] not, like what is the incident response [10:15] framework that they have. So it's a it's [10:18] a really big checklist and [10:21] they have three levels. You could be [10:23] certified at level one or two or three [10:26] and the governing body is C four [10:29] which maintains the standard and you [10:31] need certified auditor, a certified CCSS [10:34] auditor that can come and scope out your [10:36] system and go through the checklist and [10:38] gather evidence and if you pass all of [10:41] them they can give you [10:44] certificate from level one to three if [10:46] you qualify otherwise you won't get one. [10:49] So as I said there are three levels but [10:52] you only qualify for the for the lowest [10:53] level. So there are different aspects. [10:56] So let's imagine if you qualified for [10:59] level three in all but only level one in [11:03] one of the aspects, the highest [11:05] certificate level that you can you can [11:07] get is level one [11:09] then because in security and especially [11:12] in custody your weakest link always gets [11:15] you. [11:16] So no matter how strong the other things [11:18] are [11:19] if you're lacking in one place that's [11:21] probably [11:22] the one that will get exploited. [11:26] And it's supposed to be used in [11:28] conjunction with other standards like [11:30] you can also have ISO 27001 SOC two PCI [11:34] DSS whatever you deal with like whatever [11:36] applies to your system. If you also do [11:38] any kind of custody then CCSS applies [11:41] and you should probably get certified [11:43] for it. There are other standards [11:46] that you could probably use in [11:48] instead of this. So [11:50] like any CCSS certification would [11:52] basically [11:54] say like the system was assessed by a [11:57] certified auditor [11:59] and it would tell about like what were [12:01] the various aspects that were met at [12:05] what levels and what the scope of the [12:07] system was [12:09] and when it needs to be recertified. [12:12] It would never claim whether there's [12:14] contract logic that's correct because [12:16] that's not in scope or the system is [12:19] secure because that's not the point. [12:21] The point is like enforcing a floor. [12:26] The security alliance also publishes two [12:28] different things. One is seal [12:30] frameworks, the other is seal [12:31] certifications. Seal frameworks is [12:33] basically the memory [12:35] where all the good practices [12:38] and all the pitfalls are stored anytime [12:40] time a hack happens, [12:42] if anything could be added, learned and [12:44] added from there, it would be added to [12:46] the frameworks. [12:47] You can read them, you can self-assess [12:49] yourself. Seal certifications are where [12:52] basically a certified auditor who [12:54] understands the standards will come and [12:56] look at your system [12:58] and would assess it [13:00] given like whatever thing [13:03] you choose to be assessed by because [13:04] even in [13:05] the frameworks and certifications, they [13:07] have a lot of sub modules. [13:10] And this is point in time [13:12] and usually your auditor will give you a [13:16] recertification date if you're getting a [13:18] seal certification. [13:20] And you'll get a badge which can also [13:22] checked on the blockchain using the [13:24] Ethereum attestation service. [13:27] So [13:28] seal certifications have six modules. [13:31] So you can choose to be assessed for one [13:34] or multiple given which one supply to [13:37] you or which signal do you want to give [13:39] to let say [13:41] to your stakeholders. [13:43] There are so [13:45] naming them one by one, there's multi [13:46] seg ops, treasury ops, incident [13:48] response, DevOps and infrastructure, DNS [13:51] and registrar and identity and accounts. [13:54] For any blockchain or web three project, [13:57] multiple of these would apply but you [13:59] don't need to get all of them at once. [14:01] You can get yourself [14:04] ready for one or two at a time [14:06] and self-assess yourself and if you [14:10] find that you're ready, you can get them [14:11] one by one [14:13] and [14:16] would trade the [14:17] to your stakeholders about where you [14:19] stand [14:21] as far as security is concerned. [14:23] Seal is also very similar to CCSS in [14:26] that way that [14:28] it would only the the signal only says [14:30] like [14:32] the system was [14:33] assessed by a certified auditor [14:36] and it will give you the scope and what [14:41] modules were in were you assessed [14:42] against. It will never say that you are [14:44] secure or any code was audited or the [14:47] evidence is public because it's not. [14:51] So [14:53] flows already exist in web three. [14:56] We need [snorts] to understand like what [14:57] forcing functions we have because right [15:00] now we don't have any. No regulators [15:02] asking us for certifications. [15:05] Whenever like a DAT is listed on the [15:07] stock market we aren't asked for any. [15:10] Investors probably just only ask for [15:11] smart contract audits. [15:13] So we need a regime where people other [15:16] than the assessed party and the assessor [15:18] actually [15:20] cares whether you have a standard or [15:22] not. [15:23] And [15:24] that's it from my side and hopefully [15:27] we'll have this kind of regime soon [15:29] where when more awareness about [15:30] standards grow. [15:32] Thank you.