DPO Radio

A risk analyst running a vendor risk programme spends most of their week on five recurring tasks. The first two are onboarding new vendors with structured evidence collection, and walking sub-processor change notifications against Article 28(2) and SLA windows. The other three are extracting risk-relevant clauses from vendor contracts, drafting risk acceptance reasoning for proposed acceptances, and running tabular reviews across selected vendor contracts.
The Risk Analyst persona is tuned for that work. It comes with no regulatory pack of its own: each conversation is grounded in the frameworks your organisation has installed, and it reads vendor records, vendor risk scores and your documents through its search tools, within the permissions of the person asking. Its tool affinity is biased toward the vendor and risk workflow pack — vendor onboarding evidence collector, sub-processor change impact assessment, contract risk summary, risk acceptance reasoning generator.
The Risk Analyst's citation discipline matches every other persona: no risk conclusion without an inline citation to the relevant security framework. The off-topic refusal block redirects compliance-only questions to the Compliance Specialist and privacy-only questions to the DPO Advisor.
The Risk Analyst persona pre-loads no regulatory pack. Each conversation tells it which frameworks your organisation has installed, and it may cite a framework only when its regulatory search returned that text in the same turn. Where your organisation has installed, say, ISO 27001 and DORA, cross-framework reasoning across the two (the DORA Article 28 ICT third-party register beside ISO 27001 supplier relationships) stays in one conversation. Vendor records, vendor risk scores and your documents are read on demand through its search tools, never loaded in bulk.
The persona reaches for the vendor and risk workflow pack first — vendor onboarding evidence collector, sub-processor change impact assessment, contract obligation extraction, contract risk summary, risk acceptance reasoning generator, maturity assessment AI gap walkthrough. Tabular reviews over the vendor portfolio sit one click away.
The vendor onboarding evidence collector classifies uploaded files into four artefact types — data processing agreement, SOC 2 report, ISO 27001 certificate, and insurance policy — by matching the filename against an explicit rule set. A fifth category, incident history, is surfaced as a finding rather than as a required artefact. The output is a tier-driven evidence pack ready for vendor risk review.
The subprocessor change impact workflow drafts a customer notice under GDPR Article 28(2) and prepares follow-up tasks. The analyst checks the default task date against the agreement and recorded obligations before applying the proposal.
The risk acceptance reasoning generator drafts structured reasoning for a proposed acceptance (likelihood / impact / compensating controls / residual risk / acceptance horizon) with citations to the relevant security framework. The analyst reviews and the approver signs off.
Start the tabular review with the relevant vendor contracts and criteria. Check verified source evidence and rerun cells that need another look.
A question about a privacy DPIA or a contract redline triggers a redirect to the DPO Advisor or Legal Counsel persona. A question outside the risk scope entirely triggers the standard off-topic refusal block.



Every risk conclusion ships with an inline citation to the relevant security framework. When grounding is unavailable, the persona says so explicitly.

Workflow drafts are reviewed and accepted per field by the analyst. The approver for a risk acceptance signs off; Forseti does not approve the acceptance autonomously.

The persona's audit lineage is in the same Immutable Audit Trail as every other Forseti event. Vendor onboarding decisions, sub-processor change responses, and risk acceptance reasoning all flow through the same chain of custody.

English and Vietnamese playbooks guide reviews such as vendor tier explanation, treatment planning and acceptance reasoning. Use Enterprise Risk Workflows to prepare proposals against the recorded method. Use Third-Party Workflows for vendor and ICT checks.
Ready to see a vendor DPA walked, an evidence pack assembled, and a risk acceptance reasoning drafted in under fifteen minutes? Request a personalised demo.


Run the vendor onboarding evidence collector and the sub-processor change impact workflow through the Risk Analyst persona for 30 days against your vendor pipeline.

Talk to our team about how the Risk Analyst fits into your second-line risk programme and your scheduled vendor review cadence.
Vendor onboarding evidence collection, sub-processor change impact assessment, contract obligation extraction, contract risk summary, risk acceptance reasoning generation, maturity assessment AI gap walkthrough, and tabular reviews across selected vendor contracts.
The persona pre-loads no pack of its own. Each conversation tells it which frameworks your organisation has installed — ISO 27001, SOC 2, DORA, NIS2, GDPR or PDPL, where you have installed them — and it cites a framework only when its regulatory search returned that text in the same turn.
No. The risk acceptance reasoning generator drafts the structured reasoning; the approver signs off. Forseti does not approve a risk acceptance under any code path.
Select the documents and the relevant tabular workflow. The grid makes criteria comparable across contracts and records verified citations and open questions for the reviewer.
No. The Risk Analyst's prompt ships in its runtime persona pack and is identical on Light, Standard, and Enterprise — no tier offers a tenant-level override. The prompt is reviewable on request, and what it picks up per conversation is your own context: the user's locale and role, the organisation's tier, and the regulatory packs your organisation has installed.