Answer: The level of details to be included in a risk assessment will depend upon the context of the organization. The industry where the organization operates, the laws and regulations which it must comply, and the complexity of its products and services are the main aspects that will define which details you should consider. For example, aviation industry requires a high level of security, and risk details should provide enough information so the risks can be properly handled.
Answer: While SOC has the purpose to assist in reporting to customers that an organization has met established security criteria, ISO 27001 assists an organization in a broader way, by providing a framework which helps to ensure security criteria and controls that are established according organizations needs, and that they are properly verified and improved over the time. So, in a way, SOC is covered by ISO 27001, and you might tell them that by adopting ISO 27001 they will not only cover the reporting aspects of SOC but also will be able to justify any adjustments required by the business needs as well as respond properly to changes in the risk scenario and ineffective controls.
Answer: The main point you should consider to include or not the business process description and scoping as a deliverable in your ISO implementation is if there are other projects or initiatives under way, or in the near future, that will require business process description and scoping (e.g., a information system development, or processes' re-engineering). Depending upon the scope of these other projects, it may be better to treat business process description and scoping as a separated project that will provide input for your ISO implementation. If this is not the case, you may include the business process description and scoping as a deliverable in your project, reducing the administrative load to run two projects.
This article will provide you further explanation about ISO 27001 project:
- ISO 27001 project – How to make it work https://advisera.com/27001academy/knowledgebase/iso-27001-implementation-checklist/
These materials will also help you regarding ISO 27001 project:
- Book Secure & Simple: A Small-Business Guide to Implementing ISO 27001 On Your Own https://advisera.com/books/secure-and-simple-a-small-business-guide-to-implementing-iso-27001-on-your-own/
- Free online training ISO 27001 Foundations Course https://advisera.com/training/iso-27001-foundations-course/
Financial benefits of ISO 27001
Some examples of how the right kind of software can help decrease operational costs are:
increasing the number of automatized activities (i.e., fewer people required to perform the same number of tasks)
improving response time to handle incidents or deviations in processes results (by means of monitoring features)
providing information for decision making (by means of standard or customized reports and dashboards)
Answer: Yes. Provided that the mandatory topics are addressed (e.g., results of tests, controls performance, etc.) and it is possible to identify a periodicity in the conduct of the meetings, there is no mandatory form for holding meetings.
2 - Can CFST meetings be replacement for BCC?
Answer: If for BCC you refer to Business Continuity Coordinator, this meeting cannot be a replacement. BCC is a function, while the meeting is an activity, so there must be an person in the meeting with the responsibilities of the BCC.
In any case, I think the answer is probably somewhere in between, and it’s maybe a shared ownerships. We’re attempting to draw clear boundaries though in terms of who does what, and I was wondering if you’ve ever seen a RACI chart of the various activities that are involved in certification. This would help us to create clear areas of responsibility, but in the end I still believe that security should ultimately “own” this as it’s an information security standard.
Answer: Your assumption about shared responsibilities is right. ISO 9001 and ISO 27001 share a lot of clauses that can be both management by the security team as well as the quality team, and this is cl earer now with the new structure of ISO management standards. I particularly never saw a RACI chart in the way you are asking, but who is ultimately responsible for the ISMS/ISO 27001 project is typically someone responsible for security, generally the CISO (Chief Information Security Officer). Regarding other responsibilities, by following the new structure of ISO management standards, you could consider this:
4. Context of the organization - since in this case the context aims to issues that can prevent the ISMS to achieve its desired outcomes, security team should be accountable for the deliverables related to it (e.g., ISMS scope).
5. Leadership - Security team should be accountable for the information security policy elaboration and definition of security responsibilities, as well as ensuring top management commitment to information security. The quality team should be accountable for the integration of security processes to other organizational processes.
6. Planning - This section refers to information risk management and the security team should be accountable for the deliverables related to this section.
7. Support - Quality team should be accountable for almost all this section (e.g., provision of resources and competences), the exception to communications, because this is related to what, when, to whom, and by whom information security issues should be communicated.
8. Operation - The day to day security activities should be held accountable by the security team and those with defined in the procedures.
9. Performance evaluation - These processes could be integrated to the processes already managed by the quality team, so this team could be held accountable.
10. Improvement - These processes also could be integrated to the processes already managed by the quality team, so this team could be held accountable.
In short, common processes and deliverables already implemented by ISO 9001, like internal audit, control of documents and records, and management review could be designated to the quality team, and those specific related to information security could be designated to security team, but it is important to note that for the processes managed by the quality team, the security team becomes a interested party that should be listened.
Can asset list consists of asset as office networks or it has to be segregated into further components/devices.
How often should the controls be audited
1. Do we need to annually test every control that is in scope in the SoA? Or do we do this over a 3 year period?
Answer: If your question is about internal audit, then it would be better if you audit all controls each year, but you can also do it in the 3-year period. If your question was about control A.14.2.8 System security testing or A.12.6.1 Management of technical vulnerabilities (which could also include e.g. pen tests), those activities should be performed continuously or at least periodically, but certainly not only once in 3 years.
2. How should we best structure our audit plan? Should the audit scope reflect the department or the control objectives being reviewed? For example I could see it would make sense for the audit scope in the plan to be 8 Asset management and then using the checklist provided we can assign the specific tests and responsibilities to the auditors. I could then make up an annual checklist for each control area. What do you think?
Answer : You can do it both ways - by controls or by departments. If the auditor has more experience, it is probably better to do it by department; if he/she has less experience, then it will be easier by controls.