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

Example CAPAs

Internal audits need to be established and carried out on a regular basis

CAPA Name

The individual name given for the CAPA.

Internal audits need to be established and carried out on a regular basis

Status

The term status refers to the current condition or state of a Corrective and Preventive Actions (CAPA).

  • Open - This status indicates that a CAPA has been identified and is under investigation. At this stage, further investigation or analysis may be required to determine the appropriate action to take.

  • Closed - This status indicates that the CAPA has been implemented and the corrective or preventive action has been completed. At this stage, the results of the action taken may be evaluated to determine if the issue has been resolved satisfactorily.

For the purposes of this example, we'll say that this CAPA is resolved now.

Closed

Rating

  • Minor - This CAPA is seen as a minor improvement to be made to the organisation.

  • Major - This CAPA is seen as a major improvement or correction that must be made by the organisation.

Major

CAPA Owner

The CAPA Owner section refers to the person responsible for implementing and managing the corrective and preventive actions identified as part of the ISMS.

Bilbo Baggins

Identified By

The person responsible for identifying this CAPA.

Bilbo Baggins

Asset Affected

Select an asset from the asset list which is most affected by the CAPA.

Since this CAPA doesn't really affect an asset, we'll leave this blank.

CAPA Description

The description section offers a detailed and complete summary of the CAPA, providing the reader with a clear understanding of what it entails.

We currently do not carry out internal audits to determine what areas of the organisation may be lacking in terms of compliance. We will start planning and conducting these quarterly.

Date Identified

The specific date on which the CAPA was raised.

03/08/2023

Date Completed

The specific date on which the CAPA was actioned. If ongoing then leave section blank.

09/08/2023

What Investigation was carried out?

Provide a detailed explanation of what investigation was carried out.

Audit of internal processes

Root Cause Analysis

A root cause analysis (RCA) for a Corrective and Preventive Action (CAPA) in an Information Security Management System (ISMS) is a process of identifying the underlying cause(s) of an issue or problem in the organisation's security controls, processes, or procedures.

The purpose of conducting an RCA is to determine the source of the problem and prevent its recurrence in the future. The RCA process involves identifying the problem, analysing the problem's symptoms, identifying the contributing factors, and identifying the root cause(s) of the issue.

ISMS implementation was in early stages and this had not yet been implemented.

Corrective Action

Describe what actions have been identified as needed and how they have been put in place.

We now have a documented internal audit schedule.

Have you verified that the actions are effective?

If the corrective actions have been verified to be effective in solving the problem.

Yes
PreviousViewing a CAPANextIncidents

Last updated 1 year ago