Would like some clarifications for the below query
I see in the standard the use of terms such as
- Suppliers ( A15 )
- Contractors ( A.16.1.3 )
- External parties ( A5.1.1 )
- Interested parties
Answer:
All these terms are related to the same thing (although a supplier is an entity that gives you a service, and contractors can be individual external persons that works in your company): Interested parties, and what is it? Basically an interested party can be persons or organizations that can influence your information security business continuity. For more information about interested parties you can read this article How to identify interested parties according to ISO 27001 and ISO 22301 : https://advisera.com/27001academy/knowledgebase/how-to-identify-interested-parties-according-to-iso-27001-and-iso-22301//
Análisis de riesgos en un Data Center
Claro, este es tu sitio, aquí encontrarás mucha información y podrás preguntarnos todas tus dudas. En relación al riesgo del Data Center, necesitas una metodología y después necesitas realizar un análisis/tratamiento de riesgos. Una cosa importante: Hay que diferenciar entre análisis de riesgo y tratamiento de riesgo. Aquí encontrarás más información sobre esto: ISO 27001 risk assessment & treatment 6 basic steps": https://advisera.com/27001academy/knowledgebase/iso-27001-risk-assessment-treatment-6-basic-steps/
If you want to evaluate risks, the more important thing is to identify threats/vulnerabilities related to each asset, and you can consider current security controls, but in this case it is not necessary (or not mandatory by the standard) to have documents for the operation of these current security controls. When you will need to document the operation or practices is with the implementation of the security controls (risk treatment). For more information about the risk assessment, please read this article ISO 27001 risk assessment: How to match assets, threats and vulnerabilities": https://advisera.com/27001academy/knowledgebase/iso-27001-risk-assessment-how-to-match-assets-threats-and-vulnerabilities/
Finally, in this article you will find a list of mandatory (and not mandatory) documents List of m andatory documents required by ISO 27001 (2013 revision)": https://advisera.com/27001academy/knowledgebase/list-of-mandatory-documents-required-by-iso-27001-2013-revision/
Implementacion ISO 27001
Podemos ayudarte en la implementación de la ISO 27001 en tu organización, porque tenemos un toolkit con toda la documentación necesaria y además podemos darte soporte durante la implementación de los documentos. Si estás interesado en nuestras plantillas, puedes ver una versión gratuita aquí clickeando en la pestaña "Demostración gratis"
Does all the Policies and procedured need to be in Word/PDf format?
The standard ISO 27001 does not establish the format of the documents, but we recommend you to use always the same format at least for the procedures (and Excel for records). Anyway, if you want to have a procedure or a policy in Excel format it is not a problem for the standard.
I assume you are referring to our ISMS Scope template? If yes, we have suggested to leave out the employee equipment (that is not owned by the company) - e.g. laptops, mobile phones - because this equipment is used also for the private purposes. For such equipment it is much easier to regulate the use with a BYOD Policy - in such way, you can apply security rules to such equipment even if it is outside of the scope of your ISMS.
If you want to include such equipment in the scope, you do not have to list it in the ISMS Scope document - you should simply list all the processes, departments and locations that are included in the scope.
Yes, absolutely, you can perform a revision after the implementation and update the state of all security controls in the SoA. Finally, I think that it is interesting to know the importance of the SoA, so please read this article "The importance of Statement of Applicability for ISO 27001":
And if your question is related to the use of a class of asset called "workstation", you also can include a type of asset "workstation" in your methodology, but I think that it is not a good idea, because a workstation, from the point of view of the information security, can be very similar to a server, so it is better to establish a superior level for both.
Maintenance of the ISMS
I am in a relatively small (around 80 people) software company that already has the 27001 certification and am in a brand new position as Process Innovation Analyst where I have to make sure the certification is updated, improved, etc.
If you have any suggestions as to how to go about making a proper maintenance of the certification I would really appreciate it.
Answer:
It is very important for us to know that our documentation can help you, we appreciate your feedback. One question, Do you have made the update to the new ISO 27001:2013? It is very important. Regarding to the maintenance, the important things is to perform each year the internal audit, management support, measure with your defined indicators, perform test to the business continuity plan, perform meetings to deal with questions related to the ISMS, review the information security policy, define new information security objectives, perform the risk assessment & treatment, etc.
For more information about the maintenance of the ISMS, please read this article How to maintain the ISMS after the certification : https://advisera.com/27001academy/blog/2014/07/14/how-to-maintain-the-isms-after-the-certification/