Free compliance and vendors code of conduct template

Free IT Supplier Code of Conduct Template and Generator

An IT supplier code of conduct tells the companies you buy technology from what you expect of them: protecting your data and systems, honest business practices, basic labor and environmental standards, take-back and recycling of old equipment, and evidence when you ask for it. It matters because your suppliers are part of your risk: Verizon found a third party involved in 48% of breaches in its 2026 report. This free generator builds a starter code for IT purchasing that also supports EcoVadis Sustainable Procurement evidence.

Starter template only, not legal advice, may contain errors and may not reflect current law. Have qualified legal counsel review it before you rely on it. See also our Website and Free Resources Disclaimer and Terms of Service.

An IT supplier code of conduct is a written, executive-approved statement of the security, data protection, ethical, labor, and environmental standards an organization expects from the suppliers of its IT hardware, software, cloud, and services, and of how it checks that those standards are met.

Template version
v1.0.1
Last reviewed
October 2, 2026
Sections
16
Guided phases
5
Time to complete
About 4 minutes
Price
Free

Why does this code of conduct matter now?

What is inside the IT Supplier Code of Conduct template?

16 sections, ending with the document control table and the legal notice every template carries. Select any section to jump to it in the sample below.

  1. 1. PurposeWhat the code expects of IT suppliers, and why it is a starter for IT purchasing only.
  2. 2. ScopeThe IT suppliers covered, their subcontractors, and when the code takes effect.
  3. 3. DefinitionsPlain-language definitions of supplier, key supplier, take-back, corrective action and more.
  4. 4. Roles and ResponsibilitiesWho owns the code, who buys, and what suppliers commit to.
  5. 5. Security and Data ProtectionMulti-factor authentication, least privilege, patching, incident notice, and returning or deleting data.
  6. 6. Business Ethics and Legal ComplianceNo bribes or kickbacks, honest records, fair competition and legal licensing.
  7. 7. Labor, Health and SafetyBasic labor and human rights standards, with the RBA Code as the benchmark for hardware makers.
  8. 8. Environment, Take-Back and RecyclingEnvironmental compliance, energy and packaging, and responsible end of life for equipment.
  9. 9. Evidence and the Right to AskWhat evidence the company may request, how often, and how supplier information is protected.
  10. 10. Choosing and Onboarding SuppliersChecks before buying, contract terms, and the supplier acknowledgment.
  11. 11. Reviews and When a Supplier Falls ShortPeriodic reviews, corrective action plans, and ending a relationship when needed.
  12. 12. Reporting ConcernsHow suppliers and employees raise concerns, without retaliation.
  13. 13. Exceptions and ReviewHow exceptions for a supplier are approved and when the code is reviewed.
  14. 14. Related Standards and ReferencesThe guidance and standards this code is informed by.
  15. 15. Document Control and Revision HistoryDocument ID, version, effective date, next review, owner and approver, plus a revision history table.
  16. 16. Template Notice and Legal DisclaimerThe starter-template disclaimer and the reminder to have qualified counsel review the policy.
Template changelog
  • v1.0.1, October 13, 2026

    • Generated documents are marked as drafts until approved and signed, show when the template content was last reviewed, and ask you to answer facts about your organization.
    • The revision history now calls the document a code of conduct, not a policy.
  • v1.0.0, October 2, 2026

    • Initial release for IT purchasing, informed by CISA Cybersecurity Performance Goals 2.0 (goals 1.D and 1.E), NIST SP 800-161 Rev. 1, the RBA Code of Conduct v8.0 and the EcoVadis Sustainable Procurement theme.

Report an error in this template

Read the full sample IT Supplier Code of Conduct

This sample uses the suggested setting for every policy choice, example answers for the facts about an organization, and a placeholder company name. Build your own version to put in your organization's name, facts, owners and choices.

Sample template, not legal advice. Have your attorney review it before use.

Sections in this code of conduct
Sample[Company Name]

IT Supplier Code of Conduct

Document ID
PDC-ITSC-SAMPLE
Document version
1.0
Template version
v1.0.1
Effective date
October 2, 2026
Next review
October 2, 2027

1. Purpose

This code sets out what [Company Name] (the "company") expects of the suppliers it buys information technology from: that they protect the company's systems and data, act honestly, treat their workers fairly and safely, reduce their environmental impact, take responsibility for the end of life of the products they supply, and show evidence of all this when asked.

