[Company name]
Vendor and Third-Party Risk Management Policy
| Organization | [Company name] |
|---|---|
| Document | Vendor and Third-Party Risk Management Policy |
| Document owner | [Owner name], [Owner title] |
| Approved by | [Approver name], [Approver title] |
| Effective date | [Effective date] |
| Version | [Version] |
| Review frequency | Reviewed [Review frequency] and after any significant change |
| Classification | Internal use |
1. Purpose
This policy describes how [Company name] identifies, evaluates, contracts with, monitors, and offboards vendors and other third parties that access company systems or handle company or client information. Its goal is to reduce the risk that a vendor causes a data breach, service outage, or compliance failure, while keeping the process practical for a business of our size.
2. Scope
This policy applies to any third party that does one or more of the following:
- Stores, processes, transmits, or can view confidential company, client, patient, or employee information
- Has remote or on-site access to company systems, networks, or devices
- Provides a service the business cannot operate without (for example, [Main line-of-business application], [Email / productivity platform], internet service, payroll)
- Develops, hosts, or maintains software or websites for the company
This includes IT providers, software-as-a-service providers, cloud hosting, payment processors, billing and collections services, payroll and HR platforms, shredding services, and consultants. Low-risk suppliers with no data or system access (for example, office supplies) are out of scope.
3. Roles and Responsibilities
| Role | Responsibilities |
|---|---|
| Vendor risk owner ([Vendor risk owner]) | Maintains the vendor inventory, assigns risk tiers, runs due diligence and reviews, keeps records, and escalates concerns. |
| Business owner of each vendor | The employee who requests or manages the vendor relationship. Explains what the vendor will do and what data it needs; confirms the vendor is still needed at each review. |
| [IT provider / MSP] | Reviews technical security, sets up and removes vendor access, and monitors vendor activity on company systems. |
| [Approver name] | Approves Critical and High tier vendors and any accepted risk exceptions; signs contracts. |
| Legal counsel ([Legal counsel]) | Reviews contract security terms for Critical vendors and any business associate or data processing agreements. |
4. Vendor Risk Tiers
Every in-scope vendor is assigned a tier before onboarding. The tier determines the depth of due diligence and how often the vendor is reviewed.
| Tier | Criteria (any one applies) | Due diligence | Review frequency |
|---|---|---|---|
| Critical | Administrative access to company systems (such as an IT provider or remote management tool); hosts large volumes of sensitive client data; outage would stop the business. | Full questionnaire, independent attestation (SOC 2 Type II or equivalent) or detailed evidence, contract review by counsel, insurance certificate | Annually, and after any incident |
| High | Stores or processes confidential or regulated data (SSNs, health, financial, payment card data); integrates with core systems. | Full questionnaire, attestation or security documentation, contract security terms | Annually |
| Moderate | Limited confidential data or limited system access; an outage would be disruptive but workable. | Short questionnaire, review of public security and privacy information, MFA confirmation | Every two years |
| Low | No confidential data and no system access, but in scope for another reason (for example, website analytics). | Basic review of terms and privacy policy | At renewal |
5. Onboarding Due Diligence
Before a new vendor receives data or access, the business owner and vendor risk owner complete the following:
- Describe the service, the data involved, and the access required; confirm the vendor needs no more than that
- Assign a risk tier
- Send the Vendor Security Questionnaire (Section 12) to Critical, High, and Moderate vendors and review answers
- Request a SOC 2 Type II report, ISO/IEC 27001 certificate, or equivalent evidence for Critical and High vendors, and read the exceptions and complementary user entity controls sections
- Search for public reports of breaches or security problems involving the vendor
- Confirm the vendor supports MFA and single sign-on where available
- Confirm where data will be stored and whether subcontractors will handle it
- Confirm required regulatory agreements (for example, a HIPAA business associate agreement) are in place
- Document risks found and whether they are accepted, mitigated, or cause the vendor to be rejected
- Obtain approval from [Approver name] for Critical and High vendors
Drafting note: Small vendors often cannot provide a SOC 2 report. That does not automatically disqualify them. Ask for their security policy, MFA and backup practices, and insurance certificate, and weigh the risk against how much data they will hold.
6. Contract Requirements
Contracts with Critical and High vendors (and Moderate vendors where practical) should include:
- Security obligations: the vendor will maintain reasonable administrative, technical, and physical safeguards appropriate to the data, including encryption, MFA, and access controls.
- Confidentiality and use limits: company data is used only to provide the contracted service and is not sold or used to train products without written permission.
- Breach notification: the vendor will notify [Company name] of any security incident affecting company data without undue delay and no later than [Required vendor breach notice] hours after discovery, and will cooperate with investigation and notification.
- Right to assess: the company may request security documentation, independent audit reports (such as SOC 2), and completed questionnaires at least annually.
- Subcontractors: the vendor will disclose subcontractors that handle company data and flow down equivalent security obligations.
- Data return and deletion: at the end of the contract, the vendor will return company data in a usable format and securely delete remaining copies, and confirm deletion in writing.
- Insurance: the vendor will maintain cyber liability insurance of at least [Minimum vendor cyber insurance] and provide a certificate on request.
- Regulatory terms: business associate agreements, data processing terms, or other terms required by law or by our own clients.
- Service levels: uptime, support response, and backup/recovery commitments for services the business depends on.
7. Vendor Access to Company Systems
- Each vendor technician uses a named individual account. Shared or generic vendor logins are not permitted.
- MFA is required for all vendor access to company systems, including remote management tools and cloud admin portals.
- Access is limited to the systems and permissions needed for the work (least privilege), and administrative rights are granted only when necessary.
- Remote access sessions use company-approved tools only. Ad hoc remote tools sent by callers are never installed.
- Remote sessions for vendors other than [IT provider / MSP] are approved in advance, and sessions are logged; where possible, access is enabled only for the duration of the work.
- Vendor accounts are reviewed quarterly by [IT provider / MSP], and unused accounts are disabled.
- Requests from a vendor to change payment details, reset credentials, or install software are verified by calling the vendor at a known number.
8. Ongoing Monitoring
Vendors are reviewed on the schedule in Section 4. Each review confirms:
- The vendor is still needed and the data and access it has are still appropriate
- Updated attestation reports or questionnaire answers have been received and reviewed
- No unresolved security incidents, and any incidents were handled according to the contract
- Insurance certificate is current (Critical and High)
- Vendor accounts and access match current needs
- Contract terms still meet this policy; gaps are noted for the next renewal
Between reviews, the vendor risk owner watches for vendor breach announcements and security advisories. If a vendor reports a breach, the company follows its Incident Response Plan to determine whether company data was affected.
9. Vendor Offboarding
- Disable all vendor accounts, API keys, and integrations
- Remove vendor remote access tools and agents from company devices
- Change any shared credentials the vendor could have known
- Retrieve company data in a usable format and confirm it is complete
- Obtain written confirmation that remaining company data has been deleted
- Recover any company equipment, badges, or keys
- Update the vendor inventory
10. Vendor Inventory
| Vendor | Service | Data / access | Tier | Business owner | Contract end | Last review |
|---|---|---|---|---|---|---|
| [IT provider / MSP] | IT management and support | Administrative access | Critical | [Vendor risk owner] | ||
| [Email / productivity platform] | Email and files | All company data | Critical | |||
| [Main line-of-business application] | Core business application | Client records | Critical | |||
| [Backup solution / provider] | Backup | Encrypted copies of company data | High | |||
| Payroll provider | Payroll and HR | Employee SSNs, bank accounts | High | [HR contact] | ||
11. Exceptions
When a vendor cannot meet a requirement of this policy, the business owner documents the gap, the reason the vendor is still needed, and any compensating controls. Exceptions for Critical and High vendors require approval from [Approver name] and are revisited at the next review.
12. Vendor Security Questionnaire
Send this questionnaire to Critical, High, and Moderate vendors. Ask the vendor to answer Yes, No, or N/A for each question and explain any No answers. Supporting documents may be attached.
Vendor name: ____________________ Completed by (name/title): ____________________ Date: __________
A. Governance
| # | Question | Yes / No / N/A | Notes |
|---|---|---|---|
| A1 | Do you have a written information security program or policy that is reviewed at least annually? | ||
| A2 | Is a named person responsible for information security? | ||
| A3 | Do you perform a risk assessment at least annually? | ||
| A4 | Do you have a documented privacy policy describing how customer data is used? |
B. Access control and MFA
| # | Question | Yes / No / N/A | Notes |
|---|---|---|---|
| B1 | Is multi-factor authentication required for all of your staff who access customer data or production systems? | ||
| B2 | Do you offer MFA or single sign-on for our users of your service? | ||
| B3 | Is access granted on a least-privilege basis and reviewed at least quarterly? | ||
| B4 | Are accounts removed promptly when your employees leave? | ||
| B5 | If you access our systems remotely, do you use named accounts and log each session? |
C. Data protection and encryption
| # | Question | Yes / No / N/A | Notes |
|---|---|---|---|
| C1 | Is our data encrypted in transit (for example, TLS 1.2 or higher)? | ||
| C2 | Is our data encrypted at rest, including backups? | ||
| C3 | In which countries or regions will our data be stored and processed? | ||
| C4 | Is our data logically separated from other customers' data? | ||
| C5 | Will you return and securely delete our data at the end of the contract and confirm in writing? | ||
| C6 | Do you use our data to train AI models or for any purpose beyond providing the service? |
D. Vulnerability management and monitoring
| # | Question | Yes / No / N/A | Notes |
|---|---|---|---|
| D1 | Are systems patched on a defined schedule, with critical vulnerabilities addressed promptly? | ||
| D2 | Do you run endpoint detection and response or equivalent protection on servers and workstations? | ||
| D3 | Do you perform vulnerability scans and independent penetration tests? How often? | ||
| D4 | Are security logs collected and monitored? |
E. Backups and continuity
| # | Question | Yes / No / N/A | Notes |
|---|---|---|---|
| E1 | Is our data backed up at least daily, with a copy protected from deletion or ransomware? | ||
| E2 | Are restores tested at least annually? | ||
| E3 | Do you have a tested disaster recovery or business continuity plan? What are your recovery time objectives? |
F. Incident response and breach notification
| # | Question | Yes / No / N/A | Notes |
|---|---|---|---|
| F1 | Do you have a written incident response plan that is tested? | ||
| F2 | Will you notify us within [Required vendor breach notice] hours of discovering an incident affecting our data? | ||
| F3 | Have you had a security incident involving customer data in the past three years? If yes, describe. |
G. Personnel
| # | Question | Yes / No / N/A | Notes |
|---|---|---|---|
| G1 | Do employees with access to customer data pass background checks where permitted by law? | ||
| G2 | Do employees receive security awareness training at least annually? | ||
| G3 | Do employees sign confidentiality agreements? |
H. Subcontractors
| # | Question | Yes / No / N/A | Notes |
|---|---|---|---|
| H1 | Do any subcontractors or sub-processors handle our data? Please list them. | ||
| H2 | Do subcontractors have security obligations equivalent to yours? |
I. Compliance, attestations, and insurance
| # | Question | Yes / No / N/A | Notes |
|---|---|---|---|
| I1 | Do you have a current SOC 2 Type II report, ISO/IEC 27001 certification, or equivalent? Please provide it. | ||
| I2 | Will you sign a business associate agreement or other agreement required for regulated data, if applicable? | ||
| I3 | If you handle payment card data, are you PCI DSS compliant, and can you provide your attestation of compliance? | ||
| I4 | Do you carry cyber liability insurance? Please state the coverage limit and provide a certificate. |
Reviewed by: ____________________ Date: __________ Result: Approved / Approved with conditions / Not approved
13. Revision History
| Version | Date | Description of change | Author |
|---|---|---|---|
| [Version] | [Effective date] | Initial adoption of this Vendor and Third-Party Risk Management Policy | [Owner name] |
14. Approval
This Vendor and Third-Party Risk Management Policy has been reviewed and approved by the undersigned and is effective as of [Effective date]. It will be reviewed [Review frequency], after any significant incident, and whenever there is a material change to our systems, staff, or legal obligations.
| Signature: | Name / title: [Approver name], [Approver title] | Date: |
| Signature: | Name / title: [Owner name], [Owner title] | Date: |
Template adapted from the free Vendor and Third-Party Risk Management Policy template by PinellasIT (pinellasit.com/templates). Review with your legal counsel and insurer before adoption.
