Skip to content
Client Focus

Client Focus solution

Smart Contract Guard 360

Smart contract assurance for institutions that must evidence control over on-chain systems: automated analysis, continuous compliance monitoring and reproducible verdicts, deployed inside your environment.

Proprietary detection model at the core, with a rules engine applying control frameworks

EVM including Hyperledger Besu, Solana, and Move-based chains

NIST CSF, ISO 27001, DORA and MiCA, plus your own control framework

Where every component runs

SCG360 is deployed in a client VPC or on-premises environment. Analysis, models and evidence stay inside that boundary; the Client Focus control plane receives metadata only.

SCG360 reference architectureInside the client environment, the trust boundary: intake, the proprietary detection model, supporting engines, the rules engine, the verdict and certificate, and the evidence store. Outside the boundary, the Client Focus control plane receives metadata only: hashes, verdicts and version identifiers.Client environmentVPC or on-premises, the trust boundaryIntakeRepo, address or bytecodeProprietary detection modelIn production in C'ROCSupporting enginesEVM and non-EVM toolchainsRules engineControls as executable rulesVerdict and certificateBound to the bytecode hashEvidence storeFindings, traces, version manifest, audit trailClient Focuscontrol planeHashes, verdicts andversion identifiers onlyMetadataonly

Inside the client boundary

Analysis engines, self-hosted models, contract code and the client control overlay operate within the client environment.

Metadata-only control plane

The Client Focus control plane processes only hashes, verdicts and version identifiers, never contract source or bytecode.

Boundary

Contract source, bytecode and model inference never leave the client boundary.

Four capabilities, one controlled process

One governed service across EVM and non-EVM networks: a proprietary detection model at the core, a rules engine that applies control frameworks, and established engines as supporting layers.

01

Automated contract analysis

Client Focus's proprietary detection model, in production in C'ROC and fine-tuned on labeled exploit patterns, analyzes contracts across EVM and non-EVM networks, supported by established engines for each chain family. Coverage includes contract vulnerabilities, upgradeable proxy patterns with storage-layout diffing, economic dependencies and governance attack paths.

02

Continuous compliance monitoring

A customized rules engine captures control definitions as executable rules and applies them during analysis, so findings map directly to NIST CSF, ISO 27001, DORA, MiCA, the OWASP Smart Contract Top 10 and the client's own framework. Changes to implementations, administrators, owners or guardians trigger reassessment.

03

AI-assisted threat modeling

Models inside the client environment propose business-logic, economic and access-control hypotheses. A hypothesis becomes a finding only on deterministic confirmation. AI drafts exploit scenarios and remediation guidance from confirmed findings, fixed to the analyzed bytecode hash.

04

Enterprise integration

REST APIs and CI/CD hooks connect analysis to the release process. Role-based access, an audit trail, portfolio views and exportable reports support engineering, risk and audit teams.

EVM chains and Solidity, including Hyperledger BesuSlither, Mythril, Foundry, Echidna
Solana, Rust and Anchor programsX-Ray, Sec3
Move-based chains such as Aptos and SuiMove Prover

The proprietary detection model runs across all chain families. Formal verification tools can be integrated for critical invariants. Chains in scope for an engagement are agreed and validated before go-live.

Testing economic failure paths

Oracle and price-manipulation risk spans dependencies and execution paths. SCG360 turns those dependencies into executable properties and keeps model suggestions separate from confirmed evidence.

  1. 01

    Map dependencies

    Trace price feeds, update authority and liquidity sources, and record assumptions about freshness, deviation limits and available liquidity.

  2. 02

    Propose hypotheses

    The detection model ranks candidate paths against known exploit signatures, including stale prices, thin-liquidity manipulation and cross-contract sequencing.

  3. 03

    Check invariants

    Each candidate becomes a testable property, such as collateral sufficiency or bounded payout, replayed and fuzzed against a pinned state snapshot.

  4. 04

    Confirm deterministically

    Only a reproducible invariant violation or rule-backed trace becomes a finding, recorded with the bytecode, state, inputs and tool versions.

Published detection figures for SCG360's contract-analysis scope await independent substantiation against a defined corpus.

From change to evidence

Analysis runs continuously across the release and monitoring cycle, producing versioned evidence at each change.

SCG360 compliance loopFive points on one line: trigger, scan, map and report, then reassessment when an upgrade or administrative change supersedes the certificate.01Trigger

A commit, release or on-chain event starts a review

02Scan

Engines analyze the contract in sandboxed runs

03Map

Confirmed results map to the control framework

04Report

Versioned evidence for engineering, risk and audit

On changeReassess

Upgrades and admin changes supersede the certificate

A verdict that can be reproduced

Rules determine the conformance verdict. AI informs investigation and explanation; the verdict remains rule-based.

How a reviewer reproduces a verdictFour steps: pin the inputs by content hash, re-run the analysis inside the client boundary, compare findings and verdict to the issued evidence, and confirm the certificate status in the registry.Step 1Pin inputs

Bytecode, state snapshot, ruleset and images, by content hash

Step 2Re-run

The client's team runs the same analysis in its own boundary

Step 3Compare

Findings and the rule-based verdict match the evidence

Step 4Confirm status

Valid, superseded or withdrawn in the status registry

Certificates bind a result to the bytecode hash and pinned engine and ruleset versions, and can be anchored to an on-chain attestation registry where a client requires public verifiability. Model-generated explanations are excluded from the comparison. The certificate attests to the automated analysis performed; network configuration and settlement governance remain the client's responsibility, and the client retains authorship of its control framework.

Evidence for your review

Technical evaluation and third-party risk review run at the same stage. The six diligence artifacts a reviewer receives are set out in the spec sheet.

Benchmark

Go-live testing uses an agreed corpus of vulnerable and benign contracts with expected verdicts. It reports confirmed detections, misses and false positives, with the critical class reported separately. Published figures follow a defined corpus, measurement date and pinned toolchain.

Model-risk controls

The detection engine runs inside the client boundary, versioned and tested against a fixed, held-out corpus. Changes carry repeat validation, production monitoring triggers review on drift, and rule-based verdicts remain independent of model output.

Security evidence

A SOC 2 Type II examination and ISO 27001 certification are planned, with status information and control documentation available on request. Client data is segregated by client, encrypted in transit and at rest, and retained on the client's schedule.

Implementation before continuous service

Client Focus provisions the environment, calibrates the engines and models, connects the compliance loop, and validates the workflow against an agreed benchmark corpus before go-live acceptance.

Scope, supported chains, contract languages, acceptance criteria and service levels are agreed with each client. Client Focus then operates the control plane, maintains the engines and rulesets, and runs the compliance loop under agreed service levels. The client's engineers retain ownership of contract code, release decisions and remediation; named Client Focus operators remain accountable for the accuracy of the evidence.

Analysis connected to operations

SCG360 supports the contract assurance workflow. C'ROC watches live on-chain activity and manages security events through a separate operational process.

Continue reading

Build

Engineering and integration for systems that will run on public chains.

Discuss contract assurance with Client Focus.

Review your contract portfolio, control requirements and deployment boundary with a principal of the firm.