A starter for IT purchasing. This code covers IT suppliers only. A company-wide supplier code, covering materials, logistics, contract labor, facilities, and other suppliers, needs owners in human resources, legal, procurement, and sustainability. Until [Company Name] adopts one, this code applies to IT suppliers, and any company-wide code adopted later replaces the parts of this code it covers. This code is the set of expectations shared with suppliers; the internal steps for assessing a vendor's security risk are set by the company vendor risk management policy, where adopted.

The code is informed by the CISA Cybersecurity Performance Goals, NIST supply chain risk management guidance, and the Responsible Business Alliance Code of Conduct. It does not replace the law or the terms of any contract. Where a law, regulation, or contract sets a stricter requirement, the stricter requirement applies.

2. Scope

This code applies to the following suppliers of [Company Name] ("suppliers"), and to their subcontractors when they work on company matters:

  • Manufacturers, distributors, and resellers of computers, phones, servers, printers, network equipment, and other IT hardware.
  • Software publishers and cloud (SaaS) providers, including the providers of email, file storage, accounting, ERP, and security tools.
  • IT service providers, including managed IT and security providers, consultants, developers, and installers.
  • Internet, phone, and data center providers.
  • IT asset disposal (ITAD) vendors, electronics recyclers, and shredding companies.

When it applies. The code applies to new suppliers from the effective date, and to existing suppliers when their contract is renewed or significantly changed.

Key suppliers. Suppliers with access to company systems or data, suppliers that store company data, and suppliers the business could not operate without are "key suppliers" and receive closer review under this code.

3. Definitions

Supplier
A company that sells or provides IT hardware, software, cloud services, IT services, telecom services, or IT disposal and recycling to the company.
Key supplier
A supplier with access to company systems or data, that stores company data, or without which the business could not operate.
Security incident
Any event at a supplier that compromises, or may have compromised, the confidentiality, integrity, or availability of company data or systems.
Take-back program
A supplier program that collects used products or packaging for reuse or recycling.
Corrective action plan
A written, agreed plan, with owners and deadlines, to fix a gap between a supplier's practices and this code.
SOC 2 Type II report
An independent auditor's report on how well a service provider's security controls worked over a period of time.

4. Roles and Responsibilities

RoleResponsibilities
Executive sponsor (Chief Executive Officer)Approves this code, decides on exceptions for key suppliers, and decides whether to end a relationship for a serious breach.
Policy owner (IT Manager)Owns this code, keeps the list of suppliers and key suppliers, collects acknowledgments and evidence, runs reviews, and tracks corrective action plans.
Anyone who buys ITBuys only from suppliers that have accepted this code or are covered by an approved exception, and includes the code in quotes, purchase orders, and contracts.
Legal counselReviews contract terms that put this code into effect, especially for key suppliers.
SuppliersMeet this code, apply equivalent standards to their own suppliers for company work, provide evidence when asked, and report any breach of the code promptly.

5. Security and Data Protection

Suppliers that access, store, or process company data or systems, or that supply products that connect to them, must:

  • Maintain a written information security program appropriate to their size and the data they handle.
  • Use multi-factor authentication for all access to company systems and data, and for their own administrative and remote access.
  • Give their staff only the access to company systems and data they need, remove it promptly when no longer needed, and never share accounts.
  • Keep their products and systems on supported versions and apply security updates promptly.
  • Notify [Company Name] of any security incident affecting company data or systems within 72 hours of discovery, and cooperate fully with the company's response.
  • Tell the company about security vulnerabilities in the products they supply, and the fix or workaround, as soon as they know.
  • Use company data only to provide the contracted service, tell the company where it is stored, and never sell it.
  • Return or securely delete company data when the work ends, and confirm in writing that it has been done.
  • Apply equivalent requirements to any subcontractor that handles company data, and tell the company before using one.

Software and cloud providers. Software and cloud providers should build security into their products by default, for example by supporting multi-factor authentication and single sign-on without extra charge, providing security logs to customers, and publishing how they handle vulnerability reports. The company may use the questions in CISA's Secure by Demand Guide when choosing software.

IT service providers. IT service providers with administrative access must use separate, named accounts protected by phishing-resistant multi-factor authentication where available, secure and monitor their remote management tools, keep a record of who accessed company systems and when, and ensure the company always keeps its own administrator access to its systems and data.

