SecurityBoat

TriNetra · Trust

Your security questionnaire answer, self-serve.

Trust Center is a governed document library where prospects, customers, and auditors get your pentest attestations, compliance reports, policies, and certifications — on your terms. Public documents are one click away; sensitive ones sit behind an approval workflow; every view, request, and decision is logged.

Trust Center · Document Library

Every view audited
SOC 2 Type II Report — 2026PDF · 4.2 MB · 68 pages · 3 pending requestsRESTRICTED
RBI Cyber Security Framework AttestationPDF · 1.8 MB · 22 pages · 1 pending requestRESTRICTED
Sub-processor List512 KB · always currentPUBLIC
PTaaS Executive Summary — Q2 2026PDF · 2.8 MB · 14 pagesRESTRICTED
Annual Penetration Test Summary — 2025PDF · 3.1 MB · 19 pagesRESTRICTED

The problem

Security review is the slowest mile of an enterprise deal — and the messiest. The evidence a buyer needs is scattered across folders and inboxes, sensitive reports get emailed ad hoc with no approval trail, and nobody can say with certainty who has a copy of what. The team ends up re-answering the same questions deal after deal.

How Trust Center answers it

Trust Center puts every security document in one governed library — organized into Compliance, Pentest Reports, Policies, and Certifications — and lets you decide, document by document, what's public and what's gated. Buyers self-serve the public material; sensitive documents require an access request your team explicitly approves or denies. Every step lands in a full audit trail, and engagement analytics show you which documents get viewed, which get requested, and which requests get approved — so sharing evidence becomes a controlled process, not an email thread.

How it actually works

Shared on your terms.

Public documents one click away; sensitive ones behind an approval gate — every view, request, and decision logged.

SOC 2 Type II — 2026

PDF · 68 pages · 3 pending requests

RESTRICTED

RBI Cyber Framework Attestation

PDF · 22 pages · 1 pending request

RESTRICTED

Sub-processor List

Always current

PUBLIC

How it works

The workflow, end to end.

  1. 01

    Centralize

    Every security document moves into one library, organized into four categories: Compliance, Pentest Reports, Policies, and Certifications. One current version of each — no more stale copies in circulation.

  2. 02

    Publish

    You decide each document's state: public and self-serve, or restricted and gated behind a request. The choice is per-document, and reversible.

  3. 03

    Request

    A prospect, customer, or auditor hits a restricted document and submits an access request in the portal — name, company, and reason — instead of emailing someone who forwards it to someone else.

  4. 04

    Approve

    Your team reviews each request and approves or denies it deliberately — a governed decision, not whoever answers the inbox first.

  5. 05

    Audit

    Every view, request, approval, and denial is captured in a full audit trail — who, what document, what decision, when.

  6. 06

    Measure

    Engagement analytics show which documents get viewed most, which get requested, and how requests convert — a live read on what buyers actually check.

The request gate

Restricted documents are requested in the portal and released only when your team approves — a governed decision, not whoever answers the inbox first. Every request lands in the audit trail.

Access Requests

Every view audited

SOC 2 Type II — 2026

Meera Joshi · FinEdge Capital

In Review

RBI Cyber Framework Attestation

Daniel D'Souza · Northgate Bank

Requested

PTaaS Executive Summary — Q2 2026

Priya Nair · Audico LLP

Approved

Annual Penetration Test Summary

Arjun Mehta · Stealth Labs

Denied

Requested → In Review → Approved / Denied — and the view → request → approve funnel reads at a 12% approval rate.

Capabilities

What ships in the box.

Four-category document library

Compliance, Pentest Reports, Policies, and Certifications, each holding the single current version of every document. When the new attestation lands, it replaces the old one everywhere at once.

Public or restricted — your call, per document

A policy PDF can be one click away while the full pentest report sits behind a gate. Each document carries its own access state, and you can change it at any time.

Access-request approval workflow

Restricted documents are requested in the portal and released only when your team approves. Requests move through explicit states — Requested, In Review, Approved, Denied — so nothing is shared by reflex.

Full audit trail

Every view, request, and approval decision is logged with the who, the what, and the when. When someone asks "who has seen our pentest report?", the answer is a filter, not an investigation.

Engagement analytics

See your most-viewed documents and the full view → request → approve funnel. You learn what buyers actually scrutinize — and where reviews stall — from real portal activity.

A front door for security reviews

Point every "can you send us your security docs?" email at one portal. Buyers self-serve most of what they need, and the requests that do reach your team arrive structured and ready to decide.

FAQ

Common questions.

No — it's a governed document library. You choose exactly which documents are public and which require an approved request, and every access lands in the audit trail either way. Evidence over icons.

Share evidence on your terms.

Bring the last security questionnaire that stalled a deal. We'll show you how a Trust Center answers most of it before anyone emails your team.

Related: PTaaS · Continuous Controls Validation