Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Search results
11268 results
Guest
Guest
Create New Topic As guest or Sign in
Assign topic to the user
-
Design compliance plan for internal use
Kumar, it is neither option 1 nor 2.
You should start with assessing the risks, because the whole idea of ISO 27001 is centered on risk assessment - once you perform the risk assessment you will know exactly which kind of information security standards/policies/procedures you will need to implement. See this article for details: The basic logic of ISO 27001: How does information security work? https://advisera.com/27001academy/knowledgebase/the-basic-logic-of-iso-27001-how-does-information-security-work/
To get the support of your management you need to apply the techniques in this article: Four key benefits of ISO 27001 implementation https://advisera.com/27001academy/knowledgebase/four-key-benefits-of-iso-27001-implementation/
To see all the detailed steps in the implementation see this article: ISO 27001 implementation checklist https://advisera.com/27001academy/knowledgebase/iso-27001-implementation-checklist/ -
Regrading Security Framework
If you want to implement security framework according to ISO 27001, you'll find the implementation steps here: ISO 27001 implementation checklist https://advisera.com/27001academy/knowledgebase/iso-27001-implementation-checklist/
The sections/controls you need to implement depend on the results of the risk assessment - see an explanation here: The basic logic of ISO 27001: How does information security work? https://advisera.com/27001academy/knowledgebase/the-basic-logic-of-iso-27001-how-does-information-security-work/
For better understanding of the risk treatment plan, see this article: Risk Treatment Plan and risk treatment process Whats the difference? https://advisera.com/27001academy/iso-27001-risk-assessment-treatment-management/#treatment -
Confidentiality, integrity and availability in the risk assessment
Reading the standard it says; 6.1.2 c) Apply the information security risk assessment process to identify risks associated with the loss of confidentiality, integrity and availability for information within the scope of the information security management system
Should I actually record the CIA or just consider each and decide on a consequence/likelihood rating?
Answer: Neither 2005 nor 2013 revision of ISO 27001 require you to assess confidentiality, integrity or availability as a separate valuation, nor do they require you to assess C, I and A separately from the impact, nor do they require you to explicitly identify the relationship between the risk and the C, I, or A. ISO 27001 simply requires you to identify the risk.
Actually, when you look closely, loss of confidentiality, integrity and availability is nothing else but asse ssing the impact. Therefore, you can (a) assess the impact taking into consideration the highest loss from either C, I or A, or (b) you can assess the impact separately for C, for I, and for A. -
ISO 22301 certification
There is a difference between accreditation bodies and certification bodies: certification bodies issue certificates to companies, while accreditation bodies are government agencies which give approvals (accreditations) to certification bodies.
Therefore, UKAS provides accreditations not only for ISO 9001 but also for ISO 22301 and other standards. You should check https://www.ukas.com to see which certification bodies have they accredited.
In the United States the accreditation body is ANAB https://www.anab.org. -
Status of controls
ISMS manual is not a required document; however ISO 27001:2013 clause 6.1.3 d) requires you to identify the status of each control in your Statement of Applicability.
These articles will help you:
Is the ISO 27001 Manual really necessary? https://advisera.com/27001academy/blog/2014/02/03/is-the-iso-27001-manual-really-necessary/
The importance of Statement of Applicability for ISO 27001 https://advisera.com/27001academy/knowledgebase/the-importance-of-statement-of-applicability-for-iso-27001/ -
A clarification on risk assessment/ treatment
ISO 27001:2013 does not require you to comply with ISO 31000, nor with ISO 27005 when performing your risk assessment - basically, you have to create your own risk assessment methodology (compliant with ISO 27001) that suits your company.
See also these articles:
How to write ISO 27001 risk assessment methodology https://advisera.com/27001academy/knowledgebase/write-iso-27001-risk-assessment-methodology/
ISO 31000 and ISO 27001 How are they related? https://advisera.com/27001academy/blog/2014/03/31/iso-31000-and-iso-27001-how-are-they-related/ -
What is cybersecurity?Interpreting the control A.8.1.1
You'll find the answer here: https://community.advisera.com/topic/iso-27001-2013-amended-version/ -
What is cybersecurity?
Although this distinction is not yet clearly established, I would say that cybersecurity deals only with digital information, while information security deals also with information in other media (e.g. paper).
See also this article: What is cybersecurity and how can ISO 27001 help? https://advisera.com/27001academy/blog/2011/10/25/what-is-cybersecurity-and-how-can-iso-27001-help/ -
ISO 22301 Implementation
You can implement ISO 22301 without ISO 27001 rather easily - although these two standards are highly compatible, they can be implemented separately without bigger problems.
These materials will help you:
article 17 steps for implementing ISO 22301 https://advisera.com/27001academy/knowledgebase/17-steps-for-implementing-iso-22301/22301/iso-22301/
webinar ISO 22301: An overview of BCM implementation process https://advisera.com/27001academy/webinar/iso-22301-overview-bcm-implementation-process-free-webinar/ -
Asset Identification
William,
ISO 27005 is not a mandatory standard, it is only a guideline that you may or may not choose to follow; the only relevant requirements for risk assessment are those written in ISO 27001.
ISO 27001 does not require classification in primary and secondary assets, and in our view such classification may be misleading - this is why we did not recommend such approach in our templates. For instance, I do not think that your core software is more important as an asset than your system administrator - they are both very valuable for the company, and they both carry very high risks.
To answer your question, I think that you should identify threats and vulnerabilities for all of your assets, no matter how you classify them. However, ISO 27001 does allow you the flexibility to define your own methodology, which means that in theory, you could use some simplified risk identification method for "secondary" assets.