Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
You must have a way of knowing the number of distributed hard copies in use. When they became obsolete, you just exchange the now obsolete copies with the new version. Obsolete copies must be destroyed. You can use a shredder, or simply stamp obsolete in a clearly visible way. The original document, now obsolete, can be destroyed or stamped as obsolete and kept in a file just for obsolete documents.
You can find more information about document control below:
Consider the strategic orientation of your organization. What kind of training services are provided? What kind of target customers are chosen? And how does your organization want to differentiate itself in the market?
Periodically, review the internal context, for example quarterly. What kind of issues systematically arise in the reports and internal meetings (complaints, successes, costs, training occupancy rates, customer satisfaction, trainers satisfaction, ...). Classify the positive internal issues as strengths and the negative internal issues as weaknesses.
Periodically, review the external context, for example quarterly. For this kind of monitoring I use the PESTL analysis framework in order to support the discipline of questioning the mind around various areas that may affect an organization (politics, economics, social, technology, legislation and environment). After the PESTL analysis I recommend collecting positive external issues as opportunities and negative external issues as threats, and organize the information in a SWOT matrix that allows us to determine potential risks and opportunities. Please check these two free webinars where I demonstrate the use of the technique:
For example, one can imagine a training institution, considering the consequences, the opportunities and threats coming after a lockdown economy where many people started to attend webinars and training online.
You can find more information in the following links:
The best combination will depend on:
Broadly speaking, COBIT covers governance aspects of IT, ISO helps cover information security aspects of IT, and ITIL covers operational and management aspects of ITIL.
These articles will provide you a further explanation about these frameworks:
These materials will also help you regarding audit:
The types of tests to be performed will depend on:
Broadly speaking, there are basically 3 types of "tests" that can be related to ISO 27001:
Regarding the cost estimates, the best approach is to request a couple of quotations of companies which provide such tests, so you can make a comparison.
This article will provide you a further explanation about tests:
ISO 27001 does not prescribe which methodology an organization must use for risk assessment and risk treatment, only that an approach must be defined, so organizations can adopt the approach that better fits them.
Since you are already ISO 27001 certified, the initial recommendation is for you to keep the approach adopted in the preparation for the certification (it was validated by the certification auditor), and then ask both your external consultant and the auditor about the pros and cons of each recommended approach considering your organizational context, so you can evaluate if you, in fact, need to change your current approach.
For further information, see:
I'm assuming that by BAU you mean "Business as Usual".
Considering that, by the size of this company, it is easier to define that only the headquarters is in the ISMS scope, and treat all other locations as outsourced parties.
In this approach, you can treat the risks related to the remote locations by means of controls from section A.15.
These articles will provide you a further explanation about the scope definition and supplier management:
The requirements for the evaluation of the ISMS performance are stated in section 9 of the ISO 27001. It is true that the standard does not prescribe what to check, but the items included in the procedures are the most commonly used in ISO 27001 related documents, and of course, since the templates are fully editable, you can define other items for checking the effectiveness of the procedure.
This article will provide you a further explanation about performance measurement:
ISO 27001 does not prescribe how to record ISMS Internal Audit Findings, but the most common approach is through an Internal Audit Report.
To see how an Internal Audit Report compliant with ISO 27001 looks like, I suggest you see the free demo of our Internal Audit Report at this link: https://advisera.com/27001academy/documentation/internal-audit-report/
This article will provide you a further explanation about internal audit:
These materials will also help you regarding internal audit:
I'm assuming you are talking about ISO 27001, which defines requirements for the ISMS. ISO 27000 defines the vocabulary for ISO 27001 series of standards.
Considering that, regarding disaster recovery, ISO 27001 defines objectives and controls (what must be achieved) related to information security aspects of business continuity, on Annex A, section A.17, but it does not provide guidance on how to implement such controls.
But please note that disaster recovery is required by ISO 27001 only if you have relevant risks, or legal requirements (e.g., laws, regulations, and contracts), that require the implementation of disaster recovery.
In this case, for guidance, you can use either ISO 27002, which provides guidance on the implementation of ISO 27001 Annex A controls, or ISO 22301, but please note that neither are required to be used for ISO 27001 implementation.
These articles will provide you a further explanation about ISO 27002 and ISO 22301:
This material will also help you regarding controls implementation:
Generally speaking, after risk assessment you need to:
These articles will provide you a further explanation about ISO 27001 implementation:
These materials will also help you regarding ISO 27001 implementation: