A processor assessment is often reduced to a security questionnaire and a score. That produces a number without a decision. A usable assessment shows what personal data the supplier touches, which controls protect it, what the contract requires, who else is in the chain and what happens when the relationship ends. Each conclusion needs evidence and a named owner.
This checklist is for the person who signs off a new supplier or renews an existing one: a founder, operations lead, legal adviser or security manager. It assumes the supplier handles personal data on your instructions, which makes it a processor rather than a controller. If the supplier decides why and how the data is used, the relationship is different and needs a separate analysis.
Tier the relationship before sending questions
Not every supplier needs the same depth. Tier by three factors: the sensitivity of the data, the breadth of access and the consequence of failure. A payroll provider with salary and bank details sits in a different tier from a design agency that sees a campaign brief. Record the tier and the reason, then apply the corresponding due diligence.
| Tier | Typical relationship | Evidence depth | Review |
|---|---|---|---|
| High | Sensitive data, broad access, business-critical service | Full assessment, contract review, test evidence | Annually and on material change |
| Medium | Limited personal data, supervised access | Questionnaire plus selected evidence | Every two years |
| Low | No personal data or anonymised data only | Written confirmation and scope note | On renewal |
A. Scope and data map
- Data categories: list each type of personal data, including identifiers, contact details, financial data, health data, biometrics and employee records. Owner: business owner. Evidence: data map extract. Frequency: at onboarding and on change.
- Data subjects: customers, employees, applicants, contractors or children, with approximate volume bands rather than invented counts. Owner: business owner. Evidence: scope note. Frequency: annually.
- Purpose and instruction: state what the supplier is permitted to do and what it must not do, such as using the data for its own product improvement or marketing. Owner: legal and business owner. Evidence: contract schedule. Frequency: at signature.
- Access route: record whether access is through a portal, API, support session, shared inbox or exported file. Owner: IT lead. Evidence: access diagram. Frequency: at onboarding and after architecture change.
- Location and transfer: identify hosting countries and any remote access from another jurisdiction. Owner: supplier. Evidence: hosting and support locations statement. Frequency: annually.
B. Security controls and evidence
- Access control: named accounts, least privilege, MFA for administrative access and timely removal of leavers. Evidence: access policy and a recent review, not a screenshot of a settings page.
- Encryption: in transit and at rest, with key management described in plain terms. Evidence: architecture note or independent report.
- Logging and monitoring: administrative actions, authentication events and alerting for anomalies. Evidence: sample log extract or monitoring description.
- Vulnerability and patch management: how issues are identified, prioritised and fixed, with a record of the last cycle. Evidence: policy and remediation summary.
- Backup and recovery: backup frequency, restore testing and the supplier's own recovery objective. Evidence: restore test record.
- Development and change: secure development, code review, dependency management and separation of production access. Evidence: SDLC summary or certification report, if held.
- Physical and environmental: for hosting providers, the location controls and the responsibility split. Evidence: sub-processor list and hosting statement.
C. Contract terms to verify
Confirm that the agreement covers the subject matter and duration of processing, the nature and purpose, the data types and categories of data subjects, and the supplier's obligations. It should require confidentiality, compliance with instructions, assistance with data subject requests and impact assessments, breach notification, deletion or return at the end, and audit or inspection rights. It should also address sub-processors: prior authorisation, notice of changes, flow-down obligations and the right to object.
This is a legal review, not a security review. Use qualified local advice for the governing law and any sector-specific rules that apply in Bangladesh or wherever the data subjects live.
D. Sub-processor chain
Ask for the full list, including hosting, email, support, analytics and any affiliate that can access the data. For each, record the service, location and contract flow-down. Check how you will be notified of a new sub-processor and how quickly you can object. A supplier that cannot name its hosting provider is not ready for a high-tier assessment.
E. Incident and breach response
Ask what the supplier considers a reportable incident, who decides, how quickly it notifies you and what it provides in the first update. Test the answer with a scenario: a support engineer's laptop is stolen, or a misconfigured storage bucket exposes a client folder. The response should name the contact, the escalation path and the evidence you will receive. Your own incident plan should include the supplier as a route, not an afterthought.
F. Monitoring and exit
- Set the review date and the evidence refresh schedule in the contract or register.
- Track open conditions with an owner and a due date; do not close a high-tier assessment with an unresolved critical gap.
- Agree the exit format: full data export, document return, deletion confirmation and the date by which it happens.
- Confirm how access is removed at exit, including support accounts and integrations.
Scoring and sign-off
Use three outcomes: pass, conditional or fail. A conditional outcome needs a specific action, an owner and a date. Do not average a missing breach clause against a strong encryption answer; some gaps are gates. Record the decision in a short memo: supplier, service, tier, data categories, evidence reviewed, open conditions, residual risk and the name of the person accepting it. That memo is more useful than a questionnaire score because it shows what was known at the time.
Red flags
- A questionnaire returned by a salesperson with no supporting evidence.
- Refusal to name sub-processors or hosting locations.
- A breach clause that requires the supplier to notify "where legally permitted" with no timeframe.
- Access for support staff with no logging or approval.
- No deletion commitment, or deletion that leaves backups undefined.
- An audit right that exists in the contract but has no practical process behind it.
If you need help turning this checklist into a repeatable vendor assessment, start with Managed Technology & Cybersecurity. The pricing page explains how assessment and ongoing review are scoped. For the risk analysis behind the checklist, read third-party data processor assessment: risks and controls.
Sources
- EUR-Lex, Regulation (EU) 2016/679 (GDPR), Article 28, accessed 17 November 2026.
- ICO, Contracts and liabilities between controllers and processors, accessed 17 November 2026.
- NIST Privacy Framework, accessed 17 November 2026.
- ISO/IEC 27701, Privacy information management, accessed 17 November 2026.
- DataGuidance, Bangladesh data protection overview, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.