6. Business Ethics and Legal Compliance

  • Comply with all laws that apply to their business and to the products and services they supply.
  • Never offer or give bribes, kickbacks, or anything of more than modest value to [Company Name] personnel to win or keep business.
  • Disclose any conflict of interest, such as a family or financial relationship with a company employee involved in buying.
  • Compete fairly, and keep honest and accurate records, quotes, and invoices.
  • Supply only genuine, properly licensed hardware and software, and respect intellectual property.
  • Comply with applicable export control and sanctions laws for the products they supply.
  • Protect confidential information the company shares with them.

7. Labor, Health and Safety

Suppliers must treat their workers with dignity and respect and, at a minimum:

  • Use no forced, bonded, or trafficked labor, and no child labor.
  • Pay at least the legally required wages and benefits, and keep working hours within the law.
  • Not discriminate or tolerate harassment, and respect workers' rights to associate as the law provides.
  • Provide a safe and healthy workplace, including for technicians who work at company sites, who must follow company safety rules.
  • Let workers raise concerns without fear of retaliation.

Hardware makers. For manufacturers of IT hardware, the company uses the Responsible Business Alliance Code of Conduct, whose sections cover labor, health and safety, environment, ethics, and management systems, as the benchmark. Suppliers that are RBA members, or that can show a comparable code and audit program for their factories and component suppliers, meet this section.

8. Environment, Take-Back and Recycling

Suppliers must comply with the environmental laws that apply to their operations and products.

In addition, the company expects suppliers to:

  • Offer a take-back, trade-in, or recycling option for the products and packaging they supply, or tell the company how to recycle them through a certified recycler.
  • Offer energy-efficient products and share energy use information when asked, so the company can compare options.
  • Minimize packaging, use recyclable or reusable packaging where practical, and consolidate shipments.
  • Comply with laws restricting hazardous substances in electronics, and provide product safety and substance information on request.

Disposal vendors and recyclers. IT disposal vendors and recyclers must hold a current certification to a recognized electronics recycling standard, such as R2 or e-Stewards, the two standards the U.S. EPA names, for the facility that handles company equipment. They must sanitize or destroy all data following NIST SP 800-88, provide certificates, and manage downstream recycling and any export in line with the law and their certification.

9. Evidence and the Right to Ask

Suppliers must be able to show that they meet this code. [Company Name] may ask key suppliers for a self-assessment questionnaire covering the topics in this code, supported by current certifications and independent reports, such as a SOC 2 Type II report, an ISO/IEC 27001 certificate, a sustainability rating scorecard, or a certificate from a recycling standard such as R2 or e-Stewards.

  • Requests are proportionate to the supplier's size, its access to company systems and data, and the value of the relationship.
  • Where a supplier already has an independent report or certification that covers a topic, the company accepts it instead of asking the same questions again.
  • Key suppliers must provide a current certificate of insurance on request.
  • Where the contract allows it, the company or its representative may review a key supplier's practices with reasonable notice.
  • The company keeps supplier evidence confidential and uses it only to manage the relationship.

10. Choosing and Onboarding Suppliers

  1. Before buying, decide whether the supplier will be a key supplier.
  2. For key suppliers, collect evidence under this code before signing, and include in the contract the security, data protection, incident notice, and data return or deletion terms in this code.
  3. Ask every supplier to acknowledge this code in writing, or include a contract clause that requires compliance with it.
  4. Record the supplier, its category, and the evidence received in the supplier list.

Where two suppliers are otherwise comparable, the company prefers the one that better meets this code, including its environmental and take-back expectations.

11. Reviews and When a Supplier Falls Short

Reviews. The IT Manager reviews key suppliers at least once a year, checking that evidence and certifications are current and that any incidents were handled as this code requires, and reviews the full supplier list at least once a year.

Falling short. When a supplier does not meet this code, the company and the supplier agree a corrective action plan with deadlines. If the supplier does not complete it, the company may limit the supplier's access, stop new orders, or end the relationship as the contract allows.

Serious breaches. Bribery, forced or child labor, deliberate concealment of a security incident, or other serious breaches of law or ethics are reported to the Chief Executive Officer immediately and may lead to ending the relationship at once, as the contract allows.

