Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
92 changes: 76 additions & 16 deletions docs/pages/certs/certified-partners.mdx
Original file line number Diff line number Diff line change
@@ -1,39 +1,99 @@
---
title: "Certified Auditors | Security Alliance"
description: "Become a SEAL-certified auditor: demonstrate blockchain security expertise, conduct audits against SEAL Certification Framework, and issue on-chain attestations."
title: "Auditor Accreditation | Security Alliance"
description: "Become a SEAL-accredited auditor: a supervised first engagement and authorization to assess protocols against the SEAL Certification Framework and issue on-chain attestations."
tags:
- SEAL/Initiative
- Certifications
auditors:

contributors:
- role: wrote
users: [isaac]
---

import { TagList, AttributionList, TagProvider, TagFilter, ContributeFooter } from '../../../components'

<TagProvider>
<TagFilter />

# Certified Partners
# Auditor Accreditation

<TagList tags={frontmatter.tags} />
<AttributionList contributors={frontmatter.contributors} />

## Current Status: Request for Qualifications (RFQ)
SEAL accredits third-party auditing firms to assess protocols against the SEAL Certification Framework and issue on-chain attestations. The framework is stable and has been validated through engagements with major DeFi protocols, staking operations, and treasury management teams, and accreditation is open now.

Check failure on line 22 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:22:121 MD013/line-length Line length [Expected: 120; Actual: 311] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

## How Accreditation Works

Accreditation starts with an intro call about your firm: what you do, your experience and track record, and why you want to be involved. If it is a good fit, we share the accreditation agreement, and you loop us in when you are ready for your first engagement.

Check failure on line 26 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:26:121 MD013/line-length Line length [Expected: 120; Actual: 260] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

Your first client assessment is supervised by SEAL across scoping, evidence review, gap analysis, and certification issuance. We are looking at how you apply the standard, not collecting your client's data. Once we are confident in your team's judgment, you operate independently.

Check failure on line 28 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:28:121 MD013/line-length Line length [Expected: 120; Actual: 280] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

Fees and terms are set out in the accreditation agreement, which will be shared after our initial call.

## What's Involved

A full-suite assessment spans a few weeks, but it is not weeks of full-time work. Most of the time is spent coordinating with the client on evidence collection; the focused assessment work is modest. Assessments cover up to six modules (Multisig Ops, Treasury Ops, Incident Response, DevOps & Infrastructure, DNS & Registrar, and Identity & Accounts), and scoping determines which apply to a given protocol.

Check failure on line 34 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:34:121 MD013/line-length Line length [Expected: 120; Actual: 407] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

You do not need to share confidential client information with SEAL. We are observing how you assess, not collecting sensitive client data. Redacted reports or discussions about your process are sufficient, and we are happy to sign an NDA where you or your client requests one.

Check failure on line 36 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:36:121 MD013/line-length Line length [Expected: 120; Actual: 276] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

## Getting Started

If your firm is interested, [fill out the form](https://securityalliance.typeform.com/CertsAuditor). We will then have an initial call to discuss the process, your background, and how everything works.

Check failure on line 40 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:40:121 MD013/line-length Line length [Expected: 120; Actual: 201] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

## FAQ

<details>
<summary>What does accreditation cost?</summary>

Specific fees and timing are set out in the accreditation agreement, which will be shared after our initial call.

</details>
<details>
<summary>How does accreditation start?</summary>

An intro call where you tell us about your firm, experience, track record, and why you want to be involved. If it is a fit, we share the accreditation agreement and you loop us in when you are ready for your first engagement.

Check failure on line 53 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:53:121 MD013/line-length Line length [Expected: 120; Actual: 225] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

</details>
<details>
<summary>What does the supervised first engagement involve?</summary>

We check in at about five points across the engagement: scoping, where you set your evidence bar, how you deliver gap feedback to the client, how you verify remediation, and final assessment and delivery. Expect a few one-hour calls, with us on standby in between.

Check failure on line 59 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:59:121 MD013/line-length Line length [Expected: 120; Actual: 264] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

</details>
<details>
<summary>Do we have to share confidential client information with SEAL?</summary>

No. Redacted reports or discussions about your process are enough. We are observing how you assess, not collecting sensitive client data, which can itself be a liability to store.

Check failure on line 65 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:65:121 MD013/line-length Line length [Expected: 120; Actual: 179] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

</details>
<details>
<summary>Can we or our client sign an NDA with SEAL?</summary>

Yes, as needed, as long as it does not restrict our ability to run the certifications initiative.

</details>
<details>
<summary>What counts as sufficient evidence?</summary>

Assessment is judgment-based. A documented interview where you confirmed how a control is handled can be sufficient on its own; you do not need to collect and store sensitive client artifacts to satisfy a control. You are evaluating whether a protocol's practices are adequate for its scale and risk.

Check failure on line 77 in docs/pages/certs/certified-partners.mdx

View workflow job for this annotation

GitHub Actions / lint

Line length

docs/pages/certs/certified-partners.mdx:77:121 MD013/line-length Line length [Expected: 120; Actual: 300] https://github.com/DavidAnson/markdownlint/blob/v0.40.0/doc/md013.md

</details>
<details>
<summary>How prescriptive are the controls?</summary>

SEAL Certifications is currently in the process of establishing our certified auditor partner program. We are actively
seeking qualified auditing firms to become authorized certification issuers.
They are a baseline you interpret against the client's maturity. Your job is to judge whether what they have is good enough for where they are. Exceptions are fine when they are justified and documented.

### Timeline
</details>
<details>
<summary>Can we use the controls outside a full certification?</summary>

- **Now - December 31st, 2025**: RFC Phase & Auditor RFQ Period
- **Q1 2026**: Begin issuing formal certifications with certified auditor partners
Yes. The same controls work for lighter engagements such as a gap analysis or ongoing retainer work.

## Becoming a Certified Auditor
</details>
<details>
<summary>How do we give feedback on the controls?</summary>

SEAL will work with a select group of third-party auditing firms to provide certification audits. SEAL-certified
auditors will demonstrate expertise in blockchain security and operational security practices, and will be authorized to
conduct audits against the SEAL Certification Framework and issue on-chain attestations.
Open an issue or pull request in the frameworks repo. Feedback from firms running real engagements is how the standard improves. See the [Contributing guide](/certs/contributions) for details.

If your firm is interested, please fill [out this form](https://securityalliance.typeform.com/CertsAuditor)
</details>

</TagProvider>