🧠
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

Adding an Asset

PreviousOverviewNextViewing an Asset

Last updated 1 year ago

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

Asset Name

The name of the asset.

Asset Type

The type of asset. The options are as follows:

Type
Description

Browser

Any component of a web browser that is critical to maintaining the security and integrity of the information being accessed or transmitted through the browser.

Cloud Service

Any component of the cloud computing environment that is critical to the security and availability of the cloud service. This can include data storage, virtual machines, network infrastructure, and other resources provided by the cloud service provider.

Desktop

Any physical device, software or data stored on a computer that is considered important for maintaining the security and integrity of an organisations information system.Email Application.

Firewall

A security control that is used to protect a network from unauthorised access and to prevent malicious traffic from entering or leaving the network.

Hypervisor

Any software or hardware component that enables virtualisation on a server.

Information Asset

Any piece of information that is valuable to an organization and needs to be protected. It can be anything from customer data to financial information or intellectual property.

Laptop

Any laptop computer that contains sensitive or valuable information that needs to be protected from unauthorised access, use, or disclosure.

Malware Protection

A security measure that aims to prevent and detect malicious software or computer viruses from infecting computer systems or networks.

Mobile Device

Also known as a cell phone or smartphone, is a portable electronic device that allows people to make and receive phone calls, send and receive text messages, and access the internet and various mobile applications.

Network

A group of interconnected devices such as computers, servers, and other electronic devices that communicate with each other through various communication channels such as wired or wireless connections.

Office Application

Any type of computer software designed to help users perform common tasks related to office work, such as creating and editing documents, spreadsheets, presentations, emails, and other types of digital content.

Router

A router is a device that is used to connect different networks together and route data traffic between them.

Server

A computer system that is used to store and manage data and resources, and can be used to support information security management systems (ISMS).

Tablet

A type of mobile computing device that is typically larger than a smartphone but smaller than a laptop. It is a flat, portable computer that is operated through a touchscreen interface and typically lacks a physical keyboard.

Thin Client

A computer that runs a lightweight operating system, such as Google's Chrome OS, and relies on a remote server to perform most of the processing and data storage.

Virtual Desktop

A desktop computing environment that is hosted and managed in a virtualised environment, typically on a server or in the cloud.

Virtual Server

A type of server that runs within a virtual environment, created by a virtualisation technology. It is a simulated server that provides the same functionality as a physical server, but it exists only in software.

Asset Description

A brief description of what the asset is.

Date Onboarded

The date on which this asset was first introduced to the organisation.

Critical

Whether the asset is critical for business operations or not.

Asset Owner

The person responsible for this asset.

Last Review Date

The last date on which this asset was reviewed.

Next Review Date

The next scheduled date for this asset to be reviewed.

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.

Does the system encrypt data in transit?

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

Does the system encrypt data at rest?

Whether the asset encrypts data in its storage.

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

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

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.

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.

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

Whether multi-factor authentication has been enabled where possible.

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.

Result of assessment

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

Conducted by

The person responsible for conducting this assessment.

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.

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.

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 Asset form - General Information
Add Asset form - Assurance
Add Asset form - Disaster Recovery