Thank you so much. Could you please advise the two methods the company can use to determine its level of legal compliance. Thank you.
Standards in ISO 27001 series
Answer: As you pointed, ISO 27001 has recommended control objectives and controls for all areas you mentioned, and in terms of an ISO certified management system it is enough to be in compliance with only ISO 27001. The other standards you mentioned provide additional information and details about how to implement controls described in ISO 27001 Annex A, but they are not required for certification. Think of them as useful tools to improve your controls.
These materials will also help you regarding general guidelines for ISO 27001 implementation:
- Book Secure & Simple: A Small-Business Guide to Implementing ISO 27001 On Your Own https://advisera.com/books/secu re-simple-a-small-business-guide-toimplementing-iso-27001-on-your-own/
- Free online training ISO 27001 Foundations Course https://advisera.com/training/iso-27001-foundations-course/
Schedule for testing controls under ISO 27001
Answer: Specific guidance for control testing is difficult to provide since each organization context and risks are unique, but you can use some of the criteria applied to planning internal audits to help define a proper test schedule, like:
- Criticality of the assets under protection of the control: the more critical the asset, the more frequent should be controls testing.
- Frequency of changes: the more frequent changes in assets or in the environment where the asset operates, the more frequent should be controls testing.
- Results of previous test: previous tests pointing corrections or improvement to be made, should be considered to reduce interval between tests.
It is important to note that testing of controls should not be confused with internal audit; in smaller companies, internal audit is usually performed once a year by people independent of the audited process, while testing generally is performed by people involved in the process.
Regarding documentation, unfortunately we do not have a template that covers controls testing, but I suggest you to take a look at the following templates, since I believe that with some adaptations you can make them more general and use them to help you testing a wider range of controls :
Answer: ISO 27001 makes use of process approach and PDCA cycle concepts to help organizations protect their information and those from other interested parties under their responsibility. In terms of benefits, ISO 27001 can help identifying and prioritizing information security risk according business objectives, optimizing resources allocation and reducing costs of incidents.
Answer: Some techniques you may use to identify needs and expectations that are base for ISMS's requirements are:
- documentation review, covering documents like the strategic plan, policies, procedures, contracts, and laws, among others
- interviews with top management, process owners, key users, clients and suppliers representatives.
The use of checklists also can help you not forget relevant topics and optimize your time and effort.
Answer: The approach considered by certification bodies is that a proper scope statement can be defined based on processes, organizational units, or physical locations, not in the format of the information medium. Therefore, your scope statement cannot limit information to be protected to electronic data only.
Answer: Yes, the time you need to complete for each of these activities, and the sequences and dependencies that exist between them, will provide you the information about the total time required for risk treatment completion.
In the video tutorials that came with your toolkit, you will see information on how to fill out all the data about the risk treatment plan.
Is ISO 27001 Risk Assessment Methodology applicable to ISO 22301
Answer:
This is certainly a very good question - actually you can use the ISO 27001 risk assessment methodology also for ISO 22301, because this methodology is so called "asset-based" methodology which lists all the assets, then all related vulnerabilities and threats, and finally calculates the level of risk.
But you are right, there are couple of differences:
1) Information security risk assessment must take into account the consequences related to confidentiality, integrity and availability of assets, whereas the business continuity risk assessment must take into account only the consequences related to availability. Therefore, you can delete "confidentiality" and "integrity" when they are mentioned in the document.
2) ISO 22301 does not require you to have a document called Statement of Applicability, so you can avoid it if you see no value in it for your business continuity (t his document is mentioned in the Risk assessment methodology).
3) Instead of asset-based methodology you can decide to go for a methodology that will be based on critical activities and processes - this will be probably quicker than the asset-based methodology mentioned above, but this will also be less accurate.
Answer: We may say ISO 27001 can provide business values in the following aspects: compliance, marketing edge, expenses decreasing and strengthening of the internal structure. That being said, the following articles may provide you examples about business value that can be achieved with ISO 27001:
Answer: Considering the content of ISO 27013, there is no ISO similar document regarding integration of specific aspects of ISO 27001 (risk assessment and treatment) and ISO 22301 (business impact analysis and business continuity plans), but since both standards follow the same structure, based on ISO Annex SL, their management aspects (e.g., document control, internal audit, management review, etc.) are practically the same, which makes the integration job easier.