Guest
Guest
Create New Topic As guest or Sign in
Assign topic to the user
-
Statement of Applicability for network security
Within ISO 27001 we have an SOA which states the controls for IS. Does an SOA for Network Security Exist? -
Narrow ISMS scope and an Information Security policy for the whole organization
We are working towards the transition to ISO 27001:2013 , but they are having problems trying to understand this: We are writing a new Information Security Policy to be used for the whole organization, but I like to keep the ISMS scope just for one system, the one thats is required to be certified ISO 27001. Is this possible?, Can we have a narrow ISMS scope but an Information Security policy for the whole organization? The SoA is extended to include all controls in the annex A, here is my problem, I like to keep the SoA aligned with the scope and they want to all controls marked as applicable even if they are not used in the system in the scope. -
What will the ISO 22301 certification auditor check?
When I want to certify my company on ISO 22301, the auditor will check only the mandatory documents (apendix B of your book) or the total list of documents (mandatory and non-mandatory)? -
What RTO means ?
We've received the following question:
#1. The Recovery Time Objective (RTO) - is a maximum amount of time within which an activity needs to be resumed at the MBCO level (Minimum business continuity objective), or
#2. The Recovery Time Objective (RTO) - is a maximum amount of time within which an activity needs to be resumed at the full capacity.
The recovery time objective is the target time set for resumption of product, service or activity delivery after an incident. RTO is determined during the business impact analysis (BIA), and the preparations are defined in the business continuity strategy, so this means that option #1 is the correct one.
Please have a look on the following link for further explanation.
https://advisera.com/27001academy/knowledgebase/what-is-the-difference-between-recovery-time-objective-rto-and-recovery-point-objective-rpo/
Thanks -
How to document System Secure Engineering Principles
We've received the following question: I want to know how to document System Secure Engineering Principles? What is the Content for that? Answer: System Secure Engineering Principles refers to the set of security techniques in all architectural layers business, data, applications and technology you are using in your organization. Those principles shall be documented in a policy and regularly reviewed. As an example you should look on the Software Development LifeCycle phases and define the set of security techniques in each phase: - Project initiation and planning; - Functional requirements definition; - Systems design specifications; - Build (develop) and document - Acceptance - Transition to production (instalation) These set of considerations shall also be applied to outsourcers where applicable, using contracts and other binding agreements between parties. Hope it helps -
How much of business continuity to implement in ISO 27001
I've received this question: When implementing ISO 27001, how deep we have to go in Business Continuity (16)?. Is it the same as implementing a hole Business Continuity Project, or something lighter?.
Answer: When implementing business continuity according to ISO 27001, you could implement a "lighter" version that would focus only on developing a disaster recovery plan (for recovering your IT infrastructure), and a recovery plan for your information security functions. This means you do not have to implement the whole business continuity project according to ISO 22301.
However, I would argue that it would make much more sense to implement a full business continuity project according to ISO 22301 as part of your ISO 27001 project - this is because of the following:
1) This would add perhaps only 10% of additional effort to your ISO 27001 project
2) You would implement two standards (both ISO 27001 and ISO 22301) with only little additional cost
3) You can ensure the continuity of your business operations only by doing this full business continuity project - complying wi th the minimum that is set in ISO 27001 wouldn't be enough.
You can find out more in this webinar: ISO 27001 & ISO 22301: Why is it better to implement them together? https://advisera.com/27001academy/webinar/iso-27001iso-22301-certification-process-free-webinar-demand/
By the way, ISO 27001:2013 defines the controls for business continuity in Annex A, section A.17. -
ISO 27001 maintenance mode after implementation mode
We've received the following question: We recently achieved our ISO certification on Friday last - the 28 Feb. However I have been looking on your blog to find out what is the process -if any- to transition from implementation mode to maintenance mode and if there are any critical items that need to be closed off/completed before this can happen? We are still keenly in ISO operational mode and are now looking at including the rest of the business in scope (we had a limited scope initially) but at present we want to wind down activity and e.g reduce the frequency and attendance of the ISMS team meetings and suchlike. Are there any guidelines for what should still happen post audit while leaving the implementation phase behind and how to get into that mode? Answer: Regarding your description I can assume that you already sent to the certification body the CAP (Corrective Action Plan) to the non conformities arised during the audit, because this is the most critical item. The actions you mentioned in CAP should be treated in accordance with the scheduled timeframe yo u refered in the document. If you had no nonconformity you shouldn't be required to send a Corrective Action Plan. To get "in maintenance mode after implementation mode" it is just following the policies, processes, procedures and controls you've just included in your system and get the focus in the performance of the indicators you have selected, completing the PDCA cycle. If your team is motivated and you have the management commitment to include the rest of the business in the scope, please proceed in that way and increase the maturity level of the system. Thanks -
Internal and external issues and interested parties in ISO 27001
I've received this question: Can you help me to find the "internal and external issue" and the "interested parties" in order to understanding the my organization's context for iso 27001? Answer: Internal issues and external issues will be mostly discovered during the risk assessment process and by identifying interested parties, so in my opinion you don't have to do much more than that. If you want to do additional step, then you can perform the SWOT analysis (Strengths-Weaknesses-Opportunities-Threats), and PEST analysis (Political-Economical-Social-Technological impacts). To identify interested parties, you need to see who can influence the confidentiality, integrity and availability of your information, or who will be influenced by your activities. Normally, these include your customers, partners, government agencies, local community, employees, shareholders, etc. -
Where to start with education and how to prepare
We've received the following question: "I am considering to complete the exams related to 22301 and 27001 As far as I can see there is lead auditor and lead implementer certifications for both standards. Im not sure what the foundation certification is all about but maybe you can tell me if it is needed and why? I believe my best option is to start reading some course material or books prior to the course and the exam. Could you tell me which books/material you would recommend to give me the best probability to qualify for the exam and if you are able to provide them?" Answer: Regarding certification the Foundation approach is the first step to get inside this subject giving a general overview about the aspects of the standards while the Lead Implementer is a deeper approach for those who want to implement this systems using a systemic approach to all the requirements. Lead Auditor is for those who want to become auditors of the system providing guidance on the standard as well as on how to perform audits. Regarding the materials you should have a look on the following links https://advisera.com/27001academy/webinar/become-iso-27001-bs-25999-2-consultant-free-webinar/ https://advisera.com/27001academy/blog/2010/11/30/how-to-learn-about-iso-27001-and-bs-25999-2/ Also you can have a look on the ebook https://advisera.com/books/becoming-resilient-the-definitive-guide-to-iso-22301-implementation/ Many thanks -
ISO 27005 or ISO 31000
We've received the following question: I did risk assessment/management programs but my approach was identify assets, then threats...so on. I read new version does not recommend this approach of identifying asset n so on but they recommend to find risk in associated with the env environment and so on... Answer: In fact there no specif requirement on that approach but there is still a requirement on assets inventory and in order to control those assets, it is good practice to address threats and vulnerabilities on those assets, so you can follow ISO 27005 approach. The new risk approach alignment sugestion in 2013 version has a wider coverage and give the opportunity to the organization to address the context risks of the business, providing lines of thought for internal and external issues that are relevant for the business. ISO 27005 is more focused in Information Security and ISO 31000 is a framework that can be used to address those internal and external issues as well as Information security. In the new version you can used the approach that may suite better for your needs. As a detailed methodology for Information Security Risk Management, ISO 27005 is more practicable, than ISO 31000, on the other hand, ISO 31000 provides a better guidance on addressing the context analysis. So it is up to your organization on choosing any of the approaches or even both. Hope it helps Thanks