🧠
Harpe Wiki
Raise a bug
  • Introduction
  • Getting started
    • Set up your ISMS
      • Add employees
      • Complete management details
      • Add your first asset
      • Add your first supplier
      • Add your first risk
      • Add your first CAPA
      • Add your first incident
      • Review your documents tab
      • Assess your compliance
      • Configure your Harpe feed
  • Manual
    • Management
      • Overview
      • Objectives
        • Overview
        • Adding an Objective
        • Viewing an Objective
        • Example Objectives
      • Interested Parties
        • Overview
        • Adding an Interested Party
        • Viewing an Interested Party
        • Example Interested Parties
      • Management Review
        • Overview
        • Adding a Management Review
        • Viewing a Management Review
        • Example Management Reviews
      • Audit
        • Overview
        • Adding an Audit
        • Viewing an Audit
        • Example Audits
      • Legal and Regulatory
        • Overview
        • Adding a Legislation
        • Viewing a Legislation
        • Example Legislations
    • Feed
    • Assets
      • Overview
      • Adding an Asset
      • Viewing an Asset
      • Example Assets
    • Suppliers
      • Overview
      • Adding a Supplier
      • Viewing a Supplier
      • Example Suppliers
    • People
      • Overview
      • Adding a Person
      • Viewing a Person
      • Example People
    • Risks
      • Overview
      • Adding a Risk
      • Viewing a Risk
      • Example Risks
    • CAPA
      • Overview
      • Adding a CAPA
      • Viewing a CAPA
      • Example CAPAs
    • Incidents
      • Overview
      • Adding an Incident
      • Viewing an Incident
      • Example Incidents
    • Docs
      • Overview
      • Adding a Document
      • Viewing a Document
      • Example Docs
    • Assess
      • Harpe Wizard
      • ISO27001:2013
      • ISO27001:2022
      • Phishing
    • Training
      • Security Awareness Training
      • Policy and Procedure Training
  • Settings
    • Company Settings
      • Connected Services
      • Targets to monitor
      • Automations
  • ISO27001:2013 Wiki
    • Overview
    • The Clauses
      • Clause 4 - Context of the Organisation
      • Clause 5 - Leadership
      • Clause 6 - Planning
      • Clause 7 - Support
      • Clause 8 - Operation
      • Clause 9 - Performance Evaluation
      • Clause 10 - Improvement
    • Annex A Controls
      • Annex A.5 - Information Security Policies
      • Annex A.6 - Organisation of Information Security
      • Annex A.7 - Human Resources Security
      • Annex A.8 - Asset Management
      • Annex A.9 - Access Control
      • Annex A.10 - Cryptography
      • Annex A.11 - Physical and Environmental Security
      • Annex A.12 - Operations Security
      • Annex A.13 - Communications Security
      • Annex A.14 - Systems Acquisition, Development, and Maintenance
      • Annex A.15 - Supplier Relationships
      • Annex A.16 - Information Security Incident Management
      • Annex A.17 - Information Security Aspects of Business Continuity
      • Annex A.18 - Compliance
  • ISO27001:2022 Wiki
    • Overview
    • Annex A Controls
      • Annex A.5 - Organisational Controls
        • Annex A 5.1 - Policies for Information Security
        • Annex A 5.2 - Information Security Roles and Responsibilities
        • Annex A 5.3 - Segregation of Duties
        • Annex A 5.4 - Management Responsibilities
        • Annex A 5.5 - Contact With Authorities
        • Annex A 5.6 - Contact With Special Interest Groups
        • Annex A 5.7 - Threat Intelligence
        • Annex A 5.8 - Information Security in Project Management
        • Annex A 5.9 - Inventory of Information and Other Associated Assets
        • Annex A 5.10 - Acceptable Use of Information and Other Associated Assets
        • Annex A 5.11 - Return of Assets
        • Annex A 5.12 - Classification of Information
        • Annex A 5.13 - Labelling of Information
        • Annex A 5.14 - Information Transfer
        • Annex A 5.15 - Access Control
        • Annex A 5.16 - Identity Management
        • Annex A 5.17 - Authentication Information
        • Annex A 5.18 - Access Rights
        • Annex A 5.19 - Information Security in Supplier Relationships
        • Annex A 5.20 - Addressing Information Security Within Supplier Agreements
        • Annex A 5.21 - Managing Information Security in the ICT Supply Chain
        • Annex A 5.22 - Monitoring, Review and Change Management of Supplier Services
        • Annex A 5.23 - Information Security for Use of Cloud Services
        • Annex A 5.24 - Information Security Incident Management Planning and Preparation
        • Annex A 5.25 - Assessment and Decision on Information Security Events
        • Annex A 5.26 - Response to Information Security Incidents
        • Annex A 5.27 - Learning From Information Security Incidents
        • Annex A 5.28 - Collection of Evidence
        • Annex A 5.29 - Information Security During Disruption
        • Annex A 5.30 - ICT Readiness for Business Continuity
        • Annex A 5.31 - Legal, Statutory, Regulatory and Contractual Requirements
        • Annex A 5.32 - Intellectual Property Rights
        • Annex A 5.33 - Protection of Records
        • Annex A 5.34 - Privacy and Protection of PII
        • Annex A 5.35 - Independent Review of Information Security
        • Annex A 5.36 - Compliance With Policies, Rules and Standards for Information Security
        • Annex A 5.37 - Documented Operating Procedures
      • Annex A.6 - People Controls
        • Annex A 6.1 - Screening
        • Annex A 6.2 - Terms and Conditions of Employment
        • Annex A 6.3 - Information Security Awareness, Education and Training
        • Annex A 6.4 - Disciplinary Process
        • Annex A 6.5 - Responsibilities After Termination or Change of Employment
        • Annex A 6.6 - Confidentiality or Non-Disclosure Agreements
        • Annex A 6.7 - Remote Working
        • Annex A 6.8 - Information Security Event Reporting
      • Annex A.7 -Physical Controls
        • Annex A 7.1 - Physical Security Perimeters
        • Annex A 7.2 - Physical Entry
        • Annex A 7.3 - Securing Offices, Rooms and Facilities
        • Annex A 7.4 - Physical Security Monitoring
        • Annex A 7.5 - Protecting Against Physical and Environmental Threats
        • Annex A 7.6 - Working In Secure Areas
        • Annex A 7.7 - Clear Desk and Clear Screen
        • Annex A 7.8 - Equipment Siting and Protection
        • Annex A 7.9 - Security of Assets Off-Premises
        • Annex A 7.10 - Storage Media
        • Annex A 7.11 - Supporting Utilities
        • Annex A 7.12 - Cabling Security
        • Annex A 7.13 - Equipment Maintenance
        • Annex A 7.14 - Secure Disposal or Re-Use of Equipment
      • Annex A.8 - Technological Controls
        • Annex A 8.1 - User Endpoint Devices
        • Annex A 8.2 - Privileged Access Rights
        • Annex A 8.3 - Information Access Restriction
        • Annex A 8.4 - Access to Source Code
        • Annex A 8.5 - Secure Authentication
        • Annex A 8.6 - Capacity Management
        • Annex A 8.7 - Protection Against Malware
        • Annex A 8.8 - Management of Technical Vulnerabilities
        • Annex A 8.9 - Configuration Management
        • Annex A 8.10 - Information Deletion
        • Annex A 8.11 - Data Masking
        • Annex A 8.12 - Data Leakage Prevention
        • Annex A 8.13 - Information Backup
        • Annex A 8.14 - Redundancy of Information Processing Facilities
        • Annex A 8.15 - Logging
        • Annex A 8.16 - Monitoring Activities
        • Annex A 8.17 - Clock Synchronization
        • Annex A 8.18 - Use of Privileged Utility Programs
        • Annex A 8.19 - Installation of Software on Operational Systems
        • Annex A 8.20 - Networks Security
        • Annex A 8.21 - Security of Network Services
        • Annex A 8.22 - Segregation of Networks
        • Annex A 8.23 - Web filtering
        • Annex A 8.24 - Use of Cryptography
        • Annex A 8.25 - Secure Development Life Cycle
        • Annex A 8.26 - Application Security Requirements
        • Annex A 8.27 - Secure System Architecture and Engineering Principles
        • Annex A 8.28 - Secure Coding
        • Annex A 8.29 - Security Testing in Development and Acceptance
        • Annex A 8.30 - Outsourced Development
        • Annex A 8.31 - Separation of Development, Test and Production Environments
        • Annex A 8.32 - Change Management
        • Annex A 8.33 - Test Information
        • Annex A 8.34 - Protection of Information Systems During Audit Testing
  • Cyber Essentials WIKI
    • Overview
    • Controls
      • 1. Firewalls
      • 2. Secure Configuration
      • 3. User Access Control
      • 4. Malware Protection
      • 5. Security Update Management
      • Further Guidance
        • Backup Your Data
  • Harpe approved
    • Tools
      • Asana
      • Confluence
      • Datadoghq.com
      • GitHub
      • Jira
      • Logz.io
      • Opsgenie
      • Slack
      • Trello
      • Twilio
    • Suppliers
      • Acer
      • Adobe Creative Cloud
      • AgileBits Inc
      • Apple Inc.
      • Apptio
      • Atlassian
      • AWS
      • BILL
      • Block
      • Box
      • Chargebee
      • Datadog
      • Dell Technologies
      • Densify
      • DocuSign
      • Duffel
      • EMIS Health
      • Epignosis
      • ESET
      • E-Sign
      • GitLab
      • Google
      • Gremlin
      • Guidewire
      • Gusto
      • HP (Hewlett - Packard)
      • HSO
      • HubSpot
      • IASME
      • Intuit
      • JetBrains
      • Lenovo
      • Logz.io
      • Lucid Software Inc
      • Meta Platforms Inc
      • Microsoft
      • MongoDB Atlas
      • New Relic
      • Obsidian.md
      • Paycom
      • Periculo
      • Process Street
      • Qualtrics
      • Salesforce
      • ServiceNow
      • Shopify
      • Slack
      • Smartsheet
      • SolarWinds
      • Spendesk
      • Splunk
      • Stripe
      • Tenable
      • Toshiba
      • Twilio
      • Uber
      • Upwork
      • Webflow
      • Workday
      • Workiva
      • Xero
      • Zendesk
      • ZipRecruiter
      • Zoom
  • Payments and refunds