Measuring results. The IT Manager reports to the Chief Executive Officer at least once a year on the share of suppliers that have acknowledged this code, the key suppliers reviewed, and open corrective action plans, so the company can report its progress to customers and sustainability assessments.

12. Reporting Concerns

Suppliers, their workers, and company personnel can report a suspected breach of this code to the IT Manager. Reports can also be made directly to the Chief Executive Officer. The company reviews every report, keeps it as confidential as possible, and does not tolerate retaliation against anyone who reports in good faith.

13. Exceptions and Review

Exceptions. Some suppliers, such as very large software or cloud providers, will not sign a customer's code. In that case the IT Manager may accept the supplier's own published code, security documentation, and contract terms if they are substantially equivalent, and records the decision. Exceptions for key suppliers require approval by the Chief Executive Officer and are reviewed at least once a year.

Code review. The IT Manager reviews this code no later than October 2, 2027, and sooner after a supplier-related incident, a new customer or regulatory requirement, or the adoption of a company-wide supplier code.

15. Document Control and Revision History

FieldValue
StatusDraft generated from a template. Not in effect until reviewed by your legal counsel and approved and signed below.
DocumentIT Supplier Code of Conduct
Organization[Company Name]
Document IDPDC-ITSC-SAMPLE
Document version1.0
Effective dateOctober 2, 2026
Next scheduled reviewOctober 2, 2027
Policy ownerIT Manager
Approver (title)Chief Executive Officer
Source templatePreferred Data Corporation IT Supplier Code of Conduct template v1.0.1
Template content last reviewedOctober 2, 2026

Approval. Sign below to approve this document for adoption by [Company Name] after it has been reviewed by your legal counsel. Until it is signed, it is a draft and is not in effect.

Name

Title

Signature

Date

Revision history. Record every change to this code of conduct below. Increase the document version and obtain approval again each time the code of conduct is revised.

VersionDateDescription of changeApproved by
1.0October 2, 2026Draft generated from template v1.0.1; pending legal review and approvalBlank
BlankBlankBlankBlank
BlankBlankBlankBlank

16. Template Notice and Legal Disclaimer

This document was generated from a starter template provided by Preferred Data Corporation. It is general information only. It is not legal advice and it is not a substitute for advice from a licensed attorney. Using the template does not create an attorney-client, consulting, or other professional relationship.

Preferred Data Corporation is not a law firm or an insurer. It makes no representation that this document is complete, current, or suitable for any particular organization, industry, jurisdiction, or regulatory requirement. To the fullest extent permitted by law, it is not responsible or liable for any loss or damage arising from the use of this template or of any policy created from it. You are solely responsible for how you adapt, adopt, and enforce it.

Laws, regulations, insurance requirements, and contracts that apply to your organization may require different or additional terms. The facts, deadlines, and legal references in this template were checked against their sources on the date shown as "Template content last reviewed" in Document Control, not on the effective date, and may have changed since. Before you adopt, publish, or rely on this document, and in every case where you have a legal, regulatory, or contractual obligation, have it reviewed by qualified legal counsel.

In an actual security incident or data breach, contact your attorney, your cyber insurer, and law enforcement where appropriate. Do not rely on this template alone to decide whether, when, or how to notify anyone.

If Preferred Data Corporation prepared this document for you as part of its services, your service agreement governs those services. The content of this document is still general information and should be reviewed by your own counsel before you adopt it.

This template is provided "as is", without warranties of any kind, including accuracy, completeness, or fitness for a particular purpose. Links to laws, agencies, and other websites are provided for convenience and may change. Use of this template is also subject to the Website and Free Resources Disclaimer and the Terms of Service at preferreddata.com/legal/disclaimer and preferreddata.com/legal/terms-of-service.

To report an error, contact Preferred Data Corporation at preferreddata.com/contact or (336) 886-3282 and include the Document ID shown in Document Control. Corrections are listed in the template changelog on the template's page at preferreddata.com/policy-templates.

How does the IT Supplier Code of Conduct generator work?

5 short phases, about 4 minutes in total. Policy choices start at a suggested setting, with the reason we suggest it. Facts about your organization, such as the data you hold or the tools you use, start blank and you answer them.

  1. Your organization

    The basics that shape who the document covers and which obligations it has to respect.

  2. Which suppliers it covers

    The kinds of IT suppliers covered and how the code is rolled out.

  3. What you expect

    Your security deadline and environmental expectations.

  4. Checking and follow-up

    How you confirm suppliers meet the code and what happens if they do not.

  5. Ownership and review

    Who owns the document, who approves it, and how it stays current.

  6. Review and download

    Preview your code of conduct, unlock the full document and download it as a PDF with a document ID and review date.

