🧠
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. Assets

Example Assets

Below are some examples of assets and how they might look once filled in.

Frodo's Laptop

For this example, we'll be adding a work laptop for Frodo.

Asset Name

It's important to give your asset a clear name as this is what will be displayed in the table on the Assets page.

Frodo's Laptop

Asset Type

We will now select what the asset is. For this example, it is a laptop.

Laptop

Asset Description

This is a brief description of what the asset is. This could include make, model, serial number, etc. as desired. For this example, we will just write a simple description.

Frodo's work laptop.

Date Onboarded

This is the date in which the asset was introduced to the organisation. We will input 8th July 2023 as an example for this.

08/07/2023

Critical

For the purposes of this example, we will mark the asset as critical to activate the Disaster Recovery section.

Yes

Asset Owner

Since this laptop belongs to Frodo, we'll assign the asset owner as Frodo Baggins.

Frodo Baggins

Last Review Date

This would be the date where Frodo's laptop was last reviewed. For the purposes of this example we'll assume this was when we onboarded the laptop.

08/07/2023

Next Review Date

This will be automatically set to a year from the last review date. Since we've set the last review date as 08/07/2023, this will be set to 08/07/2024. To maintain compliance, assets must be reviewed at least yearly to ensure they remain up to security standards.

08/07/2024

Has an access review been carried out in the last 12 months on the system, including administrators?

Whether a review of employees' access has been conducted within the last 12 months on the respective asset.

Yes

Does the system encrypt data in transit?

Whether the asset encrypts data while it is being transferred over a connection.

Yes

Does the system encrypt data at rest?

Whether the asset encrypts data in its storage.

Yes

Have logs been reviewed regularly and incidents raised for suspicious event?

Whether any logs associated with the asset are regularly checked for potential incidents.

Yes

Has a vulnerability scan or penetration test been performed on the system and issues remediated?

Whether a vulnerability scan or penetration test has been performed to ensure there are no active vulnerabilities or misconfigurations within an asset.

Yes

Has a backup and restore been carried out to ensure that the disaster recovery process works for the system?

Whether backups of the assets data has been performed so that in case of an outage, any lost data can be restored.

Yes

Has multi-factor authentication been implemented on the system for all users?

Whether multi-factor authentication has been enabled where possible.

Yes

Has the system been reviewed to cleanse and ensure quality of the data inline with retention policies?

Whether the system has been checked to ensure data is within data retention parameters.

Yes

Result of assessment

Whether this asset has passed or failed its assessment based on previous answers.

Pass

Conducted by

The person responsible for conducting this assessment.

Bilbo Baggins

If an asset is marked as critical, the Disaster Recovery section will be available to complete.

Disaster Recovery Plan

The steps to follow in order to recover this asset in the event of an incident or disaster.

Step 1) Determine the status of the laptop:
If the laptop is lost, stolen, or damaged, immediately report it to the IT manager and follow their instructions for further actions.
In case of theft, report the incident to both the IT manager and the police to initiate appropriate measures.

Step 2) IT manager initiates remote data wipe and tracking:
If the laptop is lost or stolen, the IT manager should remotely wipe the device to protect sensitive data.
If available, utilise tracking software or services to locate the laptop or increase the chances of recovery.

Step 3) IT manager issues a temporary or new laptop:
The IT manager should provide a temporary laptop or arrange for a replacement to ensure minimal disruption to the employee's work.

Step 4) Determine repair or replacement options:
Assess the extent of damage and consult with the IT manager to determine whether the laptop can be repaired or if a replacement is necessary.
If repair is required, send the laptop to a trusted manufacturer or repair service.

Step 5) Restore data and applications:
If a new laptop is issued, the IT manager should restore necessary data and applications from backups or cloud services.
Ensure that all restored data is up to date and compatible with the new laptop.

Step 6) Change passwords and strengthen security:
Prompt the user to change passwords for all cloud-based services and accounts to prevent unauthorised access.
Encourage the use of strong, unique passwords and enable multi-factor authentication for enhanced security.

Step 7) Decommission the old laptop:
If the laptop is beyond repair or has been replaced, securely wipe all data or physically destroy the storage device before disposing of it.
Follow appropriate procedures to ensure compliance with data protection regulations.

Step 8) Evaluate and improve the disaster recovery plan:
Conduct a post-incident review to identify any gaps or areas for improvement in the plan.
Update the plan accordingly to address any shortcomings and enhance future response and recovery efforts.

Security considerations during DR

What points of security must be considered in terms of this asset in the event of an incident. For example, employee or client data if a work laptop is stolen.

Ensure IT manager is informed as soon as possible so the appropriate actions can be implemented. Ensure Police are notified if laptop is reported stolen 

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.

1 day

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.

1 day

BIA Owner

This is the person who conducted this disaster recovery assessment and is responsible. For this example, we'll say Bilbo Baggins conducted the assessment.

Bilbo Baggins
PreviousViewing an AssetNextSuppliers

Last updated 1 year ago