DSS

DSS 2026 / Day 2 / Pearl Hall

The Missing Certification: What Web3 Can Gain from Standards

Suryansh Singh

15:35 · Recording

Watch on YouTube ↗Open recording viewerOriginal programme entry
Download plain textDownload timestamped JSON

Source: YouTube automatic caption track · Exported 2026-11-16. Timestamps link to the source video. Cue end times were not supplied.

Transcript

0:01Hello guys.

0:04I'm Suryansh Singh.

0:07I'm a security researcher at Open

0:09Zeppelin.

0:10I also go by 0x Monsoon on X. Maybe you

0:13know me by my pseudonym. And today I'm

0:16going to see

0:17I'm today I'm going to speak about

0:20standards, how they work in different

0:22industries,

0:23what kind of standards we need in Web

0:25three and how they can help us.

0:31So

0:33let's first start with what a standard

0:35is

0:36and why a standard is needed

0:38in let's say any industry.

0:41So

0:43a standard in my opinion can be you know

0:46defined in three ways like it has three

0:48jobs.

0:49First, it sets a floor for something.

0:54Like

0:56for a security standard, it would set a

0:58certain floor

1:00about what security measures your

1:02project or your software

1:05or your processes need to have to

1:07qualify.

1:08Secondly,

1:10a lot of industries

1:13are very technical

1:14and they may not make a lot of sense to

1:16people outside the industry. So for for

1:19someone who works in software like the

1:21aviation industry doesn't make a lot of

1:23sense to me and it would be vice versa.

1:26So it needs to send a signal

1:28about what it is actually certifying to

1:31people who are outside the industry.

1:34So it serves as a signal.

1:37Third,

1:38it also serves as a memory

1:40for what the industry has learned. So

1:43like every newcomer doesn't need to

1:45re-derive all the best practices and

1:48avoid all the pitfalls

1:50for things that other players in the

1:52space have already through trial and

1:54error found out.

1:58So

2:00that is a standard was. So, what

2:04is a good standard in my opinion?

2:07So, a good standard does not

2:11give qualities

2:14to the work that has been assessed. It

2:16wouldn't say, let's say a software is

2:18secure

2:19or it wouldn't say that

2:22an airplane

2:24can never go down.

2:26Right? So, it would like

2:28give you very specific claims and it

2:31would tell you like how it has been

2:33reached and how that has been assessed.

2:36It wouldn't claim that every the

2:38assessor has like assessed everything

2:40that is about the thing it's assessing

2:43and it would also give

2:47like when the assessment was done, for

2:49how long it is valid

2:51and it wouldn't

2:54try to claim like once anything has a

2:56certain certification that it's good for

2:58life.

3:00So,

3:01even in the tech industry, I

3:03I think like PCI DSS is a good security

3:06standard

3:07that a lot of you may be familiar with.

3:11So, if you're not, it's basically a

3:13standard for the payments industry that

3:15deals

3:16with payments using credit cards and

3:17debit cards.

3:19So,

3:20in that any merchant or any gateway that

3:25is processing payments using credit

3:27cards

3:28has a certain standard of checklist of

3:32processes

3:34of

3:35how it assesses vendors and how how it

3:38gives permissions to everyone in the

3:39company who can

3:41gain access access to user data

3:45and

3:48there's a certified assessor

3:51who'll come and who'll look at the

3:53complete system. They'll scope it out

3:56and

3:57see if

3:59the entire system meets those standards

4:03or those points or not

4:05and then it would give them a PCI DSS

4:07compliance certificate and which is

4:10valid for a certain number

4:13or certain amount of time.

4:16So let's discuss some certificates in

4:19detail in in other industries like I

4:20gave example of one. Let's go through

4:23two or three quickly and then I'll come

4:24to

4:26Web 3 and how

4:30standards can help in our industry.

4:33So

4:35when the jet

4:36engine age began in the 1940s and 50s

4:41there were almost like 40 fatal

4:43accidents per million flights.

4:47Right now the number is less than 0.05.

4:51So what happened was

4:54it

4:55was regulated by lawmakers that anytime

4:58something

5:00would fly

5:01before that it would need an air

5:03worthiness certificate from the

5:05regulator

5:06and

5:08in that there were a lot of best

5:10practices, things you cannot do, types