Powered by GitBook
On this page
  1. Manual
  2. Suppliers

Adding a Supplier

PreviousOverviewNextViewing a Supplier

Last updated 1 year ago

Clicking the Add Supplier button brings up the Add Supplier form. The form contains three sections - General Information, Assurance, and Disaster Recovery. Only the General Information tab is required to add a new asset, but it is recommended that all areas are completed.

Supplier Name

The name of the supplier.

Supplier Description

A brief summary of what the supplier does for your organisation.

Supplier Owner

The person responsible for the supplier.

Supplier Contact

The main point of contact for the supplier. This could be, for example, a support page on a website, or a name of a person responsible for liaising between your organisations.

Supplier Email

The email address associated with the supplier.

Supplier Address

The address of the supplier.

Supplier Contact Number

The contact telephone number associated with the supplier.

Last Review Date

When the information for this supplier was last reviewed.

Next Review Date

The date when this supplier will be next reviewed.

Clicking on the Assurance section will bring up the next section which involves ensuring the supplier is up to security standards.

Does the supplier hold ISO27001, or other externally validated certificate that is in line with or exceeds ISO27001?

Whether the supplier is certified against ISO27001. By Harpe's standards, holding an ISO27001 accreditation is an automatic pass in terms of security.

Does the supplier encrypt personal data at rest and in transit?

