my question is about opportunity in clause 6 of ISO 27k it seems no clear for me to develop it
second did we need to develop process for our ISMS ?
Answer:
I am sorry but I am not sure if I have understood your questions. Regarding the clause 6, I suppose that you mean “6.1 Actions to address risks and opportunities”, if so, risks and opportunities are related to the objectives, and any action that you take that is related to the achievement of the security objectives, but is not related to the risk management, can be considered to be addressing the opportunities (An example related to an opportunity: Your organization buy a cheap firewall which gives your organization the opportunity to reduce risks, but it can produce increased risks due to low quality of the device). You can document such actions in your Management review minutes, corrective actions, or any other records or documents that you use in your company.
Regarding the process for your ISMS, again I am not sure what you mean, but really a process is a set of interrelated or interacting activities which transforms inputs into outputs, so in accordance with this you can define the process that you want to implement the ISMS (some examples: information security risk assessment process, risk treatment process, audit process, etc).
quite easily formalise additional roles if it needed. One single person might have more than one role.
Answer:
For such a small company you basically need only one additional role - a person who will coordinate the implementation of ISO 27001 (i.e. project manager), and this person can be at the same time the security manager (i.e. CISO). Of course, these roles can be performed by some of your existing employees, probably someone from the top management (it will take him/her perhaps 20% of the time).
All the other security roles will be included in the responsibilities of existing employee s/managers - e.g. for passwords or for the backup, the responsible person will be the person in charge of the IT. You should formalize those responsibilities throughout various ISMS policies and procedures.
soy estudiante de seguridad informatica y quiero implementar un SGSI de la seguridad informatica a una empresa, por eso quiero capacitarme en esta norma y lo que tenga que ver para asegurar la informacion . quedo atento de su comentarios, si es posible hablar con el asesor es mucho mejor, no hablo ingles.
Respuesta:
Antes de nada, aclarar que la seguridad de la información no es lo mismo que la seguridad informática, es muy importante tener claro esta distinción: la seguridad de la información básicamente está relacionada con la protección de la información (es un término genérico, e incluye, entre otras cosas, la seguridad informática), y la seguridad informática básicamente está relacionada con TI (servidores, hacking, etc). Por tanto, un SGSI está relacionado con la seguridad de la información.
Y si eres nuevo en seguridad de la información, nuestros recursos te ayudarán a aprender más sobre la ISO 27001, por tanto, por favor visita estos enlaces:
Por último, recordarte que nosotros tenemos un paquete de documentos que contiene todo lo necesario para implementar la ISO 27001, el cual puedes encontrar en español aquí (puedes descargarte una versión gratuita pulsando en el botón "DESCARGAR DEMOSTRACIÓN GRATIS"):
I need to get some good guidance on internal auditing for ISO 27001 as I am tasked with internal auditing as we have almost completed our development of ISMS.
If you have any tips/training videos etc for internal auditing of SOA/controls that would be very timely for me.
Although you can also use our template for the checklist (you can see a free version clicking on “Free Demo” tab), which has questions related to all clauses and controls of ISO 27001 that you can use during the internal audit “Internal Audit Checklist” : https://advisera.com/27001academy/documentation/internal-audit-checklist/
Aspect and Impact Analysis in the new version (2015)
Answer:
New version of ISO 14001 did not bring many changes regarding identification and evaluation of environmental aspects and impacts. However there is now emphasis to take into account the changes in processes, activities and products or services when conducting the evaluation as well as abnormal conditions and reasonably foreseeable emergency situations.
So if you took into account these two topics, you can keep your old evaluation as still valid. You only need to adapt your procedure to align it with the new version of the standard.
How similar are 22301 and SOC II? We are already doing SOC II. Will we be able to leverage some of the work we've done for SOC II for 22301?
Answer:
SOC II has some points where speaks about availability (references CC3.3 and A1.1 in SOC 2), system recovery, recovery plans (references A1.1, A1.2, A1.3 in SOC 2), etc. Which are directly related to ISO 22301 (mainly with the section 8), although ISO 27001 has more common points with SOC II. So, if you have implemented SOC II, the implementation of ISO 27001 will be more easy that ISO 22301 (although ISO 22301 will be also easy).
By the way, as you know, you can implement ISO 27001 and ISO 22301 together, and the integration with SOC II would be also very easy.
ISO 27001 and HITRUST
How does it relate to HITRUST? I am getting ready to start an accreditation
Answer:
Sincerely I am not an expert in HITRUST, but it is related to the information security in health information systems environments, and ISO 27001 is an international standard (also has similarities with HIPAA), and is related to information security, so probably can help you to implement the Common Security Framework (CSF) of HITRUST, because there are common areas.
By the way, ISO 27799, which is similar to ISO 27001, is an international standard that also focus on information security for health organizations.
My organization can be certified by ISO 27001?
Kindly advise me if our organisation can be certified by ISO/IEC 27001 or not and do advise me if not which certification is better for our organisation. Below is our company details
Answer:
Yes, of course. ISO 27001 is developed for any type of business, included the sector of Network & Security, Software & Website development, so you can certify your organization. Obviously, if you want to certify ISO 27001, first you need to implement it, so maybe this free webinar can be interesting for you “ISO 27001: An overview of the ISMS implementation process” : https://advisera.com/27001academy/webinar/iso-27001-overview-isms-implementation-process-free-webinar-demand/
Keep in mind that many of our clients are IT companies.
I am working on a ISO 27001. The company is using email for many purposes. They are using to exchange some confidential records / documents internally and also with external parties. Just wanna know what type of control should be put on e-mail . Encryption for outlook is not very easy.
Could you please advise ?
Answer:
In ISO 27001 you can implement the solution that you want to protect the confidential information, and there are many options. In your specific case, if the information transferred are files, you can encrypt these files with utilities software (for example AES Crypt, which is free), and you can send the encrypt file through email. Maybe this option can be more easy for you that configure Outlook to encrypt the emails, although it is also a good and a very common option.
If the information transferred is only text, maybe you can include the text in a Microsoft Word, encrypt the file and send it in the same way that I said before.
By the way, the control in the Annex A of ISO 27001 related to emails is the 13.2.3 Electr onic messaging, although here is not mandatory to encrypt the information, but is very recommendable, because you need to ensure the protection of the information from unauthorized access.
How to prepare a procedure to identify and quantify the information security incidents based on their type, volume and costs.
Control No.13.2.2- Learning from information security incidents.
Answer:
For the preparation of this procedure you can include information about the notification of the incident, classification of the incident, treatment of the incident, close the incident and knowledge base (these are also the main steps for the management of incidents). This article related to steps of the management of information security incidents, responsibilities, and classifications (based on the impact and the urgency of the incident, by the way, the impact can be related to costs), can be also interesting for you “How to handle incidents according to ISO 27001 A.16” : https://advisera.com/27001academy/blog/2015/10/26/how-to-handle-incidents-according-to-iso-27001-a-16/
By the way, the control 13.2.2 is related to the previous version of ISO 27001 (published in 2005), which is obsolete. The current version of the standard is the ISO 270 01:2013 and the control related to “Learning from information security incidents” is the A.16.1.6. This article can be interesting for you “How to make a transition from ISO 27001 2005 revision to 2013 revision” : https://advisera.com/27001academy/knowledgebase/how-to-make-a-transition-from-iso-27001-2005-revision-to-2013-revision/
Regarding the procedure, you can use our template for the management of information security incidents according to ISO 27001:2013 A.16.1.6, you can see a free version clicking on “Free Demo” tab here “Incident Management Procedure” : https://advisera.com/27001academy/documentation/Incident-Management-Procedure/