5:12of designs you can have. So all of those

5:14things were required and this

5:16certification is for a design.

5:19So you need to get the design approved

5:21then you can actually build it and then

5:23there'll there be another there'll be

5:26more tests.

5:28So this

5:31also serves as a really good

5:34example of what a memory is because

5:35every time something goes wrong in a

5:37flight there's a fatal or near fatal

5:39accident

5:41there's a big investigation that happens

5:44and all of this conclusions are actually

5:46added to the standard

5:49and then all the previous aircrafts that

5:51were certified needs to be recertified

5:54and any new aircraft would actually need

5:56to have the certification

5:58so that it's ensured that those same

6:00problems aren't

6:02in the other aircrafts.

6:07Um,

6:08during the age of maritime shipping that

6:11when it was booming in the 1500s, 1600s

6:14and so on.

6:16Um,

6:18at that point

6:20there was

6:21no quick communication systems.

6:24So anytime a voyage went whether it

6:28actually was successful

6:30you would only know when it came back.

6:33So it would take a few months, sometimes

6:35maybe even years to understand that. And

6:38there were

6:40companies and people who were invested

6:42investing in these voyages, a lot of

6:44lots of big sums of money.

6:46And they wanted to understand like what

6:48are we actually

6:51uh investing in.

6:53And to protect themselves they wanted

6:55insurance.

6:57But uh to get insurance the insurers

7:00needed to understand like how

7:03well built a ship is.

7:06So basically

7:07uh

7:08there was a society called a registered

7:09society and started it at a coffee house

7:11in London.

7:13And they started asking

7:17uh all of these

7:19uh like investors who wanted to get

7:21their voyages insured

7:23to get like hull certificates. So

7:26basically uh

7:27team of experts would come in, they

7:29would

7:30um go through

7:32the ship, check its hull, check its

7:33other things.

7:35And it would

7:37give them a certificate of how good it

7:39is. And on based of that the insurers

7:42would underwrite it and set the premiums

7:43and so on.

7:45So in this case there's no global

7:47regulator, there's no entity that would

7:49fine you.

7:50But here

7:52the forcing function was

7:54you need you needed to have a hull

7:56certificate to

7:58get

8:00insurance.

8:02And the example is FIPS 140 which is uh

8:06standard by the US government. Anytime

8:08the US government or any of its agencies

8:10want to buy

8:13any software that has a new

8:16encryption system,

8:19they basically have to go through

8:21through the standard.

8:23It takes a while to get certified

8:27and implementation is usually checked by

8:29experts and then it's also put on a

8:31public list for a year or two where

8:34anyone can break it.

8:36So basically here it's this

8:40certification is forced by the buyer

8:41because if we don't have it, the US

8:43government or its agencies cannot buy

8:45your software by law.

8:48So we we went through like three regimes

8:51and all of them were attesting different

8:54things for aviation was a design, for

8:55shipping it was a vessel,

8:57for crypto modules it's an

8:58implementation.

9:00You have different forcing functions.

9:02Sometimes it's insurers, sometimes it's

9:04regulators, sometimes it's buyers.

9:07So Web3 is also writing its flows.

9:10So we have a few nascent standards in

9:12Web3 already.

9:14So let's go through

9:16the ones we have and what the standards

9:18are for and then maybe we can discuss

9:21like

9:22what are the forcing functions that Web3

9:23has right now or can have in the future.

9:28[snorts] So let's first go through CCSS.

9:30It's a standard for custody basically.

9:33Think about any centralized exchanges,

9:35think about custodians, think about

9:39it can also also apply to self-custody.

9:42Think about there are a lot of digital

9:44asset trust fund trust

9:46funds that are listing on the exchanges

9:48now. They are they are custodying

9:50crypto. So it's it's for all of them.

9:53So it basically deals with how key

9:55material is generated, stored, accessed,

9:58used

10:00and who can actually

10:04like who are the people who have access

10:05to it, how like are their background

10:08background verified or not,

10:10do they undergo constant training or

10:12not, like what is the incident response

10:15framework that they have. So it's a it's

10:18a really big checklist and

10:21they have three levels. You could be

10:23certified at level one or two or three

10:26and the governing body is C four

10:29which maintains the standard and you

10:31need certified auditor, a certified CCSS

10:34auditor that can come and scope out your