Start the generator

Who should adopt this code of conduct?

  • Manufacturers and other suppliers asked by customers or EcoVadis for evidence of a supplier code or sustainable procurement policy.
  • IT managers and office managers who buy hardware, software, and cloud services and want security and data terms in writing.
  • Owners who rely on a managed IT provider and want clear expectations for any vendor with access to company systems.
  • Sustainability and compliance leads who need a starting point for IT before building a company-wide supplier code.

Which frameworks does this template align with?

The template was written against these public frameworks, laws and standards. Alignment is not certification, and your obligations depend on your industry and location.

Framework or lawWhy it matters for this code of conduct
CISA, Cybersecurity Performance Goals 2.0(opens in a new tab)Goal 1.D calls for contracts requiring vendors to report security incidents and vulnerabilities, and goal 1.E addresses risks from managed service providers.
CISA, Secure by Demand Guide(opens in a new tab)Questions to ask software suppliers about how they build security into their products.
NIST SP 800-161 Rev. 1, Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations(opens in a new tab)NIST guidance on identifying, assessing, and reducing cybersecurity risk from suppliers, scaled down here for a small business.
Responsible Business Alliance, Code of Conduct v8.0(opens in a new tab)The electronics industry benchmark for labor, health and safety, environment, ethics, and management systems, used as the reference for hardware makers.
EcoVadis, Sustainability Rating Methodology disclosure document(opens in a new tab)Defines the Sustainable Procurement theme and its two criteria, Supplier Environmental Practices and Supplier Social Practices.
U.S. EPA, Certified Electronics Recyclers(opens in a new tab)Names the R2 and e-Stewards standards used in this code's expectations for recyclers and take-back.

IT Supplier Code of Conduct questions, answered

What should an IT supplier code of conduct include?

Security and data protection expectations, such as multi-factor authentication and prompt notice of security incidents; business ethics, such as no bribes or kickbacks; basic labor and human rights standards; environmental expectations, including take-back and recycling of old equipment; and the company's right to ask for evidence and to act when a supplier falls short.

Is a supplier code of conduct required by law?

Not generally for a private small or mid-sized business, and this template does not claim otherwise. Some laws do require you to oversee certain suppliers, for example the FTC Safeguards Rule requires covered financial businesses to select capable service providers, require safeguards by contract, and assess them periodically. Large customers and sustainability ratings such as EcoVadis also increasingly ask whether you have one.

How does a supplier code help with EcoVadis?

EcoVadis rates companies on four themes, one of which is Sustainable Procurement, with two criteria: Supplier Environmental Practices and Supplier Social Practices. EcoVadis scores policies, actions, and reporting, so a written supplier code is a starting point, and it counts for more when you also collect supplier acknowledgments and assessments and report the results.

Why only IT suppliers?

Because IT purchasing is where an IT department can act on its own and where the security risk is concentrated. A company-wide supplier code also covers raw materials, freight, contract labor, and facilities, and needs owners in human resources, legal, procurement, and sustainability. This template is a working start that those owners can later expand or replace.

What evidence can we ask IT suppliers for?

Common evidence includes a completed security questionnaire, a SOC 2 Type II report or ISO/IEC 27001 certificate, a certificate of insurance, a sustainability rating scorecard, and for recyclers an R2 or e-Stewards certificate. For software, CISA's Secure by Demand Guide lists questions to ask manufacturers about how they build security into their products.

How fast should a supplier tell us about a security incident?

Set a deadline in the contract. CISA's Cybersecurity Performance Goals call for procurement documents and contracts that require vendors to notify the customer of security incidents and vulnerabilities within a risk-informed time frame the customer sets. This template defaults to 72 hours, which leaves time to meet your own legal deadlines.

Related policy templates

More free guides, tools, checklists and templates on the same topics as this code of conduct.

Services that put this code of conduct into practice

Want help rolling out your IT Supplier Code of Conduct?

A policy works when the tools, training and controls behind it do. Preferred Data Corporation helps businesses put policies like this one into practice, from High Point, NC since 1987.