For fintechs · Bank partners and investors

Security questionnaires: what evidence answers each question

Partner banks, investors and enterprise customers send security questionnaires. A good answer states the position and points to dated proof. This page maps common question themes to the evidence a reviewer can check, and says plainly which ones StackWeaver can produce today and which stay with your own team.

Last reviewed: 15 November 2026 · Written by StackWeaver. This is not legal advice, an audit opinion or a finding about any company's regulatory status.

Question themes and the evidence that answers them

Question themeEvidence a reviewer can checkStackWeaver today
Is multi-factor authentication required for all staff?An MFA enrolment report from your identity provider, dated.Yes, for Okta and Microsoft Entra ID: a read-only check of enrolment.
Are code changes reviewed before release?Branch protection and required-review settings on the default branch.Yes, for GitHub: default-branch protection and required pull-request reviews, among six checks.
Is privileged access limited and reviewed?A list of privileged roles, just-in-time access settings and stale accounts.Yes, for Microsoft Entra ID: privileged roles, just-in-time access and stale-account checks.
Are sign-in and audit logs kept?The log-retention setting and the period it covers.Partly: Microsoft Entra ID sign-in log retention is checked. Other log sources are not covered yet.
Are software vulnerabilities tracked?Open dependency or vulnerability alert counts for your repositories.Partly: GitHub dependency alerts are read. Penetration test reports are not produced by StackWeaver.
Do you have security, privacy and incident-response policies?The approved policy documents, with owners and review dates.No. These are your documents. The Evidence Readiness Assessment lists which ones you need and who owns each.
Do you hold an independent penetration test or certification?The report or certificate, from the independent party.No. StackWeaver does not issue certifications or audit opinions.

How to answer without overclaiming

  • State what is true today, with the date of the evidence. A setting that was on last month is not proof it is on now.
  • Show failures honestly. StackWeaver keeps failing results too, so the record matches what the system returned.
  • Do not claim a pass, an approval or a certification unless a regulator or independent auditor has issued it. StackWeaver does not make that call, and a questionnaire answer is your company's statement.

Getting a reviewer to trust the file

Each StackWeaver result is kept as an Evidence Object with a SHA-256 fingerprint. A reviewer who receives an evidence file with a StackWeaver ID can check that it matches the record on the verify page. Nothing is uploaded to do that.

Where to start

  1. Take the Evidence Readiness Assessment to see which questions you can already answer with proof.
  2. Connect the systems StackWeaver can read: see the connector guides for what each one reads and how to disconnect.
  3. Read what examiners and bank partners ask for in Nigeria in the Nigeria compliance evidence guide.

Frequently asked questions

Can StackWeaver fill in or sign our security questionnaire?

No. The answers are your company's statements. StackWeaver provides dated evidence you can cite in them, and the assessment shows which answers you can support today.

Which questions can the evidence answer today?

Questions about multi-factor authentication, code review, privileged access and some log retention, where you connect GitHub, Okta or Microsoft Entra ID. Policies, penetration test reports and certifications are your own documents.

Will a bank partner accept this evidence?

We cannot say. Each bank or investor decides what it accepts. StackWeaver evidence shows what a system's settings were at a point in time.