01
Assessment Philosophy
Preflight Audit is the security-assurance, testing and verification brand and department of TVK Labs & Technologies Ltd. Assessments apply organizational independence controls where required.
Assessment Framework
A structured engagement from intake through evidence review, remediation, controlled record release and public verification.
01
Preflight Audit is the security-assurance, testing and verification brand and department of TVK Labs & Technologies Ltd. Assessments apply organizational independence controls where required.
02
Assessments are organized across Launch Readiness, Security Assurance, Infrastructure Review, Smart Contract Review, Operational Readiness, AI Security, and Enterprise Verification. Each category defines specific review surfaces, evidence requirements, and deliverable standards.
03
A structured engagement from intake through evidence review, remediation, controlled record release and public verification.
04
Scope is defined in writing before review begins. In-scope systems, contracts, repositories, and operational surfaces are enumerated explicitly. Out-of-scope items are documented to prevent ambiguity. Scope changes require formal amendment and may trigger re-assessment.
05
Reviewers collect evidence through documentation review, architecture diagrams, repository analysis, contract verification, configuration review, and structured interviews. All evidence is traceable to specific assessment findings and retained per engagement retention policy.
06
Technical review covers smart contract logic, access controls, upgrade paths, dependency surfaces, and integration boundaries. Findings are classified by severity using a standardized matrix aligned to deployment impact.
07
Infrastructure assessment evaluates deployment architecture, redundancy patterns, key management, monitoring coverage, incident response readiness, and data handling boundaries. Cloud, on-premise, and hybrid configurations are supported.
08
Architecture review examines system design, module boundaries, trust assumptions, and failure modes. We assess whether documented architecture matches deployed reality and whether design supports stated launch readiness claims.
09
Operational readiness covers runbooks, on-call procedures, disclosure practices, upgrade governance, and communication protocols. Launch readiness requires operational maturity commensurate with deployment risk.
10
Launch readiness synthesis combines all review streams into a readiness score and classification. Critical and high-severity blockers must be remediated or formally accepted before verified status is granted.
11
Findings are classified as Critical, High, Medium, or Low based on exploitability, impact, and deployment context. Aggregate risk level (Low, Moderate, Elevated, Critical) reflects overall assessment posture at time of publication.
12
Standard deliverables include the assessment report, public verification page, stable verification record ID, verification QR code and embeddable status badge. Full reports are provided to project teams; public summaries are published with consent.
13
Assessments reflect conditions at a point in time. They do not guarantee future security, regulatory compliance, or investment performance. Experimental assets, memecoins, and pre-mainnet systems carry inherent uncertainty documented in each verification record.
14
Every assessment is versioned. Material changes create a new assessment version and verification record ID; superseded records remain available for historical traceability.
15
The methodology is reviewed regularly. Industry developments, incident lessons and client feedback inform updates, and the applicable methodology version is cited on each assessment record and verification page.
Every assessment issued follows this framework and resolves to a public verification page.
Also see our 8-stage engagement process.