Answer the security questionnaire once
Every enterprise deal now arrives with a security review attached, and your team answers substantially the same questions for every prospect. A trust center reverses the direction: publish your posture once, under your control, and let buyers and auditors serve themselves.
This page describes how we approach this work and how Govrly supports it. Where regulatory requirements are mentioned, confirm what applies to your organisation against the source documents published by the relevant authority.
What is a trust center?
From the compliance programmes we build and run in Saudi Arabia: a trust center is a controlled, externally facing page where an organisation publishes its security and compliance posture for customers, partners, and auditors. It replaces the repetitive exchange of questionnaires and emailed documents with a single published source — some of it open, some released on request under controlled access.
The distinction that matters is between a trust center and a marketing page about security. A marketing page makes claims. A trust center publishes artefacts — certifications, framework alignment, policies, audit summaries — with a controlled path to the material that cannot be posted openly.
It is the only outward-facing part of a compliance programme. Everything else you build proves your position to a regulator, an auditor, or your own board. This proves it to someone deciding whether to sign with you.
The security questionnaire tax
Nobody budgets for this, and it quietly consumes the most expensive people in the security team.
- 01/06Every deal brings its own questionnaire
Different format, different wording, largely the same underlying questions. Each one is filled in manually because none of them quite matches the last.
- 02/06It lands on the security team, not sales
The people who can answer accurately are the people you least want spending a week on a spreadsheet — and they are answering questions they have already answered.
- 03/06Answers drift between deals
Two prospects receive slightly different descriptions of the same control because two people answered on different days from different sources.
- 04/06The deal waits
Security review becomes a gate in the sales cycle, and the delay is invisible in the pipeline until someone asks why a deal has been in the same stage for six weeks.
- 05/06Documents are emailed and lost
A policy or an audit summary is sent to a prospect. Nobody records who has it, under what terms, or whether the version they hold is still current.
- 06/06The same cycle repeats annually
Existing customers re-run their vendor review, and the whole exercise starts again with people who have been your customer for three years.
Public and gated: two tiers, one page
Not everything can be posted openly, and not everything needs to be gated. Getting this split right is most of the design work.
Material that answers the first ninety per cent of questions without any exchange at all, and that a buyer can find before they ever contact you.
- Certifications held and their current validity
- Framework alignment — NCA ECC, SAMA CSF, CST CRF, ISO 27001
- High-level architecture and hosting model
- Subprocessor list
- Privacy and data handling summary
- Incident response and disclosure approach
Material that carries genuine sensitivity and should reach a named person under agreed terms — not sit on a public URL indefinitely.
- Full audit and assessment reports
- Penetration test summaries
- Detailed policies and standards
- Completed questionnaire responses
- Architecture detail beyond the public summary
- Anything released under NDA
The mistake we see most often is gating everything. If a prospect must submit a request to learn which certifications you hold, the trust center has not removed the exchange — it has added a step to it.
What changes in the sales cycle
A trust center does not eliminate security review, and it should not try to. It removes the repetitive part so the review focuses on what is genuinely specific to that customer.
| Stage | Without a trust center | With one |
|---|---|---|
| Buyer's first question | Emailed to sales, forwarded to security, answered in days | Answered on the page before anyone is contacted |
| Questionnaire arrives | Filled in manually, from scratch, by the security team | Most answers already published; only the gaps need attention |
| Document request | Emailed as an attachment, untracked afterwards | Released through a controlled path, with the request logged |
| Answer consistency | Varies by who answered and when | One approved source, same answer to everyone |
| Currency of material | Whatever version the sender had to hand | Drawn from the current approved record |
| Annual customer review | The entire exercise repeats | Customer self-serves from the same page |
Trust center in Govrly
The published view draws on the same records that run your compliance programme — so it is current by construction rather than by someone remembering to update it.
The trust center is a controlled view of one use case's output. The control library, risk and audit, evidence collection, and privacy records are separate use cases feeding the same records — linked below rather than duplicated here.
Published material comes from the control and evidence records you already maintain, rather than being re-uploaded to a separate marketing surface that immediately begins to drift.
An approval step sits between an internal record and anything visible externally. Publishing is a decision, not a side effect of updating a document.
Each item is set to open publication or controlled release, so the split is a configuration rather than a policy nobody can enforce.
Requests for gated material are recorded with the requester's identity, so you know who holds what — which matters when a document is later superseded.
When an underlying record is replaced, the published version follows. A lapsed certificate on a public page damages trust more than having no page at all.
Presented under your own brand, so a buyer is reading your posture on your surface rather than being sent to an unfamiliar portal mid-evaluation.
Why this matters selling into the Saudi market
The buyer's own obligations are what generate the questionnaire in the first place.
The NCA ECC includes a third-party and cloud domain. When a government entity assesses you, it is discharging its own regulatory obligation — which is why the questions are detailed and why "trust us" does not work.
Third Party Cyber Security is a scored domain for every SAMA-supervised entity. Your posture becomes part of their maturity assessment, not just their procurement paperwork.
Third-party security is one of the six CRF domains, applied at the licensee's assigned compliance level.
Under the Saudi PDPL, a processor moving data outside the Kingdom is still the controller's transfer. Buyers need to know where their data goes before they can approve you.
Stating clearly which Saudi frameworks you align to, and how, answers the question that determines whether you clear procurement — often before a conversation begins.
A trust center presented in Arabic as well as English removes friction with buyers whose internal review and approval process runs in Arabic.
Standing up a trust center
- 01/07Collect the questions you already answer
Pull the last ten questionnaires and find the overlap. Publishing the recurring eighty per cent removes most of the work immediately, and the exercise tells you what buyers actually ask.
- 02/07Decide the public and gated split deliberately
Certifications and framework alignment belong in the open. Audit reports and detailed architecture belong behind a request. Gating everything defeats the purpose.
- 03/07Publish only what you can substantiate
Anything on the page invites a follow-up question. A claim you cannot evidence in the next meeting costs more than saying nothing.
- 04/07Put an approval gate in front of publication
One named approver deciding what becomes externally visible, with a record of who approved what and when.
- 05/07Log gated releases
Who requested, what was released, under what terms. This matters when a document is later superseded and you need to know who holds the old one.
- 06/07Tie currency to the underlying record
An expired certificate visible on a public page is worse than no page. Publication should follow the source record, not a calendar reminder.
- 07/07Point sales at it before the questionnaire arrives
The value is realised when a buyer reads it during evaluation, not when it is sent as a reply to a questionnaire that has already been assigned to someone.
Trust center — FAQs
A controlled, externally facing page where an organisation publishes its security and compliance posture for customers, partners, and auditors. It replaces the repetitive exchange of questionnaires and emailed documents with a single published source — some of it open, some released on request under controlled access.
Publicly: certifications held and their validity, framework alignment, high-level architecture and hosting model, subprocessor list, privacy summary, and incident disclosure approach. On request: full audit reports, penetration test summaries, detailed policies, completed questionnaire responses, and anything released under NDA.
No, and this is the mistake we see most often. If a prospect has to submit a request just to learn which certifications you hold, the trust center has not removed the exchange — it has added a step to it. Certifications and framework alignment belong in the open; genuinely sensitive material belongs behind controlled access.
It removes the repetitive part rather than eliminating review entirely. Most questionnaires ask substantially the same underlying questions, and publishing those answers once means the remaining exchange focuses on what is genuinely specific to that customer. Some buyers will still require their own form completed.
A security marketing page makes claims. A trust center publishes artefacts — certifications, framework alignment, policies, audit summaries — with a controlled path to material that cannot be posted openly. The difference is whether a buyer can verify what they are reading.
By sourcing it from the records that run your compliance programme rather than maintaining it separately. A trust center updated by hand drifts within a quarter, and an expired certificate visible on a public page damages trust more than having no page at all.
A named approver, with an approval step between the internal record and anything externally visible. Publishing is best a decision with a record of who approved what and when — not a side effect of someone updating a document internally.
Because they are discharging their own regulatory obligations. Third-party security is a domain in the NCA ECC, a scored domain in the SAMA CSF, and one of the six CST CRF domains. When a buyer assesses you, they are evidencing a control they will themselves be assessed on — which is why general assurances are not sufficient.
Yes, and this is often underestimated. Customers re-run vendor reviews annually, and without a published source the entire exercise repeats with organisations that have been customers for years. A trust center lets them self-serve instead.
Direction. Vendor and third-party risk is you assessing your suppliers. A trust center is you being assessed by your customers. Both run on the same underlying records, but one faces inward at your supply chain and the other faces outward at your buyers.
Publish once. Stop answering the same questions.
A controlled trust center drawn from the records you already maintain — approved before it publishes, logged when it is released.
