ChainPlus Cybersecurityno chain, no gain

Methodology

Methodology for Security Audits

Every ChainPlus audit follows the same five stages, so your team always knows what happens next and what we need from you.

  1. 01

    Before kick-off

    Scope, services and repository access are agreed.

    • ChainPlus scopes the audit
    • The client chooses which services the audit will include
    • The client defines the commit hash and provides access to the repository
    • The client provides technical specifications
  2. 02

    Kick-off

    Code walk-through and a shared channel with your team.

    • Joint meeting for a code walk-through
    • Creation of a joint communication channel
    • Definition of dates for the sync meetings
  3. 03

    Core Audit Stage

    Audit

    Deep technical review with continuous communication.

    • Our team analyzes the protocol and its use cases
    • We perform the technical audit and record every issue and point of attention
    • The code is checked against the technical specification
    • Frequent communication between both teams
  4. 04

    Re-audit

    You fix the findings, we verify every change.

    • We deliver the initial audit report
    • The client evaluates each finding and fixes the code where necessary
    • We receive the client's re-audit notes and review the fixes
    • The client's comments on each issue become part of the final report
  5. 05

    Final

    Final report delivered and validated together.

    • We create the final report and send it to the client
    • The client validates the report and flags any inconsistencies
    • The teams can run joint marketing campaigns to promote the protocol

Reports

Reports Your Team Can Act On

Every ChainPlus audit ends with a detailed report: an independent, third-party review of your code that explains each issue, its severity, and how to fix it, and records your team's response to every finding.

Prevents costly errors

Smart contracts often handle financial transactions or sensitive data, so any vulnerability could result in significant financial losses or data breaches. An audit identifies and addresses these issues before they become major problems.

Builds trust

In decentralized applications, trust is critical. A public audit report following best auditing practices increases users' and stakeholders' confidence in the project and its underlying technology.

Improves the code

Our reports also point out areas of improvement in the contract's design and code, helping keep it scalable, maintainable, and efficient, and reducing the risk of future vulnerabilities.

ChainPlus audit reports include the following sections:

  1. 01

    Executive Summary

    A high-level summary of the audit

  2. 02

    Assumptions

    The assumptions for the audit (when needed)

  3. 03

    Summary of Issues

    A table summarizing the identified issues

  4. 04

    System Overview

    A description of the protocol and its core functionalities

  5. 05

    Risk Rating Methodology

    The strategy used to rank the issues identified

  6. 06

    List of Issues

    An in-depth description of the issues found during the audit

  7. 07

    Documentation Evaluation

    Assessment of the documentation provided for the audit

  8. 08

    Client's Test Suite Output

    Execution and assessment of the test suite provided by the client

  9. 09

    Analysis from Automated Tools

    Findings detected by automated testing tools

Ready to secure your protocol?

Tell us about your project and get a scope and quote within 24 hours.

Request a quote