Encryption of data in transit and at rest refers to the process of converting sensitive data into a coded language that cannot be read or understood by unauthorised users while it is being transmitted from one location to another or securely stored.

Does the supplier adhere to the principle of least privileged and have access control processes in place?

The principle of least privilege is the practice of ensuring employees have the minimum amount of permissions required to do their job to combat permissions creep which could lead to a security risk if the wrong person has access to information that is higher than their rank.

Does the supplier have processes in place to address risk management?

Whether the supplier has risk management processes in place.

Does the supplier train and engage their employees to become cyber aware?

Whether the supplier engages in training employees to ensure they have enough knowledge to be resistant against common cybersecurity threats. For example, phishing emails.

Does the supplier have a process to manage assets throughout their lifecycle, including security and destruction?

Whether the supplier has an adequate process for the management of assets.

Does the supplier have a process to manage disaster recovery and the backups of critical systems?

Whether the supplier has a process for disaster recovery, including taking backups, to ensure system stability in the event of an incident.

Does the supplier have a processes in place to identify and remediate vulnerabilities such as penetration testing or vulnerability scanning?

Whether the supplier performs activities such as penetration testing or vulnerability scanning to identify vulnerabilities in their systems.

Does the supplier have logging and monitoring in place to identify incidents with their assets and data?

Whether the supplier has logging and monitoring enabled for their systems and tools to ensure any changes or breaches are recorded.

Does the supplier have an incident management process in place?

Whether the supplier has processes implemented to manage any occurred incidents.

Does the supplier have process in place to protect and manage their supply chain?

Whether the supplier has processes in place to ensure their supply chain is secure.

Are there contracts that cover security requirements, data protection requirements and confidentiality?

Whether there are legally binding contracts and policies in place with the supplier to ensure cybersecurity requirements are safeguarded.

Does the Supplier have a quality management system in place?

Whether the supplier has a system in place to ensure continued quality of its processes and deliverables.

Assessment result

Whether the supplier passes or fails based on the answers to these questions.

Conducted by

The person responsible for conducting this assurance assessment.

Disaster Recovery Plan

A step-by-step plan to enable business operations to be recovered or allowed to continue in the event of the supplier becoming unavailable or suffering an incident.

Security Considerations during DR

Any security considerations that must be paid attention to in the event of the supplier becoming unavailable or suffering an incident.

RPO (Recovery Point Objective)

The maximum tolerable loss of data in terms of time. For example, a loss in 2 hours work worth of data.

RTO (Recovery Time Objective)

The maximum tolerable time in which an asset can be unavailable. For example, if the RTO is 2 hours then the asset should be available again after failure in less than 2 hours.

BIA Owner

The person who is responsible for this disaster recovery assessment.

Add Supplier form - General Information
Add Supplier form - Assurance
Add Supplier form - Disaster Recovery