10:36system and go through the checklist and

10:38gather evidence and if you pass all of

10:41them they can give you

10:44certificate from level one to three if

10:46you qualify otherwise you won't get one.

10:49So as I said there are three levels but

10:52you only qualify for the for the lowest

10:53level. So there are different aspects.

10:56So let's imagine if you qualified for

10:59level three in all but only level one in

11:03one of the aspects, the highest

11:05certificate level that you can you can

11:07get is level one

11:09then because in security and especially

11:12in custody your weakest link always gets

11:15you.

11:16So no matter how strong the other things

11:18are

11:19if you're lacking in one place that's

11:21probably

11:22the one that will get exploited.

11:26And it's supposed to be used in

11:28conjunction with other standards like

11:30you can also have ISO 27001 SOC two PCI

11:34DSS whatever you deal with like whatever

11:36applies to your system. If you also do

11:38any kind of custody then CCSS applies

11:41and you should probably get certified

11:43for it. There are other standards

11:46that you could probably use in

11:48instead of this. So

11:50like any CCSS certification would

11:52basically

11:54say like the system was assessed by a

11:57certified auditor

11:59and it would tell about like what were

12:01the various aspects that were met at

12:05what levels and what the scope of the

12:07system was

12:09and when it needs to be recertified.

12:12It would never claim whether there's

12:14contract logic that's correct because

12:16that's not in scope or the system is

12:19secure because that's not the point.

12:21The point is like enforcing a floor.

12:26The security alliance also publishes two

12:28different things. One is seal

12:30frameworks, the other is seal

12:31certifications. Seal frameworks is

12:33basically the memory

12:35where all the good practices

12:38and all the pitfalls are stored anytime

12:40time a hack happens,

12:42if anything could be added, learned and

12:44added from there, it would be added to

12:46the frameworks.

12:47You can read them, you can self-assess

12:49yourself. Seal certifications are where

12:52basically a certified auditor who

12:54understands the standards will come and

12:56look at your system

12:58and would assess it

13:00given like whatever thing

13:03you choose to be assessed by because

13:04even in

13:05the frameworks and certifications, they

13:07have a lot of sub modules.

13:10And this is point in time

13:12and usually your auditor will give you a

13:16recertification date if you're getting a

13:18seal certification.

13:20And you'll get a badge which can also

13:22checked on the blockchain using the

13:24Ethereum attestation service.

13:27So

13:28seal certifications have six modules.

13:31So you can choose to be assessed for one

13:34or multiple given which one supply to

13:37you or which signal do you want to give

13:39to let say

13:41to your stakeholders.

13:43There are so

13:45naming them one by one, there's multi

13:46seg ops, treasury ops, incident

13:48response, DevOps and infrastructure, DNS

13:51and registrar and identity and accounts.

13:54For any blockchain or web three project,

13:57multiple of these would apply but you

13:59don't need to get all of them at once.

14:01You can get yourself

14:04ready for one or two at a time

14:06and self-assess yourself and if you

14:10find that you're ready, you can get them

14:11one by one

14:13and

14:16would trade the

14:17to your stakeholders about where you

14:19stand

14:21as far as security is concerned.

14:23Seal is also very similar to CCSS in

14:26that way that

14:28it would only the the signal only says

14:30like

14:32the system was

14:33assessed by a certified auditor

14:36and it will give you the scope and what

14:41modules were in were you assessed

14:42against. It will never say that you are

14:44secure or any code was audited or the

14:47evidence is public because it's not.

14:51So

14:53flows already exist in web three.

14:56We need [snorts] to understand like what

14:57forcing functions we have because right

15:00now we don't have any. No regulators

15:02asking us for certifications.

15:05Whenever like a DAT is listed on the

15:07stock market we aren't asked for any.

15:10Investors probably just only ask for

15:11smart contract audits.

15:13So we need a regime where people other

15:16than the assessed party and the assessor

15:18actually

15:20cares whether you have a standard or

15:22not.

15:23And

15:24that's it from my side and hopefully

15:27we'll have this kind of regime soon

15:29where when more awareness about

15:30standards grow.

15:32Thank you.

Source and accuracy details

Source export SHA256: 8f56dfb216bba869bcadbcec63c1fa5d1f330d82258c8ea958197301916aa7c1